Cisco ONS 15310-CL and Cisco ONS 15310-MA Procedure Guide, Release 8.5.4

DLPs C200 to C299

DLP-C200 Provision OSI Routing Mode

Caution Do not complete this task until you confirm the role of the node within the network. It will be either an ES or IS Level 1. This decision must be carefully considered. For additional information about OSI provisioning, refer to the "Management Network Connectivity" chapter of the Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual.

Caution Link State Protocol (LSP) buffers must be the same at all NEs within the network, or loss of visibility might occur. Do not modify the LSP buffers unless you confirm that all NEs within the OSI have the same buffer size.

Caution LSP buffer sizes cannot be greater than the LAP-D maximum transmission unit (MTU) size within the OSI area.

Note The ONS 15310 primary NSAP address is also the Router 1 primary manual area address. To edit the primary NSAP, you must edit the Router 1 primary manual area address. After you enable Router 1 on the Routers subtab, the Change Primary Area Address button is available to edit the address.

Step 1 In node view, click the Provisioning > OSI > Main Setup tabs.

Step 2 Choose a routing mode:

•End System—The ONS 15310 performs OSI end system (ES) functions and relies upon an intermediate system (IS) for communication with nodes that reside within its OSI area.

Note The End System routing mode is not available if more than one virtual router is enabled.

•Intermediate System Level 1—The ONS 15310 performs OSI IS functions. It communicates with IS and ES nodes that reside within its OSI area. It depends upon an IS L1/L2 node to communicate with IS and ES nodes that reside outside its OSI area.

Step 3 If needed, change the L1 LSP Buffer Size. This adjusts the Level 1 link state protocol data unit (PDU) buffer size. The default is 512. It should not be changed.

Step 4 Return to your originating procedure (NTP).

DLP-C201 Provision or Modify TARP Operating Parameters

Step 1 In node view, click the Provisioning > OSI > TARP > Config tabs.

Step 2 Provision the following parameters, as needed:

•TARP PDUs L1 Propagation—If checked (default), TARP Type 1 PDUs that are received by the node and are not excluded by the LDB are propagated to other NEs within the Level 1 OSI area. (Type 1 PDUs request a protocol address that matches a target identifier [TID] within a Level 1 routing area.) The propagation does not occur if the NE is the target of the Type 1 PDU, and PDUs are not propagated to the NE from which the PDU was received.

Note This parameter is not used when the Node Routing Area (Provisioning > OSI > Main Setup tab) is set to End System.

•TARP PDUs Origination—If checked (default), the node performs all TARP origination functions including:

–TID to Network Service Access Point (NSAP) resolution requests (originate TARP Type 1 and Type 2 PDUs)

–NSAP to TID requests (originate Type 5 PDUs)

–TARP address changes (originate Type 4 PDUs)

Note TARP Echo is not supported.

•TARP Data Cache—If checked (default), the node maintains a TARP data cache (TDC). The TDC is a database of TID to NSAP pairs created from TARP Type 3 PDUs received by the node and modified by TARP Type 4 PDUs (TID to NSAP updates or corrections). TARP 3 PDUs are responses to Type 1 and Type 2 PDUs. The TDC can also be populated with static entries entered on the TARP > Static TDC tab.

Note This parameter is only used when the TARP PDUs Origination parameter is enabled.

•LDB—If checked (default), enables the TARP loop detection buffer. The LDB prevents TARP PDUs from being sent more than once on the same subnet.

Note The LDP parameter is not used if the Node Routing Mode is provisioned to End System or if the TARP PDUs L1 Propagation parameter is not enabled.

•LAN TARP Storm Suppression—If checked (default), enables TARP storm suppression. This function prevents redundant TARP PDUs from being unnecessarily propagated across the LAN network.

•Send Type 4 PDU on Startup—If checked, a TARP Type 4 PDU is originated during the initial ONS 15310 startup. Type 4 PDUs indicate that a TID or NSAP change has occurred at the NE. (The default setting is not enabled.)

•Type 4 PDU Delay—Sets the amount of time that will pass before the Type 4 PDU is generated when Send Type 4 PDU on Startup is enabled. 60 seconds is the default. The range is 0 to 255 seconds.

Note The Send Type 4 PDU on Startup and Type 4 PDU Delay parameters are not used if TARP PDUs Origination is not enabled.

•LDB Entry—Sets the TARP loop detection buffer timer. The LDB buffer time is assigned to each LDB entry for which the TARP sequence number (tar-seq) is zero. The default is 5 minutes. The range is 1 to 10 minutes.

•LDB Flush—Sets the frequency period for flushing the LDB. The default is 5 minutes. The range is 0 to 1440 minutes.

•T1—Sets the amount of time to wait for a response to a Type 1 PDU. Type 1 PDUs seek a specific NE TID within an OSI Level 1 area. The default is 15 seconds. The range is 0 to 3600 seconds.

•T2—Sets the amount of time to wait for a response to a Type 2 PDU. TARP Type 2 PDUs seek a specific NE TID value within OSI Level 1 and Level 2 areas. The default is 25 seconds. The range is 0 to 3600 seconds.

•T3—Sets the amount of time to wait for an address resolution request. The default is 40 seconds. The range is 0 to 3600 seconds.

•T4—Sets the amount of time to wait for an error recovery. This timer begins after the T2 timer expires without finding the requested NE TID. The default is 20 seconds. The range is 0 to 3600 seconds.

Note Timers T1, T2, and T4 are not used if TARP PDUs Origination is not enabled.

Step 3 Click Apply.

Step 4 Return to your originating procedure (NTP).

DLP-C202 Add a Static TID to NSAP Entry to the TARP Data Cache

Step 1 In node view, click the Provisioning > OSI > TARP > Static TDC tabs.

Step 2 Click Add Static Entry.

Step 3 In the Add Static Entry dialog box, enter the following:

•TID—Enter the TID of the NE. (For ONS nodes, the TID is the Node Name parameter on the node view Provisioning > General tab.)

•NSAP—Enter the OSI NSAP address in the NSAP field or, if preferred, click Use Mask and enter the address in the Masked NSAP Entry dialog box.

Step 4 Click OK to close the Masked NSAP Entry dialog box, if used, and then click OK to close the Add Static Entry dialog box.

Step 5 Return to your originating procedure (NTP).

DLP-C203 Remove a Static TID to NSAP Entry from the TARP Data Cache

Step 1 In node view, click the Provisioning > OSI > TARP > Static TDC tabs.

Step 2 Click the static entry that you want to delete.

Step 3 Click Delete Static Entry.

Step 4 In the Delete TDC Entry dialog box, click Yes.

Step 5 Return to your originating procedure (NTP).

DLP-C204 Add a TARP Manual Adjacency Table Entry

Step 1 In the node view, click the Provisioning > OSI > TARP > MAT tabs.

Step 2 Click Add.

Step 3 In the Add TARP Manual Adjacency Table Entry dialog box, enter the following:

•Level—Sets the TARP Type Code that will be sent:

–Level 1—Indicates that the adjacency is within the same area as the current node. The entry generates Type 1 PDUs.

–Level 2—Indicates that the adjacency is in a different area than the current node. The entry generates Type 2 PDUs.

•NSAP—Enter the OSI NSAP address in the NSAP field or, if preferred, click Use Mask and enter the address in the Masked NSAP Entry dialog box.

Step 4 Click OK to close the Masked NSAP Entry dialog box, if used, and then click OK to close the Add Static Entry dialog box.

Step 5 Return to your originating procedure (NTP).

DLP-C205 Provision OSI Routers

Note The Router 1 manual area address, System ID, and Selector "00" create the node NSAP address. Changing the Router 1 manual area address changes the node's NSAP address.

Note The System ID for Router 1 is the node MAC address.

Step 1 In node view, click the Provisioning > OSI > Routers > Setup tabs.

Step 2 Chose the router you want provision and click Edit.

Step 3 In the OSI Router Editor dialog box:

a. Check Enable Router to enable the router and make its primary area address available for editing.

b. Click the manual area address, then click Edit.

c. In the Edit Manual Area Address dialog box, edit the primary area address in the Area Address field. If you prefer, click Use Mask and enter the edits in the Masked NSAP Entry dialog box. The address (hexadecimal format) can be 8 to 24 alphanumeric characters (0-9, a-f) in length.

d. Click OK successively to close the following dialog boxes: Masked NSAP Entry (if used), Edit Manual Area Address, and OSI Router Editor.

Step 4 Return to your originating procedure (NTP).

DLP-C206 Provision Additional Manual Area Addresses

Step 1 Click the Provisioning > OSI > Routers > Setup tabs.

Step 2 Chose the router where you want provision an additional manual area address and click Edit. The OSI Router Editor dialog box appears.

Step 3 In the OSI Router Editor dialog box:

a. Check Enable Router to enable the router and make its primary area address available for editing.

b. Click the manual area address, then click Add.

c. In the Add Manual Area Address dialog box, enter the primary area address in the Area Address field. If you prefer, click Use Mask and enter the address in the Masked NSAP Entry dialog box. The address (hexadecimal format) can be 2 to 24 alphanumeric characters (0-9, a-f) in length.

d. Click OK successively to close the following dialog boxes: Masked NSAP Entry (if used), Add Manual Area Address, and OSI Router Editor.

Step 4 Return to your originating procedure (NTP).

DLP-C207 Enable the OSI Subnet on the LAN Interface

Note OSI subnetwork points of attachment are enabled on DCCs when you create DCCs. See the "DLP-C52 Provision Section DCC Terminations" task on page 17-68 and the "DLP-C53 Provision Line DCC Terminations" task on page 17-70.

Note The OSI subnetwork point of attachment cannot be enabled for the LAN interface if the OSI routing mode is set to ES (end system).

Note If Secure Mode is on, the OSI Subnet is enabled on the backplane LAN port, not the front TCC2P port.

Step 1 In node view, click the Provisioning > OSI > Routers > Subnet tabs.

Step 2 Click Enable LAN Subnet.

Step 3 In the Enable LAN Subnet dialog box, complete the following fields:

•ESH—Sets the End System Hello (ESH) propagation frequency. End system NEs transmit ESHs to inform other ESs and ISs about the NSAPs it serves. The default is 10 seconds. The range is 10 to 1000 seconds.

•ISH—Sets the Intermediate System Hello PDU propagation frequency. Intermediate system NEs send ISHs to other ESs and ISs to inform them about the IS NETs it serves. The default is 10 seconds. The range is 10 to 1000 seconds.

•IIH—Sets the Intermediate System to Intermediate System Hello PDU propagation frequency. The IS-IS Hello PDUs establish and maintain adjacencies between ISs. The default is 3 seconds. The range is 1 to 600 seconds.

•IS-IS Cost—Sets the cost for sending packets on the LAN subnet. The IS-IS protocol uses the cost to calculate the shortest routing path. The default IS-IS cost for LAN subnets is 20. It normally should not be changed.

•DIS Priority—Sets the designated intermediate system (DIS) priority. In IS-IS networks, one router is elected to serve as the DIS (LAN subnets only). Cisco router DIS priority is 64. For the ONS 15310-CL or ONS 15310-MA LAN subnet, the default DIS priority is 63. It normally should not be changed.

Step 4 Click OK.

Step 5 Return to your originating procedure (NTP).

DLP-C208 Create an IP-Over-CLNS Tunnel

Caution IP-over-CLNS tunnels require two end points. You will create one point on an ONS 15310-CL or
ONS 15310-MA. The other end point is generally provisioned on non-ONS equipment including routers and other vendor NEs. Before you begin, verify that you have the capability to create an IP-over-CLNS tunnel on the other equipment location.

Step 1 In node view, click the Provisioning > OSI > Tunnels tabs.

Step 2 Click Create.

Step 3 In the Create IP Over CLNS Tunnel dialog box, complete the following fields:

•Tunnel Type—Choose a tunnel type:

–Cisco—Creates the proprietary Cisco IP tunnel. Cisco IP tunnels add the CLNS header to the IP packets.

–GRE—Creates a Generic Routing Encapsulation tunnel. GRE tunnels add the CLNS header and a GRE header to the IP packets.

The Cisco proprietary tunnel is slightly more efficient than the GRE tunnel because it does not add the GRE header to each IP packet. The two tunnel types are not compatible. Most Cisco routers support the Cisco IP tunnel, while only a few support both GRE and Cisco IP tunnels. You generally should create Cisco IP tunnels if you are tunneling between two Cisco routers or between a Cisco router and an ONS node.

Caution Always verify that the IP-over-CLNS tunnel type you choose is supported by the equipment at the other end of the tunnel.

•Node Address—Enter the IP address of the IP-over-CLNS tunnel destination.

•Subnet Mask—Enter the IP address subnet mask of the IP-over-CLNS destination.

•OSPF Cost—Enter the Open Shortest Path First (OSPF) metric for sending packets across the IP-over-CLNS tunnel. The OSPF metric, or cost, is used by OSPF routers to calculate the shortest path. The default is 110. Normally, it is not be changed unless you are creating multiple tunnel routes and want to prioritize routing by assigning different metrics.

•NSAP Address—Enter the destination NE or OSI router NSAP address.

Step 4 Click OK.

Step 5 Provision the other tunnel end point.

Step 6 Return to your originating procedure (NTP).

DLP-C209 Remove a TARP Manual Adjacency Table Entry

Caution If TARP manual adjacency is the only means of communication to a group of nodes, loss of visibility will occur when the adjacency table entry is removed.

Step 1 In node view, click the Provisioning > OSI > TARP > MAT tabs.

Step 2 Click the MAT entry that you want to delete.

Step 3 Click Remove.

Step 4 In the Delete TDC Entry dialog box, click OK.

Step 5 Return to your originating procedure (NTP).

DLP-C211 Edit the OSI Router Configuration

Step 1 In node view, click the Provisioning > OSI > Routers > Setup tabs.

Step 2 Choose the router you want provision and click Edit.

Step 3 In the OSI Router Editor dialog box:

a. Check or uncheck the Enabled box to enable or disable the router.

Note Router 1 must be enabled before you can enable Routers 2 and 3.

b. For enabled routers, edit the primary area address, if needed. The address can be between 8 and 24 alphanumeric characters in length.

c. If you want to add or edit an area address to the primary area, enter the address at the bottom of the Multiple Area Addresses area. The area address can be 2 to 26 numeric characters (0-9) in length. Click Add.

d. Click OK.

Step 4 Return to your originating procedure (NTP).

DLP-C212 Edit the OSI Subnetwork Point of Attachment

Step 1 In the node view, click the Provisioning > OSI > Routers > Subnet tabs.

Step 2 Choose the subnet you want to edit, then click Edit.

Step 3 In the Edit <subnet type> Subnet <slot/port> dialog box, edit the following fields:

•ESH—The End System Hello PDU propagation frequency. An end system NE transmits ESHs to inform other ESs and ISs about the NSAPs it serves. The default is 10 seconds. The range is 10 to 1000 seconds.

•ISH—The Intermediate System Hello PDU propagation frequency. An intermediate system NE sends ISHs to other ESs and ISs to inform them about the NETs it serves. The default is 10 seconds. The range is 10 to 1000 seconds.

•IIH—The Intermediate System to Intermediate System Hello PDU propagation frequency. The IS-IS Hello PDUs establish and maintain adjacencies between ISs. The default is 3 seconds. The range is 1 to 600 seconds.

Note The IS-IS Cost and DIS Priority parameters are provisioned when you create or enable a subnet. You cannot change the parameters after the subnet is created. To change the DIS Priority and IS-IS Cost parameters, delete the subnet and create a new one.

Step 4 Click OK.

Step 5 Return to your originating procedure (NTP).

DLP-C213 Edit an IP-Over-CLNS Tunnel

Caution Changing the IP or NSAP addresses or an IP-over-CLNS tunnel can cause loss of NE visibility or NE isolation. Do not change network addresses until you verify the changes with your network administrator.

Step 1 Click the Provisioning > OSI > Tunnels tabs.

Step 2 Click Edit.

Step 3 In the Edit IP Over OSI Tunnel dialog box, complete the following fields:

•Tunnel Type—Edit the tunnel type:

–Cisco—Creates the proprietary Cisco IP tunnel. Cisco IP tunnels add the CLNS header to the IP packets.

–GRE—Creates a Generic Routing Encapsulation tunnel. GRE tunnels add the CLNS header and a GRE header to the IP packets.

The Cisco proprietary tunnel is slightly more efficient than the GRE tunnel because it does not add the GRE header to each IP packet. The two tunnel types are not compatible. Most Cisco routers support the Cisco IP tunnel, while only a few support both GRE and Cisco IP tunnels. You generally should create Cisco IP tunnels if you are tunneling between two Cisco routers or between a Cisco router and an ONS node.

Caution Always verify that the IP-over-CLNS tunnel type you choose is supported by the equipment at the other end of the tunnel.

•IP Address—Enter the IP address of the IP-over-CLNS tunnel destination.

•IP Mask—Enter the IP address subnet mask of the IP-over-CLNS destination.

•OSPF Metric—Enter the OSPF metric for sending packets across the IP-over-CLNS tunnel. The OSPF metric, or cost, is used by OSPF routers to calculate the shortest path. The default is 110. Normally, it is not be changed unless you are creating multiple tunnel routes and want to prioritize routing by assigning different metrics.

•NSAP Address—Enter the destination NE or OSI router NSAP address.

Step 4 Click OK.

Step 5 Return to your originating procedure (NTP).

DLP-C214 Delete an IP-Over-CLNS Tunnel

Caution Deleting an IP-over-CLNS tunnel might cause the nodes to loose visibility or cause node isolation. If node isolation occurs, onsite provisioning might be required to regain connectivity. Always confirm tunnel deletions with your network administrator.

Step 1 Click the Provisioning > OSI > Tunnels tabs.

Step 2 Choose the IP-over-CLNS tunnel that you want to delete.

Step 3 Click Delete.

Step 4 Click OK.

Step 5 Return to your originating procedure (NTP).

DLP-C215 View IS-IS Routing Information Base

Step 1 In node view, click the Maintenance > OSI > IS-IS RIB tabs.

Step 2 View the following RIB information for Router 1:

•Subnet Type—Indicates the OSI subnetwork point of attachment type used to access the destination address. Subnet types include SDCC, LDCC, GCC, OSC, and LAN.

•Location—Indicates the OSI subnetwork point of attachment. For DCC subnets, the slot and port are displayed. LAN subnets are shown as LAN.

•Destination Address—The destination network service access point (NSAP) of the IS.

•MAC Address—For destination NEs that are accessed by LAN subnets, the NE's MAC address.

Step 3 If additional routers are enabled, you can view their RIBs by choosing the router number in the Router field and clicking Refresh.

Step 4 Return to your originating procedure (NTP).

DLP-C216 View ES-IS Routing Information Base

Step 1 In node view, click the Maintenance > OSI > ES-IS RIB tabs.

Step 2 View the following RIB information for Router 1:

•Subnet Type—Indicates the OSI subnetwork point of attachment type used to access the destination address. Subnet types include SDCC, LDCC, GCC, OSC, and LAN.

•Location—Indicates the subnet interface. For DCC subnets, the slot and port are displayed. LAN subnets are shown as LAN.

•Destination Address—The destination IS NSAP.

•MAC Address—For destination NEs that are accessed by LAN subnets, the NE's MAC address.

Step 3 If additional routers are enabled, you can view their RIBs by choosing the router number in the Router field and clicking Refresh.

Step 4 Return to your originating procedure (NTP).

DLP-C217 Manage the TARP Data Cache

Step 1 In node view, click the Maintenance > OSI > TDC tabs.

Step 2 View the following TARP data cache information:

•TID—The target identifier of the originating NE. For ONS 15454s, the TID is the name entered in the Node Name/TID field on the Provisioning > General tab.

•NSAP/NET—The NSAP or Network Element Title (NET) of the originating NE.

•Type—Indicates how the TDC entry was created:

–Dynamic—The entry was created through the TARP propagation process.

–Static—The entry was manually created and is a static entry.

Step 3 If you want to query the network for an NSAP that matches a TID, complete the following steps. Otherwise, continue with Step 4.

Note The TID to NSAP function is not available if the TDC is not enabled on the Provisioning > OSI > TARP tab.

a. Click the TID to NSAP button.

b. In the TID to NSAP dialog box, enter the TID that you want to map to an NSAP.

c. Click OK, then click OK in the information message.

d. On the TDC tab, click Refresh.

If TARP finds the TID in its TDC, it returns the matching NSAP. If not, TARP sends PDUs across the network. Replies will return to the TDC later, and a "check TDC later" message is displayed.

Step 4 If you want to delete all the dynamically generated TDC entries, click the Flush Dynamic Entries button. If not, continue with Step 5.

Step 5 Return to your originating procedure (NTP).

DLP-C218 Soft-Reset a 15310-CL-CTX or CTX2500 Card Using CTC

Caution Soft-resetting the 15310-CL-CTX  or CTX2500 cards causes a traffic hit only if a provisioning change or firmware update has occurred. Otherwise, the soft reset is errorless.

Caution Do not soft reset more than one ONS 15310-MA card at a time. Instead, issue a soft reset command for a single card, then wait until CTC shows the card is back up. You can then issue a soft reset on another card if needed. Completing soft resets in sequence helps to avoid unexpected traffic hits.

Note Before you reset the 15310-CL-CTX or CTX2500 card, you should wait at least 60 seconds after the last provisioning change to avoid losing any changes to the database.

Note The 15310-CL-CTX and CTX2500 cards do not support a real time clock with battery backup. Hence, during a card reset, the time is reset to default and the date starts at 1970 till you set the time/date again.

Note A software reset causes a standard Telcordia protection switch of less than 50 ms.

Step 1 In node view, right-click the 15310-CL-CTX card or the CTX2500 card to reveal a drop-down list.

Step 2 Click Soft-Reset Card.

Note For an ONS 15310-MA, if there is any condition that prevents an errorless soft-reset, the "Force Soft-Reset" message appears. You can choose to abort the soft-reset or proceed with the forced soft-reset.

Step 3 Click Yes when the "Are You Sure?" dialog box appears.

Step 4 Return to your originating procedure (NTP).

DLP-C219 Hard-Reset the 15310-CL-CTX or CTX2500 Card Using CTC

Caution Typically a hard reset causes a standard Telcordia protection switch of less than 50 ms. However, in the following scenarios, hard-resetting the 15310-CL-CTX or CTX2500 cards causes a traffic loss until the 15310-CL-CTX or CTX2500 card fully resets:

If a 1+1 protection group is provisioned between optical ports located on the same 15310-CL-CTX or CTX2500 card.

If both paths of a path protection configuration traverse through optical ports on the same 15310-CL-CTX or CTX2500.

Note Before you reset the 15310-CL-CTX or CTX2500 card, you should wait at least 60 seconds after the last provisioning change to avoid losing any changes to the database.

Note The 15310-CL-CTX and CTX2500 cards do not support a real time clock with battery backup. Hence, during a card reset, the time is reset to default and the date starts at 1970 till you set the time/date again.

Step 1 In node view, click the Inventory tab. Locate the 15310-CL-CTX or CTX2500 card in the inventory pane.

Step 2 Click the Admin State drop-down list and select OOS-MT. Click Apply.

Step 3 Click Yes in the "Action may be service affecting. Are you sure?" dialog box.

Step 4 The service state of the card becomes OOS-MA,MT. The card faceplate appears blue in CTC.

Step 5 Right-click the card to reveal a shortcut menu.

Step 6 Click Hard-reset Card.

Step 7 Click Yes in the "Are you sure you want to hard-reset this card?" dialog box.

Step 8 Return to your originating procedure (NTP).

DLP-C220 Soft-Reset an Ethernet or Electrical Card Using CTC

Caution Do not soft reset more than one ONS 15310-MA card at a time. Instead, issue a soft reset command for a single card, then wait until CTC shows the card is back up. You can then issue a soft reset on another card if needed. Completing soft resets in sequence helps to avoid unexpected traffic hits.

Caution Soft-resetting an Ethernet card causes a traffic hit. However, soft-resetting a traffic card is errorless in most cases. If there is a provisioning change during the soft reset, or if the firmware is replaced during the software upgrade process, the reset is not errorless.

Step 1 In node view, right-click the card to reveal a shortcut menu.

Step 2 Click Soft-reset Card.

Step 3 Click Yes in the "Are you sure you want to soft-reset this card?" dialog box.

Step 4 Return to your originating procedure (NTP).

DLP-C221 Hard-Reset an Ethernet or Electrical Card Using CTC

Caution Hard-resetting a traffic card causes a traffic hit.

Note The hard-reset option is enabled only when the card is placed in the OOS-MA,MT service state.

Step 1 In node view, click the Inventory tab. Locate the appropriate card in the inventory pane.

Step 2 Click the Admin State drop-down list and select OOS-MT. Click Apply.

Step 3 Click Yes in the "Action may be service affecting. Are you sure?" dialog box.

Step 4 The service state of the card becomes OOS-MA,MT. The card faceplate appears blue in CTC and the SRV LED turns amber.

Step 5 Right-click the card to reveal a shortcut menu.

Step 6 Click Hard-reset Card.

Step 7 Click Yes in the "Are you sure you want to hard-reset this card?" dialog box.

Step 8 Return to your originating procedure (NTP).

DLP-C222 Print CTC Data

Step 1 Click the CTC tab (and subtab, if present) containing the information you want to print. For example, click the Alarms tab to print Alarms window data.

The print operation is available for all network, node (default login), and card view windows.

Step 2 From the File menu, choose Print.

Step 3 In the Print dialog box, click a a printing option (Figure 19-1).

•Entire Frame—Prints the entire CTC window including the graphical view of the card, node, or network. This option is available for all windows.

•Tabbed View—Prints the lower half of the CTC window containing tabs and data. The printout includes the selected tab (on top) and the data shown in the tab window. For example, if you print the History window Tabbed View, you print only history items appearing in the window. This option is available for all windows.

•Table Contents—Prints CTC data in table format without graphical representations of shelves, cards, or tabs.The Table Contents option prints all the data contained in a table with the same column headings. For example, if you print the History window Table Contents view, you print all data included in the table whether or not items appear in the window.

Tip When you print using the Tabbed View option, it can be difficult to determine whether the printout applies to the network, node, or card view. Look at the tabs to determine which view you are printing. Network, node, and card views are identical except that network view does not contain an Inventory tab; node view and card view contain a Performance tab.

Figure 19-1 Selecting CTC Data For Print

Step 4 Click OK.

Step 5 In the Windows Print dialog box, click a printer and click OK.

Step 6 Repeat this task for each window that you want to print.

Step 7 Return to your originating procedure (NTP).

DLP-C223 Export CTC Data

Step 1 Click the CTC tab containing the information you want to export (for example, the Alarms tab or the Circuits tab).

Step 2 If you want to export detailed circuit information, complete the following:

a. In the Circuits window, choose a circuit and click Edit to open it in the Edit Circuits window.

b. In the Edit Circuits window, choose the desired tab: Drops, Path Protection Selectors, Path Protection Switch Counts, State, or Merge.

Note Depending upon your configuration, you might or might not see all of the listed tabs when you click Edit.

Step 3 From the File menu, choose Export.

Step 4 In the Export dialog box (Figure 19-2), click a data format:

•As HTML—Saves data as a simple HTML table file without graphics. The file must be viewed or edited with applications such as Netscape Navigator, Microsoft Internet Explorer, or other applications capable of opening HTML files.

•As CSV—Saves the CTC table as comma-separated values (CSV). This option does not apply to the Maintenance > Timing > Report tab.

•As TSV—Saves the CTC table as tab-separated values (TSV).

Figure 19-2 Selecting CTC Data For Export

Step 5 If you want to open a file in a text editor or word processor application, procedures vary. Typically you can use the File > Open command to display the CTC data, or you can double-click the file name and choose an application such as Notepad.

Text editor and word processor applications display the data exactly as it is exported, including comma or tab separators. All applications that open the data files allow you to format the data.

Step 6 If you want to open the file in spreadsheet and database management applications, procedures vary. Typically you need to open the application and choose File > Import, then choose a delimited file to display the data in cells.

Spreadsheet and database management programs also allow you to manage the exported data.

Note An exported file cannot be opened in CTC.

The export operation applies to all tabular data except the following:

•Circuits (Edit option, General, and Monitor tabs)

•Provisioning > General tab

•Provisioning > Network > General tab

•Provisioning > Orderwire tab

•Provisioning > Security > Policy, Data Comm, Access, and Legal Disclaimer tabs

•Provisioning > SNMP tab

•Provisioning > Timing > General and BITS Facilities tabs

•Provisioning > OSI > Main Setup tab

•Provisioning > OSI > TARP > Config tab

•Maintenance > Database tab

•Maintenance > Diagnostic tab

•Maintenance > Protection tab

•Maintenance > Timing > Source tab

Step 7 Click OK.

Step 8 In the Save dialog box, enter a name in the File name field using one of the following formats:

•filename.html for HTML files

•filename.csv for CSV files

•filename.tsv for TSV files

Step 9 Navigate to the directory where you want to store the file.

Step 10 Click OK.

Step 11 Repeat the task for each window that you want to export.

Step 12 Return to your originating procedure (NTP).

DLP-C224 Change Optics Thresholds Settings for Optical Ports

Step 1 In node view, double-click the 15310-CL-CTX card or the CTX2500 card.

Step 2 Click the Provisioning > Optical > Optics Thresholds tabs.

Note If you want to modify a threshold setting, it might be necessary to click the available directional, type, and interval (15 Min, 1 Day) radio buttons and then click Refresh. This will display the desired threshold setting.

Step 3 Modify the settings described in Table 19-1 by clicking in the field that you want to modify. In some fields, you can choose an option from a drop-down list; in others you can type a value.

Note You must set the normalized optical power received (OPR) value whenever you replace or insert an SFP. After you click Set for the port you are observing, the LBC (%), OPR (%), and OPT (%) values under the Performance > Optical tabs should be close to 100 percent. Only Cisco-approved SFPs should be used. See Chapter 1, "Install the Cisco ONS 15310-CL" or Chapter 2, "Install the Cisco ONS 15310-MA" for more information about installing SFPs and fiber-optic cable.

Step 4 Click Apply.

Step 5 Return to your originating procedure (NTP).

DLP-C225 Set Up SNMP for a GNE

Step 1 In node view, click the Provisioning > SNMP tabs.

Step 2 In the Trap Destinations area, click Create.

Step 3 On the Create SNMP Trap Destination dialog box, complete the following fields:

•Destination Node Address—Enter the IP address of your network management system (NMS).

•Community—Enter the SNMP community name. (For more information about SNMP, refer to the "SNMP" chapter in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual.)

Note The community name is a form of authentication and access control. The community name assigned to the ONS 15310 is case-sensitive and must match the community name of the NMS.

•UDP Port—The default User Datagram Protocol (UDP) port for SNMP traps is 162.

•Trap Version—Choose either SNMPv1 or SNMPv2. Refer to your NMS documentation to determine whether to use SNMPv1 or SNMPv2.

Step 4 Click OK. The node IP address of the node where you provisioned the new trap destination appears in the Trap Destinations area.

Step 5 Click the node IP address in the Trap Destinations area. Verify the SNMP information that appears in the Selected Destination list.

Step 6 If you want the SNMP agent to accept SNMP SET requests on certain MIBs, click the Allow SNMP Sets check box. If the box is not checked, SET requests are rejected.

Step 7 If you want to set up the SNMP proxy feature to allow network management, message reporting, and performance statistic retrieval across ONS firewalls, click the Enable SNMP Proxy check box on the SNMP tab.

Note The ONS firewall proxy feature only operates on nodes running releases 4.6 and later. Using this information effectively breaches the ONS firewall to exchange management information.

For more information about the SNMP proxy feature, refer to the "SNMP" chapter of the Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual.

Step 8 Click Apply.

Step 9 Return to your originating procedure (NTP).

DLP-C226 Set Up SNMP for an ENE

Step 1 In node view, click the Provisioning > SNMP tabs.

Step 2 In the Trap Destinations area, click Create.

Step 3 On the Create SNMP Trap Destination dialog box, complete the following fields:

•Destination Node Address—Enter the IP address of your NMS.

•Community—Enter the SNMP community name. (For more information about SNMP, refer to the "SNMP" chapter in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual.)

Note The community name is a form of authentication and access control. The community name assigned to the ONS 15310 is case-sensitive and must match the community name of the NMS.

•UDP Port—The default UDP port for SNMP traps is 162.

•Trap Version—Choose either SNMPv1 or SNMPv2. Refer to your NMS documentation to determine whether to use SNMPv1 or SNMPv2.

Step 4 Click OK. The node IP address of the node where you provisioned the new trap destination appears in the Trap Destinations area.

Step 5 Click the node IP address in the Trap Destinations area. Verify the SNMP information that appears in the Selected Destination list.

Step 6 If you want the SNMP agent to accept SNMP SET requests on certain MIBs, click the Allow SNMP Sets check box. If the box is not checked, SET requests are rejected.

Step 7 If you want to set up the SNMP proxy feature to allow network management, message reporting, and performance statistic retrieval across ONS firewalls, click the Enable SNMP Proxy check box on the SNMP tab.

Note The ONS firewall proxy feature only operates on nodes running releases 4.6 and later. Using this information effectively breaches the ONS firewall to exchange management information.

For more information about the SNMP proxy feature, refer to the "SNMP" chapter of the Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual.

Step 8 Click Apply.

Step 9 If you are setting up SNMP proxies, you can set up to three relays for each trap address to convey SNMP traps from the NE to the NMS. To do this, complete the following substeps:

a. Click the first trap destination IP address. The address and its community name appear in the Destination fields.

b. If the node you are logged into is an ENE, set the Relay A address to the GNE and type its community name in the community field. If there are NEs between the GNE and ENE, you can enter up to two SNMP proxy relay addresses and community names in the fields for Relay and Relay C. When doing this, consult the following guidelines:

•If the NE is directly connected to the GNE, enter the address and community name of the GNE for Relay A.

•If this NE is connected to the GNE through other NEs, enter the address and community name of the GNE for Relay A and the address and community name of NE 1 for Relay B and NE 2 for Relay C.

The SNMP proxy directs SNMP traps in the following general order: ENE > RELAY A > RELAY B > RELAY C > NMS. For example:

•If there is are 0 intermediate relays, the order is ENE > RELAY A (GNE) > NMS

•If there is 1 intermediate relay, the order is ENE > RELAY A (NE 1) > RELAY B (GNE) > NMS

•If there is are 0 intermediate relays, the order is ENE > RELAY A (NE 1) > RELAY B (NE 2) > RELAY C (GNE) > NMS

Step 10 Click Apply.

Step 11 Repeat Step 2 through Step 10 for all NEs between the GNE and ENE.

Step 12 Return to your originating procedure (NTP).

DLP-C227 Format and Enter NMS Community String for SNMP Command or Operation

Step 1 If the SNMP "Get" (or other operation) is enabled on the ONS 15310-CL or ONS 15310-MA configured as a GNE, enter the community name assigned to the GNE in community name field on the MIB browser.

Note The community name is a form of authentication and access control. The community name of the NMS must match the community name assigned to the ONS 15310.

Step 2 If the SNMP "Get" (or other operation) is enabled for the ENE through a SOCKS proxy-enabled GNE, create a formatted string to enter in the MIB browser community name field. Refer to the following examples when constructing this string for your browser:

•Formatted community string input example 1:

allviews{192.168.7.4,,,net7node4}

If "allviews" is a valid community name value at the proxy-enabled SNMP agent (the GNE), the GNE is expected to forward the PDU to 192.168.7.4 at Port 161. The outgoing PDU will have "net7node4" as the community name. This is the valid community name for the ENE with address 192.168.7.4.

•Formatted community string input example 2:

allviews{192.168.7.99,,,enter7{192.168.9.6,161,,net9node6}}

If "allviews" is a valid community name value at the proxy-enabled GNE, the GNE is expected to forward the PDU to 192.168.7.99 at the default port (Port 161) with a community name of "enter7{192.168.9.6,161,,net9node6}". The system with the address 192.168.7.99 (the NE between the GNE and ENE) forwards this PDU to 192.168.9.6 at Port 161 (at the ENE) with a community name of "net9node6". The community name "enter7" is valid for the NE between the GNE and the ENE and "net9node6" is a valid community name for the ENE.

Step 3 Log into the NMS where the browser is installed to retrieve the network information from the ONS 15310.

Step 4 On this computer, go to Start and click the SNMP MIB browser application.

Step 5 In the Host and Community areas, enter the IP address of the GNE through which the ONS 15310 with the information to be retrieved can be reached.

Step 6 In the Community area, enter the community string as explained in Step 2.

Step 7 Return to your originating procedure (NTP).

DLP-C228 Provision Orderwire

Step 1 In the network view, click the Provisioning > Overhead Circuits tabs.

Step 2 Click Create.

Step 3 In the Overhead Circuit Creation dialog box, complete the following fields in the Circuit Attributes area:

•Name—Assign a name to the circuit. The name can be alphanumeric and up to 48 characters (including spaces).

•Circuit Type—Choose either Local Orderwire or Express Orderwire depending on the orderwire path that you want to create. If regenerators are not used between nodes, you can use either local or express orderwire channels. If regenerators exist, use the express orderwire channel.

•PCM—Choose the Pulse Code Modulation voice coding and companding standard, either Mu_Law (North America, Japan) or A_Law (Europe). The provisioning procedures are the same for both types of orderwire.

Caution When provisioning orderwire for nodes that reside in a ring, do not provision a complete orderwire loop. For example, a four-node ring typically has east and west ports provisioned at all four nodes. However, to prevent orderwire loops, provision two orderwire ports (east and west) at all but one of the ring nodes.

Step 4 Click Next.

Step 5 In the Circuit Source area, complete the following:

•Node—Choose the source node.

•Slot—Choose the source slot.

•Port—If displayed, choose the source port.

Step 6 Click Next.

Step 7 In the Circuit Destination area, complete the following:

•Node—Choose the destination node.

•Slot—Choose the destination slot.

•Port—If displayed, choose the destination port.

Step 8 Click Finish.

Step 9 Return to your originating procedure (NTP).

DLP-C229 Consolidate Links in Network View

Note Global consolidation persists when CTC is re-launched but local consolidation does not.

Step 1 From the View menu, choose Go to Network View. CTC shows the link icons by default.

Step 2 Perform the following steps as needed:

•To toggle between link icons, go to Step 3.

•To consolidate all the links on the network map, go to Step 4.

•To consolidate a link or links between two nodes, go to Step 5.

•To view information about a consolidated link, go to Step 6.

•To access an individual link within a consolidated link, go to Step 7.

•To expand consolidated links, go to Step 8.

•To filter the links by class, go to Step 9.

Step 3 Right-click the network map and choose Show Link Icons to toggle the link icons on and off.

Step 4 To consolidate all the links on the network map (global consolidation):

a. Right-click anywhere on the network map.

b. Choose Collapse/Expand Links from the shortcut menu. The Collapse/Expand Links dialog window appears.

c. Select the check boxes for the link classes you want to consolidate.

d. Click OK. The selected link classes are consolidated throughout the network map.

Step 5 To consolidate a link or links between two nodes:

a. Right-click the link on the network map.

b. Choose Collapse [link class] Link from the shortcut menu, where "link class" is DCC, GCC, OTS, PPC, or server trail. The selected link type consolidates to show only one link.

Note The links consolidate by class. For example, if you select a DCC link for consolidation only the DCC links will consolidate, leaving any other link classes expanded.

Figure 19-3 shows the network view with unconsolidated DCC and PPC links.

Figure 19-3 Unconsolidated Links in the Network View

Figure 19-4 shows a network view with globally consolidated links.

Figure 19-4 Consolidated Links in the Network View

Figure 19-5 shows a network view with local DCC link consolidation between two nodes.

Figure 19-5 Network View with Local Link Consolidation

Step 6 To view information about a consolidated link, either move your mouse over the link (the tooltip displays the number of links and the link class) or single-click the link to display detailed information on the left side of the window.

Step 7 To access an individual link within a consolidated link (for example, if you need to perform a span upgrades):

a. Right-click the consolidated link. A shortcut menu appears with a list of the individual links.

b. Hover the mouse over the selected link. A cascading menu appears where you can select an action for the individual link or navigate to one of the nodes where the link is attached.

Step 8 To expand locally consolidated links, right-click the consolidated link and choose Expand Links from the shortcut menu.

Step 9 To filter the links by class:

a. Click the Link Filter button in the upper right area of the window. The Link Filter dialog appears.

The link classes that appear in the Link Filter dialog are determined by the Network Scope you choose in the network view (Table 19-2).

b. Check the check boxes next to the links you want to display.

c. Click OK.

Step 10 Return to your originating procedure (NTP).

DLP-C231 Adjust the Java Virtual Memory Heap Size

Step 1 Click Start > Settings > Control Panel. The Windows Control Panel appears.

Step 2 Double-click System. The System Properties window appears.

Step 3 Click the Advanced tab.

Step 4 Click Environmental Variables. The Environmental Variables window appears.

Step 5 In the User Variables area, click New. The New User Variable window appears.

Step 6 Type "CTC_HEAP" in the Variable Name field.

Step 7 Type "512" in the Variable Value field.

Step 8 Click OK.

Step 9 Reboot your PC.

Step 10 Return to your originating procedure (NTP).

DLP-C232 Delete a Server Trail

Note Deleting server trails do not impact the circuits provisioned over it as server trail is a logical link. When you delete a server trail, the circuit state becomes PARTIAL.

Step 1 From the View menu, choose Go to Network View.

Step 2 Click the Provisioning > Server Trails tabs.

Step 3 Click the server trail that you want to delete.

Step 4 Click Delete.

Step 5 In the confirmation dialog box, click Yes.

Note You can use the server trail audit log to recreate a server trail that you may have accidentally deleted. The server trail audit log includes the following parameters:

•Server trail ID

•Peer IP address

•Circuit size

•Protection type

•Number of trails

•Starting STS/VT

•SRLG value

You can look at the audit log of the source or destination node and find the entry for the delete call. This log entry has the STS/VT path definitions on the node, peer IP address, and server trail ID. You can then look at the audit log of the peer IP address, locate the delete call for the specific server trail ID, and find the STS/VT path definitions on the node. This would provide you with the required information to recreate the server trail.

Note It is recommended that you delete one server trail at a time as the deletion of multiple trails together may cause CTC to hang and is a time consuming task.

Step 6 Return to your originating procedure (NTP).

DLP-C233 Change Line and Threshold Settings for DS-1 Ports

Note Refer to the "Network Element Defaults" appendix in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual for DS-1 port default settings.

Step 1 In node view, double-click the 15310-CL-CTX card, DS1-28/DS3-EC1-3 card, or DS1-84/DS3-EC1-3 card where you want to change line or threshold settings.

Step 2 Click the Provisioning > DS-1 tabs.

Step 3 Depending on the setting you need to modify, click the Line, Line Thresholds, Elect Path Thresholds, or SONET Thresholds subtabs.

Note If you want to modify a threshold setting, it might be necessary to click the available directional, type, and interval (15 Min, 1 Day) radio buttons and then click Refresh. This will display the desired threshold setting.

Step 4 Modify the settings found under these subtabs by clicking in the field that you want to modify. In some fields, you can choose an option from a drop-down list; in others you can type a value.

Step 5 Click Apply.

Step 6 Repeat Steps 4 and 5 for each subtab that has parameters you want to provision.

For definitions of line settings, see Table 19-3. For definitions of line threshold settings, see Table 19-4. For definitions of the electrical path threshold settings, see Table 19-5. For definitions of SONET threshold settings, see Table 19-6.

Table 19-3 describes the values on the Provisioning > DS-1> Line tab for the DS-1 ports.

Table 19-4 describes the values on the Provisioning > DS-1> Line Thresholds tab for the DS-1 ports.

Table 19-5 describes the values on the Provisioning > DS-1> Elect Path Thresholds tab for the DS-1 ports.

Table 19-6 describes the values on the Provisioning > DS-1> SONET Thresholds tab for the DS-1 ports.

Note The threshold value displays after the circuit is created.

Step 7 Return to your originating procedure (NTP).

DLP-C234 Grant Superuser Privileges to Provisioning Users

Step 1 In node view, click the Provisioning > Defaults tabs.

Step 2 In the Defaults Selector area, choose NODE > security > grantPermission.

Step 3 Click in the Default Value column for the default property you are changing and choose Provisioning from the drop-down list.

Note If you click Reset before you click Apply, all values will return to their original settings.

Step 4 Click Apply.

A pencil icon will appear next to the default name that will be changed as a result of editing the defaults file.

Note After you have activated a software load, you must close your current CTC session and restart a new CTC session for the changes to take effect.

Step 5 Return to your originating procedure (NTP).

DLP-C235 Change the OSI Routing Mode

Caution Do not complete this procedure until you confirm the role of the node within the network. It will be either an ES or IS Level 1. This decision must be carefully considered. For additional information about OSI provisioning, refer to the "Management Network Connectivity" chapter of the Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual.

Caution LSP buffers must be the same at all NEs within the network, or loss of visibility could occur. Do not modify the LSP buffers unless you are sure that all NEs within the OSI have the same buffer size.

Caution LSP buffer sizes cannot be greater than the LAP-D MTU size within the OSI area.

Step 1 In node view, click the Provisioning > OSI > Main Setup tabs.

Step 2 The following routing modes are available for the ONS 15310-CL and ONS 15310-MA:

Note Changing a routing mode should be carefully considered. Additional information about protocols are provided in the "Management Network Connectivity" chapter of the Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual.

•End System—The ONS 15310 performs OSI end system (ES) functions and relies upon an intermediate system (IS) for communication with nodes that reside within its OSI area.

Note The End System routing mode is not available if more than one virtual router is enabled.

•Intermediate System Level 1—The ONS 15310 performs OSI IS functions. It communicates with IS and ES nodes that reside within its OSI area. It depends upon an IS L1/L2 node to communicate with IS and ES nodes that reside outside its OSI area.

Step 3 Although Cisco does not recommend changing the LSP (Link State Protocol Data Unit) buffer sizes, you can change the L1 LSP Buffer Size field to change the Level 1 link state PDU buffer size.

Step 4 Return to your originating procedure (NTP).

DLP-C236 Change Line and Threshold Settings for DS-3 Ports

Note Refer to the "Network Element Defaults" appendix in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual for DS-3 port default settings.

Step 1 In node view, double-click the 15310-CL-CTX, DS1-28/DS3-EC1-3, or DS1-84/DS3-EC1-3 card where you want to change line or threshold settings.

Step 2 Click the Provisioning > DS-3 tabs.

Step 3 Depending on the setting you need to modify, click the Line, Line Thresholds, Elect Path Thresholds, or SONET Thresholds subtab.

Note If you want to modify a threshold setting, it might be necessary to click the available directional, type, and interval (15 Min, 1 Day) radio buttons and then click Refresh. This will display the desired threshold setting.

Step 4 Modify the settings found under these tabs by clicking in the field that you want to modify. In some fields, you can choose an option from a drop-down list; in others you can type a value.

Step 5 Click Apply.

Step 6 Repeat Steps 4 and 5 for each subtab that has parameters you want to provision.

For definitions of the line settings, see Table 19-7. For definitions of the line threshold settings, see Table 19-8. For definitions of the electrical path threshold settings, see Table 19-9. For definitions of the SONET threshold settings, see Table 19-10.

Table 19-7 describes the values on the Provisioning > Line tab for the DS-3 ports.

Table 19-8 describes the values on the Provisioning > Line Thresholds tab for the DS-3 ports.

Table 19-9 describes the values on the Provisioning > Elect Path Thresholds tab for the DS-3 ports.

Table 19-10 describes the values on the Provisioning > SONET Thresholds tab for the DS-3 ports.

Note The threshold value displays after the circuit is created.

Step 7 Return to your originating procedure (NTP).

DLP-C237 Change Line and Threshold Settings for the EC-1 Ports

Note Refer to the "Network Element Defaults" appendix in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual for DS-3 port default settings.

Step 1 In node view, double-click the 15310-CL-CTX card, DS1-28/DS3-EC1-3 card, or DS1-84/DS3-EC1-3 card where you want to change line or threshold settings.

Step 2 Click the Provisioning > EC-1 tab.

Step 3 Depending on the setting you need to modify, click the Line or SONET Thresholds tab.

Note If you want to modify a threshold setting, it might be necessary to click the available directional, type, and interval (15 Min, 1 Day) radio buttons and then click Refresh. This will display the desired threshold setting.

Note To modify settings on the SONET STS tab, see the "DLP-C99 Enable Intermediate-Path Performance Monitoring" task on page 17-119.

Step 4 Modify the settings found under these subtabs by clicking in the field that you want to modify. In some fields, you can choose an option from a drop-down list; in others you can type a value.

Step 5 Click Apply.

Step 6 Repeat Steps 4 and 5 for each subtab that has parameters you want to provision.

For definitions of the line settings, see Table 19-11. For definitions of SONET threshold settings, see Table 19-12.

Table 19-11 describes the values on the Provisioning > EC-1 > Line tab for the EC-1 ports.

Table 19-12 describes the values on the Provisioning > SONET Thresholds tab for the EC-1 ports.

Step 7 Return to your originating procedure (NTP).

DLP-C238 Change Optical Port Line Settings

Note Refer to the "Network Element Defaults" appendix in the Cisco ONS 15310-CL and Cisco ONS 15310-MA Reference Manual for ONS 15310-CL and ONS 15310-MA port default settings.

Step 1 In node view, double-click the 15310-CL-CTX card or the CTX2500 card.

Step 2 Click the Provisioning > Optical > Line tabs.

Note If you want to modify a threshold setting, it might be necessary to click the available directional, type, and interval (15 Min, 1 Day) radio buttons and then click Refresh. This will display the desired threshold setting.

Step 3 Modify the settings described in Table 19-1 by clicking in the field that you want to modify. In some fields, you can choose an option from a drop-down list; in others you can type a value.

Step 4 Click Apply.

Step 5 Return to your originating procedure (NTP).

DLP-C239 Change Optical Port SONET Thresholds Settings

Step 1 In node view, double-click the 15310-CL-CTX card or the CTX2500 card.

Step 2 Click the Provisioning > Optical > SONET Thresholds tabs (Figure 19-6 and Figure 19-7).

Figure 19-6 Provisioning SONET Thresholds for the ONS 15310-CL Optical Ports

Figure 19-7 Provisioning SONET Thresholds for the ONS 15310-MA Optical Ports

Note If you want to modify a threshold setting, it might be necessary to click the available directional, type, and interval (15 Min, 1 Day) radio buttons and then click Refresh. This will display the desired threshold setting.

Step 3 Modify the settings described in Table 19-14 by clicking in the field that you want to modify. In some fields, you can choose an option from a drop-down list; in others you can type a value.

Step 4 Click Apply.

Step 5 Return to your originating procedure (NTP).

DLP-C241 Edit Path Protection Dual-Ring Interconnect Circuit Hold-Off Timer

Note Cisco recommends that you set the DRI port HOT value to zero and the circuit path selector HOT value to a number equal to or greater than zero.

Step 1 From the View menu, choose Go to Network View.

Step 2 Click the Circuits tab.

Step 3 Click the path protection circuit you want to edit, then click Edit.

Step 4 In the Edit Circuit window, click the Path Protection Selectors tab.

Step 5 Create a hold-off time for the circuit source and destination ports:

a. In the Holder Off Timer area, double-click the cell of the circuit source port (top row), then type the new hold-off time. The range is 0 to 10,000 ms in increments of 100.

b. In the Hold-Off Timer area, double-click the cell of the circuit destination port (bottom row), then type the hold-off time entered in Step a.

Step 6 Click Apply, then close the Edit Circuit window by choosing Close from the File menu.

Step 7 Return to your originating procedure (NTP).

DLP-C242 Create a 1+1 Protection Group for the ONS 15310-MA

Step 1 Complete the "DLP-C29 Log into CTC" task on page 17-44 at the node where you want to create the protection group. If you are already logged in, continue with Step 2.

Step 2 Verify that pluggable port modules (PPM) are provisioned for the same port and port rate on the CTX2500 where you will create the optical protection group.

Note PPMs are referred to as small-form factor pluggables (SFPs) in the hardware chapters.

You can use either of the following methods:

•In node view, move your mouse over the CTX2500 client port. If a PPM is provisioned, two dots appear in the port graphic, and the port and PPM port and rate appear when you move the mouse over the port.

•Display the CTX2500 in card view. Click the Provisioning > Pluggable Port Module tabs. Verify that a PPM is provisioned in the Pluggable Port Module area, and the port type and rate is provisioned for it in the Selected PPM area.

The PPM port and port rate must be the same for both CTX2500 ports. As necessary, complete the "NTP-C130 Manage Pluggable Port Modules" procedure on page 10-3 to make PPM changes.

Step 3 From node view, click the Provisioning > Protection tabs.

Step 4 In the Protection Groups area, click Create.

Step 5 In the Create Protection Group dialog box, enter the following:

•Name—Type a name for the protection group. The name can have up to 32 alphanumeric (a-z, A-Z, 0-9) characters. Special characters are permitted. For TL1 compatibility, do not use question marks (?), backslash (\), or double quote (") characters.

•Type—Choose 1+1 from the drop-down list.

•Protect Port—Choose the protect port from the drop-down list. The menu displays the available optical ports on the CTX2500.

•After you choose the protect port, a list of ports available for protection is displayed under Available Ports.

Step 6 From the Available Ports list, choose the port that will be protected by the port you selected in the Protect Port field. Click the top arrow button to move the port to the Working Ports list.

Step 7 Complete the remaining fields:

•Bidirectional switching—Check this check box if you want both Tx and Rx signals to switch to the protect port when a failure occurs to one signal. Leave it unchecked if you want only the failed signal to switch to the protect port.

•Revertive—Check this check box if you want traffic to revert to the working port after failure conditions stay corrected for the amount of time entered in the Reversion Time field.

•Reversion time—If Revertive is checked, choose the reversion time from the drop-down list. The range is 0.5 to 12.0 minutes. The default is 5.0 minutes. Reversion time is the amount of time that will elapse before the traffic reverts to the working port. The reversion timer starts after conditions causing the switch are cleared.

Step 8 Click OK.

Step 9 Return to your originating procedure (NTP).

DLP-C243 Create an Optimized 1+1 Protection Group for the ONS 15310-MA

Step 1 Complete the "DLP-C29 Log into CTC" task on page 17-44 at the node where you want to create the protection group. If you are already logged in, continue with Step 2.

Step 2 Verify that pluggable port modules (PPM) are provisioned for the same port and port rate on the CTX2500 where you will create the optical protection group.

Note PPMs are referred to as small-form factor pluggables (SFPs) in the hardware chapters.

You can use either of the following methods:

•In node view, move your mouse over the CTX2500 client port. If a PPM is provisioned, two dots appear in the port graphic, and the port and PPM port and rate appear when you move the mouse over the port.

•Display the CTX2500 in card view. Click the Provisioning > Pluggable Port Module tabs. Verify that a PPM is provisioned in the Pluggable Port Module area, and the port type and rate is provisioned for it in the Selected PPM area.

The PPM port and port rate must be the same for both CTX2500 ports. As necessary, complete the "NTP-C130 Manage Pluggable Port Modules" procedure on page 10-3 to make PPM changes.

Step 3 Change the port type from SONET to SDH for each applicable port where you want to provision a 1+1 optimized protection group:

a. In node view, double-click the applicable CTX2500.

b. Click the Provisioning > Line tabs.

c. In the Type column next to port, choose SDH from the drop-down list and click Apply.

Step 4 In node view, click the Provisioning > Protection tabs.

Step 5 In the Protection Groups area, click Create.

Step 6 In the Create Protection Group dialog box, enter the following:

•Name—Type a name for the protection group. The name can have up to 32 alphanumeric (a-z, A-Z, 0-9) characters. Special characters are permitted. For TL1 compatibility, do not use question marks (?), backslash (\), or double quote (") characters.

•Type—Choose 1+1 Optimized from the drop-down list.

•Protect Port—Choose the protect port from the drop-down list. The list displays the available optical ports. If the CTX2500s are not provisioned for SDH, no ports appear in the drop-down list.

Step 7 From the Available Ports list, choose the port that will be protected by the port you selected in the Protect Port field. Click the top arrow button to move each port to the Working Ports list.

Step 8 Complete the remaining fields:

•Reversion time—If Revertive is checked, choose a reversion time from the drop-down list. The range is 0.5 to 12.0 minutes. The default is 5.0 minutes. Reversion time is the amount of time that will elapse before the primary channel is automatically renamed as secondary and the secondary channel is renamed as primary. The reversion timer starts after conditions causing the switch are cleared.

•Verification guard time—Choose the verification guard time from the drop-down list. The range is 500ms to 1s. A verification guard timer is used to ensure the acceptance of a Force switch command from the far-end node. When the Force command is received, if no Lockout is present or if Secondary section is not in a failed state, then the outgoing K1 byte is changed to indicate Force and the verification guard timer is started. If a Force switch command is not acknowledged by the far-end within the verification guard timer duration, then the Force command is cleared.

•Recovery guard time—Choose the recovery guard time from the drop-down list. The range is 0s to 10s. The default is 1 second. A recovery guard timer is used for preventing rapid switches due to signal degrade (SD) or signal failure (SF) failures. After the SD/SF failure is cleared on the line, a recovery guard timer is started. Recovery guard time is the amount of time elapsed before the system declares that a condition is cleared after the detection of an SD/SF failure.

•Detection guard time—Choose the detection guard time from the drop-down list. The range is 0s to 5s. The default is 1 second. The detection guard timer is started after detecting an SD, SF, loss of signal (LOS), loss of frame (LOF), or alarm indication signal-line (AIS-L) failure. Detection guard time is the amount of time elapsed before a traffic switch is initiated to a standby port after the detection of an SD, SF, LOS, LOF, or AIS-L failure on the active port.

Step 9 Click OK.

Step 10 Return to your originating procedure (NTP).

DLP-C244 Modify an Optimized 1+1 Protection Group for the ONS 15310-MA

Step 1 In node view, click the Provisioning > Protection tabs.

Step 2 In the Protection Groups area, click the optimized 1+1 protection group you want to modify.

Step 3 In the Selected Group area, modify the following as needed:

•Name—Type the changes to the protection group name. The name can have up to 32 alphanumeric characters.

•Reversion time—If Revertive is checked, choose a reversion time from the drop-down list. The range is 0.5 to 12.0 minutes. The default is 5.0 minutes. Reversion time is the amount of time that will elapse before the primary channel is automatically renamed as secondary and the secondary channel is renamed as primary.

•Verification guard time—Choose the verification guard time from the drop-down list. The range is 500ms to 1s. A verification guard timer is used to ensure the acceptance of a Force switch command from the far-end node. When the Force command is received, if no Lockout is present or if the Secondary section is not in a failed state, then the outgoing K1 byte is changed to indicate Force and the verification guard timer is started. If a Force user command is not acknowledged by the far-end within the verification guard timer duration, then the Force command is cleared.

•Recovery guard time—Choose the recovery guard time from the drop-down list. The range is 0s to 10s. The default is 1 second. A recovery guard timer is used for preventing rapid switches due to signal degrade (SD) or signal failure (SF) failures. After the SD/SF failure is cleared on the line, a recovery guard timer is started. Recovery guard time is the amount of time elapsed before the system declares that a condition is cleared after the detection of an SD/SF failure.

•Detection guard time—Choose the detection guard time from the drop-down list. The range is 0s to 5s. The default is 1 second. The detection guard timer is started after detecting an SD, SF, loss of signal (LOS), loss of frame (LOF), or line alarm indication signal (AIS-L) failure. Detection guard time is the amount of time elapsed before a traffic switch is initiated to a standby port after the detection of an SD, SF, LOS, LOF, or AIS-L failure on the active port.

Step 4 Click Apply. Confirm that the changes appear; if not, repeat the task.

Step 5 Return to your originating procedure (NTP).

DLP-C245 Modify a 1:1 Protection Group for the ONS 15310-MA

Step 1 In node view, click the Provisioning > Protection tabs.

Step 2 In the Protection Groups area, click the 1:1 protection group you want to modify.

Step 3 In the Selected Group area, you can modify the following, as needed:

•Name—As needed, type the changes to the protection group name. The name can have up to 32 alphanumeric characters.

•Revertive—Check this box if you want traffic to revert to the working card after failure conditions stay corrected for the amount of time chosen from the Reversion Time drop-down list. Uncheck if you do not want traffic to revert.

•Reversion time—If the Revertive check box is selected, choose the reversion time from the Reversion time drop-down list. The range is 0.5 to 12.0 minutes. The default is 5.0 minutes. This is the amount of time that will elapse before the traffic reverts to the working card. Traffic can revert when conditions causing the switch are cleared.

Step 4 Click Apply.

Step 5 Return to your originating procedure (NTP).

DLP-C248 Mount a Single ONS 15310-MA in a Rack

Note Mounting the ONS 15310-MA in a rack requires a minimum of 10.5 inches of vertical rack space, including the space needed for the standard cable management bracket. If the extended cable management bracket is used, 12.25 inches is required.

Note To install the shelf assembly justified right, secure the universal mounting ear to the right side of the shelf assembly and the appropriate mounting ear for your rack size (19-inch or 23-inch) on the left side. To install the shelf assembly justified left, secure the universal mounting ear to the left side of the shelf assembly and the appropriate mounting ear for your rack size on the right side.

Step 1 Verify that the proper fuse and alarm panel has been installed in the top mounting space. If a fuse and alarm panel has not been installed, you must install one according to manufacturer instructions. A fuse panel with two fuses per shelf (amperage depends on the fuse and alarm panel you are using) is required for Power A and B feeds.

Caution Maximum amperage rating of the fuse is determined by the rated ampacity of the selected power cable (refer to manufacturer's instructions). The fuse rating should not exceed 20 A.

Step 2 Align the screw holes on the desired mounting ear with the screw holes at the front of the shelf assembly, and install four #10-32 screws.

Step 3 Repeat Step 2 for the other mounting ear.

Step 4 Lift the shelf assembly to the desired rack position.

Step 5 Align the screw holes on the mounting ears with the mounting holes in the rack.

Step 6 Using the Phillips screwdriver, install one #12-24 mounting screws in each side of the assembly.

Step 7 When the shelf assembly is secured to the rack, install the remaining two mounting screws through the rack into the shelf assembly.

Figure 19-8 shows a single ONS 15310-MA being mounted in a rack.

Figure 19-8 Mounting a Single, Left-Justified ONS 15310-MA in a Rack

Note If you want to install a tie-down bar on the rack, be sure to leave 1 RU spacing between the ONS 15310-MA and any adjacent equipment you plan to install on the rack. This will provide adequate space for the tie-down bar and cabling.

Step 8 Return to your originating procedure (NTP).

DLP-C249 Mount Dual ONS 15310-MA Shelf Assemblies in a Rack

Step 1 Verify that the proper fuse and alarm panel has been installed in the top mounting space. If a fuse and alarm panel is not present, you must install one according to manufacturer instructions. A fuse panel with two fuses per shelf (amperage depends on the fuse and alarm panel you are using) is required for Power A and B feeds.

Caution Maximum amperage rating of the fuse is determined by the rated ampacity of the selected power cable (refer to manufacturer's instructions). The fuse rating should not exceed 20 A.

Step 2 Align the screw holes on a universal mounting ear with the screw holes at the left front of the shelf assembly, and install four #10-32x0.375 screws.

Step 3 Align the screw holes on a universal mounting ear with the screw holes at the right front of the other shelf assembly, and install four #10-32x0.375 screws.

Step 4 Align the two shelves on the front, common lateral side. Using the Phillips screwdriver, install three mounting screws; #10-32x0.31 length. Figure 19-9 shows the two shelves aligned along a common lateral side.

Figure 19-9 ONS 15310-MA Shelves Aligned along a Common Lateral Side

Step 5 Install screws #10-32x0.375 length with its #10-32 nut on the rear common lateral side as shown in Figure 19-10.

Figure 19-10 ONS 15310-MA Shelves Aligned on the Rear Common Lateral Side

Step 6 Install the dual-assembly plate at the bottom of the shelf assembly by aligning it with four screws #10-32x0.31 length as shown in Figure 19-11.

Figure 19-11 Dual-Assembly Plate aligned to the ONS 15310-MA Shelf

Step 7 Lift the dual-shelf assembly to the desired rack position.

Step 8 Align the screw holes on the mounting ears with the mounting holes in the rack.

Step 9 Using the Phillips screwdriver, install one #12-24 mounting screws in each side of the assembly.

Step 10 When the shelf assembly is secured to the rack, install the remaining two mounting screws through the rack into the shelf assembly.

Note If you want to install a tie-down bar on the rack, be sure to leave 1 RU spacing between the ONS 15310-MA and any adjacent equipment you plan to install on the rack. This will provide adequate space for the tie-down bar and cabling.

Step 11 Repeat the task with the remaining ONS 15310-MA nodes.

Step 12 Return to your originating procedure (NTP).

DLP-C250 Connect the Office Ground to the ONS 15310-MA