8600 Smart Routers Ethernet Configuration Guide 76.8600-50133K 01.06.2015 Document Information Revision History Document No Date Description of Changes 76.8600-50133K 01.06.2015 Added support for 8665 Smart Router 8.2 Ethernet Switching QoS updated ELP support for 8615 Smart Router and 8665 Smart Router stacked Ethernet PWE3 redundancy support added for 8615 Smart Router stacked QinQ interface support added for 8615 Smart Router and 8665 Smart Router VPLS Scalability table added in 12.5 8600 VPLS Implementation LAG support for 8615 Smart Router and 8665 Smart Router added Ethernet Forwarding and OAM updates for 8615 Smart Router stacked and 8665 Smart Router LAG interface support for MAC switching for 8602 Smart Router 8602-D, 8609 Smart Router, 8611 Smart Router and ELC1 line card 76.8600-50133J 05.11.2014 Support for 8615 Smart Router added MAC Switching support for 8602 Smart Router, 8609 Smart Router and 8611 Smart Router added in Ethernet Switching New chapter 8.3 QoS Aware Flooding in MAC Switching and VPLS New chapter 9.2 Flooding Policer CLI Examples New chapter 1.1.3 Pause Frames Support in 8600 Network Elements LACP support added to Ethernet Link Aggregation ELC1 LAG support added to Ethernet Link Aggregation and 3.3 Joining Links to a Link Aggregation Group LAG restrictions added to 2.8 Limitations and Restrictions for LAG New chapter Limitations and Restrictions for electrical SFP support in 16.2 Limitations and Restrictions for ELP 76.8600-50133I 28.05.2014 Support for 8602 Smart Router added QinQ interface updates added in 1.1.2 Ethernet Logical Interfaces, 4.4.2 Ethernet PWE3 Forwarding, 4.4.3 Internal Ethernet Interface Bridging , 4.4.4 Limitations and Restrictions for Ethernet PWE3, , 14.5 Limitations and Restrictions for Ethernet OAM and 2.8 Limitations and Restrictions for LAG Extended Ethernet PWE3 attachment circuit support for LAG in 8600 smart routers in Ethernet Link Aggregation and Ethernet Link Aggregation CLI Configuration Examples Updated ETH PWE3 CLI example in 8600 Smart Routers Ethernet Configuration Guide 76.8600-50133K © 2015 Coriant Document No Date Description of Changes 76.8600-50133H 23.04.2014 Support for flexible IRB in CDC2 and clarification on the Qos mapping support added to Restriction removed from 10.2 Limitations and Restrictions for IRB: • Flexible IRB is supported only in configurations with a combination of ELC1 line cards and CDC1 control cards 76.8600-50133G 13.03.2014 1x10GBASE-R HM data added in 1.1.1 Ethernet Physical Interfaces ELC1 Ethernet MAC switching support added in Ethernet Switching 8.5 Applications of Ethernet Switching title updated 8.6 Limitations and Restrictions for Ethernet Switching added Ethernet pseudowire VCCV support updated in Ethernet pseudowire redundancy data added in 4.4.4 Limitations and Restrictions for Ethernet PWE3 added Note on ARP resolution with IFC2 IRB and flexible IRB support added in 10.2 Limitations and Restrictions for IRB added Virtual Private LAN Service (VPLS) data added in and related CLI examples in Ethernet Switching Service configuration example updated in 9.1 Ethernet Switching Service CLI Examples IRB configuration examples Manual Configuration Inside One NE and Ethernet PWE3 to VRF termination via IRB/VPLS added in 11 Integrated Routing and Bridging CLI Examples ELC1 Ethernet OAM support in 8609 Smart Router and 8611 Smart Router LAG support added in Ethernet Link Aggregation Eth lag min-link parameter description updated in 2.3 Link Aggregation Configuration IP fragmentation data in LAG load balancing updated in 2.3.4 Ethernet Link Aggregation Group 2.8 Limitations and Restrictions for LAG added ELC1 ELP support added in 16 Ethernet Link Protection ELP passive-if mode description and ELP group configuration rules updated in 16.1.1 Ethernet Link Protection Group ELP passive-if mode down added to 16.1.5 Operational Examples 16.2 Limitations and Restrictions for ELP added CPU packet storm control data added in 20 CPU Packet Storm Control This revision of the manual documents the following network elements and the corresponding feature packs or higher 8602 Smart Router FP7.0 8605 Smart Router FP1.6 8607 Smart Router FP1.1 8609 Smart Router FP7.0 8611 Smart Router FP7.0 8615 Smart Router FP7.0 8620 Smart Router FP4.1 8630 Smart Router FP7.0 8660 Smart Router FP7.0 8665 Smart Router FP7.0 If a different feature pack of 8600 products, please refer to the relevant product document program on the Tellabs and Coriant Portal by navigating to www.portal.tellabs.com > Product Documentation > Data Networking > Tellabs 8600 Smart Routers > Technical Documentation © 2014 Tellabs All rights reserved This manual is protected by U.S and international copyright laws, conventions and treaties Your right to use this manual is subject to limitations and restrictions imposed by applicable licenses and copyright laws Unauthorized reproduction, modification, distribution, display or other use of this manual may result in criminal and civil penalties The following trademarks and service marks are owned by Tellabs Operations, Inc or its affiliates in the United States and/or other countries: TELLABS ®, TELLABS ® logo, TELLABS and T symbol ®, T symbol ®, CORIANT TM Any other company or product names may be trademarks of their respective companies The specifications and information regarding the products in this manual are subject to change without notice All statements, information, and recommendations in this manual are believed to be accurate but are presented without warranty of any kind, express or implied Users must take full responsibility for their application of any products Adobe ® Reader ® are registered trademarks of Adobe Systems Incorporated in the United States and/or other countries Tellabs and Coriant are joining forces You may see references to Coriant or Tellabs when doing business with us Contact information is available at http://www.coriant.com 8600 Smart Routers Ethernet Configuration Guide 76.8600-50133K © 2015 Coriant Document Information Terms and Abbreviations Term Explanation AC Attachment Circuit ARP Address Resolution Protocol ATM Asynchronous Transfer Mode BE Best Effort BFD Bidirectional Forwarding Detection BGP Border Gateway Protocol BPDU Bridge Protocol Data Unit BRAS Broadband Remote Access Server BSC Base Station Controller C Customer device, usually a router a LAN switch (not a 8600 element) The device is owned by the customer and does not have a direct WAN connectivity CCM Continuity Check Message Control card The control card in the 8600 system consists of a Control and DC Power Card CDC (used in 8630 Smart Router and 8660 Smart Router), Switching and Control Module SCM (used in 8611 Smart Router) or Control Functionality CU (used in 8615 Smart Router and 8665 Smart Router) In 8000 Intelligent Network Manager and CLI referred to as unit CE Customer Edge device CFM Connectivity Fault Management CLI Command Line Interface CSMA/CD Carrier Sense Multiple Access with Collision Detection C-tag Customer VLAN tag (the inner VLAN tag) CU Control Functionality (used in 8615 Smart Router and 8665 Smart Router) C-VLAN Customer VLAN DA Destination Address DMM Delay Measurement Message DMR Delay Measurement Response DSLAM Digital Subscriber Line Access Multiplexer E-CCM Ethernet OAM CCM for IDU-ODU ELC1 Ethernet Line Card (used in 8630 Smart Router and 8660 Smart Router) ELP Ethernet Link Protection eNB Evolved NodeB ETH-DM Ethernet OAM Frame Delay Measurement Ethernet PDU Ethernet frame excluding preamble (7 bytes), start of frame delimiter (1 byte) and inter-frame gap (12 bytes) 76.8600-50133K © 2015 Coriant 8600 Smart Routers Ethernet Configuration Guide Document Information EtherType A two-octet field in an Ethernet frame It is used to indicate which protocol is encapsulated in the payload of an Ethernet frame ETH-LM Ethernet OAM Frame Loss Measurement FD Frame Delay FDV Frame Delay Variation FEC Forward Equivalence Class FIB Forwarding Information Base FLR Frame Loss Ratio FMC Fixed-mobile convergence FTN Forwarding equivalence class To Next hop label forwarding entry map (for MPLS) GE Gigabit Ethernet HM High Speed Module (used in 8611 Smart Router) H-VPLS Hierarchical VPLS IDU Indoor Unit IEEE Institute of Electrical and Electronics Engineers IETF Internet Engineering Task Force IFC Interface Module Concentrator is a line card baseboard and it can be equipped with one or two IFMs There are three variants available: IFC1-A, IFC1-B and IFC2-B (used in 8630 Smart Router and 8660 Smart Router) IFDV Inter-Frame Delay Variation IFM Interface Module A specific term of the module which can be placed on the IFC line card or 8620 Smart Router baseboard and which consists of the physical interfaces (used in 8620 Smart Router, 8630 Smart Router and 8660 Smart Router) IGMP Internet Group Management Protocol ILM Incoming Label Map (for MPLS) IP Internet Protocol iQoS Internal Quality of Service IRB Integrated Routing and Bridging L2 OSI Layer L3 OSI Layer LACP Link Aggregation Control Protocol LACPDU Link Aggregation Control Protocol Data Unit LAG Ethernet Link Aggregation LAN Local Area Network LAN-IC LAN Interconnection LAPF Link Access Procedure/Protocol for Frame Mode Services LBM Loopback Message LBR Loopback Response LDP Label Distribution Protocol (MPLS) 8600 Smart Routers Ethernet Configuration Guide 76.8600-50133K © 2015 Coriant Document Information Line card The line card in the 8600 system consists of an Ethernet Line Card (ELC1), Interface Module Concentrator (IFC) and up to two Interface Modules (IFMs) (used in 8630 Smart Router and 8660 Smart Router) or Line Unit LU (used in 8615 Smart Router and 8665 Smart Router) In 8000 Intelligent Network Manager and CLI referred to as unit LM Line module (used in 8607 Smart Router, 8609 Smart Router and 8611 Smart Router) LMEP Local Maintenance Endpoint LMM Loss Measurement Message LMR Loss Measurement Reply LOC Loss of Continuity LSP Label Switched Path LTE Long Term Evolution LTM Linktrace Message LTR Linktrace Reply LU Line Unit (used in 8615 Smart Router and 8665 Smart Router) MA Maintenance Association MAC Media Access Control Sublayer of Data Link Layer MAID Maintenance Association Identifier MAN Metro Area Network MD Maintenance Domain MDL Maintenance Domain Level ME Maintenance Entity MEP Maintenance Endpoint MIP Maintenance Intermediate Point MLPPP Multi-Link Point to Point Protocol MP Maintenance Point MPLS Multiprotocol Label Switching, a switching method that forwards IP traffic using a label MSP1+1 Multiplex Section Trail Protection 1+1 MSTP Multiple Spanning Tree Protocol MTU Maximum Transfer/Transmission Unit MTU Multi Tenant Unit A large building block with several rental apartment of offices in different floors Multiple hop Involves multiple packet forwarding decisions path 76.8600-50133K © 2015 Coriant NE Network Element Node In 8000 intelligent network manager and CLI refers to network element OAM Operation, Administration and Maintenance ODU Out Door Unit 8600 Smart Routers Ethernet Configuration Guide Document Information P-CCM Ethernet OAM CCM for ODU-ODU PDU Protocol Data Unit PE Provider Edge Network Element PIM Protocol Independent Multicast PM Performance Monitoring POS Packet over SDH/Sonet PRI bits User Priority field bits Protecting interface This ELP group member interface is selected by default as the passive interface Note that in CLI a protecting interface is referred to as a backup interface PSN Packet Switch Network PWE3 Pseudowire Emulation Edge to Edge IETF working group QoS Quality of Service RAN Radio Access Network RDI Remote Defect Indication RMEP Remote Maintenance Endpoint RNC Radio Network Controller RSTP Rapid Spanning Tree Protocol SA Source Address SAToP Structure-Agnostic Time Division Multiplexing over Packet SCM Switching and Control Module (used in 8611 Smart Router) Single hop Involves only a single packet forwarding decision SLI Set Link Info control message SNAP Subnetwork Access Protocol SSM Synchronization Status Message S-tag Service VLAN tag (the outer VLAN tag) STP Spanning Tree Protocol SU Switch Unit (used in 8665 Smart Router) S-VLAN Service VLAN TDM Time Division Multiplexing TLV Type Length Value T-PE Terminating Provider Edge Network Element (RFC4364) TTL Time-to-Live TX Transmit VCCV Virtual Circuit Connectivity Verification VLAN Virtual LAN VPLS Virtual Private LAN Service VPWS Virtual Private Wire Service 8600 Smart Routers Ethernet Configuration Guide 76.8600-50133K © 2015 Coriant Document Information 76.8600-50133K © 2015 Coriant VRF VPN Routing and Forwarding (RFC4364) VRRP Virtual Router Redundancy Protocol VSI Virtual Switching Instance WAN Wide Area Network Working interface This ELP group member interface is selected by default as the active interface The working interface must be the right-hand side interface of the two interfaces of an ELP group (in case of 8660 Smart Router the interface residing on the right-hand side IFC, in case of 8620 Smart Router the right-hand side interface on the IFMs, and in case of 8630 Smart Router the lower interface as IFCs are in horizontal direction) Note that in CLI a working interface is referred to as primary interface 8600 Smart Routers Ethernet Configuration Guide 8600 Smart Routers Ethernet Configuration Guide 10 76.8600-50133K © 2015 Coriant 16 Ethernet Link Protection Fig 55 Ethernet Switched Network Connection Example Network element is configured with the following settings: • primary interface: ge6/0/0 • Backup interface: ge5/0/0 • Passive interface transmitter mode: down-pulse • L2 learning frame transmission: enabled (needed because attached to an Ethernet switched network) In the initial situation traffic flows via the ge6/0/0 interface as shown in Fig 56 Fig 56 Ethernet Switched Network Connection Initial Situation 8600 Smart Routers Ethernet Configuration Guide 192 76.8600-50133K © 2015 Coriant 16 Ethernet Link Protection In case the lower link fails, NE detects the failure, activates the ge5/0/0 interface (enables frame transmit and receive, enables transmitter and takes the MAC and IP addresses into use) In certain Ethernet switching technologies (e.g VPLS) setting interface physically down causes the network to flush forwarding tables It also sends a learning frame (with the MAC address of the ELP group as the source address and the broadcast address as the destination address) on every VLAN The learning frames cause the Ethernet switched network to update forwarding tables The situation is afterwards as shown in Fig 57 Fig 57 Ethernet Switched Network Connection After Switchover Replacing Hardware This example discusses how to replace an IFM or ELC1 line card without a traffic break In this example an IFM or ELC1 line card containing the primary interface of an ELP group fails First a switchover takes place, i.e traffic is directed to the backup (formerly passive) interface Thus, only a very short traffic break is experienced The MAC address of the primary (now broken) interface is still used, as discussed in chapter 16.1.4 MAC Address The failed interface may now be removed, sent to repair and temporary hardware (IFM or ELC1 line card) installed for the meantime If the backup interface (currently active) also fails, traffic is switched back to the primary interface The MAC address of the original primary interface remains in use even though it is not physically present When the original working hardware returns from repair, the temporary hardware is removed and the original one installed back Now the situation is as before the failure On the other hand, if the original hardware cannot be repaired or it is not installed back from some other reason, the system may run with the temporary hardware Note that in this case the original primary interface must not be installed into the same Ethernet broadcast domain as the ELP group, because the ELP group still uses its MAC address The problem can be avoided by triggering the MAC address of the currently installed working hardware, e.g during a maintenance period 76.8600-50133K © 2015 Coriant 8600 Smart Routers Ethernet Configuration Guide 193 16 Ethernet Link Protection Note that the MAC address problem occurs only when the working hardware is replaced as the MAC address of an ELP group is by default taken from the primary interface 16.2 Limitations and Restrictions for ELP This chapter provides an outline of ELP limitations and restrictions • 8x10/100BASE-TX IFM HW version 1.x cannot be used in the same ELP group with version 2.x (or higher) • IFC1 or IFC2 and ELC1 line cards in the same ELP group is not supported • Electrical SFP Ethernet Interface has the following limitations: • ELP switchover time may be delayed up to 800 ms in 1000 Mbps mode, except in ELC1 or IFC2 when using SFP 81.86T-SM3TX02R-R6, which support fast line failure detection • ELP switchover time may be delayed up to s in the ELP passive-if-mode down mode • IEEE1588 L2 grandmaster, boundary clock, or time slave cannot be used on ports belonging to an ELP group • Mix of electrical and optical SFP interfaces as ELP members is not supported 16.3 References [IEEE 802.1AX] 8600 Smart Routers Ethernet Configuration Guide 194 IEEE Std 802.1AX-2008 – IEEE Standard for Local and metropolitan area networks: Link Aggregation 76.8600-50133K © 2015 Coriant 17 Ethernet Link Protection CLI Configuration Examples 17 Ethernet Link Protection CLI Configuration Examples This section provides configuration examples for Ethernet link protection It is advisable always to refer to 8600 Smart Routers CLI Commands Manual for the latest information on: • Default values to avoid unnecessary configuration; • Available configuration options and parametric range 17.1 Point-to-Point Connection This example depicts how ELP is configured to protect a direct connection between two 8600 network elements The network configuration is illustrated in Fig 52, section Point-to-Point Connection First, network element is configured The network element connects with interfaces ge8/1/2 and ge6/1/2 to network element Step Create an ELP group elp_example_ptop router(config)# protection elp elp_example_ptop Step Add ge8/1/2 as the primary interface and ge6/1/2 as the backup interface in the ELP group router(cfg-elp-prot[elp_example_ptop])# primary ge8/1/2 backup ge6/1/2 Step Configure both network elements to receive also on the passive side to enable the fastest possible switchover router(cfg-elp-prot[elp_example_ptop])# passive-if-mode up rx-both Next, network element is configured The network element connects with interfaces ge3/0/0 and ge2/0/0 to the network element Step Create an ELP group in the same way as for network element router(config)# protection elp elp_example_ptop Step Add interface ge3/0/0 as the primary and interface ge2/0/0 as the backup interface in the elp_example_ptop ELP group router(cfg-elp-prot[elp_example_ptop])# primary ge3/0/0 backup ge2/0/0 Step Configure both network elements to receive also on the passive side to enable the fastest possible switchover router(cfg-elp-prot[elp_example_ptop])# passive-if-mode up rx-both When a 8600 network element connects point-to-point to a third party network element supporting Ethernet link aggregation over two interfaces, it is configured as in the above examples 76.8600-50133K © 2015 Coriant 8600 Smart Routers Ethernet Configuration Guide 195 17 Ethernet Link Protection CLI Configuration Examples 17.2 Ethernet Switched Network Connection This example depicts how ELP is configured to protect a connection between a 8600 network element and an Ethernet switched network The network configuration is illustrated in Fig 55, section Ethernet Switched Network Connection Step First create an ELP group router(config)# protection elp elp_example_eth_switched Step Add ge6/0/0 as the primary interface and ge5/0/0 as the backup interface in the ELP group router(cfg-elp-prot[elp_example_eth_switched])# primary ge6/0/0 backup ge5/0/0 Step Network element acts as the master, although it is up because l2-learning-tx-frames is enabled Thus, the passive interface is configured to the down pulse state router(cfg-elp-prot[elp_example_eth_switched])# passive-if-mode down pulse Step Enable learning frames transmission as the 8600 network element is connected to an Ethernet switched network The configuration is now ready router(cfg-elp-prot[elp_example_eth_switched])# l2-learning-tx-frames Let us assume, for the sake of illustration (e.g for traffic engineering reasons), that the ge5/0/0 interface should be active instead of interface ge6/0/0 that is selected active by default The active interface can be changed by triggering manual switchover Step Select interface ge5/0/0 as the active interface Note: This CLI command should be given only to the master network element, i.e the network element that sets the passive interface mode down That is true in this case (even though not explicitly configured) because setting the passive interface mode down is the default behavior router(cfg-elp-prot[elp_example_eth_switched])# protection manual-switchover elp elp_example_eth_switched ge5/0/0 8600 Smart Routers Ethernet Configuration Guide 196 76.8600-50133K © 2015 Coriant 18 Microwave Radio 1+1 Protection 18 Microwave Radio 1+1 Protection 8660 Smart Router and 8630 Smart Router can interoperate with the Nokia Siemens Networks (NSN) FlexiPacket Microwave system to provide equipment protection for microwave radio equipment At both ends of the radio link hop router/switch device acting as an In Door Unit (IDU) is connected directly via GE interfaces to two microwave radio devices acting as working and protecting Out Door Units (ODUs) The working and protecting ODUs are typically connected to the same physical antenna and they are configured to use the same radio channel parameters The radio path itself is not protected in this application Depending on the protection status one ODU is active and the other one is passive at both ends Two IDU topologies are supported: • Both IDUs are 8630 Smart Router or 8660 Smart Router devices • First IDU is a 8660 Smart Router or 8660 Smart Router and the second IDU is a NSN FlexiPacket Hub Ethernet switch or equivalent Both topologies operate in a similar fashion from the protection point of view However, the configuration of the ODU management connections is different Microwave radio 1+1 protected systems have the following properties: • All the services such as IPv4 routing and MPLS supported over ELP prior to 8600 FP3.1 are supported also with microwave radio 1+1 protection Ethernet switching and IRB are not supported Protected user plane traffic is typically placed to VLAN to enable traffic management capabilities in the ODU • The feature is supported only with 8x10/100/1000BASE-TX R2 IFM on IFC2 • Bandwidth over the radio path is typically 50 350 Mbps while the ODU is connected via a GE link to the IDU Therefore bandwidth rate limiter may need in IDU GE egress interface if the traffic is very bursty not to exceed ODUs packet buffering 76.8600-50133K © 2015 Coriant 8600 Smart Routers Ethernet Configuration Guide 197 18 Microwave Radio 1+1 Protection • The protection utilizes the existing Ethernet Link Protection (ELP) feature with some extensions Ethernet interfaces connected to the working and protecting ODUs form an ELP group The protection configuration states of the working and protecting IDUs (active/stand-by) are independent from ELP group protection configuration states (primary/backup) Similarly the protection activity state of an ELP group (active/passive) and the protection activity state of an ODU pair are independent • In the egress direction the ELP group replicates the traffic sent to the ELP group to both Ethernet interfaces In the ingress direction the ELP group merges all the frames from both Ethernet interfaces The ODU is responsible to drop traffic on the passive side • As an extension to ELP, it is possible to configure unprotected VLANs to both the working and protecting Ethernet interfaces in the ELP group Unprotected VLANs can be used in the same way as a regular VLAN in a regular unprotected Ethernet interface The application requires three unprotected VLANs per Ethernet interface: • Management VLAN — ODUs have an IP host for network management purposes An unprotected VLAN shall be configured to each near-end IDU to reach the ODU IP host In this application the ODU is always managed via the Ethernet interface, not via the radio interface even it is technically possible VLAN and subnet planning shall ensure this topology • ODU-IDU monitoring — Primary and backup ODU-IDU physical Ethernet links are monitored using Ethernet OAM CCM monitoring for fast failure detection Independent Maintenance Associations (E-CCM) are used for both links and dedicated unprotected monitoring VLAN is associated to Maintenance Associations The usage of the CCM organization specific TLV (nsn-mwr-tlv) shall be enabled before the CCM session can be up • ODU-ODU monitoring — Primary and backup IDUs monitor mutually their faults and protection states An Independent Maintenance Association (P-CCM) is used between the ODUs and a dedicated unprotected monitoring VLAN is associated to the Maintenance Association The unprotected VLAN interface is created to both the primary and backup Ethernet interface in the IDU and they are bridged together providing a transparent VLAN-based communication channel for the ODU-ODU Maintenance Association Fig 58 Microwave Radio 1+1 Protection 8600 Network Element at Both Ends 8600 Smart Routers Ethernet Configuration Guide 198 76.8600-50133K © 2015 Coriant 18 Microwave Radio 1+1 Protection Fig 59 Microwave Radio 1+1 Protection 8600 and NSN at Each End 76.8600-50133K © 2015 Coriant 8600 Smart Routers Ethernet Configuration Guide 199 19 Configuring Microwave 1+1 Protection in an ELP Group 19 Configuring Microwave 1+1 Protection in an ELP Group This section provides CLI configuration examples of microwave radio 1+1 protection The examples focus only on the configuration of the 8600 equipment Fig 60 Microwave Radio 1+1 Protection Example The following list includes some general guidelines and restrictions concerning ELP and microwave radio 1+1 protection configuration which need to be take into consideration: • Microwave radio 1+1 protection cannot be configured on the last physical interface of the IFM (interface #7) • Manual switchover operation is not allowed for microwave radio 1+1 protection ELP active/passive status information is not relevant because both the working and protecting sides are always active • The backup interface may not have VLAN sub-interfaces or connections at the time of addition to an ELP group • The interfaces of an ELP group must reside on different IFC line cards 8600 Smart Routers Ethernet Configuration Guide 200 76.8600-50133K © 2015 Coriant 19 Configuring Microwave 1+1 Protection in an ELP Group • The interfaces of an ELP group must have the same interface position on their IFC line cards, e.g both are upmost interfaces • An IFC may have common ELP groups only with one IFC line card In practise this means that IFC line cards work in pairs protecting each other • Microwave radio 1+1 protection cannot be configured on an IFM if ELP is already enabled on the last physical interface of the same IFM • ELP cannot be configured on the last physical interface (interface #7) of the IFM if microwave radio 1+1 protection is already configured on the same IFM • Microwave radio 1+1 protection and ELP cannot be configured on the same physical interfaces • If an interface already belongs to a LAG group, then ELP and microwave radio 1+1 protection cannot be configured on that interface • The maximum number of unprotected VLANs that can be created in a group is even the application requires only Configuring the [IEEE 802.1ag] Ethernet OAM monitoring parameters in the microwave radio 1+1 protection application is driven by the used ODU device The following examples recommend typical values but the final values may vary depending on the ODU product variant and release and need to be verified with ODU vendor 19.1 Create ELP Protection Group This example shows how an ELP protection group is created for microwave radio 1+1 protection Step Create first an ELP group router-IDU1(config)# protection elp elp_example Step Add interface ge8/1/6 as the primary and interface ge6/1/6 as the backup interface to the ELP group The ELP group is configured to transmit and receive mode VLANID values used for three unprotected VLANs are allocated for the primary and backup side using a single CLI command router-IDU1(cfg-elp-prot[elp_example])# primary ge8/1/6 backup ge6/1/6 plus rx-tx-both router-IDU1(cfg-elp-prot[elp_example])# unprotected-vlans 10 16 100 19.2 Create ODU Management VLAN This example shows how ODU management VLAN is configured Both near-end ODUs are managed via unprotected VLAN in the primary and backup interfaces ODUs shall be configured to different sub-nets Note that a different sub-netting scheme is used in 8600–8600 and 8600–3rd party topologies 76.8600-50133K © 2015 Coriant 8600 Smart Routers Ethernet Configuration Guide 201 19 Configuring Microwave 1+1 Protection in an ELP Group Step Create ODU management VLAN to the primary interface of the ELP group by issuing a sub-interface configuration mode CLI command The VLANID used in this CLI command shall be configured as unprotected in the previous step The CLI command in this example creates a VLAN with the VLAN identifier value of 100 (assuming a VLAN with this VLAN tag value does not already exist on the main interface) and puts the command prompt into the VLAN sub-interface configuration mode If a VLAN with a given VLAN identifier already exists, the sub-interface configuration mode is entered The VLAN sub-interface can be configured now router-IDU1> enable router-IDU1# config terminal router-IDU1(config)# interface ge 8/1/6 router-IDU1(cfg-if[ge8/1/6]# interface ge 8/1/6.100 router-IDU1(cfg-if[ge8/1/6.100]# Step Configure IP address for the management VLAN for the primary interface of the ELP group Primary ODU is configured to this sub-net as well Activate the interface with the no shutdown CLI command router-IDU1(cfg-if[ge8/1/6.100]# ip address 192.168.1.1/24 router-IDU1(cfg-if[ge8/1/6.100]# no shutdown Step Create ODU management VLAN to the backup interface of the ELP group The VLANID used in this CLI command shall be configured as unprotected in the previous step router-IDU1(config)# interface ge 6/1/6 router-IDU1(cfg-if[ge6/1/6]# interface ge 6/1/6.100 router-IDU1(cfg-if[ge6/1/6.100]# Step Configure management VLAN IP address for the backup interface of the ELP group Secondary ODU is configured to this sub-net as well Activate the interface with the no shutdown CLI command router-IDU1(cfg-if[ge6/1/6.100]# ip address 192.168.2.1/24 router-IDU1(cfg-if[ge6/1/6.100]# no shutdown 19.3 Create IDU-ODU Monitoring VLAN This example shows how [IEEE 802.1ag] Ethernet OAM CCM monitoring is configured Configuration shall be fully in-line with the ODU configuration to get CCM connection up Step Configure maintenance domain parameters for the ELP group This configuration is common for both the primary and secondary E-CCM connection Define at node IDU1 maintenance domain (MD) with name (domain_1) and maintenance domain level (MD level) ID (0) ’md-name’ is the Maintenance Domain keyword used to construct the MA ID that is signaled over the network For interoperability reasons it is recommended to use MD level=0 and MD name=none router-IDU1(config)# eth cfm md domain_1 level md-name none Step Configure maintenance associations for monitoring VLAN (E-CCM) in the primary interface Define the maintenance association name, short name and CCM interval In Microwave 1+1 Protection application 10ms is the only available option For interoperability reasons it is recommended to use digit integer as short-name, different than backup one router-IDU1(config)# eth cfm md domain_1 ma ma_1 short-name integer 1105 ccm interval 10ms 8600 Smart Routers Ethernet Configuration Guide 202 76.8600-50133K © 2015 Coriant 19 Configuring Microwave 1+1 Protection in an ELP Group Step Create monitoring VLAN to the primary interface of the ELP group by issuing a sub-interface configuration mode CLI command the VLANID used in this CLI command shall be configured as unprotected under the ELP group For interoperability reasons it is recommended to use VLANID range [1 15] Configure maintenance association endpoint for primary monitoring VLAN Bind a local down MEP to VLAN 10 on ge 8/1/6 interface and enable nsn-prot-state-tlv For interoperability reasons it is recommended to configure local MEP=1 Bind a remote MEP to VLAN 10 on ge 8/1/6 interface and enable nsn-prot-state-tlv For interoperability reasons it is recommended to configure remote MEP ID=2 Activate the interface with the no shutdown CLI command router-IDU1(cfg-if[ge8/1/6])# interface ge 8/1/6.10 router-IDU1(cfg-if[ge8/1/6.10]# eth cfm ma ma_1 mep local mep_1 down ccm send nsn-prot-state-tlv router-IDU1(cfg-if[ge8/1/6.10]# eth cfm ma ma_1 mep remote nsn-prot-state-tlv router-IDU1(cfg-if[ge8/1/6.10]# no shutdown Step Configure maintenance associations for monitoring VLAN (E-CCM) in the backup interface Define the maintenance association name, short name and CCM interval In the microwave radio 1+1 protection application the only available option is 10ms For interoperability reasons it is recommended to use digit integer as the short name, different from the primary one router-IDU1(config)# eth cfm md domain_1 ma ma_2 short-name integer 1106 ccm interval 10ms Step Create monitoring VLAN to backup interface of the ELP group by issuing a sub-interface configuration mode CLI command The VLANID used in this CLI command shall be configured as unprotected under ELP group It is recommended to use VLANID range [1 15] Configure maintenance association end point for backup monitoring VLAN Bind a local down MEP to VLAN 10 on ge 6/1/6 interface and enable nsn-prot-state-tlv For interoperability reasons it is recommended to configure local MEP=1 Bind a remote MEP to VLAN 10 on ge 6/1/6 interface and enable nsn-prot-state-tlv For interoperability reasons it is recommended to configure remote MEP ID=2 Activate the interface with the no shutdown CLI command router-IDU1(cfg-if[ge6/1/6])# interface ge 6/1/6.10 router-IDU1(cfg-if[ge6/1/6.10]# eth cfm ma ma_2 mep local mep_1 down ccm send nsn-prot-state-tlv router-IDU1(cfg-if[ge6/1/6.10]# eth cfm ma ma_2 mep remote nsn-prot-state-tlv router-IDU1(cfg-if[ge6/1/6.10]# no shutdown 19.4 Create ODU-ODU Monitoring VLAN This example shows how the ODU-ODU monitoring VLAN connection needed between a primary and secondary ODU is configured Note that no Ethernet OAM configuration is done for this VLAN on the IDU side Step Create the pseudowire circuit instance mwrp_bridge with ID 1000 router-IDU1(config)# pwe3 circuit mwrp_bridge 1000 mpls manual Step Configure VLAN with VLAN identifier value 16 as the ODU-ODU monitoring VLAN to the Ethernet interface in the primary interface of the ELP group The VLANID used in this CLI command shall be configured as unprotected under the ELP group For interoperability reasons it is recommended to use VLANID range [16 50] 76.8600-50133K © 2015 Coriant 8600 Smart Routers Ethernet Configuration Guide 203 19 Configuring Microwave 1+1 Protection in an ELP Group Attach the pseudowire to the interface Activate the interface with the no shutdown CLI command router-IDU1(cfg-if[ge8/1/6]# interface ge8/1/6.16 router-IDU1(cfg-if[ge8/1/6.16]# pwe3 circuit mwrp_bridge router-IDU1(cfg-if[ge8/1/6.16]# no shutdown Step Configure VLAN with VLAN identifier value 16 as the ODU-ODU monitoring VLAN to the Ethernet interface in the backup interface of the ELP group The VLANID used in this CLI command shall be configured as unprotected under the ELP group For interoperability reasons it is recommended to use VLANID range [16 50] Attach the pseudowire to the interface Activate the interface with the no shutdown CLI command router-IDU1(cfg-if[ge6/1/6]# interface ge6/1/6.16 router-IDU1(cfg-if[ge6/1/6.16]# pwe3 circuit mwrp_bridge router-IDU1(cfg-if[ge6/1/6.16]# no shutdown Step Set the bridge between the created VLANs in the primary and secondary interface in both directions of the first PWE3 circuit created router-IDU1(config)# mpls static-ftn bridge mwrp_bridge ge8/1/6.16 ge6/1/6.16 router-IDU1(config)# mpls static-ftn bridge mwrp_bridge ge6/1/6.16 ge8/1/6.16 19.5 Configure Egress Rate Limiter If the traffic is very bursty, it may be necessary to enable an egress rate limiter in the 8600 egress interface to avoid packet drops in the ODU packet buffer This example shows how the rate limiter is configured to primary interface ge8/1/6 and backup interface ge 6/1/6 Step Set the limiter for all interfaces on the IFM using the same CLI command router-IDU1(config)# eth bandwidth rate-limit module 8/1 limits max max max max max max 350 max Step Set the limiter for all interfaces on the IFM using the same CLI command router-IDU1(config)# eth bandwidth rate-limit module 6/1 limits max max max max max max 350 max 19.6 Create Protected User VLANs to ELP Group This example shows how two protected user VLANs are configured to an ELP group These VLANs are used as MPLS and IP trunks for user end-to-end traffic Step Create two user VLANIDs 200 and 300 to the primary interface of the ELP group When VLAN is configured to the primary interface, it will be protected router-IDU1(config)# interface ge 8/1/6 router-IDU1(cfg-if[ge8/1/6]# interface ge 8/1/6.200 router-IDU1(cfg-if[ge8/1/6.200]# interface ge 8/1/6.300 router-IDU1(cfg-if[ge8/1/6.300]# Step Configure VLAN IP address for VLANID=300 Activate the interface with the no shutdown CLI command 8600 Smart Routers Ethernet Configuration Guide 204 76.8600-50133K © 2015 Coriant 19 Configuring Microwave 1+1 Protection in an ELP Group router-IDU1(cfg-if[ge8/1/6.300]# ip address 192.168.100.1/24 router-IDU1(cfg-if[ge8/1/6.300]# no shutdown Step Configure VLAN IP address for VLANID=200 Activate the interface with the no shutdown CLI command router-IDU1(cfg-if[ge8/1/6.300]# interface ge 8/1/6.200 router-IDU1(cfg-if[ge8/1/6.200]# ip address 192.168.101.1/24 router-IDU1(cfg-if[ge8/1/6.200]# no shutdown 76.8600-50133K © 2015 Coriant 8600 Smart Routers Ethernet Configuration Guide 205 20 CPU Packet Storm Control 20 CPU Packet Storm Control To ensure proper operation, the Central Processing Units (CPUs) of the network element need to be protected against an excess of received Ethernet control traffic, a storm Such a storm may happen as a result of misconfigurations in the network, e.g a loop in L2 network, a broken or misbehaving network element, or an attack 8615 Smart Router, 8630 Smart Router, 8660 Smart Router, and 8665 Smart Router monitor received control traffic targeted to CPUs, and when incoming L2 control packet rate of a single line card exceeds about 30k – 40k of 256 B fragments (or frames in IFCs) per second, a storm is declared to be ongoing When the storm has been active for at least 10 seconds, the NE will detect an offending incoming VLAN(s) and blocks it to prevent the CPU from overloading An alarm will be raised to indicate blocked sub-interfaces Blocked VLAN(s) will be reactivated after 10 seconds of blocking If the storm is still active, VLAN(s) will be blocked again Faults are cleared when a storm has not been detected in 20 seconds after the reactivation of VLAN(s) IFC line cards will block only L2 multicast and broadcast traffic while ELC1 line card, 8615 Smart Router, and 8665 Smart Router will block all the traffic of the offending VLAN interface When a storm is detected in a port level interface (untagged) all supported products will block all untagged traffic 8600 Smart Routers Ethernet Configuration Guide 206 76.8600-50133K © 2015 Coriant ... fi-documentation@tellabs.com 76. 8600- 50133K © 2015 Coriant 8600 Smart Routers Ethernet Configuration Guide 21 8600 Smart Routers Discontinued Products 8600 Smart Routers Discontinued Products 8600 Smart Routers Manufacture... Networking > 8600 Smart Routers > Technical Documentation 76. 8600- 50133K © 2015 Coriant 8600 Smart Routers Ethernet Configuration Guide 17 About This Manual Document Title Description 8600 Smart Routers. .. interface is referred to as primary interface 8600 Smart Routers Ethernet Configuration Guide 8600 Smart Routers Ethernet Configuration Guide 10 76. 8600- 50133K © 2015 Coriant Table of Contents Table