Mobile Ip; Mpls - Juniper JUNOSE 10.0.3 - RELEASE NOTES 4-30-2010 Release Note

For e series broadband services routers
Table of Contents

Advertisement

Mobile IP

MPLS

Traffic statistics for dynamic subscriber interfaces associated with mobile IP
subscribers are not maintained as the subscribers move between mobile IP
nodes. Consequently the reported interface statistics are only the values
accumulated since the last time a mobile node moved. [Defect ID 174509]
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 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 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 you issue a traceroute or trace mpls command to trace the paths of
router packets over MPLS interfaces on an ES2 10G LM or ES2 10G Uplink LM,
the results include an extra unknown host. [Defect ID 174537]
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,
traceroute 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]
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.
You cannot use an underscore character (_) in an MPLS tunnel name. [Defect
ID 31291]
Release 10.0.3
Known Problems and Limitations
43

Advertisement

Table of Contents
loading

This manual is also suitable for:

Junose 10.0.3

Table of Contents