Tellabs Quick Guide

Page 1 of 28
Title Version
Tellabs 86xx Nodes / FLM Essentials 1.1 / Bern, 1.09.2010
Department Field Services Quick Guide Tellabs 86xx Nodes / FLM Essentials
Version Author Date
1.1 M. Iseli / S. Iff Bern, 01.09.2010
Date of change 1.09.2010
From Version 1.0
To Version 1.1
Person Iseli
Reason Commands Update
The material contained within this documentation is legal property of Alcatel - Lucent Switzerland AG and may not be copied, reproduced or published by any methods without prior written permission of Alcatel Lucent Switzerland AG.
Page 2 of 28
Title Version
Table of contents
1Available Racks.................................................................................................................... 3 1.1 8630 Access Switch ...................................................................................................... 3 1.2 8660 Edge Switch ......................................................................................................... 3 2 Cards for 8630 and 8660 Nodes .......................................................................................... 4 2.1 Card Slots ..................................................................................................................... 4 2.2 Control and DC Power Card CDC................................................................................. 4 2.3 Interface Module Concentrator (IFC) ............................................................................ 5 2.4 Available IFMs ............................................................................................................. 5 2.5 Ethernet Interface Standards.......................................................................................... 6 2.6 Small Form Factors Pluggable ...................................................................................... 6 3 Installation and Maintenance Essentials ............................................................................... 8 3.1 ESD and Laser Safety ................................................................................................... 8 3.2 Basic Addressing .......................................................................................................... 8 3.3 Card swapping .............................................................................................................. 9 3.4 Replacing CDC Card .................................................................................................... 9 3.5 Replacing Air Filters................................................................................................... 10 3.6 Replacing Fan Modules............................................................................................... 12 4 Login Procedures, Connectivity and Commands ................................................................ 13 4.1 Starting Console session ............................................................................................. 13 4.2 CLI Command Structure ............................................................................................. 13 4.3 Basic Configuration, Hardware Inventory ................................................................... 15 4.4 Configuring Management Communication Links ........................................................ 16 4.5 Important Commands.................................................................................................. 19 4.6 Alarm related Commands............................................................................................ 20 5 Alarms and Alarm Handling .............................................................................................. 20 5.1 Fault Severity.............................................................................................................. 20 5.2 Alarm Types ............................................................................................................... 20 5.3 LEDs ......................................................................................................................... 21 5.4 Fault Status ................................................................................................................. 22 5.5 External Alarm Relays ................................................................................................ 22 5.6 System Message Logging............................................................................................ 22 6 Software Handling............................................................................................................. 23 6.1 Software Types ........................................................................................................... 23 6.2 Updating Element Software ........................................................................................ 23 6.3 Activating Element Software ...................................................................................... 24 7 Backups............................................................................................................................. 25 8 Terms and Acronyms......................................................................................................... 26
Tellabs 86xx Nodes / FLM Activities

This document is intended to serve as a quick overview of the 8630 and 8660 Tellabs Node family hardware and the most common FLM activities related to them. For more information please use together with the corresponding ALEX library.
Page 3 of 28
Title Version
1Available Racks
1.1 8630 Access Switch
1.2 8660 Edge Switch
Page 4 of 28
Title Version
2 Cards for 8630 and 8660 Nodes

2.1 Card Slots
For the 8630 Node, there are 6 slots of which 4 are available for the line cards with user traffic interfaces, and 2 for Control and DC Power Cards (CDC). The slots are positioned horizontally. The IFC slot numbers run from 6 to 9. The CDC slots are numbered 1 and 14. The control and DC-feed functionality has been combined into a single card in order to have as many slots as possible for line cards. CDC in the slot 14 is mandatory in all configurations. In the 8660 Node, there are 14 slots of which 12 (slots 2...13) are available for the line cards with user traffic interfaces. The two outermost slots (1, 14) are for Control and DC Power Cards (CDC). CDC in the slot 14 is mandatory in all configurations. Equipping slot 1 with another CDC depends on protection needs, however, it is highly recommended. All cards are hot-removable and hot-insertable. To change or install an interface module, the line card needs to be removed from the subrack.
2.2 Control and DC Power Card CDC

Control and DC Power Card is a basic element of the 8630 / 8660 access / edge switches. It provides control, DC power, NE synchronisation, external alarm interface, control inputs and a Ethernet interface for management. It is recommended that it is 1+1 protected, mandatory one card in slot 14. The redundant CDC is hot swappable. There are two variants: CDC1-A or B (memory configuration).
Page 5 of 28
Title Version
2.3 Interface Module Concentrator (IFC)

A line card consists of an Interface Module Concentrator (IFC) board and one or two IFMs. A pair of high-density connectors for each IFM carries communication between IFM and IFC. Well defined module interfaces make it easy to use various IFMs and design new IFMs as needed to address specific line side interfaces. Backplane connectors carry high speed data between IFCs in Tellabs 8630 access switch and Tellabs 8660 edge switch.
Interface Module Concentrator (IFC) is the basic element of the line card. There are two variants: IFC1-A or B (memory configuration).
IFC Equipped with Two 2x1000BASE-X IFMs
2.4 Available IFMs

An IFM located on IFC (slots M0 or M1), provides a physical connection to the network. Typically each media type has an own dedicated IFM. Currently supported media types are: 8x10/100BASE-TX (electrical RJ-45 connectors) 8x100BASE-X (SFP connectors) 2x1000BASE-X (SFP connectors) 8x1000BASE-X (SFP connectors) 2+6x10/100/1000BASE-COMBO: 2-port Gigabit Ethernet 1000BASE-X (SFP connectors) and 6-port 10/100/1000BASE-TX Ethernet (electrical RJ-45 connectors) 1xchSTM-1/chOC-3 Multiservice (SFP connectors) 4xSTM-1/OC-3 ATM (SFP connectors)
Page 6 of 28
Title Version
4xchSTM-1/chOC-3 Multiservice (SFP connectors) 8xSTM-1 / OC3 POS (SFP connectors) 4xSTM-4 / OC-12 POS (SFP connectors) 1xSTM-16 / OC-48 POS (SFP connectors) 24xchE1/chT1 Multiservice (Sofix connectors)
2.5 Ethernet Interface Standards

There are several known standards. Below find the most important designations: IEEE 802.3: describes a collection of various Ethernet standards IEEE 802.1q: describes the standard of VLAN tagged frames On copper (twisted pair) usually 2 pairs are used for the transmission; for 1000 Base T all 4 pairs are used. Physical Layers are (important examples): 10 Base T: 10 MBit/s over twisted pair 10 Base F: 10 MBit/s over fibre optic 100 Base TX: 100 MBit/s fast Ethernet over twisted pair 100 Base FX: 100 MBit/s fast Ethernet over fibre optic 1000 Base X: 1000 MBit/s Gigabit Ethernet over fibre optic 1000 Base SX: 1000 MBit/s Gigabit Ethernet over fibre optic (850nm) 1000 Base LX: 1000 MBit/s Gigabit Ethernet over fibre optic (1300nm) 1000 Base ZX: 1000 MBit/s Gigabit Ethernet over fibre optic (singlemode 1500nm) 1000 Base CX: 1000 MBit/s Gigabit Ethernet over coaxial cable 1000 Base T: 1000 MBit/s Gigabit Ethernet over twisted pair Other standards and conventions please find in Wikipedia or elsewhere.
2.6 Small Form Factors Pluggable

Optical Transceivers: Small Form-Factor Pluggable (SFP) optical transceivers are used in optical interfaces. For optical interfaces, LC connector type is used. Only Tellabs supplied and approved lasers should be used. If any other lasers or lasers from any other source than Tellabs are used, the use thereof will be solely at the customers risk, and the laser class, compatibility with the laser safety and EMC standards must be checked. When using an SFP with a high launch power in short distances, it may be required to decrease the launch power by using an online optical attenuator in order to meet the input power range. Electrical Transceivers: The Tellabs 8600 system uses Small Form-Factor Pluggable (SFP) transceivers also in some electrical interfaces. An SFP transceiver is a hot-swappable input/output device that links a port on a transceiver module with the network. For each application a certain type of SFP is required. The connector type of the Tellabs 8600 system electrical transceiver modules is RJ-45 or DIN. You can install or remove the SFP while the device is operating.
Page 7 of 28
Title Version
Page 8 of 28
Title Version
3 Installation and Maintenance Essentials

3.1 ESD and Laser Safety
Static electricity may damage the electronic cards or components causing complete or unrevealed failures which may activate with a delay. Observe the following guidelines: Always wear an ESD-preventive wrist or ankle strap when handling electronic components. Connect one end of the strap to an ESD jack or an unpainted metal component on the rack or subrack. Handle cards by the faceplates and edges only; avoid touching the printed circuit board and connector pins. Place any removed component on an antistatic surface or in an antistatic shielding bag. Avoid contact between the cards and clothing. The wrist strap only protects the card from electrostatic voltages on the body. Electrostatic voltages on clothing can still cause damage. Do not work with the equipment during lightning activity. Invisible laser radiation may be emitted from the aperture of the optical IFM port when no cable is connected or a protective cap is not in its place. Avoid exposure to laser radiation and do not stare into open apertures. Keep the fiber optic cable ends directed away from people. Keep the source of the laser radiation as far from your eyes as possible. The optical transceivers supplied by Tellabs are solely Class 1 lasers.
3.2 Basic Addressing

Generally subracks are counted from right to left. Example for slot 8: 100Base-X on right is called fe (fe8/0/0 to fe8/0/7) 1000Base-X on left is called ge (ge8/1/0 to ge 8/1/7) Loopback Interfaces are called lo0,lo1,lo2 and so on Lan management port (outband) is called mfe (mfe14/0)
1000Base-X section 1 6 7 8 9 14 100Base-X section 1 6 7 8 9 14
CDC (mfe1/0) slave Ge6/1/0 to ge6/1/7 Ge7/1/0 to ge7/1/7 Ge8/1/0 to ge8/1/7 Ge9/1/0 to ge9/1/7 fe6/0/0 to fe6/0/7 fe7/0/0 to fe7/0/7 fe8/0/0 to fe8/0/7 fe9/0/0 to fe9/0/7
CDC (mfe14/0) main
Page 9 of 28
Title Version
3.3 Card swapping

Replacing CDC or Line Card If you are going to remove the CDC from Tellabs 8660 edge switch/Tellabs 8630 access switch, first turn off the power switch, then detach the power cable and only after these actions, remove the CDC. Never keep the power cable connected to the CDC while it is out of its slot. Otherwise the CDC may cause bodily injury or damage to the part that it is touching. When a CDC card (CBB2026 or CBB2224) is replaced by another card, the HW version of a new card should be at least equal to the HW version of the previous card. After replacement, the HW version of the new card is saved as an expected HW version. If the replacement card is of older HW version than the previous card, start permission of the replacement card is denied. In most cases it is possible to accept an older HW version in inventory, for more information refer to Tellabs 8600 Managed Edge System Equipment Management Configuration Guide. In CDC 1+1 equipment protection both CDCs must be of the same variant type (CDC1-A or CDC1-B). In CDC 1+1 equipment protection CDCs may have different types of Timing Modules, i.e. ETSI SEC Timing Module (cmt2017-etsi-timing) and S3 Timing Module (cmt2228timing). However, in this case the expected type of Timing Module must be configured to cmt2017-etsi-timing and only the features of the cmt2017-etsi-timing can be used. Remove and replace the card from the subrack as instructed in chapter 3.1.2 Line Card and CDC Assembly of the Hardware Installation Guide depending on the hardware version in use. 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 network element without any need to manually configure it.
3.4 Replacing CDC Card

Before starting the operation, make sure that the CDC that you want to extract is not active: 1 Insert a PC with a serial port terminal to the active CDC management port. The active CDC is indicated by the green CDC status/Master LED in the front panel. 2 Alternatively, you can check the active CDC with a console using the following command: show hw Example: 3 If needed, move the card using the command: manual-switchover In the following example card 1 is extracted and it is active; the active CDC is moved to slot 14. UK_8630# protection manual-switchover unit cdc slot 14 4 Now move the console port to the active CDC. Now you can proceed to remove the CDC: 1 Switch off the power of the CDC that you are going to extract. 2 Remove the clock signal cable from the SCI port. 3 Remove the DC power cable from the CDC.
Page 10 of 28
Title Version
4 Use a Torx TX10 or Pozi Drive PZ2 screwdriver to unfasten the card screws. 5 Turn the blue latches outbound, placed on the top and the bottom of the card, to extract the card. 6 Remove the CDC from the shelf. 7 Insert the new CDC into the shelf. 8 Turn the blue latches placed on the top and bottom of the card inbound to fix the card. 9 Use a Torx TX10 or Pozi Drive PZ2 screwdriver to fasten the card screws. 10 Insert the clock signal cable to the SCI port. 11 Insert the DC power cable to the CDC and fasten the screws tightly. 12 Switch ON the power of the CDC. After having replaced the CDC, you can optionally check that it is booting. Type the following command: sh hw If the CDC was part of the inventory in the network element you will see: unit in slot 1 is MISSING from node but part of inventory the expected unit type is cbb2026 CDC1A(2026) timing module has expected type cmt2228-timing active type none existing type none The new CDC will sequentially go through the following steps: unit in slot 1 is part of inventory and STARTING BOOT SEQUENCE unit in slot 1 is part of inventory and BOOTING UP unit in slot 1 is part of inventory and UP AND RUNNING Now the card is available. It will take some minutes to synchronize the NE configuration with the active CDC. This activity is indicated by the blinking CDC status/RMTalm LED. The NE will be consistent when the LED is stable.
3.5 Replacing Air Filters

Maintain the air filters to ensure a continuous air flow into the subrack. The air flow restricted by dirty filters may result in an excessive rise of the temperature. Change the Tellabs 8600 network element air filter at least every six months. Be careful not to touch the rotating fans. Tellabs 8660 Edge Switch The air filter is below the fan modules. You can remove it without pulling out any of the fan modules. 1 Open the fan module front panel by lifting it up so that the upper edge is released. Subrack V3.0 also has screws to be loosened on the front panel. 2 Pull the air filter framework out of the subrack. 3 Insert a new air filter to its place. Close the fan module front panel and tighten the screws.
Page 11 of 28
Title Version
Tellabs 8630 Access Switch The air filter is on the left side of the subrack and fan modules. The air filter is inside the filter assembly. You can remove the air filter without pulling out any of the fan modules. 1 There are four Torx 10 screws holding the filter assembly on the left side of the Tellabs 8630 access switch subrack. They need to be unscrewed first. 2 Remove the filter assembly by pulling it from the handle on the front plate. 3 Hold the filter assembly so that the front panel is towards you with the texts upside down. 4 Slide the filter holder on top of the filter assembly towards you by helping with a screwdriver at the back, so that the plate slides from under the two perforated latches on the back side of the filter assembly. 5 Now the filter holder can be slid away from you in the opposite direction so that it is released from under the four side latches. 6 Remove the air filter, insert a new air filter by carefully placing it under the six latches 7 Slide the filter holder back under the side latches from back to front. Make sure that the two drawing holes of the filter holder are on the back side of the filter assembly and the drawing is upside. 8 Slide the filter holder all the way to the front of the filter assembly so that you can press the back side of the filter holder under the perforated latches on the back side of the framework. Then slightly move the filter holder backwards so that its drawing holes snap into the perforated latches. 9 Slide the filter assembly back into its place. The guide is on the left side of the fan modules. The fitting is tight, so some force is needed. 10 Take new standard screws from the filter package. The old screws should not be used if they are the original self-tapping screws. Otherwise they may damage the threads of the screw holes. Put all four screws on their places and tighten them.
Page 12 of 28
Title Version
3.6 Replacing Fan Modules

The fan propeller will continue rotating momentarily after extraction. Be careful not to touch the propeller before the rotation has stopped. Make sure you are using an ESD wrist strap. Replace the fan module as fast as possible. Make sure that the fan module is non-operational during the replacement for less than 2 minutes. Have a replacement fan module ready to be installed before removing the former module. In one fan failure, if possible, do not replace the fan module in high ambient temperature. Tellabs 8660 Edge Switch The fan modules and air filter can be replaced on the fly without disturbing the data traffic through the NE. The fan module must be replaced within three days from failure. Open the front panel by lifting it so that the upper edge is released. Subrack V3.0 also has screws to be loosened on the front panel. Pull the fan module clear of the subrack and lay it in a safe place. The fan is adhered to the network element subrack by a connector assembly. It will come loose with enough tractive force. You can use, for instance, a screw driver when extracting the fan module. Carefully bend from the lower edge. To replace the fan module, proceed as follows: 1 Hold the fan module with the fans on the upper side and the fan status LEDs on the right. 2 Place the fan module into the slot with the power connector first so that it rests on the subrack. Align the bottom guides. 3 Push the fan module into the slot until the power connector seats in the backplane. Make sure the sliding base goes under each latch. Make sure, especially when inserting the leftmost fan module, that the wires on the left side of the fan module go in smoothly. The fan should immediately start rotating, presuming the NE power is on. 4 Close the fan module front panel and tighten the screws. 5 Verify that the green LED is lit at each fan. Tellabs 8630 Access Switch The fan modules and air filter can be replaced on the fly without disturbing data traffic through the NE. The fan module must be replaced within three days from failure. There are four Torx 10 screws holding the filter assembly on the left side of the Tellabs 8630 access switch subrack. They need to be screwed off first. Remove the filter assembly by pulling it from the handle on the front plate. Because of tight fitting, enough tractive force is needed. Pull the fan module clear of the subrack and lay it in a safe place. The fan module can be pulled out by placing the fingers behind the metal handle in the front of the module having all the version stickers. The fan is adhered to the network element subrack by a connector assembly. It will come loose with enough tractive force. Replace the fan module as soon as possible.
Page 13 of 28
Title Version
To replace the fan module, proceed as follows: 1 Hold the fan module with the fans on the right side and the fan status leds at the bottom. 2 Place the fan module into the slot with the power connector first, so that it rests on the subrack. Align the left side guides. 3 Push the fan module into the slot until the power connector seats in the backplane. The fan should immediately start rotating presuming the NE power is on. 4 Slide the filter assembly back in its place. The guide is on the left side of the fan modules. The fitting is tight, so some force is needed. 5 Take new standard screws from the filter package. The old screws should not be used if they are the original self-tapping screws. Otherwise they may damage the threads of the screw holes. Put all four screws on their places and tighten them. 6 Verify that the green LED is lit at each fan.
4 Login Procedures, Connectivity and Commands

4.1 Starting Console session
Connect the serial port of the PC to the console port of the NE using the proper serial cable. Open Hyperterminal or other terminal program. Set COM port to the following settings: 38400Bps Databits:8 Parity:None Stopbits:1 Flowcontrol:None hit enter and you should see command prompt (router>)
4.2 CLI Command Structure

The CLI commands are divided into several command modes based on the functionality of the router. Each command mode has its own set of commands available for configuring and monitoring the router. The commands available to you at any given time depend on the mode you are in. Entering a question mark (?) at the router prompt allows you to obtain a list of commands available for each command mode.
Page 14 of 28
Title Version
Page 15 of 28
Title Version
4.3 Basic Configuration, Hardware Inventory

The hw-inventory contains an expected card type for each card slot in the NE and an expected module type for each module slot in a card. Generally, add-all-units is the first command that is given to the NE after it has been populated with a full set of hardware. After the hw-inventory is created, the NE is operational. By default add-all-units sets the CDC in slot 14 to the active card and the CDC in slot 1 to the protecting card. 1 Create a new hw-inventory configuration using the following command, select ETSI or ANSI mode according your needs. ETSI mode is the default mode. hw-inventory add-all-units clean-start hw-inventory add-all-units preconfigured
(keeps existing node configuration)
Like this, the hardware units are recognized. Specially if you have two CDCs, the second unit on slot 1 is sometimes not seen if this command is not entered. After a while, the NE is operational. Wait patiently until the Bootup Done message has been displayed for each card and the yellow Remote Alarm LED has stopped blinking in all cards. A green LED will be lit, indicating the card is now online. 2 Check that all the cards are part of the inventory, UP AND RUNNING, and that the expected and active module type match the existing type. Check also that the CDC in slot 14 is the active one. A green Master LED should be on in the active CDC. Press Enter and login to the element. Router>enable show hw-inventory 3 Configure the current UTC time and date to the network element. clock set as-utc 06:45:00 29 Aug 2007 Attention: month has to be a three letter English abbreviation with a capital first letter. 4 Generate and verify Crypto Key (if instructed to do so): crypto generate key 1 ssh2-dsa show crypto key After that, follow detailed instructions for inbound or outbound management according to manual and information from network planners. Most likely you will get a .txt file with a preconfiguration. Just copy and paste the .txt file into Hyperterminal and check for faults. It is advisable not to paste all the text at once, depending of the amount, it should be done in command groups or even single commands. For a complete list of commands, see ALEX or the CLI Commands Manual.
Page 16 of 28
Title Version
4.4 Configuring Management Communication Links

Once the NE is configured, it is time to create the communication between the NE and Communication Server. Outband and Inband Management There are three options for creating the communication to the network elements; inband, outband, and a combination of the two. In the case of outband management, the communication link is connected from the Communication Server straight to the NE or via an external Fast Ethernet switch. Inband management means that the communication to a NE is established from an existing NE. Proper network management usually requires, depending on the circumstances, much configuration that is not described in this installation guide. See, in particular, Tellabs 8600 Managed EdgeSystem Management Communications Configuration Guide. Configuring Outband Management This chapter describes the configuration steps required when establishing the communication to the first NE, between Communication Server and the NE. In this example the communication link is connected to the fixed Ethernet management port of Tellabs 8660 edge switch. The IP addresses used in this step are examples.
1 Enable configuration mode and check the existing configuration: router>enable router#show running configuration 2 Enter the NE hostname and IP address to the communication link port with the following commands: router#configure terminal router(config)#hostname N-PE 10 N-PE 10(config)#interface mfe14/0
Page 17 of 28
Title Version
N-PE 10(cfg-if)#ip address 192.168.10.10/24 N-PE 10(cfg-if)#description link to Communication Server 3 Activate the link: N-PE 10(cfg-if)#no shutdown N-PE 10(cfg-if)#exit A green LED will be lit within the interface in question indicating that the interface is now online. 4 Add a static route towards the management LAN by entering the following command: N-PE 10(config)#ip route 172.19.137.0/24 192.168.10.254 5 Test communication to the Communication Server with ping: N-PE 10(config)#exit N-PE 10#ping 192.168.10.254 (Communication Server LAN adapter) 6 Enter a static route to the node elements in the Workstation: C:\>route add 192.168.10.0 mask 255.255.255.0 172.19.137.254 p 7 Enable the communication between the network element and Communication Server: N-PE 10(config)# bmp-server enable Once the IP address has been assigned to the interfaces and the static routes have been added to the NE and the Management System, you can communicate remotely by Telnet over an Ethernet network.
Configuring Inband Management This chapter describes the configuration steps required when establishing the communication to a new network element from an existing NE (between N-PE 20 and N-PE 10). After outband management is configured according to the previous example in N-PE 10, the following configurations must be added in the NEs to enable inband management to N-PE 20 through N-PE 10. In this example OSPF is used and IGP protocol to establish routing connectivity. The Tellabs 8600 system supports also other routing protocols, for example IS-IS, which can be used for route distribution. N-PE 10 1 Enter the loopback IP address: N-PE 10>enable N-PE 10#configure terminal N-PE 10(config)#interface lo0 N-PE 10(cfg-if)#ip address 10.123.100.10/32 N-PE 10(cfg-if)#no shutdown N-PE 10(cfg-if)#exit 2 Enter the communication link port IP address: N-PE 10(config)#interface fe9/1/0 N-PE 10(cfg-if)#description link to N-PE 20 N-PE 10(cfg-if)#ip address 10.123.10.1/30 N-PE 10(cfg-if)#no shutdown N-PE 10(cfg-if)#exit 3 Configure the OSPF: N-PE 10(config)#router ospf1 N-PE 10(cfg-ospf[1])#ospf router-id 10.123.100.10
Page 18 of 28
Title Version
N-PE 10(cfg-ospf[1])#network 192.168.10.0/24 area 0.0.0.0 (address of the management network) N-PE 10(cfg-ospf[1])#network 10.123.10.0/30 area 0.0.0.0 (address of the network between the elements) N-PE 10(cfg-ospf[1])#network 10.123.100.10/32 area 0.0.0.0 (NE loopback address) N-PE 10(cfg-ospf[1])# redistribute static
N-PE 20 1 Enter the hostname for the NE if not given yet: router(config)#hostname N-PE 20 2 Enter the loopback IP address: N-PE 20>enable N-PE 20#configure terminal N-PE 20(config)#interface lo0 N-PE 20(cfg-if)#ip address 10.123.100.20/32 N-PE 20(cfg-if)#no shutdown N-PE 20(cfg-if)#exit 3 Enter the communication link port IP address: N-PE 20(config)#interface fe8/1/0 N-PE 20(cfg-if)#description link to existing element N-PE 10 N-PE 20(cfg-if)#ip address 10.123.10.2/30 N-PE 20(cfg-if)#no shutdown N-PE 20(cfg-if)#exit 4 Configure the OSPF: N-PE 20(config)#router ospf1 N-PE 20(cfg-ospf[1])#ospf router-id 10.123.100.20 N-PE 20(cfg-ospf[1])#network 10.123.10.0/30 area 0.0.0.0 (address of the network between the elements)
Page 19 of 28
Title Version
N-PE 20(cfg-ospf[1])#network 10.123.100.20/32 area 0.0.0.0 (NE loopback address) 5 Enter a static route to the node elements in the Workstation: C:\>route add 10.123.100.0 mask 255.255.255.0 172.19.137.254 -p 6 Enter a static route to the node elements in the Communication Server: C:\>route add 10.123.100.0 mask 255.255.255.0 192.168.10.10 -p 7 Now you should be able to ping and Telnet the loopback addresses of both NEs, N-PE 10 and N-PE20 from a Workstation or the Communication Server: C:\>ping <NE loopback address> 8 Enable the communication between the network element and Communication Server. N-PE 20(config)# bmp-server enable Management Traffic QoS The outgoing management traffic QoS can easily be selected using the command: (config)#mgmt-traffic qos Using this command the operator can select which QoS class outgoing management traffic uses (mgmt-traffic qos affects the following protocols: CLI, BMP, including CCN, SNMP and syslog packets). The default QoS value for management traffic is CS7.
4.5 Important Commands

List of important commands:
Command ? Help ^c show hw-inventory show interface fe8/0/0 show ip interface brief Show ip route show sw-version show flash Show run Enable configure terminal ip interface xxx.xxx.xxx.xxx/xx no ip interface xxx.xxx.xxx.xxx/xx no shutdown-if; no shutdown shutdown shutdown-if snapshot-config create flash: snap101.zip snapshot-config restore flash: snap101.zip protection manual-switchover unit cdc slot 1 ftp-server enable bmp-server enable hw-inventory add-all-units clean-start etsi Exit
Show possible commands to continue Shows help for commands Stops command execution Status of all installed units, HW Status of FE interface 8/0/0; detail view Shows all IP interfaces, short display version Shows IP routes Shows SW versions Shows content of flash Shows the running configuration Enter the priviledged mode Enter the configure mode Set IP address + mask (/xx) of selected module Removes the ip address on selected interface Switch on interface Switch off interface between layer 2+3 Switch off interface on layer 1, clears the alarms on the unused interfaces Create Backup Restore Backup CDC active switching from slot 14 to slot 1 Enable FTP server (important for FTP tasks) Protocoll between management and Node First command to perform in a new Node Go back to next level / exit
Page 20 of 28
Title Version
4.6 Alarm related Commands

router# show faults active router# show faults history slot 14 router# show faults active slot 8 fault-group interface severity critical router# show faults history slot 8 | block "ge8/0/1" router# terminal monitor router# terminal monitor severity warning Show all currently active faults in the NE Show the fault history of card 14 (fault history is card-specific) You can filter active and history faults e.g. by card, fault group, severity, time, etc You can also use the output filter; in this example only the faults related to interface ge8/0/1 are shown Activate the system message logging in the CLI terminal Define the lowest event severity that will be logged (events with lower severity will not be shown) Define the address for the syslog server and the lowest event severity to be sent to the server Enable the syslog feature.
router(config)# logging syslog host 172.19.101.105 warning router(config)# logging syslog enable
5 Alarms and Alarm Handling

5.1 Fault Severity
Each fault (or event) has a predefined severity: Critical Major Minor Warning Informational (Debug) In Tellabs 8630 access switch and Tellabs 8660 edge switch the NE state LEDs in CDC reflect the severity of the currently active faults in the NE. Some faults are service affected, that is they break traffic or have major impact on service quality.
5.2 Alarm Types

Each fault has a predefined alarm type in one of the following categories: com = communication alarm type qos = quality of service alarm type pro = processing error alarm type equ = equipment alarm env = environmental alarm int = integrity violation ope = operational violation phy = physical violation sec = security service or mechanism violation
Page 21 of 28
Title Version
5.3 LEDs
A fault might light a card state and/or interface state LED. The possible consequences are: No led Yellow led (error detected but fault cause not in this card or NE) Red led (error detected in this card) In Tellabs 8630 access switch and Tellabs 8660 edge switch, also the NE state LEDs in CDC might be lit. NE Status LEDs on CDC Critical RED Major RED Minor/Warning YELLOW Battery voltage GREEN Fan module voltage GREEN Card Status LEDs on CDC Local Alarm RED
ON ON ON ON ON
when one or more critical severity level card faults when one or more major severity level cards faults when one or more minor or warning severity level cards faults when battery voltage is OK when fan module voltage is OK
ON BLINKING ON BLINKING during following operations: ON
Remote Alarm YELLOW
Active/Master GREEN
BLINKING LEDs on IFCs / IFMs Local Alarm RED
when CDC itself has a fault or not in inventory when manually set to forced blinking. when online and CDC detects or suspects fault in some other network element or remote site. 1) Boot-up sequence 2) Inventory create 3) Inventory (backup) restoration 4) Manually set to forced blinking when CDC is online (it is up meaning successful boot-up sequence finished and start-up permission granted). Note that online CDC may still contain errors. when manually set to forced blinking
ON BLINKING ON BLINKING during following operations:
Remote Alarm YELLOW
On Line GREEN
ON BLINKING
when card itself has a fault or card is not in inventory when manually set to forced blinking when error detected in some other card 1) bootup sequence 2) inventory create 3) inventory (backup) restoration 4) manually set to forced blinking when card is active and in inventory when manually set to forced blinking
Page 22 of 28
Title Version
LEDs on Ethernet ports Link/Activity GREEN
ON BLINKING OFF ON
Online GREEN
when Ethernet link is up. when Ethernet link is up and there is transmit or receive activity. when Ethernet link is down. when administrative status for Ethernet interface is online. when manually set to forced blinking. when administrative status for Ethernet interface is shutdown or Ethernet link is down.
BLINKING OFF
5.4 Fault Status

The fault status (or fault state) is one of the following: On (fault is active) Off (fault is not active) Delta; for some faults, no specific on and off time can be defined. This describes some event. After a delta event, the fault state is off.
5.5 External Alarm Relays

Tellabs 8630 access switch and Tellabs 8660 edge switch have 4 fixed and 2 programmable external output relays and 8 (per CDC) external input relays. Tellabs 8605 access switch and Tellabs 8607 access switch have one fixed and one programmable external output relays and 4 external input relays. The external line status can be: Open - not connected to GND (ground) Closed - connected to GND (ground) The fixed external outputs are: If Critical output is closed, the Critical NE alarm is ON. If Major output is closed, the Major NE alarm is ON. If Minor/Warning output is closed, the Minor/Warning NE alarm is ON If power voltage output is on, power voltage (+48 V battery in CDC) is OK. The first three outputs act like NE state alarm LEDs. The programmable output line status and non-volatile behaviour can be set by the user. Each of the external input lines can be associated to the user-defined fault or pre-defined faults.
5.6 System Message Logging

Faults and other events cause corresponding human readable system messages. The messages can be stored into: CLI console (optional) Logging server using syslog protocol [RFC3164] (optional)
Page 23 of 28
Title Version
6 Software Handling
6.1 Software Types
There are three different software types: Example Node 8630 Bern Testbed: Boot Software. The boot software is able to detect faulty Element software and can initiate a fallback: 8: boot SW gmz2710-03.04.000 3.4.0 14: boot SW gmz2700-03.04.000 3.4.0 Mini Application Software. It is used to load new ESW in case of an emergency. It can be started by pressing m at startup: 8: mini-application SW gmz2711_2.8.191 2.8.191 Backup 14: mini-application SW gmz2702_2.8.191 2.8.191 Backup Element Software ESW: 8: /flash/appl-sw/slot8/lbz2713_2.9.206 2.9.206 Active OK 4457844. 14: /flash/appl-sw/slot14/cbz2712_2.9.206 2.9.206 Active OK 8796452.
6.2 Updating Element Software

Normally, the software will be updated remotely. However, the update can be done locally. There are two ways to update the Tellabs 8660 edge switch and Tellabs 8630 access switch application software. You can either upgrade the software on one card at a time or the whole NE in one go. When the whole NE is upgraded in one go, the application software package is downloaded into the active CDC. When the software package is activated, the software is automatically distributed into all cards of the network element. This requires that all cards have enough space in their flash memories. There are two different ways to do FTP transferring: Using Windows Explorer (or an FTP program) 1 Start Windows Explorer. 2 Open an FTP connection to the IP address of the target NE. For example, if the IP address is 192.0.2.15, clear the Explorer address field and type: ftp://192.0.2.15/ 3 Fill in username and password. Otherwise the FTP connection will be disconnected. 4 Check the existing application software (enter username and password if needed): ftp://192.0.2.15/flash/appl-sw/ 5 To select a slot, click it (114). 6 Open a new explorer window. Move to the directory of the transferable application software. 7 Drag the new application software to the FTP connected appl-sw sub-folder. Do not download incompatible application software. 8 If the transfer fails, it might indicate that the flash file system is full. Delete old application software by clicking the right mouse button and selecting delete. In Telnet session you can delete all unused application software versions with the CLI command: delete slot <slot number> flash: * 2. Repeat the steps from Step 7. The application software versions should be the same in every card.
Page 24 of 28
Title Version
Through Command Prompt Session 1 Start the Command Prompt. 2 Go to the directory where the new downloadable application software exists. Check that you have correct drive and path information. 3 Open an FTP connection to the target by typing: ftp 192.0.2.15 4 Fill in username and password, if they have been defined. Otherwise, press Enter and leave the options empty. The FTP connection will be closed by a remote host if the password query fails. 5 The following command path is needed: cd/flash/appl-sw/slot(1-14). 6 Download application software to the target. The following commands are needed. 1. Type bin and press enter. 2. Type hash and press enter. 3. Type put new application software name. 7 The new application software is transferred to the target. Do not download incompatible application software. 8 If the transfer fails, it might indicate that the flash file system is full. Delete the old application software by deleting the name of the deletable software, and start again from Step 6.
6.3 Activating Element Software

1 Connect to the target through console or Telnet connection. 2 Fill in username and password. Otherwise the connection will be disconnected. 3 To move to the PRIVILEGED EXECUTION level, type enable. 4 To check the existing software, type: show flash:
Page 25 of 28
Title Version
5 After checking, type configure terminal to go to the global configure terminal mode. 6 Type the following command for all slots (cards) which have been downloaded with the new application software: boot system slot [1-14] flash: Name of SW to activate 7 To return to the PRIVILEGED EXECUTION level, type exit. 8 To check the active software, type show sw-version. The activated application software should be in activated state after reset. Note: The application software versions should be the same in every card. Slots 1 and 14 are for control cards. Slots 213 in Tellabs 8660 edge switch and slots 69 in Tellabs 8630 access switch are for line cards. The control cards and line cards have different software. After activation, to reset the target, type: reload-sw The software is activated after recovery from the reset. 9 To go to the PRIVILEGED EXECUTION level, type exit. 10 To check the active software, type: show sw-version.
7 Backups
To create a complete backup of the unit, the command snapshot-config is used. First we need to create an interface for the FTP <> PC connection (IP addresses are examples):
enable configure terminal interface fe0/3 ip address 192.168.1.1/24 no shutdown
Then create the backup file with the following command:

snapshot-config create flash: snap101.zip
Set your PCs IP address to: 192.168.1.2 subnet 255.255.255.0 Gateway 192.168.1.1 Connect using WSFTP or another FTP programm Look for the file snap101.zip (normally under: /flash/snapshot-config) and transfer it to your PC. Replace now the Tellabs HW. On the new installed Tellabs configure again the interface for FTP connection using:
enable configure terminal ftp-server enable interface fe0/3 ip address 192.168.1.1/24 no shutdown
Now transfer the file back to /flash/snapshot-config using your FTP program, then enter:
snapshot-config restore flash: snap101.zip
Finally, you need to close the port used for FTP and delete snap:
interface fe0/3 no ip address 192.168.1.1/24 shutdown-if exit snapshot-config delete flash: snap101.zip
Page 26 of 28
Title Version
8 Terms and Acronyms

Terms AAL ARP ASIC ASN ATM Backbone BFD BGP-4 BMP BRAIN BSC CAC CCN CDC CE Router CES CESoPSN CLI CPU CS CSMA/CD DSL DWDM E1 E3 EEPROM EFM EMC EMI ERM ESD ESMC Ethernet, FE FIFO FLASH Frame Relay FTP, TFTP FTP
Term Explanation
ATM Adaptation Layer Address Resolution Protocoll Application Specific Integrated Circuit Access Service Network Asynchronous Transfer Mode High Speed Main Network Bidirectional Forwarding Detection Border Gateway Protocol version 4 Broadband Management Protocol. A communication protocol which is used between Tellabs 8600 network elements and Tellabs 8000 network manager. Broadband Routing ASIC for IP Networks. The basic building block part of all Tellabs 8600 network elements. Base Station Controller Connection Admission Control Configuration Change Notification Control and DC Power Card Customer Edge Router Circuit Emulation Service CES over Packet Switched Networks Command Line Interface Central Processor Unit Circuit Switched Carrier Sense Multiple Access/Collision Detect (used with Ethernet) Digital Subscriber Line Dense Wavelenth Division Multiplexing 2 MBit/s PDH Signal 34 Mbit/s PDH Signal Electrically Erasable Programmable Read Only Memory Ethernet in the First Mile Electromagnetic Compatibility ElectroMagnetic Interference Electromagnetic Compatibility and Radiospectrum Matters Electrostatic Discharge Ethernet Synchronization Message Channel Fast Ethernet; Signal with different data rates (10-100 Mbit/s) and a usual frame length of 1500 Bytes First In First Out memory Electrically erasable and programmable memory type "Old" Data Transmission Technology File Transfer Protocol, Trivial FTP Foil Shielded Twisted Pair
Page 27 of 28
Title Version
Gigabit Ethernet GE GND GPON GUI HDLC HSDPA HSUPA I2C IEEE IFC IFM IMA IP IS-IS ITU-T LDP LED LER Line card LSP LSR MAC ML-PPP MP-BGP MPLS MSP MSPP MS MTU NE NEBS NIC NRTL OAM OC3 OSPF PCML PDH PE Router PFC PHY PLL POS PPC
Signal over 1000 Mbit/s; carried usually on fibre (1000Base-LX/SX) or on copper (1000 Base-T) Ground Gigabit Passive Optical Network Graphical User Interface High Level Data Link Control (Layer 2) High Speed Downlink Packet Access High Speed Uplink Packet Access Bidirectional two-wire serial bus that provides a communication link between integrated circuits (IC's) Institute of Electrical and Electronics Engineers Interface Module Concentrator Interface Module Inverse Multiplexing for ATM Internet Protocol Intermediate System to Intermediate System (Interior Gateway Protocol) International Telecommunication Union - Telecom Standardization Sector Label Distribution Protocol Light-Emitting Diode Label Edge Router The line card in the Tellabs 8600 system consists of an Interface Module Concentrator (IFC) and up to two Interface Modules (IFMs). Label Switched Path Label Switch Router Media Access Control Sublayer of Data Link Layer Multi Link PPP (Point to Point Protocoll) Multiprotocol Border Gateway Protocol Multiprotocol Label Switching Multiplex Section Protection Multiservice Provisioning Platform Multiservice (Interface Module) Maximum Transfer/Transmission Unit Network Element Network Equipment Building Systems Network Interface Card Nationally Recognized Testing Laboratory Operation, Administration and Maintenance Optical Carrier Level 3 (Sonet) Open Shortest Path First Pseudo Current Mode Logic Plesiochronous Digital Hierarchy Provider Edge Router Power Factor Correction Circuit Physical Layer Device Phase Locked Loop Packet over SONET/SDH Power PC (processor)
Page 28 of 28
Title Version
PPP PSN PWE3 PWM QoS
Point-to-Point Protocol Packet Switch Network Pseudowire Edge to Edge Emulation Pulse Width Modulation Quality of Service. A way of guaranteeing a defined performance through the network. Implementation of QoS in the network means specific bandwidth, latency, jitter and loss guarantees per each traffic flow. Radio Access Network Request For Comments Routing Information Protocoll Reduced Instruction Set Computer Radio Network Controller Resource Reservation Protocol Traffic Engineering Real Time Clock Structure-Agnostic Time Division Multiplexing Station Clock Input Station Clock Output Synchronous Digital Hierarchy Synchronous Dynamic Random Access Memory Synchronous Equipment Clock Small Form-Factor Pluggable. Transceiver type used in Tellabs 8600 IFMs. Serving GPRS Support Node Simple Network Management Protocol Synchronous Optical Network Synchronization Status Messages Synchronous Transfer Mode Example: STM-1, Synchronous Transport Module, 155MBit/s Shielded Twisted Pair Transmission Control Protocoll Time Division Multiplexing; "old" transmission technology User Datagramm Protocoll Unspecified Bit Rate Variable / Constant Bit Rate ATM virtual channel Virtual Channel Connection Virtual Circuit Connectivity Verification Virtual LAN (Local Area Network) Virtual Path Virtual Private Network VPN Routing and Forwarding Table Weighted Fair Queueing Weighted Random Early Detection
RAN RFC RIP RISC RNC RSVP-TE RTC SATOP SCI SCO SDH SDRAM SEC SFP SGSN SNMP SONET SSM STM STM-N STP TCP TDM UDP UBR VBR / CBR VC VCC VCCV VLAN VP VPN VRF WFQ WRED

Tellabs Quick Guide

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Tellabs Quick Guide

Uploaded by

Copyright:

Available Formats

Page 1 of 28

Tellabs 86xx Nodes / FLM Essentials 1.1 / Bern, 1.09.2010

1.1 M. Iseli / S. Iff Bern, 01.09.2010

Date of change 1.09.2010

From Version 1.0

Reason Commands Update

Tellabs 86xx Nodes / FLM Essentials 1.1 / Bern, 1.09.2010

Tellabs 86xx Nodes / FLM Activities

Tellabs 86xx Nodes / FLM Essentials 1.1 / Bern, 1.09.2010

1.2 8660 Edge Switch

Tellabs 86xx Nodes / FLM Essentials 1.1 / Bern, 1.09.2010

2 Cards for 8630 and 8660 Nodes

2.2 Control and DC Power Card CDC

Tellabs 86xx Nodes / FLM Essentials 1.1 / Bern, 1.09.2010

2.3 Interface Module Concentrator (IFC)

IFC Equipped with Two 2x1000BASE-X IFMs

2.4 Available IFMs

Tellabs 86xx Nodes / FLM Essentials 1.1 / Bern, 1.09.2010

2.5 Ethernet Interface Standards

2.6 Small Form Factors Pluggable

Tellabs 86xx Nodes / FLM Essentials 1.1 / Bern, 1.09.2010

Tellabs 86xx Nodes / FLM Essentials 1.1 / Bern, 1.09.2010

3 Installation and Maintenance Essentials

3.2 Basic Addressing

CDC (mfe14/0) main

Tellabs 86xx Nodes / FLM Essentials 1.1 / Bern, 1.09.2010

3.3 Card swapping

3.4 Replacing CDC Card

Tellabs 86xx Nodes / FLM Essentials 1.1 / Bern, 1.09.2010

3.5 Replacing Air Filters

Tellabs 86xx Nodes / FLM Essentials 1.1 / Bern, 1.09.2010

Tellabs 86xx Nodes / FLM Essentials 1.1 / Bern, 1.09.2010

3.6 Replacing Fan Modules

Tellabs 86xx Nodes / FLM Essentials 1.1 / Bern, 1.09.2010

4 Login Procedures, Connectivity and Commands

4.2 CLI Command Structure

Tellabs 86xx Nodes / FLM Essentials 1.1 / Bern, 1.09.2010

Tellabs 86xx Nodes / FLM Essentials 1.1 / Bern, 1.09.2010

4.3 Basic Configuration, Hardware Inventory

(keeps existing node configuration)

Tellabs 86xx Nodes / FLM Essentials 1.1 / Bern, 1.09.2010

4.4 Configuring Management Communication Links

Tellabs 86xx Nodes / FLM Essentials 1.1 / Bern, 1.09.2010

Tellabs 86xx Nodes / FLM Essentials 1.1 / Bern, 1.09.2010

Tellabs 86xx Nodes / FLM Essentials 1.1 / Bern, 1.09.2010

4.5 Important Commands

Tellabs 86xx Nodes / FLM Essentials 1.1 / Bern, 1.09.2010

4.6 Alarm related Commands

5 Alarms and Alarm Handling

5.2 Alarm Types

Tellabs 86xx Nodes / FLM Essentials 1.1 / Bern, 1.09.2010

ON BLINKING ON BLINKING during following operations: ON

Remote Alarm YELLOW

BLINKING LEDs on IFCs / IFMs Local Alarm RED

ON BLINKING ON BLINKING during following operations:

Remote Alarm YELLOW

Tellabs 86xx Nodes / FLM Essentials 1.1 / Bern, 1.09.2010

LEDs on Ethernet ports Link/Activity GREEN

5.4 Fault Status

5.5 External Alarm Relays

5.6 System Message Logging

Tellabs 86xx Nodes / FLM Essentials 1.1 / Bern, 1.09.2010