- Preface
- Cisco ONS Documentation Roadmap for Release 9.8.x
- New and Changed Information
- Chapter 1, Install the Cisco ONS 15454, ONS 15454 M2, and ONS 15454 M6 Shelf
- Chapter 2, Connecting the PC and Logging into the GUI
- Chapter 3, Install the Control Cards
- Chapter 4, Setup Optical Service Channel Cards
- Chapter 5, Optical Amplifier Cards
- Chapter 6, Provision Multiplexer and Demultiplexer Cards
- Chapter 7, Setup Tunable Dispersion Compensating Units
- Chapter 8, Provision Protection Switching Module
- Chapter 9, Optical Add/Drop Cards
- Chapter 10, Reconfigurable Optical Add/Drop Cards
- Chapter 11, Provision Transponder and Muxponder Cards
- Chapter 12, Node Reference
- Chapter 13, Network Reference
- Chapter 14, Turn Up a Node
- Chapter 15, Perform Node Acceptance Tests
- Chapter 16, Turn Up a Network
- Chapter 17, Create Optical Channel Circuits and Provisionable Patchcords
- Chapter 18, Monitor Performance
- Chapter 19, Manage the Node
- Chapter 20, Alarm and TCA Monitoring and Management
- Chapter 21, Change DWDM Card Settings
- Chapter 22, Manage Network Connectivity
- Chapter 23, Upgrade, Add, and Remove Cards and Nodes
- Chapter 24, Maintain the Node
- Chapter 25, Security Reference
- Chapter 26, Timing Reference
- Chapter 27, SNMP
- Appendix A, CTC Operation, Information, and Shortcuts
- Appendix B, Hardware Specifications
- Appendix C, Administrative and Service States
- Appendix D, Configure GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards Using PCLI
- Appendix E, Pseudo Command Line Interface Reference
- Appendix F, Fiber and Connector Losses in Raman Link Configuration
- Appendix G, Card Features
- Appendix H, Network Element Defaults
- 11.1 Card Overview
- 11.2 Safety Labels
- 11.3 TXP_MR_10G Card
- 11.4 TXP_MR_10E Card
- 11.5 TXP_MR_10E_C and TXP_MR_10E_L Cards
- 11.6 TXP_MR_2.5G and TXPP_MR_2.5G Cards
- 11.7 40E-TXP-C and 40ME-TXP-C Cards
- 11.8 MXP_2.5G_10G Card
- 11.9 MXP_2.5G_10E Card
- 11.10 MXP_2.5G_10E_C and MXP_2.5G_10E_L Cards
- 11.11 MXP_MR_2.5G and MXPP_MR_2.5G Cards
- 11.12 MXP_MR_10DME_C and MXP_MR_10DME_L Cards
- 11.13 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards
- 11.14 GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards
- 11.14.1 Key F eatures
- 11.14.2 Protocol Compatibility list
- 11.14.3 Faceplate and Block Diagram
- 11.14.4 GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Functions
- 11.14.4.1 Client Interface
- 11.14.4.2 DWDM Trunk Interface
- 11.14.4.3 Configuration Management
- 11.14.4.4 Security
- 11.14.4.5 Card Protection
- 11.14.5 IGMP Snooping
- 11.14.5.1 IGMP Snooping Guidelines and Restrictions
- 11.14.5.2 Fast-Leave Processing
- 11.14.5.3 Static Router Port Configuration
- 11.14.5.4 Report Suppression
- 11.14.5.5 IGMP Statistics and Counters
- 11.14.5.6 Related Procedure for Enabling IGMP Snooping
- 11.14.6 Multicast VLAN Registration
- 11.14.6.1 Related Procedure for Enabling MVR
- 11.14.7 MAC Address Learning
- 11.14.7.1 Related Procedure for MAC Address Learning
- 11.14.8 MAC Address Retrieval
- 11.14.8.1 Related Procedure for MAC Address Retrieving
- 11.14.9 Link Integrity
- 11.14.9.1 Related Procedure for Enabling Link Integrity
- 11.14.10 Ingress CoS
- 11.14.10.1 Related Procedure for Enabling Ingress CoS
- 11.14.11 CVLAN Rate Limiting
- 11.14.11.1 Related Procedure for Provisioning CVLAN Rate
- 11.14.12 DSCP to CoS Mapping
- 11.14.12.1 Related Procedure for Provisioning CoS Based on DSCP
- 11.14.13 Link Agg reg ation Control Protocol
- 11.14.13.1 Advantages of LACP
- 11.14.13.2 Function s of LACP
- 11.14.13.3 Modes o f LACP
- 11.14.13.4 Parame ters of LACP
- 11.14.13.5 Unicast Ha shing Schemes
- 11.14.13.6 LACP L imitations and Restrictions
- 11.14.13.7 Related Procedure for LACP
- 11.14.14 Ethernet Con nec tivity Fault Management
- 11.14.14.1 Maintena nce Domain
- 11.14.14.2 Maintena nce Association
- 11.14.14.3 Mainten ance End Points
- 11.14.14.4 Mainte nance Intermediate Points
- 11.14.14.5 CFM Messages
- 11.14.14.6 CFM Limitat ions and Restrictions
- 11.14.14.7 Related Procedure for Ethernet CFM
- 11.14.15 Etherne t OAM
- 11.14.15.1 Components of the Ethernet OAM
- 11.14.15.2 Benefits of the Ethernet OAM
- 11.14.15.3 Features of the Ethernet OAM
- 11.14.15.4 Ethernet OAM Limitations and Restrictions
- 11.14.15.5 Related Procedure for Ethernet OAM
- 11.14.16 Resilient E thern et Protocol
- 11.14.16.1 REP Segments
- 11.14.16.2 Characteristics of REP Segments
- 11.14.16.3 REP Port States
- 11.14.16.4 Link A djacency
- 11.14.16.5 Fast R econvergence
- 11.14.16.6 VLA N Load Balancing
- 11.14.16.7 REP Co nfiguration Sequence
- 11.14.16.8 REP Support ed Interfaces
- 11.14.16.9 REP Limitations and Restrictions
- 11.14.16.10 Related Procedure for Managing the REP Settings
- 11.14.17 Related Procedures for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards
- 11.15 ADM-10G Card
- 11.15.1 Key Features
- 11.15.2 ADM-10G POS Encapsulation, Framing, and CRC
- 11.15.2.1 POS Overview
- 11.15.2.2 POS Framing Modes
- 11.15.2.3 GFP Interoperability
- 11.15.2.4 LEX Interoperability
- 11.15.3 Faceplate and Block Diagram
- 11.15.4 Port Configuration Rules
- 11.15.5 Client Interfaces
- 11.15.6 Interlink Interfaces
- 11.15.7 DWDM Trunk Interface
- 11.15.8 Configuration Management
- 11.15.9 Security
- 11.15.10 Protection
- 11.15.10.1 Circuit Protection Schemes
- 11.15.10.2 Port Protection Schemes
- 11.15.11 Circuit Provisioning
- 11.15.12 ADM-10G CCAT and VCAT Characteristics
- 11.15.12.1 Related Procedure for VCAT Circuit
- 11.15.13 Intermediate Path Performance Monitoring
- 11.15.13.1 Related Procedure for IPPM
- 11.15.14 Pointer Justification Count Performance Monitoring
- 11.15.15 Performance Monitoring Parameter Definitions
- 11.15.16 ADM-10G Functions
- 11.15.17 Related Procedures for ADM-10G Card
- 11.16 OTU2_XP Card
- 11.16.1 Key Features
- 11.16.2 Faceplate and Block Diagram
- 11.16.3 OTU2_XP Card Interface
- 11.16.3.1 Client Interface
- 11.16.3.2 Trunk Interface
- 11.16.4 Configuration Management
- 11.16.5 OTU2_XP Card Configuration Rules
- 11.16.6 Security
- 11.16.7 ODU Transparency
- 11.16.8 OTU2_XP Functions
- 11.16.9 Related Procedures for OTU2_XP Card
- 11.17 TXP_MR_10EX_C Card
- 11.18 MXP_2.5G_10EX_C card
- 11.19 MXP_MR_10DMEX_C Card
- 11.20 AR_MXP, AR_XP, and AR_XPE Cards
- 11.20.1 Key Features
- 11.20.2 Faceplate and Block Diagram
- 11.20.3 Multiple Operating Modes
- TXP_MR (Unprotected Transponder)
- TXPP_MR (Protected Transponder)
- MXP_DME (Unprotected Data Muxponder)
- MXPP_DME (Protected Data Muxponder)
- MXP_MR (Unprotected Multirate Muxponder)
- MXPP_MR (Protected Multirate Muxponder)
- MXP-4x2.5-10G (OC48/OTU1 Unprotected Muxponder)
- MXPP-4x2.5-10G (OC48/OTU1 Protected Muxponder)
- RGN (OTU1/OTU2 Regenerator)
- MXP-VD-10G (Video Muxponder)
- 11.20.4 Scenarios of Different Operational mode Configurations on a AR_MXP, AR_XP, or AR_XPE Card
- 11.20.5 AR_MXP, AR_XP, and AR_XPE Functions and Features
- 11.20.6 Related Procedures for AR_MXP, AR_XP, and AR_XPE Cards
- 11.21 100G-LC-C,10x10G-LC, and CFP-LC Cards
- 11.21.1 100G-LC-C Card
- 11.21.1.1 Benefits
- 11.21.1.2 Key Features
- 11.21.1.3 Faceplate
- 11.21.1.4 100G-LC-C Block Diagram
- 11.21.1.5 Operating Modes for 100G-LC-C Card
- 11.21.2 10x10G-LC Card
- 11.21.2.1 Key Fe atures
- 11.21.2.2 Faceplate
- 11.21.2.3 10x10G-LC Block Diagram
- 11.21.2.4 Operating Modes for 10x10G-LC Card
- 11.21.3 CFP-LC Card
- 11.21.3.1 Key Features
- 11.21.3.2 Faceplate
- 11.21.3.3 Block Diagram
- 11.21.3.4 Operating Modes for CFP-LC Card
- 11.21.3.5 Key Features of 100G-LC-C, 10x10G-LC, and CFP-LC Cards
- 11.21.3.6 Function s and Features
- 11.22 Related Procedures for 100G-LC-C, 10x10G-LC, and CFP-LC Cards
- 11.23 WSE Card
- 11.23.1 Key Features
- 11.23.2 Faceplate Diagram
- 11.23.3 WSE workflow diagram
- 11.23.4 Multiple Operating Modes
- 11.23.4.1 TXP-10G
- 11.23.4.2 RGN-10G
- 11.23.5 Card Authentication
- 11.23.6 Key Management
- 11.23.7 Payload Encryption
- 11.23.8 AES Secure Packet
- 11.23.9 Scenarios that Affect Traffic
- 11.23.9.1 Scenario 1: Traffic in a Stacked Topology
- 11.23.9.2 Scenario 2: Traffic in a Far-end and Near-end Client Loopback
- 11.23.9.3 Scenario 3: Traffic After Enabling PRBS Ingress and Egress
- 11.23.10 Function s and Features
- 11.24 Related Procedures for WSE Card
- 11.25 MLSE UT
- 11.26 SFP, SFP+, XFP, CXP, and CFP Modules
- 11.27 Procedures for Transponder and Muxponder Cards
Provision Transponder and Muxponder Cards
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.
This chapter describes Cisco ONS 15454 transponder (TXP), muxponder (MXP), GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, ADM-10G, OTU2_XP, 100G-LC-C, 10x10G-LC, CFP-LC, WSE, AR_MXP, AR_XP, and AR_XPE cards, as well as their associated plug-in modules (Small Form-factor Pluggables [SFP, SFP+, XFP, CXP, or CFP module]). For card safety and compliance information, see the Regulatory Compliance and Safety Information for Cisco ONS Products document.
Note Unless otherwise specified, “ONS 15454” refers to both ANSI and ETSI shelf assemblies.
Note The cards described in this chapter are supported on the Cisco ONS 15454, Cisco ONS 15454 M6, Cisco ONS 15454 M2 platforms, unless noted otherwise.
Note The procedures and tasks described in this chapter for the Cisco ONS 15454 platform is applicable to the Cisco ONS 15454 M2 and Cisco ONS 15454 M6 platforms, unless noted otherwise.
Note In this chapter, “100G-LC-C card” refers to the 15454-M-100G-LC-C card. “10x10G-LC” refers to the 15454-M-10x10G-LC card. “CFP-LC” refers to the 15454-M-CFP-LC card.
- Card Overview
- Safety Labels
- TXP_MR_10G Card
- Related Procedures for TXP_MR_10G Card
- TXP_MR_10E Card
- Related Procedures for TXP_MR_10E Card
- TXP_MR_10E_C and TXP_MR_10E_L Cards
- Related Procedures for TXP_MR_10E_C and TXP_MR_10E_L Cards
- TXP_MR_2.5G and TXPP_MR_2.5G Cards
- Related Procedures for TXP_MR_2.5G and TXPP_MR_2.5G Cards
- 40E-TXP-C and 40ME-TXP-C Cards
- Related Procedures for 40E-TXP-C and 40ME-TXP-C Cards
- MXP_2.5G_10G Card
- Related Procedures for MXP_2.5G_10G Card
- MXP_2.5G_10E Card
- Related Procedures for MXP_2.5G_10E Card
- MXP_2.5G_10E_C and MXP_2.5G_10E_L Cards
- Related Procedures for MXP_2.5G_10E_C and MXP_2.5G_10E_L Cards
- MXP_MR_2.5G and MXPP_MR_2.5G Cards
- Related Procedures for MXP_MR_2.5G and MXPP_MR_2.5G Cards
- MXP_MR_10DME_C and MXP_MR_10DME_L Cards
- Related Procedures for MXP_MR_10DME_C and MXP_MR_10DME_L Cards
- 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards
- Related Procedures for 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards
- GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards
- Related Procedures for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards
- ADM-10G Card
- Related Procedures for ADM-10G Card
- OTU2_XP Card
- Related Procedures for OTU2_XP Card
- TXP_MR_10EX_C Card
- Related Procedures for TXP_MR_10EX_C Card
- MXP_2.5G_10EX_C card
- Related Procedures for MXP_2.5G_10EX_C Card
- MXP_MR_10DMEX_C Card
- Related Procedures for MXP_MR_10DMEX_C Card
- AR_MXP, AR_XP, and AR_XPE Cards
- 100G-LC-C,10x10G-LC, and CFP-LC Cards
- Related Procedures for 100G-LC-C, 10x10G-LC, and CFP-LC Cards
- WSE Card
- Related Procedures for WSE Card
- MLSE UT
- SFP, SFP+, XFP, CXP, and CFP Modules
Note Cisco ONS 15454 DWDM supports IBM's 5G DDR (Double Data Rate) InfiniBand1 interfaces.
11.1 Card Overview
The card overview section lists the cards described in this chapter and provides compatibility information.
Note Each card is marked with a symbol that corresponds to a slot (or slots) on the ONS 15454 shelf assembly. The cards are then installed into slots displaying the same symbols. For a list of slots and symbols, see the “Card Slot Requirements” section in the Cisco ONS 15454 Hardware Installation Guide.
The purpose of a TXP, MXP, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, ADM-10G, OTU2_XP, AR_MXP, AR_XP, or AR_XPE card is to convert the “gray” optical client interface signals into trunk signals that operate in the “colored” dense wavelength division multiplexing (DWDM) wavelength range. Client-facing gray optical signals generally operate at shorter wavelengths, whereas DWDM colored optical signals are in the longer wavelength range (for example, 1490 nm = violet; 1510 nm = blue; 1530 nm = green; 1550 nm = yellow; 1570 nm = orange; 1590 nm = red; 1610 nm = brown). Some of the newer client-facing PPMs, however, operate in the colored region. Transponding or muxponding is the process of converting the signals between the client and trunk wavelengths.
An MXP generally handles several client signals. It aggregates, or multiplexes, lower rate client signals together and sends them out over a higher rate trunk port. Likewise, it demultiplexes optical signals coming in on a trunk and sends them out to individual client ports. A TXP converts a single client signal to a single trunk signal and converts a single incoming trunk signal to a single client signal. GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards can be provisioned as TXPs, as MXPs, or as Layer 2 switches.
All of the TXP and MXP cards perform optical to electrical to optical (OEO) conversion. As a result, they are not optically transparent cards. The reason for this is that the cards must operate on the signals passing through them, so it is necessary to do an OEO conversion.
On the other hand, the termination mode for all of the TXPs and MXPs, which is done at the electrical level, can be configured to be transparent. In this case, neither the Line nor the Section overhead is terminated. The cards can also be configured so that either Line or Section overhead can be terminated, or both can be terminated.
Note The MXP_2.5G_10G card, by design, when configured in the transparent termination mode, actually does terminate some of the bytes. See Table G-19 for details.
11.1.1 Card Summary
Table 11-1 lists and summarizes the functions of each TXP, TXPP, MXP, MXPP, AR_MXP, AR_XP, AR_XPE, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, 100G-LC-C, 10x10G-LC, CFP-LC, WSE, ADM-10G, and OTU2_XP card.
The TXP_MR_10G card has two sets of ports located on the faceplate. |
See the “TXP_MR_10G Card” section. |
|
The TXP_MR_10E card has two sets of ports located on the faceplate. |
See the “TXP_MR_10E Card” section. |
|
The TXP_MR_10E_C and TXP_MR_10E_L cards have two sets of ports located on the faceplate. |
||
The TXP_MR_2.5G card has two sets of ports located on the faceplate. |
||
The TXPP_MR_2.5G card has three sets of ports located on the faceplate. |
||
The 40E-TXP-C and 40ME-TXP-C cards have two ports located on the face plate. |
||
The MXP_2.5G_10G card has nine sets of ports located on the faceplate. |
See the “MXP_2.5G_10G Card” section. |
|
The MXP_2.5G_10E card has nine sets of ports located on the faceplate. |
See the “MXP_2.5G_10E Card” section. |
|
The MXP_2.5G_10E_C and MXP_2.5G_10E_L cards have nine sets of ports located on the faceplate. |
||
The MXP_MR_2.5G card has nine sets of ports located on the faceplate. |
||
The MXPP_MR_2.5G card has ten sets of ports located on the faceplate. |
||
The MXP_MR_10DME_C and MXP_MR_10DME_L cards have eight sets of ports located on the faceplate. |
||
The 40G-MXP-C, 40E-MXP-C and 40ME-MXP-C cards have five ports located on the faceplate. |
See the “40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards” section. |
|
The AR_MXP, AR_XP, and AR_XPE cards have ten ports located on the faceplate. |
||
The GE_XP and GE_XPE cards have twenty Gigabit Ethernet client ports and two 10 Gigabit Ethernet trunk ports. |
See the “GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards” section. |
|
The 10GE_XP and 10GE_XPE cards have two 10 Gigabit Ethernet client ports and two 10 Gigabit Ethernet trunk ports. |
See the “GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards” section. |
|
See the “100G-LC-C Card” section. |
||
The 10x10G-LC card has 10-ports SFP+ based (gray, colored, coarse wavelength division multiplexing (CWDM), and DWDM optics available)) and one 100G CXP based port. |
See the“10x10G-LC Card” section. |
|
The CFP-LC card has two 100G CFP pluggable modules and a cross-bar embedded switch module. |
See the “CFP-LC Card” section. |
|
The WSE card has 10-ports SFP+ based (gray, colored, and DWDM optics available)). |
See the “WSE Card” section. |
|
The ADM-10G card has 19 sets of ports located on the faceplate. |
See the “ADM-10G Card” section. |
|
See the “OTU2_XP Card” section. |
||
The TXP_MR_10EX_C card has two sets of ports located on the faceplate. |
See the “TXP_MR_10EX_C Card” section. |
|
The MXP_2.5G_10EX_C card has nine sets of ports located on the faceplate. |
See the “MXP_2.5G_10EX_C card” section. |
|
The MXP_MR_10DMEX_C card has eight sets of ports located on the faceplate. |
See the “MXP_MR_10DMEX_C Card” section. |
11.1.2 Card Compatibility
Table 11-2 lists the platform and Cisco Transport Controller (CTC) software compatibility for each TXP, TXPP, MXP, MXPP, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, ADM-10G, and OTU2_XP card.
Older versions of the TXP_MR_10E_C, TXP_MR_2.5G, TXPP_MR_2.5G, and MXP_2.5G_10E_C cards cannot be installed in the Cisco ONS 15454 M2 and Cisco ONS 15454 M6 shelves because of an incompatible backplane connector.
The following table describes the version numbers of the cards that are compatible with the ONS 15454 M2 and ONS 15454 M6 shelves. The version numbers can be viewed from the HW Rev field in the Inventory tab.
11.2 Safety Labels
For information about safety labels, see the “Safety Labels” section.
11.3 TXP_MR_10G Card
The TXP_MR_10G processes one 10-Gbps signal (client side) into one 10-Gbps, 100-GHz DWDM signal (trunk side). It provides one 10-Gbps port per card that can be provisioned for an STM-64/OC-192 short reach (1310-nm) signal, compliant with ITU-T G.707, ITU-T G.709, ITU-T G.691, and Telcordia GR-253-CORE, or a 10GBASE-LR signal compliant with IEEE 802.3.
The TXP_MR_10G card is tunable over two neighboring wavelengths in the 1550-nm, ITU 100-GHz range. It is available in 16 different versions, each of which covers two wavelengths, for a total coverage of 32 different wavelengths in the 1550-nm range.
Note ITU-T G.709 specifies a form of forward error correction (FEC) that uses a “wrapper” approach. The digital wrapper lets you transparently take in a signal on the client side, wrap a frame around it and restore it to its original form. FEC enables longer fiber links because errors caused by the optical signal degrading with distance are corrected.
The trunk port operates at 9.95328 Gbps (or 10.70923 Gbps with ITU-T G.709 Digital Wrapper/FEC) and at 10.3125 Gbps (or 11.095 Gbps with ITU-T G.709 Digital Wrapper/FEC) over unamplified distances up to 80 km (50 miles) with different types of fiber such as C-SMF or dispersion compensated fiber limited by loss and/or dispersion.
You can install TXP_MR_10G cards in Slots 1 to 6 and 12 to 17 and provision this card in a linear configuration. TXP_MR_10G cards cannot be provisioned as a bidirectional line switched ring (BLSR)/Multiplex Section - Shared Protection Ring (MS-SPRing), a path protection/single node control point (SNCP), or a regenerator. They can only be used in the middle of BLSR/MS-SPRing and 1+1 spans when the card is configured for transparent termination mode.
The TXP_MR_10G port features a 1550-nm laser for the trunk port and a 1310-nm laser for the for the client port and contains two transmit and receive connector pairs (labeled) on the card faceplate.
The MTU setting is used to display the OverSizePkts counters on the receiving trunk and client port interfaces. Traffic of frame sizes up to 65535 bytes pass without any packet drops, from the client port to the trunk port and vice versa irrespective of the MTU setting.
The TXP_MR_10G card has the following available wavelengths and versions:
– 1538.19 to 1538.98 nm, 10T-L1-38.1
– 1539.77 to 1540.56 nm, 10T-L1-39.7
– 1530.33 to 1531.12 nm, 10T-L1-30.3
– 1531.90 to 1532.68 nm, 10T-L1-31.9
– 1534.25 to 1535.04 nm, 10T-L1-34.2
– 1535.82 to 1536.61 nm, 10T-L1-35.8
– 1542.14 to 1542.94 nm, 10T-L1-42.1
– 1543.73 to 1544.53 nm, 10T-L1-43.73
– 1554.13 to 1554.94 nm, 10T-L1-54.1
– 1555.75 to 1556.55 nm, 10T-L1-55.7
– 1546.12 to 1546.92 nm, 10T-L1-46.1
– 1547.72 to 1548.51 nm, 10T-L1-47.7
– 1550.12 to 1550.92 nm, 10T-L1-50.1
– 1551.72 to 1552.52 nm, 10T-L1-51.7
– 1558.17 to 1558.98 nm, 10T-L1-58.1
– 1559.79 to 1560.61 nm, 10T-L1-59.7
11.3.1 Faceplate and Block Diagram
Figure 11-1 shows the TXP_MR_10G faceplate and block diagram.
Figure 11-1 TXP_MR_10G Faceplate and Block Diagram
For information about safety labels for the card, see the “Class 1M Laser Product Cards” section.
11.3.2 TXP_MR_10G Functions
The functions of the TXP_MR_10G card are:
- Automatic Laser Shutdown
- Card level indicators—Table G-1
- Port level indicators—Table G-7
11.4 TXP_MR_10E Card
The card is fully backward compatible with the TXP_MR_10G card. It processes one 10-Gbps signal (client side) into one 10-Gbps, 100-GHz DWDM signal (trunk side) that is tunable over four wavelength channels (spaced at 100 GHz on the ITU grid) in the C band and tunable over eight wavelength channels (spaced at 50 GHz on the ITU grid) in the L band. There are eight versions of the C-band card, with each version covering four wavelengths, for a total coverage of 32 wavelengths. There are five versions of the L-band card, with each version covering eight wavelengths, for a total coverage of 40 wavelengths.
You can install TXP_MR_10E cards in Slots 1 to 6 and 12 to 17 and provision the cards in a linear configuration, BLSR/MS-SPRing, path protection/SNCP, or a regenerator. The card can be used in the middle of BLSR/MS-SPRing or 1+1 spans when the card is configured for transparent termination mode.
The TXP_MR_10E card features a 1550-nm tunable laser (C band) or a 1580-nm tunable laser (L band) for the trunk port and a separately orderable ONS-XC-10G-S1 1310-nm or ONS-XC-10G-L2 1550-nm laser XFP module for the client port.
Note When the ONS-XC-10G-L2 XFP is installed, the TXP_MR_10E card must be installed in Slots 6, 7, 12 or 13)
On its faceplate, the TXP_MR_10E card contains two transmit and receive connector pairs, one for the trunk port and one for the client port. Each connector pair is labeled.
11.4.1 Key Features
The key features of the TXP_MR_10E card are:
- OC-192 to ITU-T G.709 OTU2 provisionable synchronous and asynchronous mapping
- The MTU setting is used to display the OverSizePkts counters on the receiving trunk and client port interfaces. Traffic of frame sizes up to 65535 bytes pass without any packet drops, from the client port to the trunk port and vice versa irrespective of the MTU setting.
11.4.2 Faceplate and Block Diagram
Figure 11-2 shows the TXP_MR_10E faceplate and block diagram.
Figure 11-2 TXP_MR_10E Faceplate and Block Diagram
For information about safety labels for the card, see the “Class 1M Laser Product Cards” section.
11.4.3 TXP_MR_10E Functions
The functions of the TXP_MR_10E card are:
- Automatic Laser Shutdown
- Card level indicators—Table G-1
- Port level indicators—Table G-6
- Client Interface
- DWDM Trunk Interface
- FEC
- Client-to-Trunk Mapping
11.5 TXP_MR_10E_C and TXP_MR_10E_L Cards
TXP_MR_10E_L: (Cisco ONS 15454 only)
The TXP_MR_10E_C and TXP_MR_10E_L cards are multirate transponders for the ONS 15454 platform. The cards are fully backward compatible with the TXP_MR_10G and TXP_MR_10E cards. They processes one 10-Gbps signal (client side) into one 10-Gbps, 100-GHz DWDM signal (trunk side). The TXP_MR_10E_C is tunable over the entire set of C-band wavelength channels (82 channels spaced at 50 GHz on the ITU grid). The TXP_MR_10E_L is tunable over the entire set of L-band wavelength channels (80 channels spaced at 50 GHz on the ITU grid) and is particularly well suited for use in networks that employ DS fiber or SMF-28 single-mode fiber.
The advantage of these cards over previous versions (TXP_MR_10G and TXP_MR_10E) is that there is only one version of each card (one C-band version and one L-band version) instead of several versions needed to cover each band.
You can install TXP_MR_10E_C and TXP_MR_10E_L cards in Slots 1 to 6 and 12 to 17 and provision the cards in a linear configuration, BLSR/MS-SPRing, path protection/SNCP, or a regenerator. The cards can be used in the middle of BLSR/MS-SPRing or 1+1 spans when the cards are configured for transparent termination mode.
The TXP_MR_10E_C and TXP_MR_10E_L cards feature a universal transponder 2 (UT2) 1550-nm tunable laser (C band) or a UT2 1580-nm tunable laser (L band) for the trunk port and a separately orderable ONS-XC-10G-S1 1310-nm or ONS-XC-10G-L2 1550-nm laser XFP module for the client port.
Note When the ONS-XC-10G-L2 XFP is installed, the TXP_MR_10E_C or TXP_MR_10E-L card is required to be installed in a high-speed slot (slot 6, 7, 12, or 13)
On its faceplate, the TXP_MR_10E_C and TXP_MR_10E_L cards contain two transmit and receive connector pairs, one for the trunk port and one for the client port. Each connector pair is labeled.
11.5.1 Key Features
The key features of the TXP_MR_10E_C and TXP_MR_10E_L cards are:
- A UT2 module tunable through the entire C band (TXP_MR_10E_C card) or L band (TXP_MR_10E_L card). The channels are spaced at 50 GHz on the ITU grid.
- OC-192 to ITU-T G.709 OTU2 provisionable synchronous and asynchronous mapping.
- The MTU setting is used to display the OverSizePkts counters on the receiving trunk and client port interfaces. Traffic of frame sizes up to 65535 bytes pass without any packet drops, from the client port to the trunk port and vice versa irrespective of the MTU setting.
11.5.2 Faceplates and Block Diagram
Figure 11-3 shows the TXP_MR_10E_C and TXP_MR_10E_L faceplates and block diagram.
Figure 11-3 TXP_MR_10E_C and TXP_MR_10E_L Faceplates and Block Diagram
For information about safety labels for the cards, see the “Class 1M Laser Product Cards” section.
11.5.3 TXP_MR_10E_C and TXP_MR_10E_L Functions
The functions of the TXP_MR_10E_C and TXP_MR_10E_L cards are:
- Automatic Laser Shutdown
- Card level indicators—Table G-1
- Port level indicators—Table G-6.
- Client Interface
- DWDM Trunk Interface
- FEC
- Client-to-Trunk Mapping
11.6 TXP_MR_2.5G and TXPP_MR_2.5G Cards
The TXP_MR_2.5G card processes one 8-Mbps to 2.488-Gbps signal (client side) into one 8-Mbps to 2.5-Gbps, 100-GHz DWDM signal (trunk side). It provides one long-reach STM-16/OC-48 port per card, compliant with ITU-T G.707, ITU-T G.709, ITU-T G.957, and Telcordia GR-253-CORE.
The TXPP_MR_2.5G card processes one 8-Mbps to 2.488-Gbps signal (client side) into two 8-Mbps to 2.5-Gbps, 100-GHz DWDM signals (trunk side). It provides two long-reach STM-16/OC-48 ports per card, compliant with ITU-T G.707, ITU-T G.957, and Telcordia GR-253-CORE.
The TXP_MR_2.5G and TXPP_MR_2.5G cards are tunable over four wavelengths in the 1550-nm, ITU 100-GHz range. They are available in eight versions, each of which covers four wavelengths, for a total coverage of 32 different wavelengths in the 1550-nm range.
Note ITU-T G.709 specifies a form of FEC that uses a “wrapper” approach. The digital wrapper lets you transparently take in a signal on the client side, wrap a frame around it, and restore it to its original form. FEC enables longer fiber links because errors caused by the optical signal degrading with distance are corrected.
The trunk/line port operates at up to 2.488 Gbps (or up to 2.66 Gbps with ITU-T G.709 Digital Wrapper/FEC) over unamplified distances up to 360 km (223.7 miles) with different types of fiber such as C-SMF or higher if dispersion compensation is used.
The TXP_MR_2.5G and TXPP_MR_2.5G cards support 2R (retime, regenerate) and 3R (retime, reshape, and regenerate) modes of operation where the client signal is mapped into a ITU-T G.709 frame. The mapping function is simply done by placing a digital wrapper around the client signal. Only OC-48/STM-16 client signals are fully ITU-T G.709 compliant, and the output bit rate depends on the input client signal. Table 11-53 shows the possible combinations of client interfaces, input bit rates, 2R and 3R modes, and ITU-T G.709 monitoring.
3R2 |
|||
Note ITU-T G.709 and FEC support is disabled for all the 2R payload types in the TXP_MR_2.5G and TXPP_MR_2.5G cards.
The output bit rate is calculated for the trunk bit rate by using the 255/238 ratio as specified in ITU-T G.709 for OTU1. Table 11-5 lists the calculated trunk bit rates for the client interfaces with ITU-T G.709 enabled.
For 2R operation mode, the TXP_MR_2.5G and TXPP_MR_2.5G cards have the ability to pass data through transparently from client side interfaces to a trunk side interface, which resides on an ITU grid. The data might vary at any bit rate from 200-Mbps up to 2.38-Gbps, including ESCON, DVB-ASI, ISC-1, and video signals. In this pass-through mode, no performance monitoring (PM) or digital wrapping of the incoming signal is provided, except for the usual PM outputs from the SFPs. Similarly, this card has the ability to pass data through transparently from the trunk side interfaces to the client side interfaces with bit rates varying from 200-Mbps up to 2.38-Gbps. Again, no PM or digital wrapping of received signals is available in this pass-through mode.
For 3R operation mode, the TXP_MR_2.5G and TXPP_MR_2.5G cards apply a digital wrapper to the incoming client interface signals (OC-N/STM-N, 1G-FC, 2G-FC, GE). PM is available on all of these signals except for 2G-FC, and varies depending upon the type of signal. For client inputs other than OC-48/STM-16, a digital wrapper might be applied but the resulting signal is not ITU-T G.709 compliant. The card applies a digital wrapper that is scaled to the frequency of the input signal.
The TXP_MR_2.5G and TXPP_MR_2.5G cards have the ability to take digitally wrapped signals in from the trunk interface, remove the digital wrapper, and send the unwrapped data through to the client interface. PM of the ITU-T G.709 OH and SONET/SDH OH is implemented.
11.6.1 Faceplates and Block Diagram
Figure 11-4 shows the TXP_MR_2.5G and TXPP_MR_2.5G faceplates.
Figure 11-4 TXP_MR_2.5G and TXPP_MR_2.5G Faceplates
For information about safety labels for the cards, see the “Class 1M Laser Product Cards” section.
Figure 11-5 shows a block diagram of the TXP_MR_2.5G and TXPP_MR_2.5G cards.
Figure 11-5 TXP_MR_2.5G and TXPP_MR_2.5G Block Diagram
You can install TXP_MR_2.5G and TXPP_MR_2.5G cards in Slots 1 to 6 and 12 to 17. You can provision this card in a linear configuration. TXP_MR_10G and TXPP_MR_2.5G cards cannot be provisioned as a BLSR/MS-SPRing, a path protection/SNCP, or a regenerator. They can be used in the middle of BLSR/MS-SPRing or 1+1 spans only when the card is configured for transparent termination mode.
The TXP_MR_2.5G card features a 1550-nm laser for the trunk/line port and a 1310-nm laser for the client port. It contains two transmit and receive connector pairs (labeled) on the card faceplate. The card uses dual LC connectors for optical cable termination.
The TXPP_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 port and contains three transmit and receive connector pairs (labeled) on the card faceplate. The card uses dual LC connectors for optical cable termination.
11.6.2 TXP_MR_2.5G and TXPP_MR_2.5G Functions
The functions of the TXP_MR_2.5G and TXPP_MR_2.5G cards are:
- Automatic Laser Shutdown
- Card level indicators—Table G-1
- Port level indicators—Table G-6 (for TXP_MR_2.5G)
- Port level indicators—Table G-8 (for TXPP_MR_2.5G)
11.7 40E-TXP-C and 40ME-TXP-C Cards
The 40E-TXP-C and 40ME-TXP-C cards process a single 40-Gbps signal (client side) into a single 40-Gbps, 50-GHz DWDM signal (trunk side). It provides one 40-Gbps port per card that can be provisioned for an OC-768/STM-256 very short reach (1550-nm) signal compliant with ITU-T G.707, ITU-T G.691, and Telcordia GR-253-CORE, 40G Ethernet LAN signal compliant with IEEE 802.3ba, or OTU3 signal compliant with ITU-T G.709.
The trunk port of the 40E-TXP-C and 40ME-TXP-C cards are tunable between 1529.55 nm through 1561.83 nm, ITU 50-GHz range.
ITU-T G.709 specifies a form of forward error correction (FEC) that uses a “wrapper” approach. The digital wrapper lets you transparently take in a signal on the client side, wrap a frame around it and restore it to its original form. FEC enables longer fiber links because errors caused by the optical signal degrading with distance are corrected.
You can install and provision the 40E-TXP-C, and 40ME-TXP-C cards in a linear configuration in:
- Slots 1 to 5 and 12 to 16 in ONS 15454 DWDM chassis
- Slot 2 in ONS 15454 M2 chassis
- Slots 2 to 6 in ONS 15454 M6 chassis
When a protection switch occurs on the 40E-TXP-C, and 40ME-TXP-C cards, the recovery from PSM protection switch takes about 3 to 4 minutes.
Note The maximum ambient operating temperature for 40E-TXP-C, and 40ME-TXP-C cards is 500 Celsius.
11.7.1 Faceplates and Block Diagram
Figure 11-6 shows the 40E-TXP-C and 40ME-TXP-C faceplate and block diagram.
Figure 11-6 40E-TXP-C and 40ME-TXP-C Faceplate and Block Diagram
For information about safety labels for the card, see the “Class 1M Laser Product Cards” section.
11.7.2 40E-TXP-C and 40ME-TXP-C Functions
The functions of the 40E-TXP-C and 40ME-TXP-C cards are:
- Automatic Laser Shutdown (supported on a client interface)
- Card level indicators—Table G-1
- Port level indicators—Table G-6.
11.8 MXP_2.5G_10G Card
The MXP_2.5G_10G card multiplexes/demultiplexes four 2.5-Gbps signals (client side) into one 10-Gbps, 100-GHz DWDM signal (trunk side). It provides one extended long-range STM-64/OC-192 port per card on the trunk side (compliant with ITU-T G.707, ITU-T G.709, ITU-T G.957, and Telcordia GR-253-CORE) and four intermediate- or short-range OC-48/STM-16 ports per card on the client side. The port operates at 9.95328 Gbps over unamplified distances up to 80 km (50 miles) with different types of fiber such as C-SMF or dispersion compensated fiber limited by loss and/or dispersion.
Client ports on the MXP_2.5G_10G card are also interoperable with SONET OC-1 (STS-1) fiber optic signals defined in Telcordia GR-253-CORE. An OC-1 signal is the equivalent of one DS-3 channel transmitted across optical fiber. OC-1 is primarily used for trunk interfaces to phone switches in the United States. There is no SDH equivalent for SONET OC-1.
The MXP_2.5G_10G card is tunable over two neighboring wavelengths in the 1550-nm, ITU 100-GHz range. It is available in 16 different versions, each of which covers two wavelengths, for a total coverage of 32 different wavelengths in the 1550-nm range.
Note ITU-T G.709 specifies a form of FEC that uses a “wrapper” approach. The digital wrapper lets you transparently take in a signal on the client side, wrap a frame around it and restore it to its original form. FEC enables longer fiber links because errors caused by the optical signal degrading with distance are corrected.
The port can also operate at 10.70923 Gbps in ITU-T G.709 Digital Wrapper/FEC mode.
You can install MXP_2.5G_10G cards in Slots 1 to 6 and 12 to 17.
You can provision this card in a linear configuration. MXP_2.5G_10G cards cannot be provisioned as a BLSR/MS-SPRing, a path protection/SNCP, or a regenerator. They can be used in the middle of BLSR/MS-SPRing or 1+1 spans only when the card is configured for transparent termination mode.
The MXP_2.5G_10G port features a 1550-nm laser on the trunk port and four 1310-nm lasers on the client ports and contains five transmit and receive connector pairs (labeled) on the card faceplate. The card uses a dual LC connector on the trunk side and SFP connectors on the client side for optical cable termination.
Note When you create a 4xOC-48 OCHCC circuit, you need to select the G.709 and Synchronous options. A 4xOC-48 OCHCC circuit is supported by G.709 and synchronous mode. This is necessary to provision a 4xOC-48 OCHCC circuit.
11.8.1 Faceplates and Block Diagram
Figure 11-7 shows the MXP_2.5G_10G faceplate.
Figure 11-7 MXP_2.5G_10G Faceplate
For information about safety labels for the card, see the “Class 1 Laser Product Cards” section.
Figure 11-8 shows a block diagram of the MXP_2.5G_10G card.
Figure 11-8 MXP_2.5G_10G Card Block Diagram
11.8.2 MXP_2.5G_10G Functions
The functions of the MXP_2.5G_10G card are:
- Timing Synchronization
- Automatic Laser Shutdown
- Card level indicators—Table G-1
- Port level indicators— Table G-7
11.9 MXP_2.5G_10E Card
The faceplate designation of the card is “4x2.5G 10E MXP.” The MXP_2.5G_10E card is a DWDM muxponder for the ONS 15454 platform that supports full transparent termination the client side. The card multiplexes four 2.5 Gbps client signals (4 x OC48/STM-16 SFP) into a single 10-Gbps DWDM optical signal on the trunk side. The MXP_2.5G_10E provides wavelength transmission service for the four incoming 2.5 Gbps client interfaces. The MXP_2.5G_10E muxponder passes all SONET/SDH overhead bytes transparently.
The digital wrapper function (ITU-T G.709 compliant) formats the DWDM wavelength so that it can be used to set up generic communications channels (GCCs) for data communications, enable FEC, or facilitate performance monitoring.
The MXP_2.5G_10E works with optical transport network (OTN) devices defined in ITU-T G.709. The card supports ODU1 to OTU2 multiplexing, an industry standard method for asynchronously mapping a SONET/SDH payload into a digitally wrapped envelope. See the “Multiplexing Function” section.
The MXP_2.5G_10E card is not compatible with the MXP_2.5G_10G card, which does not support full transparent termination. You can install MXP_2.5G_10E cards in Slots 1 to 6 and 12 to 17. You can provision this card in a linear configuration, as a BLSR/MS-SPRing, a path protection/SNCP, or a regenerator. The card can be used in the middle of BLSR/MS-SPRing or 1+1 spans when the card is configured for transparent termination mode.
The MXP_2.5G_10E features a 1550-nm laser on the trunk port and four 1310-nm lasers on the client ports and contains five transmit and receive connector pairs (labeled) on the card faceplate. The card uses a dual LC connector on the trunk side and uses SFP modules on the client side for optical cable termination. The SFP pluggable modules are short reach (SR) or intermediate reach (IR) and support an LC fiber connector.
Note When you create a 4xOC-48 OCHCC circuit, you need to select the G.709 and Synchronous options. A 4xOC-48 OCHCC circuit is supported by G.709 and synchronous mode. This is necessary to provision a 4xOC-48 OCHCC circuit.
11.9.1 Key Features
The MXP_2.5G_10E card has the following high level features:
- Four 2.5 Gbps client interfaces (OC-48/STM-16) and one 10 Gbps trunk. The four OC-48 signals are mapped into a ITU-T G.709 OTU2 signal using standard ITU-T G.709 multiplexing.
- Onboard E-FEC processor: The processor supports both standard Reed-Solomon (RS, specified in ITU-T G.709) and E-FEC, which allows an improved gain on trunk interfaces with a resultant extension of the transmission range on these interfaces. The E-FEC functionality increases the correction capability of the transponder to improve performance, allowing operation at a lower OSNR compared to the standard RS (237,255) correction algorithm. A new block code (BCH) algorithm implemented in E-FEC allows recovery of an input BER up to 1E-3.
- Pluggable client interface optic modules: The MXP_2.5G_10E card has modular interfaces. Two types of optics modules can be plugged into the card. These include an OC-48/STM 16 SR-1 interface with a 7-km (4.3-mile) nominal range (for short range and intra-office applications) and an IR-1 interface with a range up to 40 km (24.9 miles). SR-1 is defined in Telcordia GR-253-CORE and in I-16 (ITU-T G.957). IR-1 is defined in Telcordia GR-253-CORE and in S-16-1 (ITU-T G.957).
- High level provisioning support: The MXP_2.5G_10E card is initially provisioned using Cisco TransportPlanner software. Subsequently, the card can be monitored and provisioned using CTC software.
- Link monitoring and management: The MXP_2.5G_10E card uses standard OC-48 OH (overhead) bytes to monitor and manage incoming interfaces. The card passes the incoming SDH/SONET data stream and its overhead bytes transparently.
- Control of layered SONET/SDH transport overhead: The card is provisionable 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.
- Automatic timing source synchronization: The MXP_2.5G_10E normally synchronizes from the TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE card. If for some reason, such as maintenance or upgrade activity, the TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE is not available, the MXP_2.5G_10E automatically synchronizes to one of the input client interface clocks.
- Configurable squelching policy: The card can be configured to squelch the client interface output if there is LOS at the DWDM receiver or if there is a remote fault. In the event of a remote fault, the card manages multiplex section alarm indication signal (MS-AIS) insertion.
11.9.2 Faceplates and Block Diagram
Figure 11-9 shows the MXP_2.5G_10E faceplate.
Figure 11-9 MXP_2.5G_10E Faceplate
For information about safety labels for the card, see the “Class 1 Laser Product Cards” section.
Figure 11-10 shows a block diagram of the MXP_2.5G_10E card.
Figure 11-10 MXP_2.5G_10E Block Diagram
11.9.3 MXP_2.5G_10E Functions
The functions of the MXP_2.5G_10E card are:
- Client Interface
- DWDM Interface
- Multiplexing Function
- Timing Synchronization
- FEC
- SONET/SDH Overhead Byte Processing
- SONET/SDH Overhead Byte Processing
- Client Interface Monitoring
- Automatic Laser Shutdown
- Jitter
- Lamp Test
- Onboard Traffic Generation
- Card level indicators—Table G-1
- Port level indicators—Table G-6.
11.9.3.1 Wavelength Identification
The card uses trunk lasers that are wave-locked, which allows the trunk transmitter to operate on the ITU grid effectively. Table 11-6 describes the required trunk transmit laser wavelengths. The laser is tunable over eight wavelengths at 50-GHz spacing or four at 100-GHz spacing.
11.10 MXP_2.5G_10E_C and MXP_2.5G_10E_L Cards
MXP_2.5G_10E_L: (Cisco ONS 15454 only)
The MXP_2.5G_10E_C and MXP_2.5G_10E_L cards are DWDM muxponders for the ONS 15454 platform that support transparent termination mode on the client side. The faceplate designation of the cards is “4x2.5G 10E MXP C” for the MXP_2.5G_10E_C card and “4x2.5G 10E MXP L” for the MXP_2.5G_10E_L card. The cards multiplex four 2.5-Gbps client signals (4 x OC48/STM-16 SFP) into a single 10-Gbps DWDM optical signal on the trunk side. The MXP_2.5G_10E_C and MXP_2.5G_10E_L cards provide wavelength transmission service for the four incoming 2.5 Gbps client interfaces. The MXP_2.5G_10E_C and MXP_2.5G_10E_L muxponders pass all SONET/SDH overhead bytes transparently.
The digital wrapper function (ITU-T G.709 compliant) formats the DWDM wavelength so that it can be used to set up GCCs for data communications, enable FEC, or facilitate PM.
The MXP_2.5G_10E_C and MXP_2.5G_10E_L cards work with OTN devices defined in ITU-T G.709. The cards support ODU1 to OTU2 multiplexing, an industry standard method for asynchronously mapping a SONET/SDH payload into a digitally wrapped envelope. See the “Multiplexing Function” section.
The MXP_2.5G_10E_C and MXP_2.5G_10E_L cards are not compatible with the MXP_2.5G_10G card, which does not support transparent termination mode.
You can install MXP_2.5G_10E_C and MXP_2.5G_10E_L cards in Slots 1 to 6 and 12 to 17. You can provision a card in a linear configuration, as a BLSR/MS-SPRing, a path protection/SNCP, or a regenerator. The cards can be used in the middle of BLSR/MS-SPRing or 1+1 spans when the cards are configured for transparent termination mode.
The MXP_2.5G_10E_C card features a tunable 1550-nm C-band laser on the trunk port. The laser is tunable across 82 wavelengths on the ITU grid with 50-GHz spacing between wavelengths. The MXP_2.5G_10E_L features a tunable 1580-nm L-band laser on the trunk port. The laser is tunable across 80 wavelengths on the ITU grid, also with 50-GHz spacing. Each card features four 1310-nm lasers on the client ports and contains five transmit and receive connector pairs (labeled) on the card faceplate. The cards uses dual LC connectors on the trunk side and use SFP modules on the client side for optical cable termination. The SFP pluggable modules are SR or IR and support an LC fiber connector.
Note When you create a 4xOC-48 OCHCC circuit, you need to select the G.709 and Synchronous options. A 4xOC-48 OCHCC circuit is supported by G.709 and synchronous mode. This is necessary to provision a 4xOC-48 OCHCC circuit.
11.10.1 Key Features
The MXP_2.5G_10E_C and MXP_2.5G_10E_L cards have the following high level features:
- Four 2.5 Gbps client interfaces (OC-48/STM-16) and one 10 Gbps trunk. The four OC-48 signals are mapped into a ITU-T G.709 OTU2 signal using standard ITU-T G.709 multiplexing.
- Onboard E-FEC processor: The processor supports both standard RS (specified in ITU-T G.709) and E-FEC, which allows an improved gain on trunk interfaces with a resultant extension of the transmission range on these interfaces. The E-FEC functionality increases the correction capability of the transponder to improve performance, allowing operation at a lower OSNR compared to the standard RS (237,255) correction algorithm. A new BCH algorithm implemented in E-FEC allows recovery of an input BER up to 1E-3.
- Pluggable client interface optic modules: The MXP_2.5G_10E_C and MXP_2.5G_10E_L cards have modular interfaces. Two types of optics modules can be plugged into the card. These include an OC-48/STM 16 SR-1 interface with a 7-km (4.3-mile) nominal range (for short range and intra-office applications) and an IR-1 interface with a range up to 40 km (24.9 miles). SR-1 is defined in Telcordia GR-253-CORE and in I-16 (ITU-T G.957). IR-1 is defined in Telcordia GR-253-CORE and in S-16-1 (ITU-T G.957).
- High level provisioning support: The cards are initially provisioned using Cisco TransportPlanner software. Subsequently, the card can be monitored and provisioned using CTC software.
- Link monitoring and management: The cards use standard OC-48 OH (overhead) bytes to monitor and manage incoming interfaces. The cards pass the incoming SDH/SONET data stream and its overhead bytes transparently.
- Control of layered SONET/SDH transport overhead: The cards are provisionable 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.
- Automatic timing source synchronization: The MXP_2.5G_10E_C and MXP_2.5G_10E_L cards normally synchronize from the TCC2/TCC2P/TCC3 card. If for some reason, such as maintenance or upgrade activity, the TCC2/TCC2P/TCC3 is not available, the cards automatically synchronize to one of the input client interface clocks.
- Configurable squelching policy: The cards can be configured to squelch the client interface output if there is LOS at the DWDM receiver or if there is a remote fault. In the event of a remote fault, the card manages MS-AIS insertion.
- The cards are tunable across the full C band (MXP_2.5G_10E_C) or full L band (MXP_2.5G_10E_L), thus eliminating the need to use different versions of each card to provide tunability across specific wavelengths in a band.
11.10.2 Faceplates and Block Diagram
Figure 11-11 shows the MXP_2.5G_10E_C and MXP_2.5G_10E_L faceplates and block diagram.
Figure 11-11 MXP_2.5G_10E _C and MXP_2.5G_10E_L Faceplates and Block Diagram
For information about safety labels for the cards, see the “Class 1 Laser Product Cards” section.
11.10.3 MXP_2.5G_10E_C and MXP_2.5G_10E_L Functions
The functions of the MXP_2.5G_10E_C and MXP_2.5G_10E_L cards are:
- Client Interface
- DWDM Interface
- Multiplexing Function
- Timing Synchronization
- FEC
- SONET/SDH Overhead Byte Processing
- SONET/SDH Overhead Byte Processing
- Client Interface Monitoring
- Automatic Laser Shutdown
- Jitter
- Lamp Test
- Onboard Traffic Generation
- Card level indicators—Table G-1
- Port level indicators—Table G-6.
11.10.3.1 Wavelength Identification
The card uses trunk lasers that are wavelocked, which allows the trunk transmitter to operate on the ITU grid effectively. Both the MXP_2.5G_10E_C and MXP_2.5G_10E_L cards implement the UT2 module. The MXP_2.5G_10E_C card uses a C-band version of the UT2 and the MXP_2.5G_10E_L card uses an L-band version.
Table 11-7 describes the required trunk transmit laser wavelengths for the MXP_2.5G_10E_C card. The laser is tunable over 82 wavelengths in the C band at 50-GHz spacing on the ITU grid.
Table 11-8 describes the required trunk transmit laser wavelengths for the MXP_2.5G_10E_L card. The laser is fully tunable over 80 wavelengths in the L band at 50-GHz spacing on the ITU grid.
11.11 MXP_MR_2.5G and MXPP_MR_2.5G Cards
The MXP_MR_2.5G card aggregates a mix and match of client Storage Area Network (SAN) service client inputs (GE, FICON, Fibre Channel, and ESCON) into one 2.5 Gbps STM-16/OC-48 DWDM signal on the trunk side. It provides one long-reach STM-16/OC-48 port per card and is compliant with Telcordia GR-253-CORE.
Note In Software Release 7.0 and later, two additional operating modes have been made available to the user: pure ESCON (all 8 ports running ESCON), and mixed mode (Port 1 running FC/GE/FICON, and Ports 5 through 8 running ESCON). When the card is part of a system running Software Release 6.0 or below, only one operating mode, (FC/GE) is available for use.
The 2.5-Gbps Multirate Muxponder–Protected–100 GHz–Tunable 15xx.xx-15yy.yy (MXPP_MR_2.5G) card aggregates various client SAN service client inputs (GE, FICON, Fibre Channel, and ESCON) into one 2.5 Gbps STM-16/OC-48 DWDM signal on the trunk side. It provides two long-reach STM-16/OC-48 ports per card and is compliant with ITU-T G.957 and Telcordia GR-253-CORE.
Because the cards are tunable to one of four adjacent grid channels on a 100-GHz spacing, each card is available in eight versions, with 15xx.xx representing the first wavelength and 15yy.yy representing the last wavelength of the four available on the card. In total, 32 DWDM wavelengths are covered in accordance with the ITU-T 100-GHz grid standard, G.692, and Telcordia GR-2918-CORE, Issue 2. The card versions along with their corresponding wavelengths are shown in Table 11-9 .
The muxponders are intended to be used in applications with long DWDM metro or regional unregenerated spans. Long transmission distances are achieved through the use of flat gain optical amplifiers.
The client interface supports the following payload types:
Note Because the client payload cannot oversubscribe the trunk, a mix of client signals can be accepted, up to a maximum limit of 2.5 Gbps.
Table 11-10 shows the input data rate for each client interface, and the encapsulation method. The current version of the ITU-T Transparent Generic Framing Procedure (GFP-T) G.7041 supports transparent mapping of 8B/10B block-coded protocols, including Gigabit Ethernet, Fibre Channel, and FICON.
In addition to the GFP mapping, 1-Gbps traffic on Port 1 or 2 of the high-speed serializer/deserializer (SERDES) is mapped to an STS-24c channel. If two 1-Gbps client signals are present at Port 1 and Port 2 of the SERDES, the Port 1 signal is mapped into the first STS-24c channel and the Port 2 signal into the second STS-24c channel. The two channels are then mapped into an OC-48 trunk channel.
Table 11-11 shows some of the mix and match possibilities on the various client ports. The table is intended to show the full client payload configurations for the card.
11.11.1 Faceplates and Block Diagram
Figure 11-12 shows the MXP_MR_2.5G and MXPP_MR_2.5G faceplates.
Figure 11-12 MXP_MR_2.5G and MXPP_MR_2.5G Faceplates
For information about safety labels for the cards, see the “Class 1M Laser Product Cards” section.
Figure 11-13 shows a block diagram of the MXP_MR_2.5G card. The card has eight SFP client interfaces. Ports 1 and 2 can be used for GE, FC, FICON, or ESCON. Ports 3 through 8 are used for ESCON client interfaces. There are two SERDES blocks dedicated to the high-speed interfaces (GE, FC, FICON, and ESCON) and two SERDES blocks for the ESCON interfaces. A FPGA is provided to support different configurations for different modes of operation. This FPGA has a Universal Test and Operations Physical Interface for ATM (UTOPIA) interface. A transceiver add/drop multiplexer (TADM) chip supports framing. Finally, the output signal is serialized and connected to the trunk front end with a direct modulation laser. The trunk receive signal is converted into an electrical signal with an avalanche photodiode (APD), is deserialized, and is then sent to the TADM framer and FPGA.
The MXPP_MR_2.5G is the same, except a 50/50 splitter divides the power at the trunk interface. In the receive direction, there are two APDs, two SERDES blocks, and two TADM framers. This is necessary to monitor both the working and protect paths. A switch selects one of the two paths to connect to the client interface.
Figure 11-13 MXP_MR_2.5G and MXPP_MR_2.5G Block Diagram
11.11.2 MXP_MR_2.5G and MXPP_MR_2.5G Functions
The functions of the MXP_MR_2.5G and MXPP_MR_2.5G cards are:
- Performance Monitoring
- Distance Extension
- Slot Compatibility
- Interoperability with Cisco MDS Switches
- Client and Trunk Ports
- Automatic Laser Shutdown
- Card level indicators—Table G-1
- Port level indicators—Table G-10
11.12 MXP_MR_10DME_C and MXP_MR_10DME_L Cards
MXP_MR_10DME_L: (Cisco ONS 15454 only)
The MXP_MR_10DME_C and MXP_MR_10DME_L cards aggregate a mix of client SAN service client inputs (GE, FICON, and Fibre Channel) into one 10.0 Gbps STM-64/OC-192 DWDM signal on the trunk side. It provides one long-reach STM-64/OC-192 port per card and is compliant with Telcordia GR-253-CORE and ITU-T G.957.
The cards support aggregation of the following signal types:
- 1-Gigabit Fibre Channel
- 2-Gigabit Fibre Channel
- 4-Gigabit Fibre Channel
- 1-Gigabit Ethernet
- 1-Gigabit ISC-Compatible (ISC-1)
- 2-Gigabit ISC-Peer (ISC-3)
Note On the card faceplates, the MXP_MR_10DME_C and MXP_MR_10DME_L cards are displayed as 10DME_C and 10DME_L, respectively.
The MXP_MR_10DME_C and MXP_MR_10DME_L muxponders pass all SONET/SDH overhead bytes transparently.
The digital wrapper function (ITU-T G.709 compliant) formats the DWDM wavelength so that it can be used to set up GCCs for data communications, enable FEC, or facilitate PM. The MXP_MR_10DME_C and MXP_MR_10DME_L cards work with the OTN devices defined in ITU-T G.709. The cards support ODU1 to OTU2 multiplexing, an industry standard method for asynchronously mapping a SONET/SDH payload into a digitally wrapped envelope. See the “Multiplexing Function” section.
Note Because the client payload cannot oversubscribe the trunk, a mix of client signals can be accepted, up to a maximum limit of 10 Gbps.
You can install MXP_MR_10DME_C and MXP_MR_10DME_L cards in Slots 1 to 6 and 12 to 17.
Note The MXP_MR_10DME_C and MXP_MR_10DME_L cards are not compatible with the MXP_2.5G_10G card, which does not support transparent termination mode.
The MXP_MR_10DME_C card features a tunable 1550-nm C-band laser on the trunk port. The laser is tunable across 82 wavelengths on the ITU grid with 50-GHz spacing between wavelengths. The MXP_MR_10DME_L features a tunable 1580-nm L-band laser on the trunk port. The laser is tunable across 80 wavelengths on the ITU grid, also with 50-GHz spacing. Each card features four 1310-nm lasers on the client ports and contains five transmit and receive connector pairs (labeled) on the card faceplate. The cards uses dual LC connectors on the trunk side and use SFP modules on the client side for optical cable termination. The SFP pluggable modules are SR or IR and support an LC fiber connector.
Table 11-12 shows the input data rate for each client interface, and the encapsulation method. The current version of the GFP-T G.7041 supports transparent mapping of 8B/10B block-coded protocols, including Gigabit Ethernet, Fibre Channel, ISC, and FICON.
In addition to the GFP mapping, 1-Gbps traffic on Port 1 or 2 of the high-speed SERDES is mapped to an STS-24c channel. If two 1-Gbps client signals are present at Port 1 and Port 2 of the high-speed SERDES, the Port 1 signal is mapped into the first STS-24c channel and the Port 2 signal into the second STS-24c channel. The two channels are then mapped into an OC-48 trunk channel.
There are two FPGAs on each MXP_MR_10DME_C and MXP_MR_10DME_L, and a group of four ports is mapped to each FPGA. Group 1 consists of Ports 1 through 4, and Group 2 consists of Ports 5 through 8. Table 11-13 shows some of the mix and match possibilities on the various client data rates for Ports 1 through 4, and Ports 5 through 8. An X indicates that the data rate is supported in that port.
GFP-T PM is available through 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.
A buffer-to-buffer credit management scheme provides FC flow control. With this feature 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_10DME_C and MXP_MR_10DME_L cards support FC credit-based flow control with a buffer-to-buffer credit extension of up to 1600 km (994.1 miles) for 1G FC, up to 800 km (497.1 miles) for 2G FC, or up to 400 km (248.5 miles) for 4G FC. The feature can be enabled or disabled.
The MXP_MR_10DME_C and MXP_MR_10DME_L cards feature 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 cards 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. The trunk port is a dual-LC connector with a 45 degree downward angle.
The throughput of the MXP_MR_10DME_C and MXP_MR_10DME_L cards is affected by the following parameters:
- Distance extension—If distance extension is enabled on the card, it provides more throughput but more latency. If distance extension is disabled on the card, the buffer to buffer credits on the storage switch affects the throughput; higher the buffer to buffer credits higher is the throughput.
Note For each link to operate at the maximum throughput, it requires a minimum number of buffer credits to be available on the devices which the link connects to. The number of buffer credits required is a function of the distance between the storage switch extension ports and the link bandwidth, that is, 1G, 2G, or 4G. These buffer credits are provided by either the storage switch (if distance extension is disabled) or by both the storage switch and the card (if distance extension is enabled).
- Forward Error Correction (FEC)—If Enhanced FEC (E-FEC) is enabled on the trunk port of the card, the throughout is significantly reduced in comparison to standard FEC being set on the trunk port.
Note If distance extension is enabled on the card, the FEC status does not usually affect the throughput of the card.
The resultant throughput of the card is usually the combined effect of the above parameters.
11.12.1 Key Features
The MXP_MR_10DME_C and MXP_MR_10DME_L cards have the following high-level features:
- Onboard E-FEC processor: The processor supports both standard RS (specified in ITU-T G.709) and E-FEC, which allows an improved gain on trunk interfaces with a resultant extension of the transmission range on these interfaces. The E-FEC functionality increases the correction capability of the transponder to improve performance, allowing operation at a lower OSNR compared to the standard RS (237,255) correction algorithm. A new BCH algorithm implemented in E-FEC allows recovery of an input BER up to 1E-3.
- Pluggable client interface optic modules: The MXP_MR_10DME_C and MXP_MR_10DME_L cards have modular interfaces. Two types of optics modules can be plugged into the card. These include an OC-48/STM 16 SR-1 interface with a 7-km (4.3-mile) nominal range (for short range and intra-office applications) and an IR-1 interface with a range up to 40 km (24.9 miles). SR-1 is defined in Telcordia GR-253-CORE and in I-16 (ITU-T G.957). IR-1 is defined in Telcordia GR-253-CORE and in S-16-1 (ITU-T G.957).
- Y-cable protection: Supports Y-cable protection between the same card type only, on ports with the same port number and signal rate. See the “Y-Cable Protection” section for more detailed information.
- High level provisioning support: The cards are initially provisioned using Cisco TransportPlanner software. Subsequently, the card can be monitored and provisioned using CTC software.
- ALS: A safety mechanism used in the event of a fiber cut. For details regarding ALS provisioning for the MXP_MR_10DME_C and MXP_MR_10DME_L cards, see the “G162 Change the ALS Maintenance Settings” section.
- Link monitoring and management: The cards use standard OC-48 OH bytes to monitor and manage incoming interfaces. The cards pass the incoming SDH/SONET data stream and its OH bytes transparently.
- Control of layered SONET/SDH transport overhead: The cards are provisionable 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.
- Automatic timing source synchronization: The MXP_MR_10DME_C and MXP_MR_10DME_L cards normally synchronize from the TCC2/TCC2P/TCC3 card. If for some reason, such as maintenance or upgrade activity, the TCC2/TCC2P/TCC3 is not available, the cards automatically synchronize to one of the input client interface clocks.
Note MXP_MR_10DME_C and MXP_MR_10DME_L cards cannot be used for line timing.
- Configurable squelching policy: The cards can be configured to squelch the client interface output if there is LOS at the DWDM receiver or if there is a remote fault. In the event of a remote fault, the card manages MS-AIS insertion.
- The cards are tunable across the full C band (MXP_MR_10DME_C) or full L band (MXP_MR_10DME_L), thus eliminating the need to use different versions of each card to provide tunability across specific wavelengths in a band.
- You can provision a string (port name) for each fiber channel/FICON interface on the MXP_MR_10DME_C and MXP_MR_10DME_L 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.
- From Software Release 9.0, the fast switch feature of MXP_MR_10DME_C and MXP_MR_10DME_L cards along with the buffer-to-buffer credit recovery feature of MDS switches, prevents reinitialization of ISL links during Y-cable switchovers.
11.12.2 Faceplates and Block Diagram
Figure 11-14 shows the MXP_MR_10DME_C and MXP_MR_10DME_L faceplates and block diagram.
Figure 11-14 MXP_MR_10DME_C and MXP_MR_10DME_L Faceplates and Block Diagram
For information about safety labels for the cards, see the “Class 1M Laser Product Cards” section.
11.12.3 MXP_MR_10DME_C and MXP_MR_10DME_L Functions
The functions of the MXP_MR_10DME_C and MXP_MR_10DME_L cards are:
11.12.3.1 Wavelength Identification
The card uses trunk lasers that are wavelocked, which allows the trunk transmitter to operate on the ITU grid effectively. Both the MXP_MR_10DME_C and MXP_MR_10DME_L cards implement the UT2 module. The MXP_MR_10DME_C card uses a C-band version of the UT2 and the MXP_MR_10DME_L card uses an L-band version.
Table 11-14 describes the required trunk transmit laser wavelengths for the MXP_MR_10DME_C card. The laser is tunable over 82 wavelengths in the C band at 50-GHz spacing on the ITU grid.
Table 11-15 describes the required trunk transmit laser wavelengths for the MXP_MR_10DME_L card. The laser is fully tunable over 80 wavelengths in the L band at 50-GHz spacing on the ITU grid.
11.13 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards
The 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards aggregate a variety of client service inputs (Gigabit Ethernet, Fibre Channel, OTU2, OTU2e, and OC-192) into a single 40-Gbps OTU3/OTU3e signal on the trunk side.
Note In CTC, the 40E-MXP-C and 40ME-MXP-C card is displayed with the same card name, 40E-MXP-C.
The 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards support aggregation of the following signals:
– 10 Gigabit Ethernet LAN-Phy (CBR mapping)
(only on 40E-MXP-C and 40ME-MXP-C cards)
– 10 GigabitEthernet LAN-Phy (GFP framing)
– 10 GigabitEthernet LAN-Phy (WIS framing)
The 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C muxponders pass all SONET/SDH overhead bytes transparently, section, or line termination.
The digital wrapper function (ITU-T G.709 compliant) formats the DWDM wavelength so that it can be used to set up GCCs for data communications, enable FEC, or facilitate performance monitoring. The 40G-MXP-C, 40E-MXP-C and 40ME-MXP-C cards work with the OTN devices defined in ITU-T G.709. The card supports ODTU23 multiplexing, an industry standard method for asynchronously mapping client payloads into a digitally wrapped envelope. See the “Multiplexing Function” section.
You can install and provision the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards in a linear configuration in:
- Slots 1 to 5 and 12 to 16 in ONS 15454 DWDM chassis
- Slot 2 in ONS 15454 M2 chassis
- Slots 2 to 6 in ONS 15454 M6 chassis
The client ports of the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards interoperates with all the existing TXP/MXP (OTU2 trunk) cards.
The auto negotiation is not supported on the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards in 8G FC client mode. Hence, during interoperation, the auto negotiation of the 8G-FC client port of the other device connected to 8G-FC client port on 40G-MXP-C, 40E-MXP-C, or 40ME-MXP-C card must be set to Fixed/Disabled.
The client port of 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards does not interoperate with OTU2_XP card when the signal rate is OTU1e (11.049 Gbps) and the “No Fixed Stuff” option is enabled on the trunk port of OTU2_XP card.
For OTU2 and OTU2e client protocols, Enhanced FEC (EFEC) is not supported on Port 1 of the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards. Table 11-16 lists the FEC configuration supported on OTU2/OTU2e protocol for 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards.
When setting up the card for the first time, or when the card comes up after clearing the LOS-P condition due to fiber cut, the trunk port of the 40G-MXP-C card takes about 6 minutes to lock a signal. The trunk port of the 40G-MXP-C card raises an OTUK-LOF alarm when the card is comes up. The alarm clears when the trunk port locks the signal.
When a protection switch occurs on the 40E-TXP-C and 40ME-TXP-C cards, the recovery from PSM protection switch takes about 3 to 4 minutes.
The 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards is tunable over C-band on the trunk port. The 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards support pluggable XFPs on the client ports on the card faceplate. The card uses dual LC connectors on the trunk side, and XFP modules on the client side for optical cable termination. The XFP pluggable modules are SR, LR, MM, DWDM, or CWDM and support an LC fiber connector. The 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards contains four XFP modules for the client interfaces. For optical termination, each XFP uses two LC connectors, which are labeled TX and RX on the faceplate. The trunk port is a dual LC connector facing downward at 45 degrees.
Table 11-17 shows the input data rate for each client interface.
11.13.1 Key Features
The 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards provides the following key features:
- The 40G-MXP-C card uses the RZ-DQPSK 40G modulation format.
- The 40E-MXP-C and 40ME-MXP-C cards uses the CP-DQPSK modulation format.
- Onboard E-FEC processor—The E-FEC functionality improves the correction capability of the transponder to improve performance, allowing operation at a lower OSNR compared to the standard RS (239,255) correction algorithm. A new BCH algorithm implemented (according to G.975.1 I.7) in E-FEC allows recovery of an input BER up to 1E-3. The 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards support both the standard RS (specified in ITU-T G.709) and E-FEC standard, which allows an improved gain on trunk interfaces with a resultant extension of the transmission range on these interfaces.
- Y-cable protection—Supports Y-cable protection only between the same card type on ports with the same port number and signal rate. For more information on Y-cable protection, seethe “Y-Cable and Splitter Protection” section.
Note Y-cable cannot be created on a 10 GE port when WIS framing is enabled on the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards.
- Unidirectional regeneration—The 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards supports unidirectional regeneration configuration. Each 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C card in the configuration regenerates the signal received from another 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C card in one direction.
Note When you configure the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards in the Unidirectional Regen mode, ensure that the payload is not configured on the pluggable port modules of the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C card.
Figure 11-15 shows a typical unidirectional regeneration configuration.
Figure 11-15 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards in Unidirectional Regeneration Configuration
- High level provisioning support—The cards are initially provisioned using Cisco Transport Planner software. Subsequently, the card can be monitored and provisioned using CTC software.
- Automatic Laser Shutdown (ALS)—A safety mechanism, Automatic Laser Shutdown (ALS), is used in the event of a fiber cut. The Auto Restart ALS option is supported only for OC-192/STM-64 and OTU2 payloads. The Manual Restart ALS option is supported for all payloads. For more information on provisioning ALS for the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards, see the “G162 Change the ALS Maintenance Settings” section.
- Control of layered SONET/SDH transport overhead—The cards are provisionable 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.
- Automatic timing source synchronization—The 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards synchronize to the TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE cards. Because of a maintenance or upgrade activity, if the TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE cards are not available, the cards automatically synchronize to one of the input client interface clocks.
- Squelching policy—The cards are set to squelch the client interface output if there is LOS at the DWDM receiver, or if there is a remote fault. In the event of a remote fault, the card manages MS-AIS insertion.
- The 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards are tunable across the full C-band wavelength.
11.13.2 Faceplate and Block Diagram
Figure 11-16 shows the faceplate and block diagram of the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards.
Figure 11-16 Faceplate and Block Diagram of the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Cards
For information about safety labels for the cards, see the “Class 1M Laser Product Cards” section.
11.13.3 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C Functions
The functions of the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards are:
11.13.3.1 Wavelength Identification
The 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards use trunk lasers that are wavelocked, which allows the trunk transmitter to operate on the ITU grid effectively. These cards implement the UT2 module; they use a C-band version of the UT2.
Table 11-18 lists the required trunk transmit laser wavelengths for the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards. The laser is tunable over 82 wavelengths in the C-band at 50-GHz spacing on the ITU grid.
11.14 GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards
GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards are Gigabit Ethernet Xponders for the ONS 15454 ANSI and ETSI platforms.
Note GE_XPE card is the enhanced version of the GE_XP card and 10GE_XPE card is the enhanced version of the 10GE_XP card.
The cards aggregate Ethernet packets received on the client ports for transport on C-band trunk ports that operate on a 100-GHz grid. The trunk ports operate with ITU-T G.709 framing and either FEC or E-FEC. The GE_XP and 10GE_XP cards are designed for bulk point-to-point transport over 10GE LAN PHY wavelengths for Video-on-Demand (VOD), or broadcast video across protected 10GE LAN PHY wavelengths. The GE_XPE and 10GE_XPE cards are designed for bulk GE_XPE or 10GE_XPE point-to-point, point-to-multipoint, multipoint-to-multipoint transport over 10GE LAN PHY wavelengths for Video-on-Demand (VOD), or broadcast video across protected 10GE LAN PHY wavelengths.
You can install and provision the GE_XP, and GE_XPE cards in a linear configuration in:
- Slots 1 to 5 and 12 to 16 in ONS 15454 DWDM chassis
- Slot 2 in ONS 15454 M2 chassis
- Slots 2 to 6 in ONS 15454 M6 chassis
The 10GE_XP and 10GE_XPE cards can be installed in Slots 1 through 6 or 12 through 17. The GE_XP and GE_XPE are double-slot cards with twenty Gigabit Ethernet client ports and two 10 Gigabit Ethernet trunk ports. The 10GE_XP and 10GE_XPE are single-slot cards with two 10 Gigabit Ethernet client ports and two 10 Gigabit Ethernet trunk ports. The client ports support SX, LX, and ZX SFPs and SR and 10GBASE-LR XFPs. (LR2 XFPs are not supported.) The trunk ports support a DWDM XFP.
The RAD pluggables (ONS-SC-E3-T3-PW= and ONS-SC-E1-T1-PW=) do not support:
GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards can be provisioned to perform different Gigabit Ethernet transport roles. All the cards can work as Layer 2 switches. However, the 10GE_XP and 10GE_XPE cards can also perform as a 10 Gigabit Ethernet transponders (10GE TXP mode), and the GE_XP and GE_XPE can perform as a 10 Gigabit Ethernet or 20 Gigabit Ethernet muxponders (10GE MXP or 20GE MXP mode). Table 11-19 shows the card modes supported by each card.
Note Changing the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card mode requires the ports to be in a OOS-DSBL (ANSI) or Locked, disabled (ETSI) service state. In addition, no circuits can be provisioned on the cards when the mode is being changed.
11.14.1 Key Features
The GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards have the following high-level features:
- Link Aggregation Control Protocol (LACP) that allows you to bundle several physical ports together to form a single logical channel.
- Ethernet Connectivity Fault Management (CFM) protocol that facilitates proactive connectivity monitoring, fault verification, and fault isolation.
- Ethernet Operations, Administration, and Maintenance (OAM) protocol that facilitates link monitoring, remote failure indication, and remote loopback.
- Resilient Ethernet Protocol (REP) that controls network loops, handles link failures, and improves convergence time.
- Configurable service VLANs (SVLANs) and customer VLANs (CVLANs).
- Ingress rate limiting that can be applied on both SVLANs and CVLANs. You can create SVLAN and CVLAN profiles and can associate a SVLAN profile to both UNI and NNI ports; however, you can associate a CVLAN profile only to UNI ports.
- CVLAN rate limiting that is supported for QinQ service in selective add mode.
- Differentiated Services Code Point (DSCP) to class of service (CoS) mapping that you can configure for each port. You can configure the CoS of the outer VLAN based on the incoming DSCP bits. This feature is supported only on GE_XPE and 10GE_XPE cards.
- Ports, in Layer 2 switch mode, can be provisioned as network-to-network interfaces (NNIs) or user-network interfaces (UNIs) to facilitate service provider to customer traffic management.
- Broadcast drop-and-continue capability for VOD and broadcast video applications.
- Gigabit Ethernet MXP, TXP, and Layer 2 switch capability over the ONS 15454 DWDM platform.
- Compatible with the ONS 15454 ANSI high-density shelf assembly, the ONS 15454 ETSI shelf assembly, ONS 15454 ETSI high-density shelf assembly, ONS 15454 M2, and the ONS 15454 M6 shelf assemblies. Compatible with TCC2, TCC2P, TCC3, TNC, TNCE, TSC, and TSCE cards.
- Far-End Laser Control (FELC) that is supported on copper SFPs from Release 8.52 and later releases. For more information on FELC, see the “Far-End Laser Control” section.
- Layer 2 switch mode that provides VLAN translation, QinQ, ingress CoS, egress QoS, Fast Ethernet protection switching, and other Layer 2 Ethernet services.
- Interoperable with TXP_MR_10E and TXP_MR_10E_C cards. Also interoperable with Cisco Catalyst 6500 and Cisco 7600 series Gigabit Ethernet, 10 GE interfaces and CRS-1 10GE interfaces.
- The GE_XP and GE_XPE cards have twenty Gigabit Ethernet client ports and two 10 Gigabit Ethernet trunk ports. The 10GE_XP and 10GE_XPE cards have two 10 Gigabit Ethernet client ports and two 10 Gigabit Ethernet trunk ports. The client Gigabit Ethernet signals are mapped into an ITU-T G.709 OTU2 signal using standard ITU-T G.709 multiplexing when configured in one of the MXP modes (10GE MXP or 20GE MXP).
- ITU-T G.709 framing with standard Reed-Soloman (RS) (255,237) FEC. Performance monitoring and ITU-T G.709 Optical Data Unit (ODU) synchronous and asynchronous mapping. E-FEC with ITU-T G.709 ODU and 2.7 Gbps with greater than 8 dB coding gain.
- IEEE 802.3 frame format that is supported for 10 Gigabit Ethernet interfaces. The minimum frame size is 64 bytes. The maximum frame size is user-provisionable.
- MAC learning capability in Layer 2 switch mode.
- MAC address retrieval in cards provisioned in the L2-over-DWDM mode.
- When a port is in UNI mode, tagging can be configured as transparent or selective. In transparent mode, only SVLANs in the VLAN database of the node can be configured. In selective mode, a CVLAN- to-SVLAN relationship can be defined.
- Layer 2 VLAN port mapping that allows the cards to be configured as multiple Gigabit Ethernet TXPs and MXPs.
- Y-cable protection is configurable in TXP and MXP modes.
- Two protection schemes are available in Layer 2 mode. They are:
– 1+1 protection—Protection scheme to address card, port, or shelf failures for client ports.
– Fast Automatic Protection—Protection scheme to address card, port, or shelf failures for trunk ports.
- End-to-end Ethernet link integrity.
- Pluggable client interface optic modules (SFPs and XFPs)—Client ports support tri-rate SX, LX, and ZX SFPs, and 10-Gbps SR1 XFPs.
- Pluggable trunk interface optic modules; trunk ports support the DWDM XFP.
- Internet Group Management Protocol (IGMP) snooping that restricts the flooding of multicast traffic by forwarding multicast traffic to those interfaces where a multicast device is present.
- Multicast VLAN Registration (MVR) for applications using wide-scale deployment of multicast traffic across an Ethernet ring-based service provider network.
- Ingress CoS that assigns a CoS value to the port from 0 (highest) to 7 (lowest) and accepts CoS of incoming frames.
- Egress QoS that defines the QoS capabilities for the egress port.
- MAC address learning that facilitates switch processing.
- Storm Control that limits the number of packets passing through a port. You can define the maximum number of packets allowed per second for the following types of traffic: Broadcast, Multicast, and Unicast. The threshold for each type of traffic is independent and the maximum number of packets allowed per second for each type of traffic is 16777215.
11.14.2 Protocol Compatibility list
Table 11-20 lists the protocol compatibility for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards.
11.14.3 Faceplate and Block Diagram
Figure 11-17 shows the GE_XP faceplate and block diagram. The GE_XPE faceplate and block diagram looks the same.
Figure 11-17 GE_XP and GE_XPE Faceplates and Block Diagram
The GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards have two trunk ports. The GE_XP and GE_XPE trunk ports are displayed as follows:
- Trunk 1 and Trunk 2 on the faceplate
- 21-1 and 22-1 on CTC
- 21 (Trunk) and 22 (Trunk) on the Optics Thresholds table
Figure 11-18 shows the 10GE_XP faceplate and block diagram. The 10 GE_XPE faceplate and block diagram looks the same.
Figure 11-18 10GE_XP and 10GE_XPE Faceplates and Block Diagram
The 10GE_XP and 10GE_XPE card trunk ports are displayed as follows:
- Trunk 1 and Trunk 2 on the faceplate
- 3-1 and 4-1 on CTC
- 3 (Trunk) and 4 (Trunk) on the Optics Thresholds table
For information about safety labels for the cards, see the “Class 1M Laser Product Cards” section.
11.14.4 GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Functions
The functions of the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards are:
11.14.4.1 Client Interface
The client interface is implemented with separately orderable SFP or XFP modules. The client interfaces support the following tri-rate SFPs and XFPs using dual LC connectors and multimode fiber:
- SFP - GE/1G-FC/2G-FC - 850 nm - MM - LC (PID ONS-SE-G2F-SX)
- SFP - GE/1G-FC/2G-FC 1300 nm - SM - LC (PID ONS-SE-G2F-LX)
- SFP - GE/1G-FC/2G-FC 1300 nm - SM - LC (PID ONS-SE-G2F-ZX)
-
SFP - 10/100/1000Base-T - Copper (PID ONS-SE-ZE-EL) Intra office up to 100;
Cable: RJ45 STP CAT5, CAT5E, and CAT6 - SFP - 1000Base BX D/Gigabit Ethernet 1550 nm - SM - LC (PID ONS-SE-GE-BXD)
- SFP - 1000Base BX U/Gigabit Ethernet 1550 nm - SM - LC (PID ONS-SE-GE-BXU)
- SFP - Fast Ethernet 1310 nm - SM - LC (PID ONS-SI-100-LX10)
- SFP - Fast Ethernet 1310 nm - MM - LC (PID ONS-SI-100-FX)
- SFP - Fast Ethernet over DS1/E1 - SM - LC (PID ONS-SC-EOP1)
- SFP - Fast Ethernet over DS3/E3 - SM - LC (PID ONS-SC-EOP3)
- SFP - E1/DS1 over Fast Ethernet - SM - LC (PID ONS-SC-E1-T1-PW)
Note SFP - E3/DS3 PDH over Fast Ethernet - SM - LC (PID ONS-SC-E3-T3-PW) The recommended topology for using ONS-SC-E1-T1-PW and ONS-SC-E3-T3-PW SFPs is shown in Figure 11-19.
Figure 11-19 Recommended Topology for Using ONS-SC-E1-T1-PW and ONS -SC-E3-T3-PW SFPs
The client interfaces support the following dual-rate XFP using dual LC connectors and single-mode fiber:
- XFP - OC-192/STM-64/10GE/10-FC/OTU2 - 1310 SR - SM LC (PID: ONS-XC-10G-S1)
- XFP - 10GE - 1550 nm - SM - LC (PID ONS-XC-10G-L2)
- XFP - 10GE - 1550 nm - SM - LC (PID ONS-XC-10G-C)
Note If ONS-XC-10G-C XFP is used on GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards on client port 1, the maximum temperature at which the system qualifies is +45 degree Celsius.
The client interfaces support the following multimode XFP using dual LC connectors and multi-mode fiber:
11.14.4.2 DWDM Trunk Interface
The GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards have two 10 Gigabit Ethernet trunk ports operating at 10 Gigabit Ethernet (10.3125 Gbps) or 10 Gigabit Ethernet into OTU2 (nonstandard 11.0957 Gbps). The ports are compliant with ITU-T G.707, ITU-T G.709, and Telcordia GR-253-CORE standards. The ports are capable of carrying C-band and L-band wavelengths through insertion of DWDM XFPs. Forty channels are available in the 1550-nm C band 100-GHz ITU grid, and forty channels are available in the L band.
11.14.4.3 Configuration Management
The GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards support the following configuration management parameters:
- Port name—User-assigned text string.
- Admin State/Service State—Administrative and service states to manage and view port status.
- MTU—Provisionable maximum transfer unit (MTU) to set the maximum number of bytes per frames accepted on the port.
- Mode—Provisional port mode, either Autonegotiation or the port speed.
- Flow Control—Flow control according to IEEE 802.1x pause frame specification can be enabled or disabled for TX and RX ports.
- Bandwidth—Provisionable maximum bandwidth allowed for the port.
- Ingress CoS—Assigns a CoS value to the port from 0 (highest) to 7 (lowest) and accepts CoS of incoming frames.
- Egress QoS—Defines the QoS capabilities at the egress port.
- NIM—Defines the port network interface management type based on Metro Ethernet Forum specifications. Ports can be defined as UNI or NNI.
- MAC Learning—MAC address learning to facilitate switch processing.
- VLAN tagging provided according to the IEEE 802.1Q standard.
Note When the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards are provisioned in a MXP or TXP mode, only the following parameters are available: Port Name, State, MTU, Mode, Flow control, and Bandwidth.
11.14.4.4 Security
GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE card ports can be provisioned to block traffic from a user-defined set of MAC addresses. The remaining traffic is normally switched. You can manually specify the set of blocked MAC addresses for each port. Each port of the card can receive traffic from a limited predefined set of MAC addresses. The remaining traffic will be dropped. This capability is a subset of the Cisco IOS “Port Security” feature.
11.14.4.5 Card Protection
The following card protection schemes are available for the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards.
- Y-Cable Protection—See the “Y-Cable Protection” section.
- 1+1 Protection—See the “1+1 Protection” section.
- Layer 2 Over DWDM Protection—See the “Layer 2 Over DWDM Protection” section.
11.14.4.5.1 Related Procedures for Card Protection
The following are the related procedures for creating card protection on GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards:
11.14.5 IGMP Snooping
As networks increase in size, multicast routing becomes critically important as a means to determine which segments require multicast traffic and which do not. IP multicasting allows IP traffic to be propagated from one source to a number of destinations, or from many sources to many destinations. Rather than sending one packet to each destination, one packet is sent to the multicast group identified by a single IP destination group address. GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards can learn up to a maximum of 1024 multicast groups. This includes groups on all the VLANs.
Internet Group Management Protocol (IGMP) snooping restricts the flooding of multicast traffic by forwarding multicast traffic to those interfaces where a multicast device is present.
When the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card receives an IGMP leave group message from a host, it removes the host port from the multicast forwarding table after generating group specific queries to ensure that no other hosts interested in traffic for the particular group are present on that port. Even in the absence of any “leave” message, the cards have a timeout mechanism to update the group table with the latest information. After a card relays IGMP queries from the multicast router, it deletes entries periodically if it does not receive any IGMP membership reports from the multicast clients.
In a multicast router, general queries are sent on a VLAN when Protocol Independent Multicast (PIM) is enabled on the VLAN. The GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card forwards queries to all ports belonging to the VLAN. All hosts interested in this multicast traffic send Join requests and are added to the forwarding table entry. The Join requests are forwarded only to router ports. By default, these router ports are learned dynamically. However, they can also be statically configured at the port level in which case the static configuration overrides dynamic learning.
For information about interaction of IGMP with other protocols, see the “Protocol Compatibility list” section.
11.14.5.1 IGMP Snooping Guidelines and Restrictions
The following guidelines and restrictions apply to IGMP snooping on GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards:
- IGMP snooping V2 is supported as specified in RFC 4541.
- IGMP snooping V3 is not supported and the packets are flooded in the SVLAN.
- Layer 2 multicast groups learned through IGMP snooping are dynamic.
- GE_XP and 10GE_XP cards support IGMP snooping on 128 stacked VLANs and GE_XPE and 10GE_XPE cards support up to 256 stacked VLANs that are enabled.
- IGMP snooping can be configured per SVLAN or CVLAN. By default, IGMP snooping is disabled on all SVLANs and CVLANs.
- IGMP snooping on CVLAN is enabled only when:
– UNI ports are in selective add and selective translate modes. For each UNI port, a CVLAN must be specified for which IGMP snooping is to be enabled.
- IGMP snooping can be enabled only on one CVLAN per port. If you enable IGMP snooping on CVLAN, you cannot enable IGMP snooping on the associated SVLAN and vice versa. The number of VLANs that can be enabled for IGMP snooping cannot exceed 128.
- When IGMP snooping is enabled on double-tagged packets, CVLAN has to be the same on all ports attached to the same SVLAN.
- When IGMP snooping is working with the Fast Automatic Protection Switch (FAPS) in a ring-based setup, it is advisable to configure all NNI ports as static router ports. This minimizes the multicast traffic hit when a FAPS switchover occurs.
The following conditions are raised from IGMP snooping at the card:
- MCAST-MAC-TABLE-FULL—This condition is raised when the multicast table is full and a new join request is received. This table is cleared when at least one entry gets cleared from the multicast table after the alarm is raised.
- MCAST-MAC-ALIASING—This condition is raised when there are multiple L3 addresses that map to the same L2 address in a VLAN. This is a transient condition.
For more information on severity level of these conditions and procedure to clear these alarms, refer to the Cisco ONS 15454 Troubleshooting Guide .
11.14.5.2 Fast-Leave Processing
Note Fast-Leave processing is also known as Immediate-Leave.
IGMP snooping Fast-Leave processing allows the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE to remove an interface that sends a leave message from the forwarding table without first sending group specific queries to the interface. When you enable IGMP Fast-Leave processing, the card immediately removes a port from the IP multicast group when it detects an IGMP, version 2 (IGMPv2) leave message on that port.
11.14.5.3 Static Router Port Configuration
Multicast-capable ports are added to the forwarding table for every IP multicast entry. The card learns of such ports through the PIM method.
11.14.5.4 Report Suppression
Report suppression is used to avoid a storm of responses to an IGMP query. When this feature is enabled, a single IGMP report is sent to each multicast group in response to a single query. Whenever an IGMP snooping report is received, report suppression happens if the report suppression timer is running. The Report suppression timer is started when the first report is received for a general query. Then this time is set to the response time specified in general query.
11.14.5.5 IGMP Statistics and Counters
An entry in a counter contains multicasting statistical information for the IGMP snooping capable GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card. It provides statistical information about IGMP messages that have been transmitted and received. IGMP statistics and counters can be viewed via CTC from the Performance > Ether Ports > Statistics tab.
This information can be stored in the following counters:
- cisTxGeneralQueries—Number of general queries transmitted through an interface.
- cisTxGroupSpecificQueries—Total group specific queries transmitted through an interface.
- cisTxReports—Total membership reports transmitted through an interface.
- cisTxLeaves—Total Leave messages transmitted through an interface.
- cisRxGeneralQueries—Total general queries received at an interface.
- cisRxGroupSpecificQueries—Total Group Specific Queries received at an interface.
- cisRxReports—Total Membership Reports received at an interface.
- cisRxLeaves—Total Leave messages received at an interface.
- cisRxValidPackets—Total valid IGMP packets received at an interface.
- cisRxInvalidPackets—Total number of packets that are not valid IGMP messages received at an interface.
11.14.5.6 Related Procedure for Enabling IGMP Snooping
To enable IGMP snooping on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards, see the “G204 Enable IGMP Snooping on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards” section.
11.14.6 Multicast VLAN Registration
Multicast VLAN Registration (MVR) is designed for applications using wide-scale deployment of multicast traffic across an Ethernet-ring-based service provider network (for example, the broadcast of multiple television channels over a service-provider network). MVR allows a subscriber on a port to subscribe and unsubscribe to a multicast stream on the network-wide multicast VLAN. It allows the single multicast VLAN to be shared in the network while subscribers remain in separate VLANs. MVR provides the ability to continuously send multicast streams in the multicast VLAN, but to isolate the streams from the subscriber VLANs for bandwidth and security reasons.
MVR assumes that subscriber ports subscribe and unsubscribe (“Join” and “Leave”) these multicast streams by sending out IGMP Join and Leave messages. These messages can originate from an IGMP version-2-compatible host with an Ethernet connection. MVR operates on the underlying mechanism of IGMP snooping. MVR works only when IGMP snooping is enabled.
The card identifies the MVR IP multicast streams and their associated MAC addresses in the card forwarding table, intercepts the IGMP messages, and modifies the forwarding table to include or remove the subscriber as a receiver of the multicast stream, even though the receivers is in a different VLAN than the source. This forwarding behavior selectively allows traffic to cross between different VLANs.
Note When MVR is configured, the port facing the router must be configured as NNI in order to allow the router to generate or send multicast stream to the host with the SVLAN. If router port is configured as UNI, the MVR will not work properly.
11.14.6.1 Related Procedure for Enabling MVR
To enable MVR on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards, see the “G206 Enable MVR on a GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Card” section.
11.14.7 MAC Address Learning
The GE_XPE and 10 GE_XPE cards support 32K MAC addresses. MAC address learning can be enabled or disabled per SVLAN on GE_XPE and 10 GE_XPE cards. The cards learn the MAC address of packets they receive on each port and add the MAC address and its associated port number to the MAC address learning table. As stations are added or removed from the network, the GE_XPE and 10 GE_XPE cards update the MAC address learning table, adding new dynamic addresses and aging out those that are currently not in use.
MAC address learning can be enabled or disabled per SVLAN. When the configuration is changed from enable to disable, all the related MAC addresses are cleared. The following conditions apply:
- If MAC address learning is enabled on per port basis, the MAC address learning is not enabled on all VLANs, but only on VLANs that have MAC address learning enabled.
- If per port MAC address learning is disabled then the MAC address learning is disabled on all VLANs, even if it is enabled on some of the VLAN supported by the port.
- If the per port MAC address learning is configured on GE-XP and 10 GE-XP cards, before upgrading to GE-XPE or 10 GE-XPE cards, enable MAC address learning per SVLAN. Failing to do so disables MAC address learning.
11.14.7.1 Related Procedure for MAC Address Learning
To enable MAC address learning on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards, see the “G221 Enable MAC Address Learning on SVLANs for GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards” section.
11.14.8 MAC Address Retrieval
MAC addresses learned can be retrieved or cleared on GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards provisioned in L2-over-DWDM mode. The MAC addresses can be retrieved using the CTC or TL1 interface.
GE_XPE and 10GE_XPE cards support 32K MAC addresses and GE_XP and 10GE_XP cards support 16K MAC addresses. To avoid delay in processing requests, the learned MAC addresses are retrieved using an SVLAN range. The valid SVLAN range is from 1 to 4093.
The MAC addresses of the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards can also be retrieved. The card MAC addresses are static and are used for troubleshooting activities. One MAC address is assigned to each client, trunk, and CPU ports of the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card. These internal MAC addresses can be used to determine if the packets received on the far-end node are generated by GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards.
11.14.8.1 Related Procedure for MAC Address Retrieving
To retrieve and clear MAC addresses on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards, see the “G237 Retrieve and Clear MAC Addresses on SVLANs for GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards” section.
11.14.9 Link Integrity
The GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE card support end-to-end Ethernet link integrity. This capability is integral to providing an Ethernet private line service and correct operation of Layer 2 and Layer 3 protocols on the attached Ethernet devices.
The link integrity feature propagates a trunk fault on all the affected SVLAN circuits in order to squelch the far end client interface. Ethernet-Advanced IP Services (E-AIS) packets are generated on a per-port/SVLAN basis. An E-AIS format is compliant with ITU Y.1731.
Note E-AIS packets are marked with a CoS value of 7 (also called .1p bits). Ensure that the network is not overloaded and there is sufficient bandwidth for this queue in order to avoid packet drops.
When link integrity is enabled on a per-port SVLAN basis, E-AIS packets are generated when the following alarms are raised;
When link integrity is enabled, GE_XP and 10 GE_XP card supports up to128 SVLANs and GE_XPE, 10 GE_XPE can support up to 256 SVLANs.
11.14.9.1 Related Procedure for Enabling Link Integrity
To enable link integrity on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards, see the “G205 Enable Link Integrity on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards” section.
11.14.10 Ingress CoS
Ingress CoS functionality enables differentiated services across the GE_XPE and 10GE_XPE cards. A wide range of networking requirements can be provisioned by specifying the class of service applicable to each transmitted traffic.
When a CVLAN is configured as ingress CoS, the per-port settings are not considered. A maximum of 128 CVLAN and CoS relationships can be configured.
11.14.10.1 Related Procedure for Enabling Ingress CoS
To enable Ingress CoS on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards, see the:
11.14.11 CVLAN Rate Limiting
CVLAN rate limiting is supported on GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards. CVLAN rate limiting is supported for QinQ service in selective add mode. The following limitations and restrictions apply to CVLAN rate limiting:
– Selective translate add mode
– Services associated with the channel group
- CVLAN rate limiting and SVLAN rate limiting cannot be applied to the same service instance.
- Pseudo-IOS command line interface (PCLI) is not supported for CVLAN rate limiting.
- A VLAN profile with Link Integrity option enabled cannot be used to perform CVLAN rate limiting.
- On GE_XP and 10 GE_XP cards, CVLAN rate limiting can be applied to up to 128 services. However, the number of provisionable CVLAN rate limiting service instances is equal to 192 minus the number of SVLAN rate limiting service instances present on the card (subject to a minimum of 64 CVLAN rate limiting service instances).
- On GE_XPE and 10 GE_XPE cards, CVLAN rate limiting can be applied to up to 256 services. However, the number of provisionable CVLAN rate limiting service instances is equal to 384 minus the number of SVLAN rate limiting service instances present on the card (subject to a minimum of 128 CVLAN rate limiting service instances).
11.14.11.1 Related Procedure for Provisioning CVLAN Rate
To provision CVLAN rate on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards, see the “G289 Provision CVLAN Rate Limiting on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Card” section.
11.14.12 DSCP to CoS Mapping
DSCP to CoS mapping can be configured for each port. You can configure the CoS of the outer VLAN based on the incoming DSCP bits. This feature is supported only on GE_XPE and 10GE_XPE cards. PCLI is not supported for DSCP to CoS mapping.
DSCP to CoS mapping is supported for the following service types:
11.14.12.1 Related Procedure for Provisioning CoS Based on DSCP
To provision CoS based on DSCP on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards, see the “G384 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE QinQ Settings” section.
11.14.13 Link Aggregation Control Protocol
Link Aggregation Control Protocol (LACP) is part of the IEEE802.3ad standard that allows you to bundle several physical ports together to form a single logical channel. LACP allows a network device such as a switch to negotiate an automatic bundling of links by sending LACP packets to the peer device.
LACP allows you to form a single Layer 2 link automatically from two or more Ethernet links. This protocol ensures that both ends of the Ethernet link are functional and agree to be members of the aggregation group before the link is added to the group. LACP must be enabled at both ends of the link to be operational.
For more information on LACP, refer to the IEEE802.3ad standard. For information about interaction of LACP with other protocols, see the “Protocol Compatibility list” section.
11.14.13.2 Functions of LACP
LACP performs the following functions in the system:
- Maintains configuration information to control aggregation.
- Exchanges configuration information with other peer devices.
- Attaches or detaches ports from the link aggregation group based on the exchanged configuration information.
- Enables data flow when both sides of the aggregation group are synchronized.
11.14.13.3 Modes of LACP
LACP can be configured in the following modes:
- On — Default. In this mode, the ports do not exchange LACP packets with the partner ports.
- Active — In this mode, the ports send LACP packets at regular intervals to the partner ports.
- Passive — In this mode, the ports do not send LACP packets until the partner sends LACP packets. After receiving the LACP packets from the partner ports, the ports send LACP packets.
11.14.13.4 Parameters of LACP
LACP uses the following parameters to control aggregation:
- System Identifier—A unique identification assigned to each system. It is the concatenation of the system priority and a globally administered individual MAC address.
- Port Identification—A unique identifier for each physical port in the system. It is the concatenation of the port priority and the port number.
- Port Capability Identification—An integer, called a key, that identifies the capability of one port to aggregate with another port. There are two types of keys:
– Administrative key—The network administrator configures this key.
– Operational key—The LACP assigns this key to a port, based on its aggregation capability.
11.14.13.5 Unicast Hashing Schemes
LACP supports the following unicast hashing schemes:
- Ucast SA VLAN Incoming Port
- Ucast DA VLAN Incoming Port
- Ucast SA DA VLAN Incoming port
- Ucast Src IP TCP UDP
- Ucast Dst IP TCP UDP
- Ucast Src Dst IP TCP UDP
Note Unicast hashing schemes apply to unicast traffic streams only when the destination MAC address is already learned by the card. Hence, MAC learning must be enabled to support load balancing as per the configured hashing scheme. If the destination MAC address is not learned, the hashing scheme is Ucast Src Dst IP TCP UDP.
11.14.13.6 LACP Limitations and Restrictions
The LACP on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards has the following limitations and restrictions:
11.14.13.7 Related Procedure for LACP
To provision Channel Group using LACP, see the “G281 Manage the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Channel Group Settings” section.
11.14.14 Ethernet Connectivity Fault Management
Ethernet Connectivity Fault Management (CFM) is part of the IEEE 802.1ag standard. The Ethernet CFM is an end-to-end per service instance that supports the Ethernet layer Operations, Administration, and Management (OAM) protocol. It includes proactive connectivity monitoring, link trace on a per service basis, fault verification, and fault isolation for large Ethernet metropolitan-area networks (MANs) and WANs.
CFM is disabled on the card by default. CFM is enabled on all the ports by default.
For more information on CFM, refer to the IEEE 802.1ag standard. For information about interaction of CFM with other protocols, see the “Protocol Compatibility list” section. The following sections contain conceptual information about Ethernet CFM.
11.14.14.1 Maintenance Domain
A maintenance domain is an administrative domain that manages and administers a network. You can assign a unique maintenance level (from 0 to 7) to define the hierarchical relationship between domains. The larger the domain, the higher the maintenance level for that domain. For example, a service provider domain would be larger than an operator domain and might have a maintenance level of 6, while the operator domain maintenance level would be 3 or 4.
Maintenance domains cannot intersect or overlap because that would require more than one entity to manage it, which is not allowed. Domains can touch or nest if the outer domain has a higher maintenance level than the nested domain. Maintenance levels of nesting domains must be communicated among the administrating organizations. For example, one approach would be to have the service provider assign maintenance levels to operators.
The CFM protocol supports up to eight maintenance domains on GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards.
11.14.14.2 Maintenance Association
A maintenance association identifies a service within the maintenance domain. You can have any number of maintenance associations within each maintenance domain. The CFM protocol supports up to 1500 maintenance associations on GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards.
Note Each maintenance association is mapped to a maintenance domain. This mapping is done to configure a Maintenance End Point (MEP). The CFM protocol supports up to 1000 mappings on GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards.
11.14.14.3 Maintenance End Points
Maintenance End Points (MEPs) reside at the edge of the maintenance domain and are active elements of the Ethernet CFM. MEPs transmit Continuity Check messages at periodic intervals and receive similar messages from other MEPs within a domain. MEPs also transmit Loopback and Traceroute messages at the request of the administrator. MEPs confine CFM messages within the boundary of a maintenance domain through the maintenance level. There are two types of MEPs:
You can create up to 255 MEPs and MIPs together on GE_XP and 10GE_XP cards. You can create up to 500 MEPs and MIPs together on GE_XPE and 10GE_XPE cards.
The MEP continuity check database (CCDB) stores information that is received from other MEPs in the maintenance domain. The card can store up to 4000 MEP CCDB entries.
11.14.14.4 Maintenance Intermediate Points
Maintenance Intermediate Points (MIPs) are internal to the maintenance domain and are passive elements of the Ethernet CFM. They store information received from MEPs and respond to Linktrace and Loopback CFM messages. MIPs forward CFM frames received from MEPs and other MIPs, drop all CFM frames at a lower level, and forward all CFM frames at a higher level.
You can create up to 255 MEPs and MIPs together on GE_XP and 10GE_XP cards. You can create up to 500 MEPs and MIPs together on GE_XPE and 10GE_XPE cards.
The MIP CCDB maintains the information received for all MEPs in the maintenance domain. The card can store up to 4000 MIP CCDB entries.
11.14.14.5 CFM Messages
The Ethernet CFM on GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards supports the following messages:
- Continuity Check—These messages are exchanged periodically among MEPs. They allow MEPs to discover other MEPs within a domain and allow MIPs to discover MEPs. These messages are confined to a domain.
- Loopback—These messages are unicast messages that a MEP transmits, at the request of an administrator, to verify connectivity to a specific maintenance point. A reply to a loopback message indicates whether a destination is reachable.
- Traceroute—These messages are multicast messages that a MEP transmits, at the request of an administrator, to track the path to a destination MEP.
11.14.14.6 CFM Limitations and Restrictions
The CFM on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards has the following limitations and restrictions:
- CFM is not supported on channel groups.
- CFM is not enabled on protected ports running REP, FAPS, and 1+1.
- Y.1731 enhancements including AIS, LCK, and performance monitoring messages along with CFM are not supported.
- IEEE CFM MIB is not supported.
- L1 and CFM are mutually exclusive on a SVLAN because LI and CFM use the same MAC address.
- MAC security and CFM are mutually exclusive on the card due to hardware resource constraints.
11.14.14.7 Related Procedure for Ethernet CFM
For information about the supported Ethernet CFM features on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards, see the “G283 Manage the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card CFM Settings” section.
11.14.15 Ethernet OAM
The Ethernet OAM protocol is part of the IEEE 802.3ah standard and is used for installing, monitoring, and troubleshooting Ethernet MANs and Ethernet WANs. This protocol relies on an optional sublayer in the data link layer of the OSI model. The Ethernet OAM protocol was developed for Ethernet in the First Mile (EFM) applications. The terms Ethernet OAM and EFM are interchangeably used and both mean the same.
Normal link operation does not require Ethernet OAM. You can implement Ethernet OAM on any full-duplex point-to-point or emulated point-to-point Ethernet link for a network or part of a network (specified interfaces). OAM frames, called OAM Protocol Data Units (OAM PDUs), use the slow protocol destination MAC address 0180.c200.0002. OAM PDUs are intercepted by the MAC sublayer and cannot propagate beyond a single hop within an Ethernet network.
Ethernet OAM is disabled on all interfaces by default. When Ethernet OAM is enabled on an interface, link monitoring is automatically turned on.
For more information on Ethernet OAM protocol, refer to IEEE 802.3ah standard. For information about interaction of Ethernet OAM with other protocols, see the “Protocol Compatibility list” section.
11.14.15.1 Components of the Ethernet OAM
Ethernet OAM consists of two major components, the OAM Client and the OAM Sublayer.
11.14.15.1.1 OAM Client
The OAM client establishes and manages the Ethernet OAM on a link. The OAM client also enables and configures the OAM sublayer. During the OAM discovery phase, the OAM client monitors the OAM PDUs received from the remote peer and enables OAM functionality. After the discovery phase, the OAM client manages the rules of response to OAM PDUs and the OAM remote loopback mode.
11.14.15.1.2 OAM Sublayer
The OAM sublayer presents two standard IEEE 802.3 MAC service interfaces:
- One interface facing toward the superior sub-layers, which include the MAC client (or link aggregation).
- Other interface facing toward the subordinate MAC control sublayer.
The OAM sublayer provides a dedicated interface for passing OAM control information and OAM PDUs to and from the client.
11.14.15.3 Features of the Ethernet OAM
The Ethernet OAM protocol has the following OAM features:
- Discovery—Identifies devices in the network and their OAM capabilities. The Discovery feature uses periodic OAM PDUs to advertise the OAM mode, configuration, and capabilities. An optional phase allows the local station to accept or reject the configuration of the peer OAM entity.
- Link Monitoring—Detects and indicates link faults under a variety of conditions. It uses the event notification OAM PDU to notify the remote OAM device when it detects problems on the link.
- Remote Failure Indication—Allows an OAM entity to convey the failure conditions to its peer through specific flags in the OAM PDU.
- Remote Loopback—Ensures link quality with a remote peer during installation or troubleshooting.
11.14.15.4 Ethernet OAM Limitations and Restrictions
The Ethernet OAM on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards has the following limitations and restrictions:
- CFM, REP, link integrity, LACP, FAPS, IGMP on SVLAN and L2 1+1 protection are not supported with EFM.
- IEEE EFM MIB is not supported.
- EFM cannot be enabled or disabled at the card level.
- Unidirectional functionality is not supported.
- Errored Symbol Period, Rx CRC errors, Tx CRC errors are not supported.
- OAM PDUs are limited to 1 frame per second.
- Dying Gasp and critical events are not supported.
Note Dying Gasp RFI is not generated on GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards. However, if the peer device sends a dying gasp RFI, the card detects it and raises an alarm.
11.14.15.5 Related Procedure for Ethernet OAM
For information about the supported Ethernet OAM features on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards, see the “G285 Manage the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card EFM Settings” section.
11.14.16 Resilient Ethernet Protocol
The Resilient Ethernet Protocol (REP) is a protocol used to control network loops, handle link failures, and improve convergence time.
REP performs the following tasks:
- Controls a group of ports connected in a segment.
- Ensures that the segment does not create any bridging loops.
- Responds to link failures within the segment.
- Supports VLAN load balancing.
For information about interaction of REP with other protocols, see the “Protocol Compatibility list” section.
11.14.16.1 REP Segments
A REP segment is a chain of ports connected to each other and configured with a segment ID. Each segment consists of regular segment ports and two edge ports. A GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card can have up to 2 ports that belong to the same segment, and each segment port can have only one external neighbor port.
A segment protects only against a single link failure. Any more failures within the segment result in loss of connectivity.
11.14.16.2 Characteristics of REP Segments
REP segments have the following characteristics:
- If all the ports in the segment are operational, one port blocks traffic for each VLAN. If VLAN load balancing is configured, two ports in the segment control the blocked state of VLANs.
- If any port in the segment is not operational, all the other operational ports forward traffic on all VLANs to ensure connectivity.
- In case of a link failure, the alternate ports are immediately unblocked. When the failed link comes up, a logically blocked port per VLAN is selected with minimal disruption to the network.
11.14.16.3 REP Port States
Ports in REP segments take one of three roles or states: Failed, Open, or Alternate.
- A port configured as a regular segment port starts as a failed port.
- When the neighbor adjacencies are determined, the port transitions to the alternate port state, blocking all the VLANs on the interface. Blocked port negotiations occur and when the segment settles, one blocked port remains in the alternate role and all the other ports become open ports.
- When a failure occurs in a link, all the ports move to the failed state. When the alternate port receives the failure notification, it changes to the open state, forwarding all VLANs.
11.14.16.4 Link Adjacency
Each segment port creates an adjacency with its immediate neighbor. Link failures are detected and acted upon locally. If a port detects a problem with its neighbor, the port declares itself non-operational and REP converges to a new topology.
REP Link Status Layer (LSL) detects its neighbor port and establishes connectivity within the segment. All VLANs are blocked on an interface until the neighbor port is identified. After the neighbor port is identified, REP determines the neighbor port that must be the alternate port and the ports that must forward traffic.
Each port in a segment has a unique port ID. When a segment port starts, the LSL layer sends packets that include the segment ID and the port ID.
A segment port does not become operational if the following conditions are satisfied:
11.14.16.5 Fast Reconvergence
REP runs on a physical link and not on per VLAN. Only one hello message is required for all VLANs that reduces the load on the protocol.
REP Hardware Flood Layer (HFL) is a transmission mechanism that floods packets in hardware on an admin VLAN. HFL avoids the delay that is caused by relaying messages in software. HFL is used for fast reconvergence in the order of 50 to 200 milliseconds.
11.14.16.6 VLAN Load Balancing
You must configure two edge ports in the segment for VLAN load balancing. One edge port in the REP segment acts as the primary edge port; the other edge port as the secondary edge port. The primary edge port always participates in VLAN load balancing in the segment. VLAN load balancing is achieved by blocking certain VLANs at a configured alternate port and all the other VLANs at the primary edge port.
11.14.16.7 REP Configuration Sequence
You must perform the following tasks in sequence to configure REP:
- Configure the REP administrative VLAN or use the default VLAN 1. The range of REP admin VLAN is 1 to 4093. VLAN 4094 is not allowed.
- Add ports to the segment in interface configuration mode.
- Enable REP on ports and assign a segment ID to it. REP is disabled on all ports by default. The range of segment ID is 1 to 1024.
- Configure two edge ports in the segment; one port as the primary edge port and the other as the secondary edge port.
- If you configure two ports in a segment as the primary edge port, for example, ports on different switches, REP selects one of the ports to serve as the primary edge port based on port priority. The Primary option is enabled only on edge ports.
- Configure the primary edge port to send segment topology change notifications (STCNs) and VLAN load balancing to another port or to other segments. STCNs and VLAN load balancing configurations are enabled only for edge ports.
Note A port can belong to only one segment. Only two ports can belong to the same segment. Both the ports must be either regular ports or edge ports. However, if the No-neighbor port is configured, one port can be an edge port and another port can be a regular port.
11.14.16.9 REP Limitations and Restrictions
The REP on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards has the following limitations and restrictions:
- Fast re-convergence and VLAN load balancing are not supported on UNI ports in transparent mode.
- Native VLAN is not supported.
- CFM, EFM, link integrity, LACP, FAPS, and L2 1+1 protection are not supported on ports that are configured as part of REP segment and vice versa.
- When a node installed with GE_XP, GE_XPE, 10GE_XP, or 10GE_XPE cards configured with REP or LACP is upgraded, traffic loss may occur. This traffic loss is due to reconvergence when the cards soft reset during the upgrade process.
- NNI ports cannot be configured as the primary edge port or blocking port at the access or aggregation layer.
- Only three REP segments can be configured on GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards.
- Consider the following configuration:
More than one REP closed segment is configured on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards and the same HFL admin VLAN is enabled on the switches.
If two different segments are configured on more than one common switch, the following consequences happen.
– Flooding of HFL packets across segments if one REP segment fails
– Segment goes down due to LSL time out even if the segment does not have faults
Hence, it is recommended not to configure two different segments on more than one common switch.
– VLAN Load Balancing is configured on GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards by specifying the VLB preempt delay.
– Primary and secondary edge ports are configured on the same switch.
This configuration leads to high convergence time during manual premption, VLB activation, and deactivation (400 to 700 milliseconds).
11.14.16.10 Related Procedure for Managing the REP Settings
To manage the REP settings on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards, see the “G287 Manage the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card REP Settings” section.
11.14.17 Related Procedures for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards
The following is the list of procedures and tasks related to the configuration of the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards:
- G165 Modify the GE_XP, 10GE_XP, GE_XPE, 10GE_XPE Cards Ethernet Parameters, Line Settings, and PM Thresholds
- G311 Provision the Storm Control Settings for GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards
- G208 Provision SVLAN Rate Limiting on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Card
- G314 Add a GE_XP or 10GE_XP Card on a FAPS Ring
- NTP-G75 Monitor Transponder and Muxponder Performance
11.15 ADM-10G Card
The ADM-10G card operates on ONS 15454 SONET, ONS 15454 SDH, ONS 15454 M2, ONS 15454 M6, and DWDM networks to carry optical signals and Gigabit Ethernet signals over DWDM wavelengths for transport. The card aggregates lower bit-rate client SONET or SDH signals (OC-3/STM-1, OC-12/STM-4, OC-48/STM-16, or Gigabit Ethernet) onto a C-band tunable DWDM trunk operating at a higher OC-192/STM-64 rate. In a DWDM network, the ADM-10G card transports traffic over DWDM by mapping Gigabit Ethernet and SONET or SDH circuits onto the same wavelength with multiple protection options.
You can install and provision the ADM-10G card in a linear configuration in:
- Slots 1 to 5 and 12 to 16 in standard and high-density ONS 15454 ANSI shelves (15454-SA-ANSI or 15454-SA-HD), the ETSI ONS 15454 standard shelf assembly, or the ONS 15454 ETSI high-density shelf assembly
- Slot 2 in ONS 15454 M2 chassis
- Slots 2 to 6 in ONS 15454 M6 chassis
The card is compliant with ITU-T G.825 and ITU-T G.783 for SDH signals. It supports concatenated and non-concatenated AU-4 mapped STM-1, STM-4, and STM-16 signals as specified in ITU-T G.707. The card also complies with Section 5.6 of Telcordia GR-253-CORE and supports synchronous transport signal (STS) mapped OC-3, OC-12, and OC-48 signals as specified in the standard.
The client SFP and trunk XFP are compliant with interface requirements in Telcordia GR-253-CORE, ITU-T G.957 and/or ITU-T G.959.1, and IEEE 802.3.
11.15.1 Key Features
The ADM-10G card has the following high-level features:
- Operates with the TCC2, TCC2P, TCC3, TNC, TNCE, TSC, or TSCE.
- Interoperable with TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10EX_C, and OTU2_XP cards.
- Has built-in OC-192/STM-64 add/drop multiplexing function including client, trunk, and STS cross-connect.
- Supports both single-card and double-card (ADM-10G peer group) configuration.
- Supports path protection/SNCP on client and trunk ports for both single-card and double-card configuration. The card does not support path protection/SNCP between a client port and a trunk port. Path protection/SNCP is supported only between two client ports or two trunk ports.
- Supports 1+1 protection on client ports for double-card configuration only.
- Supports SONET, SDH, and Gigabit Ethernet protocols on client SFPs.
- Supports XFP DWDM trunk interface single wavelengths.
- Returns zero bit errors when a TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE card switches from active to standby or when manual or forced protection switches occur.
- Has 16 SFP-based client interfaces (gray, colored, coarse wavelength division multiplexing (CWDM), and DWDM optics available).
- Supports STM1, STM4, STM16, and Gigabit Ethernet client signals (8 Gigabit Ethernet maximum).
- Has one XFP-based trunk interface supporting E-FEC/FEC and ITU-T G.709 for double-card configuration.
- Has two XFP-based trunk interface supporting E-FEC/FEC and ITU-T G.709 for single-card configuration.
- Has two SR XFP interlink interfaces supporting redundancy connection with protection board and pass-through traffic for double-card configuration.
- Supports frame-mapped generic framing procedure (GFP-F) and LEX mapping for Ethernet over SONET or SDH.
- Can be installed or pulled from operation, in any slot, without impacting other service cards in the shelf.
- Supports client to client hairpinning, that is, creation of circuits between two client ports for both single-card and double-card configuration. See the “Circuit Provisioning” section for more detailed information.
11.15.2 ADM-10G POS Encapsulation, Framing, and CRC
The ADM-10G card supports Cisco EoS LEX (LEX) and generic framing procedure framing (GFP-F) encapsulation on 8 POS ports corresponding to 8 GigE ports (Port 1 to Port 8) in both single-card and double-card (ADM-10G peer group) configuration.
You can provision framing on the ADM-10G card as either the default GFP-F or LEX framing. With GFP-F framing, you can configure a 32-bit cyclic redundancy check (CRC) or none (no CRC) (the default). LEX framing supports 16-bit or 32-bit CRC configuration. The framing type cannot be changed when there is a circuit on the port.
On the CTC, navigate to card view and click the Provisioning > Line> Ethernet Tab. To see the various parameters that can be configured on the ethernet ports, see the “CTC Display of ethernet Port Provisioning Status” section in the Cisco ONS 15454 and Cisco ONS 15454 SDH Ethernet Card Software Feature and Configuration Guide. Parameters such as, admin state, service state, framing type, CRC, MTU and soak time for a port can be configured.
It is possible to create an end-to-end circuit between equipment supporting different kinds of encapsulation (for example, LEX on one side and GFP-F on other side). But, under such circumstances, traffic does not pass through, and an alarm is raised if there is a mismatch.
11.15.2.1 POS Overview
Ethernet data packets need to be framed and encapsulated into a SONET/SDH frame for transport across the SONET/SDH network. This framing and encapsulation process is known as packet over SONET/SDH (POS).
The Ethernet frame comes into the ADM-10G card on a standard Gigabit Ethernet port and is processed through the card’s framing mechanism and encapsulated into a POS frame. When the POS frame exits, the ADM-10G card is in a POS circuit, and this circuit is treated as any other SONET circuit (STS) or SDH circuit (VC) in the ONS node. It is cross-connected and rides the SONET/SDH signal out the port of an optical card and across the SONET/SDH network.
The destination of the POS circuit is a card or a device that supports the POS interface. Data packets in the destination card frames are removed and processed into ethernet frames. The Ethernet frames are then sent to a standard Ethernet port of the card and transmitted onto an Ethernet network.
11.15.2.2 POS Framing Modes
A POS framing mode is the type of framing mechanism employed by the ADM-10G card to frame and encapsulate data packets into a POS signal. These data packets were originally encapsulated in Ethernet frames that entered the standard Gigabit Ethernet interface of the ADM-10G card.
11.15.2.2.1 GFP-F Framing
The GFP-F framing represent standard mapped Ethernet over GFP-F according to ITU-T G.7041. GFP-F defines a standard-based mapping of different types of services onto SONET/SDH. GFP-F maps one variable length data packet onto one GFP packet. GFP-F comprises of common functions and payload specific functions. Common functions are those shared by all payloads. Payload-specific functions are different depending on the payload type. GFP-F is detailed in the ITU recommendation G.7041.
11.15.2.2.2 LEX Framing
LEX encapsulation is a HDLC frame based Cisco Proprietary protocol, where the field is set to values specified in Internet Engineering Task Force (IETF) RFC 1841. HDLC is one of the most popular Layer 2 protocols. The HDLC frame uses the zero insertion/deletion process (commonly known as bit stuffing) to ensure that the bit pattern of the delimiter flag does not occur in the fields between flags. The HDLC frame is synchronous and therefore relies on the physical layer to provide a method of clocking and synchronizing the transmission and reception of frames. The HDLC framing mechanism is detailed in the IETF’s RFC 1662, “PPP in HDLC-like Framing.”
11.15.2.3 GFP Interoperability
The ADM-10G card defaults to GFP-F encapsulation that is compliant with ITU-T G.7041. This mode allows the card to operate with ONS 15310-CL, ONS 15310-MA, ONS 15310-MA SDH, or ONS 15454 data cards (for example, ONS 15454 CE100T-8 or ML1000-2 cards). GFP encapsulation also allows the ADM-10G card to interoperate with other vendors Gigabit Ethernet interfaces that adhere to the ITU-T G.7041 standard.
11.15.2.4 LEX Interoperability
The LEX encapsulation is compliant with RFC 1841. This mode allows the card to operate with ONS 15310-CL, ONS 15310-MA, ONS 15310-MA SDH, or ONS 15454 data cards (for example, G1000-4/G1K-4 cards, CE-1000-4, ONS 15454 CE100T-8 or ML1000-2 cards).
11.15.3 Faceplate and Block Diagram
Figure 11-20 shows the ADM-10G card faceplate.
Figure 11-20 ADM-10G Card Faceplate and Block Diagram
11.15.4 Port Configuration Rules
ADM-10G card client and trunk port capacities are shown in Figure 11-21.
Figure 11-21 ADM-10G Card Port Capacities
Port 17 acts as trunk2 or ILK1 interface based on single-card or double-card configuration.
11.15.5 Client Interfaces
The ADM-10G card uses LC optical port connectors and, as shown in Figure 11-21, supports up to 16 SFPs that can be utilized for OC-N/STM-N traffic. Eight of the SFPs can be used for Gigabit Ethernet. The interfaces can support any mix of OC-3/STM-1, OC-12/STM-4, OC-48/STM-16, or Gigabit Ethernet of any reach, such as SX, LX, ZX, SR, IR, or LR. The interfaces support a capacity of:
The supported client SFPs and XFPs are:
– 1000Base-SX SFP 850 nm (ONS-SE-G2F-SX=)
– 1000Base-LX SFP 1310 nm (ONS-SE-G2F-LX=)
– OC48/STM16 IR1, OC12/STM4 SR1, OC3/STM1 SR1, GE-LX multirate SFP 1310 nm (ONS-SE-Z1=)
– OC3/STM1 IR1, OC12/STM4 IR1 multirate SFP 1310 nm (ONS-SI-622-I1=)
– OC48/STM16 SR1 SFP 1310 nm (ONS-SI-2G-S1=)
– OC48/STM16 IR1 SFP 1310 nm (ONS-SI-2G-I1=)
– OC48/STM16, 1550 LR2, SM LC (ONS-SE-2G-L2=)
– 1000Base-ZX SFP 1550 nm (ONS-SI-GE-ZX=)
– OC3/STM1 LR2 SFP 1550 nm (ONS-SI-155-L2=)
– OC48/STM16 LR2 SFP 1550 nm (ONS-SI-2G-L2=)
– OC48/STM16 SFP (ONS-SC-2G-xx.x)
Note xx.x = 28.7 to 60.6. ONS-SC-2G-28.7, ONS-SC-2G-33.4, ONS-SC-2G-41.3, ONS-SC-2G-49.3, and ONS-SC-2G-57.3 are supported from Release 8.5 and later.
11.15.6 Interlink Interfaces
Two 2R interlink interfaces, called ILK1 (Port 17) and ILK2 (Port 18), are provided for creation of ADM-10G peer groups in double-card configurations. In a single-card configuration, Port 17 (OC-192/STM-64) and Port 18 (OC-192/STM-64 or OTU2 payload) must be configured as trunk interfaces. In a double-card configuration (ADM-10G peer group), Ports 17 and 18 must be configured as ILK1 and ILK2 interfaces, respectively. Physically cabling these ports between two ADM-10G cards, located on the same shelf, allows you to configure them as an ADM-10G peer group.The ILK ports carry 10 Gb of traffic each.
The interlink interfaces support STM64 SR1 (ONS-XC-10G-S1=) XFP and 10GE BASE SR (ONS-XC-10G-SR-MM=) XFPs.
11.15.7 DWDM Trunk Interface
The ADM-10G card supports OC-192/STM-64 signal transport and ITU-T G.709 digital wrapping according to the ITU-T G.709 standard.The ADM-10G card supports three trunk XFPs:
11.15.8 Configuration Management
When using OC-48/STM-16 traffic, some contiguous port configurations, listed in Table 11-21, are unavailable due to hardware limitations. This limitation does not impact the Gigabit Ethernet payload.
Note The ADM-10G card cannot be used in the same shelf with SONET or SDH cross-connect cards.
Note The total traffic rate for each trunk cannot exceed OC-192/STM-64 on each ADM-10G card, or for each ADM-10G peer group.
Note Gigabit Ethernet is supported on Ports 1 through 8. Ports 9 through Port 12 support only OC-3/STM-1 or OC-12/STM-4.
Additionally, the following guidelines apply to the ADM-10G card:
- Trunk Port 17 supports OC-192/STM-64.
- Trunk Ports 18 and 19 support OC-192/STM-64 and OTU2.
- The interlink port supports OC-192/STM-64.
- Up to six ADM-10G cards can be installed in one shelf.
- Up to 24 ADM-10G cards can be installed per network element (NE) regardless of whether the card is installed in one shelf or in multiple shelves.
- The card can be used in all 15454-SA-ANSI and 15454-SA-HD shelves as well as ETSI ONS 15454 standard and high-density shelves.
- A lamp test function can be activated from CTC to ensure that all LEDs are functional.
- The card can operate as a working protected or working non-protected card.
- In a redundant configuration, an active card hardware or software failure triggers a switch to the standby card. This switch is detected within 10 ms and is completed within 50 ms.
- ADM-10G cards support jumbo frames with MTU sizes of 64 to 9,216 bytes; the maximum is 9,216.
- After receiving a link or path failure, the ADM-10G card can shut down only the downstream Gigabit Ethernet port.
Note In ADM-10G cards, the Gigabit Ethernet port does not support flow control.
11.15.9 Security
The ADM-10G card that an SFP or XFP is plugged into implements the Cisco Standard Security Code Check Algorithm that keys on the vendor ID and serial number.
If a pluggable port module (PPM) is plugged into a port on the card but fails the security code check because it is not a Cisco PPM, a minor NON-CISCO-PPM alarm is raised.
If a PPM with an unqualified product ID is plugged into a port on this card—that is, the PPM passes the security code as a Cisco PPM but it has not been qualified for use on the ADM-10G card— a minor UNQUAL-PPM alarm is raised.
11.15.10 Protection
The ADM-10G card supports 1+1 and SONET path protection and SDH SNCP protection architectures in compliance with Telcordia GR-253-CORE, Telcordia GR-1400-CORE, and ITU-T G.841 specifications.
11.15.10.1 Circuit Protection Schemes
The ADM-10G card supports path protection/SNCP circuits at the STS/VC4 (high order) level and can be configured to switch based on signal degrade calculations. The card supports path protection/SNCP on client and trunk ports for both single-card and double-card configuration.
Note The ADM-10G card supports path protection/SNCP between client ports and trunk port 17. The card does not support path protection/SNCP between client ports and trunk ports 18 or 19. The card does not support path protection/SNCP between port 17 and trunk ports 18 and 19.
The card allows open-ended path protection/SNCP configurations incorporating other vendor equipment. In an open-ended path protection/SNCP, you can specify one source point and two possible endpoints (or two possible source points and one endpoint) and the legs can include other vendor equipment. The source and endpoints are part of the network discovered by CTC.
11.15.10.2 Port Protection Schemes
The ADM-10G card supports unidirectional and bidirectional 1+1 APS protection schemes on client ports for double-card configuration (ADM-10G peer group) only. 1+1 APS protection scheme is not supported in single-card configuration. For 1+1 optical client port protection, you can configure the system to use any pair of like facility interfaces that are on different cards of the ADM-10G peer group.
11.15.11 Circuit Provisioning
The ADM-10G card supports STS circuit provisioning both in single-card and double-card (ADM-10G peer group) configuration. The card allows you to create STS circuits between:
Note Circuits between two trunk ports are called pass-through circuits.
For an ADM-10G card in single-card configuration, if you are creating STS circuits between two client ports, the following limitation must be considered:
For an ADM-10G card that is part of an ADM-10G peer group, if you are creating STS circuits between two client ports or between client and trunk ports, the following limitations must be considered:
- Gigabit Ethernet to Gigabit Ethernet connections are not supported.
- Optical channel (OC) to OC, OC to Gigabit Ethernet, and Gigabit Ethernet to OC connections between two peer group cards are supported. Peer group connections use interlink port bandwidth, hence, depending on the availability/fragmentation of the interlink port bandwidth, it may not be possible to create an STS circuit from the Gigabit Ethernet/OC client port to the peer card trunk port. This is because, contiguous STSs (that is, STS-3c, STS-12c, STS-24c, and so on) must be available on the interlink port for circuit creation.
Note There are no limitations to create an STS circuit between two trunk ports.
The two ADM-10G cards used in a paired mode use interlink ports ILK1 (Port 17) and ILK2 (Port 18). A CCAT or VCAT circuit created between the peer ADM-10G cards uses the ILK1 port if the source or destination is Port 19. The circuits created with a single ADM-10G card uses the ILK2 port.
If the circuit is of type STS- n c (where n is an integer and can take values 3,6,9,12,18,24,36,48,96) and uses the ILK2 port, then the starting timeslot needs to use specific timeslots for traffic to flow. The timeslots can be 12 m +1 for STS-12c circuits and 48 m +1 (where m is an integer and can take values 0,1,2,3...) for STS-48c circuits. The timeslots can be 3 m +1 for the other STS- n c circuits.
The following example illustrates how to use the correct timeslot for an ILK2 port:
If there is no circuit on the ILK2 port and a STS-3c circuit is created, the circuit uses timeslots 1 to 3. An STS-12c circuit must be created on the ILK2 port later. The STS-12c circuit must have used timeslots 4 to 15. However, the STS-12c circuit uses timeslots starting from 12m+1 (1, 13, 25, and so on) as defined in the above rule. Therefore, before creating the STS-12c circuit, dummy circuits must be created in CTC that consumes STS-9 bandwidth.
11.15.12 ADM-10G CCAT and VCAT Characteristics
The ADM-10G card supports high-order (HO) contiguous concatenation (CCAT) and HO virtual concatenation (VCAT) circuits on 8 GigE ports (Port 1 to Port 8) in both single-card and double-card (ADM-10G peer group) configuration.
To enable end-to-end connectivity in a VCAT circuit that traverses through a third-party network, you can use Open-Ended VCAT circuit creation.
The ADM-10G card supports flexible non-LCAS VCAT groups (VCGs). With flexible VCGs, the ADM-10G can perform the following operations:
- Add or remove members from groups
- Put members into or out of service, which also adds/removes them from the group
- Add or remove cross-connect circuits from VCGs
Any operation on the VCG member is service effecting (for instance, adding or removing members from the VCG). Adding or removing cross-connect circuits is not service-affecting, if the associated members are not in the group
The ADM-10G card allows independent routing and protection preferences for each member of a VCAT circuit. You can also control the amount of VCAT circuit capacity that is fully protected, unprotected, or uses Protection Channel Access (PCA) (when PCA is available). Alarms are supported on a per-member as well as per virtual concatenation group (VCG) basis.
The ADM-10G card supports both automatic and manual routing for VCAT circuit, that is, all members are manually or automatically routed. Bidirectional VCAT circuits are symmetric, which means that the same number of members travel in each direction. With automatic routing, you can specify the constraints for individual members; with manual routing, you can select different spans for different members. Two types of automatic and manual routing are available for VCAT members: common fiber routing and split routing.
The ADM-10G card supports VCAT common fiber routing and VCAT split fiber (diverse) routing. With VCAT split fiber routing, each member can be routed independently through the SONET or SDH or DWDM network instead of having to follow the same path as required by CCAT and VCAT common fiber routing. This allows a more efficient use of network bandwidth, but the different path lengths and different delays encountered may cause slightly different arrival times for the individual members of the VCG. The VCAT differential delay is this relative arrival time measurement between members of a VCG. The maximum tolerable VCAT split fiber routing differential delay for the ADM-10G card is approximately 55 milliseconds. A loss of alignment alarm is generated if the maximum differential delay supported is exceeded.
The differential delay compensation function is automatically enabled when you choose split fiber routing during the CTC circuit configuration process. CCAT and VCAT common fiber routing do not enable or need differential delay support.
Note For TL1, EXPBUFFERS parameter must be set to ON in the ENT-VCG command to enable support for split fiber routing.
Available Circuit Sizes
Table 11-22 and Table 11-23 show the circuit sizes available for the ADM-10G card.
Note In ADM-10G cards, the Gigabit Ethernet port does not support flow control. When less than seven VC-4s are configured for the port, with the client traffic expected to be below the line rate, a burst in traffic beyond the supposed bandwidth leads to packet loss. It is, therefore, recommended to use an external flow control mechanism with less than seven VC-4s configured. Connecting a GE-XP or GE-XPE card between the client traffic and the ADM-10G Gigabit Ethernet interface enables such flow control.
11.15.12.1 Related Procedure for VCAT Circuit
The following is the list of procedures related to creating VCAT circuits:
11.15.13 Intermediate Path Performance Monitoring
Intermediate path performance monitoring (IPPM) allows a node to monitor the constituent channel of an incoming transmission signal. You can enable IPPM for STS/VC-4s payload on OCn and Trunk ports of ADM-10G card. The IPPM is complaint with GR253/G.826.
Software Release 9.2 and higher enables the ADM-10G card to monitor the near-end and far-end PM data on individual STS/VC-4 payloads by enabling IPPM. After provisioning IPPM on the card, service providers can monitor large amounts of STS/VC-4 traffic through intermediate nodes, thus making troubleshooting and maintenance activities more efficient. IPPM occurs only on STS/VC-4 paths that have IPPM enabled, and TCAs are raised only for PM parameters on the selected IPPM paths.
For a CCAT circuit, you can enable IPPM only on the first STS/VC-4 of the concatenation group. For a VCAT circuit, you can enable IPPM independently on each member STS/VC-4 of the concatenation group.
11.15.13.1 Related Procedure for IPPM
To enable IPPM on the ADM-10G card, see the “G247 Enable or disable Path Performance Monitoring on Intermediate Nodes” section.
11.15.14 Pointer Justification Count Performance Monitoring
Pointers are used to compensate for frequency and phase variations. Pointer justification counts indicate timing errors on SONET networks. When a network is out of synchronization, jitter and wander occur on the transported signal. Excessive wander can cause terminating equipment to slip.
Slips cause different effects in service. Voice service has intermittent audible clicks. Compressed voice technology has short transmission errors or dropped calls. Fax machines lose scanned lines or experience dropped calls. Digital video transmission has distorted pictures or frozen frames. Encryption service loses the encryption key, causing data to be transmitted again.
Pointers provide a way to align the phase variations in STS and VC4 payloads. The STS payload pointer is located in the H1 and H2 bytes of the line overhead. Clocking differences are measured by the offset in bytes from the pointer to the first byte of the STS synchronous payload envelope (SPE) called the J1 byte. Clocking differences that exceed the normal range of 0 to 782 can cause data loss.
There are positive (PPJC) and negative (NPJC) pointer justification count parameters. PPJC is a count of path-detected (PPJC-PDET-P) or path-generated (PPJC-PGEN-P) positive pointer justifications. NPJC is a count of path-detected (NPJC-PDET-P) or path-generated (NPJC-PGEN-P) negative pointer justifications depending on the specific PM name. PJCDIFF is the absolute value of the difference between the total number of detected pointer justification counts and the total number of generated pointer justification counts. PJCS-PDET-P is a count of the one-second intervals containing one or more PPJC-PDET or NPJC-PDET. PJCS-PGEN-P is a count of the one-second intervals containing one or more PPJC-PGEN or NPJC-PGEN.
A consistent pointer justification count indicates clock synchronization problems between nodes. A difference between the counts means that the node transmitting the original pointer justification has timing variations with the node detecting and transmitting this count. Positive pointer adjustments occur when the frame rate of the SPE is too slow in relation to the rate of the STS-1.
You must enable PPJC and NPJC performance monitoring parameters for ADM-10Gcard. In CTC, the count fields for PPJC and NPJC PMs appear white and blank unless they are enabled on the card view Provisioning tab.
11.15.15 Performance Monitoring Parameter Definitions
This section describes the STS and VC-4 path performance monitoring parameters that ADM-10G card support.
Table 11-24 lists the STS near-end path performance monitoring parameters.
Table 11-25 gives the VC-4 near-end path performance monitoring parameters definition that ADM-10G card support.
11.15.16 ADM-10G Functions
The functions of the ADM-10G card are:
- Automatic Laser Shutdown
- Card level indicators—Table G-1
- Port level indicators—Table G-11
11.16 OTU2_XP Card
The OTU2_XP card is a single-slot card with four ports with XFP-based multirate (OC-192/STM-64, 10GE, 10G FC, IB_5G) Xponder for the ONS 15454 ANSI and ETSI platforms. The OTU2_XP card supports multiple configurations.
Table 11-26 describes the different configurations supported by the OTU2_XP card and the ports that must be used for these configurations.
2 x 10G standard regenerator (with enhanced FEC (E-FEC) only on one port) |
||||
Client port in transponder or trunk port in regenerator configuration |
||||
All the four ports are ITU-T G.709 compliant and support 40 channels (wavelengths) at 100-GHz channel spacing in the C-band (that is, the 1530.33 nm to 1561.42 nm wavelength range).
The OTU2_XP card can be installed in Slots 1 through 6 or 12 through 17. The OTU2_XP card supports SONET SR1, IR2, and LR2 XFPs, 10GE BASE SR, SW, LR, LW, ER, EW, and ZR XFPs, and 10G FC MX-SN-I and SM-LL-L XFPs.
11.16.1 Key Features
The OTU2_XP card has the following high-level features:
- 10G transponder, regenerator, and splitter protection capability on the ONS 15454 DWDM platform.
- Compatible with the ONS 15454 ANSI high-density shelf assembly, the ETSI ONS 15454 shelf assembly, and the ETSI ONS 15454 high-density shelf assembly. Compatible with TCC2/TCC2P/ TCC3/TNC/TNCE/TSC/TSCE cards.
- Interoperable with TXP_MR_10E and TXP_MR_10E_C cards.
- Four port, multirate (OC-192/STM-64, 10G Ethernet WAN Phy, 10G Ethernet LAN Phy, 10G Fibre Channel, IB_5G) client interface. The client signals are mapped into an ITU-T G.709 OTU2 signal using standard ITU-T G.709 multiplexing.
- ITU-T G.709 framing with standard Reed-Soloman (RS) (255,237) FEC. Performance monitoring and ITU-T G.709 Optical Data Unit (ODU) synchronous mapping. Enhanced FEC (E-FEC) with ITU-T G.709 ODU with greater than 8 dB coding gain.
- The trunk rate remains the same irrespective of the FEC configuration. The error coding performance can be provisioned as follows:
– E-FEC—Standard ITU-T G.975.1 (subclause I.7)
- IEEE 802.3 frame format supported for 10 Gigabit Ethernet interfaces. The minimum frame size is 64 bytes. The maximum frame size is user-provisionable.
- Supports fixed/no fixed stuff mapping (insertion of stuffing bytes) for 10G Ethernet LAN Phy signals (only in transponder configuration).
- Supports 10G Ethernet LAN Phy to 10G Ethernet WAN Phy conversion on Ports 1 (client port) and 3 (trunk port).
- Supports 10G Ethernet LAN Phy to WAN Phy conversion using CTC and TL1. When enabled on the OTU2_XP card, the first Channel (Ports 1 and 3) supports LAN to WAN conversion. The second channel carries normal 10GE, 10G FC, and OC192/STM64 traffic.
- The LAN Phy to WAN Phy conversion functions in accordance to WAN Interface Sublayer (WIS) mechanism as defined by IEEE802.3ae (IEEE Std 802.3ae-2002, Amendment to CSMA/CD).
- Default configuration is transponder, with trunk ports configured as ITU-T G.709 standard FEC.
- In transponder or regenerator configuration, if one of the ports is configured the corresponding port is automatically created.
- In regenerator configuration, only Ports 3 and 4 can be configured as E-FEC. Ports 1 and 2 can be configured only with standard FEC.
- When port pair 1-3 or 2-4 is configured as regenerator (that is, card mode is standard regenerator), the default configuration on Ports 3 and 4 is automatically set to standard FEC.
- When Ports 3 and 4 are configured as regenerator (that is, card mode is E-FEC regenerator), the default configuration on both these ports is automatically set to E-FEC.
- In a splitter-protected transponder configuration, the trunk ports (Port 3 and Port 4) are configured as ITU-T G.709 standard FEC or E-FEC. OCHCC circuits with different trunk wavelengths can be configured for the working and protect paths. The process of setting the trunk wavelengths is similar to the G367 Change the 2.5G Multirate Transponder Trunk Wavelength Settings. OCHCC circuits having different trunk wavelengths on the working and protect paths can be upgraded to GMPLS circuits.
- Supports protection through Y-cable protection scheme.
Note When enabled, the 10G Ethernet LAN Phy to WAN Phy conversion feature does not support Y-cable protection on the LAN to WAN interface (ports 1 and 3).
- Client ports support SONET SR1, IR2, and LR2 XFPs, 10GE BASE SR, SW, LR, LW, ER, EW, and ZR XFPs, and 10G FC MX-SN-I and SM-LL-L XFPs.
- Following are the OTU2 link rates that are supported on the OTU2_XP trunk port:
– Standard G.709 (10.70923 Gbps) when the client is provisioned as “SONET” (including 10G Ethernet WAN PHY) (9.95328 Gbps).
– G.709 overclocked to transport 10GE as defined by ITU-T G. Sup43 Clause 7.2 (11.0491 Gbps) when the client is provisioned as “10G Ethernet LAN Phy” (10.3125 Gbps) with “No Fixed Stuff” enabled.
– G.709 overclocked to transport 10GE as defined by ITU-T G. Sup43 Clause 7.1 (11.0957 Gbps) when the client is provisioned as “10G Ethernet LAN Phy” (10.3125 Gbps) with “No Fixed Stuff” disabled.
– G.709 proprietary overclocking mode to transport 10G FC (11.3168 Gbps) when the client is provisioned as “10G Fiber Channel” (10.518 Gbps).
– Proprietary rate at the trunk when the client is provisioned as IB_5G.
- The MTU setting is used to display the ifInerrors and OverSizePkts counters on the receiving trunk and client port interfaces. Traffic of frame sizes up to 65535 bytes pass without any packet drops, from the client port to the trunk port and vice versa irrespective of the MTU setting.
- The OTU2_XP card configured in the Transponder or Mixed mode does not support egress Ethernet variables such as ifOutOctets, ifOutDiscards, ifOutMulticastPkts, and ifOutBroadcastPkts.
11.16.2 Faceplate and Block Diagram
Figure 11-22 shows the OTU2_XP card faceplate and block diagram.
Figure 11-22 OTU2_XP Card Faceplate and Block Diagram
Note The Swan FPGA is automatically loaded when the LAN Phy to WAN Phy conversion feature is enabled on the OTU2_XP card. The Barile FPGA is automatically loaded when the LAN Phy to WAN Phy conversion feature is disabled on the OTU2_XP card.
11.16.3 OTU2_XP Card Interface
The OTU2_XP card is a multi-functional card that operates in different configurations, such as transponder, standard regenerator, E-FEC regenerator, and 10G Ethernet LAN Phy to WAN Phy conversion mode. The OTU2_XP card acts as a protected transponder, when the 10G Ethernet LAN Phy to WAN Phy is in splitter protected transponder configuration mode.
Depending on the configuration of the OTU2_XP card, the ports act as client or trunk ports (see Table 11-26 ). This following section describes the client and trunk rates supported on the OTU2_XP card for different card configurations:
11.16.3.1 Client Interface
In transponder and 10G Ethernet LAN Phy to WAN Phy card configurations, Ports 1 and 2 act as client ports and in splitter protected transponder configuration, Port 1 acts as a client port. For these card configurations, the client rates supported are:
11.16.3.2 Trunk Interface
In transponder, 10G Ethernet LAN Phy to WAN Phy, and splitter protected transponder card configurations, Ports 3 and 4 act as trunk ports. For these card configurations, the trunk rates supported are:
- OC-192/STM-64
- 10G Ethernet WAN Phy
- 10G Ethernet LAN Phy
- 10G Fibre Channel
- OTU2 with ITU-T G.709 for OC-192 client interface
- OTU2e with ITU-T G.709 for 10G Ethernet LAN Phy client interface
- Proprietary rate at the trunk when the client is provisioned as IB_5G
In standard regenerator card configuration, all four ports act as trunk ports and in E-FEC regenerator configuration, Ports 3 and 4 act as the trunk ports. For these card configurations, the trunk rate supported is OTU2 G.709
Note The above mentioned OTU2 signal must be an OC-192/STM-64, 10G Ethernet WAN Phy, 10G Ethernet LAN Phy, or 10G Fibre Channel signal packaged into an OTU2 G.709 frame. Additionally, the standard regenerator and E-FEC regenerator configuration supports an OTU2 signal that is OTU2 has been generated by multiplexing four ODU1 signals.
11.16.4 Configuration Management
The OTU2_XP card supports the following configuration management parameters:
- Card Configuration—Provisionable card configuration: Transponder, Standard Regen, Enhanced FEC, or Mixed, or 10G Ethernet LAN Phy to WAN Phy.
- Port Mode—Provisionable port mode when the card configuration is set as Mixed. The port mode can be chosen as either Transponder or Standard Regen for each port pair (1-3 and 2-4). For card configurations other than Mixed, CTC automatically sets the port mode depending on the selected card configuration. For 10G Ethernet LAN Phy to WAN Phy mode, CTC automatically selects the port pair (1-3) as 10G Ethernet LAN Phy to WAN Phy. Port pair (2-4) in 10G Ethernet LAN Phy to WAN Phy mode is selected as Transponder or Standard Regen.
- Termination Mode—Provisionable termination mode when the card configuration is set as either Transponder or Mixed. The termination mode can be chosen as Transparent, Section, or Line. For Standard Regen and Enhanced FEC card configurations, CTC automatically sets the termination mode as Transparent. For 10G Ethernet LAN Phy to WAN Phy mode, CTC automatically selects the Termination Mode of port pair (1-3) as Line. You cannot provision the Termination Mode parameter.
- AIS/Squelch—Provisionable AIS/Squelch mode configuration when the card configuration is set as either Transponder, Mixed, or Standard Regen. The AIS/Squelch mode configuration can be chosen as AIS or Squelch. For Enhanced FEC card configuration, CTC automatically sets the AIS/Squelch mode configuration as AIS. For 10G Ethernet LAN Phy to WAN Phy mode, the CTC automatically selects the AIS/Squelch of port pair (1-3) as Squelch. You cannot provision the AIS/Squelch parameter.
Note When AIS/Squelch is enabled in Standard Regen configuration with port pairs (1-3) and (2-4), Squelch is supported on ports 1 and 2 and AIS on ports 3 and 4.
Note When you choose the 10G Ethernet LAN Phy to WAN Phy conversion, the Termination mode is automatically set to LINE. The AIS/Squelch is set to SQUELCH and ODU Transparency is set to Cisco Extended Use for Ports 1 and 3.
- Regen Line Name—User-assigned text string for regeneration line name.
- ODU Transparency—Provisionable ODU overhead byte configuration, either Transparent Standard Use or Cisco Extended Use. See the “ODU Transparency” section for more detailed information. For 10G Ethernet LAN Phy to WAN Phy mode, CTC automatically selects the ODU Transparency as Cisco Extended Use. You cannot provision the ODU Transparency parameter.
- Port name—User-assigned text string.
- Admin State/Service State—Administrative and service states to manage and view port status.
- ALS Mode—Provisionable ALS function.
- Reach—Provisionable optical reach distance of the port.
- Wavelength—Provisionable wavelength of the port.
- AINS Soak—Provisionable automatic in-service soak period.
11.16.5 OTU2_XP Card Configuration Rules
The following rules apply to OTU2_XP card configurations:
- When you preprovision the card, port pairs 1-3 and 2-4 come up in the default Transponder configuration.
- The port pairs 1-3 and 2-4 can be configured in different modes only when the card configuration is Mixed. If the card configuration is Mixed, you must choose different modes on port pairs 1-3 and 2-4 (that is, one port pair in Transponder mode and the other port pair in Standard Regen mode).
- If the card is in Transponder configuration, you can change the configuration to Standard Regen or Enhanced FEC.
- If the card is in Standard Regen configuration and you have configured only one port pair, then configuring payload rates for the other port pair automatically changes the card configuration to Mixed, with the new port pair in Transponder mode.
- If the card is in Standard Regen configuration, you cannot directly change the configuration to Enhanced FEC. You have to change to Transponder configuration and then configure the card as Enhanced FEC.
- If the card is in Enhanced FEC configuration, Ports 1 and 2 are disabled. Hence, you cannot directly change the configuration to Standard Regen or Mixed. You must remove the Enhanced FEC group by moving the card to Transponder configuration, provision PPM on Ports 1 and 2, and then change the card configuration to Standard Regen or Mixed.
- If the card is in Standard Regen or Enhanced FEC configuration, you cannot change the payload rate of the port pairs. You have to change the configuration to Transponder, change the payload rate, and then move the card configuration back to Standard Regen or Enhanced FEC.
- If any of the affected ports are in IS (ANSI) or Unlocked-enabled (ETSI) state, you cannot change the card configuration.
- If IB_5G payload has to be provisioned, the NE Default should match the values listed in the Table 11-27 . For more information on editing the NE Default values, see the G135 Edit Network Element Defaults.
- If the card is changed to 10G Ethernet LAN Phy to WAN Phy, the first PPM port is deleted and replaced by a 10G Ethernet port; the third PPM port is deleted and automatically replaced with OC192/STM64 (SONET/SDH) port. The third PPM port is automatically deleted and the third PPM port is replaced with OC192/STM64 (SONET/SDH).
Table 11-28 provides a summary of transitions allowed for the OTU2_XP card configurations.
11.16.6 Security
The OTU2_XP card, when an XFP is plugged into it, implements the Cisco Standard Security Code Check Algorithm that keys on vendor ID and serial number.
If a PPM is plugged into a port on the card but fails the security code check because it is not a Cisco PPM, a NON-CISCO-PPM Not Reported (NR) condition occurs.
If a PPM with a non-qualified product ID is plugged into a port on this card, that is, the PPM passes the security code as a Cisco PPM but it has not been qualified for use on the OTU2_XP card, a UNQUAL-PPM NR condition occurs.
11.16.7 ODU Transparency
A key feature of the OTU2_XP card is the ability to configure the ODU overhead bytes (EXP bytes and RES bytes 1 and 2) using the ODU Transparency parameter. The two options available for this parameter are:
- Transparent Standard Use—ODU overhead bytes are transparently passed through the card. This option allows the OTU2_XP card to act transparently between two trunk ports (when the card is configured in Standard Regen or Enhanced FEC).
- Cisco Extended Use—ODU overhead bytes are terminated and regenerated on both ports of the regenerator group.
The ODU Transparency parameter is configurable only for Standard Regen and Enhanced FEC card configuration. For Transponder card configuration, this parameter defaults to Cisco Extended Use and cannot be changed.
Note The Forward Error Correction (FEC) Mismatch (FEC-MISM) alarm will not be raised on OTU2_XP card when you choose Transparent Standard Use.
11.16.8 OTU2_XP Functions
The functions of the OTU2_XP card are:
- Automatic Laser Shutdown
- Y-Cable and Splitter Protection
- Card level indicators—Table G-1
- Port level indicators—Table G-11
11.17 TXP_MR_10EX_C Card
The TXP_MR_10EX_C card is a multirate transponder for the ONS 15454 platform. The card is fully backward compatible with TXP_MR_10E_C cards (only when the error decorrelator is disabled in the CTC on the TXP_MR_10EX_C card). It processes one 10-Gbps signal (client side) into one 10-Gbps, 100-GHz DWDM signal (trunk side). The TXP_MR_10EX_C card is tunable over the 82 channels of C-band (82 channels spaced at 50 GHz on the ITU grid).
You can install TXP_MR_10EX_C card in Slots 1 to 6 and 12 to 17. The card can be provisioned in linear, BLSR/MS-SPRing, path protection/SNCP configurations or as a regenerator. The card can be used in the middle of BLSR/MS-SPRing or 1+1 spans when the card is configured for transparent termination mode. The TXP_MR_10EX_C card features an MLSE-based Universal Transponder 1550-nm tunable laser and a separately orderable ONS-XC-10G-S1 1310-nm or ONS-XC-10G-L2 1550-nm laser XFP module for the client port.
Note The PRE FEC BER performance of the TXP_MR_10EX_C card may be significantly low when compared to the TXP_MR_10E card. However, this does not affect the Post FEC BER performance, but could possibly affect any specific monitoring application that relies on the PRE FEC BER value (for example, protection switching). In this case, the replacement of TXP_MR_10E card with the TXP_MR_10EX_C may not work properly.
Note When the ONS-XC-10G-L2 XFP is installed, the TXP_MR_10EX_C card must be installed in a high-speed slot (slot 6, 7, 12, or 13)
On its faceplate, the TXP_MR_10EX_C card contains two transmit and receive connector pairs, one for the trunk port and one for the client port. Each connector pair is labeled.
11.17.1 Key Features
The key features of the TXP_MR_10EX_C card are:
– (ONS-XC-10G-S1 version 3 only) IB_5G
- An MLSE-based UT module tunable through 82 channels of C-band. The channels are spaced at 50 GHz on the ITU grid.
- OC-192 to ITU-T G.709 OTU2 provisionable synchronous and asynchronous mapping.
- Proprietary rate at the trunk when the client is provisioned as IB_5G.
- The MTU setting is used to display the OverSizePkts counters on the receiving trunk and client port interfaces. Traffic of frame sizes up to 65535 bytes pass without any packet drops, from the client port to the trunk port and vice versa irrespective of the MTU setting.
11.17.2 Faceplate and Block Diagram
Figure 11-23 shows the TXP_MR_10EX_C faceplate and block diagram.
Figure 11-23 TXP_MR_10EX_C Faceplate and Block Diagram
For information about safety labels for the card, see the “Class 1M Laser Product Cards” section.
11.17.3 TXP_MR_10EX_C Functions
The functions of the TXP_MR_10EX_C card are:
- Client Interface
- DWDM Trunk Interface
- FEC
- Client-to-Trunk Mapping
- Automatic Laser Shutdown
- Card level indicators—Table G-1
- Port level indicators—Table G-6.
11.18 MXP_2.5G_10EX_C card
The MXP_2.5G_10EX_C card is a DWDM muxponder for the ONS 15454 platform that supports transparent termination mode on the client side. The faceplate designation of the card is “4x2.5G 10EX MXP.” The card multiplexes four 2.5-Gbps client signals (4xOC48/STM-16 SFP) into a single 10-Gbps DWDM optical signal on the trunk side. The card provides wavelength transmission service for the four incoming 2.5-Gbps client interfaces. The MXP_2.5G_10EX_C muxponder passes all SONET/SDH overhead bytes transparently.
The digital wrapper function (ITU-T G.709 compliant) formats the DWDM wavelength so that it can be used to set up GCCs for data communications, enable FEC, or facilitate PM.
The MXP_2.5G_10EX_C card works with OTN devices defined in ITU-T G.709. The card supports ODU1 to OTU2 multiplexing, an industry standard method for asynchronously mapping a SONET/SDH payload into a digitally wrapped envelope. See the “Multiplexing Function” section.
The MXP_2.5G_10EX_C card is not compatible with the MXP_2.5G_10G card, which does not support transparent termination mode.
You can install the MXP_2.5G_10EX_C card in slots 1 to 6 and 12 to 17. You can provision a card in a linear configuration, a BLSR/MS-SPRing, a path protection/SNCP, or a regenerator. The card can be used in the middle of BLSR/MS-SPRing or 1+1 spans when the card is configured for transparent termination mode.
The MXP_2.5G_10EX_C card features a tunable 1550-nm C-band laser on the trunk port. The laser is tunable across 82 wavelengths on the ITU grid with 50-GHz spacing between wavelengths. The card features four 1310-nm lasers on the client ports and contains five transmit and receive connector pairs (labeled) on the card faceplate. The card uses dual LC connectors on the trunk side and SFP modules on the client side for optical cable termination. The SFP pluggable modules are SR or IR and support an LC fiber connector.
Note When you create a 4xOC-48 OCHCC circuit, you need to select the G.709 and Synchronous options. A 4xOC-48 OCHCC circuit is supported by G.709 and synchronous mode, which are necessary to provision the 4xOC-48 OCHCC circuit.
11.18.1 Key Features
The MXP_2.5G_10EX_C card has the following high-level features:
- Four 2.5-Gbps client interfaces (OC-48/STM-16) and one 10-Gbps trunk. The four OC-48 signals are mapped into an ITU-T G.709 OTU2 signal using standard ITU-T G.709 multiplexing.
- Onboard E-FEC processor: The processor supports both standard RS (specified in ITU-T G.709) and E-FEC, which allows an improved gain on trunk interfaces with a resultant extension of the transmission range on these interfaces. The E-FEC functionality increases the correction capability of the transponder to improve performance, allowing operation at a lower OSNR compared to the standard RS (237,255) correction algorithm.
- Pluggable client-interface optic modules: The MXP_2.5G_10EX_C card has modular interfaces. Two types of optic modules can be plugged into the card. These modules include an OC-48/STM-16 SR-1 interface with a 7-km (4.3-mile) nominal range (for short range and intra-office applications) and an IR-1 interface with a range of up to 40 km (24.9 miles). SR-1 is defined in Telcordia GR-253-CORE and in I-16 (ITU-T G.957). IR-1 is defined in Telcordia GR-253-CORE and in S-16-1 (ITU-T G.957).
- High-level provisioning support: The card is initially provisioned using Cisco TransportPlanner software. Subsequently, the card can be monitored and provisioned using CTC software.
- Link monitoring and management: The card uses standard OC-48 OH (overhead) bytes to monitor and manage incoming interfaces. The card passes the incoming SDH/SONET data stream and its overhead bytes transparently.
- Control of layered SONET/SDH transport overhead: The card is provisionable to terminate regenerator section overhead, which eliminates forwarding of unneeded layer overhead. It can help reduce the number of alarms and help isolate faults in the network.
- Automatic timing source synchronization: The MXP_2.5G_10EX_C card normally synchronizes from the TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE card. If for some reason, such as maintenance or upgrade activity, the TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE is not available, the card automatically synchronize to one of the input client-interface clocks.
- Configurable squelching policy: The card can be configured to squelch the client interface output if LOS occurs at the DWDM receiver or if a remote fault occurs. In the event of a remote fault, the card manages MS-AIS insertion.
- The card is tunable across the full C-band, thus eliminating the need to use different versions of each card to provide tunability across specific wavelengths in a band.
11.18.2 Faceplate and Block Diagram
Figure 11-24 shows the MXP_2.5G_10EX_C faceplate and block diagram.
Figure 11-24 MXP_2.5G_10EX_C Faceplate and Block Diagram
For information about safety labels for the card, see the “Class 1 Laser Product Cards” section.
11.18.3 MXP_2.5G_10EX_C Functions
The functions of the MXP_2.5G_10EX_C card are:
- Client Interface
- DWDM Interface
- FEC
- Multiplexing Function
- Timing Synchronization
- SONET/SDH Overhead Byte Processing
- SONET/SDH Overhead Byte Processing
- Client Interface Monitoring
- Automatic Laser Shutdown
- Jitter
- Lamp Test
- Onboard Traffic Generation
- Card level indicators—Table G-1
- Port level indicators—Table G-6
11.18.3.1 Wavelength Identification
The card uses trunk lasers that are wavelocked, which allows the trunk transmitter to operate on the ITU grid effectively. The MXP_2.5G_10EX_C card implements the MLSE-based UT module. The MXP_2.5G_10EX_C card uses a C-band version of the UT2.
Table 11-29 describes the required trunk transmit laser wavelengths for the MXP_2.5G_10EX_C card. The laser is tunable over 82 wavelengths in the C-band at 50-GHz spacing on the ITU grid.
11.19 MXP_MR_10DMEX_C Card
The MXP_MR_10DMEX_C card aggregates a mix of client SAN service-client inputs (GE, FICON, and Fibre Channel) into one 10-Gbps STM-64/OC-192 DWDM signal on the trunk side. It provides one long-reach STM-64/OC-192 port per card and is compliant with Telcordia GR-253-CORE and ITU-T G.957.
The card supports aggregation of the following signal types:
- 1-Gigabit Fibre Channel
- 2-Gigabit Fibre Channel
- 4-Gigabit Fibre Channel
- 1-Gigabit Ethernet
- 1-Gigabit ISC-Compatible (ISC-1)
- 2-Gigabit ISC-Peer (ISC-3)
The MXP_MR_10DMEX_C muxponder passes all SONET/SDH overhead bytes transparently.
The digital wrapper function (ITU-T G.709 compliant) formats the DWDM wavelength so that it can be used to set up GCCs for data communications, enable FEC, or facilitate PM. The MXP_MR_10DMEX_C card works with the OTN devices defined in ITU-T G.709. The card supports ODU1 to OTU2 multiplexing, an industry standard method for asynchronously mapping a SONET/SDH payload into a digitally wrapped envelope. See the “Multiplexing Function” section.
Note You cannot disable ITU-T G.709 on the trunk side. If ITU-T G.709 is enabled, then FEC cannot be disabled.
Note Because the client payload cannot oversubscribe the trunk, a mix of client signals can be accepted, up to a maximum limit of 10 Gbps.
You can install the MXP_MR_10DMEX_C card in slots 1 to 6 and 12 to 17.
Note The MXP_MR_10DMEX_C card is not compatible with the MXP_2.5G_10G card, which does not support transparent termination mode.
The MXP_MR_10DMEX_C card features a tunable 1550-nm C-band laser on the trunk port. The laser is tunable across 82 wavelengths on the ITU grid with 50-GHz spacing between wavelengths. Each card features four 1310-nm lasers on the client ports and contains five transmit and receive connector pairs (labeled) on the card faceplate. The card uses dual LC connectors on the trunk side and SFP modules on the client side for optical cable termination. The SFP pluggable modules are SR or IR and support an LC fiber connector.
Table 11-30 shows the input data rate for each client interface, and the encapsulation method. The current version of the GFP-T G.7041 supports transparent mapping of 8B/10B block-coded protocols, including Gigabit Ethernet, Fibre Channel, ISC, and FICON.
In addition to the GFP mapping, 1-Gbps traffic on Port 1 or 2 of the high-speed SERDES is mapped to an STS-24c channel. If two 1-Gbps client signals are present at Port 1 and Port 2 of the high-speed SERDES, the Port 1 signal is mapped into the first STS-24c channel and the Port 2 signal into the second STS-24c channel. The two channels are then mapped into an OC-48 trunk channel.
The MXP_MR_10DMEX_C card includes two FPGAs, and a group of four ports is mapped to each FPGA. Group 1 consists of Ports 1 through 4, and Group 2 consists of Ports 5 through 8. Table 11-31 shows some of the mix and match possibilities on the various client data rates for Ports 1 through 4, and Ports 5 through 8. An X indicates that the data rate is supported in that port.
GFP-T PM is available through 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.
A buffer-to-buffer credit management scheme provides FC flow control. With this feature 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_10DMEX_C card supports FC credit-based flow control with a buffer-to-buffer credit extension of up to 1600 km (994.1 miles) for 1G FC, up to 800 km (497.1 miles) for 2G FC, or up to 400 km (248.5 miles) for 4G FC. The feature can be enabled or disabled.
The MXP_MR_10DMEX_C 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. The trunk port is a dual-LC connector with a 45-degree downward angle.
11.19.1 Key Features
The MXP_MR_10DMEX_C card has the following high-level features:
- Onboard E-FEC processor: The processor supports both standard RS (specified in ITU-T G.709) and E-FEC, which allows an improved gain on trunk interfaces with a resultant extension of the transmission range on these interfaces. The E-FEC functionality increases the correction capability of the transponder to improve performance, allowing operation at a lower OSNR compared to the standard RS (237,255) correction algorithm.
- Pluggable client-interface optic modules: The MXP_MR_10DMEX_C card has modular interfaces. Two types of optics modules can be plugged into the card. These modules include an OC-48/STM-16 SR-1 interface with a 7-km (4.3-mile) nominal range (for short range and intra-office applications) and an IR-1 interface with a range of up to 40 km (24.9 miles). SR-1 is defined in Telcordia GR-253-CORE and in I-16 (ITU-T G.957). IR-1 is defined in Telcordia GR-253-CORE and in S-16-1 (ITU-T G.957).
- Y-cable protection: The card supports Y-cable protection between the same card type only, on ports with the same port number and signal rate. See the “Y-Cable Protection” section for more detailed information.
- High-level provisioning support: The card is initially provisioned using Cisco TransportPlanner software. Subsequently, the card can be monitored and provisioned using CTC software.
- ALS: This safety mechanism is used in the event of a fiber cut. For details regarding ALS provisioning for the MXP_MR_10DMEX_C card, see the “G162 Change the ALS Maintenance Settings” section.
- Link monitoring and management: The card uses standard OC-48 OH (overhead) bytes to monitor and manage incoming interfaces. The card passes the incoming SDH/SONET data stream and its OH (overhead) bytes transparently.
- Control of layered SONET/SDH transport overhead: The card is provisionable to terminate regenerator section overhead, which eliminates forwarding of unneeded layer overhead. It can help reduce the number of alarms and help isolate faults in the network.
- Automatic timing source synchronization: The MXP_MR_10DMEX_C card normally synchronizes from the TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE card. If for some reason, such as maintenance or upgrade activity, the TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE is not available, the card automatically synchronizes to one of the input client-interface clocks.
Note MXP_MR_10DMEX_C card cannot be used for line timing.
- Configurable squelching policy: The card can be configured to squelch the client-interface output if LOS occurs at the DWDM receiver or if a remote fault occurs. In the event of a remote fault, the card manages MS-AIS insertion.
- The card is tunable across the full C-band, thus eliminating the need to use different versions of each card to provide tunability across specific wavelengths in a band.
- You can provision a string (port name) for each fiber channel/FICON interface on the MXP_MR_10DMEX_C card, 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.
11.19.2 Faceplate and Block Diagram
Figure 11-25 shows the MXP_MR_10DMEX_C faceplate and block diagram.
Figure 11-25 MXP_MR_10DMEX_C Faceplate and Block Diagram
For information about safety labels for the card, see the “Class 1M Laser Product Cards” section.
11.19.3.1 Wavelength Identification
The card uses trunk lasers that are wavelocked, which allows the trunk transmitter to operate on the ITU grid effectively. The MXP_MR_10DMEX_C card uses a C-band version of the MLSE-based UT module.
Table 11-32 describes the required trunk transmit laser wavelengths for the MXP_MR_10DMEX_C card. The laser is tunable over 82 wavelengths in the C-band at 50-GHz spacing on the ITU grid.
11.20 AR_MXP, AR_XP, and AR_XPE Cards
The AR_MXP (Any-Rate Muxponder), AR_XP (Any-Rate Xponder), and AR_XPE (Any-Rate Enhanced Xponder) cards are supported on ONS 15454, ONS 15454 M2, and ONS 15454 M6 platforms. The AR_MXP card supports a trunk bandwidth of up to 10 Gbps. The AR_XP and AR_XPE cards support a trunk bandwidth of up to 20 Gbps. The AR_MXP, AR_XP, and AR_XPE cards aggregate a mix of client SAN services (FC or FICON 1G/2G/4G/8G, ESCON and ISC3-STP 1G/2G), Ethernet (FE, GE, 10GE LAN), OCn (OC3/STM-1, OC12/STM-4, and OC48/STM-16), OTU (OTU1, OTU2e/1e), and Video (SD-SDI, HD-SDI, and 3G-SDI) into one 10 Gbps signal on the trunk side.
The cards support aggregation of the following signal types:
– Enterprise Systems Connection (ESCON)
– 1 Gigabit Fiber Channel or fiber connectivity (FICON)
– 2 Gigabit Fiber Channel or FICON
– 4 Gigabit Fiber Channel or FICON
– 8 Gigabit Fiber Channel or FICON
– Third-generation SDI (3G-SDI) (2.970 Gbps)
The AR_MXP, AR_XP, and AR_XPE cards pass all SONET/SDH overhead bytes transparently.
The digital wrapper function (ITU-T G.709 compliant) formats the DWDM wavelength so that it can be used to set up GCCs for data communications, enable FEC, or facilitate PM. The AR_MXP, AR_XP, and AR_XPE cards work with the OTN devices defined in ITU-T G.709. The client can be OTU1 with standard G.975 FEC or disabled FEC. The cards provide standard 4 x OTU1 to OTU2 multiplexing. The card is equipped with standard G.709 FEC, E-FEC I.4, E-FEC I.7 and disabled FEC. The cards support ODU0/ODU1 to OTU1 or OTU2 multiplexing, an industry standard method for asynchronously mapping a SONET/SDH payload into a digitally wrapped envelope. For more details on multiplexing, see “Multiplexing Function” section.
Table 11-33 shows the input data rate for each client interface, and the encapsulation method.
GFP-F |
||
11.20.1 Key Features
The AR_MXP, AR_XP, and AR_XPE cards support the following key features:
- Multiple Operating Modes—The AR_MXP, AR_XP, or AR_XPE card can be configured into multiple operating modes. The cards are equipped with pluggables for client and trunk options, and offer a large variety of configurations. For more information about multiple operating modes, see Multiple Operating Modes.
- Operating Mode to Client Payload Mapping—Each operating mode supports a specific set of client payloads. Table 11-34 and Table 11-35 lists the supported payloads for each operating mode.
- Auto Sensing—The AR_MXP, AR_XP, and AR_XPE cards support auto sensing of client payloads. The line card analyzes the received client signal and configures the payload on the client port automatically without user intervention.
Auto sensing feature is supported on the Gigabit Ethernet, OC-3/STM-1, OC-12/STM-4, and OC-48/STM-16 payloads. Following operating card modes support the autosensing feature:
CTC supports the configuration of all the provisioning parameters supported by the autosensed payload. However, creation and deletion of the
circuits are the only configurations supported on the “AUTO” payload.
- Video Multiplexing—The AR_XP and AR_XPE cards support the capability to multiplex SD-SDI, HD-SDI, and 3G-SDI signals over the OTU2 trunk interface allowing to maximize the wavelength bandwidth, maintain full transparency for uncompressed signals, and reduce latency. The video multiplexing of 3G-SDI signal is not supported on the AR_MXP card.
- Regenerator Mode—This mode regenerates the OTU2e or OTU1 signals with ODU transparent or CISCO Extended Use options. For OTU2e, FEC can be Disabled, Standard G.975, EFEC I.4 or EFEC I.7, and for OTU1, FEC can be Standard G.975 or Disabled.
- High Speed GCCs—The AR_MXP, AR_XP, and AR_XPE cards support the provisioning of GCC channel on OTN (OTU1/OTU2) enabled client and trunk ports. A maximum of five GCC channels on the Cisco ONS 15454 shelf and ten GCC channels on Cisco ONS 15454 M2 or Cisco ONS 15454 M6 shelf can be created. The high speed GCC enables you to create the GCC when both the NE and FE line cards are in Cisco ONS 15454 M2 or Cisco ONS 15454 M6 shelf. The legacy GCC on Cisco ONS 15454 shelf can be selected on one side and the Cisco ONS 15454, Cisco ONS 15454 M2 or Cisco ONS 15454 M6 shelf on the other side.
- Y-cable protection—Y-cable protection between the same card type is supported only on ports with the same port number and signal rate. For more detailed information, see “Y-Cable Protection” section.
- Splitter protection—For splitter protection, OCHCC circuits with different trunk wavelengths for the working and protect paths can be configured. The process of setting the trunk wavelengths is similar to the G367 Change the 2.5G Multirate Transponder Trunk Wavelength Settings. OCHCC circuits having different trunk wavelengths on the working and protect paths can be upgraded to GMPLS circuits.
-
SyncE Support—Customers using a packet network find it difficult to provide timing to multiple remote network elements (NEs) through an external time division multiplexed (TDM) circuit. The SyncE feature helps to overcome this problem by providing effective timing to the remote NEs through a packet network. SyncE leverages the physical layer of the Ethernet to transmit frequency to the remote sites. SyncE's functionality and accuracy resemble the SONET/SDH network because of its physical layer characteristic.
The SyncE feature provides the required synchronization at the physical level. Operation messages maintain SyncE links and ensure that a node always derives timing from the most reliable source. SyncE uses the Ethernet Synchronization Message Channel (ESMC) to enable traceability of the best clock source to correctly define the timing source and prevent a timing loop. SyncE is not supported on the AR_XPE card. - Licensing—The AR_MXP and AR_XP cards offer you an unprecedented flexibility. The cards support a wide range of different applications and configurations. To help you take advantage of such flexibility to lower capital expenditures (CapEx) on your network, Cisco provides a licensing model for AR_MXP and AR_XP cards. Licensing is not supported on the AR_XPE card. For more information on licensing, see the Cisco ONS 15454 DWDM Licensing Configuration Guide.
11.20.2 Faceplate and Block Diagram
Figure 11-26 shows the AXP_MXP, AR_XP, and AR_XPE faceplates.
The AR_MXP, AR_XP, and AR_XPE cards have eight SFP and two XFP ports. The client and trunk ports are either SFP (2.5 G) or XFP (10 G) based ports.
The AR_MXP, AR_XP, or AR_XPE card can be tuned to any wavelength over the C-band by inserting the required DWDM SFP or XFP on client or trunk ports. For optical termination, each XFP/SFP uses two LC connectors, which are labeled TX and RX on the faceplate.
Figure 11-26 AR_MXP, AR_XP, and AR_XPE Faceplates
Figure 11-27 shows the AXP_MXP, AR_XP, and AR_XPE block diagram.
Figure 11-27 AR_MXP, AR_XP, and AR_XPE Block Diagram
For information on safety labels for the cards, see the “Class 1M Laser Product Cards” section.
The AR_MXP, AR_XP, and AR_XPE cards can be installed in Slot 1 to Slot 6 and Slot 12 to Slot 17 in the Cisco ONS 15454 chassis, the Slot 2 to Slot 7 in the Cisco ONS 15454 M6 chassis, and Slot 2 and Slot 3 in the Cisco ONS 15454 M2 chassis. The AR_MXP, AR_XP, and AR_XPE cards do not interoperate with all the existing TXP or MXP cards. The AR_MXP card allows you to configure only one high rate XFP port. This can be a muxponder mode where N [N= 1 to 8] client ports goes out via 1 trunk XFP port or in a transponder mode where client and trunk are XFP ports. There is no limitation in the AR_XP and AR_XPE cards, where you can use both high rate trunk ports simultaneously.
The AR_XPE card does not interoperate with AR_MXP and AR_XP cards.
11.20.3 Multiple Operating Modes
A single AR_MXP, AR_XP, or AR_XPE card can be configured into multiple operating modes. Criteria for selecting a particular operational mode are defined by the network level design. CTP helps you to choose the appropriate operational mode. Each operating mode is divided into two categories based on the trunk rate:
The AR_XP or AR_XPE card allows you to configure two high rate operational modes, where as you can configure only one high rate operational mode on the AR_MXP card.
When you configure the AR_MXP, AR_XP, or AR_XPE card in to multiple operational modes, make sure that the following tasks are completed:
- In order to make the ports operational and to correctly report alarms, OCHCC circuit must be created for the following operating modes:
- Same operational mode is configured at both ends and ensure the port numbers are same on both ends.
- The OCHCC circuit should be created between the same client port numbers at the near and far end.
- Ensure ODU1 and timeslots are matching at both ends.
- For AR_XPE card that is configured with 1GE or 1GFC payload, ensure that ODU0 and ODU1 are matching at both ends.
- For auto sensing payloads created on auto ports, you should check the Auto Sensing checkbox in the provisioning pane.
- GMPLS circuits can be created on AR_MXP, AR_XP, and AR_XPE cards.
- PPMs must be provisioned on all ports before configuring the operational mode.
- The following conditions determine the maximum bandwidth at the client side when a 4GFC payload is configured in the TXP_MR or TXPP_MR mode:
– The maximum client bandwidth should not exceed 28G when TXP_MR or TXPP_MR operating mode is configured on the AR_MXP, AR_XP, or AR_XPE card and other operating modes, like low-rate or high-rate TXP_MR,TXPP_MR, MXP_DME, MXPP_DME, MXP_MR, MXPP_MR, MXP-4X2.5G-10G, MXPP-4X2.5G-10G, and MXP-VDC-10G, are configured on the same card.
– The maximum client bandwidth should not exceed 20G when a TXP_MR or TXPP_MR operating mode is configured on the AR_MXP, AR_XP, or AR_XPE card and if more than two or more combinations of Low-rate or high-rate TXP_MR,TXPP_MR, MXP_DME, MXPP_DME, MXP_MR, MXPP_MR, MXP-4X2.5G-10G, MXPP-4X2.5G-10G, and MXP-VDC-10G, operating modes are configured on the same card.
– The utilized client bandwidth is 8G when the TXP_MR operating mode is configured with a 4GFC as payload.
– The utilized client bandwidth is 12G when the TXPP_MR operating mode is configured with a 4GFC as payload.
– There is no restriction on the bandwidth if only TXP_MR or TXPP_MR operating mode with 4GFC payload is configured on the card. For example, four instances of TXP_MR mode with 4GFC payload on one AR_MPX, AR_XP, or AR_XPE card.
– The low-rate or high-rate RGN operating mode does not add to the client side bandwidth. For example, four instances of TXP_MR mode with 4GFC and one instance of high-rate RGN mode on same card.
For all the other payloads and operating modes, the client bandwidth utilized is the client payload data rate.
- If you revert to a release earlier than Release 9.8.x, ensure that you delete the following card modes:
– Low-rate TXPP_MR if the client payload is 4GFC.
– High-rate TXP_MR if the client payload is 10 GE.
The AR_MXP, AR_XP, and AR_XPE cards support the following operating modes:
- TXP_MR (Unprotected Transponder)
- TXPP_MR (Protected Transponder)
- MXP_DME (Unprotected Data Muxponder)
- MXPP_DME (Protected Data Muxponder)
- MXP_MR (Unprotected Multirate Muxponder)
- MXPP_MR (Protected Multirate Muxponder)
- MXP-4x2.5-10G (OC48/OTU1 Unprotected Muxponder)
- MXPP-4x2.5-10G (OC48/OTU1 Protected Muxponder)
- RGN (OTU1/OTU2 Regenerator)
- MXP-VD-10G (Video Muxponder)
TXP_MR (Unprotected Transponder)
The AR_MXP, AR_XP, or AR_XPE card can be configured as a low-rate or a high-rate TXP_MR card mode.
Note OTN cannot be enabled for 4GFC trunk ports.
- Low Rate—A maximum of four TXP_MR configurations can be provisioned on a single AR_MXP, AR_XP, or AR_XPE card (Figure 11-28). The AR_MXP, AR_XP, or AR_XPE card can be configured as a low-rate TXP_MR card by adhering to the following provisioning rules:
1. Two SFP ports must be grouped. The allowed port pairs are 1-2, 3-4, 5-6, 7-8, 1-5, 2-6, 3-7, and/or 4-8.
2. Ports 2, 4, 5, 6, 7, or 8 can be configured as trunk ports.
3. Ports 1, 2, 3, 4, 5 or 7 can be configured as client ports.
Note The trunk port is not created when the low-rate TXP_MR card operating mode is configured. It is created after the client payload is created.
Figure 11-28 Low-Rate TXP_MR Card Operating Mode Configuration
- High Rate—Only one TXP_MR configuration can be provisioned on a single AR_MXP, AR_XP, or AR_XPE card (Figure 11-29). The AR_MXP, AR_XP, or AR_XPE card can be configured as a high-rate TXP_MR card by adhering to the following provisioning rules:
1. XFP ports 9 and 10 must be grouped.
2. Port 10 must be configured as a trunk port.
3. Port 9 must be configured as a client port.
Figure 11-29 High-Rate TXP_MR Card Operating Mode Configuration
TXPP_MR (Protected Transponder)
The AR_MXP, AR_XP, or AR_XPE card can be configured as a low-rate TXPP_MR card mode. A maximum of two TXPP_MR configurations can be provisioned on a single AR_MXP, AR_XP, or AR_XPE card (Figure 11-30). The AR_MXP, AR_XP, or AR_XPE card can be configured as a low-rate TXPP_MR card by adhering to the following provisioning rules:
1. Three SFP ports must be grouped. The allowed port pairs are 1-5-6 or 2-7-8, or both.
2. Ports 5 and 6, and 7 and 8 must be configured as trunk ports, where 6 and 8 are the protect trunk ports for 5 and 6 respectively.
3. Ports 1 and 2 must be configured as client ports.
Splitter protection is automatically created between ports 5-6 and 7-8.
Figure 11-30 Low-Rate TXPP_MR Card Operating Mode Configuration
MXP_DME (Unprotected Data Muxponder)
The AR_XP or AR_XPE card can be configured as a high-rate 4:1 or 8:1 MXP_DME card mode. The AR_MXP card can be configured as a high rate 8:1 MXP_DME card mode.
- 4:1 MXP_DME mode—A maximum of two MXP_DME configurations can be provisioned on a single AR_XP or AR_XPE card (Figure 11-31). The AR_XP or AR_XPE card can be configured as a high-rate 4:1 MXP_DME card by adhering to the following provisioning rules:
1. Four SFP ports and one XFP port must be grouped. The allowed port pairs are 1-2-3-4-9 or 5-6-7-8-10, or both.
2. Port 9 or 10 must be configured as a trunk port.
3. Ports 1, 2, 3, and 4, or 5, 6, 7, and 8 must be configured as client ports.
- 8:1 MXP_DME mode—Only one MXP_DME configuration can be provisioned on a single AR_MXP, AR_XP, or AR_XPE card (Figure 11-31). The AR_MXP, AR_XP, AR_XPE card can be configured as a high-rate 8:1 MXP_DME card by adhering to the following provisioning rules:
1. Eight SFP ports and one XFP port must be grouped. The allowed port pairs are 1-2-3-4-5-6-7-8-9.
2. Port 9 must be configured as a trunk port.
3. Ports 1 to 8 must be configured as client ports.
Figure 11-31 High-Rate MXP_DME Card Operating Mode Configuration
MXPP_DME (Protected Data Muxponder)
The AR_XP or AR_XPE card can be configured as a high-rate 4:2 or 8:2 MXPP_DME card mode.
- 4:2 MXP_DME mode—Only one MXPP_DME configuration can be provisioned on a single AR_XP or AR_XPE card (Figure 11-32). The AR_XP or AR_XPE card can be configured as a high-rate 4:2 MXPP_DME card by adhering to the following provisioning rules:
1. Four SFP ports and two XFP ports must be grouped. The allowed port pairs are 1-2-3-4-9-10 or 5-6-7-8-9-10.
2. Ports 9 and 10 must be configured as trunk ports.
3. Ports 1, 2, 3, and 4, or 5, 6, 7, and 8 must be configured as client ports.
Splitter protection is automatically created between ports 9 and 10. Port 10 will be the protected trunk port for port 9.
- 8:2 MXPP_DME mode—Only one MXPP_DME configuration can be provisioned on a single AR_XP or AR_XPE card (Figure 11-32). The AR_XP or AR_XPE card can be configured as a high-rate 8:2 MXPP_DME card by adhering to the following provisioning rules:
1. Eight SFP ports and two XFP ports must be grouped. The allowed port pairs are 1-2-3-4-5-6-7-8-9-10.
2. Ports 9 and 10 must be configured as trunk ports.
3. Ports 1 to 8 must be configured as client ports.
Splitter protection is automatically created between ports 9 and 10. Port 10 will be the protected trunk port for port 9.
Figure 11-32 High-Rate MXPP_DME Card Operating Mode Configuration
MXP_MR (Unprotected Multirate Muxponder)
The AR_MXP, AR_XP, or AR_XPE card can be configured as a low-rate or a high-rate MXP_MR card mode.
- Low Rate—A maximum of two MXP_MR configurations can be provisioned depending on the availability of client ports (Figure 11-33). The AR_MXP, AR_XP, or AR_XPE card can be configured as a low-rate MXP_MR card by adhering to the following provisioning rules:
1. N:1 muxponder must be created, where N varies from client ports 2 to 7.
2. Only ports 5, 6, 7, or 8 can be configured as trunk ports.
3. Ports 1 to 8 can be configured as client ports, if they are not configured as trunk ports.
Any client port can be added or deleted, if the trunk bandwidth supports the new payload without impacting the traffic on the existing services. Minimum of two client ports should be part of the operational mode group.
On the AR_XPE card, 1GE or 1G FC payload cannot be configured with other payloads. When a 1GE or 1GFC payload is configured on a port of MXP_MR (low rate) mode, then only 1GE or 1GFC payload can be configured on the other ports.
Figure 11-33 Low-Rate MXP_MR Card Operating Mode Configuration
- High Rate—A maximum of two MXP_MR configurations can be provisioned on a AR_XP or AR_XPE card and only one such configuration can be provisioned on an AR_MXP card (Figure 11-34). The AR_MXP, AR_XP, or AR_XPE card can be configured as a high-rate MXP_MR card by adhering to the following provisioning rules:
1. N:1 muxponder must be created, where N varies from client ports 2 to 8.
2. Only ports 9 and 10 can be configured as trunk ports.
3. Ports 1 to 8 can be configured as client ports.
Any client payload can be added or deleted, if the trunk bandwidth supports the new payload without impacting the traffic on the existing services.
On the AR_XPE card, when you create a OCHCC circuit using 1GE or 1GFC payload, only ODU0 mapping is supported and timeslot mapping is not supported. When a OCHCC circuit is created on a particular ODU1 timeslot with payloads using timeslot mapping, OCHCC circuits cannot be created on payloads using ODU0 mapping, but can be created on the other ODU1 timeslot. In MXP_MR (high-rate) mode, while creating a OCHCC circuits on the GE or 1GFC client payload, you can select the ODU1 and ODU0 timeslots instead of ODU1 and timeslot selection.
Figure 11-34 High-Rate MXP_MR Card Operating Mode Configuration
MXPP_MR (Protected Multirate Muxponder)
The AR_MXP, AR_XP, or AR_XPE card can be configured as a low-rate or a high-rate MXPP_MR card mode.
- Low Rate—A maximum of two MXPP_MR configurations can be provisioned depending on the availability of client ports (Figure 11-35). Any client payload can be added or deleted, if the trunk bandwidth supports the new payload without impacting the traffic on the existing services.
The AR_MXP, AR_XP, or AR_XPE card can be configured as a low-rate MXPP_MR card by adhering to the following provisioning rules:
1. N:2 muxponder must be created, where N varies from client ports 2 to 6.
2. Only ports 5 and 6 or 7 and 8, or both can be configured as trunk port.
3. Ports 1 to 8 can be configured as client ports, if ports are not configured as a trunk ports and are not part of another muxponder.
Splitter protection is automatically created between ports 5 and 6 or 7 and 8.
On the AR_XPE card, 1GE or 1G FC payload cannot be configured with other payloads. When a 1GE or 1GFC payload is configured on a port of MXPP_MR (low rate) mode, then only 1GE or 1GFC payload can be configured on the other ports.
Figure 11-35 Low-Rate MXPP_MR Card Operating Mode Configuration
- High Rate—A maximum of one MXPP_MR configuration can be provisioned on a AR_XP or AR_XPE card (Figure 11-36). Any client payload can be added or deleted, if the trunk bandwidth supports the new payload without impacting the traffic on the existing services.
The AR_XP or AR_XPE card can be configured as a high-rate MXPP_MR card by adhering to the following provisioning rules:
1. N:2 muxponder must be created, where N varies from client ports 2 to 8.
2. Only ports 9 and 10 can be configured as trunk ports.
3. Ports 1 to 8 can be configured as client ports.
Splitter protection is automatically created between ports 9 and 10. Port 10 will be the protected trunk port for port 9.
On the AR_XPE card, when you create a OCHCC circuit using 1GE or 1GFC payload, only ODU0 mapping is supported and timeslot mapping is not supported. When a OCHCC circuit is created on a particular ODU1 timeslot with payloads using timeslot mapping, OCHCC circuits cannot be created on payloads using ODU0 mapping, but can be created on the other ODU1 timeslot.
Figure 11-36 High-Rate MXPP_MR Card Operating Mode Configuration
MXP-4x2.5-10G (OC48/OTU1 Unprotected Muxponder)
The AR_MXP, AR_XP, or AR_XPE card can be configured as a high-rate MXP-4x2.5-10G card mode. Only one MXP-4x2.5-10G configuration can be provisioned on an AR_MXP card and a maximum of two on a AR_XP or AR_XPE card (Figure 11-37).
The AR_MXP, AR_XP, or AR_XPE card can be provisioned as MXP-4x2.5-10G card by adhering to the following provisioning rules:
1. The allowed port pairs are 1-2-3-4-9 or 5-6-7-8-10, or both.
2. Ports 9 and 10 can be configured as trunk ports.
3. Ports 1-2-3-4 or 5-6-7-8 can be configured as client ports.
Figure 11-37 High-Rate MXP-4x2.5-10G Card Operating Mode Configuration
MXPP-4x2.5-10G (OC48/OTU1 Protected Muxponder)
The AR_XP or AR_XPE card can be configured as a high-rate MXPP-4x2.5-10G card mode. Only one MXPP-4x2.5-10G configuration can be provisioned on a AR_XP or AR_XPE card (Figure 11-38).
The AR_XP or AR_XPE card can be configured as MXPP-4x2.5-10G card by adhering to the following provisioning rules:
1. Four SFP ports and two XFP ports must be configured. The allowed port pair is 1-2-3-4-9-10 or 5-6-7-8-9-10, or both.
2. Only ports 9 and 10 can be configured as trunk ports.
3. Ports 1-2-3-4 or 5-6-7-8 can be configured as client ports.
Splitter protection is automatically created between ports 9 and 10. Port 10 will be the protected trunk port for port 9.
Figure 11-38 High-Rate MXPP-4x2.5-10G Card Operating Mode Configuration
RGN (OTU1/OTU2 Regenerator)
The AR_MXP, AR_XP, or AR_XPE card can be configured as a low-rate or high-rate RGN card mode.
- Low Rate—A maximum of four RGN configurations can be provisioned on a single AR_MXP, AR_XP, or AR_XPE card (Figure 11-39). The AR_MXP, AR_XP, or AR_XPE card can be configured as a low-rate RGN card by adhering to the following provisioning rules:
1. The allowed port pairs are 1-2, 3-4, 5-6, 7-8 or 1-5, 2-6, 3-7, 4-8.
Figure 11-39 Low-Rate RGN Card Operating Mode Configuration
- High Rate—Only one RGN configuration can be provisioned on a AR_MXP, AR_XP, or AR_XPE card (Figure 11-40). The AR_MXP, AR_XP, or AR_XPE card can be configured as a high rate RGN card by adhering to the following provisioning rules:
1. The allowed port pairs are 9-10.
Figure 11-40 High-Rate RGN Card Operating Mode Configuration
The 10 GE over OTU2e/OTU1e signal with disabled FEC, standard FEC, I.4 or I.7 EFEC mode can be regenerated. The ODU transparency can either be Transparent Standard Use or Cisco Extended Use.
Note Payload PMs are not supported in this operating mode.
MXP-VD-10G (Video Muxponder)
The AR_XP or AR_XPE card can be configured as a high-rate MXP-VD-10G card mode. A maximum of two MXP-VD-10G configurations can be provisioned on a AR_XP or AR_XPE card (Figure 11-41).
The AR_XP or AR_XPE card can be configured as MXP-VD-10G card by adhering to the following provisioning rules:
1. The allowed port pairs are 1-2-3-9 or 5-6-7-10.
2. Only ports 9 and 10 can be configured as trunk ports.
3. Ports 1-2-3 and 5-6-7 can be configured as client ports.
Figure 11-41 High-Rate MXP-VD-10G Card Operating Mode Configuration
11.20.4 Scenarios of Different Operational mode Configurations on a AR_MXP, AR_XP, or AR_XPE Card
The following section provides a few sample scenarios of different operational modes that can be configured on an AR_MXP, AR_XP, or AR_XPE card:
Scenario 1
In this example (Figure 11-43), the following three operational modes are configured on the AR_MXP card:
Scenario 2
In this example (Figure 11-43), the following four operational modes are configured on the AR_XP or AR_XPE card:
- Low-rate TXP_MR (Cl=1;Tr=2)
- 8G FC TXP (Cl=9;Tr=10)
- Low-rate MR_MXP (Cl=4;TR=7,8)
- Low-rate MR_MXP (Cl=3,6;TR=5)
Scenario 3
In this example (Figure 11-44), the following two operational modes are configured on the AR_XP card:
Scenario 4
In this example (Figure 11-45), the following three operational modes are configured on the AR_XP or AR_XPE card:
Scenario 5
In this example (Figure 11-46), the following two operational modes are configured on the AR_XP or AR_XPE card:
11.20.5 AR_MXP, AR_XP, and AR_XPE Functions and Features
The AR_MXP, AR_XP, and AR_XPE cards have the following functions and features:
- Client Interface—Client Interface
- DWDM Interface—DWDM Interface
- DWDM Trunk Interface—DWDM Trunk Interface
- Enhanced FEC (E-FEC) Feature—FEC
- Timing Synchronization—Timing Synchronization
- Y-Cable Protection—Y-Cable Protection
- Jitter Considerations—Jitter Considerations
- Card level indicators—Table G-1
- Port level indicators—Table G-9
11.21 100G-LC-C,10x10G-LC, and CFP-LC Cards
11.21.1 100G-LC-C Card
The 100G-LC-C card is a tunable DWDM trunk card, which simplifies the integration and transport of 100 Gigabit Ethernet and OTU-4 interfaces and services into enterprises or service provider optical networks. The 100G-LC-C card is supported on Cisco ONS 15454 M2 and Cisco ONS 15454 M6 platforms.
The 100G-LC-C card transports 100 Gigabit Ethernet LAN-PHY and Optical Transport Network (OTN) Optical Transport Unit Level 4 (OTU4) over a 50-GHz spaced, 50-GHz stabilized, ITU-compliant wavelength. The card has a pluggable client interface that is used to provide transponder capabilities, mapping the client signal to a single DWDM line interface. The client port supports a standard CXP format pluggable compliant with 100G-BASE-SR10 LAN PHY or OTU4 equivalent interface.
The card is tunable on 96 wavelength channels spaced at 50-GHz over the entire C-band. The card provides advanced capabilities necessary to deliver 100-Gbps services, which includes protocol transparency, wavelength tunability, flow-through timing, management and performance monitoring capabilities.
The digital wrapper function (ITU-T G.709-compliant) formats the DWDM wavelength so that it can be used to set up GCCs for data communications, enable FEC, or facilitate performance monitoring. The 100G-LC-C card works with the OTN devices defined in ITU-T G.709.
The trunk ports on the 100G-LC-C card support the Ultra Forward Error Correction (UFEC) standard G.975.1 (sub-clause I.7) with 20% overhead. The UFEC provides an estimated gain between 0.5 dB to 1 dB for each span on the trunk interfaces with a resultant extension of the transmission range on these interfaces. The UFEC leverages on two orthogonally concatenated block code (BCH) algorithm super FEC codes. The constructed code is iteratively decoded to rebuild the original frame.
11.21.1.1 Benefits
The 100G-LC-C card provide the following benefits:
- Provides 100 Gbps wavelengths transport over fully uncompensated networks, with more than 2,500 km of unregenerated optical links.
- Enables 100-Gbps transport over very high Polarization Mode Dispersion (PMD).
- Improves overall system density of up to 100 Gbps per slot, which is five times greater than what can be achieved with 40 Gbps units.
- Provides a 100 G DWDM trunk interface that supports up to 70000 ps/nm of CD robustness.
- Enables configuration of the CD dispersion tolerance to 50000 ps/nm and 30000 ps/nm to reduce power consumption.
The card supports the following client signal types:
- 100 Gigabit Ethernet and OTU4
- OTU4 from BP OTL4.10 (interconnect with 100G-LC-C and CFP client)
- 100 Gigabit Ethernet from BP CAUI (interconnect with CFP client)
- 3 x OTU3e(255/227) from BP OTL3.4 (interconnect with 10 x10G client)
- 2 x OTU3 from BP OTL3.4 (interconnect with CFP client)
- 2 x 40 Gigabit Ethernet from BP XLAUI (interconnect with CFP client)
11.21.1.2 Key Features
The key features of 100G-LC-C card are listed in the “Key Features of 100G-LC-C, 10x10G-LC, and CFP-LC Cards” section.
11.21.1.4 100G-LC-C Block Diagram
For information on safety labels for the cards, see the “Class 1M Laser Product Cards” section.
The 100G-LC-C card is a single-slot card and can be installed in Slot 2 to Slot 7 in the Cisco ONS 15454 M6 chassis and Slot 2 and Slot 3 in the Cisco ONS 15454 M2 chassis. The card has one DWDM port and one CXP port.
The 100G-LC-C card interoperates with 10x10G-LC and CFP-LC cards through an ONS 15454 M6 or ONS 15454 M2 backplane.
Up to six 100G-LC-C cards can be installed per ONS 15454 M6 shelf assembly, supporting up to 42 100-Gbps interfaces per 42-rack units (RU) bay frame. It is possible to place up to two 100 G TXPs, one 100 G Regen, or one 100 G MXP in an ONS 15454 M2 shelf.
Note The fan-tray assembly 15454-M6-FTA2 (for the M6 chassis) or 15454-M2-FTA2 (for the M2 chassis) must be installed in the shelf where a 100G-LC-C card is installed. When an ONS-SC+-10G-C pluggable is used along with the 10x10G-LC card, the maximum operating temperature of the shelf must not exceed 50 degrees Celsius.
11.21.1.5 Operating Modes for 100G-LC-C Card
The 100G-LC-C card supports the following operating modes:
Each operating mode can be configured using the specific set of cards and client payloads. Table 11-37 describes how each mode can be configured, the supported payloads, and the valid port pair for a specific operating mode.
11.21.1.5.1 TXP-100G (Standalone 100GE Transponder)
The 100G-LC-C card can be configured as a standalone 100 Gigabit Ethernet transponder. The 100 Gigabit Ethernet traffic is supported on the CXP and coherent optical trunk. The 100 Gigabit Ethernet or OTU4 payload traffic is routed from the CXP to the optical trunk, passing through the T100 framer and vice versa.
The supported client signals in this mode are 100 Gigabit Ethernet LAN-PHY or OTU4 data rates.
11.21.1.5.2 RGN-100G (100G Regenerator)
The 100G-LC-C card can be configured as a regenerator. Two 100G-LC-C cards can be connected to work in a back-to-back mode connecting through the Cisco ONS 15454 M6 or Cisco ONS 15454 M2 backplane in the same shelf. The allowed port pairs are 2-3, 4-5, or 6-7.
The client signals supported are 100 Gigabit Ethernet or OTU4. Regeneration is performed leveraging on the OTU4 backplane interconnection supported by the Cisco ONS 15454 M6 or Cisco ONS 15454 M2 chassis; OTU4 overhead is terminated, allowing ODU4 to transparently pass through. GCC0 is terminated, while GCC1 and GCC2 are allowed to pass through.
The CXP client is not required because communication between the two cards acting as a regeneration group is supported through the chassis backplane.
11.21.2 10x10G-LC Card
The 10x10G-LC card is a DWDM client card, which simplifies the integration and transport of 10 Gigabit Ethernet interfaces and services into enterprises or service provider optical networks. The 10x10G-LC card is supported on ONS 15454 M2 and ONS 15454 M6 platforms. The 10x10G-LC card provide 10 Gbps services to support 10x10G-LC card.
The 10x10G-LC card supports the following signal types:
- OC-192/STM-64 (9.95328 Gbps)
- 10 Gigabit Ethernet LAN PHY (10.3125 Gbps)
- 10 G FC (10.518 Gbps)
- 8 G FC
- OTU-2
- G.709 overclocked to transport 10 Gigabit Ethernet as defined by ITU-T G. Sup43 Clause 7.1 (11.0957 Gbps)
The digital wrapper function (ITU-T G.709-compliant) formats the DWDM wavelength so that it can be used to set up GCCs for data communications, enable FEC, or facilitate performance monitoring. The 10x10G-LC card works with the OTN devices defined in ITU-T G.709.
11.21.2.1 Key Features
The key features of 10x10G-LC card are listed in Key Features of 100G-LC-C, 10x10G-LC, and CFP-LC Cards.
11.21.2.3 10x10G-LC Block Diagram
For information on safety labels for the cards, see the “Class 1M Laser Product Cards” section.
The 10x10G-LC card is a single-slot card and can be installed in Slot 2 to Slot 7 in the Cisco ONS 15454 M6 chassis and Slot 2 and Slot 3 in the Cisco ONS 15454 M2 chassis. The 10x10G-LC card consists of a 10-port SFP+ based (gray, colored, coarse wavelength division multiplexing ([CWDM], and DWDM optics available) and one 100 G CXP-based port.
The 10x10G-LC card interoperates with 100G-LC -C cards through an ONS 15454 M6 or ONS 15454 M2 backplane.
Note The fan-tray assembly 15454-M6-FTA2 (for the M6 chassis) or 15454-M2-FTA2 (for the M2 chassis) must be installed in the shelf where a 10x10G-LC card is installed. When an ONS-SC+-10G-C pluggable is used along with the 10x10G-LC card, the maximum operating temperature of the shelf must not exceed 50 degrees Celsius.
11.21.2.4 Operating Modes for 10x10G-LC Card
The 10x10G-LC card supports the following operating modes:
- MXP-10x10G (10x10G Muxponder)
- RGN-10G (5x10G Regenerator)/TXP-10G (5x10G Transponder)
- Low Latency
- Fanout-10X10G
Each operating mode can be configured using the specific set of cards and client payloads. Table 11-37 describes how each mode can be configured, the supported payloads, and the valid port pair for a specific operating mode.
11.21.2.4.1 MXP-10x10G (10x10G Muxponder)
The 10x10G-LC card can be configured as a 10x10G muxponder. It can be connected with a 100G-LC-C card to support 10-port 10 G muxponder capabilities. The 100G-LC-C card can be connected through the Cisco ONS 15454 M6 or Cisco ONS 15454 M2 backplane (no client CXP required) with the 10x10G-LC card to provide OTN multiplexing of the 10 G data streams into a single 100 G DWDM OTU4 wavelength. The allowed port pairs are 2-3, 4-5, or 6-7.
The 10x10G muxponder mode supports client signals that are a mix and combination of any 10 Gigabit Ethernet LAN-PHY, OC-192, STM-64, 10 G FC/FICON, 8 G FC/FICON, or OTU2 data rates.
11.21.2.4.2 RGN-10G (5x10G Regenerator)/TXP-10G (5x10G Transponder)
The 10x10G-LC card works as a standalone supporting the multitransponder functionality. The 10 Gbps SFP+ ports should be paired to provide the 10 G transponder functionality for each of the couple of ports. By using the grey optics SFP+ to provide the client equipment connectivity and DWDM SFP+ on the WDM side, up to five 10 G transponders are supported by a single 10x10G-LC card. Up to 6 10x10G-LC cards are supported on the Cisco ONS 15454 M6 chassis allowing for 30 10 Gbps transponders in a single shelf.
All the ports can be equipped with or without the G.709 Digital Wrapper function providing wide flexibility in terms of the supported services.
As the client and trunk ports are completely independent, it is also possible to equip both the SFP+ of the same pair of ports with the DWDM SFP+ thereby allowing them to function as a WDM regenerator. The CXP pluggable is unused in this configuration.
Each of the SFP+ ports can be provisioned as a client or trunk. When one port is selected as a trunk, the other port of the pair is automatically selected as the client port. The allowed port pairs are 1-2, 3-4, 5-6, 7-8, or 9-10.
For RGN-10G mode, both the ports are trunk ports.
It is not a constraint to provision 5 couple of TXP-10G mode or 5 couple of RGN-10G mode. A mix of TXP-10G and RGN-10G modes can be configured. For example, couple 1-2 and 5-6 can be configured as a TXP-10G mode and the remaining as the RGN-10G mode.
Table 11-36 shows the supported payload mapping on a particular port and its corresponding peer.
11.21.2.4.3 Low Latency
The 10x10G-LC card can be configured in the low latency mode. This configuration minimizes the time spent by the signal to cross the card during the regeneration process. Adjacent SFP ports must be selected while provisioning this mode although each SFP port functions as a unidirectional regenerator. Both ports are trunk ports. The allowed ports are 1-2, 3-4, 5-6, 7-8, or 9-10. A mix of TXP-10G, RGN-10G, and low latency modes can be configured.
The low latency mode supports 10GE and 10G FC data rates. The same payload must be provisioned on both the SFP ports involved in this operating mode. GCC cannot be provisioned on the ports used in the low latency mode. The low latency mode does not support terminal and facility loopback.
11.21.2.4.4 Fanout-10X10G
The 10x10G-LC card can be configured in the fanout-10x10G mode.The fanout configuration configures the CXP side as the client and SFP side as the trunk. This configuration functions as ten independent transponders. The CXP lanes are managed independently and the payload for each CXP-lane-SPF+ pair is independent from the other pairs.
The fanout configuration provides the following mapping for the port pairs:
- CXP lane 2-SFP1
- CXP lane 3-SFP2
- CXP lane 4-SFP3
- CXP lane 5-SFP4
- CXP lane 6-SFP5
- CXP lane 7-SFP6
- CXP lane 8-SFP7
- CXP lane 9-SFP8
- CXP lane 10-SFP9
- CXP lane 11-SFP10
Note CXP lane 1 and CXP lane 12 are not supported in this configuration.
The fanout configuration supports the following payload types and mapping modes:
11.21.3 CFP-LC Card
The CFP-LC card is a client card, which simplifies the integration and transport of 40 GE and 100 GE interfaces and services into enterprises or service provider optical networks. The CFP-LC card is supported on the Cisco ONS 15454 M6 platform. The CFP-LC card provides 100 Gbps services to support 100 G DWDM wavelengths generated by the 100G-LC-C card. The traffic coming from CFP interfaces is switched to the trunk port through a cross-switch.
The CFP-LC card supports the following signal types:
Client ports can be equipped with a large variety of CFP pluggables.
The Digital Wrapper function (ITU-T G.709-compliant) formats the DWDM wavelength so that it can be used to set up GCCs for data communications, enable FEC, or facilitate performance monitoring.
11.21.3.1 Key Features
The key features of CFP-LC card are listed in Key Features of 100G-LC-C, 10x10G-LC, and CFP-LC Cards.
11.21.3.3 Block Diagram
For information on safety labels for the cards, see the “Class 1M Laser Product Cards” section.
The CFP-LC card is a double-slot card and can be installed in Slot 3 or Slot 5 in the Cisco ONS 15454 M6 chassis, and the 100G-LC-C peers cards must be placed in the adjacent slots (2 and 5 or 4 and 7). If the card is plugged in one of the unsupported slots or in a Cisco ONS 15454 M2 chassis, the system raises an EQPT::MEA (Mismatch of Equipment Alarm) notification. Up to two CFP-LC cards can be installed per ONS 15454 M6 shelf assembly, supporting up to 28x 40-Gbps or 14x 100 Gbps interfaces per 42-rack units (RU) bay frame.
The CFP-LC card is equipped with two 100 G CFP pluggable modules and a cross-bar embedded switch module. The CFP-LC card provides two backplane interfaces (working both at 100 Gb or 40 Gb) that are suitable for the cross-switch application on the incoming CFP signals. The CFP-LC card can be configured to send all the client CFP services towards the backplane to be connected with up to two 100G-LC-C cards placed in the two adjacent slots (upper and lower) of the Cisco ONS 15454 M6 chassis in order to provide two 100 G transponders configurations.
Note The fan-tray assembly 15454-M6-FTA2 (for the M6 chassis) must be installed in the shelf where a CFP-LC card is installed.
11.21.3.4 Operating Modes for CFP-LC Card
The CFP-LC card supports the following operating modes:
Each operating mode can be configured using the specific set of cards and client payloads. Table 11-37 describes how each mode can be configured, the supported payloads, and the valid port pair for a specific operating mode.
11.21.3.4.1 2x40G Muxponder
The CFP-LC card can be configured as a 2-port 40 G muxponder. It can be connected with the 100G-LC-C card to support 2-port 40 G muxponder capabilities. The 100G-LC card can be connected through the Cisco ONS 15454 M6 backplane (no client CXP required) with the CFP-LC card to provide OTN multiplexing of the 40 G data streams into a single 100 G WDM OTU4 wavelength.
The 2x40G muxponder mode supports client signals that are a mix and combination of any 40 Gigabit Ethernet LAN-PHY or OTU3 data rates.
11.21.3.4.2 CFP-TXP (100G Transponder)
The CFP-LC card can be configured as a 100 G transponder. It can be connected with the 100G-LC-C card to support 100GE-BASE-LR4 client interface for the 100-Gbps transponder capabilities. The 100G CXP pluggable available on the 100G-LC card supports only 100GE-BASE-SR10 client interface, while the 100GE-BASE-LR4 is supported using a CFP form factor only.
The CFP-LC card can be connected through the Cisco ONS 15454 M6 backplane with up to two 100G-LC cards placed in the upper or in the lower slot of the same shelf to provide the equivalent functionalities of two 100 G LR4 transponders, leveraging on CFP pluggables as client interface.
11.21.3.5 Key Features of 100G-LC-C, 10x10G-LC, and CFP-LC Cards
The 100G-LC-C, 10x10G-LC, and CFP-LC cards support the following key features:
- Operating Modes—The 100G-LC-C, 10x10G-LC, and CFP-LC cards can be configured into multiple operating modes. The cards can be equipped with pluggables for client and trunk options, and offer a large variety of configurations. When you configure the 100G-LC-C, 10x10G-LC, or CFP-LC card into multiple operational modes, make sure that the following tasks are completed:
– The card must be preprovisioned and the modes must be configured. None of the modes are provisioned on the card by default. All operating modes are created on the card level. These are card-specific provisioning, which decides the behavior of a particular card.
– Depending on the card mode selected, the supported payload for that particular card mode must be provisioned on the PPMs.
– The payloads can be provisioned after configuring the operational mode on the card.
Each operating mode can be configured using the specific set of cards and client payloads. Table 11-37 describes how each mode can be configured, the supported payloads, and the valid port pair for a specific operating mode.
OC192/STM-64, 10GE-LAN Phy, 10GE-WAN Phy (using OC192), OTU2, OTU2e, 8G FC, 10G FC, FICON |
|||||
For operating modes of the respective cards, see the “Operating Modes for 100G-LC-C Card” section, “Operating Modes for 10x10G-LC Card” section, and “Operating Modes for CFP-LC Card” section.
- Protocol Transparency—The 100G-LC-C card delivers any 100 Gbps services for cost-effective, point-to-point networking for the Cisco ONS 15454 platform. Table 11-38 shows the transponder client configurations and mapping for 100G-LC-C card. The 10x10G-LC card delivers any 10 Gbps services for cost-effective, point-to-point networking for the Cisco ONS 15454 platform. In case of 100 G muxponder clients that are mapped into OTU4 DWDM wavelength, Table 11-39 shows the transponder client configurations and mapping for the 10x10G-LC card. Table 11-40 shows the transponder client configurations and mapping for the CFP-LC card.
- Flow-Through Timing—The 100G-LC-C, 10x10G-LC, and CFP-LC cards allow the timing to flow through from client to line optical interface. The received timing from client interface is used to time the line transmitter interface. This flow-through timing allows multiple cards to be placed in the same shelf but be fully independently timed, independent of the NE timing.
- Far-End Laser Control (FELC)—FELC is supported on the 100G-LC-C, 10x10G-LC, and CFP-LC cards. For more information on FELC, see the “Far-End Laser Control” section.
-
Performance Monitoring—The 100-Gbps DWDM trunk provides support for both transparent and non-transparent signal transport performance monitoring. The Digital Wrapper channel is monitored according to G.709 (OTN) and G.8021 standards. Performance Monitoring of optical parameters on the client and DWDM line interface include Loss Of Signal (LOS), Laser Bias Current, Transmit Optical Power, and Receive Optical Power. Calculation and accumulation of the performance monitoring data are supported in 15-minute and 24-hour intervals as per G.7710. Physical system parameter measured at the wavelength level like Mean PMD, accumulated Chromatic Dispersion, or Received OSNR are also included in the set of performance monitoring parameters. These can greatly simplify troubleshooting operations and enhance the set of data which can be collected directly from the equipment.
The performance monitoring for the CFP-LC card takes into account that the two CFP-LC cards are an host board supporting CFP client equipment, while the digital monitoring if the incoming client is implemented on the 100G-LC-C card. There is a virtual port connection that displays the Digital Wrapper monitoring according to G.709 (OTN) as well as the RMON for Ethernet signals, while the optical performance monitoring is directly available on the two CFP-LC cards. Calculation and accumulation of the performance monitoring data are supported in 15-minute and 24-hour intervals as per G.7710. - Loopback—The terminal, facility, or backplane loopback can be provisioned on all the ports of the 100G-LC-C and 10x10G-LC cards configured in any operating mode except for the low latency mode. The backplane facility loopback cannot be configured on the 10x10G -LC card configured in the MXP-10x10G mode. Loopback can be provisioned only when the port is in OOS-MT state. A new port cannot be provisioned when the backplane loopback is configured on the 10x10G-LC card. For the CFP-LC card configured in the CFP-TXP or CFP-MXP mode, the facility or terminal loopback can be configured on the backplane of the peer 100G-LC-C card.
- Generalized Multiprotocol Label Switching — The Generalized Multiprotocol Label Switching (GMPLS) circuit can be created on the 100G-LC-C and 10 x10G-LC cards. However, this circuit cannot be created when the card is in 100 G regenerator mode. When the card is configured in MXP-10 x 10G card mode, only GMPLS Optical Channel Network Connections (OCHNCs) can be created.
- Automatic Laser Shutdown (ALS) can be configured on all the ports. ALS is supported only on the ports that are configured with OC192/STM64, OTU2, and OTU4 payloads.
- GCC channels—can be provisioned on the OTU2 client and trunk ports of the 10 x10G-LC card, OTU3 port (virtual port on the peer 100G-LC-C card) of the CFP-LC card, and the OTU4 client and trunk ports of the 100G-LC-C card.
- 50 ms switching with PSM—A protection switch time of less than 50 ms can be achieved with two CFP-LC cards on their 100GE client ports using a PSM card that is configured in the standalone mode. The client ports of the CFP-LC cards are connected to the working and protect ports of the PSM card. An OCHCC circuit must be created between the two client ports.
- The optical TX power can be set to a value from -10.0 to +0.25 dBm on the trunk port of the 100G-LC-C card to enable it to interoperate with ASR 9000 series routers and Cisco CRS-3 routers. The TX shutdown feature allows you to turn off the TX power on the 100G-LC-C cards when the trunk port in out of service or in maintenance. The 100G-LC-C cards have the ability to receive optical signals even when the TX power is turned off.
- Licensing—The 100G-LC-C card adds the capability to cost-effectively transport the 10 G service offering as a Pay-As-You-Grow licensing model for the 10 x 10G muxponder. A licensed card works in conjunction with a licensed 10 x10G line card. The two cards that can only work in this configuration and in combination of the other licensed pair card offers a price-sensitive solution with the ability to equip one 10 G service. For more information on licensing, see the Cisco ONS 15454 DWDM Licensing Configuration Guide .
Note Licensing is not supported on the CFP-LC card.
11.21.3.6 Functions and Features
The cards have the following functions and features:
- Enhanced FEC (E-FEC) Feature—FEC
- Timing Synchronization—Timing Synchronization
- Jitter Considerations—Jitter Considerations
- Card level indicators—Table G-1
- Port level indicators—Table G-12
11.22 Related Procedures for 100G-LC-C, 10x10G-LC, and CFP-LC Cards
- “G235 Provision an Operating Mode on the 100G-LC-C, 10x10G-LC, or CFP-LC Card” section.
- “G236 Modify the 100G-LC-C, 10x10G-LC, or CFP-LC Card Line Settings and PM Parameter Thresholds” section.
- NTP-G75 Monitor Transponder and Muxponder Performance.
11.23 WSE Card
The Wire Speed Encryption (WSE) card is an optical line card that provides encryption capability, at the OTN layer, to the Cisco ONS 15454 M2 and Cisco ONS 15454 M6 platforms. This card provides confidentiality of the data, which is sent over a fiber optic communication channel, using Next Generation Cryptography. In addition to providing encryption, this card also provides integrated transponder functionality.
The WSE card is FIPS 140-2 compliant, in accordance with the U.S. National Institute of Standards (NIST), and operates in FIPS mode, level 2 compliance. The Federal Information Processing Standard (FIPS) Publication 140-2, is a U.S. and Canadian government certification standard that defines requirements that cryptographic module must follow. For more information about the FIPS 140-2, see http://csrc.nist.gov/cryptval/ .
The ONS 15454 M2 and ONS 15454 M6 nodes are Common Criteria (CC) compliant. The CC certification from National Institute of Standards and Technology (NIST) using the Network Device Protection Profile (NDPP) ensures the node is accessed, managed, monitored and provisioned in a highly secure manner. The CC applies only to ONS 15454 M2 and ONS 15454 M6 stand-alone nodes with TNC/TSC/TNC-E/TSC-E cards as the node controller.
When you enable FIPS and CC mode on the WSE card, the node runs certification self-tests at startup, integrity check on cryptographic modules, and then regenerates the keying materials. Based on the “FIPS and CC”mode configuration of the node, the WSE card operates either with FIPS compliant cryptographic module or with normal cryptographic module.
The WSE card supports these client signals:
- 10GE LAN PHY mapped to OTU2e
- OTU2
- OTU2e
- OTU1e
- OC-192/STM-64
- 10GE WAN
- 10GE LAN mapped to OTU2
- 8G FC/10G FC
The WSE card passes the client payload transparently.
Note When the WSE card is configured with OC-192/STM-64 payload, it does not interoperate with other line cards due to difference in payload mapping type; the payload mapping is Asynchronous Mapping (AMP) in WSE card and Bit Synchronous Mapping (BMP) in other line cards.
The WSE card does not support auto negotiation for SAN protocols (10GFC/8GFC). The WSE card supports only speed lock for SAN protocols.
The WSE card is tunable on 96 wavelength channels, spaced at 50-GHz over the entire C-band. The digital wrapper function (ITU-T G.709 compliant) formats the DWDM wavelength so that it can be used to set up GCCs for data communications, enable FEC, or facilitate PM. The WSE card works with the OTN devices defined in ITU-T G.709. The OTN client can be FEC, standard G.975 FEC, or disabled FEC.
Table 11-41 shows the input data rate for each client payload, and the encapsulation method.
11.23.1 Key Features
The WSE card supports these key features:
- Operating Modes—The WSE card can be configured into multiple operating modes. The card can be equipped with pluggables for client and trunk options, and offers a large variety of configurations. For more information about multiple operating modes, see Multiple Operating Modes.
- Security Features
– Secure Boot—This feature does a boot verification in hardware. It ensures that only authentic Cisco software boots up on the Cisco platform, and provides tamper and cloning resistance.
– Digital Image Signing—After the secure boot, the Digital Image Signing ensures that the software that runs on Cisco devices is authentic. This maintains the integrity of the image that is loaded on the WSE card.
– Key Exchange—Key exchange between authenticated peer cards happens over the GCC2 channel that is secured using Transport Layer Security (TLS). The Elliptic Curve Diffie Hellman Ephemeral (ECDHE) algorithm is used for key exchange.
– Confidentiality of Data—The WSE card protects against ciphertext manipulation and cut-and-paste attempts. AES algorithm in XTS mode of operation.
– Role Based Access Control—Access control is enforced to ensure that there is complete separation in managing the transport (provisioning) and the security functionalities. As a result, depending on the role assigned to a user, only certain operations can be performed by that user.
- Card Authentication—The Secure Unique Device Identification (SUDI) certificate that is formatted as an X.509 certificate and conforms to the IEEE 802.1 AR standard. It is signed using Cisco's Root Certificate Authority. This certificate carries a unique identifier used to authenticate the peer card as being a WSE card before the data is exchanged. Information cannot be exchanged with a card that is not authenticated.
- High Speed GCCs—The WSE card supports the provisioning of GCC channel on OTN (OTU2/OTU2e) enabled client and trunk ports. A maximum of ten GCC0 channels, on Cisco ONS 15454 M2 or Cisco ONS 15454 M6 shelf, can be created and a maximum of five for GCC2 Cisco ONS 15454 M2 or Cisco ONS 15454 M6 shelf can be created.
- OCH-trail Protection—Provides protection for the DWDM signals through external optical switch units (Protection Switch Module [PSM]).
- Y-cable protection: Supports Y-cable protection for 10GE and OC-192/STM-64 payloads. See “Y-Cable Protection” section for more detailed information.
- Licensing—A licensed version of the card provides a cost-effective solution for customers who do not need to encrypt data on all five streams from day one itself. The licensed WSE card provides single stream encryption as a base functionality. When an additional encrypted stream is required, you need to purchase a software ugrade license. Licensing is required for only security features. A WSE card without a license acts as for transponder. For more information on licensing, see the Cisco ONS 15454 DWDM Licensing Configuration Guide .
11.23.2 Faceplate Diagram
Figure 11-50 shows the WSE faceplate.
For information on safety labels for the cards, see the “Class 1M Laser Product Cards” section.
The WSE card is a single-slot card and can be installed in slots 2 to 7 in the Cisco ONS 15454 M6 chassis, or slots 2 or 3 in the Cisco ONS 15454 M2 chassis. The card has 10 SFP+ ports. The trunk and client ports are fixed. The trunk ports are 2, 4, 6, 8, and 10; the client ports are 1, 3, 5, 7, and 9. The trunk SFP+ can be grey or DWDM. The trunks include FEC and EFEC for longer reach. Depending on the traffic pattern, the WSE card provides per port flexibility.
Up to six WSE cards can be installed at each ONS 15454 M6 shelf assembly, supporting up to 30 encrypted streams in a 6-rack unit (RU) bay frame. Up to two WSE cards can be installed at each ONS 15454 M2 shelf assembly, supporting up to 10 encrypted streams in a 2-rack unit (RU) bay frame. It is possible to aggregate the wavelength required witht 40G and 100G cards in the same chassis.
11.23.3 WSE workflow diagram
Figure 11-51 shows the workflow diagram of the WSE card. The diagram provides information on the tasks required to configure the WSE card.
Figure 11-51 WSE Card Workflow Diagram
11.23.4 Multiple Operating Modes
A single WSE card can be configured into multiple operating modes. The criteria for selecting a particular operating mode are defined by the network level design. CTP helps you to choose the appropriate operating mode. When you configure the WSE card into multiple operating modes, make sure that these tasks are completed:
– The PPMs must be configured on the card, and then the operating modes. None of the modes are provisioned on the card by default. All operating modes are created on a per port basis. This is card-specific provisioning, which decides the behavior of a particular card.
– Depending on the card mode selected, the supported payload for that particular card mode must be provisioned on the PPMs.
The WSE card supports these operating modes:
A mix of TXP-10G and RGN-10G modes can be configured on the WSE card.
11.23.4.1 TXP-10G
A maximum of five TXP-10G configurations can be provisioned on a single WSE card. When the card is configured in this mode, these features are supported:
OTN cannot be disabled on the trunk port.
Table 11-42 shows the supported payload mapping when a card is configured in TXP-10G mode.
11.23.4.2 RGN-10G
In the RGN-10G mode, the card behaves as a standard regenerator with DWDM SFP+ on both the client and trunk ports. The card supports OTU2e regeneration on all client and trunk pairs. When the WSE card is configured in this mode, card authentication and payload encryption features are not supported.
11.23.5 Card Authentication
The WSE cards provide TLS 1.2 based card-to-card authentication per port. An authentication failure on one trunk port does not affect the traffic on any other trunk port. The card authentication must be enabled to configure encryption on the card.
Cisco Signed certificates are installed on the WSE card by default. These certificates are exchanged between the cards during card authentication.
All ports are re-authenticated upon a soft-reset of the card.
In case of TLS or SSL authentication failure, the KEY_EX_FAIL alarm is raised on the particular trunk port.
11.23.6 Key Management
A single key, called a master key, is exchanged for each TLS session. It is exchanged using an asymmetric key algorithm (Elliptic Curve Diffie Hellman). The master key is used to derive a set of symmetric keys for payload encryption.
The user can change the master key at anytime from CTC, which initiates another DH exchange between the sender and the receiver. The user can also specify the time when the master key is periodically reset.
The keys used for encryption of data are never stored in plaintext on the card. All keys are deleted when the card reboots or is removed from the chassis. The key changes do not affect the traffic.
11.23.7 Payload Encryption
The payload on each port can be encrypted independent of the other streams. NIST approved Advanced Encryption Standard (AES) AES-256, a symmetric key cryptographic algorithm in XTS mode of operation, is used to encrypt the OTN payload. The payload encryption needs to be enabled at both source and destination trunk ports; otheriwse, it is traffic affecting.
11.23.8 AES Secure Packet
The concept of a packet does not exist within OTN; however, packet-based traffic is necessary for encryption using XTS-AES algorithm. A single OTN frame cannot be tagged with the necessary Encapsulating Security Payload (ESP) header, which carry the information necessary for encryption and decryption of payloads. The ESP header and trailer require a total of 32 bytes within the OTN overhead.
The AES secure packet for each port can be made up of four or eight OTN frames. In CTC, the user can choose from these two options for transporting the ESP header and trailer:
- Four OTN frame-based AES secure packet—The four OTN frame-based AES secure packet transports four ESP header and four ESP trailer bytes within each OTN frame. In the four OTN frame-based AES secure packet, eight overhead bytes are utilized in each OTN frame in order to transport all 32 bytes of ESP header and trailer within a single AES secure packet. Each location is four bytes wide, therefore two locations from each OTN frame are utilized, one for the ESP header and one for the ESP trailer.
- Eight OTN frame-based AES secure packet— The eight OTN frame-based AES secure packet transports two ESP header and two ESP trailer bytes within each OTN frame. In the eight OTN frame-based AES secure packet, four overhead bytes are utilized in each OTN frame in order to transport all 32 bytes of ESP header and trailer within a single AES secure packet. Each location is four bytes wide; therefore, only one location from each OTN is utilized. Within the selected location, two bytes are used for the ESP header, and two bytes for the ESP trailer.
Pseudo Random Binary Sequence (PRBS) testing is used to ensure that the selected overhead bytes can be used to transport the ESP header and trailer safely. Both the transmitting node and receiving node must be aware that PRBS testing is taking place. Each node must also know which bytes are to be tested.
11.23.9.1 Scenario 1: Traffic in a Stacked Topology
Consider an example where the WSE cards are connected in a stacked topology:
Client:WSE1:Trunk===Trunk:WSE2:Client===Client:WSE3:Trunk===Trunk:WSE4:Client
where WSE:Trunk represents OTU2e payload and WSE:Client represents 10GE signal.
In this scenario, card-to-card authentication and payload encryption are enabled on all the trunk ports, and loopback is not configured.
In this stacked topology, the WSE2 and WSE3 client will report a synchronization loss since the keys are different, and an ODUk-AIS is raised on the trunk ports. The key is not exchanged between WSE1 and WSE2 cards, and WSE 3 and WSE4 cards. This creates a deadlock and the traffic does not recover.
11.23.9.2 Scenario 2: Traffic in a Far-end and Near-end Client Loopback
Consider an example where loopback is configured on the WSE cards:
TS(10GE): near-end WSE1(client):(trunk)=== far-end WSE2(trunk):(client loopback)
where the trunk represents OTU2e payload and client represents 10GE signal.
In WSE card, do not enable encryption with far-end or near-end client loopback as this results in synchronization loss at the client, and an ODUk-AIS is raised on the trunk port. The key is exchanged only after the ODUk-AIS on the trunk is cleared. This forms a deadlock and the traffic does not recover.
11.23.9.3 Scenario 3: Traffic After Enabling PRBS Ingress and Egress
In a scenario when WSE cards are connected in a point-to-point setup:
10GE(client)===OTU2e(trunk)----OTU2e(trunk)===10GE(client-loopback)
When PRBS Ingress and Egress are enabled at both ends of the setup, the traffic will go down.
The traffic may be down on enabling PRBS, but the traffic comes up after disabling PRBS.
11.23.10 Functions and Features
The cards have these functions and features:
- Enhanced FEC (E-FEC) Feature—FEC
- Timing Synchronization—Timing Synchronization
- Card level indicators—Table G-1
- Port level indicators—Table G-12
11.25 MLSE UT
The maximum likelihood sequence estimation (MLSE) based universal transponder (UT) modules are added to the TXP_MR_10EX_C, MXP_2.5G_10EX_C, and MXP_MR_10DMEX_C cards to support the error decorrelator functionality to enhance system performance.
11.25.1 Error Decorrelator
The MLSE feature uses the error decorrelator functionality to reduce the chromatic dispersion (CD) and polarization mode dispersion (PMD), thereby extending the transmission range on the trunk interface. You can enable or disable the error decorrelator functionality using CTC or TL1. The dispersion compensation unit (DCU) is also used to reduce CD and PMD. The MLSE-based UT module helps to reduce CD and PMD without the use of a DCU.
11.26 SFP, SFP+, XFP, CXP, and CFP Modules
Small Form-factor Pluggable (SFP), Enhanced Small-Form-factor Pluggable (SFP+), 10-Gbps SFP (XFP), CXP, and C Form-factor pluggable (CFP) modules are integrated fiber optic transceivers that provide high-speed serial links from a port or slot to the network. For more information on SFP, SFP+, XFP, CXP, and CFP modules and for a list of SFP, SFP+, XFP, CXP, and CFP modules supported by the transponder and muxponder cards, see the Installing the GBIC, SFP, SFP+, XFP, CXP, and CFP Optical Modules in Cisco ONS Platforms .
In CTC, SFP, SFP+, XFP, CXP, and CFP modules are called pluggable port modules (PPMs). To provision SFP, SFP+, XFP, CXP, or CFP module and change the line rate for multirate PPMs, see the DLP-G726 Preprovisioning a Multirate PPM task.
11.27 Procedures for Transponder and Muxponder Cards
The procedures described below explain how to provision transponder (TXP), muxponder (MXP), Xponder (GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE), and ADM-10G cards. The provisioning must be performed before you provision the dense wavelength division multiplexing (DWDM) network and create circuits.
11.27.1 Before You Begin
Before performing any of the following procedures, investigate all alarms and clear any trouble conditions. Refer to the Cisco ONS 15454 DWDM Troubleshooting Guide as necessary.
This section lists the chapter procedures (NTPs). Turn to a procedure for applicable tasks (DLPs).
1. G128 Manage Pluggable Port Modules—Complete this procedure to provision a multirate pluggable port module (PPM), provision or change the optical line rate of a PPM, or delete a PPM. PPMs provide the fiber interface to the TXP, MXP, and ADM-10G cards. With the exception of the TXP_MR_10G card, all TXPs, MXPs, and ADM-10G cards accept PPMs.
2. G33 Create a Y-Cable Protection Group—As needed, complete this procedure for TXP, MXP, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, or OTU2_XP cards that will be protected with Y-cable protection.
3. G199 Create a Splitter Protection Group for the OTU2_XP Card—As needed, complete this procedure to create a splitter protection group for an OTU2_XP card.
4. G198 Create 1+1 Protection for GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards—As needed, complete this procedure to create 1+1 protection for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards.
5. G98 Provision the 2.5G Multirate Transponder Card Line Settings and PM Parameter Thresholds—As needed, complete this procedure to change the transmission settings for TXP_MR_2.5G and TXPP_MR_2.5G cards.
6. G96 Provision the 10G Multirate Transponder Card Line Settings, PM Parameters, and Thresholds—As needed, complete this procedure to change the transmission settings for TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, and TXP_MR_10EX_C cards.
7. NTP-G292 Provision the 40G Multirate Transponder Card Line Settings, PM Parameters, and Thresholds, page 6-72—As needed, complete this procedure to change the transmission settings for 40E-TXP-C and 40ME-TXP-C cards.
8. G170 Provision the ADM-10G Card Peer Group, Ethernet Settings, Line Settings, PM Parameters, and Thresholds—As needed, complete this procedure to provision the transmission settings for ADM-10G cards.
9. G97 Modify the 4x2.5G Muxponder Card Line Settings and PM Parameter Thresholds—As needed, complete this procedure to change the transmission settings for MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, and MXP_2.5G_10EX_C cards.
10. G99 Modify the 2.5G Data Muxponder Card Line Settings and PM Parameter Thresholds—As needed, complete this procedure to change the transmission settings for MXP_MR_2.5G and MXPP_MR_2.5G cards.
11. G148 Modify the 10G Data Muxponder Card Line Settings and PM Parameter Thresholds—As needed, complete this procedure to change the transmission settings for MXP_MR_10DME_C, MXP_MR_10DME_L, and MXP_MR_10DMEX_C cards.
12. G293 Modify the 40G Muxponder Card Line Settings and PM Parameter Thresholds—As needed, complete this procedure to change the transmission settings for 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards.
13. G281 Manage the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Channel Group Settings—As needed, complete this procedure to change the channel group settings for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards.
14. G283 Manage the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card CFM Settings—As needed, complete this procedure to change the CFM settings for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards.
15. G285 Manage the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card EFM Settings—As needed, complete this procedure to change the EFM settings for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards.
16. G287 Manage the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card REP Settings—As needed, complete this procedure to change the REP settings for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards.
17. G165 Modify the GE_XP, 10GE_XP, GE_XPE, 10GE_XPE Cards Ethernet Parameters, Line Settings, and PM Thresholds—As needed, complete this procedure to change the transmission settings for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards.
18. G314 Add a GE_XP or 10GE_XP Card on a FAPS Ring—As needed, complete this procedure to add a GE_XP or 10GE_XP Card on a FAPS Ring.
19. G197 Provision the OTU2_XP Card Line Settings, PM Parameters, and Thresholds—As needed, complete this procedure to change the transmission settings for OTU2_XP cards.
20. G162 Change the ALS Maintenance Settings—As needed, complete this procedure to change the automatic laser shutdown settings for a TXP or MXP card.
21. G302 Configure Loopback on 100G-LC-C, 10x10G-LC, CFP-LC, and WSE Cards—As needed, complete this procedure to configure the loopback on the 100G-LC, 10x10G-LC, CFP-LC, or WSE card.
22. G299 Configure the Backplane Loopback on 100G-LC-C, 10x10G-LC, and CFP-LC Cards—As needed, complete this procedure to configure the backplane loopback on the 100G-LC or 10x10G-LC card.
23. G192 Force FPGA Update—As needed, complete this procedure to force an upgrade of the FPGA image on the MXP_MR_10DME_C, MXP_MR_10DME_L, and MXP_MR_10DMEX_C cards.
24. G196 Force FPGA Update When the Card is Part of a Protection Group—As needed, complete this procedure to force an upgrade of the FPGA image on the MXP_MR_10DME_C, MXP_MR_10DME_L, and MXP_MR_10DMEX_C cards when the card is part of a protection group.
25. G232 Enabling Error Decorrelator—As needed, complete this procedure to enable error decorrelator on a TXP_MR_10EX_C, MXP_2.5G_10EX_C, or MXP_MR_10DMEX_C card.
NTP-G128 Manage Pluggable Port Modules
Complete this procedure to provision a multirate PPM, provision the optical line rate of a multirate PPM, or delete a single-rate or multirate PPM. |
|
Note If a single-rate PPM is installed, the PPM screen will autoprovision and no further steps are necessary.
Note When you autoprovision a PPM, initial alarm and TCA defaults are supplied by Cisco Transport Controller (CTC) depending on your port and rate selections and the type of PPM. These default values can be changed after you install the PPM.
Note The hardware device that plugs into a TXP, MXP, AR_MXP, AR_XP, AR_XPE, 100G-LC-C, 10x10G-LC, CFP-LC, WSE, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, ADM-10G, or OTU2_XP card faceplate to provide a fiber interface to the card is called a Small Form-factor Pluggable (SFP, SFP+, XFP, or CXP) or C Form-factor pluggable (CFP). In CTC, SFPs, XFPs, CXPs, and CFPs are called pluggable port modules (PPMs). SFPs/XFPs/CXPs/CFPs are hot-swappable I/O devices that plug into a port to link the port with the fiber-optic network. Multirate PPMs have provisionable port rates and payloads. For more information about SFPs, XFPs, and CXPs, see the “SFP, SFP+, XFP, CXP, and CFP Modules” section.
Step 1 Complete the DLP-G46 Log into CTC task to log into an ONS 15454 on the network. If you are already logged in, continue with Step 2.
a. Verify that the alarm filter is not turned on. See the “DLP-G128 Disable Alarm Filtering” task as necessary.
b. Verify that no unexplained conditions appear. If unexplained conditions appear, resolve them before continuing. Refer to the Cisco ONS 15454 DWDM Troubleshooting Guide .
Step 3 If you are provisioning a MXP_MR_2.5G or MXPP_MR_2.5G card, complete the G235 Change the 2.5G Data Muxponder Card Mode. If not, continue with Step 4
Step 4 If you are provisioning a MXP_MR_10DME_C, MXP_MR_10DME_L, or MXP_MR_10DMEX_C card, complete the G332 Change the 10G Data Muxponder Port Mode. If not, continue with Step 5.
Step 5 If you are provisioning a GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE card, complete the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode. If not, continue with Step 6.
Step 6 If you are provisioning a OTU2_XP card, complete the G452 Change the OTU2_XP Card Mode. If not, continue with Step 7.
Step 7 If you are provisioning a PPM on an ADM-10G card, complete the G411 Provision an ADM-10G PPM and Port. If not, continue with Step 11.
Step 8 If you are provisioning a PPM on an AR_MXP, AR_XP, or AR_XPE card, complete the G321 Provision Multiple Operating Modes on AR_MXP, AR_XP, or AR_XPE Cards. If not, continue with Step 11.
Step 9 If you are provisioning a PPM on an 100G-LC-C, 10x10G-LC, or CFP-LC card, complete the G235 Provision an Operating Mode on the 100G-LC-C, 10x10G-LC, or CFP-LC Card. If not, continue with Step 11.
Step 10 If you are provisioning a PPM on a WSE card, complete the G338 Provision an Operating Mode on the WSE Card. If not, continue with Step 11.
Step 11 Complete the DLP-G726 Preprovisioning a Multirate PPM task for TXP, MXP, AR_MXP, AR_XP, AR_XPE, 100G-LC-C, 10x10G-LC, CFP-LC, WSE, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, or OTU2_XP ports with multirate PPMs. If you already preprovisioned the multirate PPM, skip this step and continue with Step 12.
Step 12 If you are provisioning an IBM ETR_CLO (External Time Reference – Control Link Oscillator) or InterSystem Coupling Link (ISC) service on the PPM, complete G274 Verify Topologies for ETR_CLO and ISC Services. Otherwise, continue with Step 13.
Step 13 Complete the G278 Provision the Optical Line Rate to assign a line rate to a TXP, MXP, AR_MXP, AR_XP, AR_XPE, WSE, 100G-LC-C, 10x10G-LC, CFP-LC, or OTU2_XP port after the PPM is provisioned. (This task is not performed for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards.)
Step 14 If you need to delete a PPM at any point in this procedure, complete the DLP-G727 Delete PPM Provisioning task.
Stop. You have completed this procedure.
DLP-G235 Change the 2.5G Data Muxponder Card Mode
This task changes the card mode for MXP_MR_2.5G and MXPP_MR_2.5G muxponder cards. The card mode determines which PPMs can be provisioned for the card. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_MR_2.5G or MXPP_MR_2.5G card where you want to change the card settings.
Step 2 Click the Provisioning > Line > SONET (ANSI) or SDH (ETSI) tabs.
Step 3 Locate the Trunk port table row and verify that the Service State column value is OOS-MA,DSBLD (ANSI) or Locked-enabled,disabled (ETSI). If the service state is correct, continue with Step 6. If not, complete the following steps:
a. Click the Admin State table cell and choose OOS,DSBLD (ANSI) or Locked,Maintenance (ETSI).
Step 4 Click the Provisioning > Line > Client tabs.
Step 5 Locate the Trunk port table row and verify that the Service State column value is OOS-MA,DSBLD (ANSI) or Locked-enabled,disabled (ETSI). If the service state is correct, continue with Step 6. If not, complete the following steps:
a. Click the Admin State table cell and choose OOS,DSBLD (ANSI) or Locked,Maintenance (ETSI).
Step 6 Click the Provisioning > Card tabs.
Step 7 Change the Card Mode as needed:
- FC-GE—Choose this option if you will provision any of the following PPM port rates: FC1G (Ports 1-1 and 2-1 only), FC2G (Port 1-1 only), FICON1G (Ports 1-1 and 2-1 only), FICON2G (Port 1-1 only), and ONE_GE (Ports 1-1 through 8-1).
- Mixed—Choose this option if you will provision any of the following PPM port rates: FC1G and ONE_GE (Port 1–1 only), ESCON (Ports 5–1 through 8-1 only)
- ESCON—Choose this option if you will provision the ESCON PPM on Ports 1-1 through 8-1.
Note The Provisioning > Card tab also has the display-only Tunable Wavelengths field. This field shows the supported wavelengths of the trunk port after the card is installed in the format:
first wavelength-last wavelength-frequency spacing-number of supported wavelengths.
For example, 1529.55nm-1561.83nm-50gHz-82.
Step 9 Return to your originating procedure (NTP).
DLP-G332 Change the 10G Data Muxponder Port Mode
This task changes the port mode for the MXP_MR_10DME_C, MXP_MR_10DME_L, and MXP_MR_10DMEX_C muxponder cards. The port mode determines which PPMs can be provisioned on the ports. |
|
Note The MXP_MR_10DME_C, MXP_MR_10DME_L, and MXP_MR_10DMEX_C cards have two port mode groups, one for Ports 1 through 4, and the second for Ports 5 through 8. To change the port mode, all ports within the selected port group must be in OOS (out-of-service) service state. Ports in the second port group do not need to be in OOS service state if you are not changing the port mode for the second port group. Before you change the port mode, you must also ensure that any PPM port rate provisioned for the selected port group is deleted (see the DLP-G727 Delete PPM Provisioning).
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_MR_10DME_C, MXP_MR_10DME_L, or MXP_MR_10DMEX_C card where you want to change the port mode.
Step 2 Click the Provisioning > Card tabs.
Step 3 Change the port mode as described in Table 11-43 .
Note The PPM port rates are provisioned in the DLP-G726 Preprovisioning a Multirate PPM task.
Note The Provisioning > Cards tab also has a display-only Tunable Wavelengths field which shows the wavelengths supported by the card. If a MXP_MR_10DME_C card is installed, the 32 C-band wavelengths appear. If the MXP_MR_10DME_L card is installed, the 32 L-band wavelengths appear. If the MXP_MR_10DMEX_C card is installed, the 82 C-band wavelengths appear.
Step 5 Return to your originating procedure (NTP).
Note Loopbacks on MXP-MR-10DME are not applicable when Fiber Channel switches are present.
Note If the Fiber Channel switch version is not present then the Distance Extension settings are not supported.
DLP-G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card where you want to change the card mode.
Step 2 In card view, click Provisioning > Ether Ports > Ports .
Step 3 Verify that any provisioned client or trunk ports have an OOS-MA,DSBLD (ANSI) or Locked-enabled,disabled (ETSI) service state in the Service State column . If so, continue with Step 4. If not, complete the following substeps.
a. For the first port that is not out of service, in the Admin State column, choose OOS,DSBLD (ANSI) or Locked,disabled (ETSI).
b. Repeat Step a for each port that is not out of service.
Step 4 Click the Provisioning > Card tabs.
Step 5 Choose one of the card modes shown in Table 11-44 .
The GE-XP and GE-XPE cards operating in 10GE MXP mode and configured for 100% traffic flow, do not drop frames when up to nine ports are in use. However, when all the ten ports are in use, some frames are dropped. When the tenth port is to be used, configure the Committed Info Rate (CIR) at 55% on any one of the ports. For more information about configuring the CIR, see the G380 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Ethernet Settings.
Step 6 Click Apply , then click Yes in the confirmation dialog box.
Step 7 Return to your originating procedure (NTP).
DLP-G411 Provision an ADM-10G PPM and Port
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the ADM-10G card where you want to provision PPM settings.
Step 2 Click the Provisioning > Pluggable Port Modules tabs.
Step 3 In the Pluggable Port Modules area, click Create. The Create PPM dialog box appears.
Step 4 In the Create PPM dialog box, complete the following:
Step 5 Click OK . The newly created PPM appears in the Pluggable Port Modules area. The row in the Pluggable Port Modules area turns white and the Actual Equipment Type column lists the equipment name.
Step 6 In the Pluggable Ports area, click Create. The Create Ports dialog box appears.
Step 7 In the Create Ports dialog box, complete the following:
– Ports 1 - 8 can only be OC-3, OC-12, or ONE_GE
– Ports 9 - 12 can on be OC-3 or OC-12
– Ports 13 - 16 can only be OC-3, OC-12, or OC-48
Step 8 Click OK . The newly created port appears in the Pluggable Ports area. The port type you provisioned is listed in the Rate column.
Step 9 If you want to provision a PPM or another port, repeat Steps 4 through 8 .
Step 10 Return to your originating procedure (NTP).
DLP-G452 Change the OTU2_XP Card Mode
This task changes the OTU2_XP card mode. The card mode determines which PPMs can be provisioned for the card. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the OTU2_XP card where you want to change the card mode.
Step 2 In card view, click the Provisioning > Line > Ports tab.
Step 3 Verify that all provisioned client or trunk ports have an OOS-MA, DSBLD (ANSI) or Locked-enabled, disabled (ETSI) service state in the Service State column. If so, continue with Step 4 . If not, complete the following substeps.
a. For the first port that is not out of service, in the Admin State column, choose OOS, DSBLD (ANSI) or Locked, disabled (ETSI).
b. Repeat Step a for each port that is not out of service.
Step 4 Click the Provisioning > Card tab.
Step 5 Change the Card Configuration as needed:
- Transponder —Choose this option to provision the OTU2_XP card as a transponder. Port pairs 1-3 and 2-4 are both configured as transponders. This is the default card configuration.
- Standard Regen —Choose this option to provision the OTU2_XP card as a standard regenerator (with E-FEC only on one port). Port pairs 1-3 and 2-4 are both configured as regenerators.
- Enhanced FEC —Choose this option to provision the OTU2_XP card as an E-FEC regenerator (with E-FEC on two ports). Port pair 3-4 is configured as enhanced regenerator. Ports 1 and 2 are not used.
- Mixed —Choose this option to provision the OTU2_XP card as a transponder and a standard regenerator (mixed configuration). One of the port pair (1-3 or 2-4) is configured as a transponder and the other port pair as a standard regenerator.
- 10G Ethernet LAN Phy to WAN Phy— Choose this option to provision the OTU2_XP card to enable the 10G Ethernet LAN Phy to WAN Phy conversion. Port pair 1-3 supports LAN Phy to WAN Phy conversion. Port pair 2-4 can be configured either as a transponder or a standard regenerator.
Note If you revert to the previous release (release earlier than 9.10), be sure to disable the 10G Ethernet LAN Phy to WAN Phy conversion feature. If you do not disable the 10G Ethernet LAN Phy to WAN Phy feature, an error message stating that the user needs to disable 10G Ethernet LAN Phy to WAN Phy feature before reverting to the previous release is displayed.
Note Table 11-184 lists the Ethernet variables supported on Ports 1 and 3 of the OTU2_XP card that has the 10G Ethernet LAN Phy to WAN Phy enabled. When the card is in the 10G Ethernet LAN Phy to WAN Phy mode, no 10G FC RMONS are supported on Ports 2 and 4.
For more information on OTU2_XP card configuration rules, see the “OTU2_XP Card Configuration Rules” section.
Step 6 Click Apply . Then click Yes in the confirmation dialog box.
Step 7 Return to your originating procedure (NTP).
DLP-G274 Verify Topologies for ETR_CLO and ISC Services
Step 1 Display your site plan in Cisco TransportPlanner.
Step 2 Verify that the topology where you plan to run the ETR_CLO or ISC service can support the service. The following topologies support ETR_CLO or ISC:
– 40-MUX-C and 40-DMX-C/40-DMX-CE cards
– 40-WSS-C/40-WSS-CE and 40-DMX-C/40-DMX-CE cards
Figure 11-52 shows a single-span topology as displayed in Cisco TransportPlanner.
Figure 11-52 Single-Span Topology
– 40-MUX-C and 40-DMX-C/40-DMX-CE cards
– 40-WSS-C/40-WSS-CE and 40-DMX-C/40-DMX-CE cards
Line amplifiers can be installed between the terminal sites, but intermediate (traffic terminating) sites cannot be installed. Figure 11-53 shows a point-to-point topology as shown in Cisco TransportPlanner.
Figure 11-53 Point-to-Point Topology
– 40-MUX-C and 40-DMX-C/40-DMX-CE cards
– 40-WSS-C/40-WSS-CE and 40-DMX-C/40-DMX-CE cards
Line amplifiers can be installed between the hubs. Figure 11-54 shows two hub nodes with no line amplifier nodes installed. Figure 11-55 shows two hub nodes with line amplifier nodes installed.
Figure 11-54 Hubs with No Line Amplifiers
Figure 11-55 Hubs with Line Amplifiers
Step 3 Return to your originating procedure (NTP).
DLP-G278 Provision the Optical Line Rate
This task provisions the line rate for TXP, MXP, AR_MXP, AR_XP, AR_XPE, 100G-LC-C, 10x10G-LC, CFP-LC, WSE, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, ADM-10G, and OTU2_XP cards. |
|
DLP-G726 Preprovisioning a Multirate PPM G274 Verify Topologies for ETR_CLO and ISC Services, if you are provisioning an ETR_CLO service. |
|
Note The optical line rate for cards with single-rate PPMs is provisioned automatically when you complete the DLP-G726 Preprovisioning a Multirate PPM task if the trunk port is out of service. If the optical line rate was provisioned automatically, you do not need to complete this task for the MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, MXP_2.5G_10EX_C, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, or OTU2_XP card. If the trunk port was in-service when you provisioned the PPM, complete this task to provision the optical line rate manually for those cards.
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the TXP, MXP, AR_MXP, AR_XP, AR_XPE, 100G-LC-C, 10x10G-LC, CFP-LC, WSE, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, or OTU2_XP card where you want to provision PPM ports. If the data rate that you are provisioning is DV-6000, HDTV, ESCON, SDI/D1 Video, ISC1, ISC3 (for TXP_MR_2.5G and TXPP_MR_2.5G cards), or ETR_CLO, complete the following steps. Otherwise, continue with Step 4.
a. Click the Provisioning > OTN > OTN Lines tabs.
b. In the ITU-T G.709 OTN field for the respective PPM, choose Disable .
c. In the FEC field for the respective PPM, choose Disable .
Step 2 For the TXP_MR-10G card, click the Provisioning > Data Rate Selection tabs. For all other cards, go to Step 4.
Step 3 In the Data Rate Selection area, click Create and choose the type of port from the drop-down list. The supported port types are SONET (including 10G Ethernet WAN Phy) and 10G Ethernet LAN Phy.
Step 4 Click the Provisioning > Pluggable Port Modules tabs.
Step 5 In the Pluggable Ports area, click Create. The Create Port dialog box appears.
Step 6 In the Create Port dialog box, complete the following:
- Port—Choose the port and port number from the drop-down list. The first number indicates the PPM in the Pluggable Port Modules area, and the second number indicates the port number on the PPM. For example, the first PPM with one port appears as 1-1 and the second PPM with one port appears as 2-1. The PPM number can be 1 to 4, but the port number is always 1.
- Port Type—Choose the type of port from the drop-down list. The port type list displays the supported port rates on your PPM. See Table 11-45 for definitions of the supported rates on the TXP, MXP, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, OTU2_XP, 100G-LC-C, 10x10G-LC, CFP-LC, WSE, AR_MXP, AR_XP, or AR_XPE card.
Step 7 Click
OK
. The row in the Pluggable Ports area turns white if the physical SFP is installed and light blue if the SFP is not installed.
If the optical parameter values differ from the NE Default settings, change the port state to In-Service (for ANSI) or Unlocked (for ETSI) to synchronize the values with the NE Default settings.
Step 8 Repeat Step 5 through Step 7 to configure the rest of the port rates as needed.
|
|
|
|
TXP_MR_10G4 |
|
|
|
If the port mode is FC_GE_ISC:
|
|
Note If you have an OTU2 signal in which the OPU2 has been generated by multiplexing four ODU1 signals, choose SONET as the port rate. This allows the OTU2 signal to be transported transparently in standard or E-FEC regenerator configuration. |
|
|
|
Step 9 Return to your originating procedure (NTP).
NTP-G33 Create a Y-Cable Protection Group
This procedure creates a Y-cable protection group between the client ports of two TXP, MXP, AR_XP, AR_MXP, AR_XPE, WSE, 10x10G-LC, CFP-LC, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, or OTU2_XP cards when the cards are provisioned in the TXP or MXP mode. For additional information about Y-cable protection, see “Y-Cable Protection” section. |
|
In the Cisco ONS 15454 Hardware Installation Guide :
|
|
Note Y-cable protection is available for the 10x10G-LC card when it is provisioned in one of the following modes:
- TXP-10G mode—The client ports are provisioned with 10G Ethernet LAN Phy, 8G FC, 10G FC, OTU2, and OC192/STM-64 payloads.
- MXP-10G mode—The client ports are provisioned with 10GE, 8G FC, 10G FC, OTU2, and OC192/STM-64 payloads.
Note Y-cable protection is available for the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards when they are provisioned in the 10GE MXP, 20GE MXP, or 10GE TXP mode. If you are provisioning Y-cable protection for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards, the Ethernet mode must be set to 1000 and 10000 Mbps respectively. To provision the Ethernet mode, see the G380 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Ethernet Settings. Y-cable protection cannot be provisioned for the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards when they are provisioned in L2-over-DWDM mode.
Note Y-cable protection is available for the OTU2_XP card when it is provisioned in the TXP card mode. The OTU2-XP and 40E-MXP-C card cannot implement Y-cable protection for the client ports in 10 GE LAN PHY mode. Hence, a pair of OTU2_XP cards is used at each end in pass-through mode (Transponder mode with G.709 disabled) to implement Y-cable protection. The 40E-MXP-CE card can implement Y-cable protection without the OTU2-XP card for the client ports in LAN PHY GFP mode. However, the 40E-MXP-CE card cannot implement Y-cable protection without the OTU2-XP card for the client ports in LAN PHY WIS mode.
Note Y-cable protection for the WSE card is supported only with 10GE and OC-192/STM-64 payloads.
Note For SONET or SDH payloads, Loss of Pointer Path (LOP-P) alarms can occur on a split signal if the ports are not in a Y-cable protection group.
Step 1 View the Cisco TransportPlanner Traffic Matrix (see the Table 14-1) for your site. Verify the TXP, MXP, AR_MXP, AR_XP, AR_XPE, WSE, 10x10G-LC, CFP-LC, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, or OTU2_XP cards that need Y-cable protection groups. (Cards requiring Y-cable protection are indicated with “Y-Cable” in the Traffic Matrix table Protection Type column. For more information, see to the Cisco TransportPlanner DWDM Operations Guide .)
Step 2 Verify that the TXP, MXP, AR_MXP, AR_XP, AR_XPE, WSE, 10x10G-LC, CFP-LC, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, or OTU2_XP cards are installed according to the requirements specified in Table 14-7. Table 11-46 lists the protection types available in the ONS 15454 for DWDM client cards.
GE_XP5 10GE_XP6 |
Pairs a working transponder or muxponder card or port with a protect transponder or muxponder card or port. The protect port must be on a different card than the working port and it must be the same card type as the working port. The working and protect port numbers must be the same, that is, Port 1 can only protect Port 1, Port 2 can only protect Port 2, and so on. Note The working and protect card must be in the same shelf for a multishelf node. |
|
A splitter protection group is automatically created when a TXPP_MR_2.5G, MXPP_MR_2.5G, AR_MXP, AR_XP, or AR_XPE card is installed. You can edit the splitter protection group name. |
||
A splitter protection group is configurable for the OTU2_XP card. You can create a splitter protection group on ports 3 and 4 of the OTU2_XP card using the G199 Create a Splitter Protection Group for the OTU2_XP Card. |
||
In the Layer 2 (L2) card mode 1+1 protection is provided to protect the card against client port and card failure. |
Step 3 Verify that pluggable ports are provisioned for the same payload and payload rate on the TXP, MXP, AR_MXP, AR_XP, AR_XPE, WSE, 10x10G-LC, CFP-LC, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, or OTU2_XP cards where you want to create the Y-cable protection group:
a. Display the TXP, MXP, AR_MXP, AR_XP, AR_XPE, WSE, 10x10G-LC, CFP-LC, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, or OTU2_XP card in card view.
b. Click the Provisioning > Pluggable Port Module tab.
c. Verify that a pluggable port is provisioned in the Pluggable Port Module area, and the payload type and rate is provisioned for it in the Pluggable Ports area. If they are not the same, for example, if the pluggable port and rate are not the same, you must either delete the provisioned rate and create a new rate to match using the DLP-G725 Preprovisioning PPM Slot task or replace the pluggable port (SFP or XFP) using the DLP-G728 Remove PPM from the Line Card task.
Step 4 In node view (single-shelf mode) or shelf view (multishelf mode), click the Provisioning > Protection tabs.
Step 5 In the Protection Groups area, click Create .
Step 6 In the Create Protection Group dialog box, enter the following:
- Name—Type a name for the protection group. The name can have up to 32 alphanumeric (a-z, A-Z, 0-9) characters. Special characters are permitted. For TL1 compatibility, do not use question mark (?), backslash (\), or double quote (“) characters.
- Type—Choose Y Cable from the drop-down list.
- Protect Port—From the drop-down list, choose the port that will be the standby or protection port to the active port. The list displays the available transponder or muxponder ports. If transponder or muxponder cards are not installed, no ports appear in the drop-down list.
After you choose the protect port, a list of available working ports appear in the Available Ports list. If no cards are available, no ports appear. If this occurs, you can not complete this task until you install the physical cards or preprovision the ONS 15454 slots using the G353 Preprovision a Slot.
Step 7 From the Available Ports list, select the port that will be protected by the port you selected in Protect Ports. Click the top arrow button to move the port to the Working Ports list.
Step 8 Complete the remaining fields:
- Revertive—Check this check box if you want traffic to revert to the working port after failure conditions remain corrected for the amount of time entered in the Reversion Time field.
- Reversion time—If Revertive is checked, select a reversion time from the drop-down list. The range is 0.5 to 12.0 minutes. The default is 5.0 minutes. Reversion time is the amount of time that will elapse before the traffic reverts to the working card. The reversion timer starts after conditions causing the switch are cleared.
Note The bidirectional switching option is available for Y-cable protection groups only in the following cases:
- On the MXP_MR_10DME card when ISC3_PEER_1G/ISC3_PEER_2G is the client payload.
- On the MXP_MR_10DME and MXP_MR_2.5G cards when Fibre Channel is the client payload. In this case bidirectional switching is:
– Automatically enabled when Distance Extension is enabled.
– Automatically disabled when Distance Extension is disabled.
The bidirectional switching option is available for all SONET and SDH 1+1 protection groups.
Step 10 Repeat this procedure for every Y-cable protection group indicated in the Cisco TransportPlanner Traffic Matrix.
Stop. You have completed this procedure.
NTP-G199 Create a Splitter Protection Group for the OTU2_XP Card
This procedure creates a splitter protection group between the trunk ports of an OTU2_XP card. For additional information about splitter protection, see the “Splitter Protection” section. |
|
Note A splitter protection group is automatically created when a TXPP_MR_2.5G, MXPP_MR_2.5G, or PSM card is installed. You can edit the splitter protection group name for these cards. The splitter protection group is deleted when you delete the TXPP_MR_2.5G, MXPP_MR_2.5G, or PSM card.
Note Splitter protection is available for the OTU2_XP card when it is provisioned in Transponder configuration only. In a splitter-protected Transponder configuration, Port 1 is the client port, Port 3 is the working trunk port, and Port 4 is the standby trunk port.
Note For SONET or SDH payloads, Loss of Pointer Path (LOP-P) alarms can occur on a split signal if the ports are not in a splitter protection group.
Step 1 View the Cisco TransportPlanner Traffic Matrix (see the Table 14-1) for your site. Verify which OTU2_XP card needs a splitter protection group. (Cards requiring splitter protection are indicated with “Splitter” in the Traffic Matrix table Protection Type column. Refer to the Cisco TransportPlanner DWDM Operations Guide for more information.)
Step 2 Verify that the OTU2_XP card is installed according to the requirements specified in Table 14-7.
Step 3 Verify that the pluggable port (SFP or XFP) slot is provisioned for the same payload rate as the pluggable port on the OTU2_XP card where you will create the splitter protection group:
a. Display the OTU2_XP card in card view.
b. Click the Provisioning > Pluggable Port Module tabs.
c. Verify that a pluggable port (SFP or XFP) slot is provisioned in the Pluggable Port Module area, and that the payload rate of the pluggable port (SFP or XFP) slot is same as the payload rate of the pluggable port on the OTU2_XP card provisioned in the Pluggable Ports area. If they are not the same, you must either delete the provisioned rate and create a new rate to match using the DLP-G725 Preprovisioning PPM Slot task or replace the pluggable port (SFP or XFP) using the DLP-G728 Remove PPM from the Line Card task.
Step 4 In node view (single-shelf mode) or shelf view (multishelf view), click the Provisioning > Protection tabs.
Step 5 In the Protection Groups area, click Create .
Step 6 In the Create Protection Group dialog box, enter the following:
- Name—Type a name for the protection group. The name can have up to 32 alphanumeric (a-z, A-Z, 0-9) characters. Special characters are permitted. For TL1 compatibility, do not use question mark (?), backslash (\), or double quote (“) characters.
- Type—Choose Splitter from the drop-down list.
- Protect Card—From the drop-down list, choose the port that will be the standby or protection port to the active port. The list displays the available OTU2_XP ports. If transponder or muxponder cards are not installed or if the trunk ports of the card are part of a regenerator group, no ports appear in the drop-down list.
After you choose the protect port, a list of available working ports appear in the Available Cards list. If no cards are available, no ports appear. If this occurs, you cannot complete this task until you install the physical cards or preprovision the ONS 15454 slots using the G353 Preprovision a Slot.
Step 7 From the Available Cards list, select the port that will be protected by the port you selected in Protect Cards. Click the top arrow button to move the port to the Working Cards list.
Step 8 Complete the remaining fields:
- Revertive—Check this check box if you want traffic to revert to the working port after failure conditions remain corrected for the amount of time entered in the Reversion Time field.
- Reversion time—If Revertive is checked, select a reversion time from the drop-down list. The range is 0.5 to 12.0 minutes. The default is 5.0 minutes. Reversion time is the amount of time that will elapse before the traffic reverts to the working card. The reversion timer starts after conditions causing the switch are cleared.
Note The Bidirectional Switching option is not applicable for splitter protection groups.
Step 10 Repeat this procedure for every splitter protection group indicated in the Cisco TransportPlanner Traffic Matrix.
Stop. You have completed this procedure.
NTP-G198 Create 1+1 Protection for GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards
This procedure creates a 1+1 protection group to protect against client port and card failure of GE_XP, 10GE_XP, GE_XPE, 10GE_XPE cards. For additional information about 1+1 protection, see the “1+1 Protection” section. |
|
Step 1 Complete the” DLP-G46 Log into CTC ” task at the node where you want to protect the card against client port and card failure. If you are already logged in, continue with Step 2.
Step 2 Verify that the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card is installed according to the requirements specified in Table 14-7.
Step 3 Complete the G242 Create an Internal Patchcord Manually by selecting the Trunk to Trunk (L2) option, at the trunk port where you want to create 1+1 protection.
Step 4 Complete the G461 Create a 1+1 Protection Group for GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards to create a protection group.
Step 5 Configure the standby port behavior, by setting the Protection Action to None or Squelch . For detailed information on how to configure the standby port behavior, see the, G380 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Ethernet Settings.
Note Do not enable squelch in a 1 + 1 protection group, if the 100FX, 100LX SFP, and ONS-SE-ZE-EL SFP is used in the protection group and is connected to the peer via the parallel cable (not Y-cable)
Note When you configure L2 1 + 1 protection on 10GE_XP and 10GE_XPE cards, set the Protection Action to None on the client ports. Setting the Protection Action as Squelch results in unexpected switching behavior.
Step 6 Configure the standby and active port speed, by setting the mode parameter to Auto or 1000 or any other values. For detailed information on how to configure the standby port behavior, see the G380 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Ethernet Settings.
Stop. You have completed this procedure.
NTP-G461 Create a 1+1 Protection Group for GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards
This procedure creates a 1+1 protection group for GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE slots where internal patchcords were created. |
|
Step 1 In node view (single-shelf mode) or multishelf view (multishelf mode), click the Provisioning > Protection tabs.
Step 2 In the Protection Groups area, click Create .
Step 3 In the Create Protection Group dialog box, enter the following:
- Name—Type a name for the protection group. The name can have up to 32 alphanumeric (a-z, A-Z, 0-9) characters. Special characters are permitted. For TL1 compatibility, do not use question mark (?), backslash (\), or double quote (“) characters.
- Type—Choose L2 1+1 (port) from the drop-down list.
- Protect Port—From the drop-down list, choose the port that will be the standby or protection port for the active port. The list displays the available transponder or muxponder ports. If transponder or muxponder cards are not installed, no ports appear in the drop-down list.
After you choose the protect port, a list of available working ports appear in the Available Ports list. If no cards are available, no ports appear. If this occurs, you cannot complete this task until you install the physical cards or preprovision the ONS 15454 slots using the G353 Preprovision a Slot.
Step 4 From the Available Ports list, select the port that will be protected by the port you selected in the Protected Port drop-down list. Click the top arrow button to move the port to the Working Ports list.
Step 5 Complete the remaining fields:
- Revertive—Check this check box if you want traffic to revert to the working port after failure conditions remain corrected for the amount of time entered in the Reversion Time field.
- Reversion time—If Revertive is checked, select a reversion time from the drop-down list. The range is 0.5 to 12.0 minutes. The default is 5.0 minutes. Reversion time is the amount of time that will elapse before the traffic reverts to the working card. The reversion timer starts after conditions causing the switch are cleared.
The bidirectional switching option is available for SONET and SDH 1+1 protection groups.
Step 7 Repeat this procedure for every 1+1 protection group indicated in the Cisco TransportPlanner Traffic Matrix.
Step 8 Return to your originating procedure (NTP).
NTP-G98 Provision the 2.5G Multirate Transponder Card Line Settings and PM Parameter Thresholds
This procedure changes the line and threshold settings for TXP_MR_2.5G and TXPP_MR_2.5G transponder cards. |
|
G179 Install the TXP, MXP, AR_MXP, AR_XP, AR_XPE, 100G-LC-C, 10x10G-LC, CFP-LC, WSE, ADM-10G, and OTU2_XP Cards DLP-G723 Install PPM on a Line Card DLP-G726 Preprovisioning a Multirate PPM (if necessary) G278 Provision the Optical Line Rate (if necessary) |
|
Step 1 Complete the “DLP-G46 Log into CTC ” task at the node where you want to change the transponder card settings. If you are already logged in, continue with Step 2.
Step 2 As needed, complete the G103 Back Up the Database to preserve the existing transmission settings.
Step 3 Perform any of the following tasks as needed:
- G229 Change the 2.5G Multirate Transponder Card Settings
- G230 Change the 2.5G Multirate Transponder Line Settings
- G231 Change the 2.5G Multirate Transponder Line Section Trace Settings
- G232 Change the 2.5G Multirate Transponder SONET or SDH Line Threshold Settings
- G320 Change the 2.5G Multirate Transponder Line RMON Thresholds for 1G Ethernet or 1G FC/FICON Payloads
- G305 Provision the 2.5G Multirate Transponder Trunk Port Alarm and TCA Thresholds
- G306 Provision the 2.5G Multirate Transponder Client Port Alarm and TCA Thresholds
- G234 Change the 2.5G Multirate Transponder OTN Settings
- G367 Change the 2.5G Multirate Transponder Trunk Wavelength Settings
Stop. You have completed this procedure.
DLP-G229 Change the 2.5G Multirate Transponder Card Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the TXP_MR_2.5G or TXPP_MR_2.5G card where you want to change the card settings.
Step 2 Click the Provisioning > Card tabs.
Step 3 Modify any of the settings described in Table 11-47 .
Note The Card subtab Framing Type and Tunable Wavelengths fields are display-only. Framing Type shows the card framing type, either SONET or SDH, depending on whether the card is installed in an ANSI or ETSI chassis. The Tunable Wavelengths field shows the tunable wavelengths for the physical TXP_MR_2.5G or TXPP_MR_2.5G that is installed.
Step 5 Return to your originating procedure (NTP).
DLP-G230 Change the 2.5G Multirate Transponder Line Settings
This task changes the line settings for the client port of the TXP_MR_2.5G and TXPP_MR_2.5G transponder cards. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the TXP_MR_2.5G or TXPP_MR_2.5G card where you want to change the line settings.
Step 2 Click the Provisioning > Line > SONET tabs.
Step 3 Modify any of the settings described in Table 11-48 .
Note The 2.5G multirate transponder trunk settings are provisioned in the G305 Provision the 2.5G Multirate Transponder Trunk Port Alarm and TCA Thresholds.
The user can assign a logical name for each of the ports shown by filling in this field. |
User-defined. Name can be up to 32 alphanumeric/ special characters. Blank by default. See the G104 Assign a Name to a Port. |
|
Sets the port service state unless network conditions prevent the change. For more information about administrative states, see the Administrative and Service States document. |
||
(Display only) Identifies the autonomously generated state that gives the overall condition of the port. Service states appear in the format: Primary State-Primary State Qualifier, Secondary State. For more information about service states, see the Administrative and Service States document. |
||
(OC-N and STM-N payloads only) Sets the signal fail bit error rate. |
||
(OC-N and STM-N payloads only) Sets the signal degrade bit error rate. |
||
|
||
(OC-N and STM-N payloads only) Sets the automatic in-service soak period. |
||
Step 5 Return to your originating procedure (NTP).
DLP-G231 Change the 2.5G Multirate Transponder Line Section Trace Settings
Note This task only applies to SONET services.
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the TXP_MR_2.5G or TXPP_MR_2.5G card where you want to change the section trace settings.
Step 2 Click the Provisioning > Line > Section Trace tabs.
Step 3 Modify any of the settings described in Table 11-49 .
Step 5 Return to your originating procedure (NTP).
DLP-G367 Change the 2.5G Multirate Transponder Trunk Wavelength Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the TXP_MR_2.5G or TXPP_MR_2.5G card where you want to change the trunk wavelength settings.
Step 2 Click the Provisioning > Line > Wavelength Trunk Settings tabs.
Step 3 Modify any of the settings as described in Table 11-50 .
Step 5 Return to your originating procedure (NTP).
DLP-G232 Change the 2.5G Multirate Transponder SONET or SDH Line Threshold Settings
This task changes the line threshold settings for TXP_MR_2.5G and TXPP_MR_2.5G transponder cards carrying OC-3/STM-1, OC-12/STM-4, and OC-48/STM-16 payloads. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the TXP_MR_2.5G or TXPP_MR_2.5G card where you want to change the line threshold settings.
Step 2 Click the Provisioning > Line Thresholds tabs.
Note You must modify Near End and Far End independently; 15 Min and 1 Day independently; and Line and Section independently. To do so, choose the appropriate radio button and click Refresh.
Step 3 Modify any of the settings in Table 11-51 .
Note Some parameters and options in Table 11-51 do not apply to all TXP_MR_2.5G or TXPP_MR_2.5G cards. If a parameter or option does not apply, that parameter or option does not appear in CTC.
Step 5 Return to your originating procedure (NTP).
DLP-G320 Change the 2.5G Multirate Transponder Line RMON Thresholds for 1G Ethernet or 1G FC/FICON Payloads
This task changes the line remote monitoring (RMON) threshold settings for TXP_MR_2.5G and TXPP_MR_2.5G transponder cards carrying the 1G Ethernet or 1G FC/FICON payloads. |
|
Step 1 In card view, display the TXP_MR_2.5G or TXPP_MR_2.5G card where you want to change the line threshold settings.
Step 2 Click the Provisioning > Line Thresholds > RMON Thresholds tabs.
Step 3 Click Create . The Create Threshold dialog box appears.
Step 4 From the Port drop-down list, choose the applicable port.
Step 5 From the Variable drop-down list, choose an Ethernet variable. See Table 11-52 for a list of available Ethernet variables.
Step 6 From the Alarm Type drop-down list, indicate whether the event will be triggered by the rising threshold, the falling threshold, or both the rising and falling thresholds.
Step 7 From the Sample Type drop-down list, choose either Relative or Absolute . Relative restricts the threshold to use the number of occurrences in the user-set sample period. Absolute sets the threshold to use the total number of occurrences, regardless of time period.
Step 8 Enter the appropriate number of seconds for the Sample Period.
Step 9 Enter the appropriate number of occurrences for the Rising Threshold.
For a rising type of alarm, the measured value must move from below the falling threshold to above the rising threshold. For example, if a network is running below a rising threshold of 1000 collisions every 15 seconds and a problem causes 1001 collisions in 15 seconds, the excess occurrences trigger an alarm.
Step 10 Enter the appropriate number of occurrences in the Falling Threshold field. In most cases a falling threshold is set lower than the rising threshold.
A falling threshold is the counterpart to a rising threshold. When the number of occurrences is above the rising threshold and then drops below a falling threshold, it resets the rising threshold. For example, when the network problem that caused 1001 collisions in 15 seconds subsides and creates only 799 collisions in 15 seconds, occurrences fall below a falling threshold of 800 collisions. This resets the rising threshold so that if network collisions again spike over a 1000 per 15-second period, an event again triggers when the rising threshold is crossed. An event is triggered only the first time a rising threshold is exceeded (otherwise, a single network problem might cause a rising threshold to be exceeded multiple times and cause a flood of events).
Step 12 Return to your originating procedure (NTP).
DLP-G305 Provision the 2.5G Multirate Transponder Trunk Port Alarm and TCA Thresholds
This task changes the TXP_MR_2.5G and TXPP_MR_2.5G trunk port alarm and threshold crossing alert (TCA) thresholds. |
|
Note In this task, trunk port refers to Port 2 for TXP_MR_2.5G cards, and to Ports 2 and 3 for TXPP_MR_2.5G cards.
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the TXP_MR_2.5G or TXPP_MR_2.5G card where you want to change the trunk port alarm and TCA settings.
Step 2 Click the Pluggable Port Modules tab. Under Pluggable Ports, record the Rate that is provisioned.
Step 3 Look up the rate in Table 11-53 and note whether it is 2R or 3R.
3R7 |
|||
Step 4 Click the Provisioning > Optics Thresholds tabs.
Step 5 Under Types , verify that the TCA radio button is checked. If not, check it and click Refresh .
Step 6 Referring to Table 11-54 , verify the trunk port TCA thresholds for RX Power High and RX Power Low depending on whether the rate is 2R or 3R. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and hitting Enter .
Note Do not modify the Laser Bias parameters.
Note You must modify 15 Min and 1 Day independently. To do so, choose the appropriate radio button and click Refresh.
Step 8 Under Types, click the Alarm radio button and click Refresh .
Step 9 Verify the trunk port Alarm thresholds for RX Power High is –7 dBm, and for RX Power Low is –26 dBm. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and hitting Enter .
Step 11 Return to your originating procedure (NTP).
DLP-G306 Provision the 2.5G Multirate Transponder Client Port Alarm and TCA Thresholds
This task provisions the client port alarm and TCA thresholds for the TXP_MR_2.5G and TXPP_MR_2.5G cards. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the TXP_MR_2.5G or TXPP_MR_2.5G card where you want to change the client port alarm and TCA settings.
Step 2 Click the Provisioning > Optics Thresholds tabs. The TCA thresholds are shown by default.
Step 3 Referring to Table 11-55 , verify the Port 1 (client) TCA thresholds for RX Power High, RX Power Low, TX Power High, and TX Power Low based on the client interface at the other end. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and hitting Enter .
Note Do not modify the Laser Bias parameters.
Note You must modify 15 Min and 1 Day independently. To do so, choose the appropriate radio button and click Refresh.
Note The hardware device that plugs into a TXP, MXP, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, or ADM-10G card faceplate to provide a fiber interface to the card is called a Small Form-factor Pluggable (SFP or XFP). In CTC, SFPs and XFPs are called pluggable port modules (PPMs). SFPs/XFPs are hot-swappable input/output devices that plug into a port to link the port with the fiber-optic network. Multirate PPMs have provisionable port rates and payloads. For more information about SFPs and XFPs, see the “SFP, SFP+, XFP, CXP, and CFP Modules” section.
Step 5 Under Types, click the Alarm radio button and click Refresh .
Step 6 Referring to Table 11-56 , verify the Alarm thresholds for RX Power High, RX Power Low, TX Power High, and TX Power Low based on the client interface that is provisioned. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and hitting Enter .
Step 8 Return to your originating procedure (NTP).
DLP-G234 Change the 2.5G Multirate Transponder OTN Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the TXP_MR_2.5G or TXPP_MR_2.5G card where you want to change the OTN settings.
Step 2 Click the Provisioning > OTN tabs, then choose one of the following subtabs: OTN Lines , G.709 Thresholds , FEC Thresholds , or Trail Trace Identifier .
Step 3 Modify any of the settings described in Tables 11-57 through 11-60 .
Note You must modify Near End and Far End; 15 Min and 1 Day; and SM and PM settings independently. To do so, choose the appropriate radio button and click Refresh.
Table 11-57 describes the values on the Provisioning > OTN > OTN Lines tab.
Table 11-58 describes the values on the Provisioning > OTN > G.709 Thresholds tab.
Port8 |
||
Numeric. Can be set for Near End or Far End, for 15-minute or one-day intervals, or for SM (OTUk) or PM (ODUk). Select a bullet and click Refresh . |
||
Numeric. Can be set for Near End or Far End, for 15-minute or one-day intervals, or for SM (OTUk) or PM (ODUk). Select a bullet and click Refresh . |
||
Numeric. Can be set for Near End or Far End, for 15-minute or one-day intervals, or for SM (OTUk) or PM (ODUk). Select a bullet and click Refresh . |
||
Numeric. Can be set for Near End or Far End, for 15-minute or one-day intervals, or for SM (OTUk) or PM (ODUk). Select a bullet and click Refresh . |
||
Numeric. Can be set for Near End or Far End, for 15-minute or one-day intervals, or for SM (OTUk) or PM (ODUk). Select a bullet and click Refresh . |
Table 11-59 describes the values on the Provisioning > OTN > FEC Threshold tab.
Table 11-60 describes the values on the Provisioning > OTN > Trail Trace Identifier tab.
Step 5 Return to your originating procedure (NTP).
NTP-G96 Provision the 10G Multirate Transponder Card Line Settings, PM Parameters, and Thresholds
This procedure changes the line and threshold settings for 10G multirate transponder cards including the TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, and TXP_MR_10EX_C cards. |
|
G179 Install the TXP, MXP, AR_MXP, AR_XP, AR_XPE, 100G-LC-C, 10x10G-LC, CFP-LC, WSE, ADM-10G, and OTU2_XP Cards DLP-G723 Install PPM on a Line Card DLP-G726 Preprovisioning a Multirate PPM (if necessary) G278 Provision the Optical Line Rate (if necessary) |
|
Note The TXP_MR_10G card does not support PPMs.
Step 1 Complete the “DLP-G46 Log into CTC ” task at the node where you want to change the transponder card settings. If you are already logged in, continue with Step 2.
Step 2 As needed, complete the G103 Back Up the Database to preserve the existing transmission settings.
Step 3 If you are provisioning a TXP_MR_10G card, complete the G365 Provision the TXP_MR_10G Data Rate, and if you are provisioning a TXP_MR_10E or TXP_MR_10EX_C card, complete the G712 Provision the TXP_MR_10E or TXP_MR_10EX_C Data Rate. If not, continue with Step 4.
Step 4 Perform any of the following tasks as needed:
- G216 Change the 10G Multirate Transponder Card Settings
- G217 Change the 10G Multirate Transponder Line Settings
- G218 Change the 10G Multirate Transponder Line Section Trace Settings
- G219 Change the 10G Multirate Transponder Line Thresholds for SONET or SDH Payloads Including 10G Ethernet WAN Phy
- G319 Change the 10G Multirate Transponder Line RMON Thresholds for 10G Ethernet LAN Phy Payloads
- G301 Provision the 10G Multirate Transponder Trunk Port Alarm and TCA Thresholds
- G302 Provision the 10G Multirate Transponder Client Port Alarm and TCA Thresholds
- G221 Change the 10G Multirate Transponder OTN Settings
- G368 Change the 10G Multirate Transponder Trunk Wavelength Settings
Stop. You have completed this procedure.
DLP-G365 Provision the TXP_MR_10G Data Rate
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the TXP_MR_10G card where you want to change the card data rate settings.
Step 2 Click the Provisioning > Data Rate Selection tabs.
Step 4 In the Create Port dialog box, choose one of the following data rates:
Step 6 Return to your originating procedure.
DLP-G712 Provision the TXP_MR_10E or TXP_MR_10EX_C Data Rate
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the TXP_MR_10E or TXP_MR_10EX_C card where you want to change the card data rate settings.
Step 2 Click the Provisioning > Pluggable Port Modules tabs.
Step 3 In the Pluggable Port Modules area, click Create. The Create PPM dialog box appears.
Step 4 In the Create PPM dialog box, complete the following:
Step 5 Click OK. The newly created PPM appears in the Pluggable Port Modules area. The row in the Pluggable
Step 6 Port Modules area turns white and the Actual Equipment Type column lists the equipment name.
Step 7 In the Pluggable Ports area, click Create. The Create Ports dialog box appears.
Step 8 In the Create Port dialog box, choose one of the following data rates:
- SONET (ANSI) or SDH (ETSI) (including 10G Ethernet WAN Phy)
- 10G Ethernet LAN Phy
- 10G FIBER Channel
- (TXP-MR-10EX_C card only) IB_5G
Step 10 Return to your originating procedure.
DLP-G216 Change the 10G Multirate Transponder Card Settings
This task changes the card settings for the TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, and TXP_MR_10EX_C cards. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, or TXP_MR_10E_L card where you want to change the card settings.
Step 2 Click the Provisioning > Card tabs.
Step 3 Modify any of the settings described in Table 11-61 .
Step 5 Return to your originating procedure (NTP).
DLP-G217 Change the 10G Multirate Transponder Line Settings
This task changes the line settings for TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, and TXP_MR_10EX_C cards. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, or TXP_MR_10EX_C card where you want to change the line settings.
Step 2 Click the Provisioning > Line > SONET/SDH/Ethernet tabs. SONET is the option for ANSI shelves when 10G Ethernet WAN phy is the Pluggable Port Rate, SDH is the option for ETSI shelves when 10G Ethernet WAN phy is the Pluggable Port Rate, and Ethernet is the option for ANSI or ETSI shelves when 10GE LAN Phy is the Pluggable Port Rate.
Step 3 Modify any of the settings described in Table 11-62 .
Note In Table 11-62, some parameter tabs do not always apply to all 10G multirate transponder cards. If a tab does not apply, it will not appear in CTC.
|
|
||
User-defined. Name can be up to 32 alphanumeric/special characters. Blank by default. See the G104 Assign a Name to a Port. |
User-defined. Name can be up to 32 alphanumeric/special characters. Blank by default. See the G104 Assign a Name to a Port. |
||
Sets the port service state. For more information about administrative states, see the Administrative and Service States. |
|||
(Display only) Identifies the autonomously generated state that gives the overall condition of the port. Service states appear in the format: Primary State-Primary State Qualifier, Secondary State. For more information about service states, see the Administrative and Service States . |
|||
(SONET [ANSI] or SDH [ETSI] including 10G Ethernet WAN Phy only) Sets the signal fail bit error rate. |
|||
(SONET [ANSI] or SDH [ETSI] including 10G Ethernet WAN Phy only) Sets the signal degrade bit error rate. |
|||
(SONET [ANSI] or SDH [ETSI] including 10G Ethernet WAN Phy only) The optical transport type. |
|||
Sets the ALS function mode. The DWDM transmitter supports ALS according to ITU-T G.644 (06/99). ALS can be disabled, or it can be set for one of three mode options. |
|
|
|
(SONET [ANSI] or SDH [ETSI] including 10G Ethernet WAN Phy only) Sets the automatic in-service soak period. Double-click the time and use the up and down arrows to change settings. |
|||
(TXP_MR_10E, OC192 only) Sets the ProvidesSync card parameter. If checked, the card is provisioned as a network element (NE) timing reference. |
|||
(TXP_MR_10E, OC192 only) Sets the EnableSync card parameter. Enables synchronization status messages (S1 byte), which allow the node to choose the best timing source. |
|||
(TXP_MR_10E, TXP_MR_10G LAN Phy only) Sets the maximum Ethernet packet size. |
|||
(TXP_MR_10E, TXP_MR_10G LAN Phy only) Sets the incoming MAC address. |
|||
The Reach options depend on the traffic type that has been selected. |
The Reach options depend on the traffic type that has been selected. |
Step 5 Return to your originating procedure (NTP).
DLP-G218 Change the 10G Multirate Transponder Line Section Trace Settings
This task changes the line section trace settings for the TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, and TXP_MR_10EX_C transponder cards. |
|
Note The Section Trace tab is available for the 10G Multirate Transponder cards only if no PPMs are provisioned, or the OC192 PPM is provisioned. The tab is not available if a 10G Ethernet LAN Phy or 10G Fibre Channel PPM is provisioned.
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, or TXP_MR_10EX_C card where you want to change the section trace settings.
Step 2 Click the Provisioning > Line > Section Trace tabs.
Step 3 Modify any of the settings described in Table 11-63 .
Step 5 Return to your originating procedure (NTP).
DLP-G368 Change the 10G Multirate Transponder Trunk Wavelength Settings
This task changes the trunk wavelength settings for the TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, and TXP_MR_10EX_C cards. |
|
Note Before modifying the wavelength settings, change the port state to OOS,DSBLD (for ANSI) or Locked,disabled (for ETSI) and delete the circuit and patchcord provisioning present on the port. Payload or communication channel provisioning can be retained.
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, and TXP_MR_10EX_C card where you want to change the trunk wavelength settings.
Step 2 Click the Provisioning > Line > Wavelength Trunk Settings tabs.
Step 3 Modify any of the settings as described in Table 11-64 .
Step 5 Return to your originating procedure (NTP).
DLP-G219 Change the 10G Multirate Transponder Line Thresholds for SONET or SDH Payloads Including 10G Ethernet WAN Phy
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, or TXP_MR_10EX_C card where you want to change the line threshold settings.
Step 2 Click the Provisioning > Line Thresholds > SONET Thresholds (ANSI) or SDH Thresholds (ETSI) tabs.
Step 3 Modify any of the settings described in Table 11-65 .
Note Parameters shown in Table 11-65 do not apply to all 10G multirate transponder cards. If the parameter or option does not apply, it is not shown in CTC.
Step 5 Return to your originating procedure (NTP).
DLP-G319 Change the 10G Multirate Transponder Line RMON Thresholds for 10G Ethernet LAN Phy Payloads
This task changes the line threshold settings for TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, and TXP_MR_10EX_C transponder cards carrying the physical 10G Ethernet LAN payload. |
|
Step 1 Display the TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, or TXP_MR_10EX_C card where you want to change the line threshold settings in card view.
Step 2 Click the Provisioning > Line Thresholds > RMON Thresholds tabs.
Step 3 Click Create . The Create Threshold dialog box appears.
Step 4 From the Port drop-down list, choose the applicable port.
Step 5 From the Variable drop-down list, choose an Ethernet variable. See Table 11-66 for a list of available Ethernet variables.
Step 6 From the Alarm Type drop-down list, indicate whether the event will be triggered by the rising threshold, the falling threshold, or both the rising and falling thresholds.
Step 7 From the Sample Type drop-down list, choose either Relative or Absolute . Relative restricts the threshold to use the number of occurrences in the user-set sample period. Absolute sets the threshold to use the total number of occurrences, regardless of time period.
Step 8 Type in an appropriate number of seconds for the Sample Period.
Step 9 Type in the appropriate number of occurrences for the Rising Threshold.
For a rising type of alarm, the measured value must move from below the falling threshold to above the rising threshold. For example, if a network is running below a rising threshold of 1000 collisions every 15 seconds and a problem causes 1001 collisions in 15 seconds, the excess occurrences trigger an alarm.
Step 10 Enter the appropriate number of occurrences in the Falling Threshold field. In most cases a falling threshold is set lower than the rising threshold.
A falling threshold is the counterpart to a rising threshold. When the number of occurrences is above the rising threshold and then drops below a falling threshold, it resets the rising threshold. For example, when the network problem that caused 1001 collisions in 15 seconds subsides and creates only 799 collisions in 15 seconds, occurrences fall below a falling threshold of 800 collisions. This resets the rising threshold so that if network collisions again spike over a 1000 per 15-second period, an event again triggers when the rising threshold is crossed. An event is triggered only the first time a rising threshold is exceeded (otherwise, a single network problem might cause a rising threshold to be exceeded multiple times and cause a flood of events).
Note To view all RMON thresholds, click Show All RMON thresholds.
Step 12 Return to your originating procedure (NTP).
DLP-G301 Provision the 10G Multirate Transponder Trunk Port Alarm and TCA Thresholds
This task provisions the TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, or TXP_MR_10EX_C trunk port alarm and threshold cross alert (TCA) thresholds. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, or TXP_MR_10EX_C card where you want to change the trunk port alarm and TCA settings.
Step 2 Click the Provisioning > Optics Thresholds tabs.
Step 3 Under Types, verify that the TCA radio button is checked. If not, check it, then click Refresh .
Step 4 Referring to Table 11-67 , verify the trunk port (Port 2) TCA thresholds for RX Power High, RX Power Low, TX Power High, and TX Power Low. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting the existing value, and entering the new value. Hit Enter , then click Apply .
Note You must modify 15 Min and 1 Day independently. To do so, choose the appropriate radio button and click Refresh.
Note Do not modify the Laser Bias parameters.
Step 6 Under Types, click the Alarm radio button and click Refresh .
Step 7 Referring to Table 11-68 , verify the trunk port (Port 2) Alarm thresholds for RX Power High, RX Power Low, TX Power High, and TX Power Low. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting the existing value, and entering the new value. Hit Enter , then click Apply .
Note You must modify 15 Min and 1 Day independently. To do so, choose the appropriate radio button and click Refresh.
Step 9 Return to your originating procedure (NTP).
DLP-G302 Provision the 10G Multirate Transponder Client Port Alarm and TCA Thresholds
This task provisions the client port alarm and TCA thresholds for the TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, and TXP_MR_10EX_C cards. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, or TXP_MR_10EX_C card where you want to change the client port alarm and TCA settings.
Step 2 Click the Provisioning > Optics Thresholds tabs. The TCA thresholds are shown by default.
Step 3 Under Types, verify that the TCA radio button is checked. If not, check it, then click Refresh .
Step 4 Referring to Table 11-69 , verify the Port 1 (Client) TCA thresholds for RX Power High, RX Power Low, TX Power High, and TX Power Low based on the client interface at the other end. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting the existing value, and entering the new value. Hit Enter, then click Apply .
Note You must modify 15 Min and 1 Day independently. To do so, choose the appropriate radio button and click Refresh.
Note Do not modify the Laser Bias parameters.
Note The hardware device that plugs into a TXP, MXP, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, or ADM-10G card faceplate to provide a fiber interface to the card is called a Small Form-factor Pluggable (SFP or XFP). In CTC, SFPs and XFPs are called pluggable port modules (PPMs). SFPs/XFPs are hot-swappable input/output devices that plug into a port to link the port with the fiber-optic network. Multirate PPMs have provisionable port rates and payloads. For more information about SFPs and XFPs, see the “SFP, SFP+, XFP, CXP, and CFP Modules” section.
IB_5G9 |
Step 6 Under Types, click the Alarm radio button and click Refresh .
Step 7 Referring to Table 11-70 , provision the Port 1 (Client) Alarm thresholds for RX Power High, RX Power Low, TX Power High, and TX Power Low based on the client interface that is provisioned.
Note You must modify 15 Min and 1 Day independently. To do so, choose the appropriate radio button and click Refresh.
IB_5G10 |
Step 9 Return to your originating procedure (NTP).
DLP-G221 Change the 10G Multirate Transponder OTN Settings
This task changes the line OTN settings for the TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, and TXP_MR_10EX_C transponder cards. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the TXP_MR_10G, TXP_MR_10E, TXP_MR_10E_C, TXP_MR_10E_L, or TXP_MR_10EX_C card where you want to change the OTN settings.
Step 2 Click the Provisioning > OTN tabs, then click one of the following subtabs: OTN Lines , G.709 Thresholds , FEC Thresholds , or Trail Trace Identifier .
Step 3 Modify any of the settings described in Tables 11-71 through 11-74 .
Note You must modify Near End and Far End independently, 15 Min and 1 Day independently, and SM and PM independently. To do so, choose the appropriate radio button and click Refresh.
Table 11-71 describes the values on the Provisioning > OTN > OTN Lines tab.
Table 11-72 describes the values on the Provisioning > OTN > G.709 Thresholds tab.
Table 11-73 describes the values on the Provisioning > OTN > FEC Thresholds tab.
Table 11-74 describes the values on the Provisioning > OTN > Trail Trace Identifier tab.
Step 5 Return to your originating procedure (NTP).
NTP-G292 Provision the 40G Multirate Transponder Card Line Settings, PM Parameters, and Thresholds
This procedure changes the line settings, PM parameters, and threshold settings for 40G multirate transponder cards (40E-TXP-C, 40ME-TXP-C). |
|
Note The 40E-TXP-C and 40ME-TXP-C cards does not support PPMs.
Note The maximum ambient operating temperature for 40E-TXP-C, and 40ME-TXP-C cards is 500 Celsius.
Step 1 Complete the “DLP-G46 Log into CTC ” task at the node where you want to change the transponder card settings. If you are already logged in, continue with Step 2.
Step 2 As needed, complete the G103 Back Up the Database to preserve the existing transmission settings.
Step 3 If you are provisioning a 40E-TXP-C or 40ME-TXP-C card, complete the G656 Provision the 40E-TXP-C and 40ME-TXP-C Data Rate. If not, continue with Step 4.
Step 4 Perform any of the following tasks as needed:
- G657 Change the 40G Multirate Transponder Card Settings
- G658 Change the 40G Multirate Transponder Line Settings
- G659 Change the 40G Multirate Transponder SONET, SDH, or Ethernet Line Settings
- G660 Change the 40G Multirate Transponder Line Section Trace Settings
- G661 Change the 40G Multirate Transponder Line Thresholds for SONET or SDH Payloads Including 40G Ethernet WAN Phy
- G663 Provision the 40G Multirate Transponder Trunk Port Alarm and TCA Thresholds
- G664 Provision the 40G Multirate Transponder Client Port Alarm and TCA Thresholds
- G665 Change the 40G Multirate Transponder OTN Settings
Stop. You have completed this procedure.
DLP-G656 Provision the 40E-TXP-C and 40ME-TXP-C Data Rate
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 40E-TXP-C card where you want to change the card data rate settings.
Step 2 Click the Provisioning > Data Rate Selection tabs.
Step 4 In the Create Port dialog box, choose one of the following data rates:
Step 6 Return to your originating procedure.
DLP-G657 Change the 40G Multirate Transponder Card Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 40E-TXP-C card where you want to change the card settings.
Step 2 Click the Provisioning > Card tabs.
Step 3 Modify any of the settings described in Table 11-75 .
Step 5 Return to your originating procedure (NTP).
DLP-G658 Change the 40G Multirate Transponder Line Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 40E-TXP-C card where you want to change the line settings.
Step 2 Click the Provisioning > Line > Ports tabs.
Step 3 Modify any of the settings for the Client tab as described in Table 11-76 .
Assigns a logical name for each of the ports shown by filling in this field. |
User-defined. The port name can be up to 32 alphanumeric or special characters, or both. The port name is blank by default. For information about assigning a port name, see the G104 Assign a Name to a Port. |
|
Sets the port service state unless network conditions prevent the change. For more information about service states, see the Administrative and Service States document. |
||
(Display only) Identifies the autonomously generated state that gives the overall condition of the port. Service states appear in the format: Primary State-Primary State Qualifier, Secondary State. For more information about service states, see the Administrative and Service States document. |
||
|
||
(Display only) Displays the optical reach distance of the port. |
||
(Display only) Applicable only to client port 1. When the termination mode is set to transparent, squelch is enabled. For section/line termination mode, AIS is enabled. |
Note Both Squelch and AIS options are supported when the selected Termination Mode is Transparent. If the Termination Mode selected is Section or Line, then only AIS is supported. This is applicable for OC-192/STM-64 and OC-768/STM-256. |
|
Step 5 Return to your originating procedure (NTP).
DLP-G659 Change the 40G Multirate Transponder SONET, SDH, or Ethernet Line Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 40E-TXP-C card where you want to change the SONET, SDH, or Ethernet line settings.
Step 2 Click the Provisioning > Line > SONET/SDH/Ethernet tabs.
Step 3 Modify any of the settings described in Table 11-77 .
Note In Table 11-77, some parameter tabs do not always apply to all 40G multirate transponder cards. If a tab does not apply, it will not appear in CTC.
Note Port 17 and Port 18 are trunk ports that support OC192 payload in a single-card configuration. These ports are interlink ports in a double-card configuration (ADM-10G peer group). |
Note Port 17 and Port 18 are trunk ports that support STM64 payload in a single-card configuration. These ports are interlink ports in a double-card configuration (ADM-10G peer group). |
||
User-defined. Name can be up to 32 alphanumeric/special characters. Blank by default. See the G104 Assign a Name to a Port. |
User-defined. Name can be up to 32 alphanumeric/special characters. Blank by default. See the G104 Assign a Name to a Port. |
||
Sets the port service state. For more information about administrative states, see the Administrative and Service States document. |
|||
(Display only) Identifies the autonomously generated state that gives the overall condition of the port. Service states appear in the format: Primary State-Primary State Qualifier, Secondary State. For more information about service states, see the Administrative and Service States document. |
|||
Sets the ALS function mode. The DWDM transmitter supports ALS according to ITU-T G.644 (06/99). ALS can be disabled, or it can be set for one of three mode options. |
|
|
|
Sets the automatic in-service soak period. Double-click the time and use the up and down arrows to change settings. |
Note The AINS service state is not supported on interlink ports. |
Note The AINS service state is not supported on interlink ports. |
|
The Reach options depend on the traffic type that has been selected. |
The Reach options depend on the traffic type that has been selected. |
Step 5 Return to your originating procedure (NTP).
DLP-G660 Change the 40G Multirate Transponder Line Section Trace Settings
This task changes the line section trace settings of the 40E-TXP-C, and 40ME-TXP-C transponder cards. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 40E-TXP-C card where you want to change the line section trace settings.
Step 2 Click the Provisioning > Line > Section Trace tabs.
Step 3 Modify any of the settings described in Table 11-79 .
Step 5 Click Default to restore default values.
Step 6 Return to your originating procedure (NTP).
DLP-G692 Change the 40G Multirate Transponder OTU Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 40E-TXP-C or 40ME-TXP-C card where you want to change the OTU settings.
Step 2 Click the Provisioning > Line > OTU tabs.
Step 3 Modify any of the settings described in Table 11-80 .
Step 5 Return to your originating procedure (NTP).
DLP-G661 Change the 40G Multirate Transponder Line Thresholds for SONET or SDH Payloads Including 40G Ethernet WAN Phy
This task changes the line threshold settings of 40E-TXP-C and 40ME-TXP-C transponder cards carrying SONET or SDH payloads, including the physical 40G Ethernet WAN Phy payload. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 40E-TXP-C card where you want to change the line threshold settings.
Step 2 Click the Provisioning > Line Thresholds > SONET Thresholds (ANSI) or SDH Thresholds (ETSI) tabs.
Step 3 Modify any of the settings described in Table 11-81 .
Step 5 Return to your originating procedure (NTP).
DLP-G663 Provision the 40G Multirate Transponder Trunk Port Alarm and TCA Thresholds
This task provisions the 40E-TXP-C, and 40ME-TXP-C trunk port alarm and threshold cross alert (TCA) thresholds. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 40E-TXP-C card where you want to change the trunk port alarm and TCA settings.
Step 2 Click the Provisioning > Optics Thresholds tabs.
Step 3 Under Types area, verify that the TCA radio button is selected. If not, click it, then click Refresh .
Step 4 Referring to Table 11-82 , verify the trunk port (Port 2) TCA thresholds for RX Power High, RX Power Low, TX Power High, and TX Power Low. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting the existing value, and entering the new value. Press Enter , then click Apply .
Step 5 Under Intervals area, select 15 Min or 1 Day, then click Refresh.
Note Do not modify the Laser Bias parameters.
Step 7 Under Types area, click the Alarm radio button and click Refresh .
Step 8 Referring to Table 11-82 , verify the trunk port (Port 2) alarm thresholds for RX Power High, RX Power Low, TX Power High, and TX Power Low. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting the existing value, and entering the new value. Press Enter , then click Apply .
Step 9 Under Intervals area, select 15 Min or 1 Day, then click Refresh.
Step 11 Click Default to restore default values.
Step 12 Return to your originating procedure (NTP).
DLP-G664 Provision the 40G Multirate Transponder Client Port Alarm and TCA Thresholds
This task provisions the client port alarm and TCA thresholds for the 40E-TXP-C, and 40ME-TXP-C cards. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 40E-TXP-C card where you want to change the client port alarm and TCA settings.
Step 2 Click the Provisioning > Optics Thresholds tabs. The TCA thresholds are shown by default.
Step 3 Under Types area, verify that the TCA radio button is selected. If not, click it, then click Refresh .
Step 4 Referring to Table 11-84 , verify the client port (Port 1) TCA thresholds for RX Power High, RX Power Low, TX Power High, and TX Power Low based on the client interface at the other end. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting the existing value, and entering the new value. Press Enter, then click Apply .
Step 5 Under Intervals area, select 15 Min or 1 Day, then click Refresh.
Note Do not modify the Laser Bias parameters.
Step 7 Under Types area, click the Alarm radio button and click Refresh .
Step 8 Referring to Table 11-85 , provision the client port (Port 1) alarm thresholds for RX Power High, RX Power Low, TX Power High, and TX Power Low based on the client interface that is provisioned.
Step 9 Under Intervals area, select 15 Min or 1 Day, then click Refresh.
Step 11 Return to your originating procedure (NTP).
DLP-G665 Change the 40G Multirate Transponder OTN Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 40E-TXP-C card where you want to change the OTN settings.
Step 2 Click the Provisioning > OTN tabs, then click one of the following subtabs: OTN Lines , ITU-T G.709 Thresholds , FEC Thresholds , or Trail Trace Identifier .
Step 3 Modify any of the settings described in Tables 11-86 through 11-89 .
Note You must modify Near End and Far End, 15 Min and 1 Day, and SM and PM independently. To do so, select the appropriate radio button and click Refresh.
Table 11-86 describes the values on the Provisioning > OTN > OTN Lines tab.
Table 11-87 describes the values on the Provisioning > OTN > G.709 Thresholds tab.
Table 11-88 describes the values on the Provisioning > OTN > FEC Thresholds tab.
Table 11-89 describes the values on the Provisioning > OTN > Trail Trace Identifier tab.
Step 5 Click Default to restore default settings.
Step 6 Return to your originating procedure (NTP).
NTP-G170 Provision the ADM-10G Card Peer Group, Ethernet Settings, Line Settings, PM Parameters, and Thresholds
This procedure creates an ADM-10G peer group and changes line settings, PM parameters, and threshold settings for ADM-10G cards. |
|
G179 Install the TXP, MXP, AR_MXP, AR_XP, AR_XPE, 100G-LC-C, 10x10G-LC, CFP-LC, WSE, ADM-10G, and OTU2_XP Cards DLP-G723 Install PPM on a Line Card G411 Provision an ADM-10G PPM and Port (if necessary) G278 Provision the Optical Line Rate (if necessary) |
|
Step 1 Complete the “DLP-G46 Log into CTC ” task at the node where you want to change the ADM-10G card settings. If you are already logged in, continue with Step 2.
Step 2 As needed, complete the G103 Back Up the Database to preserve the existing transmission settings.
Step 3 To provision a peer group, complete the G403 Create the ADM-10G Peer Group.
Step 4 To provision Ethernet settings, complete the G469 Provision the ADM-10G Card Ethernet Settings.
Step 5 To change line settings, complete the following tasks as needed:
Step 6 To change thresholds, complete the following tasks as needed:
Stop. You have completed this procedure.
DLP-G403 Create the ADM-10G Peer Group
This task creates peer group protection for two ADM-10G cards within the same node, located on the same shelf. |
|
G179 Install the TXP, MXP, AR_MXP, AR_XP, AR_XPE, 100G-LC-C, 10x10G-LC, CFP-LC, WSE, ADM-10G, and OTU2_XP Cards, for two ADM-10G cards (located on the same shelf) for which a peer group is desired. |
|
Note You cannot perform this task on a single ADM-10G card; it is only available if a second ADM-10G card can be accessed through the interlink ports (Port 17 and Port 18).
Note Due to a hardware limitation, you cannot provision the SDCC/LDCC on Port 17.
Note Perform this task on only one of the two peer cards.
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the ADM-10G card where you want to change the card settings.
Step 2 Click the Provisioning > Card tabs.
Step 3 In the ADM Group Peer drop-down list, choose the slot number (for example, 14) where the companion ADM-10G card is located.
Step 4 In the ADM Peer Group field, enter a group name.
Note The Card Parameters Tunable Wavelengths area is read-only and does not contain any wavelengths until circuits are separately provisioned for the card.
Step 6 Return to your originating procedure (NTP).
DLP-G469 Provision the ADM-10G Card Ethernet Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the ADM-10G card where you want to change the Ethernet settings. The card view appears.
Step 2 Click the Provisioning > Line > Ethernet tabs.
Step 3 Modify any of the settings for the Ethernet tab as described in Table 11-90 . The parameters that appear depend on the card mode.
Step 5 Return to your originating procedure (NTP).
DLP-G397 Change the ADM-10G Line Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the ADM-10G card where you want to change the line settings.
Step 2 Click the Provisioning > Line > Ports tabs .
Step 3 Modify any of the settings described in Table 11-91 as needed.
Note In Table 11-91, some parameter tabs do not always apply to all ADM-10G cards. If a tab does not apply, it will not appear in CTC.
Note Port 17 and Port 18 are trunk ports that support OC192 payload in a single-card configuration. These ports are interlink ports in a double-card configuration (ADM-10G peer group). |
Note Port 17 and Port 18 are trunk ports that support STM64 payload in a single-card configuration. These ports are interlink ports in a double-card configuration (ADM-10G peer group). |
||
User-defined. Name can be up to 32 alphanumeric/special characters. Blank by default. See the G104 Assign a Name to a Port. |
User-defined. Name can be up to 32 alphanumeric/special characters. Blank by default. See the G104 Assign a Name to a Port. |
||
Sets the port service state. For more information about administrative states, see the Administrative and Service States document. |
|||
(Display only) Identifies the autonomously generated state that gives the overall condition of the port. Service states appear in the format: Primary State-Primary State Qualifier, Secondary State. For more information about service states, see the Administrative and Service States document. |
|||
Sets the ALS function mode. The DWDM transmitter supports ALS according to ITU-T G.644 (06/99). ALS can be disabled, or it can be set for one of three mode options. |
|
|
|
Sets the automatic in-service soak period. Double-click the time and use the up and down arrows to change settings. |
Note The AINS service state is not supported on interlink ports. |
Note The AINS service state is not supported on interlink ports. |
|
The Reach options depend on the traffic type that has been selected. |
The Reach options depend on the traffic type that has been selected. |
||
Shows the supported wavelengths of the trunk port after the card is installed in the format: first wavelength-last wavelength-frequency spacing-number of supported wavelengths . For example, 1529.55nm-1561.83nm-50gHz-8 are supported wavelengths. |
Shows the supported wavelengths of the trunk port after the card is installed in the format: first wavelength-last wavelength-frequency spacing-number of supported wavelengths . For example, 1529.55nm-1561.83nm-50gHz-8 are supported wavelengths. |
Step 5 Click the Provisioning > Line > SONET or SDH tabs.
Step 6 Modify any of the settings described in Table 11-92 as needed.
Step 7 Return to your originating procedure (NTP).
DLP-G398 Change the ADM-10G Line Section Trace Settings
Note The Section Trace tab is available for ports configured as OC-N (Ports 1 through 16, Ports 17 and 18 [only in a single-card configuration] and Port 19). Section trace is not available on interlink ports.
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the ADM-10G card where you want to change the section trace settings. The card view appears.
Step 2 Click the Provisioning > Line > Section Trace tabs.
Step 3 Modify any of the settings described in Table 11-93 .
Step 5 Return to your originating procedure (NTP).
DLP-G399 Change the ADM-10G Line Thresholds for SONET and SDH Payloads
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the ADM-10G card where you want to change the line threshold settings. The card view appears.
Step 2 Click the Provisioning > Line Thresholds > SONET or SDH Thresholds tabs.
Step 3 Modify any of the settings described in Table 11-94 .
Step 5 Return to your originating procedure (NTP).
DLP-G412 Change the ADM-10G Line RMON Thresholds for the 1G Ethernet Payload
This task changes the line RMON threshold settings for an ADM-10G card carrying the 1G Ethernet payload. |
|
Note This task can only be performed if the ADM-10G card has at least one PPM port provisioned for Gigabit Ethernet.
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the ADM-10G card where you want to change the line RMON thresholds. The card view appears.
Step 2 Click the Provisioning > Line Thresholds > RMON Thresholds tabs.
Step 3 Click Create . The Create Threshold dialog box appears.
Step 4 From the Port drop-down list, choose the applicable port.
Step 5 From the Variable drop-down list, choose the applicable Ethernet variable. See Table 11-95 for a list of available Ethernet variables.
Step 6 From the Alarm Type drop-down list, indicate whether the event will be triggered by the rising threshold, the falling threshold, or both the rising and falling thresholds.
Step 7 From the Sample Type drop-down list, choose either Relative or Absolute . Relative restricts the threshold to use the number of occurrences in the user-set sample period. Absolute sets the threshold to use the total number of occurrences, regardless of time period.
Step 8 Type an appropriate number of seconds for the Sample Period.
Step 9 Type the appropriate number of occurrences for the Rising Threshold.
For a rising type of alarm, the measured value must move from below the falling threshold to above the rising threshold. For example, if a network is running below a rising threshold of 1000 collisions every 15 seconds and a problem causes 1001 collisions in 15 seconds, the excess occurrences trigger an alarm.
Step 10 Enter the appropriate number of occurrences in the Falling Threshold field. In most cases a falling threshold is set lower than the rising threshold.
A falling threshold is the counterpart to a rising threshold. When the number of occurrences is above the rising threshold and then drops below a falling threshold, it resets the rising threshold. For example, when the network problem that caused 1001 collisions in 15 seconds subsides and creates only 799 collisions in 15 seconds, occurrences fall below a falling threshold of 800 collisions. This resets the rising threshold so that if network collisions again spike over a 1000 per 15-second period, an event again triggers when the rising threshold is crossed. An event is triggered only the first time a rising threshold is exceeded (otherwise, a single network problem might cause a rising threshold to be exceeded multiple times and cause a flood of events).
Step 12 Return to your originating procedure (NTP).
DLP-G400 Provision the ADM-10G Interlink or Trunk Port Alarm and TCA Thresholds
This task provisions the ADM-10G interlink or trunk port alarm and threshold crossing alert (TCA) thresholds. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the ADM-10G card where you want to change the interlink or trunk port alarm and TCA settings.
Step 2 Click the Provisioning > Optics Thresholds tabs.
Step 3 Under Types, verify that the TCA radio button is checked. If not, check it, then click Refresh .
Step 4 Referring to Table 11-96 , verify the interlink or trunk port TCA thresholds for RX Power High, RX Power Low, TX Power High, and TX Power Low. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and pressing Enter .
Note You must modify 15 Min and 1 Day independently. To do so, choose the appropriate radio button and click Refresh.
Note Do not modify the Laser Bias parameters.
17-1 and 18-1 (Trunk/Interlink) Note Port 17 and Port 18 are trunk ports in single-card configuration and an interlink port in double-card configuration (ADM-10G peer group). |
||||
Step 6 Under Types, click the Alarm radio button and click Refresh .
Step 7 Referring to Table 11-97 , verify the interlink or trunk port alarm thresholds for RX Power High, RX Power Low, TX Power High, and TX Power Low. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and pressing Enter .
Note You must modify 15 Min and 1 Day independently. To do so, choose the appropriate radio button and click Refresh.
Step 9 Return to your originating procedure (NTP).
DLP-G401 Provision the ADM-10G Client Port Alarm and TCA Thresholds
This task provisions the client port alarm and TCA thresholds for the ADM-10G card. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the ADM-10G card where you want to change the client port alarm and TCA settings.
Step 2 Click the Provisioning > Optics Thresholds tabs.
Step 3 Under Types, verify that the TCA radio button is checked. If not, check it, then click Refresh .
Step 4 Referring to Table 11-55 and Table 11-56, verify the Port 1 to 16 (Client) Alarm thresholds for RX Power High, RX Power Low, TX Power High, and TX Power Low based on the client interface that is provisioned. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and pressing Enter .
Note You must modify 15 Min and 1 Day independently. To do so, choose the appropriate radio button and click Refresh.
Step 6 Under Types, click the Alarm radio button and click Refresh .
Step 7 Referring to Table 11-55 and Table 11-56, verify the interlink ports 17-1 and 18-1 for RX Power High, RX Power Low, TX Power High, and TX Power Low settings. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and pressing Enter .
Step 9 Return to your originating procedure (NTP).
DLP-G402 Change the ADM-10G OTN Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the ADM-10G card where you want to change the OTN settings.
Step 2 Click the Provisioning > OTN tabs, then click one of the following subtabs: OTN Lines , ITU-T G.709 Thresholds , FEC Thresholds , or Trail Trace Identifier .
Step 3 Modify any of the settings described in Tables 11-98 through 11-101 .
Note You must modify Near End and Far End independently; 15 Min and 1 Day independently; and SM and PM independently. To do so, choose the appropriate radio buttons and click Refresh.
Table 11-98 describes the values on the Provisioning > OTN > OTN Lines tab.
Table 11-99 describes the values on the Provisioning > OTN > ITU-T G.709 Thresholds tab.
Table 11-100 describes the values on the Provisioning > OTN > FEC Thresholds tab.
Table 11-101 describes the values on the Provisioning > OTN > Trail Trace Identifier tab.
Step 5 Return to your originating procedure (NTP).
NTP-G333 Add an ADM-10G card to an Existing Topology
This procedure adds an ADM-10G card to an existing topology. Perform the steps in this procedure when OCHNC and DCC are present in the network. In case of OCH trails, delete all the circuits in Step 3 that traverses the port before deleting the OCH-trail. |
|
|
|
Step 1 If path protected circuits exist between Node A and Node B, complete the DLP-A197 Initiate a Path Protection Force Switch task. This task applies a force switch on the path between Node A and Node B.
Step 2 Complete the NTP-G129 Add a DWDM Node task to add Node C.
Step 3 Complete the G106 Delete Optical Channel Network Connections task to delete OCHNC circuit between Node A and Node B.
Step 4 Complete the G59 Create, Delete, and Manage Optical Channel Network Connections, task to create OCHNC circuit between Node A-->Node C and Node C-->Node B for wavelength connectivity.
Note The ports on the card in Node C must be tuned to the same wavelength as Node A and Node B.
Step 5 Create DCC terminations on Node C. See the DLP-A377 Provision Section DCC Terminations task.
Alternatively, if additional bandwidth is needed for CTC management, complete the DLP-A378 Provision Line DCC Terminations task.
Step 6 Ensure that the DCCs are functional between Node A-->Node C and Node C-->Node B. See the G76 Provision DCC/GCC Terminations task.
Step 7 Complete the G200 Create, Delete, and Manage STS or VC Circuits for the ADM-10G Card to create pass-through STS or VC circuits in Node C.
Step 8 Complete the NTP-A301 Merge Circuits task for each circuit created.
Step 9 If path protected circuits exist between Node A and Node B, complete the DLP-A198 Clear a Path Protection Force Switch task. This task clears a force switch on the path between Node A and Node B.
Step 10 Stop. You have completed this procedure.
NTP-G97 Modify the 4x2.5G Muxponder Card Line Settings and PM Parameter Thresholds
This procedure changes the line and threshold settings for the MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, and MXP_2.5G_10EX_C muxponder cards. |
|
G179 Install the TXP, MXP, AR_MXP, AR_XP, AR_XPE, 100G-LC-C, 10x10G-LC, CFP-LC, WSE, ADM-10G, and OTU2_XP Cards. DLP-G723 Install PPM on a Line Card DLP-G726 Preprovisioning a Multirate PPM (if necessary) G278 Provision the Optical Line Rate (if necessary) |
|
Step 1 Complete the “DLP-G46 Log into CTC ” task at the node where you want to change the muxponder card settings. If you are already logged in, continue with Step 2.
Step 2 As needed, complete the G103 Back Up the Database to preserve the existing transmission settings.
Step 3 Perform any of the following tasks as needed:
- G222 Change the 4x2.5G Muxponder Card Settings
- G223 Change the 4x2.5G Muxponder Line Settings
- G224 Change the 4x2.5G Muxponder Section Trace Settings
- G225 Change the 4x2.5G Muxponder Trunk Settings
- G226 Change the 4x2.5G Muxponder SONET/SDH Line Thresholds Settings
- G303 Provision the 4x2.5G Muxponder Trunk Port Alarm and TCA Thresholds
- G304 Provision the 4x2.5G Muxponder Client Port Alarm and TCA Thresholds
- G228 Change the 4x2.5G Muxponder Line OTN Settings
- G369 Change the 4x2.5G Muxponder Trunk Wavelength Settings
Step 4 As needed, complete the G103 Back Up the Database.
Stop. You have completed this procedure.
DLP-G222 Change the 4x2.5G Muxponder Card Settings
This task changes the card settings for the MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, and MXP_2.5G_10EX_C muxponder cards, including payload type, termination mode, and wavelength. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, or MXP_2.5G_10EX_C card where you want to change the card settings.
Step 2 Click the Provisioning > Card tabs.
Step 3 Modify any of the settings described in Table 11-102 .
Note Parameters shown in Table 11-102 do not apply to all 4x2.5G muxponder cards. If the parameter or option does not apply, it is not shown in CTC.
Step 5 Return to your originating procedure (NTP).
DLP-G223 Change the 4x2.5G Muxponder Line Settings
This task changes the line settings for the MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, and MXP_2.5G_10EX_C muxponder cards. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, or MXP_2.5G_10EX_C card where you want to change the line settings.
Step 2 Click the Provisioning > Line > SONET (ANSI) or SDH (ETSI) tabs.
Note The SONET tab appears only if you have created a PPM for a given port.
Step 3 Modify any of the settings described in Table 11-103 .
Note You must modify Near End and Far End independently; 15 Min and 1 Day independently; and Line and Section independently. To do so, choose the appropriate radio button and click Refresh.
(Display only) Port number. Ports 1 to 4 are client ports (OC-48/STM-16). Port 5 is the DWDM trunk (OC-192/STM-64) that provides wavelength services. Client ports will not appear of the pluggable port module is not provisioned for it. |
||
Provides the ability to assign the specified port a logical name. |
User-defined. Name can be up to 32 alphanumeric/ special characters. Blank by default. See the G104 Assign a Name to a Port. |
|
Sets the port service state unless network conditions prevent the change. For more information about administrative states, see the Administrative and Service States document. |
||
(Display only) Identifies the autonomously generated state that gives the overall condition of the port. Service states appear in the format: Primary State-Primary State Qualifier, Secondary State. For more information about service states, see the Administrative and Service States document. |
||
Sets the ALS function mode. The DWDM transmitter supports ALS according to ITU-T G.644 (06/99). ALS can be disabled or can be set for one of three mode options. |
|
|
Sets the automatic in-service soak period. Double-click the time and use the up and down arrows to change settings. |
||
Enables synchronization status messages (S1 byte), which allow the node to choose the best timing source. (This parameter does not appear for the MXP_2.5G_10E trunk port.) |
||
Sets the ProvidesSync card parameter. If checked, the card is provisioned as an NE timing reference. (This parameter does not appear for the MXP_2.5G_10E trunk port.) |
||
|
||
Step 5 Return to your originating procedure (NTP).
DLP-G224 Change the 4x2.5G Muxponder Section Trace Settings
This task changes the section trace settings for the MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, and MXP_2.5G_10EX_C muxponder cards. |
|
Note The Section Trace tab appears only if you have created a PPM for the card.
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, or MXP_2.5G_10EX_C card where you want to change the section trace settings.
Step 2 Click the Provisioning > Line > Section Trace tabs.
Step 3 Modify any of the settings described in Table 11-104 .
Step 5 Return to your originating procedure (NTP).
DLP-G225 Change the 4x2.5G Muxponder Trunk Settings
This task provisions the trunk settings for the MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, and MXP_2.5G_10EX_C muxponder cards. |
|
Note This task does not apply to the MXP_2.5G_10G card.
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, or MXP_2.5G_10EX_C card where you want to change the trunk settings.
Step 2 Click the Provisioning > Line > Trunk tabs.
Step 3 Modify any of the settings described in Table 11-105 .
(Display only) Displays the port number. Port 5 is the DWDM trunk (OC-192/STM-64) that provides wavelength services. |
||
Provides the ability to assign the specified port a logical name. |
User-defined. Name can be up to 32 alphanumeric/ special characters. Blank by default. See the G104 Assign a Name to a Port. |
|
Sets the port service state unless network conditions prevent the change. For more information about administrative states, see the Administrative and Service States document. |
||
(Display only) Identifies the autonomously generated state that gives the overall condition of the port. Service states appear in the format: Primary State-Primary State Qualifier, Secondary State. For more information about service states, see the Administrative and Service States document. |
||
Sets the ALS function mode. The DWDM transmitter supports ALS according to ITU-T G.644 (06/99). ALS can be disabled or can be set for one of three mode options. |
|
|
(OC-N and STM-N payloads only) Sets the automatic in-service soak period. |
Step 5 Return to your originating procedure (NTP).
DLP-G369 Change the 4x2.5G Muxponder Trunk Wavelength Settings
This task changes the trunk wavelength settings for the MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, and MXP_2.5G_10EX_C cards. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, and MXP_2.5G_10EX_C card where you want to change the trunk wavelength settings.
Step 2 Click the Provisioning > Line > Wavelength Trunk Settings tabs.
Step 3 Modify any of the settings described in Table 11-106 .
Step 5 Return to your originating procedure (NTP).
DLP-G226 Change the 4x2.5G Muxponder SONET/SDH Line Thresholds Settings
This task changes the SONET (ANSI) or SDH (ETSI) line threshold settings for the MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, and MXP_2.5G_10EX_C muxponder cards. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, or MXP_2.5G_10EX_C card where you want to change the line threshold settings.
Step 2 Click the Provisioning > Line Thresholds tabs.
Step 3 Modify any of the settings described in Table 11-107 .
Note In Table 11-107, some parameter tabs or selections do not always apply to all 4x2.5G muxponder cards. If the tabs or selections do not apply, they do not appear in CTC.
Step 5 Return to your originating procedure (NTP).
DLP-G303 Provision the 4x2.5G Muxponder Trunk Port Alarm and TCA Thresholds
This task changes the MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, and MXP_2.5G_10EX_C trunk port alarm and TCA thresholds. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, or MXP_2.5G_10EX_C card where you want to change the trunk port alarm and TCA settings.
Step 2 Click the Provisioning > Optics Thresholds tabs.
Step 3 Select TCA (if not already selected), a 15 Min or 1 Day PM interval radio button and then click Refresh .
Note You must modify 15 Min and 1 Day independently. To do so, choose the appropriate radio button and click Refresh.
Step 4 Referring to Table 11-108 , verify the trunk port (Port 5) TCA thresholds for RX Power High, RX Power Low, TX Power High, and TX Power Low. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and hitting Enter .
Note Do not modify the Laser Bias parameters.
Step 6 Under Types, click the Alarm radio button and click Refresh .
Step 7 Referring to Table 11-109 , verify the trunk port (Port 5) Alarm thresholds for RX Power High, RX Power Low, TX Power High, and TX Power Low. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and hitting Enter .
Note Do not modify the Laser Bias parameters.
Step 9 Return to your originating procedure (NTP).
DLP-G304 Provision the 4x2.5G Muxponder Client Port Alarm and TCA Thresholds
This task provisions the client port alarm and TCA thresholds for the MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, and MXP_2.5G_10EX_C cards. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, or MXP_2.5G_10EX_C card where you want to change the client port alarm and TCA settings.
Step 2 Click the Provisioning > Optics Thresholds tabs. The TCA thresholds are shown by default.
Step 3 Referring to Table 11-110 , verify the client Port N (where N = 1 through 4) TCA thresholds for RX Power High, RX Power Low, TX Power High, and TX Power Low based on the client interface at the other end. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and hitting Enter .
Note You must modify 15 Min and 1 Day independently. To do so, choose the appropriate radio button and click Refresh.
Note Do not modify the Laser Bias parameters.
Note The hardware device that plugs into a TXP, MXP, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, or ADM-10G card faceplate to provide a fiber interface to the card is called a Small Form-factor Pluggable (SFP or XFP). In CTC, SFPs and XFPs are called pluggable port modules (PPMs). SFPs/XFPs are hot-swappable input/output devices that plug into a port to link the port with the fiber-optic network. Multirate PPMs have provisionable port rates and payloads. For more information about SFPs and XFPs, see the “SFP, SFP+, XFP, CXP, and CFP Modules” section.
Step 4 Repeat Step 3 to provision each additional client port.
Step 5 Under Types, click the Alarm radio button and click Refresh .
Step 6 Referring to Table 11-111 , verify the client Port N (where N = 1 through 4) Alarm thresholds for RX Power High, RX Power Low, TX Power High, and TX Power Low based on the client interface that is provisioned. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and hitting Enter .
Note Do not modify the Laser Bias parameters.
Step 8 Repeat Steps 6 and 7 to provision each additional client port.
Step 9 Return to your originating procedure (NTP).
DLP-G228 Change the 4x2.5G Muxponder Line OTN Settings
This task changes the line OTN settings for MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, and MXP_2.5G_10EX_C muxponder cards. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, MXP_2.5G_10E_L, or MXP_2.5G_10EX_C card where you want to change the line OTN settings.
Step 2 Click the Provisioning > OTN tabs, then choose one of the following subtabs: OTN Lines , OTN G.709 Thresholds , FEC Thresholds , or Trail Trace Identifier .
Step 3 Modify any of the settings described in Tables 11-112 through 11-115 .
Note You must modify Near End and Far End independently, 15 Min and 1 Day independently, and SM and PM independently. To do so, choose the appropriate radio button and click Refresh.
Table 11-112 describes the values on the Provisioning > OTN > OTN Lines tab.
Note In Table 11-112, some parameter tabs or values do not always apply to all MXP_2.5G_10G, MXP_2.5G_10E, MXP_2.5G_10E_C, or MXP_2.5G_10E_L cards. If the tabs or values do not apply, they do not appear in CTC.
Table 11-113 describes the values on the Provisioning > OTN > OTN G.709 Thresholds tab.
Table 11-114 describes the values on the Provisioning > OTN > FEC Thresholds tab.
Table 11-115 describes the values on the Provisioning > OTN > Trail Trace Identifier tab.
Step 5 Return to your originating procedure (NTP).
NTP-G99 Modify the 2.5G Data Muxponder Card Line Settings and PM Parameter Thresholds
This procedure changes the line and threshold settings for the MXP_MR_2.5G and MXPP_MR_2.5G muxponder cards. |
|
G179 Install the TXP, MXP, AR_MXP, AR_XP, AR_XPE, 100G-LC-C, 10x10G-LC, CFP-LC, WSE, ADM-10G, and OTU2_XP Cards DLP-G723 Install PPM on a Line Card DLP-G726 Preprovisioning a Multirate PPM (if necessary) G278 Provision the Optical Line Rate (if necessary) |
|
Step 1 Complete the “DLP-G46 Log into CTC ” task at the node where you want to change the muxponder card settings. If you are already logged in, proceed to Step 2.
Step 2 As needed, complete the G103 Back Up the Database to preserve the existing transmission settings.
Step 3 Perform any of the following tasks as needed:
- G236 Change the 2.5G Data Muxponder Client Line Settings
- G237 Change the 2.5G Data Muxponder Distance Extension Settings
- G238 Change the 2.5G Data Muxponder SONET (OC-48)/SDH (STM-16) Settings
- G239 Change the 2.5G Data Muxponder Section Trace Settings
- G240 Change the 2.5G Data Muxponder SONET or SDH Line Thresholds
- G321 Change the 2.5G Data Muxponder Line Thresholds for 1G Ethernet or 1G FC/FICON Payloads
- G307 Provision the 2.5G Data Muxponder Trunk Port Alarm and TCA Thresholds
- G308 Provision the 2.5G Data Muxponder Client Port Alarm and TCA Thresholds
- G370 Change the 2.5G Data Muxponder Trunk Wavelength Settings
Note To use the Alarm Profiles tab, including creating alarm profiles and suppressing alarms, see the Alarm and TCA Monitoring and Management document.
Stop. You have completed this procedure.
DLP-G236 Change the 2.5G Data Muxponder Client Line Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_MR_2.5G or MXPP_MR_2.5G card where you want to change the line settings.
Step 2 Click the Provisioning > Line > Client tabs. Tabs and parameter selections vary according to PPM provisioning.
Note The hardware device that plugs into a TXP, MXP, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, or ADM-10G card faceplate to provide a fiber interface to the card is called a Small Form-factor Pluggable (SFP or XFP). In CTC, SFPs and XFPs are called pluggable port modules (PPMs). SFPs/XFPs are hot-swappable input/output devices that plug into a port to link the port with the fiber-optic network. Multirate PPMs have provisionable port rates and payloads. For more information about SFPs and XFPs, see the “SFP, SFP+, XFP, CXP, and CFP Modules” section.
Step 3 Modify any of the settings for the Client tab as described in Table 11-116 .
The user can assign a logical name for each of the ports shown by filling in this field. |
User-defined. Name can be up to 32 alphanumeric/special characters. Blank by default. See the G104 Assign a Name to a Port. Note 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. |
|
Sets the port service state unless network conditions prevent the change. For more information about administrative states, see the Administrative and Service States document. |
||
Identifies the autonomously generated state that gives the overall condition of the port. Service states appear in the format: Primary State-Primary State Qualifier, Secondary State. For more information about service states, see the Administrative and Service States document. |
||
|
||
The reach distances that appear in the drop-down list depend on the card:
|
||
Step 5 Return to your originating procedure (NTP).
DLP-G237 Change the 2.5G Data Muxponder Distance Extension Settings
Note Distance extension settings can be changed only if the facilities are out of service (OOS,DSBLD).
Note The distance extension parameters only apply to client ports (Ports 1 to 8) and not to the trunk ports (Port 9 for MXP_MR_2.5G card or Ports 9 and 10 for the MXPP_MR_2.5G card).
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_MR_2.5G or MXPP_MR_2.5G card where you want to change the distance extension settings.
Step 2 Click the Provisioning > Line > Client tabs. A client port must be provisioned for the tab to be present.
Note The hardware device that plugs into a TXP, MXP, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, or ADM-10G card faceplate to provide a fiber interface to the card is called a Small Form-factor Pluggable (SFP or XFP). In CTC, SFPs and XFPs are called pluggable port modules (PPMs). SFPs/XFPs are hot-swappable input/output devices that plug into a port to link the port with the fiber-optic network. Multirate PPMs have provisionable port rates and payloads. For more information about SFPs and XFPs, see the “SFP, SFP+, XFP, CXP, and CFP Modules” section.
Step 3 Locate the Client port table row and verify that the Service State column value is OOS-MA,DSBLD (ANSI) or Locked-enabled,disabled (ETSI). If yes, continue with Step 4. If not, complete the following substeps:
a. Click the Admin State table cell and choose OOS,DSBLD (ANSI) or Locked,Maintenance (ETSI).
Step 4 Click the Provisioning > Line > Distance Extension tabs. Tabs and parameter selections vary according to PPM provisioning.
Step 5 Modify any of the settings for the Distance Extension tab as described in Table 11-117 .
Step 7 Return to your originating procedure (NTP).
DLP-G238 Change the 2.5G Data Muxponder SONET (OC-48)/SDH (STM-16) Settings
This task changes the SONET (OC-48) or SDH (STM-16) settings for MXP_MR_2.5G and MXPP_MR_2.5G muxponder cards. |
|
Note SONET (OC-48)/SDH (STM-16) settings apply only to the trunk ports (Port 9 for the MXP_MR_2.5G card and Ports 9 and 10 for the MXPP_MR_2.5G card.)
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_MR_2.5G or MXPP_MR_2.5G card where you want to change the OC-48/STM-64 settings.
Step 2 Click the Provisioning > Line > SONET (ANSI) or SDH (ETSI). Tabs and parameter selections vary according to PPM provisioning.
Step 3 Modify any of the settings for the SONET or SDH tab as described in Table 11-118 .
9 (trunk for MXP_MR_2.5G) or 9 and 10 (trunks for MXPP_MR_2.5G) |
||
User-defined. Name can be up to 32 alphanumeric/ special characters. Blank by default. See the G104 Assign a Name to a Port. |
||
Sets the port service state unless network conditions prevent the change. For more information about administrative states, see the Administrative and Service States document. |
||
(Display only) Identifies the autonomously generated state that gives the overall condition of the port. Service states appear in the format: Primary State-Primary State Qualifier, Secondary State. For more information about service states, see the Administrative and Service States document. |
||
SF BER11 |
||
SD BER 1 |
||
Sets the ALS function mode. The DWDM transmitter supports ALS according to ITU-T G.644 (06/99). ALS can be disabled or can be set for one of three mode options. |
|
|
Sets the automatic in-service soak period. Double-click the time and use the up and down arrows to change settings. |
||
Sets the EnableSync card parameter. Enables synchronization status messages (S1 byte), which allow the node to choose the best timing source. |
||
Sets the Send DoNotUse card state. When checked, sends a DUS message on the S1 byte. |
||
Sets the ProvidesSync card parameter. If checked, the card is provisioned as an NE timing reference. |
Step 5 Return to your originating procedure (NTP).
DLP-G239 Change the 2.5G Data Muxponder Section Trace Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_MR_2.5G or MXPP_MR_2.5G card where you want to change the section trace settings.
Step 2 Click the Provisioning > Line > Section Trace tabs. Tabs and parameter selections vary according to PPM provisioning.
Note The hardware device that plugs into a TXP, MXP, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, or ADM-10G card faceplate to provide a fiber interface to the card is called a Small Form-factor Pluggable (SFP or XFP). In CTC, SFPs and XFPs are called pluggable port modules (PPMs). SFPs/XFPs are hot-swappable input/output devices that plug into a port to link the port with the fiber-optic network. Multirate PPMs have provisionable port rates and payloads. For more information about SFPs and XFPs, see the “SFP, SFP+, XFP, CXP, and CFP Modules” section.
Step 3 Modify any of the settings in the Section Trace tab as described in Table 11-119 .
Step 5 Return to your originating procedure (NTP).
DLP-G370 Change the 2.5G Data Muxponder Trunk Wavelength Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_MR_2.5G or MXPP_MR_2.5G card where you want to change the trunk wavelength settings.
Step 2 Click the Provisioning > Line > Wavelength Trunk Settings tabs.
Step 3 Modify any of the settings as described in Table 11-120 .
Step 5 Return to your originating procedure (NTP).
DLP-G240 Change the 2.5G Data Muxponder SONET or SDH Line Thresholds
This task changes the SONET or SDH line threshold settings for MXP_MR_2.5G and MXPP_MR_2.5G muxponder cards. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_MR_2.5G or MXPP_MR_2.5G card where you want to change the line threshold settings.
Step 2 Click the Provisioning > Line Thresholds > SONET Thresholds (ANSI) or SDH Thresholds (ETSI) tabs.
Step 3 Modify any of the settings as shown in Table 11-121 .
Note You must modify Near End and Far End independently, 15 Min and 1 Day independently, and Line and Section independently. To do so, choose the appropriate radio button and click Refresh.
Note In Table 11-121, some parameters or options do not apply to all MXP_MR_2.5G or MXPP_MR_2.5G cards. If the parameters or options do not apply, they do not appear in CTC.
Step 5 Return to your originating procedure (NTP).
DLP-G321 Change the 2.5G Data Muxponder Line Thresholds for 1G Ethernet or 1G FC/FICON Payloads
This task changes the line threshold settings for MXP_MR_10G and MXPP_MR_2.5G transponder cards carrying the 1G Ethernet or 1G FC/FICON payloads. |
|
Step 1 Display the MXP_MR_2.5G or MXPP_MR_2.5G card where you want to change the line threshold settings in card view.
Step 2 Click the Provisioning > Line Thresholds > RMON Thresholds tabs.
Step 3 Click Create . The Create Threshold dialog box appears.
Step 4 From the Port drop-down list, choose the applicable port.
Step 5 From the Variable drop-down list, choose an Ethernet variable. See Table 11-122 for a list of available Ethernet variables.
Step 6 From the Alarm Type drop-down list, indicate whether the event will be triggered by the rising threshold, the falling threshold, or both the rising and falling thresholds.
Step 7 From the Sample Type drop-down list, choose either Relative or Absolute . Relative restricts the threshold to use the number of occurrences in the user-set sample period. Absolute sets the threshold to use the total number of occurrences, regardless of time period.
Step 8 Type in an appropriate number of seconds for the Sample Period.
Step 9 Type in the appropriate number of occurrences for the Rising Threshold.
For a rising type of alarm, the measured value must move from below the falling threshold to above the rising threshold. For example, if a network is running below a rising threshold of 1000 collisions every 15 seconds and a problem causes 1001 collisions in 15 seconds, the excess occurrences trigger an alarm.
Step 10 Enter the appropriate number of occurrences in the Falling Threshold field. In most cases a falling threshold is set lower than the rising threshold.
A falling threshold is the counterpart to a rising threshold. When the number of occurrences is above the rising threshold and then drops below a falling threshold, it resets the rising threshold. For example, when the network problem that caused 1001 collisions in 15 seconds subsides and creates only 799 collisions in 15 seconds, occurrences fall below a falling threshold of 800 collisions. This resets the rising threshold so that if network collisions again spike over a 1000 per 15-second period, an event again triggers when the rising threshold is crossed. An event is triggered only the first time a rising threshold is exceeded (otherwise, a single network problem might cause a rising threshold to be exceeded multiple times and cause a flood of events).
Step 12 Return to your originating procedure (NTP).
DLP-G307 Provision the 2.5G Data Muxponder Trunk Port Alarm and TCA Thresholds
Note Throughout this task, trunk port refers to Port 9 (MXP_MR_2.5G and MXPP_MR_2.5G) and Port 10 (MXPP_MR_2.5G only).
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_MR_2.5G or MXPP_MR_2.5G card where you want to change the trunk port alarm and TCA settings.
Step 2 Click the Provisioning > Optics Thresholds tabs.
Note You must modify 15 Min and 1 Day independently. To do so, choose the appropriate radio button and click Refresh.
Step 3 Verify the trunk port TCA thresholds for RX Power High is –9 dBm and for RX Power Low is –23 dBm. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and hitting Enter .
Step 4 Under Types, click the Alarm radio button and click Refresh .
Note Do not modify the Laser Bias parameters.
Step 5 Verify the trunk port Alarm thresholds for RX Power High is –7 dBm and for RX Power Low is –26 dBm. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and hitting Enter .
Step 7 Return to your originating procedure (NTP).
DLP-G308 Provision the 2.5G Data Muxponder Client Port Alarm and TCA Thresholds
This task provisions the client port alarm and TCA thresholds for the MXP_MR_2.5G and MXPP_MR_2.5G cards. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_MR_2.5G or MXPP_MR_2.5G card where you want to change the client port alarm and TCA settings.
Step 2 Click the Provisioning > Optics Thresholds tabs. The TCA thresholds are shown by default.
Step 3 Referring to Table 11-123 , verify the client port (Ports 1 through 8) TCA thresholds for RX Power High, RX Power Low, TX Power High, and TX Power Low based on the client interface at the other end. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and hitting Enter .
Note Do not modify the Laser Bias parameters.
Note You must modify 15 Min and 1 Day independently. To do so, choose the appropriate radio button and click Refresh.
Note The hardware device that plugs into a TXP, MXP, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, or ADM-10G card faceplate to provide a fiber interface to the card is called a Small Form-factor Pluggable (SFP or XFP). In CTC, SFPs and XFPs are called pluggable port modules (PPMs). SFPs/XFPs are hot-swappable input/output devices that plug into a port to link the port with the fiber-optic network. Multirate PPMs have provisionable port rates and payloads. For more information about SFPs and XFPs, see the “SFP, SFP+, XFP, CXP, and CFP Modules” section.
Step 5 Repeat Steps 3 and 4 to provision each additional client port.
Step 6 Under Types, click the Alarm radio button and click Refresh .
Step 7 Referring to Table 11-124 , verify the client port (Ports 1 through 8) Alarm thresholds for RX Power High, RX Power Low, TX Power High, and TX Power Low based on the client interface that is provisioned. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and hitting Enter .
Step 9 Repeat Steps 7 and 8 to provision each additional client port. When you have finished provisioning client ports, continue with Step 10.
Step 10 Return to your originating procedure (NTP).
NTP-G148 Modify the 10G Data Muxponder Card Line Settings and PM Parameter Thresholds
This procedure changes the line and threshold settings for the MXP_MR_10DME_C, MXP_MR_10DME_L, and MXP_MR_10DMEX_C muxponder cards. |
|
G179 Install the TXP, MXP, AR_MXP, AR_XP, AR_XPE, 100G-LC-C, 10x10G-LC, CFP-LC, WSE, ADM-10G, and OTU2_XP Cards DLP-G723 Install PPM on a Line Card DLP-G726 Preprovisioning a Multirate PPM (if necessary) G278 Provision the Optical Line Rate (if necessary) |
|
Step 1 Complete the “DLP-G46 Log into CTC ” task at the node where you want to change the muxponder card settings. If you are already logged in, proceed to Step 2.
Step 2 As needed, complete the G103 Back Up the Database to preserve the existing transmission settings.
Step 3 Perform any of the following tasks as needed:
- G333 Change the 10G Data Muxponder Client Line Settings
- G334 Change the 10G Data Muxponder Distance Extension Settings
- G340 Change the 10G Data Muxponder Trunk Wavelength Settings
- G335 Change the 10G Data Muxponder SONET (OC-192)/SDH (STM-64) Settings
- G336 Change the 10G Data Muxponder Section Trace Settings
- G341 Change the 10G Data Muxponder SONET or SDH Line Thresholds
- G337 Change the 10G Data Muxponder Line RMON Thresholds for Ethernet, 1G FC/FICON, or ISC/ISC3 Payloads
- G338 Provision the 10G Data Muxponder Trunk Port Alarm and TCA Thresholds
- G339 Provision the 10G Data Muxponder Client Port Alarm and TCA Thresholds
- G366 Change the 10G Data Muxponder OTN Settings
Note To use the Alarm Profiles tab, including creating alarm profiles and suppressing alarms, see the Alarm and TCA Monitoring and Management document.
Stop. You have completed this procedure.
DLP-G333 Change the 10G Data Muxponder Client Line Settings
This task changes the line settings for the MXP_MR_10DME_C, MXP_MR_10DME_L, and MXP_MR_10DMEX_C muxponder cards. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_MR_10DME_C, MXP_MR_10DME_L, or MXP_MR_10DMEX_C card where you want to change the line settings.
Step 2 Click the Provisioning > Line > Client tabs. Tabs and parameter selections vary according to PPM provisioning.
Step 3 Modify any of the settings for the Client tab as described in Table 11-125 .
The user can assign a logical name for each of the ports shown by filling in this field. |
User-defined. Name can be up to 32 alphanumeric/ special characters. Blank by default. See the G104 Assign a Name to a Port. Note You can provision a string (port name) for each fiber channel/FICON interface on the MXP_MR_10DME_C, MXP_MR_10DME_L, and MXP_MR_10DMEX_C 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. |
|
Sets the port service state unless network conditions prevent the change. For more information about administrative states, see the Administrative and Service States document. |
||
(Display only) Identifies the autonomously generated state that gives the overall condition of the port. Service states appear in the format: Primary State-Primary State Qualifier, Secondary State. For more information about service states, see the Administrative and Service States document. |
||
|
||
The reach distances that appear in the drop-down list depend on the card:
|
||
Shuts down the far-end laser in response to certain defects. (Squelch does not apply to ISC COMPACT payloads.) |
Step 5 Return to your originating procedure (NTP).
DLP-G334 Change the 10G Data Muxponder Distance Extension Settings
This task changes the distance extension settings for the MXP_MR_10DME_C, MXP_MR_10DME_L, and MXP_MR_10DMEX_C muxponder card ports provisioned for Fibre Channel or FICON payloads. |
|
Note The distance extension parameters only apply to client ports (Ports 1 to 8) and not to the trunk port (Port 9).
Note The client port must be in the OOS,DSBLD (ANSI) or Locked,disabled (ETSI) state in order to change the distance extension settings. If a Y-cable is provisioned on the client port, both the working and protect client ports must be in OOS,DSBLD (ANSI) or Locked,disabled (ETSI) state before you change the distance extension settings.
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_MR_10DME_C, MXP_MR_10DME_L, or MXP_MR_10DMEX_C card where you want to change the distance extension settings.
Step 2 Click the Provisioning > Line > Distance Extension tabs.
Step 3 Modify any of the settings as described in Table 11-126 .
Step 5 Return to your originating procedure (NTP).
DLP-G340 Change the 10G Data Muxponder Trunk Wavelength Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_MR_10DME_C or MXP_MR_10DME_L card where you want to change the trunk wavelength settings.
Step 2 Click the Provisioning > Line > Wavelength Trunk Settings tabs.
Step 3 Modify any of the settings for the Wavelength Trunk Settings tab as described in Table 11-127 .
Step 5 Return to your originating procedure (NTP).
DLP-G335 Change the 10G Data Muxponder SONET (OC-192)/SDH (STM-64) Settings
This task changes the OC-192 (ANSI)/STM-64 (ETSI) settings for the MXP_MR_10DME_C and MXP_MR_10DME_L muxponder cards. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_MR_10DME_C or MXP_MR_10DME_L card where you want to change the SONET (OC-192)/SDH (STM-64) settings.
Step 2 Click the Provisioning > Line > SONET (ANSI) or SDH (ETSI). Tabs and parameter selections vary according to PPM provisioning.
Step 3 Modify any of the settings as described in Table 11-128 .
User-defined. Name can be up to 32 alphanumeric/ special characters. Blank by default. See the G104 Assign a Name to a Port. |
||
Sets the port service state unless network conditions prevent the change. For more information about administrative states, see the Administrative and Service States document. |
||
(Display only) Identifies the autonomously generated state that gives the overall condition of the port. Service states appear in the format: Primary State-Primary State Qualifier, Secondary State. For more information about service states, see the Administrative and Service States document. |
||
SF BER12 |
||
SD BER 1 |
||
Sets the ALS function mode. The DWDM transmitter supports ALS according to ITU-T G.644 (06/99). ALS can be disabled or can be set for one of three mode options. |
|
|
Sets the automatic in-service soak period. Double-click the time and use the up and down arrows to change settings. |
||
Sets the ProvidesSync card parameter. If checked, the card is provisioned as a NE timing reference. |
||
Sets the EnableSync card parameter. Enables synchronization status messages (S1 byte), which allow the node to choose the best timing source. |
||
Sets the Send DoNotUse card state. When checked, sends a DUS (do not use) message on the S1 byte. |
Step 5 Return to your originating procedure (NTP).
DLP-G336 Change the 10G Data Muxponder Section Trace Settings
This task changes the section trace settings for the MXP_MR_10DME_C and MXP_MR_10DME_L muxponder cards. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_MR_10DME_C or MXP_MR_10DME_L card where you want to change the section trace settings.
Step 2 Click the Provisioning > Line > Section Trace tabs. Tabs and parameter selections vary according to PPM provisioning.
Step 3 Modify any of the settings in the Section Trace tab as described in Table 11-129 .
Step 5 Return to your originating procedure (NTP).
DLP-G341 Change the 10G Data Muxponder SONET or SDH Line Thresholds
This task changes the SONET or SDH line threshold settings for the MXP_MR_10DME_C and MXP_MR_10DME_L muxponder cards. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_MR_10DME_C or MXP_MR_10DME_L card where you want to change the line threshold settings.
Step 2 Click the Provisioning > Line Thresholds > SONET Thresholds (ANSI) or SDH Thresholds (ETSI) tabs.
Step 3 Modify any of the settings as shown in Table 11-130 .
Note You must modify Near End and Far End independently; 15 Min and 1 Day independently; and Line and Section independently. To do so, choose the appropriate radio button and click Refresh.
Note In Table 11-130, some parameters and options do not apply to all MXP_MR_10DME cards. If the parameter or options do not apply, they do not appear in CTC.
Step 5 Return to your originating procedure (NTP).
DLP-G337 Change the 10G Data Muxponder Line RMON Thresholds for Ethernet, 1G FC/FICON, or ISC/ISC3 Payloads
This task changes the line threshold settings for MXP_MR_10DME_C and MXP_MR_10DME_L cards carrying Ethernet, FC/FICON, or ISC/ISC3 payloads. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), display the MXP_MR_10DME_C or MXP_MR_10DME_L card where you want to change the line threshold settings in card view.
Step 2 Click the Provisioning > Line Thresholds > RMON Thresholds tabs.
Step 3 Click Create . The Create Threshold dialog box appears.
Step 4 From the Port drop-down list, choose the applicable port, either the payload port, for example “1-1 (ONE_GE)”, or the equivalent ITU-T G.7041 GFP (Generic Frame Procedure) port.
Step 5 From the Variable drop-down list, choose an Ethernet, FC, FICON, or ISC variable. See Table 11-131 for a list of available Ethernet variables, Table 11-132 for a list of FC and FICON variables, Table 11-133 for a list of ISC and ISC3 variables, and Table 11-134 for a list of GFP variables.
Step 6 From the Alarm Type drop-down list, indicate whether the event will be triggered by the rising threshold, the falling threshold, or both the rising and falling thresholds.
Step 7 From the Sample Type drop-down list, choose either Relative or Absolute . Relative restricts the threshold to use the number of occurrences in the user-set sample period. Absolute sets the threshold to use the total number of occurrences, regardless of time period.
Step 8 Type in an appropriate number of seconds for the Sample Period.
Step 9 Type in the appropriate number of occurrences for the Rising Threshold.
For a rising type of alarm, the measured value must move from below the falling threshold to above the rising threshold. For example, if a network is running below a rising threshold of 1000 collisions every 15 seconds and a problem causes 1001 collisions in 15 seconds, the excess occurrences trigger an alarm.
Step 10 Enter the appropriate number of occurrences in the Falling Threshold field. In most cases a falling threshold is set lower than the rising threshold.
A falling threshold is the counterpart to a rising threshold. When the number of occurrences is above the rising threshold and then drops below a falling threshold, it resets the rising threshold. For example, when the network problem that caused 1001 collisions in 15 seconds subsides and creates only 799 collisions in 15 seconds, occurrences fall below a falling threshold of 800 collisions. This resets the rising threshold so that if network collisions again spike over a 1000 per 15-second period, an event again triggers when the rising threshold is crossed. An event is triggered only the first time a rising threshold is exceeded (otherwise, a single network problem might cause a rising threshold to be exceeded multiple times and cause a flood of events).
Note To view all RMON thresholds, click Show All RMON thresholds.
Step 12 Return to your originating procedure (NTP).
DLP-G338 Provision the 10G Data Muxponder Trunk Port Alarm and TCA Thresholds
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_MR_10DME_C or MXP_MR_10DME_L card where you want to change the trunk port alarm and TCA settings.
Step 2 Click the Provisioning > Optics Thresholds tabs.
Note You must modify 15 Min and 1 Day independently. To do so, choose the appropriate radio button and click Refresh.
Note Do not modify the Laser Bias parameters.
Step 3 If TCA is not selected, click TCA and then click Refresh. If it is selected, continue with Step 4.
Step 4 Verify the trunk port (Port 9) TCA thresholds are set at the values shown as follows. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and press Enter .
Step 5 Under Types, click the Alarm radio button and click Refresh .
Note Do not modify the Laser Bias parameters.
Step 6 Verify the trunk port (Port 9) Alarm thresholds are set at the values shown as follows. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and press Enter .
Step 8 Return to your originating procedure (NTP).
DLP-G339 Provision the 10G Data Muxponder Client Port Alarm and TCA Thresholds
This task provisions the client port alarm and TCA thresholds for the MXP_MR_10DME_C and MXP_MR_10DME_L cards. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_MR_10DME_C and MXP_MR_10DME_L card where you want to change the client port alarm and TCA settings.
Step 2 Click the Provisioning > Optics Thresholds tabs. The TCA thresholds are shown by default.
Step 3 Referring to Table 11-135 , verify the client ports (Ports 1 through 8) TCA thresholds for RX Power High, RX Power Low, TX Power High, and TX Power Low based on the client interface at the other end. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and hitting Enter .
Note Do not modify the Laser Bias parameters.
Note You must modify 15 Min and 1 Day independently. To do so, choose the appropriate radio button and click Refresh.
Note The hardware device that plugs into a TXP, MXP, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, or ADM-10G card faceplate to provide a fiber interface to the card is called a Small Form-factor Pluggable (SFP or XFP). In CTC, SFPs and XFPs are called pluggable port modules (PPMs). SFPs/XFPs are hot-swappable input/output devices that plug into a port to link the port with the fiber-optic network. Multirate PPMs have provisionable port rates and payloads. For more information about SFPs and XFPs, see the “SFP, SFP+, XFP, CXP, and CFP Modules” section.
Step 5 Repeat Steps 3 and 4 to provision each additional client port.
Step 6 Under Types, click the Alarm radio button and click Refresh .
Step 7 Referring to Table 11-136 , verify the client port (Ports 1 through 8) Alarm thresholds for RX Power High, RX Power Low, TX Power High, and TX Power Low based on the client interface that is provisioned. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and hitting Enter .
Step 9 Repeat Steps 7 and 8 to provision each additional client port.
Step 10 Return to your originating procedure (NTP).
DLP-G366 Change the 10G Data Muxponder OTN Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the MXP_MR_10DME_C and MXP_MR_10DME_L card where you want to change the OTN settings.
Step 2 Click the Provisioning > OTN tabs, then choose one of the following subtabs: OTN Lines , G.709 Thresholds , FEC Thresholds , or Trail Trace Identifier .
Step 3 Modify any of the settings described in Tables 11-137 through 11-140 .
Note You must modify Near End and Far End; 15 Min and 1 Day; and SM and PM independently. To do so, choose the appropriate radio button and click Refresh.
Table 11-137 describes the values on the Provisioning > OTN > OTN Lines tab.
Sets how the ODUk (client payload) is mapped to the optical channel (OTUk). |
Table 11-138 describes the values on the Provisioning > OTN > G.709 Thresholds tab.
Port13 |
||
Numeric. Can be set for Near End or Far End, for 15-minute or one-day intervals, or for SM (OTUk) or PM (ODUk). Select a bullet and click Refresh . |
||
Numeric. Can be set for Near End or Far End, for 15-minute or one-day intervals, or for SM (OTUk) or PM (ODUk). Select a bullet and click Refresh . |
||
Numeric. Can be set for Near End or Far End, for 15-minute or one-day intervals, or for SM (OTUk) or PM (ODUk). Select a bullet and click Refresh . |
||
Numeric. Can be set for Near End or Far End, for 15-minute or one-day intervals, or for SM (OTUk) or PM (ODUk). Select a bullet and click Refresh . |
||
Numeric. Can be set for Near End or Far End, for 15-minute or one-day intervals, or for SM (OTUk) or PM (ODUk). Select a bullet and click Refresh . |
Table 11-139 describes the values on the Provisioning > OTN > FEC Threshold tab.
Table 11-140 describes the values on the Provisioning > OTN > Trail Trace Identifier tab.
Step 5 Return to your originating procedure (NTP).
NTP-G293 Modify the 40G Muxponder Card Line Settings and PM Parameter Thresholds
This procedure changes the line and parameter threshold settings of the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C muxponder cards. |
|
Step 1 Complete the “DLP-G46 Log into CTC ” task at the node where you want to change the muxponder card settings. If you are already logged in, proceed to Step 2.
Step 2 Complete the G103 Back Up the Database to save the existing settings before modifying.
Step 3 Perform any of the following tasks as needed:
- G662 Change the 40G Multirate Muxponder Card Settings
- G666 Change the 40G Muxponder Line Settings
- G735 Provision the 40G Muxponder Ethernet Settings
- G667 Change the 40G Muxponder SONET (OC-192)/SDH (STM-64) Settings
- G668 Change the 40G Muxponder Section Trace Settings
- G669 Change the 40G Muxponder SONET or SDH Line Thresholds
- G670 Change the 40G Muxponder Line RMON Thresholds for Ethernet, 8G FC, or 10G FC Payloads
- G671 Provision the 40G Muxponder Trunk Port Alarm and TCA Thresholds
- G672 Provision the 40G Muxponder Client Port Alarm and TCA Thresholds
- G673 Change the 40G Muxponder OTN Settings
Note To use the Alarm Profiles tab, including creating alarm profiles and suppressing alarms, see the Alarm and TCA Monitoring and Management document.
Stop. You have completed this procedure.
DLP-G662 Change the 40G Multirate Muxponder Card Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 40G-MXP-C, or 40E-MXP-C card where you want to change the card settings.
Step 2 Click the Provisioning > Card tabs.
Step 3 Modify either of the settings described in Table 11-141 .
Step 5 Return to your originating procedure (NTP).
DLP-G666 Change the 40G Muxponder Line Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 40G-MXP-C or 40E-MXP-C card where you want to change the line settings.
Step 2 Click the Provisioning > Line > Ports tabs. Tabs and parameters vary according to the PPM provisioning.
Step 3 Modify any of the settings as described in Table 11-142 .
User-defined. This can be up to 32 alphanumeric or special characters, or both. The port name is blank by default. For information about assigning a port name, see the G104 Assign a Name to a Port. Note You can assign a port name for each fiber channel/FICON interface on the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C card, enabling the MDS Fabric Manager to associate the SAN port and a SAN port on the Cisco MDS 9000 switch. |
||
Sets the port service state unless network conditions prevent the change. For more information, see the Administrative and Service States document. |
||
(Display only) Shows the general condition of the port. Service states appear in the format: Primary State-Primary State Qualifier, Secondary State. For more information about service states, see the Administrative and Service States document. |
||
|
||
Sets the automatic in-service soak period. Double-click the time and use the up and down arrows to the change settings. |
||
Shuts down the far-end laser in response to certain defects. |
Note Squelch does not apply to ISC COMPACT payloads. Note Both Squelch and AIS options are supported when the selected Termination Mode is Transparent. If the Termination Mode selected is Section or Line, then only AIS is supported. This is applicable for OC-192/STM-64 and OC-768/STM-256. |
|
(Trunk port only) Enables or disables overclock mode on the trunk port. |
Note Before the overclock is changed, delete any existing 10G Ethernet LAN-Phy payload that is present on the 40E-MXP-C and 40ME-MXP-C cards. |
|
Step 5 Return to your originating procedure (NTP).
DLP-G735 Provision the 40G Muxponder Ethernet Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 40G Muxponder card (40G-MXP-C, 40E-MXP-C, or 40ME-MXP-C card) where you want to change the Ethernet settings. The card view appears.
Step 2 Click the Provisioning > Line > Ethernet tabs. The Ethernet tab is available once the 10G Ethernet LAN Phy payload is selected as the port rate for the pluggable port module.
Step 3 Modify any of the settings for the Ethernet tab as described in Table 11-143 .
Step 5 Return to your originating procedure (NTP).
DLP-G667 Change the 40G Muxponder SONET (OC-192)/SDH (STM-64) Settings
This task changes the SONET OC-192 or SDH STM-64 settings for the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C muxponder cards. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 40G-MXP-C, or 40E-MXP-C card where you want to change the SONET (OC-192) or SDH (STM-64) settings.
Step 2 Click the Provisioning > Line > SONET (ANSI) or SDH (ETSI). Tabs and parameters vary according to the PPM provisioning.
Step 3 Modify any of the settings described in Table 11-144 .
Assigns a logical name assigned to a port. This field is blank by default. |
User-defined. This can be up to 32 alphanumeric or special characters, or both. The port name is blank by default. For information about assigning a port name, see the G104 Assign a Name to a Port. |
|
(Display only) Displays the ProvidesSync card parameter state. |
||
Sets the EnableSync card parameter. Enables synchronization status messages (S1 byte), which allow the node to choose the best timing source. |
||
Sets the Send DoNotUse card state. When checked, sends a DUS (do not use) message on the S1 byte. |
||
(Display-only for Standard Regeneration and Enhanced FEC card configurations) Sets the mode of operation. |
Step 5 Return to your originating procedure (NTP).
DLP-G668 Change the 40G Muxponder Section Trace Settings
This task changes the section trace settings of the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C muxponder cards. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 40G-MXP-C, or 40E-MXP-C card where you want to change the section trace settings.
Step 2 Click the Provisioning > Line > Section Trace tabs. Tabs and parameter selections vary according to the PPM provisioning.
Step 3 Modify any of the settings described in Table 11-145 .
Step 5 Return to your originating procedure (NTP).
DLP-G691 Change the 40G Muxponder OTU Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 40G-MXP-C, or 40E-MXP-C card where you want to change the OTU settings.
Step 2 Click the Provisioning > Line > OTU tabs. Tabs and parameter selections vary according to the PPM provisioning.
Step 3 Modify any of the settings described in Table 11-146 .
Step 5 Return to your originating procedure (NTP).
DLP-G669 Change the 40G Muxponder SONET or SDH Line Thresholds
This task changes the SONET or SDH line threshold settings of the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C muxponder cards. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 40G-MXP-C, or 40E-MXP-C card where you want to change the line threshold settings.
Step 2 Click the Provisioning > Line Thresholds > SONET Thresholds (ANSI) or SDH Thresholds (ETSI) tabs.
Step 3 Modify any of the settings shown in Table 11-147 .
Note In Table 11-147, some parameters and options do not apply to all 40-G-MXP-C cards. If the parameter or options do not apply, they do not appear in CTC.
Step 5 Return to your originating procedure (NTP).
DLP-G670 Change the 40G Muxponder Line RMON Thresholds for Ethernet, 8G FC, or 10G FC Payloads
This task changes the line threshold settings of 40G-MXP-C, or 40E-MXP-C card carrying Ethernet, 8G FC, or 10G FC payloads. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), display the 40G-MXP-C, or 40E-MXP-C card where you want to change the line threshold settings in the card view.
Step 2 Click the Provisioning > Line Thresholds > RMON Thresholds tabs.
Step 3 Click Create . The Create Threshold dialog box appears.
Step 4 From the Port drop-down list, choose the payload port— for example “1-1 (TEN_GE)”, or the equivalent ITU-T G.7041 GFP (Generic Frame Procedure) port.
Step 5 From the Variable drop-down list, choose an Ethernet or FC variable. See Table 11-148 for a list of available Ethernet variables, Table 11-149 for a list of FC, and Table 11-149 for a list of GFP variables.
Step 6 From the Alarm Type drop-down list, choose an alarm type. The alarm type indicates whether or not an event is triggered by the type of threshold.
Step 7 From the Sample Type drop-down list, choose either Relative or Absolute . Relative restricts the threshold to use the number of occurrences in the user-set sample period. Absolute sets the threshold to use the total number of occurrences, regardless of time period.
Step 8 Enter the number of Sample Period occurrences.
Step 9 Enter the number of Rising Threshold occurrences.
To trigger the alarm, the measured value of a threshold must always move from below the falling threshold to above the rising threshold. For example, if a network moves from below a rising threshold of 1000 collisions every 15 seconds to 1001 collisions.
Step 10 Enter the appropriate number of occurrences for the Falling Threshold field. In most cases a falling threshold is set lower than the rising threshold.
A falling threshold is the exact opposite of a rising threshold. When the number of occurrences is above the rising threshold and then drops below a falling threshold, it resets the rising threshold. For example, when the network problem that caused 1001 collisions in 15 seconds subsides and creates only 799 collisions in 15 seconds, occurrences fall below a falling threshold of 800 collisions. This resets the rising threshold so that if network collisions again spike over a 1000 per 15-second period, an event again triggers when the rising threshold is crossed. An event is triggered only the first time a rising threshold is exceeded.
Step 12 Return to your originating procedure (NTP).
DLP-G671 Provision the 40G Muxponder Trunk Port Alarm and TCA Thresholds
This task changes the trunk port alarm and TCA thresholds of the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 40G-MXP-C, or 40E-MXP-C card where you want to change the trunk port alarm and TCA settings.
Step 2 Click the Provisioning > Optics Thresholds tabs.
Note You must modify 15 Min and 1 Day independently. To do so, select the appropriate radio button and click Refresh.
Note Do not modify the Laser Bias parameters.
Step 3 If TCA is not selected, click TCA and then click Refresh. If it is selected, continue with Step 4.
Step 4 Verify the trunk port (Port 5) TCA thresholds are set at the values shown as follows:
Provision new thresholds as needed by replacing the old values with new ones.
Step 5 Under Types area, click the Alarm radio button and click Refresh .
Note Do not modify the Laser Bias parameters.
Step 6 Verify the trunk port (Port 5) alarm thresholds are set at the values shown as follows:
Provision new thresholds as needed replacing the old values with new ones.
Step 8 Return to your originating procedure (NTP).
DLP-G672 Provision the 40G Muxponder Client Port Alarm and TCA Thresholds
This task provisions the client port alarm and TCA thresholds of the 40G-MXP-C, 40E-MXP-C, and 40ME-MXP-C cards. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 40G-MXP-C, or 40E-MXP-C card where you want to change the client port alarm and TCA settings.
Step 2 Click the Provisioning > Optics Thresholds tabs.
Step 3 If TCA is not selected, click TCA and then click Refresh. If it is selected, continue with Step 4.
Step 4 Referring to Table 11-151 , verify the client ports (Ports 1 through 4) TCA thresholds for RX Power High, RX Power Low, TX Power High, and TX Power Low based on the client interface at the other end. Provision new thresholds as needed by replacing the old values with new ones.
Note Do not modify the Laser Bias parameters.
Note You must modify 15 Min and 1 Day independently. To do so, select the appropriate radio button and click Refresh.
14.In CTC, SFPs, and XFPs are called pluggable port modules (PPMs). For more information about SFPs and XFPs, see the “SFP, SFP+, XFP, CXP, and CFP Modules” section. |
Step 6 Repeat Steps 3 and 4 to provision the additional client ports.
Step 7 Under Types area, click the Alarm radio button and click Refresh .
Step 8 Referring to Table 11-152 , verify the client port (Ports 1 through 8) Alarm thresholds for RX Power High, RX Power Low, TX Power High, and TX Power Low based on the client interface that is provisioned. Provision new thresholds as needed replacing the old values with new ones.
15.In CTC, SFPs and XFPs are called pluggable port modules (PPMs). For more information about SFPs and XFPs, see the “SFP, SFP+, XFP, CXP, and CFP Modules” section. |
Step 10 Repeat Steps 7 and 8 to provision additional client ports.
Step 11 Return to your originating procedure (NTP).
DLP-G673 Change the 40G Muxponder OTN Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 40G-MXP-C, or 40E-MXP-C card where you want to change the OTN settings.
Step 2 Click the Provisioning > OTN tabs, then choose one of the following subtabs: OTN Lines , ITU-T G.709 Thresholds , FEC Thresholds , or Trail Trace Identifier .
Step 3 Modify any of the settings described in Tables 11-153 through 11-156 .
Note You must modify Near End and Far End, 15 Min and 1 Day, and SM and PM independently. To do so, select the appropriate radio button and click Refresh.
Table 11-153 describes the values on the Provisioning > OTN > OTN Lines tab.
Table 11-154 describes the values on the Provisioning > OTN > G.709 Thresholds tab.
Table 11-155 describes the values on the Provisioning > OTN > FEC Threshold tab.
Table 11-156 describes the values on the Provisioning > OTN > Trail Trace Identifier tab.
Step 5 Return to your originating procedure (NTP).
NTP-G281 Manage the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Channel Group Settings
Step 1 Complete the “DLP-G46 Log into CTC ” task at the node where you want to change the channel group settings. If you are already logged in, continue with Step 2.
Step 2 Perform any of the following tasks as needed:
- G611 Create a Channel Group Using CTC
- G612 Modify the Parameters of the Channel Group Using CTC
- G613 Add or Remove Ports to or from an Existing Channel Group Using CTC
- G614 Delete a Channel Group Using CTC
- G615 Retrieve Information on Channel Group, REP, CFM, and EFM Using CTC
- G616 View Channel Group PM Parameters for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards Using CTC
- G617 View Channel Group Utilization PM Parameters for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards Using CTC
- G618 View Channel Group History PM Parameters for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards Using CTC
- DLP-G619 Create a Channel Group on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards Using PCLI
Step 3 Stop. You have completed this procedure.
DLP-G611 Create a Channel Group Using CTC
Note You can create up to 11 channel groups on the GE_XP and GE_XPE cards and up to 2 channel groups on the 10GE_XP and 10GE_XPE cards. You can create a channel group with ports only when the ports do not have any UNI QinQ settings or NNI SVLAN settings. Otherwise, the channel group will be created with empty ports.
For information about interaction of LACP with other protocols, see the “Protocol Compatibility list” section.
Step 1 Complete the “DLP-G46 Log into CTC ” task at the node where you want to create a channel group. If you are already logged in, continue with Step 2.
Step 2 Verify that the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card is installed according to the requirements specified in Table 14-7.
Step 3 Verify that the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card is installed in L2-over-DWDM mode. See the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode.
Step 4 In card view, click the Provisioning > Channel Groups tabs.
Step 5 Click Create. The Channel Group Creation dialog box appears.
Step 6 Enter the name of the channel group in the Name field.
Step 7 From the Stand Alone list, choose the ports that will belong to this channel group and click the right arrow button to move the selected ports to the Bundled list.
Step 8 From the LACP Mode drop-down list, choose the LACP mode as needed:
- On—Default mode. In this mode, the ports will not exchange LACP packets with the partner ports.
- Active—In this mode, the ports will send LACP packets at regular intervals to the partner ports.
- Passive—In this mode, the ports will not send LACP packets until the partner ports send LACP packets. After receiving the LACP packets from the partner ports, the ports will send LACP packets.
Step 9 From the LACP Hashing drop-down list, select the LACP hashing algorithm that the protocol uses to perform the load balancing task between the bundled ports.
The following hashing algorithms are supported:
- Ucast SA VLAN Incoming Port
- Ucast DA VLAN Incoming Port
- Ucast SA DA VLAN Incoming port
- Ucast Src IP TCP UDP
- Ucast Dst IP TCP UDP
- Ucast Src Dst IP TCP UDP
A new row is added in the LACP table and all the other parameters in the channel group are set to default values. The default values of these parameters are taken from the first port that is attached to the channel group.
Step 11 Return to your originating procedure (NTP).
DLP-G612 Modify the Parameters of the Channel Group Using CTC
Note Ports cannot be added or removed using this procedure. For adding or removing the ports, see the G613 Add or Remove Ports to or from an Existing Channel Group Using CTC.
Step 1 Complete the “DLP-G46 Log into CTC ” task the node where you want to modify the parameters of the channel group. If you are already logged in, continue with Step 2.
Step 2 In node view (single-shelf mode) or shelf view (multishelf view), double-click the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card where you want to modify the parameters of the channel group.
Step 3 In card view, click the Provisioning > Channel Groups tabs.
Step 4 Choose a channel group from the existing channel groups.
Step 5 Modify the channel group settings as described in Table 11-157 .
Note When you set the Committed Info Rate above 40% on 10GE_XP and 10GE_XPE cards, the Committed Burst Size and Excess Burst Size must be set to at least 32K. The Committed Burst Size and Excess Burst Size can be increased based on the packet size and Committed Info Rate value.
Step 7 Return to your originating procedure (NTP).
DLP-G613 Add or Remove Ports to or from an Existing Channel Group Using CTC
Before You Begin
- You can assign up to eight ports to a channel group on GE_XP and GE_XPE cards and up to three ports on the 10GE_XP and 10GE_XPE cards.
- You can assign the ports to a channel group only if the ports are in OOS-DSBLD admin state. The ports must not have any UNI QinQ rule or NNI SVLAN configuration.
- If the channel group is configured in UNI mode, only the UNI ports can be added to the channel group. If the channel group is configured in NNI mode, only the NNI ports can be added to the channel group.
Step 1 Complete the “DLP-G46 Log into CTC ” task at the node where you want add ports to an existing channel group. If you are already logged in, continue with Step 2.
Step 2 In node view (single-shelf mode) or shelf view (multishelf view), double-click the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card where you want to add ports to an existing channel group.
Step 3 In card view, click the Provisioning > Channel Groups tabs.
Step 4 Choose a channel group from the existing channel groups.
Step 5 Click Add/Remove Ports. The Add/Remove Ports dialog box appears.
Step 6 To add ports to an existing channel group, complete the following:
From the Stand Alone list, choose the required ports and click the right arrow button to move the selected ports to the Bundled list.
Step 7 To remove ports from an existing channel group, complete the following:
From the Bundled list, choose the required ports and click the left arrow button to move the selected ports to the Stand Alone list.
Step 9 Return to your originating procedure (NTP).
DLP-G614 Delete a Channel Group Using CTC
Step 1 Complete the “DLP-G46 Log into CTC ” task at the node where you want to delete the channel group. If you are already logged in, continue with Step 2.
Step 2 In node view (single-shelf mode) or shelf view (multishelf view), double-click the GE_XP, 10GE_XP, GE_XPE, or 10GE_XP card where you want to delete the channel group.
Step 3 In card view, click the Provisioning > Channel Groups tabs.
Step 4 Choose a channel group that you want to delete.
Step 6 Return to your originating procedure (NTP).
DLP-G615 Retrieve Information on Channel Group, REP, CFM, and EFM Using CTC
Step 1 Complete the “DLP-G46 Log into CTC ” task at the node where you want to view and retrieve information on the channel group, REP, CFM, and EFM. If you are already logged in, continue with Step 2.
Step 2 Verify that the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card is installed in L2-over-DWDM mode. See the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode.
Step 3 In card view, click the Maintenance > Show Commands tabs.
Step 4 From the Command drop-down list, choose a command.
The following commands are supported:
- ETH LACP—Displays detailed LACP information from the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE cards.
- REP TOPO—Displays the topology information for a specific REP segment.
- REP TOPO ARCHIVE—Displays the previous topology information for a specific REP segment.
- REP INTERFACE—Displays information on the REP interface status and configuration. You can retrieve detailed information for each segment by selecting Detailed from the Level drop-down list and providing the segment ID.
- OAM DISCOVERY—Displays discovery information for all the EFM interfaces or for a specific EFM interface.
- OAM SUMMARY—Displays the active EFM sessions on a device.
- OAM STATISTICS—Displays detailed information about the EFM packets.
- OAM STATUS—Displays information about the EFM configurations for all the EFM interfaces or for a specific interface.
For more information, see the Pseudo Command Line Interface Reference document.
Step 5 From the Level drop-down list, choose Normal or Detailed.
Step 6 Click Show. Depending on the command, the appropriate output appears in the text area.
Step 7 Return to your originating procedure (NTP).
DLP-G616 View Channel Group PM Parameters for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards Using CTC
This task enables you to view current statistical performance monitoring (PM) counts on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards and channel groups to detect possible performance problems. |
|
Step 1 Complete the “DLP-G46 Log into CTC ” task at the node where you want to view the channel group PM counts on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards.
Step 2 In node view (single-shelf mode) or shelf view (multishelf mode), double-click the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card where you want to view the channel group statistics. The card view appears.
Step 3 Click the Performance > Channel Groups > Statistics tabs.
Step 4 Click Refresh . Performance monitoring statistics for each channel group on the card appear in the Statistics tab.
View the PM parameter names in the Param column. The current PM parameter values appear in the Port # (CHGRP) column. For PM parameter definitions, see the Monitor Performance document.
Note To refresh, reset, or clear PM counts, see the “NTP-G73 Change the PM Display” procedure.
Return to your originating procedure (NTP).
DLP-G617 View Channel Group Utilization PM Parameters for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards Using CTC
This task enables you to view line utilization PM counts on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards and channel groups to detect possible performance problems. |
|
Step 1 Complete the “DLP-G46 Log into CTC ” task at the node where you want to view the channel group utilization PM parameters on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards.
Step 2 In node view, double-click the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card where you want to view the channel group utilization. The card view appears.
Step 3 Click the Performance > Channel Groups > Utilization tabs.
Step 4 Click Refresh . The utilization percentages for each channel group on the card appear in the Utilization tab.
View the Port # column to find the channel group you want to monitor.
The transmit (Tx) and receive (Rx) bandwidth utilization values, for the previous time intervals, appear in the Prev- n columns. For PM parameter definitions, see the Monitor Performance document.
Note To refresh, reset, or clear PM counts, see the “NTP-G73 Change the PM Display” procedure.
Return to your originating procedure (NTP).
DLP-G618 View Channel Group History PM Parameters for GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Cards Using CTC
This task enables you to view historical PM counts at selected time intervals on GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards and channel groups to detect possible performance problems. |
|
Step 1 Complete the “DLP-G46 Log into CTC ” task at the node where you want to view the channel group history PM parameters on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards.
Step 2 In node view (single-shelf mode) or shelf view (multishelf mode), double-click the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE card where you want to view the channel group history PM data. The card view appears.
Step 3 Click the Performance > Channel Groups > History tabs.
Step 4 From the Port field, choose a channel group.
Step 5 Click Refresh . Performance monitoring statistics for each channel group on the card appear in the History tab.
View the PM parameter names that appear in the Param column. The PM parameter values appear in the Prev- n columns. For PM parameter definitions, see the Monitor Performance document.
Note To refresh, reset, or clear PM counts, see the “NTP-G73 Change the PM Display” procedure.
Return to your originating procedure (NTP).
NTP-G283 Manage the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card CFM Settings
Step 1 Complete the “DLP-G46 Log into CTC ” task at the node where you want to change the CFM settings. If you are already logged in, continue with Step 2.
Step 2 Perform any of the following tasks as needed:
- G621 Enable or Disable CFM on the Card Using CTC
- G622 Enable or Disable CFM for Each Port Using CTC
- G623 Create a Maintenance Domain Profile Using CTC
- G624 Delete a Maintenance Domain Profile Using CTC
- G625 Create a Maintenance Association Profile Using CTC
- G626 Modify a Maintenance Association Profile Using CTC
- G627 Delete a Maintenance Association Profile Using CTC
- G628 Map a Maintenance Association Profile to a Maintenance Domain Profile Using CTC
- G629 Create a MEP Using CTC
- G630 Delete a MEP Using CTC
- G631 Create a MIP Using CTC
- G632 Delete a MIP Using CTC
- G633 Ping MEP Using CTC
- G634 Traceroute MEP Using CTC
- G615 Retrieve Information on Channel Group, REP, CFM, and EFM Using CTC
- DLP-G635 Enable CFM on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards Using PCLI
- DLP-G636 Create a Maintenance Domain on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards Using PCLI
- DLP-G637 Create a Maintenance Intermediate Point on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards Using PCLI
- DLP-G638 Create a Maintenance End Point on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards Using PCLI
Step 3 Stop. You have completed this procedure.
DLP-G621 Enable or Disable CFM on the Card Using CTC
Note CFM is disabled on the card by default. CFM must be enabled at both card and port levels for the CFM service to work.
For information about interaction of CFM with other protocols, see the “Protocol Compatibility list” section.
Step 1 Complete the “DLP-G46 Log into CTC ” task at the node where you want to enable or disable CFM on the card. If you are already logged in, continue with Step 2.
Step 2 Verify that the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card is installed in L2-over-DWDM mode. See the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode.
Step 3 In card view, click the Provisioning > Security tab.
Step 4 Uncheck the MAC security check box to disable MAC security.
Step 5 In card view, click the Provisioning > CFM > Configuration > Global Settings tabs.
Step 6 Check the Enable CFM check box that is present at the bottom of the screen.
Step 7 Choose the value for CC Timer field. The value can be 1 second, 10 seconds, or 1 minute.
Note Continuity Check (CC) messages are periodically exchanged between maintenance end points (MEPs). The CC Timer field is used to set the time frequency for transmission of CC messages.
Step 8 Click Apply to enable CFM on the card.
Note Uncheck the Enable CFM check box to disable CFM on the card.
Step 9 Return to your originating procedure (NTP).
DLP-G622 Enable or Disable CFM for Each Port Using CTC
This task allows you to enable or disable CFM for each port on GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards. |
|
Note CFM must be enabled at both card and port levels for the CFM service to work. However, CFM is enabled on all the ports by default.
Step 1 Complete the “DLP-G46 Log into CTC” task at the node where you want to enable or disable CFM for each port. If you are already logged in, continue with Step 2.
Step 2 Verify that the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card is installed in L2-over-DWDM mode. See the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode.
Step 3 In card view, click the Provisioning > CFM > Configuration > Global Settings tabs.
Step 4 If you want to enable CFM on a specific port, check the Enable CFM check box against that port.
Step 5 Choose the value for CC Timer field. The value can be 1 second, 10 seconds, or 1 minute.
Note Continuity Check (CC) messages are periodically exchanged between MEPs. The CC Timer field is used to set the time frequency for transmission of CC messages.
Step 6 Click Apply to enable CFM on the port.
Note Uncheck the Enable CFM check box against the port to disable CFM on the port.
Step 7 Return to your originating procedure (NTP).
Before You Begin
- You can create up to eight maintenance domain profiles on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE cards.
- The maximum number of characters for the maintenance domain profile and the maintenance association profile must not exceed 43 characters.
Step 1 Complete the “ DLP-G46 Log into CTC ” task at the node where you want to create a maintenance domain profile. If you are already logged in, continue with Step 2.
Step 2 Verify that the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card is installed in L2-over-DWDM mode. See the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode.
Step 3 In card view, click the Provisioning > CFM > Configuration > Domain Profiles tabs or in node/network view, click the Provisioning > CFM Profiles > Domain Profiles tabs.
Note Use the network view to store the domain profile on multiple nodes.
Step 5 Enter the name of the domain in the Domain Name field.
Step 6 Enter the level of the domain profile in the Level field. The range of the domain profile level is from 0 to 7.
Step 8 Choose the card slot where you want to store this domain profile and click OK.
Step 9 Return to your originating procedure (NTP).
DLP-G624 Delete a Maintenance Domain Profile Using CTC
This task allows you to delete a maintenance domain profile on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards. |
|
Step 1 Complete the “DLP-G46 Log into CTC ” task at the node where you want to delete a maintenance domain profile. If you are already logged in, continue with Step 2.
Step 2 Verify that the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card is installed in L2-over-DWDM mode. See the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode.
Step 3 In card view, click the Provisioning > CFM > Configuration > Domain Profiles tabs or in node/network view, click the Provisioning > CFM Profiles > Domain Profiles tabs.
Step 4 Select the domain profiles that you want to delete.
Step 5 Check the on Node check box.
Step 6 Click Delete Sel. row(s). The CFM Profile Deleting dialog box appears.
Step 7 Choose the card slot where you want to delete this profile and click OK. The Deleting Profile dialog box appears.
Step 8 In the Deleting Profile dialog box, click Yes.
Step 9 Return to your originating procedure (NTP).
DLP-G625 Create a Maintenance Association Profile Using CTC
This task allows you to create a maintenance association profile on GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards. |
|
Note You can create up to 1500 maintenance association profiles on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE cards.
Step 1 Complete the “DLP-G46 Log into CTC ” task at the node where you want to create a maintenance association profile. If you are already logged in, continue with Step 2.
Step 2 Verify that the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card is installed in L2-over-DWDM mode. See the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode.
Step 3 In card view, click the Provisioning > CFM > Configuration > MA Profiles tabs or in node/network view, click the Provisioning > CFM Profiles > MA Profiles tabs.
Note Use the network view to store the maintenance association profile on multiple nodes.
Step 5 Enter the name of the maintenance association in the Maintenance Profile Name field.
Step 6 Enter the VLAN ID in the VLAN ID field. The range of the VLAN ID is from 1 to 4093.
Step 7 Check the CC Enable check box to receive Continuity Check messages.
Step 9 Choose the card slot where you want to store this maintenance association profile and click OK.
Step 10 Return to your originating procedure (NTP).
DLP-G626 Modify a Maintenance Association Profile Using CTC
This task allows you to modify a maintenance association profile on GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards. |
|
Note Ensure that the maintenance association profile you want to modify is not associated with a maintenance domain profile.
Step 1 Complete the “DLP-G46 Log into CTC ” task at the node where you want to modify a maintenance association profile. If you are already logged in, continue with Step 2.
Step 2 Verify that the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card is installed in L2-over-DWDM mode. See the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode.
Step 3 In card view, click the Provisioning > CFM > Configuration > MA Profiles tabs or in node/network view, click the Provisioning > CFM Profiles > MA Profiles tabs.
Step 4 Select the maintenance association profiles that you want to modify.
Step 5 Click Modify Selected Profile(s). The Modify MA Profile dialog box appears.
Step 6 Modify the values as required and click OK.
Step 7 Return to your originating procedure (NTP).
DLP-G627 Delete a Maintenance Association Profile Using CTC
This task allows you to delete a maintenance association profile on GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards. |
|
Note Ensure that the maintenance association profile you want to delete is not associated with a maintenance domain profile.
Step 1 Complete the “DLP-G46 Log into CTC” task at the node where you want to delete a maintenance association profile. If you are already logged in, continue with Step 2.
Step 2 Verify that the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card is installed in L2-over-DWDM mode. See the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode.
Step 3 In card view, click the Provisioning > CFM > Configuration > MA Profiles tabs or in node/network view, click the Provisioning > CFM Profiles > MA Profiles tabs.
Step 4 Select the maintenance association profiles that you want to delete.
Step 5 Check the on Node check box.
Step 6 Click Delete Sel. row(s). The CFM Profile Deleting dialog box appears.
Step 7 Choose the card slot where you want to delete this profile and click OK. The Deleting Profile dialog box appears.
Step 8 In the Deleting Profile dialog box, click Yes.
Step 9 Return to your originating procedure (NTP).
DLP-G628 Map a Maintenance Association Profile to a Maintenance Domain Profile Using CTC
This task allows you to map a maintenance association profile to a maintenance domain profile on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards. |
|
Note Ensure that you have already created maintenance domain profiles and maintenance association profiles.
Step 1 Complete the “DLP-G46 Log into CTC ” task at the node where you want to map a maintenance association profile to a maintenance domain profile. If you are already logged in, continue with Step 2.
Step 2 Verify that the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card is installed in L2-over-DWDM mode. See the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode.
Step 3 In card view, click the Provisioning > CFM > Configuration > MA-Domain Mapping tabs.
Step 4 From the main drop-down list, choose a maintenance domain profile.
Step 5 Click Link MA Profiles. The Link MA Profiles dialog box appears.
Step 6 From the Available Profiles list, choose the required MA profiles and click the right arrow button to move the MA profiles to the Linked Profiles list and click OK.
Note The maintenance association profiles that are mapped with a specific maintenance domain profile must have a unique SVLAN ID.
Step 7 Return to your originating procedure (NTP).
DLP-G629 Create a MEP Using CTC
This task allows you to create a Maintenance End Point (MEP) for a given VLAN range on a specific maintenance domain. |
|
Note You can create up to 255 MEPs and MIPs on the GE_XP and 10GE_XP cards. You can create up to 500 MEPs and MIPs on the GE_XPE and 10GE_XPE cards.
Step 1 Complete the “DLP-G46 Log into CTC ” task at the node where you want to create a MEP. If you are already logged in, continue with Step 2.
Step 2 Verify that the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card is installed in L2-over-DWDM mode. See the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode.
Step 3 In card view, click the Provisioning > CFM > Configuration > MEP tabs.
Step 4 Click Create. The Create MEP dialog box appears.
Step 5 From the Port drop-down list, choose a port where you want to create the MEP.
Note CFM must be enabled on the port to create a MEP. The port must not belong to a channel group.
Step 6 From the Domain drop-down list, choose a maintenance domain.
Step 7 Enter the SVLAN ID in the Vlan Id field.
Note The specified VLAN must be configured on the selected port. The specified VLAN must also appear in the MA-Domain Mapping table.
Step 8 Enter the MP ID (identifier of the maintenance end point) in the MPID field and click OK. The range of the MP ID is from 1 to 8191.
The MP ID must not be the same between the maintenance end points.
Step 9 Return to your originating procedure (NTP).
DLP-G630 Delete a MEP Using CTC
Step 1 Complete the “DLP-G46 Log into CTC ” task at the node where you want to delete a MEP. If you are already logged in, continue with Step 2.
Step 2 Verify that the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card is installed in L2-over-DWDM mode. See the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode.
Step 3 In card view, click the Provisioning > CFM > Configuration > MEP tabs.
Step 4 Select the MEPs that you want to delete.
Step 6 Return to your originating procedure (NTP).
DLP-G631 Create a MIP Using CTC
This task allows you to create a Maintenance Intermediate Point (MIP) for a given VLAN range with a specific maintenance level. |
|
Note You can create up to 255 MEPs and MIPs on the GE_XP and 10GE_XP cards. You can create up to 500 MEPs and MIPs on the GE_XPE and 10GE_XPE cards.
Step 1 Complete the “DLP-G46 Log into CTC ” task at the node where you want to create a MIP. If you are already logged in, continue with Step 2.
Step 2 Verify that the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card is installed in L2-over-DWDM mode. See the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode.
Step 3 In card view, click the Provisioning > CFM > Configuration > MIP tabs.
Step 4 Click Create. The Create MIP dialog box appears.
Step 5 From the Port drop-down list, choose a port where you want to create the MIP.
Note The port must not belong to a channel group.
Step 6 From the Level drop-down list, choose a maintenance level. The range of the maintenance level is from 0 to 7.
Step 7 Enter the SVLAN range in the Vlan range field. The range of the SVLAN is from 1 to 4093.
Note The specified SVLAN must be configured on the selected port.
Step 9 Return to your originating procedure (NTP).
DLP-G632 Delete a MIP Using CTC
Step 1 Complete the “ DLP-G46 Log into CTC ” task at the node where you want to delete a MIP. If you are already logged in, continue with Step 2.
Step 2 Verify that the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card is installed in L2-over-DWDM mode. See the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode.
Step 3 In card view, click the Provisioning > CFM > Configuration > MIP tabs.
Step 4 Select the MIPs that you want to delete.
Step 6 Return to your originating procedure (NTP).
This task allows you to display the output of the ping command on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards. |
|
Step 1 Complete the “ DLP-G46 Log into CTC ” task at the node where you want to ping MEP. If you are already logged in, continue with Step 2.
Step 2 Verify that the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card is installed in L2-over-DWDM mode. See the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode.
Step 3 In card view, click the Provisioning > CFM > Ping tabs.
Step 4 Enter the MP ID value in the MPID field. The range of the MP ID is from 1 to 8191.
Note Remote MP ID user cannot ping local MP ID.
Step 5 (Optional) Enter the MAC address of the remote maintenance point in the Mac Addr field. The format of MAC address is abcd.abcd.abcd.
Step 6 Enter the SVLAN ID in the VLAN ID field. The range of the SVLAN ID is from 1 to 4093.
Step 7 Enter the domain name in the Domain Name field.
Step 8 Enter the size of the ping packet in the DataGram Size field. The default value is 100.
Step 9 Enter the number of ping packets in the No of Requests field. The default value is 5.
Step 10 Click Ping. The output of the ping command appears in the Ping Response area.
Step 11 Return to your originating procedure (NTP).
DLP-G634 Traceroute MEP Using CTC
This task allows you to display the output of the traceroute command on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards. |
|
Step 1 Complete the “ DLP-G46 Log into CTC ” task at the node where you want to view the output of the traceroute command. If you are already logged in, continue with Step 2.
Step 2 Verify that the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card is installed in L2-over-DWDM mode. See the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode.
Step 3 In card view, click the Provisioning > CFM > Traceroute tabs.
Step 4 Enter the remote MP ID value in the MPID field. The range of the MP ID is from 1 to 8191.
Step 5 (Optional) Enter the MAC address of the remote maintenance point in the Mac Addr field. The format of MAC address is abcd.abcd.abcd.
Step 6 Enter the SVLAN ID in the VLAN ID field. The range of the SVLAN ID is from 1 to 4093.
Step 7 Enter the domain name in the Domain Name field.
Step 8 Click TraceRoute Response.
The output of the traceroute command appears in the TraceRoute Response area.
- Verify the RlyHit message is shown in the traceroute display and LTM reaches a maintenance point whose MAC address matches the target MAC address.
- Verify the RlyFDB message is shown in the traceroute display when the next hop address is found in the forwarding database.
- Verify the RlyMPDB message is shown in the traceroute display when the next hop address is found in the CCDN.
Step 9 Return to your originating procedure (NTP).
NTP-G285 Manage the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card EFM Settings
Step 1 Complete the “ DLP-G46 Log into CTC ” task at the node where you want to change the EFM settings. If you are already logged in, continue with Step 2.
Step 2 Perform any of the following tasks as needed:
- G639 Enable or Disable EFM for Each Port Using CTC
- G640 Configure EFM Parameters Using CTC
- G641 Configure EFM Link Monitoring Parameters Using CTC
- G642 Enable Remote Loopback for Each Port Using CTC
- G615 Retrieve Information on Channel Group, REP, CFM, and EFM Using CTC
- DLP-G643 Enable EFM on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards Using PCLI
Stop. You have completed this procedure.
Before You Begin
- You can enable EFM on both UNI and NNI ports.
- You cannot enable or disable EFM for ports that belong to a channel group.
- For information about interaction of EFM with other protocols, see the “Protocol Compatibility list” section.
Step 1 Complete the “ DLP-G46 Log into CTC ” task at the node where you want to enable or disable EFM for each port. If you are already logged in, continue with Step 2.
Step 2 Verify that the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card is installed in L2-over-DWDM mode. See the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode.
Step 3 In card view, click the Provisioning > EFM > Configuration tabs. The EFM details appear for each port.
Step 4 From the EFM State drop-down list, choose Enabled.
Step 5 Click Apply to enable EFM for that port.
Note From the EFM State drop-down list, choose Disabled to disable EFM for that port.
Step 6 Return to your originating procedure (NTP).
DLP-G640 Configure EFM Parameters Using CTC
Step 1 Complete the “ DLP-G46 Log into CTC ” task at the node where you want to configure EFM parameters. If you are already logged in, continue with Step 2.
Step 2 Verify that the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card is installed in L2-over-DWDM mode. See the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode.
Step 3 In card view, click the Provisioning > EFM > Configuration tabs.
Step 4 Modify the EFM parameter settings as described in Table 11-158 .
Step 5 Click Apply to save the changes.
Step 6 Return to your originating procedure (NTP).
DLP-G641 Configure EFM Link Monitoring Parameters Using CTC
This task allows you to configure EFM link monitoring parameters for each port on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards. |
|
Step 1 Complete the “ DLP-G46 Log into CTC ” task at the node where you want to configure EFM link monitoring parameters. If you are already logged in, continue with Step 2.
Step 2 Verify that the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card is installed in L2-over-DWDM mode. See the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode.
Step 3 In card view, click the Provisioning > EFM > Link Monitoring tabs.
Step 4 Modify the EFM link monitoring parameter settings as described in Table 11-159 .
Step 5 Click Apply to save the changes.
Step 6 Return to your originating procedure (NTP).
DLP-G642 Enable Remote Loopback for Each Port Using CTC
This task allows you to enable remote loopback for each port on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards. |
|
Step 1 Complete the “ DLP-G46 Log into CTC ” task at the node where you want to enable the remote loopback for each port. If you are already logged in, continue with Step 2.
Step 2 Verify that the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card is installed in L2-over-DWDM mode. See the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode.
Step 3 In card view, click the Provisioning > EFM > Loopback tabs.
The remote loopback type details appear for each port.
Step 4 From the Remote Loopback Type drop-down list, choose Remote Loopback.
Step 5 Click Apply to save the changes.
Step 6 Return to your originating procedure (NTP).
NTP-G287 Manage the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card REP Settings
Step 1 Complete the “ DLP-G46 Log into CTC ” task at the node where you want to change the REP settings. If you are already logged in, continue with Step 2.
Step 2 Perform any of the following tasks as needed:
- G713 Provision Administrative VLAN for Ports in a REP Segment Using CTC
- G645 Create a Segment Using CTC
- G646 Edit a Segment Using CTC
- G647 Activate VLAN Load Balancing Using CTC
- G648 Deactivate VLAN Load Balancing Using CTC
- G615 Retrieve Information on Channel Group, REP, CFM, and EFM Using CTC
- DLP-G649 Create a Segment on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards Using PCLI
- DLP-G650 Configure STCN on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards Using PCLI
- DLP-G651 Configure Preemption Delay on the Primary Edge Port Using PCLI
Stop. You have completed this procedure.
DLP-G713 Provision Administrative VLAN for Ports in a REP Segment Using CTC
This task allows you to provision administrative VLAN for NNI and UNI ports in a REP segment on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards. |
|
Note One administrative CVLAN and one administrative SVLAN can be provisioned for each card. The REP segments using NNI ports send Hardware Flood Layer (HFL) messages using the administrative SVLAN. The REP segments using UNI ports send HFL messages using the administrative CVLAN. The two VLANs need not be the same.
Step 1 Complete the DLP-G46 Log into CTC task at the node where you want to provision administrative VLAN. If you are already logged in, continue with Step 2.
Step 2 Verify that the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card is installed in L2-over-DWDM mode. See G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode.
Step 3 In card view, click the Provisioning > REP > Admin VLAN Configuration tabs.
Step 4 To provision administrative VLAN for NNI ports in a REP segment, perform the following steps:
a. From the SVLAN drop-down list, choose a SVLAN. The following table describes the REP convergence time for SVLANs.
c. To associate the chosen SVLAN with the NNI ports, see G382 Add and Remove SVLANS to/from GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE NNI Ports.
Step 5 To provision administrative VLAN for UNI ports in a REP segment, perform the following steps:
a. Enter the CVLAN in the CVLAN field.
c. To associate the CVLAN with the UNI ports, see G384 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE QinQ Settings.
Step 6 Return to your originating procedure (NTP).
Before You Begin
- You can create up to three segments on a card. Each segment can have up to two ports on the same switch.
- You must configure the REP administrative VLAN to activate the Hardware Flood Layer (HFL).
- Before creating REP segments, you must configure the administrative VLAN or use the default VLAN 1 and add the ports to the segment. Only one SVLAN can be configured per card for all the three segments. REP uses the administrative VLAN to flood its own control traffic.
- The administrative CVLAN is required if a REP port is configured as a UNI port. However, the REP ports are configured as NNI ports in many configurations, and hence the administrative CVLAN is not required in these configurations. The option to configure the administrative CVLAN is present in CTC.
- You must configure two edge ports in the segment. A segment has only one primary edge port. If you configure two ports in a segment as the primary edge port, for example, ports on different switches, REP selects one of the ports to serve as the primary edge port based on port priority.
- If REP is enabled on two ports on a switch, both the ports must be either regular ports or edge ports. However, if the No-neighbor port is configured, one port can be an edge port and another port can be a regular port.
- You can also optionally configure where to send segment topology change notifications (STCNs) and VLAN load balancing (VLB). STCNs are enabled only for primary edge ports. VLB configurations are enabled on any edge ports.
- For information about interaction of REP with other protocols, see the “Protocol Compatibility list” section.
Step 1 Complete the “ DLP-G46 Log into CTC ” task at the node where you want to create a segment. If you are already logged in, continue with Step 2.
Step 2 Verify that the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card is installed in L2-over-DWDM mode. See the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode.
Step 3 In card view, click the Provisioning > REP > Segment tabs.
Step 4 Click Create. The Create Segment wizard appears.
Step 5 Enter the segment ID in the Segment field. The range of the segment ID is from 1 to 1024.
Step 6 From the Port drop-drown list, choose a REP port that must belong to this segment.
Note A REP port can belong to only one segment.
Step 7 From the Port Role area, choose whether you want to configure the port as an edge port or a regular port. The options are:
a. Edge—The port is configured as an edge port.
- Check the Primary check box to configure the edge port as a primary edge port. A segment can have only one primary edge port.
Note If an edge port is configured as primary edge port, the other edge port in the ring automatically becomes secondary edge port. If neither edge port is configured as primary edge port, one edge port is automatically selected as primary edge port, and the other edge port is secondary edge port. Configuring an edge port as a primary edge port is not mandatory. However, it is recommended since VLAN load balancing must be configured on the node with the primary edge port.
- Uncheck the Primary check box to configure the edge port as a secondary edge port.
- (Optional) Check the Preferred check box to configure the regular or edge port as a preferred alternate port (alternate to primary edge port). This port blocks a range of SVLANs for VLAN load balancing. There is no limit on the number of preferred ports in a REP ring. The preferred port, if configured, is relevant even without VLAN load balancing, as it takes priority over non-preferred ports for alternate port election.
Note Configuring a port as preferred does not ensure that it becomes the alternate port; it only gets preference over the other ports that are not configured as preferred when an alternate port is elected.
- Check the NoNeighbor check box if the edge port must not have a neighbor port. REP does not check for neighbor adjacency.
Note When the NoNeighbor check box is checked, ensure that only one segment is created.
b. None—The port is configured as a regular port. If you choose this option, Segment Topology Change Notifications (STCN) and VLAN Load Balancing (VLB) configurations are disabled.
Check the Preferred check box to configure the regular port as a preferred alternate port.
Step 8 From the STCN area, configure the destination of STCN messages:
a. Check the Enable check box to enable sending STCN messages.
b. From the Port drop-down list, choose the STCN port to send STCN messages or enter the segment ID in the Segment field to send STCN messages. The STCN port and REP port must be unique.
Step 9 From the VLAN Load Balancing area, configure VLAN Load Balancing on the primary edge port:
a. Check the Enable check box to enable VLB.
b. Enter a single SVLAN or range of SVLANs in the SVLAN field. These SVLANs are blocked at the alternate ports. The primary edge port blocks the remaining VLANs.
c. Enter the Rep PortId in the Rep PortId field to identify the VLAN blocking alternate port. This unique port ID is automatically generated when REP is enabled.
d. Check the Preferred check box to select the segment port previously identified as the preferred alternate port for VLAN load balancing.
When you check Preferred under VLAN Load Balancing area, you configure VLAN load balancing to use one of the previously configured preferred ports (under the Port Role area) to be the load balancing port. This restricts the load balancing port to be one among the preferred ports, but you cannot select a specific preferred port.
Step 10 From the VLB Preempt Delay area, enter the trigger delay for automatic VLB activation. The range is 15 to 300 seconds.
Step 12 Enter the details of the second port to add it to the segment.
Repeat Step 6 to 10 when the first port is configured as a regular port and the second port is configured as a primary edge port. Repeat Step 6 to 7 when the first port is configured as a primary edge port and the second port is configured as a regular port.
Step 14 Return to your originating procedure (NTP).
DLP-G646 Edit a Segment Using CTC
Note You can edit only the STCN and VLB entries for a segment.
Step 1 Complete the “ DLP-G46 Log into CTC ” task at the node where you want to edit a segment. If you are already logged in, continue with Step 2.
Step 2 Verify that the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card is installed in L2-over-DWDM mode. See the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode.
Step 3 In card view, click the Provisioning > REP > Segment tabs. The list of segments appear.
Step 4 Choose a segment from the list of segments.
Step 6 Modify the values as required and click Finish.
Step 7 Return to your originating procedure (NTP).
DLP-G647 Activate VLAN Load Balancing Using CTC
This task allows you to activate VLAN load balancing on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards. |
|
Note When VLAN load balancing is activated, the default configuration is manual preemption with the delay timer disabled.
Step 1 Complete the “ DLP-G46 Log into CTC ” task at the node where you want to activate VLAN load balancing. If you are already logged in, continue with Step 2.
Step 2 Verify that the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card is installed in L2-over-DWDM mode. See the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode.
Step 3 In card view, click the Provisioning > REP > Segment tabs. The list of segments appear.
Step 4 Choose a segment from the list of segments.
Step 6 Return to your originating procedure (NTP).
DLP-G648 Deactivate VLAN Load Balancing Using CTC
This task allows you to deactivate VLAN load balancing on the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards. |
|
Step 1 Complete the “ DLP-G46 Log into CTC ” task at the node where you want to deactivate VLAN load balancing. If you are already logged in, continue with Step 2.
Step 2 Verify that the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card is installed in L2-over-DWDM mode. See the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode.
Step 3 In card view, click the Provisioning > REP > Segment tabs. The list of segments appear.
Step 4 Choose a segment from the list of segments.
Step 6 Return to your originating procedure (NTP).
NTP-G165 Modify the GE_XP, 10GE_XP, GE_XPE, 10GE_XPE Cards Ethernet Parameters, Line Settings, and PM Thresholds
This procedure changes Ethernet, line, and PM threshold settings for the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards. |
|
G179 Install the TXP, MXP, AR_MXP, AR_XP, AR_XPE, 100G-LC-C, 10x10G-LC, CFP-LC, WSE, ADM-10G, and OTU2_XP Cards |
|
Step 1 Complete the “ DLP-G46 Log into CTC ” task at the node where you want to change the card settings. If you are already logged in, continue with Step 2.
Step 2 As needed, complete the G103 Back Up the Database to preserve the existing transmission settings.
a. Display the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE card in card view.
b. Click the Provisioning > Card tabs.
c. Verify that the card mode is set to the mode designated by your site plan:
– L2-over-DWDM (GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE)
– 10GE TXP (10GE_XP or 10 GE_XPE)
If the card mode is set correctly, continue with Step 4 . If not, complete the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode.
Step 4 Complete the G380 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Ethernet Settings.
Step 5 If the d in the GE_XPE card, complete the following tasks, as needed.
Step 6 If the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card mode is L2-over-DWDM, complete the following tasks, as needed. If the card mode is not L2-over-DWDM, continue with Step 7.
- G381 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Layer 2 Protection Settings
- G421 Create and Store an SVLAN Database
- G382 Add and Remove SVLANS to/from GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE NNI Ports
- G383 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Quality of Service Settings
- G384 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE QinQ Settings
- G205 Enable Link Integrity on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards.
- G385 Provision the MAC Filter Settings for GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Card
- G204 Enable IGMP Snooping on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards or NTP-G220 Enable IGMP Snooping on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards Using PCLI .
- G206 Enable MVR on a GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Card or NTP-G224 Enable MVR on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards Using PCLI .
- G460 Enable MAC Address Learning on SVLANs for GE_XPE or 10GE_XPE Cards Using CTC or NTP-G226 Enable MAC Address Learning on SVLANs for GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards Using PCLI .
Step 7 Complete the following tasks, as needed:
Note To use the Alarm Profiles tab, including creating alarm profiles and suppressing alarms, see the Alarm and TCA Monitoring and Management document.
Stop. You have completed this procedure.
DLP-G380 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Ethernet Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card where you want to change the Ethernet settings. The card view appears.
Step 2 Click the Provisioning > Ether Ports > Ethernet tabs.
Step 3 Modify any of the settings for the Ethernet tab as described in Table 11-161 . The parameters that appear depend on the card mode.
(Display only) The Port number ( n - n ) and rate (GE or TEN_GE). |
|||
The maximum size of the Ethernet frames accepted by the port. The port must be in OOS/locked state. |
|||
Sets the Ethernet mode. The port must be in OOS/locked state before setting the card mode. Note For GE_XP and GE_XPE cards that are in Y-cable protection groups, Mode must be set to 1000 Mbps for those client ports that are configured in Y-cable. |
Note If Mode is set to Auto on the GE_XP or GE_XPE port, autonegotiation gets enabled on the peer port. Note On GE_XP card, the copper Pluggable Port Module (PPM) interface can auto-negotiate and carry traffic even when the peer interface operates at rates other than 1000 Mbps. |
||
Enables/disables flow control messaging with its peer port. When enabled, the port can send and receive PAUSE frames when buffer congestion occurs. When disabled, no PAUSE frames are transmitted and the PAUSE frames received are discarded. Note Flow control messaging is symmetric and not negotiated. When flow control is enabled on one port, the other end of the link (peer port) is not considered. That is, even if flow control is disabled on the peer port, the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card will send PAUSE frames. |
|||
Note PROV-MISMATCH alarm is raised if the Media Type is not set to Ethernet Over DS1 (ANSI) or Ethernet Over E1 (ETSI) for ONS-SC-EOP1,Ethernet Over DS3 (ANSI) or Ethernet Over E3 (ETSI) for ONS-SC-EOP3, or DS1 Over Ethernet (ANSI) or E1 Over Ethernet (ETSI) for ONS-SC-E1-T1-PW or DS3 Over Ethernet (ANSI) or E3 Over Ethernet (ETSI) ONS-SC-E3-T3-PW. Set the correct Media Type to clear the PROV-MISMATCH alarm. |
|||
Sets the guaranteed information rate based on the service-level agreement of the service provider. The port must be in OOS/locked state. |
|||
Sets the maximum number of bits that will be transferred per second. The port must be in OOS/locked state before the Committed Burst Size is provisioned. |
|||
The maximum number of bits that are credited for later transfer in the event the committed burst rate cannot be transmitted. The port must be in OOS/locked state before the Excess Burst Size is provisioned. |
|||
Sets the port network interface mode (NIM). This parameter classifies port types designed for the Metro Ethernet market to simplify deployment, management, and troubleshooting. The port must be in OOS/locked state before the NIM is provisioned. |
|||
Enables Quality of Service (QoS) on the port’s egress or output queues. The port must be in OOS/locked state before the Egress QoS is provisioned. |
|||
Enables or disables MAC learning for the port on GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards. MAC learning is used by Layer 2 switches to learn the MAC addresses of network nodes so the Layer 2 switches send traffic to the right location. Layer 2 switches, including the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards in L2-over-DWDM mode with MAC Learning configured, maintain a MAC learning table that associates the MAC addresses and VLANs with a given port. Note MAC addresses on SVLANs attached to the port must also be enabled to provision MAC address learning on GE_XPE and 10GE_XPE cards. Note MAC address table aging is 300 seconds. It cannot be changed. |
|||
Provisions the IEEE 802.1p ingress Class of Service (CoS). The CoS .1p bits set the Ethernet frame priority. The port must be in OOS/locked state before the Ingress CoS is provisioned. Ingress CoS is used to set the priority of the Ethernet frame in the service provider network, This parameter is used to set the CoS.1p bits in the SVLAN tag. Ingress CoS applies only to ports provisioned as UNI mode. It does not apply to ports provisioned as NNI mode. |
If CVLAN CoS is configured on a GE_XP or a 10GE_XP card, a PROV-MISMATCH alarm is raised. Until this alarm is cleared, provisioning on the card is not possible. The CVLAN CoS configuration takes effect only after QinQ is configured. |
||
Defines the inner Ethertype field. The Ethertype field indicates which protocol is being transported in an Ethernet frame. The inner Ethertype applies to ports provisioned in UNI mode only. It does not apply to ports provisioned as NNI mode. The ports must be OOS/locked before the inner Ethertype is provisioned. |
|||
Defines the outer Ethertype field. The Ethertype field identifies which protocol is being transported in an Ethernet frame. The ports must be OOS/locked before the Outer Ethertype is provisioned. Note The PROV-MISMATCH alarm is raised on GE_XPE and 10GE_XPE cards if more than four different Outer Ethertype options are configured per card. |
|||
Adds multicast-capable ports to the forwarding table for every IP multicast. |
|||
Configures the standby port behavior. Set Protection Action to None if Media Type is set to Ethernet Over DS1 (ANSI) or Ethernet Over E1 (ETSI) for ONS-SC-EOP1, Ethernet Over DS3 (ANSI) or Ethernet Over E3 (ETSI) for ONS-SC-EOP3, or DS1 Over Ethernet (ANSI) or E1 Over Ethernet (ETSI) for ONS-SC-E1-T1-PW or DS3 Over Ethernet (ANSI) or E3 Over Ethernet (ETSI) for ONS-SC-E3-T3-PW. |
Table 11-162 shows the inner and outer Ethertype behavior based on the NIM setting (either NNI mode or UNI mode). When the NIM is set to UNI, and the QinQ mode is set to Selective, the Ethertype behavior depends on the SVLAN/CVLAN operation that is provisioned, either Add or Translate. (QinQ parameters are provisioned in the G384 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE QinQ Settings.)
Note A packet can exit out of any UNI/NNI port if the outermost tag in the packet matches with the SVLAN provisioned on that port. In other words, in the egress path, the inner tags (even if present) of the packet are not matched with the inner SVLAN or CVLAN provisioned on the port.
Note The Committed Burst Size and Excess Burst Size must be configured based on the expected packet size to ensure that no packets are dropped when Flow Control is enabled. For example, if the CIR is 40% and packet size is 1 KB, the Committed Burst Size and Excess Burst Size should be set to 1 MB.
Note When you set the Committed Info Rate above 40% on 10GE_XP and 10GE_XPE cards, the Committed Burst Size and Excess Burst Size must be set to at least 32K. The Committed Burst Size and Excess Burst Size can be increased based on the packet size and Committed Info Rate value.
Step 5 Return to your originating procedure (NTP).
DLP-G684 Provision the GE_XPE Card PDH Ethernet Settings
This task changes the PDH Ethernet settings for the GE_XPE card. |
|
|
|
Note The Provisioning > Ether Ports > PDH Ethernet Parameters tab is available in GE_XPE card view only, provided the PPM for GE_XPE port is created in FE mode.
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the GE_XPE card where you want to change the PDH Ethernet settings. The card view appears.
Step 2 Click the Provisioning > Ether Ports > PDH Ethernet Parameters tabs. The PDH Ethernet Parameters tab appear only when the d.
Step 3 Modify any of the settings for the PDH Ethernet Parameters tab as described in Table 11-163 .
Table 11-164 provides jitter buffer values for different payloads. Note The traffic is down if the jitter buffer is set to >=192000 when Media Type is set to DS1 over Ethernet (ANSI) ONS-SC-E1-T1-PW) and E1 Over Ethernet (ETSI) ONS-SC-E1-T1-PW). |
|||
Step 5 Return to your originating procedure (NTP).
DLP-G685 Provision the GE_XPE Card Electrical Lines Settings
This task changes the Electrical Lines settings for the GE_XPE card. |
|
|
|
Note The Provisioning > Ether Ports > Electrical Lines tab is available in GE_XPE card view only, provided the PPM for GE_XPE port is created in FE mode.
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the GE_XPE card where you want to change the Electrical Lines settings. The card view appears.
Step 2 Click the Provisioning > Ether Ports > Electrical Lines tabs. The Electrical Lines tab appear only when the d.
Step 3 Modify any of the settings for the Electrical Lines > DS1 or Electrical Lines > DS3 tab as described in Table 11-165 .
Step 5 Return to your originating procedure (NTP).
DLP-G381 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Layer 2 Protection Settings
This task provisions the Layer 2 protection settings for the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards when the cards are provisioned in L2-over-DWDM mode. |
|
Note To perform this task, the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card must be in L2-over-DWDM mode. To change the card mode, complete the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode.
Note GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Layer 2 protection settings must be planned for the entire VLAN ring. One card in the ring is provisioned as the master card and one of its port is set to Blocking. The master card coordinates the protection switching for the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE in a VLAN ring.
Note You can choose to enable another card in the ring to be the master card. However, only one card in the ring can be provisioned as master card. Make sure that the provisioning settings on the card that was previously configured as the master are disabled as soon as another card is enabled as the master card. To perform this task complete the G507 Enable a Different GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Card as the Master Card
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card where you want to change the protection settings. The card view appears.
Step 2 Click the Provisioning > Protection tabs.
Step 3 In the Status column, modify the port protection status by clicking the appropriate table cell and choosing one of the following from the drop-down list:
Note One port of the master card within a VLAN ring must be set to Blocking. All other ports must be set to Forwarding.
Step 4 Check the Master check box if you want the card to serve as the protection coordinator for the VLAN ring. If not, continue with Step 5.
Step 5 From the Protection drop-down list, choose one of the following:
- Enabled—Enables protection.
- Disabled—Disables protection.
- Forced—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.
Step 6 From the Hold Off Time drop-down list, choose one of the following:
Note To get consistent results ensure Hold Off Time values are the same throughout the ring.
Note FAPS is an Layer 2 protection enabled on a VLAN. When a fiber fault occurs, Layer 1 protection is triggered immediately to restore the traffic. Setting the Hold Off Time option prevents Layer 2 FAPS protection from triggering at the same time as Layer 1 protection thereby avoiding traffic hits.
Step 7 Set the following parameters for FAPS switching with CRC errors:
a. Switch with CRC Alarm—Check this check box to enable FAPS switching with CRC errors.
b. CRC Threshold—Threshold for CRC error count. The default CRC threshold value is 10(-e)2. The available options are 10(-e)2, 10(-e)3, and 10(-e)4.
c. CRC Soak Count—Number of times the CRC error rate exceeds the CRC threshold value before raising the DATA-CRC alarm. The default CRC Soak Count is 10. The valid range is from 3 to 10.
d. CRC Poll Interval—Time interval (in seconds) between the successive polls. The default CRC Poll Interval is 60 seconds.
For example, if the CRC Threshold value = 10(-e)2, CRC Soak Count = 10, and CRC Poll Interval = 60 seconds, then FAPS occurs when the incoming CRC error rate is more than 10(-e)2 continuously across 10 poll intervals (10*60 = 600 seconds).
e. Clear/Suppress CRC Alarm—Uncheck the Clear/Suppress CRC Alarm check box for FAPS to occur. If you check this check box, the DATA-CRC alarm gets cleared and FAPS does not occur.
Note As along as the Clear/Suppress CRC Alarm checkbox is checked, the DATA-CRC alarm is not raised on that port and FAPS does not occur.
Note For consistent result, ensure that all the values that are set in Step 7 are same throughout the ring.
Step 9 Return to your originating procedure (NTP).
DLP-G507 Enable a Different GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Card as the Master Card
This task provisions another GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card on a stable VLAN ring, to be the master card when the cards are provisioned in L2-over-DWDM mode. |
|
G381 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Layer 2 Protection Settings |
|
Note To perform this task, the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card must be in L2-over-DWDM mode. To change the card mode, complete the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode.
Note GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Layer 2 protection must be enabled for the entire VLAN ring. One card in the ring is provisioned as the master card and one of its port is set to Blocking. The master card coordinates the protection switching for the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE cards in a VLAN ring.
Note You can choose to enable another card in the ring to be the master card. However, only one card in the ring can be provisioned as master card. Make sure that the provisioning settings on the card that was previously configured as the master are disabled as soon as another card is enabled as the master card.
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card in a VLAN ring where you want to enable master card provisioning. The card view appears. Perform the following steps:
a. Click the Provisioning > Protection tabs.
b. From the Status drop-down list, choose Blocking for a trunk port.
Note One port of the master card within a VLAN ring must be set to Blocking. All other ports must be set to Forwarding.
c. Check the Master check box for the card that serves as the protection coordinator for the VLAN ring.
d. From the Protection drop-down list, choose Enabled .
Step 2 The master card provisioning on the other card must be disabled. Perform the following steps:
a. Click the Provisioning > Protection tabs.
b. Uncheck the Master check box for the card where Master node provisioning must be disabled.
d. From the Protection drop-down list, choose Disabled .
Step 3 The protection on the card that was disabled in Step 2 must be enabled again. Perform the following steps:
a. Click the Provisioning > Protection tabs.
b. From the Protection drop-down list, choose Enabled .
d. From the Status drop-down list, choose Forwarding on both ports.
Step 4 Return to your originating procedure (NTP).
DLP-G382 Add and Remove SVLANS to/from GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE NNI Ports
Note To perform this task, the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card must be in L2-over-DWDM mode. To change the card mode, complete the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode.
Note This task can only be performed on ports provisioned as NNI. See the G380 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Ethernet Settings.
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card where you want to change the SVLAN port settings. The card view appears.
Step 2 Click the Provisioning > SVLAN tabs.
Step 3 For each SVLAN shown in the table, click the check box under the Port [ port name ] table cell to include the SVLAN in that port. If you do not want the SVLAN included, uncheck the check box.
Note If no SVLANs appear in the SVLAN tab, complete the G421 Create and Store an SVLAN Database.
Step 5 Return to your originating procedure (NTP).
DLP-G383 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Quality of Service Settings
This task provisions the Weighted Round Robin (WRR) value and bandwidth for QoS Class of Service (CoS) egress queues on a GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE card port. |
|
Note To perform this task, the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card must be in L2-over-DWDM mode and the port must have QoS enabled. Refer to the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode and the G380 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Ethernet Settings, if needed.
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card where you want to change the QoS settings.
Step 2 Click the Provisioning > QoS tabs.
Step 3 In the Port field at the bottom of the window, choose the port where you want to provision the QoS settings.
Step 4 For each CoS egress queue, 0 through 7, define the following:
Note The GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE define a set of eight queues, one queue for each CoS. Only one of the queues can be assigned the 0 WRR weight (Strict Priority).
Step 5 Click Apply . Click Yes in the confirmation dialog box.
Step 6 Return to your originating procedure (NTP).
DLP-G470 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Class of Service (CoS) Settings
This task provisions Class of Service (CoS) settings on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card. |
|
Note To perform this task, the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE card must be in L2-over-DWDM mode and the port must be in OOS state.
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card where you want to change the CoS settings.
Step 2 Complete the following task:
- Refer to Ingress CoS section in the G380 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Ethernet Settings
Step 3 Return to your originating procedure (NTP).
DLP-G384 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE QinQ Settings
Note To perform this task, the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE must be in L2-over-DWDM mode. To change the card mode, complete the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode.
Note This task can only be performed on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE cards UNI ports. (To provision the port Ethernet parameters, see the G380 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Ethernet Settings.)
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card where you want to change the QinQ settings.
Step 2 Click the Provisioning > QinQ tabs.
Step 3 Click the Port field and choose the port where you want to provision QinQ.
Channel groups configured in UNI mode appear in the Port field along with the physical ports.
Step 4 Click the Mode field and choose one of the following modes from the drop-down list:
- Selective—The incoming Ethernet packet is checked against the CVLAN and SVLAN table. If the CVLAN is not found, the packet is dropped. If you choose Selective, add an entry in the QinQ tab to map the administrative CVLAN to the SVLAN (if it is not same as the one used for data).
- Transparent—All incoming packets are transported with the additional VLAN chosen in the SVLAN field. If you choose transparent, the traffic on administrative CVLAN will pass through.
Step 5 Click the BPDU field and choose one of the following bridge protocol data unit (BPDU) modes from the drop-down list:
– 01-80-c2-00-00-00—IEEE 802.1D
– 01-80-c2-00-00-02—Link Aggregation Control Protocol (LACP)
– 01-80-0c-cc-cc-cc—VLAN Spanning Tree Plus (PVST+)
– 01-00-c-cc-cc-cc—Cisco Discovery Protocol (CDP) type 0x2000, VLAN Trunk Protocol (VTP) type 0x2003, Port Aggregation Protocol (PAgP), type 0x0104, Uni-Directional Link Detection (UDLD) type 0x111, Dynamic Trunking Protocol (DTP) type 0x2004
Step 6 If the Mode was set to Selective, complete the following steps. If not, continue with Step 7.
b. Click the CVLAN table and type in the CVLAN range. You can enter a single value or a range using “–” between the two ends of the range.
Note If you are using Software Release 8.5 or earlier, it is recommended that you do not specify a CVLAN range due to certain limitations in the feature.
c. Click the SVLAN table cell and choose an SVLAN from the drop-down list.
d. Click the Operation table cell and choose an operation:
– Add (default)—Adds the SVLAN on top of the CVLAN. The operation default can be applied for any UNI port.
– Translate—CVLAN is translated with the SVLAN value.
– Double Add—(GE_XPE and 10GE_XPE cards only) Adds an inner and an outer SVLAN to double tagged packets only. CVLAN settings are not required. If this double tagged selective operation is present on a port, no other selective operation can be present.
– Translate Add—(GE_XPE and 10GE_XPE cards only) CVLAN gets translated to inner SVLAN and the SVLAN is added.
Note If Double Add and Translate Add are configured on a GE_XP or a 10GE_XP card, a PROV-MISMATCH alarm is raised. Until this alarm is cleared, provisioning on the card is not possible.
Note A CVLAN with a value of 0 means “untagged packet”.
Note Two or more CVLANs cannot be translated over the same SVLAN.
e. (GE_XPE and 10GE_XPE cards only) Click the COS table cell and choose a value from the drop down list.
g. Continue with Step 10.
Step 7 If the Mode was set to Transparent, in the SVLAN field, choose the SVLAN to be added to incoming packets.
Step 8 Click DSCP-Cos mapping Table to provision CoS based on DSCP for each port.
Step 9 For each DSCP, choose a CoS value from 0 to 7 and click OK.
Step 10 Return to your originating procedure (NTP).
DLP-G221 Enable MAC Address Learning on SVLANs for GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards
Step 1 Complete the “ DLP-G46 Log into CTC ” task at the node where you want to enable MAC Address Learning. If you are already logged in, continue with Step 2.
Step 2 Complete the following tasks, as needed:
- G460 Enable MAC Address Learning on SVLANs for GE_XPE or 10GE_XPE Cards Using CTC
- NTP-G226 Enable MAC Address Learning on SVLANs for GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards Using PCLI
Stop. You have completed this procedure.
DLP-G460 Enable MAC Address Learning on SVLANs for GE_XPE or 10GE_XPE Cards Using CTC
This task enables MAC address learning on SVLANs attached to the port of a GE_XPE or 10GE_XPE card. |
|
G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode |
|
Note To perform this task, the GE_XPE or 10GE_XPE card must be in L2-over-DWDM mode. Refer to the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode if needed.
Note MAC address learning is applicable only for GE_XPE and 10GE_XPE cards. If MAC address learning is configured on a GE_XP or a 10GE_XP card, a PROV-MISMATCH alarm is raised. Until this alarm is cleared, provisioning on the card is not possible.
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the GE_XPE or 10GE_XPE card where you want to enable MAC address learning.
Step 2 Enable MAC address learning on the port. Perform the following steps:
a. Click Provisioning > Ethernet .
b. Check the MAC Learning check box.
Note If the per port MAC address learning is configured on a GE_XP or 10 GE_XP cards, before upgrading to a GE_XPE or 10 GE_XPE card, enable MAC address learning per SVLAN. Not doing so disables MAC address learning.
Step 3 Enable MAC address learning on the SVLAN attached to the port. Perform the following steps:
a. Click SVLAN > SVLAN DB tabs.
b. Click Load . This loads an SVLAN database from a network node or local file and replaces any SVLANs that are in the network view VLAN DB table.
c. Check the MAC Learning check box related to the SVLAN (one or more than one SVLAN) to be configured with MAC address learning.
d. Click Store . This records and enables the new configuration.
Step 4 Return to your originating procedure (NTP).
DLP-G385 Provision the MAC Filter Settings for GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Card
Note To perform this task, the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card must be in L2-over-DWDM mode. To change the card mode, complete the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode.
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card where you want to change the MAC filter settings.
Step 2 Click the Provisioning > Security > MAC Filter tabs.
Step 3 Click the port for which you want to create a MAC filter.
Step 5 In the Edit MAC Address dialog box, click Add . A new table entry appears with the MAC address 00-00-00-00-00-00.
Step 6 In the MAC Address Port field, type in the MAC address you want to filter over the default 00-00-00-00-00-00 address.
Step 7 If you want to add more MAC addresses, repeat Steps 5 and 6 . (Up to eight MAC addresses can be added for each port.) If not, click OK .
Step 8 On the MAC Filter table, provision the Allowed check box:
Step 10 Repeat Steps 3 through 9 for each port of the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card that you want to set up.
Step 11 Return to your originating procedure (NTP).
NTP-G237 Retrieve and Clear MAC Addresses on SVLANs for GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards
This procedure retrieves and clears MAC addresses learned on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE cards. |
|
Note It is not possible to simultaneously retrieve learned MAC addresses from both CTC and TL1 interfaces.
Step 1 In the node view (single-shelf mode) or shelf view (multishelf view), double-click the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card where you want to retrieve the MAC addresses.
Step 2 To retrieve the MAC addresses learned, perform the following steps:
a. Click Maintenance > MAC Addresses > Learned .
b. In the SVLAN field, type a valid SVLAN range. The SVLAN range is from 1 to 4093.
The table displays the following fields:
– MAC Address—Displays the MAC address for the port.
– VLAN—Displays the VLAN identifier for the port.
– Port—Displays the port number.
Right-click the column heading to display the following options:
– Row Count—Displays the number of learned MAC addresses retrieved.
– Sort Column—Sorts the table by the column’s values.
– Hide Column—Hides the column from view.
– Reorder Columns Visibility—Displays all hidden columns.
Step 3 Click Refresh to refresh the list of MAC addresses learned.
Step 4 Click Clear to clear the MAC addresses learned on all the SVLANS of the card.
Note It is not possible to delete the MAC addresses learned on a per SVLAN basis.
Step 5 To view card MAC addresses, complete the G546 View Card MAC Addresses on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards.
Stop. You have completed this procedure.
DLP-G546 View Card MAC Addresses on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards
This task allows you to view the MAC addresses for each client and trunk port and the CPU port of the card. |
|
Step 1 To view the card MAC addresses, click Maintenance > MAC Addresses > Card . The MAC addresses for each client and trunk port and the CPU port are displayed.
The table displays the following fields:
Step 2 Return to your originating procedure.
NTP-G311 Provision the Storm Control Settings for GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards
This task provisions the storm control settings for the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE cards when the cards are provisioned in L2-over-DWDM mode. |
|
Note To perform this task, the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card must be in L2-over-DWDM mode. To change the card mode, complete the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode.
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card where you want to change the storm control settings.
Step 2 Click the Provisioning > Security > Storm Control tabs.
Step 3 Modify any of the settings as described in Table 11-166 .
Stop. You have completed this procedure.
NTP-G205 Enable Link Integrity on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards
Step 1 Complete the “ DLP-G46 Log into CTC ” task at the node where you want to enable link integrity. If you are already logged in, continue with Step 2.
Step 2 Complete the following tasks, as needed:
- G509 Enable Link Integrity on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards Using CTC
- NTP-G216 Enable Link Integrity on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards Using PCLI
Stop. You have completed this procedure.
DLP-G509 Enable Link Integrity on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards Using CTC
Step 1 From the View menu, choose Go to Network View .
Step 2 Create or load an SVLAN profile. To create a SVLAN profile see the G471 Create a SVLAN or CVLAN Profile.
Note Make sure the Link Integrity check box is selected to enable link integrity for a profile and save it to the node.
Step 3 Associate the SVLAN profile (with Link Integrity enabled) to a SVLAN on a port. To do this perform the following steps:
a. In node view (single-shelf mode), or shelf view (multishelf mode), double-click the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card. The card view appears.
b. Click the Provisioning > Profiles Mapping > SVLAN tabs.
c. Enter the SVLANs or SVLAN range in the SVLAN to View text box.
A table appears that displays SVLANs and available ports. The SVLAN profiles that was created must be applied to a SVLAN and a port. However, make sure the SVLAN has already been associated with the port via the QinQ tab (For information on how to associate a SVLAN to a port, see the G384 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE QinQ Settings).
d. Select the SVLAN for a port and choose the available SVLAN profile from the drop-box.
Step 4 AIS action must be set on a per-UNI port basis. Select None or Squelch from the AIS action drop-down list. For detailed instructions, see the G380 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Ethernet Settings.
Step 5 Return to your originating procedure (NTP).
NTP-G289 Provision CVLAN Rate Limiting on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Card
Note You cannot provision CVLAN rate limiting on channel groups.
Step 1 Complete the “ DLP-G46 Log into CTC ” task at the node where you want to provision CVLAN rate limiting. If you are already logged in, continue with Step 2.
Step 2 From the View menu, choose Go to Network View .
Step 3 Create or load a CVLAN profile by setting Committed Info Rate, Committed Burst, Excess Info, Excess Burst. To create a CVLAN Profile see the G471 Create a SVLAN or CVLAN Profile.
Step 4 Associate the CVLAN profile to a CVLAN on a UNI port. To do this perform the following steps:
a. In node view (single-shelf mode), or shelf view (multishelf mode), double-click the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE card. The card view appears.
b. Click the Provisioning > Profiles Mapping > CVLAN tabs.
c. Enter the CVLANs or CVLAN range in the CVLANS to View text box.
A table appears that displays CVLANs and available ports. The CVLAN profiles that were created must be applied to a CVLAN and port. However, make sure the CVLAN has already been associated with the port via the QinQ tab (For information on how to associate a CVLAN profile to a UNI port, see the G384 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE QinQ Settings).
d. Select the CVLAN for a given port and choose the available CVLAN profile from the drop-down list.
Stop. You have completed this procedure.
NTP-G208 Provision SVLAN Rate Limiting on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Card
Step 1 Complete the “ DLP-G46 Log into CTC ” task at the node where you want to enable SVLAN rate limiting. If you are already logged in, continue with Step 2.
Step 2 Complete the following tasks, as needed:
- G515 Provision SVLAN Rate Limiting on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Card Using CTC
- NTP-G225 Provision SVLAN Rate Limiting on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Card Using PCLI
Stop. You have completed this procedure.
DLP-G515 Provision SVLAN Rate Limiting on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Card Using CTC
Step 1 From the View menu, choose Go to Network View .
Step 2 Create or load a SVLAN profile by setting Committed Info Rate, Committed Burst, Excess Info, Excess Burst. To create a SVLAN Profile see the G471 Create a SVLAN or CVLAN Profile.
Step 3 Associate the SVLAN profile to a SVLAN on a port. To do this, perform the following steps:
a. In node view (single-shelf mode), or shelf view (multishelf mode), double-click the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE card. The card view appears.
b. Click the Provisioning > Profiles Mapping > SVLAN tabs.
c. Enter the SVLANs or SVLAN range in the SVLAN to View text box.
A table appears that displays SVLANs and available ports. The SVLAN profiles that were created must be applied to a SVLAN and port. However, make sure the SVLAN has already been associated with the port via the QinQ tab (For information on how to associate a SVLAN profile to a UNI port, see the G384 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE QinQ Settings and to a NNI port see the G382 Add and Remove SVLANS to/from GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE NNI Ports).
d. Select the SVLAN for a given port and choose the available SVLAN profile from the drop-down list.
Stop. You have completed this procedure.
DLP-G471 Create a SVLAN or CVLAN Profile
Note You cannot associate SVLAN or CVLAN profiles to channel groups. You can associate a CVLAN profile only to a UNI port.
Step 1 From the View menu, choose Go to Network View .
Step 2 Click the Provisioning > SVLAN > Profiles tabs.
Step 3 Click Add and a profile is added to the Profiles tab. Modify any of the settings as follows:
- Name—The profile name can be up to 32 alphanumeric/special characters.
- Committed Info Rate—Sets the guaranteed information rate based on the service-level agreement of the service provider. The valid value ranges from 0 to 100% with 0.1% granularity. The default value is 100%.
- Committed Burst—Sets the maximum number of bits that will be transferred per second.
- Peak Info rate—Sets the maximum access rate based on the service-level agreement of the service provider. The valid value ranges from 0 to 100% with 0.1% granularity. The default value is 100%. However, the value must be greater than or equal to the Committed Info Rate.
- Peak Burst Size—The maximum number of bits that are credited for later transfer in the event the committed burst rate cannot be transmitted.
- Link Integrity—Enables link integrity for the SVLAN profile. Do not check this check box if you are creating a CVLAN profile.
Note When you set the Committed Info Rate above 40% on 10GE_XP and 10GE_XPE cards, the Committed Burst Size and Excess Burst Size must be set to at least 32K. The Committed Burst Size and Excess Burst Size can be increased based on the packet size and Committed Info Rate value.
Step 5 In the Store Profile(s) dialog box, choose one of the following:
- To Node(s)—Stores the SVLAN profile at one or more network nodes. Choose the network nodes where you want to store the SVLAN profile. To choose more than one node, press the Shift key, or click Select All.
- To File—Stores the SVLAN profile in a file. Enter a file name, then click Browse to navigate to a local or network drive where you want to store the file.
Step 7 Return to your originating procedure (NTP).
NTP-G204 Enable IGMP Snooping on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards
This procedure enables Internet Group Management Protocol (IGMP) snooping on a per-SVLAN basis on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE cards. |
|
Step 1 Complete the “ DLP-G46 Log into CTC ” task at the node where you want to enable IGMP snooping. If you are already logged in, continue with Step 2.
Step 2 Complete the following tasks, as needed:
- G511 Enable IGMP Snooping, IGMP Fast Leave and IGMP Report Suppression on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards Using CTC.
- NTP-G220 Enable IGMP Snooping on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards Using PCLI .
- NTP-G217 Enable IGMP Fast-Leave Processing on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards Using PCLI .
- NTP-G219 Enable IGMP Report Suppression on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards Using PCLI .
Stop. You have completed this procedure.
DLP-G511 Enable IGMP Snooping, IGMP Fast Leave and IGMP Report Suppression on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards Using CTC
This procedure explains how to enable IGMP snooping, IGMP fast leave and IGMP report suppression on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE cards using CTC. |
|
Step 1 From the View menu, choose Go to Network View .
Step 2 Click the Provisioning > SVLAN > SVLAN DB tabs. Click Load to load the SVLANs on the card where IGMP must be enabled.
Step 3 For each SVLAN shown in the table, select the following:
- IGMP—Check the IGMP check box to enable IGMP for the selected SVLAN.
- IGMP Fast Leave—Checking the IGMP Fast Leave causes the switch to immediately remove a port from the IP multicast group when it detects an IGMP, version 2 (IGMPv2) leave message on that port.
- IGMP Suppression—Check the IGMP Suppression check box to enable a single IGMP report to be sent to each multicast group in response to a single query.
Step 5 In the Store SVLAN DB dialog box, choose one of the following:
- To Node/Shelf/Card—Select the node and shelf. All the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE cards in L2 over DWDM mode are displayed. Select the card where you want to store the SVLAN DB.
- Stores the SVLAN database at one or more network nodes. Choose the network nodes where you want to store the SVLAN database. To choose more than one node, press the Shift key, or click Select All .
- To File—Stores the SVLAN database in a file. Enter a file name, then click Browse to navigate to a local or network drive where you want to store the file.
- Select the card on which you want to save the changes made in step 3.
Note If you want to add the multicast-capable ports to the forwarding table for every IP multicast, select the IGMP Static Router Port check box as described in the G380 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Ethernet Settings.
Stop. You have completed this procedure.
NTP-G206 Enable MVR on a GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Card
This procedure enables Multicast VLAN Registration (MVR) on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE cards. |
|
Step 1 Complete the “ DLP-G46 Log into CTC ” task at the node where you want to enable IGMP snooping. If you are already logged in, continue with Step 2.
Step 2 Complete the following tasks, as needed:
- G513 Enable MVR on a GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Card Using CTC.
- NTP-G224 Enable MVR on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Cards Using PCLI .
Stop. You have completed this procedure.
DLP-G513 Enable MVR on a GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Card Using CTC
This procedure enables Multicast VLAN Registration (MVR) on GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE cards using CTC. |
|
G382 Add and Remove SVLANS to/from GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE NNI Ports |
|
Step 1 In node view (single-shelf mode), or shelf view (multishelf mode), double-click the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card where you want to enable MVR. The card view appears.
Note At least one SVLAN must be configured on the card.
Step 2 Click the Provisioning > MVR tabs. The MVR Settings tab appears.
Step 3 Check the Enabled check box and enter the following information:
- IGMP CVLAN—Check box to enable IGMP snooping on CVLAN. This check box is enabled only when MVR is enabled through the Enabled check box.
- Multicast SVLAN—Select the MVR SVLAN ID. The default value is the SVLAN with the lowest ID configured on the card. The drop box lists all the SVLANs on the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card.
Note SVLAN selected here can not be used for UNI port, make sure that the corresponding SVLAN on the NNI port is checked.
- Multicast Address—Sets the specified multicast group address as the MVR multicast group. The default address is 239.255.255.255 and the range is 224.0.0.0 to 239.255.255.255. Except the subrange [224-239].[0/128].0.x.
- Count—Sets the range of any additional multicast group addresses. The default is 1, and range is 1 to 256.
Step 5 Return to your originating procedure (NTP).
DLP-G386 Provision the Gigabit Ethernet Trunk Port Alarm and TCA Thresholds
Note The GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards have two trunk ports. The GE_XP and GE_XPE trunk ports are 21-1 and 22-1 on the card graphic and 21 (Trunk) and 22 (Trunk) on the Optics Thresholds table. The 10GE_XP and 10GE_XPE card trunk ports are 3-1 and 4-1 on the card graphic and 3 (Trunk) and 4 (Trunk) on the Optics Thresholds table.
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card where you want to change the trunk port alarm and TCA settings.
Step 2 Click the Provisioning > Optics Thresholds tabs.
Note You must modify 15 Min and 1 Day independently. To do so, choose the appropriate radio button and click Refresh.
Note Do not modify the Laser Bias parameters.
Note The hardware device that plugs into a TXP, MXP, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE or ADM-10G card faceplate to provide a fiber interface to the card is called a Small Form-factor Pluggable (SFP or XFP). In CTC, SFPs and XFPs are called pluggable port modules (PPMs). SFPs/XFPs are hot-swappable input/output devices that plug into a port to link the port with the fiber-optic network. Multirate PPMs have provisionable port rates and payloads. For more information about SFPs and XFPs, see the “SFP, SFP+, XFP, CXP, and CFP Modules” section.
Step 3 If TCA is not selected, click TCA and then click Refresh . When TCA is selected, continue with Step 4.
Step 4 Verify the trunk port TCA thresholds are provisioned as shown in Table 11-167 . Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and hitting Enter .
Step 5 Under Types, click the Alarm radio button and click Refresh .
Note Do not modify the Laser Bias parameters.
Step 6 Verify the trunk port alarm thresholds are provisioned as shown in Table 11-168 . Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and hitting Enter .
Step 8 Repeat Steps 3 through 7 to provision the second trunk port.
Step 9 Return to your originating procedure (NTP).
DLP-G387 Provision the Gigabit Ethernet Client Port Alarm and TCA Thresholds
This task provisions the client port alarm and TCA thresholds for the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards. |
|
Note The GE_XP card has 20 client ports. The ports are 1-1 through 20-1 on the card graphic and 1 (Client) through 20 (Client) on the Optics Thresholds table. The 10GE_XP card has 2 client ports. The ports are 1-1 and 2-1 on the card graphic and 1 (Client) and 2 (Client) on the Optics Thresholds table.
Note The hardware device that plugs into a TXP, MXP, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, or ADM-10G card faceplate to provide a fiber interface to the card is called a Small Form-factor Pluggable (SFP or XFP). In CTC, SFPs and XFPs are called pluggable port modules (PPMs). SFPs/XFPs are hot-swappable input/output devices that plug into a port to link the port with the fiber-optic network. Multirate PPMs have provisionable port rates and payloads. For more information about SFPs and XFPs, see the “SFP, SFP+, XFP, CXP, and CFP Modules” section.
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card where you want to change the client port alarm and TCA settings.
Step 2 Click the Provisioning > Optics Thresholds tabs. The TCA thresholds are shown by default.
Step 3 If TCA is not selected, click TCA and then click Refresh . When TCA is selected, continue with Step 4.
Step 4 Verify the client port TCA thresholds are provisioned as shown in Table 11-169 . Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and hitting Enter .
1000Base-SX (1Gbps)16 |
||||
Note You must modify 15 Min and 1 Day independently. To do so, choose the appropriate radio button and click Refresh.
Step 5 Under Types, click the Alarm radio button and click Refresh .
Note Do not modify the Laser Bias parameters.
Step 6 Verify the client port Alarm thresholds are provisioned as shown in Table 11-170 . Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and hitting Enter .
1000Base-SX (1Gbps)17 |
||||
Step 8 Repeat Steps 3 through 7 to provision each additional client port.
Step 9 Return to your originating procedure (NTP).
DLP-G388 Change the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE Card RMON Thresholds
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), display the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card where you want to change the RMON thresholds.
Step 2 Click the Provisioning > RMON Thresholds tabs.
Step 3 Click Create . The Create Threshold dialog box appears.
Step 4 From the Port drop-down list, choose an individual port, or choose All to provision RMON thresholds for all ports.
Step 5 From the Variable drop-down list, choose an Ethernet variable. See Table 11-171 for a list of available Ethernet RMON variables.
Note Variable descriptions were obtained from the following Internet Engineering Task Force (IETF) Requests for Comment (RFCs): RFC 3635, RFC 2233, and RFC 1757. Refer to the RFCs for additional information.
Step 6 From the Alarm Type drop-down list, indicate whether the event will be triggered by the rising threshold, the falling threshold, or both the rising and falling thresholds.
Step 7 From the Sample Type drop-down list, choose either Relative or Absolute . Relative restricts the threshold to use the number of occurrences in the user-set sample period. Absolute sets the threshold to use the total number of occurrences, regardless of time period.
Step 8 Type in an appropriate number of seconds for the Sample Period.
Step 9 Type in the appropriate number of occurrences for the Rising Threshold.
For a rising type of alarm, the measured value must move from below the falling threshold to above the rising threshold. For example, if a network is running below a rising threshold of 1000 collisions every 15 seconds and a problem causes 1001 collisions in 15 seconds, the excess occurrences trigger an alarm.
Step 10 Enter the appropriate number of occurrences in the Falling Threshold field. In most cases a falling threshold is set lower than the rising threshold.
A falling threshold is the counterpart to a rising threshold. When the number of occurrences is above the rising threshold and then drops below a falling threshold, it resets the rising threshold. For example, when the network problem that caused 1001 collisions in 15 seconds subsides and creates only 799 collisions in 15 seconds, occurrences fall below a falling threshold of 800 collisions. This resets the rising threshold so that if network collisions again spike over a 1000 per 15-second period, an event again triggers when the rising threshold is crossed. An event is triggered only the first time a rising threshold is exceeded (otherwise, a single network problem might cause a rising threshold to be exceeded multiple times and cause a flood of events).
Step 12 To view all RMON thresholds, click Show All RMON thresholds . If not, continue with Step 12
Step 13 Return to your originating procedure (NTP).
DLP-G389 Change the Gigabit Ethernet Optical Transport Network Settings
This task changes the optical transport network (OTN) settings for the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE cards. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the GE_XP, 10GE_XP, GE_XPE, or 10GE_XPE card where you want to change the OTN settings.
Step 2 Click the Provisioning > OTN tabs, then choose one of the following subtabs: OTN Lines , G.709 Thresholds , FEC Thresholds , or Trail Trace Identifier .
Step 3 Modify any of the settings described in Tables 11-172 through 11-175 .
Note You must modify Near End and Far End; 15 Min and 1 Day; and SM and PM independently. To do so, choose the appropriate radio button and click Refresh.
Table 11-172 describes the values on the Provisioning > OTN > OTN Lines tab.
Table 11-173 describes the values on the Provisioning > OTN > ITU-T G.709 Thresholds tab.
Table 11-174 describes the values on the Provisioning > OTN > FEC Threshold tab.
Table 11-175 describes the values on the Provisioning > OTN > Trail Trace Identifier tab.
Step 5 Return to your originating procedure (NTP).
NTP-G314 Add a GE_XP or 10GE_XP Card on a FAPS Ring
Step 1 Complete the “ DLP-G46 Log into CTC ” task at the node where you want to add a GE_XP or 10GE_XP card on a FAPS ring. If you are already logged in, continue with Step 2.
Step 2 Perform any of the following tasks as needed:
- G687 Add a GE_XP or 10GE_XP Card Facing Master Card on a FAPS Ring
- G688 Add a GE_XP or 10GE_XP Card Between the Slave Cards on a FAPS Ring
Stop. You have completed this procedure.
DLP-G687 Add a GE_XP or 10GE_XP Card Facing Master Card on a FAPS Ring
Step 1 Complete the “ DLP-G46 Log into CTC ” task at the node where you want to add a GE_XP or 10GE_XP card on a FAPS ring.
Step 2 Verify that the GE_XP or 10GE_XP card is installed according to the requirements specified in Table 14-7.
Step 3 Insert the new GE-XP card with XFP on the slot.
Step 4 Change the GE_XP card mode to L2-over-DWDM. See the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode.
Step 5 Create and store an SVLAN database on the new GE_XP card. See the G421 Create and Store an SVLAN Database.
Step 6 Enable FAPS protection on the new card.
Step 7 Attach SVLAN to the trunk ports of the new card.
Step 8 Choose OOS,DSBLD from the Admin State column for port 22 on the master card that is facing toward the new card. This action places port 22 in the blocking state and port 21 in the forwarding state.
FAPS configuration mismatch alarm is raised on the master card.
Step 9 Switch the traffic to the protect path.
Step 10 Choose OOS,DSBLD from the Admin State column for port 21 on the slave card that is facing toward the new card.
Step 11 Connect the fiber from the slave card (that is facing toward the new card) to the new card in segment B.
Step 12 Connect the fiber from the master card to the new card in segment A.
Step 13 Choose IS from the Admin State column for port 21 on the slave card that is facing toward the new card.
Step 14 Choose IS from the Admin State column for port 22 on the new card to bring up segment B.
Step 15 Choose IS from the Admin State column for port 21 on the new card.
Note The FAPS state of the new card will be in the forwarding state for both the ports and port 21 of the slave card will be in the blocking state.
Step 16 Choose IS from the Admin State column for port 22 on the master card to bring up segment A.
Note The FAPS state of port 21 on the master card will be in the blocking state and port 22 will be in the forwarding state. The trunk ports of the remaining GE_XP cards will be in the forwarding state. The port 21 of the slave card (that is facing toward the new card) will change to the forwarding state.
Step 17 Return to your originating procedure (NTP).
DLP-G688 Add a GE_XP or 10GE_XP Card Between the Slave Cards on a FAPS Ring
Step 1 Complete the “ DLP-G46 Log into CTC ” task at the node where you want to add a GE_XP or 10GE_XP card on a FAPS ring.
Step 2 Verify that the GE_XP or 10GE_XP card is installed according to the requirements specified in Table 14-7.
Step 3 Insert the new GE-XP card with XFP on the slot.
Step 4 Change the GE_XP card mode to L2-over-DWDM. See the G379 Change the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Card Mode.
Step 5 Create and store an SVLAN database on the new GE_XP card. See the G421 Create and Store an SVLAN Database.
Step 6 Attach SVLAN to the trunk ports of the new card.
Step 7 Choose OOS,DSBLD from the Admin State column for port 22 on both the slave cards that are facing toward the new card.
Step 8 Connect the fiber from the slave card to the new card in segment B.
Step 9 Connect the fiber from the master card to the new card in segment A.
Step 10 Choose IS from the Admin State column for port 22 on the slave card.
Step 11 Choose IS from the Admin State column for port 22 on the new card to bring up segment B.
Step 12 Choose IS from the Admin State column for port 21 on the new card.
Step 13 Choose IS from the Admin State column for port 21 on the slave card to bring up segment A.
Step 14 Return to your originating procedure (NTP).
NTP-G197 Provision the OTU2_XP Card Line Settings, PM Parameters, and Thresholds
This procedure changes line settings, PM parameters, and threshold setting for the OTU2_XP card. |
|
G179 Install the TXP, MXP, AR_MXP, AR_XP, AR_XPE, 100G-LC-C, 10x10G-LC, CFP-LC, WSE, ADM-10G, and OTU2_XP Cards |
|
Step 1 Complete the “ DLP-G46 Log into CTC ” task at the node where you want to change the card settings. If you are already logged in, continue with Step 2.
Step 2 As needed, complete the G103 Back Up the Database to preserve the existing transmission settings.
Step 3 In node view (single-shelf mode) or shelf view (multishelf view), double-click the OTU2_XP card.
a. Display the OTU2_XP card in card view.
b. Click the Provisioning > Card tabs.
c. Verify that the card mode is set to the mode designated by your site plan:
– 10G Ethernet LAN Phy to WAN Phy
If the card mode is set correctly, continue with Step 6 . If not, complete the G452 Change the OTU2_XP Card Mode.
Step 5 Refer to the “OTU2_XP Card Configuration Rules” section before performing any task listed in Step 6 .
Step 6 Perform any of the following tasks as needed.
- G453 Change the OTU2_XP Card Settings
- G454 Change the OTU2_XP Line Settings
- G455 Change the OTU2_XP Line Section Trace Settings
- G456 Change the OTU2_XP Line Thresholds for SONET or SDH Payloads
- G457 Provision the OTU2_XP Port Alarm and TCA Thresholds
- G462 Change the OTU2_XP Line RMON Thresholds for the 10G Ethernet and 10G FC Payloads
- G458 Change the OTU2_XP OTN Settings
- G523 Change the OTU2_XP Path Trace Settings
- G524 Provision the OTU2_XP Path Settings for 10G Ethernet LAN Phy to WAN Phy Configuration
Stop. You have completed this procedure.
DLP-G453 Change the OTU2_XP Card Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the OTU2_XP card where you want to change the card settings.
Step 2 Click the Provisioning > Card tab.
Step 3 Modify any of the settings described in Table 11-176 .
Step 5 Return to your originating procedure (NTP).
DLP-G454 Change the OTU2_XP Line Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the OTU2_XP card where you want to change the line settings.
Step 2 Click the Provisioning > Line > Ports/SONET/Ethernet tabs.
Step 3 Modify any of the settings described in Table 11-177 .
User-defined. Name can be up to 32 alphanumeric/special characters. Blank by default. See the G104 Assign a Name to a Port. |
User-defined. Name can be up to 32 alphanumeric/special characters. Blank by default. See the G104 Assign a Name to a Port. |
||
Sets the port service state. For more information about administrative states, see the Administrative and Service States document. |
|||
(Display only) Identifies the autonomously generated state that gives the overall condition of the port. Service states appear in the format: Primary State-Primary State Qualifier, Secondary State. For more information about service states, see the Administrative and Service States document. |
|||
Sets the ALS function mode. The DWDM transmitter supports ALS according to ITU-T G.644 (06/99). ALS can be disabled, or it can be set for one of three mode options. |
|
|
|
Displays the optical reach distance of the client/trunk ports. |
The Reach options depend on the traffic type that has been selected. |
The Reach options depend on the traffic type that has been selected. |
|
Sets the automatic in-service soak period. Double-click the time and use the up and down arrows to change settings. |
|||
(SONET [ANSI] or SDH [ETSI] only) Sets the signal fail bit error rate. |
|||
(SONET [ANSI] or SDH [ETSI] only) Sets the signal degrade bit error rate. |
|||
(SONET [ANSI] or SDH [ETSI] only) The optical transport type. |
Note When Type is set to SDH in a SONET (ANSI) provisioning, SDCC or LDCC on OTU2_XP cards cannot be provisioned. |
||
The maximum size of the Ethernet frames accepted by the port. The port must be in OOS/locked state. MTU stands for “Maximum Transmission Unit” typically meant for configuring the maximum frame size allowed. However, the OTU2_XP card does not block the frames based on Ethernet frame size and Jumbo frames are supported irrespective of the MTU setting. In 10G LAN Phy to WAN Phy mode, MTU can be set only to 1548 bytes. |
|||
Flow Control (Only when the card is in 10G Ethernet LAN Phy to WAN Phy mode) |
Enables/disables flow control messaging with its peer port. When enabled, the port can send and receive PAUSE frames when buffer congestion occurs. When disabled, no PAUSE frames are transmitted and the PAUSE frames received are discarded. |
||
Client Distance (Only when the card is in 10G Ethernet LAN Phy to WAN Phy mode) |
Sets the fiber distance between the client of OTU2_XP card and the LAN port that is connected to the OTU2_XP client port. |
Step 5 Return to your originating procedure (NTP).
DLP-G455 Change the OTU2_XP Line Section Trace Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the OTU2_XP card where you want to change the section trace settings.
Step 2 Click the Provisioning > Line > Section Trace tabs.
Step 3 Modify any of the settings described in Table 11-178 .
If a TIM on Section overhead alarm arises because of a J0 overhead string mismatch, no alarm indication signal is sent to downstream nodes if this box is checked. This is a display-only parameter under the following conditions:
|
|||
Displays the current transmit string; sets a new transmit string. You can click the button on the right to change the display. Its title changes, based on the current display mode. Click Hex to change the display to hexadecimal (button changes to ASCII); click ASCII to change the display to ASCII (button changes to Hex). |
|||
Displays the current expected string; sets a new expected string. You can click the button on the right to change the display. Its title changes, based on the current display mode. Click Hex to change the display to hexadecimal (button changes to ASCII); click ASCII to change the display to ASCII (button changes to Hex). |
|||
(Display only) Displays the current received string. You can click Refresh to manually refresh this display, or check the Auto-refresh check box to automatically refresh the display every 5 seconds. |
|||
If checked, automatically refreshes the display every 5 seconds. |
Step 5 Return to your originating procedure (NTP).
DLP-G456 Change the OTU2_XP Line Thresholds for SONET or SDH Payloads
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the OTU2_XP card where you want to change the line threshold settings.
Step 2 Click the Provisioning > Line Thresholds > SONET Thresholds (ANSI) or SDH Thresholds (ETSI) tabs.
Note If you have enabled 10G Ethernet LAN Phy to WAN Phy on the OTU2_XP card, the STS option is automatically enabled.
Only near end STS thresholds are supported. No STS thresholds are support for Far End.
Step 3 Modify any of the OTU2_XP card path threshold settings on a LAN Phy to WAN Phy mode, as seen in Table 11-179 .
Step 4 Modify any of the OTU2_XP Card Line Threshold settings described in Table 11-180
Step 6 Return to your originating procedure (NTP).
DLP-G457 Provision the OTU2_XP Port Alarm and TCA Thresholds
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the OTU2_XP card where you want to change the trunk port alarm and TCA settings.
Step 2 Click the Provisioning > Optics Thresholds tabs.
Step 3 Under Types, verify that the TCA radio button is checked. If not, select it, then click Refresh .
Step 4 Refer to Table 11-181 to provision the port TCA thresholds for RX Power High, RX Power Low, TX Power High, and TX Power Low.
Note You must modify 15 Min and 1 Day independently. To do so, choose the appropriate radio button and click Refresh.
Note Do not modify the Laser Bias parameters.
Step 6 Under Types, click the Alarm radio button and click Refresh .
Step 7 Refer to Table 11-182 to provision the port alarm thresholds for RX Power High, RX Power Low, TX Power High, and TX Power Low.
Note You must modify 15 Min and 1 Day independently. To do so, choose the appropriate radio button and click Refresh.
Step 9 Return to your originating procedure (NTP).
DLP-G462 Change the OTU2_XP Line RMON Thresholds for the 10G Ethernet and 10G FC Payloads
This task changes the line threshold settings for OTU2_XP card carrying the 10G Ethernet or 10G FC payloads. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the OTU2_XP card where you want to change the line threshold in the card view.
Step 2 Click the Provisioning > Line Thresholds > RMON Thresholds tabs.
Step 3 Click Create . The Create Threshold dialog box appears.
Step 4 From the Port drop-down list, choose the applicable port.
Step 5 From the Variable drop-down list, choose an Ethernet variable. See Table 11-183 and Table 11-184 for a list of available Ethernet variables.
Total number of octets received on the interface, including framing characters. |
|
Total number of fiber channel frames received that are less than the minimum 36-byte frame. This is inclusive of header, SOF, EOF, and CRC with no data bytes. |
|
Total number of fiber channel frames received that exceed the maximum 2148-byte frame. This is inclusive of header, SOF, EOF, CRC, and data bytes. |
|
Total number of fiber channel frames received with CRC errors. |
|
The number of inbound packets, which were chosen to be discarded even though no errors had been detected to prevent their being delivered to a higher-layer protocol. One possible reason for discarding such a packet could be to free up buffer space.18 |
|
Total number of octets transmitted out of the interface, including framing characters.1 |
|
Number of transmitted data frames with payload CRC errors when HDLC framing is used.1 |
|
Step 6 From the Alarm Type drop-down list, choose the event triggers. The available options are rising threshold, falling threshold, or rising and falling thresholds.
Step 7 From the Sample Type drop-down list, choose either Relative or Absolute . Relative restricts the threshold to use the number of occurrences in the user-set sample period. Absolute sets the threshold to use the total number of occurrences, regardless of time period.
Step 8 Enter an appropriate number of seconds for the Sample Period.
Step 9 Enter in the appropriate number of occurrences for the Rising Threshold.
For a rising type of alarm, the measured value must move from below the falling threshold to above the rising threshold. For example, if a network is running below a rising threshold of 1000 collisions every 15 seconds and a problem causes 1001 collisions in 15 seconds, the excess occurrences trigger an alarm.
Step 10 Enter the appropriate number of occurrences in the Falling Threshold field. In most cases a falling threshold is set lower than the rising threshold.
A falling threshold is the counterpart to a rising threshold. When the number of occurrences is above the rising threshold and then drops below a falling threshold, it resets the rising threshold. For example, when the network problem that caused 1001 collisions in 15 seconds subsides and creates only 799 collisions in 15 seconds, occurrences fall below a falling threshold of 800 collisions. This resets the rising threshold so that if network collisions again spike over a 1000 per 15-second period, an event again triggers when the rising threshold is crossed. An event is triggered only the first time a rising threshold is exceeded (otherwise, a single network problem might cause a rising threshold to be exceeded multiple times and cause a flood of events).
Note To view all RMON thresholds, click Show All RMON thresholds.
Step 12 Return to your originating procedure (NTP).
DLP-G458 Change the OTU2_XP OTN Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the OTU2_XP card where you want to change the OTN settings.
Step 2 Click the Provisioning > OTN tabs. Then click one of the following subtabs: OTN Lines , ITU-T G.709 Thresholds , FEC Thresholds , Trail Trace Identifier, or Proactive Protection Regen .
Step 3 Modify any of the settings described in Tables 11-71 through 11-74 .
Note You must modify Near End and Far End independently, 15 Min and 1 Day independently, and SM and PM independently. To do so, select the appropriate radio button and click Refresh.
Table 11-185 describes the values on the Provisioning > OTN > OTN Lines tabs.
Table 11-186 describes the values on the Provisioning > OTN > ITU-T G.709 Thresholds tab.
Table 11-187 describes the values on the Provisioning > OTN > FEC Thresholds tab.
Table 11-188 describes the values on the Provisioning > OTN > Trail Trace Identifier tab.
Note You cannot change the Path Trail Trace Identifier settings when the OTU2_XP card is in the Standard Regen mode, and if the ODU transparency is set to “Transparent Standard Use”.
You can change the Path Trail Trace Identifier settings when the OTU2_XP card is in the Standard Regen mode, and if the ODU transparency is set to “Cisco Extended Use”.
Table 11-189 describes the values on the Provisioning > OTN > Proactive Protection Regen tabs.
Note Proactive protection regen is supported on ports of OTU2_XP only in Standard Regen and Enhanced FEC mode.
Step 5 Return to your originating procedure (NTP).
DLP-G523 Change the OTU2_XP Path Trace Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the OTU2_XP card where you want to change the path trace settings.
Step 2 Click the Provisioning > Path> J1 Path Trace tabs.
Step 3 Modify any of the settings described in Table 11-190 .
Return to your originating procedure (NTP).
DLP-G524 Provision the OTU2_XP Path Settings for 10G Ethernet LAN Phy to WAN Phy Configuration
This task changes the path settings of the OTU2_XP card for 10G Ethernet LAN Phy to WAN Phy configuration. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the OTU2_XP card where you want to change the path settings.
Step 2 Click the Provisioning > Path > SONET/SDH tab. You can now provision the SF BER and SD BER values.
Step 3 Modify any of the OTU2_XP path settings described in Table 11-191 .
Sets the signal fail bit error rate (SONET [ANSI] or SDH [ETSI]). |
|||
Sets the signal degrade bit error rate (SONET [ANSI] or SDH [ETSI]). |
Step 5 Return to your originating procedure (NTP).
NTP-G162 Change the ALS Maintenance Settings
This procedure changes the ALS maintenance settings for the TXP, MXP, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, OTU2_XP, 100G-LC-C, 10x10G-LC, CFP-LC, WSE, AR_MXP, AR_XP, and AR_XPE cards. |
|
Note The automatic laser shutdown (ALS) function is normally disabled for TXP, MXP, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, OTU2_XP, 100G-LC-C, 10x10G-LC, CFP-LC, WSE, AR_MXP, AR_XP, and AR_XPE cards. Enable ALS only when the cards are directly connected to each other.
Note ALS is applicable only for OCn and OTN payloads.
Step 1 In node view (single-shelf mode) or shelf view (multishelf mode), double-click the TXP, MXP, GE_XP, 10GE_XP, GE_XPE, 10GE_XPE, OTU2_XP, 100G-LC-C, 10x10G-LC, CFP-LC, WSE, AR_MXP, AR_XP, or AR_XPE card where you want to change the ALS maintenance settings.
Step 2 Click the Maintenance > ALS tabs.
Step 3 Modify any of the settings described in Table 11-192 . The provisionable parameters are listed in the Options column in the table.
Step 4 Click Apply . If the change affects traffic, a warning message displays. Click Yes to complete the change.
Stop. You have completed this procedure.
NTP-G302 Configure Loopback on 100G-LC-C, 10x10G-LC, CFP-LC, and WSE Cards
Step 1 In node view (single-shelf mode) or shelf view (multishelf mode), double-click the 100G-LC-C, 10x10G-LC, CFP-LC or WSE card where you want to change the loopback settings. The card view appears.
Step 2 Click Maintenance > Loopback tab.
Step 3 Modify any of the settings described in Table 11-193 . The provisionable parameters are listed in the Options column of the table.
Note Before you configure a loopback, the port admin state must be set to OOS,MT(ANSI) or Locked,maintenance (ETSI).
Sets the port service state unless network conditions prevent the change. For more information about administrative states, see the Administrative and Service States document. |
||
(Display only) Identifies the autonomously generated state that gives the overall condition of the port. Service states appear in the format: Primary State-Primary State Qualifier, Secondary State. For more information about service states, see the Administrative and Service States document. |
||
Configures or clears a port for a terminal (inward) or facility (line) loopback on the required port. |
Stop. You have completed this procedure.
NTP-G299 Configure the Backplane Loopback on 100G-LC-C, 10x10G-LC, and CFP-LC Cards
Note This procedure is traffic-affecting.
Step 1 In node view (single-shelf mode) or shelf view (multishelf mode), double-click the 100G-LC-C, 10x10G-LC, and CFP-LC card where you want to change the backplane loopback settings. The card view appears.
Step 2 Click Maintenance > Card tabs.
Step 3 Modify any of the settings described in Table 11-194 . The provisionable parameters are listed in the Options column in the table.
Note Before you configure a backplane loopback, the port admin state must be set to OOS,MT(ANSI) or Locked,maintenance (ETSI).
Sets the port service state unless network conditions prevent the change. For more information about administrative states, see the Administrative and Service States document. |
||
(Display only) Identifies the autonomously generated state that gives the overall condition of the port. Service states appear in the format: Primary State-Primary State Qualifier, Secondary State. For more information about service states, see the Administrative and Service States document. |
||
Configures or clears backplane terminal (Inward) or facility (Line) loopback on the card. You can configure the backplane loopback only if the card is removed from service. |
Stop. You have completed this procedure.
Note Perform Step 1 through Step 4 if you are updating the node software. Otherwise continue with Step 5 to force FPGA image upgrade on MXP_MR_10DME_C or MXP_MR_10DME_L card.
Step 1 Close the CTC window, if open.
Step 2 Delete the CTC Cache from the CTC Launcher browser window.
Step 3 Close the CTC Launcher browser window.
Step 4 Relaunch the CTC Launcher browser window.
Step 5 In node view (single-shelf mode) or shelf view (multishelf mode), double-click the MXP_MR_10DME_C or MXP_MR_10DME_L card to be upgraded.
Step 6 For all ports being provisioned on the card, click the Provisioning > Line tabs.
a. Click the Admin State table cell and choose OOS,DSBLD (ANSI) or Locked,Disabled (ETSI).
Step 7 Click the Provisioning > Card tabs.
Step 8 Change the Card Mode as needed:
- FC-GE_ISC—Choose this option if you will provision any of the following PPM port rates: FC1G (Ports 1-1 through 4-1), FC2G (Ports 1-1 and 3-1 only), FICON1G (Ports 1-1 through 4-1), FICON2G (Ports 1-1 and 3-1 only), ONE_GE (Ports 1-1 through 4-1), ISC3 COMPAT (Ports 1-1 through 4-1), ISC3 PEER 1G (Ports 1-1 through 4-1), and ISC3 PEER 2G (Ports 1-1 and 3-1 only).
- FC4G—Choose this option if you will provision an FC4G or FICON4G PPM (Port 1-1 only).
Step 9 Click the Force FPGA Update button. This upgrades the FPGA image in the MXP_MR_10DME_C or MXP_MR_10DME_L card, as appropriate. The MXP_MR_10DME_C or MXP_MR_10DME_L card reboots and the FPGA now contains the updated image.
Step 10 For all ports being provisioned on the card, click the Provisioning > Line tabs.
a. Click the Admin State table cell and choose IS (ANSI) or Unlocked (ETSI).
Stop. You have completed this procedure.
NTP-G196 Force FPGA Update When the Card is Part of a Protection Group
This procedure forces an upgrade of the FPGA image on the MXP_MR_10DME_C and MXP_MR_10DME_L cards when the card is part of a protection group. |
|
Note This procedure applies to a near-end node that has two MXP_MR_10DME_C or MXP_MR_10DME_L cards, one card acting as the working card and the other as the protect card. The far-end node has a similar configuration. The near-end working card trunk port is connected to the far-end working card trunk port. The near-end protect card trunk port is connected to the far-end protect card trunk port.
Note Perform Step 1 through Step 4 if you are updating the node software. Otherwise, continue with Step 5 to force FPGA image upgrade on MXP_MR_10DME_C or MXP_MR_10DME_L card.
Step 1 Close the CTC window, if open.
Step 2 Delete the CTC Cache from the CTC Launcher browser window.
Step 3 Close the CTC Launcher browser window.
Step 4 Relaunch the CTC Launcher browser window.
Step 5 Ensure traffic is running on the near-end and far-end working cards for each protection group on the MXP_MR_10DME_C or MXP_MR_10DME_L card.
Step 6 In node view (single-node mode) or multishelf view (multishelf mode), click the Provisioning > Protection tab.
Step 7 For each protection group, verify that the working card client port is reported as working/active and the protect card client port is reported as protect/standby.
Step 8 Repeat Steps 6 and 7 for the far-end node.
Step 9 For each protection group on the near-end and far-end nodes, complete the “DLP-G182 Apply a Lockout” task to prevent traffic from switching to the protect card.
Step 10 At the near-end and far-end nodes, complete the G192 Force FPGA Update to force an upgrade of the FPGA image on the protect card.
Step 11 For each protection group on the near-end and far-end nodes, complete the “DLP-G183 Clear a Lock-On or Lockout” task to remove a lockout and return a protection group to its usual switching method.
Step 12 For each protection group on the near-end and far-end nodes, complete the “DLP-G179 Apply a Force Y-Cable or Splitter Protection Switch” task to move traffic from the working to the protect card.
Step 13 At the near-end and far-end nodes, complete the G192 Force FPGA Update to force an upgrade of the FPGA image on the working card.
Step 14 For each protection group on the near-end and far-end nodes, complete the “DLP-G180 Clear a Manual or Force Y-Cable or Splitter Protection Switch” task to clear a Force protection switch on the working card. If the protection group is revertive, this operation causes the traffic to revert to the working card. If the protection group is non-revertive, this operation causes the traffic to remain on the protect card.
Stop. You have completed this procedure.
NTP-G232 Enabling Error Decorrelator
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the TXP_MR_10EX_C, MXP_2.5G_10EX_C, or MXP_MR_10DMEX_C card where you want to enable error decorrelator.
Step 2 Click the Provisioning > Line> Error Decorrelator Settings tabs.
Step 3 In the Error Decorrelator Settings area, Select Enable.
Note To inter-operate with other cards, disable the error decorrelator.
Click the Provisioning > Line> Error Decorrelator Settings tabs and then select Disable.
NTP-G315 Enable or Disable the Wavelength Drifted Channel Automatic Shutdown Feature
This procedure allows you to enable or disable the wavelength drifted channel automatic shutdown feature for 40-SMR1-C, 40-SMR2-C, 80-WXC-C, 40-WXC-C, and 40-WSS-C cards. |
|
Step 1 In the node view (single-shelf mode) or multishelf view (multishelf mode), click the Provisioning > Defaults tabs. The Node Defaults page opens.
Step 2 Select the card from the Defaults Selector pane where you want to enable or disable the wavelength drifted channel automatic shutdown feature.
Step 3 Select the <card name>.config.card.WavelengthDrift from the Default Name column. Choose Disable or Enable from the Default Value drop-down list for the selected card.
For example, if you select 40-SMR2-C card from the Defaults Selector folder, the Default Name column reads “40-SMR2-C.config.card.WavelengthDrift”.
Step 4 Click Apply to save changes.
Stop. You have completed this procedure.
NTP-G316 Enable REP and FAPS on the same port
Note The FAPS master node on the edge ring should never be the node that has a common FAPS and REP port.
You can configure REP and FAPS on port 22 and 21 for GE_XP cards, and port 4 and 3 for 10GE_XP cards.
Step 1 To enable REP, complete the following procedures:
a. G645 Create a Segment Using CTC
b. G647 Activate VLAN Load Balancing Using CTC
Step 2 To enable FAPS, complete the G381 Provision the GE_XP, 10GE_XP, GE_XPE, and 10GE_XPE Layer 2 Protection Settings.
Stop. You have completed this procedure.
NTP-G321 Provision Multiple Operating Modes on AR_MXP, AR_XP, or AR_XPE Cards
This procedure enables you to provision multiple operating modes on the AR_MXP, AR_XP, or AR_XPE cards. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the AR_MXP, AR_XP, or AR_XPE card where you want to provision an operating mode. The card view appears.
Step 2 Click the Provisioning > Card tabs.
Step 3 In the Card tab, click Create . The Operating Mode Configuration Creation window appears.
Step 4 From the Card Config Rate Selection section, select Low Rate Mode or High Rate Mode .
Step 5 In the Card Config Selection section:
a. Choose the Operating Mode from the drop-down list.
The Operating Mode options vary depending on the Card Type (AR_MXP, AR_XP, or AR_XPE) and Card Config Rate Selection.
b. For MXP_DME and MXPP_DME card modes, choose the Client Trunk Mapping from the drop-down list. For other card modes, CTC automatically selects the client trunk mapping.
Step 7 Select the appropriate trunk port that is available and click Next .
Step 8 Select the appropriate client port that is available and click Finish .
The selected operating mode is provisioned on the AR_MXP, AR_XP, or AR_XPE card.
Note When you want to upgrade the FPGA image on the AR_MXP, AR_XP, or AR_XPE card, click the FPGA/FIRMWARE Upgrade button. This upgrades the FPGA image on the AR_MXP, AR_XP, or AR_XPE card as appropriate, without the need of upgrading the whole network.
Stop. You have completed this procedure.
NTP-G322 Modify the AR_MXP, AR_XP, or AR_XPE Card Line Settings and PM Parameter Thresholds
This procedure changes the line and PM parameter threshold settings of the AR_MXP, AR_XP, or AR_XPE cards. |
|
Step 1 Complete the DLP-G46 Log into CTC task at the node where you want to change the AR_MXP, AR_XP, or AR_XPE card line and PM threshold settings. If you are already logged in, proceed to Step 2.
Step 2 As needed, complete the G103 Back Up the Database to preserve the existing transmission settings.
Step 3 Perform any of the following tasks as needed:
- G695 Change the AR_MXP, AR_XP, or AR_XPE Card Line Settings
- G696 Change the AR_MXP, AR_XP, or AR_XPE Card Ethernet Settings
- G697 Change the AR_MXP, AR_XP, or AR_XPE Card SONET/SDH Settings
- G698 Change the AR_MXP, AR_XP, or AR_XPE Card Section Trace Settings
- G699 Enable Auto Sensing for AR_MXP, AR_XP, or AR_XPE Cards
- G700 Change the AR_MXP, AR_XP, or AR_XPE Card SONET/SDH Line Thresholds
- G701 Change the AR_MXP, AR_XP, or AR_XPE Card Line RMON Thresholds
- G702 Provision the AR_MXP, AR_XP, or AR_XPE Card with Trunk Port Alarm and TCA Thresholds
- G703 Provision the AR_MXP, AR_XP, or AR_XPE Card Client Port Alarm and TCA Thresholds
- G704 Change the AR_MXP, AR_XP, or AR_XPE Card OTN Settings
- G734 View the Mapping of ODU Object with Client Port
Note To use the Alarm Profiles tab, including creating alarm profiles and suppressing alarms, see the Alarm and TCA Monitoring and Management document.
Stop. You have completed this procedure.
DLP-G695 Change the AR_MXP, AR_XP, or AR_XPE Card Line Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the AR_MXP, AR_XP, or AR_XPE card where you want to change the line settings.
Step 2 Click the Provisioning > Line > Ports tabs. Tabs and parameter selections vary according to PPM provisioning.
Step 3 Modify any of the line settings in the Ports tab as described in Table 11-195 .
User-defined. Name can be up to 32 alphanumeric or special characters, or both. Blank by default. See the G104 Assign a Name to a Port. Note You can provision a string (port name) for each fiber channel/FICON interface on the AR_MXP, AR_XP, or AR_XPE card, 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. |
||
Sets the port service state unless network conditions prevent the change. For more information about administrative states, see the Administrative and Service States document. |
||
(Display only) Identifies the autonomously generated state that gives the overall condition of the port. Service states appear in the format: Primary State-Primary State Qualifier, Secondary State. For more information about service states, see the Administrative and Service States document. |
||
|
||
Sets the automatic in-service soak period. Double-click the time and use the up and down arrows to change settings. |
||
The reach distances that appear in the drop-down list depend on the card:
|
||
Shuts down the far-end laser in response to certain defects. (Squelch does not apply to ISC COMPACT payloads.) |
||
Sets the mode of operation. (This option is only available for SONET/SDH payloads). |
Step 5 Return to your originating procedure (NTP).
DLP-G696 Change the AR_MXP, AR_XP, or AR_XPE Card Ethernet Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the AR_MXP, AR_XP, or AR_XPE card where you want to change the Ethernet settings. The card view appears.
Step 2 Click the Provisioning > Line > Ethernet tabs.
Step 3 Modify any of the Ethernet settings in the Ethernet tab as described in Table 11-196 . The parameters that appear depend on the card mode.
DLP-G697 Change the AR_MXP, AR_XP, or AR_XPE Card SONET/SDH Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the AR_MXP, AR_XP, or AR_XPE card where you want to change the SONET (OC-192)/SDH (STM-64) settings.
Step 2 Click the Provisioning > Line > SONET (ANSI) or SDH (ETSI) tabs. Tabs and parameter selections vary according to PPM provisioning.
Step 3 Modify any of the settings as described in Table 11-197 .
User-defined. Name can be up to 32 alphanumeric or special characters, or both. Blank by default. See the G104 Assign a Name to a Port. |
||
Sets the port service state unless network conditions prevent the change. For more information about administrative states, see the Administrative and Service States document. |
||
(Display only) Identifies the autonomously generated state that gives the overall condition of the port. Service states appear in the format: Primary State-Primary State Qualifier, Secondary State. For more information about service states, see the Administrative and Service States document. |
||
SF BER19 |
||
SD BER 1 |
||
Sets the ALS function mode. The DWDM transmitter supports ALS according to ITU-T G.644 (06/99). ALS can be disabled or enabled for one of the three mode options. |
|
|
Sets the automatic in-service soak period. Double-click the time and use the up and down arrows to change settings. |
||
Sets the ProvidesSync card parameter. If checked, the card is provisioned as a NE timing reference. |
||
Sets the EnableSync card parameter. Enables synchronization status messages (S1 byte), which allow the node to choose the best timing source. |
||
Overrides the synchronization status message (SSM) and the synchronization traceability unknown (STU) value. If the node does not receive an SSM signal, it defaults to STU. |
||
The reach distances that appear in the drop-down list depend on the card:
|
||
Step 5 Return to your originating procedure (NTP).
DLP-G698 Change the AR_MXP, AR_XP, or AR_XPE Card Section Trace Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the AR_MXP, AR_XP, or AR_XPE card where you want to change the section trace settings.
Step 2 Click the Provisioning > Line > Section Trace tabs. Tabs and parameter selections vary according to PPM provisioning.
Step 3 Modify any of the settings in the Section Trace tab as described in Table 11-198 .
Step 5 Return to your originating procedure (NTP).
DLP-G699 Enable Auto Sensing for AR_MXP, AR_XP, or AR_XPE Cards
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the AR_MXP, AR_XP, or AR_XPE card where you want to enable auto sensing.
Step 2 Click the Provisioning > Line > Auto Ports tabs. Tabs and parameter selections vary according to PPM provisioning.
Step 3 Modify any of the settings in the Auto Ports tab as described in Table 11-199 .
DLP-G700 Change the AR_MXP, AR_XP, or AR_XPE Card SONET/SDH Line Thresholds
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the AR_MXP, AR_XP, or AR_XPE card where you want to change the SONET/SDH line threshold settings.
Step 2 Click the Provisioning > Line Thresholds > SONET Thresholds (ANSI) or SDH Thresholds (ETSI) tabs.
Step 3 Modify any of the settings as shown in Table 11-200 .
Note You must modify Near End and Far End independently; 15 Min and 1 Day independently; and Line and Section independently. To do so, choose the appropriate radio button and click Refresh.
Step 5 Return to your originating procedure (NTP).
DLP-G701 Change the AR_MXP, AR_XP, or AR_XPE Card Line RMON Thresholds
This task changes the line threshold settings for AR_MXP, AR_XP, or AR_XPE cards carrying Ethernet, FC/FICON, or ISC/ISC3 payloads. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the AR_MXP, AR_XP, or AR_XPE card where you want to change the line RMON threshold settings in card view.
Step 2 Click the Provisioning > Line Thresholds > RMON Thresholds tabs.
Step 3 Click Create . The Create Threshold dialog box appears.
Step 4 From the Port drop-down list, choose the applicable port, either the payload port, for example “1-1 (ONE_GE)”, or the equivalent ITU-T G.7041 GFP (Generic Frame Procedure) port.
Step 5 From the Variable drop-down list, choose an Ethernet, FC, FICON, or ISC variable. See Table 11-201 for a list of available Ethernet variables, Table 11-202 for a list of FC and FICON variables, Table 11-203 for a list of ISC and ISC3 variables, and Table 11-204 for a list of GFP variables.
Step 6 From the Alarm Type drop-down list, indicate whether the event will be triggered by the rising threshold, the falling threshold, or both the rising and falling thresholds.
The available options are Rising Threshold, Falling Threshold, and Both Rising and Falling Threshold
Step 7 From the Sample Type drop-down list, choose either Relative or Absolute . Relative restricts the threshold to use the number of occurrences in the user-set sample period. Absolute sets the threshold to use the total number of occurrences, regardless of time period.
Step 8 Enter the appropriate number of seconds in the Sample Period field.
Step 9 Enter the appropriate number of occurrences in the Rising Threshold field.
For a rising type of alarm, the measured value must move from below the falling threshold to above the rising threshold. For example, if a network is running below a rising threshold of 1000 collisions every 15 seconds and a problem causes 1001 collisions in 15 seconds, the excess occurrences trigger an alarm.
Step 10 Enter the appropriate number of occurrences in the Falling Threshold field. In most cases a falling threshold is set lower than the rising threshold.
A falling threshold is the counterpart to a rising threshold. When the number of occurrences is above the rising threshold and then drops below a falling threshold, it resets the rising threshold. For example, when the network problem that caused 1001 collisions in 15 seconds subsides and creates only 799 collisions in 15 seconds, occurrences fall below a falling threshold of 800 collisions. This resets the rising threshold so that if network collisions again spike over a 1000 per 15-second period, an event again triggers when the rising threshold is crossed. An event is triggered only the first time a rising threshold is exceeded (otherwise, a single network problem might cause a rising threshold to be exceeded multiple times and cause a flood of events).
Note To view all RMON thresholds, click Show All RMON thresholds.
Step 12 Return to your originating procedure (NTP).
DLP-G702 Provision the AR_MXP, AR_XP, or AR_XPE Card with Trunk Port Alarm and TCA Thresholds
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the AR_MXP, AR_XP, or AR_XPE card where you want to provision the trunk port alarm and TCA threshold settings.
Step 2 Click the Provisioning > Optics Thresholds tabs.
Note You must modify 15 Min and 1 Day independently. To do so, choose the appropriate radio button and click Refresh.
Note Do not modify the Laser Bias parameters.
Step 3 If TCA is not checked, check the TCA check box and then click Refresh . If it is checked, continue with Step 4.
Step 4 Verify if the trunk port (Port 9) TCA thresholds are set. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and pressing Enter.
Step 5 Under Types, click the Alarm radio button and click Refresh .
Note Do not modify the Laser Bias parameters.
Step 6 Verify if the trunk port (Port 9) Alarm thresholds are set. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and pressing Enter.
Step 8 Return to your originating procedure (NTP).
DLP-G703 Provision the AR_MXP, AR_XP, or AR_XPE Card Client Port Alarm and TCA Thresholds
This task provisions the client port alarm and TCA thresholds for the AR_MXP, AR_XP, and AR_XPE cards. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the AR_MXP, AR_XP, or AR_XPE card where you want to change the client port alarm and TCA threshold settings.
Step 2 Click the Provisioning > Optics Thresholds tabs. The TCA thresholds are shown by default.
Step 3 Referring to Table 11-135 , verify the TCA thresholds for client ports (ports 1 through 8) for RX Power High, RX Power Low, TX Power High, and TX Power Low based on the client interface at the other end. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and pressing Enter.
Note Do not modify the Laser Bias parameters.
Note You must modify 15 Min and 1 Day independently. To do so, choose the appropriate radio button and click Refresh.
Note The hardware device that plugs into a AR_MXP, AR_XP, or AR_XPE card faceplate to provide a fiber interface to the card is called a Small Form-factor Pluggable (SFP or XFP). In CTC, SFPs and XFPs are called pluggable port modules (PPMs). SFPs/XFPs are hot-swappable I/O devices that plug into a port to link the port with the fiber-optic network. Multirate PPMs have provisionable port rates and payloads. For more information about SFPs and XFPs, see the “SFP, SFP+, XFP, CXP, and CFP Modules” section.
ONS-SC-155-EL |
|||||
Step 5 Repeat Steps 3 and 4 to provision each additional client port.
Step 6 Under Types, click the Alarm radio button and click Refresh .
Step 7 Referring to Table 11-206 , verify the client port (Ports 1 through 8) Alarm thresholds for RX Power High, RX Power Low, TX Power High, and TX Power Low based on the client interface that is provisioned. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and hitting Enter .
ONS-SC-155-EL |
|||||
Step 9 Repeat Steps 7 and 8 to provision each additional client port.
Step 10 Return to your originating procedure (NTP).
DLP-G704 Change the AR_MXP, AR_XP, or AR_XPE Card OTN Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the AR_MXP, AR_XP, or AR_XPE card where you want to change the OTN settings.
Step 2 Click the Provisioning > OTN tabs, then choose one of the following subtabs: OTN Lines, G.709 Thresholds, FEC Thresholds, Trail Trace Identifier, or Proactive Protection Regen.
Step 3 Modify any of the settings described in Tables 11-207 through 11-211 .
Note You must modify Near End and Far End; 15 Min and 1 Day; and SM and PM independently. To do so, choose the appropriate radio button and click Refresh.
Table 11-207 describes the values on the Provisioning > OTN > OTN Lines tab.
Table 11-208 describes the values on the Provisioning > OTN > G.709 Thresholds tab.
Port20 |
||
Numeric. Can be set for Near End or Far End, for 15-minute or one-day intervals, or for SM (OTUk) or PM (ODUk). Select an option and click Refresh . |
||
Numeric. Can be set for Near End or Far End, for 15-minute or one-day intervals, or for SM (OTUk) or PM (ODUk). Select an option and click Refresh . |
||
Numeric. Can be set for Near End or Far End, for 15-minute or one-day intervals, or for SM (OTUk) or PM (ODUk). Select an option and click Refresh . |
||
Numeric. Can be set for Near End or Far End, for 15-minute or one-day intervals, or for SM (OTUk) or PM (ODUk). Select an option and click Refresh . |
||
Numeric. Can be set for Near End or Far End, for 15-minute or one-day intervals, or for SM (OTUk) or PM (ODUk). Select an option and click Refresh . |
Table 11-209 describes the values on the Provisioning > OTN > FEC Threshold tab.
Table 11-210 describes the values on the Provisioning > OTN > Trail Trace Identifier tab.
Table 11-211 describes the values on the Provisioning > OTN > Proactive Protection Regen tabs.
Note Proactive protection regen is supported only when the AR_MXP, AR_XP, or AR_XPE card is in high-rate REGEN card mode.
Step 5 Return to your originating procedure (NTP).
DLP-G734 View the Mapping of ODU Object with Client Port
This procedure allows you to view the mapping of ODU object with the corresponding client port for the AR_XPE card. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the AR_XPE card to view the ODU object mapping with the corresponding client port. The card view appears.
Step 2 Click the Provisioning > Card > ODU Interfaces tabs. Displays the parameters as described in Table 11-213 .
Step 3 Return to your originating procedure (NTP).
NTP-G235 Provision an Operating Mode on the 100G-LC-C, 10x10G-LC, or CFP-LC Card
This procedure enables you to provision an operating mode on the 100G-LC-C, 10x10G-LC, or CFP-LC card. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 100G-LC-C, 10x10G-LC, or CFP-LC card where you want to provision an operating mode. The card view appears.
Step 2 Click the Provisioning > Card tabs.
Step 3 In the Card tab, click Create . The Operating Mode Configuration Creation window appears.
Step 4 Choose the configuration from the Card Configuration drop-down list. The card configuration options vary depending on the card. For more information about the card configurations, see Table 11-37 . If the TXP-10G, RGN-10G, or LOW LATENCY mode was selected on the 10x10G-LC card, go to Step 6. If the FANOUT-10x10G mode was selected in the 10x10G-LC card, go to Step 7.
Step 5 Choose the slot number from the Peer Card drop-down list where the 100G-LC-C card is located. This field is enabled only if a peer card is required for the configuration.
Step 6 Select the port pair in the Card Configuration Dialog area. The 10x10G-LC card supports a maximum of five TXP-10G modes, five RGN-10G modes, five LOW LATENCY modes or a combination of five TXP-10G, RGN-10G, and LOW LATENCY modes.
Step 7 Click Finish . The selected operating mode is provisioned on the 100G-LC-C, 10x10G-LC, or CFP-LC card.
Step 8 Complete the DLP-G726 Preprovisioning a Multirate PPM task.
Step 9 Complete the G278 Provision the Optical Line Rate
Stop. You have completed this procedure.
NTP-G236 Modify the 100G-LC-C, 10x10G-LC, or CFP-LC Card Line Settings and PM Parameter Thresholds
This procedure changes the line and PM parameter threshold settings of the 100G-LC-C, 10x10G-LC, or CFP-LC cards. |
|
Step 1 As needed, complete the G103 Back Up the Database to preserve the existing transmission settings.
Step 2 Perform any of the following tasks as needed:
- G714 Change the 100G-LC-C, 10x10G-LC, or CFP-LC Card Line Settings
- G715 Change the 100G-LC-C, 10x10G-LC, or CFP-LC Card Ethernet Settings
- G716 Change the 10x10G-LC Card SONET/SDH Settings
- G717 Change the 10x10G-LC Card Section Trace Settings
- G718 Change the 10x10G-LC Card SONET/SDH Line Thresholds
- G719 Change the 100G-LC-C, 10x10G-LC, or CFP-LC Card Line RMON Thresholds
- G720 Provision the 100G-LC-C Card with Trunk Port Alarm and TCA Thresholds
- G721 Provision the 100G-LC-C, 10x10G-LC, or CFP-LC Client Port Alarm and TCA Thresholds
- G722 Change the 100G-LC-C Card OTN Settings
Note To use the Alarm Profiles tab, including creating alarm profiles and suppressing alarms, see the Alarm and TCA Monitoring and Management document.
Stop. You have completed this procedure.
DLP-G714 Change the 100G-LC-C, 10x10G-LC, or CFP-LC Card Line Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 100G-LC-C, 10x10G-LC, or CFP-LC card where you want to change the line settings.
Step 2 Click the Provisioning > Line > Ports tabs. Tabs and parameter selections vary according to pluggable port modules (PPM) provisioning.
Step 3 Modify any of the line settings in the Ports tab as described in Table 11-213 .
User-defined. Name can be up to 32 alphanumeric or special characters, or both. Blank by default. See the G104 Assign a Name to a Port. |
||
Sets the port service state unless network conditions prevent the change. For more information about administrative states, see the Administrative and Service States document. |
||
(Display only) Identifies the autonomously generated state that gives the overall condition of the port. Service states appear in the format: Primary State-Primary State Qualifier, Secondary State. For more information about service states, see the Administrative and Service States document. |
||
|
||
Sets the automatic in-service (AINS) soak period. Double-click the time and use the up and down arrows to change settings. |
||
Table 11-214 provides the reach distances for different payloads on the 10x10G-LC, 100G-LC-C, and CFP-LC cards. Note The reach distances that appear in the drop-down list depend on the card. |
||
Note When an OTU2 payload is provisioned on the 10x10G-LC card in the TXP-10G or RGN-10G operating mode, the overclock parameter is automatically set to ON. |
||
(100G-LC-C cards only) Sets the threshold for minimum chromatic dispersion. |
||
(100G-LC-C cards only) Sets the threshold for maximum chromatic dispersion. |
||
If checked, the Tx optical power is turned off. This can be done when the port is out of service or in maintenance. |
||
Shuts down the far-end laser in response to certain defects. (Squelch does not apply to ISC COMPACT payloads.) |
Note When the 100G-LC-C card is used in the standalone mode or with the CFP-LC card configured in the CFP-TXP mode, the value can be set to Squelch or AIS on the trunk port of the 100G-LC-C card. When the 100G-LC-C card is used with the CFP-LC card configured CFP-MXP mode, the value can be set to AIS on the trunk port of the 100G-LC-C card. |
|
Note The mapping mode can be configured to GFP for 10GE payloads. The GFP port is placed in service when both the client and trunk ports of the 10x10G-LC card are in service. |
||
Step 5 Return to your originating procedure (NTP).
DLP-G715 Change the 100G-LC-C, 10x10G-LC, or CFP-LC Card Ethernet Settings
This task changes the Ethernet settings of the 100G-LC-C, 10x10G-LC, or CFP-LC cards. Note The ethernet settings of the CFP-LC card can be changed on the virtual port of the peer 100G-LC-C card. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 100G-LC-C, 10x10G-LC, or CFP-LC card where you want to change the Ethernet settings. The card view appears.
Step 2 Click the Provisioning > Line > Ethernet tabs.
Step 3 Modify any of the Ethernet settings in the Ethernet tab as described in Table 11-215 . The parameters that appear depend on the card mode.
Sets the port service state unless network conditions prevent the change. For more information about administrative states, see the Administrative and Service States document. |
||
(Display only) Identifies the autonomously generated state that gives the overall condition of the port. Service states appear in the format: Primary State-Primary State Qualifier, Secondary State. For more information about service states, see the Administrative and Service States document. |
||
|
||
Sets the automatic in-service (AINS) soak period. Double-click the time and use the up and down arrows to change settings. |
||
Note The reach distances that appear in the drop-down list depend on the card. |
||
Sets the maximum size of the Ethernet frames accepted by the port. The port must be in OOS/locked state. |
||
Step 5 Return to your originating procedure (NTP).
DLP-G716 Change the 10x10G-LC Card SONET/SDH Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 10x10G-LC card where you want to change the SONET (OC-192)/SDH (STM-64) settings.
Step 2 Click the Provisioning > Line > SONET (ANSI) or SDH (ETSI) tabs. Tabs and parameter selections vary according to PPM provisioning.
Step 3 Modify any of the settings as described in Table 11-216 .
User-defined. Name can be up to 32 alphanumeric or special characters, or both. Blank by default. See the G104 Assign a Name to a Port. |
||
Sets the port service state unless network conditions prevent the change. For more information about administrative states, see the Administrative and Service States document. |
||
(Display only) Identifies the autonomously generated state that gives the overall condition of the port. Service states appear in the format: Primary State-Primary State Qualifier, Secondary State. For more information about service states, see the Administrative and Service States document. |
||
Sets the automatic laser shutdown (ALS) function mode. The DWDM transmitter supports ALS according to ITU-T G.644 (06/99). ALS can be disabled or enabled for one of the three mode options. |
|
|
Sets the automatic in-service (AINS) soak period. Double-click the time and use the up and down arrows to change settings. |
||
Sets the ProvidesSync card parameter. If checked, the card is provisioned as a NE timing reference. |
||
Sets the EnableSync card parameter. Enables synchronization status messages (S1 byte), which allow the node to choose the best timing source. |
||
Overrides the synchronization status message (SSM) and the synchronization traceability unknown (STU) value. If the node does not receive an SSM signal, it defaults to STU. |
||
Note The reach distances that appear in the drop-down list depend on the card. |
||
Step 5 Return to your originating procedure (NTP).
DLP-G717 Change the 10x10G-LC Card Section Trace Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 10x10G-LC card where you want to change the section trace settings.
Step 2 Click the Provisioning > Line > Section Trace tabs. Tabs and parameter selections vary according to PPM provisioning.
Step 3 Modify any of the settings in the Section Trace tab as described in Table 11-217 .
Step 5 Return to your originating procedure (NTP).
DLP-G718 Change the 10x10G-LC Card SONET/SDH Line Thresholds
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 10x10G-LC card where you want to change the SONET/SDH line threshold settings.
Step 2 Click the Provisioning > Line Thresholds > SONET Thresholds (ANSI) or SDH Thresholds (ETSI) tabs.
Step 3 Modify any of the settings as shown in Table 11-218 .
Note You must modify each of these options independently: Near End and Far End, 15 Min and 1 Day, and Line and Section. To do so, choose the appropriate radio button and click Refresh.
Step 5 Return to your originating procedure (NTP).
DLP-G719 Change the 100G-LC-C, 10x10G-LC, or CFP-LC Card Line RMON Thresholds
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 100G-LC-C, 10x10G-LC, or CFP-LC card where you want to change the line RMON threshold settings in the card view.
Step 2 Click the Provisioning > Line Thresholds > RMON Thresholds tabs.
Step 3 Click Create . The Create Threshold dialog box appears.
Step 4 From the Port drop-down list, choose the applicable port, either the payload port, for example “1-1 (ONEHUNDRED_GE)” port.
Step 5 From the Variable drop-down list, choose an Ethernet, FC, FICON, or GFP variable. See Table 11-219 for a list of available Ethernet variables, Table 11-220 for a list of FC and FICON variables, and Table 11-221 for a list of GFP variables.
ifInUcastPkts21 |
Total number of packets delivered by this sublayer to a higher sublayer that are not addressed to a multicast or broadcast address. |
ifInMulticastPkts 1 |
Total number of packets delivered by this sublayer to a higher sublayer that are addressed to a multicast address. For a MAC layer protocol, this includes both group and functional addresses. |
ifInBroadcastPkts 1 |
Total number of packets delivered by this sublayer to a higher sublayer that are addressed to a broadcast address. |
Total number of octets transmitted out of the interface, including framing characters. |
|
Total count of packets transmitted to a unicast group destination address. |
|
Total number of packets that higher-level protocols requested to be transmitted, which were addressed to a multicast address at this sublayer. These include packets that were discarded or not sent. For a MAC layer protocol, this includes both group and functional addresses. |
|
Total number of packets that higher-level protocols requested to be transmitted, which were addressed to a broadcast address at this sublayer. These include packets that were discarded or not sent. |
|
Total number of frames received on a particular interface that are not an integral number of octets in length and do not pass the FCS check. This counter is only valid for FE modes of operation. |
|
Total number of frames received on a particular interface that are an integral number of octets in length but do not pass the FCS check. |
|
Total number of frames received on a particular interface that exceed the maximum permitted frame size. |
|
Total number of packets received that were less than 64 octets long (excluding framing bits, but including FCS octets) and were otherwise well-formed. |
|
Total number of packets received that were less than 64 octets in length (excluding framing bits, but including FCS octets) and had either a bad FCS with an integral number of octets (FCS error) or a bad FCS with a non-integral number of octets (alignment error). Note that it is entirely normal for etherStatsFragments to increment. This is because it counts both runts (which are normal occurrences due to collisions) and noise hits. |
|
Total number of frames received on an interface in both Rx and Tx directions. |
|
Total number of packets (including bad packets) received that were 64 octets in length (excluding framing bits, but including FCS octets). |
|
Total number of packets (including bad packets) received that were between 65 and 127 octets in length inclusive (excluding framing bits, but including FCS octets). |
|
Total number of packets (including bad packets) received that were between 128 and 255 octets in length inclusive (excluding framing bits, but including FCS octets). |
|
Total number of packets (including bad packets) received that were between 256 and 511 octets in length inclusive (excluding framing bits, but including FCS octets). |
|
Total number of packets (including bad packets) received that were between 512 and 1023 octets in length inclusive (excluding framing bits, but including FCS octets). |
|
Total number of packets (including bad packets) received that were between 1024 and 1518 octets in length inclusive (excluding framing bits, but including FCS octets). |
|
Total number of good packets received that were directed to the broadcast address. Note that this number does not include multicast packets. |
|
Total number of good packets received that were directed to a multicast address. Note that this number does not include packets directed to the broadcast address. |
|
Total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets) and were otherwise well-formed. |
|
Total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets), and had either a bad FCS with an integral number of octets (FCS error) or a bad FCS with a non-integral number of octets (alignment error). |
|
Total number of octets of data (including those in bad packets) received on the network (excluding framing bits, but including FCS octets). |
|
Total number of packets (including bad packets) received that were 1591 octets in length (excluding framing bits, but including FCS octets). |
|
Step 6 From the Alarm Type drop-down list, indicate whether the event will be triggered by the rising threshold, falling threshold, or both the rising and falling thresholds.
The available options are Rising Threshold, Falling Threshold, and Both Rising and Falling Threshold
Step 7 From the Sample Type drop-down list, choose either Relative or Absolute . Relative restricts the threshold to use the number of occurrences in the user-set sample period. Absolute sets the threshold to use the total number of occurrences, regardless of time period.
Step 8 Enter the appropriate number of seconds in the Sample Period field.
Step 9 Enter the appropriate number of occurrences in the Rising Threshold field.
For a rising type of alarm, the measured value must move from below the falling threshold to above the rising threshold. For example, if a network is running below a rising threshold of 1000 collisions every 15 seconds and a problem causes 1001 collisions in 15 seconds, the excess occurrences trigger an alarm.
Step 10 Enter the appropriate number of occurrences in the Falling Threshold field. In most cases a falling threshold is set lower than the rising threshold.
A falling threshold is the counterpart to a rising threshold. When the number of occurrences is above the rising threshold and then drops below a falling threshold, it resets the rising threshold. For example, when the network problem that caused 1001 collisions in 15 seconds subsides and creates only 799 collisions in 15 seconds, occurrences fall below a falling threshold of 800 collisions. This resets the rising threshold so that if network collisions again spike over a 1000 per 15-second period, an event again triggers when the rising threshold is crossed. An event is triggered only the first time a rising threshold is exceeded (otherwise, a single network problem might cause a rising threshold to be exceeded multiple times and cause a flood of events).
Note To view all RMON thresholds, check the Show All RMON thresholds checkbox.
Step 12 Return to your originating procedure (NTP).
DLP-G720 Provision the 100G-LC-C Card with Trunk Port Alarm and TCA Thresholds
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 100G-LC-C card where you want to provision the trunk port alarm and TCA threshold settings.
Step 2 Click the Provisioning > Optics Thresholds tabs.
Note You must modify 15 Min and 1 Day independently. To do so, choose the appropriate radio button and click Refresh.
Note Do not modify the Laser Bias parameters.
Step 3 If TCA is not checked, check the TCA check box and then click Refresh . If it is checked, continue with Step 4.
Step 4 Verify if the trunk port (Port 2) TCA thresholds for RX Power High, RX Power Low, TX Power High, TX Power Low, OSNR Power High, OSNR Power low, PMD High, PMD Low are set. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and pressing Enter.
Step 5 Under Types, click the Alarm radio button and click Refresh .
Note Do not modify the Laser Bias parameters.
Step 6 Verify if the trunk port (Port 2) Alarm thresholds for RX Power High, RX Power Low, TX Power High, TX Power Low are set. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and pressing Enter.
Step 8 Return to your originating procedure (NTP).
DLP-G721 Provision the 100G-LC-C, 10x10G-LC, or CFP-LC Client Port Alarm and TCA Thresholds
This task provisions the client port alarm and TCA thresholds for the 100G-LC-C, 10x10G-LC, or CFP-LC cards. |
|
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 100G-LC-C, 10x10G-LC, or CFP-LC where you want to change the client port alarm and TCA threshold settings.
Step 2 Click the Provisioning > Optics Thresholds tabs. The TCA thresholds are shown by default.
Step 3 Verify if the TCA thresholds for client ports for RX Power High, RX Power Low, TX Power High, and TX Power Low parameters are set based on the client interface at the other end. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and pressing Enter.
Note Do not modify the Laser Bias parameters.
Note You must modify 15 Min and 1 Day independently. To do so, choose the appropriate radio button and click Refresh.
Note The hardware device that plugs into a 100G-LC-C, 10x10G-LC, or CFP-LC card faceplate to provide a fiber interface to the card is called a Small Form-factor Pluggable (SFP, XFP, or CXP) or a C Form-factor Pluggable (CFP). In CTC, SFPs, XFPs, CXPs, and CFPs are called pluggable port modules (PPMs). SFPs/XFPs/CXPs/CFPs are hot-swappable I/O devices that plug into a port to link the port with the fiber-optic network. Multirate PPMs have provisionable port rates and payloads. For more information about SFPs, XFPs, CXPS, and CFPs, see the “SFP, SFP+, XFP, CXP, and CFP Modules” section.
Step 5 Repeat Steps 3 and 4 to provision each additional client port.
Step 6 Under Types, click the Alarm radio button and click Refresh .
Step 7 Verify if the client port Alarm thresholds for RX Power High, RX Power Low, TX Power High, and TX Power Low parameters are set based on the client interface that is provisioned. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and hitting Enter .
Step 9 Repeat Steps 7 and 8 to provision each additional client port.
Step 10 Return to your originating procedure (NTP).
DLP-G722 Change the 100G-LC-C Card OTN Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the 100G-LC-C card where you want to change the OTN settings.
Step 2 Click the Provisioning > OTN tabs, then choose one of the following subtabs: OTN Lines, ITU-T G.709 Thresholds, FEC Thresholds, Trail Trace Identifier, or Proactive Protection Regen.
Step 3 Modify any of the settings described in Tables Table 11-222 through Table 11-226 .
Note You must modify each of these options independently: Near End and Far End, 15 Min and 1 Day, and SM and PM. To do so, choose the appropriate radio button and click Refresh.
Table 11-222 describes the values on the Provisioning > OTN > OTN Lines tab.
Table 11-223 describes the values on the Provisioning > OTN > ITU-T G.709 Thresholds tab.
Table 11-224 describes the values on the Provisioning > OTN > FEC Thresholds tab.
Table 11-225 describes the values on the Provisioning > OTN > Trail Trace Identifier tab.
Table 11-226 describes the values on the Provisioning > OTN > Proactive Protection Regen tabs.
Note The Proactive Protection Regen feature is supported only when the 100G-LC-C card is in the TXP-100G or the RGN-100G card mode.
Step 5 Return to your originating procedure (NTP).
NTP-G338 Provision an Operating Mode on the WSE Card
Note You cannot edit the existing operating mode on the WSE card.
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the WSE card where you want to provision an operating mode. The card view appears.
Step 2 Click the Provisioning > Card tabs.
Step 3 In the Operating Modes tab, click Create . The Operating Mode Configuration Creation window appears.
Step 4 Choose the configuration from the Card Configuration drop-down list. The card configuration options are TXP-10G and RGN-10G modes.
Step 5 Select the defined port pair in the Card Configuration Dialog area. The WSE card supports a maximum of five TXP-10G modes, five RGN-10G modes, or a combination of five TXP-10G, and RGN-10G modes.
Step 6 Click Finish . The selected operating mode is provisioned on the WSE card.
Step 7 Complete the DLP-G726 Preprovisioning a Multirate PPM task.
Step 8 Complete the G278 Provision the Optical Line Rate
Stop. You have completed this procedure.
NTP-G339 Modify the WSE Card Line Settings and PM Parameter Thresholds
Step 1 As needed, complete the G103 Back Up the Database to preserve the existing transmission settings.
Step 2 Perform any of these tasks as needed:
- G739 Change the WSE Card Line Settings
- G740 Change the WSE Card Ethernet Settings
- G744 Change the WSE Card Security Thresholds
- G745 Change the WSE Card Line RMON Thresholds
- In node view (single-shelf mode) or shelf view (multishelf view), double-click the WSE card where you want to provision the alarm and TCA threshold settings for the port.
- G747 Change the WSE Card OTN Settings
Note To use the Alarm Profiles tab, including creating alarm profiles and suppressing alarms, see the Alarm and TCA Monitoring and Management document.
Stop. You have completed this procedure.
DLP-G739 Change the WSE Card Line Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the WSE card where you want to change the line settings.
Step 2 Click the Provisioning > Line > Ports tabs. Tabs and parameter selections vary according to pluggable port modules (PPM) provisioning.
Step 3 Modify any of the line settings in the Ports tab as described in Table 11-227 .
User-defined. Name can be up to 32 alphanumeric or special characters, or both. Blank by default. See the G104 Assign a Name to a Port. |
||
Sets the port service state unless network conditions prevent the change. For more information about administrative states, see the Administrative and Service States document. |
||
(Display only) Identifies the autonomously generated state that gives the overall condition of the port. Service states appear in the format: Primary State-Primary State Qualifier, Secondary State. For more information about service states, see the Administrative and Service States document. |
||
|
||
Sets the automatic in-service (AINS) soak period. Double-click the time and use the up and down arrows to change settings. |
||
Table 11-228 provides the reach distances for different payloads on the WSE card. |
||
Note When an OTU2 payload is provisioned on the WSE card in the TXP-10G or RGN-10G operating mode, the overclock parameter is automatically set to ON. |
||
Shuts down the far-end laser in response to certain defects. |
||
In a WSE card with a 10-GE payload, when a network fault or failure occurs, and the user sets squelch to the Disable state, the faults propagated downstream are different in GFP and CBR mapping. In GFP mapping, the device connected to the client reports a momentary local fault, but in CBR mapping, the local fault is reported for the entire duration of the fault. |
||
Step 5 Return to your originating procedure (NTP).
DLP-G740 Change the WSE Card Ethernet Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the WSE card where you want to change the Ethernet settings. The card view appears.
Step 2 Click the Provisioning > Line > Ethernet tabs. Tabs and parameter selections vary according to pluggable port modules (PPM) provisioning.
Step 3 Modify any of the Ethernet settings in the Ethernet tab as described in Table 11-229 .
Sets the port service state unless network conditions prevent the change. For more information about administrative states, see the Administrative and Service States document. |
||
(Display only) Identifies the autonomously generated state that gives the overall condition of the port. Service states appear in the format: Primary State-Primary State Qualifier, Secondary State. For more information about service states, see the Administrative and Service States document. |
||
|
||
Sets the automatic in-service (AINS) soak period. Double-click the time and use the up and down arrows to change settings. |
||
Sets the maximum size of the Ethernet frames accepted by the port. The port must be in OOS/locked state. |
||
Step 5 Return to your originating procedure (NTP).
DLP-G744 Change the WSE Card Security Thresholds
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the WSE card where you want to change the security threshold settings.
Step 2 Click the Provisioning > Security Thresholds tabs.
Step 3 Modify any of the settings as described in Table 11-230 .
Note You must modify each of these options independently: TCA and Alarm, and 15 Min and 1 Day. To do so, choose the appropriate radio button and click Refresh.
Shows the number of times the Sequence Number (SEQ) for an AES packet has differed at the encryption and decryption ends. |
|
Step 5 Return to your originating procedure (NTP).
DLP-G745 Change the WSE Card Line RMON Thresholds
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the WSE card where you want to change the line RMON threshold settings in the card view.
Step 2 Click the Provisioning > Line Thresholds > RMON Thresholds tabs.
Step 3 Click Create . The Create Threshold dialog box appears.
Step 4 From the Port drop-down list, choose the applicable port, either the payload port, for example “1-1 (TEN_GE)” port.
Step 5 From the Variable drop-down list, choose an Ethernet variable. See Table 11-231 for a list of available Ethernet variables.
Total number of frames received on an interface in both Rx and Tx directions. |
|
Total number of octets of data (including those in bad packets) received on the network (excluding framing bits, but including FCS octets). |
|
Total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets) and were otherwise well-formed. |
|
Total number of frames received on a particular interface that are an integral number of octets in length but do not pass the FCS check. |
|
Total number of frames received on a particular interface that are not an integral number of octets in length and do not pass the FCS check. This counter is only valid for FE modes of operation. |
|
Contains a count of received frames that have an associated RX_ER assertion during a data reception error event (MII) or data reception error event or carrier extension error (GMII) from the PCS. |
|
Total number of frames received on a particular interface that exceed the maximum permitted frame size. |
|
Number of Layer 1 errors as defined within the following conditions:
|
|
Total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets), and had either a bad FCS with an integral number of octets (FCS error) or a bad FCS with a non-integral number of octets (alignment error). |
|
Total number of packets received that were less than 64 octets long (excluding framing bits, but including FCS octets) and were otherwise well-formed. |
|
Total number of packets received that were less than 64 octets in length (excluding framing bits, but including FCS octets) and had either a bad FCS with an integral number of octets (FCS error) or a bad FCS with a non-integral number of octets (alignment error). Note that it is entirely normal for etherStatsFragments to increment. This is because it counts both runts (which are normal occurrences due to collisions) and noise hits. |
|
Total number of packets (including bad packets) received that were 64 octets in length (excluding framing bits, but including FCS octets). |
|
Total number of packets (including bad packets) received that were between 65 and 127 octets in length inclusive (excluding framing bits, but including FCS octets). |
|
Total number of packets (including bad packets) received that were between 128 and 255 octets in length inclusive (excluding framing bits, but including FCS octets). |
|
Total number of packets (including bad packets) received that were between 256 and 511 octets in length inclusive (excluding framing bits, but including FCS octets). |
|
Total number of packets (including bad packets) received that were between 512 and 1023 octets in length inclusive (excluding framing bits, but including FCS octets). |
|
Total number of packets (including bad packets) received that were between 1024 and 1518 octets in length inclusive (excluding framing bits, but including FCS octets). |
|
Total number of good packets received that were directed to a multicast address. Note that this number does not include packets directed to the broadcast address. |
|
Total number of good packets received that were directed to the broadcast address. Note that this number does not include multicast packets. |
|
Total number of packets (including bad packets) received that were 1591 octets in length (excluding framing bits, but including FCS octets). |
|
ifInUcastPkts22 |
Total number of packets delivered by this sublayer to a higher sublayer that are not addressed to a multicast or broadcast address. |
ifInMulticastPkts 1 |
Total number of packets delivered by this sublayer to a higher sublayer that are addressed to a multicast address. For a MAC layer protocol, this includes both group and functional addresses. |
ifInBroadcastPkts 1 |
Total number of packets delivered by this sublayer to a higher sublayer that are addressed to a broadcast address. |
Total number of received errors. ifInErrors does not increment for Jumbo frames. Note ifInerrors increment for errored/erroredTooLong and erroredShortFrames. |
|
Total count of packets transmitted to a unicast group destination address. |
|
Total number of packets that higher-level protocols requested to be transmitted, which were addressed to a multicast address at this sublayer. These include packets that were discarded or not sent. For a MAC layer protocol, this includes both group and functional addresses. |
|
Total number of packets that higher-level protocols requested to be transmitted, which were addressed to a broadcast address at this sublayer. These include packets that were discarded or not sent. |
|
Total number of octets transmitted out of the interface, including framing characters. |
|
Total number of transmitted data frames with payload CRC errors when HDLC framing is used. |
|
Number of transmitted frames containing less than the minimum permitted frame size as programmed with the transmit MAC Min Frame Length Configuration Register. |
|
DLP-G746 Provision the WSE Card with Port Alarm and TCA Thresholds
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the WSE card where you want to provision the alarm and TCA threshold settings for the port.
Step 2 Click the Provisioning > Optics Thresholds tabs. The TCA thresholds are shown by default.
Note You must modify 15 Min and 1 Day independently. Choose the appropriate radio button and click Refresh.
Note Do not modify the Laser Bias parameters.
Step 3 If TCA is not selected, select the TCA option and then click Refresh . If it is checked, continue with Step 4.
Step 4 Verify whether the port TCA thresholds for RX Power High, RX Power Low, TX Power High, and TX Power Low are set. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and pressing Enter.
Step 5 Under Types, click the Alarm radio button and click Refresh .
Note Do not modify the Laser Bias parameters.
Step 6 Verify whether the port alarm thresholds for RX Power High, RX Power Low, TX Power High, and TX Power Low are set. Provision new thresholds as needed by double-clicking the threshold value you want to change, deleting it, entering a new value, and pressing Enter.
Step 8 Return to your originating procedure (NTP).
DLP-G747 Change the WSE Card OTN Settings
Step 1 In node view (single-shelf mode) or shelf view (multishelf view), double-click the WSE card where you want to change the OTN settings.
Step 2 Click the Provisioning > OTN tabs, then choose one of these subtabs: OTN Lines, ITU-T G.709 Thresholds, FEC Thresholds, or Trail Trace Identifier.
Step 3 Modify any of the settings described in Tables Table 11-233 through Table 11-234 .
Note You must modify each of these options independently: Near End and Far End, 15 Min and 1 Day, and SM and PM. Choose the appropriate radio button and click Refresh.
Table 11-233 describes the values on the Provisioning > OTN > OTN Lines tab.
Table 11-234 describes the values on the Provisioning > OTN > ITU-T G.709 Thresholds tab.
Table 11-235 describes the values on the Provisioning > OTN > FEC Thresholds tab.
Numeric. Can be set for 15-minutes or one-day intervals. Select an option and click Refresh . |
||
Numeric. Can be set for 15-minutes or one-day intervals. Select an option and click Refresh . |
Table 11-236 describes the values on the Provisioning > OTN > Trail Trace Identifier tab.
Step 5 Return to your originating procedure (NTP).
NTP-G340 Provision Encryption on the WSE Card
This procedure enables you to provision encryption on the WSE card. |
|
Security super user and Security user(only if authorized by Security super user) |
Step 1 Perform any of the following tasks as needed:
- G759 Configure GCC2 Settings
- G748 Enable Card Authentication
- G749 Enable Payload Encryption
- G753 Set AES Secure Packet Configuration
- G754 Specify ESP Header and Trailer Locations
- G755 Enable Ingress PRBS Generation and Egress PRBS Monitoring
- G751 Reset Master Key
- G752 Change Master Key Reset Interval
Stop. You have completed this procedure.
DLP-G759 Configure GCC2 Settings
Note Ensure that the KEY_EX_FAIL alarm is not present in the respective trunk pot.
Step 1 In node view (single shelf mode), or shelf view (multi-shelf mode), double-click the WSE card for which you want to configure the GCC settings.
Step 2 Go to Provisioning > Encryption > GCC2 Settings.
Step 3 In the Card IP Address field, provide the IP address of the source WSE card.
Step 4 Click on the Destination Card IP entry corresponding to a trunk port. Specify the IP address of the destination card.
Step 5 Click on the Destination Port entry corresponding to a port. Specify the port number of the destination card.
Step 7 Return to your originating procedure (NTP).
DLP-G748 Enable Card Authentication
Note Before enabling the card authentication, ensure that the current time of the day (ToD) is configured correctly on the node.
Step 1 In node view (single shelf mode), or shelf view (multi-shelf mode), double-click the WSE card for which you need to enable card authentication. The card view is displayed.
Step 2 Go to Provisioning > Encryption > Security.
Step 3 From the Port list, choose the port on which card authentication is to be enabled.
Step 4 Check the Card Authentication checkbox. .
Step 6 Repeat Step 3 to Step 5 for every trunk port that carries the encrypted payload, as the card authentication takes place independently on each trunk port of the source WSE card.
Step 7 Return to your originating procedure (NTP).
DLP-G749 Enable Payload Encryption
This task enablse encryption of OTN frames emerging from a trunk port of the source WSE card. |
|
Security super user and Security user(only if authorized by Security super user) |
Note Before enabling payload encryption, ensure that KEY_EX_FAIL alarm is not present on that port.
Step 1 In node view (single shelf mode), or shelf view (multi-shelf mode), double-click the WSE card for which you want to enable payload encryption.
Step 2 Go to Provisioning > Encryption > Security.
Step 3 Check the Payload Encryption check box for a port to enable encryption of the OTN frames on that port.
Note In WSE card, do not enable encryption with far-end client loop back. Enabling encryption with far-end client loopback will result in sync loss until the key is exchanged. The key is exchanged only after the ODUk-AIS on the trunk is cleared.
Step 5 Return to your originating procedure (NTP).
DLP-G753 Set AES Secure Packet Configuration
This task configures the number of OTN frames per AES secure packet. The AES secure packet for each port can be made up of 4 or 8 OTN frames. |
|
Step 1 In node view (single shelf mode), or shelf view (multi-shelf mode), double-click the WSE card for which you want to set the AES secure packet configuration.
Step 2 Go to Provisioning > Encryption > OTN Overhead for Packet traffic.
Step 3 Click on the AES Secure Packet entry corresponding to the port where the AES secure packet must be configured.
Step 4 From the drop-down list, choose either 4 OTN Frame Based or 8 OTN Frame Based .
By default, 8 OTN Frame Based is selected.
Step 6 Return to your originating procedure (NTP).
DLP-G754 Specify ESP Header and Trailer Locations
This task specifies the location of the ESP (Encapsulating Security Payload) Header and Trailer in each OTN frame of the AES secure packet. |
|
Step 1 In node view (single shelf mode), or shelf view (multi-shelf mode), double-click the WSE card for which you want to specify the ESP header and trailer locations.
Step 2 Go to Provisioning > Encryption > OTN Overhead for Packet traffic.
Step 3 Click on the ESP Header Location entry corresponding to a port. A drop-down list appears.
The locations available are A, B, C, D, E and F. The ESP header and trailer require a total of 32 bytes within the OTN overhead.
Step 4 Choose the ESP header location from the predefined values in the list.
The ESP Trailer Location is updated to match the location of the ESP header.
By default, location A is selected as the ESP header and trailer locations.
Step 6 Return to your originating procedure (NTP).
DLP-G755 Enable Ingress PRBS Generation and Egress PRBS Monitoring
This task lets you enable PRBS generation at the ingress, and PRBS monitoring at the egress of each port for the source and destination WSE card. |
|
Step 1 In node view (single shelf mode), or shelf view (multi-shelf mode), double-click the WSE card for which you want to enable PRBS generation and PRBS monitoring.
Step 2 Go to Provisioning > Encryption > OTN Overhead for Packet traffic.
Note If card authentication is not enabled, the PRBS Generation and PRBS Monitoring can be tested only on default OTN overhead settings. If card authentication is enabled, the PRBS Generation and Monitoring can be tested using all OTN overhead bytes in the OTN overhead settings.
Step 3 Check the Ingress PRBS Generator check box for a port to enable PRBS generation at the ingress of that port. The ingress of a port is the data path in the encryption block.
Step 4 Check the Egress PRBS Monitor check box for a port to enable PRBS monitoring at the egress of that port. The egress of a port is the data path in the decryption block.
Step 6 Return to your originating procedure (NTP)
This task lets you reset the master key for each encrypted stream of the source WSE card. |
|
Security super user and Security user(only if authorized by Security super user) |
Step 1 In node view (single shelf mode), or shelf view (multi-shelf mode), double-click the WSE card for which you want to reset the master key.
Step 2 Go to Provisioning > Encryption > Key Management.
Step 3 Click the Reset Master Key button for a port to reset the master key used for the payload encryption on that port.
When you reset the master key:
- A key exchange is enforced by overriding the existing master key reset interval.
- A new interval is calculated from the time the key is reset.
Step 5 Return to your originating procedure (NTP).
DLP-G752 Change Master Key Reset Interval
Step 1 In node view (single shelf mode), or shelf view (multi-shelf mode), double-click the WSE card for which you want to change the master key reset interval.
Step 2 Go to Provisioning > Encryption > Key Management.
Click on the Master Key Change Interval entry corresponding to a port. Two spin boxes appear in place of the entry.
The box on the left registers the time in hours; the box on the right, the time in minutes. The master key interval can be set in multiples of 15 minutes between 15 minutes to 48:45 hours.
Step 3 Set the desired values in the two boxes.
When the time interval elapses, a new master key is exchanged between the source and destination WSE cards.
Step 5 Return to your originating procedure (NTP).
NTP-G342 Provision FIPS and CC Mode
Note Provisioning a FIPS and CC mode is not supported in Macintosh computers.
Stop. You have completed this procedure.
DLP-G761 Enable FIPS and CC Mode
Note Use this procedure with caution. FIPS and CC mode is supported only in M6 stand-alone mode and not in multi-shelf environment.
Step 1 Select the node for which you want to enable FIPS and CC mode.
Step 2 Secure all the access points:
a. In the node view, click Provisioning > Security > Access.
b. Change the Access State of Shell Access, EMS Access, TL1 Access , and SNMP Access to Secure state.
Step 3 Click the FIPS and CC tab.
Step 4 Select the FIPS and CC Mode check box to run the node in FIPS and CC mode.
Note In case of secure boot failure, the key cannot be zeroized before RMA.
Step 6 Return to your originating procedure (NTP).
DLP-G760 Configure Management of FIPS and CC Enabled NE
Step 1 Install JRE version 7.0 when the version is not present in the system or a higher version is present.
a. Uninstall previous versions of JREs from the control panel.
c. Download and install the latest JRE version 7.0. for Windows x64 from http://www.oracle.com/technetwork/java/javase/downloads/jre7-downloads-1880261.html .
Step 2 Go to Java Control Panel and click the Advanced tab. Expand Security > General settings. Perform these actions:
a. Clear the Use SSL 3.0 checkbox.
b. Select the Use TLS 1.0 checkbox.
Step 3 In the Java Control Panel, click the General tab. Click Settings and perform these actions to clear the JNLP cache:
a. Clear the Keep temporary files on my computer checkbox.
c. Select the files to delete and click OK.
d. Click OK and exit the Java Control Panel.
Step 4 Install Java Cryptography Extension (JCE)version 7.0.
a. Download the JCE from http://www.oracle.com/technetwork/java/javase/downloads/index.html .
b. Extract the contents of the downloaded policy file.
c. Copy and overwrite the security policy file to C:\Program Files\Java\jre7\lib\security\.
<java-home>/lib/security [Unix]
<java-home>\lib\security [Win32]
where <java-home> is the location where the Jave SE Runtime Environmen (JRE) is installed.
Step 5 Configure the browser settings:
a. Go to Tools > Internet options.
b. Click the Advanced tab and go to the Security section.
c. Clear the Use SSL 3.0 checkbox.
d. Select the Use TLS 1.0 checkbox and click OK.
b. Click the Change Proxy settings button and click the Advanced tab.
c. Clear the Use SSL 3.0 checkbox.
d. Select the Use TLS 1.0 checkbox and click OK.
For more information on setting the FIPS and CC mode, see http://support.mozilla.org/en-US/kb/Configuring Firefox for FIPS 140-2.
Step 6 Configure the SSH client using PuTTY or Tectia:
b. In the Category area, expand Connection > click SSH.
c. In the Encryption cipher selection policy area, make 3DES as the first option.
a. Expand SSH and click the KEX tab.
b. In the Algorithm selection policy area, make Dillie-Helmangroup 14 algorithm as the first option.
c. In the Category area, click Session.
d. Enter the host name or IP address.
e. In the Connection Type area, select the SSH radio button.
a. Open the Tectia SSH client.
b. Go to Edit > Tectia Connections.
c. Expand General tab, and click Default Connection.
e. Enable DH-Group14-SHA1 algorithm and make it the first option in the Enabled KEXs area.
g. Uncheck Use factory defaults check box.
h. Enable HMAC-SHA1 MAC algorithm and make it the first option in the Enabled KEXs area.
i. Click OK. The Connect to Server dialog box appears.
j. Enter the host name and user name.
k. Click Connect to connect to the server.
Step 7 Return to your originating NTP.