JUNOSe 11.1.0 Release Notes
52
Known Problems and Limitations
The E Series router does not log a warning when it receives an MLDv1 query
but is not configured to use MLDv1 on the interface. [Defect ID 46046]
MLPPP
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.
Mobile IP
The
clear ip mobile binding nai @
realm
command does not work. [Defect ID
178652]
Work-around:
Use the following version of the command instead:
clear ip mobile binding nai
user
@
realm
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 [email protected]
Alternatively, you can display the entire Mobile IP binding table by issuing the
show ip mobile binding
command without additional options.
The setup rate for Mobile IP client sessions decreases when you repeatedly
bring a large number of sessions down and back up. [Defect ID 178760]
When mobility bindings are present and you delete the Mobile IP home agent
with the
no virtual router
command, Mobile IP sends a RADIUS Acct-Stop
message with no accounting statistics for the subscribers. [Defect ID 179081]
Work-around
: Issue the
clear ip mobile binding all
command before you
issue the
no virtual router
command. The
clear
command clears all the MIP
subscribers and sends a RADIUS Acct-Stop message with the appropriate
accounting statistics for the subscribers.
MPLS
When MPLS and IS-IS are configured on Ethernet interfaces, you cannot delete
the interface after the IP address is removed. This issue is not a problem on
Ethernet VLAN interfaces. [Defect ID 66813]