Specifications

•
When Cisco running in an old version of PVST+, it does not carry VLAN ID in the end of
BPDU. So Juniper Networks equipment fails to responds to Topology Change
Notification ACK packet when it interoperates with Cisco equipment. After the fix,
Juniper equipment will read the VLAN ID information from Ethernet header. PR984563
•
Layer 2 Control Protocol process (l2cpd) is used to enable features such as Layer 2
protocol tunneling or nonstop bridging. If a router receives a Link Layer Discovery
Protocol (LLDP) packets with multiple management address TLV, memory leak might
occur which resulting in l2cpd process crash. PR986716
•
jnxLacpTimeOut trap may show negative values and incorrect values for jnxLacpifIndex
and jnxLacpAggregateifIndex. PR994725
•
In race condition, when FPC gets rebooted or reset, link(s) from this FPC which are
part of aggregate-ethernet bundle would remain in LACP "Detached" state indefinitely.
user@node> show lacp interfaces ae102 Aggregated interface: ae102 LACP state: Role
Exp Def Dist Col Syn Aggr Timeout Activity xe-2/0/0 Actor No Yes No No No Yes Fast
Active xe-2/0/0 Partner No Yes No No No Yes Fast Passive xe-2/0/1 Actor No No Yes
Yes Yes Yes Fast Active xe-2/0/1 Partner No No Yes Yes Yes Yes Fast Active LACP
protocol: Receive State Transmit State Mux State xe-2/0/0 Defaulted Fast periodic
Detached xe-2/0/1 Current Fast periodic Collecting distributing user@node> show
interfaces xe-2/0/0 terse Interface Admin Link Proto Local Remote xe-2/0/0 up up
xe-2/0/0.0 up up aenet --> ae102.0 xe-2/0/0.32767 up up aenet --> ae102.32767 This
issue would be seen when associated aggregate-ethernet bundle is configured for
vlan-tagging. To clear this condition, the affected interface should be deactivated and
activated using cli commands. ============ [edit] user@node# deactivate
interfaces xe-2/0/0 [edit] user@node# commit [edit] user@node# activate interfaces
xe-2/0/0 [edit] user@node# commit ============ PR998246
MPLS
•
When the install prefix (specified by the "install" knob) and destination prefix (specified
by the "to" address of the LSP) are same for a static LSP, the routing protocol process
(rpd) might crash while deleting the LSP. PR958005
•
During SNMP walk on table MPLS cross-connect table (mplsXCTable) in case of flood
nexthop, the rpd might crash. PR964600
•
In the large scaled MPLS setup with NSR enabled. When restart routing protocol
daemon (rpd) on standby Routing Engine, or reload standby Routing Engine, or reload
router, some filtered output label bindings might be missed on the backup Routing
Engine, which leads to Label Distribution Protocol (LDP) database between the master
and backup Routing Engines are inconsistent. PR970816
•
In a scaled MPLS environment, whenever fast reroute (FRR) or Link Protection (LP)
or Node Protection (NP) is configured, the switchover from the primary LSP to the
secondary LSP might cause traffic loss for few seconds. PR973070
•
In the MPLS environment, when execute the command "show snmp mib walk
mplsXCTable" to walk the MPLS cross connect table, the routing protocol daemon
(rpd) CPU utilization might reach over 90%, and the rpd process doesn't respond to
any CLI show commands. PR978381
Copyright © 2015, Juniper Networks, Inc.118
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series