Setting Up TL1 Communication

The period during which a user is logged into the ONS 15454 SDH or ONS 15600 SDH is called a session. There are three options you can use to open a session (log in):

Cisco Transport Controller (CTC)

Telnet

Craft interface

The TL1 password (PID) is masked when accessing a TL1 session using any of these options. When you log out of any of these options, you are closing a session. The ONS 15454 SDH allows a maximum of 20 concurrent TL1 sessions (19 Telnet sessions and one craft session) using any one or any combination of the options listed above. The ONS 15600 SDH supports a maximum of 20 (18 Telnet sessions and two craft sessions) concurrent TL1 sessions on the customer access panel (CAP). For information on issuing commands to multiple nodes, see the TL1 Gateway.

Use the following procedures to open a TL1 session through the CTC, Telnet, or craft interface. In the procedures, the Activate and Cancel User commands are shown in their input format. For more detailed command information about these and other commands and messages, refer to the Cisco ONS 15454 SDH and Cisco ONS 15600 SDH TL1 Command Guide.

Open a TL1 Session Through CTC

Step 1: From the PC connected to the ONS 15454 SDH or the ONS 15600 SDH, start Netscape or Internet Explorer.

Step 2: Enter the IP address of the node that you want to communicate with in the Netscape or Internet Explorer Web address (URL) field.

Step 3: Log into CTC. The IP address at the title bar should match the IP address of the node you entered in Step 2.

Step 4: When you have logged into CTC, there are two ways to open a TL1 session:

Click Tools > Open TL1 Connection.

Click the Open TL1 Connection button on the toolbar.

Step 5: From the Select Node dialog box, choose the node that you want to communicate with.

Step 6: Click OK.

A TL1 interface window appears. There are three subwindows in the TL1 interface window: Request History, Message Log/Summary Log, and TL1 request. Type commands in the TL1 request window. You will see responses in the Message log window. The Request History window allows you to recall previous commands by double-clicking on them.

Step 7: Verify that the Connect button is selected (grayed out).

Step 8: Type the Activate User command in the TL1 request window and press Enter to open a TL1 session:

ACT-USER:[<TID>]:<UID>:<CTAG>::<PID>;

Note: You must press Enter after the semicolon in each TL1 command, or the command will not be issued.

Step 9: Type the Cancel User command in the TL1 request window and press Enter to close a TL1 session:

CANC-USER:[<TID>]:<USERID>:<CTAG>;

Alternatively, press the Disconnect button to close the session.

Open a TL1 Session Through Telnet

To communicate with the ONS network element (NE) using TL1 commands through a Telnet session over a craft interface or a LAN connection, you can choose from two ports:

Port number 3083 is a Telnet port that uses the Telnet protocol and associated Telnet escape sequences.

Port number 2361 is supported for backward compatibility with earlier releases and has the same behavior as Port 3083 (Telnet port). Use the following procedure with PCs running Windows operating systems.

Note: Port number 3082 is a raw TCP/IP port; it is not an interactive port and is not recommended for use as an alternate telnet port.

Step 1: At the DOS prompt, type cmd and press Enter. (The same steps can also be done from a UNIX prompt).

Step 2: At the DOS command prompt type:

Telnet <Node IP Address or Node Name> <Port Number> and press Enter.

The Node IP Address or Node Name refers to the IP address or node name of the node you want to communicate with. Port Number is the port (2361 or 3083) where TL1 commands are understood. If the connection is successful, a screen appears with a prompt.

Step 3: Type the Activate User command to open a TL1 session:

ACT-USER:[<TID>]:<UID>:<CTAG>::<PID>;

Note: When the semicolon is typed, the command is issued immediately.

Step 4: Type the Cancel User command to close a TL1 session:

CANC-USER:[<TID>]:<USERID>:<CTAG>;

Open a TL1 Session Through Craft Interface (Cisco ONS 15454 SDH)

The TCC2/TCC2P card has two built-in interface ports for accessing the ONS 15454 SDH. With one RJ-45 LAN connection you can access the system using a standard browser interface. In the browser interface, you can perform local and remote Operations, Administration, Maintenance, and Provisioning (OAM&P) functions and open a VT100 emulation window to enter TL1 commands. If a browser is not available, you can access the system using a nine-pin EIA/TIA-232 port. The EIA/TIA-232 port supports VT100 emulation, which allows TL1 commands to be entered directly without a browser. For instructions for installing the TL1 craft interface, refer to the Cisco ONS 15454 SDH Procedure Guide or theCisco ONS 15600 SDH Procedure Guide.

Step 1: Connect the serial cable to the EIA/TIA-232 port on the active TCC2/TCC2P card.

Step 4: At the > prompt, type the Activate User command to open a TL1 session:

ACT-USER:[<TID>]:<UID>:<CTAG>::<PID>;

Note: When the semicolon is typed, the TL1 command is issued immediately.

Step 5: Type the Cancel User command to close a TL1 session:

CANC-USER:[<TID>]:<USERID>:<CTAG>;

Open a TL1 Session Through Craft Interface (Cisco ONS 15600 SDH)

The TSC card has one RJ-45 port of the faceplate. The RJ-45 port allows you to access the system using a standard web browser. You must use the RJ-45 port on the active TSC. While using the web browser, you can perform local and remote OAM&P functions.

If a browser is not available, you can access the system using one of the two EIA/TIA-232 ports on the CAP. Each EIA/TIA-232 port supports VT100 emulation so that you can enter TL1 commands directly without using a web browser. Each EIA/TIA-232 port supports its own TL1 session.

Because the CAP EIA/TIA-232 port is set up as a data terminal equipment (DTE) interface, you must use a 3-pair swapping null modem adapter so that the TXD/RXC, DSR/DTR, and CTS/RTS pins are swapped when connecting to the serial ports. The null modem adapter connects the CAP EIA/TIA-232 port (male configuration) and the serial cable (female configuration). Table 2-1 lists the null modem adapter pin assignments.

Table 2-1: Null Modem Adapter Pin Assignments

TSC Signal

From Pin at TSC (DTE)

To Pin at Second DTE

NC1

1

NC

RXD

2

3

TXD

3

2

DTR

4

6

GND

5

5

DSR

6

4

RTS

7

8

CTS

8

7

NC

9

NC

1. NC = not connected

Step 1: Attach a 3-pair swapping null modem adapter to the EIA/TIA-232 port on the CAP.

Step 2: Connect a serial cable to the null modem adapter, and to the serial port on your PC or workstation.

Step 3: Complete one of the following:

If you are using a PC, configure the terminal emulation software (HyperTerminal):

Terminal emulation = vt100

Bits per second = 9600

Parity = None

Stop BITS = 1

Flow control = None

If you are using a UNIX workstation, connect from X Windows or the terminal using the tip command:

tip -9600 /dev/ttyb

Note: You might need to use ttya instead of ttyb, depending on where serial cable is connected.

Step 4: Press Enter. A > prompt appears.

Step 5: At the > prompt, type the Activate User command to open a TL1 session:

ACT-USER:[<TID>]:<UID>:<CTAG>::<PID>;

Note: When the semicolon is typed, the TL1 command is executed immediately.

Step 6: Type the Cancel User command to close a TL1 session:

CANC-USER:[<TID>]:<USERID>:<CTAG>;

Test Access

The test access (TACC) feature allows a third-party Broadband Remote Test Unit (BRTU) to create nonintrusive test access points (TAPs) to monitor the circuits on the ONS 15454 SDH or ONS 15600 SDH for errors. The test access feature also allows the circuit to be split (intrusive), so that the transmission paths can be tested for bit errors through the use of various bit test patterns. The two BRTUs supported by the ONS 15454 SDH are the Hekimian/Spirent BRTU-93 (6750) and the TTC/Acterna Centest 650.

The test access functionality provides TL1 commands for creating and deleting TAPs, connecting or disconnecting TAPs to circuit cross-connects and changing the mode of test access on the ONS 15454 SDH and ONS 15600 SDH. You can view test access information in CTC; in node view click the Maintenance > Test Access tabs.

A TAP provides the capability to connect the circuit under test to a BRTU. This connection initially provides in-service monitoring capability to permit the tester to determine that the circuit under test is idle. The monitor connection should not disturb the circuit under test. The access point and remote test unit (RTU) also provide the capability of splitting a circuit under test. A split consists of breaking the transmission path of the circuit under test. This is done out of service. The two sides of the access point are called the Equipment (E) and Facility (F) directions. For a 4-wire or 6-wire circuit, the transmission pairs within the access point are defined as the A and B pairs. The circuit under test should be wired into the access point so the direction of transmission on the A pair is from E to F, and the transmission direction for the B pair is from F to E (Figure 2-1).

Figure 2-1: Circuit With No Access Dual FAD TAP

A dual facility access digroup (FAD) TAP uses twice the bandwidth of the circuit under test. This can be specified by the TAPTYPE parameter as shown in ED-<MOD2> command syntax in the TAP Creation and Deletion. The values are SINGLE and DUAL. It defaults to DUAL.

A single FAD TAP uses half the bandwidth as that of the dual FAD, for example, it will use the same bandwidth as the circuit accessed for the TAP creation. This can be specified by the TAPTYPE parameter as shown in the TAP Creation and Deletion. The values are SINGLE and DUAL. The MONEF, SPLTEF, and LOOPEF modes are not supported by single FAD TAPs (Figure 2-2).

Edit an existing port/VC and change it to a TAP so it can be used when requesting TACC connections. This includes an optional parameter TACC=n that defines the port/VC as a test access point with a selected unique TAP number. This TAP number will be used when requesting test access connections to circuit cross-connects under test. The TAP creation will fail if the port/VC already has a cross-connect on it.

The TAPTYPE parameter values are SINGLE and DUAL. The MONEF, SPLTEF, and LOOPEF modes are not supported by single FAD TAPs. It defaults to DUAL.

Notes:

This command generates a REPT DBCHG message.

The alarms and conditions on TACC paths can be retrieved by the RTRV-ALM-ALL or RTRV-ALM-<MOD2> commands.

The TAP is a persistent object; it will exist even after the user has logged out of the TL1 session.

The following rules apply to TAP numbers:

A TAP number is an integer in the range of 1 to 999. When TACC=0 is specified, the TAP is deleted (if already present).

A TAP number is unique across E1, E3, DS3I, VC12, VC3, VC4, VC42C, VC43C, VC44C, VC48C, VC416C, and VC464C TAPs in the system.

A TAP number is not editable.

ED-E1

When an ED-E1 command is executed with a specified TACC value for a given E1 port/facility, a dual facility access digroup (DFAD) is created by using the specified port/facility and the consecutive port/facility.

Example 2-2: Create an E3 DFAD on FAC-2-1 and FAC-2-2

ED-E3:: FAC-2-1:12:::TACC=2; DV9-99 1970-01-02 03:16:11 M 12 COMPLD ;

Note: These ports/facilities cannot be used for the creation of cross-connections until the TAP is deleted.

ED-DS3I

The ED-DS3I command is used for DS3 access on a DS3i card. When an ED-DS3I is executed with a specified TACC value for a given DS3i card, a DFAD is created by using the specified facility and the consecutive port/facility.

Example 2-3: Create a DFAD on FAC-16-1 and FAC-16-1

Note: These ports/facilities cannot be used for the creation of cross-connections until the TAP is deleted.

ED-VC4n

When an ED-VC4n is executed for a TACC, it assigns the VC path for the first two-way test access connection and VC+1 as the second two-way connection. Similarly, for VC42c, VC43c, VC44c, VC48c, VC416c, the next consecutive VC of the same width is chosen. The TAP creation will fail if either of the consecutive VC's are not available.

Example 2-5: Create a VC48C Dual TAP on VC4-6-1-1 and VC4-6-1-25.

Note: These VC paths cannot be used for creation of cross-connects until the TAP is deleted.

ED-VC12

When an ED-VC12 is executed for a TACC, a VC12 TAP is created. The specified VC12 access identifier (AID) is taken as the first VC12 connection, and the consecutive VC12 connection is used as the second path for the TAP.

The command in Example 2-6 creates a VC12 TAP on VC12-1-1-1-1-1 and VC12-1-1-1-2-1.

Connect the port/VC4n/VC3 defined by <AID> to the port/VC4n/VC3 defined by the <TAP> number. The mode of test access to the circuit/cross-connect is specified by <MD>. The modes can be either of Monitor (nonintrusive), Split, or Loop (intrusive) modes. The various modes are described in the Test Access Mode Definitions.

Note: The connection is maintained only for the duration of the TL1 session (nonpersistent).

Note: The TAP number is displayed at the output if the CONN-TACC command completes successfully.

The following error codes are supported:

RTBY-Requested TAP busy

RTEN-Requested TAP does not exist

SCAT-Circuit is already connected to another TAP

SRCN-Requested condition already exists

IIAC-Invalid access identifier (AID)

EANS-Access not supported

SRAC-Requested access configuration is invalid

The command in Example 2-8 creates a connection between TAP number one and the port/facility FAC-1-3 with the access mode defined as MONE. The various modes are described in the Test Access Mode Definitions.

Use this command to change the type of test access. This might be a change from monitoring the data to inserting data into the VC. This command can only be applied to an existing TAP connection. If a TAP connection does not exist, a RTEN error is returned.

This command is modified to include the return of a TAP number if the requested <AID> is defined as a TAP. An optional TACC=<TAPNUMBER> will appear in the output list if the requested <AID> is defined as a TAP. The example in Example 2-10 retrieves TAP information for FAC-1-1.

This command changes VC4-1 and VC4-2 on Slot 1 to a TAP. The CTAG is 90. It sets the TACC number to 1.

Step 2: CONN-TACC-VC4::<AID for E or F depending on MD>:91::1:MONE

This command connects the <AID> to the TACC defined by TAP 1 on the E side. The CTAG is 91.

Note: The connection made in the CONN-TACC command can use MONE to connect to the F side AID. The AID provided designates the E side and the other automatically becomes the F side. For example, if an <AID F> is supplied to a MONE connection, then the top line would be connected to the other side of the path, or what is shown in Figure 2-3 as the F side. When a CONN-TACC is set up, these designations cannot change until a DISC-TACC or another CONN-TACC command is executed. The connection is based on the AID supplied.

Figure 2-3: Single Node View (Node 1)

In the Figure 2-4 configuration, there might be a single DS-3 port wired up, configured as 14 dual FADs (28 VTs).

Figure 2-4: Multi-Node View (MONE Example)

The following commands are performed on NE3:

ENT-CRS-VC4::<AID I-G>:100::2WAY;

A connection, not a TAP. CTAG is 100.

ENT-CRS-VC4::<AID J-H>:101::2WAY;

Second connection, not a TAP.

The following commands are performed on NE1:

Assuming the path from A to B is already entered, the A and B points in Figure 2-4 refer to entry and exit points on the node or different cards. The E/F designators refer to the two two-way connections from NE3.

The following command creates a TAP with VC4-1-1-1 and VC4-1-1-2 through NE1. TAP number assigned is 4.

Test Access Mode Definitions

The following diagrams show what the different test access modes (<MD>) refer to. Figure 2-5 shows a circuit with no access (dual FAD TAP) and Figure 2-6 shows a circuit with no access (single FAD TAP). The subsections that follow show the circuits in each test access mode. The QRS can be generated by an outside source, for example, the empty connection of the BRTU.

The subsections that follow describe the modes:

MONE, MONF, and MONEF access modes are non-service effecting and can be applied to a locked (in service) port state.

LOOPE, LOOPF, SPLTE, SPLTF, SPLTEF, SPLTA, SPLTB, and SPLTAB access modes are intrusive and can only be applied to a circuit/port that is in the Unlocked_Maintenance port state. The NE will change the state of the circuit under test to Unlocked_Maintenance during the period of TACC and restore it to the original state when the connection between the TAP and the circuit is dropped.

Figure 2-5: Circuit With No Access (Dual FAD TAP)

Figure 2-6: Circuit With No Access (Single FAD TAP)

MONE

Monitor E (MONE) mode indicates a monitor connection provided from the facility access digroup (FAD) to the A transmission path of the accessed circuit (Figure 2-7 and Figure 2-8). This is a nonintrusive mode.

Figure 2-7: MONE Access Mode Single TAP

Figure 2-8: MONE Access Mode Dual TAP

MONF

Monitor F (MONF) mode indicates that the FAD is providing a monitor connection to the B transmission path of the accessed circuit (Figure 2-9 and Figure 2-10). This is a nonintrusive mode.

Figure 2-9: MONF Access Mode Single TAP

Figure 2-10: MONF Access Mode Dual TAP

Note: The MONE and SPLTA modes are applicable to unidirectional circuits from E to F. The MONF and SPLTB modes are applicable to unidirectional circuits from F to E.

MONEF

Monitor EF (MONEF) mode is a monitor connection provided from the FAD1 (odd pair) of a DFAD, to the A transmission path, and from FAD2 (even pair) of the same DFAD, to the B transmission path of the accessed circuit. This is a nonintrusive mode (Figure 2-11).

MONEF for T3 (DS3 HCDS) indicates that the odd pair of a facility access path (FAP) is providing a monitor connection to the A transmission path and from that the even pair of an FAP to the B transmission path of the accessed circuit.

Figure 2-11: MONEF Access Mode Dual TAP

SPLTE

Split E (SPLTE) mode splits both the A and B paths and connects the E side of the accessed circuit to the FAD (Figure 2-12 and Figure 2-13).

Note: QRS is not supported. The connection will remain as-is.

Figure 2-12: SPLTE Access Mode Single TAP

Figure 2-13: SPLTE Access Mode Dual TAP

SPLTF

Split F (SPLTF) mode splits both the A and B paths and connects the F side of the accessed circuit to the FAD (Figure 2-14 and Figure 2-15).

Note: QRS is not supported. The connection will remain as-is.

Figure 2-14: SPLTF Access Mode Single TAP

Figure 2-15: SPLTF Access Mode Dual TAP

SPLTEF

Split EF (SPLTEF) mode for T1 (DS1 HCDS) splits both the A and B paths, connects the E side of the accessed circuit to FAD1 and the DFAD pair, and connects the F side to the FAD2 of the same DFAD pair (Figure 2-16).

SPLTEF for T3 (DS3 HCDS) indicates to split both the A and B paths and connect the E side of the accessed circuit to the odd pair of the FAP and the F side to the even pair of the FAP.

Figure 2-16: SPLTEF Access Mode Dual TAP

LOOPE

Loop E (LOOPE) mode splits both the A and B paths, connects the incoming line from the E direction to the outgoing line in the E direction, and connects this looped configuration to the FAD (Figure 2-17 and Figure 2-18). Loop E and F modes are basically identical to the SPLT E and F modes except that the outgoing signal is the incoming signal and not the signal from the remote test unit (RTU).

Note: QRS is not supported. The connection will remain as-is.

Figure 2-17: LOOPE Access Mode Single TAP

Figure 2-18: LOOPE Access Mode Dual TAP

LOOPF

Loop F (LOOPF) mode splits both the A and B paths, connects the incoming line from the F direction to the outgoing line in the F direction and connect this looped configuration to the FAD (Figure 2-19 and Figure 2-20).

Note: QRS is not supported. The connection will remain as-is.

Figure 2-19: LOOPF Access Mode Single TAP

Figure 2-20: LOOPF Access Mode Dual TAP

SPLTA

Split A (SPLTA) mode indicates that a connection is provided from both the E and F sides of the A transmission path of the circuit under test to the FAD and splits the A transmission path (Figure 2-21 and Figure 2-22). These modes are similar to the SPLTE and SPLTF modes, except the signals are sent to the RTU, not the NE signal configuration.

Figure 2-21: SPLTA Access Mode Single TAP

Figure 2-22: SPLTA Access Mode Dual TAP

SPLTB

Split B (SPLTB) mode indicates that a connection is provided from both the E and F sides of the B transmission path of the circuit under test to the FAD and splits the B transmission path (Figure 2-23 and Figure 2-24).

Figure 2-23: SPLTB Access Mode Single TAP

Figure 2-24: SPLTB Access Mode Dual TAP

Unmapped AID Test Access Point Connections

The Cisco ONS 15454 SDH and ONS 15600 SDH support connections to unmapped AIDs (unmapped circuits). The TAPs can be connected to an unmapped AID, for example, an AID that does not have a cross-connect on it. The access modes supported are: MONE, SPLTE, and LOOPE.

Note: VC4-5-1-3 does not have a cross-connect on it. VC4-5-1-3 becomes unusable until the connection is disconnected by the DISC-TACC command.

Note: The AID provided in the CONN-TACC command designates the E side and the other automatically becomes the F side.

Note: In the case of all one-way circuits (1-way, SNCP_HEAD, SNCP_DROP, SNCP_DC, SNCP_EN), if the AID specified is the source AID, the direction is designated as From E in Table 2-3. If the AID specified is the destination AID or the drop side, the direction is designated as From F in Table 2-3.

One-Way Circuit

The examples in this section assume that a VC TAP is already created with a TAP number of 1.

The AID specified in the above CONN-TACC command is the source AID for the one-way circuit. In this case, only MONE and SPLTA modes are allowed because there is no B path in the case of a one-way circuit (see Table 2-3).

The same examples apply for SNCP_HEAD, SNCP_DROP, SNCP_DC, and SNCP_EN, which are all one-way circuits.

The connections are made only to the working path, irrespective of which path is currently active.

Two-Way Circuits

For two-way circuits, all the modes are allowed as shown in Table 2-3. The same applies for SNCP_SNCP and SNCP circuit types. In the case of SNCP_SNCP and SNCP circuits, the working path is connected irrespective of which path is currently active.

Unmapped AID

Note: The AID provided in the CONN-TACC command designates the E side and the other automatically becomes the F side.

Table 2-3: Modes Supported by Circuit Type

Circuit Type (Direction)

MONE

MONF

MONEF

SPLTE

SPLTF

SPLTEF

LOOPE

LOOPF

SPLTA

SPLTB

One-way (from E1)

X

-

-

-

-

-

-

-

X

-

One-way (from F2)

-

X

-

-

-

-

-

-

-

X

Two-way

X

X

X

X

X

X

X

X

X

X

SNCP

X

X

X

X

X

X

X

X

X

X

SNCP_HEAD (from E)

X

-

-

-

-

-

-

-

X

-

SNCP_HEAD (from F)

-

X

-

-

-

-

-

-

-

X

SNCP_DROP SNCP_DC SNCP_EN (from E)

X

-

-

-

-

-

-

-

X

-

SNCP_DROP SNCP_DC SNCP_EN (from F)

-

X

-

-

-

-

-

-

-

X

SNCP_SNCP

X

X

X

X

X

X

X

X

X

X

Unmapped AID

X

-

-

X

-

-

X

-

-

-

1. In the case of all one-way circuits (1-way, SNCP_HEAD, SNCP_DROP, SNCP_DC, and SNCP_EN), if the AID specified is the source AID, the direction is designated as “from E” in this table.

2. In the case of all one-way circuits (1-way, SNCP_HEAD, SNCP_DROP, SNCP_DC, and SNCP_EN), if the AID specified is the destination AID or the drop side, the direction is designated as “from F” in this table.

TL1 Gateway

This section describes the TL1 gateway and provides procedures and examples for implementing TL1 gateway on the ONS 15454 SDH and ONS 15600 SDH.

Gateway Network Element Topology

You can issue TL1 commands to multiple nodes through a single connection through the TL1 gateway. Any node can serve as a Gateway Network Element (GNE), End Network Element (ENE), or Intermediate Network Element (INE). A node becomes a GNE when a TL1 user connects to it and enters a command destined for another node. An ENE is an end node because it processes a TL1 command that is passed to it from another node. An INE is an intermediate node because of topology; it has no special hardware, software, or provisioning.

To implement the TL1 gateway, use the desired ENE's TID in the ACT-USER command to initiate a session between the GNE and the ENE. After a session is established, you must enter the ENE's TID in all subsequent commands that are destined for the ENE. From the GNE, you can access several remote nodes, which become the ENEs. The ENEs are the message destinations or origins. The INE handles the data communications channel (DCC) TCP/IP packet exchange.

The GNE session is the connection that multiplexes TL1 messages between the operation support system (OSS)/craftsperson and the GNE. The GNE demulitplexes incoming OSS TL1 commands and forwards them to the remote ENE. The GNE also multiplexes incoming responses and autonomous messages to the GNE session. The ENE session is the connection that exchanges messages between the GNE and the remote ENE. Figure 2-25 shows the GNE topology.

Figure 2-25: Example of a GNE Topology

ONS 15454 SDH Gateway

With the TCC2/TCC2P card on an ONS 15454 SDH, each GNE can support eleven (10+1) concurrent gateway communication sessions (connections from an OS to the GNE). Ten of these sessions are through the LAN (wire-wrap, active TCC2/TCC2P LAN port, or DCC) and the eleventh session is reserved for the active TCC2/TCC2P serial port.

Each GNE can support 11 concurrent communication gateway sessions and up to a maximum of 176 ENEs/GNE. You can dynamically distribute the ENEs to balance the number of concurrent gateway communication sessions versus the number of NEs on the DCC. The GNE treats the 11 (10+1) concurrent gateway communication sessions and 176 ENE/GNE limit as a resource pool (Table 2-4) and continues to allocate resources until the pool is exhausted (see Table 2-5 for allocation examples). When the pool is exhausted, the GNE returns an "All Gateways in Use" message or an "All ENE Connections in Use" message.

ONS 15600 Gateway

Each GNE can support eleven (9+2) concurrent gateway communication sessions (connections from an OS to the GNE), available through the LAN (CAP, TSC, or DCC). The GNE can support 9 Telnet sessions and 2 serial port sessions. The gateway resource pools for each platform are shown in Table 2-4. Examples of GNE/ENE resource alocation are provided in Table 2-5.

Note: To issue commands to specific nodes in the network, enter a unique node name in the TID field in each TL1 message. The TID field is synonymous with the name of the node and is the second token in a TL1 command.

Note: Issuing commands to specific nodes in the network is accomplished by entering a unique node name in the TID field in each TL1 message. The TID field is synonymous with the name of the node and is the second token in a TL1 command.

Implementing TL1 Gateway

The following procedures demonstrate TL1 gateway on a four-node ring (without TL1 gateway in Figure 2-26 and with TL1 gateway in Figure 2-27), where:

Node 0 is the GNE.

Node 1 is the ENE 1.

Node 2 is the INE 2.

Node 3 is the ENE 3.

Figure 2-26: Four-Node Ring Without TL1 Gateway

Figure 2-27: Four-Node Ring With TL1 Gateway

Log Into a Remote ENE

Step 1: Telnet or connect through the serial port to Node 0, which will become the GNE.

Step 2: To connect to the ENE 1 node, enter the TL1 login command using the following input example:

Step 3: When you are logged into ENE 1, enter the following TL1 login command to connect to ENE 3:

ACT-USER:NODE3:<USERNAME>:1234:<PASSWORD>;

The GNE forwards the login to ENE 3. After successful login, the ENE 3 sends a COMPLD response.

Forward Commands by Specifying the ENE TID (Node 1 or Node 3)

To forward commands when you are logged into ENE 1 and ENE 3, enter a command and designate a specific TID, as shown in the following examples.

Enter the following command to retrieve the header of Node 1:

RTRV-HDR:NODE1::1;

Enter the following command to retrieve the header of Node 3:

RTRV-HDR:NODE3::3;

Receive Autonomous Messages from the Remote ENE

To receive autonomous messages from the remote ENE, you must log into the remote ENE. When you are logged in, you will begin to receive autonomous messages. The source of the message is identified in the header of the message.

Log Out of a Remote ENE

To disconnect from a remote ENE, you must use the CANC-USER command. To disconnect ENE1, enter the following command:

CANC-USER:NODE1:<USERNAME>:1;

To disconnect ENE2, enter the following command:

CANC-USER:NODE3:<USERNAME>:3;

The GNE forwards the logout to the remote ENEs. The GNE/ENE TCP session is closed.

In Sections 2.4.4 through 2.4.10, the form "5/1/1" (for example) represents "Slot 5, Port 1, VC 1." For VCs, add the normal VC Group and VC ID extensions. These examples also assume that the slots/ports have been autoprovisioned (through a plug-in event) and that the ports involved have been placed into the in-service (IS) state using a port configuration command, for example, ED-STMn.

SNCP Topology

No special configuration of the physical SNCP topology is required other than connecting the fibers to the desired ports on the desired nodes. The east and west paths must exit a node at different ports (to ensure link diversity), but there are no other physical topology restrictions.

ONS 15454 SDH and ONS 15600 SDH networks give you the option to set up path-protected mesh networks (PPMNs). PPMNs extend the protection scheme of an SNCP from the basic ring configuration to the meshed architecture of several interconnected rings. For more information about PPMN, refer to the Cisco ONS 15454 SDH Procedure Guideor 'Cisco ONS 15600 SDH Procedure Guide.

SNCP Cross-Connections

To create an SNCP cross-connection using TL1, you only need to designate it as a one-way or two-way cross-connect. The AID must be more explicit. For example, to create a one-way SNCP circuit over the network with Nodes A, B, C, and D and Segments A-B, B-D, A-C, C-D (as shown in Figure 2-28), enter the following commands (Node A is the source node and Node D is the destination node):

Figure 2-28: Network Configured With a One-Way SNCP Circuit

Ring-to-Ring Interconnection

In this section, both rings traverse the same node; therefore, only a single cross-connection is required to create the ring-to-ring connection. This is shown in Figure 2-29. The node named "Cisco" is in the nexus.

Figure 2-31: Selector Between 5/1/1 and 6/1/1

The command also creates a selector between 12/3/2 and 13/3/2 to a bridge to Ring 1 (5/1/1 and 6/1/1), as shown in Figure 2-32.

Figure 2-32: Selector Between 12/3/2 and 13/3/2

SNCP to Two-Fiber MS-SPRing Connection Example

This example, illustrated in Figure 2-33, uses a SNCP endpoint with a drop on a two-fiber MS-SPRing and the west span of the two-fiber MS-SPRing (Ring 2) for the active path of the circuit. The example also uses multiport addressing for Ring 2 and is based on a multiport STM-4 card, where 13/3/2 = VC-13-26 and where 26 = (((3 - 1) * 12) + 2). (This is only important for computing the VC AID for multiport cards.)

Figure 2-33: SNCP to Two-Fiber MS-SPRing

Use the following command to create a selector between 5/1/1 and 6/1/1, which connects to 12/3/2 on Ring 2:

Figure 2-34: Selector Between 5/1/1 and 6/1/1

The command also creates a bridge from 12/3/2 to Ring 1 (5/1/1 and 6/1/1), as shown in Figure 2-35.

Figure 2-35: Bridge From 12/3/2 to Ring 1

In this configuration, a two-fiber MS-SPRing switch can automatically reconnect the selector output to the protection path on the east port (12/3/2 assuming STM-4) if necessary.

Two-Fiber MS-SPRing to SNCP Connection Example

This example, illustrated in Figure 2-36, uses a SNCP endpoint with a drop on a two-fiber MS-SPRing and uses the east span of the two-fiber MS-SPRing (Ring 1) for the active path of the circuit. For VC addressing, the SNCP is an STM-1 (for example, VC-13-8).

Figure 2-36: Two-Fiber MS-SPRing to SNCP

Use the following command to create a bridge from 6/1/1 to Ring 2 (12/3/2 and 13/3/2):

Figure 2-37: Bridge From 6/1/1 to Ring 2

The command also creates a selector between 12/3/2 and 13/3/2 to Ring 1 (6/1/1) as shown in Figure 2-38.

Figure 2-38: Selector Between 12/3/2 and 13/3/2 to Ring 1

Two-Fiber MS-SPRing to Two-Fiber MS-SPRing Connection Example

All protection for a two-fiber MS-SPRing interconnecting to a two-fiber MS-SPRing is performed at the line level. You can make the connection with a two-way cross-connect from a VC on the working side of the two-fiber MS-SPRing span of Ring 1 to a VC on the working side of a two-fiber MS-SPRing span on Ring 2. The connections can be east-to-east, east-to-west, west-to-east, and west-to-west. This example, illustrated in Figure 2-39, uses Ring 1 west to Ring 2 east and assumes an STM-12-4 in Slots 12 and 13 for subtending to a two-fiber MS-SPRing (Ring 2).

Figure 2-39: Two-Fiber MS-SPRing to Two-Fiber MS-SPRing

Use the following command to create a two-way connection from 5/1/1 to 13/3/2:

Figure 2-40: Two-Way Connection from 5/1/1 to 13/3/2

Two-Fiber MS-SPRing to Four-Fiber MS-SPRing Connection Example

All protection for a two-fiber MS-SPRing interconnecting to a four-fiber MS-SPRing is performed at the line level. You can make the connection with a simple two-way cross-connect from the appropriate side, east or west, of the two-fiber MS-SPRing to the working fiber of the appropriate side, east or west, of the four-fiber MS-SPRing, as shown in Figure 2-41.

Figure 2-41: Two-Fiber MS-SPRing to Four-Fiber MS-SPRing

Use the following command to create a two-way connection from 1/1/1 to 5/1/1:

Figure 2-42: Two-Way Connection from 1/1/1 to 5/1/1

In the event of a failure, the software will automatically switch the traffic to the appropriate line and path.

SNCP to Four-Fiber MS-SPRing Connection Example

This example uses the west span of the four-fiber MS-SPRing (Ring 2) for the active path of the circuit. The example also assumes that the four-fiber MS-SPRing travels over STM-64 spans, as shown in Figure 2-43.

Figure 2-43: SNCP to Four-Fiber MS-SPRing

Use the following command to create a selector between 1/1/1 and 2/1/1 to Ring 2 (5/1/190):

Figure 2-44: Selector Between 1/1/1 and 2/1/1 to Ring 2 (5/1/190)

The command also creates a bridge from 5/1/190 to Ring 1 (1/1/1 and 2/1/1), as shown in Figure 2-45.

Figure 2-45: Bridge from 5/1/190 to Ring 1 (1/1/1 and 2/1/1)

One-Way Drop and Continue

The following examples show how to create a one-way drop and continue cross-connect. The examples use three nodes (Node 1, Node 2, and Node 3) in a ring configuration (Figure 2-46). Node 1 is the source node, Node 2 has the drop and continue, and Node 3 is the destination.

Figure 2-46: One-Way Drop and Continue

Figure 2-47 shows a circuit diagram example of the orientation of AIDs associated with the ENT-CRS command used to establish drop and continue connections.

Figure 2-47: Orientation of AIDs Used to Establish Drop and Continue Connections

Node 1 Configuration Example (Source Node)

To configure Node 1 in the one-way drop-and-continue example, issue the following command on Node 1 (see Figure 2-48):

ENT-CRS-VCn::VC-1-1,VC-5-1&VC-6-1:CTAG::1WAY;

Figure 2-48: Bridge from 1/1/1 to 5/1/1 and 6/1/1

Node 2 Configuration Example (Drop and Continue Node)

To configure Node 2 in the one-way drop-and-continue example, issue the following command on Node 2 (see Figure 2-49):

ENT-CRS-VCn::VC-5-1&VC-6-1,VC-1-1:CTAG::1WAYDC;

Figure 2-49: Selector Between 5/1/1 and 6/1/1 to 1/1/1

Node 3 Configuration Example (Destination Node)

To configure Node 3 in the one-way drop-and-continue example, issue the following command on Node 3 (see Figure 2-50):

ENT-CRS-VCn::VC-5-1&VC-6-1,VC-1-1:CTAG::1WAY;

Figure 2-50: Selector Between 5/1/1 and 6/1/1 to 1/1/1

PCA Provisioning

You can provision or retrieve protection channel access (PCA) cross-connections on two-fiber and four-fiber MS-SPRing topologies at these supported VC rates: STM-4 (two-fiber only), STM-16, and STM-64. The traffic on the protection channel is referred to as extra traffic and has the lowest priority level. Extra traffic will be preempted by any working traffic that requires the use of the protection channel.

In a two-fiber MS-SPRing, the extra traffic is provisioned on the upper half of the bandwidth path. In a four-fiber MS-SPRing, the extra traffic is provisioned on the protect fiber. The PCA provisioning feature allows you to establish the PCA cross-connection on the protection path of the two-fiber MS-SPRing and the protection channel of the four-fiber MS-SPRing only when the query is an explicit request.

There are two PCA connection types: 1WAYPCA and 2WAYPCA. The PCA cross-connection is provisioned only when the user provides an explicit request using the ENT-CRS-VCp/VC12 commands. If the cross-connection is a PCA cross-connection, either 1WAYPCA or 2WAYPCA is shown in the cross-connect type field of the RTRV-CRS-VCp/VC12 command output.

1WAYPCA and 2WAYPCA are only used in the TL1 user interface to provide usability and visibility for the user to specify a PCA cross-connection type in the TL1 cross-connection commands.

Note: The network must be configured as either a two-fiber or four-fiber STM-4, STM-16, or STM-64 MS-SPRing.

Note: The VC path cross-connection can be established with TL1 commands (ENT-CRS-xxx).

Note: Because the RTRV-CSR-xxx command does not include the optional CTYPE field to specify a connection type, the output result reports the matched cross-connections based on the queried AID(s); therefore, the retrieved cross-connection inventory can contain both PCA and non-PCA cross-connections.

Example 2-16: Provision a PCA Cross-Connect: Example

ENT-CRS-VC4::VC4-1-1,VC4-2-1:123::2WAYPCA;

Note: If the cross-connect type (CCT) of this cross-connection provisioning command is either 1WAYPCA or 2WAYPCA, and the NONE value of both <FROM> and <TO> AID is PCA AID, an IIAC (Input, Invalid PCA AIDs) error message is returned.

Note: If sending this command with a non-PCA CCT, and one or two AIDs are the PCA AIDs, an IIAC (The PCA AID Is Not Allowed for the Queried CCT Type) error message is returned.

Retrieve a PCA Cross-Connection

Use the input format in Example 2-17 to retrieve a PCA cross-connection.

COPY-RFILE

The COPY-RFILE command downloads a new software package from the location specified by the FTP URL into the inactive flash partition residing on the TCC2/TCC2P/TSC card. COPY-RFILE can also be used to back up and restore the database file.

Note: Since Software Release 5.0, PACKAGE_PATH is relative to your home directory, instead of being an absolute path from the root directory of the NE. If you want to specify an absolute path, start the path with the string '%2F'.

FTP_USER is the user ID to connect to the computer with the package file.

FTP_PASSWORD is the password used to connect to the computer with the package file.

FTP_HOST_IP is the IP address of the computer with the package file. Domain name server (DNS) lookup of hostnames is not supported.

<FTP_PORT> defaults to 21.

PACKAGE_PATH is the long path name to the package file starting from the home directory of the logged-in user.

In a firewall environment, the hostname should be replaced with a list of IP addresses each separated by an ampersand (@) character. The first IP address should be for the computer where the package file is stored. Subsequent IP addresses are for firewall computers moving outward toward the edge of the network until the final IP address listed is the computer that outside users use to first access the network.

For example, if your topology is:

"FTPHOST <-> GNE3 <->GNE2 <-> GNE1 <-> ENE"

the FTP URL is:

FTP://FTP_USER:FTP_PASSWORD@FTP_HOST_IP@GNE3@GNE2@GNE1/ PACKAGE_PATH

<DEST> specifies the destination of the file to be transferred. The comments for the SRC parameter are also valid here. <DEST> is a string.

If <OVWRT> is YES, then files are overwritten. Currently only YES is supported. Using a NO value for <OVWRT> will result in an error message.

Notes:

FTP is the only allowed file transfer method.

The use of the SWDL and the extended FTP URL syntax are required by the COPY-RFILE syntax.

APPLY

The APPLY command can activate or revert software depending on the version of software loaded on the active and protect flash. An error is returned if you attempt to activate to an older software load or try to revert to a newer software load. If this command is successful, the appropriate flash is selected and the TCC2/TCC2P2/TSC card will reboot.

The input format for the APPLY command is as follows:

APPLY:[<TID>]::<CTAG>[::<MEM_SW_TYPE>];

where <MEM_SW_TYPE> indicates memory switch action during the software upgrade.

REPT EVT FXFR

REPT EVT FXFR is an autonomous message used to report the start, completion, and completed percentage status of the FTP software download. REPT EVT FXFR also reports any failure during the software upgrade including invalid package, invalid path, invalid user ID/password, and loss of network connection.

Note: The "FXFR_RSLT" is only sent when the "FXFR_STATUS" is COMPLD. The "BYTES_XFRD" is only sent when the "FXFR_STATUS" is IP or COMPLD.

<FILENAME> indicates the transferred file path name and is a string. When a package is being transferred between the FTP server and the controller cards, the filename field will contain the string "active". Following this transfer, if there is a second controller card on the node, the file will be copied over to the second card. While this is happening, REPT EVT FXFR messages will be generated with a filename of "standby".

Step 4: Check the working and protect software on the NE by issuing the RTRV-NE-GEN command, for example:

RTRV-NE-GEN:::1;

The output should be similar to the following:

VA454-94 1970-01-06 22:22:12

M 1 COMPLD

"IPADDR=10.82.87.94,IPMASK=255.255.255.224,DEFRTR=10.82.86.1,

ETHIPADDR=10.82.87.94,ETHIPMASK=255.255.255.224,NAME=VA454-94,

SWER=3.40.00,LOAD=03.40-002G-14.21,PROTSWVER=4.00.00,

PROTLOAD=04.00-X02G-25.07,DEFDESC=\"FACTORY DEFAULTS\"" ;

Step 5: Issue the COPY-RFILE command. This command will initiate the download process. See the COPY-RFILE for command syntax.

In Example 2-20, the package is located in "/%2FUSR/CET/VINTARA" in the host 10.77.22.199. The user ID and passwords are TL1 and CISCO454SDH. The directory path of the package is similar to what you will see during an FTP session.

Step 10: If the TL1 session times out during download or if the user terminates the TL1 session, the download will continue. The download completion can be confirmed by issuing the RTRV-NE-GEN command and verifying the PROTLOAD (Example 2-26).

Example 2-28: Download is Complete

Activating New Software

After the software is successfully downloaded, the new software that resides in the protect load must be activated to run on the NE. The APPLY command can be used to activate and revert depending on the version of the protect software and the newly downloaded software (see the APPLY for correct APPLY syntax).

Activate New Software

Step 1: If the protect software is newer than the working software, activate it as shown:

APPLY::1::ACT; DEV208 1970-01-10 13:40:53 M 1 COMPLD ;

An error is reported if a revert is attempted with a newer protect software.

Step 2: If the APPLY command is successful, log out of the TL1 session using the CANC-USER command:

CANC-USER::CISCO15:1; VA454-94 1970-01-07 01:18:18 M 1 COMPLD ;

Step 3: After a successful completion of the APPLY command, the NE will reboot and the TL1 session will disconnect. When the NE comes up after the reboot, it will be running the new software. Traffic switches are possible during activation.

Remote Software Download/Activation Using the GNE

In a network with regenerator section data communications channel (RS-DCC)-connected ONS 15454 SDHs and ONS 15600 SDHs, remote download and activation are possible using the GNE/ENE feature supported in TL1. The GNE must be connected by a LAN and the remaining ENEs can download the new software package through fiber from the GNE.

Each GNE can support 11 (TCC2/TCC2P) concurrent communication gateway sessions and up to a maximum of 176 (TCC2/TCC2P) ENEs/GNE. For more information on TL1 gateway, see theTL1 Gateway.

After activating the nodes (Example 2-29), five simultaneous software downloads can be initiated using the COPY-RFILE command with appropriate TIDs, as shown in Example 2-30. All downloads will be independent of each other and download speeds might differ.

To download software to an ENE through a GNE, the FTTD URL in the COPY-RFILE command must be used as shown in Example 2-31. The FTTD parameter has the following format: "FTTD://USERID:PASSWORD@TL1 GNE NODENAME:21". Prior to Release 6.0, Port 21 is mandatory. In Release 6.0 and later, Port 21 is optional.

Example 2-32: Activate the Software Load

Scheduled PM Report

Scheduled performance monitoring (PM) reporting is a feature that extends the capability of PM reporting for the Cisco ONS 15454 SDH and ONS 15600 SDH. With scheduled PM reports, the system automatically and periodically generates the PM report of any specified facility or cross-connection. For more information on performance monitoring, refer to the Cisco ONS 15454 SDH and Cisco ONS 15600 SDH user documentation.

The following rules apply to the creation of scheduled PM reports:

The current maximum number of schedules allowed to be created for an NE is 1000. If you try to create more schedules in the NE when the maximum number of schedules has been created, an error message "Reach Limits Of MAX Schedules Allowed. Can Not Add More" is returned.

Identical schedules are not allowed for one NE. Two schedules are considered identical if they have the same AID, MOD2 type, performance monitor type, performance monitor level, location, direction, and time period.

The error message "Duplicate Schedule" is returned if you create a schedule that is a duplicate of an existing schedule. However, if the existing schedule expires (with the parameter <NUMINVL> equal to zero when retrieved by the RTRV-PMSCHED command, which means that there is no more performance monitoring report to be sent), then the new schedule with the identical parameter will replace the existing schedule.

When you create a PM schedule, the minimum report interval should not be less than five minutes.

Use the following commands to schedule and manage PM reports. Refer to each command description in the Cisco ONS 15454 SDH and Cisco ONS 15600 SDH TL1 Command Guide for command formats and syntax:

SCHED-PMREPT-<MOD2>

ALW-PMREPT-ALL

RTRV-PMSCHED-<MOD2>

RTRV-PMSCHED-ALL

INH-PMREPT-ALL

REPT PM <MOD2>

Create a PM Schedule and Receive an Autonomous PM Report

Issue the SCHED-PMREPT-<MOD2> command to create a PM schedule.

Note: The minimum interval for the PM schedule cannot be set to less than five minutes.

Issue the ALW-PMREPT-ALL command to allow the current TL1 session to be able to receive the autonomous PM report.

Manage PM Schedules

Use the following commands to manage PM schedules:

Create a PM schedule by issuing the SCHED-PMREPT-<MOD2> command.

Delete a PM schedule by issuing the SCHED-PMREPT-<MOD2> command with the <NUMREPT> parameter equal to zero.

Note: The PM schedules created on a facility or a cross-connect will be automatically deleted if the card or the cross-connect are unprovisioned.

Retrieve all the PM schedules created on the node by issuing the RTRV-PMSCHED-ALL command. Retrieve a particular MOD2 type of PM schedule by issuing the RTRV-PMSCHED-<MOD2> command.

Note: The system will not automatically delete the schedules that are expired. For example, assume that a schedule is created to report PM ten times. After ten PM reports are sent, the schedule is expired. The expired schedule can be identified by its <NUMINVL> field (equal to zero) in the response of the RTRV-PMSCHED command.

Enable or Disable a TL1 Session to Receive Autonomous PM Reports

Enable a TL1 session to receive a scheduled PM report by issuing the ALW-PMREPT-ALL command.

Note: By default, a TL1 session is disabled to receive PM reports. The ALW-PMREPT-ALL command enables a TL1 user to receive all the scheduled PM and automatic autonomous performance monitoring (AutoPM) reports from the system, regardless of whether or not the schedule is created by this TL1 user or by any other TL1 user.

Disable a TL1 session to receive any scheduled PM report by issuing the INH-PMREPT-ALL command.

Automatic Autonomous PM

The automatic autonomous performance monitoring (AutoPM) report is a feature that extends the capability of PM reporting for the Cisco ONS 15454, ONS 15310-CL, ONS 15310-MA, and ONS 15600. With this feature enabled, the system automatically generates the PM report for all cross-connections. AutoPM is disabled by default. When enabled, an automatic report is generated every 15 minutes, which is the default interval.

AutoPM can be enabled or disabled only through CTC. Refer to the "Monitor Performance" chapter in the Cisco ONS 15454 SDH Procedure Guide for the procedure.

Issue the RTRV-NE-GEN TL1 command on the node to retrieve the AutoPM configuration.

Bridge and Roll

Bridge and roll functionality allows live traffic to be moved (rolled) from one entity to another. This section provides information and sample procedures for single-rolling, dual-rolling, and protection rolling for one-way or two-way circuits using TL1 commands, including:

Line Level Rolling-Rolls all cross-connections from one port/facility to another port/facility.

Bulk Rolling-Rolls a subset of cross-connections from one port/facility to another port/facility.

There are two roll modes:

In automatic mode, the leg to be rolled is automatically dropped upon detection of a valid input signal on the new path.

In manual mode, the leg to be rolled is retained upon detection of a valid signal on the new path. The leg must be dropped manually.

Caution! If you have created a roll on the circuit and it has detected a valid signal, do not cancel it. Cancelling a valid roll will cause a traffic hit of more than 1300 ms. If you want to revert back from a valid roll, complete the roll and use bridge and roll again to roll it back.

Note: The path width rules for creating circuits apply when rolling circuits. For example, if you roll a VC4 starting at VC#1, you cannot roll it to another port and start it at VC#2. You have to start it at VC#1.

Restrictions

The following restrictions apply for bridge and roll using TL1 in this release:

Rolling is not allowed on electrical cards or Ethernet cards.

Rolling is not allowed on hairpin circuits.

Rolling is not allowed on monitor circuits.

Rolling is not allowed on any cross-connection that is involved in test access.

Rolling is not allowed on any cross-connection that is involved in cross-connect loopbacks.

Rolling is not allowed on any port that is involved in facility or equipment loopbacks. This restriction applies to both "roll from" and "roll to."

When rolling on a 1+1 protected circuit, the "roll to" cannot be on the protect port of the protection group.

Rolling on a MS-SPRing protected circuit cannot violate the rules governing MS-SPRing circuits: a circuit that traverses a MS-SPRing must use the same STS number on the ring between source and destination.

Rolling on an MS-SPRing protected circuit will be denied if there is an existing protection switch on the ring. If the protection switch happens after the roll is initiated, the system will not monitor valid signals on the "roll to" path until the protection switching is cleared.

Rolling on an SNCP protected circuit cannot violate the rules governing SNCP circuits: SNCP circuits must have one bridge and one selector.

The bridge and selector of an SNCP protected circuit cannot be rolled away.

In the case of a dual roll on an SNCP protected circuit, both roll points have to be on either the working or protect path of the circuit. For example, you cannot specify one roll point on the working path and the other roll point on the protect path of the circuit being rolled.

When rolling on a SNCP protected circuit, the "roll to" cannot be line protected (1+1 or MS-SPRing protected). TL1 can only ensure this on the bridge and selector node, not on the intermediate node.

When rolling on a mixed protection circuit, the roll points have to be within the same protection domain.

Rolling using TL1 can be performed on a CTC-created cross-connection.

Note: If a roll is created using TL1, it cannot be edited or deleted by CTC.

Rolling using TL1 can be performed on a TL1 cross-connection.

Note: If a roll is created using CTC, it cannot be edited or deleted by TL1.

If the intermediate path of a circuit is being rolled away to another circuit, the second circuit cannot carry any live traffic.

Note: After a roll is completed, the second circuit will form the new intermediate path of the original circuit.

Rolling cannot be performed on low order path tunnel or VC low order path aggregation point (VAP) circuits passing through less than four nodes.

The following restrictions apply for bridge and roll using TL1 virtual concatenation (VCAT) in this release:

For non-open-ended VCAT circuits, you cannot change the source or destination of the circuit.

For open-ended VCAT circuits, you can change the source or destination of the circuit, but only on the open end.

The following restrictions apply for bridge and roll using TL1 common fiber-routed VCAT circuits in this release:

Rolling cannot change the common fiber property of a common fiber-routed VCAT circuit.

When rolling on a VCAT member circuit, in order not to change the common fiber property of a common fiber-routed VCAT circuit, you can roll the member from one time slot to a different time slot within the same fiber.

Bridge and Roll TL1 Commands

The following commands are used for bridge and roll. Refer to the Cisco ONS 15454 SDH and Cisco ONS 15600 SDH TL1 Command Guide for full command descriptions including input and output formats and examples.

DLT-BULKROLL-<STM_TYPE>

This command deletes an attempted rolling operation or completes an attempted rolling operation. This command supports Line level and bulk rolling, but cannot be used for Path level rolling. The rolls that are created using the ENT-BULKROLL-<STM_TYPE> command can be deleted using the DLT-BULKROLL-<STM_TYPE> command.

DLT-ROLL-<MOD_PATH>

This command deletes an attempted rolling operation or completes an attempted rolling operation.

ED-BULKROLL-<STM_TYPE>

This command edits information about rolling traffic from one endpoint to another without interrupting service. This command can use the CMDMDE option to force a valid signal. The only parameter that can be edited is CMDMDE. The time slots cannot be edited. This commands supports Line level and bulk rolling, but cannot be used for Path level rolling.

ED-ROLL-<MOD_PATH>

This command edits information about rolling traffic from one endpoint to another without interrupting service. This command can use the CMDMDE option to force a valid signal. The only parameter that can be edited is CMDMDE. The time slots cannot be edited.

ENT-BULKROLL-<STM_TYPE>

This command enters information about rolling traffic from one endpoint to another without interrupting service. This commands supports Line level and bulk rolling, but cannot be used for single Path level rolling.

ENT-ROLL-<MOD_PATH>

This command enters information about rolling traffic from one endpoint to another without interrupting service. This command supports VC Path-level rolling only.

RTRV-BULKROLL-<STM_TYPE>

This command retrieves roll data parameters. This command supports Line level and bulk rolling, but cannot be used for Path level rolling.

RTRV-ROLL-<MOD_PATH>

This command retrieves roll data parameters.

Two-Way Circuit Single Roll and Dual Roll Procedures

Single roll operation moves either the source or destination of a circuit to a new endpoint on the same node or on a different node. In single roll operation, you only choose one roll point during the process.

Dual roll operation reroutes a segment between two roll points of a circuit. In dual roll operation, you choose two roll points during the process.The new route can be one of the following:

A new link (no circuit is required)

Another circuit (created before or during the bridge and roll process)

Create a Two-Way Circuit Single Roll or Dual Roll

To create a two-way circuit single roll or dual roll, enter the ENT-ROLL-<MOD_PATH> command or the ENT-BULKROLL-<STM_TYPE> command depending on the type of roll you want to perform.

Table 2-7: Two-Way Circuit Single or Dual Bulk Roll with ENT-BULKROLL

Step 2: If you performed a manual roll, you must confirm the circuit is valid by issuing the RTRV-BULKROLL-<STM_TYPE> command. The input format of the command is as follows:

RTRV-BULKROLL-<STM_TYPE>:[<TID>]:<SRC>:<CTAG>;

The following is an example of the command input:

RTRV-BULKROLL-STM4:CISCO:FAC-3-1:1;

One-Way Circuit Single Roll and Dual Roll Procedures

Single roll operation moves either the source or destination of a circuit to a new endpoint, either onto the same node or onto a different node. In single roll operation you only choose one roll point during the process.

Dual roll operation reroutes a segment between two roll points of a circuit. In dual roll operation, you choose two roll points during the process. The new route can be one of the following:

A new link (no circuit is required)

Another circuit (created before or during the bridge and roll process)

Create a One-Way Circuit Single Roll

To create a one-way circuit single roll, enter the ENT-ROLL-<MOD_PATH> command or the ENT-BULKROLL-<STM_TYPE> command, depending on the type of roll you want to perform. The input formats for these commands are as follows:

Remote Monitoring-Managed PMs

The cards that support RMON PMs include: G1K-4, CE-1000-4, ML1000-2/ML100T-12, FC_MR-4, MXP_MR_2.5G/MXPP_MR_2.5G, and ML-100T-8/CE-100T-8. The PM types for these cards include Ethernet statistic types defined in the standard SNMP/RMON MIB, and also include other statistic types managed by RMON, for example, the Fibre Channel statistical types.

When creating an RMON threshold, there are two threshold values that need to be specified. The first threshold is the rising threshold and the other is the falling threshold. There are other parameters that need to be specified when creating the RMON threshold, for example, the startup type and the sample type.

Note: There can be more than one threshold defined for each RMON statistic type.

The current bucket is not defined by the RMON. RMON-managed PM only shows the history data of the PMs and the data accumulated since the last time the counters are cleared (RAW-DATA).

In the RMON TCA, the accumulation time period is not the predefined PM bucket accumulation time, such as 15-MIN or 1-DAY. It can be any integer (any time greater than 10 seconds) that is defined when creating the RMON threshold.

RTRV-PM-<MOD2>

The RTRV-PM-<MOD2> command retrieves the RMON-managed PMs.

The TL1 modifiers FSTE, GIGE, and POS are used to retrieve the RMON-managed Ethernet PM, if the Ethernet port is an FSTE, GIGE, or POS port type. The FC modifier retrieves the RMON-managed Fibre Channel PM.

There are three accumulation time periods for RMON statistics: 1-MIN, 1-HR, and RAW-DATA. For RMON-managed PMs, only history PM buckets and RAW-DATA are supported and there is no current bucket defined for RMON-managed PMs. When RAW-DATA is specified in the input of RTRV-PM, the date and time specified in the input will be ignored. The MONDAT and MONTM in the output will be the last time the counters were cleared. RAW-DATA is the default TMPER value for RMON-managed PM retrieval.

Because RMON PM only supports the history data if the accumulation time period is 1-MIN, 15-MIN, 1-HR, or 1-DAY, you must specify the correct history PM bucket for the RTRV-PM command to succeed.

When retrieving PM, if an unsupported MONTYPE is specified, an error message is returned.

Currently there is no support of LOCN (location) and DIRN (direction) for RMON-managed data statistics.

Table 2-11: Error Messages for RTRV-PM-<MOD2>

The TMPER parameter specified is not applicable for the MOD2 type. For example, 1-MIN is not applicable for STM16 PM types.

IDNV

Current Interval Not Supported For RMON PMs

The current interval is specified by default, or is explicitly specified by MONDAT/MONTM, when the TMPER is 1-MIN, 15-MIN, 1-HR, or 1-DAY.

ENT-RMONTH-<MOD2_RMON>

The ENT-RMONTH-<MOD2_RMON> command creates a threshold type (an entry in the RMON alarm table) for an RMON statistic, for the RMON-managed PMs. An event (TCA) is generated and reported when the threshold is crossed in the appropriate direction during the sampled time period. More than one threshold can be created by using different parameters (rising/falling threshold), for each MONTYPE.

This command applies to G1000, GIGE, FSTE, POS, and FC data objects.

Input Format

Input Example

The following example creates an entry in the RMON threshold table for the etherStatsOctets statistic type with an interval equal to 100 seconds, rising threshold of 1000, falling threshold of 100, DELTA sampling type and the startup type of RISING-OR-LTING.

Table 2-12: Error Messages for ENT-RMONTH-<MOD2_RMON>

The rising or falling threshold is less than 0, or the falling threshold is greater than or equal to the rising threshold.

IDNV

Invalid MONTYPE value

The MONTYPE is not applicable to the data type (represented by the MOD2).

IIDT

Cannot Create More RMON Threshold

The number of RMON threshold created reached the maximum (256).

IIDT

Duplicate RMON Threshold

There is already a threshold created with the exact parameters.

DLT-RMONTH-<MOD2_RMON>

The DLT-RMONTH-<MOD2_RMON> command deletes a threshold type (an entry in the RMON alarm table) created for a MONTYPE (RMON statistic type). Because there can be multiple thresholds created for a particular MONTYPE, you must specify all the necessary parameters for the threshold in order to identify the particular threshold to be deleted.

This command applies to G1000, GIGE, FSTE, POS, and FC data objects.

Input Format

Input Example

The following example deletes an entry in the RMON threshold table for the etherStatsOctets statistic type, with an interval equal to 100 seconds, rising threshold of 1000, falling threshold of 100, DELTA sampling type, and the startup type of BOTH.

REPT EVT <MOD2ALM> for Threshold Crossing Events

The HT or LT is appended to the CONDTYPE when crossing the rising or falling threshold.

The table index for the threshold in the RMON alarm table is enclosed in the text of the TCA description. This table index is displayed in the output of the RTRV-RMONTH command also. You can retrieve additional information regarding the threshold that generates the TCA by issuing the RTRV-RMONTH command and comparing the output with corresponding table index.

INIT-REG-<MOD2>

Only RAW-DATA is allowed to be specified for TMPER because no history data will be cleared for RMON-managed PMs by INIT-REG-<MOD2>.

SCHED-PMREPT-<MOD2>

This command schedules or reschedules the NE to report the PM data. The three accumulation time periods for RMON statistics are: 1-MIN, 1-HR, and RAW-DATA.

RTRV-PMSCHED-<MOD2>

This command retrieves the RMON statistics reporting schedule that was set for the NE by the SCHED-PMREPT-<MOD2> command.

The LOCN parameter is optional in the output of RTRV-PMSCHED-<MOD2>, and no LOCN information will be given in the output of RTRV-PMSCHED for RMON PM schedule.

REPT PM <MOD2>

This message reports autonomous monitoring statistics as a result of the schedule created by SCHED-PMREPT-<MOD2>.

The LOCN parameter is optional in the output of REPT PM <MOD2> message, and no LOCN information will be given in the output of REPT PM <MOD2>.

REPT DBCHG

Reports any changes to the NE that result from issuing the following commands:

ENT-RMONTH-<MOD2>

DLT-RMONTH-<MOD2>

Also reports when an RMON PM schedule is created or deleted through the SCHED-PMREPT-<MO2> command.

MONTYPE Defined for Ethernet Statistics and Condition Type for TCA

The names of Ethernet and Fibre Channel MONTYPEs are defined exactly as they are defined in the corresponding SNMP MIB statistics group. For example, etherStatsUndersizePkts will be used as the name for the same RMON statistics defined in RFC 1757.

Unlike the PM of other SDH entities (such as VC path, STM), there are two condition types defined for the TCAs of each RMON-managed statistics type (Ethernet or Fibre Channel MONTYPE). One condition type is for the rising threshold, and the other is for the falling threshold. For example, there are two condition types for the etherStatsUndersizePkts statistics type: T-etherStatsUndersizePkts-HT for the rising threshold, and T-etherStatsUndersizePkts-LT for the falling threshold.

Note: For platform-specific PM information, refer to the Procedure Guide and Reference Manual of that platform.

The data shown is accumulated starting from the last time that the counters are cleared. This is only applicable to RMON managed PMs.

SAMPLE_TYPE

SAMPLE_TYPE (Table 2-16) describes how the data will be calculated during the sampling period.

Table 2-16: SAMPLE_TYPE

!Value

!Description

ABSOLUTE

Comparing directly

DELTA

Comparing with the current value of the selected variable subtracted by the last sample.

STARTUP_TYPE

STARTUP_TYPE (Table 2-17) indicates whether an event will be generated when the first valid sample is crossing the rising or falling threshold.

Table 2-17: STARTUP_TYPE

Value

Description

RISING

Generate the event when the sample is greater than or equal to the rising threshold.

FALLING

Generate the event when the sample is smaller than or equal to the falling threshold.

RISING-OR-LTING

Generate the event when the sample is crossing either the rising threshold or it the falling threshold.

Notes for DWDM Card Types

The PM for the client port and/or chunk port (OCH) can include both the RMON-managed PM and the SDH PM when the client payload is provisioned as 1GFC, 2GFC, 10GFC, 1GFICON, 2GFICON, GIGE, or 10GIGE for the following cards:

MXP_2.5G_10G

TXP_MR_10G

TXP_MR_2.5G

TXP_MR_10E

MXP_MR_2.5G

Client Port of DWDM Cards

When the client port of a dense wavelength division multiplexing (DWDM) card is provisioned as 1GFC, 2GFC, 10GFC, 1GFICON, 2GFICON, GIGE, or 10GIGE, the applicable PM for the client port includes both the RMON-managed PM and the SDH PM. Therefore, the behavior of the RTRV-PM-MMOD2>, INIT-REG-<MOD2>, and SCHED-PMREPT-<MOD2> commands is different from the Ethernet or Fibre Channel port of the other cards where only RMON PM is applicable. The differences include:

LOCN and DIRN parameters are applicable to the RTRV-PM-<MOD2>, INIT-REG-<MOD2>, and SCHED-PMREPT-<MOD2> commands because they are applicable to the SDH PM. When the LOCN or DIRN parameter is specified, it only applies to the SDH PM.

Because 1-MIN, 1-HR, and RAW-DATA are not applicable to SDH PM, no SDH PM would be returned in the output of the RTRV-PM command. If RAW-DATA is specified in the input of the INIT-REG command, no SDH PM counter will be cleared.

When the accumulation time period is specified as 15-MIN or 1-DAY and the PM history bucket is specified as 0 (current bucket), only SDH PM will be returned in the output of the RTRV-PM command. No RMON-managed PM will be included in the output of the RTRV-PM command because RMON PM does not have current bucket.

An SDH PM MONTYPE cannot be specified in the input of the INIT-REG command. Only the SDH PM counters are cleared. When the ALL MONTYPE is specified, both the RMON and the SDH PM counters are cleared.

The commands used to manage RMON thresholds (ENT-RMONTH, DLT-RMONTH, and RTRV-RMONTH) are only applicable to the RMON PM of the client port. The SDH PM thresholds of the client port are still managed by the SET-TH and RTRV-TH commands. For example, if the client port type of an MXP_MR_2.5G card is provisioned as GIGE, the following commands would be used to create an RMON threshold:

ENT-RMONTH-GIGE::FAC-2-1-1:1::IFINOTETS,,,,1000:RISE=1000,FALL=900;

and the following command would be used to set the SDH PM threshold:

SET-TH-GIGE::FAC-2-1-1:1LBCL-MIN,0.2;

OCH Port of DWDM Cards

The optical channel (OCH) port of the TXP_MR_10G and TXP_MR_10E cards include the RMON-managed 8B10B PM as well as the other SDH PM when their client port is provisioned as GIGE, 10GIGE, 1GFC, 2GFC, or 10GFC.

The RTRV-PM-OCH, INIT-REG-OCH, SCHED-PMREPT-OCH, and REPT PM OCH commands have similar behaviors as mentioned in the Client Port of DWDM Cards.

Rules for Framing Type Autoprovisioning in CTC Versus TL1

The E1, E3, and DS3i cards can autosense framing and set the format accordingly; however, this framing autosense feature can only be set using CTC. Use CTC to set the frame format (FMT) attribute on E1, E3, and DS3i cards to autoprovision. The FMT field will blank out for a few seconds while the card determines the framing mode received by that particular port. The FMT field is set accordingly to unframed, M23, or CBit. If the card is not present (preprovisioned), setting the FMT field to autoprovision will result in the FMT field defaulting to unframed.

The TL1 interface does not support the autoprovision option for the E1, E3, and DS3i cards; it only supports unframed, M23, or CBit. If autoprovision is selected from CTC and at the same time the TL1 command RTRV-E3 is issued, the TL1 output will indicate the FMT field as unframed during the time period that the card (if present) is autosensing the frame format. If the card is not present (preprovisioned), the response of the RTRV-E3 command (after CTC sets the FMT to autoprovision) will indicate the FMT field as unframed.

Provisioning Rules for Transponder and Muxponder Cards

This section provides provisioning rules associated with the following cards and their pluggable port modules (PPMs):

MXP_2.5G_10G

TXP_MR_10G

TXP_MR_2.5G

TXPP_MR_2.5G

MXP_2.5G_10E

TXP_MR_10E

MXP_MR_2.5G

MXPP_MR_2.5G

PPM Provisioning Rules

PPMs must be provisioned. Use the ENT-EQPT command to provision PPMs. For example, to provision the first PPM on Slot 2, use the following command:

ENT-EQPT::PPM-2-1:100::PPM-1PORT;

To delete PPM provisioning, use the DLT-EQPT command.

Payload Provisioning Rules

Use the following rules when provisioning payload:

PPM must first be provisioned.

Changing the payload data type requires:

All ports being edited must be in the OutOfServiceandManagement,Disabled state because this change is traffic affecting.

Payload cannot be changed if any ports being edited are part of a Y-cable protection group.

Only the TXP card can be used for the 10GIGE payload. Termination mode must be set to TRANSPARENT-ALARM INDICATION SIGNAL (AIS) or TRANSPARENT-SQUELCH (TRANSPARENT-SQUELCH is only supported on TXP_MR_10E).

To set the payload to other than STM1, STM4, STM16, or STM64, the termination mode must be set to TRANSPARENT-AIS or TRANSPARENT-SQUELCH (TRANSPARENT-SQUELCH is only supported on TXP_MR_10E). For Fibre Channel cards and all 2R payload types, the termination mode is not applicable and must be set to TRANSPARENT (AIS or SQUELCH).

Changing payload while in a regeneration group requires first unprovisioning the regeneration group, unprovisioning the payload, reprovisioning the payload, and reprovisioning the regeneration group.

TL1 commands for payload provisioning are:

ENT-(STM, nGIGE, nGFC, 2R)

DLT-(STM, nGIGE, nGFC, 2R)

ED-(STM, nGIGE, nGFC, 2R)\

Examples of provisioning payload commands include:

ENT-STM4

ENT-10GIGE

ED-2GFC

STM Payload Provisioning Parameters

SDH payloads are supported by DWDM cards according to Table 2-18. These payloads are configurable only for the Section and Line layers. STM layers cannot be provisioned or retrieved.

1. If 2GFC or 2GFICON is on Port 2, then Port 1 must be unprovisioned. If Port 1 is provisioned then Port 2 cannot contain 2GFC or 2GFICON because of bandwidth limitations. Ports 3 through 8 are not available. ESCON payload is not supported.

2. ESCON and mixed card modes are not supported.

The configuration parameters for STM ports can be edited and retrieved using the ED-<STM_TYPE> and RTRV-<STM_TYPE> commands. The following is a list of restrictions when using the parameters for these commands:

Synchronization parameters are applicable only to cards supporting synchronization: MXP-2.5G-10G, TXP-MR-10E, and MXP-2.5G-10E. Only SYNMSG and SENDDUS parameters are supported.

Signal fail and signal degrade can be provisioned using SFBER and SDBER parameters, respectively.

Soak time and administrative/service state parameters can be provisioned using SOAK, SOAKLEFT, PST, SST, and CMDMDE parameters.

The SONET/SDH selection can be provisioned using the MODE parameter.

The name of the facility can be provisioned using the NAME parameter.

The J0 section parameters can be provisioned using the EXPTRC, TRC, INCTRC, TRCMODE, and TRCFORMAT parameters.

Termination Mode Provisioning Rules

The following rules apply to provisioning the termination mode.

This is a card-level operation.

Termination mode provisioning is only applicable to the STM1, STM4, STM16, and STM64 payload types.

Changing termination mode requires:

All ports must be in OutOfService state because this change is traffic-affecting.

All ports must not have DCC termination (GCC is not applicable).

The Section Trace Mode on all ports must be <OFF>.

The trunk port must not be part of any timing source.

If any port is Y-cable protected, these rules also apply to the peer slot.

Section and Line termination mode is supported for the STM1, STM4, STM16, and STM64 payloads.

You cannot change the termination mode if the port is part of a Y-cable protection or regeneration group.

Termination mode provisioning does not apply to the MXP_MR_2.5G and MXPP_MR_2.5G cards.

To set the termination mode, use the following commands:

ENT-EQPT

ED-EQPT

Example 2-33 sets the termination mode of the card in Slot 1 to DWDM-LINE.

Example 2-33: Set the Termination Mode

ED-EQPT::SLOT-1:116:::CARDMODE=DWDM-LINE;

Wavelength Provisioning Rules

Use the following rules when provisioning wavelengths:

Changing trunk wavelength requires that all trunk ports be in the Locked-Disabled state, because this change is traffic-affecting.

Setting the wavelength to the first tunable wavelength will cause the first wavelength from the card manufacturing data to be used as the operational wavelength.

If the provisioned wavelength is set to the first tunable wavelength, any removal of an operational card and subsequent replacement with a card for a different wavelength will not cause a mismatch alarm to be raised.

To receive the mismatch alarm notification, you need to explicitly provision the wavelength and not use the first tunable wavelength.

Use the ENT-EQPT and ED-EQPT commands to provision card-level wavelength. The following example sets the wavelength of the card in Slot 1 to 1530.33:

ED-EQPT:VA454-22:SLOT-1:116:::PWL=1530.33;

Regeneration Group Provisioning Rules

Use the following rules when provisioning regeneration groups:

The TXPP and TXP versions of the transponder card can be used in a regeneration group.

When the TXPP card is used as a regeneration group, the LOCKOUT_OF_PROTECTION, inhibit switching command is issued on the working trunk port.

You cannot unlock the inhibit switching command until the regeneration group is unprovisioned for the TXPP.

Regeneration group provisioning will be denied if there is a FORCE or MANUAL switching command already provisioned on the trunk ports for the TXPP.

A regeneration group enables the continuation of the client signal across multiple spans.

Peer slot must not be itself.

Peer slot must at least be preprovisioned.

Peer slot must not be part of another regeneration group.

Peer slot must not be part of a Y-cable protection group.

Same card type.

Same payload type and data rate.

Same ITU-T G.709 OTN status.

Same FEC status.

Termination mode has to be set to transparent (AIS or SQUELCH) mode.

Use the ED-EQPT and ENT-EQPT commands to set a card-level regeneration group. The following command sets a card-level regeneration group for Slot 2.

ED-EQPT::SLOT-2:CTAG:::PROTID=SLOT-2,NAME=REGENGROUPNAME;

DCC/GCC Provisioning Rules

Use the following rules when provisioning DCCs and GCCs.

The DCC can be provisioned on the client port of a TXP or MXP card.

No 2R payload types support GCC.

Provisioning a DCC requires:

Payload data type is set to STM1, STM4, STM16, or STM64.

Termination mode is set to Line or Section terminated if the card supports provisionable termination mode.

The DCC can be provisioned on the trunk line provided that ITU-T G.709 is provisionable and ITU-T G.709 OTN status is turned off:

To provision a GCC on the trunk port, the ITU-T G.709 should be enabled.

To provision a DCC on the trunk port, the ITU-T G.709 should be disabled.

Only the working client port in a Y-cable protection scheme is allowed to be provisioned with DCC.

Only the working trunk port in a splitter protection scheme can be provisioned with DCC or GCC.

Use the ED-(STM, nGIGE, nGFC) command to provision DCC, as shown in the following command:

ED-STM64::FAC-1-1-1:100:::COMM=DCC:OutOfService,AutomaticInService;

Use the ED-OCH command to provision GCC, as shown in the following command:

ED-OCH::CHAN-6-2:114::COMM=GCC:OutOfService,AutomaticInService;

ITU-T G.709 OTN, FEC, and OTN SDBER/SFBER Provisioning Rules

Use the following rules when provisioning ITU-T G.709 OTN, FEC, and OTN SDBER/SFBER:

The ITU-T G.709 OTN, FEC, and OTN SDBER/SFBER can only be provisioned on the trunk port.

2R (transparent) payload types (HDTV and passthrough) do not support ITU-T G.709 OTN or FEC.

To enable ITU-T G.709 OTN:

All trunk ports must be in the OutOfService state.

All trunk ports must not have any RS-DCC provisioned.

To disable ITU-T G.709 OTN:

All trunk ports must be in the OutOfService state.

All trunk ports must not have any GCC or active trail trace identification (TTI) mode provisioned.

FEC status can be enabled only if ITU-T G.709 is enabled.

To change FEC status, all trunk ports must be in the OutOfService state.

Only ITU-T G.709 OTN, FEC status, and SDBER/SFBER settings on the working trunk port can be changed in the protected version of the TXP. The value provisioned on the working trunk port is reflected on the protect trunk port.

The ITU-T G.709 OTN is only provisionable in non-2R (or unframed) payload type.

When ITU-T G.709 is turned on, the OTN SFBER value is always set to 1E-5 and no other bit error rate (BER) values are provisionable.

Use the ED-OCH commands to provision ITU-T G.709, FEC, and OTN SDBER/SFBER, as shown in the following example:

Synchronization Provisioning Rules

The TXP_MR_10G, TXP_MR_2.5G and TXPP_MR_2.5G are through-timed (passthrough) and cannot be used for a timing source.

The TXP_MR_10E can be used as a time reference (only the client port, not the trunk port).

A MXP_MR_2.5G or MXPP_MR_2.5G card trunk ports can be used as a timing source.

Only MXP ports can be used for a timing source. A trunk port is only allowed as a timing reference if ITU-T G.709 is off and the termination mode is Line or Section.

For MXP cards, all client ports are available for timing source irrespective of termination mode.

Use the ENT-STM, ED-STM, and ED-OCH commands to provision port-level synchronization attributes, as shown in the following examples:

ED-STM16::FAC-1-1-1:CTAG:::SYNCMSG=Y,SENDDUS=N:;

ED-OCH::CHAN-6-2:114:::SYNCMSG=N,SENDDUS=Y;:

Section Trace Provisioning (J0) Rules

Use the following rules when provisioning section trace (J0):

The client and trunk ports only support the section trace if the payload is STM1, STM4, STM16, or STM64.

The client and the trunk ports support the section trace only in Line or Section termination mode.

In Line termination mode, the supported trace modes are MANUAL and MANUAL_NO_AIS trace modes.

In Section termination mode, the supported trace mode is only the MANUAL_NO_AIS trace mode.

The section trace supports a 1- or 16-byte length trace format.

The trace mode of AUTO and AUTO-NO-AIS are not supported.

No trace is applicable for 2R (unframed) payload types, for example, DV-6000, HDTV, and ESCON.

The section trace received string should appear when the card is in TRANSPARENT-AIS or TRANSPARENT-SQUELCH termination mode and the payload is STM1, STM4, STM16, or STM64.

When the client port is configured in a Y-cable protection group, the received string is always retrieved from the active client port.

If the line is Y-cable protected, section trace can only be provisioned on the working port. However, the provisioning is duplicated between the two ports. Both ports contain the same values. This rule applies to the following parameters: Mode, Format, Send String, and Expected String.

The MXP_2.5G_10E card is used for client test connection on client ports. For the trunk port, the TTI is used.

The TXP_MR_10E card is used to test connections on client trunk ports.

On MXP_MR_2.5G/MXPP_MR_2.5G cards, the trunk port section trace can be provisioned following the rules for line terminated SDH.

Use the ED-STM command to provision section trace of client ports provisioned for STM payload, as shown in the following example:

Trail Trace Identification Provisioning Rules

Use the following rules when provisioning trail trace identification (TTI):

For the TXPP_MR_2.5G card, TTI can be provisioned on the working trunk port only. However, the provisioning will be duplicated between the two ports. Both ports will contain the same values. This rule applies to the following parameters: Mode, Format, Send String, and Expected String.

The TTI level trace supports only 64-byte length trace format.

The TTI level trace supports only the MANUAL and MANUAL_NO_AIS trace modes.

The TTI received string is always retrieved from the active trunk port.

The TTI level trace can be provisioned for the section and path monitoring.

MXP_MR_2.5G and MXPP_MR_2.5G cards do not support TTI.

Use the ED-TRC-OCH command to provision port-level trace, as shown in the following example:

When the framing type is SONET/SDH, all monitored PM parameter terminology follows the current chassis type.

The OTN thresholds are only applicable if the ITU-T G.709 OTN status is enabled.

The FEC thresholds are only applicable if the ITU-T G.709 and FEC are enabled.

If the line is configured in a Y-cable or splitter protection group, only the working line thresholds can be provisioned. The working line thresholds will be reflected on the protect line thresholds. This rule applies for all threshold types including ITU-T G.709 OTN and FEC thresholds.

Payload PM can be independently retrieved for both the working and protect port.

Use the SET-TH-(STM, nGIGE, nGFC, OCH) command to set port-level thresholds, for example:

SET-TH-STM16::FAC-1-1-1:123::CVL,12,NEND,,15-MIN;

SET-TH-OCH::CHAN-6-1:123::ES-PM,12,NEND,,15-MIN;

Use the RTRV-PM-(STM, nGIGE, nGFC, OCH) command to retrieve port-level thresholds, for example:

RTRV-PM-STM16::FAC-1-1-1:123::CVL,10-UP,NEND,BTH,15-MIN,04-11,12-45;

RTRV-PM-OCH::CHAN-6-1:123::ES-PM,10-UP,NEND, BTH,15-MIN,04-11,12-45:

Y-Cable Protection Group Provisioning Rules

Use the following rules when provisioning a Y-cable protection group"

A Y-cable protection group can be created between the client ports of two unprotected TXPs only.

While in Y-cable protection, a TXP card cannot be part of a regeneration group.

Only the working client port can be provisioned with RS-DCC.

Y-cable cannot be provisioned for a protect version of the TXP_MR_2.5G card.

Only the working ports (not the protect) can be provisioned with DCC and timing reference.

Use the ENT-FFP-(STM, nGIGE, nGFC), DLT-FFP-(STM, nGIGE, nGFC), and ED-FFP-(STM, nGIGE, nGFC) commands to provision Y-cable protection groups, as shown in the following examples:

Loopback Provisioning Rules

Loopbacks are not applicable when the framing type is UNFRAMED (HDTV or DV6000).

For the protect TXP, the following loopback rules apply to the trunk ports:

Only one loopback is allowed to be provisioned at the trunk ports at any given time.

Loopback is allowed only if the sibling trunk port is in the OutOfService-Maintenance state.

Provisioning a loopback on a trunk port will trigger the LOCKOUT_OF_PROTECTION or LOCKOUT_OF_WORKING inhibit switching command, depending on whether the working or the protect port is placed in the loopback.

When a loopback is provisioned on a trunk port, both trunk ports will transmit the signal of the loopback port.

A loopback is denied if there is a FORCE or MANUAL switching command in place on the trunk ports.

You cannot remove the inhibit switching command issued as a result of the loopback. This inhibit switching command will be removed only when the loopback is removed.

The TL1 command is OPR-LPBK-OCH.

Example of operating a loopback:

OPR-LPBK-OCH::CHAN-2-1:1::,,,TERMINAL;

Automatic Laser Shutdown Provisioning Rules

Use the following rules when provisioning automatic laser shutdown (ALS):

ALS can be provisioned on the client and trunk ports.

If the trunk port is configured in a splitter protection group, only the working trunk can be provisioned for ALS. However, provisioning on the working trunk port is reflected on the protect port.

For the protected TXP, ALS mode will only take effect when both ports receive a loss of signal (LOS).

Use the ED-ALS and ED-ALS-(STM, nGIGE, nGFC, OTS, OMS, OCH) commands to edit ALS attributes, as shown in the following examples:

Port State Model Provisioning Rules

The OutOfService,AutomaticInService state is not supported for the 1GigE and 2GigE payload types.

The working and protect port can be put in InService and OutOfService independently.

For the protect TXP card:

Setting the protect trunk port to OutOfService enables the suppression of alarms on that port and enables the card to be used like an unprotected card, but the card still cannot be used in a Y-cable protection group.

Setting the protect trunk port to OutOfService does not switch off the transmit laser unless both trunk ports are OutOfService.

The protect trunk port cannot be InService if a loopback or a regeneration group is provisioned.

Use the ED-(STM, nGIGE, nGFC, OCH) command to edit the port state, as shown in the following examples:

ED-STM16::FAC-6-1-1:114::::OutOfService,AutomaticInService;

ED-10GIGE::FAC-6-1:114::::OutOfService,AutomaticInService;

ED-OCH::CHAN-6-1:114::::IS;

SDH-Related Provisioning Rules

Use the following rule when editing SDH trunk port attributes:

The SDBER and SFBER can only be provisioned on the working trunk port (OCH) for the protect TXP card. Values set at the working port will be reflected on the trunk port.

Use the ED-OCH command to edit the trunk port attributes, as shown in the following example: