Specifications

•
The Priority code point (PCP) and Drop eligible indicator (DEI) bit in 802.1Q header are
preserved while packet gets routed within the same Packet Forwarding Engine. The
expected behavior is resetting the PCP and DEI bit when the packet is routed. PR1036756
•
Observation domain ID in exported flow records is wrong in Hyperion and snorkel line
card. PR1066319
Routing Protocols
•
It is necessary that the MSDP peer local-address matches the PIM RP address on
routers that are RP. MSDP RPF check might fail in rare cases when both these addresses
are not equal. PR35806
•
When you configure damping globally and use the import policy to prevent damping
for specific routes, and a peer sends a new route that has the local interface address
as the next hop, the route is added to the routing table with default damping
parameters, even though the import policy has a nondefault setting. As a result, damping
settings do not change appropriately when the route attributes change. PR51975
•
Continuous soft core-dump may be observed due to bgp-path-selection code. RPD
forks a child and the child asserts to produce a core-dump. The problem is with
route-ordering. And it is auto-corrected after collecting this soft-assert-coredump,
without any impact to traffic/service. PR815146
•
When a Bidirectional Protocol Independent Multicast (PIM) rendezvous point (RP) is
configured on a physical interface, such as fe-0/0/0 not the loopback interface, after
restarting the routing, the Reverse Path Forwarding (RPF) interface might not be added
to the accepting interface list for the affected groups, then some traffic can not be
forwarded normally. PR842623
•
If Node-link protection is required in case of multiple ECMP primary paths, Node-link
protection command: ("set protocols ospf area <area_Id> interface <interface_name>
node-link-protection") needs to be configured on all the outgoing-interfaces of
PLR(Point of Local Repair)node that fall on the ECMP path to the primary. For eg.in
the following diagram: PLR: RTA Destination: RTC Primary paths:
RTA-->lt-1/2/10.102-->RTB-->lt-1/2/10.203-->RTC;
RTA-->lt-1/2/10.122-->RTB-->lt-1/2/10.203-->RTC; Outgoing interfaces on PLR:
lt-1/2/10.102 lt-1/2/10.122 Node-link protection needs to be enabled on both lt-1/2/10.102
and lt-1/2/10.122 if backup route avoiding RTB needs to be computed. (cost 1)
|-----|-------------lt-1/2/10.102(81.1.2.2 )----------------|-----| | | (cost 1) | | | RTA
|-------------lt-1/2/10.122(82.11.22.2)----------------| RTB | |_____| |_____| | | | |lt-1/2/10.203
| 81.3.3.3 | | (cost 1000) |-----| | |----lt-1/2/10.103(81.1.3.1) -----| RTC |--------------------|
|-----| The behavior is corrected from release 14.1 and Node-link protection can be
configured on any one of the interfaces on the ECMP path. PR924290
•
When a Junos OS router with multicast enabled receives IGMP packets with protocol
DVMRP (IGMP_PROTO_DVMRP) to the IGMP port is 0x5 (DVMRP_ASK_NEIGHBORS2),
IGMP builds a neighbor list and responds back to the source IP address of the sender.
This source IP address can be a unicast address or a multicast address. There is no
throttling of responses. The requests are answered at the highest rate possible.
Secondary impacts are that the routing protocol daemon (rpd) IGMP utilization goes
77Copyright © 2015, Juniper Networks, Inc.
Known Issues