Table of Contents
Advertisement
JunosE 10.3.2 Release Notes
Mobile IP
MPLS
44
Known Problems and Limitations
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.
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 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.
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]
Work-around: Issue the no mpls command to disable MPLS, then delete the
interface.
You cannot use an underscore character (_) in an MPLS tunnel name. [Defect ID
31291]
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 IGPs.
When the IPv4 explicit null label appears anywhere other than at the bottom of
the label stack, TTL expiration for this label is not handled correctly. As a result,
the traceroute command does not work correctly for LSPs that have the IPv4
explicit null label anywhere other than at the bottom of the label stack. [Defect
ID 76037]
Advertisement
Table of Contents
