Download Print this page

Nokia 7450 ESS Interface Configuration Manual

Ethernet service switch, service router, extensible routing system, virtualized service router
Hide thumbs

Advertisement

Table of Contents
INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5
7450 ETHERNET SERVICE SWITCH
7750 SERVICE ROUTER
7950 EXTENSIBLE ROUTING SYSTEM
VIRTUALIZED SERVICE ROUTER
INTERFACE CONFIGURATION GUIDE
RELEASE 15.0.R5

3HE 11968 AAAC TQZZA 01

Issue: 01

September 2017
Nokia — Proprietary and confidential.
Use pursuant to applicable agreements.

Advertisement

Table of Contents
loading

  Related Manuals for Nokia 7450 ESS

  Summary of Contents for Nokia 7450 ESS

  • Page 1: Issue

    INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 7450 ETHERNET SERVICE SWITCH 7750 SERVICE ROUTER 7950 EXTENSIBLE ROUTING SYSTEM VIRTUALIZED SERVICE ROUTER INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 3HE 11968 AAAC TQZZA 01 Issue: 01 September 2017 Nokia — Proprietary and confidential. Use pursuant to applicable agreements.
  • Page 2 © 2017 Nokia. Contains proprietary/trade secret information which is the property of Nokia and must not be made available to, or copied or used by anyone outside Nokia without its written authorization. Not to be used or disclosed except in accordance with applicable agreements.
  • Page 3: Table Of Contents

    INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Table of Contents Getting Started ................9 About This Guide..................9 Interface Configuration Process ..............11 Interfaces ..................13 Configuration Overview ................13 2.1.1 Chassis Slots and Cards ................13 2.1.2 MCMs .......................15 2.1.3 MDA-a, MDA-aXP, MDA, MDA-XP and MDA-e Modules......15 2.1.4 XMAs/C-XMAs...................18 2.1.5...
  • Page 4 INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.3.2.15 Ethernet Local Management Interface (E-LMI) ........109 2.3.2.16 Link Layer Discovery Protocol (LLDP).............110 2.3.2.17 Exponential Port Dampening..............114 2.3.3 Per Port Aggregate Egress Queue Statistics Monitoring......117 Port Cross-Connect (PXC) ..............119 2.4.1 PXC Terminology ..................120 2.4.2 PXC - Physical Port in Cross-Connect (Loopback) Mode .......121 2.4.2.1 Operational State..................122 2.4.3...
  • Page 5 INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 G.8031 Protected Ethernet Tunnels ............172 G.8032 Protected Ethernet Rings............173 Ethernet Port Monitoring .................174 2.10 802.3ah OAM ..................178 2.10.1 OAM Events ....................180 2.10.1.1 Link Monitoring ..................181 2.10.2 Remote Loopback ...................187 2.10.3 802.3ah OAM PDU Tunneling for Epipe Service........188 2.10.3.1 802.3ah Grace Announcement..............188 2.11...
  • Page 6 INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.19.1.9 Forwarding Path Extension (FPE) Commands........279 2.19.1.10 Port APS Commands ................279 2.19.1.11 Ethernet Commands................280 2.19.1.12 Interface Group Handler Commands............288 2.19.1.13 Multilink Bundle Commands ..............288 2.19.1.14 SONET-SDH Commands ................290 2.19.1.15 TDM Commands ..................292 2.19.1.16 DS3 Commands ..................295 2.19.1.17 E1 Commands..................296 2.19.1.18...
  • Page 7 INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.20.1.4 Debug Commands...................633 2.20.1.5 Tools Commands ..................633 2.20.2 Command Descriptions ................634 2.20.2.1 Hardware Show Commands..............635 2.20.2.2 PEQ Show Commands................699 2.20.2.3 APS Show Commands ................706 2.20.2.4 Port Show Commands................710 2.20.2.5 Multilink Bundle Show Commands ............805 2.20.2.6 LAG Show Commands ................825 2.20.2.7 MACsec Show Commands..............836...
  • Page 8 INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 3HE 11968 AAAC TQZZA 01 Issue: 01...
  • Page 9: Getting Started

    SR OS router. Table 1 Supported SR OS Router Chassis Types 7450 ESS 7750 SR 7950 XRS • 7450 ESS-7/12 running in • 7450 ESS-7/12 running in • 7950 XRS-16c standard mode (not mixed- mixed-mode (not standard • 7950 XRS-20/40...
  • Page 10 Getting Started INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Note: This guide generically covers Release 15.0.Rx content and may contain some content that will be released in later maintenance loads. Refer to the SR OS R15.0.Rx Software Release Notes, part number 3HE 12060 000x TQZZA or the VSR Release Notes, part number 3HE 12092 000x TQZZA, for information on features supported in each load of the Release 15.0.Rx software.
  • Page 11: Interface Configuration Process

    INTERFACE CONFIGURATION GUIDE Getting Started RELEASE 15.0.R5 1.2 Interface Configuration Process Table 2 lists the tasks necessary to configure IOMs and XCMs (also referred to as cards), MDAs and XMAs, and ports. Note: For consistency across platforms, XMAs are modeled in the SR OS (CLI and SNMP) as MDAs.
  • Page 12 Getting Started INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 3HE 11968 AAAC TQZZA 01 Issue: 01...
  • Page 13: Interfaces

    • the term “MDA” is used generically to refer to both MDAs and XMAs Nokia routers provide the capability to configure chassis slots to accept specific card and MDA types and set the relevant configurations before the equipment is actually installed.
  • Page 14 A:SR12-1>config# card 1 A:SR12-1>config>card# card-type iom3-xp The 7450 ESS-7/12, and 7750 SR-7/12, and 7750 SR-12e platforms also support a variety of IMMs in designated chassis slots. IMMs have integrated MDAs. The provisioning requirements depends on the generation of IMM that you use. Refer to the IMM Installation Guide for more information.
  • Page 15: Mcms

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 The 7750 SR-e platforms support the IOM-e modules in dedicated slots in the rear of each chassis. The 7750 SR-1e supports one physical IOM-e module. This IOM-e is represented in the CLI as card 1. The 7750 SR-2e supports two physical IOM-e cards.
  • Page 16 =============================================================================== A:ALU-3>config>card# On the 7450 ESS-7/12, 7750 SR-7/12, and 7750 SR-12e, MDAs plug into IOMs. (MDA and MDA-XP modules plug into the IOM3-XP/-B/-C. MDA-e modules plug into the IOM4-e and IOM4-e-B). Up to two MDAs can be provisioned on an IOM.
  • Page 17 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 On the 7750 SR-c12/SR-c4, 7450 ESS-7/12, 7750 SR-7/12, and 7750 SR-12e platforms, MDA names in the CLI start with the letter 'm' (for example, m10-1gb-xp- sfp). The following example displays the card, card-type, mda, and mda-type command usage in the 7750 SR-7: A:SR7>config# card 1...
  • Page 18: Xmas/C-Xmas

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 A:SR1e# admin display-config . . . ---------------------------------------------- echo "Card Configuration" #--------------------------------------------- card 1 card-type iom-e mda 1 mda-type me10-10gb-sfp+ exit mda 4 mda-type me1-100gb-cfp2 exit exit ---------------------------------------------- A:SR1e# 2.1.4 XMAs/C-XMAs Note: For consistency across platforms, XMAs are modeled in the system as MDAs, and unless specified otherwise, the term MDA is used generically in this document to refer to both MDAs and C-XMA/XMAs.
  • Page 19: Cmas

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 echo "Card Configuration " #------------------------------------------ card 1 card-type xcm-x20 mda 1 mda-type cx2-100g-cfp power-priority-level 130 exit mda 2 mda-type cx20-10g-sfp power-priority-level 135 exit exit ---------------------------------------------- A:XRS20# On the 7950 XRS, the show card state output displays an “x” in the name of the XMA and “cx”...
  • Page 20: Versatile Service Module (Vsm)

    A VSM, like an MDA, is installed and provisioned as a pluggable module in an IOM. The VSM is supported on the 7450 ESS-7/12, 7750 SR-7/12, and 7750 SR-12e platforms. The VSM is not supported on the 7950 XRS or on the 7750 SR-c12/c4 platforms.
  • Page 21: Rate Limiting

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 • packet classification and scheduling 2.1.7.1 Rate Limiting The oversubscribed MDA or CMA limits the rate at which traffic can enter the MDA or CMA on a per-port basis. If a port exceeds its configured limits then the excess traffic will be discarded, and 802.3x flow control frames (pause frames) are generated.
  • Page 22 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 • The packet is classified into 16 classes. Typically, these are the eight forwarding classes and each packet is assigned one priority per forwarding class. After classification, the packet is offered to the queuing model. This queuing model is limited to three queues each having four thresholds.
  • Page 23: Channelized Mda/Cma Support

    Each port for the channelized ASAP OC-3/STM-1 MDA supports channelization down to DS-0 and accepts one OC-3/STM-1 SFP small form factor pluggable (SFP) module. The same SFP optics used on Nokia’s SONET/SDH MDAs can be used on the channelized ASAP OC-3/STM-1 MDA.
  • Page 24: Channelized Oc-12/Stm-4 Asap Mdas

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 enables enhanced Layer 1 and Layer 2 data path functionality, for example ATM TM features, MDA-based channel or port queuing, or multilink applications like Inverse ATM Multiplexing (IMA). This MDA is supported on the 7750 SR-7/12 and the 7750 SR-c4/c12 platforms.
  • Page 25: Channelized Oc-3/Stm-1 Circuit Emulation Services (Ces) Cma And Mda

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 E-1 (G.704) channels. Also, 56 kb/s channels cannot be part of a bundle. E-3 ports do not support channelization, only clear channel operation. This MDA is supported on the 7750 SR-7/12 and the 7750 SR-c4/c12 platforms. 2.1.8.7 Channelized OC-3/STM-1 Circuit Emulation Services (CES) CMA and MDA...
  • Page 26: Network Interconnections

    2.1.8.8 Network Interconnections Nokia routers can fill the needs of smaller service providers as well as the more remote point of presence (PoPs) locations for larger service providers. To support the use of lower speed links as network links in the likelihood that lower speed circuits...
  • Page 27: Digital Diagnostics Monitoring

    Interfaces RELEASE 15.0.R5 2.2 Digital Diagnostics Monitoring Some Nokia SFPs, XFPs, QSFPs, CFPs and the MSA DWDM transponder have the Digital Diagnostics Monitoring (DDM) capability where the transceiver module maintains information about its working status in device registers including: • temperature •...
  • Page 28 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 =============================================================================== High Alarm High Warn Low Warn Low Alarm Lane Tx Bias Current (mA) 78.0 75.0 25.0 20.0 Lane Rx Optical Pwr (avg dBm) 2.30 2.00 -11.02 -13.01 ------------------------------------------------------------------------------- Lane ID Temp(C)/Alm Tx Bias(mA)/Alm Tx Pwr(dBm)/Alm Rx Pwr(dBm)/Alm -------------------------------------------------------------------------------...
  • Page 29 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 DDM information is populated into the router’s MIBs, so the DDM data can be retrieved by Network Management using SNMP. Also, RMON threshold monitoring can be configured for the DDM MIB variables to set custom event thresholds if the factory-programmed thresholds are not at the desired levels.
  • Page 30 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Table 5 DDM Alarms and Warnings Parameter SFP/XFP Units Required? MSA DWDM Temperature - High Alarm - Low Alarm - High Warning - Low Warning Supply Voltage µV - High Alarm - Low Alarm - High Warning - Low Warning TX Bias Current...
  • Page 31: Sfps And Xfps

    The availability of the DDM real-time information and the warning and alarm status is based on the transceiver. It may or may not indicate that DDM is supported. Although some Nokia SFPs support DDM, Nokia has not required DDM support in releases prior to Release 6.0. Non-DDM and DDM-supported SFPs are distinguished by a specific ICS value.
  • Page 32: Ports

    2.3.1 Port Types Before a port can be configured, the slot must be provisioned with a card type and MDA type. Nokia routers support the following port types: • Ethernet — Supported Ethernet port types include: − Fast Ethernet (10/100BASE-T) −...
  • Page 33 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Once the port is changed to hybrid, the default MTU of the port is changed to match the value of 9212 bytes currently used in network mode (higher than an access port), ensuring that both SAP and network VLANs can be accommodated.
  • Page 34 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 When a named pool policy is applied to the hybrid port’s MDA or to the hybrid port, the port’s fair share of total buffers available to the MDA is split into three parts: default pools, named pools local to the port, and named pools on the ports MDA.
  • Page 35: Port Features

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 • APS — Automatic Protection Switching (APS) is a means to provide redundancy on SONET equipment to guard against linear unidirectional or bidirectional failures. The network elements (NEs) in a SONET/SDH network constantly monitor the health of the network. When a failure is detected, the network proceeds through a coordinated pre-defined sequence of steps to transfer (or switchover) live traffic to the backup facility (called protection facility.) This is done very quickly to minimize lost traffic.
  • Page 36: Network Access Control

    2.3.2.2 802.1x Network Access Control Nokia routers support network access control of client devices (PCs, STBs, and so on) on an Ethernet network using the IEEE. 802.1x standard. 802.1x is known as Extensible Authentication Protocol (EAP) over a LAN network or EAPOL.
  • Page 37 RELEASE 15.0.R5 2.3.2.2.1 802.1x Modes Nokia routers support port-based network access control for Ethernet ports only. Every Ethernet port can be configured to operate in one of three different operation modes, controlled by the port-control parameter: • force-auth — Disables 802.1x authentication and causes the port to transition to the authorized state without requiring any authentication exchange.
  • Page 38 EAPOL-start PDU, if it doesn't receive the EAP- Request/ID frame during bootup. The client responds on the EAP-Request/ID with a EAP-Response/ID frame, containing its identity (typically username + password). Figure 2 802.1x Authentication Scenario Client 7450 ESS RADIUS Authentication Server Port Unauthorized EAPOL-Start...
  • Page 39 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 The RADIUS server checks the supplied credentials, and if approved will return an Access Accept message to the router. The router notifies the client with an EAP- Success PDU and puts the port in authorized state. 2.3.2.2.3 802.1x Timers The 802.1x authentication procedure is controlled by a number of configurable timers...
  • Page 40 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 • quiet-period — Indicates number of seconds between authentication sessions It is started after logoff, after sending an EAP-Failure message or after expiry of the supplicant-timeout timer. The default value is 60. The range is 1 to 3600. RADIUS timer and scaler: •...
  • Page 41: Macsec

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.3.2.2.5 802.1x Configuration and Limitations Configuration of 802.1x network access control on the router consists of two parts: • Generic parameters, which are configured under config>security>dot1x • Port-specific parameters, which are configured under config>port>ethernet>dot1x 801.x authentication: •...
  • Page 42 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Figure 4 802.1 AE LAN-MODE Autheticated Excrypted 802.1AE LAN-MODE DMAC SMAC 802.1AE Header 802.1Q ETYPE Payload 0x88e5 MISEec Ether PACKET TCI/AN SCI (optional) Type NUMBER sw0126 The forwarding on a MACSec packet is performed using the destination MAC address, which is in clear text.
  • Page 43 802.1AE dictates that the 802.1Q VLAN needs to be encrypted. Some vendors give the option of configuring the MACSec on a port with VLAN in clear text. SR OS supports both modes. On the 7750 SR, 7450 ESS, and 7950 XRS, 1/10 Gig cards support both mode of operation.
  • Page 44 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Table 7 MACsec Key Management Modes (Continued) Keying Explanation SR OS Support Where Used Static CAK PRE SHARED KEY Uses a dynamic Supported Switch to switch MACSec Key Management (MKA) and uses a configured pre shared key to drive the CAK.
  • Page 45 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Figure 7 MACsec Concepts for Static-CAK Node 1 CA1 Node 2 CA1 Port 1/1/1 security zone 1 Port 1/1/1 security zone 1 SC1-node1 SecY 1 SecY 1 TxSC1 TxSC1 TxSA1 (Active) TxSA1 (Inactive) SCI-node2 TxSA2 (Inactive) TxSA2 (Active) RxSC1...
  • Page 46 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Table 8 MACsec Terms (Continued) MACsec Term Description SA: Security Association In the cases of SR OS 2 SA per SC, each with a different SAK, each SC comprises a succession of SAs. Each SA is identified by the SC identifier, concatenated with a two-bit association number.
  • Page 47 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Figure 8 MACsec Generating the CAK Supplicant Authenticator RADIUS EAP Authentication Server MKA Protocol PSK: PSK: EAPoL for Authentication CAK Value: 128 or 256 CAK Value: CKN Value: 16 Char CAK: CKN Value: derived from EAP or PSK Key Server KEK: ICK:...
  • Page 48 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Figure 9 MACsec Control Plane Supplicant Authenticator RADIUS EAP Authentication Server MKA Protocol PSK: PSK: EAPoL for Authentication CAK Value: 128 or 256 CAK Value: CKN Value: 16 Char CAK: CKN Value: derived from EAP or PSK Key Server KEK: ICK:...
  • Page 49 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.3.2.3.7 Each peer operates the MACsec Key Agreement Protocol (MKA). Each node can operate multiple MKAs base on the number of CA that it belongs to. Each instance of MKA is protected by a distinct secure connectivity Association key (CAK), that allows each PAE to ensure that information for a given MKA instance is only accepted from other peer that also possess that CAK, and therefore identifying themselves as members or potential members of the same CA.
  • Page 50 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 To avoid a new participant having to respond to each MKPDU from each partner as it is received, or trying to delay its reply until it is likely that MI MN tuples have been received from all potential partners, each participant maintains and advertises both a live peers list and a potential peers list.
  • Page 51 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.3.2.3.10 MACsec Capability, Desire, and Encryption Offset 802.1x-2010 had identified two fields in the MKA PDU. Those fields are: • MACsec Capability • Desire MACsec Capability signals weather MACsec is capable of integrity and confidentiality.
  • Page 52 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 • cipher suite selection • SAK generation and distribution • SA assignment • identifying the CA when two or more CAs merge Each participant in an MKA instance uses the Key Server priority (an 8-bit integer) encoded in each MKPDU to agree on the Key Server.
  • Page 53 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.3.2.3.13 P2P (Switch to Switch) Topology In a point-to-point topology, each router needs a single security zone and single Tx- SC for encryption and a single Rx-SC for decryption. Each SC has two SAs. In total for point-to-point topology, four SAs are needed, two RxSA for RxSC1 and two TXSA for TxSC1.
  • Page 54 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Figure 11 Switch Multi-point to Switch Multi-point Topology SAI: (11:22:33:44:55:02, 00, 01) Node 2 CA1 SecY 1 N1 is Server TxSC1-----TxSA1, TxSA2 N1 Send SAK to every body RxSC1-----RxSA1, RxSA2-peer1 RxSC2-----RxSA3, RxSA4-peer2 RxSC32-----RxSA63, RxSA64-peer32 RxSC33-----NA-peer33 SAI: (11:22:33:44:55:01, 00, 01) Node 1 CA1...
  • Page 55 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Note: The operator must ensure that the number of peers do not exceed the limit of maximum peers per security zone or maximum peers per port (for example, exceeds the port max-peer parameter). If the maximum peer is exceeded, the peer connectivity will be random in case of a node failure or packet loss.
  • Page 56: Sonet/Sdh Port Attributes

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.3.2.3.17 802.1X Tunneling and Multihop MACsec MACsec is an Ethernet packet and, as with any other Ethernet packet, can be forwarded through multiple switches via Layer 2 forwarding. The encryption and decryption of the packets will be performed via the 802.1x (MKA) capable ports. To ensure that MKA is not terminated on any intermediate switch or router, the user can enable 802.1x tunneling on the corresponding port.
  • Page 57: Sonet/Sdh Path Attributes

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 The port’s transmit clock rate can be node or loop timed. The port’s receive clock rate can be used as a synchronization source for the system. The Section Trace (C1) byte can be configured by the user to ensure proper physical cabling. The port can activate and deactivate local line and internal loopbacks.
  • Page 58: Multilink Frame Relay

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Table 13 Valid SONET and SDH Path Configurations (Continued) Framing Path Configuration Options Max Number of Paths Max Number of Paths Per Physical Port Per Physical Port Per TDM Satellite Port SONET OC3>STS1 SPE>VT GROUP>VT1.5 84 DS1 or 512 n*64 kb/s 84 DS1 SPE>DS1...
  • Page 59 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 The MLFR implementation supports FRF.16.1 bundle link integrity protocol to verify serviceability of a member link. 2.3.2.6.1 MLFR Bundle Data Plane FRF.16.1 reuses the UNI/NNI fragmentation procedures defined in FRF.12. Frames on all FR SAP on the MLFR bundle have the UNI/NNI fragmentation header added regardless if they are fragmented or not.
  • Page 60 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.3.2.6.2 MLFR Bundle Link Integrity Protocol FRF.16.1 defines a MLFR Bundle Link Integrity Protocol which verifies the serviceability of a member link. If a problem is found on the member link the link integrity protocol will identify the problem, flag the link as unusable, and adjust the Bundle’s available bandwidth.
  • Page 61: Frf.12 End-To-End Fragmentation

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 The control messages are encapsulated in a single-fragment frame where the C-bit, the B-bit, and the E-bit are all set. The details of the message format are given in FRF.16.1. Table 14 lists the user configured control parameters with values as specified in FRF.16.1.
  • Page 62: Frf.12 Uni/Nni Link Fragmentation

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 The following is the mode of operation for the fragmentation in the transmit direction of the FR SAP. Frames of all the FR SAP forwarding class queues are subject to fragmentation. The fragmentation header is, however, not included when the frame size is smaller than the user configured fragmentation size.
  • Page 63: Mlfr/Frf.12 Support Of Aps, Bfd, And Mirroring Features

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 The operator must delete all configured FR SAPs on a port before enabling or disabling FRF.12 UNI/NNI on that port. Also, the user must shut down the port in order to change the value of the fragmentation threshold. A FR SAP on a FR circuit with FRF.12 UNI/NNI fragmentation enabled can be part of a VLL, VPLS, IES, or VPRN service.
  • Page 64: Multilink Point-To-Point Protocol (Mlppp)

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.3.2.10 Multilink Point-to-Point Protocol (MLPPP) Multilink point-to-point protocol is defined in the IETF RFC 1990, The PPP Multilink Protocol (MP), and provides a way to distribute data across multiple links within an MLPPP bundle to achieve high bandwidth. MLPPP allows for a single frame to be fragmented and transmitted across multiple links.
  • Page 65 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Figure 13 MLPPP 12-bit Fragment Format The required and default format for MP is the 24-bit format. During the LCP state the 12-bit format can be negotiated. The SR-series routers can support and negotiate the alternate 12-bit frame format.
  • Page 66 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.3.2.10.3 Sequence Number Sequence numbers can be either 12 or 24 bits long. The sequence number is zero for the first fragment on a newly constructed AVC bundle and increments by one for each fragment sent on that bundle. The receiver keeps track of the incoming sequence numbers on each link in a bundle and reconstructs the desired unbundled flow through processing of the received sequence numbers and B&E bits.
  • Page 67 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 • No async control character map • No link quality monitoring • No compound frames • No self-describing-padding Any non-LCP packets received during this phase must be silently discarded. 2.3.2.10.8 Link Fragmentation and Interleaving Support Link Fragmentation and Interleaving (LFI) provides the ability to interleave high priority traffic within a stream of fragmented lower priority traffic.
  • Page 68: Multi-Class Mlppp

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 3. The fragments are then transmitted out the egress port. 4. After the transmission of the fragments has begun, high priority frames arrive in the high priority queue. 5. The transmission of the remaining fragments stops and the high priority packets are transmitted out the egress interface.
  • Page 69 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Table 15 Header Formats Original MLPPP Header Format MC-MLPPP Short Sequence Header Format The new MC-MLPPP header format uses the two (previously unused) bits before the sequence number as the class identifier. This allows four distinct classes of service to be identified into separate re-assembly contexts.
  • Page 70 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Table 16 Default Packet Forwarding Class to MLPPP Class Mapping (Continued) FC ID FC Name Scheduling Priority MLPPP Class 4- MLPPP Class 3- MLPPP Class (Default) class bundle class bundle 2-class bundle Expedited Non-Expedited Non-Expedited Non-Expedited Non-Expedited...
  • Page 71 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Table 18 MLPPP Class Queue Threshold Parameters Class 0 Class 1 Class 2 Class 3 Queue Threshold (in ms @ Available bundle rate) 2-Class Bundle Default Egress QoS Profile 3-Class Bundle Default Egress QoS Profile 4-Class Bundle Default Egress QoS Profile 4-Class Bundle...
  • Page 72 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Table 19 MLPPP Class Queue Scheduling Parameters (Continued) WRR Parameters Profile 2 <1% Profile 3 <1% Figure 16 MLPPP Class Queue Scheduling Scheme Class0 > 100% Class1 > MIR Strict Priority Class2 Class3 OSSG259 Note that all queue threshold and queue scheduling parameters are adjusted to the available bundle rate.
  • Page 73 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Ingress MLPPP Class Reassembly For an MLPPP bundle with the multi-class option enabled, there is a default profile for setting the re-assembly timer value for each class. When the pre-defined MLPPP ingress QoS profile 1 is applied to a 4-class bundle, the values of the timers are modified as shown in Table Table 20...
  • Page 74 − Changes to any parameters in the ingress and egress QoS profiles. The CLI commands for the creation of ingress and egress QoS profiles and configuration of the individual QoS parameters are described in the 7450 ESS, 7750 SR, 7950 XRS, and VSR Quality of Service Guide.
  • Page 75: Cisco Hdlc

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.3.2.12 Cisco HDLC Cisco HDLC (cHDLC) is an encapsulation protocol for information transfer. It is a bit- oriented synchronous data-link layer protocol that specifies a data encapsulation method on synchronous serial links using frame characters and checksums. cHDLC monitors line status on a serial interface by exchanging keepalive request messages with peer network devices.
  • Page 76 PPP. 2.3.2.12.1 SLARP A cHDLC interface on a Nokia router will transmit a SLARP address resolution reply packet in response to a received SLARP address resolution request packet from peers. The cHDLC interface will not transmit SLARP address resolution request packets.
  • Page 77: Automatic Protection Switching (Aps)

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 The two key SONET/SDH parameters are scrambling and signal-label (C2-byte). Scrambling is off by default. The default value of the C2-byte is 0xCF. These two parameters can be modified using the CLI. The other SONET overhead values (for example, j0) follow the same rules as the current POS implementation.
  • Page 78 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Figure 17 APS Protection (Single Chassis APS) and Switchover GigE Working Facility GigE Protection Facility 7750 SR 7750 SR GigE Working Facility GigE Protection Facility 7750 SR 7750 SR GigE Working Facility GigE Protection Facility 7750 SR 7750 SR Data Flow...
  • Page 79 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 • Revertive Switching • Bidirectional 1+1 Switchover Operation Example • Protection of Upper Layer Protocols and Services • APS User-Initiated Requests • APS and SNMP • APS Applicability, Restrictions and Interactions • Sample APS Applications 2.3.2.13.1 Single Chassis and Multi-Chassis APS APS can operate in a single chassis configuration (SC-APS) or in a multi-chassis...
  • Page 80 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 APS on a Single Node (SC-APS) In a single chassis APS both circuits of an APS group are terminated on the same node. The working and protect lines of a single chassis APS group can be: •...
  • Page 81 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 impacted so it is recommended to avoid a mix of platforms in the same MC-APS group where possible. The configuration consistency between the working circuit/ router and the protection circuit/router is not enforced by the 7750 SR. Service or network-specific configuration data is not signaled nor synchronized between the two service routers.
  • Page 82 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.3.2.13.2 APS Switching Modes APS behavior and operation differs based on the switching mode configured for the APS group as shown in Table 24. Several switching modes are supported in the router. The switching mode affects how the two directions of a link behave during failure scenarios and how APS tx operates.
  • Page 83 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Bidirectional 1+1 Signaling APS In Bidir 1+1 Sig APS switching mode the Tx data is sent on the active link only (it is not bridged to both links simultaneously). 1+1 signaling, however, is used for full interoperability with signaling-compliant 1+1 architectures.
  • Page 84 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Unidirectional 1+1 Signaling APS In Uni 1+1 Sig APS switching mode the Tx data is sent on the active link only (it is not bridged to both links simultaneously). 1+1 signaling, however, is used for full interoperability with signaling-compliant 1+1 architectures.
  • Page 85 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 − If the remote end indicates an APS switch and the router can RX and TX on the circuit newly selected by the remote end, then the router will move its TX direction and will perform an APS switch of its RX direction (unless the router already TX and RX on the newly selected circuit).
  • Page 86 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.3.2.13.3 APS Channel and SONET Header K Bytes The APS channel (bytes K1 and K2 in the SONET header) exchanges APS protocol messages for all APS modes. K1 Byte The switch priority of a request is assigned as indicated by bits 1 through 4 of the K1 byte (as described in the rfc3498 APS-MIB);...
  • Page 87 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Table 26 shows bits 5 to 8 of a K1 byte and K2 Bits 1 to 4 and the channel number code assignments. Table 26 K1 Byte, Bits 5 to 8 (and K2 Bits 1 to 4), Channel Number Code Assignments Channel Number Channel and Notes Code...
  • Page 88 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Table 27 K2 Byte Functions (Continued) Bits 1 to 8 Function 6 to 8 Line AIS Line RDI Provisioned for bi-directional switching Provisioned for uni-directional switching (reserved for future use) (reserved for future use) (reserved for future use) (reserved for future use) Differences in SONET/SDH Standards for K Bytes...
  • Page 89 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 APS Protection Switching Byte Failure An APS Protection Switching Byte (APS-PSB) failure indicates that the received K1 byte is either invalid or inconsistent. An invalid code defect occurs if the same K1 value is received for 3 consecutive frames (depending on the interface type (framer) used, the 7750 SR may not be able to strictly enforce the 3 frame check per GR-253 and G.783/G.841) and it is either an unused code or irrelevant for the specific switching operation.
  • Page 90 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 APS Far-End Protection Line Failure An APS far-end protection line (APS-FEPL) failure corresponds to the receipt of a K1 byte in 3 consecutive frames that indicates a signal fail (SF) at the far end of the protection line.
  • Page 91 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Table 29 Actions for the Bi-directional Protection Switching Process Status APS Commands Sent in K1 and Action K2 Bytes on Protection Line B -> A A -> B At Site B At Site A No failure No request.
  • Page 92 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Annex B APS Outage Reduction Optimization Typical standard Annex B behavior when a local SF is detected on the primary section (circuit), and this SF is the highest priority request on both the local side and from the remote side as per the APS specifications, is to send a request to the remote end and then wait until a reverse request is received before switching over to the secondary section.
  • Page 93 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Figure 20 shows an example in which the APS working circuit is connected to IOM- 1/MDA-1 and the protection circuit is connected to IOM-2/MDA-1. In this example, assume that the working circuit is currently used to transmit and receive data. Figure 20 APS Working and Protection Circuit Example Flexible FastPath...
  • Page 94 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Switchover Process for Received Data The Flexible Fast-Path complexes for both working and protect circuits are programmed to process ingress. The inactive (protect) circuit however is programmed to ignore all packet data. To perform the switchover from working circuit to the protect circuit the Flexible Fast-Path complex for the working circuit is set to ignore all data while the Flexible Fast-Path complex of the protect circuit will be changed to accept data.
  • Page 95 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Forced Switching of Active to Protection The forced switch of active to protection command switches the active line to the protection line unless a request of equal or higher priority is already in effect. When the forced switch of working to protection command is in effect, it may be overridden either by a lockout of protection or by detecting a signal failure on the protection line.
  • Page 96 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Table 30 Switching Mode to MIB Mapping (Continued) switching-mode TIMETRA-APS-MIB APS-MIB tApsProtectionType apsConfigDirection Uni 1+1 Sig+Data APS onePlusOne unidirectional (uni-1plus1) apsConfigMode in the APS-MIB is set to onePlusOneOptimized for Annex B operation. 2.3.2.13.10 APS Applicability, Restrictions and Interactions Note: The Release Notes for the relevant SR OS release should be consulted for details about APS restrictions.
  • Page 97 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 IMA APS protection is supported only when the router is connected to another piece of equipment (possibly through an ADM) running a single IMA instance at the far end. By design, the IMA APS implementation is expected to keep the IMA protocol up as long as the far end device can tolerate some frame loss.
  • Page 98 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Table 32 MDA/Port Type Pairing for APS MDA Type Unchannelized Circuit Channelized SONET/SDH SONET/SDH For example: Emulation Any Service Satellite (POS) m4-atmoc12/3- (CES) Any Port For example: For example: (ASAP) m16-oc12/3- m4-choc3-ces- For example: m1-choc12-as- Unchannelized Supported...
  • Page 99 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 APS Switchover During CFM/CPM Switchover An APS switchover immediately before, during or immediately after a CFM/CPM switchover may cause a longer outage than normal. Removing or Failure of a Protect MDA The detection of a CMA/MDA removal or a CMA/MDA failure can take additional time.
  • Page 100 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Figure 21 SC-APS MLPPP on Channelized Access Interfaces Example PDSN, AAA GigE Switch MLS B BITS I/F GigE T1 # 2 EV-DO GigE GigE T3/OC-3/OC-12 DACS T1 # 1 Aggregation DHCP Relay GigE Router A MLS A GigE Switch...
  • Page 101 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Figure 22 MC-APS MLPPP on Channelized Access Interfaces Example PDSN, AAA Aggregation DHCP Relay Router B MLS B GigE T3/OC-3/ Switch OC-12 GigE BITS I/F T1 # 2 EV-DO VRRP GigE GigE DACS OSPF Area T1 # 1 GigE...
  • Page 102 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Figure 23 Multi-Chassis APS Application Router 7750 Switch 1483B or 7670 Edge Service Device OCx ATM 1 IP/MPLS ATM Network Network 1483B Edge Service OCx ATM 2 Device Physical Link 7750 Router Data Flow IG0001 Communication between service routers A and B is established through link 3.
  • Page 103 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Figure 24 Access and Node and Network Resilience TLDP Active Standby Aggregation Aggregation Node Node Active Standby Active Standby Inter-ChassisPW Inter-ChassisPW MSAN MSAN for VLL for VLL Standby Active Standby Active Aggregation Aggregation Node Node Standby Active...
  • Page 104 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Figure 25 MC-APS with ATM VLL Redundancy Pseudo-wire Active/Standby Segments Pseudo-wire T-PE T-PE S-PE Convergent GSM/GPRS E1 TDM Packet Network 7750 7750 SR-7 SR-7 IP MPL Core E1 ATM Layer 3 VPNs E1 IMA ATM 7750 7750 7750...
  • Page 105 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Figure 26 Mobile RAN with Microwave Transport Example E1’s (GSM / TDM / 3G) STM-1 7750c4 GSM/TDM 7750c12 STM-1’s POS 1+1/STM1 ch (MLPPP) E1’s STM-1 MLPPP/STM-1’s POS 1+1 8660 7750c4 Future 7750 7750c12 = STM-1 Microwave radio E1’s link deployed as transport (GSM / TDM / 3G)
  • Page 106: Inverse Multiplexing Over Atm (Ima)

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 • Active RX circuits are selected based on local conditions only. The SONET K Bytes are not needed to coordinate switch actions, but they are still used since they flow through and reach the far-end router. •...
  • Page 107 Hardware Applicability IMA is supported on channelized ASAP MDAs. Software Capabilities Nokia’s implementation supports IMA functionality as specified in ATM Forum’s Inverse Multiplexing for ATM (IMA) Specification Version 1.1 (af-phy-0086.001, March 1999). The following capabilities are supported: • TX Frame length — Only IMA specification default of 128 cells is supported.
  • Page 108 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 • IMA version — Both versions 1.0 and 1.1 of IMA are supported. There is no support for automatically falling to version 1.0 if the far end advertises 1.0 support, and the local end is configured as 1.1. Due to potential protocol interoperability issues between IMA 1.0 implementations, it is recommended that IMA version 1.1 is used whenever possible.
  • Page 109: Ethernet Local Management Interface (E-Lmi)

    • IMA test pattern — Nokia’s implementation supports test pattern procedures specified in the IMA specification. Test pattern procedures allow debugging of IMA group problems without affecting user data.
  • Page 110: Link Layer Discovery Protocol (Lldp)

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 The bandwidth profile sub-information element associated with the EVC Status IE does not use information from the SAP QoS policy. A value of 0 is used in this release as MEF 16 indicates the bandwidth profile sub-IE is mandatory in the EVC Status IE. The EVC identifier is set to the description of the SAP and the UNI identifier is set to the description configured on the port.
  • Page 111 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Figure 28 LLDP Internal Architecture for a Network Node Organizationally Organizationally Defined Local Device Defined Remote Device LLDP MIB Extension LLDP MIB Extensions PTOPO MIB (Optional) (Optional) (Optional) Entity MIB (Optional) LLDP Local System LLDP Remote Systems Interface MIB (Optional)
  • Page 112 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Figure 29 Generic Customer Use Case For LLDP MPLS/Native ETH SG/R Core SG/R QinQ DSLAMs Ethernet Links - FE/GE/10GE OSSG263 IEEE 802.1ab LLDP running on each Ethernet interfaces in between all the above network elements may be used to discover the topology information. Operators who are utilizing IOM3/IMM and above can tunnel the nearest-bridge at the port level using the tunnel-nearest-bridge command under the config>port>ethernet>lldp>destmac (nearest-bridge) hierarchy.
  • Page 113 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 LLDP itself does not contain a mechanism for soliciting specific information from other LLDP agents, nor does it provide a specific means of confirming the receipt of information. LLDP allows the transmitter and the receiver to be separately enabled, making it possible to configure an implementation so the local LLDP agent can either transmit only or receive only, or can transmit and receive LLDP information.
  • Page 114: Exponential Port Dampening

    SAM. Including the port-desc option as part of the tx-tlv configuration allows a Nokia remote peer supporting port-desc preferred display logic (11.0r1) to display the value in the port description TLV instead of the port-id field value. This does not change the encoding of the port-id field.
  • Page 115 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 where: N(t) is the quantity that still remains after a time t is the initial quantity is the half-life ½ In dampening, N refers to the starting penalties from the last link-down event. The quantity N(t) refers to the decayed penalties at a specific time, and is calculated starting from the last link-down event (that is, from the time when N last changed).
  • Page 116 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 i. the accumulated penalties are incremented by 1000 ii. the accumulated penalties now equal 1000, which is less than the suppress threshold (of 1500), so the dampening state is idle iii. because the dampening state is idle, link-down is passed to the upper layer iv.
  • Page 117: Per Port Aggregate Egress Queue Statistics Monitoring

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 7. t = 46: Accumulated penalties drop below the reuse threshold i. the accumulated penalties drop below the reuse threshold, so the dampening state changes to idle ii. because the dampening state is idle and the current link state is up, link-up is passed to the upper layer iii.
  • Page 118 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 config port <port-id> [no] monitor-agg-egress-queue-stats When enabled, the line card will poll the related queues to derive the aggregates which provide the delta of the queue statistics since turning on the monitoring. This means that the reported statistics are not reduced by those from a deleted queue and so the aggregates correctly represent the forwarded/dropped statistics since the start of monitoring.
  • Page 119: Port Cross-Connect (Pxc)

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.4 Port Cross-Connect (PXC) Port Cross-Connect (PXC) functionality refers to a method of redirecting ingress traffic received on I/O ports to an operator-chosen forwarding complex (anchor point). This traffic is then pre-processed in the egress data path of the anchor card and consequently looped back into the ingress data path on the same anchor card.
  • Page 120: Pxc Terminology

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Figure 31 Traffic Pre-Processing Utilizing Cross-Connected Port (PXC) SR OS Node Line Card 1 Port 1 Egress Path Ingress Path Second Stage of Port 3 Ingress Processing Ingress Path (PXC) Line Card 2 Port 2 Egress Path Ingress Path Line Card 3 —...
  • Page 121: Pxc - Physical Port In Cross-Connect (Loopback) Mode

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.4.2 PXC - Physical Port in Cross-Connect (Loopback) Mode The concept of a PXC port on an FP3-based line card is shown in Figure 32. The PXC does not require an optical transceiver. Figure 32 100 GE 2x100 Gb/s 1x200 Gb/s...
  • Page 122: Operational State

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 • Once inside the PXC ID configuration, the physical port cannot be used outside of the PXC context. For example, a regular IP interface cannot use this physical port, or a SAP on that port cannot be associated with a service. •...
  • Page 123 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Figure 33 Two Cross-Connected Ports vs Single Cross-Connected Port 10Gbps Full Duplex External Cross-Connect Physical Port 1/1/1 Physical Port 1/1/2 Upstream 10Gbps 10GE 10GE 10Gbps Downstream Optical Fiber Transition from a dual port cross-connect, to a single port cross-connect 10Gbps Single Duplex External Cross-Connect Physical Port 1/1/1...
  • Page 124: Pxc Sub-Port Operational State

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 port pxc-<pxc-id>.b shutdown The two PXC sub-ports are distinguishable by .a and .b suffixes. They transmit traffic toward each other, thus simulating two ports that are interconnected. The PXC sub-ports can be accessed through the configuration in order to modify their parameters (QoS, and so on).
  • Page 125: Port Statistics

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.4.4 Port Statistics There are two types of statistics that can be collected on a regular (non PXC) Ethernet port: • Physical port level statistics provide information about conditions on the data- link layer and physical level, for example, the aggregate number of forwarded and dropped octets/bytes on a MAC level, FCS errors, number of collisions, and so on.
  • Page 126: Lag With Pxc Ports - Pxc Lag

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Statistics are cleared when a physical port enters or leaves the PXC mode. Statistics collection to a local file is not supported on physical PXC ports. Queues are not instantiated on physical PXC ports and therefore, the network level (queue) statistics are not maintained on physical PXC ports.
  • Page 127: Basic Pxc Provisioning

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Statistics in the output of the show lag id statistics command represent combined traffic carried over the referenced lag id and its pair (LAG 1 and LAG 2 in the above example). 2.4.6 Basic PXC Provisioning The CLI flow is shown in Figure 35.
  • Page 128: Qos

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.4.7 QoS Upstream and downstream traffic on a PXC is funneled through the same physical port. In other words, upstream and downstream traffic is transmitted and then received by the same port. Each forwarding direction (upstream and downstream) is represented by a corresponding PXC sub-port (.a or .b).
  • Page 129: Pool Allocations On Pxc Ports

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.4.7.2 Pool Allocations on PXC Ports Queue buffers are created in buffer pools and are used for traffic buffering when queues are congested. Buffer pools are allocated per forwarding complex or per PXC physical port. Each physical PXC port has three associated buffer pools: •...
  • Page 130: Mirroring And Li On Pxc Ports

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.4.8 Mirroring and LI on PXC Ports Traffic on a PXC sub-port can be mirrored or lawfully intercepted (LI). For example, subscriber “Annex1” traffic arriving on a PXC sub-port will be mirrored if “Annex1” is configured as a mirror or LI source.
  • Page 131: Configuration Example

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 • efm-oam — The Information OAMPDUs are transmitted by each peer (PXC sub- port) at the configured intervals. Their purpose is to perform keepalive and critical notification functions. • CRC errors are only recorded, if frames are transmitted. •...
  • Page 132 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 configure port 3/1/1 description "access I/O port on card 3; ecap is null which means that all VLAN tagged and untagged traffic will be accepted” ethernet mode access encap-type null port 4/1/1 description "access I/O port on card 4; ecap is null which means that all VLAN tagged and untagged traffic will be accepted”...
  • Page 133 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 The following displays an example of a PXC LAG configuration: configure lag 1 create description "terminating side of the cross-connect” port pxc-1.a port pxc-2.a lag 2 create description "transient side of the cross-connect” port pxc-1.b port pxc-2.b Passing traffic from the I/O side on access (ports 3/1/1 and 4/1/1) via the transient PXC sub-ports pxc-1.b and pxc-2.b to the termination side of the PXC is performed...
  • Page 134: Forwarding Path Extensions (Fpe)

    (7450 ESS, 7750 SR, and VSR Triple Play Service Delivery Architecture Guide, 7450 ESS, 7750 SR, 7950 XRS, and VSR Layer 3 Services Guide: IES and VPRN, and 7450 ESS, 7750 SR, 7950 XRS, and VSR Layer 2 Services and EVPN Guide: VLL, VPLS, PBB, and EVPN).
  • Page 135 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Figure 36 FPE - Sample Provisioning Steps Operator (manually) configured System (dynamically) configured configure port-xc configure pxc 1 create port pxc-1.a port 1/1/1 [no] shutdown [no] shutdown port pxc-1.b pxc 2 create [no] shutdown port 1/1/3 port pxc-2.a [no] shutdown...
  • Page 136: Lag

    Packet sequencing must be maintained for any given session. The hashing algorithm deployed by the Nokia routers is based on the type of traffic transported to ensure that all traffic in a flow remains in sequence while providing effective load sharing across the links in the LAG.
  • Page 137: Lacp Multiplexing

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.6.1.1 LACP Multiplexing The router supports two modes of multiplexing RX/TX control for LACP: coupled and independent. In coupled mode (default), both RX and TX are enabled or disabled at the same time whenever a port is added or removed from a LAG group. In independent mode, RX is first enabled when a link state is UP.
  • Page 138: Active-Standby Lag Operation

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 • If the port encapsulation is QinQ, a 0.* SAP (for example, 1/1/10:0.*) can be used to tunnel these packets. LAG port states may be impacted if LACP frames are lost due to incorrect prioritization and congestion in the network carrying the tunnel.
  • Page 139 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Figure 37 Active-Standby LAG Operation without Deployment Examples In case of a link failure, as shown in Figure 38 Figure 39, the switch over behavior ensures that all LAG-members connected to the same IOM as failing link become standby and LAG-members connected to other IOM become active.
  • Page 140: Lag On Access Qos Consideration

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.6.3 LAG on Access QoS Consideration The following section describes various QoS related features applicable to LAG on access. 2.6.3.1 Adapt QoS Modes Link Aggregation is supported on the access side with access or hybrid ports. Similarly to LAG on the network side, LAG on access aggregates Ethernet ports into all active or active-standby LAG.
  • Page 141 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 When port-fair mode is enabled, per-Vport hashing is automatically disabled for subscriber traffic such that traffic sent to the Vport no longer uses the Vport as part of the hashing algorithm. Any QoS object for subscribers, and any QoS object for SAPs with explicitly configured hashing to a single egress LAG port, will be given the full bandwidth configured for each object (in a similar way to link mode).
  • Page 142: Per-Fp-Ing-Queuing

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Table 33 Adapt QoS Bandwidth/Rate Distribution (Continued) distribute link port-fair distribute include-egr-hash-cfg % # local linksa 100% 100% rate (SAP 100% bandwidth (SAP hash to a one Scheduler bandwidth hash to one link) link) %# all linksb % # local linksa (SAP hash to all (SAP hash to all...
  • Page 143: Per-Fp-Sap-Instance

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 When the feature is enabled in the config>lag>access context, the queue and virtual scheduler allocation will be optimized. Only one queuing set and one H-QoS virtual scheduler tree per SAP/encap group will be allocated per egress forwarding path (FP) instead of one set per each port of the LAG.
  • Page 144: Lag And Ecmp Hashing

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 • SAP instance optimization applies to LAG-level. Whether a LAG is sub-divided into sub-groups or not, the resources are allocated per forwarding path for all complexes LAG’s links are configured on (i.e. irrespective of whether a given sub-group a SAP is configured on uses that complex or not).
  • Page 145: Per Flow Hashing

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 For LAG load balancing: 1. LAG link map profile 2. Per link hash 3. Consistent per service hashing 4. Per flow hashing 2.6.4.1 Per Flow Hashing Per flow hashing uses information in a packet as an input to the hash function ensuring that any given flow maps to the same egress LAG port/ECMP path.
  • Page 146 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 − The hashing procedure that used to be applied for all VPLS BUM traffic would result in PBB BUM traffic being sent out on BVPLS SAP to follow only a single link when MMRP was not used. Therefore, traffic flooded out on egress BVPLS SAPs is now load spread using the algorithm described above for VPLS known unicast.
  • Page 147 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 When the ECMP set includes an IP interface configured on a spoke-SDP (IES/VPRN spoke interface), or a Routed VPLS interface, the unicast IP packets—which will be sprayed over this interface—will not be further sprayed over multiple RSVP LSPs (part of the same SDP), or multiple LDP FEC next-hops when available.
  • Page 148 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 This provides some control to the user such that this feature is disabled if labeled packets received on a specific interface include non IP packets that can be confused by the hash routine for IP packets. These could be VLL and VPLS packets without a PW control word.
  • Page 149 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 LSR IP-Only Hash Option Enabled This option behaves like the label-IP hash option except that when the algorithm reached the bottom of the label stack in the ECMP round and finds an IP packet, it throws the outcome of the label hash and only uses the source and destination address fields in the IP packet’s header.
  • Page 150 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Currently, if multiple routers have the same set of ECMP next hops, traffic will use the same nexthop at every router hop. This can contribute to the unbalanced utilization of links. The new hash option avoids this issue. This feature when enabled, enhances the default per-flow hashing algorithm described earlier.
  • Page 151 Note: Enhanced multicast load balancing is not supported with Layer 2 and ESM services. It is supported on all platforms except for the 7750 SR-c4 and SR-c12 and the 7450 ESS in standard mode. Security Parameter Index (SPI) Load Balancing IPSec tunneled traffic transported over LAG typically falls back to IP header hashing only.
  • Page 152: Per Link Hashing

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.6.4.2 Per Link Hashing The hashing feature described in this section applies to traffic going over LAG and MC-LAG. Per link hashing ensures all data traffic on a given SAP or network interface uses a single LAG port on egress. Because all traffic for a given SAP/ network interface egresses over a single port, QoS SLA enforcement for that SAP, network interface is no longer impacted by the property of LAG (distributing traffic over multiple links).
  • Page 153 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Multiple classes allow grouping of SAPs/interfaces/subscribers by similar bandwidth class/type. For example a class can represent: voice – negligible bandwidth, Broadband – 10 to 100 Mb/s, Extreme Broadband – 300 Mb/s and above types of service.
  • Page 154: Explicit Per Link Hash Using Lag Link Mapping Profiles

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Optionally an operator can use a tools perform lag load-balance command to manually re-balance all weighted per-link-hashed SAPs/interfaces/subscribers on a LAG. The rebalance follows the algorithm as used on a link failure moving SAPs/ interfaces/subscribers to different LAG links to minimize SAPs/interfaces/ subscribers impacted.
  • Page 155: Consistent Per Service Hashing

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 • Secondary link—defines a port of the LAG to be used by a SAP/network interface as a backup when the primary link is not available (not configured or down) and the secondary link is UP. •...
  • Page 156 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Per-service-hashing was introduced to ensure consistent forwarding of packets belonging to one service. The feature can be enabled using the [no] per-service- hashing configuration option under config>service>epipe and config>service>vpls, valid for Epipe, VPLS, PBB Epipe, IVPLS and BVPLS. The following behavior applies to the usage of the [no] per-service-hashing option.
  • Page 157: Esm - Lag Hashing Per Vport

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 ISID Hashing Physical Link -------- ----------------------- ------------- per-service(if enabled) 3/2/8 A:Dut-B# tools dump map-to-phy-port lag 11 isid 1 end-isid 4 ISID Hashing Physical Link -------- ----------------------- ------------- per-service(if enabled) 3/2/8 per-service(if enabled) 3/2/7 per-service(if enabled) 1/2/2 per-service(if enabled) 1/2/3...
  • Page 158 The Vport instances of the same Vport on another member links are irrelevant for QoS treatment. The Vport for Nokia routers is referenced via inter-dest-string, which can be returned via RADIUS. For this reason, the terms hashing per inter-dest-string or hashing per Vport can be interchangeably used.
  • Page 159 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 This feature can be enabled using the CLI command config>subscriber- mgmt>sub-profile>vport-hashing. On the HSMDA, the secondary shaper supports Vport hashing through the config>subscriber-mgmt>sub- profile>secondary-shaper-hashing command. 2.6.4.5.4 Multicast Consideration Multicast traffic that is directly replicated per subscriber follows the same hashing algorithm as the rest of the subscribers (per inter-dest-string hashing).
  • Page 160: Lag Hold Down Timers

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 First the ECMP hash. It consists of an initial hash based on the source port/system IP address. Each label in the stack is then hashed separately with the result of the previous hash, up to a maximum of five labels. The net result will be used to select which LDP FEC next-hop to send the packet to using a modulo operation of the net result with the number of next-hops.
  • Page 161: Bfd Over Lag Links

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 1. Port-level hold-time up/down timer This optional timer allows operator to control delay for adding/removing a port from LAG when the port comes UP/goes DOWN. Each LAG port runs the same value of the timer, configured on the primary LAG link. See the Port Link Dampening description in Port Features for more details on this timer.
  • Page 162: Mixed Port-Speed Lag Support

    RELEASE 15.0.R5 2.6.7 Mixed Port-Speed LAG Support Nokia routers support mixing different speed member ports in a single LAG. The LAG must be configured explicitly to allow mixed port-speed operation through the port- weight-speed command. The port-weight-speed defines both the lowest port speed for a member port in that LAG and the type of higher speed ports allowed to be mixed in the same LAG.
  • Page 163 • PIM lag-usage-optimization is not supported and must not be configured • LAG member links must have the default configuration for config port ethernet egress-rate/ingress-rate • not supported on the 7450 ESS-6V • not supported for ESM Issue: 01 3HE 11968 AAAC TQZZA 01...
  • Page 164: Lag Upgrade

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.6.7.1 LAG Upgrade Migrating LAGs to higher speed links involves using mixed-speed LAGs initially, and later removing lower speed links. However, a consequence is that the lower speed links in the mixed-speed LAG set the member link limit. Even after all lower speed links are removed, the higher-speed links maintain a higher weight and this limits how many physical links that a mixed-port speed LAG can include.
  • Page 165: Overview

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Typically, MC-LAG is deployed in a network-wide scenario providing redundant connection between different end points. The whole scenario is then built by combination of different mechanisms (for example, MC-LAG and redundant pseudowire to provide e2e redundant p2p connection or dual homing of DSLAMs in Layer 2/3 TPSDA).
  • Page 166 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 − In case there is a tie in the selection algorithm, for example, two sub-groups with identical aggregate weight (or number of active links) the group which is local to the system with lower system LACP priority and LAG system ID is taken.
  • Page 167 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Figure 41 MC-LAG Layer 2 Dual Homing to Remote PE Pairs PE-A PE-D IP/MPLS MSAN MSAN Network PE-B PE-C PE-A IP/MPLS MSAN PE-C MSAN Network PE-B Fig_6 Issue: 01 3HE 11968 AAAC TQZZA 01...
  • Page 168 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Figure 42 MC-LAG Layer 2 Dual Homing to Local PE-Pairs PE-A MSAN MSAN PE-B PE-A MSAN PE-B MSAN PE-A MSAN PE-B MSAN PE-C Fig_7 The forwarding behavior of the nodes abide by the following principles. Note that logical destination (actual forwarding decision) is primarily determined by the service (VPLS or VLL) and the principle below applies only if destination or source is based on MC-LAG:...
  • Page 169: Mc-Lag And Subscriber Routed Redundancy Protocol (Srrp)

    Refer to the 7450 ESS, 7750 SR, and VSR Triple Play Service Delivery Architecture Guide for information about SRRP.
  • Page 170 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Figure 43 P2P Redundant Connection Through a Layer 2 VPN Network TLDP Aggregation Aggregation node node Active Standby Active Standby Active Standby Inter-chassis Inter-chassis MSAN MSAN PW for VLL PW for VLL Standby Active Standby Active Aggregation...
  • Page 171: Dslam Dual Homing In Layer 2/3 Tpsda Model

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.6.8.4 DSLAM Dual Homing in Layer 2/3 TPSDA Model Figure 44 shows a network configuration where DSLAM is dual homed to pair of redundant PEs by using MC-LAG. Inside the aggregation network redundant-pair of PEs is connecting to VPLS service which provides reliable connection to single or pair of Broadband Service Routers (BSRs).
  • Page 172: Protected Ethernet Tunnels

    ITU-T G.8031 specification to achieve 50 ms resiliency for failures in a native Ethernet backbone. For further information regarding Ethernet tunnels, refer to “G.8031 Protected Ethernet Tunnels” in the 7450 ESS, 7750 SR, 7950 XRS, and VSR Services Overview Guide.
  • Page 173: Protected Ethernet Rings

    Ethernet OAM and often referred to as Ring Automatic Protection Switching (R- APS). For further information regarding Ethernet rings, Refer to “G.8032 Protected Ethernet Rings” in the 7450 ESS, 7750 SR, 7950 XRS, and VSR Services Overview Guide. Issue: 01 3HE 11968 AAAC TQZZA 01...
  • Page 174: Ethernet Port Monitoring

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.9 Ethernet Port Monitoring Ethernet ports can record and recognize various medium statistics and errors. There are two main types of errors: • Frame Based — Frame based errors are counted when the arriving frame has an error that means the frame is invalid.
  • Page 175 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 ---------------------------------------------- symbol-monitor sd-threshold 5 multiplier 5 sf-threshold 3 multiplier 5 no shutdown exit show port 2/1/2 ethernet =============================================================================== Ethernet Interface =============================================================================== Description : 2/1/2 Interface : 2/1/2 Oper Speed : N/A Link-level : Ethernet Config Speed : 1 Gbps Admin State...
  • Page 176 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Transceiver Data Transceiver Status : not-equipped =============================================================================== Traffic Statistics =============================================================================== Input Output ------------------------------------------------------------------------------- Octets Packets Errors Utilization (300 seconds) 0.00% 0.00% =============================================================================== =============================================================================== Port Statistics =============================================================================== Input Output ------------------------------------------------------------------------------- Unicast Packets Multicast Packets Broadcast Packets Discards Unknown Proto Discards ===============================================================================...
  • Page 177 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 A port is not returned to service automatically when a port enters the failed condition as a result of crossing a signal failure threshold for both CRC-Monitor and Symbol- Monitor. Since the port is operationally down without a physical link error monitoring stops.
  • Page 178: Ah Oam

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.10 802.3ah OAM 802.3ah Clause 57 (efm-oam) defines the Operations, Administration, and Maintenance (OAM) sub-layer, which provides mechanisms useful for monitoring link operation such as remote fault indication and remote loopback control. In general, OAM provides network operators the ability to monitor the health of the network and quickly determine the location of failing links or fault conditions.
  • Page 179 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 The value 00:00:00:00 is sent for all releases that do not support the non-zero value or are unable to identify the required elements. There is no decoding of the peer or local vendor information fields on the network element. The hexadecimal value is included in the show port port-id ethernet efm-oam output.
  • Page 180: Oam Events

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Accounting Policy : None Collect-stats : Disabled Acct Plcy Eth Phys : None Collect Eth Phys : Disabled Egress Rate : Default Ingress Rate : Default Load-balance-algo : Default LACP Tunnel : Disabled Down-when-looped : Disabled Keep-alive : 10...
  • Page 181: Link Monitoring

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 • Link Fault: The PHY has determined a fault has occurred in the receive direction of the local DTE • Dying Gasp: An unrecoverable local failure condition has occurred • Critical Event: An unspecified critical event has occurred The local node can set an unset the various Flag fields based on the operational state of the port, shutdown or activation of the efm-oam protocol or locally raised events.
  • Page 182 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 A degraded condition is raised when the configured signal degrade sd-threshold is reached. This provides a first level log only action indicating a link could become unstable. This event does not affect the port state. The critical failure condition is raised when the configured sf-threshold is reached.
  • Page 183 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 • Window: The size of the unique measurement period for the error type. The window is only checked at the end. There is not mid-window checking. • Threshold: The value of the configured sf-threshold •...
  • Page 184 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Symbol error, errored-symbols, monitoring is also supported but requires specific hardware revisions and the appropriate code release. The symbol monitor differs from the frame error monitors. Symbols represent a constant load on the Ethernet wire whether service frames are present or not.
  • Page 185 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Peer Mac Address : d8:1c:01:02:00:01 Peer Vendor OUI : 00:16:4d (alu) Peer Vendor Info : 00:01:00:02 Peer Mode : active Peer Pdu Size : 1518 Peer Cfg Revision Peer Support : LB Peer Grace Rx : false Loopback State : None...
  • Page 186 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 A clear command “clear port port-id ethernet efm-oam events [local | remote]” has been added to clear port affecting events on the local node on which the command is issued. When the optional [local | remote] options are omitted, both local and remote events will be cleared for the specified port.
  • Page 187: Remote Loopback

    Flag fields in the Information OAMPDU using the info-notifications command options when fault notification to a peer is required. Non-Nokia vendor specific information will not be processed. 2.10.1.1.1 Capability Advertising A supported capability, sometimes requiring activation, will be advertised to the peer.
  • Page 188: Ah Oam Pdu Tunneling For Epipe Service

    2.10.3 802.3ah OAM PDU Tunneling for Epipe Service Nokia routers support 802.3ah. Customers who subscribe to Epipe service treat the Epipe as a wire, so they demand the ability to run 802.3ah between their devices which are located at each end of the Epipe.
  • Page 189 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 procedure for EFM-OAM will clear all remote events that it received from the peer that performed the soft reset. The local events will not be cleared on the peer that has not undergone soft reset. The Information OAM PDU Flag fields are critical in propagating the local event to the peer.
  • Page 190 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Figure 45 Grace TLV Passive Node with Soft Reset Passive Active 1/1/1 2/2/2 Port State: Down Discovery: Start Port State: Down Port State: Up Discovery: Complete Port State: Up Info PDU Info PDU Operator Initiates Info PDU (Grace 900s) ISSU / Soft Reset Info PDU (Grace ACK)
  • Page 191 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Figure 46 Grace TLV Active Node with Soft Reset Passive Active 1/1/1 2/2/2 Port State: Down Discovery: Start Port State: Down Port State: Up Discovery: Complete Port State: Up Info PDU Info PDU Operator Initiates Info PDU (Grace 900s) ISSU / Soft Reset Info PDU (Grace ACK)
  • Page 192 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 The vendor-specific grace function benefits are realized when both peers support the transmitting, receiving and processing of the vendor-specific Grace TLV. In the case of mixed code versions, products, or vendor environments, a standard EFM-OAM message to the peer can be used to instruct the peer to treat the session as failed.
  • Page 193 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 These features do not support the clearing of an IOM which does not trigger a soft reset. IOM clearing is a forceful event that does not trigger graceful protocol renegotiation. A number of show commands have been enhanced to help operators determine the state of the802.3ah OAM Grace function and whether or not the peer is generating or receiving the Grace TLV.
  • Page 194 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Peer Grace Rx • False — Not receiving Grace TLV from the peer • True — Receiving Grace TLV from the peer 3HE 11968 AAAC TQZZA 01 Issue: 01...
  • Page 195: Mtu Configuration Guidelines

    • When the network group encryption (NGE) feature is enabled, additional bytes due to NGE packet overhead must be considered. Refer to the “NGE Packet Overhead and MTU Considerations” section in the 7450 ESS, 7750 SR, 7950 XRS, and VSR Layer 3 Services Guide: IES and VPRN for more information.
  • Page 196: Modifying Mtu Defaults

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Table 34 MTU Default Values (Continued) Port Type Mode Encap Type Default (bytes) SONET path or TDM channel network — 9208 SONET path or TDM channel access frame-relay 1578 SONET path or TDM channel access 1524 Note:...
  • Page 197 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Figure 47 MTU Configuration Example ALA-A ALA-B 1/1/1 Network Network 4/1/1 encap: 2/1/1 3/1/1 encap: null OSSG012 Since ALA-A uses Dot1q encapsulation, the SAP MTU must be set to 1518 to be able to accept a 1514 byte service frame (see Table 34 for MTU default values).
  • Page 198: Deploying Preprovisioned Components

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.12 Deploying Preprovisioned Components When a card, CMA, MDA, XCM or XMA is installed in a preprovisioned slot, the device detects discrepancies between the preprovisioned card type configurations and the types actually installed. Error messages display if there are inconsistencies and the card will not initialize.
  • Page 199: Setting Fabric Speed

    The system does not support any FP2 based cards when the chassis is set to fabric- speed-b. Note: For the 7750 SR-7/12 and 7450 ESS-7/12, the chassis must have a manufacturing date of 2008 or later (show chassis detail) to set fabric-speed-b.
  • Page 200: Versatile Service Module

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.14 Versatile Service Module 2.14.1 VSM-CCA-XP The VSM-CCA-XP MDA offers a hybrid mode for simplified provisioning and a high capacity VSM when inserted on IOM cards. The complete forwarding path bandwidth (in this case 25 Gb/s) is available, allowing single conversations up to 25 Gb/s on a single MDA.
  • Page 201 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 =============================================================================== *A:PE-1# The following is a sample VSM-CCM-XP configuration for ports: port 1/2/1 ethernet exit no shutdown exit port 1/2/2 ethernet exit no shutdown exit Port and Ethernet QoS parameters may be configured as they are for a physical port. The Ethernet on VSM-CCA-XP has a reduced set of features.
  • Page 202 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 ies 122 customer 1 create interface "Loopback" create address 10.1.1.1/24 sap lag-2:1001 create ingress qos 3 exit egress qos 1010 exit exit exit no shutdown exit 3HE 11968 AAAC TQZZA 01 Issue: 01...
  • Page 203: Configuration Process Overview

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.15 Configuration Process Overview Figure 48 displays the process to provision chassis slots, cards, MDAs, and ports. Figure 48 Slot, Card, MDA, and Port Configuration and Implementation Flow Start Chassis Specify Chassis Slot Slot Card Designate the Specific Card Type for the Slot Designate the Specific MDA Type for the Slot...
  • Page 204: Configuration Notes

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.16 Configuration Notes The following information describes provisioning caveats: • If a card or MDA type is installed in a slot provisioned for a different type, the card will not initialize. • A card or MDA installed in an unprovisioned slot remains administratively and operationally down until the card type and MDA is specified.
  • Page 205: Configuring Physical Ports With Cli

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.17 Configuring Physical Ports with CLI This section provides information to configure cards, MDAs, and ports. 2.17.1 Preprovisioning Guidelines SR OSs have a console port, either located on the CPM or CCM, or integrated into the chassis (on the 7750 SR-c4 models), to connect terminals to the router.
  • Page 206: Maximizing Bandwidth Use

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 − Configure an access port for customer facing traffic on which services are configured. An encapsulation type may be specified in order to distinguish services on the port or channel. Encapsulation types are not required for network ports. To configure an Ethernet access port, see Ethernet Access Port.
  • Page 207: Basic Configuration

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.17.2 Basic Configuration The most basic configuration must specify the following: • chassis slot • line card type (must be an allowed card type) • MCM slot for the 7750 SR-c4 and SR-c12 only (not required for CMA) •...
  • Page 208 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 card-type iom-xp mcm 1 mcm-type mcm-xp no shutdown exit mcm 3 mcm-type mcm-xp no shutdown exit mcm 7 mcm-type mcm-xp no shutdown exit mda 1 mda-type m4-choc3-as-sfp no shutdown exit mda 3 mda-type m8-oc3-sfp no shutdown exit mda 5...
  • Page 209: Common Configuration Tasks

    Card configurations include a chassis slot designation. A slot must be preconfigured with the type of cards and MDAs which are allowed to be provisioned. The following example shows card and MDA configurations for the 7750 SR or 7450 ESS: #-------------------------------------------------- ‘echo "Card Configuration"...
  • Page 210 (optional) to create and edit QoS pool resources on egress network ports, channels, and ingress MDAs. Network-queue and slope policies are configured in the config>qos context. The following example shows an MDA pool configuration for 7750 SR or 7450 ESS: A:ALA-B>config>card>mda# info ----------------------------------------------...
  • Page 211: Configuring Cards, Mcms, And Mcas

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.17.3.1.2 Configuring MDA Policies for Named Pools Mode Network ingress queues can use either MDA ingress named pools or ingress default pools but not port named pools. In the case with an IOM with multiple MDAs sharing the same buffer space (iom3-xp), network ingress queues will use only the MDA 1 named pools.
  • Page 212: Configuring Ports

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.17.3.2.1 Configuring Cards and CMAs Card configurations must include a chassis slot designation. A slot must be preconfigured with the type of cards and CMAs (Compact Media Adapters) which are allowed to be provisioned. CMAs are configured using the MDA command.
  • Page 213 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Normally, the amount of active bandwidth is considered as opposed to total potential bandwidth for the port when determining the ports fair share. If a port is channelized and not all bandwidth is allocated, only the bandwidth represented by the configured channels with queues configured is counted towards the bandwidth represented by the port.
  • Page 214 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 • All queues defined for a port receive buffers from the same buffer pool. The Named Buffer Pools feature offers the following new capabilities: • Ability to modify the port bandwidth considered for buffer allocation without changing the active port bandwidth.
  • Page 215 20 network 40 2.17.3.3.3 Changing APS Parameters Note: Nokia recommends grouping working lines and protect lines on separate IOMs. APS configuration rules: • A working port must be added first. Then a protection port can be added or removed at any time.
  • Page 216 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 The following shows a sample configuration for an ATM SC-APS group that contains an aPipe SAP: A:ALA-274>config# port (1/1/1) ---------------------------------------------- sonet-sdh speed oc3 exit no-shutdown ---------------------------------------------- A:ALA-274>config>port# aps-1 ---------------------------------------------- working-circuit 1/1/1 protect-circuit 1/1/2 exit sonet-sdh path exit...
  • Page 217 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 neighbor 13.1.1.1 protect-circuit 2/2/2 exit no shutdown ---------------------------------------------- A:ALA-274>config>port# 2.17.3.3.4 Configuring Ethernet Port Parameters Ethernet Network Port A network port is network facing and participates in the service provider transport or infrastructure network processes. The following example shows a network port configuration: A:ALA-B>config>port# info ----------------------------------------------...
  • Page 218 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 slope-policy "slopePolicy2" exit exit exit ethernet mode access encap-type dot1q exit no shutdown ---------------------------------------------- A:ALA-A>config>port# Configuring 802.1x Authentication Port Parameters The following example shows an 802.1x port configuration: A:ALA-A>config>port>ethernet>dot1x# info detail ---------------------------------------------- port-control auto radius-plcy dot1xpolicy re-authentication re-auth-period 3600...
  • Page 219 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 • ATM OC-12 • Channelized ASAP OC3 • Channelized ASAP OC12 When an Ethernet port is configured in WAN mode (xgig wan), you can change certain SONET/SDH parameters to reflect the SONET/SDH requirements for this port.
  • Page 220 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 SONET/SDH Access Port The following example shows a SONET/SDH access port configuration for the 7750 SR: A:ALA-A>config>port# info ---------------------------------------------- description "SONET/SDH access port" sonet-sdh path mode access encap-type frame-relay mac 00:03:47:c8:b4:86 frame-relay exit no shutdown exit exit no shutdown...
  • Page 221 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Table 36 Channelization Options Available on the 7750 SR Channelized MDAs (Continued) Framing Channelization/Mapping Option Channelized MDAs Supporting Services on the Port/ Channel STM4>AUG4>AUG1>VC4>TUG3>VC3 m1-choc12 m4-choc3 m12-chds3 m4-choc3-as STM4>AUG4>AUG1>VC3 m1-choc12 m4-choc3 m12-chds3 m4-choc3-as SONET OC12>STS12>STS1 SPE m1-choc12 m4-choc3...
  • Page 222 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Table 36 Channelization Options Available on the 7750 SR Channelized MDAs (Continued) Framing Channelization/Mapping Option Channelized MDAs Supporting Services on the Port/ Channel STM4>AUG4>AUG1>VC4>TUG3>VC3>DS3 m1-choc12 m4-choc3 m12-chds3 m4-choc3-as STM4>AUG4>AUG1>VC3>DS3 m1-choc12 m4-choc3 m12-chds3 m4-choc3-as SONET OC12>STS12>STS1 SPE>VT GROUP>VT2 SPE m1-choc12 m4-choc3...
  • Page 223 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Table 36 Channelization Options Available on the 7750 SR Channelized MDAs (Continued) Framing Channelization/Mapping Option Channelized MDAs Supporting Services on the Port/ Channel STM4>AUG4>AUG1>VC3>TUG2>VC12 m1-choc12 m4-choc3 m12-chds3 m4-choc3-as STM4>AUG4>AUG1>VC4>TUG3>VC3>DS3 m1-choc12 m4-choc3 m12-chds3 m4-choc3-as STM4>AUG4>AUG1>VC3>DS3 m1-choc12 m4-choc3 m12-chds3...
  • Page 224 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Table 37 Channelized Port Syntax Examples Port ID for Physical Port Speed Channel OC12/STM4 OC3/STM1 DS3/E3 speed SONET/SDH STS12/STM4 port.sts12 STS3/STM1 port.sts3-{1 to 4} port.sts3 STS1/STM0 port.sts1-{1 to 4}.{1 to 3} port.sts1-{1 to 3} TUG3 port.tug3-{1 to 4}.{1 to 3} port.tug3-{1 to 3}...
  • Page 225 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Verify the MDA Type To make sure that you have a channel-capable MDA, verify that the MDA-type you are configuring by entering a show mda slot-id command. The MDAs shown in the MDA Provisioned column in the following output are a 12- port channelized DS3 MDA (m12-ds3) on card 1, MDA slot 1, and a 1-port channelized OC12-SFP MDA (m1-choc12-sfp) on card 1, MDA slot 2.
  • Page 226 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Figure 49 Channelized DS3 Port Structure The following shows the steps to configure a channelized port on a 12-port DS3 MDA: A:ALA-A>config# port 7/1/1 A:ALA-A>config>port# tdm In order to set the channelized mode on a port, the DS3 parameter must be in a shut down state.
  • Page 227 Services can be applied to the configured channelized ports. The following example shows the CLI usage to configure a customer IES service with interface SAPs on the channelized ports. Refer to the 7450 ESS, 7750 SR, 7950 XRS, and VSR Services Overview Guide for information about how to configure services.
  • Page 228 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 A:ALA-A>config>service# ies 103 customer 1 create A:ALA-A>config>service>ies$ interface test1 create A:ALA-A>config>service>ies>if$ address 102.21.1.1/24 A:ALA-A>config>service>ies>if# sap 7/1/1.1.2 create A:ALA-A>config>service>ies>if>sap$ exit A:ALA-A>config>service>ies>if# no shutdown A:ALA-A>config>service>ies>if# exit A:ALA-A>config>service>ies# interface test2 create A:ALA-A>config>service>ies>if$ address 102.22.1.1/24 A:ALA-A>config>service>ies>if$ sap 7/1/1.2.1 create A:ALA-A>config>service>ies>if>sap$ exit A:ALA-A>config>service>ies>if# no shutdown A:ALA-A>config>service>ies>if# exit...
  • Page 229 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Figure 50 Channelized OC-12 Port Structure The following shows an example to configure a channelized port on a 1-port channelized OC-12-SFP MDA: ALA-A>config# port 5/2/1 At this level you must choose the tributary. When provisioning DS3 nodes on a channelized OC-12 MDA, you must provision the parent STS1-1 SONET path first.
  • Page 230 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 In order to set the channelized mode on a port, the DS3 parameter must be in a shut down state. Clear channel uses out-of-band signaling, not in-band signaling, so the channel's entire bit rate is available. Channelized ports use in-band signaling and must be explicitly enabled.
  • Page 231 Services can be applied to the configured channelized ports. The following example shows the CLI usage to configure a customer IES service with interface SAPs on the channelized ports. Refer to the 7450 ESS, 7750 SR, 7950 XRS, and VSR Services Overview Guide for information about how to configure services.
  • Page 232 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 ---------------------------------------------- interface "testA" create address 192.22.1.1/24 sap 5/2/1.1.1.1.1 create exit exit interface "testB" create address 192.23.1.1/24 sap 5/2/1.1.1.1.2 create exit exit no shutdown ---------------------------------------------- A:ALA-A>config>service>ies# Configuring a Channelized Any Service Any Port (ASAP) OC3-SFP Port This section provides examples to configure PPP, FR, cHDLC, and ATM n*DS0 channels on a channelized port on channelized ASAP OC-3 SFP MDA in slot 1/1/1.
  • Page 233 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 A:ALA-A>config>port>tdm>ds3# no shutdown A:ALA-A>config>port>tdm>ds3# exit A:ALA-A>config>port# info ---------------------------------------------- sonet-sdh path sts1-1 no shutdown exit exit ds3 1 channelized e1 no shutdown exit exit no shutdown ---------------------------------------------- A:ALA-A>config>port# In the TDM E1 context, configure DS0 channel groups and their parameters. For a DS1 channel-group, up to 24 timeslots can be assigned (numbered 1 to 24).
  • Page 234 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 e1 1.1 channel-group 1 timeslots 2 no shutdown exit channel-group 2 encap-type frame-relay frame-relay exit timeslots 10 no shutdown exit channel-group 3 encap-type cisco-hdlc cisco-hdlc exit timeslots 11,12 no shutdown exit no shutdown exit e1 1.2 channel-group 1 encap-type atm...
  • Page 235 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 encap-type {bcp-null|bcp-dot1q|ipcp|ppp- auto|frame-relay|wan-mirror|cisco- hdlc} timeslots timeslots no shutdown The following example shows SONET/SDH access mode configuration command usage: Example: A:ALA-29>config>port>tdm# ds3 A:ALA-29>config>port>tdm>ds3# channelized ds1 A:ALA-29>config>port>tdm>ds3# no shutdown A:ALA-29>config>port>tdm>ds3# exit A:ALA-29>config>port>tdm# ds1 1 A:ALA-29>config>port>tdm>ds1# no shutdown A:ALA-29>config>port>tdm>ds1# channel-group 1 A:ALA-29>config>port>tdm>ds1>channel-group# timeslots 1- A:ALA-29>config>port>tdm>ds1>channel-group# encap-type...
  • Page 236 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.17.3.3.7 Configuring Channelized STM1/OC3 Parameters The following example shows basic syntax to configure channelized STM1/OC3 parameters: CLI Syntax: config# port port-id sonet-sdh framing {sonet|sdh} group sonet-sdh-index payload {tu3|vt2|vt15} path [sonet-sdh-index] payload {sts3|tug3|ds3|e3} trace-string [trace-string] no shutdown Example: config# port 5/2/1...
  • Page 237 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 group tug3-3 payload vt2 path vt2-1.1.1 trace-string "LO-path 3.7.3" no shutdown exit path vt2-3.7.3 no shutdown exit exit e1 1.1.1 channel-group 1 timeslots 2-32 no shutdown exit no shutdown exit e1 3.7.3 channel-group 2 timeslots 2-32 no shutdown exit...
  • Page 238 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 BERT Errors BERT Status : idle BERT Total Bits Cfg Alarm : ais los Alarm Status =============================================================================== A:sim216# Configuring a Channel Group The following shows an example of a DS1 channel group configured for CES. A:sim216# show port 1/5/1.1.3.1 ===============================================================================...
  • Page 239 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 ATM SAP in an Epipe Service The following shows a sample Epipe service SAP configuration: B:ALA-701>config>service# info ---------------------------------------------- epipe 5 customer 1 create shutdown sap 2/1/2:15/25 create exit sap 2/1/3:25/35 create exit exit ---------------------------------------------- B:ALA-701>config>service# 2.17.3.3.9 Configuring DWDM Port Parameters...
  • Page 240 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 *A:ALA-A>config>port>dwdm>wavetracker># info detail ---------------------------------------------- power-control target-power -7.50 exit encode key1 205 key2 749 report-alarm enc-fail enc-degr pwr-fail pwr-degr pwr-high pwr-low ---------------------------------------------- 2.17.3.3.10 Configuring WaveTracker Parameters The following example shows the default configuration with WaveTracker disabled: *A:ALA-A>config>port>dwdm># info ---------------------------------------------- channel 44...
  • Page 241 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 exit rxdtv-adjust ---------------------------------------------- *A:ALA-A>config>port>dwdm># wavetracker *A:ALA-A>config>port>dwdm>wavetracker># info ---------------------------------------------- power-control target-power -7.50 exit encode key1 205 key2 749 ---------------------------------------------- *A:ALA-A>config>port>dwdm>wavetracker># info detail ---------------------------------------------- power-control target-power -7.50 exit encode key1 205 key2 749 report-alarm enc-fail enc-degr pwr-fail pwr-degr pwr-high pwr-low ---------------------------------------------- The following is an example of the show port <portId>...
  • Page 242 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 1001 1004 1018 1021 1035 1038 1052 1055 1069 1072 1086 1089 1103 1573 1587 1106 1120 1590 1604 1123 1137 1607 1621 1140 1154 1624 1638 1157 1171 1641 1655 1174 1188 1658 1672 1191 1205...
  • Page 243 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 3704 3718 2168 2182 3721 3735 2185 2199 3738 3752 2202 2216 3755 3769 2219 2233 3772 3786 2236 2250 3789 3803 2253 2267 3806 3820 2270 2284 3823 3837 2287 2301 3840 3854 2304 2318 3857...
  • Page 244 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 exit ---------------------------------------------- The following example shows the show port <portId> otu detail for the default OTU configuration as shown above: *A:ALA-A# show port 3/2/1 otu detail =============================================================================== OTU Interface =============================================================================== OTU Status : Enabled FEC Mode : enhanced Async Mapping...
  • Page 245 ATM interface parameters can only be configured for SONET/SDH ports/paths and TDM ports/channels supporting ATM encapsulation, and for IMA multilink bundles. ATM interface parameters allow users to configure characteristics of an ATM interface. The Nokia routers support configuration of the following ATM interface characteristics: Issue: 01...
  • Page 246 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 • Cell-format — Allows user to select the ATM cell format to be used on a given interface: UNI/NNI • ILMI — Allows user to enable/disable ILMI protocol • Traffic-desc — Allows user to configure ILMI PVCC TM characteristics over a given ATM interface ingress and egress direction characteristics can be configured separately) •...
  • Page 247 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Table 39 Alarm State Interactions (Continued) Content of the Received Signal Status Field Values Prob Prob Down Lower Far End Layer Alarm Rx Down Prob None Lower Incoming Layer Down Prob Prob Down Lower Incoming Layer Down...
  • Page 248 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 ATM Interface Configurations Use the following CLI syntax to configure ATM interface parameters for SONET/SDH paths: CLI Syntax: config# port port-id sonet-sdh path [sonet-sdh-index] cell-format cell-format ilmi [vpi/vci] egress traffic-desc traffic-desc- profile-id ingress traffic-desc traffic-desc- profile-id keep-alive [poll-frequency seconds] [poll-count value]...
  • Page 249 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 channel-group 1 cell-format cell-format min-vp-vpi value e3 [sonet-sdh-index] cell-format cell-format min-vp-vpi value 2.17.3.3.13 Configuring Frame Relay Parameters Frame Relay pipes are used to provide customer-to-customer Frame Relay PVCs or to interconnect individual Frame Relay clouds. Frame Relay parameters can only be configured in SONET/SDH and channelized TDM MDA contexts.
  • Page 250 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 frame-relay lmi-type itu mode dte n393dce 4 n393dte 4 n391dte 6 n392dce 3 n392dte 3 t391dte 10 t392dce 15 exit no shutdown exit exit exit no shutdown ---------------------------------------------- A:ALA-7>config>port# SONET/SDH Interfaces This section applies also to FR interfaces on Sonet/SDH high-speed channels on ASAP MDAs.
  • Page 251: Configuring Multilink Ppp Bundles

    "OC-3/OC-12 SONET/SDH" mode access encap-type frame-relay no mtu no mac crc 32 no scramble trace-string "Nokia 7750 ALA-" report-alarm plop pplm puneq no report-alarm pais prdi prei signal-label 0xcf frame-relay lmi-type itu mode dte n393dce 4 n393dte 4...
  • Page 252 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Multilink bundling operations are modeled after a virtual PPP link-layer entity where packets received over different physical link-layer entities are identified as belonging to a separate PPP network protocol (the Multilink Protocol, or MP) and recombined and sequenced according to information present in a multilink fragmentation header.
  • Page 253 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Configuration notes: An IMA group has common interface characteristics (for example, configuration that applies to a logical ATM interface either configured via the IMA group context or taken from the primary link) The following list details those common IMA group interface characteristics: •...
  • Page 254 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 • IMA group maximum bandwidth and minimum link settings allows, by default, for over-subscription of shaped services; however when that occurs scheduling of traffic over an IMA group ATM interface degrades to round-robin between shaped services, therefore to preserve full ATM TM even during a member link failure, it is recommended that maximum bandwidth is set to minimum links.
  • Page 255 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.17.3.3.16 Multi-Class MLPPP The following guidelines apply to multi-class MLPPP: • MC-MLPPP must be configured before links are added to a bundle. • MC-MLPPP and LFI (config>port>ml-bundle>interleave-fragments) are mutually exclusive. • MC-MLPPP is not supported when port is configured as network mode. •...
  • Page 256 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 1. The test procedure is performed as defined by the IMA specification version 1.1, i.e. a test pattern is sent over the specified link and is expected to be looped back over all the links in the group. ICP cells are used to perform the test. 2.
  • Page 257 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 config>card# mda 2 config>card>mda# mda-type m4-choc3-as-sfp config>card>mda# no shutdown config>card>mda# exit Configure an APS group with working and protection circuits on the ASAP MDAs. Example: config# port aps-1 config>port# aps config>port>aps# working-circuit 3/2/1 config>port>aps# protect-circuit 10/2/1 config>port>aps# exit config>port# no shutdown Create eight ATM DS1 channels on the APS group.
  • Page 258 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 config>port>multilink-bundle# protect-bundle bundle-ima- 2/1.1 config>port>multilink-bundle# member aps-1.1.1.1 config>port>multilink-bundle# member aps-1.1.2.1 config>port>multilink-bundle# member aps-1.1.3.1 config>port>multilink-bundle# member aps-1.1.4.1 config>port>multilink-bundle# member aps-1.1.5.1 config>port>multilink-bundle# member aps-1.1.6.1 config>port>multilink-bundle# member aps-1.1.7.1 config>port>multilink-bundle# member aps-1.1.8.1 config>port>multilink-bundle# exit config>port>multilink-bundle# no shutdown config>port>multilink-bundle# exit config>port# no shutdown Finally, a service can be configured on this bundle using the BPGrp ID (for example, an ATM VC 0/32 SAP would be: sap bpg-ima-1:0/32).
  • Page 259 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 − To increase the BPGrp robustness, it is recommended to provision more IMA/MLPPP links than is required and set the minimum links and max bandwidth parameters to the number of required links. This type of configuration is required on the far end as well.
  • Page 260 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 Hardware Data Part number : Sim Part# CLEI code : Sim CLEI Serial number : mda-7 Manufacture date : 01012003 Manufacturing string : Sim MfgString mda-7 Manufacturing deviations : Sim MfgDeviation mda-7 Administrative state : up Operational state : up...
  • Page 261 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 no shutdown exit channel-group 2 encap-type frame-relay frame-relay exit timeslots 10 no shutdown exit channel-group 3 encap-type cisco-hdlc cisco-hdlc exit timeslots 11,12 no shutdown exit no shutdown exit e1 1.2 channel-group 1 encap-type atm exit no shutdown exit...
  • Page 262 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 port 1/5/1 port 1/7/1 port 1/9/1 dynamic-cost port-threshold 4 action down ---------------------------------------------- A:ALA-A>config>lag# Configuring BFD on LAG Links BFD can be configured under the LAG context to create and establish the micro-BFD session per link after the LAG and associated links have been configured. An IP interface must be associated with the LAG or a VLAN within the LAG, if dot1q encapsulation is used, before the micro-BFD sessions can be established.
  • Page 263 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 • Max-Time-Admin-Down - This parameter controls how long the system will wait before bringing the associated link out of service if an admin down message is received from the far-end. The following is a sample configuration: *A:Dut-C>config>lag# info ---------------------------------------------- family ipv4...
  • Page 264 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 • The operator can update these port parameters only if the port is the sole member of an Ethernet tunnel. This means that in the example below, the operator needs to remove port 1/1/4 and port 1/1/5 before being allowed to modify 1/1/1 for the above parameters.
  • Page 265 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 no shutdown Issue: 01 3HE 11968 AAAC TQZZA 01...
  • Page 266: Service Management Tasks

    MDA,MCM, CMA, or the XMA from the configuration. To modify or delete CMAs or XMAs, use the MDA command structure. Use the following CLI syntax to modify an MDA on the 7450 ESS and 7750 SR platforms (or an XMA on the 7950 XRS platforms): CLI Syntax: config>...
  • Page 267: Deleting A Card

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 You must reset the IOM after changing the MDA type from MS-ISA to any other MDA type. Use the following CLI syntax to modify a card type already provisioned for a specific slot: CLI Syntax: config>...
  • Page 268: Deleting Port Parameters

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 2.18.4 Deleting Port Parameters Use the following CLI syntax to delete a port provisioned for a specific card or CMA: CLI Syntax: config>port port-id shutdown no port port-id 2.18.5 Soft IOM Reset This section provides basic procedures for soft IOM reset service management tasks.
  • Page 269: Deferred Mda Reset

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 Although the majority of protocols stay up during a Soft Reset, there are some limitations for a few protocols. Refer to Known Limitations in the Release Notes for the relevant release for details. Configuration changes are not allowed while any card is in the process of a soft reset. The soft IOM reset procedure is applicable during the ISSU process and for a manual soft reset procedure.
  • Page 270 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 If the MDA/IMM is not hard reset by the operator, and then a software upgrade is performed, and the older firmware is no longer compatible with the newest load being upgraded to, then the soft reset will be blocked (or an automatic hard reset will occur for Major ISSU).
  • Page 271: Configuration Command Reference

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.19 Configuration Command Reference 2.19.1 Command Hierarchies • Card Commands • MCM Commands • MDA Commands • Power Commands • Virtual Scheduler Commands • Forwarding Plane (FP) Commands • Port Configuration Commands • Port XC Commands •...
  • Page 272: Mcm Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 — [no] reset-on-recoverable-error 2.19.1.2 MCM Commands config — [no] card slot-number — [no] mcm-slot — mcm-type mcm-type — no mcm-type — [no] shutdown 2.19.1.3 MDA Commands config — [no] card slot-number — [no] mda-slot —...
  • Page 273: Power Commands

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 — ingress-xpl — threshold threshold — window window — mda-type mda-type — no mda-type — named-pool-mode — egress — named-pool-policy policy-name — no named-pool-policy — ingress — named-pool-policy policy-name — no named-pool-policy — network —...
  • Page 274: Virtual Scheduler Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 — [no] peq-slot [chassis chassis-id] — peq-type peq-type — no peq-type — input-power-mode amperage — [no] shutdown — power-safety-alert wattage — power-safety-level percent 2.19.1.5 Virtual Scheduler Commands config — [no] card slot-number — virtual-scheduler-adjustment —...
  • Page 275 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 — accounting-policy acct-policy-id — no accounting-policy — [no] collect-stats — description description-string — no description — policer-control-override [create] — no policer-control-override — max-rate {rate | max} — priority-mbs-thresholds — min-thresh-separation size [bytes | kilobytes] —...
  • Page 276: Port Configuration Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 — no policer policer-id — {size [bytes | kilobytes] | default} — no — {size [bytes | kilobytes] | default} — no — packet-byte-offset{add bytes | subtract bytes} — no packet-byte-offset — rate {max | kilobits-per-second} [cir {max | kilobits-per-second}] —...
  • Page 277 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 — [no] report-alarms [ild] [tmp] [mth] [mtl] [los] [lop] [com] — channel channel — coherent — channel channel — compatibility mode — cpr-window-size window-size — dispersion dispersion — mode {automatic | manual} — report-alarms [modflt] [mod] [netrx] [nettx] [hosttx] —...
  • Page 278 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 — resv-cbs percent-or-default amber-alarm-action step percent max [percentage] — resv-cbs percent-or-default — no resv-cbs — slope-policy name — no slope-policy — [no] — [no] async-mapping — {enhanced | g709} — no — otu2-lan-data-rate {11.049 | 11.0957} —...
  • Page 279: Port Xc Commands

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 — mismatch-reaction {squelch-rx} — no mismatch-reaction — auto-generated — bytes byte-string [byte-string] — string identifier — no — [no] shutdown 2.19.1.8 Port XC Commands config — port-xc — pxc-id [create] — no pxc-id — description description-string —...
  • Page 280: Ethernet Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 — — advertise-interval advertise-interval — no advertise-interval — hold-time hold-time — no hold-time — hold-time-aps [lsignal-failure sf-time] [lsignal-degrade sd-time] — no hold-time-aps — [no] mode-annexb — neighbor ip-address — no neighbor — protect-circuit port-id —...
  • Page 281 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 — max-peer max-peer — no max-peer — [no] rx-must-be-encrypted — [no] shutdown — port-control {auto | force-auth | force-unauth} — quiet-period seconds — radius-plcy name — no radius-plcy — re-auth-period seconds — no re-auth-period —...
  • Page 282 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 — sf-threshold errored-frames — [no] shutdown — window packets — errored-frame-seconds — [no] event-notification — sd-threshold errored-seconds — no sd-threshold — sf-threshold errored-seconds — [no] shutdown — window deciseconds — errored-symbols — [no] event-notification —...
  • Page 283 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 — max-rate rate — no max-rate — scheduling-class class rate rate — scheduling-class class weight weight-in-group — no scheduling-class class — hs-scheduler-policy policy-name — no hs-scheduler-policy — hs-secondary-shaper secondary-shaper-name [create] — no hs-secondary-shaper secondary-shaper-name —...
  • Page 284 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 — [no] ccm-enable — ccm-ltm-priority priority — no ccm-ltm-priority — ccm-padding-size ccm-padding — no ccm-padding-size — ccm-tlv-ignore [port-status] [interface-status] — no ccm-tlv-ignore — collect-lmm-stats — no collect-lmm-stats — [no] csf-enable — multiplier multiplier-value — no multiplier —...
  • Page 285 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 — ieee-address — no — min-frame-length byte-length — mode {access | network | hybrid} — no mode — [no] mon-port-sch — mtu-bytes — no — pbb-etype [ethertype-value] — no pbb-etype — ptp-asymmetry nanoseconds — no ptp-asymmetry —...
  • Page 286 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 — [no] queue-group queue-group-name [create] [instance instance-id] — accounting-policy acct-policy-id — no accounting-policy — [no] agg-rate — [no] limit-unused-bandwidth — [no] queue-frame-based-accounting — rate kilobits-per-second — no rate — [no] collect-stats — description description-string —...
  • Page 287 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 — no host-match dest destination-string — [no] mon-port-sch — port-scheduler-policy port-scheduler-policy-name — no port-scheduler-policy — ingress — [no] queue-group queue-group-name [create] — accounting-policy acct-policy-id — no accounting-policy — [no] collect-stats — description description-string — no description —...
  • Page 288: Interface Group Handler Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 — [no] hs-turbo — queue-overrides — queue queue-id [create] — no queue queue-id — adaptation-rule [pir {max | min | closest}] [cir {max | min | closest}] — no adaptation-rule — size-in-kbytes — no —...
  • Page 289 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 — no max-bandwidth — test-pattern-procedure — [no] shutdown — test-link port-id — no test-link — test-pattern pattern — no test-pattern — version IMA-version — no version — [no] interleave-fragments — [no] member port-id — minimum-links minimum-links —...
  • Page 290: Sonet-Sdh Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 — no qos-profile — [no] magic-number — multiclass count — no multiclass — [no] stateless-aps-switchover — mrru mrru — no mrru — [no] protect-bundle bundle-id — red-differential-delay red-diff-delay [down] — no red-differential-delay — [no] short-sequence —...
  • Page 291 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 — ilmi [vpi/vci] — no ilmi — egress — traffic-desc traffic-desc-profile-id — no traffic-desc — ingress — traffic-desc traffic-desc-profile-id — no traffic-desc — keep-alive [poll-frequency seconds] [poll-count value] [test-frequency seconds] — no keep-alive — protocol protocol-type —...
  • Page 292: Tdm Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 — no n393dce — n393dte count — no n393dte — t391dte keepalive — no t391dte — t392dce keepalive — no t392dce — load-balancing-algorithm option — no load-balancing-algorithm — ieee-address — no — mode {access | network | hybrid} —...
  • Page 293 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 — no bert — bit-error-insertion rate — no bit-error-insertion — [no] channel-group channel-group — — cell-format cell-format — min-vp-vpi value — cisco-hdlc — down-count down-count — no down-count — keepalive time-interval — no keepalive —...
  • Page 294 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 — no idle-cycle-flag — idle-payload-fill {all-ones} — idle-payload-fill pattern pattern — no idle-payload-fill — idle-signal-fill {all-ones} — idle-signal-fill pattern pattern — no idle-signal-fill — load-balancing-algorithm option — no load-balancing-algorithm — ieee-address — no — [no] mode {access | network} —...
  • Page 295: Ds3 Commands

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.19.1.16 DS3 Commands config — [no] port {port-id} — — [no] [sonet-sdh-index] — — cell-format cell-format — mapping mapping — min-vp-vpi value — bert {2e3 | 2e9 | 2e11 | 2e15 | 2e20 | 2e20q | 2e23 | ones | zeros | alternating} duration duration —...
  • Page 296: E1 Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 — n392dce threshold — no n392dce — n392dte threshold — no n392dte — n393dce count — no n393dce — n393dte count — no n393dte — t391dte keepalive — no t391dte — t392dce keepalive — no t392dce —...
  • Page 297 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 — bit-error-insertion rate — no bit-error-insertion — [no] channel-group channel-group-id — — cell-format cell-format — min-vp-vpi value — cisco-hdlc — down-count down-count — no down-count — keepalive time-interval — no keepalive — up-count up-count —...
  • Page 298: E3 Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 — idle-payload-fill pattern pattern — no idle-payload-fill — idle-signal-fill {all-ones} — idle-signal-fill pattern pattern — no idle-signal-fill — load-balancing-algorithm option — no load-balancing-algorithm — ieee-address — no — [no] mode {access | network} — mtu-bytes —...
  • Page 299 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 — cell-format cell-format — min-vp-vpi value — bert {2e3 | 2e9 | 2e11 | 2e15 | 2e20 | 2e20q | 2e23 | ones | zeros | alternating} duration duration — no bert — bit-error-insertion rate —...
  • Page 300: Lag Commands

    Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 — no t392dce — framing (E-3) {g751 | g832 | e3-unframed} — idle-cycle-flag {flags | ones} — no idle-cycle-flag — load-balancing-algorithm option — no load-balancing-algorithm — loopback {line | internal} — no loopback — ieee-address —...
  • Page 301 INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 — receive-interval interval — no receive-interval — remote-ip-address ip-address — no remote-ip-address — shutdown — no shutdown — transmit-interval interval — no transmit-interval — description long-description-string — no description — [no] dynamic-cost — encap-type {dot1q | null | qinq} —...
  • Page 302 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 — [no] rx-eth-vsm-grace — [no] tx-eth-vsm-grace — low-priority-defect {allDef | macRemErrXcon | remErrXcon | errXcon | xcon | noXcon} — mac-address mac-address — no mac-address — one-way-delay-threshold seconds — [no] shutdown — hold-time down hold-down-time —...
  • Page 303: Macsec Commands

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.19.1.20 MACsec Commands config — macsec — connectivity-association ca-name [create] — no connectivity-association ca-name — cipher-suite {type} — no cipher-suite — clear-tag-mode clear-tag-mode — no clear-tag-mode — description description — no description — encryption-offset {encryption-offset} —...
  • Page 304 Interfaces INTERFACE CONFIGURATION GUIDE RELEASE 15.0.R5 — no path-threshold — [no] path path-index — control-tag qtag[.qtag] — no control-tag — description description-string — no description — eth-cfm — [no] mep-id domain md-index association ma-index — alarm-notification — fng-alarm-time time — fng-reset-time time —...
  • Page 305: Multi-Chassis Redundancy Commands

    INTERFACE CONFIGURATION GUIDE Interfaces RELEASE 15.0.R5 2.19.1.22 Multi-Chassis Redundancy Commands config — redundancy — bgp-multi-homing — boot-timer seconds — no boot-timer — site-activation-timer seconds — no site-activation-timer — site-min-down-timer seconds — no site-min-down-timer — multi-chassis — peer ip-address [create] — [no] peer ip-address —...