Cisco ONS 15454 Series Multiservice Transport Platforms User Guide

OCHNC circuits establish connectivity between two optical nodes on a specified C-band wavelength. The connection is made through the ports present on the wavelength selective switches, multiplexers, demultiplexer, and add/drop cards. In an OCHNC circuit, the wavelength from a source OCH port ingresses to a DWDM system and then egresses from the DWDM system to the destination OCH port.

OCHNC Ports

Card	Source Ports	Destination Ports
32WSS, 32WSS-L, 40-WSS-C, 40-WSS-CE	ADD-RX	–
32MUX-O, 40-MUX-C	–	CHAN-RX
32DMX-O, 32DMX, 32DMX-L, 40-DMX-C, 40-DMX-CE	—	CHAN-TX

OCHCC Circuits
OCHCC circuits extend the OCHNC to create an optical connection from the source client port to the destination client port of the TXP/MXP cards. An OCHCC circuit represents the actual end-to-end client service passing through the DWDM system.

Product Usage Instructions

Creating Optical Channel Circuits
To create an optical channel circuit, follow these steps:

Select the desired circuit in the Circuits tab.
The corresponding circuit in the network map will be highlighted.

To deselect a circuit, simply click on it in the Circuits tab.
The corresponding circuit in the network map will be deselected.

Provisionable Patchcords
To provision patchcords, please refer to the specificinstructions provided in the relevant sections of the user manual.

Frequently Asked Questions (FAQ)

Q: What does ONS 15454 refer to?
A: ONS 15454 refers to both ANSI and ETSI shelf assemblies of the product.

Q: What are the different card models available for ONS 15454?
A: The different card models available for ONS 15454 are 15454-M-RAMAN-CTP, 15454-M-RAMAN-COP, 15454-M-100G-LC-C, 15454-M-10x10G-LC, and 15454-M-CFP-LC.

Q: What are the types of optical channel circuits provided by ONS 15454?
A: ONS 15454 provides OCHNC circuits and OCHCC circuits.

View Fullscreen

Creating Optical Channel Circuits and Provisionable Patchcords
This chapter explains the Cisco ONS 15454 dense wavelength division multiplexing (DWDM) optical channel (OCH) circuit types and virtual patchcords that can be provisioned on the Cisco ONS 15454. Circuit types include the OCH client connection (OCHCC), the OCH trail, and the OCH network connection (OCHNC). Virtual patchcords include internal patchcords and provisionable (external) patchcords (PPCs). This chapter also describes End-to-End SVLAN Circuit that can be created between GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE cards. This chapter explains how to create Cisco ONS 15454 dense wavelength division multiplexing (DWDM) optical channel client connections (OCHCCs), optical channel network connections (OCHNCs), optical trail circuits, and STS circuits. The chapter also tells you how to create provisionable patchcords, upgrade OCHNCs to OCHCCs, manage SVLANs for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards, and manage overhead circuits.
Note Unless otherwise specified, “ONS 15454” refers to both ANSI and ETSI shelf assemblies.
Note In this chapter, “RAMAN-CTP” refers to the 15454-M-RAMAN-CTP card. “RAMAN-COP” refers to the 15454-M-RAMAN-COP card.
Note In this chapter, the “NFV view” refers to the “DWDM Network Functional View (NFV)”. The “GMPLS view” refers to the “DWDM Network Functional View (GMPLS)”.
Note In this chapter, “100G-LC-C card” refers to the 15454-M-100G-LC-C card. “10x10G-LC” refers to the 15454-M-10x10G-LC card. “CFP-LC” refers to the 15454-M-CFP-LC card.
· Optical Channel Circuits, on page 2 · Virtual Patchcords, on page 9
Creating Optical Channel Circuits and Provisionable Patchcords 1

Optical Channel Circuits

Creating Optical Channel Circuits and Provisionable Patchcords

· End-to-End SVLAN Circuit, on page 15 · NTP-G151 Creating, Deleting, and Managing Optical Channel Client Connections, on page 17 · NTP-G178 Creating, Deleting, and Managing Optical Channel Trails, on page 40 · NTP-G59 Creating, Deleting, and Managing Optical Channel Network Connections, on page 48 · NTP-G353 Creating GMPLS Circuits Using the Fast Circuit Mode, on page 49 · NTP-G334 Configuring GMPLS Optical Restoration, on page 51 · NTP-G359 Changing the Channel Frequency Measurement Unit, on page 74 · NTP-G200 Creating, Deleting, and Managing STS or VC Circuits for the ADM-10G Card, on page 75 · NTP-G150 Upgrading Optical Channel Network Connections to Optical Channel Client Connections,
on page 85 · NTP-G183 Diagnosing and Fixing OCHNC and OCH Trail Circuits, on page 89 · NTP-G58 Locating and Viewing Optical Channel Circuits, on page 91 · NTP-G184 Creating a Provisionable Patchcord, on page 98 · NTP-G181 Managing GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card SVLAN Databases, on page
106 · NTP-G60 Creating and Deleting Overhead Circuits, on page 109 · NTP-G62 Creating a J0 Section Trace, on page 118 · NTP-G203 Creating End-to-End SVLAN Circuits, on page 119 · NTP-G229 Provisioning DCN Extension for a Network Using GCC/DCC, on page 122 · NTP-G245 Creating an Automatically Routed VCAT Circuit, on page 123 · NTP-G246 Creating a Manually Routed VCAT Circuit, on page 127 · NTP-G247 Enabling or Disabling Path Performance Monitoring on Intermediate Nodes, on page 130 · DLP-G803 Configuring an Explicit Route Object, on page 137 · DLP-G804 Recording a Route Object, on page 138 · DLP-G805 Configuring SRLG Diversity , on page 138 · DLP-G806 Repairing a Circuit, on page 139 · Understanding and Configuring SSON, on page 141 · Provision GMPLS Optical Channel Network Connections Using Non-SSON, on page 153 · NTP-G365 Creating,Managing, and Deleting ODU Circuits for the 400G-XP-LC Card, on page 154
Optical Channel Circuits
The DWDM optical circuits provide end-to-end connectivity using three OCH circuit types:
· Optical Channel Network Connections (OCHNC)
· Optical Channel Client Connections (OCHCC)
· Optical Channel Trails (OCH Trails)
A graphical representation of OCH circuits is shown in the following figure.

Creating Optical Channel Circuits and Provisionable Patchcords 2

Creating Optical Channel Circuits and Provisionable Patchcords Figure 1: Optical Channel Circuits

OCHNC Circuits

When the user selects a circuit in the Circuits tab, the corresponding circuit in the network map is highlighted. When the user deselects a circuit in the Circuits tab, the corresponding circuit in the network map is also deselected.
When the transponders are in non-co-located nodes and there is an optical loss of signal on the filter card for a particular wavelength, the circuit for that particular wavelength does not go down to OOS state.

OCHNC Circuits
OCHNC circuits establish connectivity between two optical nodes on a specified C-band wavelength. The connection is made through the ports present on the wavelength selective switches, multiplexers, demultiplexer, and add/drop cards. In an OCHNC circuit, the wavelength from a source OCH port ingresses to a DWDM system and then egresses from the DWDM system to the destination OCH port. The source and destination OCH port details are listed in the following table.
Table 1: OCHNC Ports

Card
32WSS 32WSS-L 40-WSS-C 40-WSS-CE
32MUX-O 40-MUX-C
32DMX-O 32DMX 32DMX-L 40-DMX-C 40-DMX-CE

Source Ports ADD-RX

Destination Ports —

CHAN-RX —

— CHAN-TX

Creating Optical Channel Circuits and Provisionable Patchcords 3

OCHCC Circuits

Creating Optical Channel Circuits and Provisionable Patchcords

Card

Source Ports

4MD AD-1C-xx.x AD-4C-xx.x

CHAN-RX

40-SMR1-C 40-SMR2-C

ADD-RX

15216-MD-40-ODD CHAN-RX 15216-MD-40-EVEN

15216-EF-40-ODD CHAN-RX 15216-EF-40-EVEN

15216-MD-48-ODD CHAN-RX 15216-MD-48-EVEN

15216-FLD-4

CHAN-RX

Destination Ports CHAN-TX
DROP-TX CHAN-TX CHAN-TX CHAN-TX CHAN-TX

Note When the 40-SMR1-C or 40-SMR2-C card operates along with the 15216-MD-40-ODD, 15216-EF-40-ODD, or 15216-MD-48-ODD (ONS 15216 40 or 48-channel mux/demux) patch panel, the OCH ports on the patch panel are the endpoints of the OCHNC circuit. When the 40-SMR1-C or 40-SMR2-C card operates along with the 40-MUX-C and 40-DMX-C cards, the endpoints of the OCHNC circuit are on the MUX/DMX cards.
OCHCC Circuits
OCHCC circuits extend the OCHNC to create an optical connection from the source client port to the destination client port of the TXP/MXP cards. An OCHCC circuit represents the actual end-to-end client service passing through the DWDM system.
Each OCHCC circuit is associated to a pair of client or trunk ports on the transponder (TXP), muxponder (MXP), GE_XP (in layer-1 DWDM mode), 10GE_XP (in layer-1 DWDM mode), or ITU-T line card.
The OCHCCs can manage splitter protection as a single protected circuit. However, for the Y-Cable protection, two OCHCC circuits and two protection groups are required.
OCH Trail Circuits
OCH trail circuits transport the OCHCCs. The OCH trail circuit creates an optical connection from the source trunk port to the destination trunk port of the Transponder (TXP), Muxponder (MXP), GE_XP, 10GE_XP, or ITU-T line card. The OCH trail represents the common connection between the two cards, over which all the client OCHCC circuits, SVLAN circuits or STS circuits are carried.
Once an OCHCC is created, a corresponding OCH Trail is automatically created. If the OCHCC is created between two TXP, MXP, GE_XP, or 10GE_XP cards, two circuits are created in the CTC. These are:

Creating Optical Channel Circuits and Provisionable Patchcords 4

Creating Optical Channel Circuits and Provisionable Patchcords

OCH Trail Circuits

One OCHCC (at client port endpoints) One OCH trail (at trunk port endpoints) If the OCHCC is created between two TXPP or two MXPP cards, three circuits are created in the CTC. These are:
· One OCHCC (at client port endpoints) · Two OCH Trails (at trunk port endpoints) One for the working and other for the protect trunk.
Note On a TXP, MXP, and GE_XP card (in layer 1 DWDM mode), additional OCHCC circuits are created over the same OCH trail.

Note On a TXP, MXP, GE_XP (in layer 1 DWDM mode), and 10GE_XP (in layer 1 DWDM mode) card, the OCH trail cannot be created independently, and is created along with the first OCHCC creation on the card. However, on a GE_XP card (in layer-2 DWDM mode), 10GE_XP card (in layer-2 DWDM mode), and ADM_10G card, an OCH trail can be created between the trunk ports for the upper layer circuits (SVLAN in GE_XP/10GE_XP and STS in ADM_10G). No OCHCC is supported in these cases.

If the OCHCC is created between two ITU-T line cards, only one trunk port belongs to the OCHCC at each end of the circuit. The following table lists the ports that can be OCHCC and OCH trail endpoints.
Table 2: OCHCC and OCH Trail Ports

Card
TXPs MXPs GE_XP 10GE_XP ADM-10G
ITU-T line cards: · OC48/STM64 EH · OC192 SR/STM64 · MRC-12 · MRC-2.5-12 · MRC-2.5G-4

OCHCC Any client port

OCH Trail Any trunk port

Any trunk port

The following figure shows the relationships and optical flow between the OCHCC, OCH trail, and OCHNC circuits.

Creating Optical Channel Circuits and Provisionable Patchcords 5

Administrative and Service States Figure 2: Optical Channel Management

Creating Optical Channel Circuits and Provisionable Patchcords

Administrative and Service States
OCHCCs, OCH trails, and OCHNCs occupy three different optical layers. Each OCH circuit has its own administrative and service states. The OCHCCs impose additional restrictions on changes that can be made to client card port administrative state. The OCHCC service state is the sum of the OCHCC service state and the OCH trail service state. When creating an OCHCC circuit, you can specify an initial state for both the OCHCC and the OCH trail layers, including the source and destination port states. The ANSI/ETSI administrative states for the OCHCC circuits and connections are:
· IS/Unlocked · IS,AINS/Unlocked,AutomaticInService · OOS,DSBLD/Locked,disabled
OCHCC service states and source and destination port states can be changed independently. You can manually modify client card port states in all traffic conditions. Setting an OCHCC circuit to OOS,DSBLD/Locked,disabled state has no effect on OCHCC client card ports. An OCH trail is created automatically when you create an OCHCC. OCH trails can be created independently between OCH-10G cards and GE_XP and 10GE_XP when they are provisioned in Layer 2 Over DWDM mode. The OCH trail ANSI/ETSI administrative states include:
· IS/Unlocked · IS,AINS/Unlocked,automaticInService · OOS,DSBLD/Locked,disabled
Creating Optical Channel Circuits and Provisionable Patchcords 6

Creating Optical Channel Circuits and Provisionable Patchcords

Administrative and Service States

You can modify OCH trail circuit states from the Edit Circuit window. Placing an OCH trail OOS,DSBLD/Locked,disabled causes the following state changes:
· The state of the OCH trail ports changes to OOS,DSBLD/Locked,disabled.
· The OCHNC state changes to OOS,DSBLD/Locked,disabled.
Changing the OCH trail state to IS,AINS/Unlocked,automaticInService causes the following state changes:
· The state of the OCH trail trunk ports changes to IS/Unlocked.
· The OCHNC state changes to IS,AINS/Unlocked,automaticInService.
The OCH trail service state is the sum of the OCHCC trunk port state and the OCHNC (if applicable) state. Changing the client card trunk ports to OOS,DSBLD/Locked,disabled when the OCH trail state IS/Unlocked will cause the OCH trail state to change to OOS,DSBLD/Locked,disabled and its status to change to Partial.
The OCHNC circuit states are not linked to the OCHCC circuit states. The administrative states for the OCHNC circuit layer are:
· IS,AINS/Unlocked,AutomaticInService
· OOS,DSBLD/Locked,disabled
When you create an OCHNC, you can set the target OCHNC circuit state to IS/Unlocked or OOS,DSBLD/Locked,disabled. You can create an OCHNC even if OCHNC source and destination ports are OOS,MT/Locked,maintenance. The OCHNC circuit state will remain OOS-AU,AINS/Unlocked-disabled,automaticInService until the port maintenance state is removed. During maintenance or laser shutdown, the following behavior occurs:
· If OCHNCs or their end ports move into an AINS/AutomaticInService state because of user maintenance activity on an OCHCC circuit (for example, you change an optical transport section (OTS) port to OOS,DSBLD/Locked,disabled), Cisco Transport Controller (CTC) suppresses the loss of service (LOS) alarms on the TXP, MXP, GE_XP, 10GE_XP, or ITU-T line card trunk ports and raises a Trail Signal Fail condition. Line card trunk port alarms are not changed, however.
· If TXP client or trunk port are set to OOS,DSBLD/Locked,disabled state (for example, a laser is turned off) and the OCH trunk and OCH filter ports are located in the same node, the OCH filter LOS alarm is demoted by a Trail Signal Fail condition.
OCHCCs are associated with the client card end ports. Therefore, the following port parameters cannot be changed when they carry an OCHCC:
· Wavelength
· Service (or payload type)
· Splitter protection
· ITU-T G.709
· Forward error correction (FEC)
· Mapping
Certain OCHCC parameters, such as service type, service size, and OCHNC wavelength can only be modified by deleting and recreating the OCHCC. If the OCHCC has MXP end ports, you can modify services and parameters on client ports that are not allocated to the OCHCC. Some client port parameters, such as Ethernet

Creating Optical Channel Circuits and Provisionable Patchcords 7

Creating and Deleting OCHCCs

Creating Optical Channel Circuits and Provisionable Patchcords

frame size and distance extension, are not part of an OCHCC so they can be modified if not restricted by the port state. For addition information about administrative and service states, see the Administrative and Service States document.
Creating and Deleting OCHCCs
To create an OCHCC, you must know the client port states and their parameters. If the client port state is IS/Unlocked, OCHCC creation will fail if the OTN line parameters (ITU-T G.709, FEC, signal fail bit error rate (SF BER), and signal degrade bit error rate (SD BER) on the OCHCC differ from what is provisioned on the trunk port. The port state must be changed to OOS-DSLB/Locked,disabled in order to complete the OCHCC.
If you delete an OCHCC, you can specify the administrative state to apply to the client card ports. For example, you can have the ports placed in OOS,DSBLD/Locked,disabled state after an OCHCC is deleted. If you delete an OCHCC that originates and terminates on MXP cards, the MXP trunk port states can only be changed if the trunk ports do not carry other OCHCCs.
OCHCCs and Service and Communications Channels
Although optical service channels (OSCs), generic communications channels (GCCs), and data communications channels (DCCs) are not managed by OCHCCs, the following restrictions must be considered when creating or deleting OCHCCs on ports with service or communication channels:
· Creating an OCHCC when the port has a service or a communications channel is present–OCHCC creation will fail if the OCHCC parameters are incompatible with the GCC/DCC/GCC. For example, you cannot disable ITU-T G.709 on the OCHCC if a GCC carried by the port requires the parameter to be enabled.
· Creating a service or communications channel on ports with OCHCCs–OCHCC creation will fail if the GCC/DCC/GCC parameters are incompatible with the OCHCC.
· Deleting an OCHCC on ports with service or communications channels–If an OSC/GCC/DCC is present on a TXP, MXP, GE_XP, 20GE_XP, or ITU-T line card client or trunk port, you cannot set these ports to the OOS,DSBLD/Locked,disabled state after the OCHCC circuit is deleted.
Optical Cross Connection Label
Optical Cross Connection (OXC) label is an alphanumeric label, 12 characters long, and used as an identifier on the flex nodes.
The OXC label is used for all entities, labels, and general information related to an allocated spectrum slice. The OXC label is related to an OXC only on a specific node.
There are two ways to create OXC:
· An end-to-end circuit provisioning through WSON (TL1, UNI, or CTC), through the network, built by a sequence of OXC on neighbor nodes. All OXCs of the circuit have the same label.
· A single OXC created through TL1 legacy commands, where each node gets an OXC creation request, and the end-to-end consistency of central frequency, and width must be maintained by the client.
The management of optical path with the same frequency and the same width on the neighbor nodes is supported. Two OXCs with the same label in the same port is not supported. The labels that are not uniquely

Creating Optical Channel Circuits and Provisionable Patchcords 8

Creating Optical Channel Circuits and Provisionable Patchcords

Related Procedures

identified results in a label collision. The OXC label is not applicable on legacy nodes. In legacy nodes, the OXC identifier is the central wavelength in nanometers
Related Procedures
· NTP-G151 Creating, Deleting, and Managing Optical Channel Client Connections, on page 17
· NTP-G178 Creating, Deleting, and Managing Optical Channel Trails, on page 40
· NTP-G59 Creating, Deleting, and Managing Optical Channel Network Connections, on page 48
· NTP-G58 Locating and Viewing Optical Channel Circuits, on page 91
Virtual Patchcords
The TXP, MXP, TXPP, MXPP, GE_XP, 10GE_XP, and ADM-10G client ports and DWDM filter ports can be located in different nodes or in the same single-shelf or multishelf node. ITU-T line card trunk ports and the corresponding DWDM filter ports are usually located in different nodes. OCHCC provisioning requires a virtual patchcord between the client card trunk ports and the DWDM filter ports. Depending on the physical layout, this can be an internal patchcord or a provisionable (external) patchcord (PPC). Both patchcord types are bidirectional. However, each direction is managed as a separate patchcord. Internal patchcords provide virtual links between the two sides of a DWDM shelf, either in single-shelf or multishelf mode. They are viewed and managed in the Provisioning > WDM-ANS > Internal Patchcords tab. When the NE update file is imported in CTC, the Provisioning > WDM-ANS > Internal Patchcord tab is populated with the internal patchcords. When you create an internal patchcord manually, the Internal Patchcord Creation wizard prompts you to choose one of the following internal patchcord types:
· Trunk to Trunk (L2)–Creates an internal patchcord between two trunk ports (in NNI mode) of a GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card provisioned in the L2-over-DWDM mode.
· OCH-Trunk to OCH-Filter–Creates an internal patchcord between the trunk port of a TXP, MXP, GE_XP, 10GE_XP, or ITU-T line card, and an OCH filter card (wavelength selective switch, multiplexer, or demultiplexer).
· OCH-Filter to OCH-Filter–Creates an internal patchcord between a MUX input port and a DMX output port.
· OTS to OTS–Creates an internal patchcord between two OTS ports.
· Optical Path–Creates an internal patchcord between two optical cards, or between an optical card and a passive card.

Creating Optical Channel Circuits and Provisionable Patchcords 9

Virtual Patchcords

Creating Optical Channel Circuits and Provisionable Patchcords

Note If a Side-to-Side PPC is created between nodes, it will no longer function if the node Security Mode mode is enabled (see the “DLP-G264 Enable Node Security Mode” procedure). When 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 Side-to-Side PPC no longer operates.

The following table shows the internal patchcord Trunk (L2), OCH trunk, OCH filter, and OTS/OCH ports.
Table 3: Internal Patchcord Ports

Card GE_XP 10GE_XP GE_XPE 10GE_XPE TXPs MXPs ADM-10G ITU-T line cards OPT-BST OPT-BST-E OPT-BST-L
OPT-AMP-17-C OPT-AMP-L

Trunk (L2) Port OCH Trunk Ports
Trunk port in Any trunk port NNI mode

OCH Filter Ports —

OTS/OCH Ports —

—

Any trunk port —

—

COM-TX COM-RX OSC-TX OSC-RX

COM-TX

COM-RX

Note

The

ports

prov

mod

OSC-TX OSC-RX DC-TX DC-RX

Creating Optical Channel Circuits and Provisionable Patchcords 10

Creating Optical Channel Circuits and Provisionable Patchcords

Virtual Patchcords

Card OPT-PRE
OSCM OSC-CSM
32MUX 32MUX-O 40-MUX-C 32DMX 32DMX-L 32DMX-O 40-DMX-C 40-DMX-CE 32WSS 32WSS-L 40-WSS-C 40-WSS-CE
40-WXC-C
MMU

Trunk (L2) Port OCH Trunk Ports

—

OCH Filter Ports —

—

Any CHAN RX port

OTS/OCH Por
COM-TX COM-RX DC-TX DC-RX
COM-TX COM-RX OSC-TX OSC-RX
COM-TX

—

Any CHAN TX port

COM-RX

—

Any ADD port — —

COM-TX COM-RX EXP-TX EXP-RX DROP-TX
ADD-RX DROP-TX COM TX COM RX
EXP A TX EXP A RX

PPCs are created and managed from the network view Provisioning > Provisionable Patchcord (PPC) tab, or from the node view (single-shelf mode) or multiself view (multishelf mode) Provisioning > Comm Channel > PPC tab.

Creating Optical Channel Circuits and Provisionable Patchcords 11

Virtual Patchcords

Creating Optical Channel Circuits and Provisionable Patchcords

Figure 3: Network View Provisionable Patchcords Tab

PPCs are required when the TXP, MXP, GE_XP, 10GE_XP, ADM-10G, or ITU-T line card is installed in a different node than the OCH filter ports. They can also be used to create OTS-to-OTS links between shelves that do not have OSC connectivity. PPCs are routable and can be used to discover network topologies using Open Shortest Path First (OSPF). GCCs and DCCs are not required for PPC creation. When you create a PPC, the PPC Creation wizard asks you to choose one of the following PPC types:
· Client/Trunk to Client/Trunk (L2)–Creates a PPC between two client or trunk ports (in NNI mode) on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE cards provisioned in the L2-over-DWDM mode.
· Client/Trunk to Client/Trunk–Creates a PPC between two client or trunk ports on TXP, MXP, GE_XP, 10GE_XP, ADM_10G, or ITU-T line cards.
· Side to Side (OTS)–Creates a PPC between two OTS ports that belong to a Side. This option establishes data communications network (DCN) connectivity between nodes that do not have OSCM or OSC-CSM cards installed and therefore do not have OSC connectivity. CTC selects the OTS ports after you choose the origination and termination sides.
· OCH Trunk to OCH Filter–Creates a PPC between an OCH trunk port on a TXP, MXP, GE_XP, 10GE_XP, ADM-10G, or ITU-T line card and an OCH filter port on a multiplexer, demultiplexer, or wavelength selective switch card.
Creating Optical Channel Circuits and Provisionable Patchcords 12

Creating Optical Channel Circuits and Provisionable Patchcords

Virtual Patchcords

The following table shows the PPC Client/Trunk (L2), Client/Trunk, OTS, and OCH Filter ports.
Table 4: Provisionable Patchcord Ports

Card GE_XP 10GE_XP GE_XPE 10GE_XPE TXPs MXPs ADM-10G ITU-T line cards OPT-BST OPT-BST-E OPT-BST-L OPT-AMP-17-C OPT-AMP-L
OPT-PRE
OSC-CSM
32MUX 32MUX-O 40-MUX-C

Client/Trunk (L2) Client/Trunk Port Port
Client or trunk port Any trunk port in NNI mode

OTS Port —

—

Any trunk port

—

OCH Filter —
—

—

COM RX (Lines nodes only)

—

LINE RX

LINE TX

COM RX (When card mode is — OPT-PRE)
The following OTS ports are used when card mode is OPT-LINE:
COM TX
LINE RX
LINE TX

The following OTS ports are used — when line nodes with two OPT-PRE cards and no BST cards are installed:
COM RX
COM TX

COM RX (Lines nodes only)

—

LINE RX

LINE TX

—

Any CHAN

Creating Optical Channel Circuits and Provisionable Patchcords 13

Virtual Patchcords

Creating Optical Channel Circuits and Provisionable Patchcords

Card 32DMX 32DMX-L 32DMX-O 40-DMX-C 40-DMX-CE 32WSS 32WSS-L 40-WSS-C 40-WSS-CE 40-WXC-C
80-WXC-C
16-WXC-FS

Client/Trunk (L2) Port
—

Client/Trunk Port —

OTS Port —

—

—
COM RX COM TX EAD i, i=1 to 8 AD COM COM-RX DROP-TX EXP-TX —

40-SMR1-C

—

40-SMR2-C

17 SMR9 FS, 24 SMR9 FS, 34 SMR9 FS, SMR20 FS

MMU

—

LINE RX LINE TX
LINE RX LINE TX OSC RX OSC TX
EXP A RX EXP A TX

OCH Filter Port Any CHAN TX
Any ADD port
— —
EXP TX i, i=1 EXP RX i, i=1 COM RX COM TX UPG TX UPG RX — EXP TX EXP RX
—

Creating Optical Channel Circuits and Provisionable Patchcords 14

Creating Optical Channel Circuits and Provisionable Patchcords

PPC Provisioning Rules

For related procedure, see NTP-G184 Creating a Provisionable Patchcord
PPC Provisioning Rules
For Client/Trunk to Client/Trunk (L2) PPCs, the following provisioning rules and conditions apply: · The card must be provisioned in the L2-over-DWDM mode.
· The client or trunk ports must be in the NNI mode.
· PPCs can be created only between NNI ports of the same size (1GE-1GE or 10GE-10GE).
· A wavelength check is not performed during L2 trunk-to-trunk patchcord provisioning. The source and destination wavelengths of a L2 trunk-to-trunk PPC can be different.
For Client/Trunk to Client/Trunk PPCs, the following provisioning rules and conditions apply: · Patchcords can be created on preprovisioned or physically installed cards.
· Trunk-to-trunk connections require the same wavelength if the port is equipped. A wavelength check is automatically performed during patchcord provisioning.
· For connections involving one or more preprovisioned ports, no compatibility check is performed.
For OCH Trunk to OCH Filter PPCs, the following provisioning rules and conditions apply: · GCC and DCC links are not required to create a PPC.
· PPCs can be created for preprovisioned or physically installed cards.
· OCH trunk and OCH filter ports must be on the same wavelength. CTC checks the ports for wavelength compatibility automatically during PPC provisioning.
· For OC-48/STM-16 and OC-192/STM-64 ITU-T line cards, the wavelength compatibility check is performed only when the cards are installed. The check is not performed for preprovisioned cards.
· For all other preprovisioned cards, a wavelength compatibility check is not performed if card is set to first tunable wavelength. The wavelength is automatically provisioned on the port, according to the add/drop port that you chose when you created the PPC.
For related procedures, see NTP-G200 Creating, Deleting, and Managing STS or VC Circuits for the ADM-10G Card, on page 75
End-to-End SVLAN Circuit
An end-to-end SVLAN circuit can be created between GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE cards through a wizard in CTC. SVLAN circuits created this way are only a snapshot of the SVLAN settings (NNI and QinQ) of each card in the network. If an end-to-end SVLAN circuit is created via CTC and the SVLAN settings of the cards are changed manually, CTC does not update the SVLAN circuit created with the new settings. To update the SVLAN circuit in CTC, the circuit must be refreshed. However, any changes made to subtended OCH trail circuits are reflected in the SVLAN circuit in CTC. If an OCH trail becomes incomplete and the current SVLAN circuit snapshot has some SVLAN circuits that are using it, they remain incomplete. If the snapshot contains incomplete SVLAN circuits and an OCH trail circuit becomes available, the incomplete SVLAN circuit snapshot in CTC appears to be complete.

Creating Optical Channel Circuits and Provisionable Patchcords 15

End-to-End SVLAN Provisioning Rules

Creating Optical Channel Circuits and Provisionable Patchcords

When the destination port of the SVLAN circuit facing the router is configured as a NNI client port, the outgoing ethernet packets do not drop the SVLAN tag when they exit the MSTP network allowing the router to determine the origin of the ethernet packet. SVLAN circuits are stateless circuits; an administrative or service state need not be set.
Note During SVLAN provisioning, if a SVLAN circuit span using UNI ports in transparent mode is over subscribed, a warning message is displayed. However, the circuit is created. This is supported on channel groups on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE cards.
For related procedures, see: · NTP-G181 Managing GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card SVLAN Databases, on page 106 · NTP-G203 Creating End-to-End SVLAN Circuits, on page 119
End-to-End SVLAN Provisioning Rules
The following provisioning rules and conditions apply to end-to-end SVLAN circuits: · GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards must be provisioned in L2-over-DWDM mode. · SVLAN database must be loaded with the SVLAN. · SVLAN circuits are routed through OCH trail circuits or PPC; Client/Trunk to Client/Trunk (L2). Therefore, before creating an SVLAN circuit, make sure that the subtended OCH trail circuits between GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards or PPC links are created. · For protected SVLAN circuits, create a ring (through OCH trail circuits), define a primary node, and enable the protection role.
For information on how to create end-to-end SVLAN circuit, see the NTP-G203 Creating End-to-End SVLAN Circuits, on page 119 procedure.

Creating Optical Channel Circuits and Provisionable Patchcords 16

Creating Optical Channel Circuits and Provisionable Patchcords

NTP-G151 Creating, Deleting, and Managing Optical Channel Client Connections

Purpose

This procedure creates, deletes, and manages OCHCC circuits. The OCHCC circuits can be created using the Circuit Creation wizard or the Circuit Creation view. OCHCCs create an end-to-end optical management path between TXP, MXP, GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE (when provisioned as TXPs or MXPs), OTU2_XP, 100G-LC-C, 10x10G-LC, CFP-LC, 100G-CK-C, 100GS-CK-LC, 200G-CK-LC, AR_MXP, AR_XP, or AR_XPE client ports, or between ITU-T trunk ports. ITU-T line cards include: OC48 ELR/STM64 EH, OC192 SR1/STM64 IO, MRC-12, MRC-2.5-12, and MRC-2.5G-4. An OCHCC circuit can also be created between the MSTP TXP client interface and the router PLIM interface (10 G or 100 G ethernet client interface). The OCHCC circuit is transported by an OCH trail circuit that is associated to one or more OCHNC circuits (for example, an OCHCC circuit passing through a regen node).

Tools/Equipment

None

Prerequisite Procedures

· “Turn Up a Node” chapter · DLP-G46 Log into CTC

Required/As Needed Onsite/Remote Security Level

As needed Onsite or remote Provisioning or higher

Note This procedure is not applicable to the ADM-10G card or GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards that are provisioned in L2-over-DWDM mode.
Procedure

Step 1 Step 2
Step 3

As needed, identify the OCHCC to be provisioned using the DLP-G350 Use the Cisco Transport Planner Traffic Matrix Report. If you want to assign a name to the OCHCC source and destination ports before you create the circuit, complete the DLP-G104 Assigning a Name to a Port, on page 18. If not, continue with Step 3.
Tip Naming the client ports help in identifying them correctly later.
If the client TXP, MXP, or ITU-T line cards are installed in a multishelf node, continue with Step 4. If not, complete the following substeps: a) Use the information obtained from the Cisco Transport Planner traffic matrix report in Step 1 to complete
the DLP-G344 Verifying Provisionable and Internal Patchcords, on page 88. If provisionable patchcords

Creating Optical Channel Circuits and Provisionable Patchcords 17

DLP-G104 Assigning a Name to a Port

Creating Optical Channel Circuits and Provisionable Patchcords

Step 4
Step 5 Step 6
Step 7 Step 8 Step 9 Step 10 Step 11 Step 12

(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 4. If not, continue with Step b.
b) Complete the NTP-G184 Creating a Provisionable Patchcord, on page 98 to create the PPCs between the OCHCC source and destination nodes.

Note

For the AR_XPE card, you can specify the ODU0 and ODU1 trunk side bandwidth when a

1GE or 1GFC payload is configured on the card.

If the client TXP/MXP/ITU-T line cards are installed in a multishelf node, use the information obtained from the Cisco Transport Planner 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 “NTP-G242 Create an Internal Patchcord Manually” procedure. 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 5. Complete the DLP-G345 Verifying OCHCC Client Ports, on page 19 to verify the port rate and service state. To provision the OCHCC circuit, use either of the following procedures as needed:
· DLP-G346 Provisioning Optical Channel Client Connections, on page 20
· DLP-G705 Provisioning GMPLS Optical Channel Client Connections, on page 28
Complete the DLP-G706 Performing Optical Validation of GMPLS Circuits, on page 37, as needed. Complete the DLP-G707 Upgrading a Non-GMPLS Circuit to a GMPLS Circuit, on page 37, as needed. Complete the DLP-G777 Upgrading a GMPLS Circuit from Legacy Signaling to LOGO Signaling, on page 38, as needed. Complete the DLP-G424 Editing an OCHCC Circuit Name, on page 32, as needed. Complete the DLP-G394 Changing an OCHCC Administrative State, on page 32, as needed. Complete the DLP-G347 Deleting Optical Channel Client Connections, on page 30, as needed.
Stop. You have completed this procedure.

DLP-G104 Assigning a Name to a Port

Purpose

This task assigns a name to a port on any card.

Tools/Equipment

None

Prerequisite Procedures DLP-G46 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher

Creating Optical Channel Circuits and Provisionable Patchcords 18

Creating Optical Channel Circuits and Provisionable Patchcords

DLP-G345 Verifying OCHCC Client Ports

Procedure

Step 1 Step 2 Step 3 Step 4
Step 5 Step 6

In node view, double-click the card that has the port that you want to provision. This can be any port on a traffic-carrying card. The card view opens. Click the Provisioning tab. Double-click the Port Name table cell for the port number where you are assigning a name. The cell activates and a blinking cursor indicates where you should enter the port name. Enter the port name.
The port name can be up to 80 alphanumeric/special characters. The field is blank by default.
Click Apply. Return to your originating procedure (NTP).

DLP-G345 Verifying OCHCC Client Ports

Purpose

This task verifies the rate and service state of the OCHCC client ports.

Tools/Equipment

None

Prerequisite Procedures DLP-G46 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher

Procedure

Step 1 Step 2 Step 3 Step 4
Step 5 Step 6

In node view, double-click the TXP, MXP, OTU2_XP, AR_MXP, AR_XP, AR_XPE, or ITU-T line card where you want to verify the client ports. The card view opens.
Click the Provisioning > Maintenance tabs.
Click the Provisioning > Pluggable Port Modules tabs.
Verify that a pluggable port module has been created and that the port rate under the Pluggable Port area is provisioned. If so, continue with Step 5. If not, complete the DLP-G726 Preprovisioning a Multirate PPM and “DLP-G278 Provision the Optical Line Rate” tasks.
Repeat Steps 1 through 4 for each TXP, MXP, OTU2_XP, AR_MXP, AR_XP, AR_XPE, or ITU-T line card containing OCHCC ports that you want to verify.
Return to your originating procedure (NTP).

Creating Optical Channel Circuits and Provisionable Patchcords 19

DLP-G346 Provisioning Optical Channel Client Connections

Creating Optical Channel Circuits and Provisionable Patchcords

DLP-G346 Provisioning Optical Channel Client Connections

Purpose

This task creates an OCHCC between two TXP, MXP, GE_XP and GE_XPE (when configured in TXP or MXP mode), 10GE_XP and 10GE_XPE (when configured in TXP or MXP mode), OTU2_XP, AR_MXP, AR_XP, or AR_XPE client ports, or two ITU-T-compliant line card trunk ports.

Tools/Equipment

Cisco Transport Planner Traffic Matrix Report

Prerequisite Procedures DLP-G46 Log into CTC DLP-G345 Verifying OCHCC Client Ports, on page 19

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher

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

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-G424 Editing an OCHCC Circuit Name, on page 32.

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.

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. If any of the trunk ports, including OTU2-XP regen ports, are in-service state, a warning message “Trunk settings are not applied on any of the trunk ports” is displayed with details of the trunk ports that are in in-service state.

Creating Optical Channel Circuits and Provisionable Patchcords 20

Creating Optical Channel Circuits and Provisionable Patchcords

DLP-G346 Provisioning Optical Channel Client Connections

Note In a node using OTU2_XP cards configured in the regen mode, a single OCHCC circuit can be created that passes through the OTU2_XP card. Internal patch cords must be created from the OTU2_XP regen ports to the respective add/drop cards. OCHCC circuit creation through OTU2_XP cards in regen mode is not supported if different wavelengths are used on the two OTU2_XP regen ports.

Note The OCHCC circuit creation is not supported between different payloads in the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards.

Note The 40G-MXP-C card configured in the unidirectional regen mode does not support OCHCC circuit creation. Two bidirectional OCHNC circuits can be created, one on either side of the regenerator group for managing the circuit.

Note In AR_MXP, AR_XP, and AR_XPE cards, you cannot create the circuits using FICON payload option in Circuit Creation wizard. Create circuits using FC payload to bring up FICON traffic.

Note If loopback is configured on the VTXP port, CTC does not create the OCHCC and OCH Trail circuits and displays a warning message.
Procedure

Step 1 Step 2 Step 3 Step 4 Step 5

From the View menu, choose Go to Network View. Click the Circuits tab, then click Create. In the Circuit Creation dialog box, choose OCHCC from the Circuit Type list. Click Next. In the Circuit area of the Circuit Attributes page, provision the OCHCC circuit attributes:
· Name–Assign a name to the OCHCC. The name is limited to 80 characters, which can be a combination of alphanumeric (a-z, A-Z, 0-9) and special characters (+, #,%, and so on, 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. When a circuit includes a network element with release prior to 9.60, the circuit name is limited to 48 characters.
· 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. The following table provides the OCHCC payload types and rates.

Creating Optical Channel Circuits and Provisionable Patchcords 21

DLP-G346 Provisioning Optical Channel Client Connections

Creating Optical Channel Circuits and Provisionable Patchcords

Note

The payload type and rate must match the PPM provisioning on the client cards at the source

and destination nodes.

Table 5: OCHCC Client Rates

Payload Type SONET/SDH Ethernet FC/FICON
Data Storage
Video Other

Rates
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
10GE–One Gigabit Ethernet 11.25 Gbps 1GE–One Gigabit Ethernet 1.125 Gbps
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
ESCON–Enterprise System Connection 200 Mbps (IBM signal) ISC Peer–Inter System 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) ISC1–Inter system connect Link 1 (ISC1)
HDTV–High Definition Television SDI/DI–Serial Digital Interface and Digital Video signal type 1 DV6000–Proprietary signal from video vendor DVB-ASI–Proprietary signal from video vendor
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 the following tables for C-band and L-band wavelengths.

Creating Optical Channel Circuits and Provisionable Patchcords 22

Creating Optical Channel Circuits and Provisionable Patchcords

DLP-G346 Provisioning Optical Channel Client Connections

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.

Table 6: OCH C-Band Channels
Channel No. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24

Channel ID 30.3 31.1 31.9 33.4 32.6 34.2 35.0 35.8 36.1 37.4 38.1 38.9 39.7 40.5 41.3 42.1 42.9 43.7 44.5 44.3 46.1 46.9 47.7 48.5

Frequency (GHz) 195.9 195.8 195.7 195.5 195.6 195.4 195.3 195.2 195.1 195 194.9 194.8 194.7 194.6 194.5 194.4 194.3 194.2 194.1 194 193.9 193.8 193.7 193.6

Wavelength (nm) 1530.33 1531.12 1531.90 1532.68 1533.47 1534.25 1535.04 1535.82 1536.61 1537.40 1538.19 1538.98 1539.77 1540.56 1541.35 1542.14 1542.94 1543.73 1544.53 1545.32 1546.12 1546.92 1547.72 1548.51

Creating Optical Channel Circuits and Provisionable Patchcords 23

DLP-G346 Provisioning Optical Channel Client Connections

Creating Optical Channel Circuits and Provisionable Patchcords

Channel No. 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40

Channel ID 49.3 50.1 50.9 51.7 52.5 53.3 54.1 54.9 55.7 56.5 57.3 58.1 58.9 59.7 60.6 61.3

Frequency (GHz) 193.5 193.4 193.3 193.2 193.1 193 192.9 192.8 192.7 192.6 192.5 192.4 192.3 192.2 192.1 192

Wavelength (nm) 1549.32 1550.12 1550.92 1551.72 1552.52 1553.33 1554.13 1544.94 1555.75 1556.55 1557.36 1558.17 1558.98 1559.79 1560.61 1561.42

Note

The wavelengths 1533.47, 1537.40, 1541.35, 1545.32, 1549.32, 1553.33 1557.36, 1561.42 from

the above table require 40-channel MUX or WSS cards, and 40-channel DMX cards.

Table 7: OCH L-Band Channels

Channel Number 1 2 3 4 5 6 7

Frequency Wavelength Channel

(THz)

(nm)

Number

190.85

1570.83

190.8

1571.24

190.75

1571.65

190.7

1572.06

190.65

1572.48

190.6

1572.89

190.55

1573.30

Frequency Wavelength (nm) (THz)

188.85

1587.46

188.8

1587.88

188.75

1588.30

188.7

1588.73

188.65

1589.15

188.6

1589.57

188.55

1589.99

Creating Optical Channel Circuits and Provisionable Patchcords 24

Creating Optical Channel Circuits and Provisionable Patchcords

DLP-G346 Provisioning Optical Channel Client Connections

Channel Number 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34

Frequency Wavelength Channel

(THz)

(nm)

Number

190.5

1573.71

190.45

1574.13

190.4

1574.54

190.35

1574.95

190.3

1575.37

190.25

1575.78

190.2

1576.20

190.15

1576.61

190.1

1577.03

190.05

1577.44

190

1577.86

189.95

1578.27

189.9

1578.69

189.85

1579.10

189.8

1579.52

189.75

1579.93

189.7

1580.35

189.65

1580.77

189.6

1581.18

189.55

1581.60

189.5

1582.02

189.45

1582.44

189.4

1582.85

189.35

1583.27

189.3

1583.69

189.25

1584.11

189.2

1584.53

Frequency Wavelength (nm) (THz)

188.5

1590.41

188.45

1590.83

188.4

1591.26

188.35

1591.68

188.3

1592.10

188.25

1592.52

188.2

1592.95

188.15

1593.37

188.1

1593.79

188.05

1594.22

188

1594.64

187.95

1595.06

187.9

1595.49

187.85

1595.91

187.8

1596.34

187.75

1596.76

187.7

1597.19

187.65

1597.62

187.6

1598.04

187.55

1598.47

187.5

1598.89

187.45

1599.32

187.4

1599.75

187.35

1600.17

187.3

1600.60

187.25

1601.03

187.2

1601.46

Creating Optical Channel Circuits and Provisionable Patchcords 25

DLP-G346 Provisioning Optical Channel Client Connections

Creating Optical Channel Circuits and Provisionable Patchcords

Step 6
Step 7 Step 8
Step 9

Channel Number

Frequency Wavelength Channel

(THz)

(nm)

Number

Frequency Wavelength (nm) (THz)

189.15

1584.95

189.1

1585.36

189.05

1585.78

189

1586.20

188.95

1586.62

188.9

1587.04

187.15 187.1 187.05 187 186.95 186.9

1601.88 1602.31 1602.74 1603.17 1603.60 1604.03

· 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) or a protected OCHCC when TXP is connected to a PSM card.

Note

When splitter protection is configured for a non-WSON circuit using different wavelengths,

the work and protect paths may select the same route as the shortest route unless constraints

are provisioned for diverse paths. To overcome this issue, configure the circuit with

constraints as described in Step 14 or create a WSON circuit using DLP-G705 Provisioning

GMPLS Optical Channel Client Connections, on page 28.

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,DSBLD (ANSI)/Locked,Disabled (ETSI), and IS,AINS (ANSI)/Unlocked,AutomaticInService (ETSI).
Click Next. 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 Verifying OCHCC Client Ports, on page 19 to verify the client settings.
b) If the source and/or destination nodes are not configured for multishelf, complete the DLP-G344 Verifying Provisionable and Internal Patchcords, on page 88 to verify that the patchcords were created accurately.
If these steps do not solve the problem, refer to your next level of support.
Click Next.

Creating Optical Channel Circuits and Provisionable Patchcords 26

Creating Optical Channel Circuits and Provisionable Patchcords

DLP-G346 Provisioning Optical Channel Client Connections

Step 10
Step 11 Step 12 Step 13 Step 14 Step 15

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 Verifying OCHCC Client Ports, on page 19 to verify the client settings.
b) If the source and/or destination nodes are not configured for multishelf, complete the DLP-G344 Verifying Provisionable and Internal Patchcords, on page 88 to verify that the patchcords were created accurately.
If these steps do not solve the problem, refer to your next level of support.

Click Next. If the OCHCC is between ITU-T cards, continue with Step 12. If not, skip to Step 14.
Complete the DLP-G347 Deleting Optical Channel Client Connections, on page 30.
Click Next.
Complete the DLP-G438 Setting OCH Routing Preferences, on page 35. Skip this step and continue with Step 16 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 16.
If the circuit is being created for AR_MXP, AR_XP, or AR_XPE card with MXP_MR (low or high rate) or MXPP_MR (low or high rate) operating mode, select the ODU1 and the respective timeslot within the selected ODU1. The following table describes the bandwidth utilization for the selected payload.

Note

For the all other cards/card modes, you cannot select the ODU1 and timeslot parameters.

Table 8: Bandwidth Utilization for the Selected Payload

Payload

Number of ODU1s required

OC3

OC12

OC48

FC2

ISC3-2G

ESCON

FC1

ISC3-1G

FC4G

Number of ODU0s required
—
— — —
— 1 1 — —

Number of Timeslot required/ODU1 1
4 16 14
2 NA NA
NA

Creating Optical Channel Circuits and Provisionable Patchcords 27

DLP-G705 Provisioning GMPLS Optical Channel Client Connections

Creating Optical Channel Circuits and Provisionable Patchcords

Step 16 Step 17

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.
Return to your originating procedure (NTP).

DLP-G705 Provisioning GMPLS Optical Channel Client Connections

Purpose

This task creates an OCHCC circuit between two TXP, MXP, GE_XP and GE_XPE (when configured in TXP or MXP mode), 10GE_XP and 10GE_XPE (when configured in TXP or MXP mode), OTU2_XP client ports, ITU-T-compliant line card trunk ports, or CRS routers. It is also possible to create an OCHCC circuit between the MSTP TXP client interface and the router PLIM interface (10 G or 100 G ethernet client interface).

Tools/Equipment

Cisco Transport Planner Traffic Matrix Report

Prerequisite Procedures

· DLP-G46 Log into CTC · DLP-G345 Verifying OCHCC Client Ports, on page 19 · DLP-G733 Configuring GMPLS UNI, on page 53

Required/As Needed Onsite/Remote Security Level

As needed Onsite or remote Provisioning or higher

When the GMPLS circuit creation fails due to optical validation, a detailed error message with diagnostic logs is displayed that explains the causes of the failure. The error message provides details of the optical validation parameters (channel power, OSNR, chromatic dispersion, acceptance threshold and so on) that cause the failure.
You cannot directly create the GMPLS OCHCC circuit on the 100G-LC-C, 10x10G-LC, CFP-LC, and 100G-CK-C cards when configured in MXP-10x10G (10x10G Muxponder) card mode or with AR-XP cards. There are two ways to create the GMPLS OCHCC circuit:
· Create the GMPLS OCH trail and then create the OCHCC circuit.
· Create the OCHCC circuit and then upgrade the circuit to GMPLS OCHCC circuit.

Note In release 10.5, you can create the GMPLS OCHCC circuit directly using WSON from the DWDM network functional on all TXP/MXP cards except on the AR-MXP and AR-XPE cards. The OCHCC circuit can be created on the AR-XP cards only in the TXP-MR, TXPP-MR, MXP-MR-S, and MXPP-MR-S operating modes.

Creating Optical Channel Circuits and Provisionable Patchcords 28

Creating Optical Channel Circuits and Provisionable Patchcords

DLP-G705 Provisioning GMPLS Optical Channel Client Connections

Note Non-DWDM OCHCC circuits with Trunk to Trunk PPC are not supported in GMPLS circuits. Procedure

Step 1 Step 2 Step 3

From the View menu, choose Go to Network View and click the DWDM Functional View icon in the toolbar. The DWDM netowrk functional view opens.
From the Change Perspective drop-down list in the toolbar, choose Circuit Creation. The Circuit creation view opens.
In the Circuit Parameters pane, provision the OCHCC circuit attributes: a) Name–Assign a name to the circuit. The name is limited to 80 characters, which can be a combination
of alphanumeric (a-z, A-Z, 0-9) and special characters (+, #,%, and so on, including spaces). When a circuit includes a network element with release prior to 9.60, the circuit name is limited to 48 characters. b) Label–Type a name for the circuit label. The label can be an alphanumeric string up to 14 characters. c) Type–Choose OCHCC. d) Protected–Check to route the circuit on a protected path. Select the protection type from the drop-down list. The available options are:
· PSM–When a PSM card is connected to a TXP card.
· Y-CABLE–The circuit is protected by a transponder or muxponder card in a Y-cable protection group.
· Splitter–When a MXPP/TXPP card is used. The circuit source and destination are on MXPP_MR_2.5G and TXPP_MR_2.5G cards. These cards provides splitter (line-level) protection.

e) UNI VTXP– This parameter creates a UNI VTXP circuit; otherwise a VTXP circuit is created without UNI. This check box appears only when VTXP is selected as an end point.
f) IS–Check to place the trunk ports of the TXP /MXP card in service.
g) Wavelength Configuration — Select the check box to configure the wavelength for the circuit.
h) GMPLS/WSON Wavelength Parameters — Choose a wavelength from the first field. Select C band in the second field. In the third field, indicate whether odd or even C-band wavelengths appear.

· The even C-band wavelength supports 48 channels ranging from 1528.77 nm (196.10 THz) to 1566.31 nm (191.40 THz).
· The odd C-band wavelength supports 48 channels ranging from 1529.16 nm (196.05 THz) to 1566.72 nm (191.35 THz).

Note

MSTP legacy package supports 40 odd (1530.30 to 1561.42 nm) and 0 even (1530.72 to

1561.83) channels only.

i) Validation–Set the validation mode. For more information about validation modes, see the “Validation Modes” section in “Node Reference” chapter.
j) Acceptance threshold–Set the optical validation threshold value for the GMPLS circuit. The circuit is created if the actual optical validation result is greater than or equal to the value set in this field. For more information about the acceptance threshold value, see the “Acceptance Thresholds” section in “Node Reference” chapter.
k) Protection Acceptance Threshold–Sets the optical validation threshold value for the protected GMPLS circuit.

Creating Optical Channel Circuits and Provisionable Patchcords 29

DLP-G347 Deleting Optical Channel Client Connections

Creating Optical Channel Circuits and Provisionable Patchcords

Step 4
Step 5 Step 6 Step 7 Step 8 Step 9

In the GMPLS/WSON Optional Configuration pane, specify the attributes:
a) Ignore path Alarms — Check this check box to ignore the alarms on the path and create the circuit. This parameter is used to verify whether the circuit can be created on the path.
b) Allow Regeneration — Select this check box to allow the control plane to find a regenerator deployed in the network. The regenerators are used when an optical LSP between two endpoints is not optical or lambda feasible with a single DWDM channel.
c) Circuit Diversity — Select this option to provision a diversity path for the circuit. From the circuit pane, choose the an existing circuit that will be used as reference for the LSP diversity. The diverse path that is not taken by the new circuit is displayed in the circuit pane.
d) Priority — Select the priority level for the circuit. The priority is used in resolving resource allocation when two or more circuits require the same resource during circuit creation or restoration concurrently. The priority levels are 0 (High) to 7 (Low).
e) Channel Power Offset:
· Upstream (dBm) — Set the value of offset in dBm, negative or positive, which the COM_TX of the card uses on its PerChannelPower default value. Upstream applies to the card in the outgoing path of the circuit.
· Downstream (dBm) — Set the value of offset in dBm, negative or positive, which the COM_TX of the card uses on its PerChannelPower default value. Downstream applies to the card in the incoming path of the circuit.

Configure the source and destination ports at the circuit endpoints in the map. For more information about configuring the source and destination ports, see the “Source and Destination Port Configuration” section in “Node Reference” chapter.

Note

The OCHCC circuit endpoints must be selected on the TXP/MXP cards or the router PLIM

interface. An OCHCC circuit can also be created between the MSTP TXP client interface and

the router PLIM interface (10 G or 100 G ethernet client interface). If other ports are selected, a

warning dialog box is displayed prompting you to change the circuit type.

Define the working or protect port parameters. For more information, see the “Working and Protect Port Parameters” section in “Node Reference” chapter. Click Apply in the Working Port Parameters pane and Protected Port Parameters pane, to apply the settings.
Click Apply in the Circuit Parameters pane.
Click Yes in the Create Circuits confirmation dialog box. The OCHCC and its OCH trail appear in the Circuits tab in the Network Data pane. After the circuit status has been verified, the DISCOVERED status appears in the Status column. Depending on the size of the network, the circuit might take a few minutes to come up
Return to your originating procedure (NTP).

DLP-G347 Deleting Optical Channel Client Connections

Purpose

This task deletes DWDM OCHCC circuits.

Tools/Equipment

None

Prerequisite Procedures DLP-G46 Log into CTC

Required/As Needed

As needed

Creating Optical Channel Circuits and Provisionable Patchcords 30

Creating Optical Channel Circuits and Provisionable Patchcords

DLP-G347 Deleting Optical Channel Client Connections

Onsite/Remote Security Level

Onsite or remote Provisioning or higher

Note If you are deleting more than half of all the active OCHCCs, it is recommended 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.
Procedure

Step 1 Step 2 Step 3 Step 4 Step 5 Step 6
Step 7

Complete the to preserve existing settings and, if you want to recreate the circuits, record the circuit information. Consult your network operations center (NOC) or other appropriate personnel to verify that the OCHCC can be safely deleted. Investigate all network alarms and resolve any problems that might be affected by the OCHCC deletion. Go to the network view or the DWDM network functional view and click the Circuits tab. Under the Type column, choose one or more OCHCCs that you want to delete, then click Delete. In the Delete Circuits confirmation dialog box, complete the following:
· Change drop port admin state–This checkbox is checked by default. Choose one of the following administrative states, if you want to change the circuit source and destination port administrative state:
· 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. This option is set by default.
· OOS,MT (ANSI) or Locked,maintenance (ETSI)–Removes the ports from service for maintenance.

· Notify when completed–Checked this box if you want the CTC Alerts confirmation dialog box to notify 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. 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.

Creating Optical Channel Circuits and Provisionable Patchcords 31

DLP-G424 Editing an OCHCC Circuit Name

Creating Optical Channel Circuits and Provisionable Patchcords

Step 8
Step 9 Step 10 Step 11

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 10. a) Click Save. b) Click Browse and navigate to the directory where you want to save the file. c) Type the file name using a TXT file extension, and click OK.
Click Close to close the CTC Alerts dialog box. Complete the if you require a backup of your changes. Return to your originating procedure (NTP).

DLP-G424 Editing an OCHCC Circuit Name

Purpose

This task changes the name of an OCHCC circuit.

Tools/Equipment

None

Prerequisite Procedures DLP-G105 Provisioning Optical Channel Network Connections, on page 63 DLP-G46 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher

Procedure

Step 1 Step 2
Step 3 Step 4 Step 5 Step 6

Go to the network view, NFV view, or GMPLS view, and click the Circuits tab. To rename the OCHCC circuit, do either of the following.
· Network view–Select the OCHCC circuit in the Circuits tab and click Edit. · NFV view or GMPLS view–Double-click the circuit in the Circuits tab.
In the Edit Circuit dialog box, click the General tab. In the Name field, enter the new OCHCC circuit name. Click Apply. Return to your originating procedure (NTP).

DLP-G394 Changing an OCHCC Administrative State

Purpose Tools/Equipment

This task changes the administrative state of an OCHCC circuit. None

Creating Optical Channel Circuits and Provisionable Patchcords 32

Creating Optical Channel Circuits and Provisionable Patchcords

DLP-G437 Setting OCH Circuit Attributes

Prerequisite Procedures DLP-G346 Provisioning Optical Channel Client Connections, on page 20 DLP-G46 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher

Procedure

Step 1 Step 2
Step 3 Step 4
Step 5 Step 6
Step 7

Go to the network view, Circuit Maintenance view, or Circuit Creation view, and click the Circuits tab. To change the administrative state of the OCHCC circuit, do either of the following.
· Network view–Select the OCHCC circuit in the Circuits tab and click Edit.
· Circuit Maintenance view or Circuit Creation view–Double-click the circuit in the Circuits tab.

In the Edit Circuit dialog box, click the State tab. Click the cell in the Admin State column for the card you want to change, and choose an administrative state from the drop-down list:
· IS (ANSI) or Unlocked (ETSI)
· OOS (ANSI) or Locked (ETSI)

Click Apply.
If you are changing the OCHCC state to OOS/Locked, click OK in the confirmation dialog box. (No confirmation dialog box appears when placing OCHCCs in service.)

Note

For information about the OCH circuit state transitions, see the Administrative and Service States

document.

Return to your originating procedure (NTP).

DLP-G437 Setting OCH Circuit Attributes

Purpose

This task provisions OCH trunk attributes.

Tools/Equipment

None

Prerequisite Procedures DLP-G46 Log into CTC The OCH Circuit Attributes page must be open.

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Creating Optical Channel Circuits and Provisionable Patchcords 33

DLP-G437 Setting OCH Circuit Attributes

Creating Optical Channel Circuits and Provisionable Patchcords

Security Level Procedure

Provisioning or higher

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 trunk settings are not editable and are retained as they are on both the trunk ports. An information pop up window is shown after the circuit creation indicating that the trunk settings are not applied on any of the trunk ports. 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 TXP_MR_10EX_C, 40E-TXP-C, 40ME-TXP-C, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, MXP_2.5G_10EX_C, MXP_MR_10DMEX_C, 40G-MXP-C, 40E-MXP-C, or 40ME-MXP-C 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. If the OCHCC source or destination is an TXP_MR_10EX_C, MXP_2.5G_10EX_C, MXP_MR_10DMEX_C, 40G-MXP-C, 40E-MXP-C, 40ME-MXP-C, 40E-TXP-C, or 40ME-TXP-C card, the ITU-T G.709 OTN parameter must always be checked.

· SD BER–Choose the signal degrade bit error rate. The range of SD BER values supported for Cisco 7600 router is from 5 to 9.

· (Cisco 7600 series routers only) OPU–Choose the ITU-T G.709 OPU standard. OPU-1E and OPU-2E standards are supported on the Cisco 7600 series routers.

· SF BER–Choose the signal fail bit error rate.

· Mapping–Sets the mapping for the TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, TXP_MR_10EX_C, MXP_MR_10DME_C, MXP_MR_DME_L, and MXP_MR_10DMEX_C cards: Not Used, ODU Multiplex (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,

MXP_2.5G_10E_L, or MXP_2.5G_10EX_C card, the Mapping parameter must always

be set to Synch.

Set the proactive protection attributes. Proactive Protection Regen is supported on OTU2XP ports alone in Standard Regen and Enhanced FEC mode

Creating Optical Channel Circuits and Provisionable Patchcords 34

Creating Optical Channel Circuits and Provisionable Patchcords

DLP-G438 Setting OCH Routing Preferences

Note

Proactive protection regen is supported only on CRS-based OCH trails.

· Proactive Protection–Choose Enable or Disable.
· Trigger Threshold–Choose the minimum BER threshold to trigger proactive protection by sending forward defect indication (FDI).
· Trigger Window–The trigger window value must be in multiples of 10 ms for trigger thresholds between 1E-3 and 6E-6 or 100 ms for trigger threshold between 5E-6 to 1E-7. Enter the duration to monitor the BER before triggering the proactive protection. The trigger window must be less than or equal to 10000 ms.
· Revert Threshold–Choose a BER value, to indicate the threshold at which the FDI is cleared to allow traffic.
· Revert Window–Enter the duration to monitor the BER for which it should be less than the revert threshold value before removing the FDI sent to the router. The revert window must be less than or equal to 10000ms. The revert window value must be at least 2000ms and in multiples of 10ms for a Revert Threshold of 1E-4 to 6E-7, or 100ms for a Revert Threshold of 5E-7 to 5E-8.
· 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. Set the following attributes:
· 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 2 Return to your originating procedure (NTP).

DLP-G438 Setting OCH Routing Preferences

Purpose

This task provisions OCH routing preferences.

Tools/Equipment

None

Prerequisite Procedures DLP-G46 Log into CTC The OCH Circuit Routing Preferences page must be open.

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher

Creating Optical Channel Circuits and Provisionable Patchcords 35

DLP-G438 Setting OCH Routing Preferences

Creating Optical Channel Circuits and Provisionable Patchcords

Procedure

Step 1

In the OCH Circuit Routing Preferences page, view the circuit route. The new OCH appears with blue span arrows. The direction of the LMP links between the PLIM interface of the router and the OCH ports of the DWDM node, as well as the internal patchcords, are displayed with arrows. The LMP links and internal patchcords are unidirectional. Moving your cursor over the arrow displays span information that includes 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) The circuit constraints are displayed. Select the required option. Include and Exclude cannot be applied
to source or destination nodes.
The displayed constraints are:
· Include Node in Working Circuit Path
· Include Node in Working Restored Circuit Path
· Include Node in Protect Circuit Path
· Exclude Node from Working Circuit Path
· Exclude Node from Working Restored Circuit Path
· Include Regen Node in Working Circuit Path
· Include Regen Node in Working Restored Circuit Path
· Include Regen Node in Protect Circuit Path

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.

Step 2

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, evaluate the error, 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.
Return to your originating procedure (NTP).

Creating Optical Channel Circuits and Provisionable Patchcords 36

Creating Optical Channel Circuits and Provisionable Patchcords

DLP-G706 Performing Optical Validation of GMPLS Circuits

Purpose

This task performs revalidation of a GMPLS circuit.

Tools/Equipment

None

Prerequisite Procedures DLP-G46 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher

Procedure

Step 1 Step 2
Step 3

Go to the network view or the DWDM network functional view and click the Circuits tab.
Select the GMPLS circuit to be re-validated and click Opt Val. The optical validation is performed and its result is displayed in a pop-up window.
Return to your originating procedure (NTP).

DLP-G707 Upgrading a Non-GMPLS Circuit to a GMPLS Circuit

Purpose

This task upgrades a non-GMPLS circuit to a GMPLS circuit.

Tools/Equipment

None

Prerequisite Procedures DLP-G46 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher

Procedure

Step 1 Step 2

If the non-GMPLS circuit was provisioned in a release older than R9.40, ensure that fiber attributes are available in the Provisioning > WDM-ANS -> GMPLS/WSON -> Fiber Attributes tab. For more information about the Fiber Attributes tab, see the “Fiber Attributes and Alien Wavelength Provisioning” section. If the Fiber Attributes tab is empty, import the latest Cisco Transport Planner NE Update configuration file as described in the NTP-G143 Import the Cisco Transport Planner NE Update Configuration File” task.
Define the Alien Wavelength parameters in the Provisioning > WDM-ANS -> GMPLS/WSON -> Alien Wavelength tab if one of the following conditions exist. If not, continue with the next step.

Creating Optical Channel Circuits and Provisionable Patchcords 37

DLP-G777 Upgrading a GMPLS Circuit from Legacy Signaling to LOGO Signaling

Creating Optical Channel Circuits and Provisionable Patchcords

Step 3 Step 4
Step 5 Step 6 Step 7 Step 8

From Release 10.7, the Alien Wavelength tab available at Provisioning > WDM-ANS -> GMPLS/WSON tab is read-only. To define or update Alien Wavelength parameters, see DLP-G800 Create a Link Management Protocol (LMP) Link Using CTC , on page 57
· In the non-GMPLS circuit, the TXP or MXP or ITU-T line cards are connected to the add/drop DWDM ports with provisionable patchcords (PPCs).
· No internal patchcords exist between the TXP/MXP and the add/drop DWDM ports (for example, in the case of a CRS connected to the add/drop DWDM ports).

For more information about the Alien Wavelength tab, see the “Fiber Attributes and Alien Wavelength Provisioning”.

Go to the network view, Circuit Maintenance view, or Circuit Creation view, and click the Circuits tab. Select the circuit to be upgraded and click WSON Upgrade.

Note

The WSON Upgrade option is available only when a non-GMPLS circuit is selected.

Note

The user can also upgrade an existing GMPLS circuit from the legacy signaling to the new

signaling that supports the LOGO and regeneration features on the GMPLS circuit.

Click Yes in the Upgrade Circuits confirmation dialog box. The WSON/GMPLS Circuit Promotion dialog box is displayed.
From the Validation drop-down list, choose the validation mode. For more information about the validation modes, see the ” Validation Modes” section.
From the Promotion Validation degree drop-down list, choose the optical validation value. For more information about the acceptance threshold value, see the “Acceptance Thresholds” section.
Return to your originating procedure (NTP).

DLP-G777 Upgrading aGMPLS Circuit from Legacy Signaling to LOGO Signaling

Purpose

This task upgrades an existing GMPLS circuit from the legacy signaling to the new signaling that supports the LOGO and regeneration features on the GMPLS circuit.

Tools/Equipment

None

Prerequisite Procedures None

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher

Note This procedure applies only to R10.0.2.1.

Creating Optical Channel Circuits and Provisionable Patchcords 38

Creating Optical Channel Circuits and Provisionable Patchcords

DLP-G777 Upgrading a GMPLS Circuit from Legacy Signaling to LOGO Signaling

Procedure

Step 1 Step 2 Step 3
Step 4

Upgrade the software on nodes from R9.6.0.5 to R10.0.2.1.
After the upgrade, navigate to Provisioning > WDM-ANS > GMPLS/WSON > Fiber Attributes tab to view and define the fiber parameters.
Ensure that the following parameters in the Fiber Attributes tab have the default values on all the 10.0.2.1 nodes.

Parameter

Description

Default Value

PMD

Polarization Mode Dispersion fibre 0 coefficient in ps/sqrt(km)

Attenuator In

Input optical attenuation in dB 0 between the node output port (typically LINE-TX port) and the input of the fiber span. The span might include patchcords, attenuators, and patch panels.

Attenuator Out

Output optical attenuation in dB 0 between the node input port (typically LINE-RX port) and the output of the fiber span. The span might include patchcords, attenuators, and patch panels.

Channel Spacing

Minimum frequency spacing

between two adjacent channels in

the optical grid.

Channel Number

Maximum number of channels 80 expected on the span.

Span Validation

Specifies whether the span can be TRUE used by GMPLS algorithm for channel routing and validation.

Domain

Algorithm that is active on the span.

LOGO

Side

Specifies the optical side.

Fiber Type

Type of fiber deployed.

G652-SMF

Fiber Number

Fiber number in the duct.

Length

Length of the optical span.

(Optional) If the Attenuator In and Attenuator Out values on the node are set to NA, change the values to 0 or set to proper values based on your network design.

Creating Optical Channel Circuits and Provisionable Patchcords 39

NTP-G178 Creating, Deleting, and Managing Optical Channel Trails

Creating Optical Channel Circuits and Provisionable Patchcords

Step 5 Step 6
Step 7

For example, if an Attenuator is present on the Line side of the node, the related values need to be added in the Fiber Attributes tab.
(Optional) Run ANS on the nodes where the attenuator values were manually changed. See NTP-G37 Running Automatic Node Setup. Upgrade circuits to GMPLS signaling. a) In the Circuits tab, choose the circuit with Type=OCHTRAIL WSON UPGRADEABLE. b) From the Tools menu, choose Circuit > Gmpls Signaling Circuits. c) Click Yes in the pop-up dialog that appears.
The circuit type is upgraded to OCHTRAIL WSON. LOGO signaling will be used for the new circuit.
Return to your originating procedure (NTP).

NTP-G178 Creating, Deleting, and Managing Optical Channel Trails

Purpose

This procedure creates and deletes DWDM OCH trail circuits and changes their administrative states. The OCH trail circuits can be created using the Circuit Creation wizard or the Circuit Creation view.

Tools/Equipment

None

Prerequisite Procedures

· Turning up a Node · DLP-G46 Log into CTC

Required/As Needed Onsite/Remote Security Level

As needed Onsite or remote Provisioning or higher

Procedure

Step 1 Step 2
Step 3 Step 4

If you want to assign a name to the OCHNC source and destination ports before you create the circuit, complete the DLP-G104 Assigning a Name to a Port, on page 18. If not, continue with the next step. Complete either of the following procedures as needed, between ADM-10G cards or GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards that are provisioned in L2-over-DWDM mode:
· DLP-G395 Creating an Optical Channel Trail, on page 41
· DLP-G708 Create a GMPLS Optical Channel Trail, on page 43
Complete the DLP-G706 Performing Optical Validation of GMPLS Circuits, on page 37, as needed. Complete the DLP-G707 Upgrading a Non-GMPLS Circuit to a GMPLS Circuit, on page 37, as needed.

Creating Optical Channel Circuits and Provisionable Patchcords 40

Creating Optical Channel Circuits and Provisionable Patchcords

DLP-G395 Creating an Optical Channel Trail

Step 5
Step 6 Step 7 Step 8 Step 9

Complete the DLP-G777 Upgrading a GMPLS Circuit from Legacy Signaling to LOGO Signaling, on page 38, as needed. Complete the DLP-G710 Re-route Wavelength of GMPLS Circuits, on page 73, as needed. Complete the DLP-G425 Editing an OCH Trail Circuit Name, on page 47, as needed. Complete the DLP-G419 Changing an OCH Trail Administrative State, on page 47, as needed. Complete the DLP-G418 Deleting an Optical Channel Trail, on page 45, as needed. Stop. You have completed this procedure.

DLP-G395 Creating an Optical Channel Trail

Purpose

This task creates an OCH trail circuit between ADM-10G cards, CRS routers, or GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards when provisioned in L2-over-DWDM mode.
For OCH trails connecting ADM-10G cards, the OCH trail provides the low-layer path to route STS or VC circuits over ADM-10G cards.
For OCH trails connecting GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards in L2-over-DWDM mode, the OCH trail provides the links associated to the SVLAN entities.
For OCH trails connecting CRS or Cisco 7600 routers, the OCH trail provides end-to-end circuit connectivity between the CRS or Cisco 7600 routers passing through an MSTP network.

Tools/Equipment

None

Prerequisite Procedures DLP-G46 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher

Note OCH trail circuits are created automatically when you provision OCHCC circuits between TXP and MXP cards.

Note If loopback is configured on the VTXP port, CTC does not create the OCHCC and OCH Trail circuits and displays a warning message.

Creating Optical Channel Circuits and Provisionable Patchcords 41

DLP-G395 Creating an Optical Channel Trail

Creating Optical Channel Circuits and Provisionable Patchcords

Step 1 Step 2 Step 3 Step 4 Step 5
Step 6 Step 7
Step 8 Step 9

Procedure
From the View menu, choose Go to Network View. Click the Circuits tab, then click Create. The Circuit Creation wizard is displayed. In the Circuit Creation wizard, choose OCHTRAIL from the Circuit Type list. Click Next. In the Circuit area of the Circuit Attributes page, provision the OCH trail circuit attributes:
· Name–Assign a name to the OCH trail. The name is limited to 80 characters, which can be a combination of alphanumeric (a-z, A-Z, 0-9) and special characters (+, #,%, and so on, 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. When a circuit includes a network element with release prior to 9.60, the circuit name is limited to 48 characters.
· Type–(Display only) Displays the OCH trail type–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 6: OCH C-Band Channels, on page 23 and Table 7: OCH L-Band Channels, on page 24 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)/Unlocked automatic inservice (ETSI) or OOS,DSBLD (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,DSBLD (ANSI)/Locked,Disabled (ETSI).
Click Next. 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.
If you are creating an OCH trail circuit between CRS or Cisco 7600 routers, choose the source CRS or Cisco 7600 router from the Node drop-down list. The Shelf, Slot, and Port fields are not available. CTC automatically selects the PLIM port depending on the OCHNC Wavelength value specified in Step 5.
The source In and Out shelf (multishelf nodes only), slot, and port appear under the OTS Lines area.
Click Next. 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.
If you are creating an OCH trail circuit between CRS or Cisco 7600 routers, choose the destination CRS or Cisco 7600 router from the Node drop-down list. The Shelf, Slot, and Port fields are not available. CTC automatically selects the PLIM port depending on the OCHNC Wavelength value specified in Step 5.

Creating Optical Channel Circuits and Provisionable Patchcords 42

Creating Optical Channel Circuits and Provisionable Patchcords

DLP-G708 Create a GMPLS Optical Channel Trail

Step 10 Step 11 Step 12 Step 13
Step 14
Step 15

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.
Click Next.
Complete the DLP-G437 Setting OCH Circuit Attributes, on page 33.
Click Next.
Complete the DLP-G438 Setting OCH Routing Preferences, on page 35. 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.
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.)
Return to your originating procedure (NTP).

DLP-G708 Create a GMPLS Optical Channel Trail
Purpose
Tools/Equipment Prerequisite Procedures Required/As Needed Onsite/Remote Security Level

This task creates a GMPLS OCH trail In Release 10.0.1, as regards OCH trail routers passing through an MSTP netw None
· DLP-G46 Log into CTC
As needed Onsite or remote Provisioning or higher

Note OCH trail circuits are created automatically when you provision OCHCC circuits between TXP and MXP cards or TXP or MXP cards and router PLIM interfaces (10G ethernet controllers).

Note When the user creates a GMPLS OCH Trail circuit on the VTXP port, it is possible to retune the wavelength under these conditions:
· When the circuit is configured as restorable. · When the same wavelength is not available on the secondary path during the circuit failure.

Creating Optical Channel Circuits and Provisionable Patchcords 43

DLP-G708 Create a GMPLS Optical Channel Trail

Creating Optical Channel Circuits and Provisionable Patchcords

Step 1 Step 2 Step 3
Step 4

Procedure

From the View menu, choose Go to Network View and click the Network Functional View icon in the toolbar. The Circuit Maintenance View opens.
From the Change Perspective drop-down list in the toolbar, choose Circuit Creation. The Circuit Creation view opens.
In the Circuit Parameters pane, provision the OCH Trail circuit attributes:
a) Name–Assign a name to the circuit. The name is limited to 80 characters, which can be a combination of alphanumeric (a-z, A-Z, 0-9) and special characters (-, _). When a circuit includes a network element with release prior to ONS 15454 release 9.60, the circuit name is limited to 48 characters.
b) Label–Type a name for the circuit label. The label can be an alphanumeric string up to 14 characters. c) Type–Choose OCHTrail. d) Bidirectional–This parameter does not apply to OCH trail circuits. e) Protected–This parameter does not apply to OCH trail circuits. f) UNI VTXP– This parameter creates a UNI VTXP circuit; otherwise a VTXP circuit is created without
UNI. This check box appears only when VTXP is selected as an end point. g) IS–Check to place the trunk ports of the TXP /MXP card in service. h) Wavelength Configuration — Select the check box to configure the wavelength for the circuit. i) GMPLS/WSON Wavelength Parameters — Choose a wavelength from the first field. j) Check the Required check box to specify the original wavelength.
If the Required wavelength is available then only system will assign it else system will assign any of the available wavelength.
k) Select C band in the second field. In the third field, indicate whether odd or even C-band wavelengths appear.

Note

MSTP legacy package supports 40 odd (1530.30 to 1561.42 nm) and 0 even (1530.72 to

1561.83) channels only.

l) Validation–Set the validation mode. For more information about the validation modes, see the “Validation Modes” section in “Node Reference” chapter.
m) Acceptance threshold–Set the optical validation threshold value for the GMPLS circuit. The circuit is created if the actual optical validation result is greater than or equal to the value set in this field. For more information about the acceptance threshold value, see the “Acceptance Thresholds” section in “Node Reference” chapter.

In the GMPLS/WSON Optional Configuration pane, specify the attributes:
a) Ignore path Alarms–Check this check box to ignore the alarms on the path and create the circuit. This parameter is used to verify whether the circuit can be created on the path.
b) Allow Regeneration–Check this check box to allow the control plane to find a regenerator deployed in the network. The regenerators are used when an optical LSP between two endpoints is not optical or lambda feasible with a single channel.
c) Circuit Diversity–Select this option to provision a diversity path for the circuit. Choose a diversity condition from the Type drop down list and from the Reference drop down list, choose the circuit whose diverse circuit you want to create.

Creating Optical Channel Circuits and Provisionable Patchcords 44

Creating Optical Channel Circuits and Provisionable Patchcords

DLP-G418 Deleting an Optical Channel Trail

Step 5 Step 6
Step 7
Step 8
Step 9 Step 10
Step 11

Note

The selected reference circuit gets highlighted in the Network Functional View Map.

d) Priority–Select the priority level for the circuit. The priority is used in resolving resource allocation when two or more circuits require the same resource during circuit creation or restoration concurrently. The priority levels are 0 (High) to 7 (Low).
e) Channel Power Offset:
· Upstream (dBm)–Set the value of offset in dBm, negative or positive, which the COM_TX of the card uses on its PerChannelPower default value. Upstream applies to the card in the outgoing path of the circuit.
· Downstream (dBm)–Set the value of offset in dBm, negative or positive, which the COM_TX of the card uses on its PerChannelPower default value. Downstream applies to the card in the incoming path of the circuit.

In the GMPLS/WSON Wavelength Parameters pane, choose a wavelength from the field.
Configure the restoration parameters for the OCH trail circuit in the GMPLS/WSON Restoration Configuration pane. For more information about configuring the restoration parameters, see the “GMPLS Restoration Configuration” section in “Node Reference” chapter.
Configure the source and destination ports at the circuit endpoints in the map. For more information about configuring the source and destination ports, see the “Source and Destination Port Configuration” section in “Node Reference” chapter.. Right-click the node in the map and select the source and destination ports from the drop-down list.
Define the working or protect port parameters. For more information, see the “Working and Protect Port Parameters” section in “Node Reference” chapter. Click Apply in the Working Port Parameters pane and Protected Port Parameters pane, to apply the settings.
Click Apply in the Circuit Parameters pane.
Click Yes in the Create Circuits confirmation dialog box. The OCH trail appear in the Circuits tab in the Network Data pane. After the circuit status has been verified, the DISCOVERED status appears in the Status column. Depending on the size of the network, the circuit might take a few minutes to come up.
Return to your originating procedure (NTP).

DLP-G418 Deleting an Optical Channel Trail

Purpose

This task deletes the OCH trail circuits.

Tools/Equipment

None

Prerequisite Procedures DLP-G46 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher

Creating Optical Channel Circuits and Provisionable Patchcords 45

DLP-G418 Deleting an Optical Channel Trail

Creating Optical Channel Circuits and Provisionable Patchcords

Note If you are deleting more than half of all the active OCH trails, it is recommended 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.
Procedure

Step 1 Step 2 Step 3 Step 4 Step 5 Step 6
Step 7 Step 8

Complete the “NTP-G103 Back Up the Database” task to preserve existing settings and, if you want to recreate the circuits, record the circuit information. Consult your network operations center (NOC) or other appropriate personnel to verify that the OCH trail can be safely deleted. Investigate all network alarms and resolve any problems that might be affected by the OCH trail deletion. Go to the network view or the DWDM network functional view and click the Circuits tab. Under the Type column, choose one or more OCH trails that you want to delete, then click Delete. In the Delete Circuits confirmation dialog box, complete the following:
· Change drop port admin state–This checkbox is checked by default. Choose one of the following administrative states, if you want to change the circuit source and destination port administrative state:
· 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. This option is set by default.
· OOS,MT (ANSI) or Locked,maintenance (ETSI)–Removes the ports from service for maintenance.

· Notify when completed–Check this box if you want the CTC Alerts confirmation dialog box to notify you 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. 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.

Complete either 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 8. If you do not want to save the information, continue with Step 9.
· If you did not check Notify when completed, the Circuits page appears. Continue with Step 10.
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 10. a) Click Save.

Creating Optical Channel Circuits and Provisionable Patchcords 46

Creating Optical Channel Circuits and Provisionable Patchcords

DLP-G425 Editing an OCH Trail Circuit Name

Step 9 Step 10 Step 11

b) Click Browse and navigate to the directory where you want to save the file. c) Type the file name using a TXT file extension, and click OK.
Click Close to close the CTC Alerts dialog box. Complete the “NTP-G103 Back Up the Database” task if you require a backup of your changes. Return to your originating procedure (NTP).

DLP-G425 Editing an OCH Trail Circuit Name

Purpose

This task changes the name of an OCH trail circuit.

Tools/Equipment

None

Prerequisite Procedures DLP-G105 Provisioning Optical Channel Network Connections, on page 63 DLP-G46 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher

Procedure

Step 1 Step 2
Step 3 Step 4 Step 5 Step 6

Go to the network view, NFV view, or GMPLS view, and click the Circuits tab. To rename the OCH trail circuit, do either of the following.
· Network view–Select the OCHCC circuit in the Circuits tab and click Edit. · NFV view or GMPLS view–Double-click the circuit in the Circuits tab.
In the Edit Circuit dialog box, click the General tab. In the Name field, enter the new OCH trail circuit name. Click Apply. Return to your originating procedure (NTP).

DLP-G419 Changing an OCH Trail Administrative State

Purpose

This task changes the administrative state of an OCH trail circuit.

Tools/Equipment

None

Prerequisite Procedures DLP-G395 Creating an Optical Channel Trail, on page 41 DLP-G46 Log into CTC

Creating Optical Channel Circuits and Provisionable Patchcords 47

NTP-G59 Creating, Deleting, and Managing Optical Channel Network Connections

Creating Optical Channel Circuits and Provisionable Patchcords

Required/As Needed Onsite/Remote Security Level
Procedure

As needed Onsite or remote Provisioning or higher

Step 1 Step 2
Step 3 Step 4
Step 5 Step 6 Step 7

Go to the network view, NFV view, or GMPLS view, and click the Circuits tab. To change the administrative state of the OCH trail circuit, do either of the following.
· Network view–Select the OCHCC circuit in the Circuits tab and click Edit.
· NFV view or GMPLS view–Double-click the circuit in the Circuits tab.
In the Edit Circuit dialog box, click the State tab. Click the cell in the Admin State column for the card you want to change, and choose an administrative state from the drop-down list:
· IS,AINS (ANSI) or Unlocked,AutomaticInService (ETSI)
· OOS,DSBLD (ANSI) or Locked (ETSI)
Click Apply. If you are changing the OCH trail state to OOS/Locked, click OK in the confirmation dialog box. (No confirmation dialog box appears when you place OCH trails in service.) For information about the OCH circuit state transitions, see the Administrative and Service States document. Return to your originating procedure (NTP).

NTP-G59 Creating, Deleting, and Managing Optical Channel Network Connections

Purpose

This procedure creates and deletes DWDM OCHNC channels and changes their administrative states. The OCHNC circuits can be created using the Circuit Creation wizard or the GMPLS view.

Tools/Equipment

None

Prerequisite Procedures

· DLP-G46 Log into CTC

Required/As Needed Onsite/Remote Security Level

As needed Onsite or remote Provisioning or higher

Creating Optical Channel Circuits and Provisionable Patchcords 48

Creating Optical Channel Circuits and Provisionable Patchcords

NTP-G353 Creating GMPLS Circuits Using the Fast Circuit Mode

Procedure

Step 1
Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9

To provision an OCHNC circuit, use either of the following procedures as needed:
· DLP-G105 Provisioning Optical Channel Network Connections, on page 63
· DLP-G709 Provision GMPLS Optical Channel Network Connections, on page 65
Complete the DLP-G493 Provisioning Protected Optical Channel Network Connections, on page 66, as needed. Complete the DLP-G706 Performing Optical Validation of GMPLS Circuits, on page 37, as needed. Complete the DLP-G707 Upgrading a Non-GMPLS Circuit to a GMPLS Circuit, on page 37, as needed. Complete the DLP-G777 Upgrading a GMPLS Circuit from Legacy Signaling to LOGO Signaling, on page 38, as needed. Complete the DLP-G710 Re-route Wavelength of GMPLS Circuits, on page 73, as needed. Complete the DLP-G426 Editing an OCHNC Circuit Name, on page 69, as needed. Complete the DLP-G420 Changing an OCHNC Administrative State, on page 72, as needed. Complete the DLP-G106 Deleting Optical Channel Network Connections, on page 68, as needed.
Stop. You have completed this procedure.

NTP-G353 Creating GMPLS Circuits Using the Fast Circuit Mode

Purpose

This procedure creates a protected or unprotected GMPLS circuit between two TXP, MXP, or CRS routers using the fast circuit option in the Circuit Creation perspective of the NFV. It is also possible to create a circuit between the MSTP TXP client interface and the router PLIM interface.

Tools/Equipment

Cisco Transport Planner Traffic Matrix Report

Prerequisite Procedures DLP-G46 Log into CTC DLP-G345 Verifying OCHCC Client Ports, on page 19

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher

Procedure

Step 1

From the View menu, choose Go to Network View and click the DWDM Functional View icon in the toolbar. The DWDM network functional view opens.

Creating Optical Channel Circuits and Provisionable Patchcords 49

NTP-G353 Creating GMPLS Circuits Using the Fast Circuit Mode

Creating Optical Channel Circuits and Provisionable Patchcords

Step 2 Step 3

From the Change Perspective drop-down list in the toolbar, choose Circuit Creation. The Circuit creation view opens.
To create a unprotected circuit, perform the following steps:
a) From the Circuit Creation drop-down list, choose FastCircuit Unprotected.

The option selected is grayed out and a Cancel button appears in the toolbar. To change the selection, click Cancel and reselect an option from the Circuit Creation drop-down list.

Alternatively, you can right-click the source node and select Create New Circuit > Unprotected and proceed to Step 3c.

b) Click the source node from where the circuit must originate and then the destination node.

A blue arrow appears that connects the two nodes. On clicking the destination node, the WSON checks for the compatible interfaces on both the nodes and displays the circuit types that can be created. The invalid options are grayed out in the menu.

c) Choose the circuit type from the menu.

The GMPLS/WSON S/D selection window appears that contains the most used configuration parameters.

d) Specify a name and label for the circuit. The fields are not mandatory. A default value will be applied in case the fields are left empty.
e) Set the validation mode and acceptance threshold. For more information, see Validation Modes and Acceptance Thresholds.
f) Select the mode from the drop-down list.

This field is visible only when a Cisco CRS router is selected as the source or destination.

g) Check the Wavelength Configuration check box to configure the wavelength for the circuit.

A new panel called the “Preferred Wavelength Parameters” appears that allows the user to choose a wavelength. The wavelengths associated with the interfaces displayed in the Working Circuit panel are displayed with an asterisk in the drop-down list. If the Wavelength Configuration checkbox remains unchecked, the WSON automatically finds the best wavelength that matches the validation required.

h) Check the IS checkbox to place the trunk ports of the TXP /MXP card in service.

This field is visible only for OCHCC circuit creation.

i) Select the interfaces in the Working Circuit panel for the source and destination nodes.

Based on the circuit type, the GMPLS/WSON Optical Configuration, GMPLS/WSON Restoration Configuration, Working and Protect Port Parameters, and Alien Wavelength Selection panes are displayed on the right where additional parameters can be configured. For more information about these parameters, see GMPLS Optical Configuration Parameters, GMPLS Restoration Configuration, Working and Protect Port Parameters, Alien Wavelength Parameters. If you want WSON to compute a path using the configuration parameters specified, go to substep j, else goto substep o.

j) Click Pre-Routed.

The WSON computes the path of the circuit. When the route is found by the WSON, it is placed in DISCOVERED Preroute state and is highlighted in blue on the map. The circuit is created but placed out of service. All the configuration parameters are disabled except for the circuit action options in the GMPLS/WSON S/D selection window.

Note

You can close CTC and restart the preroute operation at a later time.

Creating Optical Channel Circuits and Provisionable Patchcords 50

Creating Optical Channel Circuits and Provisionable Patchcords

NTP-G334 Configuring GMPLS Optical Restoration

Step 4

To restart the preroute operation at a later time, go to substep k, else go to substep n.
k) Restart CTC and repeat Steps 1 and 2. l) Select the circuit in the DISCOVERED Preroute state from the Network Data pane.
The circuit is highlighted in blue on the map.
m) Click Continue PreRoute to restart the preroute operation. The GMPLS/WSON S/D selection window appears.
n) Click Accept to accept the path determined by WSON and place the circuit in service. If the path is not acceptable, modify the constraints using the right-click menu options on the nodes and spans or the W & P Constraints config drop-down list and click Refresh. The WSON recomputes the path and if the path is feasible, the WSON displays the new path. Click Accept to accept the path and place the circuit in service.
o) Click Create. All the configurations are applied to the circuit. The circuit appears in the Circuits tab in the Network Data pane.
To create a protected circuit, perform the following steps: a) From the Circuit Creation drop-down list, choose FastCircuit Protected.
The option selected is grayed out and a Cancel button appears in the toolbar. To change the selection, click Cancel and reselect an option from the Circuit Creation drop-down list. Alternatively, you can right-click the source node and select Create New Circuit > Protected and proceed to substep c.
b) Click the source node from the where the circuit must originate and then the destination node. A blue arrow with a “P” appears that connects the two nodes. On clicking the destination node, the WSON checks if both the source and destination nodes have the same type of protection model before checking for the compatibility of the interfaces. The invalid options are grayed out in the menu.
c) Choose the circuit type from the menu. The GMPLS/WSON S/D selection window appears that contains the most used configuration parameters.
d) Repeat Steps 3d through 3o to complete the circuit creation. The working and protected circuits appear in the Circuits tab in the Network Data pane.
Stop. You have completed this procedure.

NTP-G334 Configuring GMPLS Optical Restoration

Purpose

This procedure configures optical restoration for GMPLS circuits.

Tools/Equipment

None

Prerequisite Procedures DLP-G46 Log into CTC

Creating Optical Channel Circuits and Provisionable Patchcords 51

DLP-G731 Clearing WSON Alarms

Creating Optical Channel Circuits and Provisionable Patchcords

Required/As Needed Onsite/Remote Security Level
Procedure

As needed Onsite or remote Provisioning or higher

Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7

Complete the DLP-G709 Provision GMPLS Optical Channel Network Connections, on page 65 as needed. Complete the DLP-G708 Create a GMPLS Optical Channel Trail, on page 43 as needed. Complete the DLP-G732 Edit a GMPLS Circuit, on page 70 as needed. Complete the DLP-G731 Clearing WSON Alarms, on page 52 as needed. Complete the DLP-G733 Configuring GMPLS UNI, on page 53 as needed. Complete the DLP-G800 Create a Link Management Protocol (LMP) Link Using CTC , on page 57 as needed. Complete the DLP-G801 Configure Local UNI Using CTC , on page 62 as needed. Stop. You have completed this procedure.

DLP-G731 Clearing WSON Alarms

Purpose

This task clears the unverified alarms that appear in the Unverified Alarms tab at the node, network, and circuit levels.

Tools/Equipment

None

Prerequisite Procedures DLP-G46 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher

Procedure

Step 1

Clear the alarms at the node, network, or circuit levels.
Clear the alarms at the node level.
a) From the View menu, choose Go to Home View. b) Click the Maintenance > DWDM > WSON tabs to view the list of unverified alarms at the node level. c) Choose each alarm and click Acknowledge to clear the unverified alarms at the node level.
Clear the alarms at the network level.
d) Click the DWDM Functional View icon in the toolbar. The DWDM Network Functional View window opens.

Creating Optical Channel Circuits and Provisionable Patchcords 52

Creating Optical Channel Circuits and Provisionable Patchcords

VTXP Commands in Cisco CRS Documentation

Step 2

e) In the Network Data pane, click the Unverified Alarms tab to view the list of unverified alarms at the network level.
f) Choose each alarm and click Acknowledge to clear the unverified alarms at the network level.
Clear the alarms at the circuit level.
g) Click the DWDM Functional View icon in the toolbar. The DWDM Network Functional View (NFV) window opens.
h) From the Change Perspective drop-down list in the toolbar, choose the Circuit Maintenance option. i) From the Circuits tab, choose a GMPLS circuit that you want to edit. j) Click the Unverified Alarms tab to view the list of unverified alarms at the circuit level. k) Choose each alarm and click Acknowledge to clear the unverified alarms at the circuit level.
Return to your originating procedure (NTP).

VTXP Commands in Cisco CRS Documentation

The following table lists the VTXP commands and references to Cisco CRS router documentation.

Command

Where Documented

vtxp-monitor

Note

It is required to enable the VTXP

interface using the vtxp-monitor

command to discover the Cisco CRS

PLIM port in the CTC CRS panel.

See here

lmp vrf GMPLS UNI Commands

See here

DLP-G733 Configuring GMPLS UNI

Purpose

This procedure creates a static LMP link between a DWDM node and the Cisco CRS router.

Tools/Equipment

None

Prerequisite Procedures DLP-G46 Log into CTC

Required/As Needed

As needed

Onsite/Remote

Onsite or remote

Security Level

Provisioning or higher

Creating Optical Channel Circuits and Provisionable Patchcords 53

DLP-G733 Configuring GMPLS UNI

Creating Optical Channel Circuits and Provisionable Patchcords

Procedure

Step 1 Step 2 Step 3 Step 4

From the View menu, choose Go to Home View. Click the Provisioning > WDM-ANS > GMPLS/WSON > UNI tabs. Click Create. In the UNI window, provision these parameters:

From Release 10.7, the UNI tab is not available in the Provisioning > WDM-ANS -> GMPLS/WSON tab. To define or update UNI parameters, see DLP-G800 Create a Link Management Protocol (LMP) Link Using CTC , on page 57.

· Tx Port Selection–Choose the card type from the Type drop-down list; choose a shelf from the Shelf drop-down list; choose a destination slot from Slot drop-down list; choose a port from the Port drop-down list.

· Local UNI–Check this check box to configure the UNI parameters on the client port of the TXP card on the MSTP node. It is required when the user creates a hybrid VTXP circuit between the Cisco CRS router and the MSTP node using UNI.

When Local UNI is checked, the Remote System IP, Remote Interface IP, and VTXP fields are disabled in CTC.

· Remote System IP–Enter the IP address of the router.

· Remote Interface IP–Enter the IP address of the client side of the UNI, that is, the UNI-C interface.

Note

Remote/ MSTP Interface IP address must be unique inside the node and network. The

following values cannot be assigned to remote / MSTP interface IP UNI panel.

IP Address

Assigned to

000/8

IANA – Local Identification

127/8

IANA – Loopback

224/8 to 239/8

Multicast

240/8 to 255/8

–

· MSTP Interface IP–Enter the IP address of the network side of the UNI, that is, the UNI-N interface.
· Remote Communication Channel–Enter the IP address of the communication channel remote endpoint. If the IP address is not provided, the remote system IP address is used as the remote communication channel address. The remote communication channel address must be defined if the remote system IP address is not a routable address. If the remote communication channel address is not defined, the UNI client uses another address as source address for signaling messages.
· UNI State–Choose Enable or Disable from the UNI State drop-down list.
The Enable state is used to configure the UNI interface for the circuits to pass through, between the router and DWDM node. In the Disable state, the interface is configured but not active and circuit activation

Creating Optical Channel Circuits and Provisionable Patchcords 54

Creating Optical Channel Circuits and Provisionable Patchcords

DLP-G733 Configuring GMPLS UNI

Step 5 Step 6

is rejected. When the status is changed from Enable to Disable, all the active circuits on the interface are deleted.

· Description–Enter the description of the UNI interface. The description can be up to 256 characters.

· Label — Enter an alphanumeric string. This label is an unique circuit identifier.

Note

Two identical strings can coexist if the circuits do not use any single span in common.

· Validation–Set the validation mode. For more information about the validation modes, see the Validation Modes section.

· Acceptance threshold–Set the optical validation threshold value for the GMPLS circuit. The circuit is created if the actual optical validation result is greater than, or equal to, the value set in this field. For more information about the acceptance threshold value, see the Acceptance Thresholds section.

· Restoration–Check this check box to enable the restoration of the GMPLS circuits on the UNI interface.

· Revert–Check this check box to enable the revert of the GMPLS circuits on the UNI interface.

· Mode–Sets the type of revertive restoration to either UNI-C or UNI-N. This field is displayed when the Revert checkbox is checked. If the mode is set to UNI-C, the reversion of the circuit from the restored path to the original path is triggered by the UNI client that is connected, typically a Cisco CRS router. If the mode is set to UNI-N, the reversion of the circuit is triggered by the DWDM network and can be either a manual revert or an auto revert.

· Auto Revert–Click this radio button to automatically revert the circuit from the restored path to the original path after the failure is fixed, WSON alarms are acknowledged, and the soak time expires.

· Manual Revert–Click this radio button to manually revert the circuit from the restored path to the original path after the failure is fixed, the WSON alarms are acknowledged, and the soak time expires.

· Soak Time–Enter the time (in hours, minutes, and seconds) in the Soak Time field that the circuit on the restored path waits before moving to the original path after the failure is fixed. The circuit reverts to the original path after the soak time expires. The soak time must be set only if both the Restoration and Revert check boxes are checked.

Click OK to configure the UNI on a DWDM node.

Note

When the UNI is configured on a DWDM node, CTC runs the necessary CLI commands to

configure the UNI on the connected router.

Return to your originating step (NTP)

Creating Optical Channel Circuits and Provisionable Patchcords 55

Remote Transponder Shelf Node

Creating Optical Channel Circuits and Provisionable Patchcords

Remote Transponder Shelf Node
This feature remotize the transponder present in the different nodes of the optical or virtual network. The graphical representation of a Remote Transponder Nodes network is shown in the following figure:

The transponder node containing a set of transponders is physically connected to the ROADM-A node using the external PPC. The transponder node and the ROADM nodes must be on the same IP routing domain to have a control plane running on the entire network. Data that are related to TE Link Database (TED), UNI defined on ROADM and on a remote transponder node are exchanged between the ROADM and the transponder node that is attached in order to maintain an alignment of data between them. When multiple ROADM nodes are attached to the same remote transponder node, they must be part of the same OSPF area. In this case, it is assumed that the data on the two ROADM is aligned by OSPF, so only one preferred ROADM is chosen in order to get the data. The PPC represents the physical connection between transponder and ROADM node add/drop port. The LMP or UNI must be created on remote transponder and ROADM accordingly. This feature supports the following transponder cards:
· NCS2K-100G-LC-C
· NCS2K-100G-CK-C
· NCS2K-100GS-CK-C
· NCS2K-200G-CK-C
· NCS2K-400G-XP-LC with both MXP/OTNXC operating modes
Limitations · The transponder node supports all the coherent transponders (NCS2K-100G-LC-C, NCS2K-100G-CK-C, NCS2K-100GS-CK-C, NCS2K-200G-CK-C, NCS2K-400G-XP-LC with both MXP/OTNXC operating modes) and as the client card they can be combined in the known configuration with NCS2K-MR-MXP, NCS2K-10x10G-LC.
· Multiplexer/Demultiplexer cards are not part of the remote transponder node, which means that the transponders present on the remote transponder node can be connected directly to one or more ROADM nodes. ROADM node must be part of the same OSPF area.
· Regenerators are not managed on the remote transponder node.
· PSM protection is not supported.
Creating Optical Channel Circuits and Provisionable Patchcords 56

Creating Optical Channel Circuits and Provisionable Patchcords

DLP-G800 Create a Link Management Protocol (LMP) Link Using CTC

· Hybrid circuit between NCS 4000 and NCS 2000 is not supported, if the transponder is placed on a remote transponder node.

DLP-G800 Create a Link Management Protocol (LMP) Link Using CTC

Table 9: Feature History

Feature Name
ZR+ Configuration Support on NCS 2000.

Release Information Cisco NCS 2000 Release 11.12

Feature Description
The following two alien wavelengths are supported in R11.12:
· QSFP-DD-ZR
· QSFP-DD-ZR+

Purpose

Link Management Protocol (LMP) is a logical link that must be created between the DWDM node and non-DWDM node in CTC to manage a non-DWDM node. The LMP creation wizard provides the capability to select source/destination endpoints of the link, the optical parameters, and alien wavelength settings.

Tools/Equipment

None

Prerequisite Procedures

· The VTXP Monitor parameter in the Cisco CRS node must be enabled.

Required/As Needed Onsite/Remote Security Level

As needed Onsite or remote Provisioning or higher

Procedure

Step 1 Step 2 Step 3
Step 4

From the View menu, choose Go to Network View. Click the Provisioning > LMP tabs. Click Create. The LMP Creation window appears, with six options: Router Manage by CTC – Click one of the options and follow the procedure explained in Step 4. The available options are – CRS, NCS4K, Local UNI, Signaled, Remote TXP, Local TXP/OCHNC Local TXP/OCHNC: NCS 2000 node is connected with specific alien wavelength.
Choose one of the above options and a wizard appears with the following options. LMP Origination, LMP Termination, Optical Parameters, Alien Wavelength

Creating Optical Channel Circuits and Provisionable Patchcords 57

DLP-G800 Create a Link Management Protocol (LMP) Link Using CTC

Creating Optical Channel Circuits and Provisionable Patchcords

Step 5 Step 6 Step 7 Step 8 Step 9 Step 10
Step 11

Click LMP origination and for Remote TXP, user should choose an ingress port and the egress port is automatically selected. In the next step, user should choose an Add/Drop port number that is consistent with the Remote Txp ports that are chosen in the previous step. To help user to associate the Add/Drop port with the correct TXP Port, wizard shows a table with the selected TXP Ports. When user adds a new Add/Drop port, the first empty row will be populated. As last wizard’s step user could add the UNI description. If user leaves the description field as empty,no description will be configured. When user click finish, system creates the configured UNI. System will also create one or more couples of PPC between TXP and Add/Drop ports. The operation is completed when both, UNI and PPC , are successfully created. In the LMP Origination screen of the wizard, provision these parameters.
· From the Originating Node drop-down list, choose the source node of the LMP.
If the source node is Cisco CRS, NCS 4000 or local UNI, then the destination node must be MSTP and conversely.
If the source node is Remote TXP, then the destination node must be ROADM.
· From the Local Interfaces drop-down list, choose an available interface.
· Choose the Type, Shelf, Slot, and Port for Ingress Port Selection and Egress Port Selection.
· Choose Numbered or Unnumbered interface.
The interface must be Numbered for Cisco CRS node.
· Enter the IP address of the source node in the Interface IP field.
· Mode–Sets the type of revertive restoration to either UNI-C or UNI-N. If the mode is set to UNI-C, the reversion of the circuit from the restored path to the original path is triggered by the UNI client that is connected, to a Cisco CRS router or an NCS 4000 router. If the mode is set to UNI-N, the reversion of the circuit is triggered by the DWDM network, and can be either a manual revert or an auto revert.
The Local UNI check box is checked by default and is read-only when you choose the Local UNI option in the LMP Creation window. The Local UNI check box is not visible when you choose CRS or Signaled in the LMP Creation window.
· Enter the RSVP signaling interval and RSVP signaling missed values in the respective fields.
When LMP link is created, the RSVP values are configured in the Cisco CRS node.
· Click the Include or Exclude button to add or remove a carrier. This option is available only when you choose the Signaled or No Signaled/ OCHNC option in the LMP Creation window.
· Click Next.
In the LMP Termination screen of the wizard, provision these parameters.
The LMP Termination pane is not applicable when you choose No Signaled in the LMP Creation window.
· From the Terminating Node drop-down list, choose the destination node of the LMP, for example, MSTP node.

Creating Optical Channel Circuits and Provisionable Patchcords 58

Creating Optical Channel Circuits and Provisionable Patchcords

DLP-G800 Create a Link Management Protocol (LMP) Link Using CTC

Step 12

· Rx Port Selection–Choose the card type from the Type drop-down list; choose a shelf from the Shelf drop-down list; choose a source slot from Slot drop-down list; choose a port from the Port drop-down list.
· Tx Port Selection–Choose the card type from the Type drop-down list; choose a shelf from the Shelf drop-down list; choose a destination slot from Slot drop-down list; choose a port from the Port drop-down list.
· Enter the IP address of the destination node in the Interface IP field.
· Mode–Sets the type of revertive restoration to either UNI-C or UNI-N. If the mode is set to UNI-C, the reversion of the circuit from the restored path to the original path is triggered by the UNI client that is connected, typically a Cisco CRS router. If the mode is set to UNI-N, the reversion of the circuit is triggered by the DWDM network, and can be either a manual revert or an auto revert.
· (Only for NCS 1002) Enter the remote Ifindex of NCS 1002 node (in decimals) in the Remote If Index field.
· Click Next.

In the Optical Parameters screen of the wizard, provision these parameters.

Note

If Remote TXP is chosen in the LMP wizard, only the Description parameter must be provisioned

under Optical Parameters.

· Allow Regeneration–When checked, the computed path traverses through the regeneration site only if the optical validation is not satisfied. The user can regenerate a circuit that is created from UNI interface or VTXP. If a transparent path is feasible, the regenerator will not be used.
· UNI State–Choose Enable or Disable from the UNI State drop-down list.
The Enable state is used to configure the UNI interface for the circuits to pass through, between the router and DWDM node. In the Disable state, the interface is configured but not active and circuit activation is rejected. When the status is changed from Enable to Disable, all the active circuits on the interface are deleted.
· Description–Enter the description of the UNI interface. The description can be up to 256 characters.
This is the only field that is displayed when you choose No Signaled in the LMP Creation window.
· Label–Enter an alphanumeric string. This label is a unique circuit identifier.
· Validation–Sets the optical validation mode. For more information about the validation modes, see the “Validation Modes” section.
· Acceptance threshold–Sets the acceptance threshold value for the GMPLS circuit. The circuit is created if the actual acceptance threshold value is greater than, or equal to, the value set in this field. For more information about the acceptance threshold value, see the “Acceptance Thresholds” section.
· Restoration–Check this check box to enable the restoration of the GMPLS circuits on the UNI interface.
· Revert–Check this check box to enable the revert of the GMPLS circuits on the UNI interface.
· Auto Revert–Click this radio button to automatically revert the circuit from the restored path to the original path after the failure is fixed, WSON alarms are acknowledged, and the soak time expires.
· Manual Revert–Click this radio button to manually revert the circuit from the restored path to the original path after the failure is fixed, the WSON alarms are acknowledged, and the soak time expires.

Creating Optical Channel Circuits and Provisionable Patchcords 59

Modify an LMP Link Using CTC

Creating Optical Channel Circuits and Provisionable Patchcords

Step 13 Step 14

In the Alien wavelength screen of the wizard, provision these parameters.

Note

For Remote TXP, there is no need to provision the alien wavelength parameter as the alien

wavelength will be retrieved from the TXP and then propagated to the passive port on ROADM

node.

· From the Alien Wavelength drop-down list, choose the alien wavelength class.

Note

The following alien profiles are supported in R11.12:

· QSFP-DD-ZR

· QSFP-DD-ZR+

· For NCS 1004, from the Trunk Selection drop-down list, choose – 200G/2bps, 200G/2.3125bps, 300G/3.4375bps, or 400G/4.4375bps.

Note

Alien Wavelength class is supported only for SSON package for Media Channel (MCH)

circuit creation.

For NCS 1002, the different trunk modes are 100G, 200G and 250G.

· From the FEC drop-down list, choose a valid value for Forward Error Correction (FEC) mode depending on the card. If an invalid FEC value is chosen, LMP link is created. However, circuit creation fails.

Note

For NCS 1004, the 200G Trunk Selection is supported with 27% Soft Decision FEC DE

OFF only.

· From the TXP Control Mode drop-down list, choose a valid value for Control Mode Selection depending on the card.
For NCS 1004, from the TXP Control Mode drop-down list, choose GMPLS.
· Click Finish to create an LMP link. The newly created LMP link appears in the LMP table.

Return to your originating procedure (NTP).

Modify an LMP Link Using CTC

Purpose

This task enables you to edit or delete LMP links

Documents / Resources

Cisco ONS 15454 Series Multiservice Transport Platforms [pdf] User Guide
ONS 15454 Series Multiservice Transport Platforms, ONS 15454 Series, Multiservice Transport Platforms, Transport Platforms, Platforms

References

User Manual

Cisco ONS 15454 Series Multiservice Transport Platforms User Guide

Cisco ONS 15454 Series Multiservice Transport Platforms

Product Information

OCHNC Circuits

Product Usage Instructions

Frequently Asked Questions (FAQ)

Optical Channel Circuits

Purpose

Prerequisite Procedures

Documents / Resources

References

Leave a comment

Cancel reply