Table of Contents
Advertisement
JUNOSe 10.2.2 Release Notes
L2TP
MLD
MLPPP
Mobile IP
42
Known Problems and Limitations
If LSPs are announced into IS-IS, then the IS-IS routes cannot be used for
multicast RPF checks, because LSPs are unidirectional. [Defect ID 28526]
Work-around: Configure static RPF routes with native hops when LSPs are
autoroute announced to IS-IS.
After a unified ISSU completes on a router functioning as an L2TP access
concentrator (LAC), traffic outages occur on the L2TP network server
(LNS)-facing interface at the LAC in a configuration with 16,000 or 32,000 L2TP
sessions over 500 tunnels. [Defect ID 180147]
The E Series router MLDv2 proxy does not operate correctly in the presence of
MLDv1 queriers. [Defect ID 46039/46045]
Work-around: If an MLDv1 router is present on the network, configure version
1 with the ipv6 mld-proxy version command on that network interface.
(Version 2 is the default.)
The default value for the MLDv2 proxy unsolicited report interval timer should
be 1 second rather than 10 seconds (the value for v1). [Defect ID 46040]
Failure to meet all of the following conditions for fragmented packets can result
in an incorrect operation during packet classification of the resulting
reassembled packet: [Defect ID 50111]
The initial fragment of a packet must either contain the entire MLPPP
packet or be greater than 128 bytes.
The fragment size of the peer must not be lower than 128 bytes.
The initial fragment of a packet must be larger than subsequent fragments
of that packet.
The @realm variable and the @ keyword alone do not work for the show ip
mobile binding command. [Defect ID 178653]
Work-around: You can use the user@realm syntax instead to display the
binding for a specific user, as in this example:
host1#show ip mobile binding nai xyz@example.com
Alternatively, you can display the entire Mobile IP binding table by issuing the
show ip mobile binding command without additional options.
Advertisement
Table of Contents
