76 8600 50118i 8600 smart routers equipment management configuration guide

76.8600-50118G 12.03.2014 Related documentation updated in8600 Smart Routers Technical Documentation.Updates on 8609 Smart Router and 8611 Smart Router hot insertionline module to3.6 Add

Trang 2

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 to1.1 User Authentication.Information about replacing an IFC1 line card when part of andMSP1+1 protection group added to3.4 Replacing Cards.76.8600-50118H 22.10.2014 8602 Smart Router and 8615 Smart Router data added

CDC1-CDC2 upgrade instructions updated in chapter3.5.2 UpgradingCDC1 to CDC2

76.8600-50118G 12.03.2014 Related documentation updated in8600 Smart Routers Technical

Documentation.Updates on 8609 Smart Router and 8611 Smart Router hot insertionline module to3.6 Adding and Removing Interface Modules (IFM),Line Modules (LM) and High Speed Modules (HM)

CDC1-CDC2 upgrade instructions updated in chapter3.5.2 UpgradingCDC1 to CDC2

Footnote added about the range of characters allowed in ‘username’CLI command in chapter1 User Management

AppendixTroubleshooting Equipment Management Problemsadded

Trang 3

The functionality described in this document for 8615 Smart Router is also applicable to 8615 Smart Router stacked, unless otherwise stated.

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.

Trang 5

BFD Bidirectional Forwarding DetectionBGP-4 Border Gateway Protocol version 4BMI Broadband Management InterfaceBMP 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)

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 ModuleSCM (used in 8611 Smart Router) In 8000 Intelligent Network Manager and CLIreferred to as unit

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)

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)

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 8630Smart Router and 8660 Smart Router) In 8000 Intelligent Network Manager andCLI 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, thecontrol functionality (CU)

LM Line module (used in 8607 Smart Router, 8609 Smart Router and 8611 Smart Router)

Trang 6

LU1 Line Unit in 8665 Smart RouterMAC Media Access Control Sublayer of Data Link Layer

MPLS Multiprotocol Label SwitchingMSP Multiplex Section Protection

OSPF Open Shortest Path First

PBRF Packet Buffer RAM FailurePKG Software package fileRADIUS Remote Authentication Dial-In User Service Commonly used to provide centralized

authentication, authorization, and accounting functionalities

RSVP-TE Resource Reservation Protocol – Traffic EngineeringSCM Switching and Control Module (used in 8611 Smart Router)SDH Synchronous Digital Hierarchy

SNMP Simple Network Management Protocol

SU1 Switch Unit (used in 8665 Smart Router)

Unit In CLI refers to a cardVRRP Virtual Router Redundancy Protocol

Trang 7

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

1 User Management 17

1.1 User Authentication 17

1.2 Forgotten Password 17

1.3 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

2 Interface Numbering and Legal IF Modules 20

2.1 8602 Smart Router IF Numbering 20

2.7 8615 Smart Router Stacked IF Numbering 23

Trang 8

3.1 ETSI/ANSI/DSL Mode Configuration in HW Inventory 29

3.2 Creating and Deleting HW Inventory 29

3.3 Adding and Removing Cards 30

3.4 Replacing Cards 31

3.5 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

4 HW Inventory CLI Configuration Procedures 43

4.1 First Installation 43

4.2 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

4.3 Changing Interface Module or ETSI/ANSI/DSL Mode 45

4.4 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

4.5 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

4.6 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

5 Software Management 56

5.1 Software Packages 56

5.1.1 Software Package Types in 8660 Smart Router and 8630 Smart Router 56

5.2 Configuring Expected Application ESW to Be Used at Next Reset 57

5.3 Expected Software and Automatic Software Loader 58

5.4 ESW Shutdown before Removing Card(s) or Switching NE Power off 59

5.5 Software Management CLI Configuration Procedures 60

5.5.1 Taking Application ESW into Use in the NE 60

Trang 9

6.1 Overview 63

6.2 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

6.3 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

6.4 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

6.5 CDC Protection CLI Configuration Examples 67

6.5.1 CDC Protection Information 67

6.5.2 Manual CDC Protection Switchover 67

7 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

8 CU 1+1 Equipment Protection 76

8.1 Overview 76

8.2 Protected Software-Level Functionality 76

Trang 10

8.2.2 Backup of Configuration Data 76

8.2.3 Protection of IP and MPLS Protocols 77

8.2.4 References 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

8.4 CU Protection CLI Configuration Examples 79

8.4.1 CU Protection Information 79

8.4.2 Manual CU Protection Switchover 79

9 SU Equipment Protection 80

9.1 Overview 80

9.2 Functional Model 80

9.2.1 Unicast Traffic 80

9.2.2 Multicast Traffic 82

9.3.1 Hitless SU Upgrade Procedure 83

9.4 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

Trang 11

This chapter discusses the objectives and intended audience of this manual, 8600 Smart Routers

Equipment Management Configuration Guide and consists of the following sections:

Audience

This manual is designed for administration personnel for configuring 8600 functions with CLI

On the other hand, 8000 Intelligent Network Manager provides access to equal functionality foradministration personnel with a graphical user interface

It is assumed that you have a basic understanding of data communication equipment with plug-incards and software upgrading in such equipment

8600 Smart Routers Technical Documentation

The document numbering scheme consists of the document ID, indicated by numbers, and thedocument revision, indicated by a letter The references in the Related Documentation table beloware generic and include only the document ID To make sure the references point to the latestavailable document versions, please refer to the relevant product document program on the Tellabsand Coriant Portal by navigating towww.portal.tellabs.com> Product Documentation & Software

> Data Networking > 8600 Smart Routers > Technical Documentation

Trang 12

8600 Smart RoutersATM and TDM Configuration Guide(76.8600-50110)

Provides an overview of 8600 NEs PWE3 applications,including types, Single-Segment and Multi-Segment; PWE3Redundancy; ATM applications, including PWE3 tunnelling,Traffic Management, Fault Management OAM, protection andTDM applications as well as instructions on how to configurethem with CLI

8600 Smart RoutersBoot and Mini-ApplicationsEmbedded Software Release Notes(76.8600-50108)

Provides information related to the boot and mini-applicationssoftware of 8605 Smart Router, 8607 Smart Router, 8609Smart Router, 8611 Smart Router, 8620 Smart Router, 8630Smart Router and 8660 Smart Router as well as the installationinstructions

8600 Smart RoutersCLI Commands Manual(76.8600-50117)

Provides commands available to configure, monitor and maintain

8600 system with CLI

8600 Smart RoutersEmbedded Software Release Notes

8600 Smart Routers SR7.0 Embedded Software Release Notes(76.8670-50177) for the following products:

Provides an overview of 8600 system HW inventory, softwaremanagement, equipment protection 1+1 (CDC and SCM) as well

as instructions on how to configure them with CLI

8600 Smart RoutersEthernet Configuration Guide (76

8600-50133)

Provides an overview of 8600 system Ethernet applications,including interfaces; Ethernet forwarding (MAC Switching,Ethernet PWE3, IRB, VLAN, VPLS); Ethernet OAM; LAG;ELP as well as instructions on how to configure them with CLI

8600 Smart Routers Smart RoutersFault Management ConfigurationGuide (76.8600-50115)

Provides an overview of 8600 system fault management,including fault source, types and status as well as instructions onhow to configure it with CLI

8600 Smart RoutersFrame Relay Configuration Guide(76.8600-50120)

Provides an overview of 8600 system Frame Relay applications,including interfaces; Performance Monitoring; protection; TrafficManagement as well as instructions on how to configure themwith CLI

8600 Smart RoutersHardware Installation Guide(76.8600-40039)

Provides guidance on mechanical installation, cooling,grounding, powering, cabling, maintenance, commissioning andESW downloading

Trang 13

instructions on how to configure them with CLI The followinginterface configuration guides are available:

• 8600 Smart Routers Network Interfaces ConfigurationGuide (76.8600-50161) (for 8602 Smart Router, 8615 SmartRouter and 8665 Smart Router)

• 8609 Smart Router and 8611 Smart Router FP7.0 InterfaceConfiguration Guide (76.8670-50179)

• 8600 Smart Routers FP7.0 Interface Configuration Guide(76.8670-50180) (for 8630 Smart Router and 8660 SmartRouter)

8600 Smart Routers

IP Forwarding and TrafficManagement Configuration Guide(76.8600-50122)

Provides an overview of 8600 NEs IP, forwarding and trafficmanagement functionality, including: IP addressing; IP hosting(ARP, DHCP); IP routing (static); ACL; Differentiated Services(Policing, Queue Management, Shaping) as well as instructions

on how to configure them with CLI

8600 Smart RoutersManagement CommunicationsConfiguration Guide

(76.8600-50125)

Provides an overview of 8600 system managementcommunications functions, including communication protocols:BMP; FTP; RADIUS; SNMP; SSH; TELNET as well asinstructions for configuring them with CLI

8600 Smart RoutersMobile Optimization ConfigurationGuide (76.8600-50100)

Provides an overview of 8600 system Mobile Optimizationapplications as well as instructions on how to configure themwith CLI

8600 Smart RoutersMPLS Applications ConfigurationGuide (76.8600-50123)

Provides an overview of 8600 NEs MPLS applications (includingFRR (one-to-one and facility backup); LDP; protection andTraffic Engineering), MPLS-TP applications (including OAM,linear protection), S-MPLS applications as well as instructions

on how to configure them with CLI

8600 Smart RoutersPerformance Counters ReferenceGuide (76.8600-50143)

Provides an overview of 8600 system supported performancecounters

Trang 14

8600 Smart RoutersReference Manuals The reference manuals describe the 8600 network elementfeatures including:

• NE enclosure, baseboard, power supply modules, andinterfaces in 8602 Smart Router FP7.0 Reference Manual(76.8670-40130)

• NE enclosure, baseboard, power supply modules, interfacesand physical LM types in 8609 Smart Router FP7.0 Refer-ence Manual

• NE enclosure, baseboard, power supply modules, SCMs, HMand LM types in 8611 Smart Router FP7.0 Reference Manual

• NE enclosure, baseboard, power supply modules, and terfaces in 8615 Smart Router FP7.0 Reference Manual(76.8670-40132)

in-• NE subrack, fan modules, CDCs, line cards and IFMs in 8630Smart Router FP7.0 Reference Manual

• NE subrack, fan modules, CDCs, line cards and IFMs in 8660Smart Router FP7.0 Reference Manual

• NE subrack, fan modules, line unit and switch unit in 8665Smart Router FP7.0 Reference Manual (76.8670-40128)

8600 Smart RoutersRouting Protocols ConfigurationGuide (76.8600-50121)

Provides an overview of 8600 NEs routing protocols, includingBFD; BGP; BGP MP; ECMP; IS-IS; OSPF and VRRP as well asinstructions on how to configure them with CLI

8600 Smart RoutersScalability Reference Manual(76.8600-50160)

Provide a summary of tested scalability limits of the 8600 SmartRouters

8600 Smart RoutersSNMP MIB Support(76.8600-50116)

Describes SNMP MIB support by the 8600 NEs and providesinformation on the supported objects and traps For furtherinformation on SNMP MIBs, see the related RFCs

8600 Smart RoutersStatistic Counters Reference Guide(76.8600-50142)

Provides an overview of 8600 system supported statistic counters

8600 Smart RoutersSynchronization ConfigurationGuide (76.8600-50114)

Provides an overview of 8600 NEs synchronization functionality,including physical layer Frequency Synchronization (SEC, EEC);PTP Frequency Synchronization; Phase-Time Synchronization(L2 and L3 applications) as well as instructions on how toconfigure them with CLI

8600 Smart RoutersTest and Measurement ConfigurationGuide (76.8600-50124)

Provides an overview of 8600 NEs measurement and connectivityverification tools, including Ethernet loopback; IP ping andtraceroute; MAC swap loopback; MPLS ping and traceroute;PLT; PWE3 loopback; VCCV (BFD, LSP ping) as well asinstructions on how to configure them with CLI

8600 Smart RoutersVPNs Configuration Guide(76.8600-50128)

Provides an overview of 8600 system virtual private network(VPN) layer 3 applications as well as instructions on how toconfigure them with CLI

8000 Intelligent Network ManagerOnline Help Provides instructions on how different operations are performedwith the 8000 Intelligent Network Manager Describes also

different parameters and controls of the 8000 Intelligent NetworkManager dialogs and windows

Note that the Online Help is not available on the Portal but it isincorporated in the 8000 Intelligent Network Manager

Trang 15

Smart Routers CLI Commands Manual.

Document Conventions

This is a note symbol It emphasizes or supplements information in the document.

This is a caution symbol It indicates that damage to equipment is possible if the instructions are not followed.

This is a warning symbol It indicates that bodily injury is possible if the instructions are not followed.

Documentation Feedback

Please contact us to suggest improvements or to report errors in our documentation:

Email: fi-documentation@tellabs.com

Trang 16

8600 Smart Routers Discontinued Products

8600 Smart Routers Manufacture Discontinued (MD) notifications are available on the Tellabsand Coriant Portal,www.portal.tellabs.com > Product Documentation & Software > Data Networking > [8600 Smart Router product name] > Product Notifications.

Trang 17

The user management feature is used for managing the user account database information in the

8600 system It can contain the information of up to 128 users Viewable information about eachregistered user has the following parameters:

• 6 32 character long user name.1

• User’s privilege level (0–31) Level 31 is superuser level

See more information in 8600 Smart Routers CLI Commands Manual, chapter Security CLI

In addition to the built-in user account database, it is possible to use a remote user database usingRADIUS There must, however, always be a local superuser account before the user authenticationcan be enabled

In 8665 Smart Router, 8615 Smart Router and CDC2 control card the superuser is referred to as rootuser The root user account is mandatory when the user authentication is enabled and when new useraccounts are created The root account is created the same way as any other superuser account

1.2 Forgotten Password

If all user passwords are forgotten and there is no other way to access the network element, theforgotten password feature can be helpful It allows the user to login via the console connection by

using the username lostpassword and password lostpassword.

The lostpassword can only be used from the console port.

Step 1 Login using username/password lostpassword.

user name: lostpassword

password: ************

After login the user will be informed:

1 Supported characters are: a z, A Z, 0 9 and special characters ,_- :;\\/.\'",$+#&^~*|[]()=$@{}

Trang 18

All user account database information and all NE configurationswill be lost.

Are you sure you want to continue (y/n)?

If the letter n is pressed, the operation will be cancelled and the console connection is disconnected.

If the letter y is pressed, a fault will be sent to the network management system and after a delay

of 30 seconds the device will boot up and create the HW inventory from the scratch All existingentries are removed from the user account database and authentication is disabled after the operation

All CLI commands are disabled when logging in using the lostpassword user name.

It is possible to change the default password lostpassword to the one selected by the user.

Step 1 Change username/password from lostpassword to mysecret.

router# lost-password-user

type combined username/password: ********

retype combined username/password: ********

1.3 User Management CLI Configuration Examples

In this chapter you can see supported CLI commands for user management

1.3.1 Creating Superuser Account and Enabling User Authentication

Step 1 Create a new user admin1 with a password mysecret and a privilege level 31 (i.e superuser level).

router# username admin1 privilege 31 description "superuser of the router"

type password: ********

retype password: ********

Step 2 Enable user authentication

router(config)# user-authentication

1.3.2 Disabling User Authentication and Deleting Superuser Account

Disabling user authentication and deleting superuser account must be done in reverse order

Step 1 Disable user authentication

router(config)# no user-authentication Step 2 Delete an existing user named admin1.

router(config)# no username admin1

1.3.3 Changing User Password

Step 1 Change the password to abcd1234.

router# password

type password: *******

retype password: *******

Trang 19

1.3.5 Displaying Logged-in Users

Step 1 Display a list of logged-in users

router# show users

1.3.6 Displaying User Account Activity

Step 1 Displays the user's login history, i.e the user's account activity

router# show user-account-activity

Trang 20

2 Interface Numbering and Legal IF Modules

2.1 8602 Smart Router IF Numbering

Fig 1presents 8602 Smart Router interface numbering It also show legal module positions forsupported modules

The interfaces are referred to as module/if For example, the last interface position is referred as 5/0.

Fig 1 8602 Smart Router IF Numbering

The interfaces are referred to as module/if For example, the 8th interface position (interface 7) in module 1 is referred as 1/7.

Trang 21

Fig 3 8607 Smart Router LM Slots and IF Numbering

Fig 4presents 8609 Smart Router interface numbering It also show legal module positions forsupported modules The LM slots are identified by slot numbers M0–4

Fig 4 8609 Smart Router LM Slots IF Numbering

Trang 22

Fig 5presents 8611 Smart Router interface numbering It also show legal module positions forsupported modules The HM slots are identified by slot numbers M4–6, the LM slots by slotnumbers M0–3, and the SCM slots by slot numbers SCM1–2

The interfaces are referred to as slot/module/if (slot being fixed 2) For example, the 8th interface position (interface 7) in module 3 is referred as 2/3/7.

Fig 5 8611 Smart Router HM, SCM and LM Slot IF Numbering

The interfaces are referred to as 13/module/if For example, the 8th interface position (interface 7) in module 1 is referred as 13/1/7.

Trang 23

2.7 8615 Smart Router Stacked IF Numbering

Fig 7presents 8615 Smart Router stacked interface numbering Interface modules are in virtualcard slot ‘n’

The interfaces are referred to as slot/module/if Master unit slot is 13 and slave unit slot is 2 For example, the 8th interface position (interface7) in module 1 of the master unit is referred as 13/1/7 The corresponding interface of the slave unit is referred as 2/1/7.

8615 Smart Router does not have a dedicated MFE (Management Fast Ethernet) port, instead anyavailable Ethernet port can be used as management interface If this port needs to be protected in

8615 Smart Router stacked, ELP should be used to protect it

Fig 7 8615 Smart Router Stacked Interface Numbering

Trang 24

The interfaces are referred to as slot/module/if For example, the 8th interface position (interface 7)

in module 0 in slot 6 is referred as 6/0/7.

Trang 25

Fig 11presents 8660 Smart Router interface numbering It also show legal module positionsfor supported modules

in module 0 in slot 3 is referred as 3/0/7

Trang 26

Fig 11presents 8665 Smart Router interface numbering It also show legal module positionsfor supported modules

in module 1 in slot 3 is referred as 3/1/7

8665 Smart Router LU1 does not have a dedicated management port, instead any available Ethernetport can be used as management interface If this port needs to be protected, ELP should be used toprotect it

Trang 27

Trang 28

3 HW Inventory

The following descriptions apply to multi-card NEs, that is 8611 Smart Router, 8615 Smart Router, 8615 Smart Router stacked, 8630 Smart Router, 8660 Smart Router and 8665 Smart Router.

In 8620 Smart Router, 8609 Smart Router, 8607 Smart Router, 8605 Smart Router and 8602 Smart Router inventory is more simple: there is only one “slot”, which is always expected

to be occupied by the card type that happens to be there.

However, the module type configuration descriptions apply also to 8620 Smart Router, 8609 Smart Router, 8605 Smart Router and 8607 Smart Router.

The main function of HW inventory in 8600 system is to monitor the hardware configuration in anetwork element (NE) Each card and module is identified by a HW type, HW version, and serialnumber Each NE has a configuration of the expected hardware: what type of cards belong to the NEand what type of modules belong to a card This configuration is kept on the non-volatile memory of

the NE The "expected HW configuration" is later referred to as hw-inventory configuration.

The hw-inventory contains an expected card type and HW version for each card slot in the NE and anexpected module type and mode for each module slot in a card If the type and the HW version of anexisting card in a slot matches with the expected type and HW version in the hw-inventory, the card

is allowed to operate The HW versions do not have to match exactly, but the existing HW version(major and minor fields) must be equal to or higher than the expected HW version (HW version isdisplayed with the notation of major.minor.revision, e.g 1.0.1) If a module type in a module slot ofthis card matches with the expected type in the hw-inventory, the module will be allowed to operate

A NE also maintains configuration backups for all cards belonging to the hw-inventoryconfiguration When a card is replaced by another card of the same type with the same type ofmodules, the new card (replacement card) will get the configuration of the old card and will startoperating as part of the NE without any need to manually configure it

If a card that does not belong to the hw-inventory configuration is inserted into the NE, it will not beallowed to operate as part of the NE until it is added to the hw-inventory configuration In addition,

it will not get configuration backups from the NE Similarly, if a card has a module that is not part ofthe hw-inventory, it will not become operational

When a CDC1 control card (CDC1-A or CDC1-B) is replaced by another CDC1 card, the

HW Major.Minor (e.g 2.0.x) version of a new CDC1 control card base board (CBB2026 or CBB2224) should be at least equal to the HW version of the previous card After replacement, the HW version of the new CDC card base board is saved as an expected HW version If the replacement CDC card base board is of an older HW version than the previous card, the start permission of the replacement card is denied In most cases it is possible to accept an older

HW version in the inventory by using a “hw-inventory slot X force-accept hw-version” CLI command For more information refer to chapter 3.4 Replacing Cards

Trang 29

is possible to accept an older HW version in the inventory by using a “hw-inventory slot X force-accept hw-version” CLI command For more information refer to chapter 3.4 Replacing Cards

3.1 ETSI/ANSI/DSL Mode Configuration in HW Inventory

The 8600 system supports both ETSI and ANSI modes for some types of interfaces (in 8607 SmartRouter also DSL-ETHERNET or DSL-ATM mode is supported) The ETSI mode refers to SDHand E1, while the ANSI mode refers to SONET and T1 The mode is configurable for each IFMand the clock module individually

When a completely new element is equipped, the ETSI/ANSI and DSL mode can be set either on a

module, unit or NE level when the module is taken to the inventory with the add-all-units, add

unit or add module CLI command When the module is added to the inventory without the mode

switch in the CLI command, the mode is set according to the setting stored in the baseboard Thecurrent setting of the module is originated from the factory setting or from the previous installation

If the mode of the module is incorrect, it is possible to set the desired mode using the etsi/ansi or

dsl-ethernet/dsl-atm switch in the CLI command.

If a network element has an existing configuration for the ETSI/ANSI/DSL-capable module and themodule is replaced in the element e.g as a spare part, the new added module automatically inheritsthe settings of the previous one including the ETSI/ANSI/DSL mode from the element backupmemory regardless of the ETSI/ANSI/DSL mode factory setting of the new module

Use the show hw-inventory details CLI command to find out which modes (ETSI/ANSI

or DSL-ETHERNET/DSL-ATM) are supported by a module For more details, refer to 8600

Smart Routers Interface Configuration Guide.

The ETSI/ANSI mode configuration can be done on an interface module level Therefore, the operator ensures that all interface modules in all line cards and the node clock are configured

to operate either in ETSI or ANSI mode Mixed configurations are not supported.

3.2 Creating and Deleting HW Inventory

Generally, add-all-units is the first CLI command that is given to the NE after it has been populated

with a full set of hardware After this the hw-inventory is created and the NE is operational

Trang 30

that is currently present in the NE to the hw-inventory If there is illegal or incompatible HWinstalled in the NE (e.g illegal IFM combination in IFC), a card or module might be left out fromthe hw-inventory or the card might be part of the hw-inventory but in "SW INIT FAILED" state.

In this case the illegal card or module must be removed from the hw-inventory, in some casesalso illegal HW must be removed from the NE

The remove-all-units CLI command, on the other hand, deletes hw-inventory: after

remove-all-units no card in the NE is allowed to operate This CLI command is used when the NE

is to be completely reorganized, i.e all the cards will be relocated to other NEs

When creating hw-inventory, the working CDC, SCM or LU1 in slot 13 must be present!

If the NE has not been issued the add-all-units CLI command, i.e if the working CDC in

8630 Smart Router or 8660 Smart Router, working SCM in 8611 Smart Router or working CU in

8665 Smart Router does not belong to the inventory, there will be a corresponding fault raised.

Deleting inventory by using the remove-all-units CLI command may endanger normal management communication channels to the NE However, the local serial port will always

be available for management use.

If there are two CDCs in 8630 Smart Router or 8660 Smart Router, both CDCs must be of the same variant type (CDC1-A, CDC1-B or CDC2-B).

3.3 Adding and Removing Cards

Before removing a card: If the NE is running FP3.0 or higher ESW, use the "esw-shutdown slot

<slot#>" CLI command and wait until the red (Local Alarm) and yellow (Remote Alarm) LEDs are blinking in the target card (for details see chapter 5.4 ESW Shutdown before Removing Card(s) or Switching NE Power off )!

Refer to 8600 Smart Routers Hardware Installation Guide for more detailed instructions and

restrictions when adding and removing cards

You can add a card that is present in the NE to the hw-inventory The cards existing in theconfiguration will be backed up and the card will be allowed to start up and operate

Adding a new card to the NE inventory consists of the following steps:

• Insert the new card into the NE

• Register the new type by adding the card to the hw-inventory

Trang 31

• A CDC in a 8660 Smart Router's or 8630 Smart Router's working slot (slot 14) is mandatory As

such, it has to be added via add-all-units and removed only via remove-all-units.

• An SCM in a 8611 Smart Router's working slot (slot 2) is mandatory As such, it has to be added

via add-all-units.

• A CU in a 8665 Smart Router’s working slot (slot 14) is mandatory As such, it has to be added

via add-all-units and removed only via remove-all-units.

• If the hw-inventory already has a card in a certain slot, it has to be removed before a card ofanother type can be added to that slot

• A card has to be present before it can be added to the hw-inventory It does not have to be present,however, to be removed from the hw-inventory

• In 8665 Smart Router:

• By default virtual module M2, which comprises the 14x10GBASE-R interface, is alwaysavailable in 8665 Smart Router Virtual modules M0 or M1 cannot be enabled at the sametime Add M0 or M1 to the inventory using the following commands:

hw-inventory slot 13 add module 0 type 1*100GBASE-Rhw-inventory slot 13 add module 1 type 10*10GBASE-R

• If the hw-inventory already has M0, M1 can be added only after removing M0 followed byreload:

hw-inventory slot 13 remove module 0reload-sw

Whenever the NE has an extra card or a card is missing from the NE, there will be a corresponding fault raised.

3.4 Replacing Cards

Before removing a card: If the NE is running FP3.0 or higher ESW, use the "esw-shutdown slot

<slot#>" CLI command and wait until the red (Local Alarm) and yellow (Remote Alarm) LEDs are blinking in the target card (for details see chapter 5.4 ESW Shutdown before Removing Card(s) or Switching NE Power off )!

restrictions when replacing cards

Trang 32

Router maintains configuration backups for all cards belonging to the hw-inventory configuration.When a card is replaced by another card of the same type, the new card (replacement card) willget the configuration of the old card If the replacement card has module(s) and if they are thesame or compatible with the previous module(s), the card will start operating as part of the NEwithout any need to manually configure it Note that a CDC, SCM or CU (running in LU1) can bereplaced maintaining configurations only if it is protected (i.e both CDCs/SCMs/CUs are part of thehw-inventory in the NE) and the one is working while the other one is being replaced.

If a CDC control card (CBB2026, CBB2224 or CBB2300) in 8630 Smart Router or 8660 SmartRouter, an SCM control card in 8611 Smart Router, a SU1 or LU1 units in 8665 Smart Router isreplaced, the HW version of the replacement card should be equal to or higher than in the originalcard If the HW version of the replacement card is lower, the start permission of the replacement

card is denied A replacement card can be accepted in the hw-inventory by using a force-accept

CLI command

If the Management Fast Ethernet interface of 8630 Smart Router or 8660 Smart Router is configured in half duplex mode and the HW version of the replacement CDC1 is lower than 2.0, the start permission of the replacement CDC is still denied The start permission is granted after configuring interface MFE 14/0 (or MFE 1/0 if CDC in slot 1 is active) to use full duplex mode.

If an IFC1 line card part of an MSP1+1 protection group is replaced by another IFC1 line card fromthe same network element and the replacing IFC1 line card contains earlier configuration, duringbootup the replacement IFC1 line card may use some of the old configuration and might mix upthe operation of the protection group This may cause data cut In this case, it is recommended toclean the configuration of the replacement card before the installation using the CLI command

‘hw-inventory slot N add unit clean-start’ Note that the cleaning has to be done in some other slot

or network element

3.5 Upgrading Line and Control Cards in 8630 Smart Router and 8660

Smart Router

restrictions when replacing cards

In case of upgrade failure, it is possible to restore the previous configuration using configuration snapshot, if the previous cards are first installed back to the NE.

For more detailed information on using configuration snapshots for restoring previous

configuration, refer to 8600 Smart Routers ESW Release Notes, chapters Operations Before

Upgrade and Restoring Previous FP and Configuration in Case of Upgrade Failure

Trang 33

according to the table below Upgrading cards is a corresponding operation to "replacing cards"

as described in the previous chapter: IFC2 obtains the configuration of the previous IFC1 card, inaddition the new expected card type (IFC2) is automatically updated in the hw-inventory

During upgrade the IFC1 configuration is converted to IFC2 configuration Note that the operation is irreversible!

The following IFMs can be upgraded during the IFC1–IFC2 upgrade

In addition to the IFMs listed in the table, the IFC1–IFC2 upgrade is supported if the IFM type is

not changed (for the IFM types supported by both IFC1 and IFC2) Refer to 8630 Smart Router

Reference Manual and 8660 Smart Router Reference Manual for supported IFMs in IFC1 and IFC2.

Automatic Upgrade Support for IFMs in IFC1–IFC2 Upgrade Old Module Type in IFC1 Compatible New Module Type in IFC2

8x10/100BASE-TX IFM 8x10/100/1000BASE-TX R2 IFM8x100BASE-X IFM 8x100/1000BASE-X R2 IFM2x1000BASE-X IFM 8x100/1000BASE-X R2 IFM8x1000BASE-X IFM 8x100/1000BASE-X R2 IFM

8x10/100/1000BASE-TX R2 IFM2+6x10/100/1000BASE-COMBO IFM

8x100/1000BASE-X R2 IFM1xchSTM-1/chOC-3 MS IFM 4xchSTM-1/chOC-3 MS IFM

Refer to 8600 Smart Routers ESW Release Notes for FP4.0 or higher for more detailed

instructions and restrictions when upgrading IFC1 to IFC2.

3.5.2 Upgrading CDC1 to CDC2

In 8630 Smart Router and 8660 Smart Router with CDC-1+1 protection, CDC1-A or CDC1-B cardscan be replaced with CDC2-B cards During upgrade operation CDC2 obtains the configuration ofthe previous CDC1 card; in addition the new expected card type (CDC2-B) is automatically updated

in the hw-inventory The operation is non-service affecting and irreversible

During upgrade the CDC1 configuration is converted to CDC2 configuration Note that the operation is irreversible!

Trang 34

Refer to 8600 Smart Routers Hardware Installation Guide for more detailed instructions and

restrictions.

CDC2 control card has a mandatory root user that is needed when new users are created

or user authentication is enabled.

When upgrading from CDC1 to CDC2 and the user authentication is enabled on the CDC1 control card, it will also be enabled on CDC2 control card after the upgrade The root user can then be created on the CDC2 control card by any superuser.

The requirements before the CDC upgrade are:

• CDC 1+1 protection is required (CDC1-A or CDC1-B)

• The NE must be running ESW version FP4.1 SP1 or above

• The new CDC2 units must have the same ESW version active as the rest of the cards have IfCDC2 has wrong ESW version active, use an external, preferably non-live traffic network ele-ment to download the correct ESW with FTP to the CDC2 card, activate it and reload

The following procedure shall be used for the CDC upgrade:

Step 1 Check that CDC in slot 14 is active:

router# show protection unit cdc

If CDC in slot 1 is active, switch activity to slot 14:

router# protection manual-switchover unit cdc slot 14

Step 2 Grant upgrade permission

router# hw-inventory slot 14 upgrade-permission cdc1-cdc2

Step 3 NE configuration is denied until step 12 However configurations mentioned in this step list are

allowed Cancelling the upgrade permission is possible before slot 14 gets the start permission instep 8, after this point the upgrade is irreversible

Trang 35

Unit 14 is in OK state.

Unit 14 is passive

Unit 14 is non-revertive

Unit 14 is a working unit

Unit 1 is in OK state

Unit 1 is active

Unit 1 has no switch command active.

Unit 1 has noRequest switch type.

Unit 1 is a protecting unit

Step 5 Shutdown slot 14

router# esw-shutdown slot 14

Step 6 When the red and yellow LEDs (local and remote alarm) of CDC1 slot 14 are blinking, you can

remove the card according to instructions in the 8600 Smart Routers Hardware Installation Guide.

Step 7 Change the needed cable types (Serial interface/Alarm I/O, SCO/SCI, power cable) of the CDC

in slot 14

Step 8 Insert CDC2 to slot 14 according to the 8600 Smart Routers Hardware Installation Guide.

CDC2 must have the same ESW version active as the rest of the cards have

Step 9 Wait until CDC2 in slot 14 is up and running

router#show hw-inventory slot 14 detailsunit in slot 14 is part of inventory and UP AND RUNNING

…

Trang 36

router# protection manual-switchover interface mfe slot 14router# protection manual-switchover unit cdc slot 14Wait until switching is completed Use the following command and wait for the highlighted state:router#show protection unit cdc

Unit 14 is active

Unit 14 has no switch command active.

Unit 14 is a working unit

Unit 1 is passive

Unit 1 is a protecting unit

After switchover command CDC1 in slot 1 might do automatic reboot to synchronize configuration with new CDC2 If reboot happens before executing step 5 to slot 1, wait until slot 1 is up and running again after reboot:

router#show hw-inventory slot 1 unit in slot 1 is part of inventory and UP AND RUNNING

Step 11 Repeat steps 5-9 to the CDC in slot 1.

Step 12 NE configuration is allowed again.

Step 13 Create root user.

router# username root privilege 31 description "root user ofthe router"

type password:********

retype password:********

3.6 Adding and Removing Interface Modules (IFM), Line Modules

(LM) and High Speed Modules (HM)

restrictions when adding and removing modules.

Trang 37

• The active type (and mode) is the type that has been configured last and has become operational

last

• The expected type (and mode) is the type that the HW inventory currently expects.

Whenever the existing, active and expected types or modes do not match, there will be a corresponding fault raised.

A card has to be part of the HW inventory before its module configuration can be changed Whenthe card is first added, the modules it has are automatically added to the HW inventory

The user can add or remove a module to/from a card Removing a module means setting its expected

type to none Adding a module means setting a new value to its expected type and/or mode.

The add or remove operation will change the expected type, but the active type or mode willnot change before the next card reset, except for the special case where the expected type was

previously none.

When removing a module, the expected type is set to none A reset is required for the active module type to be set to none Typically the module will continue to be operational, if no action is taken by

the user to reset the card, but in LMs data flow is cut immediately

3.6.1 Changing an Existing Module or Installing a New Module

Changing an existing module or installing a new module consists of the following steps Note thatwhen replacing a HM with the same type, SCM switchover is not needed

• If only the expected mode is changed, the card must be restarted and the remaining steps are notneeded

• For 8630 Smart Router and 8660 Smart Router:

• Configure the new type and/or mode by adding a module

• Run the "esw-shutdown" CLI command for the line card

• Remove the line card (IFC) from the NE

• Detach the old module (IFM), if any, from the line card

• Insert the new module in the line card

• Insert the line card in the NE

Trang 38

• Configure the new type and/or mode by adding a module.

• Run the "esw-shutdown" CLI command

• Power off the NE before detaching/inserting modules

• Detach the old module, if any, from the NE

• Insert the new module in the NE

• Power on the NE

• For 8609 Smart Router and 8611 Smart Router (LM changes only)

This procedure applies also to line modules 8x10/100BASE-TX 81.86LFETX82243-R6 Rev D

or higher and 8xchE1/chT1 81.86LE1T082242-R6 Rev D or higher when the replacing line module is of the same type as the active one.

• Power off the NE before detaching/inserting modules

• Power on the NE

• For 8609 Smart Router and 8611 Smart Router (HM and LM changes):

This procedure applies also to line modules 8x10/100BASE-TX 81.86LFETX82243-R6 Rev D

or higher and 8xchE1/chT1 81.86LE1T082242-R6 Rev D or higher when the replacing line module is not of the same type as the active one.

• Initiate NE reset and/or switchover actions

Now the existing, active and expected types should match and the module should be operational

3.6.2 Removing a Module

Removing a module consists of the following steps:

Trang 39

• Remove the line card (IFC) from the NE.

• Detach the old module (IFM) from the line card

• Insert the card in the NE

• For 8607 Smart Router, 8620 Smart Router:

• Configure the new type and/or mode by adding a module

• Power off the NE before detaching modules

• Detach the old module from the NE

• Power on the NE

• For 8609 Smart Router and 8611 Smart Router (LM changes only):

This procedure applies to all line modules, expect for 8x10/100BASE-TX 81.86LFETX82243-R6 Rev D or higher and 8xchE1/chT1 81.86LE1T082242-R6 Rev D or higher.

• Power off the NE before detaching modules

• Power on the NE

• For 8607 Smart Router, 8609 Smart Router and 8611 Smart Router (HM and LM removal):

This procedure applies also to line modules 8x10/100BASE-TX 81.86LFETX82243-R6 Rev D or higher and 8xchE1/chT1 81.86LE1T082242-R6 Rev D or higher.

• Initiate NE reset and/or switchover actions

Now the existing, active and expected types should match (all should be none).

Instead of detaching an old module and inserting a new module, a replacement card having thecorrect modules installed can be used!

3.7 Upgrading Modules

restrictions when upgrading modules.

Trang 40

new module In such cases the new module will be saved automatically in the HW inventory (as anexpected type) without any user configuration.

Upgrading a module in a card consists of the following steps:

• Run the "esw-shutdown" CLI command for the card

• Remove the line card (IFC) from the NE

• Use a replacement card (IFC) with the new module (IFM) or detach the old module from the cardand insert the new module in the card

• Insert the card in the NE

Now the existing, active and expected types should match and the module should be operational

During upgrade the old IFM configuration is converted to a new IFM configuration Note that the operation is irreversible!

Certain IFM upgrades can be done when upgrading from IFC1 to IFC2, see chapter 3.5 Upgrading Line and Control Cards in 8630 Smart Router and 8660 Smart Router for more information.

Automatic upgrade is supported for the following modules:

1xchSTM-1/chOC-3 MS IFM 4xchSTM-1/chOC-3 MS IFM

3.8 Control Functionality (CU) in 8615 Smart Router and 8665 Smart

Router

The control functionality (CU) in 8615 Smart Router and 8665 Smart Router is SW based andhas no physical entity

In 8665 Smart Router CU software runs in the LU1s Currently CU can be run only in slots 2 and

13, respectively the leftmost and rightmost line units in the network element When both units inslots 2 and 13 are installed, the network element is fully redundant

In 8615 Smart Router redundancy can be achieved by stacking two 8615 Smart Routers For moredetails refer to3.10 8615 Smart Router Stacked Inventory

The CLI may use both ‘cdc’ and ‘cu’ when configuring CU in 8615 Smart Router and 8665 Smart Router When a CU functionality is 8615 Smart Router or 8665 Smart Router specific, it will be shown in the documentation.

Định dạng
Số trang	88
Dung lượng	2,49 MB