0% found this document useful (0 votes)

352 views129 pages

76 8660-50169C PDF

Uploaded by

Mauro Guaño

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

352 views129 pages

76 8660-50169C PDF

Uploaded by

Mauro Guaño

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 129

8600 Smart Routers SR6.

0
Embedded Software Release Notes

76.8660-50169C
10.11.2014
Document Information

Revision History

Document Date Description of Changes

No.
76.8660- 10.11.2014 New application software version for SR6.0 SP1 GA in chapter
50169C 12.1 Version SR6.0 SP1 GA (Application SW Version .308).
Rows for 8602-D variant added in 1.2 8602 Smart Router
Applications Software Compatibility Matrix.
The tables in ch. 2 Supported Upgrade Paths updated.
Chapters 5.1 Upgrade Related Notifications for 8609 Smart Router
and 8611 Smart Router and 5.2 Upgrade Related Notifications for
8630 Smart Router and 8660 Smart Router updated.
Removed the notes stating that non-service affecting upgrade is
NOT supported for any 8600 Smart Routers at SR6.0 CIR2 in ch.
7 Non-Service Affecting Software Upgrade.
Note regarding automatic reboot added in ch. 8.1 Upgrading CDC1
to CDC2.
The following restrictions removed from ch. 13 Restrictions in 8600
Smart Routers SR6.0:
• Restriction about Synchronous Ethernet capable SFP
(81.86T-SM3TX02R-R6) being restricted to lab use only at
SR6.0 CIR
• “8615 Smart Router does not fully support the packet loop testing
(PLT) functionality in the SR6.0 CIR release, and its use is not
recommended. (CR ID cq300248824)”
• “The amount of L2 IEEE1588 capable ports is limited to 14.
Supported ports are xe13/0/0...1 and ge13/1/0...11. (CR ID
cq300246841)”
• “Synchronization quality levels (SSM messages) are not sup-
ported on 8615 Smart Router SCI port when the network element
is in ANSI operating mode.”
• "Link Aggregation Control Protocol (LACP) is not supported.".
The following restrictions removed from ch. 14 Restrictions in
Releases Prior to 8600 Smart Routers SR6.0:
• “DHCP relay functionality” (for 8602 FP1.0)
• "Link Aggregation Control Protocol (LACP) is not supported."
• “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.”.
Added as known bugs since previous SR6.0 CIR2 ESW Release
Notes: cq300247919, cq300248359, cq300249103, cq300249839,
cq300249881, cq300249899, cq300249944, cq300250316,
cq300250457, cq300250667, cq300250669, cq300250763,
cq300250766, cq300250802, cq300250940, cq300251033,
cq300251035, cq300251083, cq300251100.
Ch. 16 Rejected Bugs added.
76.8660- 21.10.2014 New application software version .244 for SR6.0 CIR2 in chapter
50169B 12 Application Software.
Upgrade paths for 8609 Smart Router and 8611 Smart Router updated
in ch. 2 Supported Upgrade Paths.
Warning added to ch. 5.1 Upgrade Related Notifications for 8609
Smart Router and 8611 Smart Router.
BGP labeled unicast (S-MPLS) related restrictions edited in ch.
13.1 Common Restrictions in SR6.0. (Continued on the next page)

8600 Smart Routers SR6.0 76.8660-50169C

2
Document Date Description of Changes
No.
76.8660- 21.10.2014 (Continued)
50169B The following restrictions removed from ch. 13 Restrictions in 8600
Smart Routers SR6.0:
• “8615 Smart Router and ELC1 packet storm detection and
isolation feature (feature IDs F00508 and F00283) is not
supported in 8600 Smart Routers SR6.0 CIR. (CR IDs
cq300248899 and cq300248892.)”
• “When jumbo frames larger than 3000 Bytes need to be for-
warded, a maximum of 12 ports of GE can be used. (CR ID
cq300248295)”.
The following restrictions removed from ch. 14 Restrictions in
Releases Prior to 8600 Smart Routers SR6.0, as they are discussed
elsewhere in 8600 Smart Routers SR6.0 customer documentation:
• “In MSP/APS protected configurations, VCG should not be
configured if the IFC of the primary interface of VCG is not
present.”
• “If an interface of 8602 Smart Router is configured to a fixed line
speed and duplexity (with e.g. CLI command 'mode speed 100
duplex full') and connected to an interface that is auto-negotiat-
ing, the line status goes down. For the line status to go up, the in-
terfaces at both ends of the line must be configured to fixed speed
and duplexity, or they must both be configured to auto-negotiate.
(cq300241104)”
• ETHoATM restrictions
• “PWE3 redundancy should not be used in ANSI mode.”.
Added as known bugs since previous SR6.0 CIR ESW Release
Notes: cq300230282, cq300231048, cq300244423, cq300245824,
cq300248248, cq300248466, cq300249465, cq300249524,
cq300249985, cq300250023, cq300250041, cq300250052,
cq300250135, cq300250205, cq300250224, cq300250273,
cq300250430, cq300250436, cq300250579, cq300250604.
76.8660- 28.08.2014 Initial version of the document for 8600 Smart Routers SR6.0 CIR.
50169A
This revision of the manual documents the following network elements and the corresponding
feature pack.

8602 Smart Router FP1.1

8609 Smart Router, 8611 Smart Router FP2.0
8615 Smart Router FP1.0
8630 Smart Router, 8660 Smart Router FP5.0

If a different feature pack of 8600 products is in use, please refer to the relevant product document
program on the Tellabs and Coriant Portal by navigating to www.portal.tellabs.com > Product
Documentation & Software > Data Networking > Tellabs 8600 Smart Routers > Technical
Documentation.

© 2014 Coriant. All rights reserved.

This manual is protected by U.S. and international copyright laws, conventions and treaties. Your right to use this manual is
subject to limitations and restrictions imposed by applicable licenses and copyright laws. Unauthorized reproduction, modification,
distribution, display or other use of this manual may result in criminal and civil penalties.

The specifications and information regarding the products in this manual are subject to change without notice. All statements,
information, and recommendations in this manual are believed to be accurate but are presented without warranty of any kind,
express or implied. Users must take full responsibility for their application of any products.

Adobe ® Reader ® are registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Unless otherwise agreed in a written document, the software in the product is licensed under the license terms
found at http://coriant.com/legal/documents/coriant_tandc_global_deliverables.pdf and
http://coriant.com/legal/documents/tellabs_product_specific_tandc.pdf.

8600 Smart Routers SR6.0 76.8660-50169C

4
Document Information

Terms and Abbreviations

Term Explanation
AC Attachment Circuit
APS Automatic Protection Switching
ATM Asynchronous Transfer Mode
BFD Bidirectional Forwarding Detection
BGP Border Gateway Protocol
BMI Broadband Management Interface of 8000 Intelligent Network Manager
BMP Broadband Management Protocol. The communication protocol which is used
between the 8600 network elements and 8000 Intelligent Network Manager.
CDC Control and DC Power Card (used in 8630 Smart Router and 8660 Smart Router)
CIR Controlled Introduction Ready
CLI Command Line Interface
Control card The term ‘control card’ in the 8600 system refers to a Control and DC Power Card
CDC (used in 8630 Smart Router and 8660 Smart Router), Switching and Control
Module SCM (used in 8611 Smart Router), or Virtual Control Unit CU (used in 8615
Smart Router). In 8000 Intelligent Network Manager and CLI referred to as unit.
CU Virtual Control Unit (used in 8615 Smart Router)
DM Delay Measurement
ELC1 Ethernet Line Card (used in 8630 Smart Router and 8660 Smart Router)
ELP Ethernet Link Protection
ESW Embedded Software
Fan One fan in a fan module
Fan Module A module consisting of two or more fans, the mechanics and possibly the control
electronics. 8609 Smart Router fan module: five fans per module. 8611 Smart Router
fan module: ten fans per module.
FE Fast Ethernet
FP Feature Pack
FRR Fast Reroute
FTP File Transfer Protocol
GA General Availability
GE Gigabit Ethernet
HM High Speed Module (used in 8611 Smart Router)
HW Hardware
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 8630 Smart Router and 8660 Smart Router).

76.8660-50169C 8600 Smart Routers SR6.0

5
Document Information

IFM Interface Module. A specific term of the module which can be placed on the IFC line
card or 8620 Smart Router baseboard and which consists of the physical interfaces
(used in 8620 Smart Router, 8630 Smart Router and 8660 Smart Router).
IP Internet Protocol
IPv4 Internet Protocol version 4
IRB Integrated Routing and Bridging
IS-IS Intermediate System to Intermediate System (Interior Gateway Protocol)
LAG Ethernet Link Aggregation
LPD Label Distribution Protocol (MPLS)
Line card The term ‘line card’ in the 8600 system refers to an Ethernet Line Card (ELC1),
Interface Module Concentrator (IFC) and up to two Interface Modules (IFMs) (used
in 8630 Smart Router and 8660 Smart Router), or Virtual Line Unit LU (used in 8615
Smart Router). In 8000 Intelligent Network Manager and CLI referred to as unit.
LM Line Module
LM Loss Measurement
LSP Label Switched Path
LU Virtual Line Unit (used in 8615 Smart Router)
MAC Media Access Control Sublayer of Data Link Layer
MEP Maintenance Endpoint
MFE Management Fast Ethernet
MIB Management Information Base (SNMP)
MLPPP Multi-Link PPP
MO Mobile Optimization (Interface Module)
MPLS Multiprotocol Label Switching
MPLS-TP Multiprotocol Label Switching Transport Profile
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 8611 Smart
NE Router, 8630 Smart Router and 8660 Smart Router.
NE Network Element
OAM Operation, Administration and Maintenance
OSPF Open Shortest Path First
OSPF-TE Open Shortest Path First with Traffic Engineering Extension
Physical line Refers to both the line modules (LMs) in 8609 Smart Router and 8611 Smart Router
module and the high speed modules (HMs) in 8611 Smart Router.
PKG Software package file
POS Packet over SDH/Sonet
PPN Product Performance Notice

8600 Smart Routers SR6.0 76.8660-50169C

6
Document Information

PPP Point-to Point Protocol

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.
PTP Precision Time Protocol
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
RSVP-TE Resource Reservation Protocol with Traffic Engineering Extensions
SAToP Structure-Agnostic Time Division Multiplexing over Packet
SCM Switching and Control Module (used in 8611 Smart Router)
SFP Small Form-Factor Pluggable. A transceiver type used in 8600 IFMs, HMs, LMs
and network elements.
SFTP Secure File Transfer Protocol
Single-card Network element whose hw-inventory contains only one slot. Refers to 8602 Smart
NE Router, 8605 Smart Router, 8607 Smart Router, 8609 Smart Router, 8615 Smart
Router and 8620 Smart Router.
SNMP Simple Network Management Protocol
SSH Secure Shell
SW Software
TDM Time Division Multiplexing
VCG Virtual Circuit Group
VLAN Virtual Local Area Network
VPN Virtual Private Network
VRF VPN Routing and Forwarding
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 8660 Smart Router the interface residing on the right-hand side
IFC, in case of 8620 Smart Router the right-hand side interface on the IFMs, and in
case of 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.

76.8660-50169C 8600 Smart Routers SR6.0

7
8600 Smart Routers SR6.0 76.8660-50169C
Embedded Software Release Notes © 2014 Coriant.

8
Table of Contents

Table of Contents

About This Manual ............................................................................................................ 12

Objectives....................................................................................................................................................................... 12
Audience......................................................................................................................................................................... 12
8600 Smart Routers Technical Documentation.............................................................................................................. 13

8600 Smart Routers Discontinued Products .................................................................. 16

1 Embedded Software Interrelation Tables.................................................................. 17

1.1 8600 Boot and Mini-Applications Software........................................................................................................ 18

1.2 8602 Smart Router Applications Software Compatibility Matrix....................................................................... 24
1.3 8609 Smart Router and 8611 Smart Router Applications Software Compatibility Matrix................................. 24
1.4 8615 Smart Router Applications Software Compatibility Matrix....................................................................... 27
1.5 8630 Smart Router and 8660 Smart Router Applications Software Compatibility Matrix................................. 29

2 Supported Upgrade Paths .......................................................................................... 35

3 Software Upgrade Order............................................................................................. 37

4 Operations Before Upgrade ....................................................................................... 38

4.1 Operations Before Upgrading 8602 Smart Router and 8609 Smart Router ....................................................... 38
4.2 Operations Before Upgrading 8611 Smart Router .............................................................................................. 39
4.3 Operations Before Upgrading 8615 Smart Router .............................................................................................. 40
4.4 Operations Before Upgrading 8630 Smart Router and 8660 Smart Router ........................................................ 41

5 Upgrade Related Notifications ................................................................................... 43

5.1 Upgrade Related Notifications for 8609 Smart Router and 8611 Smart Router ................................................. 43
5.1.1 Recommended Procedure for Upgrading to 8609 Smart Router and 8611 Smart Router FP1.3 SP1.. 43
5.2 Upgrade Related Notifications for 8630 Smart Router and 8660 Smart Router ................................................. 43

76.8660-50169C 8600 Smart Routers SR6.0

9
Table of Contents

5.2.1 Notification Regarding ELC1 ESW Upgrade to 8630 Smart Router and 8660 Smart Router FP4.1
SP1....................................................................................................................................................... 44

6 Service Affecting Software Upgrade of the Whole NE............................................. 45

6.1 8611 Smart Router Service Affecting Hardware and Software Upgrade of the Whole NE................................ 47

7 Non-Service Affecting Software Upgrade ................................................................. 49

7.1 8611 Smart Router Non-Service Affecting Software Upgrade ........................................................................... 49

7.2 8630 Smart Router and 8660 Smart Router Non-Service Affecting Software Upgrade.................................... 50

8 Upgrading Cards ......................................................................................................... 54

8.1 Upgrading CDC1 to CDC2.................................................................................................................................. 54

8.2 IFC1 to IFC2 Upgrade......................................................................................................................................... 56
8.2.1 Service Affecting Upgrade of IFC1 to IFC2 ....................................................................................... 58
8.2.2 Non-Service Affecting Upgrade of IFC1 to IFC2 ............................................................................... 59

9 ESW Upgrade with Downgrade Support for 8602 Smart Router and 8615 Smart
Router........................................................................................................................... 60

10 Restoring Previous FP and Configuration in Case of Upgrade Failure ................. 62

10.1 Restoring Previous FP and Configuration in Case of Upgrade Failure in 8602 Smart Router and 8609 Smart
Router .................................................................................................................................................................. 62
10.2 Restoring Previous FP and Configuration in Case of Upgrade Failure in 8611 Smart Router, 8615 Smart Router,
8630 Smart Router and 8660 Smart Router......................................................................................................... 63

11 SR6.0 Features ............................................................................................................ 65

12 Application Software................................................................................................... 67

12.1 Version SR6.0 SP1 GA (Application SW Version .308) ..................................................................................... 67

12.1.1 Enhancements in SR6.0 SP1 GA......................................................................................................... 69
12.1.2 Fixed Bugs in SR6.0 SP1 GA.............................................................................................................. 69
12.2 Version SR6.0 CIR2 (Application SW Version .244).......................................................................................... 72
12.2.1 Enhancements in SR6.0 CIR2 ............................................................................................................. 72
12.2.2 Fixed Bugs in SR6.0 CIR2 .................................................................................................................. 73
12.3 Version SR6.0 CIR (Application SW Version .103)............................................................................................ 84

8600 Smart Routers SR6.0 76.8660-50169C

10
Table of Contents

12.3.1 Enhancements in SR6.0 CIR ............................................................................................................... 84

12.3.2 Fixed Bugs in SR6.0 CIR .................................................................................................................... 84

13 Restrictions in 8600 Smart Routers SR6.0................................................................ 96

13.1 Common Restrictions in SR6.0 ........................................................................................................................... 96

13.2 8602 Smart Router FP1.1 Specific Restrictions .................................................................................................. 98
13.3 8609 Smart Router and 8611 Smart Router FP2.0 Specific Restrictions ............................................................ 99
13.4 8615 Smart Router FP1.0 Specific Restrictions .................................................................................................. 99
13.5 8630 Smart Router and 8660 Smart Router FP5.0 Specific Restrictions ............................................................ 99

14 Restrictions in Releases Prior to 8600 Smart Routers SR6.0 ............................... 100

14.1 Common Restrictions ........................................................................................................................................ 100

14.2 8602 Smart Router Specific Restrictions........................................................................................................... 101
14.3 8609 Smart Router and 8611 Smart Router Specific Restrictions..................................................................... 101
14.4 8630 Smart Router and 8660 Smart Router Specific Restrictions.................................................................... 102

15 Known Bugs .............................................................................................................. 103

16 Rejected Bugs ........................................................................................................... 120

76.8660-50169C 8600 Smart Routers SR6.0

11
About This Manual

About This Manual

This chapter discusses the objectives and intended audience of this manual, 8600 Smart Routers
Embedded Software Release Notes.

Objectives

This manual consists of the embedded software of 8600 Smart Routers. At the beginning of the
manual you can find the embedded software interrelation tables for:

• boot software and mini-applications

• network elements
• interface modules
The ESW of 8600 Smart Routers 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 7 Non-Service Affecting Software Upgrade.

Features introduced in 8600 Smart Routers SR6.0 are listed in chapter 11 SR6.0 Features.

Chapter 12 Application Software describes the enhancements and fixed bugs in the following
application software:

• 8602: SBZ2755 Application Software

• 8609: SBZ2751 Application Software
• 8611: SBZ2748 Application Software
• 8615: CBZ2764 and LBZ2765 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 are listed in chapters 13 Restrictions in 8600 Smart Routers SR6.0 and
14 Restrictions in Releases Prior to 8600 Smart Routers SR6.0.

Chapter 15 Known Bugs lists the open issues in 8600 Smart Routers SR6.0 SP1 GA, and ch.
16 Rejected Bugs those CRs that will remain as permanent limitations and restrictions in the 8600
Smart Routers.

Audience

This manual is designed for 8600 network element installation personnel and system specialists
when planning or maintaining the network, updating software or installing network elements.

8600 Smart Routers SR6.0 76.8660-50169C

12
About This Manual

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
and Coriant Portal by navigating to www.portal.tellabs.com > Product Documentation & Software
> Data Networking > 8600 Smart Routers > Technical Documentation.

Document Title Description

8600 Smart Routers Provides an overview of 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 tunnelling,
Traffic Management, Fault Management OAM, protection and
TDM applications as well as instructions on how to configure
them with CLI.
8600 Smart Routers Provides information related to the boot and mini-applications
Boot and Mini-Applications software of 8605 Smart Router, 8607 Smart Router, 8609
Embedded Software Release Notes Smart Router, 8611 Smart Router, 8620 Smart Router, 8630
(76.8600-50108) Smart Router and 8660 Smart Router as well as the installation
instructions.
8600 Smart Routers Provides commands available to configure, monitor and maintain
CLI Commands Manual 8600 system with CLI.
(76.8600-50117)
8600 Smart Routers Consists of the embedded software release notes of the 8600 NEs.
Embedded Software Release Notes • 8600 Smart Routers SR6.0 Embedded Software Release
Notes (76.8660-50169) for the following:
- 8602 Smart Router FP1.1
- 8609 Smart Router and 8611 Smart Router FP2.0
- 8615 Smart Router FP1.0
- 8630 Smart Router and 8660 Smart Router FP5.0
8600 Smart Routers Provides an overview of 8600 system HW inventory, software
Equipment Management management, equipment protection 1+1 (CDC and SCM) as well
Configuration Guide as instructions on how to configure them with CLI.
(76.8600-50118)
8600 Smart Routers Provides an overview of 8600 system Ethernet applications,
Ethernet Configuration Guide (76. including interfaces; Ethernet forwarding (MAC Switching,
8600-50133) Ethernet PWE3, IRB, VLAN, VPLS); Ethernet OAM; LAG;
ELP as well as instructions on how to configure them with CLI.
8600 Smart Routers Provides an overview of 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.
8600 Smart Routers Provides an overview of 8600 system Frame Relay applications,
Frame Relay Configuration Guide including interfaces; Performance Monitoring; protection; Traffic
(76.8600-50120) Management as well as instructions on how to configure them
with CLI.
8600 Smart Routers Provides guidance on mechanical installation, cooling,
Hardware Installation Guide grounding, powering, cabling, maintenance, commissioning and
(76.8600-40039) ESW downloading.

76.8660-50169C 8600 Smart Routers SR6.0

13
About This Manual

Document Title Description

8600 Smart Routers Consists of the hardware release notes of the network element
Hardware Release Notes components in 8605 Smart Router, 8607 Smart Router, 8609
(76.8600-40027) Smart Router, 8611 Smart Router, 8615 Smart Router, 8620
Smart Router, 8630 Smart Router and 8660 Smart Router
8600 Smart Routers The Interface Configuration Guides provide an overview of the
Interface Configuration Guides 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:
• 8600 Smart Routers Network Interfaces Configuration
Guide (76.8600-50161) (for 8602 Smart Router and 8615
Smart Router)
• 8609 Smart Router and 8611 Smart Router FP2.0 Interface
Configuration Guide (76.8660-50171)
• 8600 Smart Routers FP5.0 Interface Configuration Guide
(76.8660-50170) (for 8630 Smart Router and 8660 Smart
Router)
8600 Smart Routers Provides an overview of 8600 system IP, forwarding and traffic
IP Forwarding and Traffic management functionality, including: IP addressing; IP hosting
Management Configuration Guide (ARP, DHCP); IP routing (static); ACL; Differentiated Services
(76.8600-50122) (Policing, Queue Management, Shaping) as well as instructions
on how to configure them with CLI.
8600 Smart Routers Provides an overview of 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.
8600 Smart Routers Provides an overview of 8600 system Mobile Optimization
Mobile Optimization Configuration applications as well as instructions on how to configure them
Guide (76.8600-50100) with CLI.
8600 Smart Routers Provides an overview of 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), S-MPLS applications as well
as instructions on how to configure them with CLI.
8600 Smart Routers Provides an overview of 8600 system supported performance
Performance Counters Reference counters.
Guide (76.8600-50143)

8600 Smart Routers SR6.0 76.8660-50169C

14
About This Manual

Document Title Description

8600 Smart Routers The reference manuals describe the 8600 network element
Reference Manuals features including:
• NE enclosure, baseboard, power supply modules, and
interfaces in 8602 Smart Router FP1.1 Reference Manual
(76.8660-40120)
• NE enclosure, baseboard, power supply modules, interfaces
and physical LM types in 8609 Smart Router FP2.0 Refer-
ence Manual (76.8660-40121)
• NE enclosure, baseboard, power supply modules, SCMs, HM
and LM types in 8611 Smart Router FP2.0 Reference Manual
(76.8660-40122)
• NE enclosure, baseboard, power supply modules, and in-
terfaces in 8615 Smart Router FP1.0 Reference Manual
(76.8660-40117)
• NE subrack, fan modules, CDCs, line cards and IFMs in 8630
Smart Router FP5.0 Reference Manual (76.8660-40123)
• NE subrack, fan modules, CDCs, line cards and IFMs in 8660
Smart Router FP5.0 Reference Manual (76.8660-40124)
8600 Smart Routers Provides an overview of 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.
8600 Smart Routers Describes SNMP MIB support by the 8600 NEs and provides
SNMP MIB Support information on the supported objects and traps. For further
(76.8600-50116) information on SNMP MIBs, see the related RFCs.
8600 Smart Routers Provides an overview of 8600 system supported statistic counters.
Statistic Counters Reference Guide
(76.8600-50142)
8600 Smart Routers Provides an overview of 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.
8600 Smart Routers Provides an overview of 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.
8600 Smart Routers Provides an overview of 8600 system virtual private network
VPNs Configuration Guide (VPN) layer 3 applications as well as instructions on how to
(76.8600-50128) configure them with CLI.
8000 Intelligent Network Manager Provides instructions on how different operations are performed
Online Help with the 8000 Intelligent Network Manager. Describes also
different parameters and controls of the 8000 Intelligent Network
Manager dialogs and windows.
Note that the Online Help is not available on the Portal but it is
incorporated in the 8000 Intelligent Network Manager.

76.8660-50169C 8600 Smart Routers SR6.0

15
8600 Smart Routers Discontinued Products

8600 Smart Routers Discontinued Products

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

8600 Smart Routers SR6.0 76.8660-50169C

16
1 Embedded Software Interrelation Tables

1 Embedded Software Interrelation Tables

The following embedded software interrelation tables are shown below:

• Boot software and mini-application used in 8600. For a comprehensive list of software ver-
sions, please refer to 8600 Smart Routers Boot and Mini-Applications Embedded Software Re-
lease Notes.
• Application software used in 8600 network elements, control cards, line cards, interface modules
and line modules
The tables show, in a compact form, the dependencies between 8600 embedded software and
dependencies between 8600 embedded software and 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 Coriant.
• 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.

76.8660-50169C 8600 Smart Routers SR6.0

17
1 Embedded Software Interrelation Tables

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
Coriant technical support.
NE Dependencies ESW dependencies related to a NE.
8000 INM Release 8000 Intelligent Network Manager release that supports all
functionality of the product.
8000 INM EMS Driver Version 8000 Intelligent Network Manager EMS driver version
related to 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.

1.1 8600 Boot and Mini-Applications Software

8600 Smart Routers SR6.0 76.8660-50169C

18
© 2014 Coriant.
76.8660-50169C 8600 Boot and Mini-Applications Software
Basic Data Other
Data
Mini- Ap- Version 8600 Base- HW Boot SW Version Application Production
plication NE/card board Version Version Status
GMZ2702 2.11.156 CDC1-A CBB2026 1.1 or GMZ2700 3.4.0 2.11.134 or GA
higher higher
GMZ2702 2.11.134 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
GMZ2702 2.0.100 CDC1-A CBB2026 1.1 or higher GMZ2700 3.0 2.8.212 or GA
lower
GMZ2702 2.0.0 CDC1-A CBB2026 1.1 or higher GMZ2700 3.0 2.8.212 or GA
lower
GMZ2702 1.17.15 CDC1-A CBB2026 1.1 or higher GMZ2700 3.0 2.8.212 or GA
lower
GMZ2702 2.11.156 CDC1-B CBB2224 1.0 or GMZ2700 3.4.0 2.11.134 or GA
higher higher
GMZ2702 2.11.134 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

1 Embedded Software Interrelation Tables

lower
Embedded Software Release Notes

GMZ2702 2.0.101 CDC1-B CBB2224 1.0 or higher GMZ2700 3.1 2.8.212 or GA

lower
8600 Smart Routers SR6.0

CBZ2745 5.0.301 CDC2-B CBB2300 1.0 or GMZ2743 1.57.0 FP4.1 CIR2 GA

higher or higher
CBZ2745 4.1.509 CDC2-B CBB2300 1.0 or higher GMZ2743 1.20.0 FP4.1 CIR2 GA
or higher
19
20

Embedded Software Release Notes

8600 Smart Routers SR6.0

1 Embedded Software Interrelation Tables

Basic Data Other
Data
Mini- Ap- Version 8600 Base- HW Boot SW Version Application Production
plication NE/card board Version Version Status
CBZ2745 4.1.259u CDC2-B CBB2300 1.0 or higher GMZ2743 1.16.0 FP4.1 CIR2 CIR
or FP4.1
CIR3
LBZ2754 4.0.44 ELC1 ELC2269 1.0 or GMZ2752 1.2.0 Any GA
higher
LBZ2754 4.0.44 ELC1 ELC2269 1.0 or higher GMZ2752 1.1.0 Any GA
LBZ2754 4.0.34 ELC1 ELC2269 1.0 or higher GMZ2752 1.0.2 4.0.19 HW CIR sw
load
LBZ2754 4.0.21 ELC1 ELC2269 1.0 or higher GMZ2752 1.0.0 4.0.19 HW CIR sw
load
GMZ2711 2.11.156 IFC1-A LBA2024 1.0 or GMZ2710 3.4.0 2.11.134 or GA
higher higher
GMZ2711 2.11.134 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
GMZ2711 2.0.100 IFC1-A LBA2024 1.0 or higher GMZ2710 3.0 2.8.212 or GA
lower
GMZ2711 2.0.0 IFC1-A LBA2024 1.0 or higher GMZ2710 3.0 2.8.212 or GA
lower
GMZ2711 1.17.15 IFC1-A LBA2024 1.0 or higher GMZ2710 3.0 2.8.212 or GA
lower
GMZ2711 2.11.156 IFC1-B LBA2225 1.0 or GMZ2710 3.4.0 2.11.134 or GA
higher higher
GMZ2711 2.11.134 IFC1-B LBA2225 1.0 or higher GMZ2710 3.4.0 2.11.134 or GA
higher
76.8660-50169C
© 2014 Coriant.

GMZ2711 2.8.191 IFC1-B LBA2225 1.0 or higher GMZ2710 3.4.0 Any GA

© 2014 Coriant.
76.8660-50169C Basic Data Other
Data
Mini- Ap- Version 8600 Base- HW Boot SW Version Application Production
plication NE/card board Version Version Status
GMZ2711 2.0.104 IFC1-B LBA2225 1.0 or higher GMZ2710 3.3.7 2.8.212 or GA
lower
GMZ2711 2.0.101 IFC1-B LBA2225 1.0 or higher GMZ2710 3.1 2.8.212 or GA
lower
GMZ2740 3.0.128 IFC2-B LBA2250 1.0 or GMZ2739 1.0.6 3.0.126 or GA
higher higher
GMZ2740 3.0.128 IFC2-B LBA2250 1.0 or higher GMZ2739 1.0.5 3.0.126 or GA
higher
GMZ2740 3.0.122 IFC2-B LBA2250 1.0 or higher GMZ2739 1.0.5 3.0.126 or GA
higher
GMZ2716 2.11.156 8620 SBB2030 1.0 or GMZ2715 3.4.0 2.11.134 or GA
higher higher
GMZ2716 2.11.134 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
lower
GMZ2716 2.0.101 8620 SBB2030 1.0 or higher GMZ2715 3.1 2.8.212 or GA
lower
GMZ2716 2.0.0 8620 SBB2030 1.0 or higher GMZ2715 3.0 2.8.212 or GA
lower
GMZ2716 1.17.15 8620 SBB2030 1.0 or higher GMZ2715 3.0 2.8.212 or GA

1 Embedded Software Interrelation Tables

lower
SBZ2755 1.1.300 8602-D SBB2315 1.0 or GMZ2756 1.0.0 Any GA
Embedded Software Release Notes

higher
SBZ2755 1.1.83 8602-D SBB2315 1.0 or higher GMZ2756 0.16.1 Any CIR
8600 Smart Routers SR6.0

SBZ2755 1.1.300 8602-A SBB2305 1.0 or GMZ2756 1.0.0 Any GA

higher
SBZ2755 1.0.151 8602-A SBB2305 1.0 or higher GMZ2756 0.15.1 Any GA
SBZ2755 1.0.57 8602-A SBB2305 1.0 or higher GMZ2756 0.14.1 1.0.102 CIR
21
22

Embedded Software Release Notes

8600 Smart Routers SR6.0

1 Embedded Software Interrelation Tables

Basic Data Other
Data
Mini- Ap- Version 8600 Base- HW Boot SW Version Application Production
plication NE/card board Version Version Status
GMZ2728 1.3.105 8605 SBB2230 1.0 or GMZ2727 1.3.0 Any GA
higher
GMZ2728 1.3.105 8605 SBB2230 1.0 or higher GMZ2727 1.2.0 Any GA
GMZ2728 1.3.105 8605 SBB2230 1.0 or higher GMZ2727 1.1.0 Any GA
GMZ2728 1.0.157 8605 SBB2230 1.0 or higher GMZ2727 1.1.0 Any GA
GMZ2728 0.40.2 8605 SBB2230 1.0 or higher GMZ2727 1.1.0 Any GA
GMZ2737 1.0.250 8607 SBB2238 1.0 or GMZ2736 1.1.0 Any GA
higher
GMZ2737 1.0.250 8607 SBB2238 1.0 or higher GMZ2736 1.0.0 Any GA
GMZ2737 1.0.27 8607 SBB2238 1.0 or higher GMZ2736 1.0.0 Any GA
GMZ2737 1.0.17 8607 SBB2238 1.0 or higher GMZ2736 1.0.0 Any GA
SBZ2751 2.0.300 8609 SBB2284 1.0 or GMZ2749 1.3.0 Any GA
higher
SBZ2751 1.2.303 8609 SBB2284 1.0 or higher GMZ2749 1.2.1 Any GA
GMZ2750 1.1.75 8609 SBB2284 1.0 or higher GMZ2749 1.1.0 Any GA
GMZ2750 1.0.67 8609 SBB2284 1.0 GMZ2749 1.0.0 Any GA
SBZ2748 2.0.300 8611 (SCM) SCM2265 81.86C- GMZ2746 1.3.0 Any GA
8611-R6
Rev. A or
higher
SBZ2748 1.2.303 8611 (SCM) SCM2265 81.86C- GMZ2746 1.2.1 Any GA
8611-R6
Rev. A or
higher
GMZ2747 1.1.75 8611 (SCM) SCM2265 81.86C- GMZ2746 1.1.0 Any GA
8611-R6
Rev. A or
higher
76.8660-50169C
© 2014 Coriant.

LBZ2765 1.0.304 8615 (LU) SBB2306 1.0 or GMZ2758 1.57.0 Any GA

higher
LBZ2765 1.0.86 8615 (LU) SBB2306 1.0 or higher GMZ2758 1.52.0 1.0.103 CIR
© 2014 Coriant.
76.8660-50169C Basic Data Other
Data
Mini- Ap- Version 8600 Base- HW Boot SW Version Application Production
plication NE/card board Version Version Status
CBZ2764 1.0.304 8615 (CU) VID9109 1.0 or GMZ2758 1.57.0 Any GA
higher
CBZ2764 1.0.86 8615 (CU) VID9109 1.0 or higher GMZ2758 1.52.0 1.0.103 CIR

1 Embedded Software Interrelation Tables

Embedded Software Release Notes
8600 Smart Routers SR6.0
23
1 Embedded Software Interrelation Tables

1.2 8602 Smart Router Applications Software Compatibility Matrix

8602 Smart Router Hardware and Software Compatibility Matrix

Basic Data 8000 INM 8000
Release INM EMS
Base- HW ESW ESW Production Driver
board Version Version Status Version
SBB2305 1.0 or SBZ2755 1.1.308 GA SR6.0-SP2 101.2
higher (SR6.0 SP1) or higher
SBB2305 1.0 or SBZ2755 1.1.244 CIR SR6.0-SP2 101.2
higher (SR6.0 CIR2) or higher
SBB2305 1.0 or SBZ2755 1.1.103 CIR SR6.0-SP1 101.0
higher (SR6.0 CIR) or higher
SBB2315 1.0 or SBZ2755 1.1.308 GA SR6.0-SP2 101.2
higher (SR6.0 SP1) or higher
SBB2315 1.0 or SBZ2755 1.1.244 CIR SR6.0-SP2 101.2
higher (SR6.0 CIR2) or higher
SBB2315 1.0 or SBZ2755 1.1.103 CIR SR6.0-SP1 101.0
higher (SR6.0 CIR) or higher

1.3 8609 Smart Router and 8611 Smart Router Applications Software
Compatibility Matrix

8609 Smart Router Hardware and Software Compatibility Matrix

Basic Data 8000 INM 8000
Release INM EMS
Base- HW ESW ESW Production Driver
board Version Version Status Version
SBB2284 1.0 or SBZ2751 2.0.308 GA SR6.0-SP2 200.2
higher (SR6.0 SP1) or higher
SBB2284 1.0 or SBZ2751 2.0.244 CIR SR6.0-SP2 200.2
higher (SR6.0 CIR2) or higher
SBB2284 1.0 or SBZ2751 2.0.103 CIR SR6.0-SP1 200.0
higher (SR6.0 CIR) or higher

8600 Smart Routers SR6.0 76.8660-50169C

24
1 Embedded Software Interrelation Tables

8611 Smart Router Hardware and Software Compatibility Matrix

Basic Data 8000 INM 8000
Release INM EMS
8611 HW ESW ESW Production Driver
Card Version Version Status Version
SCM 81.86C- SBZ2748 2.0.308 GA SR6.0- 200.2
(SCM2265) 8611-R6 (SR6.0 SP1) SP2 or
Rev. A or higher
higher
SCM 81.86C- SBZ2748 2.0.244 CIR SR6.0-SP2 200.2
(SCM2265) 8611-R6 (SR6.0 CIR2) or higher
Rev. A or
higher
SCM 81.86C- SBZ2748 2.0.103 CIR SR6.0-SP1 200.0
(SCM2265) 8611-R6 (SR6.0 CIR) or higher
Rev. A or
higher

76.8660-50169C 8600 Smart Routers SR6.0

25
26

Embedded Software Release Notes

8600 Smart Routers SR6.0

1 Embedded Software Interrelation Tables

Hardware and Software Compatibility Matrix for Switching and Control Module and Physical Line Modules
Basic Data Required ESW Version
Line Module HW Version Down- Firmware 8609 8611
loadable Version SBZ2751 SBZ2748
Firmware
SCM 81.86C-8611-R6 Rev. A — — — 1.1.102 or higher
8x10/100BASE-TX LM 81.86LFETX82243-R6 — — 1.2.322 or higher 1.2.322 or higher
LME2243 Rev. D
8x10/100BASE-TX LM 81.86LFETX82243-R6 — — 1.0.100 or higher 1.1.102 or higher
LME2243 Rev. C
8xchE1/chT1 LM 81.86LE1T082242-R6 — — 1.2.322 or higher 1.2.322 or higher
LMP2242 Rev. D
8xchE1/chT1 LM 81.86LE1T082242-R6 Rev. — — 1.0.100 or higher 1.1.102 or higher
LMP2242 C
4x10/100/1000BASE-TX 81.86M-HMGE4RJ-R6 — — — 1.1.102 or higher
HM HMG2274 Rev. A
4x100/1000BASE-X HM 81.86M-HMGE4SFP-R6 — — — 1.1.102 or higher
HMG2266 Rev. A
1x10GBASE-R HM 81.86M-HM10GE1-R6 — — — 1.2.322 or higher
HMX2267 Rev. A
76.8660-50169C
© 2014 Coriant.
1 Embedded Software Interrelation Tables

1.4 8615 Smart Router Applications Software Compatibility Matrix

76.8660-50169C 8600 Smart Routers SR6.0

27
28

Embedded Software Release Notes

8600 Smart Routers SR6.0

1 Embedded Software Interrelation Tables

8615 Smart Router Hardware and Software Compatibility Matrix
Basic Data NE Dependencies 8000 8000
INM INM EMS
8615 Card Base- HW ESW ESW Version Production CU LU Release Driver
board Version Status Version
CU VID9109 1.0 or CBZ2764 1.0.308 (SR6.0 SP1) GA 1.0.308 1.0.308 SR6.0- 100.2
higher SP2 or
higher
CU VID9109 1.0 or CBZ2764 1.0.244 (SR6.0 CIR2) CIR 1.0.244 1.0.244 SR6.0- 100.2
higher SP2 or
higher
CU VID9109 1.0 or CBZ2764 1.0.103 (SR6.0 CIR) CIR 1.0.103 1.0.103 SR6.0- 100.0
higher SP1.1 or
higher
LU SBB2306 1.0 or LBZ2765 1.0.308 (SR6.0 SP1) GA 1.0.308 1.0.308 SR6.0- 100.2
higher SP2 or
higher
LU SBB2306 1.0 or LBZ2765 1.0.244 (SR6.0 CIR2) CIR 1.0.244 1.0.244 SR6.0- 100.2
higher SP2 or
higher
LU SBB2306 1.0 or LBZ2765 1.0.103 (SR6.0 CIR) CIR 1.0.103 1.0.103 SR6.0- 100.0
higher SP1.1 or
higher
76.8660-50169C
© 2014 Coriant.
1 Embedded Software Interrelation Tables

1.5 8630 Smart Router and 8660 Smart Router Applications Software
Compatibility Matrix

76.8660-50169C 8600 Smart Routers SR6.0

29
30

Embedded Software Release Notes

8600 Smart Routers SR6.0

1 Embedded Software Interrelation Tables

8630 Smart Router and 8660 Smart Router Hardware and Software Compatibility Matrix
Basic Data NE Dependencies 8000 INM 8000
Release INM EMS
8630 Base- HW ESW ESW Produc- CDC1 CDC2 ELC1 IFC1 IFC2 Driver
/8660 board Version Version tion Version
Card Status
CDC1-A CBB2026 1.1 or CBZ2712 5.0.308 GA 5.0.308 5.0.308 5.0.308 5.0.308 5.0.308 SR6.0- 500.2
higher (SR6.0 SP2 or
SP1) higher
CDC1-A CBB2026 1.1 or CBZ2712 5.0.244 CIR 5.0.244 5.0.244 5.0.244 5.0.244 5.0.244 SR6.0-SP2 500.2
higher (SR6.0 or higher
CIR2)
CDC1-A CBB2026 1.1 or CBZ2712 5.0.103 CIR 5.0.103 5.0.103 5.0.103 5.0.103 5.0.103 SR6.0-SP1 500.0
higher (SR6.0 or higher
CIR)
CDC1-B CBB2224 1.0 or CBZ2712 5.0.308 GA 5.0.308 5.0.308 5.0.308 5.0.308 5.0.308 SR6.0- 500.2
higher (SR6.0 SP2 or
SP1) higher
CDC1-B CBB2224 1.0 or CBZ2712 5.0.244 CIR 5.0.244 5.0.244 5.0.244 5.0.244 5.0.244 SR6.0-SP2 500.2
higher (SR6.0 or higher
CIR2)
CDC1-B CBB2224 1.0 or CBZ2712 5.0.103 CIR 5.0.103 5.0.103 5.0.103 5.0.103 5.0.103 SR6.0-SP1 500.0
higher (SR6.0 or higher
CIR)
CDC2-B CBB2300 1.0 or CBZ2745 5.0.308 GA 5.0.308 5.0.308 5.0.308 5.0.308 5.0.308 SR6.0- 500.2
higher (SR6.0 SP2 or
SP1) higher
CDC2-B CBB2300 1.0 or CBZ2745 5.0.244 CIR 5.0.244 5.0.244 5.0.244 5.0.244 5.0.244 SR6.0-SP2 500.2
higher (SR6.0 or higher
CIR2)
CDC2-B CBB2300 1.0 or CBZ2745 5.0.103 CIR 5.0.103 5.0.103 5.0.103 5.0.103 5.0.103 SR6.0-SP1 500.0
higher (SR6.0 or higher
CIR)
ELC1 ELC2269 1.0 or LBZ2754 5.0.308 GA 5.0.308 5.0.308 5.0.308 5.0.308 5.0.308 SR6.0- 500.2
76.8660-50169C

higher (SR6.0 SP2 or

SP1) higher
© 2014 Coriant.
76.8660-50169C Basic Data NE Dependencies 8000 INM 8000
Release INM EMS
8630 Base- HW ESW ESW Produc- CDC1 CDC2 ELC1 IFC1 IFC2 Driver
/8660 board Version Version tion Version
Card Status
ELC1 ELC2269 1.0 or LBZ2754 5.0.244 CIR 5.0.244 5.0.244 5.0.244 5.0.244 5.0.244 SR6.0-SP2 500.2
higher (SR6.0 or higher
CIR2)
ELC1 ELC2269 1.0 or LBZ2754 5.0.103 CIR 5.0.103 5.0.103 5.0.103 5.0.103 5.0.103 SR6.0-SP1 500.0
higher (SR6.0 or higher
CIR)
IFC1-B LBA2225 1.0 or LBZ2713 5.0.308 GA 5.0.308 5.0.308 5.0.308 5.0.308 5.0.308 SR6.0- 500.2
higher (SR6.0 SP2 or
SP1) higher
IFC1-B LBA2225 1.0 or LBZ2713 5.0.244 CIR 5.0.244 5.0.244 5.0.244 5.0.244 5.0.244 SR6.0-SP2 500.2
higher (SR6.0 or higher
CIR2)
IFC1-B LBA2225 1.0 or LBZ2713 5.0.103 CIR 5.0.103 5.0.103 5.0.103 5.0.103 5.0.103 SR6.0-SP1 500.0
higher (SR6.0 or higher
CIR)
IFC2-B LBA2250 1.0 or LBZ2741 5.0.308 GA 5.0.308 5.0.308 5.0.308 5.0.308 5.0.308 SR6.0- 500.2
higher (SR6.0 SP2 or
SP1) higher
IFC2-B LBA2250 1.0 or LBZ2741 5.0.244 CIR 5.0.244 5.0.244 5.0.244 5.0.244 5.0.244 SR6.0-SP2 500.2
higher (SR6.0 or higher
CIR2)
IFC2-B LBA2250 1.0 or LBZ2741 5.0.103 CIR 5.0.103 5.0.103 5.0.103 5.0.103 5.0.103 SR6.0-SP1 500.0
higher (SR6.0 or higher

1 Embedded Software Interrelation Tables

CIR)
Embedded Software Release Notes
8600 Smart Routers SR6.0
31
32

Embedded Software Release Notes

8600 Smart Routers SR6.0

1 Embedded Software Interrelation Tables

8600 Interface Module Hardware and Software Compatibility Matrix
Basic Data Compatible NEs/Cards & ESW Versions
Interface Module HW Version CDC1 CDC2 IFC1 IFC2
CBZ2712 CBZ2745 LBZ2713 LBZ2741
8x10/100BASE-TX 2.2 2.2.7 or higher 4.1.322 or higher 2.2.7 or higher —
LIE2018 (81.86MFETX82018-R6
Rev. D)
8x10/100BASE-TX 2.1 (81.86MFETX82018-R6 2.2.7 or higher 4.1.322 or higher 2.2.7 or higher —
LIE2018 Rev. C)
8x10/100BASE-TX 2.0 2.2.7 or higher 4.1.322 or higher 2.2.7 or higher —
LIE2018
8x10/100BASE-TX 1.0 1.17.15 or higher 4.1.322 or higher 1.17.15 or higher —
LIE2018
8x100BASE-X 1.1 (81.86MFEX082028-R6 1.22.7 or higher 4.1.322 or higher 1.22.7 or higher —
LIO2028 Rev. A)
8x100BASE-X 1.0 1.22.7 or higher 4.1.322 or higher 1.22.7 or higher —
LIO2028
2x1000BASE-X LIO2019 2.0 (81.86MGE0022019-R5 1.17.36 or higher 4.1.322 or higher 1.17.36 or higher —
Rev. A)
2x1000BASE-X LIO2019 1.0 1.17.15 or higher 4.1.322 or higher 1.17.15 or higher —
8x1000BASE-X LIO2208 2.0 (81.86MGE0082208-R6 1.22.7 or higher 4.1.322 or higher 1.22.7 or higher —
Rev. B)
8x1000BASE-X LIO2208 1.2 1.22.7 or higher 4.1.322 or higher 1.22.7 or higher —
8x1000BASE-X LIO2208 1.0 1.22.7 or higher 4.1.322 or higher 1.22.7 or higher —
2+6x10/100/1000 1.3 2.5.113 or higher 4.1.322 or higher 2.5.113 or higher —
BASE-COMBO (81.86MGEC082231-R6
LIC2231 Rev. C)
2+6x10/100/1000 1.2 (81.86MGEC082231-R6 2.5.113 or higher 4.1.322 or higher 2.5.113 or higher —
BASE-COMBO Rev. B)
LIC2231
2+6x10/100/1000 1.0 2.5.113 or higher 4.1.322 or higher 2.5.113 or higher —
76.8660-50169C

BASE-COMBO
© 2014 Coriant.

LIC2231
8x10/100/1000BASE-TX 81.86M-IFMGET08-R6 3.1.309 or higher 4.1.322 or higher — 3.1.309 or higher
R2 LIE2256 Rev. A
© 2014 Coriant.
76.8660-50169C Basic Data Compatible NEs/Cards & ESW Versions
Interface Module HW Version CDC1 CDC2 IFC1 IFC2
CBZ2712 CBZ2745 LBZ2713 LBZ2741
8x100/1000BASE-X R2 81.86M-IFMGEX08-R6 3.0.126 or higher 4.1.322 or higher — 3.0.126 or higher
IFM LIO2252 Rev. B
8x100/1000BASE-X R2 1.0 3.0.126 or higher 4.1.322 or higher — 3.0.126 or higher
IFM LIO2252 (81.86M-IFMGEX08-R6
Rev. A)
1x10GBASE-R R2 IFM 81.86M-IFM10GS1-R6 3.0.126 or higher 4.1.322 or higher — 3.0.126 or higher
LIO2257 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 (81.86MS1P082020-R6 1.17.15 or higher 4.1.322 or higher 1.17.15 or higher 3.1.309 or higher
LIO2020 Rev. A)
8xSTM-1 POS 1.0 1.17.15 or higher 4.1.322 or higher 1.17.15 or higher —
LIO2020
4xSTM-4/OC-12 POS 1.0 (81.86MS4P042233-R6 2.7.20 or higher 4.1.322 or higher 2.7.20 or higher 3.1.309 or higher
LIO2233 Rev. A)
1xSTM-16/OC-48 POS 1.0 (81.86MS16P12021-R6 1.17.15 or higher 4.1.322 or higher 1.17.15 or higher 3.1.309 or higher
LIO2021 Rev. A)
4xSTM-1/OC-3 ATM 1.1 (81.86MS1A042210-R6 2.0.2 or higher 4.1.322 or higher 2.0.2 or higher 3.1.309 or higher
LIA2210 Rev. A)
4xSTM-1/OC-3 ATM 1.0 2.0.2 or higher 4.1.322 or higher 2.0.2 or higher —
LIA2210
1xchSTM-1/chOC-3 MS 1.0 (81.86MS1C012203-R5 2.0.2 or higher 4.1.322 or higher 2.0.2 or higher 3.1.309 or higher

1 Embedded Software Interrelation Tables

LIO2203 Rev. B)
Embedded Software Release Notes

4xchSTM-1/chOC-3 MS 2.0 (81.86MS1C042234-R6 2.9.143 or higher 4.1.322 or higher 2.9.143 or higher 3.1.309 or higher
LIO2234 Rev. B)
8600 Smart Routers SR6.0

4xchSTM-1/chOC-3 MS 1.1 (81.86MS1C042234-R6 2.9.143 or higher 4.1.322 or higher 2.9.143 or higher —

LIO2234 Rev. A)
24xchE1/chT1 MS 2.1 (81.86ME1T242226-R6 2.7.20 or higher 4.1.322 or higher 2.7.20 or higher 3.1.309 or higher
LIE2226 Rev. B)
24xchE1/chT1 MS LIE2226 2.0 2.7.20 or higher 4.1.322 or higher 2.7.20 or higher —
33
34

Embedded Software Release Notes

8600 Smart Routers SR6.0

1 Embedded Software Interrelation Tables

Basic Data Compatible NEs/Cards & ESW Versions
Interface Module HW Version CDC1 CDC2 IFC1 IFC2
CBZ2712 CBZ2745 LBZ2713 LBZ2741
24xchE1 MS 1.0 2.2.7 or higher 4.1.322 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 —
LIE2237 (81.86ME1M242237-R6
Rev. A)
76.8660-50169C
© 2014 Coriant.
2 Supported Upgrade Paths

2 Supported Upgrade Paths

The supported upgrade paths are listed in the tables below. See also ch. 5 Upgrade Related
Notifications.

8602 Smart Router

From To
FP1.0 SP1 (1.0.163) FP1.1 SP1
FP1.0 CIR (1.0.102) FP1.0 SP1

8609 Smart Router and 8611 Smart Router

From To
FP2.0 CIR (2.0.103) FP2.0 SP1
FP1.3 SP1 (1.3.163) FP2.0 SP1
FP1.2 SP2 (1.2.629) FP2.0 SP1
FP1.3 CIR (1.3.102) FP1.3 SP1
FP1.2 SP1 (1.2.586) FP1.2 SP2
FP1.2 SP1 (1.2.586) FP1.3 SP1
FP1.2 CIR1 (1.2.182) FP1.2 SP2
FP1.1 SP1 (1.1.215) FP1.2 SP2
FP1.1 SP1 (1.1.215) FP1.3 SP1
8609 FP1.0 SP2 (1.0.308)1 FP1.3 SP1
8609 FP1.0 SP2 (1.0.308) FP1.2 SP2

8630 Smart Router and 8660 Smart Router

From To
SR5.0 CIR (5.0.103) FP5.0 SP1
FP4.1 SP2 (4.1.629) FP5.0 SP1
FP4.1 SP1 (4.1.586) FP4.1 SP2
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)

1In case IEEE1588 is in use with FP1.0 SP2, it is not possible to upgrade directly to FP1.3. Otherwise, acceptable master table and the associated
configuration will be lost. See cq300245984 for details and workaround instructions.

76.8660-50169C 8600 Smart Routers SR6.0

35
2 Supported Upgrade Paths

From To
FP4.0 SP4 (4.0.405) FP5.0 SP1
FP4.0 SP3 (4.0.309) FP4.1 SP2
FP4.0 SP2 (4.0.205) FP4.1 SP2
FP4.0 SP1 (4.0.123) FP4.1 SP2
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

8600 Smart Routers SR6.0 76.8660-50169C

36
3 Software Upgrade Order

3 Software Upgrade Order

Boot and mini-application software should be updated only if there is a real need to do it, e.g.:

• Mini- or application SW release notes say mini-application upgrade is mandatory or

• There is some other customer related reason for update, e.g. a new feature or bug fix in newer
mini-application is needed.

When upgrading both the application software and the mini-application software in 8602
Smart Router and 8609 Smart Router it is recommended that the application software is
upgraded first.

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 8600 Boot and
Mini-Applications Embedded Software Release Notes.

If you are currently using application ESW FP2.11A SP1 in 8630 Smart Router and 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.

76.8660-50169C 8600 Smart Routers SR6.0

37
4 Operations Before Upgrade

4 Operations Before Upgrade

Prior to upgrading, validate that the network element is ready for upgrade by performing the steps
outlined below, which are common for all 8600 Smart Routers.

• Check and record the state of the NE before starting the upgrade.
• Free flash space by removing the previous unused ESWs.
• Free flash space by removing the old unused configuration snapshot files in each slot.
• Backup the current configuration of the NE.

4.1 Operations Before Upgrading 8602 Smart Router and 8609 Smart
Router

Note that 'x.y.z' in the examples below refers to the relevant ESW version number.

Step 1 Check and record the state of the NE before starting the upgrade. Check the hardware inventory and
verify that the NE is in up-and-running state and check the 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 canceled manually).
Step 2 Free flash space by removing the previous unused ESWs:
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:
/flash/snapshot-config/
This CLI command will give a list of the already created and stored snapshots:
router# show snapshot-config flash: ?
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 flash: <filename>

8600 Smart Routers SR6.0 76.8660-50169C

38
4 Operations Before Upgrade

Step 4 Backup the current configuration of the NE:

4.2 Operations Before Upgrading 8611 Smart Router

Note that in 8611 Smart Router the working slot (primary) is slot 2.

Note that 'x.y.z' in the examples below refers to the relevant ESW version number.

Step 1 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 canceled manually).
Step 2 Free flash space by removing the previous unused ESWs:
router# delete slot * 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:
/flash/snapshot-config/slot<slot#>/
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 SCM 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 2 flash: <filename>

76.8660-50169C 8600 Smart Routers SR6.0

39
4 Operations Before Upgrade

Step 4 Backup the current configuration of the NE:

router# snapshot-config create flash: <filename> description
<x.y.z>
The current configuration and running config text file will be stored in the snapshot file:
router# snapshot-config create flash: <filename>
running-config description <x.y.z>
In 8611 Smart Router the configuration snapshot file can be uploaded using FTP from either
directory (depending on which SCM is active):
/flash/snapshot-config/slot2/ OR
/flash/snapshot-config/slot1/

4.3 Operations Before Upgrading 8615 Smart Router

Note that 'x.y.z' in the examples below refers to the relevant ESW version number.

Step 1 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 canceled manually).
Step 2 Free flash space by removing the previous unused ESWs:
router# delete slot * 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:
/flash/snapshot-config/slot<slot#>/
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 CU 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>

8600 Smart Routers SR6.0 76.8660-50169C

40
4 Operations Before Upgrade

Step 4 Backup the current configuration of the NE:

4.4 Operations Before Upgrading 8630 Smart Router and 8660 Smart
Router

Note that in 8630 Smart Router and 8660 Smart Router, which are multi-card NEs, the working slot
(primary) is slot 14.

Note that 'x.y.z' in the examples below refers to the relevant ESW version number.

Step 1 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 canceled manually).
Step 2 Free flash space by removing the previous unused ESWs:
router# delete slot * 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:
/flash/snapshot-config/slot<slot#>/
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>

76.8660-50169C 8600 Smart Routers SR6.0

41
4 Operations Before Upgrade

Step 4 Backup the current configuration of the NE:

router# snapshot-config create flash: <filename> description
<x.y.z>
The current configuration and running config text file will be stored in the snapshot file:
router# snapshot-config create flash: <filename>
running-config description <x.y.z>
In 8630 Smart Router and 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/

8600 Smart Routers SR6.0 76.8660-50169C

42
5 Upgrade Related Notifications

5 Upgrade Related Notifications

This chapter provides information about items to be taken into account when upgrading to the
current release.

Please also refer to chapter 2 Supported Upgrade Paths.

5.1 Upgrade Related Notifications for 8609 Smart Router and 8611
Smart Router

When upgrading to 8609 Smart Router or 8611 Smart Router ESW release 1.2.586, all
IEEE1588 configurations MUST be removed prior to the upgrade, and re-applied after 1.2.586
has been activated.
Contact Coriant Technical Assistance for further information (http://www.coriant.com/ser-
vices_support).

5.1.1 Recommended Procedure for Upgrading to 8609 Smart Router and 8611
Smart Router FP1.3 SP1

In software versions previous to FP1.3, the 'IP domain-lookup' is not initialized properly, though it
should be enabled by default. As a result of this, no 'IP domain-lookup' is set.

Before upgrading to FP1.3, set explicitly the IP domain lookup functionality to a desired one with
CLI or 8000 Intelligent Network Manager, or fix any possible inconsistencies with CLI or 8000
Intelligent Network Manager after upgrade (cq300214881).

5.2 Upgrade Related Notifications for 8630 Smart Router and 8660
Smart Router

Non-service affecting upgrade of IFC1 to IFC2 cards is NOT supported in 8600 Smart Routers
FP5.0 SP1 GA. Refer to 8600 Smart Routers FP3.1 Embedded Software Release Notes (doc. ID
76.8631-50146), ch. 2.7.2, for the procedure.

Non-service affecting upgrade of ELC1 card is NOT supported from SR6.0 CIR1 or SR6.0 CIR2
to SR6.0 SP1 GA version. Attempting the upgrade will cause a card reset. Only service
affecting upgrade is supported from SR6.0 CIR1 or SR6.0 CIR2 to SR6.0 SP1 GA.
Non-service affecting software upgrade of ELC1 card is working from SR5.0 to SR6.0 SP1
GA version.

76.8660-50169C 8600 Smart Routers SR6.0

43
5 Upgrade Related Notifications

5.2.1 Notification Regarding ELC1 ESW Upgrade to 8630 Smart Router and
8660 Smart Router FP4.1 SP1

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

8600 Smart Routers SR6.0 76.8660-50169C

44
6 Service Affecting Software Upgrade of the Whole NE

6 Service Affecting Software Upgrade of the

Whole NE

For 8611 Smart Router upgrade from FP1.2 CIR1 or any earlier ESW version, both the software
and hardware should be upgraded. For the said upgrade paths the procedure in chapter
6.1 8611 Smart Router Service Affecting Hardware and Software Upgrade of the Whole NE
should be used instead of the one identified in this section.

Never activate an older ESW than the current one without restoring configurations or carrying
out a clean-start of the NE (see chapter 10 Restoring Previous FP and Configuration in Case
of Upgrade Failure). The end result of the operation is otherwise fully nondeterministic.

When an ESW package file 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.

76.8660-50169C 8600 Smart Routers SR6.0

45
6 Service Affecting Software Upgrade of the Whole NE

Note that in the file name 'x.y.z' refers to the ESW version number.

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 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 in 8630 Smart Router or 8660 Smart Router, 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.z_c1i1 and then pkg_8660_x.y.z_i2e1.
Select the file which is transferred to the NE using FTP/SFTP and the target directory in the NE
according to the following table.
Note that in the file name 'x.y.z' refers to the ESW version number.

NE Type File Name for ESW Upgrade FTP Target Directory in NE

8602 Smart Router sbz2755_x.y.z /flash/appl-sw
8609 Smart Router sbz2751_x.y.z /flash/appl-sw
8611 Smart Router pkg_8611_x.y.z /flash/appl-sw/slot2
8615 Smart Router pkg_8615_x.y.z /flash/appl-sw/slot14
8630 Smart Router and 8660 pkg_8660_x.y.z_C1 2 /flash/appl-sw/slot1 or
Smart Router with CDC1 /flash/appl-sw/slot14 3 or
/flash/appl-sw/slot<slot#>4
8630 Smart Router and 8660 pkg_8660_x.y.z_C2 2 /flash/appl-sw/slot1 or
Smart Router with CDC2 /flash/appl-sw/slot14 or3
/flash/appl-sw/slot<slot#>4

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.

8600 Smart Routers SR6.0 76.8660-50169C

46
6 Service Affecting Software Upgrade of the Whole NE

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 10 Restoring Previous FP
and Configuration in Case of Upgrade Failure.
8602 Smart Router:
router(config)# boot system flash: sbz2755_x.y.z backup-config
reload
8609 Smart Router:
router(config)# boot system flash: sbz2751_x.y.z backup-config
reload
8611 Smart Router:
router(config)# boot system slot 2 flash: pkg_8611_x.y.z
backup-config reload
8615 Smart Router:
router(config)# boot system slot 14 flash: pkg_8615_x.y.z
backup-config reload
8630 Smart Router and 8660 Smart Router:
router(config)# boot system slot 14 flash: pkg_8660_x.y.z
backup-config reload

6.1 8611 Smart Router Service Affecting Hardware and Software

Upgrade of the Whole NE

For 8611 Smart Router upgrade from FP1.2 CIR1 or any earlier ESW version, the following
service affecting upgrade procedure MUST be followed to ensure that the node-clock related
hardware is also automatically upgraded with the software.

The 8611 Smart Router ESW includes a mechanism that allows the support of upgrading hardware.
Because this upgrade affects hardware, it is traffic impacting. The hardware related image is
downloaded as part of the software package and is activated by the reset hardware command.

Step 1 If the SCM in slot 2 is not active, then do an SCM protection switch:
router# protection manual-switchover unit scm slot 2
Step 2 Wait until SCM1 has booted up completely. Use the following command; wait until slot 1 is “UP
AND RUNNING”:
router# show hw-inventory slot 1 | include slot

76.8660-50169C 8600 Smart Routers SR6.0

47
6 Service Affecting Software Upgrade of the Whole NE

Step 3 Transfer with FTP/SFTP the new software package to the active SCM in slot 2. Before using
FTP/SFTP, the server must be enabled (it is disabled by default). The following characterizes
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).
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

8611 Smart Router pkg_8611_2.0.308 /flash/appl-sw/slot2

Step 4 The upgraded package is downloaded and activated to the NE, all cards get a new version of the
ESW stored in their local flash.
router(config)# boot system slot 2 flash: pkg_8611_2.0.308
backup-config
Step 5 The new application ESW and hardware image is taken in use following a hardware reset.
router# reset-hw
Step 6 Verify that the hardware was properly upgraded after the SCMs have booted up completely (i.e.
they are both in the “UP and RUNNING” state). The hardware upgraded in FP2.0 is identified as
“SCT” and is displayed as revision “0x0204”. Use the following command to verify that the string
“SCT expected and active revision: 0x0204” is present:
router# show hw-inventory details | include SCT

8600 Smart Routers SR6.0 76.8660-50169C

48
7 Non-Service Affecting Software Upgrade

7 Non-Service Affecting Software Upgrade

7.1 8611 Smart Router Non-Service Affecting Software Upgrade

For 8611 Smart Router, the non-service affecting software upgrade procedure is supported
when upgrading from FP1.2 SP1 or any later ESW version. For other upgrade paths, the
procedure in chapter 6.1 8611 Smart Router Service Affecting Hardware and Software Upgrade
of the Whole NE should be followed instead.

The 8611 Smart Router ESW can be upgraded with the non-service affecting upgrade procedure
as follows.

Step 1 Transfer with FTP/SFTP the new software package to the active SCM which should be in slot 2.
Step 2 The upgraded package is downloaded and activated to the NE, all cards get a new version of the
ESW stored to their local flash.
router(config)# boot system slot 2 flash: pkg_8611_2.0.308
backup-config

Do not reload the network element, which will start the whole network element with the new
ESW. Reloading the whole network element is a service affecting upgrade method.

Step 3 SCM1 (protecting) slot is switched to be the active SCM. SCM2 (working) slot will automatically
boot up with the new ESW version.
router# protection manual-switchover unit scm slot 1
Step 4 Wait until SCM2 has booted up completely. Use the following command; wait until slot 2 is “UP
AND RUNNING”:
router# show hw-inventory slot 2 | include slot
Step 5 SCM2 (working) slot is switched to be the active SCM. SCM1 (protecting) slot will automatically
boot up with the new ESW version.
router# protection manual-switchover unit scm slot 2

76.8660-50169C 8600 Smart Routers SR6.0

49
7 Non-Service Affecting Software Upgrade

7.2 8630 Smart Router and 8660 Smart Router Non-Service Affecting
Software Upgrade

The 8600 NE series ESW can be upgraded with the non-service affecting upgrade procedure
as follows.

The terminology used:

• IFC#W: IFC line card configured to be MSP/APS/ELP protection Working side.

• IFC#Pt: IFC line card configured to be MSP/APS/ELP protection Protecting side.
• IFC#Py: IFC line card configured as RSVP path protection Primary path (LSP#P).
• IFC#S: IFC line card configured as RSVP path protection Secondary path (LSP#S).
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).
Select the file which is transferred to the NE using FTP/SFTP and the target directory in the NE
according to following table. In the file name x.y.z refers to the ESW version number.

NE Type File Name for ESW Upgrade FTP Target Directory in NE

8630 Smart Router and 8660 pkg_8660_x.y.z 5 /flash/appl-sw/slot1 or
Smart Router /flash/appl-sw/slot14 6 or
/flash/appl-sw/slot<slot#>7

Step 2 Activate the software package (or all packages if you need to download several packages) to the NE,
all cards get a new version of the ESW stored to their local flash.
router(config)# boot system slot 14 flash: pkg_8660_4.1.586
backup-config

Do not reload the network element which will start the whole network element with the new
ESW. Reloading the whole network element is a service affecting upgrade method.

Step 3 Switch CDC#1 (protecting) slot to be the active CDC.

router# protection manual-switchover unit cdc slot 1
During CDC activity switch, the management connection is cut. Start a Telnet/SSH session again or
start using the console of the CDC in slot 1. There should be no effect on the running data traffic or
routing/signalling. If there is, it is due to some other limitation than the CDC switching action.
Step 4 Boot up CDC#14 (working) slot with the new ESW version.
router# reload-sw slot 14

5Several types of package files may be available.

6Select the slot number of the passive CDC. Check the slot number of the passive CDC with the CLI command “router# show protection unit cdc”
7Select the slot number of IFC2 or ELC1 card.

8600 Smart Routers SR6.0 76.8660-50169C

50
7 Non-Service Affecting Software Upgrade

Step 5 After CDC#14 has booted up completely, activate the CDC#14 slot.
Use the following CLI command; wait until slot 14 is “UP AND RUNNING”:
router# show hw-inventory slot 14
Switch CDC#14 active:
router# protection manual-switchover unit cdc slot 14
During CDC activity switch, the management connection is cut. Start a Telnet/SSH session again or
start using the console of the CDC in slot 14. There should be no effect on the running data traffic or
routing/signalling. If there is, it is due to some other limitation than the CDC switching action.
Step 6 Boot up CDC#1 (protecting) with the new ESW version.
router# reload-sw slot 1
Step 7 Do manual switchover to switch all protected interface traffic to IFC#Pt (the protecting side
interfaces of the protected pairs). E.g.
router# protection manual-switchover ms <GroupName> so 7/0/0
There will be a short traffic break, ideally the break lasts at maximum what standards allow on
switchovers.
A. If the topology consists of IFC with only MSP1+1/APS1+1/ELP:

When an Ethernet IFM which is used as the primary interface of an ELP group is changed, the
“Duplicate mac address risk” fault is set active if the ELP group is using a MAC address that
is not the MAC address of the currently installed primary interface.
Refer to 8600 Ethernet Configuration Guide, chapter 'MAC Address'.

RSVP path protected LSPs switchovers on different cards are handled automatically without
specific user actions using normal RSVP path failure detection logic and recovery mechanisms. It is
assumed that both RSVP paths are functional during this upgrade.

B.1. If MSP#W is in the same IFC as RSVP LSP#Py, the following steps are required:

NOTE! It is assumed that RSVP LSP#S is carried over IFC#Pt.

76.8660-50169C 8600 Smart Routers SR6.0

51
7 Non-Service Affecting Software Upgrade

1. Due to a delay with a new routing configuration at IFC reload, it is recommended to set RSVP
Protection Primary path links administratively down to IFC#W interfaces. This operation will
guarantee that IP routed traffic will really move to the protecting path. There may be a short
traffic break due to RSVP switching to the secondary path. There will be a fault reported about
RSVP primary path down.
2. Reboot IFC#W (the working side interface of the protected pair) with the new ESW version
There should be NO traffic break.
3. Wait until IFC#W is "UP AND RUNNING" so that the protection status is ok for all.
4. Do manual switchover to switch all protected interface traffic to IFC#W (to the working side
interfaces of the protected pairs). There will be a short traffic break, ideally the break lasts at
maximum what standards allow on switchovers.
5. Perform RSVP primary path interface link from down to up state after the IFC#W is in up and
running state. This will cause RSVP LSP to switch from the secondary path to the primary path.
There may be a short traffic break due to RSVP switching to the primary path. The reported
RSVP primary path down fault will be removed.
6. Reboot IFC#Pt (the protecting side interface of the protected pair) carrying the RSVP secondary
LSP path. There should be no effect on traffic and RSVP LSPs when IFC#Pt is booted There
will be a fault reported about the RSVP secondary path down. RSVP LSP and MSP should be
using the primary path/working link existing in IFC#W.
7. Wait until IFC#Pt is "UP AND RUNNING" so that the protection status is ok for all. The
reported RSVP secondary path down fault will be removed.
8. Reboot the rest of the IFC#W one by one as described in steps 1–5 in this list B.1.
9. Reboot the rest of the IFC#Pt one by one as described in steps 6–7 in this list B.1.
B.2. If MSP#W is in same IFC as RSVP LSP#S, the following steps are required:

NOTE! It is assumed that RSVP LSP#P is carried over IFC#Pt.

1. Reboot IFC#W (the working side interface of the protected pair) with the new ESW version
There should be NO traffic break since the RSVP path which should be in the primary path is
not affected. There will be a fault reported on the RSVP secondary path down. There is no need
to administratively shutdown the RSVP LSP#S links.
2. Wait until IFC#W is "UP AND RUNNING" so that the protection status is ok for all. The
reported RSVP secondary path down fault will be removed.
3. Do a manual switchover to switch all protected interface traffic to IFC#W (to the working side
interfaces of the protected pairs). There will be a short traffic break, ideally the break lasts at
maximum what standards allow on switchovers.
4. Due to a delay with a new routing configuration at IFC reload, it is recommended to set the
RSVP protection primary path links administratively down to the IFC#Py interfaces. This op-
eration will guarantee that IP routed traffic will really move to the protecting path. There may
be a short traffic break due to RSVP switching to the secondary path. There will be a fault
reported about the RSVP primary path down.
5. Reboot IFC#Pt (the protecting side interface of the protected pair) or IFC#Py carrying the RSVP
primary LSP path. There should be no effect on traffic and RSVP LSPs when IFC#Pt is booted.
6. Wait until IFC#Pt is "UP AND RUNNING" so that the protection status is ok for all.
7. Perform RSVP primary path interface link from down to up state after the IFC#Py is in up and
running state. This will cause RSVP LSP to switch from the secondary path to the primary path.
There may be a short traffic break due to RSVP switching to the primary path. The reported
RSVP primary path down fault will be removed.

8600 Smart Routers SR6.0 76.8660-50169C

52
7 Non-Service Affecting Software Upgrade

8. Reboot the rest of the IFC#W one by one as described in steps 1–3 in this list B.2.
9. Reboot the rest of the IFC#Pt one by one as described in steps 4–7 in this list B.2.
B.3. If MSP pairs are in different IFC to RSVP LSP pairs, the following steps are required:

1. Reboot IFC#W (the working side interface of the protected pair) with the new ESW version
There is no traffic cut on the protected interfaces, because all traffic is flowing through the
protecting side interfaces.
2. Wait until IFC#W is "UP AND RUNNING" so that the protection status is ok for all.
3. Do manual switchover to switch all protected interface traffic to IFC#W (to the working side
interfaces of the protected pairs). There will be a short traffic break, ideally the break lasts at
maximum what standards allow on switchovers.
4. Reboot IFC#Pt (the protecting side interface of the protected pair) with the new ESW version.
There is no traffic cut on the protected interfaces, because all traffic is flowing through the
working side interfaces.
5. Wait until IFC#Pt is "UP AND RUNNING" so that the protection status is ok for all.
6. Reboot the rest of the IFC#W one by one.
7. Reboot the rest of the IFC#Pt one by one.
8. Due to a delay with a new routing configuration at IFC reload, it is recommended to set the
RSVP protection primary path links administratively down to IFC#Py interfaces. This opera-
tion will guarantee that IP routed traffic will really move to the protecting path. There may be a
short traffic break due to RSVP switching to the secondary path. There will be a fault reported
on the RSVP primary path down.
9. Reboot IFC#Py carrying RSVP path-protected primary paths.
10. Wait until IFC#Py is "UP AND RUNNING".
11. Perform RSVP primary path interface link from down to up state after the IFC#Py is in up and
running state. This will cause RSVP LSP to switch from the secondary path to the primary path.
There may be a short traffic break due to RSVP reverting to the primary path.
12. Reboot IFC#S carrying RSVP path protected secondary paths. There should be NO traffic
break since the RSVP path is in the primary path. There will be a fault reported on the RSVP
secondary path down.
13. Wait until IFC#S is "UP AND RUNNING". The reported RSVP secondary path down fault
will be removed.
14. Reboot the rest of the IFC#Py one by one.
15. Reboot the rest of the IFC#S one by one.

76.8660-50169C 8600 Smart Routers SR6.0

53
8 Upgrading Cards

8 Upgrading Cards
Refer to 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 4 Operations Before Upgrade and 10 Restoring Previous FP and
Configuration in Case of Upgrade Failure.

8.1 Upgrading CDC1 to CDC2

In 8630 Smart Router and 8660 Smart Router with CDC-1+1 protection, CDC1-A or CDC1-B cards
can be replaced with CDC2-B cards. During the 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!

Refer to 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

8600 Smart Routers SR6.0 76.8660-50169C

54
8 Upgrading Cards

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
router# protection manual-switchover unit cdc 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 in OK state.
Unit 1 is active.
Unit 1 has no switch command active.
Unit 1 has noRequest switch type.
Unit 1 is non-revertive.
Unit 1 is a protecting unit.
Protection group of unit 1 has 1 working units: 14.
Protection group of unit 1 has 1 protecting units: 1.
Protection group of unit 1 is of type: 1+1.
Protection group of unit 1 is named: cdc.
Step 5 Shutdown slot 14.
router# esw-shutdown slot 14
Step 6 When the red and yellow LEDs (local and remote alarm) of CDC1 slot 14 are blinking, you can
remove the card according to instructions in the 8600 Smart Routers Hardware Installation Guide.
Step 7 Change the needed cable types (Serial interface/Alarm I/O, SCO/SCI, power cable) of the CDC
in slot 14.
Step 8 Insert CDC2 to slot 14 according to the 8600 Smart Routers Hardware Installation Guide.
CDC2 must have the same ESW version active as the rest of the cards have.
Step 9 Wait until CDC2 in slot 14 is up and running
router#show hw-inventory slot 14 details
unit in slot 14 is part of inventory and UP AND RUNNING
upgrade-state cdc1-cdc2: not upgradeable
…

76.8660-50169C 8600 Smart Routers SR6.0

55
8 Upgrading Cards

Step 10 Switch CDC and MFE activity to slot 14

router# protection manual-switchover interface mfe slot 14
router# protection manual-switchover unit cdc 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 in OK state.
Unit 14 is active.
Unit 14 has no switch command active.
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 in OK state.
Unit 1 is passive.
Unit 1 has noRequest switch type.
Unit 1 is non-revertive.
Unit 1 is a protecting unit.
Protection group of unit 1 has 1 working units: 14.
Protection group of unit 1 has 1 protecting units: 1.
Protection group of unit 1 is of type: 1+1.
Protection group of unit 1 is named: cdc.

After the switchover command, the CDC1 in slot 1 might initiate automatic reboot to
synchronize configuration with the new CDC2. If reboot happens before executing step 5 to
slot 1, wait until slot 1 is up and running again after the reboot:
router#show hw-inventory slot 1
unit in slot 1 is part of inventory and UP AND RUNNING

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

Step 12 NE configuration is allowed again.

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 8660 Smart Router Reference Manual, 8630
Smart Router Reference Manual and 8600 Smart Routers Hardware Installation Guide.

8.2 IFC1 to IFC2 Upgrade

In 8630 Smart Router and 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.

8600 Smart Routers SR6.0 76.8660-50169C

56
8 Upgrading Cards

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 8000 intelligent network manager, the upgrade permission must
be set in the 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
2x1000BASE-X IFM 8x100/1000BASE-X R2 IFM
8x1000BASE-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-4/OC-12 POS IFM
• 1xSTM-16/OC-48 POS IFM
• 4xSTM-1/OC-3 ATM IFM
• 1xchSTM-1/chOC-3 Multiservice IFM
• 4xchSTM-1/chOC-3 Multiservice IFM
• 24xchE1/chT1 Multiservice IFM

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!

76.8660-50169C 8600 Smart Routers SR6.0

57
8 Upgrading Cards

Check the current IFC upgrade state, e.g.

router# show hw-inventory details

unit in slot 6 is part of inventory and UP AND RUNNING
upgrade-state ifc1-ifc2: can be upgraded, but not yet
permitted
...
unit in slot 7 is part of inventory and UP AND RUNNING
upgrade-state ifc1-ifc2: not upgradeable
...
unit in slot 8 is part of inventory and UP AND RUNNING
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 8.2.1 Service Affecting Upgrade of IFC1 to
IFC2 and Non-Service Affecting Upgrade8 for instructions.

8.2.1 Service Affecting Upgrade of IFC1 to IFC2

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 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
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.

8Ch. 2.7.2, ‘Non-Service Affecting Upgrade’, is included in ‘8600 Smart Routers FP3.1 Embedded Software Release Notes’ (document ID 76.8631-
50146).

8600 Smart Routers SR6.0 76.8660-50169C

58
8 Upgrading Cards

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 8600 Smart Routers
FP3.1 Embedded Software Release Notes (document ID 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
8x100BASE-X IFM 8x100/1000BASE-X R2 IFM

Step 1 Perform IFC1 to IFC2 upgrade for all needed card slots in the network elements according to
previous step lists, 8.2.1 Service Affecting Upgrade of IFC1 to IFC2 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.

8.2.2 Non-Service Affecting Upgrade of IFC1 to IFC2

Non-service affecting upgrade of IFC1 to IFC2 cards is not supported in 8600 Smart Routers FP5.0 SP1 GA.
Refer to 8600 Smart Routers FP3.1 Embedded Software Release Notes (doc. ID 76.8631-50146), ch. 2.7.2, for the
procedure.

76.8660-50169C 8600 Smart Routers SR6.0

59
9 ESW Upgrade with Downgrade Support for 8602 Smart Router and 8615 Smart Router

9 ESW Upgrade with Downgrade Support for

8602 Smart Router and 8615 Smart Router
8602 Smart Router and 8615 Smart Router ESW update procedure with 8000 Intelligent Network
Manager, which includes the option to revert back to the original ESW version, is described below.

Step 1 Make sure that a valid 8000 Intelligent Network Manager database backup exists. For more
information see 8000 Intelligent Network Manager Maintenance Procedures.
Step 2 Update the new ESW version with 8000 Intelligent Network Manager tools.
1. Create a download plan with the Element Software Management tool.
• Enable the option Create node configuration backup before ESW update in the Prop-
erties tab.
• Disable the option Version update for EMS data in the Properties tab.
• Otherwise the default options can be used.
2. Update the new ESW version in the network elements by activating the download plan.
• A new ESW version is downloaded to the network elements.
• The new ESW is activated in the network elements.
• The backup is copied to 8000 Intelligent Network Manager database with the file name
EswUpdate.
Step 3 Check that the network elements work properly with the new ESW version.

The network elements should not be configured during this monitoring period. 8000
Intelligent Network Manager data in the database may get inconsistent because the version
update has not been performed.

8600 Smart Routers SR6.0 76.8660-50169C

60
9 ESW Upgrade with Downgrade Support for 8602 Smart Router and 8615 Smart Router

Step 4 A) If the updated network elements work properly, the update must be committed by finalizing the
ESW update in 8000 Intelligent Network Manager.
• ‘Version update’ must be performed separately with 8600 Node Manager for every node in
the download plan.

After version update the only way to revert back to the original configuration is to restore the
8000 Intelligent Network Manager database backup.

B) If the new ESW version does not work properly, run rollback.
• Activate the previous ESW version in the ESW Management dialog in 8600 Node Man-
ager. Do not reset the network element!
• Download the EswUpdate snapshot file in the Node Configuration Backup dialog in 8600
Node Manager.
• Restore the EswUpdate file in the Node Configuration Backup dialog.
• When the snapshot is restored successfully, the network element will restart and boot the
previous application software with the restored configurations.
• After completing the rollback in the network elements, 8000 Intelligent Network Manager
will work again without restrictions.

76.8660-50169C 8600 Smart Routers SR6.0

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

10 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.

10.1 Restoring Previous FP and Configuration in Case of Upgrade

Failure in 8602 Smart Router and 8609 Smart Router

Procedure 1

Step 1 Remove all unused ESW files from all cards.

router# delete flash: *
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.
8602 Smart Router
router(config)# boot system flash: sbz2755_x.y.z
restore-config reload
8609 Smart Router:
router(config)# boot system flash: sbz2751_x.y.z
restore-config reload
Procedure 2

If procedure 1 cannot be used for some reason, the NE level snapshot configuration must be restored
(see chapter 4 Operations Before Upgrade). Before restoring, previous FP ESW package must be
activated.

Step 1 Remove all unused ESW files from all cards.

router# delete flash: *
Step 2 Download the previous ESW package to the NE.

8600 Smart Routers SR6.0 76.8660-50169C

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

Step 3 Activate the previous ESW.

NOTE: In the file name 'x.y.z' refers to the ESW version number of the previous FP.
8602 Smart Router
router(config)# boot system flash: sbz2755_x.y.z
8609 Smart Router:
router(config)# boot system flash: sbz2751_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>
The NE is automatically reloaded after the CLI command above.

10.2 Restoring Previous FP and Configuration in Case of Upgrade

Failure in 8611 Smart Router, 8615 Smart Router, 8630 Smart
Router and 8660 Smart Router

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.

router# delete slot * flash: *
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.
router(config)# boot system slot 2 flash: pkg_8611_x.y.z
restore-config reload
router(config)# boot system slot 14 flash: pkg_8615_x.y.z
restore-config reload
router(config)# boot system slot 14 flash: pkg_8660_x.y.z
restore-config reload
Procedure 2

Step 1 Remove all unused ESW files from all cards.

router# delete slot * flash: *
Step 2 Download the previous ESW package to the NE.

76.8660-50169C 8600 Smart Routers SR6.0

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

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 slot 2 flash: pkg_8611_x.y.z
router(config)# boot system slot 14 flash: pkg_8615_x.y.z
router(config)# boot system slot 14 flash: pkg_8660_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.

8600 Smart Routers SR6.0 76.8660-50169C

64
11 SR6.0 Features

11 SR6.0 Features
This chapter lists the 8600 system features introduced in the 8600 Smart Routers SR6.0 release.
Refer to 8600 Smart Routers Product Definition documents for further information.

Feature Support Related 8600 Smart Routers

Technical Document
8615 Smart Router 8615 8615 Smart Router Reference Manual
(76.8660-40117A)
8615 Smart Router Product Definition
(76.8660-40107A)
Synchronization Configuration Guide
(76.8600-50114H)
Network Interfaces Configuration Guide
(76.8600-50161B)
Ethernet Configuration Guide
(76.8600-50133J)
Hardware Installation Guide
(76.8600-40039L)
Labeled BGP ELC1, CDC1, MPLS Configuration Guide
CDC2, 8602, 8609 (76.8600-50123E)
BGP signaled PSN tunnel for IP ELC1, 8602, 8609 MPLS Configuration Guide
VPN (76.8600-50123E)
BGP signaled PSN tunnel for ELC1, 8602, 8609 MPLS Configuration Guide
Ethernet PWE3 (76.8600-50123E)
Inter-AS VPN option C IFC1, IFC2, ELC1, MPLS Configuration Guide
CDC1, CDC2, (76.8600-50123E)
8602, 8609, 8611
ETH PWE3 to IPoPPP IFC1, IFC2 8600 Smart Routers FP5.0 Interface
interworking ARP support Configuration Guide (76.8660-50170A)
8602.1ad QinQ interface ELC1 Ethernet Configuration Guide
(76.8600-50133J)
8600 Smart Routers FP5.0 Interface
Configuration Guide (76.8660-50170A)
IEEE1588 L2 Boundary Clock IFC2 Synchronization Configuration Guide
(IFC2 interfaces) (76.8600-50114H)
IEEE1588 L2 Slave (IFC2 IFC2, CDC2 Synchronization Configuration Guide
interfaces) (76.8600-50114H)
IEEE1588 L2 Master 8615 Synchronization Configuration Guide
(76.8600-50114H)
1G Ethernet Link Aggregation ELC1 Ethernet Configuration Guide
802.1AX (76.8600-50133J)
8600 Smart Routers FP5.0 Interface
Configuration Guide (76.8660-50170A)
Terminal Access Controller CDC1, CDC2, Management Communications
Access-Control System 8602, 8609, 8611 Configuration Guide (76.8600-50125F)
(TACACS+)

76.8660-50169C 8600 Smart Routers SR6.0

65
11 SR6.0 Features

Feature Support Related 8600 Smart Routers

Technical Document
10G Ethernet Link Aggregation ELC1 Ethernet Configuration Guide
802.1AX (76.8600-50133J)
8600 Smart Routers FP5.0 Interface
Configuration Guide (76.8660-50170A)
VLAN group shaping for multiple ELC1 IP Forwarding and Traffic Management
VLANs Configuration Guide (76.8600-50122H)
Ethernet MAC switching 8602, 8609, 8611, Ethernet Configuration Guide
8615 (76.8600-50133J)
QoS aware flooding in MAC ELC1 Ethernet Configuration Guide
switching and VPLS (76.8600-50133J)
8602 Smart Router 8602-D 8602-D 8602 Smart Router FP1.1 Reference
Manual (76.8660-40120A)
Synchronization Configuration Guide
(76.8600-50114H)
Network Interfaces Configuration Guide
(76.8600-50161B)
Ethernet Configuration Guide
(76.8600-50133J)
8602 Smart Router FP1.1 Product
Definition (76.8660-40114A)
Hardware Installation Guide
(76.8600-40039L)
SyncE and ELP capable electrical IFC2, ELC1, 8602 8600 Smart Routers FP5.0
100/1000BASE-TX SFP support Interface Configuration Guide
(76.8641-50170A)
Network Interfaces Configuration Guide
(76.8600-50161B)
Synchronization Configuration Guide
(76.8600-50114H)
Hardware Installation Guide
(76.8600-40039L)
IEEE1588 (L2) and SSM support IFC2, ELC1, 8609, Synchronization Configuration Guide
on LAG member links 8611 (76.8600-50114H)
IEEE1588 L3 Frequency ELC1, CDC2 Synchronization Configuration Guide
Synchronisation Slave (76.8600-50114H)
100M Electrical SFP support 8602 Hardware Installation Guide
(76.8600-40039L)
802.1AX Link Aggregation IFC2, ELC1, 8602, Ethernet Configuration Guide
Control Protocol (LACP) 8609, 8611 (76.8600-50133J)

8600 Smart Routers SR6.0 76.8660-50169C

66
12 Application Software

12 Application Software

12.1 Version SR6.0 SP1 GA (Application SW Version .308)

76.8660-50169C 8600 Smart Routers SR6.0

67
68

Embedded Software Release Notes

8600 Smart Routers SR6.0

12 Application Software
Application Embedded Software Codes
Network Element Card Baseboard ESW Current ESW Version Previous GA Level ESW
Version
8602 Smart Router SBB2305 SBZ2755 1.1.308 (FP1.1 GA) 1.0.163 (FP1.0 SP1)
8609 Smart Router SBB2284 SBZ2751 2.0.308 (FP2.0 GA) 1.2.629 (FP1.2 SP2) and 1.3.163
(FP1.3 SP1)
8611 Smart Router SCM SCM2265 SBZ2748 2.0.308 (FP2.0 GA) 1.2.629 (FP1.2 SP2) and 1.3.163
(FP1.3 SP1)
8615 Smart Router VID9109 CBZ2764 1.0.308 (FP1.0 GA) —
SBB2306 LBZ2765 1.0.308 (FP1.0 GA) —
8630 Smart Router CDC1 CBB2026 CBZ2712 5.0.308 (FP5.0 GA) 4.1.629 (FP4.1 SP2)
8660 Smart Router
CDC2 CBB2300 CBZ2745 5.0.308 (FP5.0 GA) 4.1.629 (FP4.1 SP2)
ELC1 ELC2269 LBZ2754 5.0.308 (FP5.0 GA) 4.1.629 (FP4.1 SP2)
IFC1 LBA2024 LBZ2713 5.0.308 (FP5.0 GA) 4.1.629 (FP4.1 SP2)
IFC2 LBA2250 LBZ2741 5.0.308 (FP5.0 GA) 4.1.629 (FP4.1 SP2)
76.8660-50169C
© 2014 Coriant.
12 Application Software

12.1.1 Enhancements in SR6.0 SP1 GA

cq300244168 CDC1, IFC1
Enhancements to Queue stuck workaround to allow configurable amount of
consecutive Queue Manager (QM) resets without network element resets and
infinite length for the workaround. The user is allowed to:
- set manually the number of consecutive QM resets until the unit is rebooted,
using command:
"debug sw slot X set brdd QMRRECOVERYREBOOT=0xffffffff", where
0xffffffff=no reboots
- to set infinite length for QM workaround), using command:
"debug sw slot X set bsdip QMRFAILSECS=0xffffffff"

12.1.2 Fixed Bugs in SR6.0 SP1 GA

cq300195694 8609 NE, 8611 NE
ATM OAM Rx cells are not counted correctly on IMA interfaces.
Impact: The OAM Rx counter is always zero.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300218766 8611 NE
When a VC interface is removed from a VCG group, followed by a change in the
ATM usage value, which is then followed by a deletion of the VC interface itself,
some error messages appear on the console in addition to some unexpected errors
messages. This seems to happen after a few protection switches.
Impact: Some error messages appear on the console and an unexpected error is
seen when this happens.
scm1 console error message:
------------------------------------
8611-89>AtmcdDeleteVxCtpConnection:TrhwdrDeallocateLinkId(iLink=65512)
failed, rc=4097, instId(0x64016000 0x405a0500)
Finished AtmcdDeleteVxCtpConnection rc=4097
scm2 console error message:
------------------------------------
AtmcdDeleteVxCtpConnection:TrhwdrDeallocateLinkId(iLink=65512) failed,
rc=4097, instId(0x64016000 0x805a0500)
Finished AtmcdDeleteVxCtpConnection rc=4097
Risk of occurrence: This seems to happen only after a few switchovers, when the
sequence mentioned above is followed.
Workaround: When the SCM is reloaded, the interface is deleted properly.

cq300238805 CDC1
In case of very heavy SW load, internal communication fails temporarily and
causes SW reboot.
Impact: Network element reboot and restart.
Risk of occurrence: Very rare.
Workaround: Not available.

76.8660-50169C 8600 Smart Routers SR6.0

69
12 Application Software

cq300244214 ELC1
There has been a short IRB traffic drop at a 60 s interval. 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.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300248924 IFC2, IFC1

When removing the Alias interface after switchover from the Primary to the Alias
path, the data traffic is not resumed in the Primary path when the Primary PWE3
is UP again.
Impact: Data loss is observed when the Primary PWE3 is UP.
Workaround: Deleting the PWE3 from the alias interface before removing
the alias interface, will help the traffic to recover when the Primary interface is
recreated.

cq300249041 ELC1
If the SLI ports vlan mode is changed more than once, the port will go to shutdown
state.
Impact: The SLI will drop all the traffic.
Risk of occurrence: Always under the described circumstances.
Workaround: Give shut/no shut down command to the port after the VLAN
mode is changed.

cq300249735 IFC2, ELC1

When upgrading slot1 of CDC1 control card to CDC2 control card, IFC2 line
cards (and in very rare cases IFC1 line cards) may get an 'Expected module not
activated.' alarm for a few seconds. Also in the network element that is already
upgraded to CDC2 control cards, if performing 'reset-hw slot 1' to the passive
CDC2 the same issue may appear.
Impact: Traffic is cut for approximately 2 seconds for each IFC2 line card that
suffers from the issue.
In rare cases IFC1 line cards may be affected as well.
Risk of occurrence: Sometimes.
Workaround: Not available.

cq300249985 8611 NE, 8609 NE, 8602 NE

Ethernet OAM delay measurement ping times out, if a MEP configured on MAC
switching interface is supposed to reply to the dm-ping.
Impact: No impact to other traffic, only dm-ping will not work.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

8600 Smart Routers SR6.0 76.8660-50169C

70
12 Application Software

cq300250023 8611 NE, 8609 NE, 8602 NE

The number of static MAC forwarding entries supported in the network element
is higher than what is required. The required number of static MAC forwarding
entries is 512 for 8609 Smart Router and 8611 Smart Router and 256 for 8602
Smart Router.
Impact: The user is able to configure more static MAC rules than what will be
supported in the next release, which means there will be an upgrade issue.
Risk of occurrence: Always under the described circumstances.
Workaround: Avoid configuring more static MAC forwarding entries as
mentioned, in order to avoid future upgrade issues.

cq300250052 8615 NE, CDC2

Station Clock Output (SCO) port cannot be set to 2048 kHz mode, in case the
unit is in ANSI mode.
Impact: Adjacent NEs cannot be synchronized via SCO port in case the signal
must be 2048 kHz.
Risk of occurrence: Always under the described circumstances.
Workaround: Set the SCO (and the port taking the timing from it) to 1544 kHz
mode.

cq300250135 8611 NE
During active SCM reset using 'reload-sw / reset-hw' command with passive SCM
up and running, TX laser state of all the interfaces are turned OFF, which leads to
traffic loss. The laser state remains turned OFF until a complete node reset is done.
Impact: Traffic loss will occur.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300250430 ELC1
When AggregateStat for specific QoS is enabled/disabled and an attempt is made to
enable/disable SingleTaggedStat/CvlanStat QoS, the SingleTaggedStat/CvlanStat
counters will be cleared and vice versa.
Impact: The SingleTaggedStat/CvlanStat statistics counter values will be lost.
Risk of occurrence: Always under the described circumstances.
Workaround: When the QoS is/are enabled before traffic is sent, there will be no
impact on the counters.

cq300250436 8615 NE, ELC1

If ACL space in the network element gets full or nearly full, the deletion of ACL
rules occasionally fails.
Impact: Deletion of ACL rule is not possible.
Risk of occurrence: Occasionally.
Workaround: Create another ACL rule with the desired changes. Detach the
original rule from an interface and attach the changed rule to the interface.

cq300250579 IFC2
As a result of SW upgrade on the network element, a data cut may occur on the
connections using VLAN group shaper on VLAN PWE trunks for which a type
AF3 or AF4 vc-qos is configured.
Impact: Live traffic will be cut off on the connections having the configuration
depicted above.
Risk of occurrence: Always under the described circumstances.
Workaround: Unbinding VLAN group shaper from a trunk VLAN by entering
the ‘no service-shaper-group <nameOfShaperGroup>‘ command will restore data
flow and if group shaping is required, one can then bind it back.

76.8660-50169C 8600 Smart Routers SR6.0

71
12 Application Software

cq300250604 IFC2
As a result of SW upgrade on the network element, VLAN statistics will be
disabled, although according to the running configuration they are enabled.
Impact: Entering the 'show int <VLAN interface>' command will indicate that
VLAN statistics are not collected.
Risk of occurrence: Always under the described circumstances.
Workaround: Re-enable VLAN statistics with the 'vlan statistics non-qos in-qos'
command.

cq300250898 8602 NE, 8611 NE, 8609 NE

If BPDU filtering, i.e. dropping BPDU frames in switching interface ingress, is
enabled the receiving BPDU frame will lead into reboot of the network element.
Impact: The BPDU filtering option cannot be enabled,
Risk of occurrence: Always under the described circumstances
Workaround: Not available.

cq300250934 8602 NE, 8609 NE, 8611 NE

The network element may reset spontaneously if IEEE1588 slave is provisioned
with VRF and this VRF is deleted before removing IEEE1588 configuration.
Impact: All services are affected.
Risk of occurrence: Frequently.
Workaround: Remove all IEEE1588 configuration with VRF associations before
deleting the VRF.

cq300251149 8609 NE, 8602 NE, 8611 NE

Memory leaks are observed on the 8602, 8609 and 8611 Smart Routers when
invalid ETHOAM packets like LBM, LBR, LTM, LTR, etc. of large size (more
than 1500B) are received. This memory leak will cause the system either to crash
or all protocols to go down.
Some of the error scenarios are described below:
1. Packet received when the interface down
2. Wrong SA or DA MAC in packet
3. Invalid ETHOAM header.
Impact: 1. Complete traffic outage.
2. All protocols will be down.
3. No CLI responses.
Risk of occurrence: Only when packets of large size are received in the above
mentioned scenarios.
Workaround: Not available.

12.2 Version SR6.0 CIR2 (Application SW Version .244)

12.2.1 Enhancements in SR6.0 CIR2

cq300213123 8611 NE, 8609 NE, 8602 NE
The 'ifAlias' object does not allow 8000 Intelligent Network Manager to give one
or more interfaces their own unique names and it returns an empty string.

8600 Smart Routers SR6.0 76.8660-50169C

72
12 Application Software

cq300244714 IFC1, IFC2

The enhancement displays/removes corrupted bundles and members.
To find corrupted MLPPP members, the command "show debugging sw
mlppp-find-phantom-members [mp<module/if>]" was introduced. This will
display the corrupted MLPPP members either per unit or per MLPPP bundle.
To remove the corrupted MLPPP bundles/members, the command "debug sw
mlppp-remove-phantom-members mp<module/if>[pdh<unit/module/if>]" was
introduced. This will remove phantom members from a particular MP bundle
or the corrupted bundle itself.

cq300245083 8609 NE, 8611 NE, 8602 NE, ELC1

IPv4 VPN traffic over MPLS network was not distributed since hashing was based
only on MPLS labels for LAG interface. To correct this, traffic hashing logic was
changed to consider both MPLS labels and IP header fields.

cq300245571 8609 NE, 8602 NE, 8615 NE, CDC2

Previously, IEEE1588 master clock statistics for each interface had to be cleared
separately. A new option was added for clearing all with one command.

cq300245851 8609 NE, 8602 NE, CDC2, 8615 NE

When the network element is using ieee1588 'mac-multicast' mode, the selected
port is now specified in 'show node-timing ieee1588 slave' CLI printouts.

cq300245852 8609 NE, 8602 NE, 8615 NE, CDC2

Added a new 'brief' option to CLI command 'show node-timing ieee1588 clock-if'.
It shows all active L2 PTP clock interface statuses:
show node-timing ieee1588 clock-if brief
Interface Port Mode Port State Asymm. Mac Address
Corr.
ge0/0 auto listening 20 011b.1900.0000
ge1/0 auto slave 0 011b.1900.0000

12.2.2 Fixed Bugs in SR6.0 CIR2

cq300116238 CDC1, 8609 NE, 8611 NE, CDC2
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.
Workaround: Not available.

cq300126508 CDC1, 8609 NE, 8611 NE, CDC2

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.
Risk of occurrence: Always under the described circumstances.
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.

76.8660-50169C 8600 Smart Routers SR6.0

73
12 Application Software

cq300160637 IFC2, ELC1

When an Ethernet interface is ELP protected and you remove with 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.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300184995 CDC1, 8609 NE, 8611 NE

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.

cq300194305 IFC1, IFC2

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.
Risk of occurrence: Always under the described circumstances.
Workaround: Delete the n-to-1 pseudowire configuration and then reconfigure it.

cq300203507 CDC1, CDC2, 8609 NE, 8611 NE, 8602 NE

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.
Risk of occurrence: Low.
Workaround: Disable FTP and CLI (Telnet/SSH) when there is no need to use
them.

8600 Smart Routers SR6.0 76.8660-50169C

74
12 Application Software

cq300211086 CDC1, 8611 NE, 8609 NE, ELC1, IFC1, IFC2, CDC2, 8602 NE, 8615 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.

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.
Impact: It does not affect live traffic.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300232115 IFC2, IFC1

The following Ethernet modules do not support Equipment loopback:
- 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).
Impact: It does not affect live traffic.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300235115 ELC1, 8615 NE

Unknown unicast MAC flooding has a performance issue in ELC1 and 8615 Smart
Router 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.

cq300238671 CDC2
When upgrading CDC2 to a different ESW version, MFE packet loss is observed.
Impact: Management traffic may get affected.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300241791 CDC2
CS7 ping with size 65000 fails when traffic is sent at full bandwidth.
Impact: It does not affect live traffic.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

76.8660-50169C 8600 Smart Routers SR6.0

75
12 Application Software

cq300243766 CDC1, IFC1, IFC2, ELC1, 8611 NE, 8609 NE, 8602 NE
In a very rare scenario, due to corrupted IP packet, both the control unit and the
line card unconditionally reboot.
Impact: Service outage due to network element reload.
Risk of occurrence: Very rare.
Workaround: Not available.

cq300243829 8602 NE
When the user tries to ping the loopback interface IP address or back to back
connected interface IP address, the first ping packet fails with a timeout error. The
first ping command fails only if the source IP address is specified as an option.
Impact: The first ping packet alone will fail with a timeout error.
Risk of occurrence: Rare.
Workaround: The ping command should not specify any option.

cq300243925 ELC1, 8615 NE

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.
Workaround: Not available.

cq300244509 CDC2
In 8630 Smart Router and 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.
Impact: It does not affect live traffic.
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 up to 5700 is successful.
Impact: EOAM UP MEP will go down with LoC state.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300244763 ELC1
Multicast replication due to flooding in VPLS network transient situations may
exceed the ELC1 with IRB forwarding performance of 10 Mbps causing the unit
to reboot and traffic to be cut. Fourfold replication of unknown destination and
unicast traffic may exceed the 20 Gbps 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.

8600 Smart Routers SR6.0 76.8660-50169C

76
12 Application Software

cq300245274 CDC1, CDC1, IFC1, 8609 NE, 8611 NE

While executing PPP related commands/configuration of PPP attributes via BMI,
no proper error codes are given for error scenarios.
Impact: It does not affect live traffic.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300245307 8615 NE
LAN connected interface (RX Unicast) counters will display very high values.
Impact: LAN connected interface will not display correct RX unicast count.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300245385 CDC1, CDC2

Longer than expected packet loss (10-30 ms) is seen in BGP Labeled Unicast
signaled network during manual CDC control card switchover in 8630 Smart
Router or 8660 Smart Router. Usually the first manual CDC control card
switchover operation takes longer than the consecutive switchovers.
Impact: Longer than expected packet loss is observed (10-30 ms).
Risk of occurrence: Always when manual CDC control card switchover is
performed in 8630 Smart Router or 8660 Smart Router.
Workaround: Not available.

cq300245500 CDC1, CDC2, 8611 NE, 8609 NE

When RADIUS authentication is configured for higher priority with the 'order'
CLI command under AAA context, the system erroneously proceeds to the next
possible authentication method on the list even if RADIUS authentication denies
access.
The correct behavior with the described configuration is such that local user
database authentication is attempted only if connection to the RADIUS server fails.
Impact: Authentication with local user database is always attempted if it exists in
the authentication order list, even if it is not configured as highest priority.
Risk of occurrence: Always if ESW version is at least
- FP1.1 SP1 (1.1.215) for 8609 and 8611 Smart Router
- FP4.1 ECE1 (4.1.71) for 8630 and 8660 Smart Routers.
Never with older ESW versions.
Workaround: Not available.

cq300245562 CDC2, CDC1

During the CDC switchover, the VLAN statistics value for the last one minute
duration is not updated to the database and therefore, VLAN statistics on an
interface will lose the packet count value for upto a duration of one minute, after a
CDC switchover.
Impact: If a CDC switchover happens, VLAN statistics on an interface will miss
counting the traffic for up to one minute duration.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300246121 CDC1
The passive CDC may reload if multiple (>180) attempts to connect and
disconnect to the MPLS-TP tunnels are made iteratively.
Impact: Traffic gets affected in the tunnel that is down.
Risk of occurrence: Rare.
Workaround: The automatic switchover to the passive control card will help
in this case.

76.8660-50169C 8600 Smart Routers SR6.0

77
12 Application Software

cq300246710 CDC2, CDC1, 8615 NE

If the destination port is used in a load balancing algorithm, IP traceroute results
are likely to be incorrect.
Impact: It does not affect live traffic.
Risk of occurrence: Nearly always under the described circumstances.
Workaround: Not available.

cq300246711 8609 NE
8609 Smart Router does not respond to ping request after some time from node
bootup.
Impact: Control packets destined to CPU processing will be affected.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300246841 8615 NE
The amount of L2 IEEE1588 capable ports is limited to 14. Supported ports are
xe13/0/0...1 and ge13/1/0...11.
Impact: L2 IEEE1588 service cannot be provisioned to non-supported ports.
Risk of occurrence: Always under the described circumstances.
Workaround: Use ports xe13/0/0...1 and/or ge13/1/0...11.

cq300247480 8615 NE
EEC noise transfer bandwidth cannot be changed from the CLI. The correct
bandwidth (G.8262 Opt.1/Opt2) is set according to the network element
operation mode (ETSI/ANSI) and, therefore, the issue is limited to non-standard
configurations.
Impact: It does not affect live traffic.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300247526 8602 NE, 8609 NE

The phase synchronization quality is poor during the initial setup of IEEE1588
L2 master. This happens with both PPS and GNSS inputs. After the initial setup
is completed and the master is locked to a phase/time source, the issue is not
repeated, even if the phase/time source is subsequently lost.
Impact: Poor phase synchronization quality during the first 2 minutes of master
operation.
Risk of occurrence: Always under the described circumstances.
Workaround: Keep the PTP interfaces disabled until the IEEE1588 master has
locked to PPS/GNSS. After this (approx. 2 minutes), set the required interfaces
to master mode.

cq300247537 8609 NE, 8602 NE, 8611 NE, 8609 NE

BGP labeled unicast sessions are not re-established after the failed link is restored
between the network elements, when the number of prefix received by BGP is
around 8000 in 8609 Smart Router and 8611 Smart Router.
Impact: BGP labeled unicast session will not be established.
Risk of occurrence: Always under the described circumstances.
Workaround: Prefix count received by BGP should be 7900 or less.

cq300247643 8615 NE
ACL host statistics (show ip access-list in/out host statistics) do not show the
correct value.
Impact: ACL host statistics (MO:ipHostAccessListStat) are not shown
correctly.This is statistics issue, does not affect traffic.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

8600 Smart Routers SR6.0 76.8660-50169C

78
12 Application Software

cq300247687 CDC1, CDC2

After creation of Flexible IRB interface for a bridging instance, if configure the
same MAC for the same bridging instance, removal of bridging MAC will remove
the IRB MAC also.
Impact: Traffic loss for IRB interface will be seen during that period.
Risk of occurrence: Always under the described circumstances.
Workaround: Delete and recreate the Flexible IRB interface or add static MAC
for the same bridging instance on which IRB interface is created.

cq300247923 8615 NE
The station clock input (SCI) port of 8615 Smart Router stays in failed state if the
network element is in the ANSI operating mode.
Impact: NE cannot be synchronized via SCI if the unit is in ANSI operating
mode and the unit is not rebooted again.
Risk of occurrence: Always under the described circumstances.
Workaround: Reboot the unit again after changing the timing mode.

cq300247982 8615 NE
Unexpected "NPXD error" messages may be seen in console when shutdown or
shutdown-if is issued while traffic is running.
Impact: Has only minor impact. Unexpected messages take space in the os-log.
Risk of occurrence: Occures often, at the moment when traffic forwarding
is stopped due to various reasons (a link goes down, a connection goes down,
manual configuration, etc).
Workaround: Not available.

cq300248013 ELC1
Scenario: two VLANs for a physical interface (say 'VLAN1_ID:100' and
'VLAN2_ID:200') are created. The primary pseudowires are attached to both these
VLANs. The secondary pseudowires are attached to the alias interfaces of those
two VLANs. When the traffic is sent via both the VLANs with their primary
pseudowires up, the VLAN statistics for 'VLAN2_ID:200' resets to zero.
Impact: It does not affect live traffic.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300248031 8609 NE, 8611 NE, 8602 NE

MAC switching SLI uses layer2-frame to map ingress PRI to internal QoS instead
of the default DSCP which would result in BE internal QoS. The 'vpls-qos'
command can be used to define fixed internal QoS but 'qos vlan ingress vlan-pri'
command does not work. The customer should be determining the use of
layer2-frame for internal QoS to override the default DSCP, and both 'vpls-qos'
and 'qos vlan ingress' should be available for fixed ingress internal QoS definition
per SLI.
Impact: The MAC switching ingress QoS behaviour is not in line with the system
QoS principles, and this may cause confusion when compared to earlier default
configuration.
Risk of occurrence: Always under the described circumstances.
Workaround: If the fixed QoS BE resulting from default DSCP use is required,
the 'vpls-qos be' command can be used.

76.8660-50169C 8600 Smart Routers SR6.0

79
12 Application Software

cq300248078 ELC1
When QinQ interface is configured in an ELC1 line card with ELP enabled and all
statistics are enabled (in-qos, out-qos and non-qos for aggregate, VLAN single
tagged and CVLAN), the CVLAN Tx statistics may show an incorrect/junk value
(~2^64).
Impact: Only the CVLAN Tx statistics is incorrect, but there will be no impact on
the QinQ functionality.
Risk of occurrence: Inconsistently.
Workaround: Deleting and recreating the ELP protection group will resolve
the issue.

cq300248148 8615 NE, ELC1

IEEE1588 L2 message mode (one-step/two-step) has an invalid value in the slave
statistics.
Impact: It does not affect live traffic.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300248281 CDC1, CDC2, 8611 NE, 8609 NE, 8602 NE

If RSVP soft update occurs in LSP path and the transit NE’s (network
element) upstream interface changes (incoming interface), the downstream
interface (outgoing) stays the same. The transit NE does not update the
downstream direction in such a case. The result is a missing forwarding label on
the outgoing interface.
The following conditions must be fulfilled:
1. The topology must be such that the destination can be reached via the affected
transit NE with multiple upstream paths where the outgoing interface does not
need to change.
2. There must be the type of failure where the upstream NE notices LSP failure
(e.g. link down or timeout) but downstream does not notice it.
a. Sub-cases may be caused by certain types of packet drops, asymmetric packet
drops, etc., as long as the end-result is that upstream notices the failure, but ptear
message does not get received by downstream and downstream does not notice
the situation.
3. Upstream (either the ingress or transit) must signal LSP with the same LSP ID
(and most of the other parameters too), the new path must "cross" the old one
on the affected NE and must have same downstream on the affected NE. This
re-signaling must occur before the state expires from the affected transit NE.
Impact: Traffic using the affected RSVP tunnel will stop flowing. No additional
alarm or failure notifications are generated by the issue. Also, the RSVP tunnel
configuration is normal and tunnel status is up.
Risk of occurrence: Always under the described circumstances.
Workaround: Strict paths:
RSVP should be configured to change LSP ID on resignaling.
“change-lsp-id-on-resignal" in the router RSVP configuration mode.
Loose paths:
Enabling CSPF for RSVP will change the loose hops to strict hops. Thereafter, the
above preventive action for RSVP tunnels with strict hops will prevent the issue.
PPN ID: 14043

8600 Smart Routers SR6.0 76.8660-50169C

80
12 Application Software

cq300248295 8615 NE
MTU (Maximum Transmission Unit) of a link connected to 8615 Smart Router
shall not be configured above 3000 bytes.
Impact: Forwarding plane getting stuck has been observed when 8615 Smart
Router is congested with a large amount of jumbo frame traffic.
Risk of occurrence: High under the described circumstances.
Workaround: When MTU > 3000 is needed, the number of 1000Base Ethernet
ports used with MTU > 3000 shall be limited to 12.

cq300248413 ELC1, 8615 NE

In case of Ethernet VLAN PWE3, in the PSN->AC direction, if the pwe3 data
packet has VLAN tag and when there are no explicit Ethertype configurations,
default Ethertype value of 0x8100 is used for the outgoing tagged packet instead
of using the Ethertype of the vlan tag that is present in the incoming packet.
Impact: The packet will have incorrect Ethertype. Ethertype of the vlan pwe3
packet is overwritten with the default Ethertype value of 0x8100 when no explicit
Ethertype configurations are made.
Risk of occurrence: Always under the described circumstances.
Workaround: Explicit Ethertype configurations to configure the outgoing desired
Ethertype for the vlan tag can be made using the command:
eth ethertype egress <ether-type>

cq300248438 CDC2, CDC1, 8615 NE

cq300248799 IFC1, IFC2

Show ip interface error statistics may show incorrect values in 8000 Intelligent
Network Manager, while CLI shows the correct value (0).
Impact: It does not affect live traffic.
Risk of occurrence: Sometimes.
Workaround: Use CLI.

cq300248824 8615 NE
8615 Smart Router Packet Loop Tester (PLT) transmitter side causes CLI to be
inaccessible.
Impact: PLT transmitter is not recommended to be used in 8615 Smart Router.
Risk of occurrence: Always under the described circumstances.
Workaround: Open another Telnet session to get access to CLI.

76.8660-50169C 8600 Smart Routers SR6.0

81
12 Application Software

cq300248832 8602 NE, 8609 NE

If GNSS SFP is configured as node-clock source and configurations are removed
and then added again, GNSS does not work as node-clock source.
Impact: Removing and adding the following GNSS configurations will cause
node-clock not to lock to GNSS source:
node-timing gnss interface ge5/0
node-timing gnss enable
node-timing ieee1588 master clock-source gnss
node-timing clock-source gnss priority 1
Risk of occurrence: Always under the described circumstances.
Workaround: If the user needs to remove and reconfigure GNSS as node-clock
source, they can set GNSS mode to Glonass and then back to GPS to go around
the problem. Also reboot helps.

cq300248885 8609 NE, 8611 NE

When the network element is reloaded with the 'reload-sw' command, in some
cases there is a delay of 7 - 30 sec before interface lasers are turned off. As a
result, the other end notices link down slowly in the reload case.
Impact: The other end should see links go down immediately when the network
element is reloaded.
Risk of occurrence: Moderate.
Workaround: Lasers can be manually turned off with CLI before issuing the
'reload-sw' command.

cq300248892 ELC1
ELC1 packet storm detection and isolation feature (feature ID F00283) is not
detecting storms and thus not recommended to be used.
Impact: ARP or IS-IS packet storms in some VLAN interfaces may block
processing of ARP or IS-IS messages from well-behaving interfaces.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300248899 8615 NE
8615 Smart Router packet storm detection and isolation feature (feature ID
F00508) is not detecting storms and thus not recommended to be used.
Impact: ARP or IS-IS packet storms in some VLAN interfaces may block
processing of ARP or IS-IS messages from well-behaving interfaces.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300248907 ELC1
ELC1 VLAN shaping attached to the switching side of IRB (Integrated Routing
and Bridging) is not working after CDC switchover or ELC1 reload.
Impact: Traffic is passing by the VLAN shapers, i.e., it is not shaped.
Risk of occurrence: High.
Workaround: If VLAN shaping is reconfigured after CDC switchover or ELC1
reload, it will work again.

cq300249073 8609 NE, 8602 NE, 8611 NE

MAC addresses of L2 PTP frames may get corrupted in case the 8600 port is in
master mode and Sync messages are received from another master.
Impact: Adjacent NEs may learn hundreds of MAC addresses, PTP connection
between the master ports does not work properly.
Risk of occurrence: Happens after several hours of operation.
Workaround: Not available.

8600 Smart Routers SR6.0 76.8660-50169C

82
12 Application Software

cq300249079 8609 NE, 8615 NE, CDC2, 8602 NE

IEEE1588 L2 boundary clock (or grandmaster clock) announces PTP clock
accuracy to be 100 ns while it is recovering from time holdover. The correct value
should be 'unknown' until the clock is locked again.
Impact: This clock may be selected by adjacent 1588 clocks although 1588 clocks
with better clock accuracy value may be available.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300249104 CDC1, CDC2, 8611 NE, 8609 NE, 8602 NE

INM consistency check fails for IP route map objects.
Impact: Consistency check from INM to an 8600 network element fails for IP
route map.
Risk of occurrence: Always when consistency check is performed from INM for
an 8600 network element having IP route maps.
Workaround: Avoid database consistency check with IP route maps.

cq300249124 8602 NE, 8609 NE

The longitude coordinates may be incorrectly displayed with the CLI command
"show node-timing gnss". This is just a display issue and has no impact on
synchronization quality or the positioning function of the GNSS (GPS) SFP.
Impact: It does not affect live traffic.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300249327 8609 NE, 8611 NE, CDC1, ELC1, IFC1, IFC2, CDC2, 8602 NE, 8615 NE
BGP route reflection leaks memory used for cluster list attribute. At minimum,
about 68 bytes per route reflected advertisement is leaked (depending on similarity
of peers advertised to, this may or may not be multiplied by the number of peers).
The issue has been present since SR5.0 SP2.
Impact: The network element will eventually run out of memory.
Risk of occurrence: Always when performing route reflection.
Workaround: Not available.

cq300249854 8609 NE, 8611 NE, 8602 NE

Ethernet OAM ping to the peer UP MEP randomly fails as the request times out, if
the UP MEP replying to the ping is a MAC switching interface. For example, if
the ping is initiated for 100 packets, then 2 or 3 replies may time out randomly.
Impact: It does not affect live traffic.
Risk of occurrence: Random.
Workaround: Not available.

cq300249980 8615 NE
When broadcast storm is detected in the network, it is incorrectly reported: storm
alarm is turned on and off repeatedly.
Impact: This is only seen when there is a netowrk misconfiguration which causes
a broadcast storm. The resulting alarm should be seen as constantly on, but is now
turned on and off repeatedly.
Risk of occurrence: High.
Workaround: Broadcast storm alarm turning repeatedly on and off should be
interpreted to equal a continuous broadcast alarm.

76.8660-50169C 8600 Smart Routers SR6.0

83
12 Application Software

cq300249981 8611 NE, 8609 NE, 8602 NE

When MIP and UP MEP are configured on the same network element on the
switching interface, the ping or traceroute destined to the UP MEP will not work.
Impact: Ping/traceroute does not work in the situation described.
Risk of occurrence: Occurs only when MIP and UP MEP are on the same VSI.
Workaround: Configuring static MAC rule with the MAC address of VSI AC
with UP MEP configured on it will solve the issue.

12.3 Version SR6.0 CIR (Application SW Version .103)

12.3.1 Enhancements in SR6.0 CIR

cq300227545 CDC1, CDC2, 8611 NE, 8609 NE, 8602 NE
When IP TTL expires, the source IP address of the ICMP error message is
chosen based on the incoming interface, when available. This gives more useful
information for traceroute, for example, when a network topology has asymmetric
routes between network elements.

cq300241286 CDC1, CDC2, 8611 NE, 8609 NE, 8602 NE

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

12.3.2 Fixed Bugs in SR6.0 CIR

cq300171590 CDC1, 8609 NE, 8611 NE, CDC2
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.
Risk of occurrence: Low.
Workaround: Not available.

cq300193476 8609 NE, 8611 NE

In 8609 Smart Router and 8611 Smart Router, for VLAN interface, the 'show
interface' command displays values in Rx priority counters and Tx counters though
they are not supported. Discarded L3 packets counter displays always value 0.
Impact: It does not affect live traffic.
Risk of occurrence: Always, when the 'show interface' command is executed.
Workaround: Not available.

cq300198107 CDC1, IFC1, IFC2, ELC1, 8611 NE, 8609 NE

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.
Risk of occurrence: Always under the described circumstances.
Workaround: Make names unique with the first 48 characters.

8600 Smart Routers SR6.0 76.8660-50169C

84
12 Application Software

cq300225036 8609 NE, 8611 NE, 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 more likely to happen 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.

cq300227967 CDC1, 8602 NE

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.
Impact: It does not affect live traffic.
Risk of occurrence: Very rare.
Workaround: Not available.

cq300228864 IFC1, IFC2, 8611 NE, 8609 NE, 8602 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.
Workaround: Not available.

cq300228901 CDC1, 8609 NE, 8611 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.
Risk of occurrence: Always under the described circumstances.
Workaround: Do not use PHP in one hop configurations.

cq300231487 IFC2, ELC1, IFC1

Ethernet port that has had Stacked-VLAN configuration is not usable for normal
use until the unit is rebooted.
Impact: No control traffic in Ethernet port or its VLANs if the port has earlier
had Stacked-VLAN interfaces.
Risk of occurrence: Always under described circumstances.
Workaround: Reboot the line card that had Stacked-VLAN configuration.

76.8660-50169C 8600 Smart Routers SR6.0

85
12 Application Software

cq300232005 8611 NE, 8609 NE, 8602 NE

Interface queue statistics show higher packet counts than what the actual traffic
amount is.
Impact: Although traffic will flow successfully, the interface queue statistics
will not show the correct packet count.
Risk of occurrence: Occasionally.
Workaround: Not available.

cq300232238 CDC1, CDC2, 8611 NE, 8609 NE, 8602 NE

The wrong error code ('target unit not responding') is returned to 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.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300232810 CDC1, IFC1, IFC2, ELC1

When the IRB interface is deleted, the network element software may access
some memory that has already been freed. This may result in spontaneous reset
or memory corruption.
Impact: The network elements may reset immediately or memory corruption
may occur.
Risk of occurrence: Very low.
Workaround: Not available.

cq300234841 CDC1, CDC2, 8611 NE

VLAN priority marking is transiently disabled for control card originated control
packets (OSPF, IS-IS, 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 control card 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.
Workaround: Not available.

cq300235064 8611 NE
SNMP shows each interface twice. This can be seen in different MIBs (e.g.
interfaces, ATM). This is because in dual SCM environment, both SCMs fetch the
SNMP data and hence data is displayed twice for all the interfaces.
Impact: It does not affect live traffic.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

8600 Smart Routers SR6.0 76.8660-50169C

86
12 Application Software

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.
Risk of occurrence: Always under the described circumstances.
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.

cq300238176 IFC1
Packets that have no entry on the NHOP table on IFC1 line card may get
duplicated in the HW. The duplicated packets have ended up on an IRB ELP link
connecting two 8660 Smart Router or 8630 Smart Router. Such packets have no
Ethernet header so they cause phantom MAC entrys in the MAC table.
Impact: False MAC entries are seen on the MAC table of the other 8660 Smart
Router or 8630 Smart Router.
Risk of occurrence: Occasionally. The triggering phenomenon is not known.
Workaround: Not available.

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.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300240030 8611 NE, 8609 NE, 8602 NE

Some interfaces displayed with the CLI command 'show interface ?' are not
supported on the system.
Impact: It does not affect live traffic.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300240874 IFC1, IFC2

When Laser OFF/ON command or manual switchover is tried multiple times
continuously (more than 30 iterations) in a protected interface which contains
instances belonging to an MLPPP interface, traffic loss is observed in the MLPPP
interface.
Impact: Traffic loss will be observed.
Risk of occurrence: Always under the described circumstances.
Workaround: Either give 'shutdown' and 'no-shutdown' commands on the
affected MLPPP interface or perform manual switchover again.

76.8660-50169C 8600 Smart Routers SR6.0

87
12 Application Software

cq300241150 CDC1, IFC1, IFC2

CDC1 control card might reset spontaneously when several IFC line cards send
statistics data in parallel to the CDC1.
Impact: If the CDC1 control card is protected, live traffic is not affected. But if
the CDC1 control card is not protected, the whole network element will reboot,
affecting live traffic.
Risk of occurrence: Rare.
Workaround: Disable periodic statistics collection using the CLI command
'debug sw ista periodic disable' in 8630 Smart Router/8660 Smart Router if the
CDC1 is not protected.

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.
Impact: It does not affect live traffic.
Risk of occurrence: Always under the described circumstances.
Workaround: Either add the unit back to inventory or remove it from the rack.

cq300241465 CDC1
When a large amount of 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: 8000 Intelligent Network Manager dialogs will open slower than
expected. CLI command execution will experience delay (200-400 ms).
Risk of occurrence: Always under the described circumstances.
Workaround: If possible, reduce 8000 Intelligent Network Manager statistics
polling.

cq300242280 CDC1, CDC2

When LAG configuration exists in the network element, bundled LAG messages
are being sent out from CDC control card periodically. When the network element
has LAG groups configured in such a way that the bundled LAG message size
exceeds the actual message size that it is able to send, the message is discarded
without releasing the already allocated memory. As the messages are sent out
periodically, memory consumption will start incrementing until the system
memory is exhausted.
Impact: As long as system memory is available, there is no impact on traffic.
If the system memory gets exhausted, the impact can be observed on traffic, as
dynamic protocols are disabled automatically.
Risk of occurrence: The issue might not be observed always in the presence of
LAG configuration but with a matching amount of LAG groups with particular
number of members in each group cases, this issue can be observed always under
the described circumstances.
Workaround: By creating/deleting LAG/LAG VLAN and/or changing the
number of members of LAG, so that the LAG message size will not exceed the
actual allocated message size.

cq300243115 IFC1, IFC2

During upgrade or reload, if the protecting line card is active and there are scalable
SATOP/CESoP PWE3 configurations with MSP protection, it is possible that
PWE3 configurations will not come up or the read of PWE3 parameters such as
jitter buffer or PWE3 AC detection will fail.
Impact: Traffic hit will be observed if the PWE3 is down.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

8600 Smart Routers SR6.0 76.8660-50169C

88
12 Application Software

cq300243478 CDC1, CDC2, 8611 NE, 8609 NE

Routemap delete is not possible if the map is emptied and less than 30 seconds has
passed since the last BMI/CLI operation.
Impact: It does not affect live traffic.
Risk of occurrence: Always under the described circumstances.
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 8000 Intelligent Network Manager, the right
interface information cannot be mapped.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300243533 CDC2
Username must contain at least 6 characters (exception username:root, in linux
environment). But in CDC2 control card, non-root username which is less than 6
characters are also accepted when configured using the 8000 Intelligent Network
Manager.
Impact: Username less than 6 character is accepted using the 8000 Intelligent
Network Manager.
Risk of occurrence: Whenever CDC2 control card is used and user name less
than 6 character is configured.
Workaround: Not available.

cq300243760 CDC1, CDC2

'MiscCommonTaskStartRemoteService failed' is written to os-log without a cause
in 8660 Smart Router and 8630 Smart Router.
Impact: It does not affect live traffic.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300243950 8602 NE
On the 8602 Smart Router, 8602-A variant electrical ports performing a 'no
shutdown-if' when the port's line state is up, a Link Down fault will post and clear.
Impact: Users will see the Link Down post and clear after a 'no shutdown-if'.
Since traffic is already down because the port is shutdown, there is no outage.
Risk of occurrence: High, but traffic on the network element is unaffected.
Workaround: Not available.

cq300243977 8611 NE
IS-IS graceful restart may fail if one of the connected devices does not support
IS-IS graceful restart.
Impact: When an SCM redundancy switch occurs, all IS-IS routes drop and
re-establish about 30 seconds after the switch completes.
Risk of occurrence: High, 2 out of 10 times of switchover attempt.
Workaround: Ensure that all adjacent IS-IS speakers utilize IS-IS graceful restart.

76.8660-50169C 8600 Smart Routers SR6.0

89
12 Application Software

cq300244423 ELC1
Full ELC1 capacity of 25 Gbps is not supported for ELC1 with IRB. ELC1 IRB IP
interface has a forwarding performance limitation of 10 Mpps (Million packets
per second), which supports a maximum 20 Gbps bidirectional traffic when the
average packet size is 250 bytes.
Impact: Packets are dropped with no QoS consideration, if the 10 Mpps 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 10 Mpps
egress traffic rate on the ELC1 IRB interfaces on single line card.

cq300244460 CDC1
Configuring equipment loopback ("loopback to-equipment") on a non-tunneled
LAG interface will not be succesful, as equipment loopback can be configured
only on a tunneled interface.
But later if a CDC control card switchover is performed, the configuration on this
LAG interface will show as if equipment loopback is configured.
Impact: This will not affect functionality, but only the display result will
provide wrong information, stating that equipment loopback is configured on a
non-tunneled interface.
Risk of occurrence: Always under the described circumstances.
Workaround: Reconfigure the loopback configuration to the desired mode to
solve the issue.

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.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300244557 ELC1
SLI mode change between VLAN AC and trunk AC on the fly causes traffic cut
on the SLI.
Impact: Traffic-affecting.
Risk of occurrence: Always under the described circumstances.
Workaround: Performing shutdown/no shutdown operation on the interface is
required before traffic starts flowing again.

cq300244660 IFC1, CDC1

In 4xchSTM-1/chOC-3 Multiservice IFM (LIO2234) in IFC1 line card: when large
ATM configurations of around 252 ATM interfaces are configured with PWE3
redundancy and there are 251 ATM VCG (Virtual Circuit Group) with 12 members
each, the line card will take a long time to bootup (more than 17 minutes).
Impact: It does not affect live traffic.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

8600 Smart Routers SR6.0 76.8660-50169C

90
12 Application Software

cq300244711 CDC2
When routes are retrieved and are filtered so that more than one route type is
included but not all routes, the result set contains also some of the ECMP routes
partially filled.
Impact: It does not affect live traffic.
Risk of occurrence: Always under the described circumstances.
Workaround: Either filter with one route type only or retrieve all routes.

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.
Risk of occurrence: Low.
Workaround: Avoid using these commands during and right after a CDC
switchover.

cq300244782 CDC1, CDC2, 8611 NE

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

cq300244967 ELC1
VLAN tag is not added in PWE3(VLAN) egress direction(PSN-->AC) with
encapsulaton type Ethernet-VLAN and the untagged mode is configured.
Impact: PWE3 egress traffic will be corrupted or incorrect. The VLAN tag will
be missing in the egress traffic.
Risk of occurrence: Always under the described circumstances.
Workaround: Use the "ethernet untagged" mode instead of the "ethernet-vlan
untagged" mode.

cq300245099 ELC1
Application ESW upgrade from FP4.1 CIR1 (4.1.182) to FP4.1 SP1 (4.1.586) may
fail in ELC1 line card.
Impact: ESW in ELC1 line card will not be upgraded
Risk of occurrence: Sometimes
Workaround: Not available.

cq300245210 CDC1
When upgrading 8630 and 8660 Smart Router from FP4.1 SP1 GA to FP4.1
SP1.1 FL (4.1.586 --> 4.1.587) or 8609 and 8611 Smart Router from FP1.3 CIR
to FP1.3 CIR1.1 FL (1.3.102 --> 1.3.103), the VCCV states of MS-PW circuits
may remain down.
Impact: A set of VCCV-BFD enabled MS-PWE3 circuits is not forwarding after
the specified ESW upgrade.
Risk of occurrence: Always under the described circumstances.
Workaround: Disconnect and re-connect MS-PWE3 to get PWE3 up and running.

76.8660-50169C 8600 Smart Routers SR6.0

91
12 Application Software

cq300245365 CDC1, CDC2, 8611 NE, 8609 NE, 8602 NE

IPv4 Echo Reply from the NE may contain an incorrect source address, namely
127.0.0.1, if the corresponding Echo Request was sent to a broadcast address.
Impact: No impact on live traffic. Ping tests may show incorrect results.
Risk of occurrence: Always with certain ESW versions.
Workaround: Use normal IPv4 unicast addresses as ping targets.

cq300245383 CDC1, CDC2

The newly passive CDC may go to spontaneous reset immediately after CDC
switchover.
Impact: It does not affect live traffic.
Risk of occurrence: Rare.
Workaround: Not available.

cq300245423 CDC1, CDC2, 8611 NE

RSVP-TE tunnels may flap during CDC switchover due to having different
LSP-IDs in the active and the passive CDC.
Impact: Traffic via RSVP-TE LSPs may be transiently interrupted on CDC
switchover.
On nodes with excessive loads, this may cause additional load spikes, potentially
leading to other issues.
Risk of occurrence: Depends on LSP ID ranges assigned by SW and
re-optimization parameters. Option change-lsp-id-on-resignal increases the risk
significantly.
Workaround: Not available.

cq300245501 8609 NE
The pull-in range of adaptive timing (ACR) is limited to +/-10 ppm instead of the
required +/-50 ppm for E1 and +/-32ppm for T1 interfaces. In other words, an
ACR enabled E1/T1 port cannot track the remote-end input frequency if it deviates
more than 10 ppm from the nominal E1/T1 frequency.
Impact: This does NOT impact mobile backhaul, as its timing must be PRC
traceable (0 ppm offset from nominal).
In other applications, the SAToP/CESoP data will be dropped periodically, if
the E1/T1 service timing deviates more than 10 ppm from the nominal E1/T1
frequency.
Risk of occurrence: Always
Workaround: Not available.

cq300245516 ELC1
When a slot containing an ELC1 with EOAM DOWN MEP configured is rebooted
immediately after a reconfiguration of the MEP attributes, the fault status shown
it does not match the exact fault status. This does not happen, in a normal
reconfiguration scenario and happens only after a slot reload is done after a
reconfiguration. It is not a recommended procedure as well.
Impact: The fault status shows the LoC as the fault but the actual fault is RDI.
There is a mismatch in the actual fault on the line and the fault shown.
Risk of occurrence: Always under above circumstances
Workaround: Reload immediately after the reconfiguration is to be avoided.
Also a reload before the reconfiguration of the MEP, if needed, would not get the
node into this situation.

8600 Smart Routers SR6.0 76.8660-50169C

92
12 Application Software

cq300245725 8611 NE
RSVP trace route does not function and returns error.
Impact: The RSVP trace route command cannot be used to check connectivity
over the RSVP-TE tunnels. Data traffic is not affected.
Risk of occurrence: Always.
Workaround: Not available.

cq300245902 8609 NE, 8602 NE

GNSS fault reporting does not work properly without 'node-timing ieee1588
master clock-source gnss' or another 'node-timing ieee1588 master clock-source...'
command.
Impact: Without a 'node-timing ieee1588 master clock-source ...' command,
GNSS faults are not shown properly and GNSS will not work properly either.
Risk of occurrence: Always under the described circumstances.
Workaround: The user needs to add 'node-timing ieee1588 master clock-source
gnss' or other node-timing ieee1588 master clock-source command.

cq300245934 ELC1
For an ELC1 interface configured in fixed mode (Eth autonegotiation is disabled)
random noise generation will be observed on an interface when the link is down.
This results in link state flapping. If this interface is part of FBL, this will also
result in Sync source flapping.
Impact: Random SSM message transmission will be observed and there will be
flapping in the Sync source, as a result of which the Sync functionality will be
affected.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300245952 ELC1
The IEEE1588 Delay Response message does not contain the same correction
value as the Delay Request.
Impact: The network element is not correctly synchronized (IEEE1588).
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300246566 8609 NE, 8602 NE

The announce interval and timeout are not correctly calculated when the Announce
packet rate is more than 1 pps.
Impact: Network element synchronization is affected.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300246583 8609 NE, 8602 NE, ELC1, CDC2

The boundary clock continues to send Announce messages with the old GM data
and therefore the sync flow direction does not change properly.
Impact: The slave connected to the boundary clock does not select a new master
clock as the announce messages contain the old GM data.
Risk of occurrence: Always, if the packet rate of the announce messages is
more than 1 pps.
Workaround: Not available.

76.8660-50169C 8600 Smart Routers SR6.0

93
12 Application Software

cq300246699 CDC1, CDC2, IFC2

The 'shutdown' command for IFC/IRB resets IRB's IP MTU back to the default
value 1500.
Impact: Jumbo frames (>1500) do not pass after the interface has been in
shutdown state.
Risk of occurrence: Always under the described circumstances.
Workaround: Delete and recreate IRB.

cq300246834 8609 NE, 8602 NE

The compensation value for GNSS antenna signal propagation delay has no effect
in the HW. This compensation is critical to do for phase/time sync applications
(+/-100 ns requirement, while 1 meter of cable will cause 4-5 ns error).
Impact: With very strict phase/time synchronization budget (e.g., LTE-A) and the
lack of compensation may cause too much static error for the end application.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300247170 CDC1, CDC2, IFC1, IFC2, ELC1

During service affecting ESW upgrade card(s) might not be able to boot up after
reset. It might stop waiting for start permission, e.g.:
router#show hw-inventory slot 5
unit in slot 5 is part of inventory and WAITING FOR START PERMISSION
-->UNIT START PERMISSION DENIED!
-->WRONG ESW VERSION! POSSIBLE RESET-LOOP: OPERATOR
ACTIONS NEEDED!
1) Autoloader: card is running wrong ESW version
expected SW: IFC1_4.1.586
active SW is wrong: IFC1_4.1.625 ...
Impact: Live traffic through the card is stopped until the card successfully boots
up.
Risk of occurrence: Rarely
Workaround: Workaround 1: When activating ESW PKG, do not use 'reload'
option in "boot system slot <slot#> flash" command. Execute the command first,
then wait at least 30 seconds, and finally use reload-sw command to finalize
upgrade.
Workaround 2: If a card cannot get start permission after an upgrade, activate
ESW again for the given card "boot system flash slot N flash: <sw-name> reload"
where N is a slot number of the problematic card and <sw-name> is the new
ESW on that card.

cq300247442 8609 NE, 8602 NE

The MAC address of the Delay Request messages are corrupted.
Impact: The reverse flow of the 1588 phase sync does not work. The 1588 is
not locked to the master clock.
Risk of occurrence: Seldom.
Workaround: Not available.

cq300247622 CDC1, CDC2

After upgrading from FP4.0 to FP4.1 IFC2 IRB may fail to resolve ARPs until the
network element is rebooted.
Impact: IFC2 IRB does not always resolve ARPs after software upgrade from
FP4.0 to FP4.1.
Risk of occurrence: Frequently
Workaround: Reboot the node second time after the boot up with FP4.1 software
is completed.

8600 Smart Routers SR6.0 76.8660-50169C

94
12 Application Software

cq300247672 CDC1, CDC2

Replacement of the ELC1 line card with a spare line card may cause reload of
the CDC control cards if the spare line card has different ESW version than the
replaced line card.
Impact: In case both CDC control cards reset at the same time, replacing the
ELC1 line card will cause traffic cut.
Risk of occurrence: Rarely.
Workaround: Before plugging the replacement line card into the NE, make sure
that it is running the same ESW version as the replaced line card.

76.8660-50169C 8600 Smart Routers SR6.0

95
13 Restrictions in 8600 Smart Routers SR6.0

13 Restrictions in 8600 Smart Routers SR6.0

The issues listed in this section may require special attention during network configuration and
troubleshooting sessions.

For installation related restrictions, refer to chapter 5 Upgrade Related Notifications.

13.1 Common Restrictions in SR6.0

General (8602 FP1.1; 8609 and 8611 FP2.0; 8615 FP1.0; 8630 and 8660 FP5.0)

• Using RSVP-TE hellos is not recommended. Instead, BFD should be used for RSVP-TE neighbor
liveliness detection. Small RSVP hello timers are especially harmful, as RSVP hellos are not
executed on real-time process (BFDs are) and are susceptible to timeouts during load spikes.
Synchronization (8602 FP1.1; 8609 and 8611 FP2.0; 8615 FP1.0; 8630 and 8660 FP5.0)

• In SR6.0, 8600 Smart Routers implement a pre-standard version of the ITU-T G.8275.1 (Preci-
sion time protocol telecom profile for phase/time synchronization with full timing support from
the network, July 2014). Consequently some timing parameters are subject to change in a future
software release. In addition to this, there are these known restrictions:
• In the current IEEE1588v2 Boundary Clock implementation, defaultDS parameters prior-
ity1 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 ac-
count when building synchronization topologies consisting of both Coriant 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.
• PTP Announce message rate is 1 pps instead of the 8 pps required by G.8275.1. This how-
ever has no impact on the achievable synchronization quality.
• It is not recommended to use GLONASS operating mode on the GNSS SFP. While the
GLONASS now has global coverage, and also the accuracy has improved to almost GPS
levels, it is still not accurate and stable enough for network synchronization purposes. In-
stead the default setting (GPS) is preferred. (Restriction in all 8602 and 8609 feature packs.)
• IEEE1588 Packet Delay Variation (PDV) statistics do not work with L2 IEEE1588 clocks
(boundary, master, or slave). Querying the statistics will fail with an 'instance not found'
error.
• 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. (Restriction in 8630 and 8660 FP5.0 only.)

8600 Smart Routers SR6.0 76.8660-50169C

96
13 Restrictions in 8600 Smart Routers SR6.0

Traffic Management (8602 FP1.1; 8609 and 8611 FP2.0)

• When the flood of control packets received is more than 600 pkts per second, the remaining
packets, i.e. the packets exceeding the 600 limit will be dropped in the host rate limiter. Due to
this some control packets will get missed. BFD sessions may flap due to this host packet drop.
(CR ID cq300234582)

76.8660-50169C 8600 Smart Routers SR6.0

97
13 Restrictions in 8600 Smart Routers SR6.0

BGP Labeled Unicast (S-MPLS) (8602 FP1.1; 8609 and 8611 FP2.0; 8630 and 8660
FP5.0)

• Product Support
• 8611 Smart Router and 8615 Smart Router not supported
• 8630 Smart Router/8660 Smart Router: IFC1 and IFC2 not supported on the trunk side
• 8630 Smart Router/8660 Smart Router: IFC1 not supported on the AC side
• 8630 Smart Router/8660 Smart Router: Multi Service IFMs not supported on the AC side
IFC2.
• Services
• Ethernet port mode PW, ATM PW, TDM PW, HDLC PW, FR PW over BGP-LU tunnels not
supported
• VPLS, Ethernet switching, VSI, IRB services over BGP-LU tunnels not supported
• IEEE 1588 frequency syncronization over BGP-LU routed IP VPN not supported
• LDP signaled LSPs for BGP-LU tunnels not supported
• MPLS short pipe QoS model for services using BGP-LU tunnels not supported
• BGP multipath for BGP Labeled Unicast routes not supported
• Features not supported when associated to BGP-LU service:
• AC and Trunk interfaces
• ELP and ETH OAM service not supported
• Trunk interfaces
• QinQ service not supported
• Feature concurrency restrictions on AC interfaces
• LAG.

13.2 8602 Smart Router FP1.1 Specific Restrictions

Features or Functionalities Not Supported in 8602 FP1.1

• The following types of optical 1000M SFPs:

• 1000BASE-EX singlemode 1310nm 40km
• 1000BASE-ZX singlemode 1550nm 70km
• 1000BASE-CWDM singlemode 70km
• Optical 100M SFPs
• 10BASE-T mode in fixed (RJ-45) ports
• MPLS-TP functionality.
Note: See also ch. 13.1 Common Restrictions in SR6.0 for other 8602 Smart Router FP1.1 related
restrictions.

8600 Smart Routers SR6.0 76.8660-50169C

98
13 Restrictions in 8600 Smart Routers SR6.0

13.3 8609 Smart Router and 8611 Smart Router FP2.0 Specific
Restrictions

• In 8609 Smart Router the use of GPS (GNSS) SFP requires NE hardware version R2 Rev. B or
later.
• In 8611 Smart Router LAG is not supported in 10G Ethernet interfaces.
Note: See also ch. 13.1 Common Restrictions in SR6.0 for other 8609 Smart Router and 8611
Smart Router FP2.0 related restrictions.

13.4 8615 Smart Router FP1.0 Specific Restrictions

• 8615 Smart Router has a limitation with ACL rule hit statistics (CR ID cq300247643) preventing
to retrieve statistics counters even though statistics collection is enabled. This limitation exists
both in interface ACLs and host ACLs. Executing statistics retrieval command fails at command
execution (no statistic are seen). The actual ACL rules work as configured.
• 8615 Smart Router ingress RSVP-TE protection scalability is limited to 900 RSVP-TE tunnel
pairs.
• 8615 Smart Router Packet Loop Tester (PLT) supports only throughput test type.
Note: See also ch. 13.1 Common Restrictions in SR6.0 for other 8615 Smart Router FP1.0 related
restrictions.

13.5 8630 Smart Router and 8660 Smart Router FP5.0 Specific
Restrictions

• Cross connect error condition (XCONE) will not be detected if the remote MEP (RMEP) is al-
ready discovered in the local MEP (LMEP) and the entry is not aged out. Also if an XCONE
condition occurs, while the RMEP is in discovered state, the entry will not age out as long as
there are packets coming from the RMEP.
According to definition, XCONE error is detected when a MEP receives a CCM with an
incorrect maintenance association identifier (MAID) as the first packet when auto discovery is
enabled. But if incorrect MAID is received while the RMEP entry is still active, the EOAM
implementation in IFC2 considers this as a valid packet for RMEP and continues to preserve
the current state.
• Ethernet OAM DM is not supported in ELC1.
• IEEE1588 L2 grandmaster, boundary clock, or time slave cannot be used on ports belonging to
an ELP group.
Note: See also ch. 13.1 Common Restrictions in SR6.0 for other 8630 Smart Router and 8660
Smart Router FP5.0 related restrictions.

76.8660-50169C 8600 Smart Routers SR6.0

99
14 Restrictions in Releases Prior to 8600 Smart Routers SR6.0

14 Restrictions in Releases Prior to 8600 Smart

Routers SR6.0
The issues listed in this section are still valid for the feature packs mentioned and may require
special attention during network configuration and troubleshooting sessions.

For installation related restrictions, refer to chapter 5 Upgrade Related Notifications.

14.1 Common Restrictions

General (All 8600 Smart Router Feature Packs)

Using RSVP-TE hellos is not recommended. Instead, BFD should be used for RSVP-TE neighbor
liveliness detection. Small RSVP hello timers are especially harmful, as RSVP hellos are not
executed on real-time process (BFDs are) and are susceptible to timeouts during load spikes.

Synchronization (8602 FP1.0; 8609 and 8611 FP1.3; 8620, 8630 and 8660 FP4.1)

In SR5.1, 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 once 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 L2 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 Coriant 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.
• 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).
• 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.
• GNSS fault reporting does not work properly without 'node-timing ieee1588 master clock-source
gnss' or another 'node-timing ieee1588 master clock-source...' command. (cq300245902) (Re-
striction in 8602 FP1.0 and 8609 FP1.3 only.)

8600 Smart Routers SR6.0 76.8660-50169C

100
14 Restrictions in Releases Prior to 8600 Smart Routers SR6.0

• It is not recommended to use GLONASS operating mode on the GNSS SFP. While the GLONASS
now has global coverage, and also the accuracy has improved to almost GPS levels, it is still not
accurate and stable enough for network synchronization purposes. Instead the default setting
(GPS) is preferred. (Restriction in 8602 FP1.0 and 8609 FP1.3 only.)
• The ‘Gnss accuracy degraded’ fault is not fully operational yet. It is linked to the ‘Loss of signal’
fault, i.e. it comes on and is removed with the the ‘Loss of signal’ fault. (Restriction in 8602
FP1.0 and 8609 FP1.3 only.)
• The real time clock of the NE cannot be referenced from GNSS, 1PPS/ToD or IEEE1588 yet.
Note that this real time clock (typically referenced from NTP) is the one used for logging pur-
poses etc. and this limitation has no impact on the IEEE1588 timebase and/or PTP timestamp
generation. (Restriction in 8602 FP1.0 and 8609 FP1.3 only.)
• IEEE1588 Packet Delay Variation (PDV) statistics do not work with boundary clock. (Restriction
in FP4.1 only.)
• 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. (Restriction in FP4.1 only.)
Traffic Management (8602 FP1.0, 8609 and 8611 FP1.3)

14.2 8602 Smart Router Specific Restrictions

Features or Functionalities Not Supported in 8602 FP1.0

• The following types of optical 1000M SFPs:

• 1000BASE-EX singlemode 1310nm 40km
• 1000BASE-ZX singlemode 1550nm 70km
• 1000BASE-CWDM singlemode 70km
• Optical 100M SFPs
• 100Base-T mode in electrical SFP
• 10BASE-T mode in fixed (RJ-45) ports
• MPLS-TP functionality.

14.3 8609 Smart Router and 8611 Smart Router Specific Restrictions

Hardware

• In 8609 Smart Router the use of GPS (GNSS) SFP requires NE hardware version R2 Rev. B or
later. (Restriction in FP1.3.)

76.8660-50169C 8600 Smart Routers SR6.0

101
14 Restrictions in Releases Prior to 8600 Smart Routers SR6.0

Ethernet Link Aggregation

• In 8611 Smart Router LAG is not supported in 10G Ethernet interfaces. (Restriction in FP1.2 and
FP1.3.)

14.4 8630 Smart Router and 8660 Smart Router Specific Restrictions

Flexible IRB Restrictions

• IFCs cannot be part of the ELC1 based flexible mode IRB configuration at all, neither on the
bridging nor on the routing side.
• '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.
• 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.
Other Restrictions

• In 8660 Smart Router and 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.
• Ethernet OAM DM is not supported in ELC1.
• ELC1 RSVP-TE path protection switchover time may exceed 50ms, being in the order of 300ms.

8600 Smart Routers SR6.0 76.8660-50169C

102
15 Known Bugs

15 Known Bugs

cq300129850 CDC1, 8609 NE, 8611 NE, CDC2, 8602 NE

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.
Workaround: Not available.

cq300134123 CDC1, IFC1, CDC2

The number of shapers that can be associated to a VLAN is limited to 961 in an
8630 or 8660 Smart Router.

cq300136667 CDC1, IFC1, 8611 NE, 8609 NE, 8602 NE, IFC2
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.
Workaround: Not available.

cq300173356 CDC1, IFC1, IFC2, CDC2

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, 8609 NE, 8611 NE, CDC2

Adaptive jitter buffer cannot be configured correctly by using 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.
Impact: TDM PWE (CESOPSN, SATOP) traffic is impacted.
Risk of occurrence: Always under the described circumstances.
Workaround: Configure jitter buffer with CLI.

cq300194919 8609 NE, 8611 NE

Traffic is not passing through electrical GE ports when configured for 10M or
100M half-duplex.
Impact: Traffic cannot be carried in half-duplex mode on GE ports.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

76.8660-50169C 8600 Smart Routers SR6.0

103
15 Known Bugs

cq300200379 IFC1, IFC2

PPP links may not always be inserted into an MLPPP group.
Impact: MLPPP group cannot be configured with a desired PPP interface.
Risk of occurrence: Rare.
Workaround: Line card reload should be performed to enable all configurations
pertaining to PPP interface.

cq300201508 8609 NE, IFC1, IFC2, 8611 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.
Risk of occurrence: Always under the described circumstances.
Workaround: Do not configure non-active TDM pseudowires.

cq300210342 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 OSPF 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, which may increase CPU usage.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300213169 8611 NE, 8609 NE, IFC1, IFC2, ELC1, 8615 NE, 8602 NE
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.
Workaround: Not available.

cq300213714 CDC1, CDC2

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".
Impact: After changing VRRP tracking delay value, there is a period during
which, if a failure occurs in the network, VRRP still handles it according to the
initial tracking delay value. The user may see traffic affected, in a different way
than expected.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

8600 Smart Routers SR6.0 76.8660-50169C

104
15 Known Bugs

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.
Risk of occurrence: Always under the described circumstances.
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.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300220057 ELC1, 8615 NE

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.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

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.
Risk of occurrence: Always under the described circumstances.
Workaround: If a group shaper is configured, the ingress card must be IFC2 (full
support) or IFC1 (some limitations).

cq300225540 8611 NE, 8609 NE, 8602 NE

If the network element that is used as a transit node in an FRR configuration is
restarted via a reload-sw command, the FRR re-routing node will not detect link
down failure for several seconds. This is because the network element does not
immediately bring the links down during a reload-sw operation.
Impact: The FRR switch time will not be in the 100s of milliseconds, but will
rather take seconds.
Risk of occurrence: Always under the described circumstances.
Workaround: If a faster switchover time is required, it is recommended that the
'reset-hw' command be used to restart the node, or the customer should also run IP
BFD on the MPLS link connecting the edge node to the network element.
Either of these approaches will speed up the node failure/link down detection by
the far end and facilitate faster FRR switchovers.

76.8660-50169C 8600 Smart Routers SR6.0

105
15 Known Bugs

cq300225787 8611 NE
Traffic will be lost on 4x10/100/1000BASE-TX HM (HMG2274) Electrical GE
ports in a scenario where they are initially running at 1000M speed and then it is
attempted to set the speed to 10/100M using the following CLI commands:
mode auto speed 10 100 duplex full (with Autonegation Enabled)
mode speed 10 100 duplex full (with Autonegation Disabled)
Impact: Traffic will be down on the 4x10/100/1000BASE-TX HM (HMG2274)
Electrical port that is in LinkDown fault.
Risk of occurrence: Frequently under the described circumstances.
Workaround: If a specific lower-speed is desired on an 4x10/100/1000BASE-TX
HM (HMG2274) Electrical GE port involved in a connection, the port and the
Link Partner port should be configured to the specific speed only, 10M or 100M.
The CLI commands to do this are:
mode auto speed 10 duplex full (with Autonegation Enabled)
mode auto speed 100 duplex full (with Autonegation Enabled)
mode speed 10 duplex full (with Autonegation Disabled)
mode speed 100 duplex full (with Autonegation Disabled)

cq300225896 CDC1, IFC1, IFC2, ELC1, CDC2, 8615 NE

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.
Risk of occurrence: Low.
Workaround: Give the "shutdown" CLI command and then the "no shutdown"
command to the IRB interface.

cq300226053 IFC1, IFC2

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
Workaround: Not available.

cq300226103 8611 NE
SCO1 sends AIS in E1 Framed mode.
Impact: If SCO1 is used as clock reference with E1 Framed mode configured, the
receiving end sees AIS and discards the clock.
Risk of occurrence: Always on SCO1.
Workaround: SCO1 should not be used for clock source, SCO2 should be used
instead.

8600 Smart Routers SR6.0 76.8660-50169C

106
15 Known Bugs

cq300226785 ELC1, 8615 NE

ARP cache is not properly updated when an ARP entry moves from one interface
to another within the same ELC1 card or 8615 Smart Router. This may happen
when IP configuration is created on an interface, then removed and recreated on
another interface within the same ELC1 card or 8615 Smart Router.
Impact: The moved ARP entry is not functional, and traffic to/via that IP address
will not flow.
Risk of occurrence: Always under the described circumstances.
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.

cq300227489 CDC1, 8609 NE, 8611 NE, 8602 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. Even then the packet causes trouble only in the
unlikely case that there are bit errors in IP layer transmission.
Workaround: Not available.

cq300228011 CDC1, CDC2, 8611 NE, 8609 NE, 8602 NE, 8615 NE
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".
Impact: It does not affect live traffic.
Risk of occurrence: Always under the described circumstances.
Workaround: The user shall interpret "01/01/2000 00:00:00" as “never
happened”.

cq300228181 8611 NE
Incorrect data is displayed in some cases for SNMP descriptions of entities.
Modules and interfaces are listed twice within the Entity descriptions and are
labeled as 'contained in' each individual SCM.
Impact: It affects the results in the 'Containment Tree', if this is used by a
customer. OID numbers are issued twice for entities, once per SCM present.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

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.
Risk of occurrence: Always under the described circumstances.
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).

76.8660-50169C 8600 Smart Routers SR6.0

107
15 Known Bugs

cq300230282 8609 NE
Interoperability issue found between 8800 OC3 IMA functionality and 860x
Smart Routers, when the 8800 OC3 interface is connected to 860x using 6335. If
a protection switch occurs on an 8800 IMA interface in a protection group, it is
possible the IMA group on the 860x will not transition states correctly, causing
the IMA group to transition to a Down state for approx. twenty seconds. This
problem has been found in ETSI and ANSI modes with multiple links configured
in the IMA group.
Impact: Potential 20 - 25 second traffic outage.
Risk of occurrence: Usually with four or more active IMA members.
Workaround: Not available.

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.

cq300231048 IFC1, IFC2, ELC1, 8615 NE

Error message in linecard's os-log when VRF is deleted without unbinding it first.
VRF is deleted successfully despite of os-log error message.
Impact: It does not affect live traffic.
Risk of occurrence: Always when VRF is deleted without unbinding it first.
Workaround: Unbind VRF from all interfaces using it before deleting VRF.

cq300231620 CDC1
8000 Intelligent Network Manager operations may slow down if query rate
(queries/second) from 8000 Intelligent Network Manager to the network element
is continuously high.
Impact: It does not affect live traffic.
Risk of occurrence: Always under the described circumstances, more likely
with big configurations.
Workaround: Not available.

cq300232626 CDC1, CDC2, 8609 NE, 8602 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.

8600 Smart Routers SR6.0 76.8660-50169C

108
15 Known Bugs

cq300232742 CDC1, CDC2

Some short IS-IS frames may have 4 bytes of additional padding.
Impact: It does not affect live traffic.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300234582 8609 NE, 8611 NE, 8602 NE

When the flood of packets received is more than 600 pkts per second (8602 Smart
Router/8609 Smart Router/8611 Smart Router), the remaining packets, i.e. the
packets exceeding the 600 limit will be dropped in the host rate limiter. Due to
this some control packets will get missed. BFD sessions may flap due to this
host packet drop.
Impact: BFD will go down for some time, due to which traffic will get dropped.
Risk of occurrence: Always when a flood of packets is received in the host.
Workaround: Increasing BFD time parameter may help in resolving this issue.
May not work always.

cq300235456 8611 NE, 8609 NE, 8602 NE

QoS markings for CCM/LMM/DMM (EOAM UP MEPs pkts) do not follow
Ethernet VLAN PWE3 VC-QoS settings.
When vc-qos option is set on Eth VLAN PWE3, the EOAM pkts traversing (or
generated internally by the LC for that) the VLAN should be re-marked using
vc-qos value as long as the qos ingress setting is set to 'qos mapping use ingress
traffic layer2-frame'. Instead the defined per EOAM VLAN settings are still used.
Impact: EOAM traffic may get affected during network congestion.
Risk of occurrence: Always under the described circumstances.
Workaround: It is recommended to set LM and DM QoS with VC QoS setting.

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.
Risk of occurrence: Always under the described circumstances.
Workaround: shut/no-shut on the near end link will make the far end link go up.

cq300237044 8611 NE, 8609 NE

Switchover in ANSI mode from SCI (framed mode) to PDH causes transient of
500 ns in the output clock. The permanent phase shift is only around 30 ns.
Impact: Only in ANSI mode. It does not affect customer traffic or synchronization
since the transient is brief and the permanent phase shift is only around 30 ns.
Risk of occurrence: Rarely. It requires ANSI mode and Loss of Signal in the
primary clock source (SCI).
Workaround: Not available.

cq300238924 8609 NE
Setting PDH interface SSM SA-bit to any value other than 4 does not work. The
Tx side is ok, but the Rx side stays in bit 4 setting. Note that the SSM SA-bits
apply to ETSI mode only.
Impact: SSMs cannot be used in case the SA-bit is modified from its default
value of 4. This can cause loss of synchronization in case quality-levels are
enabled in the network.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

76.8660-50169C 8600 Smart Routers SR6.0

109
15 Known Bugs

cq300238925 8611 NE, CDC1, CDC2

SSM SA-bit cannot be modified on the protecting side SCI. This fails only with
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.
Risk of occurrence: Always under the described circumstances.
Workaround: Issue the command from CLI.

cq300238998 ELC1, 8615 NE

When associated ACL contains unsupported actions for ELC1 or 8615 Smart
Router, 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 or 8615 Smart Router.
Workaround: Do not configure unsupported ACL actions for ELC1 or 8615
Smart Router, e.g. 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.
Workaround: Not available.

cq300239229 8609 NE, 8611 NE

Traffic is cut for a short period of time (e.g. about 24 ATM cells/25 ms) when
the 1588 boundary clock is enabled with the command “node-timing ieee1588
slave enable-sci”.
Impact: Traffic will be cut.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

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.

cq300239602 8611 NE, 8609 NE

Ethernet PWE3 redundancy feature for 8609 Smart Router/8611 Smart Router
exceeds the expected switchover timing target of 50ms for 25 protection groups in
revertive switchover case if PWs are dynamically (LDP) provisioned. This occurs
regardless of VCCV BFD Interval and Multiplier options because of slowness of
LDP session negotiations compared to VCCV BFD sessions.
Impact: A few protection groups will not complete their protection switching
within the 50ms time limit.
Risk of occurrence: Always under the described circumstances.
Workaround: Use static pseudowires.

8600 Smart Routers SR6.0 76.8660-50169C

110
15 Known Bugs

cq300239762 ELC1, 8615 NE

The number of learned MAC addresses exceeding 256K limit will be visible in the
MAC forwarding table (show bridging-instance) until manually cleared.
Impact: It does not affect live traffic.
Risk of occurrence: Always under the described circumstances.
Workaround: Clear MAC table manually (clear bridging-instance name
<bridging-instance name> macs).

cq300240150 8609 NE
The PPS clock source of the IEEE1588 master cannot be disabled, if the frequency
slave specific IEEE1588 virtual SCI has been active and disabled prior to disabling
the master clock source. An error "Command failed: instance does not exist" is
returned.
Impact: It does not affect live traffic.
Risk of occurrence: Always under the described circumstances.
Workaround: Re-enable IEEE1588 grandmaster with PPS input and disable
it again.

cq300240652 8609 NE, 8611 NE, 8602 NE, CDC2

PTP clock class and clock identity of an adjacent master is not shown with the
command 'show node-timing ieee1588 slave'.
Impact: It does not affect live traffic.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300241252 8609 NE, 8602 NE, 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.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300242297 IFC1, IFC2

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.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300242522 CDC1, IFC1, IFC2, ELC1, 8611 NE, 8609 NE, 8615 NE, CDC2, 8602 NE
ARP cache entry may be left unexpired for an indefinite time.
Impact: It does not affect live traffic.
Risk of occurrence: Dependent of ARP cache timer values, thus rare.
Workaround: ARP cache can be cleared, which should resolve the issue.

76.8660-50169C 8600 Smart Routers SR6.0

111
15 Known Bugs

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.
Risk of occurrence: Always under the described circumstances.
Workaround: Overwrite the IEEE clockId manually. For example, from the CLI
command 'node-timing ieee1588 clock-id'.

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.
Risk of occurrence: Low.
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 VC4 unequipped error is received in an STM-1 port of the
4xchSTM-1/chOC-3 Multiservice IFM (LIO2248), the port does not send back the
VC4 RDI (Remote Defect Indicator) alarm.
Impact: VC4 Remote Defect Indicator alarm is not reported even when the
STM-1 port is in VC4 unequipped state.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

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.
Risk of occurrence: Low.
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).

8600 Smart Routers SR6.0 76.8660-50169C

112
15 Known Bugs

cq300245124 8602 NE
In IEEE1588 slave setting, the slave clock remains in holdover mode indefinitely
when it loses its master, even though it should go to freerun state after the holdoff
time has expired.
Impact: It does not affect live traffic.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300245446 8602 NE, 8609 NE

IEEE1588 slave frequency accuracy cannot be monitored against GPS (GNSS)
SFP reference clock.
Impact: It does not affect live traffic.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300245581 8615 NE
When LSP traceroute command is executed for an unknown destination address,
instead of "destination not reachable", the "timedout message" is seen.
Impact: It does not affect live traffic.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300245824 ELC1
ACLs containing the map-route option may cause an ACL statistics counting
failure. That is, ACL statistics counters will not increment when traffic hits the
ACL rules on the list.
Impact: No impact to traffic. When this issue is met, ACL statistics for the ACL
instance is useless.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300245891 8602 NE, 8609 NE

When the IEEE1588 L2 master is referenced from a GNSS SFP which is operated
in GLONASS mode, a static phase error of 2 microseconds is introduced to the
sent PTP frames.
Impact: It is not possible to meet the LTE TDD or LTE-A phase/time
synchronization requirement of 1.5 microseconds.
Risk of occurrence: Always under the described circumstances.
Workaround: Use GPS operating mode for the GNSS SFP.

cq300245972 8602 NE, 8609 NE

Certain PTP dataset members have incorrect values when the IEEE1588 master is
referenced from the GPS (GNSS) SFP. In particular:
timeTraceable is FALSE while TRUE expected,
frequencyTraceable is FALSE whileTRUE expected, and
timeSource is 0xA0 while 0x20 expected
Impact: It does not affect live traffic.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

76.8660-50169C 8600 Smart Routers SR6.0

113
15 Known Bugs

cq300245984 8609 NE, 8611 NE

After SW upgrade from 8609 Smart Router FP1.0.x to 8609 Smart Router or
8611 Smart Router FP1.2 SP2 or FP1.3.x, IEEE1588 configurations related to
acceptable-master settings will be lost.
Impact: IEEE1588 frequency synchronization is not recovered after the upgrade,
until the acceptable-master settings have been reapplied.
Risk of occurrence: Always under the described circumstances.
Workaround: 1) Reapply the missing configurations manually
or
2) Upgrade to FP1.1 first, and upgrade again to FP1.2 SP2 or FP1.3.

cq300246007 8609 NE, ELC1, 8602 NE

QoS mapping is done incorrectly, if the VLAN traffic contains raw interfaces in its
traffic path and the network elements have L2 VLAN classification globally.
Impact: Received VLAN priority bits may not be the same as what has been
sent on the TX side.
Risk of occurrence: High.
Workaround: In addition to 'layer2-frame' at node-level, raw interfaces in VLAN
traffic path should be configured with 'ip-dscp' as shown below to receive VLAN
priority bits unchanged.
qos mapping use ingress traffic ip-dscp qos mapping use egress traffic ip-dscp

cq300247276 8615 NE
Snapshot restoration of the 8615 Smart Router configuration may fail
approximately once every 10 times.
Impact: After restoration failure the NE configuration may be in inconsistent state.
Risk of occurrence: Low.
Workaround: If snapshot restoration fails, retry.

cq300247919 8602 NE, 8609 NE, 8611 NE

On the 8602, 8609 and 8611 Smart Routers, BFD transmitter may experience
delay variation due to other forwarding plane operations. This is especially
evident in (but not limited to) cases where a large number of routes (>500) are
updated at once.
BFD configurations should provide at least 100 ms detection time.
Examples of safe parameter sets:
- 100 ms interval multipler 1
- 100 ms interval multiplier 2
Impact: BFD session flapping leading to traffic losses and protocol adjacency
flaps.
Risk of occurrence: Always under the described circumstances.
Workaround: On the network elements in question, avoid BFD detection times
shorter than 100 ms.

cq300248248 8615 NE
Ethernet OAM ping is not working for a packet size of 1500 bytes and above
with default link and IP MTU values.
There are no increments on the egress side (Tx) when Ethernet OAM ping is done
with packet sizes of 1500 bytes and above.
Impact: Ethernet OAM ping request will not work for a packet size of 1500
bytes and above.
Risk of occurrence: Always under the described circumstances.
Workaround: By configuring both link MTU and IP MTU with 1530, ping works
for a maximum packet size of 1504 bytes (1530-header(26)).

8600 Smart Routers SR6.0 76.8660-50169C

114
15 Known Bugs

cq300248359 8602 NE, 8609 NE, 86011 NE, CDC1, CDC2

When VPN route aggregation is used, aggregation attempts incorrectly to include
non-imported routes of the same Route Distinguisher (RD) into aggregation
leading to eventual spontaneous reset.
Impact: The control card or network element may reset spontaneously.
Risk of occurrence: Only if the VPN route aggregation is used and incorrectly
added routes matching the aggregation are present.
Workaround: Use unique RDs to ensure that no VRF has incorrectly added
routes into aggregation.

cq300248466 8615 NE
In 8615 Smart Router the commands 'hw-inventory slot 13 remove unit' and
'hw-inventory slot 13 add unit' are not supported and must not be used.
Impact: It does not affect live traffic.
Risk of occurrence: Always under the described circumstances.
Workaround: Use the command 'hw-inventory add-all-units clean-start' to clear
configurations and add all units to inventory.

cq300248622 8615 NE
The SSM SA-bit position cannot be changed on the 8615 Smart Router station
clock input (SCI) port.
Impact: Quality levels cannot be used if other than the default SA-bit position
is required to be used.
Risk of occurrence: Always under the described circumstances.
Workaround: Use the default SA-bit postion (4) and change the bit position also
in the connected equipment.

cq300248884 8609 NE, 8611 NE, 8602 NE

Low priority exception frames are raised to management CPU in the same queue
as frames addressed to local CPU in BE, AF1-4 and EF classes. This means
that exception frames (e.g. packets that do not have the available route and will
need ICMP error to be generated for) may saturate the queue and hamper other
communications. Routing protocols and CS7 traffic use high priority queue, and
are not affected.
Impact: Communications to CPU on non-CS7 classes may be hampered under
specific circumstances.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300248949 ELC1
ELC1 has a reduced Ethernet OAM scalability in ELP protected interfaces. ELP
interfaces shall not contain more than 200 Remote-MEPs per ELC1. If the limit
is exceeded, there is a risk that after ELC1 boot up, traffic connections are not
restored properly.
Impact: Impact to live traffic if the limit is exceed.
Risk of occurrence: High under the described circumstances.
Workaround: Not available.

76.8660-50169C 8600 Smart Routers SR6.0

115
15 Known Bugs

cq300249103 IFC2
IFC2 Gigabit Ethernet (GE) ports link failure may occur when the auto-negotiation
remote fault bit is set from the remote end. This has been observed so far while
interfacing with NSN FPH800 equipment. Most likely, interfacing IFC2 ports
with any such devices that indicate the remote auto-negotiation failure may cause
a problem of this kind.
Impact: Link will be down and traffic flow will be interrupted through this link.
Risk of occurrence: Always under the described circumstances.
Workaround: Workaround 1:
1. Uncheck auto-negotiation feature and manually set speed and duplex - on both
sides, 8600 system and FPH800.
2. Reset the SFP (Unplug/Plug).
3. Insert the cable back to the SFP.
Workaround 2:
1. Uncheck auto-negotiation feature and manually set speed and duplex - on both
sides, 8600 system and FPH800.
2. Reload IFC (traffic-affecting).
Workaround 3 / at commissioning of interface:
1. Manually configure the speed and duplex mode on both endpoint ports.
2. Insert the SFP and connect the fibre.

cq300249465 8609 NE, 8602 NE, CDC2, 8615 NE

GNSS SFP cannot be used in node-clock fallback list at the same time with
L3 IEEE1588 frequency slave clock. When L3 1588 is configured, GNSS as
node-clock frequency reference does not work properly.
The user needs to remove L3 1588 configurations in order to use GNSS as
node-clock reference.
Impact: Does not affect service, but GNSS cannot use 1588 as a backup source in
case satellite connectivity is lost.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300249524 IFC2
In an 8600 NE which is being reloaded, sometimes the LOS fault for an interface
is not cleared immediately, but only after 1 hr 50 mins.
Impact: It does not affect live traffic.
Risk of occurrence: Sometimes under the described circumstances.
Workaround: After the slot reload "no laser" and "laser" should be issued in
the interface in question.

cq300249839 8615 NE
IP host access list statistics are not counting.
Impact: IP host statistics are not usable e.g. for debugging on which ACL rule
certain packets are hitting.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300249881 8609 NE
The creation of maximum number of VLANs is affected when the 8609 Smart
Router is fully loaded with Ethernet Ports in all available modules.
Impact: With the combination of 12 GE and 2 FE modules, only a maximum of
2046 VLANs can be created.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

8600 Smart Routers SR6.0 76.8660-50169C

116
15 Known Bugs

cq300249899 8615 NE
L3 ACL Host Out packet filtering is not working for 8615 Smart Router.
Impact: An L3 ACL filter bound to host interface is not capable of filtering
outgoing packets.
Risk of occurrence: Always.
Workaround: Not available.

cq300249944 IFC2
L3 traffic from IRB interface that is flooded in VSI may get invalid MTU handling
under specific circumstances. Namely (for the flooded traffic):
-Even if IRB MTU is smaller than 1500, no fragmentation is done for frames <
1500
-If IRB MTU is larger than 1500, frames larger than 1500 are not forwarded.
Depending on the size of the MTU configured and the size of the frame, some of
the frames may get properly fragmented, but not all of them.
Impact: Loss of some flooded traffic originated by the IRB interface.
Risk of occurrence: Can occur after snapshot restore. Only impacts flooded
traffic (however note that traffic flooding may occur permanently if traffic that is
being dropped is required to trigger reverse traffic).
Workaround: If the issue occurs, delete and re-add MTU config. To avoid
occurrence, do not change IRB interface default MTU. Also ensure that devices
sending traffic that is forward to IRB interface also use IP MTU 1500.

cq300250316 IFC1
During snapshot reload, WDDI errors may be seen in os-log. These errors are
harmless and do not impact functionality.
On occurence, errors will be flooded in the os-log for all the configured TDM PWs.
Impact: It does not affect live traffic.
Risk of occurrence: Occurs 3 out of 5 times.
Workaround: To resolve the issue, perform one of the following:
1. Slot reload
2. Node reload.

cq300250457 CDC1, CDC2, 8615 NE, 8611 NE, 8609 NE, 8602 NE
Attribute genIfmNetMtu used by PW redundancy is missing from
l2tTunnelInterfaceAlias1/Alias2/Alias3 managed objects APIs.
Impact: For alias PW redundancy objects, the maximum size of IP or MPLS
packets (including the header) sent on an interface cannot be set by 8000
Intelligent Network Manager.
Risk of occurrence: Always when 8000 Intelligent Network Manager is expected
to set IP or MPLS maximun packet size for PW alias.
Workaround: Use CLI instead of 8000 Intelligent Network Manager to set the
maximum size.

cq300250667 CDC2
LACP should use system MAC address from EEPROM (for CDC2) as its system
ID through system MAC service. Now system MAC service is using MFE port
MAC address.
Impact: LACP protocol is not advertising system ID as per requirement.
Risk of occurrence: Always under the described circumstances.
Workaround: Manual configuration of system ID for LACP using the command
"eth lag lacp system-id <AABB.CCDD.EEFF>". Set LACP system ID in
AAAA.BBBB.CCCC format.

76.8660-50169C 8600 Smart Routers SR6.0

117
15 Known Bugs

cq300250669 IFC2
IFC2 Ethernet OAM Delay Measurement (DM) transmitter is not working
properly. DM-Ping will always show a time-out error.
Impact: IFC2 EOAM Delay Measurement transmitter cannot be used.
Risk of occurrence: Always under the described circumstances.
Workaround: Use IFC2 DM receiver by sending DM messages from the far-end
NE.

cq300250763 CDC1, CDC2

8000 Intelligent Network Manager Consistency Check may fail for route-map
objects if the CDC control card in slot 1 is active.
Impact: 8000 Intelligent Network Manager Consistency Check works for
route-map objects only if the CDC control card in slot 14 is active.
Risk of occurrence: Always under the described circumstances.
Workaround: Check that the CDC control card in slot 14 is active when
consistency check is being performed.

cq300250766 CDC1, CDC2

8000 Intelligent Network Manager Consistency Check gives incorrect results
about the existence of route-map objects that have been deleted.
Impact: This may lead to incorrect actions based on the Consistency Check
results.
Risk of occurrence: Always under the described circumstances.
Workaround: Avoid 8000 Intelligent Network Manager Consistency Check
when route-map objects are deleted.

cq300250802 ELC1, 8611 NE, 8609 NE, CDC2, CDC1

Some of the MPLS-TP tunnel protection status remains in passive state only when
both primary/backup links are changed to DOWN and then to UP at the same time
in both the ingress and the egress node.
Impact: When the issue occurs, it impacts PSC packet transmission for some
tunnels.
Risk of occurrence: Always under the described circumstances.
Workaround: When hold-off timer is not configured, the issue does not occur.

cq300250940 CDC2, CDC1

The passive CDC hangs up in boot up state when lag.vlan is configuring while the
passive CDC is booting up. This can be observed immediately after the passive
CDC starts booting up (before coming to "start permission state") when lag.vlan is
configuring in the active CDC.
Impact: It does not affect live traffic.
Risk of occurrence: Always under the described circumstances.
Workaround: To come out of the boot up state, reload the passive CDC by
issuing the CLI command "reset-hw slot / boot system slot 1".

8600 Smart Routers SR6.0 76.8660-50169C

118
15 Known Bugs

cq300251033 IFC2
When more than one MEP (Maintenance association End Point) is configured on
the same interface, deletion of one MEP will affect the status of the other MEP.
Specifically, a MEP sending RDI (Remote Defect Indication) to the far end MEP
will stop sending the RDI after the deletion of other MEP on the same interface.
This problem occurs if the RMEP (Remote MEP) on the deleted MEP was initially
discovered or configured before the RMEP on the other MEP.
For example:
Two MEPs 101 and 202 are created in the same interface, say, xe9/0/0.
MEP202 discovers a RMEP before MEP101.
After MEP101 discover a RMEP, LoC (Loss of Continuity) fault occurs as 101 is
not receiving the CCM packets.
101 will send RDI to the far end MEP
Now if MEP202 is deleted, the MEP101 will stop sending the RDI.
Impact: RDI condition on far end MEP will be lost, if another MEP is deleted
from the same interface, provided the RMEP on the deleted MEP was initially
discovered or configured before the RMEP on the other MEP sending the RDI.
Risk of occurrence: Always under the described circumstances.
Workaround: For statically configured RMEPs, deletion and re-creation of
RMEP that generates the RDI will help in recovering from the situation. There
is no workaround available for Discovered RMEPs.

cq300251035 CDC2, CDC1, IFC2, ELC1

When passive CDC is replaced by another CDC card, LAG configuration is
corrupted in the replacement unit. The replacement could be a HW replacement of
a CDC of the same type, or a CDC1 to CDC2 upgrade.
Impact: LAG does not work after activating the new replaced CDC unit.
Risk of occurrence: Always under the described circumstances.
Workaround: LAG configuration needs to be removed from node before
replacing CDC unit and reconfigured after replacement.

cq300251083 CDC1, CDC2, 8611 NE, IFC2, ELC1

After performing a non-service affecting upgrade to SR6.0, the parameters of LAG
groups that existed before the upgrade cannot be modified.
Note that the parameters of LAG groups that are created after the upgrade can
be freely modified.
Impact: The customer will not be able to change any LAG related parameters
(e.g. enable / disable LACP, LAG MTU, etc.) on existing LAG groups after a
non-service affecting upgrade. The existing configuration and traffic are not
affected.
Risk of occurrence: Always under the described circumstances.
Workaround: Deletion and re-creation of the LAG group will resolve the
problem.
It is recommended to do a service affecting upgrade to SR6.0 when LAG
configurations are present.

cq300251100 CDC1
Occasionally after FP4.0 to FP5.0 upgrade, the usage of RAM memory overflows
and as a consequence the protocols go down.
Impact: Traffic is cut because protocols are down due to low memory.
Risk of occurrence: Occasionally. More probable if the NE is fully equipped
and has a large configuration.
Workaround: Network element reload.

76.8660-50169C 8600 Smart Routers SR6.0

119
16 Rejected Bugs

16 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.
cq300149764 CDC1
If uncontrolled reset happens in a CDC control card during hw-inventory
operation in a NE having CDC-1+1 protection, CDCs might get into inconsistent
hw-inventory state. Inconsistent state sometimes cause linecard(s) to jam in
"Waiting for startpermission" state. CDC control card activity switch might also
remove start permission of some card(s).
Impact: Affects in traffic, if line cards are not getting start permission after reset.
Risk of occurrence: Rarely.
Workaround: Remove CDC1 control card from hw-inventory. Fix possible
problems (add or remove IFCs to/from inventory). Add CDC1 control card to
hw-inventory again.

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.

cq300163609 8605 NE, CDC1, 8620 NE, 8607 NE, 8609 NE, 8611 NE, 8602 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.

cq300167470 8605 NE, 8607 NE, 8611 NE, 8609 NE, 8602 NE
The "shutdown-if" CLI command on an Ethernet port running OAM CCM does
not cause LOC on the remote port.
Impact: CCM indicates that the interface is able to transmit traffic when in reality
it is not.
Workaround: Not available.

cq300170259 CDC1, 8620 NE, 8605 NE, 8607 NE, 8611 NE, 8609 NE
The CLI command "copy running-config flash:" is not supported and returns
"operation failed".
Impact: It does not affect live traffic.
Risk of occurrence: Always when the "copy running-config flash:" CLI command
is used.
Workaround: Use the "show running-config" CLI command; if the result is really
needed in the flash file, use (S)FTP to transfer it there.

8600 Smart Routers SR6.0 76.8660-50169C

120
16 Rejected Bugs

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.

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.
Workaround: Not available.

cq300192871 8609 NE, 8605 NE, 8607 NE, 8611 NE

If an interface is bound to a LDP signaled PWE3 and that PWE3 is unbound
and a non-signaled PWE3 is attached to the same interface, the PWE3 statistics
stop working. The PWE3 statistics start to work again if the CLI command pair
"shutdown + no shutdown" is issued for the affected interface.
Impact: PWE3 statistics may not work after binding a static PWE3 to an interface
that was previously used for a LDP signaled PWE3.
Risk of occurrence: Occurs if PWE3 control protocol change is performed
(very rare operation).
Workaround: After changing the PWE3 type, issue the "shutdown" + "no
shutdown" CLI commands for the AC.

cq300193502 8605 NE, 8611 NE, 8609 NE, 8607 NE

Egress untagged and priority tagged traffic counters may not count correctly in a
FE interface when IP broadcast packets are sent out.
Impact: Egress untagged and priority tagged traffic counters report wrong values
for the customer in specific circumstances.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

76.8660-50169C 8600 Smart Routers SR6.0

121
16 Rejected Bugs

cq300194914 8609 NE, 8611 NE, 8602 NE

Regular Ethernet flow control using Ethernet pause frames is not working in the
transmit or receive direction. During network congestion, packets will get dropped
instead of being flow controlled. This problem applies to the following interfaces:
8611 Smart Router:
- 4x100/1000BASE-X High Speed Module (HMG2266)
- 1x10GBASE-R High Speed Module (HMX2267)
- 4x10/100/1000BASE-TX High Speed Module (HMG2274)
8609 Smart Router:
- 4x10/100/1000BASE-T
- 4x100/1000BASE-X 8602 Smart Router:
- 1x10/100/1000BASE-TX
-1x1000BASE-X
Impact: Packets will get dropped.
Risk of occurrence: Only during congestion.
Workaround: Not available.

cq300195374 8609 NE, 8605 NE, 8611 NE

When the "show snapshot flash: <file name>" CLI command is used with the
"running-config" option the running-configuration is not displayed.
Impact: The running-config cannot be easily extracted in the CLI from the
snapshot file.
Risk of occurrence: Always under the described circumstances.
Workaround: When creating a snapshot-config with the running-config option,
FTP the snapshot off the NE, and then extract the running-config from the snapshot
file (the snaphot file needs to be renamed to a .zip extension first).

cq300197715 8605 NE, 8611 NE, 8609 NE, 8602 NE

Ethernet interface untagged and priority tagged Rx octet and Tx octet counters are
only reported up to max 32bit value, rather than max 64bit value.
Impact: Counter values are not reliable.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300200128 IFC2
MAC address aging in IFC2 is based on monitoring traffic from that MAC address.
Due to a SW/HW synchronization problem, on IRB interface, this monitoring
sometimes yields incorrect results when new MAC addresses are learned and a
large amount of MACs were already known. This may cause some MACs to not
be aged when they should be, or some MACs to be aged when they should not.
Improperly aged MACs will be learned again shortly and those not aged when
they should will be aged after next aging interval (default 300 seconds). Plain
MAC switching is not affected, only IRB.
Impact: A MAC which will not age properly will consume resources. If the learn
table is full (4096 MACs learned) this will prevent new MACs to be learned. This
is unlikely to be a problem in practice.
A MAC which was aged out improperly will cause the traffic to that MAC address
to be flooded, consuming bandwidth. The situation resolves shortly after this
MAC is seen again as source MAC address.
Risk of occurrence: Very low.
Workaround: Not available.

8600 Smart Routers SR6.0 76.8660-50169C

122
16 Rejected Bugs

cq300200538 8609 NE, 8605 NE, 8611 NE

If a PWE3 is attached to an interface that already has an ACL bound to it, it is not
possible to remove the ACL without first removing the PWE3 circuit attachment.
The attached ACL is never in use on that interface once a PWE3 circuit has been
attached to it.
Impact: It does not affect traffic nor services. A customer may end up having an
ACL attached to an interface that is being used as a PWE3 endpoint.
Risk of occurrence: Always if the ACL is left bound to the interface prior to
adding the PWE3 to the interface.
Workaround: 1. Remove the PWE3 circuit from the interface.
2. Remove the ACL.
3. Attach the PWE3 circuit back to the interface.

cq300208836 8605 NE, 8611 NE, 8609 NE, 8607 NE

ATM PWE3 statistics may show invalid values if the ATM interface traffic
parameters are modified while the PWE3 (LDP) is already established.
Impact: The statistics may be inaccurate if the ATM service category is modified
after the PWE3 is attached to the interface and enabled.
Risk of occurrence: Sometimes.
Workaround: Shutdown the ATM PWE3 interface before updating the traffic
parameters. Once the traffic parameters have been updated, clear the PWE3
circuit statistics.

cq300214596 8611 NE, 8609 NE

When configuring an ATM interface as type UBR+, the minimum shaping rate
(PCR) is 50 cells/second. The CLI allows PCR values less than 50 to be specified,
but the network element will still shape to a minimum of 50 cells/second.
Impact: The minimum shaping rate for a UBR+ ATM interface is 50 cells/second.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300215122 CDC1, 8620 NE, 8605 NE, 8607 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.
Risk of occurrence: Always under the described circumstances.
Workaround: Do not use RSVP-TE load balancing with FRR.

cq300217196 8611 NE
Ethernet OAM Y.1731 ETH-LM probe counters reset to zero for the current
15-min interval after an SCM switchover. The previous interval values remain
synchronized to their values prior to the SCM switchover.
Impact: The ETH-LM counters for the current 15-min interval restart from the
point the SCM switchover happened.
Risk of occurrence: Only occurs if a protection switch has occurred.
Workaround: Not available.

cq300218033 8611 NE, 8609 NE, 8605 NE

When a PDH interface is used as an ATM PWE3 endpoint, an error messages may
be seen in the system OS logs when the interface is deleted (e.g. pdhx/y:0) before
the PWE3 circuit is removed from the interface. Both the circuit and the interface
are deleted correctly even though the error messages are shown in the logs.
Impact: It does not affect live traffic.
Risk of occurrence: Always under the described circumstances.
Workaround: The correct procedure is to remove the PWE3 from the interface
and then delete the timeslot group. If the correct procedure is followed, no error
messages are seen.

76.8660-50169C 8600 Smart Routers SR6.0

123
16 Rejected Bugs

cq300219460 8609 NE, 8611 NE

The ATM OAM ping fails for an AAL5 PWE3 when an in-to-switch ping is
executed.
Impact: ATM OAM ping cannot be used to check connectivity for an AAL5
PWE3 (in-to-switch).
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300221874 CDC1, 8620 NE, 8605 NE, 8607 NE, CDC2

SNMP traps are sent to an unknown socket if SNMP socket creation fails.
Impact: It does not affect live traffic.
Risk of occurrence: Rarely.
Workaround: Not available.

cq300222531 8611 NE, 8609 NE, 8605 NE, 8607 NE, 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.

cq300223333 8611 NE
If a MPLS PWE3 ping is being run and a control card switchover is performed
while the pings are in progress from the far-end of the PWE3 towards the
network element endpoint, several ping packets will timeout during the control
card switchover.
Impact: Some pings will timeout during the control card switchover, so the PWE3
may appear to be down even though user traffic is working as expected.
Risk of occurrence: This happens only if a control card switchover occurs while
pings are being executed.
Workaround: Not available.

8600 Smart Routers SR6.0 76.8660-50169C

124
16 Rejected Bugs

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.
Risk of occurrence: Always under the described circumstances.
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".

cq300226321 8611 NE, IFC2, 8609 NE, 8602 NE, 8605 NE

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.
Risk of occurrence: Always under the described circumstances.
Workaround: Multiply the time by constant 1 nanoseconds/tick.

cq300226855 CDC1, IFC1, IFC2, ELC1

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, 8611 NE

ARP cache listing might show unnecessarily incomplete entries regarding the
management interface.
Impact: It does not affect live traffic.
Risk of occurrence: Occurs sometimes after control unit boot-up.
Workaround: Clearing the ARP cache should remove the incomplete entries.

cq300227963 8611 NE, 8609 NE

Regular Ethernet flow control using Ethernet pause frames is not working in the
transmit or receive direction. During network congestion, packets will get dropped
instead of being flow controlled. This problem applies to the fixed GE interface
10BASE-T/100BASE-TX/1000BASE-T and FE 8x10/100BASE-TX Line Module
(LME2243).
Impact: Packets will drop.
Risk of occurrence: Only during congestion.
Workaround: Not available.

76.8660-50169C 8600 Smart Routers SR6.0

125
16 Rejected Bugs

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.
Risk of occurrence: High.
Workaround: Switch protection manually to the primary side.

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.
Risk of occurrence: Always under the described circumstances.
Workaround: Use 8000 Intelligent Network Manager instead of CLI.

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.
Workaround: Not available.

cq300234359 8609 NE, 8611 NE

Pause frame configuration fails when the configuration is done at the same time
when pause frame transmitting is active.
Impact: Pause frame configuration fails in certain circumstances.
Risk of occurrence: Always under the described circumstances.
Workaround: Ensure that the ingress interface is not congested when configuring
pause frame settings.

cq300235294 ELC1, 8615 NE

Received pause frames are ignored by ELC1 and 8615 Smart Router. The
command for enabling and disabling pause frame handling does not have effect on
ELC1 and 8615 Smart Router.
Impact: The NE does not react to pause frames.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

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
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

8600 Smart Routers SR6.0 76.8660-50169C

126
16 Rejected Bugs

cq300235576 CDC1
CDC card spontaneous reset will happen after CDC switchover, if the master
member's interface number is not the lowest of all the LAG member's interface
number when configured after clean start.
For example:
In a LAG group with three members the below configuration will not have this
issue.
Master member = Ge6/1/2
non-master member = Ge6/1/3
non-master member = Ge6/1/5
In a LAG group with three members the below configuration will lead to this issue
(CDC reload after a CDC switchover).
Master member = Ge6/1/3
non-master member = Ge6/1/2
non-master member = Ge6/1/5
This issue is seen only when configuration is done after clean start and then
followed by CDC switchover.
Impact: When CDC swithcover happens due to failure in active the CDC, the
passive CDC will go for a reload leaving the NE without the control card until the
passive CDC boots-up and becomes active.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300236327 IFC2, 8609 NE, 8611 NE

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.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

cq300239134 CDC1, CDC2

During IFC2 IRB Ethertype 0x88a8 traffic tests CDC2 MFE interface protection
in CDC2 switchover is not working properly and console errors are seen.
Impact: It does not affect live traffic.
Risk of occurrence: Always under the described circumstances.
Workaround: Not available.

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: Always when applying learning limits on the fly.
Workaround: Not available.

cq300239570 ELC1, IFC2

After setting bridging instance (VSI) mac-learning limit, re-learning after
manually clearing MAC Addresses is not always reaching the limit.
Impact: The MAC Addresses are not learned up to the limit set because of
simultaneous aging.
Risk of occurrence: Always when aging removes some macs when the limit
is reached and learning is suspended.
Workaround: Not available.

76.8660-50169C 8600 Smart Routers SR6.0

127
16 Rejected Bugs

cq300239571 CDC1, CDC2

During software upgrade, the software package may be left unactivated with an
unexpected error.
Impact: It does not affect live traffic.
Risk of occurrence: Rare.
Workaround: Software package needs to be reactivated.

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.
Risk of occurrence: Always under the described circumstances.
Workaround: The user can clear the ARP cache.

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.

cq300244147 8611 NE, 8609 NE

Tellabs 8609 and Tellabs 8611 do not show AIS alarm on an E1 interface, when
the TDM PWE's other end point is not connected to a tester or the tester has the
wrong configuration. This occurs with unframed PWE's only. Framed PWEs
work correctly.
Impact: It does not affect live traffic.
Risk of occurrence: Occurs consistently under the described circumstances.
Workaround: Not available.

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.
Risk of occurrence: Rare.
Workaround: Not available.

cq300245570 8609 NE, 8602 NE

The command 'clear node-timing ieee1588 slave statistics' is not working.
Impact: It does not affect live traffic.
Risk of occurrence: Always.
Workaround: The command 'clear node-timing ieee1588 clock-if statistics
<module/port>' can be used to clear the slave port statistics.

cq300245693 CDC1, CDC2

L3 broadcast packet storm can overload the CPU and cause MPLS protocols
to go down.
Impact: May cause traffic outage.
Risk of occurrence: Low.
Workaround: Not available.

8600 Smart Routers SR6.0 76.8660-50169C

128
16 Rejected Bugs

cq300245814 8602 NE
L2 PTP packets are received even if the Ethernet port is in 'shutdown-if' state.
Impact: It does not affect live traffic.
Risk of occurrence: Always under the described circumstances.
Workaround: Set the IEEE1588 clock-if to 'disabled' state on the Ethernet
interface in question.

cq300247434 ELC1, 8615 NE, 8615 NE

L3/L4 ACLs do not support non-initial IP packet fragments, that is, the keyword
"fragments" is not supported.
Impact: It does not affect live traffic.
Workaround: Avoid packet fragmentation by using proper MTU values in the
network.

cq300247820 CDC1, ELC1, CDC2

ELC1 IRB distributed ARP timeout is about one minute longer than the value set
per card where the ARP is locally resolved.
Impact: The locally resolved entry expires first and distributed entries followed
with approximately one minute randomised delay, ensuring proper traffic
forwarding and avoiding race conditions.
Risk of occurrence: Always, as this is a feature of the system.
Workaround: Not available.

76.8660-50169C 8600 Smart Routers SR6.0

129

8000 Intelligent Network Manager SR6.1 System Description
No ratings yet
8000 Intelligent Network Manager SR6.1 System Description
177 pages
Coriant Training Services: 8600 Series Provisioning Using 8000 INM
No ratings yet
Coriant Training Services: 8600 Series Provisioning Using 8000 INM
148 pages
Telecom Engineering Manual
No ratings yet
Telecom Engineering Manual
150 pages
Manual Del JDSU 6300
No ratings yet
Manual Del JDSU 6300
390 pages
Design and Automate With NDFC
No ratings yet
Design and Automate With NDFC
131 pages
Hardware Configuration Manual - 7300
No ratings yet
Hardware Configuration Manual - 7300
162 pages
8600 Smart Routers SNMP MIB Support: 76.8600-50116M November 9, 2018
No ratings yet
8600 Smart Routers SNMP MIB Support: 76.8600-50116M November 9, 2018
75 pages
1830PSS Product Information and Planning Guide 2 (14-17 - 15-82)
No ratings yet
1830PSS Product Information and Planning Guide 2 (14-17 - 15-82)
166 pages
Tellabs 8000 Network Manager R17A Software Installation Manual
No ratings yet
Tellabs 8000 Network Manager R17A Software Installation Manual
197 pages
76 8600-40039G
No ratings yet
76 8600-40039G
321 pages
DXX 6340 Switch Node: Installation Manual
No ratings yet
DXX 6340 Switch Node: Installation Manual
195 pages
Ic Inst-Emxpii
No ratings yet
Ic Inst-Emxpii
173 pages
ERX Intro+bras
No ratings yet
ERX Intro+bras
156 pages
Operation: Surpass Hit 7070 3.3 Operator Guidelines (Ogl)
No ratings yet
Operation: Surpass Hit 7070 3.3 Operator Guidelines (Ogl)
62 pages
Tellabs 8000 Intelligent Network Manager
0% (1)
Tellabs 8000 Intelligent Network Manager
40 pages
Guimn - E-Surpass Hit 7070 3.2
100% (3)
Guimn - E-Surpass Hit 7070 3.2
666 pages
Transcend Chorus For Packet SR10.0 Third Party Hardware and Software Requirements
No ratings yet
Transcend Chorus For Packet SR10.0 Third Party Hardware and Software Requirements
34 pages
Tellabs 8600 Smart Routers System Troubl PDF
No ratings yet
Tellabs 8600 Smart Routers System Troubl PDF
245 pages
Demo_Cheating - Hoang + Duc
No ratings yet
Demo_Cheating - Hoang + Duc
74 pages
NTRN 10 An
No ratings yet
NTRN 10 An
342 pages
Tnms SNMP Nbi - Operation Guide
No ratings yet
Tnms SNMP Nbi - Operation Guide
90 pages
71noptnms Am A
No ratings yet
71noptnms Am A
280 pages
Huawei Sx700 Switch Quick Reference Guide
100% (1)
Huawei Sx700 Switch Quick Reference Guide
124 pages
Lab 4 sockets_lab
No ratings yet
Lab 4 sockets_lab
48 pages
CS610 Mcqs MidTerm by Vu Topper RM
No ratings yet
CS610 Mcqs MidTerm by Vu Topper RM
46 pages
15 200 52s2
No ratings yet
15 200 52s2
390 pages
7670 RSP ESE Product Engineering Information Nov07
No ratings yet
7670 RSP ESE Product Engineering Information Nov07
73 pages
450-3101-012.r11.0.i02interface User Login
No ratings yet
450-3101-012.r11.0.i02interface User Login
72 pages
DS 8660 Smart Router 74C0026
No ratings yet
DS 8660 Smart Router 74C0026
3 pages
Tellabs 8620 Access Switch Reference Manual FP 2.7
No ratings yet
Tellabs 8620 Access Switch Reference Manual FP 2.7
90 pages
8830 Hardware Installation Guide
100% (1)
8830 Hardware Installation Guide
132 pages
323-1051-101G GUI Network Element Description
No ratings yet
323-1051-101G GUI Network Element Description
122 pages
Dialnet RedesOpticasElasticas 5364584
No ratings yet
Dialnet RedesOpticasElasticas 5364584
70 pages
Surpass Hit 7070: Interconnect, Configuration and Mechanical Assembly (Icma)
No ratings yet
Surpass Hit 7070: Interconnect, Configuration and Mechanical Assembly (Icma)
54 pages
81.5517A DS3/1 Port Module (PM31A)
100% (2)
81.5517A DS3/1 Port Module (PM31A)
32 pages
Ecler TP Net Protocol User Manual en
No ratings yet
Ecler TP Net Protocol User Manual en
62 pages
RNC2600 HW Expansion PDF
No ratings yet
RNC2600 HW Expansion PDF
15 pages
8609 Smart Router Modular-Access-Router
No ratings yet
8609 Smart Router Modular-Access-Router
3 pages
BRKRST 3363
No ratings yet
BRKRST 3363
120 pages
8830 HW Installation Manual
No ratings yet
8830 HW Installation Manual
132 pages
HTB Dzs Pon Olt Product - 20220527
No ratings yet
HTB Dzs Pon Olt Product - 20220527
3 pages
NSR User Guide V1.0
No ratings yet
NSR User Guide V1.0
28 pages
XMS Administration Training
No ratings yet
XMS Administration Training
33 pages
Infinera-7100-Series-0169-SN-RevB-0122
No ratings yet
Infinera-7100-Series-0169-SN-RevB-0122
2 pages
Coriant 8660 Datasheet
No ratings yet
Coriant 8660 Datasheet
3 pages
Data Plane - SM-OS - r5
No ratings yet
Data Plane - SM-OS - r5
30 pages
CN 4200 Product Brochure
No ratings yet
CN 4200 Product Brochure
8 pages
Eclipse Packet Node INU - INUe ETSI Technical Specifications - March 2013
No ratings yet
Eclipse Packet Node INU - INUe ETSI Technical Specifications - March 2013
13 pages
Apollo V8.0 What's New Guide
No ratings yet
Apollo V8.0 What's New Guide
6 pages
E6000 Converged Edge Router (CER) System Release 6.0 Data Sheet
No ratings yet
E6000 Converged Edge Router (CER) System Release 6.0 Data Sheet
4 pages
CS601 Quiz-3 File by Vu Topper RM
No ratings yet
CS601 Quiz-3 File by Vu Topper RM
44 pages
E6000 Converged Edge Router (CER) Downstream Cable Access Module (DCAM) Technical Specifications
No ratings yet
E6000 Converged Edge Router (CER) Downstream Cable Access Module (DCAM) Technical Specifications
2 pages
323-1059-210 - Optical Metro 3500 Ing
No ratings yet
323-1059-210 - Optical Metro 3500 Ing
36 pages
Huawei CloudEngine 6800 Series Switches Data Sheet PDF
No ratings yet
Huawei CloudEngine 6800 Series Switches Data Sheet PDF
12 pages
Configuring Remote Access VPN Via ASDM - Posted - 1!15!09
No ratings yet
Configuring Remote Access VPN Via ASDM - Posted - 1!15!09
45 pages
What Is Proxy
No ratings yet
What Is Proxy
3 pages
NN10012-111 - 08.05 SPM Fundamentals
No ratings yet
NN10012-111 - 08.05 SPM Fundamentals
22 pages
Draft Filsfils Spring SR Policy Considerations 06
No ratings yet
Draft Filsfils Spring SR Policy Considerations 06
23 pages
Zhone Product Guide
100% (1)
Zhone Product Guide
12 pages
telnet email and ftp
No ratings yet
telnet email and ftp
15 pages
Transmode DS - TM - EMXP - B PDF
No ratings yet
Transmode DS - TM - EMXP - B PDF
2 pages
J86sapt8000nla-Etc-G Louhi Cust
No ratings yet
J86sapt8000nla-Etc-G Louhi Cust
20 pages
Oggetto: Limiti Ottiche SFP & XFP: Assistenza Tecnica System Test
No ratings yet
Oggetto: Limiti Ottiche SFP & XFP: Assistenza Tecnica System Test
2 pages
Tellabs 8800 Multi Service Router MSR Series Enabling New
No ratings yet
Tellabs 8800 Multi Service Router MSR Series Enabling New
13 pages
1662 SMC Ds tcm228-701431635
No ratings yet
1662 SMC Ds tcm228-701431635
12 pages
Data Sheet SFP Raisecom
No ratings yet
Data Sheet SFP Raisecom
1 page
Flashwave 9500 DCS: Data Sheet
No ratings yet
Flashwave 9500 DCS: Data Sheet
2 pages
Configurar VPN ASA PIX Cisco
No ratings yet
Configurar VPN ASA PIX Cisco
23 pages
Transmode TS Series 6p A
No ratings yet
Transmode TS Series 6p A
6 pages
BG 64 Details
100% (1)
BG 64 Details
4 pages
1678 MCC R4-5 ETSI Ds
No ratings yet
1678 MCC R4-5 ETSI Ds
2 pages
Tellabs Get Schooled Cheat Sheet: Pseudowires: The Building Blocks To Mobile
No ratings yet
Tellabs Get Schooled Cheat Sheet: Pseudowires: The Building Blocks To Mobile
5 pages
Arp Rarp Icmp
No ratings yet
Arp Rarp Icmp
22 pages
Sitio Principal Resepción de Material
No ratings yet
Sitio Principal Resepción de Material
6 pages
CEG5101-Aug-2023-Tutorial 3
No ratings yet
CEG5101-Aug-2023-Tutorial 3
8 pages
Tellabs Interface Module Concentrator 2 (IFC2)
No ratings yet
Tellabs Interface Module Concentrator 2 (IFC2)
2 pages
OpenFlow Circuit Switch Specification v0.3
No ratings yet
OpenFlow Circuit Switch Specification v0.3
16 pages
Exam Instructions
No ratings yet
Exam Instructions
5 pages
SDH Multiplexers For High Capacity Network Solutions: Nortel Networks Tn-16X
No ratings yet
SDH Multiplexers For High Capacity Network Solutions: Nortel Networks Tn-16X
2 pages
Flash Wave 7500 r5.2 Catalog
No ratings yet
Flash Wave 7500 r5.2 Catalog
4 pages
Licence
No ratings yet
Licence
8 pages
Trojan Port List
No ratings yet
Trojan Port List
13 pages
ELEN 4017 - Network Fundamentals Tutorial No. 1: Instructions
No ratings yet
ELEN 4017 - Network Fundamentals Tutorial No. 1: Instructions
3 pages
2021-22 AKTU CN QP
No ratings yet
2021-22 AKTU CN QP
2 pages
Volte Packet Aggregation
No ratings yet
Volte Packet Aggregation
3 pages
Communication Network: Modbus
No ratings yet
Communication Network: Modbus
4 pages
ONT by Cisco
No ratings yet
ONT by Cisco
2 pages
Filtering ARP Traffic With Linux Arptables
No ratings yet
Filtering ARP Traffic With Linux Arptables
6 pages
Highly Dynamic Destination-Sequenced Distance-Vector Routing (DSDV) For Mobile Computers
No ratings yet
Highly Dynamic Destination-Sequenced Distance-Vector Routing (DSDV) For Mobile Computers
11 pages
4 SDWAN Components
No ratings yet
4 SDWAN Components
2 pages
C1N Super Wifi Cpe: 802.11N Capable, With Bandwidth Control and Remote Management Capabilities
No ratings yet
C1N Super Wifi Cpe: 802.11N Capable, With Bandwidth Control and Remote Management Capabilities
2 pages
View Tips and Tricks How To Create Keyboard Shortcut On Kali Linux
No ratings yet
View Tips and Tricks How To Create Keyboard Shortcut On Kali Linux
4 pages
Network Programming BTCS703: TCP & IP Headers
No ratings yet
Network Programming BTCS703: TCP & IP Headers
3 pages
Voice over LTE Standard Requirements
From Everand
Voice over LTE Standard Requirements
Gerardus Blokdyk
3/5 (1)