Tellabs 8600 Smart Routers FP4.1 Embedded Software Release Notes

Tellabs ® 8600 Smart Routers FP4.
1
Embedded Software Release Notes
76.8641-50156E
15.04.2014
Document Information
Revision History
Document Date Description of Changes

No.
76.8641- 15.04.2014 New FP4.1 application software version for Tellabs 8600 SR5.0 SP1
50156E in ch. 4.2 Version 4.1.586 (FP4.1 SP1 GA).
Ch. 1 Embedded Software Interrelation Tables updated.
New CBZ2745 mini-application software and GMZ2743
boot software versions added in the Tellabs 8600 Boot and
Mini-Applications Software table.
Supported upgrade paths added and installation instructions updated
in ch. 2 Installation Notes.
Ch. 2.4 Upgrade Related Notifications updated.
Ch. 2.7.2 IFC1 to IFC2 Upgrade added.
Ch. 3 FP4.1 Features updated.
Ch. 5.1.1 Restrictions in Tellabs 8600 Smart Routers FP4.1 updated.
The following restrictions removed, as they are discussed elsewhere
in Tellabs 8600 SR5.0 customer documentation.
• ELC1 has an ingress bandwidth limitation of 3 Gbps for Ethernet
switched multicast, broadcast, and flooded packets. Ingress
multicast, broadcast or flooded traffic exceeding the limit is
dropped. The limitation does not apply to switched unicast
traffic.
• Link Aggregation Control Protocol (LACP) is not supported.
Ch. 5.1.2 Restrictions in Tellabs 8600 Smart Routers Prior to FP4.1
updated. The following restrictions removed, as they are discussed
elsewhere in Tellabs 8600 SR5.0 customer documentation.
• When doing inter VRF routing in an NE, its own addresses are
unreachable from one VRF to another, and ping does not work.
The same also happens when trying to connect/ping some VRF
via network.
• Interface MIB query does not work with the SNMPv1 protocol.
Interface MIB can be queried using the SNMPv2 protocol.
• 4xSTM-1/OC-3 ATM IFM throughput restriction.
• 256 VCGs at maximum are supported per IFC.
• LSP1+1 hardware and software restrictions.
• In Tellabs 8620 smart router MSP1+1/APS1+1 uni-directional
and bi-directional protections are not supported with 4xSTM-
1/OC-3 ATM (LIA2210), 1xchSTM-1/chOC-3 MS (LIO2203)
and 4xchSTM-1/chOC-3 MS (LIO2234) IFMs.
• During graceful restart after CDC switchover if there are config-
ured alternative LSPs which have the same FEC (for example
RSVP primary and LDP), traffic may be briefly switched to the
LSP which has lower priority. This is temporary and traffic is
switched back to the best available LSP by the end of graceful
restart.
• Disabling of one Non-Real time queue apparently affects the
other Non-Real time queue's shaping behavior. The Overall CIR
configured for the shaper is still achieved but the split between
different Non-Real time traffic is getting changed.
New chapter 5.3 Rejected Bugs added.
PPN ID added for cq300240437.
Customer text updated for cq300234920.
Tellabs ® 8600 Smart Routers FP4.1 76.8641-50156E

Embedded Software Release Notes © 2014 Tellabs.
2
No.
76.8641- 12.12.2013 New application software version 4.1.466 (CIR3) in ch. 4.3 Version
50156D 4.1.466 (FP4.1 CIR3).
Renewed related documentation table in ch. Tellabs 8600 Smart
Routers Technical Documentation.
in ch. 2 Installation Notes.
Added a notification regarding ELC1 ESW upgrade to FP4.1 CIR3 in
ch. 2.4 Upgrade Related Notifications.
Ch. 3 FP4.1 Features renamed and updated.
CR ID cq300239483 added as fixed in application software version
4.1.322 (CIR2).
CR ID cq300201631 added as fixed in application software version
4.1.182 (CIR1).
PPN ID added for cq300234327 and cq300238021.
Customer text modified for cq300239507 and cq300239584.
Added as known bugs since previous FP4.1 release notes:
cq300162577, cq300227993, cq300228415, cq300228864,
cq300232233, cq300232624, cq300232626, cq300232736,
cq300232742, cq300233848, cq300234572, cq300236384,
cq300237046, cq300239134, cq300239567, cq300239579,
cq300239581, cq300240437, cq300240981, cq300241136,
cq300241252, cq300241410, cq300241632, cq300241633,
cq300241665.
76.8641- 29.11.2013 New application software version 4.1.323 (CIR2.1 fast lane) in ch.
50156C 4.4 Version 4.1.323 (FP4.1 CIR2.1 Fast Lane).
Supported upgrade paths and installation instructions updated in ch.
2 Installation Notes.

No.
76.8641- 30.09.2013 New application software version 4.1.322 (CIR2).
50156B Embedded software interrelations tables updated in chapter 1.
in chapter 2.
CDC1 to CDC2 upgrade instructions added in ch. 2.7 Upgrading
Cards.
Ch. 3 New Features updated.
Ch. 5.1 Restrictions reorganized.
CR ID cq300216944, cq300216952, cq300229733, cq300231761,
cq300235931, cq300236078, cq300236926 and cq300236943 added
as fixed in application software version 4.1.182 (CIR1).
CRs removed from known bugs: cq300110632, cq300110634,
cq300123197, cq300123204, cq300150704, cq300184835,
cq300221729, cq300228405, cq300235240.
Added as known bugs since previous FP4.1 release notes:
cq300065174, cq300183257, cq300188025, cq300194302,
cq300200128, cq300226641, cq300229182, cq300229733,
cq300232238, cq300232502, cq300232810, cq300234142,
cq300234613, cq300235294, cq300235768, cq300235931,
cq300236005, cq300236056, cq300236172, cq300236327,
cq300236450, cq300236684, cq300236932, cq300237308,
cq300237335, cq300237592, cq300237950, cq300238014,
cq300238328, cq300238439, cq300238440, cq300238636,
cq300238637, cq300238638, cq300238669, cq300238891,
cq300238895, cq300238925, cq300238930, cq300238931,
cq300239002, cq300239013, cq300239034, cq300239055,
cq300239114, cq300239123, cq300239127, cq300239128,
cq300239131, cq300239133, cq300239135, cq300239166,
cq300239261, cq300239282, cq300239293, cq300239366,
cq300239369, cq300239370, cq300239406, cq300239475,
cq300239483, cq300239498, cq300239507, cq300239529,
cq300239554, cq300239568, cq300239569, cq300239570,
cq300239576, cq300239584.
76.8641- 10.05.2013 New application software version 4.1.182 (CIR1).
50156A Tellabs 8600 Discontinued Products table added.
Application software compatibility data updated in chapter 1.
ELC1 boot software data updated in chapter 1.

4
This revision of the manual documents the following network elements and the corresponding
feature pack.
Tellabs 8620 smart router, Tellabs 8630 smart router, Tellabs 8660 smart router FP4.1
If you have a different feature pack of Tellabs 8600 products, please refer to the relevant product
document program on the Tellabs Portal by navigating to www.portal.tellabs.com > Product
Documentation > Data Networking > Tellabs 8600 Smart Routers > Technical Documentation.
© 2014 Tellabs. All rights reserved.
This Tellabs manual is owned by Tellabs or its licensors and protected by U.S. and international copyright laws, conventions and
treaties. Your right to use this manual is subject to limitations and restrictions imposed by applicable licenses and copyright laws.
Unauthorized reproduction, modification, distribution, display or other use of this manual may result in criminal and civil penalties.
The following trademarks and service marks are owned by Tellabs Operations, Inc. or its affiliates in the United States and/or
other countries: TELLABS ®, TELLABS ® logo, TELLABS and T symbol ®, and T symbol ®.
Any other company or product names may be trademarks of their respective companies.
The specifications and information regarding the products in this manual are subject to change without notice. All statements,
information, and recommendations in this manual are believed to be accurate but are presented without warranty of any kind,
express or implied. Users must take full responsibility for their application of any products.
Adobe ® Reader ® are registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.
Unless otherwise agreed in a written document, the software in the product is licensed under the license terms found
at http://www.tellabs.com/legal/tlab_sw_license-global.pdf and http://www.tellabs.com/le-
gal/tlab_terms-product_specific.pdf.
76.8641-50156E Tellabs ® 8600 Smart Routers FP4.1

© 2014 Tellabs. Embedded Software Release Notes
5
6
Terms and Abbreviations
Term Explanation
AAA Authentication, Authorization, Accounting
AC Attachment Circuit
APS Automatic Protection Switching
ATM Asynchronous Transfer Mode
BFD Bidirectional Forwarding Detection
BGP Border Gateway Protocol
BMI Broadband Management Interface of Tellabs 8000 intelligent network manager
BMP Broadband Management Protocol. The communication protocol which is used
between the Tellabs 8600 network elements and Tellabs 8000 intelligent network
manager.
CCM Continuity Check Message
CDC Control and DC Power Card (used in Tellabs 8630 smart router and Tellabs 8660
smart router)
CESoPSN Circuit Emulation Service over Packet Switched Network
CFM Connectivity Fault Management
CIR Controlled Introduction Ready
CLI Command Line Interface
Control card The control card in the Tellabs 8600 system consists of an Control and DC Power
Card CDC (used in Tellabs 8630 smart router and Tellabs 8660 smart router) or
Switching and Control Module SCM (used in Tellabs 8611 smart router). In Tellabs
8000 intelligent network manager and CLI referred to as unit.
DM Delay Measurement
DNU Do Not Use
DSCP DiffServ Code Point
ELC1 Ethernet Line Card (used in Tellabs 8630 smart router and Tellabs 8660 smart router)
ELP Ethernet Link Protection
ESW Embedded Software
FE Fast Ethernet
FEC Forward Equivalence Class
FP Feature Pack
FRR Fast Reroute
GA General Availability
GE Gigabit Ethernet
GUI Graphical User Interface
HW Hardware

7
ICMP Internet Control Message Protocol

IFC Interface Module Concentrator is a line card baseboard and it can be equipped with
one or two IFMs. There are three variants available: IFC1-A, IFC1-B and IFC2-B
(used in Tellabs 8630 smart router and Tellabs 8660 smart router).
IFM Interface Module. A specific term of the module which can be placed on the IFC
line card or Tellabs 8620 smart router baseboard and which consists of the physical
interfaces (used in Tellabs 8620 smart router, Tellabs 8630 smart router and Tellabs
8660 smart router).
IMA Inverse Multiplexing for ATM
IP Internet Protocol
IRB Integrated Routing and Bridging
IS-IS Intermediate System to Intermediate System (Interior Gateway Protocol)
LAG Ethernet Link Aggregation
Line card The line card in the Tellabs 8600 system consists of an Ethernet Line Card (ELC1),
or Interface Module Concentrator (IFC) and up to two Interface Modules (IFMs)
(used in Tellabs 8630 smart router and Tellabs 8660 smart router). In Tellabs 8000
intelligent network manager and CLI referred to as unit.
LM Line Module
LM Loss Measurement
LSP Label Switched Path
MAC Media Access Control Sublayer of Data Link Layer
MEP Maintenance Endpoint
MFE Management Fast Ethernet
MIB Management Information Base (SNMP)
MIP Maintenance Intermediate Point
MLPPP Multi-Link PPP
MO Mobile Optimization (Interface Module)
MPLS Multiprotocol Label Switching
MS Multiservice (Interface Module)
MSP1+1 Multiplex Section Trail Protection 1+1
MTU Maximum Transfer/Transmission Unit
Multi-card Network element whose hw-inventory contains multiple slots, refers to Tellabs 8611
NE smart router, Tellabs 8630 smart router and Tellabs 8660 smart router
NE Network Element
OAM Operation, Administration and Maintenance
OSPF Open Shortest Path First
PKG Software package file
POS Packet over SDH/Sonet
PPN Product Performance Notice
PPP Point-to Point Protocol

8
Protecting This ELP group member interface is selected by default as the passive interface. Note
interface that in CLI a protecting interface is referred to as a backup interface.
PWE3 Pseudowire Emulation Edge to Edge. IEFT working group.
RADIUS Remote Authentication Dial-In User Service. Commonly used to provide centralized
authentication, authorization, and accounting functionalities.
RSVP Resource Reservation Protocol
SFP Small Form-Factor Pluggable. A transceiver type used in Tellabs 8600 IFMs, HMs,
LMs and network elements.
Single card Network element whose hw-inventory contains only one slot, refers to Tellabs
NE 8605 smart router, Tellabs 8607 smart router, Tellabs 8609 smart router and Tellabs
8620 smart router
SNMP Simple Network Management Protocol
SSH Secure Shell
SW Software
TDM Time Division Multiplexing
TLV Type Length Value
VCG Virtual Circuit Group
VLAN Virtual Local Area Network
VRRP Virtual Router Redundancy Protocol
VSI Virtual Switching Instance
Working This ELP group member interface is selected by default as the active interface. The
interface working interface must be the right-hand side interface of the two interfaces of
an ELP group (in case of Tellabs 8660 smart router the interface residing on the
right-hand side IFC, in case of Tellabs 8620 smart router the right-hand side interface
on the IFMs, and in case of Tellabs 8630 smart router the lower interface as IFCs
are in horizontal direction). Note that in CLI a working interface is referred to as
primary interface.
XFP 10-Gigabit Small Form-Factor Pluggable. A transceiver type used in Tellabs 8600
ELC1.

9
10
Table of Contents
Table of Contents
About This Manual ............................................................................................................ 13
Objectives....................................................................................................................................................................... 13
Audience......................................................................................................................................................................... 13
Tellabs 8600 Smart Routers Technical Documentation ................................................................................................. 14
Tellabs 8600 Rebranding .................................................................................................. 17
Tellabs 8600 Discontinued Products............................................................................... 18
Tellabs 8600 Discontinued Features ............................................................................... 19
1 Embedded Software Interrelation Tables.................................................................. 20
2 Installation Notes ........................................................................................................ 32
2.1 Supported Upgrade Paths .................................................................................................................................... 32

2.2 Software Upgrade Order...................................................................................................................................... 33
2.3 Operations Before Upgrade ................................................................................................................................. 33
2.4 Upgrade Related Notifications............................................................................................................................. 34
2.4.1 Recommended Procedure for Upgrading from FP4.0 or above to FP4.1 SP1 .................................... 35
2.4.2 Notifications Regarding ELC1 ESW Upgrade to FP4.1 SP1 .............................................................. 36
2.5 Service Affecting Software Upgrade of the Whole NE....................................................................................... 36
2.6 Non-Service Affecting Software Upgrade........................................................................................................... 38
2.7 Upgrading Cards.................................................................................................................................................. 38
2.7.1 Upgrading CDC1 to CDC2.................................................................................................................. 38
2.7.2 IFC1 to IFC2 Upgrade......................................................................................................................... 41
2.8 Restoring Previous FP and Configuration in Case of Upgrade Failure............................................................... 44
3 FP4.1 Features............................................................................................................. 46

11
Table of Contents
4 Application Software................................................................................................... 49
4.1 Overview ............................................................................................................................................................. 49

4.2 Version 4.1.586 (FP4.1 SP1 GA)......................................................................................................................... 50
4.2.1 Enhancements Compared to 4.1.466 (FP4.1 CIR3) ............................................................................ 50
4.2.2 Fixed Bugs Compared to 4.1.466 (FP4.1 CIR3) ................................................................................. 50
4.3 Version 4.1.466 (FP4.1 CIR3) ............................................................................................................................. 61
4.3.1 Enhancements Compared to 4.1.323 (FP4.1 CIR2.1 Fast Lane)......................................................... 61
4.3.2 Fixed Bugs Compared to 4.1.323 (FP4.1 CIR2.1 Fast Lane).............................................................. 62
4.4 Version 4.1.323 (FP4.1 CIR2.1 Fast Lane).......................................................................................................... 72
4.5 Version 4.1.322 (FP4.1 CIR2) ............................................................................................................................. 72
4.5.1 Enhancements Compared to 4.1.182 (FP4.1 CIR1) ............................................................................ 73
4.6 Version 4.1.182 (FP4.1 CIR1) ............................................................................................................................. 88
4.6.1 Enhancements Compared to 4.0.309 ................................................................................................... 88
4.6.2 Fixed Bugs Compared to 4.0.309 ........................................................................................................ 89
5 Known Restrictions and Bugs ................................................................................. 109
5.1 Restrictions ........................................................................................................................................................ 109

5.1.1 Restrictions in Tellabs 8600 Smart Routers FP4.1 ............................................................................ 109
5.1.2 Restrictions in Tellabs 8600 Smart Routers Prior to FP4.1 ................................................................112
5.2 Bugs ....................................................................................................................................................................112
5.3 Rejected Bugs .................................................................................................................................................... 136

12
About This Manual
About This Manual

This chapter discusses the objectives and intended audience of this manual, Tellabs ® 8600 Smart
Routers Embedded Software Release Notes.
Objectives
This manual consists of the embedded software of Tellabs 8620 smart router, Tellabs 8630 smart
router and Tellabs 8660 smart router. At the beginning of the manual you can find the Tellabs 8620
smart router, Tellabs 8630 smart router and Tellabs 8660 smart router related embedded software
interrelation tables for:
• network elements
• interface modules
• boot software and mini-applications
The ESW of Tellabs 8630 smart router and Tellabs 8660 smart router can be upgraded with
non-service affecting upgrade procedure under certain configuration combinations. The latest
detailed description of the upgrade procedure is presented in chapter 2 Installation Notes.
Chapter 4 Application Software describes the enhancements and fixed bugs in the following
application software:
• 8620: SBZ2714 Application Software

• CDC1: CBZ2712 Application Software
• CDC2: CBZ2745 Application Software
• ELC1: LBZ2754 Application Software
• IFC1: LBZ2713 Application Software
• IFC2: LBZ2741 Application Software
The known restrictions and bugs are listed in chapter 5.
Audience
This manual is designed for Tellabs 8600 network element installation personnel and system
specialists when planning or maintaining the network, updating software or installing network
elements.

13
About This Manual
Tellabs 8600 Smart Routers Technical Documentation
The document numbering scheme consists of the document ID, indicated by numbers, and the
document revision, indicated by a letter. The references in the Related Documentation table below
are generic and include only the document ID. To make sure the references point to the latest
available document versions, please refer to the relevant product document program on the Tellabs
Portal by navigating to www.portal.tellabs.com > Product Documentation > Data Networking >
Tellabs 8600 Smart Routers > Technical Documentation.
Document Title Description

Tellabs ® 8600 Smart Routers Provides an overview of Tellabs 8600 system PWE3 applications,
ATM and TDM Configuration Guide including types, Single-Segment and Multi-Segment; PWE3
(76.8600-50110) Redundancy; ATM applications, including PWE3 tunneling,
Traffic Management, Fault Management OAM, protection and
TDM applications as well as instructions on how to configure
them with CLI.
Tellabs ® 8600 Smart Routers Provides information related to the boot and mini-applications
Boot and Mini-Applications software of Tellabs 8605 smart router, Tellabs 8607 smart router,
Embedded Software Release Notes Tellabs 8609 smart router, Tellabs 8611 smart router, Tellabs
(76.8600-50108) 8620 smart router, Tellabs 8630 smart router and Tellabs 8660
smart router as well as the installation instructions.
Tellabs ® 8600 Smart Routers Provides commands available to configure, monitor and maintain
CLI Commands Manual Tellabs 8600 system with CLI.
(76.8600-50117)
Tellabs ® 8600 Smart Routers Consists of the embedded software release notes of the Tellabs
Embedded Software Release Notes 8600 NEs. The following embedded software release notes are
available:
• Tellabs ® 8605 Smart Router FP1.6 Embedded Software
Release Notes (76.8616-50154)
• Tellabs ® 8607 Smart Router FP1.1 Embedded Software Re-

lease Notes (76.8611-50139)
• Tellabs ® 8609 Smart Router and Tellabs ® 8611 Smart Router

FP1.2 Embedded Software Release Notes (76.8612-50155)
• FP4.1 Embedded Software Release Notes (76.8641-50156)
of Tellabs 8620 smart router, Tellabs 8630 smart router and
Tellabs 8660 smart router
Tellabs ® 8600 Smart Routers Provides an overview of Tellabs 8600 system HW inventory,
Equipment Management software management, equipment protection 1+1 (CDC and
Configuration Guide SCM) as well as instructions on how to configure them with CLI.
(76.8600-50118)
Tellabs ® 8600 Smart Routers Provides an overview of Tellabs 8600 system Ethernet
Ethernet Configuration Guide (76. applications, including interfaces; Ethernet forwarding (MAC
8600-50133) Switching, Ethernet PWE3, IRB, VLAN, VPLS); Ethernet OAM;
LAG; ELP as well as instructions on how to configure them
with CLI.
Tellabs ® 8600 Smart Routers Provides an overview of Tellabs 8600 system fault management,
Fault Management Configuration including fault source, types and status as well as instructions on
Guide (76.8600-50115) how to configure it with CLI.

14
About This Manual

Tellabs ® 8600 Smart Routers Provides an overview of Tellabs 8600 system Frame Relay
Frame Relay Configuration Guide applications, including interfaces; Performance Monitoring;
(76.8600-50120) protection; Traffic Management as well as instructions on how to
configure them with CLI.
Tellabs ® 8600 Smart Routers Provides guidance on mechanical installation, cooling,
Hardware Installation Guide grounding, powering, cabling, maintenance, commissioning and
(76.8600-40039) ESW downloading.
Tellabs ® 8600 Smart Routers Consists of the hardware release notes of the network element
Hardware Release Notes components in Tellabs 8605 smart router, Tellabs 8607 smart
(76.8600-40027) router, Tellabs 8609 smart router, Tellabs 8611 smart router,
Tellabs 8620 smart router, Tellabs 8630 smart router and Tellabs
8660 smart router
Tellabs ® 8600 Smart Routers The Interface Configuration Guides provide an overview of the
Interface Configuration Guides Tellabs 8600 NEs interface functions, including NE supported
interface types and equipping; interface features; configuration
options and operating modes; fault management; performance
monitoring; interface configuration layers and port protocols as
well as instructions on how to configure them with CLI. The
following interface configuration guides are available:
• Tellabs ® 8605 Smart Router FP1.6 Interface Configuration
Guide (76.8616-50157)
• Tellabs ® 8607 Smart Router FP1.1 Interface Configuration
Guide (76.8611-50136)
• Tellabs ® 8609 Smart Router and Tellabs ® 8611 Smart Router
FP1.2 Interface Configuration Guide (76.8612-50158)
• FP4.1 Interface Configuration Guide (76.8641-50159) of
Tellabs 8620 smart router, Tellabs 8630 smart router and
Tellabs ® 8600 Smart Routers Provides an overview of Tellabs 8600 system IP, forwarding and
IP Forwarding and Traffic traffic management functionality, including: IP addressing; IP
Management Configuration Guide hosting (ARP, DHCP); IP routing (static); ACL; Differentiated
(76.8600-50122) Services (Policing, Queue Management, Shaping) as well as
instructions on how to configure them with CLI.
Tellabs ® 8600 Smart Routers Provides an overview of Tellabs 8600 system management
Management Communications communications functions, including communication protocols:
Configuration Guide BMP; FTP; RADIUS; SNMP; SSH; TELNET as well as
(76.8600-50125) instructions for configuring them with CLI.
Tellabs ® 8600 Smart Routers Provides an overview of Tellabs 8600 system Mobile
Mobile Optimization Configuration Optimization applications as well as instructions on how to
Guide (76.8600-50100) configure them with CLI.
Tellabs ® 8600 Smart Routers Provides an overview of Tellabs 8600 system MPLS applications
MPLS Applications Configuration (including FRR (one-to-one and facility backup); LDP;
Guide (76.8600-50123) protection and Traffic Engineering), MPLS-TP applications
(including OAM, linear protection) as well as instructions on
how to configure them with CLI.
Tellabs ® 8600 Smart Routers Provides an overview of Tellabs 8600 system supported
Performance Counters Reference performance counters.
Guide (76.8600-50143)

15
About This Manual

Tellabs ® 8600 Smart Routers The reference manuals describe the Tellabs 8600 network
Reference Manuals element features including:
• NE enclosure, baseboard, power supply modules, interfaces
types in Tellabs ® 8605 Smart Router FP1.6 Reference
Manual (76.8616-40099)
and physical LM types in Tellabs ® 8607 Smart Router FP1.1
Reference Manual (76.8611-40067)
and physical LM types in Tellabs ® 8609 Smart Router FP1.2
Reference Manual (76.8612-40100)
• NE enclosure, baseboard, power supply modules, SCMs, HM
and LM types in Tellabs ® 8611 Smart Router FP1.2 Refer-
ence Manual (76.8612-40101)
• NE enclosure, baseboard, power supply modules, fan mod-
ule, timing module, IFMs in Tellabs ® 8620 Smart Router
FP4.1 Reference Manual (76.8641-40102)
• NE subrack, fan modules, CDCs, line cards and IFMs
in Tellabs ® 8630 Smart Router FP4.1 Reference Manual
(76.8641-40103)
• NE subrack, fan modules, CDCs, line cards and IFMs
in Tellabs ® 8660 Smart Router FP4.1 Reference Manual
(76.8641-40104)
Tellabs ® 8600 Smart Routers Provides an overview of Tellabs 8600 system routing protocols,
Routing Protocols Configuration including BFD; BGP; ECMP; IS-IS; OSPF and VRRP as well as
Guide (76.8600-50121) instructions on how to configure them with CLI.
Tellabs ® 8600 Smart Routers Describes SNMP MIB support by the Tellabs 8600 NEs and
SNMP MIB Support provides information on the supported objects and traps. For
(76.8600-50116) further information on SNMP MIBs, see the related RFCs.
Tellabs ® 8600 Smart Routers Provides an overview of Tellabs 8600 system supported statistic
Statistic Counters Reference Guide counters.
(76.8600-50142)
Tellabs ® 8600 Smart Routers Provides an overview of Tellabs 8600 system synchronization
Synchronization Configuration applications, including physical layer Frequency Synchronization
Guide (76.8600-50114) (SEC, EEC); Frequency Packet Synchronization (CES, PTP);
Phase-Time Synchronization as well as instructions on how to
configure them with CLI.
Tellabs ® 8600 Smart Routers Provides an overview of Tellabs 8600 system measurement and
Test and Measurement Configuration connectivity verification tools, including Ethernet loopback;
Guide (76.8600-50124) IP ping and traceroute; MAC swap loopback; MPLS ping and
traceroute; PLT; PWE3 loopback; VCCV (VCCV BFD, VCCV
LSP ping) as well as instructions on how to configure them with
CLI.
Tellabs ® 8600 Smart Routers Provides an overview of Tellabs 8600 system virtual private
VPNs Configuration Guide network (VPN) layer 3 applications as well as instructions on
(76.8600-50128) how to configure them with CLI.
Tellabs ® 8000 Intelligent Network Provides instructions on how different operations are performed
Manager Online Help with Tellabs 8000 intelligent network manager. Describes also
different parameters and controls of the Tellabs 8000 intelligent
network manager dialogs and windows.
Note that the online help is not available on the portal but it is
incorporated in Tellabs 8000 intelligent network manager.

16
Tellabs 8600 Rebranding
Tellabs 8600 Rebranding

Starting from September 2012, Tellabs 8600 product names are being rebranded. The table below
lists previous and new product names. You may see instances of both the previous and the new
product names in the customer documents during the transition period to the new naming system.
Previous Product Name New Product Name

Tellabs® 8600 Managed Edge System Tellabs® 8600 Smart Routers
Tellabs® 8605 Access Switch Tellabs® 8605 Smart Router
Tellabs® 8660 Edge Switch Tellabs® 8660 Smart Router

17
Tellabs 8600 Discontinued Products

Tellabs is announcing the Manufacture Discontinued (MD) for the following Tellabs 8600 products:

Discontinued Product Replacement MD Notification
Product/Solution
Tellabs 8620 smart router AC For most applications Tellabs 8609 SC1005135-1
(81.86S8620ACCHA-R5 Rev. B) smart router and Tellabs 8611 smart
router can be used, please check.
Tellabs 8620 smart router DC48 For most applications Tellabs 8609 SC1005136-1
(81.86S8620DC48C-R5 Rev. B) smart router and Tellabs 8611 smart
router can be used, please check.
Tellabs 8660 smart router subrack Tellabs 8660 smart router R2 SC1003044-1
V3.1 subrack
(81.86S-8660-R6 Rev. A) 82.86S-8660-R6 Rev. A
IFC1-A (81.86IFC1A02024-R5 IFC2-B (81.86L-IFC2B-R6) is SC1005144-1
Rev. B) main replacement but check IFM
compatibility.
8x10/100BASE-TX IFM 8x100/1000BASE-X R2 IFM SC1005147-1
(81.86MFETX82018-R6 Rev. (81.86M-IFMGEX08-R6) with
D) IFC2
8x100BASE-X IFM 8x100/1000BASE-X R2 IFM SC1005148-1
(81.86MFEX082028-R6 Rev. (81.86M-IFMGEX08-R6) with
A) IFC2
(81.86MGE0022019-R5 Rev. (81.86M-IFMGEX08-R6) with
A) IFC2
(81.86MGE0082208-R6 Rev. (81.86M-IFMGEX08-R6) with
B) IFC2
1xchSTM-1/chOC-3 Multiservice 4xchSTM-1/chOC-3 Multiservice SC1005145-1
IFM (81.86MS1C012203-R5 Rev. IFM (81.86MS1C042234-R6)
B)
24xchE1/chT1 Mobile Optimization None. SC1005146-1
IFM (81.86ME1M242237-R6 Rev.
A)
For details regarding Tellabs MD policy, refer to the Tellabs North America Manufacturing
Discontinued Policy found on the Tellabs Portal (www.portal.tellabs.com).

18
Tellabs 8600 Discontinued Features

Tellabs is announcing the discontinuation of the following Tellabs 8600 features:

Discontinued Feature Affected Products and Workaround Notification
Feature Packs
MPLS OAM LSP 1+1 Tellabs 8620 smart router, RSVP-TE 1:1 PPN 11071
protection Tellabs 8630 smart router protection with BFD or
and Tellabs 8660 smart MPLS fast reroute
router FP3.1 and higher
For details regarding Tellabs customer notifications, refer to the Tellabs Portal
(www.portal.tellabs.com).

19
1 Embedded Software Interrelation Tables

The following embedded software interrelation tables are shown below:
• Tellabs 8620 smart router

• Tellabs 8630 smart router and Tellabs 8660 smart router
• Tellabs 8600 interface modules used in Tellabs 8620 smart router, Tellabs 8630 smart router and
• Tellabs 8600 boot software and mini-application used in Tellabs 8620 smart router, Tellabs 8630
smart router and Tellabs 8660 smart router. For a comprehensive list of software versions, please
refer to Tellabs® 8600 Smart Routers Boot and Mini-Applications Embedded Software Release
Notes.
The tables show, in a compact form, the dependencies between Tellabs 8600 embedded software
and dependencies between Tellabs 8600 embedded software and Tellabs 8600 hardware. See the
embedded software release note of a relevant network element for more information.
The following conventions are used in the release notes.
• The text No known bugs means that there are no bugs known to Tellabs.
• The text No known restrictions under version information means that there are no restrictions
when using this version of software or hardware.
The notations used in the rows of the network element dependencies and compatible network
elements and embedded software versions are explained in the following table.
Version number A specific ESW version is required.

Any Any version of the ESW is compatible.
– No logical connection or not applicable.
A particular NE or SW is not required or supported by
another NE.
Rows marked in bold indicate the latest HW or SW product generally available and in
production.
Rows marked in italics indicate the fast lane or CIR products that are not generally available.
The older generally available HW and SW versions are in normal font type.

20
The meaning of different columns and notations are described below.
Baseboard Baseboard where the ESW is downloaded.

HW Version Hardware version of the baseboard.
ESW Embedded software product name.
ESW Version Embedded software version whose dependencies are
described in that row. Also the Service Pack mentioned.
Production Status Production status of the embedded software version whose
dependencies are described in that row. The production
status can be
• GA: refers to a generally available version that is in
production.
• CIR: refers to a first customer shipment version of the
software that is intended for controlled introduction.
This version should not be used by customers after the
general availability of the software has been reached
and a new version is available.
• Fast lane: refers to a version of software with a limited
distribution released to fix a potentially critical prob-
lem that is typically impacting only a small number of
customers. This version can be obtained by contacting
Tellabs technical support.
NE Dependencies ESW dependencies related to a NE.
Tellabs 8000 INM Release Tellabs 8000 intelligent network manager release that
supports all functionality of the product.
Tellabs 8000 INM EMS Driver Version Tellabs 8000 intelligent network manager EMS driver
version related to Tellabs 8600 NE FP.
Interface Module Name of the interface module and HW identification code.
Compatible NEs and ESW Versions Compatible NEs and ESW versions for an IFM.
Mini-Application Mini-application product name.
NE/Card Name of network element or card.
Boot SW Boot software product name.
Mini-Application Version Specifies the oldest software version of mini-application
which co-operates with the given application software,
boot software or product HW version. For example, a new
product HW version may require that the mini-application
has to be at least this version level due to HW changes.
Boot Version Boot SW activates the application or mini-application
software. Boot SW must be at least at the minimum
specified level specified by the activated application
software or mini-application for correct product behavior.
Application Version Application software running at product normal operational
state. Application, mini-application and boot software have
internal dependencies where each software version must be
at least at the specified level to co-operate correctly.

21
22

Tellabs ® 8600 Smart Routers FP4.1

Tellabs 8620 Smart Router Hardware and Software Compatibility Matrix
Basic Data 8000 INM 8000 INM EMS
Release Driver Version
Baseboard HW Version ESW ESW Version Production
Status
SBB2030 1.0 or higher SBZ2714 4.1.586 (SP1) GA SR5.0 or higher 401.2

SBB2030 1.0 or higher SBZ2714 4.1.466 (CIR3) CIR SR5.0 or higher 401.2
SBB2030 1.0 or higher SBZ2714 4.1.323 (CIR2.1) fast lane SR5.0 or higher 401.2
76.8641-50156E
© 2014 Tellabs.
© 2014 Tellabs.
76.8641-50156E Tellabs 8630 Smart Router and Tellabs 8660 Smart Router Hardware and Software Compatibility Matrix
Basic Data NE Dependencies 8000 INM 8000
Release INM EMS
Tellabs Base- HW ESW ESW Produc- CDC1 CDC2 ELC1 IFC1 IFC2 Driver
8630 board Version Version tion Version
/8660 Status
card
CDC1-A CBB2026 1.1 or CBZ2712 4.1.586 GA 4.1.586 4.1.586 4.1.586 4.1.586 4.1.586 SR5.0 or 401.2
higher higher
CDC1-A CBB2026 1.1 or CBZ2712 4.1.466 CIR 4.1.466 4.1.466 4.1.466 4.1.466 4.1.466 SR5.0 or 401.2
higher higher
CDC1-A CBB2026 1.1 or CBZ2712 4.1.323 fast lane 4.1.323 4.1.323 4.1.323 4.1.323 4.1.323 SR5.0 or 401.2
higher higher
higher higher
higher higher
CDC1-B CBB2224 1.0 or CBZ2712 4.1.586 GA 4.1.586 4.1.586 4.1.586 4.1.586 4.1.586 SR5.0 or 401.2
higher higher
CDC1-B CBB2224 1.0 or CBZ2712 4.1.466 CIR 4.1.466 4.1.466 4.1.466 4.1.466 4.1.466 SR5.0 or 401.2
higher higher
CDC1-B CBB2224 1.0 or CBZ2712 4.1.323 fast lane 4.1.323 4.1.323 4.1.323 4.1.323 4.1.323 SR5.0 or 401.2
higher higher
higher higher

higher higher
CDC2-B CBB2300 1.0 or CBZ2745 4.1.586 GA 4.1.586 4.1.586 4.1.586 4.1.586 4.1.586 SR5.0 or 401.2
higher higher
higher higher
CDC2-B CBB2300 1.0 or CBZ2745 4.1.323 fast lane 4.1.323 4.1.323 4.1.323 4.1.323 4.1.323 SR5.0 or 401.2
higher higher
higher higher
23
24


Basic Data NE Dependencies 8000 INM 8000
Release INM EMS
/8660 Status
card
ELC1 ELC2269 1.0 or LBZ2754 4.1.586 GA 4.1.586 4.1.586 4.1.586 4.1.586 4.1.586 SR5.0 or 401.2
higher higher
ELC1 ELC2269 1.0 or LBZ2754 4.1.466 CIR 4.1.466 4.1.466 4.1.466 4.1.466 4.1.466 SR5.0 or 401.2
higher higher
ELC1 ELC2269 1.0 or LBZ2754 4.1.323 fast lane 4.1.323 4.1.323 4.1.323 4.1.323 4.1.323 SR5.0 or 401.2
higher higher
higher higher
higher higher
IFC1-A LBA2024 1.0 or LBZ2713 4.1.586 GA 4.1.586 4.1.586 4.1.586 4.1.586 4.1.586 SR5.0 or 401.2
higher higher
IFC1-A LBA2024 1.0 or LBZ2713 4.1.466 CIR 4.1.466 4.1.466 4.1.466 4.1.466 4.1.466 SR5.0 or 401.2
higher higher
IFC1-A LBA2024 1.0 or LBZ2713 4.1.323 fast lane 4.1.323 4.1.323 4.1.323 4.1.323 4.1.323 SR5.0 or 401.2
higher higher
higher higher
higher higher
IFC1-B LBA2225 1.0 or LBZ2713 4.1.586 GA 4.1.586 4.1.586 4.1.586 4.1.586 4.1.586 SR5.0 or 401.2
higher higher
IFC1-B LBA2225 1.0 or LBZ2713 4.1.466 CIR 4.1.466 4.1.466 4.1.466 4.1.466 4.1.466 SR5.0 or 401.2
higher higher
IFC1-B LBA2225 1.0 or LBZ2713 4.1.323 fast lane 4.1.323 4.1.323 4.1.323 4.1.323 4.1.323 SR5.0 or 401.2
higher higher
76.8641-50156E
© 2014 Tellabs.
higher higher
higher higher
© 2014 Tellabs.
76.8641-50156E Basic Data NE Dependencies 8000 INM 8000
Release INM EMS
/8660 Status
card
IFC2-B LBA2250 1.0 or LBZ2741 4.1.586 GA 4.1.586 4.1.586 4.1.586 4.1.586 4.1.586 SR5.0 or 401.2
higher higher
higher higher
IFC2-B LBA2250 1.0 or LBZ2741 4.1.323 fast lane 4.1.323 4.1.323 4.1.323 4.1.323 4.1.323 SR5.0 or 401.2
higher higher
higher higher
higher higher

25
26


Tellabs 8600 Interface Module Hardware and Software Compatibility Matrix
Basic Data Compatible NEs/Cards & ESW Versions
Interface Module HW Version CDC1 CDC2 IFC1 IFC2 8620
CBZ2712 CBZ2745 LBZ2713 LBZ2741 SBZ2714
8x10/100BASE-TX 2.2 2.2.7 or higher 4.1.322 or higher 2.2.7 or higher — 2.2.7 or higher
LIE2018 (81.86MFETX82018-R6
Rev. D)
LIE2018 (81.86MFETX82018-R6
Rev. C)
LIE2018
LIE2018
8x100BASE-X 1.1 1.22.7 or higher 4.1.322 or higher 1.22.7 or higher — 1.22.7 or higher
LIO2028 (81.86MFEX082028-R6
Rev. A)
LIO2028
LIO2019 (81.86MGE0022019-R5
Rev. A)
LIO2019
LIO2208 (81.86MGE0082208-R6
Rev. B)
LIO2208
LIO2208
2+6x10/100/1000 1.3 2.5.113 or higher 4.1.322 or higher 2.5.113 or higher — 2.5.113 or higher
BASE-COMBO (81.86MGEC082231-R6
76.8641-50156E
© 2014 Tellabs.
LIC2231 Rev. C)
© 2014 Tellabs.
76.8641-50156E Basic Data Compatible NEs/Cards & ESW Versions
BASE-COMBO (81.86MGEC082231-R6
LIC2231 Rev. B)
BASE-COMBO
LIC2231
8x10/100/1000BASE-TX 81.86M- 3.1.309 or higher 4.1.322 or higher — 3.1.309 or higher —
R2 LIE2256 IFMGET08-R6 Rev. A
8x100/1000BASE-X 81.86M- 3.0.126 or higher 4.1.322 or higher — 3.0.126 or higher —
R2 IFM LIO2252 IFMGEX08-R6 Rev. B
8x100/1000BASE-X 1.0 3.0.126 or higher 4.1.322 or higher — 3.0.126 or higher —
R2 IFM LIO2252 (81.86M-
IFMGEX08-R6 Rev.
A)
1x10GBASE-R R2 81.86M- 3.0.126 or higher 4.1.322 or higher — 3.0.126 or higher —
IFM LIO2257 IFM10GS1-R6 Rev.
B
1x10GBASE-R R2 IFM 1.0 3.0.126 or higher 4.1.322 or higher — 3.0.126 or higher —
LIO2257 (81.86M-
IFM10GS1-R6 Rev.
A)
8xSTM-1/OC-3 POS 1.1 1.17.15 or higher 4.1.322 or higher 1.17.15 or higher 3.1.309 or higher 1.17.15 or higher
LIO2020 (81.86MS1P082020-R6
Rev. A)

8xSTM-1 POS 1.0 1.17.15 or higher 4.1.322 or higher 1.17.15 or higher — 1.17.15 or higher
LIO2020
4xSTM-4/OC-12 POS 1.0 2.7.20 or higher 4.1.322 or higher 2.7.20 or higher 3.1.309 or higher 2.7.20 or higher
LIO2233 (81.86MS4P042233-R6
Rev. A)
1xSTM-16/OC-48 POS 1.0 1.17.15 or higher 4.1.322 or higher 1.17.15 or higher 3.1.309 or higher —
LIO2021 (81.86MS16P12021-R6
Rev. A)
27
28


Basic Data Compatible NEs/Cards & ESW Versions
4xSTM-1/OC-3 ATM 1.1 2.0.2 or higher 4.1.322 or higher 2.0.2 or higher 3.1.309 or higher 2.0.2 or higher
LIA2210 (81.86MS1A042210-R6
Rev. A)
4xSTM-1/OC-3 ATM 1.0 2.0.2 or higher 4.1.322 or higher 2.0.2 or higher — 2.0.2 or higher
LIA2210
1xchSTM-1/chOC-3 1.0 2.0.2 or higher 4.1.322 or higher 2.0.2 or higher 3.1.309 or higher 2.0.2 or higher
MS LIO2203 (81.86MS1C012203-R5
Rev. B)
4xchSTM-1/chOC-3 2.0 2.9.143 or higher 4.1.322 or higher 2.9.143 or higher 3.1.309 or higher 2.9.143 or higher
MS LIO2234 (81.86MS1C042234-R6
Rev. B)
4xchSTM-1/chOC-3 1.1 2.9.143 or higher 4.1.322 or higher 2.9.143 or higher — 2.9.143 or higher
MS LIO2234 (81.86MS1C042234-R6
Rev. A)
24xchE1/chT1 MS 2.1 2.7.20 or higher 4.1.322 or higher 2.7.20 or higher 3.1.309 or higher 2.7.20 or higher
LIE2226 (81.86ME1T242226-R6
Rev. B)
24xchE1/chT1 MS 2.0 2.7.20 or higher 4.1.322 or higher 2.7.20 or higher — 2.7.20 or higher
LIE2226
24xchE1 MS 1.0 2.2.7 or higher 4.1.322 or higher 2.2.7 or higher — 2.2.7 or higher
LIE2226
24xchE1/chT1 MO 1.0 2.9.242 or higher 4.1.322 or higher 2.9.242 or higher — 2.9.242 or higher
LIE2237 (81.86ME1M242237-R6
Rev. A)
76.8641-50156E
© 2014 Tellabs.
© 2014 Tellabs.
76.8641-50156E Tellabs 8600 Boot and Mini-Applications Software
Basic Data
Mini- Version Tellabs 8600 Baseboard HW Version Boot SW Version Application Production
Application NE/card Version Status
GMZ2702 2.11.156 CDC1-A CBB2026 1.1 or higher GMZ2700 3.4.0 2.11.134 or GA
higher
GMZ2702 2.8.191 CDC1-A CBB2026 1.1 or higher GMZ2700 3.4.0 Any GA
GMZ2702 2.0.104 CDC1-A CBB2026 1.1 or higher GMZ2700 3.3.7 2.8.212 or GA
lower
GMZ2702 2.0.101 CDC1-A CBB2026 1.1 or higher GMZ2700 3.1 2.8.212 or GA
lower
lower
lower
lower
GMZ2702 2.11.156 CDC1-B CBB2224 1.0 or higher GMZ2700 3.4.0 2.11.134 or GA
higher
GMZ2702 2.8.191 CDC1-B CBB2224 1.0 or higher GMZ2700 3.4.0 Any GA
GMZ2702 2.0.104 CDC1-B CBB2224 1.0 or higher GMZ2700 3.3.7 2.8.212 or GA
lower
GMZ2702 2.0.101 CDC1-B CBB2224 1.0 or higher GMZ2700 3.1 2.8.212 or GA
lower
CBZ2745 4.1.509 CDC2-B CBB2300 1.0 or higher GMZ2743 1.20.0 FP4.1 CIR2 or GA

higher
CBZ2745 4.1.259u CDC2-B CBB2300 1.0 or higher GMZ2743 1.16.0 FP4.1 CIR2 or CIR
FP4.1 CIR3
LBZ2754 4.0.44 ELC1 ELC2269 1.0 or higher GMZ2752 1.2.0 Any GA
LBZ2754 4.0.34 ELC1 ELC2269 1.0 or higher GMZ2752 1.0.2 4.0.19 HW CIR ESW
load
LBZ2754 4.0.21 ELC1 ELC2269 1.0 or higher GMZ2752 1.0.0 4.0.19 HW CIR ESW
load
29
30


Basic Data
GMZ2711 2.11.156 IFC1-A LBA2024 1.0 or higher GMZ2710 3.4.0 2.11.134 or GA
higher
GMZ2711 2.8.191 IFC1-A LBA2024 1.0 or higher GMZ2710 3.4.0 Any GA
GMZ2711 2.0.104 IFC1-A LBA2024 1.0 or higher GMZ2710 3.3.7 2.8.212 or GA
lower
GMZ2711 2.0.101 IFC1-A LBA2024 1.0 or higher GMZ2710 3.1 2.8.212 or GA
lower
lower
lower
lower
GMZ2711 2.11.156 IFC1-B LBA2225 1.0 or higher GMZ2710 3.4.0 2.11.134 or GA
higher
GMZ2711 2.8.191 IFC1-B LBA2225 1.0 or higher GMZ2710 3.4.0 Any GA
lower
GMZ2711 2.0.101 IFC1-B LBA2225 1.0 or higher GMZ2710 3.1 2.8.212 or GA
lower
higher
higher
GMZ2716 2.11.156 8620 SBB2030 1.0 or higher GMZ2715 3.4.0 2.11.134 or GA
higher
GMZ2716 2.8.191 8620 SBB2030 1.0 or higher GMZ2715 3.4.0 Any GA
GMZ2716 2.0.104 8620 SBB2030 1.0 or higher GMZ2715 3.3.7 2.8.212 or GA
76.8641-50156E
© 2014 Tellabs.
lower
GMZ2716 2.0.101 8620 SBB2030 1.0 or higher GMZ2715 3.1 2.8.212 or GA
lower
© 2014 Tellabs.
76.8641-50156E Basic Data
lower
lower

31
2 Installation Notes
2.1 Supported Upgrade Paths
The supported upgrade paths are listed below:
From To
FP4.1 CIR3 (4.1.466) FP4.1 SP1
FP4.1 CIR2 (4.1.322) FP4.1 SP1
FP4.1 CIR1 (4.1.182) FP4.1 SP1
FP4.1 ECE (4.1.71) FP4.1 CIR1 (followed by immediate mandatory
upgrade to FP4.1 SP1)
FP4.0 SP3 (4.0.309) FP4.1 SP1
FP3.1 SP3 (3.1.558) FP4.1 SP1
FP3.1 SP2 (3.1.507) FP4.0 SP3
FP3.1 SP1 (3.1.425) FP4.0 SP3
FP3.0 CIR (3.0.126) FP3.1 SP3
FP2.11A SP5 (2.11.850) FP4.0 SP3
FP2.11A SP4 (2.11.804) FP4.0 SP3
FP2.11A SP3 (2.11.706) FP4.0 SP3
FP2.11A SP2.1 (2.11.620) FP4.0 SP3
FP2.11A SP2 (2.11.612) FP3.1 SP3
FP2.11A SP1.1 (2.11.515) FP2.11A SP5

32
2.2 Software Upgrade Order
For all the CDC2-B control cards delivered before FP4.1 SP1, CDC2 boot software GMZ2743
version 1.20.0 or higher needs to be updated before upgrading the application ESW to FP4.1
SP1.
Check the current boot SW version in slot 1 and 14. E.g.:
router#show sw-version slot 1

1: boot SW gmz2743-1.20.0 1.20.0
1: mini-application SW cbz2745_4.1.509 4.1.509 Backup.
...
See the Boot and Mini-Application Upgrade chapter for installation instructions in Tellabs 8600
Boot and Mini-Applications Embedded Software Release Notes. The latest boot and mini-application
PKG is pkg_boot_cdc2_4.1.509.
If you are currently using application ESW FP2.11A SP1 in Tellabs 8620 smart router, Tellabs
8630 smart router and Tellabs 8660 smart router, the boot and mini-application upgrade
is optional in CDC1, IFC1, IFC2 and ELC1 cards and should be done after upgrading the
application ESW to FP2.11A SP2 or higher.
2.3 Operations Before Upgrade
Prior to upgrading, validate that the network element is ready for upgrade by performing the steps
outlined below.
In Tellabs 8630 smart router and Tellabs 8660 smart router, which are multi-card NEs, the working
slot (primary) is slot 14. In Tellabs 8620 smart router the hw-inventory contains only one slot.
Step 1 The target is to check and record the state of the NE before the upgrade is started. Check the
hardware inventory and verify that all cards are present, in up-and-running state and all cards
are running the same ESW version.
router# show hw-inventory | include slot
router# show sw-version | include OK
If problems are found:
• Consider if they need to be fixed before starting the upgrade, or
• Consider using the "force" option when activating the new ESW
router(config)# boot system <…> backup-config force
Using this option the upgrade is forced; the previous ESW or configurations will not be
automatically restored (but the upgrade can still be cancelled manually).
Step 2 Free flash space by removing the previous unused ESWs:
Tellabs 8630 smart router and Tellabs 8660 smart router:
router# delete slot * flash: *

33
Tellabs 8620 smart router:

router# delete flash: *
Step 3 Free flash space by removing the old unused configuration snapshot files in each slot. Before
deleting make backup copies by uploading the configuration snapshot files from the network element
using FTP. The snapshot files can be found in the following directory:
For Tellabs 8630 smart router and Tellabs 8660 smart router:
/flash/snapshot-config/slot<slot#>/
For Tellabs 8620 smart router:
/flash/snapshot-config/
This CLI command will give a list of the already created and stored snapshots:
router# show snapshot-config flash: ?
The “show snapshot” CLI command can also contain the slot number part. If it is omitted, the slot
number of the active CDC is used by default.
To get more details regarding a specific snapshot use the following CLI command:
router# show snapshot-config flash: <filename>
Delete unused snapshot files:
router# snapshot-config delete slot 14 flash: <filename>
router# snapshot-config delete flash: <filename>
Step 4 Backup the current configuration of the NE:
router# snapshot-config create flash: <filename> description <xyz>
The current configuration and running config text file will be stored in the snapshot file:
router# snapshot-config create flash: <filename> running-config
description <xyz>
In Tellabs 8630 smart router and Tellabs 8660 smart router the configuration snapshot file can be
uploaded using FTP from either directory (depending on which CDC is active):
/flash/snapshot-config/slot14/ OR
/flash/snapshot-config/slot1/
2.4 Upgrade Related Notifications
Please also refer to chapter 2.1 Supported Upgrade Paths.
If CDC2 cards have been installed in Tellabs 8630 smart router and Tellabs 8660 smart router,
the 2+5x10/100/1000BASE interface in CDC2 must be removed from hw-inventory before
upgrading to FP4.1 SP1 ESW.
Use the following command before reloading new ESW to the network element:
router#hw-inventory slot 14 remove module 1

34
CDC2 boot SW GMZ2743 version must be 1.20.0 or higher before CDC2 can be upgraded
to FP4.1 SP1.
Check the current boot SW version. E.g.:
router#show sw-version slot 14

14: boot SW gmz2743-1.20.0 1.20.0
...
CDC2 may very rarely cancel a requested SW version upgrade operation, due to an additional
internal CDC2 reboot event. If this situation occurs during an upgrade related boot, CDC2
re-activates the previously used SW version. To complete SW upgrade, re-activate the SW
version upgrade manually for the specific CDC2 unit with the command sequence given below.
enable
configure terminal
boot system slot <CDC2 unit> flash: <sw-version> reload
NOTE: Check after the SW upgrade operation that each cards is running the upgraded SW versions:
enable
show sw-version
Non-service affecting upgrade of IFC1 to IFC2 cards is not supported in Tellabs 8600 smart
routers FP4.1. Refer to Tellabs® 8600 Smart Routers FP3.1 Embedded Software Release Notes
(76.8631-50146), ch. 2.7.2, for the procedure.
2.4.1 Recommended Procedure for Upgrading from FP4.0 or above to FP4.1 SP1
The recommended procedure for upgrading from FP4.0 or above to FP4.1 is as follows:
1. Upgrade from FP4.0 to FP4.1 according to the instructions in this chapter (chapter 2 Installation
Notes). Use the following ESW files in the upgrade:
• pkg_8620_4.1.586 in Tellabs 8620 smart router
• pkg_8660_4.1.586_C1 in Tellabs 8630 smart router and Tellabs 8660 smart router with
CDC1 card(s) installed.
To avoid out of memory situation you might want to download the package file to an IFC2
or ELC1 card instead of CDC, or consider using a smaller package file if you do not have
IFC2 or ELC1 cards installed in the NE.
pkg_8660_4.1.586_c1i12 contains ESW for CDC1, IFC1 and IFC2 cards. You can also
use pkg_8660_4.1.586_c1i1 if there are no IFC2 card(s) installed in the NE.
• pkg_8660_4.1.586_C2 in Tellabs 8630 smart router and Tellabs 8660 smart router if CDC2
cards have already been installed before the ESW upgrade.
2. If desired, install new line cards to the NE before ESW upgrade (CDC2 cards can be installed
only after ESW has been upgraded to FP4.1 SP1 or above). (See Tellabs ® 8600 Smart Routers
Hardware Installation Guide.)

35
3. Upgrade ESW to the NE.

4. Add new cards to the hw-inventory after the ESW upgrade.
2.4.2 Notifications Regarding ELC1 ESW Upgrade to FP4.1 SP1
Notification 1
The following needs to be considered in ELC1 Gigabit Ethernet Interface using electrical SFP
module when ELC1 ESW upgrade to FP4.1 SP1 is planned.
Interactions with ELP Configuration Options
The operator needs to ensure that the following unsupported ELP options are not configured to an
ELC1 interface equipped with an electrical SFP:
• Passive-if-mode down
• Passive-if-mode down pulse.
These modes are supported only by optical SFPs and may be present in the configuration if an
optical SFP has been used earlier or if an erroneous configuration has been made. There is no logic
that prevents using these unsupported options with an electrical SFP. If such options are present
before the upgrade, the operator needs to re-configure the interface to rx-both mode before the
upgrade. rx-both mode is the only supported option for the electrical SFP. If re-configuration is
not carried out before the upgrade, a persistent data cut may appear immediately after the upgrade or
after the first switch-over. In the worst case the operator needs to remove and recreate the ELP group
to recover from the failure state caused by the Passive-if-mode down or Passive-if-mode
down pulse modes. Removing the ELP group may require removing also the configurations for
upper layer services in some cases.
Impact for the customer: Persistent data cut if the upgrade procedure is not followed.
Notification 2
With (and only with) ELC1 based IEEE1588, a fault will be posted after the SW upgrade to a
version supporting IEEE1588 (see below for fault description). IEEE1588 is not functional before
the ELC1 unit in question is rebooted once again, after which the new PLD image is activated and
the fault cleared. The command 'reset-hw' MUST be used, to activate the new PLD image. E.g.,
router#reset-hw slot x.
Fault description:
001: Slot 6: HW-INVENTORY:Unit 6: PLD image update requires unit

reset to be completed.
Warning, Equipment alarm, No led
Fault ON 13:40:00.2 UTC Tue Jan 21 2014 /13:40:00.2 LOCAL Tue
2.5 Service Affecting Software Upgrade of the Whole NE
Never activate an older ESW than the current one without restoring configurations or carrying
out a clean-start of the NE (see chapter 2.8 Restoring Previous FP and Configuration in Case
of Upgrade Failure). The end result of the operation is otherwise fully nondeterministic.

36
When an ESW package file (pkg_8620_x.y.z1 for Tellabs 8620 smart router and pkg_8660_x.y.z
for Tellabs 8630 smart router and Tellabs 8660 smart router) is used, it is possible to activate and
reload new ESW to all slots in a NE with one CLI command. All traffic is temporarily affected
during NE bootup.
Step 1 Transfer with FTP/SFTP the new software file or package. 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 a 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).
If the transfer fails, you can try to use smaller PKGs, e.g. instead of the full package
file pkg_8660_x.y.z_C1 transfer and activate first pkg_8660_x.y.zc1i1 and then
pkg_8660_x.y.zi2e1.
Select the file which is transferred to the NE using FTP/SFTP and the target directory in the NE
according to the following table.
NE Type File Name for ESW Upgrade FTP Target Directory in NE

Tellabs 8620 smart router pkg_8620_x.y.z /flash/appl-sw
Tellabs 8630 smart router and pkg_8660_x.y.z_C1 2 /flash/appl-sw/slot1 or
Tellabs 8660 smart router with /flash/appl-sw/slot14 3 or
CDC1 /flash/appl-sw/slot<slot#>4
Tellabs 8630 smart router and pkg_8660_x.y.z_C2 2 /flash/appl-sw/slot1 or
Tellabs 8660 smart router with /flash/appl-sw/slot14 or3
CDC2 /flash/appl-sw/slot<slot#>4
Step 2 The application ESW must be activated and the card/NE must be reset before the new application
ESW is in use.
The following CLI command activates new ESW to all slots in a NE, reloads the NE and creates
card specific configuration backup (i.e. bootsnap) for each slot containing configurations before
upgrade. If the system detects problems during upgrade, it restores the previous configuration and
ESW automatically in the individual slot(s). See more details in chapter 2.8 Restoring Previous FP
and Configuration in Case of Upgrade Failure.
router(config)# boot system slot 14 flash: pkg_8660_x.y.z
backup-config reload
router(config)# boot system flash: pkg_8620_x.y.z backup-config
reload
1Inthe file name 'x.y.z' refers to the ESW version number.

2Several types of package files may be available.
3Select the slot number of the passive CDC. Check the slot number of the passive CDC with the CLI command “router# show protection unit cdc”.
4Select the slot number of IFC2 or ELC1 card.

37
Sometimes rarely one shot service affecting ESW upgrade might fail in one CDC in Tellabs 8630
smart router or Tellabs 8660 smart router when CDC1+1 protection is used (CR ID cq300228047).
After failure other cards are successfully running new ESW while one CDC might be running the
previous ESW version or might not get start permission, e.g.
router# show hw-inventory slot 14

unit in slot 14 is part of inventory and WAITING FOR START PERMISSION
-->UNIT START PERMISSION DENIED!
-->WRONG ESW VERSION! POSSIBLE RESET-LOOP: OPERATOR ACTIONS NEEDED!
Workaround: Activate the new ESW again for the CDC whose upgrade has failed and reload
the CDC:
router# boot system slot <slot#> flash: <cbz2712-filename> reload
2.6 Non-Service Affecting Software Upgrade
The non-service affecting software upgrade procedure is not supported in FP4.1 SP1 for
Tellabs 8630 smart router and Tellabs 8660 smart router. The procedure in chapter 2.5 Service
Affecting Software Upgrade of the Whole NE should be followed instead.
2.7 Upgrading Cards
Refer to Tellabs ® 8600 Smart Routers 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. For more
detailed information on using configuration snapshots for restoring previous configuration,
refer to chapters 2.3 Operations Before Upgrade and 2.8 Restoring Previous FP and
Configuration in Case of Upgrade Failure.
2.7.1 Upgrading CDC1 to CDC2
In Tellabs 8630 smart router and Tellabs 8660 smart router with CDC-1+1 protection, CDC1-A
or CDC1-B cards can be replaced with CDC2-B cards. During upgrade operation CDC2 obtains
the configuration of the previous CDC1 card; in addition the new expected card type (CDC2-B) is
automatically updated in the hw-inventory. The operation is non-service affecting and irreversible.
During upgrade the CDC1 configuration is converted to CDC2 configuration. Note that the
operation is irreversible!

38
Refer to Tellabs ® 8600 Smart Routers Hardware Installation Guide for more detailed
instructions and restrictions.
The requirements before the CDC upgrade are:
• CDC 1+1 protection is required (CDC1-A or CDC1-B)

• The NE must be running ESW version FP4.1 SP1 or above.
• The new CDC2 units must have the same ESW version active as the rest of the cards have. If
CDC2 has wrong ESW version active, use an external, preferably non-live traffic network ele-
ment to download the correct ESW with FTP to the CDC2 card, activate it and reload.
The following procedure shall be used for the CDC upgrade:
Step 1 Check that CDC in slot 14 is active:

router# show protection unit cdc
If CDC in slot 1 is active, switch activity to slot 14:
router# protection manual-switchover unit cdc slot 14
Step 2 Grant upgrade permission.
router# hw-inventory slot 14 upgrade-permission cdc1-cdc2
Step 3 NE configuration is denied until step 12. However configurations mentioned in this step list are
allowed. Cancelling the upgrade permission is possible before slot 14 gets the start permission in
step 8, after this point the upgrade is irreversible.
Step 4 Switch CDC and MFE activity to slot 1.
router# protection manual-switchover interface mfe slot 1
Wait until switching is completed. Use the following command and wait for the highlighted state:
router#show protection unit cdc
Unit 14 is in OK state.
Unit 14 is passive.
Unit 14 has noRequest switch type.
Unit 14 is non-revertive.
Unit 14 is a working unit.
Protection group of unit 14 has 1 working units: 14.
Protection group of unit 14 has 1 protecting units: 1.
Protection group of unit 14 is of type: 1+1.
Protection group of unit 14 is named: cdc.
Unit 1 is active.
Unit 1 has no switch command active.
Unit 1 is a protecting unit.
Step 5 Shutdown slot 14.
router# esw-shutdown slot 14

39
Step 6 When the red and yellow LEDs (local and remote alarm) of CDC1 slot 14 are blinking, you can
remove the card according to instructions in the Tellabs ® 8600 Smart Routers Hardware Installation
Guide.
Step 7 Change the needed cable types (Serial interface/Alarm I/O, SCO/SCI, power cable) of the CDC
in slot 14.
Step 8 Insert CDC2 to slot 14 according to the Tellabs ® 8600 Smart Routers Hardware Installation Guide.
CDC2 must have the same ESW version active as the rest of the cards have.
Step 9 Wait until CDC2 in slot 14 is up and running
router#show hw-inventory slot 14 details
unit in slot 14 is part of inventory and UP AND RUNNING
upgrade-state cdc1-cdc2: not upgradeable
…
Step 10 Switch CDC and MFE activity to slot 14
router# protection manual-switchover interface mfe slot 14
Wait until switching is completed. Use the following command and wait for the highlighted state:
router#show protection unit cdc
Unit 14 is active.
Unit 14 has no switch command active.
Unit 14 is a working unit.
Unit 1 is passive.
Unit 1 is a protecting unit.
Step 11 Repeat steps 5-9 to the CDC in slot 1.
Step 12 NE configuration is allowed again.
All external alarm configurations are lost in the CDC1 to CDC2 upgrade process since the
external alarm connector is different in the CDC1 (D-25 connector) and the CDC2 (RJ-45
connector) cards. For more information, see Tellabs ® 8660 Smart Router Reference Manual,
Tellabs ® 8630 Smart Router Reference Manual and Tellabs ® 8600 Smart Routers Hardware
Installation Guide.

40
2.7.2 IFC1 to IFC2 Upgrade
In Tellabs 8630 smart router and Tellabs 8660 smart router with FP3.1 or higher, the IFC1 card can
be upgraded to the IFC2 card if the IFMs of the IFC2 cards are the same or compatible with the
IFMs of the IFC1 according to the table below. The configuration parameters from the existing IFMs
are automatically copied to the new IFMs when IFC1 is replaced with IFC2. The new expected
card type (IFC2) is automatically updated in the hw-inventory.
IFC1 is not SW upgradeable to IFC2.
The NE must be upgraded to FP3.1 or higher before IFC1 to IFC2 upgrade can be started.
When the NE is managed with Tellabs 8000 intelligent network manager, the upgrade
permission must be set in the Tellabs 8000 intelligent network manager to enable the IFC1 to
IFC2 upgrade. See the user instructions in the online help for more instructions.
Automatic Upgrade Support for IFMs in IFC1–IFC2 Upgrade

Old Module Type in IFC1 Compatible New Module Type in IFC2
8x10/100BASE-TX IFM 8x10/100/1000BASE-TX R2 IFM
8x100BASE-X IFM 8x100/1000BASE-X R2 IFM
2+6x10/100/1000BASE-COMBO IFM 8x10/100/1000BASE-TX R2 IFM
8x100/1000BASE-X R2 IFM
1xchSTM-1/chOC-3 MS IFM 4xchSTM-1/chOC-3 MS IFM
In addition to the IFMs listed in the table, IFC1 to IFC2 upgrade is supported if the IFM type is not
changed, that is, for the IFMs supported both in IFC1 and IFC2:
• 8xSTM-1/OC-3 POS IFM

• 4xSTM-1/OC-3 ATM IFM
• 1xchSTM-1/chOC-3 Multiservice IFM
• 4xchSTM-1/chOC-3 Multiservice IFM
• 24xchE1/chT1 Multiservice IFM

41
During upgrade the IFC1 configuration is converted to an IFC2 configuration. Note that the
operation is irreversible!
Before the IFC1 to IFC2 upgrade can be started, there must not be "Conflicting Module" or
"Expected Module Not Activated" alarms regarding IFMs in the card to be upgraded!
First you must get rid of the alarms by changing the module configuration and/or reloading
the card!
Check the current IFC upgrade state, e.g.
router# show hw-inventory details

upgrade-state ifc1-ifc2: can be upgraded, but not yet
permitted
...
upgrade-state ifc1-ifc2: not upgradeable
...
upgrade-state ifc1-ifc2: upgrade pending
...
When performing IFC1 to IFC2 upgrade automation there is a restriction that affects
ELP/APS1+1/MSP1+1 protection. Refer to chapters Service Affecting Upgrade and Non-Service
Affecting Upgrade5 for instructions. Note that non-service affecting upgrade is NOT supported
in Tellabs 8600 smart routers FP4.1.
Service Affecting Upgrade
Upgrading Non-Protected IFC1 to IFC2
Prerequisites:
• The NE is running FP3.1 or higher ESW version x.y.z. The same ESW version x.y.z must be
updated to IFC2 card(s) before the upgrade is started, this can be done e.g. by using an empty
slot (= not part of the hw-inventory) in the NE or an empty slot in some other NE. See Tellabs ®
8600 Equipment Management Configuration Guide for more information.
In cases when IFC is not protected, follow this procedure:
Step 1 Switch the CDC in slot 14 to active.

Step 2 Give the upgrade permission in the hw-inventory for the IFC slot you are going to upgrade.
router# hw-inventory slot <slot#> upgrade-permission ifc1-ifc2
5Ch. 2.7.2, ‘Non-Service Affecting Upgrade’, is included in ‘Tellabs® 8600 Smart Routers FP3.1 Embedded Software Release Notes’ (76.8631-
50146).

42
Step 3 NE configuration is denied until Step 9 (except those commands required for performing the
upgrade, e.g. software management).
Step 4 Shutdown the IFC1 card.
router# esw-shutdown slot <slot#>
Step 5 Replace IFC1 with IFC2.
Step 6 Repeat Steps 2 to 6 for all the cards to be upgraded in the NE.
Step 7 If applies, follow the instructions according to CDC Reset for FE to GE IFM Upgrade.
Step 8 NE configuration is allowed again.
Upgrading IFC1 Pair with ELP/APS1+1/MSP1+1 Protection
Mixed IFC1 and IFC2 protection combination (ELP, MSP1+1/APS1+1) may cause a traffic cut
during upgrade and IFC2 will not boot up as a protection pair with IFC1, except for specific HW and
feature combinations described in ch. 2.7.2 Non-Service Affecting Upgrade, in Tellabs® 8600 Smart
Routers FP3.1 Embedded Software Release Notes (76.8631-50146).
Due to this restriction, any other configuration where there is IFC1 + IFC1 with
ELP/APS1+1/MSP1+1 protection requires that protection is removed before the upgrade and added
after replacing the working and protecting IFC2. Follow this procedure:
The NE is running FP3.1 or higher ESW version x.y.z.
Step 1 Switch the CDC in slot 14 to active.

Step 2 Remove the protection groups (ELP/APS1+1/MSP1+1) for all the cards to be upgraded.
Step 3 Perform upgrade according to Upgrading Non-Protected IFC1 to IFC2.
Step 4 Reconfigure the protection groups (ELP/APS1+1/MSP1+1).
CDC Reset for FE to GE IFM Upgrade
Notice that if IFC1 has one or more of the IFMs specified in the left column of the following table,
you must reboot the CDC(s) after IFC1 to IFC2 upgrade. For other IFM types (not mentioned in the
table below) CDC reset is not needed and these steps can be omitted.
Old Module Type in IFC1 Compatible New Module Type in IFC2

8x10/100BASE-TX IFM 8x10/100/1000BASE-TX R2 IFM
Step 1 Perform IFC1 to IFC2 upgrade for all needed card slots in the network elements according to
previous step lists, Service Affecting Upgrade in case of non-protected configuration and Upgrading
IFC1 Pair with ELP/APS1+1/MSP1+1 Protection in case of protected configuration.
Step 2 Change the CDC in slot 1 to active.
Step 3 Reload the CDC in slot 14 and wait until it is up and running again.
Step 4 Switch CDC in slot 14 to active.
Step 5 Reload CDC in slot 1 and wait until it is up and running again.

43
Non-Service Affecting Upgrade
Non-service affecting upgrade of IFC1 to IFC2 cards is not supported in Tellabs 8600 smart
routers FP4.1. Refer to Tellabs® 8600 Smart Routers FP3.1 Embedded Software Release Notes
(76.8631-50146), ch. 2.7.2, for the procedure.
2.8 Restoring Previous FP and Configuration in Case of Upgrade

Failure
The previous (older) ESW version shall never be activated without restoring the previous
configurations (or clearing the configurations of the whole NE), otherwise the end result of
the operation is fully nondeterministic. There are two alternative procedures to restore the
state that existed before upgrade.
Procedure 1
If CDC2 card(s) are installed in the network element, procedure 1 cannot be used (cq300244435).
With CDC2 follow procedure 2 below instead.
Step 1 Remove all unused ESW files from all cards.

Step 2 Download the previous ESW package to the NE.
Step 3 Activate the previous ESW with the “restore-config” option: this causes each card to activate the
previous ESW and restore the previous configurations. Configurations are restored in each card
from snapshot file “bootsnap”, which was created when the new FP was activated.
NOTE: In the file name 'x.y.z' refers to the ESW version number of the previous FP.
restore-config reload
router(config)# boot system flash: pkg_8620_x.y.z restore-config
reload
Procedure 2

44
If procedure 1 cannot be used for some reason, the NE level snapshot configuration must be restored
(see chapter 2.3 Operations Before Upgrade). Before restoring, previous FP ESW package must be
activated.
Step 1 Remove all unused ESW files from all cards.

Step 2 Download the previous ESW package to the NE.
Step 3 Activate the previous ESW.
NOTE: In the file name 'x.y.z' refers to the ESW version number of the previous FP.
router(config)# boot system flash: pkg_8620_x.y.z
Do not reload the software yet.
Step 4 Restore the NE level configuration snapshot file which was created before starting upgrade.
router# snapshot-config restore flash: <filename>
If the step fails due to a lack of flash space, the “clear-flash” option can be used.
router# snapshot-config restore flash: <filename> clear-flash
The NE is automatically reloaded after the CLI command above.

45
3 FP4.1 Features
3 FP4.1 Features
This chapter lists the Tellabs 8600 system features and network elements supported in the FP4.1
CIR3 ESW release. Refer to Tellabs ® 8600 Smart Routers FP4.1 Product Definition for more
specific information.
Feature Related Tellabs 8600 Smart Routers

Network Configuration Guide
CDC2 Tellabs 8600 Smart Routers FP4.1
• Supported in Tellabs 8630 smart router and Tellabs Interface Configuration Guide
8660 smart router (76.8641-50159)
Equipment Management Configuration
Guide (76.8600-50118)
Synchronization Configuration Guide
(76.8600-50114)
EtherType 0x88A8 in IFC2 Ethernet Configuration Guide
(76.8600-50133)
Ethernet Link Protection Ethernet Configuration Guide
• Supported in ELC1 (76.8600-50133)
Ethernet MAC Switching Ethernet Configuration Guide
802.1ag/Y.1731 Ethernet OAM (CCM, LBM/LBR, Tellabs 8600 Smart Routers FP4.1
LTM/LTR) Interface Configuration Guide
Ethernet Configuration Guide
(76.8600-50133)
Y.1731 Frame Loss (LMM/LMR) Tellabs 8600 Smart Routers FP4.1
• Supported in ELC1 Interface Configuration Guide
(76.8641-50159)
(76.8600-50133)
VPLS and H-VPLS Ethernet Configuration Guide
Ethernet PW-PPP Interworking Tellabs 8600 Smart Routers FP4.1
• Supported in IFC2 Interface Configuration Guide
(76.8641-50159)
Ethernet PWE3 Redundancy for Ethernet over MLPPP ATM and TDM Configuration Guide
in 24-Port chE1 IFM (76.8600-50110)
• Supported in IFC1 and IFC2 with 24xchE1/chT1 Ethernet Configuration Guide
MS IFM (76.8600-50133)
Ethernet Pseudowire Redundancy ATM and TDM Configuration Guide
(76.8600-50133)

46
3 FP4.1 Features

Port Shaping IP Forwarding and Traffic Management
• Supported in ELC1 Configuration Guide (76.8600-50122)
Tellabs 8600 Smart Routers FP4.1
Interface Configuration Guide
(76.8641-50159)
Packet Storm Detection and Isolation Ethernet Configuration Guide
L3/L4 ACL IP Forwarding and Traffic Management
Faster ACL Configuration IP Forwarding and Traffic Management
Configuration Guide (76.8600-50122)
ACL Hit Counters Tellabs 8600 Smart Routers FP4.1 Product
• Supported in ELC1 Definition (76.8641-40092)
Policing IP Forwarding and Traffic Management
RED/WRED Queue Management IP Forwarding and Traffic Management
VLAN Shaping IP Forwarding and Traffic Management
VLAN + QoS Queuing IP Forwarding and Traffic Management
VLAN + QoS Traffic Counters Statistics Counters Reference Guide
EoMLPPP PWE3 Local Bridge from 24-Port Tellabs 8600 Smart Routers FP4.1 Product
Channelized E1 IFM to 1GE Port Definition (76.8641-40092)
• Supported in IFC1 and IFC2
Ethernet/VLAN PWE3 Attachment Circuit Tellabs 8600 Smart Routers FP4.1 Product
• Supported in ELC1 Definition (76.8641-40092)
ATM and TDM Configuration Guide
(76.8600-50110)
(76.8600-50133)
IEEE1588 L2 Boundary Clock Synchronization Configuration Guide
• Supported in ELC1 with CDC2 (76.8600-50114)
IEEE1588 L2 Master Synchronization Configuration Guide
IEEE1588 L2 Slave Synchronization Configuration Guide
2*10G + 12*1G ELC1 Over-Subscription Tellabs 8600 Smart Routers FP4.1
• Supported in ELC1 Interface Configuration Guide
(76.8641-50159)
ELC1: Support for Electrical SFPs Tellabs 8600 Smart Routers FP4.1 Product
• 1GE Electrical SFP Support Definition (76.8641-40092)
Hardware Installation Guide (76.8600-
• 100M Electrical SFP Support 40039J)
• New Electrical SFP 100/1000BASE-TX E-TEMP Tellabs 8600 Smart Routers FP4.1
(81.86T-SM3TX01Q-R6A) Interface Configuration Guide
(76.8641-50159)

47
3 FP4.1 Features

BFD for Single-Hop eBGP Routing Protocols Configuration Guide
(76.8600-50121)
VCCV LSP Ping and Traceroute Test and Measurement Configuration Guide
IPv4 Load Balancing to RSVP-TE Tunnels on ELC1 MPLS Applications Configuration Guide
(76.8600-50123)
IPv4 Load Balancing over RSVP-TE Tunnels for IP MPLS Applications Configuration Guide
VPN Routes (76.8600-50123)
• Supported in ELC1
IPv4 Load balancing (ECMP) Routing Protocols Configuration Guide
Integrated Routing and Bridging Ethernet Configuration Guide
MPLS-TP: Co-Routed Bidirectional LSP MPLS Applications Configuration Guide
MPLS-TP OAM: Proactive CC, CV and RDI (BFD) MPLS Applications Configuration Guide
MPLS-TP OAM: MEP Support MPLS Applications Configuration Guide
MPLS-TP OAM: Generic Associated Channel Label MPLS Applications Configuration Guide
(GAL) Support (76.8600-50123)
• Supported in ELC1
MPLS-TP 1:1 Linear Protection MPLS Applications Configuration Guide

48
4 Application Software
4.1 Overview
This chapter describes the FP4.1 versions of the following application software:
8620: SBZ2714 Application Software
• The application software SBZ2714 is used on SBB2030 card in Tellabs 8620 smart router.
CDC1: CBZ2712 Application Software
• The application software CBZ2712 is used on CBB2026 card and on CBB2224 card (CDC1) in
Tellabs 8630 smart router and Tellabs 8660 smart router.
CDC2: CBZ2745 Application Software
• The application software CBZ2745 is used on CBB2300 card (CDC2) in Tellabs 8630 smart
router and Tellabs 8660 smart router.
ELC1: LBZ2754 Application Software
• The application software LBZ2754 is used on ELC2269 card (ELC1) in Tellabs 8630 smart router
and Tellabs 8660 smart router.
IFC1: LBZ2713 Application Software
• The application software LBZ2713 is used on LBA2024 card and on LBA2225 card (IFC1) in
IFC2: LBZ2741 Application Software
• The application software LBZ2741 is used on LBA2250 card (IFC2) in Tellabs 8630 smart router
and Tellabs 8660 smart router.

49
4.2 Version 4.1.586 (FP4.1 SP1 GA)
NOTE: Starting from FP4.1 SP1, the affected network elements are referred to as ‘8620 NE’,
‘CDC1’, ‘CDC2’, ‘IFC1’, ‘IFC2’ and ‘ELC1’, instead of the ESW codes SBZ2714, CBZ2712,
CBZ2745, LBZ2713, LBZ2741 and LBZ2754.
4.2.1 Enhancements Compared to 4.1.466 (FP4.1 CIR3)

cq300238051 CDC1
Added generic ESW support for recovering from power brownout situations by
initiating an extra HW reset.
cq300240864 ELC1
Case 1: When an interface with electrical SFP is configured with 'mode auto speed
100 duplex full' and the card is manually plugged out and the SFP is replaced
with an optical SFP and reinserted, the speed values are set to default mode(i.e.
mode auto).
Case 2: When an interface with no SFP is configured with 'mode auto speed 100
duplex full' and the card is manually plugged out and an optical SFP is inserted in
that interface and plugged in, the speed values are set to default mode(i.e.mode
auto).
No 'Conflicting Module' alarm is reported as the interface now has the default
configuration.
cq300241286 CDC1, CDC2

IP related command history has now real calendar time stamps. This makes it easy
to correlate os-log messages and IP command history.
cq300243569 CDC1, CDC2

Support for arbitrary length of ISIS protocol host names to be displayed in any
CLI ISIS commands.
4.2.2 Fixed Bugs Compared to 4.1.466 (FP4.1 CIR3)

cq300180987 CDC1, CDC2
Creating or deleting an interface protection group (ELP, MSP or APS) may crash
the active control unit when the protection change affects a large amount of
routes or tunnels.
Impact: Active control unit may crash. In single unit network elements this will
also cut the traffic.
Risk of occurrence: Low.
Workaround: Not available.
cq300193116 IFC2
PWE3 configured with a static or LDP PUSH_FOR_VC FTN entry and forwarded
via the VLAN MPLS interface on IFC2 stops working if the CLI command "qos
vlan egress vlan-pri <X>" is given on this MPLS interface.
Impact: Traffic is cut on the affected PWE3.
Risk of occurrence: Always for this kind of PWE3 configuration if the "qos" CLI
command is given on an MPLS interface.
Workaround: Force reprovisioning of the PWE3 MPLS configuration, i.e.
remove and then reinstall the static PWE3 commands.

50
cq300210920 CDC1, IFC1, IFC2, ELC1

Performance Management Utilization Report shows incorrect values if there has
been a reset on a line card.
Impact: It does not affect live traffic.
Risk of occurrence: Incorrect values are shown always under the described
circumstances.
Workaround: Tellabs 8000 intelligent network manager SR2.2 or later has
changed the logic and this case is correctly calculated as counter reset.
cq300225691 IFC1, IFC2, ELC1, CDC1

Large PWE3 configuration may trigger data cut of about 20 seconds at the
maximum when e.g. one interface or next-hop goes down.
Impact: PWE3 configuration triggers data cuts.
Risk of occurrence: High with a large PWE3 configuration which includes at
least hundreds of PWE3 circuits.
Workaround: Do not use large PWE3 configurations.

RSVP path protection and FRR may be slow (switchover time is more than 1
second) when the working line card is removed or the working line card goes to
spontaneous reset.
Impact: Traffic may be slowly switched to the protecting path.
Risk of occurrence: High.
cq300227082 CDC1
Severe packet buffer RAM failure (PBRF) may stop all internal communication
between the CDCs. In this state an isolation "blocked from use" status of a PBRF
faulty CDC has been removed and the faulty CDC may cause an illegal state,
where both CDCs are working in the active state.
Impact: The illegal state may cause problems to data traffic.
Risk of occurrence: Rarely.
Workaround: Power off reboot on PBRF faulty CDC may fix PBRF failures.
PPN 09036

51
cq300228047 CDC1
Sometimes the one shot service affecting ESW upgrade might fail in one CDC1
when CDC1+1 protection is used. After failure the other cards are successfully
running the new ESW while one CDC1 might be running the previous ESW
version or might not get start permission, e.g. router#show hw-inventory slot 14
unit in slot 14 is part of inventory and WAITING FOR START PERMISSION
-->UNIT START PERMISSION DENIED!
-->WRONG ESW VERSION! POSSIBLE RESET-LOOP: OPERATOR
ACTIONS NEEDED!
Risk of occurrence: Rare. The risk is higher with high CPU loads in CDC1 cards
(e.g. with a lot of IP protocols running).
Workaround: Workaround 1: Activate the new ESW again for the CDC1 whose
upgrade has failed and reload the CDC1:
boot system slot <slot#> flash: <CDC1-filename>reload
Workaround 2: Use the non-service affecting upgrade method according to ESW
release notes, or upgrade just CDC1 cards using non-service affecting method:
1. Activate new ESW PKG to the NE
2. Switch CDC1 in slot 1 to active
3. reload-sw slot 14, wait until up
4. switch CDC1 in slot 14 to active
5. reload-sw slot 1, wait until up
6. Reload all the line cards, no need for non-service affecting method if not wanted.
cq300229182 CDC2
The timing mode of the network element is not set according to the hardware
inventory mode in case the unit is set to ANSI mode.
Impact: SSM messages are handled according to ETSI specification (G.781
Opt.1) and if ANSI quality levels are in use elsewhere in the network this will
lead to loss of synchronization.
Risk of occurrence: Always under the described circumstances.
Workaround: After setting the HW inventory mode and rebooting the network
element, set the node-timing mode manually to ANSI and reboot the nework
element again.
cq300234142 IFC2
Removal of VLAN shapers may trigger corruption of internal MPLS connection
bookkeeping contents, disturbing LSP connectivity.
Impact: LSP connectivity may be disrupted for a long time after the removal of
the VLAN shaper configuration.
Risk of occurrence: Sometimes under the described circumstances, given enough
time.
Workaround: Do not use VLAN shapers, or arrange a network element boot after
each VLAN shaper removal.
PPN 13050
cq300234505 CDC1, IFC1, IFC2, ELC1, 8620 NE

Network element rejects arriving IP packets that have been fragmented to
extremely many pieces (70 or 130 fragments, depending on ESW release).
Impact: Large and fragmented IP packets may disappear.
Risk of occurrence: Always for large IP packets if some routers in the network
are misconfigured to produce small fragments, especially if IP packets travel over
MPLS tunnels, which may cause an additional layer of fragmenting.
Workaround: Configure the network with reasonable MTUs so that fragmentation
is moderate.

52
cq300234841 CDC1, CDC2

VLAN priority marking is transiently disabled for control card originated control
packets (OSPF, ISIS, LDP hellos, etc) during control card switchover. Other
consequence is that Y.1731 Frame Loss measurement is not supported on upMEP
of VLAN trunk mode interface of VSI, since it will not work properly after CDC
switchover.
Impact: Protocol flapping can occur in cases of fully congested L2 switched
networks. In most cases there is no noticeable impact and proper mappings are
taken into use after control card switchover is completed.
Risk of occurrence: Always for about less than a minute after first control card
activity switchover following (newly active) control card boot.
cq300234957 ELC1
Error prints are seen in the console and the os-log if MTU is modified when
the interface status is down. However, the MTU is configured properly in spite
of the error printings.
Workaround: To avoid error prints, change the MTU when the interface state
is up.
cq300235033 CDC1, CDC2

The management interface command reply of the passive CDC is not set properly,
if the passive CDC is booting up.
Impact: The active CDC reboots.
cq300235122 CDC1
MPLSoETHoATM encapsulation does not work. Any frames sent to:
-RSVP tunnels routed via ETHoATM interfaces
-Static MPLS tunnels routed via ETHoATM interfaces
-VPN and PWE3 traffic sent via LDP PSN tunnels routed via ETHoATM interfaces
will be corrupted and dropped on the link.
Impact: The operator cannot use MPLS trunks where MPLSoETHoATM
encapsulation is needed.
cq300236005 IFC2
IFC2 initialisation may fail due to a very short network element level
power-off/power-on failure. The problem stays active until the failed IFC2 unit
is powered off and back on.
Impact: The failure causes permanent traffic break on all interfaces of the IFC2
until the workaround is applied.
Risk of occurrence: Very low.
Workaround: CLI command reset-hw slot <x> needs to be given to the failed
slot for it to recover from the problem.

53
cq300236172 CDC1, CDC2, IFC1, IFC2, ELC1, 8620 NE

Inter-vrf routing to node local address does not work.
Basically inter-vrf ping will always fail if destination address is in the same node
that does the inter-vrf routing. It should be noted that MPLS->VRF POP does not
count as inter-VRF, as the packet in effect arrives directly to the correct VRF.
This has no impact on forwarded traffic.
cq300237335 CDC1, CDC2

The current implementation of the RADIUS (RFC2865) feature is not in line with
the released customer requirements documentation, although it complies with the
standard. The NAS-IP-Address attribute is not used in Access-Request packets as
required, instead NAS-Identifier is used.
Impact: RADIUS does not work against a server which requires the
NAS-IP-Address attribute in the Access-Request packets.
cq300237602 CDC1, CDC2, 8620 NE

LDP may stop accepting new TCP connections, if the connection made to LDP
TCP port is aborted within certain small time window.
Impact: New LDP connections are not established.
Workaround: Perform CDC switchover and reload the previously active CDC.
cq300238014 CDC2
CDC2 virtual Ethernet interface module is visible in CLI, and it may report link
down faults, although the module is not supported.
Workaround: Unused Ethernet interfaces should be set to the "shutdown-if"
mode in order to avoid extra faults.
cq300238891 CDC2
After upgrading CDC1 to CDC2, Tellabs 8000 intelligent network manager reports
HW/DB inconsistency for the advertised speed of autonegotiation parameter in the
MFE interface. If in the CDC1 unit autonegotiation was enabled to advertise all
speed rates, then CDC2 will be limited to advertise only 10M and 100M, although
CDC2 MFE supports also the 1000M rate.
Impact: Tellabs 8000 intelligent network manager reports HW/DB inconsistency
for the advertised speed of autonegotiation parameter.
Workaround: After upgrading both CDC1 control cards to CDC2, the user
can reconfigure the advertised speed of autonegotiation parameter in the MFE
interface.
cq300238895 CDC1
When deleting an AC VLAN Pseudowire interface, some unexpected error
messages are displayed in the console.

54
cq300238971 IFC1, IFC2, 8620 NE

If the length of SDH configuration in running-config in one unit is more than 63
kB, the rest of the configuration is not shown. Also an error message is shown
(see module value 1093 to identify this error case):
####### THIS RUNNING-CONFIG IS NOT COMPLETE ##############
##########
returned error (unit=8 module=1093 rcfg=0x14d9b84)
Impact: Show running-config fails with "THIS RUNNING-CONFIG IS NOT
COMPLETE".
cq300239114 IFC2
In MAC switching and IRB application the IFC may reset spontaneously under
heavy MAC address learning and flooding load, when looped SLIs cause the
unknown MAC DA frames to be flooded back to learning.
Impact: IFC resets spontaneously and stops forwarding traffic when overloaded.
Workaround: Do not loop the SLIs. Use STP in connected networks.
cq300239135 CDC2
CDC2 MFE ports are not passing Tellabs 8000 intelligent network manager
configuration properly after CDC2 switchover. Some of the commands return
-1 error.
Impact: CDC2 MFE ports are not working for management communication.
Workaround: Do not use CDC2 MFE for management communication. Use
other system interfaces instead.
cq300239370 CDC2, CDC1

CLI command "hw-inventory add-all-units" might fail in Tellabs 8630 smart router
and Tellabs 8660 smart router with 1+1 protected CDC2. The fail happens when
- hw-inventory already exists when the "hw-inventory add-all-units" command
is applied and
- exceptionally, the control card in slot 1 is selected as the active CDC in the next
bootup after giving the command (text displayed "Unit activity decided: booting
as ACTIVE CDC" in console of slot 1).
As a result, the NE may fail to recover and the CLI consoles get stuck.
If the CLI consoles are stuck after 1 hour, contact your Tellabs representative.
Risk of occurrence: Rare.
cq300239406 ELC1
A harmelss error message ''UNIV_EGR: "NpxdUnivEgr_ReadArpEntryStats''
may be seen in the serial console from time to time.
cq300239498 CDC1, CDC2

IRB creation and deletion are not reliable on the passive CDC.
Impact: If IRB interfaces have been created, the passive CDC may reboot itself.
The passive CDC interface database may get corrupted so that it is not possible to
create any kind of interfaces after CDC switchover.
Risk of occurrence: Always, if the passive CDC is CDC2. Rare with CDC1.

55
cq300239568 CDC2
The user account shall be retained when snapshot restoration without issuing
"restore user-account" CLI command.
Impact: User is able to access with previous updated privilege after snapshot
restoration without the "restore user-account" CLI command.
cq300239579 CDC2
After upgrading from CDC1 to CDC2 control card, the IEEE1588 slave transport
mode is changed to value 0 (illegal value). As a result, the Tellabs 8000 intelligent
network manager consistency check fails after the upgrade.
Workaround: The inconsistency can be resolved via Tellabs 8000 intelligent
network manager.
cq300239581 CDC2
IEEE1588 L2 Boundary clock (BC) sends sync packets while its own slave
phase-lock is being calibrated. Because of this, output sync packets do not have
accurate timing information until BC reaches locked state.
Impact: Topology for this problem to occur:
IEEE1588 master - L2 Boundary clock node - L2 slave
If BC is connected to slave(s) and it is calibrating its own 1588 slave port
phase-lock, the slaves might experience problems acquiring lock due to inaccurate
timing information sent by the BC node.
The said slaves could end up in a state where their recovered clock is not
synchronized properly to the BC node. If this happens, they can be recovered only
by reboot or reconfiguration.
Risk of occurrence: Moderate.
Workaround: L2 IEEE1588 Slaves should be configured only after the BC node
is locked properly or rebooted also when the BC is rebooted.
cq300240922 CDC1
With ELP protection group configured, if the working line card is removed and
the network element is reloaded, the protecting line card will come up as active,
but traffic through the protecting interface will not be forwarded. Only when the
working line card is inserted, traffic forwarding would resume.
Impact: Traffic will not be forwarded after reloading the network element.
cq300240923 CDC1, CDC2, IFC2, ELC1

The "PM measurement accuracy of this period compromised: YES" message in
LM QoS statistics is shown for only one of the QoS classes.
Impact: It is not shown for all QoS classes that PM measurement period is
compromised.
Risk of occurrence: Always when there is a break in measurement due to some
kind of connection failure.

56
cq300241070 ELC1
In ELC1 line card swithcover will not work, if ELP is configured with down/down
pulse mode on an interface that contains Electrical SFP of the type Finisar with
Tellabs part number 81.86T-SM3TX01.
Impact: If there is a link failure in the active interface, traffic will not flow
through the backup interface and therefore traffic will be lost.

The maximum values of Loss Measurement Current and History 24h counter
are too low.
Impact: When the maximum value is reached, the counter value is cleared and
the counting starts again from zero. This means that all counter values so far are
lost for the current 24h measurement and the user is not able see the total value
(total number of frames during that 24 h period). There is no indication to the user
that the counter has reached its maximum value.
cq300241136 CDC1, CDC2

The CLI print format of Loss Measurement statistics is unclear with larger values.
Impact: Large values are difficult to read.
cq300241476 CDC1
Boot-time packet buffer RAM failure detection in CDC1 may not correctly detect
a scenario where isolating the whole CDC1 control card would be the appropriate
action. The detection may either be slow or, in very rare cases, not happen at all.
Impact: CDC1 control card suffering from the issue is automatically reloaded
and Packet buffer RAM reduced fault is raised during boot-up. While the problem
is not correctly isolated, the problematic CDC may disturb the other cards in the
network element, and hence disturb the control plane. Parts or all of the traffic in
the network element may be affected.
Risk of occurrence: Extremely rare.
Workaround: There is no preventive workaround.
The problematic CDC must be physically removed from the network element
and re-inserted.
PPN 09036
cq300241632 ELC1
When changing Ethernet interface speed with auto-negotiation enabled option
(e.g.mode auto...) in electrical SFP, the interface may remain in failed state. In
that case traffic does not pass through the interface.
"Rx Errors" and "FCS Check Failed" counters are increasing, but there is no fault
indicating the failure.
Impact: After changing Ethernet interface speed with autonegotiation enabled
option in electrical SFP, occasionally traffic does not pass through.
Risk of occurrence: Occasionally, when speed change is configured. More likely
to occur for an interface that starts using 100M bitrate. Very rare for an interface
that starts with 1000M.
Workaround: For 100M mode, forcing speed to 100M first (mode speed
100 duplex full), the interface starts to work, and can be configured to use
auto-negotiation as well (mode auto speed 100 duplex full).
For 1000M mode, reloading the unit will solve this issue.

57
cq300241663 IFC2
The CLI command 'queue leak-rate qos cs7' configures leak rates so that CS7 is
always leaking, although with the command 'no-leak' it should be treated as Strict
Priority. With the 'no-leak' command, the leak rate is misconfigured to be leaking
for every 255th packet.
Impact: Every 255th packet is given scheduling turn instead of Strict Priority
of CS7/EF. This could cause some small delay variation from the optimal SP
scheduling. There is also a theoretical situation where the CS7/EF queues are
almost full and the 255th scheduling turn would be required or the SP queue will
drop.
Risk of occurrence: In some extremely rare cases the SP queues might be
dropping due to leakage - this is however a very rare situation and should be
fixed by giving the SP queues enough capacity. This scenario would require the
SP queues to stay almost full for a long period of time, which is a relatively
theoretical situation.
cq300241665 IFC2
IFC2 may spontaneously reset when 1) it has an AC (either port, vlan-access or
vlan-trunk mode) in a VSI 2) the said VSI has 501 or more learned MACs 3) the
AC is unbound from the VSI, using Tellabs 8000 intelligent network manager or
the CLI command 'no bridging bridging-instance <bridge-name>'.
Impact: The line card will spontaneously reset. All traffic will be lost until the
unit comes up.
Workaround: Shut down the interface before removing it from the VSI.
cq300242238 CDC1, 8620 NE, IFC1, IFC2, ELC1

If BFD is removed from an interface when the interface has a defect, the defect
stays at least until BFD is configured again on the interface.
Impact: Loss of connectivity on old BFD supervised interfaces.
Risk of occurrence: Rare, but quite likely under the described circumstances.
Workaround: Never remove BFD configuration from an interface that has a
defect.
cq300242331 CDC1, CDC2

When the VRRP virtual address of the network element is incorrectly used as a
next hop and the VRRP interface is either shut down, or a link is cut, the control
units of the network element may reboot.
Impact: Data cut is encountered during network element reboot.
Risk of occurrence: Sometimes under the described circumstances.
Workaround: The VRRP virtual address of the network element should not be
used as next hop address, i.e. as gateways to other routes.
PPN 14005
cq300242610 CDC1, CDC2, 8620 NE

The reply to 'show running-config' does not show username description.
Risk of occurrence: Always with 'show running-config'.
Workaround: Use 'show user-list' instead.

58
cq300242864 CDC1, CDC2, IFC2, ELC1, 8620 NE

Y.1731 Loss Measurement: the BMI attribute "periodEndTime" has an out-of-date
value.
Impact: Since August 2013, Tellabs 8000 intelligent network manager has had
invalid period end time in Y.1731 Loss Measurement data.
cq300243074 8620 NE, IFC2

Modifying "sdh send-ssm" for a 8xSTM-1/OC-3 POS IFM (LIO2020) on the
affected line card or network element, crashes the card if the neighboring interface
module position also has POS IFM or the IFM position is empty.
On a Tellabs 8620 smart router with the same module combinations the command
spontaneously resets the node.
Impact: Connectivity is lost for the duration of the line card or network element
bootup.
cq300243077 IFC2
"MPLS Lookup RAM usage high" fault may be incorrectly raised, if MPLS
Lookup RAM is broken. If configuration is normal, so that the number of
pseudowires and incoming MPLS paths is not particularly high, then this fault
may actually be caused by faulty HW. The fault disappears with card reload, but in
case of faulty HW the line card needs to be replaced.
Impact: The fault is misleading, indicating user configuration error while the
actual problem is faulty HW.
Risk of occurrence: Rarely; only if hardware has a certain type of RAM failure.
cq300243433 CDC1, CDC2

'ip vrrp N accept-data' option does not work after CDC switchover. The situation
can be resolved with administrative down/up cycle of the VRRP interface, or
reloading the line unit.
Impact: The VRRP VIP does not accept data after CDC switchover. VRRP
instance still forwards traffic normally.
cq300243513 CDC1
After CDC switchover, Ethernet Bridging object instances are reported as having
unit 1 instead of the correct unit 14.
Impact: In the Bridging dialog in Tellabs 8000 intelligent network manager, the
right interface information cannot be mapped.

59
cq300243538 IFC1, IFC2

User sees MSP freeze alarm in case an IMA link is removed from an IMA group,
and the modified IMA group is located in MSP/APS protected interface.
Impact: There is not direct impact to live traffic. However, MSP freeze prevents
MSP protection switchovers and thus IMA traffic is affected if line or equipment
failure occurs on the active MSP protected interface.
Risk of occurrence: Always when IMA links are removed from IMA group
configuration.
Workaround: Avoid removal of existing IMA links from IMA group. Reboot
passive side line card during maintenance window when MSP freeze alarm is
detected.
cq300243803 ELC1
Fixed 1000M configuration will not be accepted for optical SFP in the ELC1
line card.
Impact: Disabling autonegotiation for 1000M speed will not be possible in optical
SFP in ELC1. So the interface will always work with default configuration ("mode
auto" - autonegotiation enabled and 1000M speed).
Traffic will not flow if the peer end is configured in fixed 1000M mode. However,
there will be no traffic loss if the peer is also operating in auto 1000M mode.
Risk of occurrence: The issue will be observed always when the user tries to
configure fixed 1000M speed - "mode speed 1000 duplex full". The command will
not be accepted.
cq300244103 IFC1
If the configuration has Ethernet VLAN PWE3s with VC QoS and the VLAN IDs
are consecutively configured, after upgrade to the SR5.0 CIR3 image there will be
complete traffic loss. This will happen to PWE3s that are on VLAN IDs divisble
by 8.For example, if VLAN ISs from 200 to 207 are present with PWE3s and VC
QoS configurations are also present, then after the upgrade the traffic will stop
flowing. The starting VLAN ID needs to be divisible by 8.
This does not happen on an upgarde to SR5.0 GA image.
Impact: Traffic stops on the Ethernet PWE3s that meet the described conditions.
Workaround: Unbind and bind the PWE3 on that non-traffic flowing interface.
cq300244119 IFC1
During restoration, the same PPP member is getting restored for two different mp
bundles. Misconfiguration is seen in the snapshot database. The database files
of the snapshot config consists of the same member added to two different mp
bundles. The wrong information in snapshot database needs to be cleaned up.
Impact: The "show running config" command does not return full
configurations.Occassionally, Slot crash can be seen during "show running config"
command execution.

60
cq300244143 CDC2, CDC1

Tellabs 8000 intelligent network manager is not able to indicate that Loss
Measurement performance data for the current period may not be reliable, because
the data has not been received correctly from the network element.
Impact: "Loss Measurement performance data for the current period not reliable"
information missing from Tellabs 8000 intelligent network manager.
Workaround: Use CLI to obtain the information. CLI command:
"show eth cfm mp [ name mp-name ] [ rmep mep-id ] lm [ qos { cs7 | ef | af1 |
af2 | af3 | af4 | be } ]".
cq300244243 IFC2, ELC1

If there are multiple VRRP routers all having priority 0, all routers will become
master competing for the mastership. This can happen if priority is dropped to
zero due to tracking.
Impact: Unnecessary VRRP advertisements are sent creating load to the network
and the routers.
Risk of occurrence: Always when multiple VRRP routers all have priority 0.
Workaround: Make sure that the priority of all the VRRP routers cannot drop
to zero.
cq300244294 CDC1
A significant CPU load is experienced in Tellabs 8660 smart router and Tellabs
8630 smart router in case VCCV is used and there are many interface state changes
in ELP protected interfaces. This causes unstable behavior in ELP protection
interfaces, and eventually the affected line cards need to be reloaded.
Impact: The state of the ELP interfaces on the line card becomes unstable and a
reload of the software is needed.
cq300244295 IFC1, IFC2

When MS-RDI is injected from the SDH tester to 4xchSTM-1/chOC-3 (LIO2234)
or 1xchSTM-1/chOC-3 (LIO2203) Multiservice IFMs, L-bit is set in the PWE3
packet transmitted over PSN. L-bit should not be set for MS-RDI defect.
Impact: MS-RDI indicatesa defect at the remote end. The data is still valid. Since
the L-bit is set in the PWE3 packet, the packet is dropped at the other end of PWE3.
4.3 Version 4.1.466 (FP4.1 CIR3)
This version is intended for controlled introduction of the FP4.1 ESW. This version should not be
used after the general availability has been reached and a new version is available.
4.3.1 Enhancements Compared to 4.1.323 (FP4.1 CIR2.1 Fast Lane)

cq300238879 CBZ2745
When software version was changed, the binary log did not have proper task name
mapping in the parsed output. This incompatibility has been now fixed.
cq300239970 CBZ2712, SBZ2714

Improved relative priority of processing incoming IS-IS hello packets (to high
degree) and other incoming IS-IS packets (to lesser degree) over processing
internal CSPF processing and other IS-IS activities.

61
4.3.2 Fixed Bugs Compared to 4.1.323 (FP4.1 CIR2.1 Fast Lane)

cq300161281 SBZ2714, CBZ2712, CBZ2745
When multiple ISIS areas (multiple 'router isis' instances) are in use, if re-distribute
of external protocol (not isis inter-level redistribution) is removed and then
re-added to one of the areas, routes are not re-distributed.
Impact: Routes are not redistributed to the given ISIS area.
Risk of occurrence: Always under the described circumstances. Does not occur
spontaneously.
Workaround: When re-enabling redistribution, include one of the following
optional parameters: metric, metric-type, route-map (route-map is only available
in SR5.0 and later).
cq300186200 CBZ2712
If the CLI server task in CDC is busy performing some operation, it may miss the
software upgrade performed on IFC. After that the next CLI command given to
that IFC points to a wrong part in the code.
Impact: Usually the function pointer changes with the software version and when
a wrong part of the program is executed the IFC goes to spontaneous reset.
Risk of occurrence: Only rarely during upgrade.
Workaround: Having only one CLI session to the network element should
prevent this. If multiple sessions are open, they should not be performing
commands when the "reload" CLI command is given for the upgraded IFC.
cq300212200 SBZ2714
When an ATM member of the VCG group is removed and added again to the same
VCG group whose AIS is ON, the newly added member does not send AIS cells.
AIS state is currently set to the VCG members only when the AIS state changes
happen, not on the deletion/addition of members.
Impact: When a VCG group sends OAM cells (AIS) and when one of the ATM
VCG members is removed and added again, it will not send AIS, while the other
existing members of the group continue to send AIS. The newly added member
does not inherit the AIS ON state of the VCG group to which it is added.
cq300222402 CBZ2712
When a fuse blows in Tellabs 8660 R2 subrack Power Input Module (PIM2296),
it cannot be detected. The fuse blow detection requires ESW support which is
currently missing.The ESW should detect blown fuse and turn off the LED on
the Power Input Module (PIM2296).
Impact: The network element power input is off, if the fuse in both Power Input
Modules (PIM2296) blow simultaneously.
cq300223643 LBZ2713, LBZ2754

Currently there is no separate counter for flooded packets and they will be counted
as part of the discarded packets. This can be seen via the 'show interface' command
for the IFC1 and ELC1 line cards.

62
cq300227210 LBZ2713, LBZ2741

If VLAN PRI mappings are changed at runtime, the change does not apply to
control messages (e.g. BGP protocol). Any VLAN traffic passing via this path
will experience the same issue.
Impact: Control messages are transferred with incorrect VLAN PRI bits.
Workaround: Entering the "shutdown" and "no shutdown" CLI commands for
the parent interface will solve the issue.
cq300231048 CBZ2712
During VRF removal, VRF might not always be removed correctly.
Risk of occurrence: Sometimes when interfaces are configured to a certain VRF.
cq300232502 LBZ2713, LBZ2741, LBZ2754

The fault 'sync source blocked off' behaves inconsistently and may be raised for
ports that do not have SFP installed. This alarm should only be raised if the port is
confirmed to be non-SyncE capable (eg. 10BASE-TX or Electrical Ethernet SFP).
cq300234696 CBZ2712, CBZ2745, SBZ2714

Storing command history log may fail.
Impact: Command history is not complete and lots of 'CCN: zipping CCN log
failed, len=61440' warnings in os-log.
Workaround: In order to store the whole command history, save it to flash before
reloading the unit.
cq300235211 CBZ2712
After reloading a line card, the following harmless but misleading error print
is output into the console and system logs: "unit_state.c:284::Reconf. failure
reason: TD_NOT_RESPONDING & INV_NOT_IN_INVENTORY, unit 2
Reconf failure:..."
cq300235455 LBZ2754
Penultimate hop popping does not work in ELC1.
Impact: Penultimate hop popping cannot be used with ELC1 configurations.
cq300235653 LBZ2741, CBZ2745

The maximum amount of configurable Ethernet OAM MEPs on IFC2 is limited to
505 entries. This figure will decrease if IRB is configured on the same IFC2 card.
Impact: Ethernet OAM and IRB entries configured earlier may not work anymore
after upgrade to FP4.1 if the limit of 505 entries is exceeded.

63
cq300235906 LBZ2741
When two routes are established for the same destination through two different
LAG interfaces, traffic will flow through the LAG interface with higher bandwidth.
When some members are removed and added again to the LAG group having
higher bandwidth, traffic is not flowing through that interface, instead it is flowing
through the lower bandwidth one.
Impact: Traffic will not flow through the LAG interface having higher bandwidth
when members are removed and added. Instead, traffic will flow through the
LAG having lower bandwidth.
Risk of occurrence: Rare. Only when members are removed and added.
cq300236056 LBZ2754, LBZ2741

If a unit is rebooted a short time after there has been a configuration action in a
LAG group having a large number of members and a large number of VLANs, the
unit may spontaneously reboot a second time during the boot-up sequence.
Impact: This issue occurs only in the following scenario:
1) Create a LAG group with eight members.
2) Enable the admin-state for all members.
3) Create the maximun amount of VLANs for the group (i.e. 227).
4) Remove seven (non-master) members from the LAG group.
5) Add seven members to the LAG group.
6) Quickly issue a reload-sw command.
While reloading, an error similar to the following may be seen on the console:
"restoreIf2: Slp group parent(ifndex 0) not found for ifIndex 5562"
After that the network element may reset spontaneously. It then recovers and
everything works as expected.
cq300236273 LBZ2741
After giving the 'no shutdown-if' command for an interface port in
8x10/100/1000BASE-TX R2 IFM (LIE2256), the interface is erroneously enabled
with default speed (1000 Mbps). If the port is connected to a far end that does
not support 1000Mbps speed, traffic will not flow through the interface after the
'no shutdown-if' command is issued.
Impact: When 8x10/100/1000BASE-TX R2 IFM (LIE2256) is connected to a far
end that does not support 1000Mbps speed, the traffic will not flow through the
interface after the 'no shutdown-if' command is issued.
Workaround: Configure 'mode speed auto 100M full duplex' on the
8x10/100/1000BASE-TX R2 IFM (LIE2256) port in case the remote end is not
capable of 1G.
cq300236450 CBZ2712, CBZ2745, SBZ2714

If SNMP Traps are enabled, the active control unit or single-unit network element
goes occasionally to spontaneous reset.
Impact: Traffic is not affected in a system with CDC/SCM equipment protection.
In other systems traffic is affected when the network element resets.
Workaround: Disable SNMP Traps.

64
cq300236897 LBZ2754, LBZ2713, LBZ2741

After creating an ELP group, the first laser activation on a interface turns the
laser OFF.
Impact: Laser transmitter may remain turned OFF in an Ethernet interface
belonging to an ELP group.
Risk of occurrence: Only the first laser activation fails after ELP group creation.
Workaround: After creating an ELP group, the laser transmitter should be
enabled twice.
cq300237592 LBZ2741
Disabling the VLAN in-QoS statistics in a VLAN interface associated with a
bridging instance causes the line card spontaneous reset. Also enabling VLAN
in-QoS statistics in a bridging instance attached interface fails but works, if it is
done in a VLAN interface before associating the interface with a bridging instance.
Impact: Traffic affecting because the line card goes to spontaneous reset.
PPN 13058
cq300237746 CBZ2712, SBZ2714

When traffic is sent to a connected route subnet destination before a new host (/32)
route is added under the same subnet IP address, IP stack internal routing entry
(cloned route) prevents adding the same (non-cloned) entry to the routing table.
Workaround: Shutdown-if is known to remove the inconsistency of routing
tables.
cq300238202 CBZ2712, LBZ2741, LBZ2713, CBZ2745

1. Traffic will not be load balanced for qos if the map route of qos is deleted
and recreated in RSVP trunk. It may or may not affect traffic. 2. Deletion and
Reconfiguration of rsvp trunks alternatively when two trunks are configured will
affect the load balancing with IP_VPN_VRF.
Impact: 1,Traffic will not be load balanced, due to which traffic may or may not
be dropped. 2. Traffic will not flow in the reconfigured trunk.
Workaround: 1. Clear other RSVP trunks that have the same map route qos.
I.e. if RSVP trunk T1 and T2 have qos map route configured and qos map route
is deleted and recreated in T2, clear RSVP trunk T1.
2. Delete and recreate the same qos map route in another RSVP session mapped to
the same destination, i.e. if RSVP trunk T1 and T2 have qos map route configured
and qos map route is deleted and recreated in T2, delete and recreate the same qos
map route in T1.
3. If the intention is to change the weights by removing and reconfiguring, modify
the weights alone instead of removing.

65
cq300238328 CBZ2712, SBZ2714, CBZ2745

The 'control-word ordered' option is removed from a pseudowire when that
pseudowire is bound to a MS-PW switching point at S-PE. Pseudowire endpoints
define the usage of control word. Because of that the option cannot do anything
when pseudowire is bound to the switching point, thus the option is removed.
There are two issues related to this that can cause confusion. One is that the option
'control-word ordered' is silently removed when the pseudowire is bound to the
switching point. The other is that it is possible to use pseudowire configuration
commands to reconfigure the 'control-word ordered' option after pseudowire is
bound to switching point.
Workaround: The 'control-word ordered' option should not be used with
pseudowires that are bound to switching points.
cq300238627 CBZ2712, CBZ2745, SBZ2714

It is not possible to set infinite duration for keychain keys.
Workaround: Use an end date far enough in the future.
cq300238636 CBZ2712, CBZ2745

A Tellabs 8600 network element may at times resolve ISIS router instance name
of routes incorrectly. Instead of showing the correct ISIS peer router, "isis (null)"
is shown with the CLI command 'show ip route'.
Risk of occurrence: Frequently under the described circumstances.
cq300238637 LBZ2754
In Tellabs 8630 smart router and Tellabs 8660 smart router, if Ethernet PWE3
redundancy is set up with service-policer attached to the endpoint interfaces, the
traffic will not get policed for the backup interface. When the primary PWE3 is
active, traffic will be correctly policed in both directions. But when the primary
PWE3 goes down and the backup PWE3 is active, the policer is not working and
all data will go through in both directions.
Impact: Traffic will not be policed when the backup interface is active in the
PWE3 redundancy group.
cq300238930 LBZ2741, CBZ2745

Unnecessary console error "ERROR : VPLS:Learning Entry Pool Empty " shown
for IFC2 slot under heavy mac learning load.
cq300239002 CBZ2712, LBZ2713, LBZ2741, LBZ2754, SBZ2714, CBZ2745

Interface removal may in some very rare cases cause false handling of those
packets that are received from the removed interface, if such packets are in the
receive queue.
Impact: False packet handling may cause spontaneous reset of the network
element.

66
cq300239013 LBZ2754
MTU configuration might cause an error message if done when the interface is
in "shutdown" mode.
Impact: If the MTU value is configured in shutdown mode, an error message
may be logged.
Workaround: MTU configuration needs to be done in "no shutdown" mode.
cq300239034 CBZ2712, CBZ2745, SBZ2714

VCCV may truncate message bundles that have over 50 messages.
Impact: Some interfaces may have incorrect configuration.
Workaround: Set interface to shutdown and then to no shutdown.
cq300239123 LBZ2713, LBZ2741, SBZ2714

The Performance Management (PM) counters will not start counting
for CESoP/SAToP when there is already configured one or more
PPP/MLPPP/ATM/IMA/CESOP/SATOP in the same physical interface.
This is applicable for 4xchSTM-1/chOC-3 Multiservice IFM (LIO2234) and
1xchSTM-1/chOC-3 Multiservice IFM (LIO2203), 24xchE1/chT1 Multiservice
IFM (LIE2226) and 8xchE1/chT1 LM (LMP2242) when configured in different
timeslot groups.
Impact: The PM monitoring will not work for the CESoP/SAToP interface. The
functionality of the CESoP/SAToP interface is not affected. The PWE3 will be up
and traffic will flow as expected. Also the PWE3 circuit and interface statistics
will work.
Workaround: Reboot the line card.
This will make the PM counters work as expected.
cq300239131 CBZ2745, CBZ2712

The new active CDC may reset spontaneously after CDC switchover when PWE3
interface is bound to MPLS tunnel locating in a LAG interface. Observed only
when activity is changed from CDC1 to CDC2 during CDC1 to CDC2 upgrade,
but in theory possible in all types of switchovers. Spontaneous reset of CDC2
may cause also simultaneous CDC1 reset when the network element is totally
unresponsive for a while.
Impact: The network element will go to spontaneous reset.
Risk of occurrence: Almost always under the described circumstances.
Workaround: Do not use PWE3 interface bound to MPLS tunnel locating in
LAG interface with CDC2.
cq300239137 CBZ2712, CBZ2745, SBZ2714

Due to an issue in command line handling, the following operations may cause
CDC to reset spontaneously due to a heavy CLI load:
1. Telnet session times out
2. Control cards switch over
3. Superuser forces other users to log out
4. User logs out.
Impact: CDC may go to spontaneous reset due to a heavy CLI load.

67
cq300239293 CBZ2712, CBZ2745, SBZ2714, LBZ2741

While trying to ping an IRB interface for the first time (MAC not learned yet), the
second ping packet is timed out. All subsequent ping attempts are working fine.
Impact: One ping packet is lost when pinging an IRB interface for the first time
before MAC has been learned. No other impact.
cq300239369 CBZ2745, CBZ2712

Replacing of a passive CDC2 card may cause flapping of IP BFD sessions during
the boot-up of the passive CDC2 card.
Impact: Protocol sessions may go down temporarily.
Workaround: Replace CDC2 during a maintenance window.
cq300239475 CBZ2712, CBZ2745

An IMA interface that is flapping at high frequency causes excessive CPU load on
the control card. High CPU load has direct impact on the amount of control traffic
the card can handle. The following group interface types are affected in addition
to IMA: ABIS, MLPPP and ATM VCG.
Impact: Protocols (RSVP, OSPF, LDP, ISIS, etc) may go down due to excessive
CPU load on the control card.
Workaround: If IMA interface flapping is detected, to prevent the issue configure
IMA min-links higher than the actual link amount so that IMA group is going
down, then flapping IMA members will not affect the CDC CPU load.
cq300239509 CBZ2712, SBZ2714

The ’show running-config’ command may not always work properly in case the
network element has a large IP configuration. For instance, the user may not be
able to retrieve an IP configuration containing over 1000 lines.
Impact: ’show running-config' does not work for large IP configurations.
Risk of occurrence: Always when the configuration of any configuration segment
is large.
cq300239529 CBZ2712, CBZ2745

When the power from the passive CDC is switched off, the logic levels of the
I2C bus are not within the specification. Fans are controlled via IC2 bus and fan
modules of the Tellabs 8660 smart router R2 subrack misinterpret the control
messages due to the power outage. This causes the faulty fans alarm.
Impact: Faulty fans alarm is risen although the fans are functional.
Risk of occurrence: When a short power break with a duration of 5s occurs.
cq300239584 CBZ2745, CBZ2712

Serial console port or telnet access to CDC may get blocked if any MPLS or Eth
variants of ping or traceroute are used and protecting is switched. The freezing
happens when an IP related command is used after protection switch.
Impact: Serial console and/or telnet sessions are stuck. Operations using Tellabs
8000 intelligent network manager are not affected.
Risk of occurrence: Occasionally.
Workaround: Apply 'mpls/eth ping' as the first command in session or use
ping/traceroute only via Tellabs 8000 intelligent network manager. If some of the
sessions are stuck, reload the software on the protecting side and switch there,
then repeat the process.

68
cq300239705 LBZ2713
When eight consecutive VLANs (8 - 15, 16 - 23, 24 - 31, and so on)
are used to attach PWE with encapsulation as untagged on IFC1 with
2+6x10/100/1000BASE-COMBO or 8x1000BASE-X IFM modules, the IFC1
will go in a continuous reconfiguration loop and sessions configured on these
modules will flap.
Impact: Traffic loss due to flapping sessions.
Workaround: Avoid creating eight consecutive VLANs while attaching PWE
with untagged option.
cq300239758 CBZ2712, CBZ2745

It is not possible to reuse the same PWE3 circuit as VPLS spoke once it has been
removed.
Workaround: Reload the software on both CDCs.
cq300239771 CBZ2712
Tellabs 8000 intelligent network manager is not able to use lmep in mepfilter in any
ethrCfm history data command. If that filter selection is used, an error is returned.
Workaround: Do not filter by lmep name.
cq300239810 LBZ2713
IFC1 with 24xchE1/chT1 multiservice IFMs does not start up properly if it has
EoMLPPP+SATOP or IMA configurations.
Impact: It is not possible to create more than 24 ethoany interfaces at node level.
cq300239842 CBZ2712, SBZ2714

Use of quotation marks in ISIS router name leads to router instance ghosts. Use
of empty ISIS router instance name may cause the protecting unit to reload the
software.
Workaround: Do not use quotation marks " or ' in names. Do not use an empty
name for an ISIS router instance.
cq300239886 CBZ2712, SBZ2714

The CLI of the active CDC may get stuck in certain situations.
Impact: CLI stops responding (all Telnet and console connections).
Risk of occurrence: Very rare.
Workaround: In the case of CDC card, switch CDC activity using Tellabs 8000
intelligent network manager and after that reload the previously active CDC.
cq300239912 LBZ2741
Ping does not work when configuring 'mode auto' in one end and 'mode auto speed
[10/100] duplex [full/half]' in the other end with IFC2/LIE2256 IFM.
Impact: The issue will be there always when configuring 'mode auto' in one end
and 'mode auto speed [10/100] duplex [full/half]' in the other end.
Workaround: E.g. use the same configuration at boths ends.

69
cq300239980 CBZ2712, LBZ2741

Setting a virtual switching instance (VSI) administratively down (shutdown) stops
multicast traffic and disables MAC learning, but does not have effect on the
unicast traffic with already learned MAC addresses.
Impact: A VSI forwards unicast traffic even when it is set administratively down
(shutdown).
cq300239983 CBZ2712, LBZ2741

The configuration refresh logic for IFC IRB and MAC switching during CDC
switchover and line card reconfiguration is sub-optimal. This degrades somewhat
the tolerancy against internal data corruption caused by ESW malfunction.
Impact: Recovery from some classes of rare ESW-internal data corruptions
is compromised. This may lead to resource leakage or forwarding hardware
misconfiguration in the rare cases where an unknown ESW fault has corrupted the
ESW internal data in a way that would get repaired by a flawless refresh sequence.
cq300239984 LBZ2741
CLI command 'qos mapping use egress traffic layer2-frame' is always enabled for
SLIs connected to a VSI, so only the mappings defined by 'qos mapping egress
qos' always take effect. CLI command 'qos vlan ingress/egress vlan-pri' does not
take effect, instead the mappings defined by 'qos mapping ingress/egress qos'
always take effect.
Impact: It is not possible to override 'qos mapping ingress/egress qos' by the
commands specified above. You should always define specific mappings between
PRI and internal QoS both ingress and egress to ensure correct PRI for Ethernet
services.
cq300239985 LBZ2741
Synchronous Ethernet does not work over switched interfaces.
Impact: The network element is not locked to the configured clock source, if the
clock source is behind the switching interface.
cq300240029 CBZ2712, CBZ2745

When a network element is undergoing CDC1 to CDC2 upgrade, the passive
CDC2 may spontaneously reset if certain 'show' commands are executed.
Impact: The passive CDC may reset spontaneously. Does not affect live traffic.
Workaround: Disable terminal monitor messages during the passive CDC
replacement.
cq300240226 LBZ2754
VRRP activation in the network element will cause all incoming VRRP traffic
to be mapped to best effort QoS class.
Impact: All VRRP traffic will be mapped to BE QoS class.
Risk of occurrence: Always when VRRP interface is used.

70
cq300240398 LBZ2754
Using ACL deny rule with VRRP traffic may disrupt traffic on the ELC1 card.
Impact: Loss of traffic on the ELC1 card.
Risk of occurrence: High under the described circumstances.
Workaround: ACL should not be used with VRRP traffic.
cq300240525 CBZ2712, CBZ2745, LBZ2741, LBZ2713

Traffic flooding is observed with IRB configuration.
Impact: Traffic through IRB is sometimes flooded, even though MAC is learned.
cq300240571 LBZ2741, CBZ2712, CBZ2745, LBZ2754, LBZ2713

ESW error in legacy IRB ARP handling code causes occasional unit reboots when
IRB is in use.
Impact: Unit reboots when legacy IRB in use (approximately once or a few
times a day).
cq300240869 CBZ2712, SBZ2714

After two retries for opening a TCP session, SYN options are changed to not
include the Window scale and Timestamp options. The other end may still try to
use the original Window scale option, which degrades TCP session performance.
Impact: TCP sessions performance is degraded when the situation occurs.
Risk of occurrence: Quite rare as it needs certain time-dependent network actions
to occur.
Workaround: Sessions may be restarted manually to re-establish TCP session
with the proper parameters.
cq300240888 LBZ2754
The correction field of IEEE1588 Delay_Req messages is not set to zero as
required by IEEE1588-2008/11.3.2.
Impact: May cause synchronization failure if the correction field is being updated
by other NEs in the network.
cq300241315 CBZ2712, CBZ2745, SBZ2714

Dynamic targeted peers are not expired (deleted) if targeted-peer-hello-receipt is
unconfigured.
Impact: Existing dynamic LDP targeted peers remain even if
targeted-peer-hello-receipt is unconfigured.
There is no adverse effect to data forwarding.
Risk of occurrence: When disabling targeted-peer-hello-receipt in LDP and
dynamic peers exist.
Typically Tellabs 8600 customers only use manually configured LDP targeted
peers.
Workaround: To delete extra dynamic peers, configure them as static and then
delete static peer after having disabled targeted-peer-hello-receipt.
cq300241508 CBZ2712
IP configuration is not mirrored to the protecting unit in case it differs only for
instace IDs or other minor details that do not change the length of the configuration.
Impact: The unit is not fully protected.

71
cq300241566 LBZ2713, LBZ2741

In case there are over 100 interface protection state changes in a time frame of
a few seconds, state change handling gets stuck. This may happen if protection
group is created/deleted and it contains 100 or more interfaces.
Impact: VCCV does not work correctly for the affected interfaces.
Workaround: Limit the number of interfaces in each protection group to max.
99 interfaces.
4.4 Version 4.1.323 (FP4.1 CIR2.1 Fast Lane)
This is a fast lane version with a limited distribution released to fix a potentially critical problem.
This version can be obtained by contacting Tellabs technical support.

cq300239584 CBZ2712, CBZ2745
Serial console port or telnet access to CDC may get blocked if any MPLS or Eth
variants of ping or traceroute are used and protecting is switched. The freezing
happens when an IP related command is used after protection switch.
Impact: Serial console and/or telnet sessions are stuck. Operations using Tellabs
8000 intelligent network manager are not affected.
Workaround: Apply 'mpls/eth ping' as the first command in session or use
ping/traceroute only via Tellabs 8000 intelligent network manager.
If some of the sessions are stuck, reload the software on the protecting side and
switch there, then repeat the process.
cq300239758 CBZ2712, CBZ2745

It is not possible to reuse the same PWE3 circuit as VPLS spoke once it has been
removed.
Workaround: Reload the software on both CDCs.
cq300240226 LBZ2754
VRRP activation in the network element will cause all incoming VRRP traffic
to be mapped to best effort QoS class.
Impact: All VRRP traffic will be mapped to BE QoS class.
Risk of occurrence: Always when VRRP interface is used.
cq300240398 LBZ2754
Using ACL deny rule with VRRP traffic may disrupt traffic on the ELC1 card.
Impact: Loss of traffic on the ELC1 card.
Workaround: ACL should not be used with VRRP traffic.
4.5 Version 4.1.322 (FP4.1 CIR2)
This version is intended for controlled introduction of the FP4.1 ESW. This version should not be
used after the general availability has been reached and a new version is available.

72
4.5.1 Enhancements Compared to 4.1.182 (FP4.1 CIR1)

cq300195650 LBZ2713
BGP network statement support added to BGP VRF mode.
cq300222735 LBZ2713, LBZ2741

Support added in BMI ('bandwidth-if' command) to change Adjustable Forwarding
Capacity (Bandwidth Allocation) of 4*chSTM-1.
cq300235198 CBZ2712, CBZ2745, SBZ2714

Improved ISIS stability under heavy load by preferred queuing of ISIS hello
frames over other ISIS frame types.
cq300236911 CBZ2712, CBZ2745

Tellabs 8600 mac address withdraw is implemented as specified in RFC4762 and
draft-ietf-l2vpn-vpls-ldp-mac-opt-06. The incoming pseudowire is used to limit
the scope of the mac withdraw. On some other implementations the incoming
pseudowire is not used. Those routers do not support inverted wildcard rule with
mac withdraw. Instead an empty mac list is used with the expectation that all macs
from that particular vpls instance are removed. As Tellabs 8600 limits the scope of
mac withdraw as specified in RFC4762, some mac addresses are not removed as
expected when an empty mac list is used.

cq300183257 LBZ2713, LBZ2741, SBZ2714
VC-12 equipment loop does not work on 4xSTM-1/OC-3 ATM IFM (LIA2210) if
there are SDH defects in the line.
Impact: Setting equipment loop on VC-12 level (e.g. IMA links) does not work if
there are SDH defects present in the signal.
cq300187323 LBZ2713
When more than 512 pseudowires are configured on pdh interfaces, 'unexpected
error' is returned in CLI.
Impact: It will not be possible to configure more than 512 CESoP/SAToP
pseudowires.
Risk of occurrence: Occurs only when trying to attach more than 512
pseudowires on pdh interface.
cq300193575 LBZ2713, LBZ2741, SBZ2714

ATM CAC may not work properly when existing interfaces are deleted and other
interface service classes are modified to CBR. This may cause the total committed
PCR for that port (across all interfaces) to exceed the port bandwidth.
Impact: There may be congestion drops due to over-subscription (at PCR) on
the ATM interface.
Risk of occurrence: It will occur only if the user deletes existing interfaces and
then modifies a remaining ATM VP/VC on the same interface to the CBR service
class.
Workaround: When adding to modifying ATM VP/VC interfaces, delete the
interface and recreate it with the new service-class rather than just modifying
the service class.

73
cq300194309 LBZ2713, LBZ2741

CLI command "show interface" may occasionally fail due to high CPU load in
line card.
Impact: No information is retrieved when the "show interface" CLI command
is targeted to an interface in a line card under high CPU load. The line card may
experience high CPU load when the network element is being heavily configured.
Workaround: CLI command "show interface" works normally after high CPU
condition is over.
cq300194471 LBZ2713, LBZ2741, SBZ2714

The network element returns an unexpected error when a VCG (Virtual Circuit
Group) having one or more VP/VC members is being deleted.
Impact: The operation itself is unsupported and it is correctly denied, but the
error code is misleading.
Workaround: Delete all VP/VC members for VCG before deleting the VCG
group.
cq300194656 LBZ2713, LBZ2741, SBZ2714

Attempting to delete jitter buffer parameters when they do not exist results in
an CLI internal error.
Impact: This issue does not affect actual payload or traffic, but is a CLI
provisioning error. The error is not properly reported to a user, but it does not
cause other harmful effects.
Workaround: Applying the CLI command "no pdh pwe3 jitter-buffer" to a
non-existing SAToP or CESoP interface should be avoided.
cq300223745 LBZ2713, LBZ2741

Some SFPs may have laser transmitter failure signal on for some time after they
have been inserted in the network element. If periodical IFM health check is
performed during that time, a HW fault is set ON. The fault is cleared after ten
seconds when the next health check is made.
Impact: It is possible that the IFC is declared temporarily faulty and the
ELP/MSP1+1/APS1+1 protection groups that have the OK signal on the pair
IFC are switched.
Risk of occurrence: Depends on the SFP type.
cq300226320 LBZ2741
LAG does not support synchronous Ethernet. Therefore links added in a LAG
group cannot send SSM messages.
Risk of occurrence: Always when SSM is configured.
Workaround: Disable SSM with the "no-ssm" CLI command.

74
cq300227306 SBZ2714, LBZ2713, LBZ2741

Traffic entering a VLAN PWE3 in Tellabs 8600 with VLAN PRI bits mapped
in ingress into AF2 and AF3 traffic classes are dropped in the traffic policer if
the traffic policer is configured to take into account the existing coloring (CLI
command "use-pre-set-markings").
Impact: Traffic drop in the described scenario.
Workaround: Workaround options are:
a) Make the policer unaware of the existing color, by removing the
"use-pre-set-markings" parameter from the marker, or
b) Modify NE-wide or interface specific QoS mappings with "qos mapping ingress
vlan-pri" CLI commands so that no VLAN PRI value is mapped to the AF2 or
AF3 traffic class.
PPN 13021
cq300228198 LBZ2741, LBZ2741

PWE3 performance counters are showing higher value than expected when VCCV
BFD is enabled for the connection.
Impact: PWE3 counter value is not reliable.
Risk of occurrence: Always when VCCV BFD configuration is applied.
cq300229929 LBZ2741, LBZ2741, LBZ2754

The help text is incorrect for the CLI on 'no-ccm' option (cfg-if[xe3/0/1])#eth
cfm ma elc1_ethoam_ma mep remote 100 ?, displaying 'Disable sending
Continuity Check Messages'. The help text should say "Disable CCM receive-side
monitoring".
cq300230657 LBZ2741
Illegal configuration involving both port SLI and VLAN SLI(s) in the same port
disables traffic permanently on IFC2, when port SLI configuration is removed.
Impact: When illegal configuration involving both port SLI and VLAN SLI(s) in
the same port is applied, no recovery without some loss of traffic is possible.
Workaround: Avoiding illegal configuration.
cq300231010 LBZ2754
The line loop in ELC1 (both one-Gigabit (12x1000BASE-X) and 10-Gigabit
(2x10GBASE-R) ports) works in such a way that traffic is looped back properly
but also a copy is sent forward.
Impact: Traffic is seen also in the forwarded path even though expected to be
only looped back.

75
cq300232833 LBZ2713
Interface specific ingress QoS mappings do not work correctly for certain
configuration types for IFC1 hardware running ESW FP4.0 or newer. The
problem affects:
1) VLAN PWE attachment circuits where the QoS classification is configured to
be taken from the VLAN PRI bits, and
2) VLAN interfaces where an IP tunnel is terminated (MPLS over IP over VLAN)
and the QoS classification is taken from either the VLAN PRI or IP DSCP bits.
Due to wrong initialization, the erroneous QoS mapping behavior depends on the
HW module type as follows:
- All ports in 8xFE modules (LIE2018v2 and LIO2028) use "qos mapping ingress"
configured to physical port 0
- All ports in 8xGE module (LIO2208) use "qos mapping ingress" configured
to physical port 7
- All ports in combo module (LIC2231) use "qos mapping ingress" configured
to physical port 4.
If no mapping is set in the port defined above, all ports in all the above module
types use node global mappings.
The problem does not affect other traffic and configuration types, e.g. IP or MPLS
forwarding or other HW besides IFC1.
Impact: Traffic is forwarded with incorrect QoS classification. In a congested
link traffic may be dropped due to wrong classification.
Workaround: Use only node global ingress QoS mappings in interface modules
where the problematic configuration is used.
PPN 13051
cq300233286 LBZ2754, SBZ2714, LBZ2741, LBZ2713, CBZ2745

In case SSM messages are flooded in the network, this may result in spontaneous
reset of the receiving Tellabs 8600 line card. This may happen for instance
if several SyncE aware switches/routers are aggregated by SyncE non-aware
switch/router and all SSMs forwarded to an ELC1 port.
The root cause is a bug in the Rx SSM buffer overflow handling that causes fatal
error detection and consequently forced reboot of the unit. In lab conditions this
was repeatable when 10000 SSMs per second were sent to an ELC1 port.
Impact: Line card SW will reset spontaneously.
Risk of occurrence: Low. In SyncE aware networks such SSM floods should be
non-existent.
Workaround: The SSM flood scenario should be possible only if there are
non-SyncE capable units in the network. In this case the sending of SSMs should
be disabled from all SyncE capable units.
cq300233905 LBZ2713, LBZ2713

The “no laser” command does not disable the laser on the 2x1000BASE-X IFM
(LIO2019). Additionally, the TX and RX power values as output of the command
'show hw-inventory slot <slot number> details', display some values instead of
displaying "disabled".
Impact: Never look into the laser or fiber to verify operation. Optic operation
should be verified by observing the status LEDs.
PPN 13045

76
cq300233958 LBZ2741
Tellabs 8630 smart router and Tellabs 8660 smart router LAG PWE3 does not
display any counter fields similar to ethernet PWE3 statistics.
The implementation to display the pwe3 statistics for ethernet interface is not yet
done in case of Tellabs 8630 smart router and Tellabs 8660 smart router, hence
the same is applicable to LAG interface as well in Tellabs 8630 smart router and
Tellabs 8660 smart router.
Risk of occurrence: This issue occurs always in Tellabs 8630 smart router and
Tellabs 8660 smart router when "show pwe3 statistics" command is executed and
when pwe3 is attached to ETHERNET/LAG interface.
cq300234246 LBZ2741
VCCV ping/traceroute is not working when PWE is attached to LAG/LAG VLAN
interface in Tellabs 8630 smart router or Tellabs 8660 smart router.
Impact: VCCV ping/traceroute fails when PWE3 is attached to LAG interface in
Tellabs 8630 smart router or Tellabs 8660 smart router, but this does not have any
impact on traffic. After the fix VCCV ping/traceroute works as expected.
cq300234327 LBZ2741
Link aggregation (LAG) logic managing the mapping from hash result to physical
port has a bug that sometimes causes the packet to be sent to physical port
calculated for the previous packet of the same LAG group.
Impact: Packets mapped to the wrong physical port can result in packets of one
stream not arriving to the destination in sequential order.
Risk of occurrence: In the worst case seen 3 % of packets were out-of-stream.
PPN 13067
cq300234424 LBZ2713
Traffic is dropped from every eighth PWE if eight consecutive VLAN IDs are used
in the range 8..15,16..23, ....1000..1008 and so on, and all eight are configured as
untagged VLAN PWE mode while using IFC1 card with ethernet module.
Impact: If consecutive VLAN IDs are used (in the range 8..15,16..23,
....1000..1008 and so on) to attach PWE in untagged VLAN PWE mode, then one
of the VLANs in the above mentioned range will drop traffic completely. The
affected VLAN will be the one which is bound to untagged PWE last and after
reboot it will be the highest VLAN ID in the above mentioned range. This issue is
observed only on the IFC1 card.
Workaround: Either:
- Skip the eighth consecutive VLAN ID (if consecutive VLAN IDs are used as
in the range 8..15,16..23....1000..1008 and so on) or
- Do not configure one of the eight VLANs in untagged VLAN PWE3 mode.
cq300234923 CBZ2712, SBZ2714, LBZ2713, LBZ2741, LBZ2754

In a routing table indexing error case, when a routing table cannot find ECMP
route gateway, an erroneous path is taken which cannot handle route reference
count correctly.
Impact: A card with erroneous path may reboot.
Risk of occurrence: May occur in releases where a matching gateway is
incorrectly not found.

77
cq300235023 LBZ2754
When the Active port line status of ELP goes down, there will be a one-time flap
in the RMEP status, i.e. the status goes to LoC and returns back to UP state.
Impact: No impact to traffic, but the CCM monitoring status indicates LoC for the
RMEPs and then returns back to UP state after the ELP switchover is completed.
cq300235079 CBZ2712, CBZ2745, SBZ2714

Deletion of ELP protected VLAN interface that has service-policer configured
does not complete correctly. Later configuration, e.g. when another VLAN is
bound to the policer, may trigger a complete management interface hang. The
hang affects both CLI and Tellabs 8000 intelligent network manager connectivity.
Impact: Node management is not possible. In detail the behavior is as follows:
- Node does not respond to Tellabs 8000 intelligent network manager requests
- CLI sessions open, but get stuck to any normal CLI command.
Risk of occurrence: Almost always under the described circumstances.
Workaround: The problem can be prevented by removing service-policer binding
from VLAN before deletion of VLAN interface.
If the problem has already occurred, cold reset for the active CDC recovers
management connectivity. If cold reset is not a feasible option, please contact
Tellabs customer service for instructions to recover the node with a debug
command.
cq300235114 LBZ2754
BPDU filter does not apply for Ethernet spoke PWE3. Configuration via CLI is
possible but it does not take effect and it is not shown in PWE3 AC interface
configuration.
Impact: BPDU filtering cannot be fully accomplished per VPLS with spoke
PWE3 and mesh PWE3 filters only.
Risk of occurrence: Always per spoke PWE3.
Workaround: Enable filtering on all VSI ACs where it is expected to receive
BPDU frames.
cq300235121 CBZ2712, SBZ2714

VCCV and ethernet OAM may stop working when the configuration is
approaching its maximum size.
Impact: VCCV and ethernet OAM do not work.
Risk of occurrence: Under the described conditions and under heavy load within
24 hours.
cq300235211 CBZ2712
After reloading a line card, the following harmless but misleading error print is
output into the console and system logs:
"unit_state.c:284::Reconf. failure reason: TD_NOT_RESPONDING &
INV_NOT_IN_INVENTORY, unit 2 Reconf failure:..."
cq300235242 LBZ2741, LBZ2741, CBZ2712

The network element goes to spontaneous reset when deleting/re-creating ELP
(IFC2, VLAN group shapers).
Impact: ELP on IFC2 with VLAN Group Shapers cannot be used.

78
cq300235265 CBZ2712, SBZ2714

In case a key chain key has the duration field set, it is not possible to set an explicit
end time without removing the key. This causes configuration mismatch between
Tellabs 8000 intelligent network manager and the network element. This may
affect live traffic if the key expires due to this configuration error.
Impact: Traffic may stop as OSPF connectivity stops.
Workaround: Before editing keys in any way, remove them always when they
have a duration set.
cq300235344 CBZ2712, SBZ2714

In case ISIS has level specific SPF intervals only for Level-1 or Level-2, then the
defaults for the other level are returned as zeroes. This prevents Tellabs 8000
intelligent network manager from retrieving the configuration from the network
element correctly.
Workaround: Use either global spf-interval setting or specify both levels at
the same time.
cq300235352 LBZ2754
In high traffic overload situations for hundreds of VLAN shapers per ELC1 a few
low priority packets are scheduled over high priority packets. This may cause a
few high priority packets to be dropped. The observed rate has been a few packets
per minute.
Impact: A few high priority packets may be dropped.
Risk of occurrence: Likely to occur in long-lasting congestions.
cq300235367 CBZ2712
If near to maximum number of VLANs are configured on LAG interfaces in Tellabs
8630 smart router or Tellabs 8660 smart router, after doing CDC switchover, a few
VLANs will not be available in the newly active CDC. Switching back again from
the newly active CDC to the passive CDC will cause the passive CDC to reload.
For example: For four LAG groups, each with two LAG member ports, the
maximum allowed number of VLANs is 4096. The problem is visible after
configuring more than 4062 VLANs. If 4096 VLANs are configured, around 30
VLANs are missing in the newly active CDC.
The problem is not seen when there is only one CDC in Tellabs 8630 smart router
or Tellabs 8660 smart router.
Impact: After CDC switchover, the missing VLANs cannot be managed.
Risk of occurrence: Only when near to maximum number of VLANs are
configured on LAG interfaces and performing CDC switchover.

79
cq300235368 CBZ2712
If more than 4000 VLANS are configured over LAG interfaces, after CDC
switchover either the network element resets spontaneously with a error message
(see below), or the error message is shown continuously without any spontaneous
reset.
The error message is spontaneously printed in console of newly active CDC and
also in os-log.
Sample error message is:
"LnkGetSlpGroupParent: group parent not found for ifIndex=17324"
Impact: If more than 4000 VLANS are configured over LAG interfaces, after
CDC switchover, the network element resets spontaneously, because of which
traffic loss will be seen for a short time till the network element boots up or an
error message is shown continuously without any spontaneous reset/traffic loss.
Risk of occurrence: Only when more than 4000 VLANs are configured on LAG
interfaces and CDC switchover is performed.
cq300235442 LBZ2754
ELP and VRRP is not working concurrently in ELC1. During the switchover both
unexpected error messages and too long traffic cuts may happen.
Impact: Creating ELP configuration in ELC1 causes NPXD Errors and too long
traffic cuts during the switchover may happen.
Risk of occurrence: Always under above described circumstances.
cq300235528 LBZ2741, LBZ2713

As a result of ESW upgrade to FP4.1 CIR1, the network element returns the
value of ipInterface::IpIfAccessControlListsV2C:statisticsEnabled as 'disabled'
for ACLs configured to interfaces on IFC cards. This causes Tellabs 8000
intelligent nework manager database inconsistency for IP Interfaces that have
ACL associated. ACL statistics can still be read and cleared normally. The
inconsistency can be resolved from Tellabs 8000 intelligent network manager
database to the NE.
Impact: Tellabs 8000 intelligent network manager DB Inconsistency in ACL
statistics.
cq300235535 LBZ2754
ELC1 card may report instance name as pdh0/0:0 wrongly while raising interface
related faults during bootup. This happens only once. The wrong instance name
vanishes when the fault goes to OFF or when the active faults are retrieved.
Otherwise the ELC1 card reports correct instance name in all interface related
faults and the fault with wrong instance name should be unnoticed after the card
boot up.

80
cq300235601 CBZ2712, SBZ2714

The OSPF 'tiebreak' attribute returns 0 as default when it should return 1. This
causes problems with Tellabs 8000 intelligent network manager consistency check
when software is upgraded from older releases (see the list below).
The issue is seen with the following software upgrade paths:
- Tellabs 8660, Tellabs 8630 and Tellabs 8620 smart routers: FP2.11A -> FP4.0
or FP4.1 CIR1, FP3.1 -> FP4.1 CIR1.
Workaround: Set 'tiebreak' explicitly to value 'random'.
cq300235603 LBZ2741
LAG PWE3 does not display any counter fields similar to ethernet
PWE3 performance. Relevant for modules 4x100/1000BASE-X HM,
4x10/100/1000BASE-TX HM, 8x10/100BASE-TX LM and 8x100/1000BASE-X
R2.
Impact: LAG PWE3 does not display the PWE3 performance statistics when
traffic flows through the interface.
cq300235637 LBZ2754
The sum of VLAN shaping CIR rates is recommended to be less or equal to the
port physical rate (or port rate limiter CIR when used).
Impact: If CIR values are overbooked, fair scheduling is not guaranteed in
congestion when shapers are activated.
Risk of occurrence: High in the described configuration
Workaround: Avoid configuration with overbooking of CIR values.
cq300235708 CBZ2712
Occasionally MAC withdraw message is not sent when pseudowire down option
is used. Due to this MAC entries might not get flushed from other mesh peers
when the pseudowire goes down. The situation is fixed when the correct MAC
is relearned or the old entry ages out.
Impact: Traffic might flow to wrong destination until the old MAC entry is aged
out. This might cause traffic loss during that time.
Workaround: Use pseudowire up option.
cq300235736 CBZ2712, SBZ2714

LDP neighbor authentication strings of more than 80 characters are silently
discarded.
Workaround: Use authentication strings of a maximum of 80 characters.
cq300235744 LBZ2741, LBZ2713, LBZ2741, CBZ2712

Random PWE3 redundancy circuits may stay down when CDC protection switch
is carried out. This happens especially in FP4.1 CIR1 release.
Impact: Show vccv bfd name CIRCUIT_NAME listing shows that everything is
ok, but the circuit stays down.
Risk of occurrence: In FP4.1 CIR1 very likely when CDC protection switch is
carried out and there are pwe3 redundancy circuits. In older releases extremely
rare.
Workaround: Issue shutdown/no shutdown for the attached interface, or switch
protection to the other CDC.

81
cq300235898 CBZ2712, LBZ2741, LBZ2713

After pwe3 is removed from the interface (GE/LAG), equipment loopback is
still set to the interface.
cq300235899 LBZ2741
IPv4 frames that have the Total Length field 5 bytes larger than the L2 payload
permits are handled incorrectly and as a result of this, ingress traffic of the
affected port will not be forwarded anymore. The affected modules are
8x100/1000BASE-X R2 IFM and 8x10/100/1000BASE-TX R2 IFM.
Impact: Ingress traffic of the affected port will no longer be forwarded.
Risk of occurrence: Very rarely and only when this very rare kind of corrupted
frame is received.
cq300235906 LBZ2741
When two routes are established for the same destination through two different
LAG interfaces, traffic will flow through the LAG interface with higher bandwidth.
When some members are removed and added again to the LAG group having
higher bandwidth, traffic is not flowing through that interface, instead it is flowing
through the lower bandwidth one.
Impact: Traffic will not flow through the LAG interface having higher bandwidth
when members are removed and added. Instead, traffic will flow through the
LAG having lower bandwidth.
Risk of occurrence: Rare. Only when members are removed and added.
cq300235909 LBZ2754
Enabling the VLAN statistics on any GE port affects the IP traffic flow in the XE
port of the same ELC1 card.
Impact: IP traffic in the XE port will be affected when VLAN statistics of any GE
port is enabled in the same ELC1 card.
cq300235932 LBZ2741
The bandwidth of admin disabled LAG member is counted while calculating
active bandwidth of LAG group. When member is added and its admin status is
not enabled, active bandwidth shows the allocated bandwidth of LAG group.
Impact: When a member is removed and added again, bandwidth update will not
happen and OSPF routes will not be established with newer bandwidth.
Risk of occurrence: Rare, only when LAG member is removed and added again.
cq300236138 CBZ2712
If the promised scalability values for CDC1 are exceeded, there is memory
corruption in case any LDP related GET attribute without continuation index
is retrieved.
Impact: Will cause spontaneous reset of the network element.

82
cq300236262 CBZ2712
If CDC1 scalability parameters are exceeded, several ldp list attributes cause
memory corruption in the NE when the mentioned attributes are retrieved via BMI.
Impact: The network element crashes.
Workaround: Do not use BMI get oparations, if the promised scalability values
have been exceeded.
cq300236323 LBZ2741
Excessively padded Ethernet frames with very small IPv4 datagrams (very small
Total Length value) are dropped. Affected modules are 8x100/1000BASE-X R2
IFM (LIO2252) and 8x10/100/1000BASE-TX R2 IFM (LIE2256).
Impact: Small IPv4 datagrams that are transported in Ethernet frames with
unneccessary padding are not routed.
cq300236518 CBZ2712, SBZ2714

Default ip TTL is not stored permanently in the network element. Therefore the
network element returns the hard coded default value after reboot.
cq300236576 CBZ2712, CBZ2745

The protecting CDC may boot twice in case the whole network element is booted
and the protecting CDC has substantially different configurations from cdc14.
cq300236782 LBZ2713
Abis configuration will cause the network element to enter into a restart loop and
eventually fall onto mini-application.
Impact: Abis service is unusable.
Risk of occurrence: The spontaneous reset happens always
- when signaling traffic received to Abis interfaces when using auto protocol
detection or
- without traffic when Abis signaling protocol is configured while manual protocol
detection is set.
cq300236843 CBZ2712
VPLS peer faults have on CLI listing only the first four letters of identification
text, instead of the bridge name followed by peer ip address.
cq300236856 CBZ2712
Configuring vc-qos parameter for vpls-peer does not have the expected effect.
The configured vc-qos is not used when routing decisions are made. However,
vc-qos works correctly with vpls-spokes.
Impact: The vc-qos parameter does not have any effect. Due to this, traffic might
use an unexpected path.
Risk of occurrence: Always when the vc-qos parameter is used with vpls-peer.

83
cq300236863 CBZ2712, SBZ2714

In case any interface name is over 48 characters long, memory is corrupted and the
network element may reset spontaneously.
Impact: The network element may reset spontaneously or otherwise be unusable.
Risk of occurrence: Always when the length of any interface name exceeds
48 characters.
cq300236868 CBZ2712, SBZ2714

IP community-list is removed in boot up in case there is more than one community
per configuration line and at least one of them is a special community like
"internet" or "local-AS".
cq300236918 CBZ2712, CBZ2745, SBZ2714

In cases where VRF redistribute route-map is used to modify ext-community of
the redistributed routes, ext-community modifications of the route-map can be
executed twice if the following sequence of events occurs:
1. VRF export route target list is modified
2. Route-maps are re-evaluated (e.g. due to change in route-map itself or objects
referenced by route-map)
This sequence may be caused by Tellabs 8000 intelligent network manager actions.
Risk of occurrence: Only if ext-community is modified by VRF redistribute
route-map and VRF export RT is changed while route-map modified routes are
present, which is then followed by route-map re-execution for these routes.
Workaround: One can get rid of duplicated ecommunity parts by changing
VRF export RTs.
Can be avoided by not setting ext-community in VRF redistribute route-map.
cq300236970 CBZ2712
LSP ping and LSP traceroute do not work via BMI if the instance number was
autorecovered for some earlier ping/traceroute.
Workaround: Always explicitly delete ping/traceroute instances after use.
cq300237307 CBZ2712, LBZ2713, LBZ2741, LBZ2754, CBZ2745

If a unit that has learned MACs from switching-interface goes down due to an
internal bug in distributed MAC database or some external event, like unit reboot,
then the other units remove all distributed MACs from that unit. MAC removal
removes Explicitly Connected Routes (/32 nhop routes) for those MACS and
updates ARP-cache and transit routes accordingly. This causes traffic cut that may
not recover even though the MAC is re-learned later.
Impact: Traffic outage in IRB connected and transit routes. For transit routes the
traffic may be permanently cut.
Workaround: Do not use IRB in live network.
PPN 13060

84
cq300237721 LBZ2754
Single label pseudowires do not work properly when the egress (tunnel) side unit
is an ELC1. An additional MPLS label is pushed into the packet.
Impact: MPLS static-ftn push-for-vc command (or a similar Tellabs 8000
intelligent network manager operation) does not work properly for ELC1, thus it
should be avoided.
A pseudowire that originates from the penultimate hop of an LSP does not work
correctly when PHP (Penultimate Hop Popping) is used. The packets should
contain only the inner label, but there are two labels instead.
Workaround: Ensure that single label pseudowires are not formed in the network.
Avoid using static-ftn push-for-vc pseudowires and disable PHP for the affected
nodes.
cq300237730 CBZ2712, SBZ2714

The RSVP process in a Tellabs 8600 node may get stuck if it receives "soft
update" for RSVP LSP where the flags of the session attribute change and no
other session attribute field changes.
Impact: RSVP control plane stops functioning. IP and MPLS related management
actions stop working.
Risk of occurrence: - Can only occur in transit LSR.
- Can occur due to management action in changing label-recording or
local-protection setting on the fly.
- Can occur due to third party equipment sending suitable message.
- Can occur due to packet loss and timeouts (extremely rare case).
Workaround: Avoid session attribute changes on the fly. In Tellabs 8600 this
means avoiding the following commands for LSP that is already up:
-rsvp-trunk TRUNK-NAME / [no] (primary|secondary) label-recording
-rsvp-trunk TRUNK-NAME / [no] (primary|secondary) local-protection
Additionally avoid any actions in third party devices that change any of the flags
in the session attribute without performing some other change also or changing
the LSP ID.
The workaround is not completely fool proof, as in some extremely rare cases
packet loss or timeouts may cause the node to see change in these attributes due to
network activity.
cq300237939 CBZ2712, SBZ2714, LBZ2713, LBZ2741, LBZ2754

During interface VRF changes, ARP cache database regarding the changed VRF is
not cleared properly for the previous VRF.
Impact: The problem is not traffic-affecting.
If VRF is changed right before the removal of the interface, the old, now incorrect,
ARP cache entries may be left in the database for some time for dynamic entries
and permanently for static entries. Listing the ARP cache table may show the
incorrect entries as "unknown".
Risk of occurrence: May occur during interface removal, if VRF is changed
before the removal.
Workaround: Do not change the VRF before removing the interface.
cq300238021 LBZ2713, LBZ2741, SBZ2714

PDH/SDH line and PWE3 performance monitoring statistics history data end time
may show the wrong time and date after Sun Aug 11 00:38:49 2013.
PPN 13075

85
cq300238068 CBZ2712, CBZ2745

CLI or BMI may freeze for up to 300 seconds following loopback, VLAN or
IRB interface creation.
Impact: No impact to live traffic. The BMI interface experiences a 5-minute
freeze.
cq300238080 SBZ2714, CBZ2712, CBZ2745

Updating any of the bmp-server attributes may not take effect (when using BMP
over TCP).
Impact: The configuring of the bmp-server attributes may not take effect.
Risk of occurrence: Always under the described circumstances on the Tellabs
8609 smart router and the Tellabs 8611 smart router.
On the other network elements it happens less frequently, but since it is shared
code it could happen.
Workaround: Use CLI or BMP over UDP.
cq300238208 CBZ2745, LBZ2754

In Tellabs 8630 and Tellabs 8660 smart routers, no more than 110,000 switched
MAC addresses can be supported with VPLS.
The issue is seen in the CDC2 unit.
Impact: The upper limit of supported switched MAC addresses is lower than
specified.
Risk of occurrence: Always if the number of switched MAC addresses reaches
the limit, if control unit is of type CDC2.
cq300238326 CBZ2712, CBZ2745

Reading the EthOAM DM counters sometimes fails with UNEXPECTED
ERROR.
Impact: No traffic or functionality is affected with this. Reading the EthOAM
DM counters may fail sometimes if it is fetched immediately after the 15 min/24
hr DM history update.
Risk of occurrence: Occurs when the DM counters are fetched immediately after
the 15 min/24 hrs history update. If the command is executed after 1 min of the 15
min/24 hrs history update, this issue will not be observed.
cq300238635 CBZ2712, CBZ2745

Tellabs 8000 intelligent network manager is not always able to create VPLS
spokes if spoke names are reused.
Risk of occurrence: When bridge is deleted and recreated and has nontrivial
configuration.
Workaround: Create primary spoke with CLI and then remove it using CLI. The
spoke instance is deleted at the same time.
cq300238725 CBZ2745, CBZ2712

A BFD session that is up may be reported as down by the BFD clients (for
example, ISIS) even though they are in up (as seen in "show ip bfd").
Impact: Some services may remain inactive.
Risk of occurrence: Very unlikely. Only when the same BFD peer is used with
multiple clients and even in this case, it requires very unlikely timing.
Workaround: Issuing shutdown - no shutdown sequence to the appropriate
interface resolves the problem.

86
cq300238809 CBZ2712, SBZ2714, CBZ2745

In case GenInstanceName of any object ends with the characters 'no', there is a
risk that any IP related attribute may (silently) fail.
Impact: No impact to live traffic. It might be impossible to set any attribute
for some MOs.
Workaround: Make sure that IP related MOs have names that do not end with
the characters 'no'.
cq300238893 CBZ2712, CBZ2745, SBZ2714

Deleting an interface may not free all resources attached to the interface, causing
resource leak.
Impact: The leaked resources cannot be used.
cq300239045 LBZ2741
When configuring VLAN over LAG, the below error is returned in the console
" XDB_HANDLE_NOT_VALID and XDB MUTEX RESERVE/RELEASE
MISMATCH "
This error will be seen only if the same NE has another IFC2 card with only one
4xSTM-1/OC-3 ATM IFM (LIA2210).
Impact: Console errors can be seen while configuring the VLAN over LAG in
the condition described above.
cq300239133 CBZ2745, CBZ2712, SBZ2714

Tellabs 8620 smart router/CDC1/CDC2 may randomly hang on boot. Booting the
card again may bring it up. If the boot was due to the hanging unit being added
to inventory, the unit may be permanently rejected from the inventory. In this
case it is necessary to enter the mini-application SW and load the application
SW package again.
Impact: Tellabs 8620 smart router/CDC1/CDC2 may not boot up at all.
Risk of occurrence: Medium on CDC2, possible but never seen on CDC1/Tellabs
8620 smart router.
cq300239158 CBZ2712, SBZ2714

OSPF instances can be created only via CLI when they have an instance number
that exceeds the already existing instance numbers.
Workaround: Use BMI.
cq300239291 CBZ2712, CBZ2745

When the user logs in and gives the "enable" command followed by a space, the
IRB interface command will fail on the protecting CDC. This will happen when
the command is executed under another interface to create a new IRB interface.
Impact: The protecting CDC will crash.
Workaround: Use BMI only.

87
cq300239447 CBZ2712, CBZ2745

Giving the command 'show bridging-instance brief' immediately after disabling
mac-learning causes the active CDC2 to reset spontaneously due to a mutex
deadlock in the ESW.
Impact: Traffic cut if CDC units are not protected.
Risk of occurrence: Always under the described circumstances. Spontaneous
reset of both CDCs has not been seen but it is possible, e.g. by giving the 'show
bridging-instance brief' command immediately after CDC switchover on the new
active CDC.
Workaround: Wait some seconds after giving the '[no] mac-learning' command
before giving the 'show bridging-instance brief' command.
cq300239483 LBZ2754
Attaching and then detaching a pseudowire to an ELC1 interface while the VLAN
interfaces exist on that interface triggers unpredictable traffic forwarding for the
VLANs.
Impact: Unexpected echoing traffic out from the XE0 port. The neighbouring
network elements in the subrack crash.
Workaround: Remove any VLANs from the port before attaching the PWE3
to it or viceversa.
4.6 Version 4.1.182 (FP4.1 CIR1)
This is a first customer shipment version intended for controlled introduction. This version should
not be used after the general availability has been reached and a new version is available.
4.6.1 Enhancements Compared to 4.0.309

cq300154868 CBZ2712, SBZ2714
Fine-grained control of setting of ATT bit on ISIS L2 areas. Original behavior is
to set ATT bit whenever non-local area number is seen on some other L2 router.
The following policies are available:
* foreign-area-seen (default, old behavior)
* l2-connected (must see at least one other L2 node)
* always (when L2 area is configured/active)
* never
* route-map RMAPNAME
* Match by L2 node area-id ("match isis area")
* Match by L2 node system-id ("match isis sys-id")
cq300170967 LBZ2713, CBZ2712, LBZ2741

Optimization that reduces the amount of internal messages sent between units.
cq300188608 CBZ2712, SBZ2714

Lenient option added for ISIS BFD. This allows the establishment of BFD sessions
after ISIS adjacencies (regular mode of operation requires BFD as prequisite).
This improves the interoperability with certain other equipment.
cq300188802 LBZ2713
Addition of CLI and Tellabs 8000 intelligent network manager Queue Length
configuration support for MLPPP interface from Debug CLI.

88
cq300191214 CBZ2712, SBZ2714

Route-map support added for controlling connected/static/OSPF/BGP
redistribution to ISIS. Supported:
-Permit/deny
-Setting metric
-Matching prefix, nexthop, and nexthop-interface.
cq300195658 LBZ2713, CBZ2712

Support BGP ORF prefix capability for VPN address family. This allows efficient
filtering of routes if overlapping addresses are not used in VPNs (ORF is not
VRF aware).
cq300214777 CBZ2712, SBZ2714

Allow ISIS redistribution to apply connected routes of ISIS enabled interfaces
(make ISIS redistribution more like OSPF in this regard).
ISIS connected routes are now always considered superior (within ISIS, that is)
to any other routes and if inter-level isis redistribution is configured, it applies to
these routes.
This enhancement does not change the following existing mechanisms:
1) L1 connected route is better than L2 connected route (l1-2 circuit with
redistribute l2 to l1 does nothing as L1 route is better).
2) L1 <-> L1 instance redistribution is not performed within the node (redistribute
isis does note redistribute connected routes between different L1 instances).
cq300215278 CBZ2712
Improved BGP VPN route inspection commands.
cq300224786 CBZ2712, SBZ2714

A new option will allow CLI users to see at a glance what was the described
use of each interface.
cq300225600 LBZ2741, LBZ2713, LBZ2754

ARP cache entry distribution optimized when ELP and/or IRB is used.
cq300230590 LBZ2741, LBZ2713, LBZ2754

QOS classes are defined in the output of the 'show interface mp ppp-multiclass'.
cq300232054 CBZ2712, LBZ2713, LBZ2741, LBZ2754

Implemented the new field 'top level serial number' to BMI attributes eqmMod-
uleIdentification::eqmModuleIdsV4 and eqmUnitIdentification::eqmUnitIdsV5.
The value is read from EEPROM. Also added the new field to CLI command
'show hw-inventory'.
4.6.2 Fixed Bugs Compared to 4.0.309

cq300145098 CBZ2712, LBZ2713, SBZ2714
Modifying an existing ACL configuration can lead to a configuration timeout error.
This may happen most probably when a large ACL is bound to several interfaces.
The hardware is configured correctly in the background despite the error message.
PPN 10027

89
cq300146216 LBZ2713, SBZ2714

When LSP is created from 3rd party equipment where on the originating network
the MTU is higher than the destination network, RSVP MTU negotiation fails due
to an incorrect path MTU. LSPs signaled by Tellabs 8800 do not work if MTUs in
Tellabs 8800 and Tellabs 8600 are different.
Risk of occurrence: This happens in all affected configurations. However these
configurations do not work in the first place, so this does not occur spontaneously.
Workaround: Verify that the MTU values are correctly set before creating the
LSP.
cq300148422 CBZ2712, SBZ2714, LBZ2713, LBZ2741

When a shaper is configured with CLI, the full burst size range proposed by the
interactive help may not be configurable. The syntax for the CLI command is:
"shape cir cir [ burst-size burst-size ] pir pir". The actual maximum of configurable
burst size depends on the CIR value and the CLI interactive help is not able
to propose the correct range.
The configurable burst size in bytes can be calculated by the following equation:
burst size = 1 .. min(32 000 000, (CIR*256 000 000) / x)
where "x" is the port data rate (in kbps).
cq300162578 CBZ2712, SBZ2714

The SNMP agent reports conflicting tunneling information for stacked VLANs. It
always reports "ip routing". The CLI and BMI interface of Tellabs 8000 intelligent
network manager report correctly as "tunneling".
cq300165215 LBZ2741, LBZ2713

RSVP tunnel goes down when reloading the working card of a protection group in
case of Ethernet over Frame Relay/ATM /PPP encapsulation.
Impact: Data break occurs until the working card has finished its reload.
cq300166372 CBZ2712, SBZ2714

Using network element route filtering on the GUI causes all IS-IS and OSPF
routes to be removed from the display. These routes will still be present on the
network element, they are just missing from the display.
Risk of occurrence: Always when route filtering with two or more simultaneous
filters is used.
cq300182357 CBZ2712, SBZ2714

Running configuration contains dummy "ip unnumbered xx" commands that have
no effect on routing when such commands are applied to interfaces that are not
point-to-point, e.g. atm interfaces.
Workaround: Do not apply unnumbered commands to non point-to-point
interfaces.

90
cq300190062 LBZ2713
Using shutdown-if command while traffic is flowing may cause congestion of all
the traffic in that port. This affects all the Ethernet IFMs.
Impact: Traffic flow may get congested if shutdown-if command is used when
traffic is flowing.
Workaround: Do not use shutdown-if command while traffic is flowing.
cq300190960 SBZ2714, LBZ2713, LBZ2741

The queue monitoring algorithm may give false alarms and cause short traffic cuts.
This may happen if egress traffic is limited by shaping or by adjusting queue
weights. The traffic cuts can occur if the egress configuration sets the data rate
of a single traffic class very low (for example 235 kbps when the packet size
is 300 bytes).
Impact: Short traffic cuts occur.
Workaround: Use a higher CIR in shaper configuration.
If a smaller CIR is needed, contact Tellabs Technical Assistance Center to disable
queue monitoring.
cq300194155 CBZ2712, SBZ2714, LBZ2741, LBZ2713

CLI command "qos vlan ingress ..." has no immediate effect if applied to a PWE3
VLAN interface.
Impact: Newly configured QoS mapping is not effective until a PWE3 is
reprovisioned or PWE3 VLAN interface is reconfigured.
Risk of occurrence: Always if the CLI command "qos vlan ingress ..." is given
for a PWE3 VLAN interface.
Workaround: Reprovision the PWE3 or reconfigure PWE3 VLAN interface (i.e.
"shutdown"/"no shutdown" on the PWE3 interface).
cq300196512 SBZ2714, CBZ2712

The 1544 kHz interface mode for the SCI and SCO ports is not supported in the
S3 Timing Module (CMT2228). However, a configuration option for these exists
in the CLI and no error is returned if they are used. If a SCI is used in 1544 kHz
mode as a reference clock for a NE with the S3 Timing Module (CMT2228), the
synchronization performance is not acceptable.
Impact: Loss of synchronization under the described circumstances.
Workaround: Use the SCI interface in 2048 kHz, E1 or T1 mode.
cq300196516 LBZ2713
Changing Ethernet (electrical) IF pause frame setting in Combo IFM causes
internal error. An error message is seen if IF speed and duplex are set to
autonegotiation, 100M half duplex or 10M half duplex. With other speed/duplex
settings the operation seems to succeed without any error message.
Impact: The pause frame settings in ComboIFM cannot be done for 10 and 100
Mbps half duplex modes.

91
cq300198575 LBZ2713, LBZ2741, LBZ2754, SBZ2714

Unnecessary IP stack logging causes major slowness when a line card or network
element with a large number of protected VLANs is booting up. Inefficient
protection group creation architecture adds additional slowness to it.
Impact: It may take a long time after unit bootup until traffic is going through.
Risk of occurrence: Depends on the number of protected VLANs in the line card
or network element that is rebooted.
cq300198750 CBZ2712, LBZ2713, SBZ2714

Queue manager test may cause one out-of-cells situation which is harmless, but
prints the following warning print to os-log: "Queue manager test round failed". If
this print appears once, it is no sign of a real error and the test is still ok.
cq300201631 LBZ2741, CBZ2712, SBZ2714

Ethernet ping results are duplicated in case the outgoing interface is ELP protected.
cq300204954 LBZ2713, LBZ2741, SBZ2714

The numSupressedIntervals variable in the SDH/PDH/DSL 15-minute history data
is incremented in an inconsistent manner.
Impact: The numSupressedIntervals variable in the SDH/PDH/DSL 15-minute
history data is incremented so that if suppression has been done this value includes
also the original 15 interval. I.e. the value is 0 when no suppression has taken
place and the value is 2 after first 15min interval is suppressed and 3 after second
15min interval is suppressed etc...
Value should be 0 when no suppression has taken place.
Value should be 1 when first 15min interval is suppressed and 2 after second
15min interval is suppressed etc...
cq300205183 LBZ2741, LBZ2713, SBZ2714

The "bandwidth-if" CLI command accepts more than 8 bandwidth values.
Impact: It does not affect live traffic. Extra values are ignored.
cq300208597 CBZ2712, SBZ2714

ARP removal for a non-existing entry results in an error. As the entry does not
exist, an error should not be returned.

92
cq300208845 SBZ2714, LBZ2713, LBZ2741

If SAToP PWE3 line loopback is set and later the CLI command "no pwe3
loopback to-line" is entered to remove the loopback, traffic is lost.
Impact: If SAToP PWE3 line loopback is set and later the CLI command "no
pwe3 loopback to-line" is entered to remove the loopback, traffic is lost.
Workaround: Take down the PWE3 and set it back up following the steps below:
1. no pdh usage connected 2. pdh usage connected 3. pwe3 circuit satop_name 4.
no shutdown
cq300209864 LBZ2713, SBZ2714

Setting of Pause Admin Mode to values "transmit" and "transmit and receive"
fails in the electrical GE interfaces of 2+6x10/100/1000BASE-COMBO IFM
(LIC2231) if the electrical GE link is either in down operational state or in
half duplex mode. In these cases the SET operation returns an error message
because the hardware configuration fails. Nevertheless the value is stored to the
non-volatile memory.
Impact: Pause Admin Mode changes to values "transmit" and "transmit and
receive" are not taken into use in the hardware.
Workaround: Restart the line card or network element where
2+6x10/100/1000BASE-COMBO IFM (LIC2231) is or make sure that the
electrical GE interfaces of 2+6x10/100/1000BASE-COMBO IFM (LIC2231)
are in UP operational state and in full duplex mode before these configurations
are done.
cq300210457 CBZ2712
ICMP-Sent Echo count is not working.
Impact: ICMP-Sent Echo count will not increment in the affected network
elements.
cq300212033 CBZ2712
Obsolete protection data remains on line cards which may cause very rare
RSVP-TE path protection related traffic cuts or traffic to an incorrect destination.
This bug has always been in Tellabs 8600 products.
Impact: There can be very rare traffic cuts or traffic to an incorrect destination
when RSVP-TE path protection is used.
cq300212336 CBZ2712, LBZ2713, LBZ2741, SBZ2714

Packet loop tester echo statistics may sometimes be incorrect. The mismatch is
usually some packets.
cq300216944 LBZ2741
When IRB traffic (L3 -> L2 direction) with unlearned MAC is sent, it uses AC
MTU instead of IRB MTU. When MAC is learned, IRB traffic starts to use the
correct IRB MTU. This should usually not be a problem as MAC is typically
learned at the very beginning.
Impact: IRB traffic may briefly use AC MTU instead of IRB MTU until MAC is
learned.

93
cq300216952 LBZ2741, CBZ2712

The MTU for the multi- and broadcast traffic for a VSI is determined by the
last MTU given for an attachment circuit (AC) belonging to that VSI (not the
minimum of the VSI ACs).
Impact: The MTU for multi- and broadcast traffic in a VSI is indeterministic if
different MTUs are used in VSI ACs.
Workaround: All ACs in a VSI must use the same MTU.
cq300217198 SBZ2714, CBZ2712

The "show arp sort-by mac address" CLI command does not correctly sort the
ARP entries by MAC address.
Impact: The MAC address ordering is not sorted as expected - so it may be more
difficult to find the specific ARP entry being searched.
cq300217279 CBZ2712, LBZ2713, LBZ2741, LBZ2754, SBZ2714

The PLT generator prints the actual used data rate after packets are generated. The
shown value can be inaccurate if the test time is short (close to some milliseconds).
This has no effect on the actual bit rate used in the PLT generator.
cq300218244 CBZ2712, SBZ2714

The destination UDP port number for traceroute probe packets is counted with
the formula: (port given by user) + (probe packet sequence number) = probe port
number. Therefore, if the user inputs a port number near the upper limit of the port
area 65535, the port number may overflow. In case of overflow, the probe packet
sending fails which then can be seen as packet loss in the traceroute results.
Impact: Traceroute probing will give false negative results if probe sequence +
port number exceeds 65535.
Workaround: Do not invoke traceroute in such a way that packets + port > 65535.
cq300218893 LBZ2741
After a control card switchover from active to standby the VLAN counters "RX
Priority 0 Packets" and "RX Priority 1 Packets" will be set to zero. After a
switchover back these counters are set to a random value. If the counters are
cleared, they will increment correctly until the next switch.
Workaround: If the counters are cleared, they will increment correctly until the
next switch.
cq300220909 CBZ2712, SBZ2714

Setting a loopback interface as the source address for syslog messages fails with
Tellabs 8000 intelligent network manager.
Workaround: Use the corresponding CLI command. For example: logging
syslog source lo0

94
cq300220957 CBZ2712, SBZ2714

In some cases Tellabs 8600 network element either fails to send fault change
notification to Tellabs 8000 intelligent network manager, or the notification is lost.
This causes Tellabs 8000 intelligent network manager Fault Management to get
updated with a long delay, i.e. when the next periodical Fault poll is done.
cq300222008 CBZ2712, SBZ2714

Invalid IP address configuration is accepted in the "ip host" CLI command without
validation check.
Impact: It may lead to IP connectivity failure for some of statically configured
hosts.
Risk of occurrence: Only if the CLI command is mistyped.
Workaround: Be careful when typing the CLI command "ip host - -".
cq300223763 SBZ2714
After port protection has been removed from the network element with an
8xSTM-1/OC-3 POS IFM (LIO2020), the protecting line state remains down.
Impact: The port remains unusable until manual intervention.
Workaround: Switch the laser off and on to get the line state up again.
cq300224596 LBZ2754, LBZ2754

When an Ethernet interface receives Ethernet frames that have a MAC address
which does not belong to the interface, the frames are correctly dropped but they
are not shown in any statistics.
cq300225136 CBZ2712, SBZ2714

If there are no ICMP unreachable errors on a network element (CLI command
"show ip unreachables") and if the query is done through the BMI of Tellabs
8000 intelligent network manager, a BMI error "21002(Un expected Error)". The
expected output is "0(No Error)".
cq300225327 CBZ2712, SBZ2714

When several entries are included in the domain-name search list and some of the
domains is not found, all client queries for domains fail.
Impact: The correct domain cannot be found under the described circumstances.

95
cq300225657 SBZ2714, CBZ2712

Some T1/E1 ports lose visibility to changes in the network. The has been observed
on random ports in E1 cards. Entering the "loopback to-equipment" CLI command
on non-connected E1 spans does not clear the LOS alarm.
The T1/E1 cards that have the issue share the same handler.
The modules 8xchE1/chT1 LM(LMP2242) and 24xchE1/chT1 Multiservice IFM
(LIE2226) are affected.
Impact: LOS alarms can potentially not be reported when E1 is disconnected or
remote E1 goes out of service. Also, LOS can potentially not clear when E1 is
connected to a good E1 span.
Workaround: When this behavior is encountered the ‘debug sw write-memory 1
0xf300000e 16 0x0cff ‘ command should be issued to clear the stuck alarms and
force processing of the LOS alarms once again.
cq300225712 LBZ2754
Very small packet loss in low priority traffic occurs when there is bursty high
priority traffic in the same egress port. The egress port utilization rate has to be
high for the drop to happen. The observable drop rate is at worst hundreds of
packets in a minute but usually much less.
Impact: Some low priority packets may get dropped.
Workaround: Higher queue depths for low priorities may improve the situation
but does not fix it entirely.
cq300225769 CBZ2712, SBZ2714

BGP PUSHes are not properly configured to hardware in card or network element
reload.
Impact: Data break occurs for BGP PUSHes after card or network element reload.
Workaround: Use the BGP PUSH_AND_LOOKUP + PUSH combination
instead.
cq300226207 LBZ2741, LBZ2713, SBZ2714

When using ATM with VCCV bft, the ATM VC and VP will not come up on the
required time so the traffic flow will be affected.
Impact: ATM VP and VC will not coming up, so it will affect the traffic.
Risk of occurrence: Only when ATM is configured with VCCV bft.
Workaround: ATM VP and VC will come UP, if VCCV bft is not used.
cq300226220 LBZ2713, LBZ2741

The "show running-config" CLI command prints MLPPP configuration
commands in an incorrect order that does not replay correctly: "ppp mp
ip-header-compression enable" is too early in the printout.
Impact: MLPPP header compression cannot be configured correctly with a
textual copy of the "running-config" output if header compression is used.
Risk of occurrence: Sometimes.
Workaround: After using the "running-config" output as the CLI input, if the CLI
command "ppp mp ip-header-compression enable" produces an error message,
repeat that command manually afterwards. Or, rearrange CLI commands manually
before using the "running-config" as the CLI input.

96
cq300226276 LBZ2741
IP fragmentation does not work for packets sent to IRB L2 interface when the
destination MAC address is not learned.
Impact: The fragmented packet is dropped.
Risk of occurrence: Always under the described circumstances. Traffic from the
destination to IRB will cause the MAC address to be learned, so the problem only
affects unidirectional traffic.
cq300226433 LBZ2713, SBZ2714

The network element resets spontaneously due to a bug in the event handler of
the E1-driver.
Impact: The network element spontaneous reset might cause a traffic outage.
cq300226618 LBZ2713, LBZ2741, SBZ2714

When the "dns-server" option is configured for the PPP POS interface, it
seems that the configuration succeeds although POS is not supported and the
configuration is not really applied. The failure can be seen from os-log.
cq300227144 CBZ2712, LBZ2741, LBZ2754

Missing implementation of a part of the configuration recovery mechanism causes
reduced fault tolerance. Fault situations that are repairable by refreshing the
running line card configuration, may require rebooting the network element.
Impact: Missing implementation of a part of bridging instance configuration
recovery mechanism causes reduced fault tolerance. Fault situations that are
repairable by refreshing the running line card configuration, may require rebooting
the network element.
Risk of occurrence: Small. Impacts only in rare situations where 1) bridging
instances have been configured and 2) configuration has somehow got corrupted.
cq300227424 LBZ2741
If a RJ-45 port of the 8x10/100/1000BASE-TX R2 IFM (LIE2256) is first set to
10 Mbps mode and subsequently to autonegotiation mode (which allows all link
speeds), the Rx SSM status is always set to 'do not use' (ql-DNU). Consequently
such port will not be accepted as a synchronous Ethernet (SyncE) clock source.
Impact: Synchronization service is lost on said port.
Workaround: Workaround options are:
1. Force the port mode to 100Mbps or 1000Mbps.
2. Disable quality levels.

97
cq300227615 CBZ2712, SBZ2714

The Tellabs 8600 network element sends outgoing NTP packets erroneously
with DSCP value 11 instead of the DSCP value the EF traffic class is mapped to
as recommended in RFC4594 for carrier networks. The value does not follow
the QoS mapping set by the user with the "qos mapping egress qos ef ip-dscp
<value>" CLI command.
Impact: In a congested network, NTP packets may be dropped.
Workaround: In the network element generating the NTP packets there is no
workaround. In a network consisting of multiple Tellabs 8600 network elements,
NTP traffic QoS can be corrected by the network element neighboring the NTP
server node. This can be done with an ingress ACL bound to the interface,
containing a rule such as "permit udp any eq ntp any action qos ef". With this
configuration, the first IP hop remains impacted with the problem.
cq300227655 LBZ2713, LBZ2741, SBZ2714

The "show bandwidth-if module" CLI command and lpoPhyBand-
widthUsage::lpoPhyBandwidthAllocation BMP attribute show inaccurate
bandwidth values when the interface has been configured with a bandwidth value
that is not divisible by 20. The ESW will round up the user configured bandwidth
value to the next value that is divisible by 20 when the value is taken into use in
the HW, if user defined bandwidth value was not divisible by 20. The "show
bandwidth-if module" CLI command and lpoPhyBandwidthUsage::lpoPhyBand-
widthAllocation BMP attribute do not show this rounded up value at the moment.
Impact: This can confuse the user when bandwidth values are adjusted. For
example, when lpoPhyLackOfBandwidth fault is set on for some reason and the
user wants to adjust bandwidth values to get rid of lpoPhyLackOfBandwidth
fault. In this case, the user can, for example, set bandwidth value to 990 from the
previous value 1000. ESW will round 990 to 1000 and this adjustment has no
effect on state of fault.
Workaround: Use bandwidth values that are divisible by 20.
cq300227889 CBZ2712
The MAC address has incorrect user information in the "mac-address" CLI
command help text.
Impact: If the help text for the "mac-address" CLI command is used for
configuration, an error message is shown.
Workaround: If the MAC address specified in the help text of the "mac-address"
CLI command is not used for configuration and a valid MAC address is used, the
CLI command is successful.
cq300227890 LBZ2741
ELP down (down and down pulse) modes allow "if hold down" configuration
to ELP link.
Impact: Hold down still exists when passive if mode is changed from "rx-both"
mode to "phyIfDowndown/ phyIfDownPulse". The hold down time must not be
supported when ELP is signaling passive state using the physical layer, i.e. in
phyIfDown and phyIfDownPulse modes.
Workaround: Passive interface mode must not be configured with the "if down"
mode when hold down is already configured.

98
cq300227953 LBZ2741, LBZ2713

When there are lots of PWEs for which VCCV is enabled, and then there is
congestion in the PSN network, lots of VCCV packets may be lost due to the PSN
network congestion. The consequence is that there will be lots of VCCV state
changes, that is, VCCV events. The VCCV events are processed by the node’s
CPU but there is a limit to how many VCCV events the CPU can process. If the
rate of VCCV events exceeds a certain limit (few hundreds of events per second in
sustained manner) the CPU gets stuck, and consequently the network element may
reboot. At the very least, the CPU becomes unresponsive in this situation.
Further, since the CPU cannot process all VCCV events, some events will be lost
and the result is that some VCCV sessions will remain in the wrong state.
Impact: The number of VCCV sessions should be restricted if the PSN network
can experience sustained congestions.
Risk of occurrence: Occurs always when the rate of VCCV events exceeds the
CPU processing capability.
Workaround: Restrict the number of VCCV sessions if the PSN network can
experience sustained congestion. VCCV event rate can be also restricted by using
longer VCCV intervals.
cq300227957 CBZ2712
SNMP entity MIB entPhysicalModelName value is not set for the Tellabs 8660
smart router R2 subrack. The Tellabs 8660 smart router R2 subrack part number is
incorrectly not set to entPhysicalModelName value if it exists.
Impact: SNMP entity MIB entPhysicalModelName value is not set for the Tellabs
8660 smart router R2 subrack (index 1).
Risk of occurrence: Occurs when getting SNMP entity MIB
entPhysicalModelName value of the Tellabs 8660 smart router R2 subrack.
Workaround: See the value the following CLI command: "show hw-inventory |
bl SUBRACK | inc part"
cq300227978 LBZ2713, LBZ2741, SBZ2714, CBZ2712,

Modifying an access list containing a large amount of policy based routing entries
(map-route actions) may fail due to temporarily running out of HW resources.
When an ACL is modified, the system temporarily reserves resources for both the
existing and the new ACL entries, and the system does not handle gracefully
the situation when load balancing table entries run out. If this occurs, the alarm
"Load balancing usage overflow" is raised. In the same scenario only the "Load
balancing usage high" alarm may be temporarily raised. This is a warning and
HW resources are still within limits. "Load balancing usage high" alarm alone
is not traffic-affecting.
Impact: Access list update may fail. When some of the map-route actions are
not written to HW, the issue causes a partial outage.
Risk of occurrence: The issue does not occur in most common configurations.
The risk is high when an ACL with hundreds of map-route actions is bound to
several interfaces on the same IFC.
Workaround: To prevent running out of load balancing table entries, modify
access-lists containing a lot of map-route actions as follows:
1. Remove access list bindings
2. Update access list
3. Add access list bindings back
If the issue has already occurred and traffic is not passing, the only workaround is
to reload the IFC in question.

99
cq300228342 LBZ2754
The packet/octets count given by the "Show rsvp session details" command is
less than the actual packet/octets sent through the tunnel. This is due to an issue
in hardware statistics counting and not to traffic loss.
Impact: Inaccurate statistics count for RSVP statistics.
cq300228350 CBZ2712, LBZ2713

There is one chance in ten that one circuit (VCCV transmit channels) out of 4000
will stay down after CDC protection switch. In addition, circuits handled with
IFC1 boards may go down for a few minutes.
Impact: A random circuit goes down and stays down.
Risk of occurrence: One in ten attempts when CDC protection switch is carried
out.
Workaround: Perform shutdown/no shutdown to circuit.
cq300228351 CBZ2712
In Tellabs 8660 smart router and Tellabs 8630 smart router, if 1+1 protected CDC
control cards have different types of timing modules, sometimes the protecting
timing module stays as inactive in the hw-inventory. The command 'show
hw-inventory' displays "active type none" the for timing module:
...
timing module has
expected type cmt2017-etsi-timing
active type none
existing type cmt2228-timing
Impact: Protecting timing module cannot be used.
Workaround: Requires FTP connection to the network element. For details
contact Tellabs Technical Assistance Center.
cq300228399 CBZ2712
When Ethernet OAM with ELP is configured, the ELP protecting side
autodiscovered CCM sessions might incorrectly show LOC state.

100
cq300228648 LBZ2713, LBZ2741, SBZ2714

When setting one Ethernet interface to line loopback mode, also other interfaces
in the same IFM are affected. The problem is due to a HW feature. Line loop
settings is a Mac-chip level feature.
The following IFMs have this problem:
-8x10/100BASE-TX IFM (LIE2018) HW V2.0, affected interfaces: 0..7
-8x100BASE-X IFM (LIO2028), affected interfaces: 0..7
-8x1000BASE-X IFM (LIO2208), affected interfaces: 0..3 and 4..7
-2+6x10/100/1000BASE-COMBO IFM (LIC2231), affected interfaces: 0..3
and 4..7
For example:
if line loop is set on port 0 in 8x10/100BASE-TX IFM (LIE2018) HW V2.0,
ports 0..7 go to line loop state,
if line loop is set on port 7 in 8x1000BASE-X IFM (LIO2208), ports 4..7 go
to line loop state.
Impact: The "loopback to-line" CLI command affects several interfaces at the
same time. Which interfaces are affected depends on the IFM type.
PPN 12099
cq300228659 LBZ2754
Tunnel src statistics counters are mixed in the BMI interface.
Impact: Tunnel src counter values are not accurate via BMI interface.
Risk of occurrence: Always in the BMI interface, when traffic is going through.
Workaround: CLI "show rsvp session name <tunnel-name>" shows correct
counter values.
cq300228911 LBZ2741, LBZ2713, SBZ2714

The "shutdown-if" CLI command does not fully disable the port for
4xSTM-1/OC-3 ATM (LIA2210) interface module. The port is fully disabled only
after reloading the line card or network element.
"no shutdown-if" is not affected, i.e. the port is immediately enabled when the
command is given.
Impact: Forwarding traffic to a disabled port is not completely prevented.
Risk of occurrence: Always under the described circumstances
Workaround: Reload the line card or network element after disabling the ports
from use.
cq300229014 LBZ2754
LnkAct LED on the 10G interface shows incorrect link status after change in
the link state.
Impact: The LED on the 10G interfaces will not show the correct state of the link,
after link state changes from up to down and vice versa.
cq300229525 CBZ2712
After protection switch, the ping instances on the protecting side have extra replies.
Risk of occurrence: Always under described circumstances.
Workaround: Use different ping instance.

101
cq300229661 LBZ2754
Ethernet OAM linktrace replies do not have correct priority set in VLAN priority
bits, when values differing from zero are used.
Impact: Ethernet OAM linktrace replies may drop when the network is congested
on the zero VLAN priority.
cq300229733 LBZ2754, LBZ2741

Dynamic MAC address entries learned from an SLI that is down may remain in
the switching table, if traffic is on while SLI is being shut down.
Impact: When shutting down an SLI while traffic is on, entries for MAC
addresses appearing in traffic may be left in the switching table. Traffic to these
MAC addresses may find an alternative path -- if one exists -- only after the MACs
have aged out and the traffic gets flooded.
Workaround: Case-specific: may involve adjustment of aging timeout, manually
clearing MACs, or setting static MAC entries.
cq300230148 CBZ2712, SBZ2714

Keychain Key lifetime can not be set with duration in OSPF security settings.
Risk of occurrence: Always when duration is used.
Workaround: Do not use duration variant of end time.
cq300230161 LBZ2741
After adding a member to the LAG group and configuring loopback on top of
the LAG, the following occurs: when the member is removed from the LAG or
the LAG group is deleted, the removed member will still contain the loopback
configurations.
Impact: LAG loopback configuration exists on LAG member even after it is
deleted from the LAG group.
cq300230554 CBZ2712, SBZ2714

Routemap internet community is coded with wrong first part when Tellabs 8000
intelligent network manager is used.
Impact: Internet community works wrongly.
Risk of occurrence: Always when the internet community was used with Tellabs
8000 intelligent network manager.
cq300230989 LBZ2754
ELC1 will increase Tx error count when Ethernet frames with a size of less than
64B are padded and transmitted by it. In spite of Tx error, these frames are padded
and transmitted successfully. Tx error is risen even though the frame is padded
before it comes to ELC1 from the backplane (for example ISIS LSPs generated
and padded from CDC). The effect does not seem to cause any harm to the traffic.
Risk of occurrence: Frequently occurs when ISIS L2 is configured on ELC1 links.

102
cq300231050 LBZ2713, LBZ2741, SBZ2714

Policer packet statistics cannot be read through Tellabs 8000 intelligent network
manager if policer id is above 255 and octec counters have not been enabled for
the policer.
Impact: Policer packet statistics cannot be read through Tellabs 8000 intelligent
network manager.
Workaround: 1. Enable octec-counter for the policer through CLI, or
2. Read policer statistics through CLI.
cq300231103 CBZ2712
The Tellabs 8000 intelligent network manager does not support the show and
clearing of the DHCP statistics.
Impact: There is no "show dhcp-relay stats" with the Tellabs 8000 intelligent
network manager.
Workaround: Use CLI instead of Tellabs 8000 intelligent network manager.
cq300231315 CBZ2712
It takes a while to clear the Excessive Frequency Offset fault after the fault
condition is over.
cq300231320 LBZ2754
The 'show hw-inventory slot detail' command is not showing the optical power
in dBm.
Impact: The optical power is shown in mW (milliwatt) only.
Risk of occurrence: Whenever 'show hw-inventory slot detail' is executed.
cq300231707 LBZ2741
If VLAN discard frames is configured on top of a LAG and a member is removed
from the the LAG, or the LAG group is deleted, the VLAN discard frames
configuration still remains for the removed member(s).
Impact: VLAN discard frames configuration remains for the removed LAG
member(s).
cq300231761 CBZ2712, SBZ2714

If ISIS is not enabled on the node or ISIS CSPF is disabled on all ISIS instances,
ISIS process may get stuck if:
- Tellabs 8000 intelligent network manager consistency check is performed
- The command 'show isis cspf config' is issued ISIS can block all other IP and
MPLS management commands, block 'show running config', excessive CPU
consumption occurs and ISIS no longer works.
Impact: The node becomes unresponsive, ISIS stops working, running
configuration cannot be obtained, many CLI commands and management actions
stop working. Other protocols may fail due to excessive CPU consumption.
Risk of occurrence: 100 % if all pre-conditions are met. Otherwise none.
Workaround: Always have at least one CSPF enabled ISIS instance (no actual
ISIS enabled interfaces are required).

103
cq300232118 CBZ2712, SBZ2714

PWE3 circuit name given via CLI is limited to 32 characters. This prevents PWE3
removal via CLI in case Tellabs 8000 intelligent network manager has created it
with a longer name than 32 characters.
Workaround: Use only Tellabs 8000 intelligent network manager when creating
circuit names.
cq300232309 CBZ2712
After the removal of ETH-OAM maintenance domain or maintenance association,
the network element has ghost instances of MAs, MEPs and MIPs -- i.e. the
network element believes there is an instance, tries to use it, and then fails.
Workaround: Always remove the related configuration before deleting MA or
MD.
cq300232453 CBZ2712
IP VPN BGP routes are mirrored incorrectly between control cards, if MPLS
nexthop is non-recusrive. This can occur in the following situations:
- single-hop MP-eBGP sessions
- any MP-BGP session (iBGP/eBGP) configured to use link addresses between
adjacent nodes
- labeled VPN routes with nexthop set to link IP of adjacent neighbor This issue
does not occur if VPN labels use loopback addres as nexthop.
Impact: VPN services stop working.
This issue can be detected by seeing the same BGP route in "show debug sw bsdip
slot <active-cdc> route" and in "show mpls ftn" in the same VRF. Note that for
VRF0 it is normal that the same route is in both tables.
Occurence at switchover can be inspected prior to switchover by checking the
passive control card bsdip route table.
Risk of occurrence: The problem will occur if one of the following is true:
- single-hop MP-eBGP sessions
- any MP-BGP session (iBGP/eBGP) configured to use link addresses between
adjacent nodes
- labeled VPN routes with nexthop set to link IP of adjacent neighbor
And additionally passive control card is rebooted while routes have been learned
from one of the listed BGP session types. The passive control card is "corrupted"
at that time, but no ill effect will occur unless control card switchover is performed
to the passive control card.
This problem can occur in all SW versions, but in 2.11 and prior SW version
it resolves itself shortly after control card switchover. In newer SW versions
problem persists until NE boot or until control card switchover is performed back
to the original card (assuming the card has not been rebooted --> corrupted).
Workaround: Prevent the problem by using only loopback to loopback MP-BGP
sessions. This is the typical configuration with Tellabs 8600 system.
If the problem occurs, it is possible to resolve this on a prefix by prefix basis by
provisioning higher priority static route for each affected prefix and then removing
it. Route to null0 interface is convenient.
The problem is also resolved at network element boot or by swiching immediately
back to the original active control card, assuming that the control card has not
been reloaded (in passive role).

104
cq300232829 CBZ2712, SBZ2714

Tellabs 8000 intelligent network manager is not able to retrieve the attribute
mplsFtnPushAndLookupVcList correctly. This causes problems with the
Consistency Checker.
cq300233118 CBZ2712
ICMP Counters will increment twice when CDC protection is enabled in Tellabs
8630 smart router or Tellabs 8660 smart router.
cq300233506 LBZ2741
IP MPLS statistics read from the lower IFM of IFC2 are not reliable.
Impact: Incorrect IP MPLS statistics values are given.
cq300233713 CBZ2712, SBZ2714

In case IP configuration is full and the related FAULT (IP_CONFIG_LOCKED)
is raised, there is the risk that memory corrupts and the network element goes
to spontaneous reset. This is likely to happen on both CDCs approximately
simultaneously.
Impact: In case IP configuration is full, the network element will go to
spontaneous reset each time the IP configuration is changed, until such a time
when the configuration is reduced sufficiently.
Risk of occurrence: Always under the described circumstances. However, it is
very unlikely that any customer fills the whole IP configuration area fully.
Workaround: Reduce IP configuration below the allowed maximum limit.
cq300233748 CBZ2712
The control card reboots if protected Management Ethernet port receives a packet
before the protection group is fully created. This can happen after control card and
full network element boot-ups.
Impact: The control card reboots.
cq300233785 CBZ2712
Tellabs 8000 intelligent network manager is not able to see change notifications
related to null interfaces.
cq300233786 CBZ2712, SBZ2714

Tellabs 8000 intelligent network manager is not able to see configuration notices
(CCNs) concerning loopback interfaces.

105
cq300233953 CBZ2712, LBZ2741, LBZ2754

Egress QoS mapping settings are not considered when binding interfaces to
bridging-instances, but the mapping is always enabled. Later the QoS mapping
settings may take effect, but get overridden by any later SLI configuration
(system-initiated refresh or user-initiated), independently of which attribute is
configured.
Impact: It is not possible to reliably disable egress QoS mapping for SLIs.
cq300233963 CBZ2712
RSVP load balancing does not work reliably after CDC switchover.
Impact: Temporary data cuts may occur after CDC switchover.
Risk of occurrence: Medium.
cq300233964 CBZ2712
When the passive CDC is rebooted (e.g. during SW upgrade), its configuration
may never finish if the combined amount of ECMP routes and RSVP load
balancing groups is more than 500.
Impact: The passive CDC may not boot. The active CDC wastes a lot of CPU
time endlessly trying to bring the passive unit up. Network element reboot is
needed to resolve the situation.
Risk of occurrence: High with big load balancing/ECMP configurations.
Workaround: Avoid big load balancing configurations.
cq300234059 CBZ2712, SBZ2714

RSVP LSP ILM entry may not get programmed to HW under rare circumstances.
Impact: RSVP-TE tunnel does not forward data.
Risk of occurrence: Requires that the LSP in question has loose path and does not
use CSPF, and that the LSP is either FRR FB protected or FRR local protection is
active, and that the underlaying route used to resolve the loose ERO changes.
Workaround: Use CSPF or strict paths.
cq300234096 CBZ2712, SBZ2714

RSVP priority resolution is not working correctly between loadbalancing
group and non-loadbalanced trunks. The datapath selection depends on trunk
configuration order. The selected datapath may also change during node reload or
CDC switchover.
Impact: May lead to unwanted trunk usage if the user has rsvp loadbalancing
group and single trunk(s) to the same ip destinations (map-route).
Workaround: Avoid configuring single rsvp-trunks and loadbalancing group with
the same ip destination addresses (map-route).
cq300234122 CBZ2712, SBZ2714

Show running configuration displays DebugEthernet interfaces that are not
configured after SW upgrade, e.g.: interface DebugEthernet5/2 ip address €
shutdown.
Note that any other random character or symbol may be displayed instead of
the € symbol.
Impact: Unconfigured DebugEthernet interface with IP address as "€" shown in
"show run".
Risk of occurrence: Whenever show run is executed.

106
cq300234171 CBZ2712, SBZ2714, SBZ2755

Only the first DNS nameserver is used from the configured list.
Impact: Ping and traceroute with hostname will fail in case the first DNS server
is not responding.
Workaround: Set the working DNS server as the first one on the nameserver list.
cq300234172 CBZ2712, SBZ2714, SBZ2755

If DNS server is not reached during the first attempt, new queries will fail for a
while until requests timeout.
Workaround: Wait until all sent DNS requests are timed out and try again.
cq300234256 CBZ2712, SBZ2714

Removing members from a load balancing group may lead to datacut. Rsvp-trunk
can be removed from a load balancing group by removing the "lb-weight" option
from map-route. This may lead to a permanent datacut if the member to be
removed is the second last member of the load balancing group. If the data is cut,
reconfiguring the trunks is needed to restore the data.
Impact: Data cut may occur during reconfiguration of rsvp-trunks that are part of
a load balancing group.
Risk of occurrence: High in the described situation.
cq300234284 CBZ2712, SBZ2714

If a value greater than 2^31 -1 is assigned to ipIsIsMeshGroupV2, Tellabs 8000
intelligent network manager is not able to retrieve it correctly. This prevents
consistency check and configuration retrieval from the network element.
cq300234507 SBZ2714, CBZ2712

It is not possible to have 64-character names for pwe3 circuits that are used for
static ilm or ftn operations. For those circuits only names with up to 32 characters
are possible.
Workaround: Use names with max. 32 characters.
cq300234768 CBZ2712, SBZ2714

A delay might be introduced when removing point-to-point interface host (prefix
/32) entries from the routing table.
Impact: With a large number of /32 routes, the delay may cause some routing
protocols to lose connections to neighbors.
Risk of occurrence: On average the introduced delay is proportional to the
number of routes in general in the routing table.

107
cq300234920 SBZ2714
OSPF area additions and removals via the Tellabs 8000 Intelligent Network
Manager result in spontaneous reset of the network element in case there is not at
least 12 MB of free contiguous memory.
Impact: Loss of traffic during network element boot in single element network
elements. The network element does protection switch for the first command
(as the previously active side reboots).
cq300235931 LBZ2741
Failure in control card communication when the active backup card is reloaded
with ELP groups.
Impact: It is not possible to recover the control traffic when the backup card is
active and reloaded with ELP groups.
cq300236078 LBZ2713
Link state of the interface goes DOWN in ANSI mode after giving SONET
path-trace configuration to the POS interface.
Impact: If the link carries traffic, traffic flow will be cut during link down.
cq300236926 CBZ2712, CBZ2745, SBZ2714

IP reachability for PSN-tunnel is not checked for inner label with the value 3
(implicit null). When an IP route with MPLS nexthop using implicit null (3)
label is mapped onto an RSVP trunk with "IP traffic only" constraint, the route
is marked as inactive.
Impact: IP routes with MPLS nexthop using implicit null (3) label are marked
inactive if PSN tunnel has IP constraint set.
Workaround: Workaround is to not configure ip constraint when mapping a route
to PSN tunnel. E.g. in the RSVP case:
Before workaround:
rsvp-trunk abc
map-route 1.1.1.1/32 ip
After workaround:
rsvp-trunk abc
map-route 1.1.1.1/32
cq300236943 LBZ2754
Tunnel src pkt and octet counters are mixed in the BMI interface.
Impact: BMI shows incorrect counter values.
Workaround: CLI or SNMP shows the correct value.

108
5 Known Restrictions and Bugs
5.1 Restrictions
The issues listed in this section may require special attention during network configuration and
troubleshooting sessions.
For installation related restrictions, refer to chapter 2.4 Upgrade Related Notifications.
5.1.1 Restrictions in Tellabs 8600 Smart Routers FP4.1
• In Tellabs 8660 smart router and Tellabs 8630 smart router, sufficient CPU capacity should be
available in all the slots before upgrading the ESW from FP4.1 CIR3 to FP4.1 SP1, in order for
the package upgrade to succeed. The current 15-min CPU load of a slot can be verified using the
‘show cpu load minutes 15 slot <slot no>’ command. The upgrade should be performed when
the average CPU load is below 65%.
• CDC2 Ethernet user ports are not supported in the CBZ2745 embedded software in FP4.1.
• CDC2 USB port is currently not supported.
• CDC2 does not support the flexible Integrated Routing and Bridging (IRB) feature, whereas
CDC1 does.
• IFCs cannot be part of the ELC1 based flexible mode IRB configuration at all, neither on the
bridging nor on the routing side.
• The PLT network element sync pulse sending is disabled on a NE that has flexible IRB configured
and an ELC1 line card up and running to prevent the short traffic drops observed.
• 'All ports in use' is not supported for ELC1 with IRB. ELC1 IRB IP interface has a forwarding
performance limitation of 10 Mpps, which supports a maximum 20 Gbit/s bidirectional traffic
when the average packet size is 250B.
• The FP4.1 SP1 release does not support Ethernet OAM DM in ELC1.
• Multicast replication due to flooding in VPLS network transient situations may exceed the ELC1
with IRB forwarding performance of 10Mpps. Fourfold replication of unknown destination and
unicast traffic may exceed the 20Gbit/s bidirectional traffic limit with average packet size of
250B. VPLS network design should use dual-homed spokes (MTU-s Dual-Homing) and traffic
balancing to minimize flooding caused by single node failure, and avoid using ELC1 IRB with
VPLS. The ELC1 IRB application for RNC as well as the ELC1 IRB application for ETH-PW
termination to VRF are supported.
• Ethernet OAM is not supported on LAG and it shall not be configured.

109
• LAG interfaces and LAG member interfaces cannot be used as Ethernet OAM MEP or MIP. In
other words, Ethernet OAM frames cannot be terminated to a LAG interface; this covers all OAM
operations. Non-terminated Ethernet OAM packets are transparently passing by a LAG group.
Ethernet OAM configuration must be disabled on a link before a link is added to a LAG group.
Ethernet OAM can be used normally in non-LAG interfaces while other interfaces are forming a
LAG group.
• ELC1 RSVP-TE path protection switchover time may exceed 50ms, being in the order of 300ms.
• In MSP/APS protected configurations, VCG should not be configured if the IFC of the primary
interface of VCG is not present.

110
Pause Frame Restrictions
Ethernet provides a flow control mechanism by using pause frames. Handling of pause frames is not
uniformly supported by Tellabs 8600 smart routers. The following table identifies which products
support the handling of pause. See the footnote for the abbreviations used in the table6.
FE-LM GE-HM XE-HM GE

Tellabs 8605 Sup n/a n/a Sup
Tellabs 8609 NSup n/a n/a NSup
Tellabs 8611 NSup NSup NSup n/a
GE XE R1-IFM R2-IFM
ELC1 Nsup Nsup n/a n/a
IFC2 n/a n/a n/a Txsup
IFC1 n/a n/a Sup n/a
CDC2 n/a n/a n/a n/a
CDC1 n/a n/a n/a n/a
IEEE1588 L2 Boundary Clock Related Restrictions
In SR5.0, Tellabs 8600 smart routers implement a pre-standard version of the upcoming ITU-T
G.8275.1 (Precision time protocol telecom profile for phase/time synchronization with full timing
support from the network). Consequently some timing parameters are subject to change after the
standard has been approved (tentatively May 2014).
In addition to this, there are these known restrictions:
• Precision Time Protocol (PTP) over plain Ethernet (IEEE1588-2008 Annex F encapsulation) is
not supported by LAG interfaces or LAG member interfaces. That is, IEEE1588 Boundary Clock,
Grandmaster or Time Slave Clocks cannot be used over LAG. The IEEE1588 Frequency Slave
Clock is not affected, as it uses the IPv4 encapsulation (Annex D).
• In the current IEEE1588v2 Boundary Clock implementation, defaultDS parameters priority1 and
priority2 have a fixed value of 128 that cannot be changed. As these parameters have a strong
effect on the resulting Boundary Clock Topology, this must be taken into account when building
synchronization topologies consisting of both Tellabs and third party equipment.
• Per-link delay asymmetry compensation is not yet supported for the IEEE1588 Boundary Clock.
The expectation is that either equivalent length fibers are used or a single fiber with bi-directional
traffic.
• IEEE1588 Packet Delay Variation (PDV) statistics do not work with boundary clock.
• The pulse per second (PPS) port delay cannot be compensated yet. This means that the PPS cable
length should be taken into account while performing performance testing (typical figure is 4-5
ns of phase error per one meter of cable).
• LAG interfaces and LAG member interfaces do not support Synchronization Status Messaging
(SSM).
6Sup: RX and TX are supported. | Txsup: supports TX - received pause frames are ignored. | Rxsup: supports RX - pause frames are not transmitted.
| Nsup: No support for RX nor TX - received pause frames are ignored.

111
• The IEEE1588 clock identity is incorrectly set in dual CDC2 environments. By default, both
CDCs have a unique clockId while this identity should be global on one NE. As a result, the
clock identity MUST be overwritten manually when provisioning IEEE1588 L2 Boundary Clock,
Grandmaster, or Time Slave Clock.
• PTP Announce message rate is 1 pps instead of the 8 pps anticipated for the final version of
G.8275.1. This however has no impact on the achievable synchronization quality.
5.1.2 Restrictions in Tellabs 8600 Smart Routers Prior to FP4.1
• ETHoATM restrictions
• Supported only in 4xSTM-1 ATM IFM (LIA2210) IFM.
• Only one queue per ATM circuit is supported.
• VLANs and priority tagged frames are not supported on ETHoATM interfaces.
• ETHoIMA is not supported.
• PWE3 redundancy should not be used in ANSI mode.
5.2 Bugs
NOTE: Starting from FP4.1 SP1, the affected network elements are referred to as ‘8620 NE’,
‘CDC1’, ‘CDC2’, ‘IFC1’, ‘IFC2’ and ‘ELC1’, instead of the ESW codes SBZ2714, CBZ2712,
CBZ2745, LBZ2713, LBZ2741 and LBZ2754.
cq300026728 CDC1
1+1 protection of the management fast Ethernet interface does not work if VLANs
are used in the interface.
cq300067584 CDC1, IFC1, 8620 NE

The 2-bit traffic light (TL) assigned to a packet on the basis of an ACL rule is set
only to the first cell of the packet. Even if a policer is configured into a color aware
mode, the traffic light that is marked to the packet by ACL is not preserved because
the policer does its decision based on the last cell of the packet. Since the last cell
of the packet does not contain the TL assigned by ACL, the ACL TL value is lost.
cq300096058 CDC1, IFC1

Reverse address lookup works only in Tellabs 8620 smart router. In other products
it may pass through packets that should be dropped.
cq300109570 IFC1
A 24xchE1/chT1 Multiservice IFM (LIE2226) with an active HW fault causes the
card to remain in the booting up phase.
cq300109805 8620 NE, IFC1, CDC1, IFC2

If changing the IP MTU value to a higher value without shutting down the
interface, the interface does not take the new MTU size into use.
Impact: Packets that are larger than the prior MTU setting will experience
unnecessary fragmentation on the IP layer on the affected interface.
Risk of occurrence: This unnecessary fragmentation will always occur if an
interface is up during the IP MTU change to a higher value.
Workaround: Give the "shutdown" CLI command and then the "no shutdown"
command to the interface where IP MTU has been increased.

112
cq300115308 IFC1, 8620 NE

The CLI command "clear interface statistics so u/m/i" accepts "ppp-.." keywords
for the channelized SDH IFMs in ETSI mode.
cq300115309 IFC1, 8620 NE

The CLI command "clear interface statistics so u/m/i:k:l:m" fails for channelized
STM IFMs in ETSI mode.
cq300116238 CDC1, 8620 NE

When a Telnet connection is initiated from the network element, the TCP port used
cannot be specified. Instead the default port number is always used.
Impact: Telnet connections to third-party network elements that are using
non-standard port numbers cannot be established.
cq300116345 IFC1
MLPPP data cut when the laser off (MSP 1+1 unidir).
cq300126508 CDC1, 8620 NE

Traffic towards a particular VPN IP prefix may stop if this VPN IP prefix is
configured simultaneously by BGP and static configuration entry.
Impact: The traffic forwarded via the affected VPN route may stop.
Workaround: Do not mix static and BGP IP-VPN routing configurations in the
same VPN (VRF). Or if it is not feasible, make sure that BGP and static IP-VPN
routing do not configure the same IP prefixes.
cq300129850 8620 NE, CDC1

When logging in with SSH, the username/password must be given before the
banner is shown.
Impact: The custom banner message will not be displayed before login.
cq300134123 CDC1, IFC1, 8620 NE

The number of shapers that can be associated to a VLAN is limited to 930 in a
Tellabs 8620 smart router and 961 in a Tellabs 8630 smart router.
cq300136667 CDC1, IFC1, 8620 NE

RSVP FRR switchover times <50 ms protection cannot be guaranteed. The
number of protected LSPs and interface technology in use affect slightly the
switchover times. The best-case switchover times are ~5 ms, typical performance
is 40-70 ms while in some setups it can be up to 500 ms.
cq300156874 IFC2
For MPLS traffic coming in through IFC2, the DiffServ classification is not the
expected one. The setting "layer2Frame" for classification does not work for
MPLS traffic.
Also IFC2 follows the "short pipe" model, even if the uniform or pipe model
is configured.
Impact: If MPLS shim headers do not have DiffServ classification, traffic will
possibly be classified to a wrong class, often best effort.
Risk of occurrence: Always for pipe and uniform tunnel models, in IFC2.
Workaround: Arrange the network so that all MPLS headers contain reasonable
DiffServ classification in TC(EXP) bits.

113
cq300160637 IFC2, ELC1

When an Ethernet interface is ELP protected and you remove with Tellabs 8000
intelligent network manager the VLAN interfaces from the working side while the
protecting side is active, the running configuration and the interfaces configuration
of the working side become inconsistent, that is, the running configuration still
shows the interfaces.
Impact: The running configuration is inconsistent with the actual configuration.
cq300160798 CDC1, IFC1, IFC2, 8620 NE

In large configurations the "show interface" CLI command might cut and drop the
tail of the report.
Impact: The "show interface" CLI command report tail might be cut when there
is a large number of sub-interfaces per physical interface.
Workaround: Use a detailed sub-interface query instead of the "show interface"
query if the report tail is missing.
cq300163609 CDC1, 8620 NE

While logged in through AAA, a RADIUS user will not be able to create a local
user with the same username as currently logged in.
Impact: No other impacts than this: Only creating a local user with exactly the
same username that was used when logged in using RADIUS fails.
Workaround: Log in with a different username than is used for the RADIUS
server. Now it is possible to create an "original" user in the local database.
cq300170743 IFC1, IFC2

Copy&pasting the ELP passive mode rx-both configuration immediately after
creating the group causes ARP entries to be incomplete.
Impact: Continuous data cut.
Risk of occurrence: Regularly.
Workaround: Give the configuration commands after a little pause.
cq300171215 IFC1
When replacing the IFC1 part of the MSP1+1 protection group with a replacement
card which contains earlier configuration of the same network element and card.
During the bootup the replacement card is not fully handled as a replacement
but uses some of the old configuration and might mix up the operation of the
protection group.
Impact: Data cut is possible when doing switchover or directly after bootup
is done.
Risk of occurrence: Often under the described circumstances.
Workaround: Reboot both of the cards, one after the other. A better solution is
to clean the configuration of the replacement card before the installation with the
"clean-start" CLI command.
cq300171590 CDC1, 8620 NE

When the secondary path is active (the RSVP trunk configured to use the
secondary path with the "secondary prefer" parameter) and the secondary path link
fails, the data cut is over 50 ms (about 100 ms).
Impact: Over 50 ms data cut occurs on RSVP LSP.

114
cq300173356 CDC1, IFC1, IFC2

Due to asynchronous configuration of line cards, there can be a data cut when
traffic is restored from the protecting RSVP trunk to the primary one.
Impact: Data is cut when traffic is restored to the primary RSVP trunk. Large
amounts of trunks restored in a short time frame make the situation worse. A
single trunk is unlikely to be affected, but 100 trunks all restored at once (because
e.g. they all use the same link which becomes operational) cause a large load to
the line card CPU and is very likely to cause data drops.
Risk of occurrence: The risk of data cuts increases when the number of RSVP
trunks increases. The greater the number of RSVP trunks in use, the more likely
the longer data cuts become.
Workaround: The situation can be improved by spreading the wait-to-restore
timers of the trunks over a long period of time. For example, 500 ms spacing
between the trunks leaves that much time for every trunk to be restored before
next one.
cq300175308 CDC1, IFC1, IFC2, 8620 NE

Adaptive jitter buffer cannot be configured correctly by using Tellabs
8000 intelligent network manager. When trying to set adaptive jitter
buffer by using the VPN Provisioning tool, only the parameters
minimumDelayThresholdCrossingLimit and targetDelayThresholdCrossingLimit
can be set correctly. The other parameters cannot be changed from the default
values.
Workaround: Configure jitter buffer with CLI.
cq300184995 8620 NE, CDC1

The current implementation of resolution between competing IP and MPLS paths
is broken. One symptom of this can be seen when there exists a static IP route
using recursive MPLS lookup ("ip route 1.2.3.4/32 5.6.7.8 recursive-mpls") and
another protocol entry to the same FEC.
The following cases have been identified to be suffering from this bug:
1) When there exists at the same time a static IP route with recursive MPLS lookup
and at least one entry to the same FEC from one of the following sources:
- static MPLS
- RSVP
- LDP
- BGP
- non-recursive IP route
2) When there exists at the same time a BGP route and at least one entry to the
same FEC from one of the following sources:
- static MPLS
- non-recursive IP route
Impact: Permanent data break and wrong information displayed in "show ip
forwarding-table".
Risk of occurrence: High in vulnerable configurations.
Workaround: The existing functionality helps in some cases by not creating a
competing LDP PUSH entry when adding a static IP route with recursive MPLS
lookup. For example, the LDP in with label 1025 would not be created and this
would fix the problem as the priority resolution would not be needed anymore.
This workaround however is very limited in the sense that it only helps in some
cases with LDP PUSH causing the priority resolution, so it is useless in some other
cases, for example if the competing entry is RSVP.

115
cq300190069 IFC2
The ingress MPLS forwarding resource (MPLS lookup CAM) is a shared hardware
resource used by different protocol entries, such as MPLS LSPs, VLANs and
PWE3s. It is possible that this shared resource is fully consumed while the amount
of configured forwarding entries is within supported limits, in which case any new
configuration which requires an MPLS CAM forwarding resource will fail.
Impact: HW resource consumption prevents new forwarding configuration.
Risk of occurrence: Occurs always with a sufficient number of concurrent MPLS
LSPs, PWE3 and VLANs.
cq300193500 IFC1, IFC2, 8620 NE

When the CBR VP interface is created with the default Supported Service
Category (UBR) and the interface is reverted from the switched to terminated
state, the supported category list is extended to include all 5 service categories.
Impact: The protection mechanism to prevent the user from configuring VCCs
with wrong service categories does not always work.
Risk of occurrence: Occurs in a typical case.
Workaround: Remove additional service categories after reverting to the
switched mode.
cq300194305 8620 NE, IFC1

An n-to-1/VCG pseudowire stops carrying traffic if its traffic parameters are
changed from an IMA VC circuit, which is a part of an n-to-1 pseudowire.
Non-IMA VC circuits can handle the same kind of change in traffic parameters
without data cut.
Impact: Data transmission is affected.
Workaround: Delete the n-to-1 pseudowire configuration and then reconfigure it.

CLI fault and alarm messages do not contain full 64 character resource names,
only approximately 50 characters.
Impact: It might be impossible to differentiate between different resources.
Workaround: Make names unique with the first 48 characters.
cq300198951 IFC2
The Rx queue configuration fails occasionally for interface modules
8x10/100/1000BASE-TX R2 IFM (LIE2256), 8x100/1000BASE-X R2 IFM
(LIO2252) and 1x10GBASE-R R2 IFM (LIO2257) at boot up or when the QoS
mappings are enabled for the interface ports of the IFM.
Impact: Rx queue configurations are missing for the failing interface port.
cq300200379 IFC1, IFC2

PPP links may not always be inserted into an MLPPP group during an automated
test.
Impact: MLPPP group cannot be configured with a desired PPP interface.
Risk of occurrence: Minor.
Workaround: Deletion and recreation of PPP interface can be attempted.

116
cq300201508 IFC1, IFC2, 8620 NE

Action "ac-defect-action pw-down" does not work for TDM pseudowires.
Impact: In the case of CESoPSN or SAToP attachment circuit failure, the
pseudowire is not torn down and it still sends AIS traffic through the network, thus
consuming bandwidth unnecessarily. This is a problem if the network bandwidth
is a bottleneck.
Workaround: Do not configure non-active TDM pseudowires.
cq300203507 CDC1, 8620 NE, CDC2

FTP/CLI login attempts may cause a temporary (15-minute) denial of the
emergency snapshot functionality.
Impact: Emergency snapshot is not written to the flash and thus the latest
snapshot cannot be restored if necessary.
Workaround: Disable FTP and CLI (Telnet/SSH) when there is no need to use
them.
cq300210342 8620 NE, IFC1, IFC2, CDC1

MAC multicast filters added to a defined Ethernet interface during restart or
after it are not removed before the next restart even though the user changes the
configuration so that they should be removed.
For example, the OSPF multicast address is not removed from the interface before
the next restart even if OSFP has been disabled in the defined interface. Restart
the line card or the whole network element.
Impact: Unwanted Ethernet multicast frames are accepted to a defined Ethernet
interface.
cq300211086 CDC1, 8620 NE

Setting small interface link or IP MTU values, i.e. 64 bytes, while TCP connections
are already established might cause the network element to be unresponsive or
cause the control card of the network element to go to spontaneous reset.
Impact: A network element or card which is unresponsive or goes to spontaneous
reset may affect traffic.
Risk of occurrence: It could happen under the described circumstances.
Workaround: Use MTU values 512 or higher.
cq300213169 IFC1, IFC2, ELC1

If there is a static ARP configured for a given interface and there is routed traffic
transiting that interface (for the static ARP entry), if the interface is shutdown,
traffic will continue to flow for up to 30 seconds after the "shutdown" CLI
command is issued.
Impact: Traffic will not stop immediately on an interface that is shutdown if it has
an associated static ARP entry. Traffic stops after 30 seconds.
Risk of occurrence: Only occurs if that interface has a static ARP entry.
cq300213714 CDC1
After configuring a tracking delay for VRRP there is a period of 2 x "max delay
interval" when the tracking delay is not increased. During that time the tracking
delay works with the initial value. Tracking delay starts to increase correctly after
the period of 2 x "max delay interval".

117
cq300215122 CDC1, 8620 NE

RSVP-TE load balancing does not work if combined with FRR (fast reroute).
Impact: With FRR, traffic is not load balanced but goes through exactly one
RSVP-TE tunnel.
Workaround: Do not use RSVP-TE load balancing with FRR.
cq300215625 IFC2
VLAN statistics cannot be activated for a VSI port.
Impact: Once an interface is attached to a VSI, VLAN statistics cannot be
activated or deactivated.
Workaround: If VLAN statistics are required for a VSI port, they should be
enabled before the port is attached to a VSI. To enable or disable VLAN statistics
for a VSI port, the port needs to be detached from the VSI, VLAN statistics then
enabled or disabled, and reattached to the VSI.
cq300219948 IFC2, IFC1

ATM interface statistics are not protected. Interface statistics from the working
side are not delivered to the protecting side.
Impact: Interface statistics values are lost when protection is switched.
cq300220057 ELC1
When multicast/broadcast frames greater than 1518 bytes are received in a
line card or sent from it, the Rx/Tx multicast/broadcast frame counts are not
incremented. Instead, these packets are counted as unicast packets.
Impact: Statistics do not work correctly for the mentioned packets.
cq300222531 CDC1
When an ATM VP/VC interface is first used as a PWE3 endpoint and then the
PWE3 is removed and the interface is re-used as an AAL5 ATM IP interface (IMA
or ATM), the interface will not ping/respond to IP pings.
Impact: The interface will not ping/work correctly as an IP interface if it is
"converted" from an ATM PWE3 endpoint to an ATM AAL5 IP interface (same
applies to IMA interfaces).
Risk of occurrence: Always under the described operational sequence.
Workaround: Delete the ATM/IMA VP/VC first, and recreate it before assigning
an IP address to the interface. If this sequence is followed, the interface will work
as expected.

118
cq300225036 CDC1
During boot up the following alarm can be seen:
001: Slot 1: SW-MANAGEMENT:Boot SW: Corrupted SW.
Critical, Equipment alarm, Red led
Fault ON 12:44:14.5 UTC Thu Apr 12 2012 /12:44:14.5 LOCAL Thu
This is due to a timing issue in the algorithm used to calculate the checksum.
The checksum is incorrectly calculated and the software thinks the boot code is
corrupted. However the alarm is invalid and the alarm can be ignored.
Impact: It does not affect live traffic. The user will see an alarm stating the boot
code is corrupt.
Risk of occurrence: Low. It seems to happen more when the network element
has a clean start.
Workaround: The alarm is cleared if the software is reloaded in the control card
or network element. If that control card is a redundant control card, switchover to
the standby control card should be done first.
cq300225142 IFC2
PE-bound VLAN statistics are not counted for an Ethernet PWE3 (traffic coming
from an attachment circuit). Port statistics and CE-bound VLAN statistics are
counted.
Impact: PE-bound VLAN statistics are not counted for an Ethernet PWE3 (traffic
coming from an attachment circuit).
cq300225143 ELC1
In group shaping, an ELC1 line card cannot be in the ingress side of shaped traffic.
As a result, in group shaping, traffic coming through the ELC1 does not participate
in group shaping but in port shaping (if any).
Impact: In group shaper configuration, traffic where the ELC1 line card is at
ingress is not shaped.
Workaround: If a group shaper is configured, the ingress card must be IFC2 (full
support) or IFC1 (some limitations).
cq300225574 CDC1, IFC2

When using ~5000 or more pseudowires and 500 + 500 RSVP sessions in a single
network element with IFC2(s) present, some of the RSVP sessions might flap
after control card switchover.
Impact: If there is no backup path or both primary and backup happen to flap
simultaneously, there will be data loss.
Risk of occurrence: Uncommon.
cq300225683 CDC1
Extra "InstCalcInstIdGenerateId: Unknown InstIdExt" prints are printed to the
console output on boot up. This happens only if there are created VCs and the
network element is upgraded from earlier releases to FP4.0.

119
cq300225896 CDC1, IFC1, IFC2, ELC1, CDC2

Gateway ARP resolution may hang on IRB when the IRB interface administrative
state is changed to 'up'. The problem is automatically resolved after the ARP
timeout period (default 1200 seconds).
Impact: Traffic will not flow through a gateway route until the gateway MAC is
resolved.
Workaround: Give the "shutdown" CLI command and then the "no shutdown"
command to the IRB interface.
cq300225978 CDC1, CDC2, IFC2

If the user has attempted to create more VLANs on an Ethernet Link Aggregation
(LAG) group than is allowed by the internal resources of the network element,
and then deletes some of the successfully created VLANs, there are some minor
problems in the user interface.
Impact: If the user has attempted to create more VLANs on an Ethernet Link
Aggregation (LAG) group than is allowed by the internal resources of the network
element, and then deletes a successfully created VLAN,
- the deletion takes a long time, approximately 1 minute;
- a message "Not created/deleted, failure in command execution" is printed, even
though the VLAN actually is deleted.
Workaround: 1) Do not attempt to create too many VLANs. The limit to be
observed is:
(number of all interfaces (including VLANs) outside LAG groups) + (sum over
LAG groups)(number of group members * (number of VLANs in the group+1))
<= 8000 per line unit, and <= 16000 in the network element.
2) If too many creations were nevertheless attempted, and you later want to delete
some of the existing VLANs on the LAG group, be prepared to wait for 1 minute
for command completion, and ignore the error message "Not created/deleted,
failure in command execution".
cq300226053 IFC1, IFC2, 8620 NE

If line loopback (loopback-to-line) is enabled on a 4xchSTM-1/chOC-3
Multiservice IFM (LIO2234) and a pseudowire redundancy group is configured
on the IFM, the operational states of the pseudowires belonging to the group go
DOWN.
Impact: If loopback-to-line is configured in 4xchSTM-1/chOC-3 MS IFM, the
pseudowire redundancy group configured in the interface will go DOWN and
traffic cut will be observed. When the loop is removed, the traffic recovers.
Risk of occurrence: Always under the described circumstances
cq300226321 IFC2
Inter-Frame Delay Variation (IFDV) in EOAM is presented as system internal
time ticks, instead of microseconds as the Two Way Delay (TWD).
Impact: IFDV is value shown is incorrect.
Workaround: Multiply the time by constant 1 nanoseconds/tick.
cq300226720 ELC1, IFC1, IFC2

When ELC1 goes to spontaneous reset, the PWE3 redundancy switch causes data
break without VCCV BFD and prefer-all options.
Impact: Data break of 1s - 6s will occur.
Workaround: Use options VCCV BFD and prefer-all to minimize the downtime.

120
cq300226785 ELC1
On ELC1, ARP cache is not properly updated when an ARP entry moves from one
interface to another within the same card. This may happen when IP configuration
is created on an interface, then removed and recreated on another interface within
the same ELC1 card.
Impact: The moved ARP entry is not functional, and traffic to/via that IP address
will not flow.
Workaround: Clear the ARP cache with the CLI command "clear arp-cache".
This will clear all ARP entries in the entire network element so all Ethernet traffic
will be momentarily cut. An unused ARP entry will also expire, so it is possible to
avoid traffic breaks by waiting until the ARP entry expires before recreating the
IP configuration on another interface.

VRF connected route leaking does not work between two VRFs if IRB is an
endpoint of the VRF and the VRFs are in the same network element. In fact the
routes leak between two VRFs but traffic is not passing between VRFs.
Impact: It affects live traffic.
Risk of occurrence: Always when two VRFs are terminated on the same network
element and IRB is a VRF interface. When VRFs are terminated on two different
network elements, traffic is passing between two VRFs.
Workaround: Do not use IRB.
cq300227080 CDC1
ARP cache listing might show unnecessarily incomplete entries regarding the
management interface.
Risk of occurrence: Occurs sometimes after control unit boot-up.
Workaround: Clearing the ARP cache should remove the incomplete entries.
cq300227102 CDC1, CDC2, 8620 NE

There are inconsistencies in the CLI command "snmp-server traps mib" between
CLI and "Tellabs 8600 CLI Commands Manual"
Impact: In the CLI command "snmp-server traps mib <mib> <trap_name>" the
format of the trap_name is changed so that e.g. the trap name 'rsvpMplsTnDown'
is replaced with rsvp_mpls_tn_down if the used MIB value is among these:
[ping|traceroute|entity|rsvp|ldp|isis|tlab8600FaultTraps]
Risk of occurrence: It occurs only if the CLI command "snmp-
server traps mib <mib> <trap_name>" is used with MIB values
[ping|traceroute|entity|rsvp|ldp|isis|tlab8600FaultTraps].
Workaround: Use new trap names in the CLI command "snmp-server traps mib
<mib> <trap_name>".
cq300227489 CDC1, 8620 NE

UDP checksum calculation can result in zero for the packet to be transmitted. In
this case all bits of the resulting checksum should be swapped to one as stated
in RFC768. However this is not done for protocol packets and zero is used as
a checksum.
Impact: Because a zero value signifies “no checksum validation”, packets with
zero value will not be dropped in the receiving network element even if they
have been corrupted in transmission.
Risk of occurrence: Only in the case when checksum calculation of transmitted
UDP packet would result in zero.

121
cq300227967 8620 NE, CDC1

Packet Loop Test (PLT) delay test may lose some packets. In very rare cases the
test generator sends less packets than specified. This is seen as packet timeouts in
test results and missing packets in the echo server side. Usually only a miss of one
packet is seen if the problem occurs.

ELP switchover from the working to the protecting side or vice versa may cause
a ca. 500ms data cut.
Impact: Temporary loss of traffic.
Risk of occurrence: Randomly.
cq300228011 CDC1, CDC2

SNMP tlab8600FaultMIB eventHistoryTable object value for
eventHistoryLastTimeString shows value "01/01/2000 00:00:00" as null value (i.e.
the value to indicate that the event never happened). According to specification
the null value should be "01/01/1970 00:00:00".
Workaround: The user shall interpret "01/01/2000 00:00:00" as “never
happened”.
cq300228305 IFC2
MSP1+1/ELP groups may switch from the primary to backup interfaces when the
active CDC is disconnected and reconnected back in less than 10 minutes.
Impact: Traffic is not cut. The activity of the protection group is on the wrong
side.
Workaround: Switch protection manually to the primary side.
cq300228311 ELC1
The interface hold down feature does not clear the link down fault immediately
after the link is physically UP.
Impact: Troubleshooting with the present implementation will have no impact on
the functionality.
Workaround: "show interface <interface>" will show the exact state
of the hold-down behavior, i.e. when the link is down, the state will be
"entering-hold-down", and when the link is up and restoring, the "state" will be
"hold-down", "exit timer" will be decrementing and exit packet counter will be
incrementing (if exit packet counter is configured) .
cq300228864 IFC1, IFC2, 8620 NE

Show interface <eth> always shows the current MAC address in use and not
the actual hardware MAC address when a user-configured MAC address exists
on the interface.
Impact: The actual hardware MAC address will not be visible if a user-configured
MAC address is present in the interface. The configured MAC address needs to be
removed in order to see the actual hardware MAC address.
Risk of occurrence: Always under the described circumstances..

122
cq300228901 CDC1, 8620 NE

RSVP-TE path protection switch time is slow when PHP is used in one hop
configurations.
Impact: RSVP-TE path protection works in slow mode only if PHP is used in
one hop case.
Workaround: Do not use PHP in one hop configurations.
cq300229733 ELC1, IFC2

Dynamic MAC address entries learned from an SLI that is down may remain in
the switching table, if traffic is on while SLI is being shut down.
Impact: When shutting down an SLI while traffic is on, entries for MAC
addresses appearing in traffic may be left in the switching table. Traffic to these
MAC addresses may find an alternative path -- if one exists -- only after the MACs
have aged out and the traffic gets flooded.
Workaround: Case-specific: may involve adjustment of aging timeout, manually
clearing MACs, or setting static MAC entries.
cq300230657 IFC2
Illegal configuration involving both port SLI and VLAN SLI(s) in the same port
disables traffic permanently on IFC2, when port SLI configuration is removed.
Impact: When illegal configuration involving both port SLI and VLAN SLI(s) in
the same port is applied, no recovery without some loss of traffic is possible.
Workaround: Avoiding illegal configuration.
cq300230985 IFC2
When VLAN statistics are enabled for a VLAN interface on an IFC2, a line card
that is rebooted (for example due to software upgrade) may enter into a very long
reconfiguration loop. The reconfiguration loop will eventually finish, but uses a
lot of CPU. This may starve other tasks in the system of CPU, and cause network
protocols to timeout and clear established sessions.
The problem has been corrected in FP4.0 SP3, but older SW may have left internal
databases in inconsistent state. Thus upgrade to FP4.0 SP3 may also be affected.
Upgrade from FP4.0 SP3 to newer SW is not affected.
Impact: Network protocols may timeout and clear established sessions. This
will cause traffic cut until the sessions are re-established. The duration of the cut
depends on the number of VLANs with statistics enabled. This may be several
minutes in large configurations.
Risk of occurrence: Increases in direct proportion to the increase in the number
of statistics enabled VLANs. Hundreds of statistics enabled VLANs are almost
certain to cause data breaks.
Workaround: Disable VLAN statistics during SW upgrade.
cq300231620 CDC1
Tellabs 8000 intelligent network manager operations may slow down if query rate
(queries/second) from Tellabs 8000 intelligent network manager to the network
element is continuously high.
Risk of occurrence: Always under the described circumstances, more likely
with big configurations.

123
cq300232115 IFC2, ELC1, IFC1, 8620 NE

The following Ethernet modules do not support Equipment loopback:
- Tellabs 8605 smart router
- ELC1
- 8x100BASE-X IFM (for IFC1)
- 2+6x10/100/1000BASE-COMBO IFM (for IFC1).
The following Ethernet modules do not support Equipment loopback only if SFP
is missing from the interface
- 8x100/1000BASE-X R2 IFM (for IFC2)
- 1x10GBASE-R R2 IFM (for IFC2).
cq300232238 CDC1, CDC2, 8620 NE

The wrong error code ('target unit not responding') is returned to Tellabs 8000
intelligent network manager when trying to remove a non-existing static DNS
hostname through BMI.
Impact: It does not affect live traffic. The error code can be ignored.
cq300232369 CDC1, IFC2, ELC1

Port related QoS configuration commands fail after IFC2 upgrade to ELC1. Port
related CLI commands such as 'qos mapping use ingress' are not working after
the upgrade.
Impact: Port related QoS configuration commands fail.
Workaround: Reboot of the network element.
cq300232626 CDC1, CDC2, 8620 NE

ARP table entries for static routes are not removed immediately after deleting
the route.
Impact: Obsolete ARP entries are temporarily shown in the ARP table.
Risk of occurrence: Always when static routes are deleted.
Workaround: Obsolete ARP entries are removed after ARP timeouts or interface
link status changes.
cq300232742 CDC1, CDC2

Some short ISIS frames may have 4 bytes of additional padding.
cq300233630 CDC1, CDC2

The actions service-policer and no-reverse-path-verification cannot be configured
for the same ACL sequence number by CLI.
Impact: The latter action of the ACL rule is not performed.
Workaround: Use Tellabs 8000 intelligent network manager instead of CLI.

124
cq300233848 IFC1, IFC2

The documented scalability figures are not achievable for CESoUDP.
Impact: When the actual scalability figures (to be measured) are exceeded, all
circuits configured on the same module start to drop packets. This may cause
an outage.
Risk of occurrence: Always when the actual scalability figures are exceeded.
cq300234567 ELC1, IFC1, IFC2

When an ECMP group member is dropped due to link down and then added back
to the group the loadbalancing may send traffic over the member before ARP has
resolved for the destination IP on the added link, and traffic on interfaces on this
link may be dropped for a limited period of time.
Impact: Some the IP traffic streams over ECMP are dropped for a limited period
of time.
Workaround: Use link protection - ELP or LAG - to prevent the link down
impact.
cq300235115 ELC1
Unknown unicast MAC flooding has a performance issue in ELC1 VSI
configurations with a large number (m) of SLIs. When a number (n) of nearly
simultaneous unknown DA frames need to be flooded to a large number (m-1) of
SLIs, the actual number of flooded packets (p) is less than required n*(m-1) to
ensure that the frames are flooded to all SLIs.
Impact: Flooded frames do not always reach destination and they need to be
resent.
Risk of occurrence: High in very large VSI (>100 SLIs) configurations.
Workaround: Avoid large VSI configurations, that is, VSIs with more than 100
SLIs, excluding mesh-pseudowires.
cq300235294 ELC1
Received pause frames are ignored by ELC1 cards. The command for enabling
and disabling pause frame handling does not have effect on ELC1.
Impact: ELC1 does not react to pause frames.
cq300235364 CDC1, CDC2

When Ethernet port protection is enabled, the protecting-side MTU values are
not copied from the working side as they should. This may cause data cuts after
switchover to the protecting side, if the working side has a higher link MTU value
than the protecting side at the time of the creation of the protection group.
Impact: If the working interface has a greater link MTU than the protecting
interface when Ethernet port protection group is configured, data packets larger
than protecting side MTU do not pass after switchover to protecting side.
Workaround: MTU values should be configured after the creation of the Ethernet
port protection group and after the removal of Ethernet port protection group, to
ensure consistent configuration.

125
cq300235531 IFC1, IFC2

ETHoMLPPP pseudowire statistics (Tx Bytes and Tx packets) are not incremented
with 24xchE1/chT1 Multiservice IFM (LIE2226) when "no ppp mp headers
mlppp" is configured. This issue is related only to statistics and traffic will not be
affected.
Impact: ETHoMLPPP pseudowire Tx statistics are not incremented when "no
ppp mp headers mlppp" is configured
cq300235687 IFC1
The far end link state is down after giving "shutdown-if" command in the near end.
Impact: Whenever the "shutdown-if" command is given in the near end, the far
end link will go down.
Workaround: shut/no-shut on the near end link will make the far end link up.
cq300236327 IFC2
Queue statistics will not increment for LAG VLAN interface. It will not be
possible to see the number of passed through packets and octets for the interface.
Impact: Although traffic will flow successfully through a LAG VLAN interface,
it will not be possible to see the statistics for the interface.
cq300238440 CDC1, CDC2

Removal of the primary or secondary E-LSP with 'no {primary|secondary}
elsp-preconfigured' command is not perfectly handled by the LSP protection pair
algorithm, which results in an error being shown on the console output.
Impact: An LSP protection related error is shown on the console output. The
configuration is nevertheless properly removed.
cq300238771 8620 NE, IFC1, IFC2

Synchronization quality value ql_stu (ANSI mode) is not transmitted from
1xchSTM-1/chOC-3 Multiservice IFM (LIO2203).
Impact: Best possible synchronization source might not be selected for network
element synchronization.
cq300238805 CDC1, 8620 NE

In case of very heavy load, sending a poll message fails even once the network
element is reset.
Impact: In case issue occurs, the network element reboot will be initiated.
Risk of occurrence: Very rarely.
cq300238840 CDC1, CDC2, 8620 NE

When an ATM interface is protected, and the protecting side interface is removed,
the protection is left into an inconsistent state. Removing the working side may
cause a spontaneous reboot of the network element.
Impact: All traffic will be lost until the network element recovers.
Workaround: Always remove protection before removing an interface.

126
cq300238925 CDC1, CDC2

SSM SA-bit cannot be modified on the protecting side SCI. This fails only with
Tellabs 8000 intelligent network manager, the corresponding CLI command works
fine.
Impact: May cause loss of synchronization in case quality levels are enabled in
the network, and a non-default SA-bit setting is used on the working side control
unit, and a unit switchover is triggered.
Workaround: Issue the command from CLI.
cq300238931 IFC1, IFC2, 8620 NE

When setting pdh-interface to 'shutdown-if' state and then 'no shutdown-if' state,
the interface starts to send wrong quality level to the remote end node. For
instance, when 0xa (ql-st3) should be sent, 0 (ql-stu) is sent instead. This error
happens only in ANSI mode.
Impact: Loss of synchronization in downstream NEs, in case quality-levels are
used in the network.
cq300238998 ELC1
When associated ACL contains unsupported actions for ELC1, faults are not
raised accordingly.
Impact: Faults are raised and cleared incorrectly. This has no impact on services.
Risk of occurrence: Always when configuring unsupported ACL actions for
ELC1.
Workaround: Do not configure unsupported ACL actions for ELC1/action
Policer or reverse action lookup (RAL).
cq300239055 IFC1, IFC2

For pseudowires attached to ETHoPPP/ETHoMLPPP interfaces, the Rx bit rate
field in the pseudowire performance statistics shows incorrect value. The value
will be slightly less than the actual rate.
Impact: Rx bit rate field will display incorrect value for ETHoPPP/ETHoMLPPP
pseudowires.
Risk of occurrence: Always for ETHoPPP/ETHoMLPPP interfaces.
cq300239128 CDC2
In CDC2 protection topology, when more than 7350 PWE3 are attached to VLAN
interfaces, CDC2 in slot 1 (passive CDC2) will go to continuous booting. Slot 14
(Active CDC2) will be up and running
Impact: CDC2 protection will be degraded.
Workaround: Do not attach more than 7350 PWE3 to VLAN interfaces.
cq300239134 CDC1, IFC2

During IFC2 IRB Ethertype 0x88a8 traffic tests CDC2 MFE interface protection
in CDC2 switchover is not working properly and console errors are seen.

127
cq300239150 8620 NE, IFC1

PPP OSINL-CP Link Down fault may appear on PPP or ML-PPP interfaces which
have ISIS enabled. This is a false alarm which does not affect traffic.
cq300239261 CDC2
In some rare cases, during boot-up SCI input interrupts may not be handled
correctly and the SCI state remains failed.
Impact: If SCI is the only clock source and this problem should occur,
synchronization from SCI cannot be used without the workaround.
Risk of occurrence: Very rare. This condition may occur only when booting up
with a preconfigured CDC2 and SCI is the only clock source.
Workaround: If SCI remains in failed state even though the cabling is correctly
done, disable and re-enable SCI to solve the problem.
cq300239366 CDC2
Per bridging instance MAC learning commands flush the MAC forwarding table
for all bridging instances in the H-VPLS application setup.
Impact: MAC forwarding table is reset, which causes flooding and relearning to
happen until the flushed addresses are relearned.
Risk of occurrence: High in very large VPLS configurations.
cq300239567 CDC2, ELC1

IEEE1588 slave RX Announce message counter does not increment, although the
announce messages are sent and received to the Tellabs 8609 smart router. The
message counter has value 0.
Impact: Received announce messages are not seen in the 1588 statistics when
"show node-timing IEEE1588 slave" command is used. This does not affect the
functionality of the IEEE1588 slave. This is a bug in the statistics.
Workaround: The CLI command 'show node-timing ieee1588 clock-if geX/Y'
shows the announce message RX counters.
cq300239570 ELC1, IFC2

After setting bridging instance (VSI) mac-learning limit, re-learning after
manually clearing MAC Addresses is not always happening correctly.
Impact: Sometimes the MAC Addresses are not learned up to the limit set.
Workaround: Avoid using MAC Address learning limits.
cq300239571 CDC1, CDC2

During software upgrade, the software package may be left unactivated with an
unexpected error.
Workaround: Software package needs to be reactivated.
cq300239762 ELC1
The number of learned MAC addresses exceeding 256K limit will be visible in the
MAC forwarding table (show bridging-instance) until manually cleared.
Workaround: Clear MAC table manually (clear bridging-instance name
<bridging-instance name> macs).

128
cq300239980 CDC1, IFC2

Setting a virtual switching instance (VSI) administratively down (shutdown) stops
multicast traffic and disables MAC learning, but does not have effect on the
unicast traffic with already learned MAC addresses.
Impact: A VSI forwards unicast traffic even when it is set administratively down
(shutdown).
cq300239983 CDC1, IFC2

The configuration refresh logic for IFC IRB and MAC switching during CDC
switchover and line card reconfiguration is sub-optimal. This degrades somewhat
the tolerancy against internal data corruption caused by ESW malfunction.
Impact: Recovery from some classes of rare ESW-internal data corruptions
is compromised. This may lead to resource leakage or forwarding hardware
misconfiguration in the rare cases where an unknown ESW fault has corrupted the
ESW internal data in a way that would get repaired by a flawless refresh sequence.
cq300239984 IFC2
CLI command 'qos mapping use egress traffic layer2-frame' is always enabled for
ACs connected to a VSI, so only the mappings defined by 'qos mapping egress
qos' always take effect.
CLI command 'qos vlan ingress/egress vlan-pri' does not take effect, instead the
mappings defined by 'qos mapping ingress/egress qos' always take effect.
Impact: It is not possible to override 'qos mapping ingress/egress qos' by the
commands specified above. You should always define specific mappings between
PRI and internal QoS both ingress and egress to ensure correct PRI for Ethernet
services.
cq300240149 IFC1
When MSP is configured on a interface, its line state remains UP even when both
the primary and backup interface links go to down state. So in a redundancy
setup with MSP for primary trunk, if the link down occurs in both primary and
backup interfaces of the primary trunk, it is not detected and hence switchover to
the alias interface happens only after LDP timeout. This results in a switchover
time of around 40 to 50 seconds.
Impact: Data traffic during the switchover will be lost.
Workaround: IP OSPF BFD configuraton reduces switchover time.
cq300240652 CDC2
PTP clock class and clock identity of an adjacent master is not shown with the
command 'show node-timing ieee1588 slave'.

129
cq300240706 IFC2, IFC1

MSP secondary side interface is not passing traffic after network element reload
with the primary interface removed because the MTU setting on the secondary
side is not correctly synchronised with the working side.
Impact: Packets exceeding the MTU are dropped on the secondary interface.
Workaround: The working side interface must be present when doing the
network element reload.
cq300240872 IFC1, IFC2

ARP does not resolve for protected ETH_o_FR, ETH_VLAN_o_FR,
ETH_o_ATM, ETH_VLAN_o_ATM, ETH_o_PPP, ETH_VLAN_o_PPP logical
interfaces when working side is missing at network element reload.
Impact: There is no IP traffic over the Ethernet logical interfaces.
Workaround: Ensure that the working side is present at network element reload
time.
cq300240971 CDC2
1588 TIE monitor is not supported on the CDC2 card.
Risk of occurrence: Always.

Loss-measurement quality of service is not found correctly during boot from the
interface, which may prevent the addition of loss measurement configuration to
the network element. If the situation occurs, the configuration is lost. In NEs with
protected control units this causes also occasional boot of the passive unit.
Impact: Missing configuration.
cq300241017 CDC1, CDC2

Proper ingress and egress VLAN PRI QoS mappings are required for Ethernet
OAM loss measurements. Also VLAN PRI mappings shall not be modified when
Ethernet OAM loss measurement is ongoing.
Impact: If VLAN PRI mappings are not properly set, loss measurements cannot
be enabled. If mappings are modified while the LM is active, proper measurement
values or behaviour cannot be guaranteed.
Workaround: Disabling the loss measurement before modifying QoS mappings,
and re-starting the loss measurement again after that.
cq300241252 CDC2
Manual overwrite of the IEEE1588 clockIdentity attribute is not reflected in
PTP header (sourcePortIdentity.clockIdentity). Instead the default clockIdentity
value is kept.
Impact: May impact IEEE1588 clock selection in adjacent nodes in case the sync
topology requires the clockId to be overwritten manually.

130
cq300241410 CDC1, CDC2, IFC2, IFC1

The 'show-ip-statistics' command may produce an error if the CDC in slot 1 is
physically present in the network element but not added to inventory.
Workaround: Either add the unit back to inventory or remove it from the rack.
cq300241465 IFC1
When a large amount of Tellabs 8000 intelligent network manager or CLI
commands are executed, there will be delay in the response (200-400 ms) for
every few commands executed.
Impact: Tellabs 8000 intelligent network manager dialogs will open slower than
expected. CLI command execution will experience delay (200-400 ms).
Workaround: If possible, reduce Tellabs 8000 intelligent network manager
statistics polling.
cq300242104 CDC1
When a network element has non-stateful ARP configuration and a neighboring
network element MAC address is changed, unnecessary ARP status messages
may be shown on the console.
cq300242154 CDC2
IEEE1588 Packet Delay Variation (PDV) statistics do not work with boundary
clock. Querying the statistics will fail with 'instance not found' error.
cq300242297 IFC1, IFC2, 8620 NE

ATM circuits, which are members of a VCG group, do not send OAM AIS cells
when the VCG PWE3 is down.
Impact: OAM AIS consequent action is missing from the VCG member ATM
circuits.

ARP cache entry may be left unexpired for an indefinite time.
Risk of occurrence: Dependent of ARP cache timer values, thus rare.
Workaround: ARP cache can be cleared, which should resolve the issue.
cq300242757 CDC2
When route database is larger than 225000 entries, IP lookup CAM current usage
shows more than 100% usage.
Impact: IP lookup CAM current usage shows incorrect reading.

131
cq300243384 ELC1
IRB ARP cache is not cleared via normal IP interface ARP cache timeout, but
the ARP entry for the IRB network IP is refreshed automatically just before the
timeout. The ARP cache can only be cleared by the user with clear ARP cache
command.
Impact: ARP cache entries for IRB IP interface do not expire.
Workaround: The user can clear the ARP cache.
cq300243478 CDC1, CDC2, 8620 NE

Routemap delete is not possible if the map is emptied and less than 30 seconds has
passed since the last BMI/CLI operation.
Workaround: If the last routemap section is removed, wait 30 seconds before
deleting routemap.
cq300243513 CDC1
After CDC switchover, Ethernet Bridging object instances are reported as having
unit 1 instead of the correct unit 14.
Impact: In the Bridging dialog in Tellabs 8000 intelligent network manager, the
right interface information cannot be mapped.
cq300243760 CDC1, CDC2

'MiscCommonTaskStartRemoteService failed' is written to os-log without a cause
in Tellabs 8660 smart router and Tellabs 8630 smart router.
cq300243917 CDC2
The IEEE1588 clock identity is incorrectly set in dual CDC2 environments. By
default, both CDCs have a unique clockId while this identity should be global on
one NE.
Impact: In case of CDC2 switchover, the IEEE1588 clockId is changed unless it
was manually overwritten. As a result the other IEEE1588 clocks may change their
BMCA selection, and the synchronization topology of the network may be altered.
Workaround: Overwrite the IEEE clockId manually. For example, from the CLI
command 'node-timing ieee1588 clock-id'.
cq300243919 CDC1, CDC2

When sending large frames exceeding IP/MPLS MTU through IRB there is
significant loss of frames. This is due to the fact that the fragmentation must be
handled by the CPU, which has a limited capacity and is protected by shapers.
Shapers will drop fragments quite early to prevent DoS attacks.
Impact: Loss of traffic exceeding IP/MPLS MTU, if the rate is high enough.
Risk of occurrence: Always when packets exceeding IP/MPLS MTU are sent
on a high enough rate.
Workaround: Network should be configured so that there is no need for
fragmenting MTU exceeded packets.

132
cq300243925 ELC1
There is no multicast storm fault for IRB IP interface. Storm protection however
is working.
Impact: There is no fault indication when the storm is on.
Risk of occurrence: Always under the storm.
cq300244214 ELC1
There has been a short IRB traffic drop at a 60 s interval (when network element
RTC turns to xx:xx:58) in some test environments. The data cut has not been
reproducible by a known method. Analysis of the failing cases indicates that
Packet Loop Test (PLT) network element sync pulse causes the drop in ELC1 line
cards. The PLT network element sync pulse sending is disabled on a NE that has
flexible IRB configured and an ELC1 line card up and running to prevent the
short traffic drops observed.
Impact: PLT delay measurements for round-trip and one-way delay will not give
any usable results, if there is flexible IRB configuration in the NE and there is at
least one ELC1 line card up and running.
PLT delay variation test and PLT throughput test are still usable.
cq300244247 IFC2, ELC1

A fault generated by VRRP mastership change is stored only on the CDC control
card that was active during the generation of that fault. Due to this, faults can be
found only in the history of the CDC that was active during the fault.
Impact: Live traffic is not affected. The impact is that some faults might be
missed, if the fault history is taken from one CDC only.
Workaround: Fault history should be taken from both CDC control cards, if the
VRRP mastership change alarms need to be tracked.
cq300244303 IFC2, IFC1

In 1xchSTM-1/chOC-3 Multiservice IFM (LIO2203), the MS layer signal degrade
fault will not be reported when the SDH port receives the MS BIP errors and the
error rate is greater than the configured signal degrade threshold. The BIP counters
will increment in the 'show interface' CLI command.
Impact: MS BIP error counters will be incremented, but the MS signal degrade
fault will not be reported.
Risk of occurrence: Always under the describes circumstances.
cq300244423 ELC1
'All ports in use' is not supported for ELC1 with IRB. ELC1 IRB IP interface has a
forwarding performance limitation of 10 Mpps, which supports a maximum 20
Gbit/s bidirectional traffic when the average packet size is 250B.
Impact: Packets are dropped with no QoS consideration, if the 10Mpps egress
traffic rate is exceeded.
Risk of occurrence: Always on ELC1 with IRB interfaces.
Workaround: Plan the IRB connectivity so that you do not exceed the 10Mpps
egress traffic rate on the ELC1 IRB interfaces on single line card.

133
cq300244461 CDC2, ELC1

With 450 MPLS-TP protection groups the traffic loss is sometimes present for
more than 50 ms. This is seen when the attachment circuit is in the same line card
as the MPLS-TP back-up tunnels. With 400 groups this loss is always less than
50 ms. With 450 protection groups the issue is not seen when the attachment
circuit is in another line card.
Impact: Traffic loss for more than 50 ms can be seen when the attachment circuit
is in the same line card.
Workaround: If 450 protection groups are needed, then the attachment circuit
must be configured on another line card which is not same as the line card with
the MPLS-TP backup tunnels.
cq300244475 IFC1, IFC2

When HP-SDH tester injects VC4-UNEQ error to the STM-1 port of
4xchSTM-1/chOC-3 Multiservice IFM (LIO2248), the port does not send back
VC4-RDI to HP-SDH tester.
Impact: VC4-RDI alarm is not received by HP-SDH tester.
cq300244478 ELC1
If the network element is operating as a IEEE1588 boundary clock (slaved from a
PTP input), the seconds part of the sent PTP frames is incorrectly set on ELC1s
that do not have the slave port. The nanosecond part is accurate and thus this as no
impact on phase synchronization accuracy.
If the network element is operating as a grandmaster (slaved from a 1PPS input)
also the seconds part is updated correctly.
Impact: Customer cannot see proper calendar time from PTP messages sent from
ELC1s that do not have a slave port. However, phase synchronization works fine.
cq300244509 CDC2
In Tellabs 8630 smart router and Tellabs 8660 smart router, if CDC2 control
card(s) are installed, the command "boot system slot <slot#> flash: <filename>
restore-config..." is not working if the optional parameter "restore-config" is used.
Risk of occurrence: Always when CDC2 control card(s) are installed.
Workaround: Before ESW upgrade, use the command "snapshot-config create
flash:" to create configuration backup. If previous FP must be restored after ESW
upgrade, activate first previous ESW version without reloading the cards and use
the command "snapshot-config restore flash:" to restore previous configurations.
cq300244511 IFC2
In 1x10GBASE-R R2 IFM (LIO2257), with UP MEP configuration, EOAM ping
for multicast packet size 5800 and greater will not be successful and the MEP will
enter LoC state. Multicast EOAM ping of size upto 5700 is successful.
Impact: EOAM UP MEP will go down with LoC state.

134
cq300244527 CDC2, ELC1, CDC1

When the passive CDC control card is rebooted, Y.1731 Loss Measurement
counters may get too high values: existing counter values are incremented by
32-bit maximum value 4294967296. This issue happens on both UP and DOWN
MEP, and also when MEPs do not reside on same line card (ELC1).
Impact: Loss Measurement shows too high values.
Workaround: For Current-statistics, clear the statistics with CLI command “clear
eth cfm mp lm”, and for History-records, re-initiate the LM sessions (e.g. remove
and add LM Initiator config).
cq300244557 ELC1
SLI mode change between VLAN AC and trunk AC on the fly causes traffic cut
on the SLI.
Impact: Traffic-affecting.
Workaround: Performing shutdown/no shutdown operation on the interface is
required before traffic starts flowing again.
cq300244763 ELC1
Multicast replication due to flooding in VPLS network transient situations may
exceed the ELC1 with IRB forwarding performance of 10Mpps causing the unit
to reboot and traffic to be cut. Fourfold replication of unknown destination and
unicast traffic may exceed the 20Gbit/s bidirectional traffic limit with average
packet size of 250B.
Impact: ELC1 reboots due to overload and causes traffic cut.
Risk of occurrence: Always when the performance limit is exceeded.
Workaround: VPLS network design should use dual-homed spokes (MTU-s
Dual-Homing) and traffic balancing to minimize flooding caused by single node
failure, and avoid using ELC1 IRB with VPLS.
cq300244781 CDC1, CDC2, IFC1, IFC2, ELC1

A line card may spontaneously reset if 'show tech-support' command is executed
while the NE is doing configuration processing that modifies the data shown by
the command. The risk is increased during CDC switchover operation.
Impact: Traffic going via the resetting line card is cut until the card is up and
running again.
Workaround: Avoid using these commands during and right after a CDC
switchover.
cq300244782 CDC1, CDC2

Passive CDC reboots if the Maintenance Domain configurations are created or
modified in the following sequence:
Create a MD --> Manually Delete it --> Manually Reload Passive CDC -->
Re-create the MD --> Passive CDC resets spontaneously after a reboot.
Impact: Traffic is not impacted. Passive CDC reloads to get back in synch.
Risk of occurrence: Rare. Only when the particular sequence of configuration
and deletion and Passive CDC reload is attempted.
Workaround: Deletion of MD should not be done immediately after a create
operation. Wait for 5 - 10 seconds before deleting MD.

135
cq300244819 CDC2, ELC1

Reload of the passive CDC2 may rarely cause ELC1 IRB reconfiguration to occur
and a 200ms cut for part of the ELC1 IRB traffic.
Impact: 200ms traffic cut on ELC1 IRB.
cq300244894 CDC1
In network element boot-up with CDC1 units, with a configuration that exceeds
the recommended maximum scalability limits of the NE, the L2 configuration
of some flexible IRB interfaces may remain in shutdown state until manually
refreshed. This is due to IRB IF UP state transition message getting internally lost
because of message buffer overflow.
Impact: After NE boot-up, some of the IRB interfaces that should go to UP
state may remain partially down (L2 --> L3 direction) under the described
circumstances.
Risk of occurrence: Rare under the described circumstances. Not systematically
reproducible.
Workaround: IRB configuration refresh, for example IRB interface
shutdown/no-shutdown, CDC switchover.
Exceeding the documented maximum scalability limits is not recommended.
5.3 Rejected Bugs
The CRs listed in this chapter have previously been communicated as known bugs. They will not be
fixed in future software releases and will thus be considered and documented as features, restrictions
and limitations. Consequently they are removed from the list of known bugs.
cq300065174 CDC1, 8620 NE, IFC1
4xSTM-1/OC-3 ATM IFM (LIA2210) provides bidirectional wire-speed
throughput on all ports simultaneously for ATM pseudowires and ATM switching
when cell concatenation is used. In order to guarantee wire-speed throughput,
a proper network element synchronization has to be provided along with cell
concatenation. The number of cells that should be concatenated is dependent on
the configuration, for instance, a VPI pseudowire requires less cells compared to a
VCI pseudowire. Typically, seven to ten cells should be concatenated in order to
achieve bidirectional wire-speed on all ports. The cell concatenation timeout value
has an effect on the throughput. If the timeout value is small when compared to
the cell rate of an ATM circuit, the effective concatenation level is reduced due
to timeout expiration, which requires additional processing capacity relative to
case where a concatenated packet gets to be built without timer involvement.
Without cell concatenation, the bidirectional throughput is approximately 50%
of the 4-port STM-1 capacity. The throughput with VCG (Virtual Circuit Group)
configuration is less than that with pseudowires without VCG configuration. VCG
configuration is needed if n-to-1 (N>1) ATM pseudowires are used. In this case,
the throughput without cell concatenation is 48%, and the wire-speed throughput
is not achieved even with cell concatenation. Further, AAL5 services provide
wire-speed throughput for large enough packet sizes. For instance, IPoAAL5 is
wire-speed for IP packets larger than 140 bytes. It should be noted that if the
IFM is loaded with more traffic than its peak throughput, the throughput actually
decreases because part of the processing capacity is wasted for processing packets
that will be dropped due to the overload situation.

136
cq300067263 CDC1, IFC1

There is a short traffic break caused by IMA resynchronization with a line
protected 1xchSTM-1/chOC-3 Multiservice IFM (LIO2203) if the protection
switch is caused by cutting the receive or transmit signal, and if the far-end IMA
group is located behind of the far-end protection switch. In case of two Tellabs
8660 smart routers or Tellabs 8630 smart routers connected back-to-back, there is
no traffic break caused by IMA resynchronization.
cq300076120 IFC1, 8620 NE

An MLPPP bundle can contain up to 8 links for wire speed transmission. This
limitation is relevant with small packet sizes (less than 64 bytes). For a packet size
distribution with longer packets, the wire speed transmission is achieved with 16
links per bundle as well. The 1xchSTM-1/chOC-3 Multiservice IFM (LIO2203)
can handle 205 000 packets per second with MLPPP application. For instance,
with an IP packet size of 22 bytes, the line rate with MLPPP overhead is 56 Mbps.
With a packet size of 52 bytes, the line rate is 105 Mbps. With these maximum
line rates, the MLPPP traffic uses up the total throughput capacity of the interface.
With a packet size of 68 bytes, the wire speed transmission is achieved. If either
type of performance limitation described above is exceeded, the MLPPP bundle
in question will be reset. Therefore, if traffic is constantly transmitted so that
performance limits are exceeded, the bundle state goes to up and down sequence.
cq300100439 CDC1, IFC1

When a new software version is activated under mini-application, the card claims
sw version being wrong after boot-up.
Workaround: Activating the same sw versions again (outside mini-application)
fixes the situation.
cq300105589 IFC1
A failure in creating a PPP/MLPPP MSP group is not handled properly.
Risk of occurrence: Typically this problem occurs when a setting is written
into HW and that fails for some reason. Usually this causes the starting of the
protecting interface to fail and protection switching cannot be started. This is
shown as INIT state in the "show protection aps/ms/elp" CLI command.
cq300123110 IFC1, 8620 NE

Unframed HDLC, cHDLC and PPP in T1 interfaces should return the bandwidth
of 1544 kbps. The returned bandwidth is 1536 kbps.
cq300155753 IFC1
Protection group creation might fail if protection groups are created fast in a row
on a same card pair.
Impact: Not available.
Risk of occurrence: Failure is more probable if there is configuration on the
interface to be protected. There are no problems if the interface does not have
any configuration.
Workaround: In case the interface has configuration, wait a minute or two before
creating another protection group on the same card pair.

137
cq300157441 CDC1, IFC1, IFC2

When a hardware failure on an IFM module is detected in a MSP or APS protected
interface, traffic is correctly switched. If the active line card is rebooted before
the failed IFM is replaced, the traffic will not recover (the protection remains
in the INIT state).
Impact: Protection remains in the INIT state, manual actions are required to
recover the traffic.
Workaround: Replace a failed IFM immediately or remove the IFC card with a
failed IFM. Do not reload the other line card before the IFM is replaced or card
removed.
cq300158801 8620 NE
Autodiscovery of the Tellabs 8620 network element does not work fully.
Management interface attributes cannot be retrieved using the autodiscovery
mechanism.
Impact: Manual configuration is needed.
Workaround: Manual configuration.
cq300159947 CDC1, IFC1, IFC2, 8620 NE

In case the network element configuration (hw-inventory) is cleared by removing
and then adding all cards as preconfigured cards to it, there is the risk that some of
the configuration is not deleted. In the specific case of Tellabs 8660 smart router,
CDCs disagree with each other about the configuration.
Risk of occurrence: Always when there are over 100 IP interfaces.
Workaround: In the specific case of Tellabs 8660 smart router, first remove and
add all other cards except CDCs. Wait for several minutes (one minute per 100
interfaces) and then add the cards back. Do not reboot the network elements or
CDCs until all cards have been added and booted up.
cq300161671 IFC1, 8620 NE, CDC1

Error message "Operation failed!" in CLI is not descriptive when protection
removal is denied due to previous protection group operation (creation or removal)
that is still in processing.
Risk of occurrence: Always if new protection removal is started too soon. The
time depends on the configuration.
Workaround: Wait until the previous operation has been finished.
cq300161888 CDC1, 8620 NE, CDC2

An illegal, meaning for example, corrupted or incompatible ESW package (pkg
file) seems to be correct according both to the "show flash" CLI command and
Tellabs 8000 intelligent network manager, the ESW Management window in
Node Manager. The file is detected illegal only during activation, due to the fact
that an illegal file cannot be activated.
Risk of occurrence: Always when the ESW package file contents are illegal.
cq300162577 8620 NE, IFC1, IFC2

Changing the PPP/MLPPP WFQ configuration may need a reload to take effect.
Impact: Changing WFQ configuration may occasionally fail.
Workaround: Change WFQ configuration only when there is no user data traffic
or alternatively reboot the HW after the change.

138
cq300167030 IFC2
For incoming priority tagged traffic (VLAN ID equals 0), MPLS is not supported.
IP is supported.
Workaround: Also MPLS is supported when VLAN ID is other than 0.
cq300167701 IFC2
If the user copies the output of "show running configuration" from CLI and
later tries to configure a network element by pasting the copied lines to the CLI
prompt, Ethernet Link Aggregation groups (if there are any) are not configured
successfully.
Impact: If a running configuration that includes Ethernet Link Aggregation
groups is pasted to CLI, some error messages are printed ("Command failed: error
code 2109. Restriction: the interface has SSM transmission enabled." and "No
such LAG link available") and the groups are not configured as expected.
Workaround: If you have pasted a running configuration that contains Ethernet
Link Aggregation (LAG) groups, enter also the following commands, in this order:
1) for all links that are going to be LAG group members, go to interface
configuration mode (e.g. router(config)#interface ge2/0/0) and give the CLI
command "no send-ssm";
2) for all LAG groups, go to interface configuration mode (e.g.
router(config)#interface lag0) and use the CLI command "eth lag member" to join
the desired links to the group;
3) for all links that are LAG members, go to interface configuration mode and use
the CLI command "eth lag admin-status" to enable traffic on the member links.
cq300172669 CDC1, IFC1, IFC2, 8620 NE, CDC2

If card bootup fails e.g. due to a HW fault or missing SW files for FPGA circuits,
in some cases the card can be seen in "up and running" state in the hw-inventory.
If bootup fails, the hw-inventory state should be "sw init failed".
Impact: HW inventory gives the user the wrong impression of the network
element status.
Risk of occurrence: Rare. It depends on the location of the HW fault.
Workaround: Despite of the card state in the hw-inventory the appropriate HW
fault is reported correctly. The HW fault state can be checked using the CLI
command "show faults active fault-group hw".
cq300172909 CDC1
The CLI command "show environment fans" shows sometimes wrong "problem
has lasted" time, if one or more fans are broken.
Risk of occurrence: Cooling fan(s) must be broken. Most probably reload of
CDC and CDC switchover after that is needed.
cq300180723 8620 NE
MFE interface of Tellabs 8620 and Tellabs 8611 smart routers is software-based
and has simulated managed objects. The IP stack reserves interface indexes for
the software interfaces from a different value range than the hardware-based
interfaces. Therefore the mapping of the Tellabs 8000 intelligent network manager
index to the interface index is not supported.
Workaround: Use CLI commands to those operations that are not possible via
Tellabs 8000 intelligent network manager.

139
cq300187522 IFC2
VLAN packets are delayed by the shaper when the maximum rate is exceeded
and therefore cannot be served according to their arrival times by the scheduler.
This leads to non-deterministic scheduling between the shaped and non-delayed
packets from different flow queues of the same QoS class.
The non-delayed packets are always getting a proper scheduling and may pass by
delayed packets from other queues of the same QoS class.
Affected modules: 8x100/1000BASE-X R2 IFM (LIO2252) or
8x10/100/1000BASE-TX R2 IFM (LIE2256), and 1x10GBASE-R R2 IFM
(LIO2257).
Impact: QoS behavior of weighted queues (AFX,BE), when there is shaped and
non-shaped traffic in the same port.
cq300193498 IFC1, IFC2, 8620 NE

The CAC algorithm is leaking in the case of UBR+ if the MCR value is increased
gradually. In this configuration fashion the network element allows overbooking
the ATM interface.
Impact: The ATM interface may become overbooked unintentionally.
Risk of occurrence: Occurs typically.
Workaround: The MCR value of UBR+ circuit is not updated. Instead the circuit
is removed and re-created.
cq300194696 IFC2
Policing cannot be done correctly on MPLS traffic on 8x10/100/1000BASE-TX
R2 (LIE2256) and 8x100/1000BASE-X R2 (LIO2252) on IFC2.
Impact: It will affect the MLPS traffic.
Workaround: If the policing is critical, then an IFC1 based Ethernet IFM should
be used.
cq300195166 CDC1
When RSVP and LDP are both used on the same interface, CDC switchover may
cause a short data break.
Impact: A data break may occur on an interface when both RSVP and LDP are
used on that interface and a CDC switchover occurs. The length of the break
is roughly 1-7 milliseconds.
cq300195690 CDC1, 8620 NE, CDC2

Ping incorrectly accepts replies from a host whose source address differs from
the original destination.
cq300195767 IFC1, IFC2

Sometimes "hw-inventory add module" (when adding IFM) might fail and cause a
"SW INIT FAILED" state for the target card in the hw-inventory. This can happen
only if the previous "active type" of the IFM is "none" in the hw-inventory.
Risk of occurrence: Sometimes (depends of the IFM type), but only if the
previous active type of the IFM is "none" in the hw-inventory.
Workaround: Use "reload-sw slot <slot#>" for the problematic card to resume
normal operation.

140
cq300198913 IFC1, IFC2, 8620 NE

Synchronous Ethernet (SyncE) protection in a ring topology is not possible with
electrical Gigabit Ethernet interfaces (1000BASE-T). The Ethernet link must
work in slave mode for the NE to recover the clock, but additional SyncE links
must be kept in master mode. Now all SyncE links on the NE fallback list are
autonegotiated to slave mode.
Impact: Synchronous Ethernet cannot be link protected in case 1000BASE-T
ports are used.
cq300205100 IFC1
Ingress bandwidth allocation does not work efficiently if two (or more) traffic
sources are feeding the same module and the allocation for some ports is very small
while for others it is large. The source with low value allocation affects the higher
bandwidth allocated path when excessive amount of traffic is used in both sources.
8x1000BASE-X IFM (LIO2208) and 2+6x10/100/1000BASE-COMBO
IFM (LIC2231) are certainly affected; 2x1000BASE-X IFM (LIO2019) and
8x100BASE-X IFM (LIO2028) most likely are not affected.
Impact: The throughput of the higher bandwidth interface is reduced.
Risk of occurrence: Always when bandwidth allocation has both very small and
large values, and the low bandwidth port capacity is exceeded a lot.
Workaround: -Allocate more bandwidth to low bandwidth interfaces (100 is
recommended).
-Limit the bandwidth of the low bandwidth interfaces somewhere upstream.
PPN 173
cq300208501 IFC2
VLAN policing is not supported in IFC2 in FP3.1 or higher.
Impact: VLAN policing is not supported in PWE3 attachment circuit (i.e. end
point) in IFC2 based Ethernet interface modules.
Workaround: Use IFC1 based Ethernet interface modules where VLAN policing
works for PWE3.

When the hw-inventory is created ("hw-inventory add-all-units") or a new card
is added in the inventory ("hw-inventory add unit"), ESW does not check the
compatibility of the IFMs/LMs/HMs in the target card(s). This might cause
ESW init to fail in the target card(s) after the operation if the IFM/LM/HM is not
supported by the target card or if the combination of IFMs/LMs/HMs is illegal.
Workaround: Remove illegal HW configuration from the inventory
("hw-inventory remove unit") and remove illegal HW from the NE. Execute CLI
command "hw-inventory add-all-units" or "hw-inventory add unit" again with
legal HW configuration.
cq300208900 IFC2
VLAN Ethernet pseudowire does not collect statistics at ingress direction due to
a limitation.
Impact: It is not possible to collect VLAN Ethernet pseudowire statistics at
ingress direction.
Risk of occurrence: Often.

141
cq300216705 IFC1, IFC2

Synchronous Ethernet SSMs are forwarded in case the SSMs are received on a
port that is an endpoint of an internal Ethernet pseudowire. Consequently, the
node clock disqualifies the synchronous Ethernet source and stays in freerun in
case there are no other clock sources available. This issue does NOT exist on
R2 Ethernet IFMs.
Impact: The next hop network element receives the forwarded quality
level information and may lock to the freerunning clock source causing a
synchronization failure.
Workaround: Disable quality levels or overwrite Ethernet port quality level from
the network element with the internal Ethernet pseudowire.
cq300224854 IFC2
The interfaces of 8x100/1000BASE-X R2 IFM (LIO2252) and
8x10/100/1000BASE-TX R2 IFM (LIE2256) accept pause frames only with the
length of 64 bytes. Longer pause frames are ignored.
Impact: 8x100/1000BASE-X R2 IFM (LIO2252) and 8x10/100/1000BASE-TX
R2 IFM (LIE2256) do not process pause frames correctly. Egress traffic is not
halted if a received pause frame is longer than 64 bytes.
cq300225998 CDC2, CDC1

Some SSM quality levels are received wrong from SCI T1 (ANSI) mode.
These wrongly received quality levels are in Tellabs 8609 smart router and Tellabs
8611 smart router:
QL-TNC (0100) ( received QL is QL-PRS)
QL-SMC(1100) ( received QL is QL-DUS)
QL-ST3E(1101) ( received QL is QL-STU)
QL-PROV(1110) ( received QL is QL-DUS)
And in Tellabs 8660 smart router wrongly received quality levels are:
QL-SMC(1100) ( received QL is QL-DUS)
Impact: Some quality levels cannot be used reliably.
Risk of occurrence: This will occur every time when SSM listed above quality
levels are used in nodes listed above. Occurs only in ANSI mode.
Workaround: Use only working quality levels.
cq300226020 IFC2
In a LAG VLAN interface the statistics counter "Discarded Vlan frames" does not
increment at all. For example:
router#show interface lag 0.32
Interface lag0.32 (vlan)
Discarded Vlan frames: 0
cq300226346 ELC1
When changing the interface IP MTU in shutdown state, an error message is
shown. The error message is:
FP4.0:NPXD ERROR: UNIV_EGR: "entryFound" failed at NpxdFpi_Univer-
salChangeMtu() npxd_fpi_univ_egress.c.
Impact: There is no traffic cut and no effect to the normal operation.

142
cq300227935 CDC1
IS-IS does not work on IRB VLANs when VLAN trunk mode attachment circuits
are used for that particular IRB.
Impact: IS-IS does not work under the described circumstances. In that case
routes are not distributed by IS-IS.
cq300228872 IFC2
IFC2 does not allow IPv4 traffic, if there is excessive padding in Ethernet frame
after the IPv4 datagram, i.e. Ethernet frame is longer than 64 bytes but IPv4
Total Length indicates some bytes after the IPv4 datagram are not part of the
IPv4 payload.
Impact: Excessively padded IPv4 datagrams are not forwarded.
Risk of occurrence: Always when IPv4 datagram is excessively padded in
Ethernet frame.
Workaround: Configure the transmitting node to not add excess padding
to Ethernet frames after IPv4 datagrams. This consumes link bandwidth
unneccessarily. If the transmitting device does not support such functionality,
please contact Tellabs customer service for workaround.
cq300228904 IFC2
The deletion of LAG port can cause timeout via Tellabs 8000 intelligent network
manager. The situation will eventually correct itself and the command will
function as expected.
Impact: Timeout is seen on Tellabs 8000 intelligent network manager and this
results in an inconsistency between Tellabs 8000 intelligent network manager and
the NE, that is, LAG exists in Tellabs 8000 intelligent network manager database
but not in the NE.
cq300235153 IFC1
When replacing an old Ethernet IFM by a new Ethernet IFM, e.g., replacing
8x10/100BASE-TX (LIE2018) with 2+6x10/100/1000BASE-COMBO IFM
(LIC2231), the old interface module's interfaces are displayed before performing
any inventory operations.
Impact: If any of the affected ports are involved in sending traffic, there will
be traffic loss.
Risk of occurrence: Always for all Ethernet to Ethernet IFMs.
Workaround: Before physically removing the interface module from the network
element, perform the remove module inventory operation.
cq300235550 IFC1, IFC2

When adaptive packet timing (ACR) is active on an E1/T1 port of a 24xchE1/chT1
Multiservice IFM (LIE2226) on Tellabs 8660 smart router and the adaptive jitter
buffer (AJB) is activated on the same port, a long SAToP pseudowire loss may
cause a re-convergence of the clock recovery of the respective E1/T1 egress
timing. Consequently the phase of the recovered clock may exceed the applicable
G.823 MTIE masks. However, the fault does not occur if the adaptive jitter buffer
of the respective port is not in use. Because the adaptive jitter buffer is beneficial
only in connections where the SAToP packets meet unexceptionally high packet
delay variation, disabling the AJB is a workaround in most cases.
Workaround: Disable the adaptive jitter buffer (use normal jitter buffer) on ports
using adaptive packet timing.

143
cq300236684 CDC1
RSVP tunnels may start flapping if the configuration is too large. This may happen
if there are more than 2000 RSVP tunnels configured in Tellabs 8630 smart router
and Tellabs 8660 smart router. The CDC1 unit can get overloaded and it is unable
to keep all the RSVP tunnels up.
Impact: Flapping RSVP tunnels are not able to carry traffic reliably.
Risk of occurrence: When more than 2000 RSVP tunnels are configured in
Workaround: Reduce the number of RSVP tunnels in Tellabs 8630 smart router
and Tellabs 8660 smart router. Also, RSVP path refresh reduction can be tried to
reduce the risk of occurrence when large number of RSVP tunnels are created in
cq300236932 IFC1, 8620 NE, IFC2

The electrical SFP interface line state is always up, even though the Ethernet link
is down or the cable has been unplugged, if auto-negotiation is disabled.
Impact: Link state detection does not work for electrical SFP interface.
Workaround: Enable auto-negotiation for the interface.
cq300237046 IFC1, IFC2, 8620 NE

Adaptive timing (ACR) and adaptive jitter buffer (AJB) cannot be used
concurrently.
Impact: Concurrent use of AJB and ACR will cause synchronization failure on
the device connected to the port having this configuration (assuming that this port
was the primary source for synchronization).
cq300237308 IFC2
In 8x10/100/1000BASE-TX R2 IFM, in all Gigabit Ethernet interfaces of Tellabs
8609 smart router and Tellabs 8611 smart router, and in LAG interfaces in Tellabs
8609 smart router and Tellabs 8611 smart router having GE interfaces as members,
when "no loopback to-equipment" is configured, the link state goes down for a
few seconds and then comes up.
Impact: For a few seconds following the removal of loopback, the link is down,
i.e., link down fault is reported and the link cannot transmit traffic.
cq300238669 IFC2
Only two IRB MAC values are supported per IFM. Since the default IRB MAC is
used on any VSI with SLIs on the IFM, then only one IRB MAC can be configured
on any other VSI having SLIs on that IFM.
Impact: Configuring more than one MAC address will cause alarm and
configuration is not working %2013-09-04 09:05:43Z %ALERT: slot 7:
MEASURE: HW Resource 7/1: Fault ON, Critical, Processing error, Red led: Irb
MAC addresses usage overflow

144
cq300239166 CDC2
When the existing CDC2 card in any slot in passive mode is replaced with another
CDC2, and now it is made active by manual switchover, the active MFE mac
address is returning as 0000.0000.0000 and ping fails.
Impact: If MAC address is 0000.0000.0000, it will affect the management traffic.
Workaround: Rebooting the node will solve the issue.
cq300239282 ELC1, IFC1, IFC2

The passive interface of an Ethernet Link Protection (ELP) group cannot send
SSM messages. This causes the receiving interface to be declared as Do Not Use
for synchronization and hence it is never selected as a clock source, if quality
levels are used.
Impact: Network element synchronization is lost, if there are no other interfaces
in the network element fallback list.
Workaround: Use synchronization without quality levels.

145

Tellabs 8600 Smart Routers FP4.1 Embedded Software Release Notes

Uploaded by

Document Information

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 8600 Smart Routers FP4.1 Embedded Software Release Notes

Uploaded by

Copyright:

Available Formats

Tellabs ® 8600 Smart Routers FP4.

Document Date Description of Changes

Tellabs ® 8600 Smart Routers FP4.1 76.8641-50156E

Document Date Description of Changes

Tellabs ® 8600 Smart Routers FP4.1 76.8641-50156E

© 2014 Tellabs. All rights reserved.

76.8641-50156E Tellabs ® 8600 Smart Routers FP4.1

Terms and Abbreviations

76.8641-50156E Tellabs ® 8600 Smart Routers FP4.1

ICMP Internet Control Message Protocol

Tellabs ® 8600 Smart Routers FP4.1 76.8641-50156E

76.8641-50156E Tellabs ® 8600 Smart Routers FP4.1

About This Manual ............................................................................................................ 13

Tellabs 8600 Rebranding .................................................................................................. 17

Tellabs 8600 Discontinued Products............................................................................... 18

Tellabs 8600 Discontinued Features ............................................................................... 19

1 Embedded Software Interrelation Tables.................................................................. 20

2 Installation Notes ........................................................................................................ 32

2.1 Supported Upgrade Paths .................................................................................................................................... 32

76.8641-50156E Tellabs ® 8600 Smart Routers FP4.1

4.1 Overview ............................................................................................................................................................. 49

5 Known Restrictions and Bugs ................................................................................. 109

5.1 Restrictions ........................................................................................................................................................ 109

Tellabs ® 8600 Smart Routers FP4.1 76.8641-50156E

About This Manual

• 8620: SBZ2714 Application Software

76.8641-50156E Tellabs ® 8600 Smart Routers FP4.1

Tellabs 8600 Smart Routers Technical Documentation

Document Title Description

• Tellabs ® 8607 Smart Router FP1.1 Embedded Software Re-

• Tellabs ® 8609 Smart Router and Tellabs ® 8611 Smart Router

Tellabs ® 8600 Smart Routers FP4.1 76.8641-50156E

Document Title Description

76.8641-50156E Tellabs ® 8600 Smart Routers FP4.1

Document Title Description

Tellabs ® 8600 Smart Routers FP4.1 76.8641-50156E

Tellabs 8600 Rebranding

Previous Product Name New Product Name

76.8641-50156E Tellabs ® 8600 Smart Routers FP4.1

Tellabs 8600 Discontinued Products

Tellabs 8600 Discontinued Products

Tellabs ® 8600 Smart Routers FP4.1 76.8641-50156E

Tellabs 8600 Discontinued Features

Tellabs 8600 Discontinued Features

76.8641-50156E Tellabs ® 8600 Smart Routers FP4.1

1 Embedded Software Interrelation Tables

• Tellabs 8620 smart router

The following conventions are used in the release notes.

Version number A specific ESW version is required.

Tellabs ® 8600 Smart Routers FP4.1 76.8641-50156E

The meaning of different columns and notations are described below.

Baseboard Baseboard where the ESW is downloaded.

76.8641-50156E Tellabs ® 8600 Smart Routers FP4.1

Embedded Software Release Notes

1 Embedded Software Interrelation Tables

SBB2030 1.0 or higher SBZ2714 4.1.586 (SP1) GA SR5.0 or higher 401.2

1 Embedded Software Interrelation Tables

Embedded Software Release Notes

1 Embedded Software Interrelation Tables

1 Embedded Software Interrelation Tables

Embedded Software Release Notes

1 Embedded Software Interrelation Tables

1 Embedded Software Interrelation Tables