009-3240-013 (39XX 51XX SAOS 6.12 Customer Release Notes) RevA

39XX/51XX Service Delivery and Aggregation Switches
Release Notes
SAOS 6.12.0.232
Whats Inside
New in this release
Issues fixed in this release
Issues found in this release
Issues fixed prior to this release
Issues found prior to this release
009-3240-013 - Standard Revision A

May 2014
Copyright 2013-2014 Ciena Corporation. All rights reserved.
LEGAL NOTICES
THIS DOCUMENT CONTAINS CONFIDENTIAL AND TRADE SECRET INFORMATION OF CIENA
CORPORATION AND ITS RECEIPT OR POSSESSION DOES NOT CONVEY ANY RIGHTS TO REPRODUCE
OR DISCLOSE ITS CONTENTS, OR TO MANUFACTURE, USE, OR SELL ANYTHING THAT IT MAY
DESCRIBE. REPRODUCTION, DISCLOSURE, OR USE IN WHOLE OR IN PART WITHOUT THE SPECIFIC
WRITTEN AUTHORIZATION OF CIENA CORPORATION IS STRICTLY FORBIDDEN.
EVERY EFFORT HAS BEEN MADE TO ENSURE THAT THE INFORMATION IN THIS DOCUMENT IS
COMPLETE AND ACCURATE AT THE TIME OF PUBLISHING; HOWEVER, THE INFORMATION CONTAINED
IN THIS DOCUMENT IS SUBJECT TO CHANGE.
While the information in this document is believed to be accurate and reliable, except as otherwise expressly
agreed to in writing CIENA PROVIDES THIS DOCUMENT AS IS WITHOUT WARRANTY OR CONDITION OF
ANY KIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document are
subject to change without notice.
Copyright 2013-2014 Ciena Corporation. All Rights Reserved
The material contained in this document is also protected by copyright laws of the United States of America and
other countries. It may not be reproduced or distributed in any form by any means, altered in any fashion, or
stored in a data base or retrieval system, without express written permission of the Ciena Corporation.
Security
Ciena cannot be responsible for unauthorized use of equipment and will not make allowance or credit for
unauthorized use or access.
Contacting Ciena
Corporate Headquarters 410-694-5700 or 800-921-1144 www.ciena.com

Customer Technical Support/Warranty
In North America 1-800-CIENA24 (243-6224)
410-865-4961
In Europe, Middle East, 800-CIENA-24-7 (800-2436-2247)
and Africa +44-207-012-5508
In Asia-Pacific 800-CIENA-24-7 (800-2436-2247)
+81-3-6367-3989
+91-124-4340-600
In Caribbean and Latin 800-CIENA-24-7 (800-2436-2247)
America 410-865-4944 (USA)
Sales and General Information 410-694-5700 E-mail: sales@ciena.com
In North America 410-694-5700 or 800-207-3714 E-mail: sales@ciena.com
In Europe +44-207-012-5500 (UK) E-mail: sales@ciena.com
In Asia +81-3-3248-4680 (Japan) E-mail: sales@ciena.com
In India +91-124-434-0500 E-mail: sales@ciena.com
In Latin America 011-5255-1719-0220 (Mexico City) E-mail: sales@ciena.com
Training 877-CIENA-TD (243-6283) E-mail: techtng@ciena.com
or 410-865-8996
For additional office locations and phone numbers, please visit the Ciena web site at www.ciena.com.
39XX/51XX Service Delivery and Aggregation Switches Release Notes

SAOS 6.12.0 009-3240-013 Standard Revision A
Copyright 2013-2014 Ciena Corporation. May 2014
IMPORTANT: PLEASE READ THIS LICENSE AGREEMENT (AGREEMENT) CAREFULLY BEFORE
INSTALLING OR USING CIENA CORPORATION (Ciena) SOFTWARE, HARDWARE OR
DOCUMENTATION (COLLECTIVELY, THE EQUIPMENT).
BY INSTALLING OR USING THE EQUIPMENT, YOU ACKNOWLEDGE THAT YOU HAVE READ THIS
AGREEMENT AND AGREE TO BE BOUND BY ITS TERMS AND CONDITIONS.
1. Right to Use License; Restrictions. Subject to these terms, and the payment of all applicable license fees,
Ciena grants to you, as end user, a non-exclusive license to use the Ciena software (the Software) in object
code form solely in connection with, and as embedded within, the Equipment,. You shall have the right to use the
Software solely for your own internal use and benefit. You may make one copy of the Software and
documentation solely for backup and archival purpose, however you must reproduce and affix all copyright and
other proprietary rights notices that appear in or on the original. You may not, without Ciena's prior written
consent, (i) sublicense, assign, sell, rent, lend, lease, transfer or otherwise distribute the Software; (ii) grant any
rights in the Software or documentation not expressly authorized herein; (iii) modify the Software nor provide any
third person the means to do the same; (iv) create derivative works, translate, disassemble, recompile, reverse
engineer or attempt to obtain the source code of the Software in any way; or (v) alter, destroy, or otherwise
remove any proprietary notices or labels on or embedded within the Software or documentation. You
acknowledge that this license is subject to Section 365 of the U.S. Bankruptcy Code and requires Ciena's
consent to any assignment related to a bankruptcy proceeding. Sole title to the Software and documentation, to
any derivative works, and to any associated patents and copyrights, remains with Ciena or its licensors. Ciena
reserves to itself and its licensors all rights in the Software and documentation not expressly granted to you. You
shall preserve intact any notice of copyright, trademark, logo, legend or other notice of ownership from any
original or copies of the Software or documentation.
2. Audit: Upon Ciena's reasonable request, but not more frequently than annually without reasonable cause, you
shall permit Ciena to audit the use of the Software at such times as may be mutually agreed upon to ensure
compliance with this Agreement.
3. Confidentiality. You agree that you will receive confidential or proprietary information (Confidential
Information) in connection with the purchase, deployment and use of the Equipment. You will not disclose
Confidential Information to any third party without prior written consent of Ciena, will use it only for purposes for
which it was disclosed, use your best efforts to prevent and protect the contents of the Software from
unauthorized disclosure or use, and must treat it with the same degree of care as you do your own similar
information, but with no less than reasonable care. You acknowledge that the design and structure of the
Software constitute trade secrets and/or copyrighted materials of Ciena and agree that the Equipment is
Confidential Information for purposes of this Agreement.
4. U.S. Government Use. The Software is provided to the Government only with restricted rights and limited
rights. Use, duplication, or disclosure by the Government is subject to restrictions set forth in FAR Sections 52-
227-14 and 52-227-19 or DFARS Section 52.227-7013(C)(1)(ii), as applicable. The Equipment and any
accompanying technical data (collectively Materials) are commercial within the meaning of applicable Federal
acquisition regulations. These Materials were developed fully at private expense. U.S. Government use of the
Materials is restricted by this Agreement, and all other U.S. Government use is prohibited. In accordance with
FAR 12.212 and DFAR Supplement 227.7202, software delivered to you is commercial computer software and
the use of that software is further restricted by this Agreement.
5. Term of License. This license is effective until terminated. Customer may terminate this license at any time by
giving written notice to Ciena [or] and destroying or erasing all copies of Software including any documentation.
Ciena may terminate this Agreement and your license to the Software immediately by giving you written notice of
termination in the event that either (i) you breach any term or condition of this Agreement or (ii) you are wound
up other than voluntarily for the purposes of amalgamation or reorganization, have a receiver appointed or enter
into liquidation or bankruptcy or analogous process in your home country. Termination shall be without prejudice
to any other rights or remedies Ciena may have. In the event of any termination you will have no right to keep or
use the Software or any copy of the Software for any purpose and you shall destroy and erase all copies of such
Software in its possession or control, and forward written certification to Ciena that all such copies of Software
have been destroyed or erased.

6. Compliance with laws. You agree to comply with all applicable laws, including all import regulations,
and to obtain all required licenses and permits related to installation and use of Equipment. Software,
including technical data, is subject to U.S. export control laws, including the U.S. Export Administration
Act and its associated regulations, and may be subject to export or import regulations in other countries.
Customer agrees to comply strictly with all such regulations and acknowledges that it has the
responsibility to obtain licenses to export, re-export, or import Software.
7. Limitation of Liability. ANY LIABILITY OF Ciena SHALL BE LIMITED IN THE AGGREGATE TO
THE AMOUNTS PAID BY YOU FOR THE SOFTWARE. THIS LIMITATION APPLIES TO ALL CAUSES
OF ACTION, INCLUDING WITHOUT LIMITATION BREACH OF CONTRACT, BREACH OF
WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS. THE
LIMITATIONS OF LIABILITY DESCRIBED IN THIS SECTION ALSO APPLY TO ANY THIRD-PARTY
SUPPLIER OF Ciena. NEITHER Ciena NOR ANY OF ITS THIRD-PARTY SUPPLIERS SHALL BE
LIABLE FOR ANY INJURY, LOSS OR DAMAGE, WHETHER INDIRECT, SPECIAL, INCIDENTAL OR
CONSEQUENTIAL INCLUDING WITHOUT LIMITATION ANY LOST PROFITS, CONTRACTS, DATA
OR PROGRAMS, AND THE COST OF RECOVERING SUCH DATA OR PROGRAMS, EVEN IF
INFORMED OF THE POSSIBILITY OF SUCH DAMAGES IN ADVANCE
8. General. Ciena may assign this Agreement to any Ciena affiliate or to a purchaser of the intellectual
property rights in the Software, but otherwise neither this Agreement nor any rights hereunder may be
assigned nor duties delegated by either party, and any attempt to do so will be void. This Agreement shall
be governed by the laws of the State of Maryland (without regard to the conflict of laws provisions) and
shall be enforceable in the courts of Maryland. The U.N. Convention on Contracts for the International
Sale of Goods shall not apply hereto. This Agreement constitutes the complete and exclusive statement
of agreement between the parties relating to the license for the Software and supersedes all proposals,
communications, purchase orders, and prior agreements, verbal or written, between the parties. If any
portion hereof is found to be void or unenforceable, the remaining provisions shall remain in full force and
effect.

v
Publication history
May 2014
Revision A
Release for SAOS 6.12.0.232.

vi
Contents
Publication history v
Contents vi
New in this release 1
Issues fixed in this release 2
Issues found in this release 11
Issues fixed prior to this release 18
Issues found prior to this release 19

vii
About this document

The system software for the 39XX/51XX Service Delivery and Aggregation Switches is
based on a common service aware operating system (SAOS) code base designed to
deliver consistent benefits across all Ethernet aggregation, distribution, and delivery
configurations. This document summarized the new features, fixed issues, and known
issues associated with this release.
This release supports the 3916, 3930, 3931, 3932, 3940, 3960, 5140, 5142, 5150,
5160 switches only.
3902, 3911, and 3920 switches are supported up to the 6.10.2 release.
Related Documentation
Ciena offers the following related documents:
39XX/51XX SAOS 6.12 Product Fundamentals
39XX/51XX SAOS 6.12 Software Management and Licensing
39XX/51XX SAOS 6.12 Administration and Security)
39XX/51XX SAOS 6.12 Configuration
39XX/51XX SAOS 6.12 Fault and Performance
39XX/51XX SAOS 6.12 Command Reference Manual
39XX/51XX SAOS 6.12 MIB Reference Manual (009-3220-011)
3916 Hardware Installation and Startup Manual (009-3226-001)
3931 Enclosure Installation and Startup Manual (009-3225-019)

viii
Packet Networking Glossary (009-3299-026)
Packet Networking transceivers Reference (009-2011-602)
Ciena Standard Cleaning and Equipment Safety Practices (009-2003-121)
Trademark Acknowledgements
Ciena acknowledges the following trademarks:
Ciena is a trademark of Ciena Corporation.
Juniper Networks, the Juniper Networks logo, JUNOS, Steel-Belted Radius,

NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc.
in the United States and other countries. JUNOSe is a trademark of Juniper
Networks, Inc. All other trademarks, service marks, registered trademarks, or
registered service marks are the property of their respective owners.
We wish to acknowledge the following copyrighted works that make up portions of this
software release:
libTACACS developed by Roman Volkov via SourceForge.net.
Please see copyright in ~leos/common/application/tacPlusMgr/tacClient/COPYRIGHT.

We have modified the source code for our usage. The source code shall be available
upon request.

New in this release 1
New in this release

Key Summary
JE-34911 Anchor: Support MEF 26.1 E-NNI Hairpin
JE-34912 Anchor: Static MC-LAG
JE-35119 MPLS Enhancements
JE-35896 Support In Service SW Upgrade (ISSU): Phase 1: Rapid Start
JE-35898 Supporting TWAMP v6
JE-35899 RADIUS Round Robin Search Method support
JE-35901 RADIUS Accounting
JE-35903 Port-based PFG support
Support comprehensive (non-simplified) L2/L3 Hashing algorithm with no need to
JE-35904
enable MAC learning
JE-35908 MPLS On Demand Activity & Route Trace
JE-35909 BFD Performance Improvements
JE-35916 PW Status for Static PWs (RFC 6478)
JE-35920 Support SNMP set for wwpLeosBenchmark MIB
JE-35924 6.12.0: Support 10GE BiDirectional Single Fiber SFP+
JE-35926 Static MC-LAG (with NNI ICCL)
JE-36524 EVC Ping (IPv6)
JE-36527 TWAMP Multi-NNI (with DCL deny)
JE-36529 RFC 2544 UNI Generator and UNI Reflector IPv6
JE-37000 1588v2 OC (5150) & Advanced Synchronization License support
JE-37200 Anchor: IEEE 1588 - Boundary Clock Support
JE-38236 Support new 10G DWDM tunable SFP+
JE-38941 Configurable Ethernet L1 Inter-Packet Gap (IPG)
JE-39001 Support TSOP OC3 Modules RSP02SI1-IT3IT1
JE-40504 Support Tri-rate Copper SFPs on 3916 NNI ports 5 and 6
JE-40505 Allow the removal of traffic shaper

2 Issues fixed in this release
Issues fixed in this release

Customer Network
Affects Product
Key Release Notes Content Tracking Tracker
Features
ID ID
802.1x, RADIUS, JE- Dot1x authentication now correctly tries the second RADIUS R13-
Security 37240 server when the first one fails to reply. NE_0015
802.1x, Alarm Dot1X no longer reauthorizes with RADIUS unless config-
Mgmt, Fault Mgmt, JE- reauth is set to 'on'. Also, re-authentication now generates "Port R13-
Logging, Syslog, 37136 Auth" or "Port Not Auth" traps instead of "LinkUp" or NE_0013
System Stability "LinkDown".
ARP, Dataplane -
SAOS now transparently passes end customer DHCP and IPv6
CPU Sub Interface,
management (NDP) frames through the node and no longer
DHCP, IPv6 Mgmt JE- R14-
send the frames to the CPU to be processed. This protects the
Plane, Mgmt 37569 NE_0006
CPU from becoming unable to process other control traffic in
Interfaces, MPLS -
the event of a broadcast storm of these frames in the network.
L3 Interface Mgmt
CFM does not comply with the IEEE 802.1ag/8.1 standard for
JE- MEP Continuity Check Receivers to update their MEP CCM DB
CFM
14849 when CCMs with mismatched destination addresses and MD
levels are not accepted.
CCM frames are sent directly from the CPU to the egress port,
CFM, Dataplane - JE- so port settings that perform frame transformation functions,
General 21296 such as egress untagged VLAN, VLAN translation, CoS
mapping, and TPID re-marking are not applied.
CLI allows user to set LTM-Priority at MEP level. This MEP
JE-
CFM, CLI level priority setting is only available for LTM and not for other
38757
messages.
The SNMP tables with for Y.1731 test results now provide test
measurement results in real time that match what is shown in
JE- the CLI. These tables include:
CFM
37111 wwpLeosCfmExtDelaySessionTable
wwpLeosCfmExtFrameLossSessionTable
wwpLeosCfmExtSynLossSessionTable
All ICC-based type MA names are now padded to 13 characters
in the resulting MAID using the value 0. Also, MAID length
JE-
CFM validation is now performed correctly for all configurations to
39496
resolve issues with valid length MAIDs being rejected as too
long for some parameter combinations.
The "cfm mip-ccm-db show" command now correctly displays
the time since the last received CCM. Previously, it was always
JE- showed as "0". Also, the "cfm mip-ccm-db show vlan" command
CFM
32241 now displays the MIPs for the specified VLAN. Previously, it
always reported "MIP CCM database records found" even
though displayed "cfm mip-ccm-db show".

Customer Network
Affects Product
Features
ID ID
SNMP traps have been implemented in the WWP-LEOS-CFM-
JE- MIB to support simultaneous Y.1731 tests running on the
CFM
36009 system for a specific local-mep using the new OIDs for
<service-index,local-mep,remote-mep,test-id>.
JE- The cfm remote show y1731 table does not update the
Y1731-DM
31981 statistics for SLM.
JE- On the 5150 CLI, ports 1-48 were sometimes numbered 1.1 -
CLI
37974 1.48, and sometimes numbered as 1-48 and 1.1-1.48.
JE- Changing TWAMP parameters on an existing client session is
CLI, TWAMP
35785 now saved to the configuration file.
Tab auto completion of "cfm md" commands now works
JE-
CLI properly for Maintenance Domain (MD) names containing an
16660
asterisk.
On a 5160 with benchmark reflector testing configured and fully
JE-
Configuration Mgmt enabled, attempting to clear the all egress port queue group
39666
statistics no longer results in a system failure.
Configuration errors resulting from configuration augment
JE-
Configuration Mgmt operations now correctly generate SNMP traps and Syslog
15519
message entries.
The egress shaper CLI shows the Port Shaper Burst value
Dataplane - Egress JE- labeled as Kb implying a rate (in bits). It should be represented
QoS 38692 as a size in Kbytes, which is how it is represented on the CBS
and EBS.
When the scheduling mode is weighted and the scheduler
weight is configured as zero, strict scheduling does not appear
Dataplane - Egress JE- to have been applied to that queue. For example, with four
QoS 40020 different priorities of traffic, the schedule weight is set on queue
5 to 0. Queue 5 is expected to get a strict scheduling mode, but
instead, queue 4 gets a higher proportion of traffic.
Dataplane -
FCoS_RCoS,
Dataplane - After changing a ports resolved-cos-policy from fixed to dot1d-
JE-
General, Dataplane tag1-cos, the color re-marking now works properly without
37767
- Traffic having to re-boot.
Classification, PBB-
TE
When a link aggregation group is configured to use a custom
Dataplane - JE- RCoS ingress to egress queue mapping, the custom mapping is
FCoS_RCoS 36776 now applied. Previously, the custom mapping was ignored and
the Default-RCOS map was always used.

Customer Network
Affects Product
Features
ID ID
Dataplane -
FCoS_RCoS,
Dataplane -
JE- When traffic-profiling is globally disabled, remarking of the
General, Dataplane
37774 frame no longer occurs.
- Traffic
Classification, PBB-
TE
Dataplane - Adding or removing ports from an aggregation produces BCM
General, Dataplane errors in the console.
JE-
- Ingress Metering- Workaround: Delete and re-create the default traffic-profile after
37761
QoS, Dataplane - a port is added or removed from the aggregation where the
Traffic Classification traffic-profile is created.
JE- PFG show port has an error on the 5150 platform with 0 or 1
Dataplane - General
38584 optional modules present.
Missing length check before memcopy of control pkt into frame
buffer caused memory corruption. A length check is added prior
JE- R14-
Dataplane - General to memcpy of pkt into frame buffer. Current pkt size limit and
40230 NE_0009
frame buffer payload size are sufficient to avoid memory
corruption.
Under certain circumstances, while encapsulating a large
JE- amount of traffic and transiting large frames, the 5150 C130828-
Dataplane - General
36277 enhanced ports experience an overflow and become stuck in a 155
permanent full state.
Dataplane -
JE- MPLS Echo on 3942, 5142, and 5160 now drop frames whose
General, OAM-
41291 MAC DA doesn't match the MAC Address of the box.
MPLS Echo
For non-native PBB-TE control frame tunneling with a tunnel-
Dataplane - L2CFT, JE-
mode of L2PT, the priority of the tunneled control frame is now
PBB-TE 37671
correct.
Pressing TAB after typing in the command traffic-profile show
port <PortName> auto-completes with the next set of command
Dataplane - Traffic JE-
options and the first set of unique characters of the next option.
Classification 17103
Workaround: Backspace to remove the auto-completed text, if it
is not the desired command option.
When the traffic profiling mode for the port is set to standard-
Dataplane - Traffic JE- vlan, the system prevents setting the ip-prec, dot1d, and dscp
Classification 36264 classifiers. This fix prevents a system failure that occurred when
running the "traffic-profiling standard-profile unset" command.
The CLI prevents creation of a traffic profiles with unsupported
Dataplane - Traffic JE-
combinations of a non-zero CIR with a CBS of zero and non-
Classification 35661
zero EIR with an EBS of 0.

Customer Network
Affects Product
Features
ID ID
After enabling EOAM loopback on an NNI port with a
continuous port-based RFC2544 benchmark test running and
Dataplane - VLAN, JE- R12-
then removing the loopback, the port now remains in its VLAN
EOAM, RFC 2544 35440 NE_0053
forwarding group, and the benchmark generator properly
restarts.
No error message is displayed when unavailable dhcp12-relay
JE-
DHCP agent vlan is deleted in the system. When available multicast
37614
vlan is deleted in the system, an error message is generated.
Attempting to add both east and west ports as the RPL owner
JE-
G.8032 results in error, but actually configures the last entered port as
36045
RPL owner.
The system now checks all logical ring associations with a port
before clearing the "isG8032" flag upon deletion of the last
virtual ring under a logical ring. Previously, the flag was always
JE- cleared upon the deletion of the last virtual ring under an logical C140109-
G.8032
39101 ring. Since two or more logical rings can be associated with the 077
same port, clearing of this flag resulted in cases where the CLI
displayed the port as blocked, even though the port continued
to forward traffic.
When a port is removed from a VLAN and there is a
accelerated MEP configured on that port, the MEP is deleted
JE- from the software is not deleted from the hardware causing the
G.8032
35935 CCMs to be continued to be generated.
Workaround: Delete the MEP before the port is removed from
the VLAN.
Command ring-protection logical-ring show ring <ring>" no
JE- C131001-
G.8032 longer truncates the last character of a CFM service name
36738 123
when the name is greater than 25 characters.
G.8032, Link Agg -
JE- Ingressing L2PT frames are now correctly blocked by the ring C130906-
LACP, Link Agg -
36410 port in blocked state when part of a LAG. 134
Manual
When a switch from an external frequency lock (BITS) to a PTP
JE-
IEEE 1588v2 frequency lock occurs, the phase shift in 6.12 is smaller and
33585
remains within 1us.
In 1588v2 signalling messages, the TargetPortID is now sent as
all 1s. Previously, it was sent as all 0s, which did not comply to
JE-
IEEE 1588v2 the IEEE 1588-2008 standard and caused interoperability
37529
issues with many 1588v2 Masters\Grand Masters in the field,
because the signalling message was ignored.

Customer Network
Affects Product
Features
ID ID
The system now prevents creation of:
phase protection-group without creating frequency protection-
group
time-of-day protection-group without creating phase protection-
JE- group
IEEE 1588v2
36201 The system now prevents deletion of:
frequency protection-group while a phase protection-group
exists
phase protection-group while a time-of-day protection-group
exists
JE- If igmp-snooping is enabled after it has been disabled, it no
IGMP_Multicast
37680 longer continues to snoop the IGMP frames to the software.
JE- Port 1.31 on the 5150 now properly passes video streaming C140122-
IGMP_Multicast
39371 data towards the client port. 087
If you are using the (console) serial port, are using terminal
emulation software with a window that is not 24x80 in size, and
your session's More is turned on, then you will see occasional
problems where wider tables are formatted oddly. (Tables are
formatted assuming that up to 128 columns are available.)
Workaround:
1) Use telnet or ssh instead;
2) Turn More off;
3) Resize your window to 24x80;
JE-
IP ACL 4) Tell your session what your true window size is via:
31184
system shell session set window-width X window-height Y
The same kinds of formatting problems will be seen when
editing command lines that are longer than the lesser of one
screen width and the session's width setting; the fix is the
same.
This problem, where software is formatting display output for a
channel that doesn't have formatting feedback, is inherent and
has existed practically since serial ports were invented. The
fixes and workarounds are just as old.
The "ip-acl import" command now properly imports the link local
address. Previously, it imported the first IPv6 address and
JE- subnet (the global entry) of the remote interface. Because of
IP ACL
26575 this, enabling IP-ACL blocked IP interface control plane traffic
unless IP and loopback interface IP addresses and subnets
were added to the IP-ACL list.
IP-Routing, MPLS - If at least one TE or TP dynamic tunnel is successfully created
JE-
RSVP-TE, MPLS - and then the ISIS instance is disabled, subsequent newly
34065
Tunnel Mgmt created dynamic tunnels now remain operationally down.

Customer Network
Affects Product
Features
ID ID
Broadcast containment has been changed, so that filters are
not directly attached to or detached from physical port members
of a link aggregation group. Instead, the filters are attached to
JE- C140219-
Link Agg - LACP the port upon adding it as an aggregation member and
39689 130
detached upon its removal. This resolves a system failure that
occurred when removing ports with an attached broadcast filter
from an link aggregation group.
When configuring the IP address on the remote interface, the
system now checks if the subnet overlaps with the local
JE-
Mgmt Interfaces interface and the IP interfaces and prevents the
35745
misconfiguration. Previously, the misconfiguration was allowed,
but then removed after re-boot.
The 5150 operating in non-native PBB-TE mode no longer fails
JE- C130723-
Mgmt Interfaces when setting the remote management VLAN to a VLAN already
35989 061
associated with a PBB-TE tunnel.
JE- Disabling a primary spoke to allow a backup spoke to come up
MPLS - General
40464 in a protected dual-home E-Line no longer results in a re-boot.
In a maximum MPLS configuration, the CLI remains responsive
JE-
MPLS - General after disabling and then enabling an MPLS associated port,
35872
followed by "mpls tunnel show" commands.
ISIS area auth send-only and snp-authenticate values can be
JE- changed back to the default using either the set or unset
MPLS - ISIS
34670 command. Previously, the default values were not available
using the set command.
CPE can ping the IP interface outside its EVC/Subnet. Ideally,
MPLS - L3 Interface JE-
CPEs on each EPL should be able to ping the IP Interfaces for
Mgmt 35211
their respective EVC/Subnet but not the other one.
When an unknown statusTLV is recieved in an LDP notification
JE-
MPLS - LDP message, the Pseudowire operational state now correctly goes
26350
down and generates the remote fault.
JE- After disabling an MTU-s NNI port, a virtual circuit over a static
MPLS - LDP
26405 tunnel now correctly generates a remote "Tnl Tx" fault.
JE- MPLS Ping does not inherit TTL value specified on the tunnel
MPLS - OAM
34755 or pseudowire.
JE- MPLS ping fails even though data traffic and MPLS traceroute
MPLS - OAM
36119 are working on the tunnel.
Three new options have been added to the remark-rcos-policy
attribute in the traffic-profile standard-profile create and set
commands. The new options are remark-green-rcos-only,
MPLS - QoS, PBB- JE-
remark-yellow-rcos-only, and remark-both-rcos-only, and
TE 38666
support the ability to configure traffic profiling to remark the
frame's CoS with the R-CoS value without remarking the
CTAG.

Customer Network
Affects Product
Features
ID ID
The cienaCesMplsStaticIngressTunnelFrmCosPolicy MIB
JE-
MPLS - QoS object does not return the correct "fixed" policy value for static
27778
ingress tunnels. It always returns "rcos-mapped".
The cienaCesMplsStaticTransitTunnelFcosPolicy,
JE- cienaCesMplsStaticTransitTunnelRcosPolicy, and
MPLS - QoS
27785 cienaCesMplsStaticTransitTunnelRCosMapId MIB objects
return accurate values.
JE- The Pseudowire operational state reported in SNMP now
MPLS - VC
26675 matches the Pseudowire state reported in the CLI.
LDP session-history show active now show the active sessions
JE-
MPLS - VC which have been active prior to the LDP session-history disable
32845
and enable.
The MD5 key can now be configured for an IPv6 NTP server.
JE-
NTP Previously, an error message was displayed: "ERROR: Server
40487
not found.
JE-
NTP NTP server can now be displayed when it is set through DHCP.
37932
NTP logging is now written to the evt.log, which is capped at
JE- 80K and will rotate when exceeded. Previously, it was written to
NTP
40450 a separate ntp.log in the \tmp directory, and was only deleted
after every reboot.
JE- When AIS is disabled on the tunnel, the AIS profile no longer
OAM-AIS/LDI
35696 reverts to the default.
JE- The "ais profile show" command now shows the correct number
OAM-AIS/LDI
35133 of LSPs.
JE- An IP BFD session now becomes operationally down when
OAM-BFD
26689 both ends of the IP session are set to passive mode.
JE- BFD now goes down after changing the LER forward-out label
OAM-BFD
31110 to a different label.
When BFD is enabled, the session fault reason now correctly
JE-
OAM-BFD shows the start state. Previously, it showed as faulted because
35970
BFD global/session admin was down.
JE- The system now properly prevents creation of remote bridges
PBB-TE
12944 with the same bridge MAC address.
JE- For non-native PBB-TE, when the decap cos policy is fixed, Q-
PBB-TE
37283 in-Q L2 transform PCP values are now correct.
JE- The first time the statistics are shown for a VC, they display
PBB-TE
33954 correctly instead of 0.
JE- Byte counts on PBB-TE tunnel encap statistics are now correct.
PBB-TE
36002 Before they always showed as 20 bytes higher per frame.

Customer Network
Affects Product
Features
ID ID
For PM Instances with end-time configured outside of the
aligned 15-minute period end time, the actual end time will be
when either the aligned 15-minute period end time is reached
(at 00, 15, 30, and 45 minutes after the hour) or when SNMP or
Performance JE-
CLI is used to view the PM Instance and its Current Bin,
Monitoring 33532
whichever occurs first. When using the CLI to view the Current
Bin of such PM Instance, the first display of the PM Instance will
indicate an operState of enabled. A subsequent display of the
PM Instance will then show an operState of disabled.
Port - This release fixes a 5160 issues where the operational status of
JE-
Mgmt/Statistics, a port would remain in a down state after multiple system
36094
System Mgmt reboots.
The "port show port <PortName>" command output now
displays the value of the operational state for the following
Port - JE- items:
TBD
Mgmt/Statistics 35822 Ingress FCOS->RCOS Map
Ingress RCOS Remark L2
Egress RCOS->FCOS Map
The POST error code for the 3930 FPGA port in the packet test
JE-
POST has been corrected. Previously, it showed up as port 11, even
36238
thought there are only 10 ports.
JE-
POST Greylin POST errors are reported correctly.
36237
JE- In the WWP-LEOS-BENCHMARK-MIB.my file, the MIB
RFC 2544
19103 objectswith read-write access now do support SNMP set.
RMON file names now contain the IPv6 address of the
JE-
RMON operational interface if IPv6 is the only interface. Previously, if
37531
IPv6 was the only interface, the file name contained 0.0.0.0.
JE- Installing a license key on one CLI session now properly
RSTP
22634 synchronizes to other active CLI sessions.
When mstp disable is applied in base configuration, if RSTP is
JE- R14-
RSTP configured to be enabled, it will be after startup. Previously, it
39076 NE_0007
was disabled.
The pwUp and pwDown traps have two operational statuses
JE-
SNMPv3 that should indicate a range of PWs if multiple are brought up or
26877
down, instead traps are sent for each PW.
On the 5160, a port in the oam-services role are not included in
JE-
SNMPv3 the snmpwalk of the WWP-LEOS-PORT-STATS-MIB for the
35424
wwpLeosPortTotalStatsPortId object.
JE- The SNMP Agent reports OIDs are now in order for the LLDP
SNMPv3
29179 standard MIB.
JE- SNMP now supports the use of IPv6 link local addresses on 6.x
SNMPv3
36556 devices.

Customer Network
Affects Product
Features
ID ID
JE- This release fixes an issue where repeatedly enabling and
SNMPv3
37322 disabling the DHCP client caused a SAOS heartbeat crash.
The "software cancel" command appears in the CLI for all
Software Mgmt - JE- platforms, but is only supported on the 3911 and 3920 for 2-
Upgrade 19257 stage upgrade. When run on platforms other the 3911 and
3920, the command does nothing.
Syslog messages now correctly identify source IPv6 addresses.
Previously, if the device had link local, SLAAC and manual
JE-
Syslog addresses configured, then the SLAAC was used in the Syslog TBD
38201
message. If it had link local and manual addresses configured,
then the link local address was used.
JE- Tab auto-completion is now supported for Syslog collector IP
Syslog
22394 addresses.
Changing the system shell global login timeout or timer to
JE-
System Mgmt another value is now correctly displayed with the system shell
38765
show command.
JE- The 5150 now handles TACACS user name or password
System Stability
35852 greater than 500 characters.
If a serial console, Telnet session, or SSH session is terminated
JE-
TACACS abnormally, the TACACs stop message is now correctly
13008
generated for TACACs logging.
When XCVR-A10S31/55 and XCVR-A40S31/55 (100M SFP
JE-
Transceivers single fiber) are installed on the 5142 platform without fiber
36113
inserted, the LEDs remain off and the port down.
JE- Disabling TWAMP on an individual UNI port no longer results in R13-
TWAMP
37542 the loss of other TWAMP sessions. NE_0023
JE- Simultaneous LMM/DMM tests no longer causes bad Near Loss C140417-
Y1731-LM
41365 and Far Loss values to be returned. 066

Issues found in this release

Customer
Affects Product Network
Key Release Notes Content Tracking
Features Tracker ID
ID
Core dump occurs from dot1xMgr on startup with specific
configuration. The system crashed while attempting to
802.1x, RADIUS,
JE- perform a system downgrade to 6.10.2.110. Dot1x is
Software Mgmt -
39327 receiving the port state changes in an order that is causing
Upgrade
a deinit function to be called on something where the init
had not yet been called.
When Down MEP is created on VS EVPL, the AC port VC
CFM, Dataplane - JE-
ethertype policy was All. Y173 DMM had port ethertype. All
General 41963
other CFM frames (CCM, LMM, LBK, LTM) have 0x8100.
When VS CVID=SVID, the UNI port ethertype policy was
CFM, Dataplane - JE-
vlan-tpid or All. Down MEP Y1731 DMM frames were
General 41962
untagged.
Attempting to create a CFM service with the same name as
a deleted CFM service with a configured MIP generates an
JE- C131216-
CFM error.
42143 132
Workaround: Delete the MIP configuration prior to deleting
the CFM service.
The ingress untagged traffic was double mapped by ingress
Dataplane -
JE- port fixed-Rcos and then mapped by ingress FCos > RCos.
FCoS_RCoS,
38565 The untagged traffic should be mapped by the fixed R-Cos
Dataplane - General
of the ingress port only.
Dataplane - JE- On 5142 and 5160, the virtual switch adds its own priority
FCoS_RCoS 40218 when frames exit the UNI port state of the system.
On 5160, when port 20 is used as a QiQ NNI port, after
Dataplane - General, removing port 20 from SVLAN, traffic continues to transmit
Dataplane - Q-in-Q, JE- out on this port.
Dataplane - Virtual 40095 Workaround: Disable/enable port 20. Traffic will stop
Switches egressing port 20 and start egressing the newly added NNI
port.
A port set to traffic-profiling mode standard-dot1dpri and
configured with multiple profiles with the same VLAN allows
its mode to be changed to standard-VLAN in which the
profiles should be unique for a VLAN. However, once the
Dataplane - Ingress JE-
mode has been changed, the node does not allow the
Metering-QoS 39037
configuration of further traffic-profiles using the same VLAN
on that given port.
Workaround: Delete all the profiles except one per VLAN,
and then change the mode.

12 Issues found in this release
Customer
Features Tracker ID
ID
Dataplane - Ingress JE- When a VS is using tunnel mode L2PT, L2CFs do not
Metering-QoS 39594 adhere to the traffic profile.
Dataplane - MAC
JE- When multiple MPLS VSs learn the same MAC, flow mac
Learning, MPLS -
41589 show mac only returns the first VS.
General
In flow mac show, all PWs and mpls VS are returned
Dataplane - MAC JE-
correctly. In flow mac show mac, the PW is missing in
Learning 41590
the Port column. The VS is returned correctly.
When a PBT VS has an EVPL as port 4 VLAN2 and the
second EVPL is port 4 VLAN10, with MAC learning enabled
and traffic coming from both the EVPLs, flow show mac
displays both MACs as though they came against VLAN 2
Dataplane - MAC JE- (the first of the EVPLs) instead of displaying one each from
Learning 39387 VLAN 2 and VLAN 10. The UNI port is also not displayed.
Flow show mac output should display the correct UNI
VLANs and appropriate UNI port from where the MAC is
learned.
Dataplane - Resource Make sure applicable transport OAM resources are
JE-
Mgmt, OAM-MPLS allocated on Enduro devices prior to creation of any MPLS
42159
Echo based service on the device.
G.8032 cannot protect the reserved VLAN of a sub-port
Dataplane - Sub-port JE- based virtual switch. This means that G.8032 cannot protect
Interface, G.8032 40930 the traffic within a ring topology if the frames are being
switched by a sub-port-based virtual switch.
For EVC Ping6, Case C is not working for the 3960/5150
with translate-tag 0. The EVPL is added to the VS with
CVLAN 24, but through the use of vs-12-transform, the
CVID is popped and the STAG is pushed on in the ingress
direction. Through the QiQ network, the frame only has the
Dataplane - Virtual
JE- STAG on and is used to ping the remote NTEs SVLAIN IP
Switches, IPv6 Mgmt
38411 interface address. The CVID should be popped off as the
Plane
EVPL is added to the virtual-switch with a translate-tag of 0.
For the 3960, the CVIC is popped off, however, the internal
VLAN 4095 is pushed on as the inner tag. Once the
NDP/Ping packet arrives at the remove NTE, it is not
processed.
A module numbers does not need to be specified as module
1 is implied. Only the license number needs to be specified.
Feature License JE- However, if you dont specify a module number, the key fails
Mgmt 41304 to install and the error message: In valid module number is
shown in the CLI.
Workaround: Add the module number to the license file.

Customer
Features Tracker ID
ID
When an RG is the slave and on an RG active member
when there are LAGs other than the MC-LAG, disabling
aggregation globally and enabling it back again causing
G.8032, Link Agg - JE-
traffic restoration time of up to 8 seconds. The workaround
MC-LAG 41605
is to configure the RG as the master or not to globally
disable aggregation on the active RG member when the RG
is the slave.
When G8032 is used with LAG ports, when a port is
disabled, the failover time is not guaranteed to be sub-
50ms. This is due to the fact that this operations involves
JE-
G.8032 two failovers. The first within the LAG when the LAG port is
40458
disabled as the ports are brought down sequentially and the
second is a G8032 failover as a result of the LAG becoming
inoperational.
The 3931 1588 Boundary Clock can support a maximum of
JE- three 1588 Ordinary Clock client sessions.
IEEE 1588v2
42303 Workaround: Only connect to three or fewer clients to a
3931 BC.
A large two-way time error occurs with Paragon-X master-
slave emulation when using one-step mode.
JE-
IEEE 1588v2 Workaround: When running a time error measurement
42188
using Paragon-X master-slave emulation, run in two-step
mode instead of one-step mode.
Multiple Precision Time Protocol (PTP) output interfaces
cause synchronization issues to GrandMaster and Ordinary
JE-
IEEE 1588v2 Clock slave.
42211
Workaround: Ensure that you only use a single IP interface
for PTP.
The 5150 cannot lock to adjacent neighbor when in BC
mode. The device stays in Acquiring Lock and never locks
JE-
IEEE 1588v2 to the upstream device.
40768
Workaround: Use 1PPS and/or BITS/SyncE input refs to
provide timing.
Timing cannot be recovered on a 5160 when using a TP-
5000 as a virtual switch member connected to an EVC.
JE-
IEEE 1588v2 Workaround: Use an IP-interface using straight VLAN to GM
39872
to recover the timing. Then use a second IP-interface to
generate EVC/VS timing across the network.
When an NNI port ethertype-policy is all and ethertype is
JE-
IP-ISIS 0x88a8, the ISIS frames se 0x8100 and ISIS adjacency
41754
cannot form.

Customer
Features Tracker ID
ID
For an MC-LAG configuration, use system-priorities below
32768 for the RG and the DHD. If the RG system priority is
JE-
Link Agg - MC-LAG more than 32768 and the RG is the Master, this results in a
42161
transient traffic loss when the Primary RG member node
resets, although the issue corrects itself.
In MC-LAG configurations, set the reversion hold time to at
least 1 minute or choose the RG as master for LACP
JE-
Link Agg - MC-LAG negotiation. This issue is with the DHD trying to revert
41518
before the RG is ready to revert. The high reversion time
prevents this issue.
With DHD as the Mater, when aggregation is disabled
globally on both the RG members and enabled back again
JE- on the primary RG member, the LAG takes about 14
Link Agg - MC-LAG
41996 seconds to converge in the case of LACP short timeout and
about 90 seconds when using Long timeout. The
workaround in this scenario is to use RG as the master.
When using revertive mode for MC-LAG, and a small
JE-
Link Agg - MC-LAG reversion delay, traffic drop can occur. The work around is
41182
to use a reversion delay of 1 minute or longer
Aggregation goes out of distribution for two to three seconds
with short timer and up to 50 seconds with long timer when
JE-
Link Agg - MC-LAG there is a failure to both Primary, Backup RG, and Primary
42160
RG is enabled. This occurs with both DHD as master and
RG as master.
When downgrading to SAOS 6.11.0, the aggregation ports
JE- are in the configuration, but they do not show up in Agg
Link Agg - MC-LAG
39747 show. The Agg ports should show up if it is downgraded.
Workaround: None
MC-LAG switchover and reversion time are all over one
JE-
Link Agg - MC-LAG second if large amounts of VLANs are associated with the
39909
aggregation port on the DHD.

Customer
Features Tracker ID
ID
When a LAG is configured with Asymmetric configuration on
both ends, for e.g. when one node contains more/less
number of links in the LAG than the other end, the behavior
of the LAG is undetermined. This is due to the fact that the
ports which or not in the LAG still send LACPDUs which can
cause a contention on the peer to choose the right ports for
JE-
Link Agg - MC-LAG the LAG. If the LAG ports are not going to match on both
40727
ends, one workaround is to mark the port ports which are
not in the LAG as being in Manual mode so that they don't
send LACPDUs anymore. For e.g. if Node A has port 1 & 2
in LAG and Node B has only port 1 in the LAG and port 2 is
not added to any LAG, port 2 on Node B should be put in
Manual mode.
Reversion post reboot does not occur when the system
JE- priority is the same for multiple RG groups.
Link Agg - MC-LAG
42198 Workaround: Set different system priorities on RG, or set
RG as the master.
MC_LAG reversion does not work after nodal warm
reboot/recovery while DHD is the master. The failure applies
JE- on both protection modes and on all revert delay settings.
Link Agg - MC-LAG
42273 Workaround: Perform a cold reboot or power cycle to
perform MC-LAG switchover or revision, or configure the
RG as the master.
For an MC-LAG configuration, if reversion needs to be
JE-
Link Agg - MC-LAG turned ON, either with the DHD or RG being the master, use
41413
a reversion delay of 1 minute or longer.
Interface Manager does not report duplicate IPv6 addresses
on the remote interface after a reboot.
JE-
Mgmt Interfaces *Workaround: Enabling/disabling the remote interface will
41301
re-initiate a DAD. The remote interface will correctly show
DAD.
There is inconsistency with Port MTU on the 5160 device
which allows traffic to exceed the max-frame size in one
MPLS - General, JE- direction, but not the other. There should be consistency in
MPLS - VC 40379 both directions.
Workaround: Use 4-bytes less than whatever max-frame-
size is set to on the NNI port when transmitting to a 5160.
Egress MPLS traffic exceeding port Max Frame Size is not
dropped (non-T3 platforms). The ports Max Frame Size
JE-
MPLS - General (MFS) should allow only frames that are at or below the
41071
configured size to ingress or egress the port. This is not the
case for MPLS on the 3960 and 5150.

Customer
Features Tracker ID
ID
NTPv6 server establishes a server condition of syspeer
that changes to Candidate when the MD5 authentication is
JE- disabled in dual stack. The NTPv4 server resumes the
NTP
40581 syspeer state afterwards, which could cause temporary
disruption of NTPv6.
Workaround: Do not disable ntp md5 authentication.
There is a potential risk that the NTP log may keep growing
out of disk space. The log is deleted after every reboot, but
JE-
NTP the devices in the field normally do not get rebooted for
41700
months or years.
Workaround: Delete ntp.log manually or reboot the system.
A system with a remote interface and IP interface
JE-
NTP configured does not synchronize to an NTP IPv6 multicast
42362
server after reboot.
OAM-BFD, System JE- Prior to deleting an IPv4 interface, disable an existing IP-
Mgmt 41108 BFD session that traverses the IPv4 interface.
A BFD session configured with different intervals between a
SAOS 6.12.0 and a SAOS 6.11.0 device will not negotiate
to a common BFD session interval value. The defect lies in
JE- the SAOS 6.11.0 image.
OAM-BFD
42119 Workaround:
When SAOS 6.11.0 is the image used for a BFD session
peer, make sure both the BFD peers are configured with a
common transmit and receive interval.
The total Tx and Rx is showing the sum of CC frames plus
JE-
OAM-BFD the number of CV frames prior to issuing the clear stat
40462
command.
The LSP-BFD session is not getting established while
having NENDs BFD role as active and FEND role as
passive, and chassis reboot is done to make label range to
JE-
OAM-BFD effective.
41378
Workaround: Configure both sides of the BFD session on
the Active BFD session peer or reboot the chassis with the
passive BFD session peers.
IP and LSP BFD sessions do not recover after chassis
JE-
OAM-BFD reboot when BFD peers are in a passive role.
41593
Workaround: Do not use BFD peers in a Passive role.
When the agg port is the UNI interface to a PBT V-S, the
MAC learning rate is poor, between 10-30 macs/s on a
JE-
PBB-TE 3930. When a phy port is the UNI interface, the learning rate
38766
is ~4500 macs/s on a 3930.
Workaround; Do not use an agg as the UNI port.

Customer
Features Tracker ID
ID
An auto-negotiated multi-speed port is impacted by the
admin speed setting such that if the speed setting is less
than the negotiated rate, the port throughput will be limited
JE- to the configured speed. This only impacts egress traffic.
Port - Mgmt/Statistics
41853 The speed setting should have no impact on the port when
auto-neg is enabled.
Workaround: Turn auto-neg off on both sides or set the
speed to gig.
RFC2544 IPv6 test causes the device to become in
JE-
RFC 2544 accessible as a generator for the 3916, 3930 and
39862
3931platforms.
If the "chassis reboot delay" is set to be longer than 1hr, the
reboot always occurs after 1hr. If configured to be less than
Software Mgmt - JE- or equal to 1hr then the reboot occurs according to the C140516-
Upgrade 42120 configured delay time. 062
Workaround: Do not use a reboot delay value greater than 1
hour.
XCVR CIENA-AGI XCVR-000CRJ Rev001 is not supported
JE- in ports 5/6 of 3916-900/901/902 platforms This new
Transceivers
41782 000CRJ XCVR shows show link up with lights on when
inserted into port 5 or 6 of one of these 3916 platforms.
XCVR A10Y31 is not recognized on random ports of
multiple devices after warm restart/upgrade. This results in
being unable to query the XCVR information. Note that this
JE-
Transceivers does not affect the link status of the XCVR.
38849
Workaround: Remove and re-insert the affected XCVR or
power cycle the device or perform a cold reboot using the
chassis reboot cold-start command.

18 Issues fixed prior to this release
Issues fixed prior to this release

This section is a place holder for any tracking fixed issues for any future 6.12
releases.

Issues found prior to this release

Customer Network
Affects Product
Features
ID ID
For 802.1x authentication, if the switch is in MSTP mode,
802.1x JE-31143 even with MSTP disabled, the port continues to block traffic
after the port is authenticated.
CPU rate limiting is counts and drops ARP packets when a C131007-
ARP JE-41789
remote interface is created and attached to a virtual switch. 128
If CFM is disabled globally and a CFM service is configured
which need OAM resources, if the resources are not available
CFM, Dataplane -
JE-35499 there is no error returned at this point. This issue does not
Resource Mgmt
occur if CFM is globally enabled when the CFM service is
configured.
When using software based CCMs, use an Ethertype value of
0x8902. This is the default value and this is also the value
CFM JE-34721 required by the 802.1ag standard. When using an Ethertype
which is different, the CCMs will not be recognized as actually
being CCMs.
If the number of CFM stacks is exceeded, MEP configuration
is lost. For example, if there are 511 MEPs and 4 ports in the
CFM JE-23929
associated virtual switch, adding a 5th port to the virtual
switch causes 103 MEPs to be lost.
Setting the CFM EtherType to the same value an EtherType
in use by another protocol (such as PBB-TE) can cause other
CFM, PBB-TE JE-22913
protocol packets to be classified as CFM.
Workaround: Ensure that the CFM EtherType is unique.
At times, the CLI does not respond to the "cfm show" show
command on the 3930 with Mulit-NNI twamp set up, 10
TWAMP client sessions and 20 TWAMP server sessions
CFM JE-24788
running, 530 CFM local MEPs, 8192 CFM remote MEPs
configured. CFM CCM packets has been sent at 400
packet/second.
There are 2 issues here:
1. PBT services are created with an 'Alarm Priority' of 1.
Virtual switch and VLAN services are correctly created with a
CFM JE-24429 default value of 3. Requirement CFM-SER-7 specifies that
default value shall be 3.
2. CFM service detail show for the service does not display
Sender TLV type.

20 Issues found prior to this release
Customer Network
Affects Product
Features
ID ID
On 3930, 3931, and 3960 switches with 4 SNMP servers and
CFM, Port - 512 CFM services on port 9, disabling port 9 results in
Mgmt/Statistics, sending 2048 SNMP CFM traps, which causes SNMP agent IPAGR9-
JE-23699
SNMPv3, Syslog, to timeout and the guardian heartbeat to fail the system. NE_0053
System Stability Workaround: Decrease the number of CFM services on Port
9 (such as 256 instead of 512).
If a CFM service with up MEPs is created over a VPLS virtual
switch and provisioned with a uni-directional VLLI instance,
CFM, VLLI JE-26759
when the CFM service detects a peer fault and moves to the
"no CCM" state, the CFM service does not show an RDI fault.
Maintenance Association (MA) and CFM service names are
CFM JE-18171
limited to 43 characters. The intended length is 45 characters.
With a CFM service running in accelerated mode over a PBT
tunnel (with PBT in Native mode) on a 5150 device, one may
see a MAC entry periodically and randomly appear and
disappear within the list of learned MAC entries when viewing
the MAC table via a "flow mac-addr show" CLI command.
This entry will contain the MAC address of the remote PBT
tunnel end-point, with the VLAN equal to the B-VLAN
reserved and used by a PBT tunnel end-point local to the
CFM, Dataplane -
JE-31487 5150.
General
Note that this anomaly of the remote end-point MACs
appearing and disappearing in the MAC table will have no
impact on functionality nor the switching behavior of CFM or
PBB-TE frames. The remote PBT tunnel end-point MAC entry
is not referenced for CFM frames originating from the device,
nor data frames entering the PBT tunnel at the device's local
tunnel end-point.
Workaround: None
Untagged CFM frames received on a port based subscriber
CFM JE-28519 port are forwarded out the provider ports as double tagged,
but should be single tagged.
In case of CFMoPBT or CFMoMPLS, when there is an UP
MEP configured, the CCMs for this UP MEP do not contain
the RDI flag when they're supposed to. This can mean that in
CFM JE-34195
case of uni-directional faults, one end cannot detect the fault
since we need RDI to indicate a fault to the end that doesn't
detect the fault itself.

Customer Network
Affects Product
Features
ID ID
When MEP tag-mode is on, a CFM service over a MPLS
associated tunnel is always in IS fault. It never counts the
CCMs as received and does not discover the remote MEP.
CFM, MPLS - OAM JE-33844 After disabling the MEP tag-mode, the service comes up
without fault. On a MPLS-TP co-routed tunnel with MEP tag-
mode on or off the service comes up fault free.
Workaround: Do not use tagged mode for CFM MEPs.
If a CFM service was previously deleted with a MIP
configured, then attempting to re-create it will fail. C131216-
CFM JE-30244
Workaround: Delete the MIP configuration prior to deleting 132
the CFM service.
LTR, LMR, DMR, LMR, and LSR frames can have Exp bit of
CFM, MPLS - OAM JE-32073
0 in tunnel label and PW label.
When a VLAN name changes, it does not properly display in
CFM JE-14709 the CFM service information. However, the CFM service
continues to work properly.
CFM, MPLS - A virtual switch CFM service continues to use the label of a
General, MPLS - virtual circuit even when it is no longer attached to that virtual
JE-32750
Tunnel Mgmt, switch.
MPLS - VC Workaround: Delete and re-create the CFM service.
Attempting to create a CFM service on a virtual switch after
the same CFM Service name was used by a VLAN fails.
Workaround: Remove the VLAN service, save the
configuration, and reboot. Then, create the CFM Service on
the virtual switch.
Note: Using a different CFM service name for the virtual
switch service name does not resolve the issue.
Alternative Workaround: Delete all CFM services from the C131216-
CFM JE-41547
virtual circuit's VLAN. Then, create the CFM service on the 132
virtual switch and re-create the VLAN services. The order that
services are created does not matter as long as the virtual
switch and virtual circuit both have no CFM services or MIPs
at some point after the virtual circuit is attached to the virtual
switch. After that, CFM can be configured on both the vs and
vlan in any order and previous CFM services names can be
reused if desired.
For ETH-SLM, if NTP is configured on the device it may take
some time to synchronize which results in the start time being
equal to the defaulted time (January 1st 2000) and the end
Y1731-DM JE-31922
time being equal to the now synchronized current time. The
duration is correct but the start and end times are not
consistent with the duration.

Customer Network
Affects Product
Features
ID ID
Y1731 frames with an Ethertype other than 0x8902 are not
recognized as valid Y1731 frames and are hence not
Y1731-DM JE-33157
processed. Use the Ethertype 0f 0x8902, which is the default
and the chosen value per the Y1731 standard.
On the 5150, with 64 10ms PBB-TE CFM services running,
when MIPs are configured for all these services, the tunnel
Y1731-DM JE-32522 flap continuously.
Workaround: MIPs are not recommended for 10ms
sessions.
5150 and 3960 CFM DMM frames always egress with a
Y1731-DM JE-34400 Ethertype of 8100 regardless of what Ethertype is set on the
egress port.
When the port is changed for a PBB-TE tunnel which has a
CFM service configure on it, the CFM session continues to
use the old port and it may not detect a fault. As a
Y1731-DM JE-34564 workaround when changing a PBB-TE tunnel port if there is a
CFM service configured on the Tunnel, delete the CFM
service and reconfigure it after the Tunnel port has been
changed.
On the 3911 configured with a CFM service over a Q-in-Q
virtual switch with two Provider ports (NNI) and two
subscriber ports, when DMM messages are sent from one
Y1731-DM JE-28449 subscriber port (MEP for the subscriber VLAN), the DMMs
are not forwarded out the second subscriber port (without a
MEP for the subscriber VLAN) even though both are
members of the subscriber VLAN.
Y1731-DM JE-30570 Statistics and service statistics are not clearing as expected.
The accelerated delay tests can sometimes yield an
Y1731-DM JE-33425 occasional high delay result of the order of tens of
microseconds, compared to the regular results in single digits.
The use of file names that contain spaces is not supported in
(at least) the 'file' commands. If you attempt to use a file
name that contains a space, it will be treated as multiple
CLI JE-34853 parameters rather than a single name.
Workaround: Do not use spaces in filenames. Rename file
names with spaces to something that does not include a
space.

Customer Network
Affects Product
Features
ID ID
CLI, Dataplane - On 3930, 3960, and 5150 switches, a hierarchical VLAN
General, based parent's child-mode cannot be modified when in
Dataplane - advanced mode. Attempting to do so, causes an error "Parent
Ingress Metering- JE-24374 is missing EVC(VS) classifier" which does not apply when the
QoS, Dataplane - child mode is not "vlan-cos."
Traffic Workaround: Delete the parent profile and re-create with the
Classification desired mode.
When Ctrl+C is entered at the CLI and the MPLS license is
not installed, an event similar to the following is generated.
However, this is not service affecting.
Event Record Number: 355
Date : 2012.03.02 17:11:47 (uptime 74481.189 seconds)
Level : EVT ERROR (10000003)
Message: getThreadPidByName: Can't find thread for name,
mplsOamMgr
Source : process_wrapper.c(710)
tag : default
CLI, OAM-MPLS C120220-
JE-25493 sw ver : 06-09-01-0100
Echo pid: 17222 (leos) 104
lwp: 17241 thread: 2b9da4b0
Calling Sequence
Address Nearest Symbol
0080a524 leos(getThreadPidByName+0xa8)
0089f3d4 leos(shellMenuCoreParser+0x4f0)
008a3a18 leos(shellMenuParser+0x178)
005ad88c leos(leosShell+0x7a0)
005ada84 leos(mainClientThread+0xc0)
**** END OF EVENT RECORD ****
A VC ping operation can fail over VC over TE tunnel with
CLI, MPLS -
JE-31783 PHP when it is operationally up and the LSP is operationally
General
up and can be pinged and traced.
Various show commands do not display in CIDR format, even
though the items configured with CIDR notation, including:
interface show ip-interface <InterfaceName>
ospf interface show detail
ospf data show ospf-instance <OSPFInstance> network
CLI, IP-IFM-SR JE-26274
isis tables show ip-ra
ip fib interfaceIpAddresses show
ip fib interfaceIpAddresses show details
ip fib interfaceIpAddresses show summary
ip route show

Customer Network
Affects Product
Features
ID ID
After installing a software package prior to 6.9.1 on a switch
currently running 6.9.1, saving the configuration and re-
Configuration booting does not properly convert the configuration and
Mgmt, Software JE-24777 leaves 6.9.1 commands in the configuration file.
Mgmt - Upgrade Workaround: Before installing a software package prior to
6.9.1 on a switch currently running 6.9.1, save the
configuration.
Configuration Running a configuration augment results in an "Unknown
JE-24608
Mgmt error" even if the TFTP sever is reachable and the file exists.
CPU rate limiting statistics always report "0" dropped and
CPU Protection JE-18316
passed for ARP, IGMP, and DHCP packets.
When control frame packets are sent at high rates, CPU rate
CPU Protection JE-13701 limiting does not protect the CPU as it should, and the system
drops the control protocol messages.
On the 5142, setting the encap-cos-policy to port-inherit on a
Dataplane - port within a virtual switch does not use the CVID dot1d
Access Interface, priority in the SVID priority.
Dataplane - JE-41844 Workaround: Set the port's egress frame CoS policy to map
General, RCoS to the L2 outer PCP:
Dataplane - Q-in-Q port set port <PortName> egress-frame-cos-policy rcos-to-l2-
outer-pcp-map
ARP frames are dropped when traffic profiling is in narrow
mode for IP management interfaces.
Dataplane - CPU
JE-22174 Workaround: Traffic profiling for IP management interfaces
Sub Interface
is not a typically used, but if it is the mode should be set to
wide.
When a link aggregation operates in LACP mode, LACP
frames are dropped and the link aggregation drops selected
Dataplane - CPU
JE-14646 ports when the rate of RSTP, LLDP, and LACP frames reach
Sub Interface
the default CPU rate limit.
Workaround: Change the aggregation mode to manual.
The 5142 and 5160 platforms require the resolved-cos-
remark-l2 true and egress-frame-cos-policy rcos-to-l2-outer-
pcp-map attributes to be set in order to remark an ingressing
Dataplane - Egress
JE-37549 frames pbit to the rcos mapped value.
QoS
Workaround: Use the port set port <port> resolved-cos-map
untrusted resolved-cos-remark-l2 true and port set port <port>
egress-frame-cos-policy rcos-to-l2-outer-pcp-map commands.
On applying an egress-frame-cos-policy on a 3916 NNI to
Dataplane - Egress remark the S-VID PCP to 0 for yellow traffic, the C-VID (only C130614-
JE-34826
QoS in the case of untagged-data-vid) tag is also undesirably 062
remarked with same PCP as that for S-VID tag.

Customer Network
Affects Product
Features
ID ID
Dataplane - Egress The "decap-cos-policy" attribute does not work for Ethernet
JE-23940
QoS Q-in-Q virtual switches.
Dataplane - Egress The "decap-cos-policy" attribute does not work for Ethernet
JE-23934
QoS Q-in-Q virtual switches.
The wdrr-granularity is intended to provide a means to control
the scheduling mechanism such that a small granularity gives
lower latency and higher jitter, and large granularity gives the
opposite. However, the actual operation is that the distribution
Dataplane - Egress
JE-24410 of the traffic flows is not accurate (based on configured
QoS
weights) when changing the wdrr-granularity from the default
1600 to 50.
Workaround: Keep the wdrr-granularity set to the default
value of 1600.
On the 3916, 3930, 3931, 3960, and 5150 platforms, an
option has been added to ports to ignore or apply the egress
CoS map. This map will remark an egressing frame's CoS
and DEI value. However, the behavior of this option is tied to
the ingress port's resolved-remark-l2 setting with enterprise
VLAN switching. When the ingress port is configured with a
resolved-cos-policy of either dot1dpri or l3-dscp, the ingress
resolved-remark-l2 must be "True" before the egress-frame-
Dataplane - Egress
JE-18180 cos-policy is applied. When the ingress port's resolved-cos-
QoS
policy is fixed, the resolved-remark-l2 is ignored, and egress
remarking control is based only on the egress-frame-cos-
policy. Also, on 3916, 3930, 3931, 3960, and 5150 platforms
the egress-frame-cos-policy at the port level controls egress
marking. Other platforms will always remark on egress. With
Ethernet Private Line (EPL) configuration, the egress-frame-
cos-policy controls the egress remarking regardless of the
ingress remark-l2 option.
Dataplane - Egress
JE-31581 WFQ does not work as expected when learning is disabled.
QoS
Remarking of MPLS TC/EXP bit value at LSR has a different
behavior on 3960 and 3930 platforms. When the
DefaultRcosFcos map is modified to map a specified R-CoS
value to a MPLS TC/EXP field value. On the 3930, the packet
Dataplane - Egress sniffed at ingress side of node shows that the MPLS TC/EXP
JE-34550
QoS field is changed to the configured value, and the L2-COS and
L2-VPN TC keep the original R-CoS value. On the 3960, the
MPLS TC/EXP field and the L2-COS are changed to the
configured value, and the L2-VPN TC keep the original R-
CoS value.

Customer Network
Affects Product
Features
ID ID
Dataplane - Egress
QoS, Dataplane - In native PBB-TE mode, the S-Tag is marked with C-Tag
FCoS_RCoS, JE-37506 pbit/DEI.
Dataplane - Virtual Workaround: Use non-native PBB-TE mode.
Switches
When sending a tagged IPv4 or IPv6 DSCP value of 32 with
Dataplane - Egress PCP value of 2 to a UNI port of a VPLS virtual switch with the
JE-36666
QoS port policy set to l3-dscp-cos, the traffic is marked with RCOS
2, rather than 4 (based on default RCOS map).
In PBB-TE native mode, custom frame CoS mapping on an
egress port does not work.
Dataplane - Egress
Workaround: When using frame CoS mapping to remark the
QoS, Dataplane -
JE-41003 DEI bit in egress frames in native PBB-TE mode, use the
Traffic
default Rcos-Fcos map name DefaultRcosFcos and set the
Classification
egress port egress-frame-cos-policy to rcos-to-l2-outer-pcp-
map.
Dataplane - Egress Egress shaper on a link aggregation group limits burst is not
JE-42091
QoS consistent between the 5160 and 5142.
Dataplane - An MPLS EPL attachment circuit loses L3 connectivity after
FCoS_RCoS, setting the fixed RCoS on the port, because the ARP frame is
C130924-
MPLS - General, JE-37171 sent to the CPU where it is then forwarded to the virtual
104
MPLS - QoS, swtich with the port level PVID on the frame.
MPLS - VC Workaround: Reboot.
Due to hardware limitations, configuring to remark on the
traffic profile and at the egress using the F-CoS map only
works for one or the other, but not both.
Dataplane -
JE-28399 Workaround: Set the ingressing R-CoS queue to be the
FCoS_RCoS
lower priority desired queue that will have DEI set. Police the
traffic as desired, then remark the green traffic to the
"better/higher" R-CoS.
For non-native PBB-TE, the inner tag can be changed on
decap but it shouldn't be under the following conditions:
Dataplane - the UNI port is configured for "i-stamp:push,e-match-
JE-29009 pop:stamp"
FCoS_RCoS
the UNI port is a VS member with a translate tag 0
the VS decap cos policy is fixed
Dataplane -
FCoS_RCoS, PBT CoS: When using native mode PBT setting of the decap-
Dataplane - Traffic cos-policy to leave is allowed in the CLI but is not supported
JE-37639
Classification, and should be blocked. The actual setting is not changed,
Dataplane - Virtual and uses what was set before.
Switches, PBB-TE

Customer Network
Affects Product
Features
ID ID
Dataplane -
FCoS_RCoS,
Dataplane - Traffic For PBB-TE in non-native mode, the DEI bit is not marked as
JE-37640
Classification, being drop eligible based on color.
Dataplane - Virtual
Switches, PBB-TE
On the 5160 platform, when an Ethernet virtual switch in a Q-
Dataplane - in-Q configuration has an EVPL with an Encap Cos Policy set
JE-37608
FCoS_RCoS to fixed, the S-tag of the egress frame is set to the vs-inherit
priority setting.
Remove any broadcast filters from a physical port before
Dataplane - Flood adding it to a link aggregation group. Otherwise, the system
JE-15814
Containment will generate a "BCM error -5: Table empty" fault on the serial
port every 15 seconds.
The broadcast-containment feature with containment-
classification set to l2-mcast (unknown L2 multicast) does not
Dataplane - Flood limit traffic in the following mac address ranges:
JE-17604
Containment 01-00-5E-00-00-00 to 01-00-5E-7F-FF-FF (IPV4 multicast
address range) and 33-33-00-00-00-00 to 33-33-FF-FF-FF-
FF (IPV6 multicast address range).
Upon downgrade from 6.9.1 to 6.8.0 builds, the classifier-
Dataplane -
JE-24878 mode setting reverts to the default setting of "wide."
General
Workaround: Manually set the classifier-mode to "narrow."
Dataplane -
General, If the traffic profile has the resolved-rcos-policy set, this policy
Dataplane - takes precedence over the RCOS->FCOS map configured on
Ingress Metering- JE-24351 the egress port. Similarly, if the remark-color-policy is set, the
QoS, Dataplane - new color for the packet is not used for CFI remarking at the
Traffic egress port.
Classification
39xx/51xx products comply with the weak-end system
model based on RFC1122. As such, the system responds to
Dataplane -
JE-32580 a ping request for any of its configured IP/management
General
interface IP addresses, from any of its IP/management
interfaces.
When PFG is enabled on MPLS IGP VLANs, MPLS tunnels
Dataplane -
JE-30743 BFD sessions may go down.
General
Workaround: Disable PFG on IGP VLANs.
Dataplane -
MPLS Echo on 3960 and 5160 receives frames whose MAC
General, OAM- JE-41611
DA doesn't match the MAC Address of the box.
MPLS Echo

Customer Network
Affects Product
Features
ID ID
Dataplane - The untagged profile can not be set to the non-conform-
Ingress Metering- JE-24146 standard-profile when the port mode is in advanced. Defaults
QoS are used instead.
Dataplane - When a frame contains multiple VLAN tags, classification and
Ingress Metering- metering does not work properly for virtual switch, outer
QoS, Dataplane - JE-24365 VLAN, and Class of Service (CoS), virtual switch and CoS,
Traffic and CoS only scenarios.
Classification Workaround: Use one VLAN tag.
If the port speed is changed to 100 Mbps, and then a traffic
Dataplane - profile is created with a CIR of 1 Gbps, the system does not
Ingress Metering- JE-15166 generate an oversubscription error. If the profile is created
QoS first, and then the port speed is changed, the system properly
generates an oversubscription error.
Dataplane - Ingress control frames are not metered correctly on the 3960.
Ingress Metering- JE-26753 They should hit the non-conforming profile and be discarded if
QoS they do not match the classifier.
When L2-CFT mode is set to L2TP and not transparent, L2TP
tunnelled frames are switched (and encapsulated) by the
CPU and not the hardware pipeline. PFG is currently not
Dataplane - L2CFT JE-35863 supported for CPU-switched frames. The result is that
tunneled RSTP control packets over PFG are broadcast to
ports with in the same forwarding group when the UNIV policy
is set different.
802.3X Pause Frames are not forwarded when bridges-block
Dataplane - L2CFT JE-35300
L2CFT is added to a virtual switch with a tunnel disposition.
The configured L2 control frame tunneling CoS value is not
properly applied to frames with the Cisco PVST MAC
Dataplane - L2CFT JE-24110
01:00:0C:CC:CC:CD on 3916, 3930, 3931, 3960, and 5150
platforms operating in Transparent mode.
The add ctrl-protocol command fails when run after changing
Dataplane - L2CFT JE-36111 mode from CE 1.0 to CE 2.0 by means of SNMP.
Workaround: Retry the ctrl-protocol command.
Dataplane - MAC Do not configure physical port settings when there is an
Learning, MPLS - JE-22876 MPLS attachment circuit attached to the virtual switch
VC associated with that port.
The number of learned MAC entries for a virtual switch is
Dataplane - MAC reported correctly, however, the number of flooded frames is
JE-16431
Learning less than it should be. For example, when 10000 MAC entries
are learned, only 9660 frames are reported as egressing.

Customer Network
Affects Product
Features
ID ID
When frames do not belong to a VLAN forwarding group for a
port, the frame should not be forwarded and the MAC
Dataplane - MAC
JE-11495 address should not be learned. On 3920 devices, the MAC
Learning
address is learned and the frame is forwarded to the original
receiving port.
The "flow mac-addr show vlan" command does not display all
MAC address entries for the VLANs shown in the "flow mac-
addr show" command. The "flow mac-addr show" command
Dataplane - MAC
JE-31192 includes entries where the VLAN is not an actual VLAN; it is
Learning
the VID that is part of the AC that the entry is learned against.
The "flow mac show vlan" command only shows MAC entries
that are learned on actual existing VLANs.
The 3916, 3930, and 3931 traffic profiling statistics are
Dataplane -
JE-19357 disabled by default, and resource-manager show does not
Resource Mgmt
reflect added counters when profiles created.
Dataplane - Traffic The 3960 drops 1 or 2 frames upon configuring the traffic IPAG78-
JE-23117
Classification profile statistics from off to on. NE_0021
When a traffic profile is created without specifying the CBS
Dataplane - Traffic and EBS, the system will use a default CBS of 256 and EBS
JE-24344 of 0, instead of accounting for the port's configured MTU.
Classification
Workaround: Specify the values for the CBS and EBS.
The 3911 and 3940 mis-classify the priority of frames with
Dataplane - Traffic Ethertype 0x9200. Also, these frames ingress as tagged, but
JE-13880
Classification are dropped before egress. These frames should be treated
as untagged frames.
Traffic profiling statistics are not always accurate. For
Dataplane - Traffic example, traffic rates exceed the PIR more than 13 Mbps, the
JE-11872
Classification traffic profiling dropped and accepted statistics are lower than
the actual number of frames.
When downgrading from a release with greater capabilities to
a release with less capabilities, the system software removes
Dataplane - Virtual
configuration for any items that exceed the capabilities. For
Switches, System JE-20247
example, if a 5150 running 6.9 with 1024 virtual switches
Stability
running 6.9 is downgraded to 6.8, only the first 512 virtual
switches remain after the downgrade.
The wwpLeosVplsVirtualSwitchEthDecapCosPolicy in the
Dataplane - Virtual wwpLeosVplsVirtualSwitchEthTable MIB object is not defined
JE-26495
Switches correctly. The inheritTunnel(3) value is not accepted and
returns a generic error.

Customer Network
Affects Product
Features
ID ID
When a port that is a member of a network facing virtual
Dataplane - Virtual
JE-14473 circuit is added to a virtual switch, its membership with the
Switches
VLAN associated with the virtual circuit will be removed.
After removing or adding the Advanced-Ethernet license the
Dataplane - Virtual
VS configuration can be lost. The VC configuration remains.
Switches, Feature JE-30952
Workaround: Re-configure all VS commands after the
License Mgmt
license is re-installed.
The "vlan translate show port <PortName>" command does
Dataplane - VLAN JE-19202 not always display entries.
Workaround: Use the "vlan translate show" command.
When a physical port (already added to a link aggregation) is
add to a VLAN and configured for VLAN translation, when the
port is removed from the link aggregation, the ingress VLAN
Dataplane - VLAN JE-19201 translation does not work, though the egress translation does
work.
Workaround: Re-boot to restore the ingress VLAN
translation.
The capacity of the egress VLAN translation table is limited to
Dataplane - VLAN JE-14722
about 4K rather than the expected capacity of 8K.
When a new remote address is obtained via DHCP on
devices that don't have a local interface, a "local IP Address
DHCP, Syslog JE-35311 changed" message is received via SNMP and Syslog. If the
device does not have a local interface these messages
should not be sent.
When the remote interface address is changed via DHCP the
DHCP, Syslog JE-35310 address that it is changed to is the user configured address
and not the new address.
The Errored Frame Event Window range is 14880-8928000,
EOAM JE-15418 but the IEEE 802.3ah-2004 standard requires a range of 0-
8928000.
Devices do not properly copy the peer's last local TLV state
EOAM JE-15419
information.
When devices are in Loopback transmit state with a Juniper
device, when the remote loopback is committed on the
Juniper, the device status changes to Loopback received
state but continues transmitting, which results in the CPU
EOAM JE-14869
load reaching 100%, and the loopback statistics being
skewed.
Workaround: Before committing remote loopback on a
connected Juniper device, stop loopback transmission.

Customer Network
Affects Product
Features
ID ID
On 3911 and 3940 platforms, stop EOAM loopback prior to
EOAM JE-12513 pulling the link. If EOAM loopback is running while the links
are pulled, the ports remain in a link up state.
On the 3940 platform, EOAM statistics for sent critical events
EOAM JE-12506 are not incremented locally, but they do increment as
received on the peer.
When an EOAM Loopback test is initiated, at times the
EOAM JE-33595 Loopback status can show 'Dis' (Disabled) instead of 'Lb-tx'
(Loopback-Tx)
File Mgmt JE-22006 Use "rm <corefile> -f" to remove corefiles from CLI
The tget <LocalFileName> <RemoteFileName> command will
File Mgmt JE-13919 delete the specified local file, even if the remote file does not
exist and the file transfer fails.
G.8032 JE-23214 Failover for G.8032 with aggregation ports exceeds 50ms.
When clearing a forced switch on a non-RPL owner, the WTR
timer is not taken into account. The restore time should be 5
G.8032 JE-22133 minutes but actually takes place in under 10 seconds. If the
forced switch and clear is executed on the RPL owner, then
the WTR timer is applied.
Restoration time for G.8032 with aggregation ports exceeds
G.8032 JE-24414
50ms.
Uni-directional failure does not send Signal Failure (SF) on
G.8032 JE-23812 both ports resulting in an inconsistent state, where local node
is in protecting state, but the remote nodes are idle.
MAC entries are learned on the 5150 platform after ERP
switching failover in hardware. However, they may not be
displayed in the CLI.
G.8032 JE-18130
Workaround: To ensure full display of the MAC table,
manually flush the forwarding database per VLAN or port, and
then display it.
Creating a CFM service against a VLAN that is currently
assigned as an R-APS VID for a virtual ring can prevent R-
APS control frames on the virtual ring from being propagated
to all ring nodes, and therefore cause an outage on the virtual
G.8032 JE-17538
ring.
Workaround: Do not create and enable a CFM service on a
virtual ring's R-APS VID, an alternative is to assign it to a data
VLAN member of the virtual ring instead.

Customer Network
Affects Product
Features
ID ID
Deleting and recreating IGMP on a VLAN causes General
G.8032, Query packet drop on G.8032 controlled ports.
JE-30864
IGMP_Multicast Workaround: Bounce the RING ports, or, on the client node,
save the configuration and restart.
G.8032, Link Agg - The aggregate UNI port on the 5150 platform moves to the
LACP, Link Agg - JE-37665 STG disabled/blocked state when rebooted.
Manual Workaround: Disable and then enable the LAG port.
Traffic is lost when a forced switch is invoked while the ring
WTR is active. The forced switch should override the WTR
and not cause a service disruption. While the virtual ring is in
a recovering state, then a forced switch is invoked against the
G.8032 JE-41881 associated Logical Ring traffic is lost. Clear the force switch
against the Logical ring, then traffic will recover after the WTR
expires.
Workaround: Manually flush the MAC table for all the nodes
in the affected ring.
On the 3930 Extended Timing platform with two active PTP
input references within a frequency protection group, 1588v2
IEEE 1588v2 JE-35814 can become stuck in a holdover state after an L2 bridging
loop occurs within the topology.
Workaround: Disable SyncE and re-enable to clear.
Syslog events and SNMP traps are not properly generated for
IGMP_Multicast JE-14774
multicast join and leave events.
Multicast VLAN translation is not being reported correctly in
frame structure on some platforms. As a result, IGMP
IGMP_Multicast JE-37792
services and IGMP forking are not supported on translated
VLAN's.
IP ACL, IPv6 Mgmt Adding an entry to an IP-ACL by host name is not supported.
JE-26680
Plane Workaround: Add entries by IP address.
ISIS adjacency does not form when the IP Interface MTU
exceeds 1642 bytes and Hello Padding is on.
Workaround: Set the IP interface MTU at or below 1642
IP-ISIS JE-28235 bytes or disable Hello Padding. If the MTU is set already then
you must detach the interface from ISIS, delete the interface,
re-create the interface with the new MTU and then re-attach it
to ISIS.
IPv6 Mgmt Plane,
JE-24520 IPv6 IP interfaces do not respond to ping6.
Mgmt Interfaces
When configuring an IPv6 SNMP trap target, the CLI rejects
IPv6 Mgmt Plane,
JE-26669 host names.
SNMPv3
Workaround: Use the IPv6 address.

Customer Network
Affects Product
Features
ID ID
When using a 1+1 LACP based aggregation, to achieve sub-
Link Agg - LACP JE-19298
50ms reversion, use a reversion hold time of 0.
The aggregation show aggregation <LagPortName> info
Link Agg - LACP JE-18070 command lists the aggregation by its port group ID rather
than the link aggregation port name.
When copper ports are used in link aggregations, the failover
and reversions times are significantly slower.
Before uninstalling the Advanced-Ethernet license, remove all
Link Agg - LACP JE-13847 ports from any link aggregation groups, and then delete the
link aggregation groups.
A link aggregation group with a port in a passive state
establishes aggregation using actor port 0.
A link aggregation group with ports in a passive state
establishes aggregation with two different systems.
A link aggregation group links up with ports operating in half
Link Agg - LACP JE-13342 duplex mode, but should only do so when all ports are in full
duplex mode.
When adding ports to an aggregation, ensure that the port
settings match the other ports in the aggregation. The system
Link Agg - LACP JE-12504 does not prevent adding ports with different settings to the
same aggregation, but if the settings are different, QoS
features may not work properly.
When adding ports to a link aggregation group, do not add 1
Link Agg - LACP JE-13003 Gig and 10 Gig ports to the same group. The system will not
prevent it, but the link aggregation will not work properly.
3930, 5142, 5160, 5142, 3931, 3932 platforms allow adding
Link Agg - LACP,
JE-35936 1Gig and 10Gig ports to the same link aggregation group, but
Link Agg - Manual
3960 and 5150 platforms do not.
This issue here is that reducing the CPU rate limit to 0 for the
LAG ports and resetting it back can causes the LAG ports to
Link Agg - LACP JE-37367 not go into distribution sometimes. The workaround in this
scenario is to remove the ports from the LAG and add them
back.
The CLI allows adding a physical member port of a link
aggregation group to a VLAN, which prevents traffic flow for
Link Agg - Manual JE-22245 that VLAN.
Workaround: Before adding a port to a VLAN, ensure that it
is not a member or a link aggregation group.

Customer Network
Affects Product
Features
ID ID
IP-Interface ping does not work after the 10G manual
aggregation port is disabled and re-enabled when in MSTP
Link Agg - Manual JE-34443 mode. Note that this applies even if MSTP is disabled.
Workaround: Disable 10G aggregation ports on both nodes
and then re-enable the 10G aggregation ports.
Log packet filters do not decode packets regardless of the
Logging JE-7392
configuration setting.
System software does not pop the Customer VLAN tag at UNI
egress, so does not comply with the following MEF 9 test
cases:
MEF JE-16776
* TC 8: Service Frame Transparency Tag Exception 2
* TC 19: CE-VLAN ID for Untagged and Priority Tagged
Service Frames (with the exception of the untagged stream)
The system does not limit the number of simultaneous Telnet
or SSH connections displaying a login prompt. The number of
available login prompt sessions should not exceed the
maximum number of available (unused) Telnet or SSH
Mgmt Interfaces JE-17830
sessions. The maximum number of supported available
sessions is 12; the number of login prompt sessions is the
difference between 12 and the total number of currently active
Telnet sessions.
The Oper State on the remote interface is not consistent with
the Oper State of the virtual switch. This is only an issue
Mgmt Interfaces JE-29585
when the remote interface is associated to a Management
VS and not a VLAN.
Mgmt Interfaces,
Port - Executing the 'port set port speed' command results in the
JE-30247
Mgmt/Statistics, port being unresponsive for about 30 seconds.
Transceivers
OID wwpLeosSwXgradeOptype is not supported in release
C140416-
MIBs JE-41691 6.x.
Workaround: Limited functionality exists in alternative OID 092
wwpLeosSwXgradeOp.
A UNI port with an attachment circuit in used by a VPLS or
MPLS - General JE-24731 VPWS virtual switch cannot be attached to a default Ethernet
virtual switch for a Q-in-Q EVPL.
Configure physical port settings before associating the port
MPLS - General JE-22137
with an MPLS attachment circuit and virtual switch.
MPLS - General, 3916/3930 CCMs do not have Ethernet-tagged PW's service
JE-32065
MPLS - OAM delimiter VID and TPID.

SAOS 6.12.0 009-3240-013 Standard Revision
Customer Network
Affects Product
Features
ID ID
The IS-IS system ID is derived from the loopback IP address.
If the system loopback IP address is changed, the IS-IS
system ID will continue to use the old system ID.
MPLS - ISIS JE-22132
Workaround: Ensure the system loopback IP address is
correct, so that it does not need to be changed. Or disable
and then enable IS-IS to use the new system ID.
The "isis interface detach" and "isis interface attach"
MPLS - ISIS JE-22119 commands are not supported. Attachment and detachment of
IP interfaces to the IS-IS instances occurs automatically.
IS-IS 3-way handshake and DIS election does not strictly
conform to the protocol standard. Instead of waiting 2 twice
the hello timer, switches declare themselves as DIS as soon
as the 3-way handshake is performed.
Attempting to attach an IP interface to an ISIS instance that is
disabled generates an error. If the ISIS instance is disabled
and the system is rebooted, configuration load errors are
generated as a result, and the interfaces are not attached.
Workaround: Do not disable an ISIS instance and then
attach an interface to the disabled ISIS instance.
Disabling and then re-enabling an ISIS instance clears the
ISIS instance statistics.
Workaround: Do not disable/enable the ISIS instance if
statistics are required.
Untagged data is not handled properly by EVC ping of an IP
interface when both EVC ping and SVLAN IP interfaces exist
on a EVC. Untagged ECHO response should be received
MPLS - L3
JE-35212 when pinged. Instead, untagged ARP Requests are being
Interface Mgmt
sent without being stamped by the configured untagged-data-
vid, which results in ARP not being resolved and ECHO
responses not being sent.
MPLS - L3 Creation of an IP interface generates 3 traps each with
JE-21935
Interface Mgmt incorrect IP address and subnet.
The LDP session history statistics "Unknown message type"
MPLS - LDP JE-26402 count does not increase when it receives the "unknown LDP
message".
If PHP is enabled on the tail-end LER, and a TE tunnel
traceroute is performed from the head-end LER, the
MPLS - OAM JE-35811
traceroute times out at the last LSR hop.
Workaround: Do not use PHP.
Setting OSPF instance "RFC 1583 compatible" parameter to
MPLS - OSPF JE-22112
"on" does not remove duplicate routes.

Customer Network
Affects Product
Features
ID ID
Open Shortest Path First (OSPF) hello does not have the
MPLS - OSPF JE-21797
opaque bit set to signal traffic engineering.
The OSPF area statistic "Reachable ABR Count" is not
MPLS - OSPF JE-25226 correct. One additional ABR is added in some circumstance
even when there are no reachable ABRs.
The 3960 does not support OSPF adjacencies for 256 IP
interfaces. OSPF adjacencies stay in various states of "Init,
MPLS - OSPF JE-35614 Loading, ExStart" and the dead timers appear to be expiring
and then try again.
Workaround: Keep the number of adjacencies to 64.
MPLS does not support Class of Service (CoS) marking in
this release, so tagged data traffic with non-zero priority is
MPLS - QoS JE-22134
changed to priority 0 upon reaching the destination
attachment circuit.
The "rsvp-te show statistics" command is not accurate for the
"RSVP hello Tx/Rx" count (includes transmitted and received
MPLS - RSVP-TE JE-24220
RSVP hello ACK messages) and "RSVP Hello ACK Tx/Rx"
(the count is always 0).
MPLS - Tunnel The "mpls tunnel show static-egress" command does not
JE-22067
Mgmt display the source IP address for the specified static tunnel.
MPLS - Tunnel MPLS Fast Re-Route (FRR) signaling supports one-to-one
JE-21036
Mgmt only.
When the device loopback interface is not attached to the
MPLS - Tunnel
JE-26407 OSPF instance, the RSVP-TE tunnel to the adjacent device
Mgmt
remains up.
Configure the acceptable frame type for physical port settings
MPLS - VC JE-21744 before associating the port with an MPLS attachment circuit
and virtual switch.
The "mpls l2 protect switchover dynamic-vc <vc-name>"
command always switches the to the current inactive virtual
MPLS - VC JE-23583
circuit, regardless of whether the primary or protection virtual
circuit name is selected.
Multiple Spanning Tree Protocol (MSTP) convergence time
MSTP JE-21569
exceeds 50 ms for a 4 switch ring.
After enabling MSTP, the shell session locks up for
approximately 15 seconds. The system generates a warning
MSTP JE-12423 message explaining the delay, however, not until after the
command is complete and the shell session is already
unlocked.

Customer Network
Affects Product
Features
ID ID
It is not recommended to repeatedly paste large buffers of
commands into a CLI session as it may cause session to
OAM-AIS/LDI JE-34546
lockup.
Workaround: If the session locks up, use Ctrl-C to unlock.
AIS fault is cleared on an LER when multiple faults occur on a
OAM-AIS/LDI JE-35871
static co-routed tunnel.
The CLI saves an internal identifier called logical-id to the
configuration file. If a configuration augment file contains
commands with the logical-id parameter, the "configuration
OAM-BFD JE-34852 augment" command will not work when loaded from the TFTP
server.
Workaround: Remove any "logical-id" parameters from
commands in a configuration augment file.
For a newly created associated/corouted tunnel, if the next-
hop-ip is down or does not exist, the "bfd session show"
OAM-BFD JE-34221
command returns an empty tunnel name in the "Bidir" field
and 0 values for other tunnel fields.
BFD statistics collection session hangs when a session is
OAM-BFD JE-35671 deleted while in the midst of a statistics collection operation.
Workaround: End the current statistics collection session.
When CPU rate limiting is enabled for LSP BFD frames, BFD
sessions will flap when the transmit rate increases, however,
OAM-BFD JE-27413
the "flow cpu-rate-limit show" port level statistics do not show
any dropped frames.
The BFD Sessions Oper Up count statistic is incorrect if a
reboot of the system occurs while BFD sessions are up. It
OAM-BFD JE-35850
shows more sessions up than are administratively enabled.
Workaround: Reboot with sessions down to fix the count.
Running an MPLS ping immediately after reboot may report
packet timeout.
OAM-MPLS Echo JE-35636 Workaround: Wait for the system to stabilize (virtual circuits
and tunnels to be operationally up) and then issue a MPLS
ping.
On 5142 and 5160 platforms, PBB-TE decapsulated data
PBB-TE JE-35851 frames get the PCP from the B-tag instead of the I-tag when
the decap CoS policy is set to vc-inherit.
Non-native PBB-TE virtual switch encap CoS policy of fixed is
PBB-TE JE-35273
not applied.

Customer Network
Affects Product
Features
ID ID
When a Provider Backbone Bridge Traffic Engineering (PBB-
TE) encapsulation tunnel CoS policy is set to inherit from the
PBB-TE JE-23423
associated virtual switch (vs-inherit), the Priority Code Point
(PCP) value is always set to 0.
After modifying the tunnel for a virtual circuit, the BVID in the
PBB-TE JE-23387 PBB-TE header is the BVID of the tunnel previously
associated with the virtual circuit.
PBB-TE, Port - 3940 and 5140 PBB-TE tunnel reversion exceeds 500 ms
JE-23713
Mgmt/Statistics during back-to-back testing over 1 Gbps SFP ports.
PBB-TE, Port - 3960 and 5150 PBB-TE tunnel reversion exceeds 1 second
JE-23700
Mgmt/Statistics during back-to-back testing over 10Gbps ports.
Without CFM, 3940 PBB-TE tunnel failover times do not meet
the 50 ms threshold as LoS detection is used to perform the
failover. For a sub-50ms failover to occur, CFM (preferably
PBB-TE JE-19222
accelerated) should be used with a CCM interval of 3.33 or
10msec if using accelerated and 10msec if not using
accelerated.
Native PBT reversion times are high when the reversion hold
PBB-TE JE-31589
time is greater than 30 seconds.
Non-native PBB-TE tunnel and virtual circuit statistics are not
PBB-TE JE-34407 cleared properly after delete.
Workaround: Clear statistics after configuring virtual circuit.
Only 127 PBB-TE remote bridges can be created instead of
PBB-TE JE-35763
128 because MPLS uses up 1 hardware entry at initialization.
5142 and 5160 platforms remark the customer frame with the
PBB-TE JE-35988 wrong priority when the virtual switch decap CoS policy is set
to fixed.
With native PBB-TE the "flow mac show mac <mac>"
PBB-TE JE-35274
command does not show the learned port or VLAN.
Need to note that the defect is reproduced after the decap
tunnel is created on the 3916:
>tunnel decap create static-pbt from_OTT b-vid 300 src-
PBB-TE JE-34924 bridge-name OTT port 3
Essentially, one must have PBT fully configured on the 3930
before provisioning the 3916. During the creation of the decap
PBT tunnel the CPU gets flooded with ingress packets.
PBB-TE JE-36021 PBB-TE virtual circuit statistics always show as zero.

Customer Network
Affects Product
Features
ID ID
Deleting a tunnel pair PBB-TE virtual circuit path sharing NNI
ports with another tunnel pair causes service disruption to the
PBB-TE JE-19287
untouched virtual circuit and its traffic flow for about 238-250
ms.
With non-native PBB-TE, QinQ customer frames with the
PBB-TE JE-35275 outer tag ethertype of 0x9100 are overwritten with 0x8100.
Workaround: Use the decap CoS policy of leave.
PBB-TE virtual circuit statistics only account for traffic
C140428-
PBB-TE JE-41778 traversing one of the 2 member ports of the associated link
084
aggregation group.
PM will roll the 24HrCurrent Bin into the 24HrHistory Bin at
Performance
JE-34043 UTC Midnight, regardless of the value of the global timestamp
Monitoring
setting.
When an uncertified transceiver is removed from a
Port - combination port, the "port show port <PortName>" command
JE-23358
Mgmt/Statistics continues to display the type as "Uncertified," but it should
revert to "10/100/G."
A port set to loopback while in SFP connector mode will
continue traffic flow on the port set in loopback (both ingress
Port -
JE-15451 and egress traffic).
Mgmt/Statistics
Workaround: Set the port connector mode to RJ45 to stop
the traffic flow.
The ifSpeed and ifHighSpeed MIB objects do not report
nominal values as defined by RFC1213. Instead, when a port
Port - C100309-
JE-15731 is operationally down, the polled ifSpeed OID returns a "0"
Mgmt/Statistics 010
value. The ifHighSpeed OID always returns "0" no matter the
port state or negotiated speed.
On the 3940 and 5150, if ports are disabled, re-enabled, and
then displayed immediately, the port link state duration
Port -
JE-16610 displays erroneous values.
Mgmt/Statistics
Workaround: Wait a few seconds before displaying the port
state.
Port statistic throughput values may be off by 10% with short
Port - polling durations.
JE-17509
Mgmt/Statistics Workaround: Wait a minute between commands for more
accurate values.
The system software does not properly track statistics for
Port -
JE-13152 frames marked with illegal or unknown sub-types received
Mgmt/Statistics
over an aggregation.

Customer Network
Affects Product
Features
ID ID
The system software does not properly track statistics for
Port -
JE-13151 frames marked with illegal or unknown sub-types received
Mgmt/Statistics
over an aggregation.
When physical loopback is turned on for a port, the port
Port -
JE-12373 operational status does not always accurately reflect the
Mgmt/Statistics
actual status.
Do not configure both service access control and physical
Port - loopback on the same port. The settings of the service access
JE-11873
Mgmt/Statistics control for forward unlearned action and learning are applied,
but should not be until the physical loopback is disabled.
When the SFP is unplugged from ports 9-12 on the 3911
Port - platform, the port type is displayed as unknown (?? ??). Ports
JE-12116
Mgmt/Statistics 9 and 10 should display "10/100/G," and ports 11 and 12
should display "Gig."
After setting the port speed on an auto-negotiated port, the
egress port shaper is set to the port speed instead of the
Port -
JE-41459 auto-negotiated speed.
Mgmt/Statistics
Workaround: Change the port speed setting back to auto-
negotiated.
Port - Link Down and Link Up traps are generated when a member R13-
JE-37226
Mgmt/Statistics physical port is removed from a link aggregation group. NE_0016
Link aggregation group ports whose physical port members
Port State
JE-19184 are already in a port state mirroring group are not prevented
Mirroring
from being added to another group.
Attempting to run TWAMP tests concurrently with benchmark
(RFC 2544) tests results in inaccurate TWAMP
RFC 2544, measurements or may prevent the TWAMP test from running
JE-24409
TWAMP at all.
Workaround: Before running TWAMP tests, disable
benchmark testing.
When an L3 interface is created and enabled for OSPF on a
VLAN associated with either the UNI or NNI involved in a
benchmark test, the test gives a result of zero for the 64Byte
RFC 2544 JE-25906 frame size. The latency test also shows very high latency for
the 64Byte frame size.
Workaround: Disable OSPF on the L3 interface before
running benchmark test.

Customer Network
Affects Product
Features
ID ID
If benchmark generator or UNI reflector is enabled, any
configuration changes to the port used for benchmark tests
RFC 2544 JE-18027 may lead to unexpected behavior. It is recommended to
disable benchmark test processing, if any port configuration
changes are required.
Real-time RFC 2544 statistics run during the test do not
RFC 2544 JE-17476 match the UNI reflector port statistics (Tx and Rx). Once
traffic is stopped, the statistics do match up correctly.
The RSTP hello time changes whenever the root bridge hello
RSTP JE-14585
time changes.
The 802.1D-2004 RSTP standard requires BPDUs to be
processed within 1.2 seconds. This system software can take
RSTP JE-16248
up to 4 seconds to process certain BPDUs, such as STP and
Unknown.
If a port is set to SFP mode, and physically looped back, the
RSTP JE-14102 RSTP state should display as "Blocked." However, it displays
as "Forwarding."
If you have configured service access control (SAC) and then
remove the Advanced Ethernet (AE) license, the system
software overrides the SAC settings in the hardware with the
global setting. If you then reinstall, the AE license, the SAC
Security JE-11894
entry will still be there, but may not correspond to what is
actually in the hardware.
Workaround: After installing or removing the AE license,
restart the system software.
SNMPv3 JE-25576 The SNMP tcpConnTable object is not populated.
The "snmp create target" command will accept addresses
from the reserved range (0.0.0.0/8). The reserved range is
used for other purposes as specified in the IPv4 standards.
SNMPv3 JE-25557
Using this range as part of this command is not
recommended but also does not produce any adverse effects.
Workaround: Use an IP address from a valid range.
The wwpLeosTrafficProfileStdTotalStatsTable is not
supported in 6.x, even though the object is defined as current
C121104-
SNMPv3 JE-30090 in the WWP-LEOS-TRAFFIC-PROFILE-MIB.my file.
014
Workaround: Use the wwpLeosTrafficProfileStdStatsTable
instead.
The order of the variable bindings in the MIB definition for the
wwpLeosEthLinkDown notification does not match the order
C131009-
SNMPv3 JE-37126 in which the devices send them. The
170
wwpLeosEtherPortName is actually sent before the
wwpLeosEtherPortType.

Customer Network
Affects Product
Features
ID ID
Software Mgmt - Software upgrade may fail with a core dump if 14 slices of
JE-25721
Upgrade traffic profiling resources are allocated.
On the 3960 and 5150 platforms, if you run a software
installation, run a software validation, and then reboot, the
Software Mgmt -
JE-15617 installation process will fail upon reboot.
Upgrade
Workaround: Run the software installation, re-boot, and then
run the software validation.
Software Mgmt - The system does not provide MIB support for displaying the
JE-15605
Upgrade release status of the software.
The 3930 Sync + External Timing port keeps sending and
SyncE JE-31750
receiving when oper is disabled.
Recovery of SyncE timing on RJ-45 connectors of 3930-930
SyncE JE-29478 ports 1-4 is not supported in 6.10.1. These ports may be used
as SyncE outputs, but not SyncE inputs.
On the 5150 with DHCP enabled and 10 Gig ports with link
up, upon re-boot Syslog messages use the local static IP
Syslog JE-16046 address for interface messages until the device is completely
up. Also, link up messages are not logged for the 10 Gig
ports.
If a device is stuck in a software upgrade state and will not
reboot or upgrade in that state, the chassis force-reset
command does not reload the device. The device exits to the
System Mgmt JE-37498
SAOS login prompt.
Workaround: Use the diag crash server command to reset
the device.
The 3940 stops responding when the console port is
TROUT C110830-
System Mgmt JE-23942 connected to a terminal server port that is in "login two-way"
497959 152
mode instead of "login device" mode.
A system re-boot will remove an IP interface created on
VLAN 127.
Running the "sniff start" command, which is available for
System Mgmt JE-19779 users with diagnostics access level, causes the CPU to stop
responding and requires a reboot to recover.
Cancelling a "system state-dump" with Ctrl+C leaves 2
temporary files in the CLI session. Multiple iterations can fill
System Mgmt JE-19304 up the \tmp directory.
Workaround: Exit the CLI session to remove the temporary
files.

Customer Network
Affects Product
Features
ID ID
The system show load command displays the load average
as a percentage derived from internal process and load
average values. The actual values should be displayed as the
average number of processes in the run queue calculated
over the time periods 1 minute, 5 minutes and 15 minutes.
Workaround: Use the cat /proc/loadavg command to display
average number of processes in the run queue calculated
over the time periods. For example:
> cat /proc/loadavg
1.06 1.08 0.91 2/131 4247
In this example, the average number of processes in the run

queue are:
* 1.06 for 1 minute
* 1.08 for 5 minutes
* 0.91 for 15 minutes
On the 3932, an E1 port cannot be put into local or remote
loopback if there is a CESoP service provisioned on it. Also, if
TDM PWE JE-35876
there is a local or remote loopback applied to an E1 port, a
CESoP service can not be created on that port.
If you set a Small Form-factor Pluggable (SFP) port to the
default (port set port <PortName> mode default), the port type
is set to 10/100/G. If an uncertified transceiver is installed, the
Transceivers JE-16118 port continues to display the type as 10/100/g, instead of
"uncertified."
Workaround: Set an SFP port explicitly to the SFP mode
rather than "default" (port set port <PortName> mode sfp).
The AXCEN Photonics AXFE-R1S4-05H1 Rev1 SFP is
Transceivers JE-19419 supported for passing traffic only when the speed is set to
100 MB with auto-negotiation turned off.
Note that in releases prior to 6.10.1, the system uptime will
roll over after 497 days. There does not appear to be any
Unlisted Feature JE-29092 noticable impact of this rollover. This is resolved in 6.10.1 in
terms of the CLI display of uptime, but will still be an issue in
terms of SNMP queries of the system uptime.
Duplicate notifications are sent for
wwpLeosPortXcvrRxPowerNormalNotification and
Unlisted Feature JE-26876 wwpLeosPortXcvrRxPowerLowNotification, which also
appears as
wwpLeosPortXcvrRxPowerLowWarningNotification.

Customer Network
Affects Product
Features
ID ID
Adding a link aggregation group port into a VLLI group where
mode is equal to the destination is not valid configuration.
VLLI JE-27786
However, the CLI does not prevent it. The CLI should
generate and error message and discard the configuration.

39XX/51XX Service Delivery and Aggregation Switches
Release Notes
Copyright 2013-2014 Ciena Corporation. All rights reserved.
Release 6.12
Publication: 009-3240-013
Document status: Standard
Document issue: Revision A
Document release date: May 2014
CONTACT CIENA
For additional information, office locations, and phone numbers, please visit the Ciena
web site at www.ciena.com

009-3240-013 (39XX 51XX SAOS 6.12 Customer Release Notes) RevA

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

009-3240-013 (39XX 51XX SAOS 6.12 Customer Release Notes) RevA

Transféré par

Droits d'auteur :

Formats disponibles

39XX/51XX Service Delivery and Aggregation Switches

009-3240-013 - Standard Revision A

Corporate Headquarters 410-694-5700 or 800-921-1144 www.ciena.com

39XX/51XX Service Delivery and Aggregation Switches Release Notes

39XX/51XX Service Delivery and Aggregation Switches Release Notes

39XX/51XX Service Delivery and Aggregation Switches Release Notes

Release for SAOS 6.12.0.232.

39XX/51XX Service Delivery and Aggregation Switches Release Notes

39XX/51XX Service Delivery and Aggregation Switches Release Notes

About this document

39XX/51XX SAOS 6.12 Product Fundamentals

39XX/51XX SAOS 6.12 Software Management and Licensing

39XX/51XX SAOS 6.12 Administration and Security)

39XX/51XX SAOS 6.12 Configuration

39XX/51XX SAOS 6.12 Fault and Performance

39XX/51XX SAOS 6.12 Command Reference Manual

39XX/51XX SAOS 6.12 MIB Reference Manual (009-3220-011)

3916 Hardware Installation and Startup Manual (009-3226-001)

3930 Hardware Installation and Startup Manual (009-3223-001)

3931 Hardware Installation and Startup Manual (009-3225-001)

3931 Enclosure Installation and Startup Manual (009-3225-019)

3932 Hardware Installation and Startup Manual (009-3227-001)

3940 Hardware Installation and Startup Manual (009-3230-001)

3960 Hardware Installation and Startup Manual (009-3231-001)

5140 Hardware Installation and Startup Manual (009-3232-001)

39XX/51XX Service Delivery and Aggregation Switches Release Notes

5142 Hardware Installation and Startup Manual (009-3206-001)

5150 Hardware Installation and Startup Manual (009-3222-001)

5160 Hardware Installation and Startup Manual (009-3207-001)

Packet Networking Glossary (009-3299-026)

Packet Networking transceivers Reference (009-2011-602)

Ciena Standard Cleaning and Equipment Safety Practices (009-2003-121)

Ciena is a trademark of Ciena Corporation.

Juniper Networks, the Juniper Networks logo, JUNOS, Steel-Belted Radius,

libTACACS developed by Roman Volkov via SourceForge.net.

Please see copyright in ~leos/common/application/tacPlusMgr/tacClient/COPYRIGHT.

39XX/51XX Service Delivery and Aggregation Switches Release Notes

New in this release

39XX/51XX Service Delivery and Aggregation Switches Release Notes

Issues fixed in this release

39XX/51XX Service Delivery and Aggregation Switches Release Notes

39XX/51XX Service Delivery and Aggregation Switches Release Notes

39XX/51XX Service Delivery and Aggregation Switches Release Notes

39XX/51XX Service Delivery and Aggregation Switches Release Notes

39XX/51XX Service Delivery and Aggregation Switches Release Notes

39XX/51XX Service Delivery and Aggregation Switches Release Notes

39XX/51XX Service Delivery and Aggregation Switches Release Notes

39XX/51XX Service Delivery and Aggregation Switches Release Notes

39XX/51XX Service Delivery and Aggregation Switches Release Notes

Issues found in this release

39XX/51XX Service Delivery and Aggregation Switches Release Notes

39XX/51XX Service Delivery and Aggregation Switches Release Notes

39XX/51XX Service Delivery and Aggregation Switches Release Notes

39XX/51XX Service Delivery and Aggregation Switches Release Notes

39XX/51XX Service Delivery and Aggregation Switches Release Notes

39XX/51XX Service Delivery and Aggregation Switches Release Notes

39XX/51XX Service Delivery and Aggregation Switches Release Notes

Issues fixed prior to this release

39XX/51XX Service Delivery and Aggregation Switches Release Notes

Issues found prior to this release

39XX/51XX Service Delivery and Aggregation Switches Release Notes

39XX/51XX Service Delivery and Aggregation Switches Release Notes

39XX/51XX Service Delivery and Aggregation Switches Release Notes