8600 Smart Routers SR5.0 Service Pack 2 Embedded Software Release Notes

8600 Smart Routers SR5.
0 Service Pack 2
Embedded Software Release Notes
76.8650-50172B
15.07.2014
Document Information
Revision History
Document No. Date Description of Changes

76.8650-50172B 15.07.2014 Added cq300109805 in 2.2 Bugs and corrected
Mbps=>Mpps (Million packets per second) in cq300244423
and 2.1 Restrictions in 8600 Smart Routers FP4.1.
76.8650-50172A 14.07.2014 Release notes for 8600 Smart Routers SR5.0 SP2 GA
application software version.
© 2014 Tellabs. 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 following trademarks and service
marks are owned by Tellabs Operations, Inc. or its affiliates in the United States and/or other countries: TELLABS ®, TELLABS ®
logo, TELLABS and T symbol ®, T symbol ®, CORIANT TM.
Any other company or product names may be trademarks of their respective companies.
The specifications and information regarding the products in this manual are subject to change without notice. All statements,
information, and recommendations in this manual are believed to be accurate but are presented without warranty of any kind,
express or implied. Users must take full responsibility for their application of any products.
Adobe ® Reader ® are registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.
Tellabs and Coriant are joining forces. You may see references to Coriant or Tellabs when doing business with us. Contact
information is available at http://www.coriant.com.
Unless otherwise agreed in a written document, the software in the product is licensed under the license terms found
at http://www.tellabs.com/legal/tlab_sw_license-global.pdf and http://www.tellabs.com/le-
gal/tlab_terms-product_specific.pdf.
8600 Smart Routers SR5.0 Service Pack 2 76.8650-50172B

Embedded Software Release Notes © 2014 Tellabs.
2
Terms and Abbreviations
Term Explanation
ACL Access Control List
ANSI American National Standards Institute
ARP Address Resolution Protocol
ATM Asynchronous Transfer Mode
BFD Bidirectional Forwarding Detection
CAM Content Addressable Memory
CCM Continuity Check Message
CESoPSN Circuit Emulation Service over Packet Switched Network
CIR Controlled Introduction Ready
CLI Command Line Interface
CPU Central Processing Unit
ELP Ethernet Link Protection
ESW Embedded Software
FL Fast Lane
FP Feature Pack
GA General Availability
IP Internet Protocol
IRB Integrated Routing and Bridging
IS-IS Intermediate System to Intermediate System (Interior Gateway Protocol)
LAG Ethernet Link Aggregation
LAN Local Area Network
LDP Label Distribution Protocol (MPLS)
LOC Loss of Continuity
LSP Link State Packet
MAC Media Access Control Sublayer of Data Link Layer
MD Maintenance Domain
MEP Maintenance End Point
MPLS Multiprotocol Label Switching
Mpps Million packets per second
MS Multiservice
MSP Multiplexer Section Protection
MS-PWE3 Multi-Segment PWE3
MTU Maximum Transfer/Transmission Unit
76.8650-50172B 8600 Smart Routers SR5.0 Service Pack 2

© 2014 Tellabs. Embedded Software Release Notes
3
NE Network Element
OSPF Open Shortest Path First
PWE3 Pseudowire Emulation Edge to Edge
RMEP Remote Maintenance End Point
RSVP-TE Resource Reservation Protocol with Traffic Engineering Extensions
SAToP Structure-Agnostic Time Division Multiplexing over Packet
SDH Synchronous Digital Hierarchy
SP Service Pack
SSM Synchronization Status Message
TCP Transmission Control Protocol
VCCV Virtual Circuit Connectivity Verification
VCG Virtual Circuit Group
VLAN Virtual LAN
VP Virtual Path
VRF VPN Routing and Forwarding
VSI Virtual Switching Instance

4
Table of Contents
Table of Contents
1 8600 Smart Routers SR5.0 SP2 ESW Release Notes ............................................... 6
1.1 Application Embedded Software Codes.............................................................................................................. 6

1.2 Supported Upgrade Paths .................................................................................................................................... 7
1.2.1 8605 Smart Router............................................................................................................................... 7
1.2.2 8609 Smart Router and 8611 Smart Router......................................................................................... 7
1.2.3 8620 Smart Router, 8630 Smart Router and 8660 Smart Router ........................................................ 7
1.3 Upgrade Related Notifications............................................................................................................................. 8
1.4 Enhancements Compared to SR5.0 SP1 ESW .................................................................................................... 8
1.5 Fixed Bugs Compared to SR5.0 SP1 ESW ......................................................................................................... 9
2 Known Restrictions and Bugs ................................................................................... 15
2.1 Restrictions in 8600 Smart Routers FP4.1........................................................................................................... 15

2.2 Bugs ..................................................................................................................................................................... 15
3 Rejected Bugs ............................................................................................................. 46

5
1 8600 Smart Routers SR5.0 SP2 ESW Release Notes
1 8600 Smart Routers SR5.0 SP2 ESW Release

Notes
This document describes the contents of the SR5.0 SP2 release for the following 8600 Smart
Routers products:
• 8605 Smart Router FP1.6

For more information on SR5.0, please refer to the following SR5.0 SP1 documents on the
Tellabs and Coriant Portal (www.portal.tellabs.com > Product Documentation & Software > Data
Networking > Tellabs 8600 Smart Routers > Technical Documentation):
• 8605 Smart Router FP1.6 Embedded Software Release Notes (76.8616-50154B)

• 8609 Smart Router and 8611 Smart Router FP1.2 Embedded Software Release Notes (76.8612-
50155C)
• 8600 Smart Routers FP4.1 Embedded Software Release Notes (76.8641-50156F).
1.1 Application Embedded Software Codes
Network Element Card Base- ESW ESW Version

board
8605 Smart Router SBB2230 SBZ2729 1.6.629 (SP2 GA)
8611 Smart Router SCM SCM2265 SBZ2748 1.2.629 (SP2 GA)
8630 Smart Router CDC1 CBB2026 CBZ2712 4.1.629 (SP2 GA)
8660 Smart Router
CDC2 CBB2300 CBZ2745 4.1.629 (SP2 GA)
ELC1 ELC2269 LBZ2754 4.1.629 (SP2 GA)
IFC1 LBA2024 LBZ2713 4.1.629 (SP2 GA)
IFC2 LBA2250 LBZ2741 4.1.629 (SP2 GA)

6
1.2 Supported Upgrade Paths
1.2.1 8605 Smart Router
From To
FP1.6 SP1 (1.6.586) FP1.6 SP2
FP1.6 CIR1 (1.6.182) FP1.6 SP1
FP1.5 SP2 (1.5.509) FP1.6 SP2
FP1.4 SP2 (1.4.355) FP1.6 SP1
FP1.3 SP2.3 (1.3.207) FP1.5
FP1.3 SP2 (1.3.204) FP1.5
FP1.3 SP1 (1.3.105) FP1.4
FP1.2 SP3 (1.2.180) FP1.4
FP1.2 SP2 (1.2.173) FP1.4
FP1.2 SP1 (1.2.98) FP1.4
FP1.1 SP2 (1.1.60) FP1.4
FP1.1 SP1 (1.1.55) FP1.4
FP1.1 GA (1.1.38) FP1.4
FP1.0 SP1 (1.0.180) FP1.2
FP1.0 (1.0.11) FP1.2
1.2.2 8609 Smart Router and 8611 Smart Router
From To
8609 and 8611 FP1.2 SP1 (1.2.586) 8609 and 8611 FP1.2 SP2
8609 and 8611 FP1.2 CIR1 (1.2.182) 8609 and 8611 FP1.2 SP1
8609 and 8611 FP1.1 SP1 (1.1.215) 8609 and 8611 FP1.2 SP2
8609 FP1.0 SP2 (1.0.308)1 8609 FP1.2 SP1
1.2.3 8620 Smart Router, 8630 Smart Router and 8660 Smart Router
From To
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
1 This upgrade path is not supported if IEEE1588 is used (see cq300245984)

7
From To
FP4.1 ECE (4.1.71) FP4.1 CIR1 (followed by immediate mandatory
upgrade to FP4.1 SP1)
FP4.0 SP3 (4.0.309) FP4.1 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
1.3 Upgrade Related Notifications
When upgrading from FP4.1 SP1 (4.1.586) to FP4.1 SP2, in 8660 Smart Router and 8630 Smart
Router, the reload option in CLI command boot system slot must not be used. When the
boot system slot command is ready, wait at least 30 seconds before reloading the NE using
the following command:
router#reload-sw
1.4 Enhancements Compared to SR5.0 SP1 ESW

cq300153384 IFC1, IFC2, 8620 NE, 8605 NE
When ATM VP is created, the amount of ATM capacity reserved and the amount
available on that interface can be monitored using the show command 'show
interface pdhx/x/x'.
cq300241286 CDC1, CDC2, 8609 NE, 8611 NE

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

Support for arbitrary length of IS-IS protocol host names to be displayed in any
CLI IS-IS commands.

8
1.5 Fixed Bugs Compared to SR5.0 SP1 ESW

cq300161281 CDC1, CDC2, 8605 NE, 8609 NE, 8611 NE, 8620 NE
When multiple IS-IS areas (multiple 'router isis' instances) are in use, if
re-distribute of external protocol (not isis inter-level redistribution) is removed
and then re-added to one of the areas, routes are not re-distributed.
cq300225574 CDC1, IFC2

When using ~5000 or more pseudowires and 500 + 500 RSVP sessions in a single
network element with IFC2(s) present, some of the RSVP sessions might flap
after control card switchover.
cq300226720 ELC1, IFC1, IFC2

When ELC1 goes to spontaneous reset, the PWE3 redundancy switch causes data
break without VCCV BFD and prefer-all options.
cq300229733 ELC1, IFC2

Dynamic MAC address entries learned from an SLI that is down may remain in
the switching table, if traffic is on while SLI is being shut down.
cq300230657 IFC2
Illegal configuration involving both port SLI and VLAN SLI(s) in the same port
disables traffic permanently on IFC2, when port SLI configuration is removed.
cq300231487 ELC1, IFC1, IFC2

Ethernet port that has had Stacked-VLAN configuration is not usable for normal
use until the unit is rebooted.
cq300232810 CDC1, ELC1, IFC1, IFC2

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.
cq300233503 ELC1
When RX-fiber is plugged out from interfaces configured with 1000BASE-X
speed, line state flapping occurs causing the LED to blink. In such cases, random
noise is generated that appears to be real signal causing false link-up.
cq300235736 CDC1, 8605 NE, 8609 NE, 8611 NE, 8620 NE

LDP neighbour authentication strings of more than 80 characters are silently
discarded.
cq300236172 CDC1, CDC2, IFC1, IFC2, ELC1, 8605 NE, 8609 NE, 8611 NE, 8620 NE
Inter-vrf routing to node local address does not work.
Basically inter-vrf ping will always fail if destination address is in the same node
that does the inter-vrf routing. It should be noted that MPLS->VRF POP does not
count as inter-VRF, as the packet in effect arrives directly to the correct VRF.
This has no impact on forwarded traffic.
LDP may stop accepting new TCP connections, if the connection made to LDP
TCP port is aborted within certain small time window.

9
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 entries in the MAC table.
cq300238636 CDC1, CDC2, 8605 NE, 8609 NE, 8611 NE

An 8600 network element may at times resolve IS-IS router instance name of
routes incorrectly. Instead of showing the correct IS-IS peer router, "isis (null)" is
shown with the CLI command 'show ip route'.
cq300238931 IFC1, IFC2, 8605 NE, 8609 NE, 8611 NE, 8620 NE
When setting pdh-interface to 'shutdown-if' state and then 'no shutdown-if' state,
the interface starts to send wrong quality level to the remote end node. For
instance, when 0xa (ql-st3) should be sent, 0 (ql-stu) is sent instead. This error
happens only in ANSI mode.
Due to an issue in command line handling, the following operations may cause
CDC to reset spontaneously due to a heavy CLI load:
1. Telnet session times out
2. Control cards switch over
3. Superuser forces other users to log out
4. User logs out.
cq300239554 ELC1, IFC1

Access Control List (ACL) hit counters are not fully accurate. Some packets may
match an ACL entry without increasing the counters.
cq300239567 CDC2, ELC1, 8609 NE

IEEE1588 slave RX Announce message counter does not increment, although
the announce messages are sent and received to the NE. The message counter
has value 0.
cq300239886 CDC1, 8605 NE, 8609 NE, 8611 NE, 8620 NE

The CLI of the active CDC may get stuck in certain situations.
cq300239980 CDC1, IFC2

Setting a virtual switching instance (VSI) administratively down (shutdown) stops
multicast traffic and disables MAC learning, but does not have effect on the
unicast traffic with already learned MAC addresses.
cq300239983 CDC1, IFC2

The configuration refresh logic for IFC IRB and MAC switching during CDC
switchover and line card reconfiguration is sub-optimal. This degrades somewhat
the tolerance against internal data corruption caused by ESW malfunction.
cq300239984 IFC2
CLI command 'qos mapping use egress traffic layer2-frame' is always enabled for
ACs connected to a VSI, so only the mappings defined by 'qos mapping egress
qos' always take effect. CLI command 'qos vlan ingress/egress vlan-pri' does not
take effect, instead the mappings defined by 'qos mapping ingress/egress qos'
always take effect.

10
cq300240149 IFC1
When MSP is configured on a interface, its line state remains UP even when both
the primary and backup interface links go to down state. So in a redundancy
setup with MSP for primary trunk, if the link down occurs in both primary and
backup interfaces of the primary trunk, it is not detected and hence switchover to
the alias interface happens only after LDP timeout. This results in a switchover
time of around 40 to 50 seconds.
cq300240706 CDC1, IFC1

MSP secondary side interface is not passing traffic after network element reload
with the primary interface removed because the MTU setting on the secondary
side is not correctly synchronised with the working side.
cq300240869 CDC1, 8605 NE, 8609 NE, 8611 NE, 8620 NE

After two retries for opening a TCP session, SYN options are changed to not
include the Window scale and Timestamp options. The other end may still try to
use the original Window scale option, which degrades TCP session performance.
cq300240872 IFC1, IFC2

ARP does not resolve for protected ETH_o_FR, ETH_VLAN_o_FR,
ETH_o_ATM, ETH_VLAN_o_ATM, ETH_o_PPP, ETH_VLAN_o_PPP logical
interfaces when working side is missing at network element reload.
cq300240981 CDC1, CDC2, ELC1, IFC2, 8609 NE, 8611 NE

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

Proper ingress and egress VLAN PRI QoS mappings are required for Ethernet
OAM loss measurements. Also VLAN PRI mappings shall not be modified when
Ethernet OAM loss measurement is ongoing.
cq300241150 CDC1, IFC1, IFC2

CDC1 control card might reset spontaneously when several IFC line cards send
statistics data in parallel to the CDC1.
Dynamic targeted peers are not expired (deleted) if targeted-peer-hello-receipt is
unconfigured.
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.
cq300241508 CDC1, 8611 NE

IP configuration is not mirrored to the protecting unit in case it differs only
for instance IDs or other minor details that do not change the length of the
configuration.
cq300241959 ELC1
ELC1 line card goes into reload mode when PLT throughput generator is executed
at the rate greater than 3 Gbps.

11
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.
cq300242485 CDC1, CDC2

High load of SSM messages may lead to CPU overload, which may cause unstable
behaviour.
cq300242757 CDC2
When route database is larger than 225000 entries, IP lookup CAM current usage
shows more than 100% usage.
cq300242787 8605 NE, 8609 NE, 8611 NE

The priority tagged frames are not dropped by the affected network elements
when 'discard untagged frames' are configured, instead the untagged frames alone
are dropped.
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.
cq300243539 8605 NE, 8609 NE, 8611 NE

The network element stops transmitting continuity check messages (CCM) when
MEPs (Maintenance End Points) are configured, which leads to LOC (Loss of
Continuity) condition in the RMEP (Remote MEP).
cq300244097 8605 NE, 8609 NE, 8611 NE

When packets bigger than the MTU size are received by the network element
with TTL=1, the packets are fragmented and forwarded, though they should be
dropped instead.
cq300244303 IFC1, IFC2

In 1xchSTM-1/chOC-3 Multiservice IFM (LIO2203), the MS layer signal degrade
fault will not be reported when the SDH port receives the MS BIP errors and the
error rate is greater than the configured signal degrade threshold. The BIP counters
will increment in the 'show interface' CLI command.
cq300244557 ELC1
SLI mode change between VLAN AC and trunk AC on the fly causes traffic cut
on the SLI.
cq300244660 CDC1, IFC1

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).
cq300244781 CDC1, CDC2, ELC1, IFC1, IFC2

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.

12
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.
cq300244894 CDC1
In network element boot-up with CDC1 units, with a configuration that exceeds
the recommended maximum scalability limits of the NE, the L2 configuration
of some flexible IRB interfaces may remain in shutdown state until manually
refreshed. This is due to IRB IF UP state transition message getting internally lost
because of message buffer overflow.
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.
cq300245101 CDC1
In some rare cases, registering enhanced CLI commands for BRAIN ASIC
debugging can cause a spontaneous reset of the network element.
This enhanced ASIC debugging support is now not loaded by default, but has to
be manually enabled in the network element at the start of a debugging session.
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-PWE3 circuits
may remain down.
cq300245362 CDC1, CDC2

OSPF session on IFC/IRB does not come up if the IRB interface is bound to VRF.
cq300245383 CDC1, CDC2

The new passive CDC may go to spontaneous reset immediately after CDC
switchover.
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.
cq300245501 8605 NE, 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.
cq300245520 8609 NE
Rare NE software crash when IEEE1588 boundary clock is enabled.
cq300245645 8611 NE
When VC-QoS is defined for a PWE3 entry and the matching outer label tunnel
entry has no QoS defined, the multi-segment PWE3 may go down.
cq300245725 8611 NE
RSVP trace route does not function and returns error.

13
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.
cq300245952 ELC1
The Delay Response message does not contain the same correction value as the
Delay Request.
cq300245987 8605 NE, 8609 NE, 8611 NE

After upgrade, IEEE1588 configurations related to acceptable-master settings
will be lost.
cq300246699 CDC1, CDC2, IFC2

The 'shutdown' command for IFC/IRB resets IRB's IP MTU back to the default
value 1500.
cq300247059 CDC1, CDC2

IFC IRB has distributed ARP database and there is a variation in ARP expirations
timers between units. An ARP entry that expires first on control card may
temporarily cut the traffic that is using the ARP entry.
cq300247384 CDC1, CDC2

Reloading of the active CDC will cause MAC disappear for flexible IRB in other
units during CDC booting, If a CDC switchover happens after booting and before
MAC distribution, MAC disappear permanently.
cq300247726 CDC1, CDC2

Passive CDC will crash, if more than one VLAN shaper groups are added or
deleted. Configuration is changed successfully and no impact on traffic.

14
2 Known Restrictions and Bugs
2.1 Restrictions in 8600 Smart Routers FP4.1
• IFCs cannot be part of the ELC1 based flexible mode IRB configuration at all, neither on the
bridging nor on the routing side. The routing side IFCs may appear to be working until ELC1
IRB reconfiguration happens, after which IFC traffic through ELC1 IRB is cut.
• 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.
• 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.
• Multicast replication due to flooding in VPLS network transient situations may exceed the ELC1
with IRB forwarding performance of 10 Mpps. Fourfold replication of unknown destination and
unicast traffic may exceed the 20 Gbps bidirectional traffic limit with average packet size of 250
bytes. 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-PWE3
termination to VRF are supported.
2.2 Bugs
cq300109805 CDC1, IFC1, IFC2, 8605 NE, 8609 NE, 8611 NE, 8620 NE
If changing the IP MTU value to a higher value without shutting down the
interface, the interface does not take the new MTU size into use.
Impact: Packets that are larger than the prior MTU setting will experience
unnecessary fragmentation on the IP layer on the affected interface.
Risk of occurrence: This unnecessary fragmentation will always occur if an
interface is up during the IP MTU change to a higher value.
Workaround: Give the "shutdown" CLI command and then the "no shutdown"
command to the interface where IP MTU has been increased.
cq300116238 CDC1, 8605 NE, 8609 NE, 8611 NE, 8620 NE

When a Telnet connection is initiated from the network element, the TCP port used
cannot be specified. Instead the default port number is always used.
Impact: Telnet connections to third-party network elements that are using
non-standard port numbers cannot be established.
Workaround: Not available.
cq300126508 CDC1, 8605 NE, 8609 NE, 8611 NE, 8620 NE

Traffic towards a particular VPN IP prefix may stop if this VPN IP prefix is
configured simultaneously by BGP and static configuration entry.
Impact: The traffic forwarded via the affected VPN route may stop.
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.

15
cq300129850 CDC1, 8605 NE, 8609 NE, 8611 NE, 8620 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.
cq300134123 CDC1, IFC1, 8620 NE

The number of shapers that can be associated to a VLAN is limited to 930 in a
8620 smart router and 961 in a 8630 smart router.
Impact: Not known
Workaround: Not known
cq300136667 CDC1, IFC1, 8609 NE, 8611 NE, 8620 NE

RSVP FRR switchover times <50 ms protection cannot be guaranteed. The
number of protected LSPs and interface technology in use affect slightly the
switchover times. The best-case switchover times are ~5 ms, typical performance
is 40-70 ms while in some setups it can be up to 500 ms.
Impact: Not known
cq300148763 8605 NE, 8609 NE, 8611 NE

The "reload-sw" CLI command in the FRR application causes a 1800 ms cut time
before FRR finds an alternative network route.
Impact: Not known
cq300149748 8605 NE
For a large number of PPP timeslot groups configured, and when groups are
created and deleted, the system sometimes hangs. This happens when there are
around 300 PPP interfaces configured, and the hang happens specifically when a
PPP interface is deleted. Currently there is a system level limitation to support 256
logical PPP/HDLC pseudowires on the E1/T1 interfaces and the system works fine
with traffic on all 256 logical interfaces without any issues.
Impact: Not known
Risk of occurrence: This issue is related to scalability numbers and, as there
already is limitation at system level, the risk of occurrence is lower.
Workaround: The system already supports the workaround of 256 logical PPP
interfaces.
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 line card(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.

16
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.
cq300160637 ELC1, IFC2

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.
In large configurations the "show interface" CLI command might cut and drop the
tail of the report.
Impact: The "show interface" CLI command report tail might be cut when there
is a large number of sub-interfaces per physical interface.
Risk of occurrence: Rare.
Workaround: Use a detailed sub-interface query instead of the "show interface"
query if the report tail is missing.
cq300163609 CDC1, 8605 NE, 8609 NE, 8611 NE, 8620 NE

While logged in through AAA, a RADIUS user will not be able to create a local
user with the same username as currently logged in.
Impact: No other impacts than this: Only creating a local user with exactly the
same username that was used when logged in using RADIUS fails.
Workaround: Log in with a different username than is used for the RADIUS
server. Now it is possible to create an "original" user in the local database.
cq300167470 8605 NE, 8609 NE, 8611 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.
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.

17
cq300171215 IFC1
When replacing the IFC1 part of the MSP1+1 protection group with a replacement
card which contains earlier configuration of the same network element and card.
During the bootup the replacement card is not fully handled as a replacement
but uses some of the old configuration and might mix up the operation of the
protection group.
Impact: Data cut is possible when doing switchover or directly after bootup
is done.
Risk of occurrence: Often under the described circumstances.
Workaround: Reboot both of the cards, one after the other. A better solution is
to clean the configuration of the replacement card before the installation with the
"clean-start" CLI command.
cq300171590 CDC1, 8605 NE, 8609 NE, 8611 NE, 8620 NE

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

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

18
cq300184995 CDC1, 8605 NE, 8609 NE, 8611 NE, 8620 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.
cq300192871 8605 NE, 8609 NE, 8611 NE

If an interface is bound to a LDP signalled PWE3 and that PWE3 is unbound
and a non-signalled 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 signalled 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.
cq300192888 8605 NE
The network element may have a spontaneous reset in the circumstances
where the element has a configuration of more than 100 CESoPSN PWE3s
and simultaneously more than 250 Mbps bidirectional routed IP traffic with a
packet size smaller than 256 bytes is fed to the network element. Extensive ACL
configuration with more than 100 CESoPSN PWE3s may also expose the system
to a spontaneous reset.
Impact: The network element may have a spontaneous reset.
Risk of occurrence: Seldom under the described circumstances.
Workaround: In mixed CESoPSN and routing configuration keep the number of
CESoPSN PWE3s moderate or do not to have a high volume of IP traffic with a
small packet size.

19
cq300193476 8605 NE, 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.
Risk of occurrence: Always, when the 'show interface' command is executed.
When the CBR VP interface is created with the default Supported Service
Category (UBR) and the interface is reverted from the switched to terminated
state, the supported category list is extended to include all 5 service categories.
Impact: The protection mechanism to prevent the user from configuring VCCs
with wrong service categories does not always work.
Risk of occurrence: Occurs in a typical case.
Workaround: Remove additional service categories after reverting to the
switched mode.
cq300193502 8605 NE, 8609 NE, 8611 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.
cq300194305 IFC1, 8620 NE

An n-to-1/VCG pseudowire stops carrying traffic if its traffic parameters are
changed from an IMA VC circuit, which is a part of an n-to-1 pseudowire.
Non-IMA VC circuits can handle the same kind of change in traffic parameters
without data cut.
Impact: Data transmission is affected.
Workaround: Delete the n-to-1 pseudowire configuration and then reconfigure it.
cq300194914 8609 NE, 8611 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 get dropped.
Risk of occurrence: Only during congestion.
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.

20
cq300195374 8605 NE, 8609 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.
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).
cq300195694 8609 NE, 8611 NE

ATM OAM Rx cells are not counted correctly on IMA interfaces.
Impact: The OAM Rx counter is always zero.
cq300197715 8605 NE, 8609 NE, 8611 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.
cq300198107 CDC1, IFC1, IFC2, ELC1, 8605 NE, 8609 NE, 8611 NE, 8620 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.
Workaround: Make names unique with the first 48 characters.
cq300200379 IFC1, IFC2

PPP links may not always be inserted into an MLPPP group during an automated
test.
Impact: MLPPP group cannot be configured with a desired PPP interface.
Risk of occurrence: Minor.
Workaround: Deletion and recreation of PPP interface can be attempted.
cq300200538 8605 NE, 8609 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.

21
Action "ac-defect-action pw-down" does not work for TDM pseudowires.
Impact: In the case of CESoPSN or SAToP attachment circuit failure, the
pseudowire is not torn down and it still sends AIS traffic through the network, thus
consuming bandwidth unnecessarily. This is a problem if the network bandwidth
is a bottleneck.
Workaround: Do not configure non-active TDM pseudowires.
FTP/CLI login attempts may cause a temporary (15-minute) denial of the
emergency snapshot functionality.
Impact: Emergency snapshot is not written to the flash and thus the latest
snapshot cannot be restored if necessary.
Workaround: Disable FTP and CLI (Telnet/SSH) when there is no need to use
them.
cq300208836 8605 NE, 8609 NE, 8611 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.
cq300210342 CDC1, IFC1, IFC2, 8620 NE

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

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

22
cq300213169 IFC1, IFC2, ELC1, 8605 NE, 8609 NE, 8611 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.
cq300213714 CDC1
After configuring a tracking delay for VRRP there is a period of 2 x "max delay
interval" when the tracking delay is not increased. During that time the tracking
delay works with the initial value. Tracking delay starts to increase correctly after
the period of 2 x "max delay interval".
cq300214596 8609 NE, 8611 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.
cq300215122 CDC1, 8605 NE, 8620 NE

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

23
cq300218033 8605 NE, 8609 NE, 8611 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.
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.
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:Trhw-
drDeallocateLinkId(iLink=65512) failed, rc=4097, instId(0x64016000
0x405a0500) Finished AtmcdDeleteVxCtpConnection rc=4097 scm2 console
error message:
------------------------------------ AtmcdDeleteVxCtpConnection:TrhwdrDeallo-
cateLinkId(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.
cq300219014 8609 NE, 8611 NE

Deleting a route-map sometimes fails when trying to delete it from 8000 intelligent
network manager.
Impact: The "delete route-map" command fails.
Risk of occurrence: Occasionally.
Workaround: The customer can repeat the delete from 8000 intelligent network
manager and it will work on the second try.
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).
cq300219948 IFC1, IFC2

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.

24
cq300220057 ELC1
When multicast/broadcast frames greater than 1518 bytes are received in a
line card or sent from it, the Rx/Tx multicast/broadcast frame counts are not
incremented. Instead, these packets are counted as unicast packets.
Impact: Statistics do not work correctly for the mentioned packets.
cq300221874 CDC1, CDC2, 8605 NE, 8620 NE

SNMP traps are sent to an unknown socket if SNMP socket creation fails.
Impact: Control card switchover occurs.
Workaround: Disable SNMP traps.
cq300222531 CDC1, 8605 NE, 8609 NE, 8611 NE

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

8609 smart router and 8611 smart router can exhaust memory buffer pools
when numerous OSPF instances are in the same VRF. When the pools become
exhausted, the 8609 smart router will display messages about bpool buffer errors
on the console. When the pools become exhausted on the 8611 smart router,
errors about bpool buffers will also be displayed on the console and eventually
the SCM will reset.
Impact: The memory pool exhaustion can result in control card reset depending
on what process tries to get a buffer from the exhausted pool.
Risk of occurrence: Low. The normal use of OSPF instances is a unique VRF for
only a very small number of OSPF instances. This normal use scenario is safe and
results in no occurrences of this defect.
Workaround: Do not put more than a few (1 - 3) OSPF instances into a single
VRF (including the default VRF). By default an OSPF instance is placed in the
default VRF, specific VRF assignment is needed when more than a few OSPF
instances are created.

25
cq300225036 CDC1, 8605 NE, 8609 NE, 8611 NE

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.
cq300225142 IFC2
PE-bound VLAN statistics are not counted for an Ethernet PWE3 (traffic coming
from an attachment circuit). Port statistics and CE-bound VLAN statistics are
counted.
Impact: PE-bound VLAN statistics are not counted for an Ethernet PWE3 (traffic
coming from an attachment circuit).
cq300225143 ELC1
In group shaping, an ELC1 line card cannot be in the ingress side of shaped traffic.
As a result, in group shaping, traffic coming through the ELC1 does not participate
in group shaping but in port shaping (if any).
Impact: In group shaper configuration, traffic where the ELC1 line card is at
ingress is not shaped.
Workaround: If a group shaper is configured, the ingress card must be IFC2 (full
support) or IFC1 (some limitations).
cq300225540 8609 NE, 8611 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.
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.
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.

26
cq300225787 8611 NE
Traffic will be lost on 4x10/100/1000BASE-TX HM (HMG2274) Electrical GE
ports at 10/100 speeds in a cabled connection and if the link speed is attempted to
be set to lower speed 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
mode auto speed 100 duplex full
mode speed 10 duplex full
mode speed 100 duplex full
cq300225896 CDC1, CDC2, IFC1, IFC2, ELC1

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

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

27
cq300226053 IFC1, IFC2, 8620 NE

If line loopback (loopback-to-line) is enabled on a 4xchSTM-1/chOC-3
Multiservice IFM (LIO2234) and a pseudowire redundancy group is configured
on the IFM, the operational states of the pseudowires belonging to the group go
DOWN.
Impact: If loopback-to-line is configured in 4xchSTM-1/chOC-3 MS IFM, the
pseudowire redundancy group configured in the interface will go DOWN and
traffic cut will be observed. When the loop is removed, the traffic recovers.
Risk of occurrence: Always under the described circumstances
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.
cq300226321 IFC2, 8605 NE, 8609 NE, 8611 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.
Workaround: Multiply the time by constant 1 nanoseconds/tick.
cq300226785 ELC1
ARP cache is not properly updated when an ARP entry moves from one interface
to another within the same ELC1 card This may happen when IP configuration is
created on an interface, then removed and recreated on another interface within
the same ELC1 card.
Impact: The moved ARP entry is not functional, and traffic to/via that IP address
will not flow.
Workaround: Clear the ARP cache with the CLI command "clear arp-cache".
This will clear all ARP entries in the entire network element so all Ethernet traffic
will be momentarily cut. An unused ARP entry will also expire, so it is possible to
avoid traffic breaks by waiting until the ARP entry expires before recreating the
IP configuration on another interface.
cq300227080 CDC1, 8611 NE

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

28
cq300227102 CDC1, CDC2, 8605 NE, 8609 NE, 8620 NE

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

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

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.
cq300227967 CDC1, 8620 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.
Risk of occurrence: Very rare.

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

29
cq300228011 CDC1, CDC2, 8605 NE, 8609 NE, 8611 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".
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
labelled 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.
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.
cq300228311 ELC1
The interface hold down feature does not clear the link down fault immediately
after the link is physically UP.
Impact: Troubleshooting with the present implementation will have no impact on
the functionality.
Workaround: "show interface <interface>" will show the exact state
of the hold-down behavior, i.e. when the link is down, the state will be
"entering-hold-down", and when the link is up and restoring, the "state" will be
"hold-down", "exit timer" will be decrementing and exit packet counter will be
incrementing (if exit packet counter is configured) .
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.
cq300228901 CDC1, 8605 NE, 8609 NE, 8611 NE, 8620 NE

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

30
cq300230985 IFC2
When VLAN statistics are enabled for a VLAN interface on an IFC2, a line card
that is rebooted (for example due to software upgrade) may enter into a very
long reconfiguration loop. The reconfiguration loop will eventually finish, but
uses a lot of CPU. This may starve other tasks in the system of CPU, and cause
network protocols to timeout and clear established sessions. The problem has
been corrected in FP4.0 SP3, but older SW may have left internal databases in
inconsistent state. Thus upgrade to FP4.0 SP3 may also be affected. Upgrade from
FP4.0 SP3 to newer SW is not affected.
Impact: Network protocols may timeout and clear established sessions. This
will cause traffic cut until the sessions are re-established. The duration of the cut
depends on the number of VLANs with statistics enabled. This may be several
minutes in large configurations.
Risk of occurrence: Increases in direct proportion to the increase in the number
of statistics enabled VLANs. Hundreds of statistics enabled VLANs are almost
certain to cause data breaks.
Workaround: Disable VLAN statistics during SW upgrade.
cq300231620 CDC1
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.
Risk of occurrence: Always under the described circumstances, more likely
with big configurations.
cq300232115 IFC1, IFC2, ELC1, 8605 NE, 8620 NE

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

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

31
cq300232742 CDC1, CDC2

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

The actions service-policer and no-reverse-path-verification cannot be configured
for the same ACL sequence number by CLI.
Impact: The latter action of the ACL rule is not performed.
Workaround: Use 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.
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.
Workaround: Ensure that the ingress interface is not congested when configuring
pause frame settings.
cq300234582 8605 NE, 8609 NE, 8611 NE

When the flood of packets received is more than 600 pkts per second (8602
smart router /8609 smart router /8611 smart router) or 300 (8605 smart router
/8607 smart router), the remaining packets, i.e. the packets exceeding the 600
(8602/8609/8611) or 300 (8605/8607) limit will be dropped in the host rate limiter.
Due to this some control packets will get missed. BFD may get 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.
cq300234989 8605 NE
During RSVP tunnel flap (primary or secondary), upper layer software may fail to
remove tunnel handle resource from bookkeeping. As a result of this, a stale handle
resource entry is left in the bookkeeping. At this time if an LSP protection switch
is initiated due to fiber cut or link down, the software tries to trigger path protection
in the hardware with the stale handle and that results in an error message.
Impact: An error message may appear on the console during LSP protection
switch event.
Workaround: Network element restart is required to clear the stale entry in the
software.

32
cq300235064 8611 NE
SNMP shows twice the same interface. This can be seen in different MIBs (e.g.
interfaces, atm).
cq300235115 ELC1
Unknown unicast MAC flooding has a performance issue in ELC1 VSI
configurations with a large number (m) of SLIs. When a number (n) of nearly
simultaneous unknown DA frames need to be flooded to a large number (m-1) of
SLIs, the actual number of flooded packets (p) is less than required n*(m-1) to
ensure that the frames are flooded to all SLIs.
Impact: Flooded frames do not always reach destination and they need to be
resent.
Risk of occurrence: High in very large VSI (>100 SLIs) configurations.
Workaround: Avoid large VSI configurations, that is, VSIs with more than 100
SLIs, excluding mesh-pseudowires.
cq300235294 ELC1
Received pause frames are ignored by ELC1. The command for enabling and
disabling pause frame handling does not have effect on ELC1.
Impact: The NE does not react to pause frames.
cq300235456 8605 NE, 8609 NE, 8611 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.
cq300235531 IFC1, IFC2

ETHoMLPPP pseudowire statistics (Tx Bytes and Tx packets) are not incremented
with 24xchE1/chT1 Multiservice IFM (LIE2226) when "no ppp mp headers
mlppp" is configured. This issue is related only to statistics and traffic will not be
affected.
Impact: ETHoMLPPP pseudowire Tx statistics are not incremented when "no
ppp mp headers mlppp" is configured
cq300235687 IFC1
The far end link state is down after giving "shutdown-if" command in the near end.
Impact: Whenever the "shutdown-if" command is given in the near end, the far
end link will go down.
Workaround: shut/no-shut on the near end link will make the far end link up.

33
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.
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).
cq300238440 CDC1, CDC2

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

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

In case of very heavy load, sending a poll message fails even once the network
element is reset.
Impact: In case issue occurs, the network element reboot will be initiated.
Risk of occurrence: Very rarely.
When an ATM interface is protected, and the protecting side interface is removed,
the protection is left into an inconsistent state. Removing the working side may
cause a spontaneous reboot of the network element.
Impact: All traffic will be lost until the network element recovers.
Workaround: Always remove protection before removing an interface.

34
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.
cq300238925 CDC1, CDC2, 8611 NE

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.
Workaround: Issue the command from CLI.
cq300238998 ELC1
When associated ACL contains unsupported actions for ELC1, faults are not
raised accordingly.
Impact: Faults are raised and cleared incorrectly. This has no impact on services.
Risk of occurrence: Always when configuring unsupported ACL actions for
ELC1.
Workaround: Do not configure unsupported ACL actions for ELC1, 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.
cq300239128 CDC2
In CDC2 protection topology, when more than 7350 PWE3s are attached to VLAN
interfaces, the CDC2 in the passive slot will go to continuous booting. The active
CDC2 will be up and running.
Impact: CDC2 protection will be degraded.
Workaround: Do not attach more than 7350 PWE3s to VLAN interfaces.
cq300239150 IFC1, 8605 NE, 8620 NE

PPP OSINL-CP Link Down fault may appear on PPP or ML-PPP interfaces which
have IS-IS enabled. This is a false alarm which does not affect traffic.
Risk of occurrence: High.

35
cq300239229 8605 NE, 8609 NE, 8611 NE

Traffic is cut for a short period of time (e.g. about 24 ATM cells) when the
1588 boundary clock is enabled with the command “node-timing ieee1588 slave
enable-sci”.
Impact: Traffic will be cut.
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.
cq300239571 CDC1, CDC2

During software upgrade, the software package may be left unactivated with an
unexpected error.
Workaround: Software package needs to be reactivated.
cq300239602 8609 NE, 8611 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.
Workaround: Use static pseudowires.
cq300239762 ELC1
The number of learned MAC addresses exceeding 256K limit will be visible in the
MAC forwarding table (show bridging-instance) until manually cleared.
Workaround: Clear MAC table manually (clear bridging-instance name
<bridging-instance name> macs).
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.
Workaround: Re-enable IEEE1588 grandmaster with PPS input and disable
it again.

36
cq300240652 CDC2, 8609 NE, 8611 NE

PTP clock class and clock identity of an adjacent master is not shown with the
command 'show node-timing ieee1588 slave'.
cq300241252 CDC2, 8609 NE

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.
cq300241410 CDC1, CDC2, IFC2, IFC1

The 'show-ip-statistics' command may produce an error if the CDC in slot 1 is
physically present in the network element but not added to inventory.
Workaround: Either add the unit back to inventory or remove it from the rack.
cq300241569 8609 NE, 8611 NE

The command 'show npu load' will show incorrect wingine utilization values when
traffic sent to the NE exceeds 2.55 Gbps.
Risk of occurrence: Always under the described circumstances
cq300242104 CDC1
When a network element has non-stateful ARP configuration and a neighbouring
network element MAC address is changed, unnecessary ARP status messages
may be shown on the console.
Risk of occurrence: Sometimes under the described circumstances.
cq300242154 CDC2
IEEE1588 Packet Delay Variation (PDV) statistics do not work with boundary
clock. Querying the statistics will fail with 'instance not found' error.
cq300242270 8609 NE
When the user tries to configure queue length for different QoS classes to the
minimal value (that is, 1), and if traffic is sent for all QoS classes, traffic will
not be received at the expected rate.
Impact: After modifying the queue length to the minimal value, traffic will not be
received at the expected rate.
Workaround: Avoid configuring the minimal value for queue length.

37
cq300242297 IFC1, IFC2, 8605 NE, 8620 NE

ATM circuits, which are members of a VCG group, do not send OAM AIS cells
when the VCG PWE3 is down.
Impact: OAM AIS consequent action is missing from the VCG member ATM
circuits.
cq300242522 CDC1, ELC1, IFC1, IFC2, 8605 NE, 8609 NE, 8611 NE, 8620 NE
ARP cache entry may be left unexpired for an indefinite time.
Risk of occurrence: Dependent of ARP cache timer values, thus rare.
Workaround: ARP cache can be cleared, which should resolve the issue.
cq300243339 CDC1, IFC1

Some faulty or unusual received packets (e.g. IPv4 packet is too short, total length
is less than 20; or MPLS packet has expired, TTL = 0) can cause queue manager
reset in the unit.
Impact: Short traffic cut during queue manager reset. Very rarely can cause
network element reset.
cq300243436 IFC1
PPP LCP down alarm may appear on port 0 of 8xSTM-1/OC-3 POS (LIO2020)
interface module that is on module slot 1, if ELP protected interface 0 on module
slot 0 has activity on the protecting interface,.
Impact: PPP LCP down alarm becomes active and traffic may be affected.
Risk of occurrence: Sometimes.
Workaround: If possible, perform ELP switchover back to the working interface.
Routemap delete is not possible if the map is emptied and less than 30 seconds has
passed since the last BMI/CLI operation.
Workaround: If the last routemap section is removed, wait 30 seconds before
deleting routemap.
cq300243513 CDC1
After CDC switchover, Ethernet Bridging object instances are reported as having
unit 1 instead of the correct unit 14.
Impact: In the Bridging dialogue in 8000 intelligent network manager, the right
interface information cannot be mapped.
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.

38
cq300243760 CDC1, CDC2

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

When sending large frames exceeding IP/MPLS MTU through IRB there is
significant loss of frames. This is due to the fact that the fragmentation must be
handled by the CPU, which has a limited capacity and is protected by shapers.
Shapers will drop fragments quite early to prevent DoS attacks.
Impact: Loss of traffic exceeding IP/MPLS MTU, if the rate is high enough.
Risk of occurrence: Always when packets exceeding IP/MPLS MTU are sent
on a high enough rate.
Workaround: Network should be configured so that there is no need for
fragmenting MTU exceeded packets.
cq300243925 ELC1
There is no multicast storm fault for IRB IP interface. Storm protection however
is working.
Impact: There is no fault indication when the storm is on.
Risk of occurrence: Always under the storm.
cq300243977 8611 NE
On a LAG interface created over an FE/GE interface on 8611 smart router, IS-IS
routes drop and re-establish after an SCM redundancy switch.
Impact: When an SCM redundancy switch occurs, all IS-IS routes drop and
re-establish about 30 seconds after the switch completes.
This causes LDP and RSVP sessions to drop also. BGP and OSPF traffic are
not affected.
Risk of occurrence: High, 2 out of 10 times of switchover attempt.

39
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.
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, 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-tunnelled
LAG interface will not be successful, as equipment loopback can be configured
only on a tunnelled 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-tunnelled interface.
Workaround: Reconfigure the loopback configuration to the desired mode to
solve the issue.
cq300244461 CDC2, ELC1

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

When HP-SDH tester injects VC4-UNEQ error to the STM-1 port of
4xchSTM-1/chOC-3 Multiservice IFM (LIO2248), the port does not send back
VC4-RDI to HP-SDH tester.
Impact: VC4-RDI alarm is not received by HP-SDH tester.

40
cq300244478 ELC1
If the network element is operating as a IEEE1588 boundary clock (slaved from a
PTP input), the seconds part of the sent PTP frames is incorrectly set on ELC1s
that do not have the slave port. The nanosecond part is accurate and thus this as no
impact on phase synchronization accuracy. If the network element is operating as a
grandmaster (slaved from a 1PPS input) also the seconds part is updated correctly.
Impact: Customer cannot see proper calendar time from PTP messages sent from
ELC1s that do not have a slave port. However, phase synchronization works fine.
cq300244509 CDC2
In 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.
Risk of occurrence: Always when CDC2 control card(s) are installed.
Workaround: Before ESW upgrade, use the command "snapshot-config create
flash:" to create configuration backup. If previous FP must be restored after ESW
upgrade, activate first previous ESW version without reloading the cards and use
the command "snapshot-config restore flash:" to restore previous configurations.
cq300244511 IFC2
In 1x10GBASE-R R2 IFM (LIO2257), with UP MEP configuration, EOAM ping
for multicast packet size 5800 and greater will not be successful and the MEP will
enter LoC state. Multicast EOAM ping of size upto 5700 is successful.
Impact: EOAM UP MEP will go down with LoC state.
cq300244527 CDC1, CDC2, ELC1

When the passive CDC control card is rebooted, Y.1731 Loss Measurement
counters may get too high values: existing counter values are incremented by
32-bit maximum value 4294967296. This issue happens on both UP and DOWN
MEP, and also when MEPs do not reside on same line card (ELC1).
Impact: Loss Measurement shows too high values.
Workaround: For Current-statistics, clear the statistics with CLI command “clear
eth cfm mp lm”, and for History-records, re-initiate the LM sessions (e.g. remove
and add LM Initiator config).
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.
Workaround: Either filter with one route type only or retrieve all routes.

41
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.
cq300244819 CDC2, ELC1

Reload of the passive CDC2 may rarely cause ELC1 IRB reconfiguration to occur
and a 200 ms cut for part of the ELC1 IRB traffic.
Impact: 200 ms traffic cut on ELC1 IRB.
cq300244967 ELC1
VLAN tag is not added in PWE3(VLAN) egress direction(PSN-->AC) with
encapsulation 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.
Workaround: Use the "ethernet untagged" mode instead of the "ethernet-vlan
untagged" mode.
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.
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 behaviour 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 Routers
- FP4.1 ECE1 (4.1.71) for 8620, 8630 and 8660 Smart Routers or
- FP1.6 CIR1 (1.6.182) for 8605 smart router.
Never with older ESW versions.

42
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.
cq300245570 8609 NE
The command 'clear node-timing ieee1588 slave statistics' is not working.
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.
cq300245984 8609 NE
After SW upgrade from 8609 smart routers FP1.0.x to 8609 smart router FP1.2x
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.
Workaround: 1) Reapply the missing configurations manually
or, alternatively
2) Upgrade to FP1.1 first, and upgrade again to FP1.2 or FP1.3.
cq300246121 CDC1, 8609 NE, 8611 NE

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.
Workaround: The automatic switchover to the passive control card will help
in this case.
cq300246566 8609 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.
cq300246583 CDC2, ELC1, 8609 NE

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.

43
cq300246834 8609 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.
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: lbz2713_4.1.586
active SW is wrong: lbz2713_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.
cq300247521 8609 NE
Per-link delay asymmetry compensation is not yet supported for the IEEE1588
Boundary Clock.
Impact: Static error in phase/time synchronization output (PTP or 1PPS) which
may affect the end application (e.g., LTE-A), if very high time accuracy (in the
order of 10s of nanoseconds) is required per Boundary Clock.
Workaround: The expectation is that either equivalent length fibers are used or a
single fiber with bi-directional traffic.
cq300247622 CDC1, CDC2, IFC2

After upgrading from FP4.0 to FP4.1 IFC2 IRB may fail to resolve ARPs until the
node 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.

44
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 in the above explained scenario.
Workaround: Delete and recreate the Flexible IRB interface or add static MAC
for the same bridging instance on which IRB interface is created.

45
3 Rejected Bugs
3 Rejected Bugs
The CRs listed in this chapter have previously been communicated as known bugs. They will not be
fixed in future software releases and will thus be considered and documented as features, restrictions
and limitations. Consequently they are removed from the list of known bugs.
cq300026728 CDC1
1+1 protection of the management fast Ethernet interface does not work if VLANs
are used in the interface.
cq300067584 CDC1, IFC1, 8620 NE

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

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

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

The CLI command "clear interface statistics so u/m/i:k:l:m" fails for channelized
STM IFMs in ETSI mode.
cq300116345 IFC1
MLPPP data cut when the laser off (MSP 1+1 unidir).
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.

46
3 Rejected Bugs
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.

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.
cq300232369 CDC1, ELC1, IFC2

Port related QoS configuration commands fail after IFC2 upgrade to ELC1. Port
related CLI commands such as 'qos mapping use ingress' are not working after
the upgrade.
Impact: Port related QoS configuration commands fail.
Risk of occurrence: Occasionally.
Workaround: Reboot of the network element.
cq300234567 ELC1, IFC1, IFC2

When a target interface of static IPv4 routes comes up, packets are silently
discarded before associated ARP entries are resolved. For a large amount of ARP
entries this is seen as a short traffic cut.
Impact: Packet drops in static routes before ARP entries have been resolved.
Workaround: For large amount of static routes with different next-hops use static
ARP entries, enable BFD, or start using a routing protocol (OSPF, IS-IS).
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.

47
3 Rejected Bugs
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.
cq300243384 ELC1
IRB ARP cache is not cleared via normal IP interface ARP cache timeout, but
the ARP entry for the IRB network IP is refreshed automatically just before the
timeout. The ARP cache can only be cleared by the user with clear ARP cache
command.
Impact: ARP cache entries for IRB IP interface do not expire.
Workaround: The user can clear the ARP cache.
cq300244247 ELC1, IFC2

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

L3 broadcast packet storm can overload the CPU and cause MPLS protocols
to go down.
Impact: May cause traffic outage.
Workaround: If user is able to identify the interface where broadcast packets are
coming in, then shutting down that interface will recover the services.

48

8600 Smart Routers SR5.0 Service Pack 2 Embedded Software Release Notes

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

8600 Smart Routers SR5.0 Service Pack 2 Embedded Software Release Notes

Încărcat de

Drepturi de autor:

Formate disponibile

8600 Smart Routers SR5.

Document No. Date Description of Changes

© 2014 Tellabs. All rights reserved.

8600 Smart Routers SR5.0 Service Pack 2 76.8650-50172B

Terms and Abbreviations

76.8650-50172B 8600 Smart Routers SR5.0 Service Pack 2

8600 Smart Routers SR5.0 Service Pack 2 76.8650-50172B

1 8600 Smart Routers SR5.0 SP2 ESW Release Notes ............................................... 6

1.1 Application Embedded Software Codes.............................................................................................................. 6

2 Known Restrictions and Bugs ................................................................................... 15

2.1 Restrictions in 8600 Smart Routers FP4.1........................................................................................................... 15

3 Rejected Bugs ............................................................................................................. 46

76.8650-50172B 8600 Smart Routers SR5.0 Service Pack 2

1 8600 Smart Routers SR5.0 SP2 ESW Release

• 8605 Smart Router FP1.6

• 8605 Smart Router FP1.6 Embedded Software Release Notes (76.8616-50154B)

1.1 Application Embedded Software Codes

Network Element Card Base- ESW ESW Version

8600 Smart Routers SR5.0 Service Pack 2 76.8650-50172B

1.2 Supported Upgrade Paths

1.2.1 8605 Smart Router

1.2.2 8609 Smart Router and 8611 Smart Router

1 This upgrade path is not supported if IEEE1588 is used (see cq300245984)

76.8650-50172B 8600 Smart Routers SR5.0 Service Pack 2

1.3 Upgrade Related Notifications

1.4 Enhancements Compared to SR5.0 SP1 ESW

cq300241286 CDC1, CDC2, 8609 NE, 8611 NE

cq300243569 CDC1, CDC2, 8605 NE, 8609 NE, 8611 NE

8600 Smart Routers SR5.0 Service Pack 2 76.8650-50172B

1.5 Fixed Bugs Compared to SR5.0 SP1 ESW

cq300225574 CDC1, IFC2

cq300226720 ELC1, IFC1, IFC2

cq300229733 ELC1, IFC2

cq300231487 ELC1, IFC1, IFC2

cq300232810 CDC1, ELC1, IFC1, IFC2

cq300235736 CDC1, 8605 NE, 8609 NE, 8611 NE, 8620 NE

76.8650-50172B 8600 Smart Routers SR5.0 Service Pack 2

cq300238636 CDC1, CDC2, 8605 NE, 8609 NE, 8611 NE

cq300239554 ELC1, IFC1

cq300239567 CDC2, ELC1, 8609 NE

cq300239886 CDC1, 8605 NE, 8609 NE, 8611 NE, 8620 NE

cq300239980 CDC1, IFC2

cq300239983 CDC1, IFC2

8600 Smart Routers SR5.0 Service Pack 2 76.8650-50172B

cq300240706 CDC1, IFC1

cq300240869 CDC1, 8605 NE, 8609 NE, 8611 NE, 8620 NE

cq300240872 IFC1, IFC2

cq300240981 CDC1, CDC2, ELC1, IFC2, 8609 NE, 8611 NE

cq300241017 CDC1, CDC2

cq300241150 CDC1, IFC1, IFC2

cq300241508 CDC1, 8611 NE

76.8650-50172B 8600 Smart Routers SR5.0 Service Pack 2

cq300242280 CDC1, CDC2

cq300242485 CDC1, CDC2

cq300242787 8605 NE, 8609 NE, 8611 NE

cq300243115 IFC1, IFC2

cq300243539 8605 NE, 8609 NE, 8611 NE

cq300244097 8605 NE, 8609 NE, 8611 NE

cq300244303 IFC1, IFC2

cq300244660 CDC1, IFC1

cq300244781 CDC1, CDC2, ELC1, IFC1, IFC2

8600 Smart Routers SR5.0 Service Pack 2 76.8650-50172B

cq300244782 CDC1, CDC2, 8611 NE