The Automatic Laser Shutdown (ALS) procedure is supported on both client and trunk interfaces. On the client interface, ALS is compliant with ITU-T G.664 (6/99). On the data application and trunk interface, the switch on and off pulse duration is greater than 60 seconds and is user-configurable.

For information on ALS provisioning, refer the following procedures, as necessary:

• NTP-G162 Changing the ALS Maintenance Settings

• DLP-G203 Changing the ALS Maintenance Settings for OSCM and OSC-CSM Cards

• DLP-G322 Changing the ALS Maintenance Settings for OPT-BST Card

Multiple colored LEDs indicate the status of the card.

For the following cards, the status of the card ports is indicated on the LCD screen of the ONS 15454 fan-tray assembly that displays the number and severity of alarms for a given port or slot.

• OPT-PRE, OPT-BST, OPT-BST-E, and OPT-BST-L

• OPT-AMP-L, OPT-AMP-17-C, and OPT-AMP-C

• OPT-RAMP-C and OPT-RAMP-CE

• RAMAN-CTP and RAMAN-COP

• EDRA-1-26, EDRA-1-35, EDRA-2-26, and EDRA-2-35

• OSCM and OSC-CSM

• 32MUX-O and 32DMX-O

• 4MD-xx.x

• 32WSS and 32WSS-L

• 32DMX, 32DMX-L, 40-DMX-C, 40-DMX-CE, and 40-MUX-C

• 40-WSS-C, 40-WSS-CE, 40-WXC-C, 80-WXC-C, and 16-WXC-FS

• 40-SMR1-C, 40-SMR2-C, 17 SMR9 FS, 24 SMR9 FS, 34 SMR9 FS, and SMR20 FS

• MMU

• OPT-EDFA-17 and OPT-EDFA-24

In some cards, multiple colored LEDs indicate the status of the port.

Port-Level LEDs for AR_MXP, AR_XP, and AR_XPE cards depend on the configured card mode.

The following table lists the port-level LEDs on the following cards:

• TXP_MR_10E, TXP_MR_10E_C, and TXP_MR_10E_L

• TXP_MR_2.5G and TXP_MR_10EX_C

• 40E-TXP-C and 40ME-TXP-C

• MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, and MXP_2.5G_10EX_C

The following table lists the port-level LEDs on the following cards:

• GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE

• MXP_MR_10DME_C, MXP_MR_10DME_L, and MXP_MR_10DMEX_C

• 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C

The client interface in TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, and TXP_MR_10EX_C cards is implemented with a separately orderable XFP module. The module is a tri-rate transceiver, providing a single port that can be configured in the field to support an OC-192 SR-1 (Telcordia GR-253-CORE) or STM-64 I-64.1 (ITU-T G.691) optical interface, as well as 10GE LAN PHY (10GBASE-LR), 10GE WAN PHY (10GBASE-LW), 10G FC signals or IB_5G signals (TXP_MR_10EX_C only).

The client side XFP pluggable module supports LC connectors and is equipped with a 1310-nm laser.

The MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, and MXP_2.5G_10EX_C cards provide four intermediate- or short-range OC-48/STM-16 ports per card on the client side. Both SR-1 or IR-1 optics can be supported and the ports use SFP connectors. The client interfaces use four lasers of 1310-nm wavelength.

The client interface in AR_MXP, AR_XP, and AR_XPE cards are implemented with a separately orderable XFP/SFP module. The module can be single-rate or tri-rate transceiver, providing a single port that can be configured in the field to support available payloads. For the list of supported payloads, see the section.

The MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, and MXP_2.5G_10EX_C cards serve as an OTN multiplexer, transparently mapping four OC-48 channels asynchronously to ODU1 into one 10-Gbps trunk. The tunable wavelengths for the DWDM trunk is as follows:

• MXP_2.5G_10E—Tunable for transmission over four wavelengths in the 1550-nm, ITU 100-GHz spaced channel grid.

• MXP_2.5G_10E_C and MXP_2.5G_10EX_C—Tunable for transmission over the entire C-band and the channels are spaced at 50-GHz on the ITU grid.

• MXP_2.5G_10E_L—Tunable for transmission over the entire L-band and the channels are spaced at 50-GHz on the ITU grid.

• AR_MXP, AR_XP, and AR_XPE—The wavelengths for the DWDM trunk is based on the pluggable.

  • 100G-LC-C, 10X10G-LC, CFP-LC, 100G-ME-C, 100GS-CK-LC, 200G-CK-LC, 100G-CK-C, and 100ME-CKC—Tunable on 96 wavelength channels spaced at 50-GHz on the ITU grid over the entire C band.

    Caution

    You must use a 20-dB fiber attenuator (15 to 25 dB) when working with the card in a loopback on the trunk port. Do not use direct fiber loopbacks as it can cause irreparable damage to the card.

    Note	On the MXP_2.5G_10EX_C card, you cannot disable ITU-T G.709 on the trunk side. If ITU-T G.709 is enabled, then FEC cannot be disabled.

On the trunk side, the TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, and TXP_MR_10EX_C cards provide a 10-Gbps STM-64/OC-192 interface. There are four tunable channels available in the 1550-nm band or eight tunable channels available in the 1580-nm band on the 50-GHz ITU grid for the DWDM interface. The card provides 3R (retime, reshape, and regenerate) transponder functionality for this 10-Gbps trunk interface. Therefore, the card is suited for use in long-range amplified systems. The DWDM interface is complaint with ITU-T G.707, ITU-T G.709, and Telcordia GR-253-CORE standards.

The DWDM trunk port operates at a rate that is dependent on the input signal and the presence or absence of the ITU-T G.709 Digital Wrapper/FEC. The possible trunk rates are:

• OC192 (9.95328 Gbps)

• OTU2 (10.70923 Gbps)

• 10GE (10.3125 Gbps) or 10GE into OTU2 (ITU G.sup43 11.0957 Gbps)

• 10G FC (10.51875 Gbps) or 10G FC into OTU2 (nonstandard 11.31764 Gbps)

• (TXP_MR_10EX_C only) Proprietary rate at the trunk when the client is provisioned as IB_5G.

The maximum system reach in filterless applications without the use of optical amplification or regenerators is nominally rated at 23 dB over C-SMF fiber. This rating is not a product specification, but is given for informational purposes. It is subject to change.

On the trunk side, the AR_MXP, AR_XP, and AR_XPE cards provide a 10-Gbps OTU2 or 2.5-Gbps OTU1 or 4-Gbps FC interfaces. The trunk wavelength can be tuned to any C-band wavelength, based on the pluggable inserted. The card provides 3R (retime, reshape, and regenerate) transponder functionality for this 10-Gbps trunk interface. Therefore, the card is suited for use in the long-range amplified systems. The DWDM interface is complaint with ITU-T G.707, ITU-T G.709, and Telcordia GR-253-CORE standards. The DWDM trunk port operates at a rate that is dependent on the input signal and the presence or absence of the ITU-T G.709 Digital Wrapper/FEC.

The maximum system reach in filterless applications without the use of optical amplification or regenerators is nominally rated at 23 dB over C-SMF fiber. This rating is not a product specification, but is given for informational purposes. It is subject to change.

Forward error correction (FEC) is a feature used for controlling errors during data transmission. This feature works by adding data redundancy to the transmitted message using an algorithm. This redundancy allows the receiver to detect and correct a limited number of errors occurring anywhere in the message, instead of having to ask the transmitter to resend the message.

The TCC2/TCC2P/TCC3 card performs all system-timing functions for each ONS 15454. The TNC/TNCE/TSC/TSCE/TNCS card performs all the system-timing functions for the ONS 15454 M2, ONS 15454 M6, and ONS 15454 M15 shelves.

Note	Due to memory limitations, TCC2/TCC2P cards are not supported from Release 10.5.2 onwards. As a result, in a multishelf configuration, the TCC2/TCC2P card cannot be a node controller or a shelf controller. Upgrade the TCC2/TCC2P card to a TCC3 card.

The control card monitors the recovered clocks from each traffic card and two BITS ports for frequency accuracy. The control card selects a recovered clock, a BITS, or an internal Stratum 3 reference as the system-timing reference. You can provision any of the clock inputs as primary or secondary timing sources. A slow-reference tracking loop allows the control card to synchronize with the recovered clock, which provides holdover if the reference is lost. The control card supports 64/8K composite clock and 6.312 MHz timing output.

Note	The TNC/TNCE/TSC/TSCE/TNCS card supports the BITS-1 and BITS-2 external timing interfaces on the ONS 15454 M6 and NCS 2015 shelves. The card supports the BITS-1 interface on the ONS 15454 M2 shelf.

The TNC/TNCE/TSC/TSCE/TNCS card supports SNTP operation that allows the nodes to synchronize the system clock automatically with a reference SNTP server following system reboots, card resets, and software upgrades.

For more information on the timing function, see Timing Reference document.

The MXP_2.5G_10G card is synchronized to the the control card clock during normal conditions and transmits the ITU-T G.709 frame using this clock. The control card can operate from an external building integrated timing supply (BITS) clock, an internal Stratum 3 clock, or from clock recovered from one of the four valid client clocks. If clocks from both the control cards are not available, the MXP_2.5G_10G card switches automatically (with errors, not hitless) to an internal 19.44 MHz clock that does not meet SONET clock requirements. This will result in a clock alarm.

The MXP_2.5G_10E and MXP_2.5G_10EX_C cards are synchronized to the control clock and the MXP_2.5G_10E_C and MXP_2.5G_10E_L cards are synchronized to the control card clock during normal conditions and transmits the ITU-T G.709 frame using this clock. No holdover function is implemented. If neither control clock is available, the cards switch automatically (hitless) to the first of the four valid client clocks with no time restriction as to how long it can run on this clock. The cards continue to monitor the control card. If a control card is restored to working order, the cards revert to the normal working mode of running from the control-card clock. If no valid control-card clock is available and all of the client channels become invalid, the cards wait (no valid frames processed) until the control card supplies a valid clock. In addition, the cards can select the recovered clock from one active and valid client channel and supply that clock to the control card card.

The AR_MXP, AR_XP, and AR_XPE cards are able to transparently transport synchronization and timing information for payload enveloped within ODU-1 and ODU-2. The AR_MXP and AR_XP cards are synchronized to the control card clock during normal conditions and transmit the ITU-T G.709 frame using this clock. The AR_XPE card is synchronized to the control card clock during normal conditions and transmit the ITU-T G.709 frame using this clock. The AR_MXP, AR_XP, and AR_XPE cards select its synchronization source between an optical line, an external synchronization input, and the internal source. The optical line can be either OCN, OTN or Ethernet based. The AR_MXP and AR_XP cards transmit the SyncE information from an incoming SyncEthernet (ITU-T G.8262 and G.8264 ESMC) signal to the node controller (TNC).

The 100G-LC-C, 10x10G-LC, CFP-LC, 100G-ME-C, 100G-CK-C, and 100ME-CKC cards are synchronized to TNC/TSC/TNCE/TSCE/TNCS clock during normal conditions and transmits the ITU-T G.709 frame using this clock.

The 100GS-CK-LC and 200G-CK-LC cards cannot be used as a timing reference source.

Note	Only one port per card can be selected as a timing reference. The OTN ports configured as clients shall not be provisionable as timing source.

The muxponder is an integral part of the reconfigurable optical add/drop multiplexer (ROADM) network. The key function of the MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, MXP_2.5G_10EX_C, AR_MXP, AR_XP, and AR_XPE cards is to multiplex 4 OC-48/STM16 signals onto one ITU-T G.709 OTU2 optical signal (DWDM transmission). The multiplexing mechanism allows the signal to be terminated at a far-end node by another similar card.

Termination mode transparency on the muxponder is configured using OTUx and ODUx OH bytes. The ITU-T G.709 specification defines OH byte formats that are used to configure, set, and monitor frame alignment, FEC mode, section monitoring, tandem connection monitoring, and termination mode transparency.

The card performs ODU to OTU multiplexing as defined in ITU-T G.709. The ODU is the framing structure and byte definition (ITU-T G.709 digital wrapper) used to define the data payload coming into one of the SONET/SDH client interfaces on the card. The term ODU1 refers to an ODU that operates at 2.5-Gbps line rate. On the card, four client interfaces can be defined using ODU1 framing structure and format by asserting an ITU-T G.709 digital wrapper.

The output of the muxponder is a single 10-Gbps DWDM trunk interface defined using OTU2. It is within the OTU2 framing structure that FEC or E-FEC information is appended to enable error checking and correction.

The MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, MXP_2.5G_10EX_C, AR_MXP, AR_XP, AR_XPE, 100G-LC-C, 10x10G-LC, CFP-LC, 100G-CK-C, 100GS-CK-LC, 200G-CK-LC, 100G-ME-C, and 100ME-CKC cards pass the incoming SONET/SDH data stream and its overhead bytes for the client signal transparently. The card can be provisioned to terminate regenerator section overhead. This is used to eliminate forwarding of unneeded layer overhead. It can help reduce the number of alarms and help isolate faults in the network.

The following parameters are monitored on the MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, MXP_2.5G_10EX_C, AR_MXP, AR_XP, AR_XPE, 100G-LC-C, 10x10G-LC, CFP-LC, 100G-CK-C, 100GS-CK-LC, , 200G-CK-LC, 100G-ME-C, and 100ME-CKC cards:

• Laser bias current is measured as a PM parameter

• LOS is detected and signaled

• Transmit (TX) and receive (RX) power are monitored

The following parameters are monitored in real time mode (one second):

• Optical power transmitted (client)

• Optical power received (client)

In case of loss of communication (LOC) at the DWDM receiver or far-end LOS, the client interface behavior is configurable. AIS can be invoked or the client signal can be squelched.

For SONET and SDH signals, the MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, MXP_2.5G_10EX_C, AR_MXP, AR_XP, AR_XPE cards comply with Telcordia GR-253-CORE, ITU-T G.825, and ITU-T G.873 for jitter generation, jitter tolerance, and jitter transfer. For more information, see the Jitter Considerations.

The MXP_2.5G_10E, MXP_2.5G_10E_C and MXP_2.5G_10E_L, MXP_2.5G_10EX_C, AR_MXP, AR_XP, AR_XPE, TDC-CC, TDC-FC, TNC, TNCE, TSC, TSCE, TNCS, RAMAN-CTP, and RAMAN-COP cards support lamp test function activated from the shelf front panel or through CTC to ensure that all LEDs are functional.

The Lamp Test is run during the initial node turn-up, periodic maintenance routine, identification of specific cards, or LED testing.

The MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, and MXP_2.5G_10EX_C cards provide internal traffic generation for testing purposes according to pseudo-random bit sequence (PRBS), SONET/SDH, or ITU-T G.709.

GFP-T performance monitoring (GFP-T PM) in MXP_MR_2.5G, MXPP_MR_2.5G, AR_MXP, AR_XP, AR_XPE, 100G-LC-C, 10x10G-LC, 100G-CK-C, 100GS-CK-LC, 200G-CK-LC, 100G-ME-C, and 100ME-CKC cards are available via remote monitoring (RMON), and trunk PM is managed according to Telcordia GR-253-CORE and ITU G.783/826. Client PM is achieved through RMON for FC and GE.

In MXP_MR_2.5G and MXPP_MR_2.5G cards, buffer-to-buffer credit management scheme provides FC flow control. When this feature is enabled, a port indicates the number of frames that can be sent to it (its buffer credit), before the sender is required to stop transmitting and wait for the receipt of a “ready” indication The MXP_MR_2.5G and MXPP_MR_2.5 cards support FC credit-based flow control with a buffer-to-buffer credit extension of up to 1600 km (994.2 miles) for 1G FC and up to 800 km (497.1 miles) for 2G FC. The feature can be enabled or disabled, as necessary.

You can provision a string (port name) for each fiber channel/FICON interface on the MXP_MR_2.5G and MXPP_MR_2.5G cards, which allows the MDS Fabric Manager to create a link association between that SAN port and a SAN port on a Cisco MDS 9000 switch.

The MXP_MR_2.5G card features a 1550-nm laser for the trunk/line port and a 1310-nm or 850-nm laser (depending on the SFP) for the client ports. The card contains eight 12.5 degree downward tilt SFP modules for the client interfaces. For optical termination, each SFP uses two LC connectors, which are labeled TX and RX on the faceplate. In a MXP_MR_2.5G card, the trunk port is a dual-LC connector with a 45 degree downward angle. In a MXPP_MR_2.5G card, there are two trunk port connectors (one for working and one for protect), each a dual-LC connector with a 45-degree downward angle.

A transient gain range of 20 to 23 dB is available to APC in order to permit other amplifiers to reach their expected set points. However, operation in this range is not continuous. At startup, the OPT-AMP-17-C card caps the gain at a maximum of 20 dB.

Note	When the OPT-AMP-17-C operates as a booster amplifier, APC does not control its gain.

The following table lists the alarms and its related thresholds for the OSC-CSM card.

Y-cable and splitter protection are two main forms of card protection that are available for TXP, MXP, AR_MXP, AR_XP, AR_XPE, and Xponder (GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, and OTU2_XP) cards when they are provisioned in TXP or MXP mode. Y-cable protection is provided at the client port level. Splitter protection is provided at the trunk port level.

Note	GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards use VLAN protection when they are provisioned in L2-over-DWDM mode. For more information, see the Layer 2 Over DWDM Protection. The ADM-10G card uses path protection and 1+1 protection. For more information, see the Protection section.

The 1+1 protection is available for the GE_XP, GE_XPE, 10GE_XP, and 10GE_XPE cards:

The 1+1 protection is provided in the Layer 2 (L2) card mode to protect against client port and card failure. 1+1 protection is supported in both single shelf and multishelf setup. This means that the working card can be in one shelf and the protect card can be in another shelf of a multishelf setup. Communication between the two cards is across 10 Gigabit Ethernet interconnection interface using Ethernet packets. The Inter link (ILK) trunk or internal pathcord must be provisioned on both the cards. This link is used to transmit protection switching messages and data.

Note	With 1+1 protection mechanisms, the switch time of a copper SFP is 1 second.

With 1+1 protection, ports on the protect card can be assigned to protect the corresponding ports on the working card. A working card must be paired with a protect card of the same type and number of ports. The protection takes place on the port level, and any number of ports on the protect card can be assigned to protect the corresponding ports on the working card.

To make the 1+1 protection scheme fully redundant, enable L2 protection for the entire VLAN ring. This enables Fast Automatic Protection Switch (FAPS). The VLAN configured on the 1+1 port must be configured as protected SVLAN.

1+1 protection can be either revertive or nonrevertive. With nonrevertive 1+1 protection, when a failure occurs and the signal switches from the working card to the protect card, the signal remains on the protect card until it is manually changed. Revertive 1+1 protection automatically switches the signal back to the working card when the working card comes back online. 1+1 protection uses trunk ports to send control traffic between working and protect cards. This trunk port connection is known as ILK trunk ports and can be provisioned via CTC.

The standby port can be configured to turn ON or OFF but the traffic coming to and from the standby port will be down. If the laser is ON at the standby port, the other end port (where traffic originates) will not be down in a parallel connection. Traffic is blocked on the standby port.

1+1 protection is bidirectional and nonrevertive by default; revertive switching can be provisioned using CTC.

The Layer 2 Over DWDM protection is available for the following cards:

• GE_XP and GE_XPE

• 10GE_XP and 10GE_XPE

When the card is in L2-over-DWDM card mode, protection is handled by the hardware at the Layer 1 and Layer 2 levels. Fault detection and failure propagation is communicated through the ITU-T G.709 frame overhead bytes. For protected VLANs, traffic is flooded around the 10 Gigabit Ethernet DWDM ring. To set up the Layer 2 protection, you identify a node and the card port that is to serve as the primary node and port for the VLAN ring on the card view Provisioning > Protection tab. If a failure occurs, the node and port are responsible for opening and closing VLAN loops.

Note

The Forced option in the Protection drop-down list converts all the SVLANs to protected SVLANs irrespective of the SVLAN protection configuration in the SVLAN database. This is applicable to a point-to-point linear topology. The SVLAN protection must be forced to move all SVLANs, including protected and unprotected SVLANs, to the protect path irrespective of provisioned SVLAN attributes.

A FAPS switchover happens in the following failure scenarios:

• DWDM line failures caused by a fiber cut

• Unidirectional failure in the DWDM network caused by a fiber cut

• Fiber pull on the primary card trunk port followed by a hard reset on the primary card

• Hard reset on the primary card

• Hard reset on the secondary card

• An OTN failure is detected (LOS, OTUK-LOF, OTUK-LOM, OTUK-LOM, OTUK-SF, or OTUK-BDI on the DWDM receiver port in the case of ITU-T G.709 mode)

• Trunk ports are moved to OOS,DSBLD (Locked,disabled) state

• Improper removal of XFPs

A FAPS switchover does not happen in the following scenarios:

• Secondary card trunk port in OOS,DSBLD (Locked,disabled) state followed by a hard reset of the secondary card

• OTN alarms raised on the secondary card trunk port followed by a hard reset of the secondary card

The cards provide a transparent mode that accurately conveys the client input signal to the far-end client output signal. The client signal is normally carried as payload over the DWDM signals. Certain client signals, however, cannot be conveyed as payload. In particular, client LOS or LOF cannot be carried. Far-end laser control (FELC) is the ability to convey an LOS or LOF from the near-end client input to the far-end client output.

If an LOS is detected on the near-end client input, the near-end trunk sets the appropriate bytes in the OTN overhead of the DWDM line. These bytes are received by the far-end trunk, and cause the far-end client laser to be turned off. When the laser is turned off, it is said to be squelched. If the near-end LOS clears, the near-end trunk clears the appropriate bytes in the OTN overhead, the far-end detects the changed bytes, and the far-end client squelch is removed.

FELC also covers the situation in which the trunk port detects that it has an invalid signal; the client is squelched so as not to propagate the invalid signal.

Payload types with the 2R mode preclude the use of OTN overhead bytes. In 2R mode, an LOS on the client port causes the trunk laser to turn off. The far end detects the LOS on its trunk receiver and squelches the client.

FELC is not provisionable. It is always enabled when the DWDM card is in transparent termination mode. However, FELC signaling to the far-end is only possible when ITU-T G.709 is enabled on both ends of the trunk span.

Jitter introduced by the SFPs used in the transponders and muxponders must be considered when cascading several cards. With TXP_MR_2.5G, TXPP_MR_2.5G, MXP_MR_2.5G, MXPP_MR_2.5G, TXP_MR_10E, 100G-LC-C, 10x10G-LC, CFP-LC, 100G-CK-C, 200G-CK-LC, 100GS-CK-LC, 100G-ME-C, 100ME-CKC, AR_MXP, AR_XP, AR_XPE cards several transponders can be cascaded before the cumulative jitter violates the jitter specification. The recommended limit is 20 cards. With TXP_MR_10G cards, you can also cascade several cards, although the recommended limit is 12 cards. With MXP_2.5G_10G and MXP_2.5G_10E cards, any number of cards can be cascaded as long as the maximum reach between any two is not exceeded. This is because any time the signal is demultiplexed, the jitter is eliminated as a limiting factor.

The maximum reach between one transponder and the other must be halved if a Y cable is used. For more information on Y-cable operation, see the “Y-Cable and Splitter Protection” section on page G-24.

Transponder and Muxponder cards have various SONET and SDH termination modes that can be configured using CTC. The termination modes are summarized in the following table.

For TXP and MXP cards, adhere to the following conditions while DCC termination provisioning:

• For SDCC/RS-DCC provisioning, the card should be in the Section/RS-DCC or Line/MS-DCC termination mode.

• For LDCC/MS-DCC provisioning, the card should be in the Line/MS-DCC termination mode.