AVIAT CTR 8600 EQUIPMENT MANAGEMENT
Aviat CTR 8600 Routers
Equipment Management Configuration Guide
December 2014
260-668268-004
DECEMBER 2014
1
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
2
AVIAT NETWORKS
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
Copyright and Terms of Use
DECEMBER 2014
CTR 8600 Routers Equipment Management Configuration Guide
This documentation incorporates features and functions provided with CTR 8611 FP2.0, CTR 8602 FP1.3.
Copyright © 2014 by AVIAT NETWORKS, Inc.
All rights reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system,
or translated into any language or computer language, in any form or by any means, electronic, magnetic, optical,
chemical, manual or otherwise, without the prior written permission of Aviat Networks Inc. To request permission,
contact techpubs@aviatnet.com.
Warranty
Aviat Networks makes no representation or warranties with respect to the contents hereof and specifically disclaims any
implied warranties or merchantability or fitness for any particular purpose. Further, Aviat Networks reserves the right to
revise this publication and to make changes from time to time in the content hereof without obligation of Aviat Networks
to notify any person of such revision or changes.
Safety Recommendations
The following safety recommendations must be considered to avoid injuries to persons and/or damage to the equipment:
1. Installation and Service Personnel: Installation and service must be carried out by authorized personnel who have the
technical training and experience necessary to be aware of any hazardous operations during installation and service, and
of measures to avoid any danger to themselves, to any other personnel, and to the equipment.
2. Access to the Equipment: Access to the equipment in use must be restricted to service personnel only.
3. Safety Norms: Recommended safety norms are detailed in the Health and Safety sections of this manual. Local safety
regulations must be used if mandatory. Safety instructions in this document should be used in addition to the local safety
regulations. In the case of conflict between safety instructions stated in this manual and those indicated in local
regulations, mandatory local norms will prevail. Should local regulations not be mandatory, then the safety norms in
Volume 1 will prevail.
4. Service Personnel Skill: Service personnel must have received adequate technical training on telecommunications and
in particular on the equipment this manual refers to.
Trademarks
All trademarks are the property of their respective owners.
Revision History
Document
No.
Date
Description of Changes
001
12/19/2014
Initial release of the document for Aviat CTR 8611/8602 Router
260-668268-004
DECEMBER 2014
3
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
Aviat Networks Technical & Sales Support
Technical Service and Support
For customer service and technical support, contact one of the regional Technical Help Desks listed below, or for 24/7
(all day, every day) there is a Global Technical Help Desk (GTHD). A call will be answered by GTHD support staff who
will resolve the issue, if possible, or quickly pass the call to the appropriate TAC engineer for resolution. Contact
information is available below or on the Aviat Networks web site.
Global Technical Help Desk (GTHD)
The GTHD number is +1-210-526-6345, or toll free 1-800-227-8322 within USA.
For 24/7 access you will need your Support Assurance PIN. Without a PIN, you will still receive
support, but the support process will require an additional screening step. After-hours calls to Paris
are routed to the GTHD, with the existing number left in place during business hours.
America Technical Help Desk
Aviat Networks
5200 Great America Parkway
Santa Clara, CA 95054
U.S.A
Asia Pacific Technical Help Desk
Aviat Networks
Bldg 10, Units A&B
Philexcel Industrial Park
M. Roxas Hi-way
Clark Freeport Zone
Philippines 2023
Toll Free (Canada/USA):
800 227 8332
Phone: 210 561 7400
Fax: 210 561 7399
EMEA Technical Help Desk
Aviat Networks
4 Bell Drive
Hamilton International Technology
Park
Blantyre, Glasgow, Scotland
G72 oFB
United KIngdom
Phone:
Hamilton: +44 (0) 1698 717 230
Paris: +33 (0) 1 77 31 00 33
Fax: +44 (0) 1698 717 204
TAC.AM@aviatnet.com
TAC.EMEA@aviatnet.com
TAC.APAC@aviatnet.com
Phone: +63 45 599 5192
Fax: +63 45 599 5196
AviatCare Online Customer Support Portal
To open cases, request Return Material Authorizations (RMA), track orders, and access our knowledge base
and documentation download service:
• AviatCare Online Support Site: http://support.aviatnetworks.com
Sales and Sales Support
Contact one of the Aviat Networks headquarters, or find your regional sales office on the Aviat Networks web site.
Corporate Headquarters, California
USA
Aviat Networks
5200 Great America Parkway
Santa Clara, CA 95054
U.S.A
Phone: + 408 567 7000
Fax: + 408 567 7001
4
International Headquarters,
Singapore
Aviat Networks (S) Pte. Ltd.
17, Changi Business Park Central 1
Honeywell Building, #04-01
Singapore 486073
Phone: +65 6496 0900
Fax: +65 6496 0999
Sales Inquiries: +1-321-674-4252
AVIAT NETWORKS
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
260-668268-004
DECEMBER 2014
5
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
Table of Contents
1.0
Aviat CTR 8600 System Overview .......................................................................................................................... 9
1.1
2.0
Introduction - Aviat CTR 8611 Router ............................................................................................................... 9
User Management ............................................................................................................................................... 10
2.1
User Authentication ......................................................................................................................................... 10
2.2
Forgotten Password ......................................................................................................................................... 10
2.3
User Management CLI Configuration Examples ............................................................................................... 11
2.3.1
Creating Superuser Account and Enabling User Authentication ................................................................ 11
2.3.2
Disabling User Authentication and Deleting Superuser Account ............................................................... 11
2.3.3
Changing User Password ............................................................................................................................. 11
2.3.4
Displaying Configured User List ................................................................................................................... 11
2.3.5
Displaying Logged-in Users .......................................................................................................................... 12
2.3.6
Displaying User Account Activity ................................................................................................................. 12
3.0
HW Inventory ...................................................................................................................................................... 13
3.1
General ............................................................................................................................................................. 13
3.2
Module Inventory of the CTR 8602 and 8611 Routers .................................................................................... 14
3.3
ETSI/ANSI/DSL Mode Configuration in Inventory ............................................................................................ 14
3.4
Creating and Deleting HW Inventory ............................................................................................................... 15
3.5
Adding and Removing Cards ............................................................................................................................ 16
3.6
Replacing Cards ................................................................................................................................................ 16
3.7
Upgrading Cards ............................................................................................................................................... 17
3.8
Adding and Removing Modules ....................................................................................................................... 17
3.9
Upgrading Modules .......................................................................................................................................... 19
3.10
NE Installation CLI Examples ............................................................................................................................ 19
3.10.1
First Installation ....................................................................................................................................... 19
3.10.2
Adding a Card or an SCM ........................................................................................................................ 20
3.10.3
Removing a Card or an SCM ................................................................................................................... 21
3.10.4
Changing Interface Module or ETSI/ANSI/DSL Mode .............................................................................. 21
3.10.5
Adding a Line Module ............................................................................................................................. 22
3.10.6
Removing a Line Module......................................................................................................................... 22
3.10.7
Replacing a Line Module ......................................................................................................................... 23
3.10.8
Adding a High Speed Module.................................................................................................................. 24
3.10.9
Removing a High Speed Module ............................................................................................................. 25
3.10.10
4.0
Replacing a High Speed Module ......................................................................................................... 26
Software Management ........................................................................................................................................ 28
4.1
Software Packages ........................................................................................................................................... 28
4.2
Configuring Expected Application ESW to Be Used at Next Reset .................................................................. 28
6
AVIAT NETWORKS
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
4.3
Expected Software and Automatic Software Loader ....................................................................................... 29
4.4
ESW Shutdown before Removing Card(s) or Switching NE Power off ............................................................. 30
4.5
Software Management CLI Configuration Examples ....................................................................................... 30
4.5.1
Taking Application ESW into Use in NE ....................................................................................................... 31
4.5.2
Using Configuration Backup and Restore .................................................................................................... 31
5.0
SCM 1+1 Equipment Protection .......................................................................................................................... 33
5.1
Overview .......................................................................................................................................................... 33
5.1.1
Manual SCM Protection Switchover ............................................................................................................ 33
5.1.2
Automatic SCM Protection Switchover ....................................................................................................... 33
5.2
Forwarding Functions and Protocols ............................................................................................................... 34
5.3
Signaling Functions and Protocols ................................................................................................................... 34
5.3.1
5.4
References ................................................................................................................................................... 35
Management Functions, Protocols, and Interfaces ......................................................................................... 35
5.4.1
Management Ethernet Port Protection ....................................................................................................... 35
5.4.2
Console Port Protection .............................................................................................................................. 36
5.4.3
Management Functions ............................................................................................................................... 36
5.5
System Alarm Interfaces .................................................................................................................................. 36
5.6
System Status Indicators .................................................................................................................................. 37
5.7
Station Clock Interfaces ................................................................................................................................... 38
5.8
Backup of Configuration Data .......................................................................................................................... 38
5.9
Non-Service Affecting Software Upgrade ........................................................................................................ 38
5.10 SCM Protection CLI Configuration Examples ....................................................................................................... 38
5.10.1
SCM Protection Information ................................................................................................................... 39
5.10.2
Manual SCM Protection Switchover ....................................................................................................... 39
6.0
Troubleshooting Equipment Management Problems ......................................................................................... 40
6.1
HW Inventory Health Check ............................................................................................................................. 40
6.2
Checklist for Resolving ESW Incompatibility Issues ......................................................................................... 41
Terms and Abbreviations................................................................................................................................................... 42
260-668268-004
DECEMBER 2014
7
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
About This Document
This chapter discusses the objectives and intended audience of this manual, Aviat CTR 8600
Router Equipment Management Configuration Guide.
Objectives
This manual provides an overview of the Aviat CTR 8600 user management, hardware
inventory, software management and SCM equipment protection and instructions on how to
configure them using command line interface (CLI) with a router’s console or remote terminal
(Telnet or SSH).
Audience
This manual is designed for administration personnel for configuring Aviat CTR 8600 functions
with CLI. On the other hand, Aviat INM provides access to equal functionality for
administration personnel with a graphical user interface.
It is assumed that you have a basic understanding of data communication equipment with plug-in
cards and software upgrading in such equipment.
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.
8
AVIAT NETWORKS
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
1.0
Aviat CTR 8600 System Overview
The Aviat CTR 8600 Routers are key elements of the Aviat Mobile Backhaul Solution. The Aviat
CTR 8600 routers offer a managed IP/MPLS access solution primarily focused on mobile backhaul
networks, enabling smooth radio access network (RAN) evolution to long term evolution (LTE)
from 2G and 3G. It optimizes the cost per bit in the access and aggregation networks as well as
streamlines the network and service operations with the help of the integrated management system,
the Aviat ProVision Intelligent Network Management System or INM.
Thanks to the flexible equipping options enabling capacity growth, variety of interfaces and services
on the CTR 8600 portfolio, the same platform may be used as a basis for fixed service transport.
IP/MPLS as a technology is commonly used in core networks. It is also a great fit for access
networks as it simplifies the network operations administration and maintenance (OAM), supports
multiple transport and service protocols and offers great QoS and resilience management.
The CTR 8600 system and IP/MPLS technology first of all enables building a network with a
mixture of transport technologies and therefore provides a great transition path to pure packet
transport. Another great advantage is the ability to transport multiple connection and service types,
which are inherently part of the element designs. As a result the operators can truly use the Aviat
CTR 8600 system as a unified access platform for any service. Accurate synchronization is vital
for mobile network operation. Along with the technology transition to packet based technologies,
the synchronization must be part of the solution. Aviat has been active in packet synchronization
standardization and offers thorough packet synchronization tools integrated with the entire Aviat
CTR 8600 system. Advanced synchronization caters not only the needs of 3G and LTE networks
but also the phase synchronization requirement of the LTE Advanced.
The CTR 8600 routers features and functionalities, including all the network elements and related
Aviat ProVision INM, are designed and tested as a solution which makes its introduction and
operation easy for the operators. The platform is easy to scale and enhance with small incremental
investments, justifying it as a long term platform
1.1
Introduction - Aviat CTR 8611 Router
The Aviat CTR 8600 family of products provides a complete network solution and includes
Aviat CTR 8611 Microwave router and the Aviat Provision Intelligent Network Manager (INM),
an advanced network management system for managing the entire network including all of its
connections and services.
The CTR 8611 Microwave router is a 2RU, environmentally hardened network element with a
completely modular design. The CTR 8611 Microwave router can be equipped with redundant
switching and control modules for carrier grade reliability and has seven slots for physical line
modules. The CTR 8611 Microwave router provide versatile service capabilities including
support for TDM, ATM, HDLC and Ethernet based connections as well as IP routing and
MPLS switching. Both products enable the migration of 2G TDM and 3G ATM, Ethernet or IP
based networks into a single network infrastructure and both have packet based forwarding with
QoS support enabling network optimization for voice and data services.
260-668268-004
DECEMBER 2014
9
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
2.0
User Management
The user management feature is used for managing the user account database information in the
Aviat CTR 8600 system. It can contain information of up to 128 users. Viewable information
about each registered user has the following parameters:
• 6 - 32 character long user name.
• User’s privilege level (0–31). Level 31 is superuser level.
• 80-character-long free format user description.
2.1
User Authentication
When a new network element is taken into use, user authentication is disabled. This means
that anybody can login and change its configuration. It is essential that the initial
configuration of the network element includes creating a new superuser account with the
maximum privilege level and enabling user authentication.
In addition to the built-in user account database, it is possible to use a remote user database using
RADIUS. There must, however, always be a local superuser account before the user authentication
can be enabled.
2.2
Forgotten Password
If all user passwords are forgotten and there is no other way to access the network element, the
forgotten 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:
This operation will reset the NE with factory settings.
All user account database information and all NE
configurations will 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 existing entries 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.
10
AVIAT NETWORKS
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
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: ********
2.3
User Management CLI Configuration Examples
In this chapter you can see supported CLI commands for user management.
2.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
Enable user authentication.
router(config)# user-authentication
2.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
2.3.3
Changing User Password
Step 1 Change the password to abcd1234.
router# password
type password: *******
retype password: *******
2.3.4
Displaying Configured User List
Step 1 Display a list of users.
router# show user-list
260-668268-004
DECEMBER 2014
11
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
2.3.5
Displaying Logged-in Users
Step 1 Display a list of logged-in users.
router# show users
2.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
12
AVIAT NETWORKS
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
3.0
3.1
HW Inventory
General
The main function of HW inventory in Aviat CTR 8600 system is to monitor the hardware
configuration in a network element (NE). Each card and module is identified by a HW type, HW
version, and serial number. Each NE has a configuration of the expected hardware: what type
of cards belong to the NE and 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 an expected module type and mode for each module slot in a card. If the type and the HW
version of an existing card in a slot matches with the expected type and HW version in the hwinventory, 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 is displayed with the notation of major.minor.revision, e.g. 1.0.1). If a
module type in a module slot of this card matches with the expected type in the hw-inventory,
the module will be allowed to operate.
An NE also maintains configuration backups for all cards belonging to the hw-inventory
configuration. When a card is replaced by another card of the same type with the same type
of modules, the new card (replacement card) will get the configuration of the old card and will
start operating as part of the NE without any need to manually configure it.
When an SCM module is replaced by another module, the HW Major.Minor (e.g. 2.0.x)
version of the new SCM module (SCM2265) should be at least equal to the HW version of
the previous module. After replacement, the HW version of the new SCM module is saved
as an expected HW version. If the replacement SCM module is of an older HW version
than the previous card, the start permission of the replacement module is denied. In most
cases it is possible to accept an older HW version in the inventory by using a “hwinventory slot X force-accept hw-version” CLI command.
If a card or SCM that does not belong to the hw-inventory configuration is inserted into the NE,
it will not be allowed 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 of the hw-inventory, it will not become operational.
260-668268-004
DECEMBER 2014
13
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
3.2
Module Inventory of the CTR 8602 and 8611 Routers
The following figure presents CTR 8602 Router interface numbering.
Fig. 1 CTR 8602 Router IF Numbering
In the CTR 8611 router, the pluggable high speed module (HM) slots are located on the top
shelf, the pluggable switching and control module (SCM) slots are located on the middle shelf,
and the pluggable line module (LM) slots on the bottom shelf.
The HM slots are identified by slot numbers M4–6, the LM slots by slot numbers M0–3, and the
SCM slots by slot numbers SCM1–2 according to the front view shown in the figure below.
Fig. 2 CTR 8611 Router HM, SCM and LM Slot and Interface Numbering
3.3
ETSI/ANSI/DSL Mode Configuration in Inventory
The Aviat CTR 8600 system supports both ETSI and ANSI modes for some types of interfaces.
The ETSI mode refers to SDH and E1, while the ANSI mode refers to SONET and T1. The
mode is configurable for each IFM and 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-
14
AVIAT NETWORKS
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
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. The current 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 the module is replaced in the element e.g. as a spare part, the new added module
automatically inherits the settings of the previous one including the ETSI/ANSI/DSL mode
from the element backup memory 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.
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.4
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.
The add-all-units CLI command adds all hardware (every card and every module in every card)
that is currently present in the NE to the hw-inventory. If there is illegal or incompatible HW
installed in the NE (e.g. illegal IFM combination in IFC), a card or module might be left
out from the 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 cases also 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 or SCM must be present!
If the NE has not been issued the add-all-units CLI command, i.e. working SCM (in
CTR 8611 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.
260-668268-004
DECEMBER 2014
15
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
3.5
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
Refer to Aviat CTR 8600 Router 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 the
configuration 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.
Now the card should be operational after restart. The modules which logically belong to the card
will be added to the hw-inventory automatically.
A card can be removed from the hw-inventory. This can be done whether or not it is present.
When a card is removed from inventory, it will reset. After the reset it will not receive a
permission to operate.
Restrictions:
• An SCM in a CTR 8611 router's working slot (i.e. slot 2) is mandatory. As such, it has to be
added via add-all-units.
• If the hw-inventory already has a card in a certain slot, it has to be removed before a card of
another 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.
Whenever the NE has an extra card or a card is missing from the NE, there will be a
corresponding fault raised.
3.6
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
Refer to Aviat CTR 8600 Router Hardware Installation Guide for more detailed instructions
and restrictions when replacing cards.
The hw-inventory in the C T R 8611 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) will get the configuration of the old card. If the
16
AVIAT NETWORKS
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
replacement card has module(s) and if they are the same or compatible with the previous
module(s), the card will start operating as part of the NE without any need to manually
configure it. Note that a CDC or an SCM can be replaced maintaining configurations only if
it is protected (i.e. both CDCs/SCMs are part of the hw-inventory in the NE) and the other one
is working while the other one is replaced.
If an SCM card in the CTR 8611 router is replaced, the HW version of the replacement card
should be equal to or higher than in the original card. 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.
3.7
Upgrading Cards
Refer to Aviat CTR 8600 Router Hardware Installation Guide for more detailed instructions and
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.
3.8
Adding and Removing Modules
Refer to Aviat CTR 8600 Router Hardware Installation Guide for more detailed instructions
and restrictions when adding and removing modules.
A card or enclosure can have replaceable modules, for instance interface modules and
timing modules. A module can be physically located either in the card baseboard or in the
enclosure, but in both cases it logically belongs to a card in the hw-inventory. The inventory has
three fields for a replaceable module: existing, active, and expected.
• The existing type (and mode) is the actual type of the hardware module.
• 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.
A card has to be part of the HW inventory before its module configuration can be changed.
When the 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 will
not 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.
260-668268-004
DECEMBER 2014
17
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
Changing an existing module or installing a new module consists of the following steps.
Note that when 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 not needed.
For Aviat CTR 8611 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.
• 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 Aviat CTR 8611 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.
• Detach the old module, if any, from the NE.
• Insert the new module in the NE.
• Initiate NE reset and/or switchover actions.
Now the existing, active and expected types should match and the module should be
operational.
Removing a module consists of the following steps:
• Configure the new expected type by removing the module.
For Aviat CTR 8611 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.
• Run the "esw-shutdown" CLI command.
• Power off the NE before detaching modules.
• Detach the old module from the NE.
• Power on the NE.
For Aviat CTR 8611 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.
• Detach the old module from the NE.
• Initiate NE reset and/or switchover actions.
18
AVIAT NETWORKS
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
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 the
correct modules installed can be used!
Whenever the existing, active and expected types or modes do not match, there will be a
corresponding fault raised.
3.9
Upgrading Modules
Refer to Aviat CTR 8600 Router Hardware Installation Guide for more detailed instructions
and restrictions when upgrading modules.
A module can be upgraded to a newer one automatically, if a module is replaced with a
compatible new module. In such cases the new module will be saved automatically in the
HW inventory (as an expected 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
card and 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!
Automatic upgrade is supported for the following modules:
Old Module Type
Compatible New Module Type
1xchSTM-1/chOC-3 MS IFM
4xchSTM-1/chOC-3 MS IFM
3.10 NE Installation CLI Examples
3.10.1
First Installation
The C T R 8611 router contains two slots for SCMs, of which slot SCM2 is the working
slot: if only one SCM is used, it must be installed in slot SCM2.
In this example, install CDC physically to slot 14 and line cards to slots 5 and 9.
260-668268-004
DECEMBER 2014
19
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
Step 1
Enter the Privileged Exec CLI command mode.
NE> enable
Step 2
Check the hw-inventory configuration.
The show CLI command indicates that all cards 5, 9 and 14 exist, but these are extra cards
that do not belong to the inventory.
The CLI command also indicates types of the interface modules and the supported mode(s)
or if the mode is not relevant for the module.
NE# show hw-inventory details
Step 3 Create a new hw-inventory configuration. Clean all the configurations possibly left in the
cards from a previous installation. Select ETSI mode for all the interface modules
supporting ETSI mode.
After a while, the NE is operational.
NE# hw-inventory add-all-units clean-start etsi
Step 4 Check the hw-inventory configuration.
The show CLI command indicates that all cards 5, 9 and 14 are part of the inventory and
UP AND RUNNING. All interface modules and Timing Modules (if any) are active, as the
expected types and modes match with the existing types and modes.
NE# show hw-inventory
3.10.2
Adding a Card or an SCM
The CLI example below is written for multi-card NEs.
The CTR 8611 router contains two slots for SCMs, of which slot SCM2 is the working slot and
SCM1 is the protecting slot. The CLI commands shown below are also used for adding a
Switching and Control Module.
In this example, install a protecting CDC physically to slot 1.
Step 1
Check the card status.
The show CLI command indicates that card 1 exists, but it is an extra card that does not
belong to the inventory. It will remain inoperative until it is added to the hw-inventory.
NE# show hw-inventory slot 1
Step 2
Add a new card to the hw-inventory configuration.
After a while, card 1 is operational.
NE# hw-inventory slot 1 add unit clean-start
Step 3
Check the card status.
The show CLI command indicates that card 1 is part of the inventory and UP AND RUNNING.
All interface modules and Timing Modules (if any) are active, as the expected types and modes
match with the existing types.
20
AVIAT NETWORKS
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
NE# show hw-inventory slot 1
For the NE timing mode configuration, refer to Aviat CTR 8600 Router Hardware Installation
Guide.
3.10.3
Removing a Card or an SCM
The C T R 8611 router contains two slots for SCMs, of which slot SCM2 is the working slot
and SCM1 is the protecting slot. The CLI commands shown below are also used for adding a
Switching and Control Module.
Step 1
Remove a useless card from the hw-inventory configuration.
NE# hw-inventory slot 9 remove unit
Step 2
When card 9 is restarted, check the card status.
The show CLI command indicates that card 9 exists, but it is an extra card that does not belong
to the inventory. The card in slot 9 remains inoperative and it can now be detached from the NE
if the active software is ESW version 2.11.xxx or lower.
NE# show hw-inventory slot 9
The card (SCM in slot 1 or line card) does not have to be present to be removed from the
HW inventory if it is not used as a node timing source or in ELP/APS1+1/MSP1+1
protection.
3.10.4
Changing Interface Module or ETSI/ANSI/DSL Mode
Step 1 Set the expected interface module type and mode to the HW inventory configuration.
If only the module mode was changed, you need to reboot card 5 (use the CLI command
reload-sw slot 5).
NE# hw-inventory slot 5 add module 0 type 1*ch-STM-1 ansi
Step 2 Use this CLI command only if the module type has to be changed and the active ESW version is
FP3.0 (3.0.100) or higher. Wait until the red (Local Alarm) and yellow (Remote Alarm) LEDs
are blinking before detaching the card from the NE. Change the interface module to another
type of a module. Insert line card 5 back to the NE.
NE# esw-shutdown slot 5
Step 3 When card 5 is started, check the card status.
The show CLI command indicates that the interface module existing type matches with the
expected type, and it is active.
NE# show hw-inventory slot 5
260-668268-004
DECEMBER 2014
21
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
3.10.5
Adding a Line Module
This example describes adding a Line Module (LM) in the CTR 8611 router.
This procedure applies to all line modules except for 8x10/100BASE-TX
81.86LFETX82243-R6 Rev. D or higher and 8xchE1/chT1 81.86LE1T082242-R6 Rev. D or
higher.
Step 1
Check the hw-inventory configuration. The show CLI command indicates which LM
positions are empty.
NE# show hw-inventory details
Step 2
Add a new T1/E1 LM in module position 3 to the inventory configuration. The successful
execution of this CLI command raises an Expected Module Not Activated alarm.
NE# hw-inventory add module 3 type 8*chE1/chT1-LM etsi
Step 3
Check the hw-inventory configuration. The show CLI command indicates which LMs are not
active
(i.e. the expected types and modes do not match with the existing types and modes).
NE# show hw-inventory details
Step 4
NE power shutdown sequence is as follows:
– esw-shutdown will shut down ESW gracefully in a controlled fashion prior to powering
off the NE.
– Power off the NE before inserting a new module.
– Insert the new module in the NE.
– Power on the NE.
The successful execution of this sequence clears the Expected Module Not Activated alarm.
NE# esw-shutdown whole-ne
Step 5
Check the hw-inventory configuration. The show CLI command indicates which LMs are
active
(i.e. the expected types and modes match with the existing types and modes).
NE# show hw-inventory details
3.10.6
Removing a Line Module
This example describes removing an activated Line Module (LM) from the CTR 8611 router.
This procedure applies to all line modules except for 8x10/100BASE-TX
81.86LFETX82243-R6 Rev. D or higher and 8xchE1/chT1 81.86LE1T082242-R6 Rev. D or
higher.
Step 1
22
Check the hw-inventory configuration. The show CLI command indicates which LMs are
activated.
AVIAT NETWORKS
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
NE# show hw-inventory details
Step 2
Remove LM from the inventory configuration. The successful execution of this CLI
command raises a Removed Module Not De-Activated alarm.
NE# hw-inventory remove module 3
Step 3
Check the hw-inventory configuration. The show CLI command indicates which LMs are not
contained in inventory configuration but not de-activated (i.e. the expected types and modes do
not match with the existing types and modes).
Extract the LM from desired module position.
NE# show hw-inventory details
Step 4
This CLI command causes the NE to undergo a soft reset.
Subsequent to reset, the just removed LM is now de-activated in the NE's forwarding
hardware. The successful execution of this CLI command clears the Removed Module Not DeActivated alarm.
NE# reload-sw
Step 5
Check the hw-inventory configuration. The show CLI command indicates which LM positions
are empty.
NE# show hw-inventory details
3.10.7
Replacing a Line Module
This example describes replacing one type of Line Module (LM) with another type of LM. This
procedure is valid for the CTR 8611 router.
This procedure applies to all line modules except for 8x10/100BASE-TX 81.86LFETX82243R6 Rev. D or higher and 8xchE1/chT1 81.86LE1T082242-R6 Rev. D or higher.
Step 1
Check the hw-inventory configuration. The show CLI command indicates which interface
LMs are activated.
NE# show hw-inventory details
Step 2
Remove LM from the inventory configuration. The successful execution of this CLI
command raises a Removed Module Not De-Activated alarm.
NE# hw-inventory remove module 3
Step 3
Add a new Fast Ethernet LM in the same module position to the inventory configuration. The
successful execution of this CLI command raises an Expected Module Not Activated
alarm.
NE# hw-inventory add module 3 type 8*10/100BASE-TX-LM
Step 4
260-668268-004
Check the hw-inventory configuration. The show CLI command indicates which LMs are not
contained in the inventory configuration but not de-activated and which LMs are not active (i.e.
the expected types and modes do not match with the existing types and modes).
DECEMBER 2014
23
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
NE# show hw-inventory details
Step 5
NE power shutdown sequence as follows:
– esw-shutdown will shut down ESW gracefully in controlled fashion prior to powering off
the NE.
– Power off the NE before extracting / inserting modules.
– Extract an E1 / T1 LM from desired module position.
– Insert a Fast Ethernet LM into same module position.
– Power on the NE.
The successful execution of this sequence clears both the Removed Module Not DeActivated and the Expected Module Not Activated alarms.
NE# esw-shutdown whole-ne
Step 6
Check the hw-inventory configuration. The show CLI command indicates which LMs are
active
(i.e. the expected types and modes match with the existing types and modes).
NE# show hw-inventory details
3.10.8
Adding a High Speed Module
This example describes adding a High Speed Module (HM) to a CTR 8611 router configured
for 1+1 SCM protection with SCM 2 active.
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.
Step 1
Check the hw-inventory configuration. The show CLI command indicates that both SCMs
are part of the inventory and UP AND RUNNING with SCM 2 active. It also indicates which
HM positions (4..6) (and LM positions (0..3)) are empty.
Insert a new electrical Gigabit Ethernet High Speed Module (HM) into empty module position 4
in the NE.
NE# show hw-inventory details
Step 2
Add a new electrical Gigabit Ethernet HM in module position 4 to the inventory configuration.
The successful execution of this CLI command raises an Expected Module Not Activated
alarm.
NE# hw-inventory slot 2 add module 4 type 4*10/100/1000BASE-T
Step 3
Check the hw-inventory configuration. The show CLI command indicates that both SCMs are
part of the inventory and UP AND RUNNING with SCM 2 active. It also indicates which HMs
(and LMs) are not active (i.e. the expected types and modes do not match with the existing types
and modes).
NE# show hw-inventory details
Step 4
24
This CLI command causes the passive SCM to undergo a soft reset.
Subsequent to reset, the newly added HM is now activated in the forwarding hardware of
the passive SCM.
AVIAT NETWORKS
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
NE# reload-sw slot 1
Step 5
This CLI command causes the passive SCM to become the active SCM. Subsequent to its
execution the previously active SCM will automatically reset and become the newly passive
SCM. The successful execution of this CLI command clears the Expected Module Not
Activated alarm.
NE# protection manual-switchover unit scm slot 1
Step 6
This CLI command causes the passive SCM to become the active SCM. Subsequent to its
execution the previously active SCM will automatically reset and become the newly passive
SCM and the newly added HM is now activated in the forwarding hardware of the active
SCM.
NE# protection manual-switchover unit scm slot 2
Step 7
Check the hw-inventory configuration. The show CLI command indicates that both SCMs are
part of the inventory and UP AND RUNNING with SCM 1 is now active. It also indicates
which HMs (and LMs) are active (i.e. the expected types and modes match with the existing
types and modes).
NE# show hw-inventory details
3.10.9
Removing a High Speed Module
This example describes removing an activated High Speed Module (HM) from a CTR 8611 router
configured for 1+1 SCM protection with SCM 2 active.
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.
Step 1
Check the hw-inventory configuration. The show CLI command indicates that both SCMs are
part of the inventory and UP AND RUNNING with SCM 2 active. It also indicates which
interface HMs (and LMs) are activated.
NE# show hw-inventory details
Step 2
Remove HM in module position 4 from the inventory configuration. The successful
execution of this CLI command raises a Removed Module Not De-Activated alarm.
NE# hw-inventory slot 2 remove module 4
Step 3
Check the hw-inventory configuration. The show CLI command indicates that both SCMs are
part of the inventory and UP AND RUNNING with SCM 2 active. It also shows which HMs
(and LMs) are not contained in the inventory configuration but not de-activated (i.e. the
expected types and modes do not match with the existing types and modes).
Extract the HM to be replaced from module position 4.
NE# show hw-inventory details
Step 4
This CLI command causes the passive SCM to undergo a soft reset.
Subsequent to reset, the newly removed HM is now de-activated in the forwarding hardware
of the passive SCM.
NE# reload-sw slot 1
260-668268-004
DECEMBER 2014
25
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
Step 5
This CLI command causes the passive SCM to become the active SCM. Subsequent to its
execution the previously active SCM will automatically reset and become the newly passive
SCM. The successful execution of this CLI command clears the Removed Module Not DeActivated alarm.
NE# protection manual-switchover unit scm slot 1
Step 6
This CLI command causes the passive SCM to become the active SCM. Subsequent to its
execution the previously active SCM will automatically reset and become the newly passive
SCM and the newly removed HM is now de-activated in the forwarding hardware of the active
SCM.
NE# protection manual-switchover unit scm slot 2
Step 7
Check the hw-inventory configuration. The show CLI command indicates that both SCMs are
part of the inventory and UP AND RUNNING with SCM 1 is now active. It also indicates
which HM positions (4..6) (and LM positions (0..3)) are empty.
NE# show hw-inventory details
3.10.10
Replacing a High Speed Module
This example describes replacing one type of High Speed Module (HM) with another type
of HM in a CTR 8611 r outer configured for 1+1 SCM protection with SCM 2 active.
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.
Step 1
Check the hw-inventory configuration. The show CLI command indicates that both SCMs
are part of the inventory and UP AND RUNNING with SCM 2 active. It also indicates which
interface HMs (and LMs) are activated.
NE# show hw-inventory details
Step 2
Remove HM in module position 4 from the inventory configuration. The successful execution of
this CLI command raises a Removed Module Not De-Activated alarm.
NE# hw-inventory slot 2 remove module 4
Step 3
Check the hw-inventory configuration. The show CLI command indicates that both SCMs are
part of the inventory and UP AND RUNNING with SCM 2 active. It also shows which
HMs (and LMs) are not contained in the inventory configuration but not de-activated (i.e.
the expected types and modes do not match with the existing types and modes).
Extract an electrical Gigabit Ethernet HM from module position 4.
Insert a replacement optical Gigabit Ethernet HM into module position 4.
NE# show hw-inventory details
Step 4
Add a new optical Gigabit Ethernet HM in module position 4 to the inventory configuration.
The successful execution of this CLI command raises an Expected Module Not Activated
alarm.
NE# hw-inventory slot 2 add module 4 type 4*100/1000BASE-X
26
AVIAT NETWORKS
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
Step 5
Check the hw-inventory configuration. The show CLI command indicates that both SCMs are
part of the inventory and UP AND RUNNING with SCM 2 active. It also shows which
HMs (and LMs) are not contained in the inventory configuration but not de-activated and
which HMs (and LMs) are not active (i.e. the expected types and modes do not match with the
existing types and modes).
NE# show hw-inventory details
Step 6
This CLI command causes the passive SCM to undergo a soft reset.
Subsequent to reset, the newly removed HM is now de-activated in the forwarding hardware of
the passive SCM.
NE# reload-sw slot 1
Step 7
This CLI command causes the passive SCM to become the active SCM. Subsequent to its
execution the previously active SCM will automatically reset and become the newly passive
SCM at which point the newly added HM has also activated its forwarding hardware. The
successful execution of this CLI command clears both the Removed Module Not DeActivated and the Expected Module Not Activated alarms.
NE# protection manual-switchover unit scm slot 1
Step 8
This CLI command causes the passive SCM to become the active SCM. Subsequent to its
execution the previously active SCM will automatically reset and become the newly passive
SCM and the newly added HM is now activated in the forwarding hardware of the active
SCM.
NE# protection manual-switchover unit scm slot 2
Step 9
Check the hw-inventory configuration. The show CLI command indicates that both SCMs
are part of the inventory and UP AND RUNNING with SCM 1 is now active. It also
indicates which HMs (and LMs) are active (i.e. the expected types and modes match with
the existing types and modes).
NE# show hw-inventory details
260-668268-004
DECEMBER 2014
27
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
4.0
Software Management
Software management is used for managing the embedded software in the Aviat CTR 8600
system. It provides functions for uploading one or more separate software images to the NE.
Depending on the available memory size every card can hold one or few different software
images. The user can freely choose any image to be activated.
Briefly, software management means
• Adding and removing application ESW files to/from the available ESW list. The files are
added using the FTP/SFTP protocol. The NE supports FTP/SFTP file transfer but at the remote
terminal end a separate FTP/SFTP client is necessary, in addition to the Telnet terminal program
for CLI.
• Maintaining stability information about the used application ESW versions. Software
management verifies that a file is a valid application ESW binary, that it has not caused too
many malevolent resets, and that it is compatible with the HW.
• Choosing an application ESW to start. The application ESW to start is either chose by
the user or, if software management determines that the application ESW is not stable enough,
mini- application ESW is chosen by software management.
• Loading and starting application ESW from the non-volatile memory.
• Checking that the expected software version is running on each card. If the active
software ver- sion is not correct, the card is not allowed to operate until the expected software
version is loaded and activated.
4.1
Software Packages
In addition to plain application ESW files, it is possible to upgrade the network element
with software package files. These files may contain application ESW for multiple card
types and possibly upgrades for the boot and mini-application ESW.
Software packages are downloaded and activated in the same way as the plain application ESW.
Since activating a package upgrades all cards of a network element, it may take a long time
(up to 10...15 minutes).
In the case of CTR8611 router the software package should be downloaded to the working
SCM application ESW directory: /flash/appl-sw/slot2.
The working SCM in slot 2 must be the active SCM.
4.2
Configuring Expected Application ESW to Be Used at Next Reset
The actual executable application ESW must be transferred with FTP/SFTP. Before using
FTP/SFTP, the server must be enabled (it is disabled by default). The following characterizes the
FTP/SFTP:
• The mode must be bin (i.e. downloading binary file).
• The transfer will fail if the file system is full, if the ESW directory quota is all used or if
the number of files in the ESW directory has reached its maximum (10).
28
AVIAT NETWORKS
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
Select the file which is transferred to the NE using FTP/SFTP and the target directory in the
NE according to following table. In the file name x.y.z refers to the ESW version number.
NE Type
File Name for ESW
Upgrade
Aviat 8602 router
Aviat 8611 router
sbz2755_x.y.z
pkg_8611_x.y.z
FTP Target Directory in
NE
/flash/appl-sw
/flash/appl-sw/slot2
A software package (PKG) is a file whose name starts with “pkg_” (e.g.
pkg_8620_3.1.103). The package may contain several ESWs for several cards, IFMs etc.
The application ESW must be activated and the card/NE must be reset before the new
application ESW is in use.
4.3
Expected Software and Automatic Software Loader
An expected software version is the last ESW version activated for the card. For empty card
slots, the expected software version is the version of the last activated ESW package, when
activation has been done using ESW version FP2.11 or higher. If there is no expected software
for a card slot, then any ESW running in the target card is accepted. The expected software
version is kept on the non-volatile memory of SCM for all card slots of the NE (in case of Aviat
8611 router).
The ESW version of the replacement card and ESW version of a new card, when added to the
HW inventory, is automatically checked against the expected ESW version. If the active ESW
version is not correct, the card is not allowed to operate. The software autoloader makes a search
for the expected ESW version in all cards of the NE and, if found, the software will
automatically be loaded and activated.
If a card which belongs to the HW inventory is not a replacement card but has a wrong ESW
version, the card is not allowed to operate. This is most probably due to some rare error situation
and the expected ESW version will not be automatically activated. In this case, operator actions
are needed to resolve the conflict.
The current state of the expected vs. active ESW can be followed using the show hw-inventory
CLI command.
Example 1:
Step 1
The active ESW version of a replacement card is wrong. The autoloader has found the
expected ESW version in slot 7 and is loading it. The correct ESW version will automatically
be activated. The CLI output is shown below.
8630.14# show hw-inventory slot 8
unit in slot 8 is part of inventory and WAITING FOR START
PERMISSION
-->UNIT START PERMISSION DENIED!
1) Autoloader:
card is running wrong ESW version expected SW:
lbz2713_2.11.29 (loading SW src:7, 20%)
active SW is wrong:
lbz2713_2.10.181
260-668268-004
DECEMBER 2014
29
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
Example 2:
Step 1
The autoloader is not able to resolve the conflict. The CLI output is shown below.
8630.14# show hw-inventory slot 8
unit in slot 8 is part of inventory and WAITING FOR START
PERMISSION
-->UNIT START PERMISSION DENIED!
-->WRONG ESW VERSION! POSSIBLE RESET-LOOP: OPERATOR ACTIONS
NEEDED!
1) Autoloader:
card is running wrong ESW version expected SW:
lbz2713_2.11.29
active SW is wrong:
lbz2713_2.10.181
4.4
ESW Shutdown before Removing Card(s) or Switching NE Power off
After the shutdown command, power off is needed for the target card(s) to resume normal
operation.
Management connection to the NE is lost if the inband management connection goes
through the target card, and always in case of shutdown of the whole NE!
The "esw-shutdown" CLI command is used before removing card(s) or switching the NE
power off. The shutdown is used to:
• Confirm all configurations are flushed to the non-volatile and backup memory.
• Avoid disturbance of other cards in case one card is removed.
The CLI command:
router# esw-shutdown { whole-ne | slot <slot#> }
Wait until the red (Local Alarm) and yellow (Remote Alarm) LEDs are blinking in all target
cards before switching the power off or removing the card.
4.5
Software Management CLI Configuration Examples
CTR 8611 router contains two slots for SCMs, of which slot SCM2 is the working slot: if
only one SCM is used, it must be installed in slot SCM2.
The CLI commands shown below are the same for all NEs.
30
AVIAT NETWORKS
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
4.5.1
Taking Application ESW into Use in NE
Before it is possible to activate an application ESW, it must exist in the application ESW
directory.
Step 1
Delete the old unused ESW files of all cards to free flash space. This CLI command does
not delete active ESW files.
router# delete slot * flash:
Step 2
*
The FTP server is disabled by default. Before using FTP the server must be enabled. After this
step FTP can be used to download a new application ESW to any card. Download software
package to the NE directory as follows:
In CTR 8611 router check that the SCM in slot 2 is the active SCM:
router# show protection unit scm
If needed, use the following CLI command to switch SCM activity:
router# protection manual-switchover unit scm slot 2
Download software package to the SCM directory: /flash/appl-sw/slot2.
router(config)# ftp-server enable
Step 3
Disable the FTP server.
router(config)# no ftp-server enable
Step 4
Step 5
Activate the ESW package. A new ESW is copied and activated to all cards in NE. The
ESW will be used after next reset of a card. If you are NOT performing non-service affecting
upgrade, use the reload option in the CLI command above to force reset of all cards
immediately.
router(config)# boot system slot 14 flash: pkg_2.11.804
Display which application ESW is active, inactive, becoming active or backup.
router# show sw-version
Step 6
4.5.2
After the application ESW has been activated, the card must be reset to get the new application
ESW running. It can be done with this CLI command. This CLI command is not needed if you
used the reload option of the earlier CLI command or if you did not activate the application
ESW but only the boot and/or mini-application ESW.
router# reload-sw slot <N>
Using Configuration Backup and Restore
Configuration backup and restore can be used with ESW packages as well as with a single card
update. The operation requires enough free flash space to succeed.
Step 1
Download a new ESW package to the NE according to instructions in chapter 3.5.1 Taking
Application ESW into Use in NE.
Step 2
Activate the application ESW.
Option backup-config refers to the previous ESW version and configuration is saved and will
automatically be returned if errors are detected during the ESW upgrade. Option force can
260-668268-004
DECEMBER 2014
31
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
be used to force an update regardless of errors.
router(config)# boot system slot 1 flash:
pkg_8660_4.0.120 backup-
config reload
Step 3
If the previous ESW needs to be restored, download the previous ESW package to the NE
according to instructions in chapter 3.5.1 Taking Application ESW into Use in NE.
Use the restore-config option to restore the previous application ESW and its configuration.
router(config)# boot system slot 1 flash:
pkg_2.11.804 restore-
config reload
32
AVIAT NETWORKS
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
5.0
5.1
SCM 1+1 Equipment Protection
Overview
The CTR 8611 router supports the protection of important NE-level capabilities via the
protected SCM pair. If there is an SCM in both slot 1 and slot 2 and if both of them are members
of the NE inventory, protection is automatically on. The protected system capabilities supported
by SCM 1+1 equipment protection are as follows:
•
•
•
•
•
•
•
•
Forwarding functions and protocols
Signaling functions and protocols
Management functions, protocols and interfaces
System alarm interfaces
System status indicators
Station clock interfaces
Backup of configuration data
Non-service affecting software upgrades
The CTR 8611 router can operate in non-protected mode with only a single SCM in operation. In
non-protected operation, the only SCM in the NE is placed in slot 2 and is a member of NE
inventory. In non-protected mode, the system capabilities listed above will no longer be
protected / possible.
5.1.1
Manual SCM Protection Switchover
Manual switchover is performed by the user to change the active SCM side. Protection
switchover is possible when both SCMs are in equal protection states. Factors that affect the
SCM protection states are the start-up permission of the module, faults in the NE, software
types being run and the presence of the module.
Manual switchover should not be needlessly used, as it may temporarily disturb the
forwarding 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.
5.1.2
Automatic SCM Protection Switchover
If the protection state of the active SCM is degraded and the state of the other SCM is not,
the result is an immediate protection switchover to the other SCM. The automatic protection
switchover is non-revertive, i.e. if protection state degradation disappears, a new switchover
will not take place automatically.
260-668268-004
DECEMBER 2014
33
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
5.2
Forwarding Functions and Protocols
The forwarding functions and protocols of the CTR 8611 router propagate service bearing
traffic across its transport interfaces. Each protected SCM hosts a concurrent copy of the same
forwarding functions and protocols as are also hosted by its mate SCM. An ingressing service
bearing packet is presented concurrently to both SCMs. The forwarding function(s) of the
active SCM dominate and will be allowed to egress the packet over the selected transport
interfaces of the NE. The same packet presented by the forwarding function(s) of the passive
SCM will be discarded before it can egress the same selected transport interface(s). This
mechanism, along with the mechanisms as described for signaling functions and protocols,
ensure the maintenance of the forwarding continuity across the CTR 8611 router with minimal
disruptions.
5.3
Signaling Functions and Protocols
The signaling functions and protocols of the CTR 8611 router maintain state and continuity
of network forwarding functions and protocols. The signaling functions of the CTR 8611 router
communicate with network peers via signaling protocols across transport interfaces. Each
protected SCM hosts a concurrent copy of the same signaling functions and protocols as are also
hosted by its mate SCM. An ingress signaling packet is presented concurrently to both SCMs.
Only the signaling functions of the active SCM will be allowed to egress signaling packets
over the transport interfaces of the NE. The active SCM also communicates forwarding table
changes to the passive SCM to maintain forwarding table continuity in the event of a SCM
protection switchover. Subsequent to SCM protection switchover, signaling protocols utilize
graceful restart mechanisms to ensure the latest protocol states are utilized from NE signaling
peers. In this fashion the forwarding functions and protocols within t h e CTR 8611 router
are maintained with minimal disruptions subsequent to SCM protection switchovers.
The signaling protection mechanism described above is utilized as the implementation basis
for minimal disruption and continuity of the following protocols.
• 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
34
AVIAT NETWORKS
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
• RSVP-TE
• Method of protection: Internal protection of RSVP-TE 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 SCM suffered from a temporary failure only, having protected SCMs
is useful because protocol restart is always remarkably faster if another SCM is ready at the
time of a failure of the other SCM than if the NE were equipped with a single SCM only.
5.3.1
5.4
5.4.1
References
Feature
Description
[draft-ietf-idrrestart]
[RFC3478]
[RFC3623]
draft-ietf-idr-restart-13.txt (2006–07), Graceful restart
mechanism for BGP
RFC3478 (2003–02), Graceful restart mechanism for label
distribution protocol
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
Management Functions, Protocols, and Interfaces
Management Ethernet Port Protection
Each SCM hosts a single management 10/100/1000BASE-TX Ethernet port (designated
“MGMT”) for management traffic of the CTR 8611 router. Therefore, the MGMT port is
protected if the SCM is protected with one of the MGMT ports being active and the other
MGMT port being passive. The protected MGMT ports share the same configuration except
for the MAC address that is unique to each MGMT port. The status information, fault reports
and counters are gathered separately for both MGMT ports. Depending on the line status
and the equipment status of the SCMs, one of the two MGMT ports is active passing the
traffic through while the passive MGMT drops the traffic in both directions.
The MGMT port protection switching can function independently of the SCM protection
switching with the active MGMT port being hosted by either the active or passive SCM as
long as that hosting SCM is in a non-faulted, operational state. The configuration of which
MGMT port is active can be configured independently via BMP action or CLI commands. In
the case of MGMT ports. In addition to commanded MGMT port protection switchovers, a
MGMT port switchover may also be automatically initiated due to SCM protection switchovers
as well.
260-668268-004
DECEMBER 2014
35
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
Aviat CTR 8611 Router Interface Configuration Guide contains information about how to
configure MGMT ports. The same document also describes how you can see information
about the MGMT protection status.
5.4.2
Console Port Protection
Each SCM supports a single RS-232 serial port (designated “Console”) using an RJ-45
connector for management traffic of CTR 8611 router. The protection of the Console port is
optional but automatic if the SCM is protected with the active Console port always hosted
by the active SCM. The CLI commands received across the Console port hosted by the passive
SCM are discarded.
5.4.3
Management Functions
BMI, CLI, and SNMP are all supported across the active MGMT port and CLI only is
supported across the active Console port. If the protected SCM pair is used, the management
agents (BMI, CLI and SNMP) of CTR 8611 router are redundantly hosted by both SCMs
and thus protected and reachable even though one of the SCM modules fails. It may happen
that either the active MGMT / Console port are being hosted by a newly failed SCM in
which case an automatic MGMT / Console port protection switchover to the other MGMT
port hosted by the other SCM would be enacted.
During a MGMT port switchover event, BMP and SNMP messages may disappear briefly as the
Provision INM re-establishes management communication automatically across the newly
active MGMT port.
For both MGMT port and Console port switchovers however, CLI sessions will be terminated
automatically and the users must re-establish their sessions manually subsequent to the
completion of the switchover.
5.5
System Alarm Interfaces
Each SCM supports an external alarm input/output port (designated “ALM”) using an RJ-45
connector. The protection of the ALM port is optional but automatic if the SCM is protected
with the active ALM port always hosted by the active SCM.
36
AVIAT NETWORKS
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
5.6
System Status Indicators
Each SCM supports its own set of four status LEDs, the meaning of which depends on the
active/passive status of the hosting SCM as follows:
Indicators in Active SCM
LED Name
Color
States
Local Alarm
RED
ON indicates Major/Critical level NE alarm or that NE is in
reset state.
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
ON indicates Minor/Warning level NE alarm.
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
ON indicates that SCM is operating in the "active" role.
BLINKING indicates command induced verification of
Active Status LED operation.
OFF otherwise.
Indicators in Passive SCM
260-668268-004
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.
DECEMBER 2014
37
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
5.7
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 CTR
8611 router synchronization / timing function(s) regardless of the active/passive status of the
hosting SCM.
For more information on the network synchronization function in CTR 8611 router, see
Aviat CTR 8600 Router Synchronization Configuration Guide.
5.8
Backup of Configuration Data
If SCM 1+1 protection is configured on the CTR 8611 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.
5.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 CTR 8611 router avoids this downfall.
When SCM protection is in use, the standard procedure for the SCM software upgrade is as
follows.
Step 1
Download and activate a software package. Do not restart.
Step 2
Switch to the protecting SCM in slot 1.
Step 3
Restart the working SCM in slot 2.
Step 4
Wait until the working SCM in slot 2 is up and running again.
Step 5
Switch to SCM in slot 2 which now has the updated software.
Step 6
Restart the protecting SCM in slot 1.
Step 7 Wait until the protecting SCM in slot 1 is up and running again.
5.10 SCM Protection CLI Configuration Examples
This chapter provides SCM protection CLI configuration examples.
38
AVIAT NETWORKS
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
5.10.1
SCM Protection Information
Step 1
Show the module protection information when SCM protection is enabled.
router# show protection unit scm
5.10.2
Manual SCM Protection Switchover
Step 1
Turn the protection switch to the protecting SCM 1.
router# protection manual-switchover unit scm slot 1
260-668268-004
DECEMBER 2014
39
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
6.0
6.1
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 1
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 2
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: 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 9 is reported as missing from the NE:
router# show hw-inventory | include slot
in slot 1 is part of inventory and UP AND RUNNING
in slot 9 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 9 stay
continuously in "MISSING" state, there might communication problems.
Use Case 2: Line Card Has No Start Permission
Use the following command to display the inventory information in the console. In this example
the line card in slot 9 has no start permission:
router# show hw-inventory slot 9
in slot 9 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.
40
AVIAT NETWORKS
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
6.2
Checklist for Resolving ESW Incompatibility Issues
•
Check the boot and mini-application software version in all card slots. 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:
6:
boot SW gmz2710-03.04.000 3.4.0
mini-application SW gmz2711_4.1.466 4.1.466 Active.
system up-time 0 hours, 3 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.
260-668268-004
DECEMBER 2014
41
AVIAT CTR 8600 EQUIPMENT MANAGEMENT
Terms and Abbreviations
42
BFD
Bidirectional Forwarding Detection
BGP-4
Border Gateway Protocol version 4
BMI
Broadband Management Interface
BMP
Broadband Management Protocol. A communication protocol which is used
between CTR 8600 network elements and ProVision INM.
CLI
Command Line Interface
FE
Fast Ethernet
FP
Feature Pack
FTP
File Transfer Protocol
GE
Gigabit Ethernet
HM
High Speed Module
HW
Hardware
IP
Internet Protocol
IS-IS
Intermediate System to Intermediate System (Interior Gateway Protocol)
LDP
Label Distribution Protocol
LM
Line module
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
SDH
Synchronous Digital Hierarchy
SEC
Synchronous Equipment Clock
SNMP
Simple Network Management Protocol
STM
Synchronous Transfer Mode
SW
Software
Unit
In CLI refers to a card
VRRP
Virtual Router Redundancy Protocol
AVIAT NETWORKS