the mobile node. If the packet is already encapsulated, and the inner destination address
is the same as the outer destination address, then the system examines the outer source
address. If the outer source address is the same as the tunnel destination address or the
foreign agent care-of-address (CoA), the system silently discards the packet. In all other
cases, the tunnel encapsulation is successful.
For more information about configuring Mobile IP using GRE or DVMRP tunnels, see
“Configuring the Mobile IP Home Agent” on page 303
.
Combining Dynamic and Static IP Tunnels in the Same Chassis
You can configure both dynamic and static IP tunnels in the same chassis.
A tunnel pair consists of two endpoints; one side encapsulates and the other side
decapsulates. You can create a tunnel pair with two statically configured endpoints, two
dynamically created endpoints, or with one static and one dynamic endpoint.
When configuring IP tunnels, you must consider that a tunnel is uniquely defined by its
tunnel source, tunnel destination, transport virtual router, and mode (GRE or DVMRP).
The system does not allow multiple tunnels with the same parameters. For example,
when you configure a static tunnel with the same parameters as an existing dynamic IP
tunnel, the system does not create the dynamic IP tunnel.
Changing and Removing Existing Dynamic IP Tunnels
You can modify the parameters in a destination profile referenced by existing dynamic
IP tunnels. The changes only affect new dynamic IP tunnels that reference the destination
profile.
You can relocate a dynamic IP tunnel for the Mobile IP application.
You cannot relocate a dynamic IP tunnel for the data MDT application because it is
created using a profile. The system deletes dynamic IP tunnels that are relocated.
Connections between a static tunnel endpoint and a dynamic tunnel endpoint can fail
if the dynamic tunnel endpoint is deleted.
The client application removes dynamic IP tunnel interfaces when one of the following
situations occur:
•
The transport virtual router is removed.
•
The tunnel interface relocates and the tunnel had an IP interfaced stacked on it.
•
The tunnel interface indicates that setup is complete when the system is warm started,
but it has no upper IP interface.
Platform Considerations
For information about modules that support IP tunnels on the ERX7xx models, ERX14xx
models, and the ERX310 Broadband Services Router:
•
See
ERX Module Guide, Table 1, Module Combinations
for detailed module specifications.
253
Copyright © 2010, Juniper Networks, Inc.
Chapter 10: Configuring Dynamic IP Tunnels
Summary of Contents for JUNOSE 11.2.X IP SERVICES
Page 6: ...Copyright 2010 Juniper Networks Inc vi...
Page 8: ...Copyright 2010 Juniper Networks Inc viii JunosE 11 2 x IP Services Configuration Guide...
Page 18: ...Copyright 2010 Juniper Networks Inc xviii JunosE 11 2 x IP Services Configuration Guide...
Page 22: ...Copyright 2010 Juniper Networks Inc xxii JunosE 11 2 x IP Services Configuration Guide...
Page 28: ...Copyright 2010 Juniper Networks Inc 2 JunosE 11 2 x IP Services Configuration Guide...
Page 116: ...Copyright 2010 Juniper Networks Inc 90 JunosE 11 2 x IP Services Configuration Guide...
Page 144: ...Copyright 2010 Juniper Networks Inc 118 JunosE 11 2 x IP Services Configuration Guide...
Page 230: ...Copyright 2010 Juniper Networks Inc 204 JunosE 11 2 x IP Services Configuration Guide...
Page 262: ...Copyright 2010 Juniper Networks Inc 236 JunosE 11 2 x IP Services Configuration Guide...
Page 294: ...Copyright 2010 Juniper Networks Inc 268 JunosE 11 2 x IP Services Configuration Guide...
Page 328: ...Copyright 2010 Juniper Networks Inc 302 JunosE 11 2 x IP Services Configuration Guide...
Page 345: ...PART 2 Index Index on page 321 319 Copyright 2010 Juniper Networks Inc...
Page 346: ...Copyright 2010 Juniper Networks Inc 320 JunosE 11 2 x IP Services Configuration Guide...
Page 356: ...Copyright 2010 Juniper Networks Inc 330 JunosE 11 2 x IP Services Configuration Guide...