EasyManua.ls Logo

Juniper JUNOS 10.1 - RELEASE NOTES REV 4

Juniper JUNOS 10.1 - RELEASE NOTES REV 4
205 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
The SFC management interface em0 is often displayed as fxp0 in several warning
messages. [PR/454074]
The VPN label does not get pushed on the label stack for Routing
Enginegenerated traffic with l3vpn-composite-next-hop activated. As a
workaround, configure per-packet load balancing to push the VPN/tunnel labels
correctly. [PR/472707]
On restarting with a large-scale configuration (16,000 logical interfaces per MPC),
the MPC-3D-16XGE-SFPP card may take up to 15 minutes to come up.
[PR/478548]
Swapping out eight FPC cards and replacing them with a different FPC type
causes the kernel to crash when the last FPC is powered on. [PR/502075]
The tty sessions to a router can cause a null pointer de-reference. [PR/502816]
The TTL for a GRE-encapsulated IPv6 packet malfunctions as the TTL on the wire
is one less than the CLI-configured tunnel TTL. [PR/506454]
In a setup with two VPN routing and forwarding tables (VRFs) of a provider edge
connected to different customer edges and auto-export configured, when a ping
is executed from a customer edge to a provider edge interface in the other VRF
, the Internet Control Message Protocol reply returns the source interface IP of
the provider edge that is connected directly instead of the interface IP of the
other VRF provider edge. [PR/510834]
Under certain conditions, traffic flow through an RLSQ bundle can be dropped
after it is removed and added back to a VPN routing and forwarding table (VRF).
[PR/518170]
Asp_ifl_update messages may be seen on routers running Junos OS Release 10.0
and above. Ignore these messages as they do not impact functionality.
[PR/532648]
Routing Policy and Firewall Filters
If a routing protocol running an MSDP receives an SA that is filtered via the MSDP
import policy, it will still create a forwarding entry if it subsequently receives a
(*,G) join for that group. [PR/63053]
The following features are not supported in a 12-16x10G DPC:
Known unicast and unknown unicast types in the input match condition
'Traffic-type' in a family bridge/VPLS
The following match conditions do not work:
learn-vlan-1p-priority
learn-vlan-1p-priority-except
learn-vlan-id
learn-vlan-id-except
user-vlan-1p-priority
user-vlan-1p-priority-except
60 Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
JUNOS 10.1 Software Release Notes

Table of Contents

Related product manuals