There are two main DWDM network types: metro core, where the channel power is equalized and dispersion compensation is applied, and metro access, where the channels are not equalized and dispersion compensation is not applied. The DWDM network topologies supported are hubbed rings, multihubbed rings, meshed rings, linear configurations, and single-span links. The DWDM node types supported are hub, terminal, optical add/drop multiplexing (OADM), reconfigurable optical add/drop multiplexing (ROADM), anti-amplified spontaneous emissions (anti-ASE), and line amplifier. For DWDM and hybrid node turn-up procedures, see Chapter 3 "Turn Up a Node."

b. Verify that no equipment alarms appear (EQPT in the Cond column) indicating equipment failure or other hardware problems. If equipment failure alarms appear, investigate and resolve them before continuing. Refer to the Cisco ONS 15454 DWDM Troubleshooting Guide for procedures.

Step 3 Verify that the software version shown in the node view (single-shelf mode) or multishelf view (multishelf mode) status area matches the version required by your network. (The status area is located to the left of the shelf graphic.) If the software is not the correct version, perform one of the following procedures:

Step 7 Click the Provisioning > Security tabs. Verify that all users have been created and that their security levels are correct according to documentation provided by the network administrator. If not, see the "NTP-G88 Modify Users and Change Security" procedure.

Step 8 If Simple Network Management Protocol (SNMP) is provisioned on the node, click the Provisioning > SNMP tabs. Verify that all SNMP settings are correct according to documentation provided by the network administrator. If not, see the "NTP-G89 Change SNMP Settings" procedure.

Step 9 Repeat this procedure at each node in the network.

Stop. You have completed this procedure.

NTP-G52 Verify Node-to-Node Connections

Purpose

This procedure verifies optical service channel (OSC) terminations between nodes and checks span attenuation. This procedure applies to all ROADM, OADM, and line-amplifier locations.

Step 4 Click the Provisioning > Comm Channels > OSC tabs. Verify that OSC terminations appear under the OSC Terminations area for the east and west OSC-CSM or OSCM cards and that the port state is In-Service and Normal (IS-NR [ANSI]/Unlocked-enabled [ETSI]). If so, continue with Step 5. If OSC terminations are not created, complete the "NTP-G38 Provision OSC Terminations" procedure.

Step 2 In the General Timing area, complete the following information:

•Timing Mode—Choose External if the ONS 15454 derives its timing from a BITS source wired to the backplane pins (ANSI) or a MIC-C/T/P front mount electrical connection (FMEC) (ETSI); choose Line if timing is derived from an OSC-CSM or OSCM card that is optically connected to the timing node. A third option, Mixed, allows you to set both external and line timing references. Because Mixed timing might cause timing loops, Cisco does not recommend its use. Use this mode with care.

Note Generation 1 is used only by SONET or SDH ONS 15454 nodes that are connected to equipment that does not support Generation 2.

•Quality of RES—Sets the timing quality for the user-defined, reserved (RES) S1 byte if your timing sources supports RES. Most timing sources do not use RES. If it does not support RES, choose RES=DUS (do not use for timing reference). Qualities are displayed in descending quality order as ranges. For example, in Generation 1 SSM, ST3<RES<ST2 means that the timing reference RES is higher than a Stratum 3 (ST3) and lower than a Stratum 2 (ST2).

•Revertive—Select this check box if you want the ONS 15454 to revert to a primary reference source after the conditions that caused it to switch to a secondary timing reference are corrected.

•Reversion Time—If Revertive is checked, choose the amount of time that the ONS 15454 will wait before reverting to its primary timing source. Five minutes is the default.

Step 3 In the Reference Lists area, complete the following information:

Note You can define up to three timing references for the node and up to six BITS Out references. BITS Out references define the timing references used by equipment that can be attached to the node's BITS Out pins on the backplane (ANSI) or the MIC-C/T/P FMEC (ETSI). If you attach equipment to BITS Out pins, you normally attach it to a node with Line mode, because equipment near the external timing reference can be directly wired to the reference.

•NE Reference—Allows you to define three timing references (Ref 1, Ref 2, Ref 3). The node uses Reference 1 unless a failure occurs to that reference, in which case the node uses Reference 2. If Reference 2 fails, the node uses Reference 3, which is typically set to Internal Clock. Reference 3 is the Stratum 3 clock provided on the TCC2/TCC2P card. The options that appear depend on the Timing Mode setting.

–If the Timing Mode is set to External, your options are BITS-1, BITS-2, and Internal Clock.

–If the Timing Mode is set to Line, your options are the node's working OSCM cards, OSC-CSM cards, transponder (TXP) cards, muxponder (MXP) cards, and Internal Clock. Choose the cards/ports that are directly or indirectly connected to the node wired to the BITS source. Set Reference 1 to the card that is closest to the BITS source. For example, if Slot 5 is connected to the node wired to the BITS source, choose Slot 5 as Reference 1.

–If the Timing Mode is set to Mixed, both BITS references and the OSCM, OSC-CSM, TXP, or MXP cards are available, allowing you to set a mixture of external BITS clocks and OSCM, OSC-CSM, TXP, or MXP cards as timing references.

•BITS-1 Out/BITS-2 Out—Sets the timing references for equipment wired to the BITS Out backplane (ANSI) or MIC-C/T/P FMEC (ETSI) pins. BITS-1 Out and BITS-2 Out are enabled when BITS-1 Out and BITS-2 Out facilities are put in service. If Timing Mode is set to external, choose the OSCM, OSC-CSM, TXP, or MXP card used to set the timing. If Timing Mode is set to Line, you can choose an OSCM, OSC-CSM, TXP, or MXP card or choose NE Reference to have the BITS-1 Out and/or BITS-2 Out follow the same timing references as the network element (NE).

Note All TXP or MXP card client ports are available for timing regardless of the card's termination mode. TXP or MXP trunk ports can be a timing reference when ITU-T G.709 is set to OFF and the Termination Mode is set to LINE.

Note The system prevents BITS In and BITS Out timing to be set on the same node.

Step 4 Click Apply.

Step 5 Click the BITS Facilities tab.

Note The BITS Facilities section sets the parameters for your BITS-1 and BITS-2 timing references. Many of these settings are determined by the timing source manufacturer. If equipment is timed through BITS Out, you can set timing parameters to meet the requirements of the equipment.

•BITS In State—If Timing Mode is set to External or Mixed, set the BITS In State for BITS-1 and/or BITS-2 to IS (in service) depending on whether one or both BITS input pin pairs are connected to the external timing source. If Timing Mode is set to Line, set the BITS In State to OOS (out of service).

Step 7 If the BITS In State is set to OOS, continue with Step 8. If the BITS In State is set to IS, complete the following information:

Step 8 In the BITS Out area, complete the following information, as needed:

•Facility Type—(TCC2P only) Choose the BITS Out signal type, either DS1 or 64Khz+8Khz.

•BITS Out State—If equipment is connected to the node's BITS output pins on the backplane (ANSI) or MIC-C/T/P FMEC (ETSI) and you want to time the equipment from a node reference, set the BITS Out State for BITS-1 and/or BITS-2 to IS, depending on which BITS Out pins are used for the external equipment. If equipment is not attached to the BITS output pins, set the BITS Out State to OOS.

Step 9 If the BITS Out State is set to OOS, continue with Step 10. If BITS Out State is set to IS, complete the following information:

•Coding—Choose the coding used by your BITS reference, either B8ZS or AMI.

•Framing—Choose the framing used by your BITS reference, either ESF or SF (D4).

•AIS Threshold—If SSM is disabled or Super Frame is used, choose the quality level where a node sends an alarm indication signal (AIS) from the BITS 1 Out and BITS 2 Out backplane pins (ANSI) or MIC-C/T/P FMEC (ETSI). An AIS alarm is raised when the optical source for the BITS reference falls to or below the SSM quality level defined in this field.

•LBO—If an external device is connected to the BITS Out pins, sets the line build-out (LBO) distance between the ONS 15454 and an external device. If an external device is connected to BITS Out, choose the distance between the device and the ONS 15454. Options are: 0-133 ft. (default), 134-266 ft., 267-399 ft., 400-533 ft., and 534-655 ft. Line build out (LBO) relates to the BITS cable length. If an external device is not connected to BITS Out, leave this field set to the default.

Caution Internal timing is Stratum 3 and is not intended for permanent use. All ONS 15454 SONET (ANSI) or SDH (ETSI) nodes should be timed to a Stratum 2 or better primary reference source. Internal timing is appropriate for DWDM nodes.

–Dest Port is the port label reported on the front panel of the optical path destination card.

•Cl Service Type—Identifies the service type of the optical channel.

•Protection—Identifies the type of protection used for the optical channel:

–Optical paths for unprotected-east and unprotected-west optical channels are routed along one direction only in the network.

–Optical paths for Y-cable, fiber-switched, and client 1+1 optical channels are routed along two independent directions in the network.

•Op Bypass Site Name—Identifies where the optical channel is dropped and reinserted when it is not terminated on a TXP or MXP card (optical bypass).

Note If the word None appears in the Op Bypass Site Name column, no optical bypass is defined for the optical channel.

•Wavelength—Identifies the wavelength used for the optical channel. Table 7-2 lists the thirty-two available wavelengths.

•DWDM Interface Type—Identifies the DWDM interface type that is used for the optical channel:

–Transponder indicates that an transponder (TXP), muxponder (MXP), or DWDM pluggable port module is used for the optical channel.

–Line Card indicates that an ITU line card is used for the optical channel.

•DWDM Card Type—identifies the type of TXP or line card that is used for the optical channel. For information about card types supported by Cisco MetroPlanner, refer to the Cisco MetroPlanner DWDM Operations Guide.

Step 3 Return to your originating procedure (NTP).

NTP-G54 Provision and Verify a DWDM Network

Purpose

This procedure verifies the performance of all cable connections and cards in a network topology. You can also use this procedure to troubleshoot any problems with DWDM network set up.

b. Verify that no equipment (EQPT) alarms appear. If equipment failure alarms appear, investigate and resolve them before continuing. Refer to the Cisco ONS 15454 DWDM Troubleshooting Guide for procedures.

Step 3 Using the Cisco MetroPlanner Traffic Matrix (see Table 3-1) for your site, identify the first channel (ITU wavelength) to be provisioned. Use the TXP, MXP, or line card that corresponds to the selected wavelength.

Step 4 For the ITU wavelength identified in Step 3, create an OCHCC or OCHNC circuit using one of the following tasks:

.After creating the OCHCC or OCHNC circuit, return to this procedure and continue with Step 5.

Note Every time a channel is created in the DWDM network, the amplifiers automatically calculate the optical output power needed to maintain a constant power level on each channel. Automatic power control (APC) also starts every 60 minutes. If the span length changes, APC modifies amplifier gains and modifies express variable optical attenuation (VOA). For more information about APC, refer to the "Network Reference" chapter in the Cisco ONS 15454 DWDM Reference Manual.

Step 5 In node view (single-shelf mode) or multishelf view (multishelf mode), click the Circuits tab. Verify that the OCHCC or OCHNC created in Step 4 has a DISCOVERED status and an IS state. If so, continue with Step 6.

Step 6 Click the circuit and click Edit.

Step 7 In the Edit Circuit dialog box, click the State tab.

Step 8 In the Cross-Connections table, record all the nodes that appear in the Node column. These are the nodes that are in the circuit path. The first node is the circuit source, and the last node is the circuit destination.

Step 9 Display the circuit source node in node view (single-shelf mode), or shelf view (multishelf mode). If an OPT-PRE card is installed, complete the following steps. If not, continue with Step 10.

a. Display the OPT-PRE card in card view.

b. Click the Provisioning > Opt.Ampli.Line > Parameters tabs.

c. Check the value of the Port 2 (COM-TX) Signal Output Power:

–If the OPT-PRE card is not carrying traffic, the values will not match. Skip this step and go to Step 10.

–If the value is equal to or greater than the value shown in the Channel Power Ref table cell, continue with Step d.

–If the value is lower than the value shown in the Channel Power Ref table cell, contact your next level of support.

d. If a second OPT-PRE is installed, repeat Steps a through c for the second OPT-PRE card. If not, continue with Step 10.

Step 10 If an OPT-BST card is installed, complete the following steps. If not, continue with Step 11.

a. Display the OPT-BST card in card view.

b. Click the Provisioning > Opt.Ampli.Line > Parameters tabs.

c. check the value of the Port 6 (COM-TX) Signal Output Power:

–If the OPT-BST card is not carrying traffic, the values will not match. Skip this step and go to Step 11.

–If the value is equal to or greater than the value shown in the Channel Power Ref table cell, continue with Step d.

–If the value is lower than the value shown in the Channel Power Ref table cell, contact your next level of support.

d. If a second OPT-BST is installed, repeat Steps a through c for the second OPT-BST card. If not, continue with Step 11.

Step 11 If the node is a ROADM with 32WSS and 32DMX or 32DMX-O cards installed and the circuit is an Add/Drop circuit, complete the following steps. If not, continue with Step 12.

f. Locate the channel that carries the circuit and verify that the value in the Power column matches the value recorded in Step c, +/- 2 dB. If so, continue with Step g. If the value is lower, contact your next level of support.

Note Note If the 32DMX card is not carrying traffic, the values will not match and the verification must be skipped.

h. In the Selector area, click the West Side > Tx > Power > Add&Drop - Output Power parameters. Record the value under the Value column. If the value is not present, skip this step and continue with step i.

k. Locate the CHAN-TX port, 1 through 32, that corresponds to the circuit and verify that the value in the Power column matches the value recorded in step e., +/- 1 dB. If the value is lower, contact your next level of support.

Note Note If the 32WSS card is not carrying traffic, the values will not match and the above check must be skipped.

l. Repeat steps from b through k for cards that are installed on the east side.

b. In the Selector area, double-click the West Side > TX > Power parameters. Record the value in the Power.Add&Drop - Output Power Value column. If the value is not present, skip this step and continue with Step c.

e. Locate the port (CHAN-TX), 33 through 64, that corresponds to the circuit and verify that the value in the Power column matches the value recorded in step b., +/- 1 dB. If the value is lower, contact your next level of support.

Note Note If the 32WSS card is not carrying traffic, the values will not match and the verification must be skipped.

f. Repeat steps a through e or the cards installed on the east side of the node.

Step 13 Check the received power range:

a. Navigate to the node where the first TXP, MXP, or line card is installed.

Step 19 After the circuit status is DISCOVERED and its state is IS, click the circuit and then click Edit.

Step 20 In the Edit Circuit dialog box, click the State tab.

Step 21 In the Cross-Connections table, record all the nodes that appear in the Node column. These are the nodes that are in the circuit path. The first node is the circuit source, and the last node is the circuit destination.

•Are a circuit source or destination, and the circuit created in Step 4 did not originate or terminate on the same side (west or east).

For all the remaining nodes, no further checks are needed.

Step 23 Repeat Steps 9 through 22 for all OCHCC or OCHNC circuits listed in your Traffic Matrix report. If a node fails any test, verify the setup and configuration and then repeat the test. If the test fails again, refer to the next level of support.

After all tests are successfully completed and no alarms exist in the network, the network is ready for service.

Stop. You have completed this procedure.

NTP-G56 Verify the OSNR

Purpose

This procedure verifies the optical signal-to-noise ratio (OSNR). The OSNR is the ratio between the signal power level and the noise power level.

Step 2 Using an optical spectrum analyzer, check the received OSNR for each transmitted channel on both ends of the span. Identify the last OSC-CSM, OPT-PRE, or OPT-BST MON port that the channel passes through before it is dropped. If OPT-PRE cards are installed with an OPT-BST, OPT-BST-E, or OSC-CSM card, use the OPT-PRE MON port.

Note For OSNR values for each card class, refer to the "Card Reference" chapter in the Cisco ONS 15454 DWDM Reference Manual.

Step 3 If the OSNR is too low, check the following, depending on your node configuration:

Note The purpose of this step is not to improve the signal-to-noise ratio (SNR), but to match the per-channel power level within the RX port power range.

NTP-G142 Perform a Protection Switch Test

Purpose

This procedure tests the optical path, client TXP cards, MXP cards, and Y-cable protection groups in your network for proper operation. The test signals can be generated by either the actual client device or a test set (whichever is available). Cisco recommends that you repeat this test at each node in the network where protection group traffic is dropped.

Tools/Equipment

A list of protection groups. This information is provided in the Cisco MetroPlanner Traffic Matrix.

A test set or actual client device that provides the required payload for the circuits that are provisioned.

Prerequisite Procedures

None

Required/As Needed

As needed

Onsite/Remote

Onsite; personnel are required to be on site at each end of the circuit under test.

Step 4 Repeat Step 3 for each Y-cable protection group at the node. When all protection groups are verified, continue with the next step.

Step 5 Physically connect the transmitter of the client or test set to either Port 10 or Port 12 of the Y-cable module protecting the test circuit. (See Table 3-3 and Table 3-4.)

Step 6 If you connected the transmitter to Port 10, connect the client or test set receiver to Port 5 on the Y-cable module. If not, connect the client or test set receiver to Port 11 on the Y-cable module.

Step 7 At the far-end site for the test circuit, physically loop the Y-cable module as follows:

a. If this is the first client on the Y-cable module, loop Port 10 to Port 5 on the far-end Y-cable module.

b. If this is the second client on the Y-cable module, loop Ports 11 and 12 on the far-end Y-cable module.

Step 8 At the near-end site for the test circuit, place the client device or test set into service and begin transmitting the required payload.

Step 4 In the Local Node Id text entry box, enter the local node ID in the form of an IP address.

Note Do not set the LMP Local Node ID to another IP address in use on the network. This introduces a duplicate IP address in the network for traffic going to the IP address that is used as the LMP Local Node ID. It is recommended to set the LMP Local Node ID to the node's IP address since this will not introduce a duplicate IP address in the network.

Step 5 If you are going to use LMP to manage a control channel between a Calient PXC node and a Cisco ONS 15454DWDMnode, ensure that the LMP-WDM check box is unchecked.

Step 6 If you are going to use LMP to manage a control channel between ONS 15454 nodes, check the LMP-WDM checkbox and use the Role drop-down box to choose either PEER or OLS.

•Choose PEER to use LMP to manage links between two nodes where the other node is configured as OLS.

•Choose OLS to use LMP to manage links between two nodes where the other node is configured as PEER.

The role selection is only available when LMP-WDM is enabled on the local node. Both the local and remote nodes must be configured with LMP-WDM enabled.

Step 7 Click Apply.

Step 8 In the Status area, verify that the Operational State is Up. This indicates that LMP is enabled and the link is active.

Step 9 Return to your originating procedure (NTP).

DLP-G373 Create LMP Control Channels

Purpose

This task creates, edits, or deletes one or more LMP control channels between pairs of Cisco ONS 15454 nodes or between a Calient PXC and a Cisco ONS 15454

Note The values of the Admin State, Requested Hello Interval, Min Hello Interval, Max Hello Interval, Requested Hello Dead Interval, Min Hello Dead Interval, and Max Hello Dead Interval fields correspond to the values specified for these fields in the NODE > lmp section of the node view Provisioning > Defaults tabs. If you change the NODE > lmp values, those values are reflected as defaults in the Create LMP Control Channel dialog box (Figure 6-3). You can change the default values using the dialog box. However, the NODE > lmp values are always used as the initial defaults.

Figure 6-3 Create LMP Control Channel Dialog Box

Step 3 In the Create LMP Control Channel dialog box, complete the following:

•Admin State—Click this drop-down box and select unlocked (if you are using an ETSI shelf or IS (if you are using an ANSI shelf) to establish the Control Channel; otherwise, choose locked, disabled (ETSI) or OOS-DSBLD (ANSI) to set the Control Channel to out of service.

•Local Port—Click this drop-down box and select Routed if the Control Channel is to be sent over the control plane or management network; otherwise, if the Control Channel is to be sent over the same fiber as the traffic (either in the payload or in the overhead), select one of the available traffic ports.

•Local Port Id (Display only)—Displays the local port identifier assigned by the node.

•Remote Node IP Address—In dotted decimal format, enter the number that identifies the IP address of the remote node (either a Calient PXC peer node or a Cisco ONS 15454 node) where the Control Channel will be established.

•Remote Node ID—Initially, CTC autopopulates this value to the Remote Node IP Address you just assigned. However, you can change the identifier to any non-zero 32-bit integer in dotted decimal format (for example, 10.92.29.10).

Note Do not set the LMP Local Node ID to another IP address in use on the network. This introduces a duplicate IP address in the network for traffic going to the IP address that is used as the LMP Local Node ID. It is recommended to set the LMP Local Node ID to the node's IP address since this will not introduce a duplicate IP address in the network.

•Requested Hello Interval—Enter the Requested Hello Interval in milliseconds (ms). Before sending Hello messages, the HelloInterval and Hello Dead Interval parameters must be established by the local and remote nodes. These parameters are exchanged in the Config message. The Hello Interval indicates how frequently LMP Hello messages will be sent; the interval must be in the 300 ms to 5000 ms range. The Min Hello Interval must be less than or equal to the Requested Hello Interval and the Requested Hello Interval must be less than or equal to the Max Hello Interval.

•Min Hello Interval—Enter the minimum Hello Interval in milliseconds. When the two nodes negotiate for the Hello Interval, the value you enter here will be the minimum Hello Interval acceptable for the local node. The Min Hello Interval must be in the 300 ms to 5000 ms range. The Min Hello Interval must be less than or equal to the Requested Hello Interval and the Requested Hello Interval must be less than or equal to the Max Hello Interval.

•Max Hello Interval—Enter the maximum Hello Interval in milliseconds. When the two nodes negotiate for the Hello Interval, the value you enter here will be the maximum Hello Interval acceptable for the local node. The Max Hello Interval must be in the 300 ms to 5000 ms range. The Min Hello Interval must be less than or equal to the Requested Hello Interval and the Requested Hello Interval must be less than or equal to the Max Hello Interval.

•Requested Hello Dead Interval—Enter the Requested Hello Dead Interval in milliseconds. The Requested Hello Dead Interval indicates how long a device should wait to receive a Hello message before declaring a control channel dead. The Requested Hello Dead interval must be in the 2000 ms to 20000 ms range. The Min Hello Dead Interval must be less than or equal to the Requested Hello Dead Interval and the Requested Hello Dead Interval must be less than or equal to the Max Hello Dead Interval.

Note The Requested Hello Dead Interval must be at least three times greater than the Requested Hello Interval.

•Min Hello Dead Interval—Enter the minimum Hello Dead Interval in milliseconds. The minimum Hello Dead Interval must be in the 2000 ms to 20000 ms range. The minimum Hello Dead Interval must be less than or equal to the Requested Hello Dead Interval and the Requested Hello Dead Interval must be less than or equal to the Max Hello Dead Interval. When the two nodes negotiate for the Hello Dead Interval, the value you enter here will be the minimum Hello Dead Interval acceptable for the local node.

Note The value of the Min Hello Dead Interval must be greater than the Min Hello Interval.

•Max Hello Dead Interval—Enter the maximum Hello Dead Interval in milliseconds. This interval must be in the 2000 ms to 20000 ms range. The Min Hello Dead Interval must be less than or equal to the Requested Hello Dead Interval and the Requested Hello Dead Interval must be less than or equal to the Max Hello Dead Interval. When the two nodes negotiate for the Hello Dead Interval, the value you enter here will be the maximum Hello Dead Interval acceptable for the local node.

Note The Max Hello Dead Interval must be greater than the Max Hello Interval.

Step 4 Click OK to accept the parameters you have entered, or click Cancel to return to the Control Channels tab without creating a control channel.

Step 5 If you created a control channel, verify that the parameters for the new Control Channel appear properly in the Control Channels tab.

Note The Actual Hello Interval and Actual Hello Dead Interval parameters reflect the values of these parameters as a result of the negotiated agreement of the local and remote nodes. They may be different than the requested values.

Step 6 After the LMP control channel has been created, observe the status of the channel in the Operational State column of the Control Channels tab, and take the appropriate action as shown in the following list:

•Up: The control channel contacted the far-end node and successfully negotiated a control channel.

•Down: LMP is enabled and the link is inactive. Check that the Admin State of the control channel is unlocked (ETSI) or IS (ANSI) and not disabled (ETSI) or OOS-DSBLD (ANSI). If the state still does not transition to UP, the far-end control channel might have disjointed Hello negotiation times that prevent a control channel from transitioning to the UP state. For example, the local 15454 ONS Min Hello Interval and Max Hello Interval is 900-1000, and the remote Min Hello Interval and Max Hello Interval is 1100-1200.

•Config Send: The connection could not be made to the remote node. Check to make sure the Remote Node IP address and Remote Node ID addresses are correct.

Note Do not set the LMP Local Node ID to another IP address in use on the network. This introduces a duplicate IP address in the network for traffic going to the IP address that is used as the LMP Local Node ID. It is recommended to set the LMP Local Node ID to the node's IP address since this will not introduce a duplicate IP address in the network.

•Config Received: The local node sent a configuration request to the remote node and received a response of either ConfigNack or ConfigAck.

Step 7 To delete a control channel, click on the channel row to highlight it and click Delete. A confirmation dialog box appears that allows you to click OK or Cancel.

Step 8 To edit a control channel, click on the channel row to highlight it and click Edit. A dialog box similar to Figure 6-3 appears that allows you to change the control channel parameters. You can then click OK or Cancel.

•Admin State—Click this drop-down box and select unlocked (for ETSI shelves) or IS (for ANSI shelves) to put the TE Link in service; otherwise, choose locked, disabled (ETSI) or OOS-DSBLD (ANSI) to set the TE Link to out of service.

•Remote Node ID—Click the drop-down box and select a remote node for the other end of the TE link.

•Remote TE Link ID—Enter an unsigned 32-bit value (such as 0x00000001) to identify the remote node identifier for the other end of the TE Link.

•Mux Capability—Choose Lambda Switch from the drop-down box. Even though there are other choices, you must choose Lambda Switch because the ports that can be selected are restricted to DWDM client ports, which means they are lambda switched onto the DWDM trunk port for transport across the DWDM network.

Step 4 Click OK to accept the parameters you have entered and create the TE Link, or click Cancel to return to the Control Channels tab without creating a TE Link.

Step 5 If you created a TE Link, verify that the parameters for the new TE Link now appear properly in the TE Links tab.

Step 6 After the TE Link has been created, observe the status of the TE Link in the Operational State column of the TE Links pane, and take the appropriate action as shown in the following list:

•Up: The TE Link is active.

•Down: Check that the Admin State of the TE Link is unlocked (ETSI) or IS (ANSI) and not disabled (ETSI) or OOS-DSBLD (ANSI). The TE link will not transition to the Up state until a data link has been provisioned.

•Init: Verify that the Remote Node IP Address and Remote TE Link ID values are correct for the remote node. Verify that the remote node is using the Cisco ONS 15454 IP address for its remote node IP and that the remote node is using the local TE link index for its remote TE link index.

Step 7 To delete a TE link, click on the link row to highlight it and click Delete. A confirmation dialog box appears that allows you to click OK or Cancel.

Step 8 To edit a TE link, click on the link row to highlight it and click Edit. A dialog box similar to Figure 6-4 appears that allows you to change the TE link parameters. You can then click OK or Cancel.

Step 9 Return to your originating procedure (NTP).

DLP-G378 Create LMP Data Links

Purpose

This task creates, edits, or deletes one or more data links, which define the node's transport parameters. CTC supports up to 256 LMP data links.

Tools/Equipment

None

Prerequisite Procedures

The PPM on a TXP or MXP card where you will create a data link should already be provisioned or preprovisioned (the line rates and payloads must be assigned). Card and PPM provisioning should be already completed. Otherwise, the ports will not show up in the local port drop down window. To do this, complete the following NTP:

Note A port cannot be deleted if it is being used by a data link. A card cannot be deleted if any of its ports are being used by data links. Changing the state of the port impacts the state of a data link using the port.

•Local Port—Click this drop-down box and choose one of the available local ports for the data link.

•Local Port Id (Display Only)—The local port identifier.

•Data Link Type—Click this drop-down box and choose Port or Component. A data link is a "port" or a "component link" on each node where it terminates depending on the multiplexing capability of the endpoint on that link; component links are multiplex capable, whereas ports are not multiplex capable.

•Local TE Link Id—Click this drop-down box and choose an identifier for one of the local TE Links that has already been created.

•Remote Port Id—Enter an unsigned 32-bit value (such as 0x00000001) to identify the remote node identifier for the other end of the data link.

Step 4 Click OK to accept the parameters you have entered and create the data link, or click Cancel to return to the Data Links tab without creating a data link.

Step 5 If you created a Data Link, verify that the parameters for the new data link now appear properly in the Data Links tab.

Step 6 After the data link has been created, observe its status in the Operational State column of the Data Links tab, and take the appropriate action as shown in the following list:

•Up-Alloc or Up-Free: If the data link state doesn't transition to Up-Alloc or Up-Free, verify that the port is in service. Verification must be done using the CTC card view port provisioning tabs for the cards. (The difference between Up-Alloc and Up-Free is that an Up-Alloc data link is allocated for data traffic. An Up-Free data link is not allocated for traffic. The far end is either not ready to receive traffic through this port, or the path is being used as a backup in case some other allocated data link goes down).

•Down: The data link will be in the Down state if the port is not unlocked or not in-service. Verify that the remote port ID for the far-end data link is correct. On the far end, verify that the data link is using the Local Port Id as its remote port ID.

Step 7 To delete a data link, click on the data link row to highlight it and click Delete. A confirmation dialog box appears that allows you to click OK or Cancel.

Step 8 To edit a data link, click on the data link row to highlight it and click Edit. A dialog box similar to Figure 6-5 appears that allows you to change the data link parameters. You can then click OK or Cancel.

Step 9 Return to your originating procedure (NTP).

NTP-G57 Create a Logical Network Map

Purpose

This procedure allows a Superuser to create a consistent network view for all nodes on the network, meaning all users see the same network view on their login nodes.

Tools

None

Prerequisite Procedures

This procedure assumes that network turn up is complete.

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Superuser

Step 1 Complete the "DLP-G46 Log into CTC" task at a node on the network where you want to create the network map. If you are already logged in, continue with Step 2.

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

Step 3 Change the position of the nodes in the network view according to your site plan.

a. Click a node to select it, then drag and drop the node icon to a new location.

Step 4 On the network view map, right-click and choose Save Node Position from the shortcut menu.

Step 5 Click Yes in the Save Node Position dialog box.

CTC opens a progress bar and saves the new node positions.

Note Retrieve, Provisioning, and Maintenance users can move nodes on the network map, but only Superusers can save new network map configurations. To restore the view to a previously saved version of the network map, right-click the network view map and chooseReset Node Position.