Procedures and Provisioning

Note The terms "Unidirectional Path Switched Ring" and "UPSR" may appear in Cisco literature. These terms do not refer to using Cisco ONS 15xxx products in a unidirectional path switched ring configuration. Rather, these terms, as well as "Path Protected Mesh Network" and "PPMN," refer generally to Cisco's path protection feature, which may be used in any topological network configuration. Cisco does not recommend using its path protection feature in any particular topological network configuration.

2.1 Setting up TL1 Communication

The period during which a user is logged into the node is called a session. There are three options you can use to open a session (login):

•Cisco Transport Controller (CTC)

•Telnet

•Craft interface

The TL1 password identifier (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 and ONS 15310-CL allow a maximum of 20 (19 Telnet sessions and one craft session) concurrent TL1 sessions using any one or any combination of the options listed above. The ONS 15600 and ONS 15310-MA support a maximum of 20 (18 Telnet sessions and two craft sessions) concurrent TL1 sessions on the customer access panel (CAP). For information about issuing commands to multiple nodes, see the "TL1 Gateway" section.

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 information about these and other commands and messages, refer to the Cisco ONS SONET TL1 Command Guide.

Open a TL1 Session Through CTC

Step 1 From the PC connected to the ONS node, 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 the CTC. The IP address on the title bar should match the IP address of the node that you entered in Step 2.

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

•Click Tools > Open TL1 Connection.

•Click the Open TL1 Connection buttonon 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 them.

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

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

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

Step 9 Press Enter.

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

Step 10 Type the Cancel User command in the TL1 request window or press the Disconnect button to close a TL1 session:

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

Step 11 Press Enter.

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 an alternative Telnet port.

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 a Craft Interface (Cisco ONS 15454, ONS 15310-CL, and ONS 15310-MA)

The TCC2/TCC2P, XTC, 15310-CL-CTX, and CTX2500 cards have two built-in interface ports for accessing the ONS 15454, ONS 15310-CL, and ONS 15310-MA respectively. 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 Operation, 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 such that TL1 commands can be entered directly without a browser. The ONS 15310-MA has two EIA/TIA-232 ports.

Step 1 Connect the serial cable to the EIA/TIA-232 port on the active TCC2/TCC2P, XTC, 15310-CL-CTX, or CTX2500 card.

Step 2 Configure the terminal emulation software (HyperTerminal):

•Terminal emulation = vt100

•Bits per second = 9600

•Parity = None

•Stop BITS = 1

•Flow control = None

Step 3 Press Enter. An angle bracket prompt (>) appears.

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 a Craft Interface (Cisco ONS 15600)

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.

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, ONS 15310-MA, and ONS 15600 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, ONS 15310-MA, and ONS 15600 are the Hekimian/Spirent BRTU-93 (6750) and the TTC/Acterna Centest 650.

A TAP provides the capability of connecting 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 that 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 the ED-<MOD2> command syntax in the "TAP Creation and Deletion" section. The values are SINGLE and DUAL. It defaults to DUAL.

A single FAD TAP uses half the bandwidth as that of the dual FAD, that is, it uses 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" section. The values are SINGLE and DUAL. The MONEF, SPLTAB, and SPLTEF modes are not supported by single FAD TAPs (Figure 2-2).

Edit an existing port, STS, or VT and change it to a TAP so it can be used when requesting TACC connections. Includes a new optical parameter, TACC=n, that defines the port, STS, or VT as a TAP with a selected unique TAP number. This TAP number will be used when requesting test access connections to circuit cross-connections under test. The TAP creation will fail if there is a cross-connection already on the port, STS, or VT.

Note•This command generates a REPT DBCHG message.

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

•The TAP is a persistent object. It will exist after the user has logged out of the TL1 session.

The following list applies to TAP numbers:

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

•The TAP number is unique across T1/T3/STS/VT/DS1 TAPs in the system.

•The TAP number is not editable.

2.2.2.2 ED-T1

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

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

2.2.2.5 ED-STSn

When the ED-STSn command is issued for a TACC, it assigns the STS for the first two-way test access connection and STS+1 as the second two-way connection. For STS3c, STS9c, STS12c, STS24c, and STS48c, the next consecutive STS of same width is chosen. The TAP creation will fail if either of the consecutive STSs are not available.

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

2.2.2.6 ED-VT1

When the ED-VT1 command is issued for a TACC, a VT TAP is created. The specified VT access identifier (AID) is taken as the first VT connection. The second VT connection is made by incrementing the VT group and keeping the VT number the same.

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

Example 2-6 Create a VT TAP on VT1-1-1-1-1 and VT1-1-1-2-1

ED-VT1-1-1-1-1:12:::TACC=6;
DV9-99 1970-01-02 03:16:11
M 12 COMPLD
;

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

2.2.3 Connect Test Access Points

The connect test access points command (CONN-TACC-<rr>) is used to make a connection between the TAP and the circuit or cross-connect under test.

Connect the port, STS, or VT defined by <AID> to the port, STS, or VT defined by the <TAP> number. The mode of test access to the circuit or cross-connect is specified by <MD>. The mode can be either monitor (nonintrusive), split (intrusive), or loop (intrusive) mode. The various modes are described in the "Test Access Mode Definitions" section.

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.

Use this command to change the type of test access. This might be a change from monitoring the data to inserting data into the STS. 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-9 retrieves TAP information for FAC-1-1.

2.2.8 Test Access Configurations

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

Step 2 CONN-TACC-STS1::<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-3 configuration, there might be a single DS-3 port wired up, configured as 14 dual FADs (28 VTs).

Figure 2-4 Multinode View (MONE Example)

The following commands are performed on NE3:

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

A connection, not a TAP. CTAG is 100.

ENT-CRS-STS1::<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 STS-1-1 and STS-1-2 through NE1. TAP number assigned is 4.

ED-STS1::STS-1-1:TACC=4;

The following command connects TAP 4 to the circuit:

CONN-TACC-STS1::<AID A or B>:102::4:<MD>

Note The I and J connections above are TAPs in Figure 2-3, but normal connections in the Figure 2-4.

2.2.9 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 Affecting and can be applied to an In Service (IS) port state.

LOOPE, LOOPF, SPLTE, SPLTF, SPLTEF, SPLTA, SPLTB, and SPLTAB access modes are intrusive and can be applied only to a circuit or /port that is in the Out Of Service, Maintenance (OOS_MT) port state. The NE will change the state of the circuit under test to OOS_MT 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)

2.2.9.1 MONE

Monitor E (MONE) mode indicates a monitor connection provided from the 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

2.2.9.2 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.

2.2.9.3 MONEF

Monitor EF (MONEF) mode is a monitor connection provided from the FAD1 (odd pair) to 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 mode for T3 (DS3 high capacity digital service [HCDS]) indicates that the odd pair of an FAP is providing a monitor connection to the A transmission path and from the even pair of an FAP to the B transmission path of the accessed circuit.

Figure 2-11 MONEF Access Mode Dual TAP

2.2.9.4 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 on the ONS 15454 and ONS 15310-CL. The connection will remain as is. The ONS 15600 inserts alarm indication signal (AIS) instead of QRS.

Figure 2-12 SPLTE Access Mode Single TAP

Figure 2-13 SPLTE Access Mode Dual TAP

2.2.9.5 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 on the ONS 15454 and ONS 15310-CL. The connection will remain as is. The ONS 15600 inserts AIS instead of QRS.

Figure 2-14 SPLTF Access Mode Single TAP

Figure 2-15 SPLTF Access Mode Dual TAP

2.2.9.6 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 mode for T3 (DS3 HCDS) splits both the A and B paths and connects 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

2.2.9.7 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 on the ONS 15454 and ONS 15310-CL. The connection will remain as is. The ONS 15600 inserts AIS instead of QRS.

Figure 2-17 LOOPE Access Mode Single TAP

Figure 2-18 LOOPE Access Mode Dual TAP

2.2.9.8 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 connects this looped configuration to the FAD (Figure 2-19 and Figure 2-20).

Note QRS is not supported on the ONS 15454 and ONS 15310-CL. The connection will remain as is. The ONS 15600 inserts AIS instead of QRS.

Figure 2-19 LOOPF Access Mode Single TAP

Figure 2-20 LOOPF Access Mode Dual TAP

2.2.9.9 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). This mode is 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

2.2.9.10 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

2.2.10 Unmapped AID Test Access Point Connections

The ONS 15454 and ONS 15600 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 STS-5-3 does not have a cross-connect on it. STS-5-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, UPSR_HEAD, UPSR_DROP, UPSR_DC, UPSR_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.

2.2.10.1 One-Way Circuit

The examples in this section assume that an STS 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).

Note•The same examples apply for UPSR_HEAD, UPSR_DROP, UPSR_DC and UPSR_EN, which are all one-way circuits.

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

2.2.10.2 Two-Way Circuits

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

1If the AID specified is the source AID, the direction is designated as "from E" in all one-way circuits (1-way, UPSR_HEAD, UPSR_DROP,UPSR_DC, and UPSR_EN).

2If the AID specified is the destination AID or the drop side, the direction is designated as "from F" in all one-way circuits (1-way, UPSR_HEAD, UPSR_DROP,UPSR_DC, and UPSR_EN).

2.3 TL1 Gateway

This section describes the TL1 gateway and provides procedures and examples for implementing TL1 gateway on the ONS 15454, ONS 15310-CL, ONS 15310-MA, and ONS 15600.

2.3.1 Gateway Network Element Topology

You can issue TL1 commands to multiple nodes through a single connection using 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 need to enter the ENE's TID in all of the 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 operations 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

2.3.2 TL1 Sessions

Each NE can support up to a maximum of 20 concurrent communication sessions (connections from an OS/NE to the GNE). The TL1 connections can be made through telnet sessions from the LAN or from the craft/serial port connection on the NE. One TL1 session is reserved for the active serial port connection. The remaining 19 sessions are used for TL1 sessions through the LAN (wire-wrap, active serial port, or DCC). Table 2-4 shows the number of serial port and LAN connections per platform.

Table 2-4 Number of TL1 Sessions per Platform

Platform

Number of Serial Port Sessions

Number of LAN Sessions

Total Number of TL1 Sessions

Cisco ONS 15454

1

19

20

Cisco ONS 15310-CL

1

19

20

Cisco ONS 15310-MA

2

18

20

Cisco ONS 15600

2

18

20

2.3.3 TL1 Gateway and ENE Sessions

Only a limited number of TL1 users logged into an NE at any given time can establish sessions to other ENEs. The active serial port sessions are reserved and can always become a GNE session. The number of ENE sessions is based on the number of gateway communications sessions (GNE sessions).

Each NE can support up to 12 concurrent communication gateway sessions, depending on the NE type. The maximum number of ENE sessions also varies depending on the NE type.

You can dynamically distribute the maximum number of ENE sessions to balance the number of concurrent gateway communication sessions. The GNE treats the concurrent gateway communication sessions and ENE/GNE limit as a resource pool. It continues to allocate resources until the pool is exhausted. When the pool is exhausted, the GNE returns an "All Gateways in Use" message or an "All ENE Connections in Use" message.

Note The speed of the TL1 gateway and the maximum number of connections are limited by shared system resources, such as CTC, CTM, etc. The response time is slow as connections are increased and activity on these connections increases. Alarm storms, additional users, netwoork latency, etc. also increase response time.

Note Every ENE over an OSI DCC is equivalent to two ENEs over an IP DCC. If you use a combination of IP and OSI ENE sessions, it is important to remember that the maximum number of ENEs supported is equal to the number if IP ENEs plus two times the number of OSI ENEs (IP + 2*OSI).

For example, for Cisco ONS 15454 GNE, if you use 100 ENEs over IP DCC, then you can use only 38 ENEs over OSI DCC (100 + 2*38 = 176). For Cisco ONS 15310-MA GNE, if you use 30 ENEs over OSI DCC, then you can use only 52 ENEs over IP DCC (2*30+52 = 112).

2.3.4 Implementing TL1 Gateway

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.

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)

When you are logged into ENE 1 and ENE 3, enter a command and designate a specific TID. To retrieve the header of Node 1, enter the following command:

RTRV-HDR:NODE1::1;

To retrieve the header of Node 3, enter the following command:

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. Use the following command to disconnect from ENE 1:

CANC-USER:NODE1:USERNAME:1;

Use the following command to disconnect from ENE 3:

CANC-USER:NODE3:USERNAME:3;

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

2.4 Ring Provisioning

This section provides information and sample procedures for setting up STS or VT circuits over existing path protection and bidirectional line switch ring (BLSR) configurations using TL1, including:

•Path Protection topology

•Path Protection cross-connections

•Ring-to-ring interconnection

•One-way drop and continue

For VTs, add the normal VT Group and VT 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 IS state using a port configuration command, for example, ED-OCN.

Note Because the ONS 15454, ONS 15310-CL, and ONS 15600 implement logical path protection, there are no defined east and west ports. Instead, the east STS path for one circuit can exit a different port than the east STS path of another circuit, even though the west STS paths for both circuits might share the same port.

Note The ONS 15310-CL and ONS 15310-MA do not support BLSR.

2.4.1 Two-Fiber BLSR to Two-Fiber BLSR Connection Example

All protection for a two-fiber BLSR interconnecting to a two-fiber BLSR is performed at the line level. You can make the connection with a two-way cross-connect from an STS on the working side of the two-fiber BLSR span of Ring 1 to an STS on the working side of a two-fiber BLSR 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-28, uses Ring 1 west to Ring 2 east and assumes an OC12-4 card in Slots 12 and 13 for subtending to a two-fiber BLSR (Ring 2).

Figure 2-28 Two-Fiber BLSR to Two-Fiber BLSR

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

All protection for a two-fiber BLSR interconnecting to a four-fiber BLSR 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 BLSR to the working fiber of the appropriate side, east or west, of the four-fiber BLSR, as shown in Figure 2-30.

Figure 2-30 Two-Fiber BLSR to Four-Fiber BLSR

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

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-34.

Figure 2-34 Bridge From 5/1/190 to Ring 1 (1/1/1 and 2/1/1)

2.4.4 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-35). Node 1 is the source node, Node 2 has the drop and continue, and Node 3 is the destination.

Figure 2-35 One-Way Drop and Continue

Figure 2-36 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-36 Orientation of AIDs Used to Establish Drop and Continue Connections

2.4.4.1 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-37):

ENT-CRS-STSn::STS-1-1,STS-5-1&STS-6-1:CTAG::1WAY;

Figure 2-37 Bridge from 1/1/1 to 5/1/1 and 6/1/1

2.4.4.2 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-38):

ENT-CRS-STSn::STS-5-1&STS-6-1,STS-1-1:CTAG::1WAYDC;

Figure 2-38 Selector Between 5/1/1 and 6/1/1 to 1/1/1

2.4.4.3 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-39):

ENT-CRS-STSn::STS-5-1&STS-6-1,STS-1-1:CTAG::1WAY;

Figure 2-39 Selector Between 5/1/1 and 6/1/1 to 1/1/1

2.5 PCA Provisioning

You can provision or retrieve protection channel access (PCA) cross-connections on two-fiber and four-fiber BLSR topologies at these supported OC rates: OC-12 (two-fiber only), OC-48, and OC-192. 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 BLSR, the extra traffic is provisioned on the upper half of the bandwidth path. In a four-fiber BLSR, 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 BLSR and the protection channel of the four-fiber BLSR 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-STSp/VT1 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-STSp/VT1 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.

The following restrictions apply to PCA provisioning:

•Cisco ONS 15600 does not support BLSR for OC-12.

•The network must be configured as either a two-fiber or four-fiber OC-12, OC-48, or OC-192 BLSR.

•The STS or VT1 path cross-connection can be established with TL1 commands (ENT-CRS-xxx).

•Because the RTRV-CRS-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 include both PCA and non-PCA cross-connections.

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 is/are the PCA AIDs, an IIAC (The PCA AID Is Not Allowed for the Queried CCT Type) error message is returned.

2.5.2 Retrieve a PCA Cross-Connection

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

2.6.1 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 either the TCC2/TCC2P, XTC,15310-CL-CTX, CTX2500, or TSC card. COPY-RFILE can also be used to backup 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 used 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. 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 host name 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.

Note•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.

2.6.2 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 the node is attempting to activate to an older software load or trying to revert to a newer software load. If this command is successful, the appropriate flash is selected and the TCC2/TCC2P, XTC, 15310-CL-CTX, CTX2500, or 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 the memory switch action during the software upgrade.

2.6.3 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 userid/password, and loss of network connection.

•<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 5 Issue the COPY-RFILE command. This command will initiate the download process. See the "COPY-RFILE" section for command syntax.

In Example 2-19, the package is located in "/%2FUSR/CET/VINTARA" in the host 10.77.22.199. The user ID and passwords are TL1 and CISCO454. 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 sessio,n the download will continue. The download completion can be confirmed by issuing the RTRV-NE-GEN command and verifying the PROTLOAD (Example 2-25).

2.6.5 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" section 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:53M 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:18M 1 COMPLD;

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.

2.6.6 Remote Software Download/Activation Using the GNE

In a network with Section data communications channel (SDCC)-connected ONS 15454s, ONS 15310-CLs, and ONS 15310-MAs, 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 20 (TCC2/TCC2P) or 6 (XTC, 15310-CL-CTX, CTX2500) concurrent communication gateway sessions and up to a maximum of 176 (TCC2/TCC2P) or 96 (XTC, 15310-CL-CTX, CTX2500) ENEs/GNEs. For more information on TL1 gateway, see the "TL1 Gateway" section.

After activating the nodes (Example 2-28), five simultaneous software downloads can be initiated using the COPY-RFILE command with appropriate TIDs, as shown in Example 2-29. 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-30. 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.

2.7 Scheduled PM Report

The scheduled performance monitoring (PM) 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 a scheduled PM report, the system automatically and periodically generates the PM report of any specified facility or cross-connection.

Note•The current maximum number of schedules allowed to be created for an NE is 1000. If the limit has been reached and the user tries to create more schedules on the NE, the error message "Reach Limits Of MAX Schedules Allowed. Can Not Add More" is returned.

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

•An 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 (and the parameter <NUMINVL> is equal to zero when retrieved by the RTRV-PMSCHED command, which means that no more performance monitoring reports are 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.

2.7.1 Create a PM Schedule and Receive an Autonomous PM Report

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.

2.7.2 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 10 times. After 10 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 RTRV-PMSCHED.

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.

2.8 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 Procedure Guide for the procedure.

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

2.9 Bridge and Roll

Bridge and Roll functionality in the Cisco ONS 15454, ONS 15310-CL, ONS 15310-MA, and ONS 15600 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:

•Path Level Rolling—Rolls cross-connections at the VT1.5, STS1, and STSNc rate for all supported time division multiplexing (TDM) drops (OC3, OC12, OC48, and OC192). Individual rolls are done at the Path level.

•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 an STS3c starting at STS#1, you cannot roll it to another port and start it at STS#2. You have to start it at STS#1.

2.9.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 BLSR protected circuit cannot violate the rules governing BLSR circuits: a circuit that traverses a BLSR must use the same STS number on the ring between source and destination.

•Rolling on a BLSR 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 a path protection protected circuit cannot violate the rules governing path protection circuits: path protection circuits must have one bridge and one selector.

•In the case of a dual roll on a path protection 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 path protection protected circuit, the "roll to" cannot be line protected (1+1 or BLSR 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 VT tunnels or VT aggregation point (VAP) circuits passing through less than four nodes.

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

•For VCAT circuits that are not open-ended, 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.

2.9.2 Bridge and Roll TL1 Commands

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

•DLT-BULKROLL-<OCN_TYPE>

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

•DLT-ROLL-<MOD_PATH>

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

•ED-BULKROLL-<OCN_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 rolling and bulk rolling. It 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-<OCN_TYPE>

This command enters information about rolling traffic from one endpoint to another without interrupting service. This commands supports Line-level and bulk rolling. It 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 STS and VT Path-level rolling only.

•RTRV-BULKROLL-<OCN_TYPE>

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

•RTRV-ROLL-<MOD_PATH>

This command retrieves roll data parameters.

2.9.3 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: onto the same node or onto a different node. In a 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. 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

In dual roll operation, you choose two roll points during the 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-<OCN_TYPE> command depending on the type of roll you want to perform.

Step 2 If you performed a manual roll, you must confirm the circuit is valid by issuing the RTRV-BULKROLL-<OCN_TYPE> command:

Input format:

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

Input example:

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

2.9.4 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: 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-<OCN_TYPE> command depending on the type of roll you want to perform.

2.9.5 Protection Rolling Procedures

Note Before performing a protection roll, either from one protection group to another or within the same protection group, the protection group must already be provisioned.

Table 2-11 shows what kind of protection rolls are supported from one domain to another. An X indicates the roll is allowed. A dash indicates that the roll is not allowed.

Table 2-11 Supported Protection Rolls

Roll From Domain

Roll To Domain

BLSR

PCA

1+1

Path Protection

Unprotected

BLSR

X

X

X

—

X

PCA

X

X

X

—

X

1+1

X

X

X

—

X

Path Protection

—

—

—

X

—

Unprotected

X

X

X

—

X

2.10 1:N Low-Density to 1:N High-Density Upgrade

In the Cisco ONS 15454, DS1 electrical cards can be upgraded to DS1/E1-56 high-density cards using TL1. This procedure can be performed only when logged in as a Superuser.

Note•Protect cards must be upgraded before working cards because working cards cannot have more capabilities than their protect card.

•You cannot upgrade electrical cards from low-density to high-density if the low-density electrical cards are installed in Slots 4, 5 or 6 on the A side or 12, 13 or 14 on the B side of the shelf. Only cards in slots 1, 2, 16 and 17 can be upgraded to high-density electrical cards.

Note Cisco ONS 15600 does not support RMONTH commands. For ONS 15600, RMON counts can be retrieved using TL1 commands, but RMON thresholds cannot be set using TL1.

The cards that support RMON PMs include: G1K-4, CE-1000-4, ML1000-2/ML100T-12, FC_MR-4, ASAP-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 standard Simple Network Management Protocol (SNMP)/RMON MIBs, and also include other statistic types managed by RMON, for example, the Fibre Channel statistic 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.

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

2.11.1 RTRV-PM-<MOD2>

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

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

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 MONDATE and MONTIME in the output will be the last time the counters were cleared. RAW-DATA will be 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 MONYYPR is specified, an error message will be returned.

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

The TMPER parameter specified is not applicable for the MOD2 type. For example, 1-MIN is not applicable for OC48 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.

2.11.2 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 startup type of RISING-OR-LTING.

The rising/falling threshold is less than 0, or the falling threshold is greater than or equal to 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 thresholds created has reached the maximum (256).

IIDT

Duplicate RMON Threshold

There already is a threshold created with the exact same parameters.

2.11.3 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 startup type of BOTH.

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

IDNV

Invalid MONTYPE value

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

SROF

RMON Threshold Does Not Exist

The RMON threshold you are trying to delete does not exist.

2.11.5 REPT EVT <MOD2ALM> for Threshold Crossing Events

The REPT EVT <MOD2ALM> autonomous message reports the threshold crossing event for the RMON statistics. The high threshold (HT) designator is generated when crossing the RISING threshold. The low threshold (LT) is generated when crossing the FALLING threshold.

The table index for thresholds in the RMON alarm table is enclosed in the text of the TCA description. This table index also appears in the output of the RTRV-RMONTH command. 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.

2.11.6 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>.

2.11.7 SCHED-PMREPT-<MOD2>

This command schedules/reschedules the NE to report the performance monitoring data.

The three accumulation time periods form RMON statistics are: 1-MIN, 1-HR, and RAW-DATA.

2.11.8 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.

2.11.9 REPT PM <MOD2>

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>.

2.11.10 REPT DBCHG

Reports any changes on 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.

2.11.11 MONTYPE and CONDEF Defined 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 request for comment (RFC)1757.

Unlike the PM parameters of other SONET entities (such as STS path and OCn), there are two CONDEFs defined for the TCAs of each RMON-managed statistics type: Ethernet or Fibre Channel MONTYPE. One CONDEF is for the rising threshold, and the other is for the falling threshold. For example, there are two CONDEFs 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.

24 hours of history data are available for this accumulation interval length.

RAW-DATA

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

2.11.12.2 SAMPLE_TYPE

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

Table 2-17 SAMPLE_TYPE

Value

Description

ABSOLUTE

Comparing directly.

DELTA

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

2.11.12.3 STARTUP_TYPE

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

Table 2-18 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 the rising or falling threshold.

2.11.13 Notes for DWDM Card Types

The PM for client port and/or optical channel (OCH) can include both the RMON-managed PM and the SONET 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

2.11.13.1 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 SONET PM. Therefore, the behavior of the RTRV-PM-<MOD2>, 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 SONET optics PM. When the LOCN or DIRN parameter is specified, it only applies to the SONET optics PM.

•Because 1-MIN, 1-HR, or RAW-DATA are not applicable to the SONET optics PM, no SONET optics PM would be returned in the output of RTRV-PM. If RAW-DATA is specified in the input of the INIT-REG command, no SONET optics 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 the SONET optics 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 the RMON PM does not have current bucket.

•A SONET optics PM MONTYPE cannot be specified in the input of the INIT-REG command. Only the SONET optics PM counters will be cleared. When the ALL MONTYPE is specified, both the RMON and the SONET optics PM counters will be 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 SONET optics 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 command would be used to create an RMON threshold:

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

In the same client port, the following command would be used to set the SONET the optics PM threshold:

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

2.11.13.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 SONET PMs, when their client port is provisioned as GIGE, 10GIGE, 1GFC, 2GFC, or 10GFC.

2.12 Rules for Framing Type Autoprovisioning in CTC Versus TL1

The DS3, DS3E, DS3XM, DS3i, and DS1 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 DS3, DS3E, DS3XM, DS3i, and DS1 cards to autoprovision. The FMT field will blank out for a few seconds while the card is determining 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 DS3, DS3E, DS3XM, DS3i, and DS1 cards; it only supports unframed, M23, or CBit. If autoprovision is selected from CTC and at the same time the TL1 command RTRV-T3 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-T3 command (after CTC sets the FMT to autoprovision) will indicate the FMT field as unframed.

2.13 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

2.13.1 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.

2.13.2 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 Out-of-Service and Management, Disabled (OOS-MA,DSBLD) state because this change is service affecting.

–The 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-AIS or TRANSPARENT-SQUELCH (TRANSPARENT-SQUELCH is only supported on TXP_MR_10E).

•To set the payload to a speed other than OC-3, OC-12, OC-48, or OC-192, 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.

The TL1 commands for provisioning payload are:

•ENT-(OCn, nGIGE, nGFC, 2R)

•DLT-(OCn, nGIGE, nGFC, 2R)

•ED-(OCn, nGIGE, nGFC, 2R)

2.13.3 OC-N Payload Provisioning Parameters

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

1If 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.

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

•DCC parameters are used to enable and disable SDCC functionality.

•Line DCC (LDCC) parameters are used to enable and disable LDCC functionality.

•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 can be provisioned using the SFBER parameter.

•Signal degrade can be provisioned using the SDBER parameter.

•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.

2.13.4 Termination Mode Provisioning Rules

Use the following rules when provisioning the termination mode:

•This is a card-level operation.

•Termination mode is only applicable to the OC-3, OC-12, OC-48, and OC-192 payload types.

•Changing termination mode requires the following:

–All ports must be in the Out of Service (OOS) state because this change is traffic-affecting.

–All ports must not have DCC terminations (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 modes are supported for the OC-3, OC-12, OC-48, and OC-192 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-32 sets the termination mode of the card in Slot 1 to DWDM-LINE.

Example 2-32 Set the Termination Mode

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

2.13.5 Wavelength Provisioning Rules

Use the following rules when provisioning the wavelength:

•Changing the trunk wavelength requires that all trunk ports must be in the OOS state, because this change is service-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 set the 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;

2.13.6 Regeneration Group Provisioning Rules

Use the following rules when provisioning the regeneration group:

•Both 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 will be 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.

•The peer-slot must not be itself.

•The peer-slot must be provisioned or preprovisioned.

•The peer-slot must not be part of another regeneration group.

•The peer-slot must not be part of a Y-cable protection group.

•Both cards must have the same card type.

•Both cards must have the same payload type and data rate.

•Both cards must have the same ITU-T G.709 OTN status.

•Both cards must have the same FEC status.

•Termination mode must 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;

2.13.7 DCC/GCC Provisioning Rules

Use the following rules when provisioning DCC and GCC:

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

•2R payload types do not support GCC.

•To provision a DCC, the payload data type must be set to OC-3, OC-12, OC-48, or OC-192.

•To provision a DCC, the termination mode must be 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 the ITU-T G.709 OTN status is turned off:

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

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

•Only the working client port in a Y-cable protection scheme can be provisioned with DCC.

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

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

ED-OC192::FAC-1-1-1:100:::COMM=DCC:OOS,AINS;

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

ED-OCH::CHAN-6-2:114::COMM=GCC:OOS,AINS;

2.13.8 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.

–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 OOS state.

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

•The section trace received string should appear when the card is in TRANSPARENT-AIS or TRANSPARENT-SQUELCH termination mode and the payload is OC-3, OC-12, OC-48, or OC-192.

•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, trace can only be provisioned on the working port. However, the provisioning will be duplicated between the two ports, that is, both ports will 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 SONET equipment.

Use the ED-OCn command for trace provisioning of client ports provisioned for OCn payload, as shown in the following example:

2.13.11 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.

2.13.12 PM and Alarm Threshold Provisioning Rules

Use the following rules when provisioning PM parameters and alarm thresholds:

•When the framing type is unframed, for example, HDTV and DV6000, only optics threshold provisioning and PM are applicable. Support for optics threshold provisioning and PM depends on the ESCON SFP type.

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

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

•The FEC thresholds are only applicable if 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 the working and protect ports.

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

SET-TH-OC48::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-(OCn, nGIGE, nGFC, OCH) command to retrieve port-level thresholds, for example:

RTRV-PM-OC48::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:

2.13.13 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 cannot be part of a regeneration group.

•Only the working client port can be provisioned with SDCC.

•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-(OCn, nGIGE, nGFC), DLT-FFP-(OCn, nGIGE, nGFC), and ED-FFP-(OCn, nGIGE, nGFC) commands to provision Y-cable protection groups, as shown in the following examples:

2.13.15 Loopback Provisioning Rules

•Loopback is not applicable when the framing type is UNFRAMED (HDTV, DV6000).

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

–Only one loopback can be provisioned at the trunk ports at any given time.

–Loopback is allowed only if the sibling trunk port is OOS-MT.

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

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

–A loopback will be 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 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;

2.13.16 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 port 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-(OCn, nGIGE, nGFC, OTS, OMS, OCH) commands to provision ALS, as shown in the following examples:

2.13.17 Port State Model Provisioning Rules

•The Out of Service, Automatic In-Service (OOS,AINS) port service state is not supported for the 1GigE and 2GigE payload types.

•The working and protect ports can be put in the IS and OOS states independently.

•For the protect TXP card:

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

–Setting the protect trunk port to OOS will not switch off the transmit laser unless both trunk ports are OOS.

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

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

ED-OC48::FAC-6-1-1:114::::OOS,AINS;

ED-10GIGE::FAC-6-1:114::::OOS,AINS;

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

2.13.18 SONET-Related Provisioning Rules

When provisioning SONET-related parameters, 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 SONET trunk port attributes, as shown in the following example: