76 8600 50118i 8600 smart routers equipment management configuration guide

8600 Smart Routers Equipment Management Configuration Guide 76.8600-50118I 02.06.2015 Document Information Revision History Document No Date Description of Changes 76.8600-50118I 02.06.2015 8665 Smart Router data added 8615 Smart Router stacked data added Root user added to 1.1 User Authentication Information about replacing an IFC1 line card when part of and MSP1+1 protection group added to 3.4 Replacing Cards 76.8600-50118H 22.10.2014 8602 Smart Router and 8615 Smart Router data added CDC1-CDC2 upgrade instructions updated in chapter 3.5.2 Upgrading CDC1 to CDC2 76.8600-50118G 12.03.2014 Related documentation updated in 8600 Smart Routers Technical Documentation Updates on 8609 Smart Router and 8611 Smart Router hot insertion line module to 3.6 Adding and Removing Interface Modules (IFM), Line Modules (LM) and High Speed Modules (HM) CDC1-CDC2 upgrade instructions updated in chapter 3.5.2 Upgrading CDC1 to CDC2 Footnote added about the range of characters allowed in ‘username’ CLI command in chapter User Management Appendix Troubleshooting Equipment Management Problems added 8600 Smart Routers Equipment Management Configuration Guide 76.8600-50118I © 2015 Coriant 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 is in use, 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 The functionality described in this document for 8615 Smart Router is also applicable to 8615 Smart Router stacked, unless otherwise stated © 2015 Coriant 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 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 76.8600-50118I © 2015 Coriant 8600 Smart Routers Equipment Management Configuration Guide 8600 Smart Routers Equipment Management Configuration Guide 76.8600-50118I © 2015 Coriant Document Information Terms and Abbreviations Term Explanation BFD Bidirectional Forwarding Detection BGP-4 Border Gateway Protocol version BMI Broadband Management Interface BMP Broadband Management Protocol A communication protocol which is used between 8600 Smart Routers and 8000 Intelligent Network Manager CDC Control and DC Power Card (used in 8630 Smart Router and 8660 Smart Router) CLI Command Line Interface 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) In 8000 Intelligent Network Manager and CLI referred to as unit 76.8600-50118I © 2015 Coriant CU Control functionality (used in 8615 Smart Router and 8665 Smart Router) ELC1 Ethernet Line Card (used in 8630 Smart Router and 8660 Smart Router) ESW Embedded Software FE Fast Ethernet FP Feature Pack FTP File Transfer Protocol GE Gigabit Ethernet HM High Speed Module (used in 8611 Smart Router) HW Hardware 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) 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) IP Internet Protocol IS-IS Intermediate System to Intermediate System (Interior Gateway Protocol) LDP Label Distribution Protocol 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) In 8000 Intelligent Network Manager and CLI referred to as unit Line Unit The line unit in the 8665 Smart Router is the basic building block for the element One line unit contains always the traffic functionality (LU) and, optionally, the control functionality (CU) LM Line module (used in 8607 Smart Router, 8609 Smart Router and 8611 Smart Router) 8600 Smart Routers Equipment Management Configuration Guide Document Information LU Traffic functionality (used in 8615 Smart Router and 8665 Smart Router) LU1 Line Unit in 8665 Smart Router MAC Media Access Control Sublayer of Data Link Layer MFE Management Fast Ethernet MPLS Multiprotocol Label Switching MSP Multiplex Section Protection NE Network Element OSPF Open Shortest Path First PBR Packet Buffer RAM PBRF Packet Buffer RAM Failure PKG Software package file RADIUS Remote Authentication Dial-In User Service Commonly used to provide centralized authentication, authorization, and accounting functionalities RSVP-TE Resource Reservation Protocol – Traffic Engineering SCM Switching and Control Module (used in 8611 Smart Router) SDH Synchronous Digital Hierarchy SEC Synchronous Equipment Clock SNMP Simple Network Management Protocol STM Synchronous Transfer Mode SU1 Switch Unit (used in 8665 Smart Router) SW Software Unit In CLI refers to a card VRRP Virtual Router Redundancy Protocol 8600 Smart Routers Equipment Management Configuration Guide 76.8600-50118I © 2015 Coriant Table of Contents Table of Contents About This Manual 11 Objectives 11 Audience 11 8600 Smart Routers Technical Documentation 11 Interface Numbering Conventions 15 Document Conventions 15 Documentation Feedback 15 8600 Smart Routers Discontinued Products 16 User Management 17 1.1 1.2 1.3 User Authentication 17 Forgotten Password 17 User Management CLI Configuration Examples 18 1.3.1 Creating Superuser Account and Enabling User Authentication 18 1.3.2 Disabling User Authentication and Deleting Superuser Account 18 1.3.3 Changing User Password 18 1.3.4 Displaying Configured User List 19 1.3.5 Displaying Logged-in Users 19 1.3.6 Displaying User Account Activity 19 Interface Numbering and Legal IF Modules 20 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 2.10 2.11 76.8600-50118I © 2015 Coriant 8602 Smart Router IF Numbering 20 8605 Smart Router IF Numbering 20 8607 Smart Router IF Numbering 21 8609 Smart Router IF Numbering 21 8611 Smart Router IF Numbering 22 8615 Smart Router IF Numbering 22 8615 Smart Router Stacked IF Numbering 23 8620 Smart Router IF Numbering 23 8630 Smart Router IF Numbering 24 8660 Smart Router IF Numbering 25 8665 Smart Router IF Numbering 26 8600 Smart Routers Equipment Management Configuration Guide Table of Contents HW Inventory 28 3.1 3.2 3.3 3.4 3.5 ETSI/ANSI/DSL Mode Configuration in HW Inventory 29 Creating and Deleting HW Inventory 29 Adding and Removing Cards 30 Replacing Cards 31 Upgrading Line and Control Cards in 8630 Smart Router and 8660 Smart Router 32 3.5.1 Upgrading IFC1 to IFC2 33 3.5.2 Upgrading CDC1 to CDC2 33 3.6 Adding and Removing Interface Modules (IFM), Line Modules (LM) and High Speed Modules (HM) 36 3.6.1 Changing an Existing Module or Installing a New Module 37 3.6.2 Removing a Module 38 3.7 Upgrading Modules 39 3.8 Control Functionality (CU) in 8615 Smart Router and 8665 Smart Router 40 3.8.1 Dependencies between Control Functionality (CU) and Traffic Functionality (LU) 41 3.9 8665 Smart Router Inventory 41 3.10 8615 Smart Router Stacked Inventory 42 HW Inventory CLI Configuration Procedures 43 4.1 4.2 4.3 4.4 4.5 4.6 First Installation 43 Line Unit, Control Functionality, Control Card, SCM 44 4.2.1 Adding a Control Card, SCM to HW Inventory 44 4.2.2 Removing a Control Card, SCM from HW Inventory 44 4.2.3 Replacing a Control Card with an Older HW Version 45 Changing Interface Module or ETSI/ANSI/DSL Mode 45 Line Module 46 4.4.1 Adding a Line Module to HW Inventory 46 4.4.2 Removing a Line Module from HW Inventory 47 4.4.3 Replacing a Line Module 47 High Speed Module 49 4.5.1 Adding a High Speed Module to HW Inventory 49 4.5.2 Removing a High Speed Module from HW Inventory 50 4.5.3 Replacing a High Speed Module 50 8615 Smart Router Stacked 52 4.6.1 Creating 8615 Smart Router Stacked 52 4.6.2 Removing 8615 Smart Router Stacked 52 4.6.3 Replacing One of the Members in an 8615 Smart Router Stacked 53 4.6.4 Replacing 8615 Smart Router Stacking Cable 54 4.6.5 Operational Notes for 8615 Smart Router Stacked 55 Software Management 56 5.1 5.2 5.3 5.4 5.5 Software Packages 56 5.1.1 Software Package Types in 8660 Smart Router and 8630 Smart Router 56 Configuring Expected Application ESW to Be Used at Next Reset 57 Expected Software and Automatic Software Loader 58 ESW Shutdown before Removing Card(s) or Switching NE Power off 59 Software Management CLI Configuration Procedures 60 5.5.1 Taking Application ESW into Use in the NE 60 8600 Smart Routers Equipment Management Configuration Guide 76.8600-50118I © 2015 Coriant Table of Contents 5.5.2 CDC 1+1 Equipment Protection 63 6.1 6.2 6.3 6.4 6.5 Using Configuration Backup and Restore 62 Overview 63 Protected Hardware 63 6.2.1 Power Supply Protection 63 6.2.2 Management Fast Ethernet Protection 64 6.2.3 CDC Node Clock Protection 64 6.2.4 References 64 Protected Software-Level Functionality 65 6.3.1 Management Interfaces 65 6.3.2 Backup of Configuration Data 65 6.3.3 Protection of IP and MPLS Protocols 65 6.3.4 References 66 Usage Guidelines 66 6.4.1 Manual CDC Protection Switchover 66 6.4.2 Automatic CDC Protection Switchover 67 6.4.3 Non-Service Affecting Software Upgrade 67 CDC Protection CLI Configuration Examples 67 6.5.1 CDC Protection Information 67 6.5.2 Manual CDC Protection Switchover 67 SCM 1+1 Equipment Protection 69 7.1 Overview 69 7.1.1 Manual SCM Protection Switchover 69 7.1.2 Automatic SCM Protection Switchover 70 7.2 Forwarding Functions and Protocols 70 7.3 Signaling Functions and Protocols 70 7.3.1 References 71 7.4 Management Functions, Protocols, and Interfaces 72 7.4.1 Management Ethernet Port Protection 72 7.4.2 Console Port Protection 72 7.4.3 Management Functions 72 7.5 System Alarm Interfaces 73 7.6 System Status Indicators 73 7.7 Station Clock Interfaces 74 7.8 Backup of Configuration Data 74 7.9 Non-Service Affecting Software Upgrade 74 7.10 SCM Protection CLI Configuration Examples 75 7.10.1 SCM Protection Information 75 7.10.2 Manual SCM Protection Switchover 75 CU 1+1 Equipment Protection 76 8.1 8.2 76.8600-50118I © 2015 Coriant Overview 76 Protected Software-Level Functionality 76 8600 Smart Routers Equipment Management Configuration Guide Table of Contents 8.3 8.4 8.2.1 Management Interfaces 76 8.2.2 Backup of Configuration Data 76 8.2.3 Protection of IP and MPLS Protocols 77 8.2.4 References 78 Usage Guidelines 78 8.3.1 Manual CU Protection Switchover 78 8.3.2 Automatic CU Protection Switchover 78 8.3.3 Non-Service Affecting Software Upgrade 78 CU Protection CLI Configuration Examples 79 8.4.1 CU Protection Information 79 8.4.2 Manual CU Protection Switchover 79 SU Equipment Protection 80 9.1 9.2 9.3 9.4 Overview 80 Functional Model 80 9.2.1 Unicast Traffic 80 9.2.2 Multicast Traffic 82 Usage Guidelines 83 9.3.1 Hitless SU Upgrade Procedure 83 SU Protection CLI Configuration Examples 83 9.4.1 SU Protection Information 84 9.4.2 Forced SU Protection Switchover 84 Troubleshooting Equipment Management Problems 85 Backplane Communication Health Check in 8630 Smart Router and 8660 Smart Router 85 HW Inventory Health Check 86 Checklist for Resolving ESW Incompatibility Issues 88 8600 Smart Routers Equipment Management Configuration Guide 10 76.8600-50118I © 2015 Coriant SCM 1+1 Equipment Protection Indicators in Passive SCM 7.7 LED Name Color States Local Alarm RED BLINKING during the following operations: 1) Command induced verification of Local Alarm LED operation 2) If the yellow LED is also blinking, the card/NE has reached shutdown state after "esw-shutdown" command and can be removed from the NE or power can be switched off OFF otherwise Remote Alarm YELLOW BLINKING during the following operations: 1) Command induced verification of Remote Alarm LED operation 2) If the red LED is also blinking, the card/NE has reached shutdown state after "esw-shutdown" command and can be removed from the NE or power can be switched off OFF otherwise Ready GREEN ON indicates that SCM is operating normally BLINKING indicates command induced verification of Ready Status LED operation OFF otherwise Master GREEN BLINKING indicates command induced verification of Active Status LED operation OFF otherwise Station Clock Interfaces Each SCM supports the external station clock input (SCI) and station clock output (SCO) functionality via a balanced 120/100 Ω E1/T1 port (designated “Sync”) on an RJ-48c connector The protection of the Sync interfaces is optional but automatic if SCM 1+1 protection is configured The Sync interfaces on a hosting SCM may be selected for activity by the 8611 Smart Router synchronization / timing function(s) regardless of the active/passive status of the hosting SCM For more information on the network synchronization function in 8611 Smart Router, see 8600 Smart Routers Synchronization Configuration Guide 7.8 Backup of Configuration Data If SCM 1+1 protection is configured on the 8611 Smart Router, all configuration data of the NE is also protected This means that the SCM can be replaced with a spare SCM without losing any of the NE-level configuration data residing on the SCMs 7.9 Non-Service Affecting Software Upgrade If a NE has only one SCM, the software in the SCM can still be updated However, when a new software version is taken into use by a management CLI command and the SCM is not protected, restart in the SCM causes a service break in the whole NE The service break can last for minutes in the worst case (with a very complicated routing configuration) The use of SCM 1+1 protection in the 8611 Smart Router avoids this downfall 8600 Smart Routers Equipment Management Configuration Guide 74 76.8600-50118I © 2015 Coriant SCM 1+1 Equipment Protection When SCM protection is in use, the standard procedure for the SCM software upgrade is as follows The detailed instructions can be found in 8611 Smart Router ESW Release Notes Step Download and activate a software package Do not restart Step Switch to the protecting SCM in slot Step Restart the working SCM in slot Step Wait until the working SCM in slot is up and running again Step Switch to SCM in slot which now has the updated software Step Restart the protecting SCM in slot Step Wait until the protecting SCM in slot is up and running again 7.10 SCM Protection CLI Configuration Examples This chapter provides SCM protection CLI configuration examples 7.10.1 SCM Protection Information Step Show the module protection information when SCM protection is enabled router# show protection unit scm 7.10.2 Manual SCM Protection Switchover Step Turn the protection switch to the protecting SCM router# protection manual-switchover unit scm slot 76.8600-50118I © 2015 Coriant 8600 Smart Routers Equipment Management Configuration Guide 75 CU 1+1 Equipment Protection CU 1+1 Equipment Protection 8.1 Overview 8665 Smart Router and 8615 Smart Router stacked support the protection of important NE-level functionalities via the protected CU pair If there is a CU running in both logical slots and 14 and if both of them are members of the NE inventory, protection is automatically on The CU 1+1 protection features are: • SEC/S3 node clock protection • Non-volatile configuration backup • Various IP routing and MPLS switching protocols • Non-service affecting software upgrades in CUs 8665 Smart Router and 8615 Smart Router stacked can operate in non-protected mode with only a single CU In non-protected operation, the only CU in the NE is placed in slot 14 and is a member of the NE inventory In non-protected mode, the system capabilities listed above will no longer be protected nor possible 8665 Smart Router and 8615 Smart Router LU1 not have a dedicated MFE (Management Fast Ethernet) port, instead any available Ethernet port can be used as management interface If this port needs to be protected in 8665 Smart Router and 8615 Smart Router stacked, ELP should be used to protect it 8.2 8.2.1 Protected Software-Level Functionality Management Interfaces If the protected CU pair is used, the management agents (BMI, CLI and SNMP) of 8665 Smart Router and 8615 Smart Router stacked are protected and reachable even though one of the CU would fail During protection switchover BMP messages may disappear although 8000 Intelligent Network Manager re-establishes management communication automatically On the other hand, CLI sessions are disconnected at switchover and the user has to re-establish them manually 8.2.2 Backup of Configuration Data If the protected CU pair is running in the NE, all configuration data of 8665 Smart Router and 8615 Smart Router stacked is also protected This means that also the LU1 where the CU is running can be replaced with a spare unit without losing NE-level configuration data residing on the CUs 8600 Smart Routers Equipment Management Configuration Guide 76 76.8600-50118I © 2015 Coriant CU 1+1 Equipment Protection 8.2.3 Protection of IP and MPLS Protocols If the CU is protected, both CUs are capable of running the same IP and MPLS protocols If there is a protection switchover, the CU that turns active attempts to maintain the state of the routing and signaling protocols so that the forwarding activity in the NE is not disturbed How this is achieved depends on the protocols that are used in the network The following list names all supported IP and MPLS protocols and the type of equipment protection supported • BFD • Method of protection: Internal protection of BFD protocol in NE • No limitations • BGP-4 • Method of protection: Graceful restart mechanism for BGP [draft-ietf-idr-restart] and Graceful restart mechanism for BGP with MPLS [RFC4781] • Limitations: BGP-4 neighbors of the NE in the network must support graceful restart for BGP • IS-IS • Method of protection: Restart signaling for IS-IS [RFC3847] • Limitations: IS-IS neighbors of the NE in the network must support restart signaling • LDP • Method of protection: Graceful restart mechanism for LDP [RFC3478] • Limitations: LDP neighbors of the NE in the network must support graceful restart for LDP • OSPF • Method of protection: Graceful OSPF restart [RFC3623] • Limitations: OSPF neighbors of the NE in the network must support graceful OSPF restart • RSVP-TE • Method of protection: Internal protection of RSVP-TE protocol in NE • No limitations • VRRP • Method of protection: Internal protection of VRRP protocol in NE • No limitations All protocols are independent of each other with respect to equipment protection If, for example, BGP graceful restart fails for whatever reason, OSPF graceful restart may still succeed; as a result, the OSPF routes are applied in the forwarding plane without interruptions but the BGP routes disappear temporarily until the normal BGP recovery repairs the BGP routes, too As the limitations listed above indicate, it is possible that smooth protection switchover fails for various reasons for one or more protocols In that case the NE recovers as any normal router after a temporary failure Even if smooth switchover failed for all protocols in use and even if the other CU suffered from a temporary failure only, having protected CUs is useful because protocol restart is always remarkably faster if another CU is ready at the time of a failure of the other CU than if the NE were equipped with a single CU only 76.8600-50118I © 2015 Coriant 8600 Smart Routers Equipment Management Configuration Guide 77 CU 1+1 Equipment Protection 8.2.4 8.3 8.3.1 References Feature Description [draft-ietf-idr-restart] draft-ietf-idr-restart-13.txt (2006-07), Graceful restart mechanism for BGP [RFC3478] RFC3478 (2003-02), Graceful restart mechanism for label distribution protocol [RFC3623] RFC3623 (2003-11), Graceful OSPF restart [RFC3847] RFC3847 (2004-07), Restart signaling for IS-IS [RFC4781] RFC4781 (2007-01), Graceful restart mechanism for BGP with MPLS Usage Guidelines Manual CU Protection Switchover Manual switchover is performed by the user to change the active CU side Protection switchover is possible when both CUs are in equal protection states Factors that affect the CU protection states are the start-up permission of the card, faults in the NE, software types being run and the presence of the card Manual switchover should not be needlessly used, as it may temporarily disturb the routing functionality and management connections The state of the manual switchover is not permanent, an automatic protection switchover will override the state set by manual protection switchover 8.3.2 Automatic CU Protection Switchover If the protection state of the active CU is degraded and the state of the other CU is not, the result is an immediate protection switchover to the other CU The automatic protection switchover is non-revertive, i.e if protection state degradation disappears, a new switchover will not take place automatically 8.3.3 Non-Service Affecting Software Upgrade If a NE has only one CU, the ESW in the CU can still be updated However, when a new software version is taken into use by a management CLI command and the CU is not protected, restart in the CU causes a service break in the whole NE The service break can last for minutes in the worst case (with a very complicated routing configuration) The use of CU 1+1 protection in 8665 Smart Router and 8615 Smart Router stacked avoids this downfall When CU protection is in use, the standard procedure for the CU software upgrade is as follows The detailed instructions can be found in 8600 Smart Routers ESW Release Notes 8600 Smart Routers Equipment Management Configuration Guide 78 76.8600-50118I © 2015 Coriant CU 1+1 Equipment Protection After the new SW package has been downloaded and the control functionality is rebooted, the whole line unit will reboot Step Download and activate a software package Do not restart Step Switch to the protecting CU in slot Step Restart the working CU in slot 14 Step Wait until the working CU in slot 14 is up and running again Step Switch to the CU in slot 14 which now has the updated ESW Step Restart the protecting CU in slot Step Wait until the protecting CU in slot is up and running again Step Update the protected line cards in the similar manner as the CU cards above Step Restart the unprotected line cards 8.4 CU Protection CLI Configuration Examples This chapter provides CU protection CLI configuration examples 8.4.1 CU Protection Information Step Show the card protection information when CU protection is enabled router# show protection unit cdc 8.4.2 Manual CU Protection Switchover Step Turn the protection switch to the protecting CU router# protection manual-switchover unit cdc slot 76.8600-50118I © 2015 Coriant 8600 Smart Routers Equipment Management Configuration Guide 79 SU Equipment Protection SU Equipment Protection 9.1 Overview 8665 Smart Router supports the protection of the switching fabric via the protected SU pair If there is an SU in both slots and slot and if both of them are members of the NE hardware inventory, protection is automatically on The protected system capabilities supported by SU equipment protection are as follows: • User data traffic • Control traffic, such as LDP and BGP • 8665 Smart Router internal control traffic Under normal operation, both SUs are active and the traffic is distributed over the two SUs as discussed in 9.2.1 Unicast Traffic and 9.2.2 Multicast Traffic If one of the SUs fails, all the traffic is automatically switched to the normally operating SU The SU protection is revertive, that is, when the failed SU becomes operational again, the traffic that was flowing via the SU prior to the failure is automatically switched back 8665 Smart Router can operate in non-protected mode with only a single SU in operation In non-protected mode, the system capabilities listed above will no longer be protected / possible 9.2 9.2.1 Functional Model Unicast Traffic When both SUs are operational, the ingress line unit (LU1) selects the SU for unicast traffic based both on the egress LU1 and the outgoing port, as illustrated in Fig 13 The ports are associated with the SUs based on the port capacities, so that the traffic load distribution to the SUs is as even as possible 8600 Smart Routers Equipment Management Configuration Guide 80 76.8600-50118I © 2015 Coriant SU Equipment Protection Fig 13 Unicast Traffic Distribution to the SUs If one of the SUs fails, the traffic going through the failed SU is switched to the remaining operational SU, as shown in Fig 14 The switchover decisions are made independently by each LU1 to ensure fast protection The switchover will be triggered, for instance, by loss of connectivity to the SU (i.e backplane link down), SU service affecting faults or loss of connectivity to the egress LU1s, as reported by the internal monitoring protocol that runs between each pair of LU1s via both SUs Fig 14 Unicast Traffic Protection Switchover Between Two SUs 76.8600-50118I © 2015 Coriant 8600 Smart Routers Equipment Management Configuration Guide 81 SU Equipment Protection 9.2.2 Multicast Traffic Multicast Traffic refers to all the traffic that is replicated by 8665 Smart Router, including the Ethernet switched unicast traffic that is flooded because of unknown destination MAC address In normal operation multicast traffic is distributed to the SUs based on multicast group, as illustrated in Fig 15 The SUs replicate the multicast packets to all the LU1s that have members in the multicast group The egress side LU1s further replicate the packets to all the ports/tunnels that have members in the group Fig 15 Multicast Traffic Distribution to the SUs If one of the SU fails, all the multicast traffic is switched to remaining operational SU, as shown in Fig 16 Like in the case of unicast traffic, switchover decisions are made independently by each LU1 to ensure fast reaction 8600 Smart Routers Equipment Management Configuration Guide 82 76.8600-50118I © 2015 Coriant SU Equipment Protection Fig 16 Multicast Traffic Protection Switchover Between SUs 9.3 Usage Guidelines 9.3.1 9.4 Hitless SU Upgrade Procedure Step Download and activate a software package Do not restart Step Switch all traffic from the SU that is to be upgraded first, for instance the SU in slot 7, to the SU in slot Step Restart the working SU in slot Step Wait until the SU in slot is up and running again Step Switch all the traffic from slot to slot 7, which now has the updated ESW Step Restart the SU in slot Step Wait until the SU in slot is up and running again Step Clear the traffic forcing to slot Now both SUs are in use again Step Restart the unprotected line cards SU Protection CLI Configuration Examples This chapter provides SU protection CLI configuration examples 76.8600-50118I © 2015 Coriant 8600 Smart Routers Equipment Management Configuration Guide 83 SU Equipment Protection 9.4.1 SU Protection Information Step Show the card protection information when SU protection is enabled router# show protection unit su 9.4.2 Forced SU Protection Switchover Step Turn all taffic to the SU in slot router# protection force-switchover unit su slot 8600 Smart Routers Equipment Management Configuration Guide 84 76.8600-50118I © 2015 Coriant Troubleshooting Equipment Management Problems Troubleshooting Equipment Management Problems Backplane Communication Health Check in 8630 Smart Router and 8660 Smart Router Before creating the NE inventory or adding new cards to inventory, check the health of the cards and backplane communication Run this test always after card(s) have been removed, replaced or added to the NE It is recommended to repeat this test in case of any indeterminate behavior Faults Name Description Cause Backplane data bus A failure This fault is active if the internal data bus A between cards is not functioning correctly Typically this is an indication that the backplane contact of one or several cards is poor Backplane data bus B failure This fault is active if the internal data bus B between cards is not functioning correctly Typically this is an indication that the backplane contact of one or several cards is poor Backplane slot id reading failure This fault is active when reading the slot id from backplane partly failed due to parity errors For now the correct value coould be deduced and the system functions OK The original HW problem, though, still exists Typically this is an indication that the backplane contact of one or several cards is poor Node clock missing This fault is active when the synchronization module is not feeding clock to this network element Typically this is an indication that the backplane contact of one or several cards is poor Troubleshooting Step Check possible HW related faults in the network element Use the following command: show faults active fault-group hw If the backplane data bus failure fault is active, there is either defective HW or the card(s) is not properly connected to the backplane Refer to document 8600 Smart Routers Hardware Installation Guide, chapters Mechanical Installation and Maintenance, for example, provide detailed instructions Notice that it is normal that the backplane data bus failure fault is temporarily active after card reset 76.8600-50118I © 2015 Coriant 8600 Smart Routers Equipment Management Configuration Guide 85 Troubleshooting Equipment Management Problems HW Inventory Health Check Run this test after creating the inventory or after a new card(s) has been added to the inventory Step Check boot states If all slots are present in the CLI command output and UP AND RUNNING, then all cards have booted up successfully Use the following command: show hw-inventory | include slot Step Check hw-inventory related faults Use the following command: show faults active fault-group hw-inventory The sections below illustrate three use cases of HW inventory related issues Use Case 1: CDC Control Card With Packet Buffer RAM Failure (PBRF) The system detected a CDC control card in slot 14 having serious Packet Buffer RAM Failure (PBRF) problems and the CDC control card has been blocked to prevent disturbance in the NE functionality Use the following command to display the inventory information in the console: router# show hw-inventory | include slot in in in in slot slot slot slot is part of inventory and UP AND RUNNING is part of inventory and UP AND RUNNING 14 is BLOCKED FROM USE and not allowed to startup 14 is part of inventory Troubleshooting Step Turn the faulty CDC control card power off Step Remove the faulty CDC and keep it with the power off for a few minutes Step Plug in CDC to NE again and turn the power on The CDC control card will boot up normally If it s till remains in "BLOCKED FROM USE" state, contact Coriant representative for further instructions Use Case 2: Line Card Shows Missing from Inventory but Is Physically Present in the Network Element Use the command to display the inventory information in the console In this example the line card in slot is reported as missing from the NE: router# show hw-inventory | include slot in slot is part of inventory and UP AND RUNNING in slot is MISSING from node but part of inventory in slot 14 is part of inventory and UP AND RUNNING Troubleshooting The slot might still be resetting Wait few minutes and check the situation again If slot stay continuously in "MISSING" state, there might communication problems Check the backplane communication link status as described in chapter Backplane Communication Health Check in 8630 Smart Router and 8660 Smart Router 8600 Smart Routers Equipment Management Configuration Guide 86 76.8600-50118I © 2015 Coriant Troubleshooting Equipment Management Problems USe Case 3: Line Card or Line Unit Has No Start Permission Use the following command to display the inventory information in the console In this example the line card in slot has no start permission: router# show hw-inventory slot in slot is part of inventory and WAITING FOR START PERMISSION >UNIT START PERMISSION DENIED! In some cases, the ESW is able to resolve the situation automatically For example, if a line card has just been replaced with another line card having the wrong ESW version, the correct ESW is downloaded and activated automatically, if the correct ESW version exists in some other card For 8630 Smart Router and 8660 Smart Router in FP2.10A and higher, the ESW is able to show the reason why the start permission has been denied and provide instructions for resolving the situation: router# show hw-inventory slot unit in slot is part of inventory and WAITING FOR START PERMISSION >UNIT START PERMISSION DENIED! 1) Autoloader: checking for ESW version (wait) 2) Incompatible ESW, missing ESW support (IF-protection) router# show hw-inventory slot details in slot is part of inventory and WAITING FOR START PERMISSION >UNIT START PERMISSION DENIED! 1) Incompatible ESW, missing ESW support (IF-protection) The card is not allowed to start up, because it is running an older ESW than its protection pair The ESW is missing support for some vital protection features Download and activate a new application ESW now and reset the card Troubleshooting The most usual reason for denying start permission is that the ESW version in a card is incompatible with other ESW version in the NE or inside a card Step Identify the problematic cards by displaying the active faults In this example there is ESW incompatibility between slots and 9: router# show faults active fault-group hw-inventory 001: Slot 1: HW-INVENTORY: Unit Inventory 9: Incompatible sw version Step 76.8600-50118I © 2015 Coriant Download and activate correct ESW versions Refer to the corresponding 8600 Smart Routers Embedded Software Release Notes for further instructions 8600 Smart Routers Equipment Management Configuration Guide 87 Troubleshooting Equipment Management Problems Checklist for Resolving ESW Incompatibility Issues • Check the boot and mini-application software version in all card slots from the interrelation tables from 8600 Smart Routers Embedded Software Release Notes Use the following command: router# show sw-version 1: boot SW gmz2700-03.04.000 3.4.0 1: mini-application SW gmz2702_2.8.191 2.8.191 Backup 1: /flash/appl-sw/slot1/cbz2712_4.1.466 4.1.466 Active OK 9213492 • The following restrictions apply to CDC1 control and IFC1 line cards: • the minimum boot software version is 3.4.0 and • minimum mini-application software version is 2.8.191 • The following restrictions apply to CDC2 control card (FP4.1 and newer): • the minimum boot software version is 1.20.0 and • minimum mini-application software version is 4.1.509 • Check that all cards are running the correct application software version and that no cards are missing from the list Use the following command: router# show sw-version | include OK 1: /flash/appl-sw/slot1/cbz2712_4.1.466 4.1.466 Active OK 9511774 6: /flash/appl-sw/slot6/lbz2713_4.1.466 4.1.466 Active OK 5371638 7: /flash/appl-sw/slot7/lbz2713_4.1.466 4.1.466 Active OK 5371638 14: /flash/appl-sw/slot14/cbz2712_4.1.466 4.1.466 Active OK 9511774 • Check if the card is running the mini-application software Use the following command: router# show sw-version slot 6: 6: 6: boot SW gmz2710-03.04.000 3.4.0 mini-application SW gmz2711_4.1.466 4.1.466 Active system up-time hours, minutes, 5.216 seconds If the card running the mini-application software is a spare card that has just been installed, activate the correct ESW version If the card is not a spare card and it has been part of the hw-inventory, there is probably an ESW or HW issue which has caused the card to drop to the mini-application due to instability and the situation requires further investigation before activating the application software Refer to 8600 Smart Routers Boot and Mini-Applications Software Release Notes, chapter Recovering from Mini-Application 8600 Smart Routers Equipment Management Configuration Guide 88 76.8600-50118I © 2015 Coriant ... other countries 76. 8600- 50118I © 2015 Coriant 8600 Smart Routers Equipment Management Configuration Guide 8600 Smart Routers Equipment Management Configuration Guide 76. 8600- 50118I © 2015 Coriant... fi-documentation@tellabs.com 76. 8600- 50118I © 2015 Coriant 8600 Smart Routers Equipment Management Configuration Guide 15 8600 Smart Routers Discontinued Products 8600 Smart Routers Discontinued Products 8600 Smart Routers. .. Configuration Guide (76. 8670-50179) • 8600 Smart Routers FP7.0 Interface Configuration Guide (76. 8670-50180) (for 8630 Smart Router and 8660 Smart Router) 76. 8600- 50118I © 2015 Coriant 8600 Smart