This procedure creates, deletes, and manages OCHCC circuits. OCHCCs create an end-to-end optical management path between TXP, MXP, GE_XP, or 10GE_XP (when provisioned as TXPs or MXPs) client ports, or between ITU-T trunk ports. ITU-T line cards include: OC48/STM64 EH, OC192 SR/STM64, MRC-12, MRC-2.5-12, and MRC-2.5G-4. The OCHCC circuit is transported by an OCH trail circuit that is associated to one or more OCHNC circuits.

Step 4 If the client TXP, MXP, or ITU-T line cards are installed in a multishelf node, continue with Step 5. If not, complete the following substeps:

a. Use the information obtained from the Cisco MetroPlanner traffic matrix report in Step 1 to complete the "DLP-G344 Verify Provisionable and Internal Patchcords" task. If provisionable patchcords (PPCs) exist between the nodes containing the TXP/MXP/ITU-T line cards and the DWDM nodes at each end of the OCHCC, continue with Step 5. If not, continue with Step b.

Step 5 If the client TXP/MXP/ITU-T line cards are installed in a multishelf node, use the information obtained from the Cisco MetroPlanner traffic matrix report in Step 1 to create internal patchcords between the 32DMX, 32DMX-O, or 32DMX-L ports and the TXP/MXP trunk ports using the "DLP-G354 Create an Internal Patchcord Manually" task. Create the internal patchcords on both the source and destination nodes of each OCHCC path. If the TXP/MXP/ITU-T line cards are not installed in a multishelf node, continue with Step 6.

Note OCHCCs can be created on preprovisioned client cards or physically installed client cards.

Note If you want the OCHCC circuit to provision the client card trunk port's ITU-T G.709, FEC, SD and SF threshold settings and Mapping parameters, you must place the client card trunk ports out of service.

Note Creating an OCHCC circuit automatically creates an OCH trail circuit between the OCHCC source and destination client card trunk ports. The OCH trail circuit is created for the first OCHCC between two MXP cards. The OCH trail circuit is used by succeeding OCHCCs created between the MXP cards. When the OCH trail is created, it is assigned a system-generated name in the format circuit-type_NE-name::unique sequence number. To edit the OCH trail circuit name, complete the "DLP-G425 Edit an OCH Trail Circuit Name" task.

Note If trunk ports are connected by a peer-to-peer provisionable patchcord (PPC), an OCH trail is not created.

Note The OCH Wlen (wavelength) parameter on the Circuits page can be used to determine the OCHCC and OCH trail associations.

Step 5 In the Circuit area of the Circuit Attributes page (Figure 7-1), provision the OCHCC circuit attributes:

•Name—Assign a name to the OCHCC. The name can be alphanumeric and up to 48 characters (including spaces). Circuit names should be 44 characters or less if you want the ability to create monitor circuits. If you leave the field blank, Cisco Transport Controller (CTC) assigns a default name to the circuit.

•Type—(Display only) OCHCC.

•Size—Defines the circuit payload type and rate. Two fields are provided. The first specifies the payload type. Choose a payload type, then choose the rate in the next field. Table 7-1 provides the OCHCC payload types and rates.

Note The payload type and rate must match the PPM provisioning on the client cards at the source and destination nodes.

Table 7-1 OCHCC Client Rates

Payload Type

Rates

SONET/SDH

OC-192 (ANSI)/STM-64 (ETSI)—9.92 Gbps

OC-48 (ANSI)/STM-12 (ETSI)—2.48 Gbps

OC-12 (ANSI)/STM-4 (ETSI)—622 Mbps

OC-3 (ANSI)/STM-1 (ETSI)—155 Mbps

Ethernet

10GE—One Gigabit Ethernet 11.25 Gbps

1GE—One Gigabit Ethernet 1.125 Gbps

FC/FICON

10GFC—Fibre Channel 10 Gbps

4GFC—Fibre Channel 4 Gbps

2GFC—Fibre Channel 2.125 Gbps

1GFC—Fibre Channel 1.06 Gbps

4GFICON—FICON 4 Gbps

2GFICON—FICON 2.125 Gbps

1GFICON—FICON 1.06 Gbps

Data Storage

ESCON—Enterprise System Connection 200 Mbps (IBM signal)

ISC Peer—InterSystem Coupling Link 3 (ISC3)

ISC3 Peer 1G—InterSystem Coupling Link 3 (ISC3) 1 Gbps

ISC3 Peer 2G—InterSystem Coupling Link 3 (ISC3) 2 Gbps

ISC COMPAT—InterSystem Coupling Link 1 (ISC1)

Video

HDTV—High Definition Television

SDI/DI—Serial Digital Interface and Digital Video signal type 1

DV6000—Proprietary signal from video vendor

Other

Pass Through—Creates a pass-through OCHCC

•OCHNC Wavelength—Provides three fields to define the wavelength that the OCHCC will use to travel across the OCH network. Choose a wavelength from the first field. In the second field, you can change the wavelength band by choosing either C Band or L Band. In the third field, you can indicate whether odd or even C-band or L-band wavelengths appear. See Table 7-2 and Table 7-3 for C-band and L-band wavelengths.

Note The OCHNC wavelength must match the trunk wavelength provisioned on the source and destination TXP or MXP cards. If the wavelengths do not match, the card will not appear as a source or destination.

•Bidirectional—(Display only) OCHCCs are bidirectional. This field cannot be changed.

•Protection—Check to create a splitter-protected OCHCC (only MXPP/TXPP cards will be selectable as circuit endpoints).

Figure 7-1 OCHCC Attributes Page

Step 6 In the State area of the Circuit Attributes page, provision the OCHCC state attributes:

•State—Provisions the OCHCC circuit state. The state can be IS (ANSI)/Unlocked (ETSI) or OOS,DSBLD (ANSI)/Locked,Disabled (ETSI).

•Apply to OCHCC ports—If checked, applies the state chosen in the Apply to OCHCC ports drop-down list to the OCHCC client ports. For TXP, MXP, TXPP, or MXPP cards, the administrative state will apply to the client and all trunk ports. For ITU-T-compliant line cards, the administrative state will apply to the trunk port only. The states that you can apply include: IS (ANSI)/Unlocked (ETSI), OOS,DSBLED (ANSI)/Locked,Disabled (ETSI), and IS,AINS (ANSI)/Unlocked,AutomaticInService (ETSI).

Step 7 Click Next.

Step 8 In the Source area, choose the source node from the Node drop-down list, then choose the source shelf (multishelf nodes only) from the Shelf drop-down list, the source slot from the Slot drop-down list, and, if needed, the source port from the Port drop-down list.

If no nodes appear in the Node drop-down list, complete the following steps:

a. Click Back and review your circuit attribute settings. Verify that they are set to the client attributes provisioned on the client cards. If necessary, click Cancel and complete the "DLP-G345 Verify OCHCC Client Ports" task to verify the client settings.

If these steps do not solve the problem, refer to your next level of support.

Step 9 Click Next.

Step 10 In the Destination area, choose the destination node from the Node drop-down list, then choose the destination shelf (multishelf nodes only) from the Shelf drop-down list, the destination slot from the Slot drop-down list, and, if needed, the destination port from the Port drop-down list.

If no nodes appear in the Node drop-down list, complete the following steps:

a. Click Back and review your circuit attribute settings. Verify that they are set to the client attributes provisioned on the client cards. If necessary, click Cancel and complete the "DLP-G345 Verify OCHCC Client Ports" task to verify the client settings.

Step 14 Complete the "DLP-G438 Set OCH Routing Preferences" task. Skip this step and continue with Step 15 if no constraints are needed. If the trunk ports are already connected by an existing OCH Trail (MXP case) or by a direct PPC link, the OCH Circuit Routing Preferences page appears in read-only mode; all buttons are disabled. Continue with Step 15.

Step 15 Click Finish. The OCHCC and its OCH trail appear in the Circuits page. After the circuit status has been verified, the DISCOVERED status appears in the Status column.

If the OCHCC status does not change to DISCOVERED within 2 to 3 minutes, contact your next level of support.

Step 16 Return to your originating procedure (NTP).

DLP-G347 Delete Optical Channel Client Connections

Note If you are deleting more than half of all the active OCHCCs, Cisco recommends that you delete them two at a time to allow for proper power compensation. You do not need to delete the active OCHCCs two at a time if you are deleting all them.

•Change drop port admin state—Check this box if you want to change the circuit source and destination port administrative state. After checking the box, choose one of the following administrative states:

–IS (ANSI) or Unlocked (ETSI)—Puts the ports in service.

–IS,AINS (ANSI) or UnlockedAutomaticInService (ETSI)—Puts the ports in automatic in service.

–OOS,DSBLD (ANSI) or Locked,disabled (ETSI)—Removes the ports from service and disables them.

–OOS,MT (ANSI) or Locked,maintenance (ETSI)—Removes the ports from service for maintenance.

•Notify when completed—If checked, the CTC Alerts confirmation dialog box notifies you when the OCHCC is deleted. During this time, you cannot perform other CTC functions. If you are deleting many OCHCCs, waiting for confirmation might take a few minutes. Circuits are deleted whether or not this check box is checked.

Note The CTC Alerts dialog box will not automatically open to show a deletion error unless you checked All alerts or Error alerts only in the CTC Alerts dialog box. For more information, see the "DLP-G53 Configure the CTC Alerts Dialog Box for Automatic Popup" task. If the CTC Alerts dialog box is not set to open automatically, the red triangle inside the CTC Alerts toolbar icon indicates that a notification exists.

Step 8 Complete one of the following:

•If you checked Notify when completed, the CTC Alerts dialog box appears. If you want to save the information, continue with Step 9. If you do not want to save the information, continue with Step 10.

•If you did not check Notify when completed, the Circuits page appears. Continue with Step 11.

Step 9 If you want to save the information in the CTC Alerts dialog box, complete the following substeps. If you do not want to save it, continue with Step 11.

a. Click Save.

b. Click Browse and navigate to the directory where you want to save the file.

Step 1 In the OCH Circuit Attributes Preferences page, change the trunk settings as necessary. The settings provisioned here can only be provisioned on the ports when the ports are out of service. If the ports are in service, these parameters must be the same as the source and destination card ports. If not, the OCHCC cannot be created. You can view the current trunk settings (display only) in the Current Values area.

•To change any of the trunk settings, complete the following in the Provisioning Values area:

–ITU-T G.709 OTN—Choose Enable or Disable to set or disable the IEEE G.709 monitoring on the optical transport network. If the OCHCC source or destination is an MXP_2.5G_10E, MXP_2.5G_10E_C, or MXP_2.5G_10E_L card, the ITU-T G.709 OTN parameter must always be checked. If ITU-T G.709 OTN is checked, the MXP_MR_2.5G and MXPP_MR_2.5G cards will not appear as OCHCC source and destination options.

–FEC—Choose the type of FEC: Disabled, Standard, or Enhanced. The options that appear depend on the card type.

–SD BER—Choose the signal degrade bit error rate.

–Mapping—Sets the mapping for the TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, MXP_MR_10DME_C, and MXP_MR_DME_L cards: Not Used, ODUMultiplex (client SONET/SDH payload), Asynchronous, or Synchronous. The choices available depend on the card. If you set mapping to Synchronous, the client signal is mapped into the OTU2 signal without justification of the payload because the client signal timing (the timing source) is the same as the trunk output timing. If you set mapping to Asynchronous, the trunk timing is disconnected from the client timing (because the network element [NE] is the timing source), so justification is needed to map the client signal (OC192/STM64) to OTU2 trunk output.

Note When you create a 4xOC-48 OCHCC circuit, you need to select the G.709 and Synchronous options. A 4xOC-48 OCHCC circuit is supported by G.709 and synchronous mode. This is necessary to provision a 4xOC-48 OCHCC circuit.

Note If the OCHCC source or destination is an MXP_2.5G_10E, MXP_2.5G_10E_C, or MXP_2.5G_10E_L card, the Mapping parameter must always be set to Synch.

•Set the protection in the Protection area, as needed. The fields in the Protection area are disabled if the OCHCC is not protected and for OCH Trails.

–Revertive—If checked, traffic reverts to the working card after failure conditions remain corrected for the amount of time entered in the Reversion Time field.

–Reversion Time—Sets the reversion time when Revertive is checked. 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 card after conditions causing the switch are cleared.

Step 1 In the OCH Circuit Routing Preferences page, view the circuit route. The new OCHCC appears with blue span arrows. Moving your cursor over the arrow displays span information including source, destination, and span loss. Complete the following steps to manually provision the routing constraints.

a. In the circuit map area, click a node that you want to include or exclude from the circuit route.

b. Click Include or Exclude. The node name will appear under the Included nodes or Excluded nodes list. Include and Exclude cannot be applied to source or destination nodes.

c. Repeat Steps a and b until the circuit routing constraints are complete. To remove a node from the Included nodes or Excluded nodes list, click the node in the list and click Remove. To move a node up or down in the routing sequence, click the node in the list and click Up or Down.

Note Use the Reset button as needed to clear the constraints and set the default routing.

d. To force the circuit route through specific links, click Advanced. Select the sides where the circuit must cross this node and click OK:

–No Side Constraints—Uncheck.

–Side In—Choose the first side from the drop-down list.

–Side Out—Choose the second side from the drop-down list.

Note All forced links appear in yellow.

e. Click Apply. CTC verifies the circuit route. If the route is valid, a "Routing evaluation succeeded." message appears. If this message appears, click OK. If the route is not valid, a Route Error dialog box appears with an error message. If an error message appears, click Close to close the error dialog box and repeat Steps a through e until the circuit route is successfully validated.

f. If the OCHCC is protected, repeat Steps a through e for the protect trunk ports.

Step 5 In the Circuit area of the Circuit Attributes page, provision the OCH trail circuit attributes (Figure 7-2):

•Name—Assign a name to the OCH trail. The name can be alphanumeric and up to 48 characters (including spaces). Circuit names should be 44 characters or less if you want the ability to create monitor circuits. If you leave the field blank, CTC assigns a default name to the circuit.

•Type—(Display only) OCHTRAIL.

•Size—(Display only) Equipped non specific is the default.

•OCHNC Wavelength—Choose a band (either C Band or L Band) in the lower drop-down list. Then, choose the OCHNC wavelength that you want to assign to the OCH trail circuit in the upper drop-down list. See Table 7-2 and Table 7-3 for C-band and L-band wavelengths.

•Bidirectional—This parameter does not apply to OCH trail circuits.

•State—Provision the OCH trail circuit state. The state can be IS,AINS (ANSI)/Unlockedautomatic inservice (ETSI) or OOS,DSBLED (ANSI)/Locked,Disabled (ETSI).

•Apply to trunk ports—Check this box if you want to provision the administrative state of the OCH trail trunk ports. If checked, choose the state in the next field, either IS (ANSI)/Unlocked (ETSI) or OOS,DSBLED (ANSI)/Locked,Disabled (ETSI).

Figure 7-2 OCH Trail Attributes Page

Step 6 Click Next.

Step 7 In the Circuit Source area, choose the source node from the Node drop-down list, then choose the source shelf (multishelf nodes only) from the Shelf drop-down list, the source slot from the Slot drop-down list, and, if needed, the source port from the Port drop-down list. For most cards, the port will be automatically chosen.

The source In and Out shelf (multishelf nodes only), slot, and port appear under the OTS Lines area.

Step 8 Click Next.

Step 9 In the Circuit Destination area, choose the destination node from the Node drop-down list (only the source node will be available because the source and destination nodes are the same), then choose the destination shelf (multishelf nodes only) from the Shelf drop-down list, the destination slot from the Slot drop-down list, and, if needed, the destination port from Port drop-down list.

The destination In and Out shelf (multishelf only), slot, and port appear under the OTS Lines area to show the destination in and out shelf, slots, and ports.

Step 13 Complete the "DLP-G438 Set OCH Routing Preferences" task. Skip this step and continue with Step 14 if no constraints are needed. If the trunk ports are already connected by an existing OCH Trail (MXP case) or by a direct PPC link, the OCH Circuit Routing Preferences page appears in read-only mode; all buttons are disabled. Continue with Step 14.

Step 14 Click Finish. The Create Circuit wizard closes and the OCH trail circuit appears in the Circuits table with a DISCOVERED status in the Status column. (The circuit might take a few minutes to come up, depending on the size of the network.)

Step 15 Return to your originating procedure (NTP).

DLP-G418 Delete an Optical Channel Trail

Note If you are deleting more than half of all the active OCH trails, Cisco recommends that you delete them two at a time to allow for proper power compensation. You do not need to delete the active OCH trails two at a time if you are deleting all of them.

•Change drop port admin state—Check this box if you want to change the administrative state for the circuit source and destination ports. After checking the box, choose one of the following administrative states:

–IS (ANSI) or Unlocked (ETSI)—Puts the ports in service.

–IS,AINS (ANSI) or UnlockedAutomaticInService (ETSI)—Puts the ports in automatic in service.

–OOS,DSBLD (ANSI) or Locked,disabled (ETSI)—Removes the ports from service and disables them.

–OOS,MT (ANSI) or Locked,maintenance (ETSI)—Removes the ports from service for maintenance.

•Notify when completed—If checked, the CTC Alerts confirmation dialog box indicates when the OCH trail is deleted. During this time, you cannot perform other CTC functions. If you are deleting many OCH trails, waiting for confirmation might take a few minutes. Circuits are deleted whether or not this check box is checked.

Note The CTC Alerts dialog box will not automatically open to show a deletion error unless you checked All alerts or Error alerts only in the CTC Alerts dialog box. For more information, see the "DLP-G53 Configure the CTC Alerts Dialog Box for Automatic Popup" task. If the CTC Alerts dialog box is not set to open automatically with a notification, the red triangle inside the CTC Alerts toolbar icon indicates that a notification exists.

Step 8 Complete one of the following:

•If you checked Notify when completed, the CTC Alerts dialog box appears. If you want to save the information, continue with Step 9. If you do not want to save the information, continue with Step 10.

•If you did not check Notify when completed, the Circuits page appears. Continue with Step 11.

Step 9 If you want to save the information in the CTC Alerts dialog box, complete the following steps. If you do not want to save it, continue with Step 11.

a. Click Save.

b. Click Browse and navigate to the directory where you want to save the file.

DLP-G105 Provision Optical Channel Network Connections

Purpose

This task creates an OCHNC between two 32WSS, 32WSS-L, 40-WSS-C, 32MUX, 32MUX-O, 40-MUX-C, or 4MD-xx.x cards to create a passive optical path between two DWDM nodes. OCH trails, which carry OCHCC circuits, are associated to the OCHNCs.

Step 5 In the Circuit area of the Circuit Attributes page, provision the OCHNC circuit attributes (Figure 7-3):

•Name—Assign a name to the OCHNC. The name can be alphanumeric and up to 48 characters (including spaces). Circuit names should be 44 characters or less if you want the ability to create monitor circuits. If you leave the field blank, CTC assigns a default name to the circuit.

•Type—(Display only) OCHNC.

•Size—(Display only) Equipped non specific is the default.

•OCHNC Wavelength—Choose a band (either C Band or L Band) in the lower drop-down list. Then, choose the wavelength that you want to provision in the upper drop-down list. See Table 7-2 and Table 7-3 for C-band and L-band wavelengths.

•Bidirectional—Check this box to create a bidirectional OCHNC; uncheck it to create a unidirectional OCHNC.

•OCHNC DCN—Check this box to create an OCHNC DCN. The OCHNC DCN establishes preliminary connectivity between nodes that lack LAN or optical service channel (OSC) connections. After the OCHNC is created, you create a GCC termination to provide permanent communications channel between the nodes. See the "DLP-G76 Provision DCC/GCC Terminations" task.

•State—Provisions the OCHNC circuit state. The state can be IS,AINS (ANSI)/Unlocked, automatic in-service (ETSI) or OOS,DSBLED (ANSI)/Locked,Disabled (ETSI).

Figure 7-3 OCHNC Attributes Page

Step 6 Click Next.

Step 7 In the Circuit Source area, choose the source node from the Node drop-down list, then choose the source shelf (multishelf nodes only) from the Shelf drop-down list, the source slot from the Slot drop-down list, and, if needed, the source port from the Port drop-down list.

The source In and Out shelf (multishelf nodes only), slot, and port appear under the OTS Lines area.

Step 8 Click Next.

Step 9 In the Circuit Destination area, choose the destination node from the Node drop-down list, then choose the destination shelf (multishelf nodes only) from the Shelf drop-down list, the destination slot from the Slot drop-down list, and, if needed, the destination port from the Port drop-down list.

The destination In and Out shelf (multishelf nodes only), slot, and port appear under the OTS Lines area.

Step 10 Click Next.

Step 11 Complete the "DLP-G438 Set OCH Routing Preferences" task. Skip this step and continue with Step 12 if no constraints are needed. If the trunk ports are already connected by an existing OCH Trail (MXP case) or by a direct PPC link, the OCH Circuit Routing Preferences page appears in read-only mode; all buttons are disabled. Continue with Step 12.

Step 12 Click Finish. The Circuit Creation wizard closes and the new OCHNC appears in the Circuits table with a DISCOVERED status in the Status column. (The circuit might take a few minutes to come up, depending on the size of the network.)

Step 13 Return to your originating procedure (NTP).

DLP-G106 Delete Optical Channel Network Connections

Note If you are deleting more than half of all the active OCHNCs, Cisco recommends that you delete them two at a time to allow for proper power compensation. You do not need to delete the active OCHNCs two at a time if you are deleting all the them.

If checked, the CTC Alerts confirmation dialog box will alert you when the OCHNC is deleted. During this time, you cannot perform other CTC functions. If you are deleting many OCHNCs, waiting for confirmation might take a few minutes. Circuits are deleted whether or not this check box is checked.

Note The CTC Alerts dialog box will not automatically open to show a deletion error unless you checked All alerts or Error alerts only in the CTC Alerts dialog box. For more information, see the "DLP-G53 Configure the CTC Alerts Dialog Box for Automatic Popup" task. If the CTC Alerts dialog box is not set to open automatically with a notification, the red triangle inside the CTC Alerts toolbar icon indicates that a notification exists.

Step 9 Complete one of the following:

•If you checked Notify when completed, the CTC Alerts dialog box appears. If you want to save the information, continue with Step 10. If you do not want to save the information, continue with Step 11.

•If you did not check Notify when completed, the Circuits page appears. Continue with Step 12.

Step 10 If you want to save the information in the CTC Alerts dialog box, complete the following steps.

a. Click Save.

b. Click Browse and navigate to the directory where you want to save the file.

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

Step 2 If you want to assign a name to the STS or VC source and destination ports before you create the circuit, complete the "DLP-G104 Assign a Name to a Port" task. If not, continue with the next step.

Note This procedure requires the use of automatic routing. Automatic routing is not available if both the Automatic Circuit Routing NE default and the Network Circuit Automatic Routing Overridable NE default are set to FALSE. For a full description of these defaults see the "Network Element Defaults" appendix in the Cisco ONS 15454 Reference Manual.

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

Step 2 Click the Circuits tab, then click Create.

Step 3 In the Circuit Creation dialog box, complete the following fields:

•Circuit Type—Choose STS for a SONET circuit from the Circuit Type list.

•Number of Circuits—Enter the number of STS or VC circuits that you want to create. The default is 1. If you are creating multiple circuits with the same slot and sequential port numbers, you can use Auto-ranged to create the circuits automatically.

•Auto-ranged—This check box is automatically selected if you enter more than 1 in the Number of Circuits field. Auto-ranging creates identical (same source and destination) sequential circuits automatically. Uncheck the box if you do not want CTC to create sequential circuits automatically.

Step 4 Click Next.

Step 5 Define the circuit attributes:

•Name—Assign a name to the circuit. The name can be alphanumeric and up to 48 characters, (including spaces). Circuit names should be 43 characters or less if you want the ability to create monitor circuits. If you leave the field blank, CTC assigns a default name to the circuit.

Note For creating a circuit using a Gigabit Ethernet port, choose the circuit size as STS-24c for a SONET circuit or VC4-8c for a SDH circuit. The only supported configuration for the Gigabit Ethernet circuit is for the ADM-10G card to be setup in a peer group configuration. For non peer group ADM-10G card setup, the node needs to have release 9.x software or higher.

Note An equivalent SDH circuit size for STS-1 SONET circuit does not exist.

•Bidirectional—Leave checked for this circuit (default).

•Create cross-connects only (TL1-like)—Check this box if you want to create one or more cross-connects to complete a signal path for TL1-generated circuits.

•Diagnostic—Leave unchecked.

•State—Choose the administrative state to apply to all of the cross-connects in a circuit:

–IS—Puts the circuit cross-connects in the In-Service and Normal (IS-NR) service state.

Note The IS administrative state is not supported in Release 8.0. You must create a circuit in IS,AINS service state.

–OOS,DSBLD—Puts the circuit cross-connects in the Out-of-Service and Management, Disabled (OOS-MA,DSBLD) service state. Traffic is not passed on the circuit.

–IS,AINS—Puts the circuit cross-connects in the Out-of-Service and Autonomous, Automatic In-Service (OOS-AU,AINS) service state and suppresses alarms and conditions. When the connections receive a valid signal, the service state automatically changes to IS-NR.

–OOS,MT—Puts the circuit cross-connects in the Out-of-Service and Management, Maintenance (OOS-MA,MT) service state. The maintenance state does not interrupt traffic flow; it suppresses alarms and conditions and allows loopbacks to be performed on the circuit. Use OOS,MT for circuit testing or to suppress circuit alarms temporarily.

•Apply to drop ports—Check this check box if you want to apply the administrative state chosen in the State field to the circuit source and destination ports. CTC applies the administrative state to the ports only if the circuit bandwidth is the same as the port bandwidth or, if the port bandwidth is larger than the circuit, the circuit must be the first circuit to use the port. If not, a Warning dialog box displays the ports where the administrative state could not be applied. If the check box is unchecked, CTC does not apply the administrative state to the source and destination ports.

Note If ports managed into the IS administrative state are not receiving signals, loss of signal alarms are generated and the port service state transitions to OOS-AU,FLT.

•Protected Drops—Check this box if you want the circuit routed on protected drops only, that is, to ONS 15454 cards that are in 1:1, 1:N, 1+1, or optimized 1+1 protection. If you check this box, CTC displays only protected cards and ports as source and destination choices.

Step 8 In the Circuit Source area, choose the source node from the Node drop-down list, then choose the source shelf (multishelf nodes only) from the Shelf drop-down list, the source slot from the Slot drop-down list, and, if needed, the source port from the Port drop-down list. For most cards, the port will be automatically chosen.

Step 9 If you need to create a secondary source, for example, a path protection bridge/selector circuit entry point in a multivendor path protection configuration, click Use Secondary Source and repeat Step 8 to define the secondary source. If you do not need to create a secondary source, continue with Step 10.

Step 10 Click Next.

Step 11 In the Circuit Destination area, choose the destination node from the Node drop-down list (only the source node will be available because the source and destination nodes are the same), then choose the destination shelf (multishelf nodes only) from the Shelf drop-down list, the destination slot from the Slot drop-down list, and, if needed, the destination port from Port drop-down list.

•Using Required Nodes/Spans—Check this check box if you want to specify nodes and spans to include or exclude in the CTC-generated circuit route.

Including nodes and spans for a circuit ensures that those nodes and spans are in the working path of the circuit (but not the protect path). Excluding nodes and spans ensures that the nodes and spans are not in the working or protect path of the circuit.

•Review Route Before Creation—Check this check box if you want to review and edit the circuit route before the circuit is created.

Step 14 To set the circuit path protection, complete one of the following:

•To route the circuit on a protected path, leave Fully Protected Path checked and continue with Step 15. CTC creates a fully protected circuit route based on the path diversity option you choose. Fully protected paths might or might not have path protection path segments (with primary and alternate paths), and the path diversity options apply only to path protection path segments, if any exist.

Step 15 If you selected Fully Protected Path in Step 14 and the circuit will be routed on a path protection configuration, choose one of the following:

•Nodal Diversity Required—Ensures that the primary and alternate paths within path protection portions of the complete circuit path are nodally diverse.

•Nodal Diversity Desired—Specifies that node diversity is preferred, but if node diversity is not possible, CTC creates fiber-diverse paths for the path protection portion of the complete circuit path.

•Link Diversity Only—Specifies that only fiber-diverse primary and alternate paths for path protection portions of the complete circuit path are needed. The paths might be node-diverse, but CTC does not check for node diversity.

Step 16 If you checked Using Required Nodes/Spans in Step 13, complete the following substeps. Otherwise, continue with Step 17.

a. In the Circuit Constraints for Automatic Routing area, click a node or span on the circuit map.

b. Click Include to include the node or span in the circuit. Click Exclude to exclude the node or span from the circuit. The order in which you choose included nodes and spans is the order in which the circuit is routed. Click spans twice to change the circuit direction.

c. Repeat Step b for each node or span you wish to include or exclude.

d. Review the circuit route. To change the circuit routing order, choose a node in the Required Nodes/Lines or Excluded Nodes Links lists and click the Up or Down buttons to change the circuit routing order. Click Remove to remove a node or span.

Step 17 Click Next.

Step 18 If you selected Review Route Before Creation in Step 13, complete the following substeps. If not, continue with Step 19.

a. Click Next.

b. Review the circuit route. To add or delete a circuit span, choose a node on the circuit route. Blue arrows show the circuit route. Green arrows indicate spans that you can add. Click a span arrowhead, then click Include to include the span or Remove to remove the span.

Step 19 Click Finish. One of the following results occurs if you entered more than one circuit in the Number of Circuits field on the Circuit Creation dialog box.

•If you chose Auto-ranged, CTC automatically creates the number of circuits entered in the Number of Circuits field. If auto-ranging cannot complete all the circuits, for example, because sequential ports are unavailable at the source or destination, a dialog box appears. Set the new source or destination for the remaining circuits, then click Finish to continue auto-ranging. After completing the circuits, the Circuits window appears.

•If you did not choose Auto-ranged, the Circuit Creation dialog box appears so you can create the remaining circuits. Repeat Steps 3 through 18 for each additional circuit. After completing the circuits, the Circuits window appears.

Step 20 In the Circuits window, verify that the new circuits appear in the circuits list.

Stop. You have completed this procedure.

DLP-G464 Create a Manually Routed STS or VC Circuit

Purpose

This procedure creates an STS or VC circuit and allows you to provision the circuit route for the ADM-10G card.

•Number of Circuits—Enter the number of STS or VC circuits that you want to create. The default is 1.

•Auto-ranged—(Automatically routed circuits only) If you entered more than 1 in the Number of Circuits field on the Circuit Creation dialog box, uncheck this box. (The box is unavailable if only one circuit is entered in the Number of Circuits field.)

Step 4 Click Next.

Step 5 Define the circuit attributes:

•Name—Assign a name to the circuit. The name can be alphanumeric and up to 48 characters (including spaces). Circuit names should be 43 characters or less if you want the ability to create monitor circuits. If you leave the field blank, CTC assigns a default name to the circuit.

Note For creating a circuit using a Gigabit Ethernet port, choose the circuit size as STS-24c for a SONET circuit or VC4-8c for a SDH circuit. The only supported configuration for the Gigabit Ethernet circuit is for the ADM-10G card to be setup in a peer group configuration. For non peer group ADM-10G card setup, the node needs to have release 9.x software or higher.

Note An equivalent SDH circuit size for STS-1 SONET circuit does not exist.

•Bidirectional—Leave checked for this circuit (default).

•Create cross-connects only (TL1-like)—Check this box if you want to create one or more cross-connects to complete a signal path for TL1-generated circuits.

•State—Choose the administrative state to apply to all of the cross-connects in a circuit:

–IS—Puts the circuit cross-connects in the IS-NR service state.

Note The IS administrative state is not supported in Release 8.0. You must create a circuit in IS,AINS service state.

–OOS,DSBLD—Puts the circuit cross-connects in the OOS-MA,DSBLD service state. Traffic is not passed on the circuit.

–IS,AINS—Puts the circuit cross-connects in the OOS-AU,AINS service state and suppresses alarms and conditions. When the connections receive a valid signal, the service state automatically changes to IS-NR.

–OOS,MT—Puts the circuit cross-connects in the OOS-MA,MT service state. The maintenance state does not interrupt traffic flow; it suppresses alarms and conditions and allows loopbacks to be performed on the circuit. Use OOS,MT for circuit testing or to suppress circuit alarms temporarily.

•Apply to drop ports—Check this check box if you want to apply the administrative state chosen in the State field to the circuit source and destination ports. CTC applies the administrative state to the ports only if the circuit bandwidth is the same as the port bandwidth or, if the port bandwidth is larger than the circuit, the circuit must be the first circuit to use the port. If not, a Warning dialog box displays the ports where the administrative state could not be applied. If the check box is unchecked, CTC does not apply the administrative state to the source and destination ports.

Note If ports managed into the IS administrative state are not receiving signals, loss of signal alarms are generated and the port service state transitions to OOS-AU,FLT.

•Protected Drops—Check this box if you want the circuit routed on protected drops only, that is, to ONS 15454 cards that are in 1:1, 1:N, 1+1, or optimized 1+1 protection. If you check this box, CTC shows only protected cards and ports as source and destination choices.

Step 8 In the Circuit Source area, choose the source node from the Node drop-down list, then choose the source shelf (multishelf nodes only) from the Shelf drop-down list, the source slot from the Slot drop-down list, and, if needed, the source port from the Port drop-down list. For most cards, the port will be automatically chosen.

Step 9 If you need to create a secondary source, for example, a path protection bridge/selector circuit entry point in a multivendor path protection configuration, click Use Secondary Source and repeat Step 8 to define the secondary source. If you do not need to create a secondary source, continue with Step 10.

Step 10 Click Next.

Step 11 In the Circuit Destination area, choose the destination node from the Node drop-down list (only the source node will be available because the source and destination nodes are the same), then choose the destination shelf (multishelf nodes only) from the Shelf drop-down list, the destination slot from the Slot drop-down list, and, if needed, the destination port from Port drop-down list.

Step 15 If you selected Fully Protected Path in Step 14 and the circuit will be routed on a path protection configuration, choose a Node-Diverse Path option:

•Nodal Diversity Required—Ensures that the primary and alternate paths within the path protection portions of the complete circuit path are nodally diverse.

•Nodal Diversity Desired— Specifies that node diversity is preferred, but if node diversity is not possible, CTC creates fiber-diverse paths for the path protection portion of the complete circuit path.

•Link Diversity Only—Specifies that only fiber-diverse primary and alternate paths for path protection portions of the complete circuit path are needed. The paths might be node-diverse, but CTC does not check for node diversity.

Step 16 Click Next.

Step 17 In the Route Review/Edit area, node icons appear for you to route the circuit manually. Click the source node icon if it is not already selected.

Step 18 Starting with a span on the source node, click the arrow of the span you want the circuit to travel. The arrow turns yellow. In the Selected Span area, the From and To fields provide span information. The source STS or VC appears.

Step 19 If you want to change the source STS or VC, adjust the Source STS or VC field; otherwise, continue with Step 20.

Step 20 Click Add Span. The span is added to the Included Spans list and the span arrow turns blue.

Step 21 If the Fully Protect Path check box is checked in the Circuit Routing Preferences panel, you must add two spans for all path protection or unprotected portions of the circuit route from the source to the destination.

Step 22 Repeat Steps 18 through 21 until the circuit is provisioned from the source to the destination node through all intermediary nodes.

Step 23 Click Finish. CTC compares your manually provisioned circuit route with the specified path diversity option you chose in Step 15. If the path does not meet the specified path diversity requirement, CTC displays an error message and allows you to change the circuit path.

Step 24 If you entered more than 1 in the Number of Circuits field on the Circuit Creation dialog box, the Circuit Creation dialog box appears so you can create the remaining circuits. Repeat Steps 3 through 23 for each additional circuit.

Step 25 When all the circuits are created, the main Circuits window appears. Verify that the circuits you created are correct.

Stop. You have completed this procedure.

DLP-G465 Provision Path Protection Selectors

Purpose

This task provisions path protection selectors during circuit creation or during a topology upgrade conversion.

The Circuit Attributes page of the Circuit Creation wizard must be open.

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher

Note Provisioning path signal degrade (SD-P) or path signal fail (SF-P) thresholds in the Circuit Attributes page of the Circuit Creation wizard sets the values only for path protection-protected spans. The circuit source and destination use the node default values of 10E-4 for SD-P and 10E-6 for SF-P for unprotected circuits and for the source and drop of path protection circuits.

Step 1 In the path protection area of the Circuit Attributes page of the Circuit Creation wizard, set the path protection selectors:

•Provision working go and return on primary path—Check this box to route the working path on one fiber pair and the protect path on a separate fiber pair. This feature only applies to bidirectional path protection circuits.

•Revertive—Check this box if you want traffic to revert to the working path when the conditions that diverted it to the protect path are repaired. If you do not choose Revertive, traffic remains on the protect path after the switch.

•Reversion time—If Revertive is checked, click the Reversion time field and choose a reversion time from the 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 path. Traffic can revert when conditions causing the switch are cleared.

•Change drop port admin state—Check this box if you want to change the administrative state for the circuit source and destination ports. After checking the box, choose one of the following administrative states:

–IS (ANSI) or Unlocked (ETSI)—Puts the ports in service.

–IS,AINS (ANSI) or UnlockedAutomaticInService (ETSI)—Puts the ports in automatic in service.

–OOS,DSBLD (ANSI) or Locked,disabled (ETSI)—Removes the ports from service and disables them.

–OOS,MT (ANSI) or Locked,maintenance (ETSI)—Removes the ports from service for maintenance.

•Notify when completed—If checked, the CTC Alerts confirmation dialog box indicates when the circuit is deleted. During this time, you cannot perform other CTC functions. If you are deleting many circuits, waiting for confirmation might take a few minutes. Circuits are deleted whether or not this check box is checked.

Note The CTC Alerts dialog box will not automatically open to show a deletion error unless you checked All alerts or Error alerts only in the CTC Alerts dialog box. For more information, see the "DLP-G53 Configure the CTC Alerts Dialog Box for Automatic Popup" task. If the CTC Alerts dialog box is not set to open automatically with a notification, the red triangle inside the CTC Alerts toolbar icon indicates that a notification exists.

Step 8 Complete one of the following:

•If you checked Notify when completed, the CTC Alerts dialog box appears. If you want to save the information, continue with Step 9. If you do not want to save the information, continue with Step 10.

•If you did not check Notify when completed, the Circuits page appears. Continue with Step 11.

Step 9 If you want to save the information in the CTC Alerts dialog box, complete the following steps. If you do not want to save it, continue with Step 11.

a. Click Save.

b. Click Browse and navigate to the directory where you want to save the file.

This procedure upgrades OCHNCs created in earlier software releases to OCHCCs. It also upgrades an OCHNC circuit to an OCH trail circuit (without the OCHCC circuit) in case the PPCs or internal patchcords connect to an ADM_10G or GE_XP/10GE_XP (only in L2 over DWDM mode) cards.

Note During this procedure, the OCHNC is replaced with two circuit types, the OCHCC, which establishes a connection between the client card client ports, and the OCH trail, which establishes a connection between the client card trunk ports. The OCH trail is given the same name as the OCHNC. The OCHCC is given a system-generated name in the format: circuit-type_NE-name::unique sequence number. To edit the OCHCC circuit name, complete the "DLP-G424 Edit an OCHCC Circuit Name" task. To edit the OCH trail circuit name, complete the "DLP-G425 Edit an OCH Trail Circuit Name" task.

Note Multiple OCHCCs might use the same OCH trail. The OCH Wlen (wavelength) parameter on the Circuits page can be used to determine the OCHCC and OCH trail associations.

•G184 Create a Provisionable Patchcord and DCN Extension—Complete this procedure if you know that PPCs were not created between the OCHNC node and the client node. If you recently upgraded from a previous release, you must create PPCs between the source client and OCHNC node and between the destination client and OCHNC node.

a. Click each failure reason to view the failure details. A common cause of initialization failures is the absence or incorrect completion of PPCs or internal patchcords between the client nodes and the optical channel (OCH) nodes.

b. Repeat Steps 3 through 8, verifying that the OCHNC ports and provisionable patchcord (PPC) path match on both sides. If the upgrade "Failed" status appears again, click Save to save the results to a local or network computer. (The file can be opened with any text editor.) Then, contact your next level of support.

Figure 7-4 Upgrade OCHNC Initialization—Completed

Figure 7-5 Upgrade OCHNC Initialization—Failed

Step 9 Click each result to review the details. If you want to save the results, click Save and save the results to a file on a local or network computer. Click Continue.

Step 3 Use one of the following methods to verify that PPCs exist from the client TXP, MXP, ADM-10G, GE_XP, 10GE_XP, or ITU-T line card node, slot, and port to the DWDM OCH node, slot, port, and wavelength:

•Review the Patchcord Terminations table. PPCs should exist from the client TXP, MXP, ADM-10G, GE_XP, 10GE_XP, or ITU-T line card node to the OCH node, slot, and port recorded in the referring procedure.

•Review the network graphic (see Figure 7-7). PPCs are represented by a small hand holding a lambda symbol. Clicking the PPC line on the graphic displays the PPC source and destination nodes, slots, and ports in the CTC information area. This information should match the node, slot, and port recorded in the referring procedure.

NTP-G183 Diagnose and Fix OCHNC and OCH Trail Circuits

Purpose

This procedure checks nodes that are traversed by an OCHNC or OCH trail circuit to verify that all conditions required for bringing the circuit in service are in place. If not, the procedure identifies the invalid condition and provides links to the location in CTC where it can be fixed.

•No problems are found—A "node: No issues found" message appears, where node is the node name or IP address of an ONS 15454 containing the OCHNC or OCH trail source, destination, or pass-through connection. If this message appears for all nodes, continue with Step 9.

•Problems are found—Error messages appear with a hyperlink labeled Fix or Check. If error messages appear, complete the fixes using the tasks and procedures listed in Table 7-4.

Note Only one error per node is displayed. If multiple errors exist, you must fix the first error, then rerun the diagnostic to display the next error(s).

The state of a port traversed by the circuit is not valid, for example, the port is in service. Click Fix to display the card view Provisioning tab, where you can change the port administrative state using the appropriate task for changing the optical line settings in Chapter 11 "Change DWDM Card Settings."

APC could not be regulated for the port. Click Fix to display the network view Maintenance > APC tab. Double-click the domain to expand the view. Right-click the node/side and choose the end you want to view. APC information is displayed on the right side. Read any message that might explain the failure, or restart APC by completing the "DLP-G158 Enable Automatic Power Control" task.

APC regulation is running

Indicates that APC regulation is running and must be allowed to finish. Click Check to display the node view Maintenance > DWDM > APC tab where you can monitor the APC regulation.

•To search for circuits that originate, terminate, or pass through a specific node, from the View menu choose Go to Other Node, then choose the node you want to search and click OK.

•To search for circuits that originate, terminate, or pass through a specific card, double-click the card on the shelf graphic in node view (single-shelf mode) or shelf view (multishelf mode) to open the card in card view.

Step 2 Click the Circuits tab.

Step 3 If you are in node or card view, choose the scope for the search, Node or Network (All), in the Scope drop-down list located at the bottom right side of the screen. Choose Node to see all of the circuits on that node, or choose Network (All) to see all circuits in the network.

Step 4 Click Search if you need to search through the list of circuits.

Step 5 In the Circuit Name Search dialog box, complete the following:

•Find What—Enter the text of the circuit name you want to find. This field is not case-sensitive.

•Match whole word only—Check this check box to instruct CTC to select circuits only if the entire word matches the text in the Find What field.

•Match case—Check this check box to instruct CTC to select circuits only when the capitalization matches the capitalization entered in the Find What field.

•Direction—Choose the direction for the search. Searches are conducted up or down from the currently selected circuit.

Step 6 Click Find Next. If a match is found the circuit will be highlighted in the Circuits page. To continue the search, click Find Next again to find the next circuit.

Step 7 Repeat Steps 5 and 6 until you are finished, then click Cancel.

•To view circuits for an entire network, from the View menu choose Go to Network View.

•To view circuits that originate, terminate, or pass through a specific node, from the View menu choose Go to Other Node, then choose the node you want to search and click OK.

•To view circuits that originate, terminate, or pass through a specific card, in node view (single-shelf mode) or shelf view (multishelf mode), double-click the card containing the circuits you want to view.

Note In node or card view, you can change the scope of the circuits that appear by choosing Card (in card view), Node, or Network from the Scope drop-down list in the bottom right corner of the Circuits page.

Step 2 Click the Circuits tab. The Circuits tab shows the following information:

Note The following order is the default column sequence, the order might be different on your screen, depending on your individual CTC setup.

•Circuit Name—Name of the circuit. The circuit name can be manually assigned or automatically generated.

Note The following circuit types under the circuit size column are not applicable to DWDM nodes: STS, VT, VCAT, VC12, VC11, VC3, and VC4.

•OCHNC Wlen—The wavelength provisioned for the OCHNC, OCHCC, or OCH trail. See Table 7-2 for a list of channels and wavelengths.

•Dir—The circuit direction, either two-way or one-way.

•Protection—The type of circuit protection. See Table 7-5 for a list of protection types.

•Status—The circuit status. See Table 7-6 for a list of circuit statuses.

•Source—The circuit source in the format: node/slot/port "port name". The port name will appear in quotes only if a name was assigned to it. (To assign names to ports, see the "DLP-G104 Assign a Name to a Port" task.)

•Destination—The circuit destination in the format: node/slot/port "port name". The port name will appear in quotes only if a name was assigned to it. (To assign names to ports, see the "DLP-G104 Assign a Name to a Port" task.)

•# of VLANS—The number of VLANs used by an Ethernet circuit. VLANs are not applicable to DWDM nodes.

•# of Spans—The number of internode links that constitute the circuit. Right-clicking the column title shows a shortcut menu from which you can choose Span Details to show or hide circuit span detail.

•State—The circuit service state, which is an aggregate of the service states of its cross-connects. For ANSI shelves, the service state is IS, OOS, or OOS-PARTIAL. For ETSI shelves, the service state is Unlocked, Locked, or Locked-partial. For more information about ANSI and ETSI service states, see the "Administrative and Service States" appendix in the Cisco ONS 15454 DWDM Reference Manual.

–IS/Unlocked—All cross-connects are in service and operational.

–OOS/Locked—For ANSI, all cross-connects are OOS-MA,MT and/or OOS-MA,DSBLD. For ETSI, all cross-connects are Locked-enabled,maintenance and/or Locked-enabled,disabled.

–OOS-PARTIAL/Locked-partial—At least one cross-connect is IS-NR (ANSI) or Unlocked-enabled (ETSI) and others are out-of-service.

Note Right-clicking a column title (Circuit name, Type, etc.) opens a shortcut menu that allows you to show or hide circuit details.

Table 7-5 Circuit Protection Types

Protection Type

Description

Y-cable

(OCHNC and OCH-Trail circuit types only) The circuit is protected by a transponder or muxponder card Y-cable protection group.

Splitter

The circuit is protected by the protect transponder splitter protection.

Unprot

A circuit with a source and destination on different nodes is not protected.

N/A

A circuit with connections on the same node is not protected.

Unknown

A circuit has a source and destination on different nodes and communication is down between the nodes. This protection type appears if not all circuit components are known.

Table 7-6 Cisco ONS 15454 Circuit Status

Status

Definition/Activity

CREATING

CTC is creating a circuit.

DISCOVERED

CTC created a circuit. All components are in place and a complete path exists from the circuit source to the circuit destination.

DELETING

CTC is deleting a circuit.

PARTIAL

A CTC-created circuit is missing a cross-connect or network span, a complete path from source to destination(s) does not exist, or an alarm interface panel (AIP) change occurred on one of the circuit nodes and the circuit is in need of repair. (AIPs store the node MAC address.)

In CTC, circuits are represented using cross-connects and network spans. If a network span is missing from a circuit, the circuit status is PARTIAL. However, a PARTIAL status does not necessarily mean that a circuit traffic failure has occurred, because traffic might flow on a protect path.

Network spans are in one of two states: up or down. On CTC circuit and network maps, up spans are shown as green lines, and down spans are shown as gray lines. If a failure occurs on a network span during a CTC session, the span remains on the network map but its color changes to gray to indicate the span is down. If you restart your CTC session while the failure is active, the new CTC session cannot discover the span and its span line will not appear on the network map.

Subsequently, circuits routed on a network span that goes down will appear as DISCOVERED during the current CTC session, but they will appear as PARTIAL to users who log in after the span failure.

This status does not appear for OCHNC circuit types.

DISCOVERED_TL1

A TL1-created circuit or a TL1-like CTC-created circuit is complete. A complete path from source to destination(s) exists.

This status does not appear for OCHNC circuit types.

PARTIAL_TL1

A TL1-created circuit or a TL1-like CTC-created circuit is missing a cross-connect, and a complete path from source to destination(s) does not exist.

This status does not appear for OCHNC circuit types.

Step 3 Return to your originating procedure (NTP).

DLP-G102 Filter the Display of Optical Channel Circuits

Purpose

This task filters the display of OCHNCs, OCHCCs, OCH trails and SONET or SDH circuits in the Circuits page. You can filter the circuits in network, node, or card view based on circuit or OCHNC name, size, type, direction, and other attributes.

•To filter circuits that originate, terminate, or pass through a specific node, from the View menu choose Go to Other Node, then choose the node you want to search and click OK.

•To filter circuits that originate, terminate, or pass through a specific card, double-click the card on the shelf graphic in node view (single-shelf mode) or shelf view (multishelf mode) to open the card in card view.

Step 2 Click the Circuits tab.

Step 3 Set the attributes for filtering the circuit display:

a. Click the Filter button.

b. In the General tab of the Circuit Filter dialog box, set the following filter attributes, as necessary:

•Name—Enter a complete or partial circuit name to filter circuits based on the circuit name.

•Direction—Choose one: Any (direction not used to filter circuits), 1-way (display only one-way circuits), or 2-way (display only two-way circuits).

•Status—Choose one: Any (status not used to filter circuits) or Discovered (display only discovered circuits). Other statuses do not apply to OCHNCs.

•State—Choose one: OOS (ANSI) or Locked (ETSI) to display only out-of-service circuits, IS (ANSI)or Unlocked (ETSI) todisplay only in-service circuits (OCHNCs have IS/Unlocked states only), or OOS-PARTIAL (ANSI) or Locked-partial (ETSI) to display only circuits with cross-connects in mixed service states.

•Protection—Enter the circuit protection type to filter circuits based on their protection.

•Shelf—(multishelf nodes only) Enter the shelf name to filter circuits based on that shelf.

•Slot—Enter a slot number to filter circuits based on the source or destination slot.

•Port—Enter a port number to filter circuits based on the source or destination port.

•Type—Choose one: Any (type not used to filter circuits), OCHNC (displays only OCHNCs), OCHCC (displays only OCHCCs), or OCH-Trail (displays only OCH trail circuits).

The check boxes shown depend on the Type field selection. If you chose Any, all sizes are available. If you chose OCHNC as the circuit type, only Multi-rate, Equipment non specific, 2.5 Gbps FEC, 2.5 Gbps No FEC, 10 Gbps FEC, and 10 Gbps No FEC appear. If you choose OCHCC, only OCHCC is available. If you choose OCH Trail, only Equipment non specific is available.

Step 4 To set the filter for the ring, node, link, and source and drop types, click the Advanced tab and complete the following substeps. If you do not want to make advanced filter selections, continue with Step 5.

a. If you made selections on the General tab, click Yes in the confirmation box to apply the settings.

b. In the Advanced tab of the Circuit Filter dialog box, set the following filter attributes as necessary:

•Ring—Choose the ring from the drop-down list.

•Node—Click the check boxes by each node in the network to filter circuits based on node.

•Link—Choose a link in the network.

•Source/Drop—Choose one of the following to filter circuits based on whether they have single or multiple sources and drops: One Source and One Drop Only or Multiple Sources or Multiple Drops.

Step 6 To turn filtering off, click the Filter icon in the lower right corner of the Circuits page. Click the icon again to turn filtering on, and click the Filter button to change the filter attributes.

Step 7 Return to your originating procedure (NTP).

DLP-G103 View Optical Channel Circuits on a Span

Purpose

This task allows you to view OCHNCs, OCHCCs, and OCH trails on an ONS 15454 span.

Step 1 In node view (single-shelf mode) or multishelf view (multishelf mode), from the View menu choose Go to Network View. If you are already in network view, continue with Step 2.

Step 2 Right-click the green line between the nodes containing the circuits that you want to view and choose Circuits to view OCHNCs, OCHCCs, or unprotected circuits on the span.

Step 3 In the Circuits on Span dialog box, view information about the circuits that traverse the span. The information that appears depends on the circuit type. For OCHNCs, the following information appears:

•Type—The type of circuit: OCHNC, OCHCC, or OCH-Trail.

•Size—The circuit size.

•OCHNC Wavelength—The wavelength provisioned for the OCHNC.

•DIR—2-way or 1-way.

•Circuit—The OCHNC circuit name.

•OCHNC Dir—The direction provisioned for the OCHNC, either Side B-to-Side A or Side A-to-Side B.

Step 4 Return to your originating procedure (NTP).

NTP-G184 Create a Provisionable Patchcord and DCN Extension

Purpose

This procedure creates a PPC, also called a virtual link. Three types can be created. The OCH Trunk-to-OCH Trunk or OCH Trunk-to-OCH Filter PPC is required by OCHCC circuits when the TXP, MXP, ADM-10G, GE_XP, 10GE_XP, or ITU-T line cards are not installed in the same node (in either single or multishelf mode) as the OCH (DWDM) cards. PPCs create a virtual connection between the OCH and the client nodes. (PPCs are not required for OCHNCs.)

The OTS-to-OTS PPC is required when nodes do not have OSC connectivity. The OTS-to-OTS PPC creates a DCN extension link between the nodes. DCN extensions are used to overcome OSC constraints on span length or when a GCC/DCC or LAN connection already exists between two nodes. For more information about provisionable patchcords, refer to the "Circuits and Virtual Patchcords" chapter in the Cisco ONS 15454 DWDM Reference Manual.

Note If an OTS-to-OTS PPC is created between nodes, it will no longer function if the node Security Mode mode is enabled (see "G264 Enable Node Security Mode" section). The reason for this is that if the Secure mode is enabled, it is no longer possible for the DCN extension feature to use the LAN interface to extend the internal network (due to the network isolation in this configuration mode). The result is that the topology discovery on the OTS-to-OTS PPC no longer operates.

Note An external LAN within a DCN connection must have a minimum bandwidth of 192 kb/s and a maximum latency of 100 ms.

Note This task requires data communications channel (DCC) or GCC connectivity between the OCH node and the subtended TXP, MXP, or ITU-T line card client shelves.

Note An optical port requires two patchcords when the remote end is Y-cable protected or is an add/drop multiplexer or multiplexer/demultiplexer port.

Note Networks using the DCN extension must have the safety feature enabled at all times. A link that does not use OSC must be terminated by two Booster amplifiers. Only two line sites containing pre-amplifiers are allowed between these boosters. The missing OSC amplifiers cannot automatically restart in case of fiber repair. One of the amplifiers must be manually restarted to activate the link.

Step 1 Complete the following tasks, as needed, to verify the cabling between the TXP/MXP/line cards in the client node and the OCH cards in the DWDM node:

PPCs can be created in either node or network view. However, if you create the PPC in node view, the PPC origination ports will be restricted to the cards installed on the node. Therefore, choose node view only if you know that the PPC origination port resides on a card installed in the node.

Step 4 Choose one of the following PPC link types. See Table 7-7 for a list of ports that serve as PPC end points for each option.

•OCH-Trunk to OCH-Trunk—Creates a PPC between two optical channel trunk ports on TXP, MXP, GE_XP, 10GE_XP, ADM-10G, or ITU-T line cards.

•OTS to OTS—Creates a PPC between two OTS (optical transport section) ports. This option establishes DCN connectivity between nodes that do not have OSCM or OSC-CSM cards installed and therefore do not have OSC connectivity. OTS ports are selected by CTC after you choose the origination and termination sides.

•OCH-Trunk to OCH-FILTER—Creates a PPC between an optical channel trunk port on a TXP, MXP, GE_XP, 10GE_XP, ADM-10G, or ITU-T line card and an optical channel filter port on a MUX, DMX, or WSS card.

Displays the ID automatically assigned to the PPC. You can enter a different ID, if needed. Patchcord IDs (0 through 32767) are used for your internal tracking and to help identify PPCs. All IDs must be unique within each node.

Yes

No

No

Tx ID

Displays the transmit ID automatically assigned to the PPC. You can enter a different Rx ID, if needed, 0 through 32767.

No

Yes

Yes

Rx ID

Displays the receive ID automatically assigned to the PPC. You can enter a different Tx ID, if needed, 0 through 32767.

Step 8 Click Next. If you chose OCH-Trunk to OCH-Trunk or OCH-Trunk to OCH Filter with the Protected option in Step 4, continue with Step 9. If not, continue with Step 11.

Step 9 In the PPC Protect Termination page, provision the ID field(s). If you chose OCH-Trunk to OCH-Trunk in Step 4, one ID field is available. If you chose OCH-Trunk to OCH-Filter in Step 4, two ID fields are available, Rx ID and Tx ID.

Step 10 Click Next.

Step 11 In the PPC Termination page, complete the fields shown in Table 7-9. The OCH-Trunk to OCH-Trunk, OCH-Trunk to OCH-Filter, and OTS to OTS columns indicate whether the field is provisionable.

Displays the ID automatically assigned to the PPC. You can enter a different ID, if needed. Patchcord IDs (0 through 32767) are used for your internal tracking and to help identify PPCs. All IDs must be unique within each node.

Yes

No

Yes

Rx ID

Displays the receive ID automatically assigned to the PPC. You can enter a different Tx ID, if needed, 0 through 32767.

No

Yes

No

Tx ID

Displays the transmit ID automatically assigned to the PPC. You can enter a different Rx ID, if needed, 0 through 32767.

Step 12 Click Next. If you chose OCH-Trunk to OCH-Trunk or OCH-Trunk to OCH Filter with the Protected option in Step 4, continue with Step 13. If not, continue with Step 14.

Step 13 In the PPC Protect Termination page, provision the ID fields. If you chose OCH-Trunk to OCH-Trunk in Step 4, one ID field is available. If you chose OCH-Trunk to OCH-Filter in Step 4, two ID fields are available, Rx ID and Tx ID.

Step 14 In the PPCs ID page, review the PPC information. If the PPC information is correct, click Finish. If you need to make corrections, click Back and return to the wizard page where you want to change the information.

Stop. You have completed this procedure.

NTP-G181 Manage GE_XP and 10GE_XP Card SVLAN Databases

Purpose

This procedure creates a service provider VLAN (SVLAN) database for nodes that have GE_XP and 10GE_XP cards provisioned in L2-over-DWDM mode. The procedure stores newly created SVLANs at network nodes. It also loads and merges SVLAN databases into the VLAN DB tab where they can be edited. Finally, the procedure associates SVLANs to OCH trail circuits.

Step 3 In the box next to the Add row(s) button, enter the number of SVLANs you want to create.

Step 4 Click Add row(s).

Step 5 For each SVLAN row, enter the following:

•VLAN ID—Enter the SVLAN ID. The range is 1 to 4093 with the following restrictions:

–0 indicates an untagged frame.

–The database can contain a maximum of 4092 unprotected SVLANS. However, it can contain a maximum of 256 protected SVLANs.

•VLAN Name—Enter the SVLAN name. It can be up to 32 alphanumeric characters.

•Protected—If this is a protected SVLAN, check the Protected checkbox.

Step 6 Click Store.

Step 7 In the Store Profile(s) dialog box, choose one of the following:

•To Node(s)—Stores the SVLAN database at one or more network nodes. Choose the network nodes where you want to store the SVLAN database. To choose more than one node, press the Shift key, or click Select All.

•To File—Stores the SVLAN database in a file. Enter a file name, then click Browse to navigate to a local or network drive where you want to store the file.

Step 8 Click OK.

Step 9 Return to your originating procedure (NTP).

DLP-G422 Load or Merge an SVLAN Database

Purpose

This task loads or merges an SVLAN database stored at a node or local file into the VLAN DB tab on the CTC network view.

•Load—Loads an SVLAN database from a network node or local file and replaces any SVLANs that are in the network view VLAN DB table.

•Merge—Loads a SVLAN database from a network node or local file, but does not replace any SVLANs that are in the network view VLAN DB table. The loaded database is merged with any SVLANs that might be in the table.

Step 4 In the Load Profile(s) dialog box, choose one of the following:

•From Node—Loads the SVLAN database from a network node. Choose the network node where you want to load the SVLAN database.

•From File—Loads the SVLAN database from a file. Enter the file path in the blank field, or click Browse to navigate to a local or network directory containing the database file.

Step 5 Click OK.

Step 6 Return to your originating procedure (NTP).

DLP-G423 View OCH Trails that Support an SVLAN

Purpose

This task shows which OCH trail circuits support an SVLAN stored on a GE_XP or 10GE_XP card. The task verifies that an SVLAN is provisioned on both ends of an OCH trail circuit.

Step 7 On the right side, view the OCH trail circuits that support the SVLAN selected in Step 5. The OCH trails appear as lines between the node selected in Step 4 and other nodes connected by the OCH trails. The color of the OCH trails indicate whether both ends, one end, or neither end support the SVLAN, as follows:

•Green—Both ends of the OCH trail support the selected SVLAN.

•Orange—One end of the OCH trail supports the selected SVLAN. If an orange OCH trail circuit is shown, double-click the source or destination OCH trail point on the graphic to display the source or destination GE_XP or 10GE_XP card. You can change or assign the VLAN ID.

Note The DCCs, GCCs, and OSCs should not be provisioned between SONET (ANSI) and SDH (ETSI) nodes using CTC or TL1 because they cannot operate between SONET and SDH nodes. These communication channels should be provisioned on similar nodes, such as SONET-to-SONET or SDH-to-SDH.

DLP-G76 Provision DCC/GCC Terminations

Purpose

This task creates the DWDM DCC/GCC terminations required for network setup when using the TXP and MXP cards. Perform this task before you create OCHCC or OCHNC circuits for these cards. In this task, you can also set up the node so that it has direct IP access to a far-end non-ONS node over the DCC/GCC network.

Note The DCCs, GCCs, and OSCs should not be provisioned between SONET (ANSI) and SDH (ETSI) nodes using CTC or TL1 because they cannot operate between SONET and SDH nodes. These communication channels should be provisioned on similar nodes, such as SONET-to-SONET or SDH-to-SDH.

Step 1 If you are provisioning DCC termination on the TXP and MXP card, set the termination mode of the card as appropriate. For details, see the section "Termination Modes" in the chapter "Provision Transponder and Muxponder Cards" of Cisco ONS 15454 DWDM Reference Manual.

Step 2 If you are provisioning DCC termination, ensure that the OTN is disabled on OTN interfaces (usually trunk ports). If OTN is enabled, provision GCC instead of DCC termination. For more information about managing OTN setting on the card, see the procedures for changing card OTN settings in Chapter 5 "Provision Transponder and Muxponder Cards".

•Set to IS or Set to Unlocked —Puts the DCC/GCC termination port in service.

•Set OOS,DSLBD to IS,AINS (for ANSI) or Set Locked,disabled to Unlocked,automaticInService (for ETSI)—Changes a port that is currently out of service or locked to automatic in service.

•Set OOS,DSLBD to OOS,MT (for ANSI) or Set Locked,disabled to Locked,maintenance (for ETSI)—Changes a port that is currently out of service or locked to out of service for maintenance.

Note For GCC termination, the GCC Rate is set as 192 kbps by default. This rate currently cannot be changed.

Step 8 Verify that the Disable OSPF on Link is unchecked. If this check box is checked, node discovery through the link termination will not happen.If the DCC/GCC termination includes a non-ONS node, check the Far End is Foreign check box. This automatically sets the far-end node IP address to 0.0.0.0, which means that any address can be specified by the far end. To change the default to a specific IP address, see the "DLP-G184 Change a DCC/GCC Termination" task.

Step 9 In the Layer 3 area, perform one of the following options:

•Check the IP box only if the DCC/GCC is between the ONS 15454 and another ONS node and only ONS nodes reside on the network. The DCC/GCC will use Point-to-Point Protocol (PPP).

•Check both the IP box and the OSI box if the DCC/GCC is between the ONS 15454 and another ONS node, and third-party NEs that use the OSI protocol stack are on the same network. The DCC/GCC will use PPP.

Step 10 If you checked OSI, complete the following substeps. If you checked IP only, continue with Step 11.

a. Click Next.

b. Provision the following fields:

–Router—Choose the OSI router.

–ESH—Sets the End System Hello (ESH) propagation frequency. End system (ES) NEs transmit ESHs to inform other ESs and intermediate systems (ISs) about the Network Service Access Points (NSAPs) that the ES NEs serve. The default is 10 seconds. The range is 10 to 1000 seconds.

–ISH—Sets the Intermediate System Hello (ISH) protocol data unit (PDU) propagation frequency. IS NEs send ISHs to other ESs and ISs to inform them about the IS NEs that the IS NEs serve. The default is 10 seconds. The range is 10 to 1000 seconds.

–IIH—Sets the Intermediate System to Intermediate System Hello (IIH) 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 metric cost for LAN subnets is 60. The cost normally should not be changed.

Step 11 Click Finish. The following alarms appear until all the network DCC/GCC terminations are created and the ports are in service:

•GCC-EOC for GCC termination

•EOC for SDCC termination

•EOC-L for LDCC termination

Step 12 Return to your originating procedure (NTP).

DLP-G97 Provision a Proxy Tunnel

Purpose

This task sets up a proxy tunnel to communicate with a non-ONS far-end node. Proxy tunnels are only necessary when the proxy server is enabled and a foreign GCC termination exists, or if static routes exist so that the GCC network is used to access remote networks or devices. You can provision a maximum of 12 proxy server tunnels.

DLP-G98 Provision a Firewall Tunnel

Purpose

This task provisions destinations that will not be blocked by the firewall. Firewall tunnels are only necessary when the proxy server is enabled and a foreign GCC termination exists, or if static routes cause the GCC network to access remote networks or devices. You can provision a maximum of 12 firewall tunnels.

Note For more information about service states, refer to the "Administrative and Service States" appendix in the Cisco ONS 15454 DWDM Reference Manual.

Step 1 In node view (single-shelf mode) or shelf view (multishelf mode) on the shelf graphic, double-click the card with the ports you want to put in or out of service. The card view appears.

Step 2 Click the Provisioning > Line tabs.

Step 3 In the Admin State column for the target port, choose one of the following from the drop-down list:

•IS (ANSI) or Unlocked (ETSI)—Puts the port in the IS-NR (ANSI) or Unlocked-enabled (ETSI) service state.

•OOS,DSBLD (ANSI) or Locked,disabled (ETSI)—Puts the port in the OOS-MA,DSBLD (ANSI) or Locked-enabled,disabled (ETSI) service state.

For ANSI nodes, traffic is not passed on the port until the service state is changed to IS-NR; OOS-MA,MT; or Out-of-Service and Autonomous, Automatic In-Service (OOS-AU,AINS). For ETSI nodes, traffic is not passed on the port until the service state is changed to Unlocked-enabled; Locked-enabled,maintenance; or Unlocked-disabled,automaticInService.

•OOS,MT (ANSI) or Locked,maintenance (ETSI)—Puts the port in the OOS-MA,MT/Locked-enabled,maintenance service state. This state does not interrupt traffic flow, but alarm reporting is suppressed and loopbacks are allowed. Raised fault conditions, whether or not their alarms are reported, can be retrieved from the CTC Conditions tab or by using the TL1 RTRV-COND command. Use the OOS-MA,MT/Locked-enabled,maintenance administrative state for testing or to suppress alarms temporarily. Change to the IS-NR/Unlocked-enabled or OOS-AU,AINS/Unlocked-disabled,automaticInService administrative states when testing is complete.

•IS,AINS (ANSI) or Unlocked,automaticInService (ETSI)—Puts the port in the OOS-AU,AINS/Unlocked-enabled,automaticInService service state. In this state, alarm reporting is suppressed, but traffic is carried and loopbacks are allowed. After the soak period passes, the port changes to IS-NR/Unlocked-enabled. Raised fault conditions, whether their alarms are reported or not, can be retrieved from the CTC Conditions tab or by using the TL1 RTRV-COND command.

Note CTC will not allow you to change a port's service state from IS-NR (ANSI)/Unlocked-enabled (ETSI) to OOS-MA,DSBLD (ANSI)/Locked-enabled,disabled (ETSI). You must first change a port to the OOS-MA,MT (ANSI)/Locked-enabled,maintenance (ETSI) state before putting it in the OOS-MA,DSBLD (ANSI)/Locked-enabled,disabled (ETSI) state.

Step 4 If you set the Admin State field to IS-AINS or Unlocked,automaticInService, set the soak period time in the AINS Soak field. This is the amount of time that the port will stay in the OOS-AU,AINS or Unlocked-enabled,automaticInService state after a signal is continuously received. When the soak period elapses, the port changes to the IS-NR or Unlocked-enabled state.

Step 5 Click Apply. The new port service state appears in the Service State column.

Step 6 As needed, repeat this task for each port.

Step 7 Return to your originating procedure (NTP).

DLP-G109 Provision Orderwire

Purpose

This task provisions orderwire on the AIC-I card.

Tools/Equipment

An AIC-I card must be installed in Slot 9.

An OSCM, OSC-CSM, MXP_2.5_10E, MXP_2.5_10G, MXPP_MR_2.5G, or MXP_MR_2.5G card must be installed.

Step 4 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 ONS 15454 nodes, you can use either local or express orderwire channels. If regenerators exist, use the express orderwire channel. You can provision up to four ONS 15454 OC-N/STM-N ports for each orderwire path.

•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 ONS 15454 nodes residing in a ring, do not provision a complete orderwire loop. For example, a four-node ring typically has Side B and Side A ports provisioned at all four nodes. However, to prevent orderwire loops, provision two orderwire ports (Side B and Side A) at all but one of the ring nodes.

Step 5 Click Next.

Step 6 In the Circuit Source area, complete the following information:

•Node—Choose the source node.

•Shelf—(Multishelf mode only) Choose the source shelf.

•Slot—Choose the source slot.

•Port—If applicable, choose the source port.

Step 7 Click Next.

Step 8 In the Circuit Destination area, complete the following information:

•Node—Choose the destination node.

•Shelf—(Multishelf mode only) Choose the destination shelf.

•Slot—Choose the destination slot.

•Port—If applicable, choose the destination port.

Step 9 Click Finish.

Step 10 Return to your originating procedure (NTP).

DLP-G110 Create a User Data Channel Circuit

Purpose

This task creates a UDC circuit on the ONS 15454. A UDC circuit allows you to create a dedicated data channel between nodes.

Tools/Equipment

An OSCM, OSC-CSM, MXPP_MR_2.5G, or MXP_MR_2.5G card must be installed.

Step 6 In the Transmit Section Trace String Size area, click 1 byte or 16 byte. The 1 byte option allows you to enter one character and the 16 byte option allows a 15 character string.

Step 7 In the New Transmit String field, enter the string that you want to transmit. Enter a string that makes the destination port easy to identify, such as the node IP address, node name, or another string. If the New Transmit String field is left blank, the J0 transmits a string of null characters.

Step 8 If you set the Section Trace Mode field to Manual, enter the string that the destination port should receive from the source port in the New Expected String field.