Table of Contents
Advertisement
JunosE 11.2.x IP Services Configuration Guide
Configuration Example
242
Example 2—ATM interface on an ERX7xx model, ERX14xx model, or the ERX310 router
that uses the slot/port format
host1(config)#interface tunnel dvmrp:boston-tunnel-1
host1(config-if)#tunnel source atm 5/0.12
Example 3—ATM interface on an E320 router that uses the slot/adapter/port format
host1(config)#interface tunnel dvmrp:boston-tunnel-1
host1(config-if)#tunnel source atm 5/1/0.12
Use the no version to remove the source of a tunnel.
See tunnel source.
In this example, two GRE tunnel interfaces are configured on different virtual routers of
an E Series router. The source of the first tunnel interface matches the destination of the
second tunnel interface and vice versa.
NOTE: This example contains an ATM interface configuration for an ERX7xx model,
ERX14xx model, or ERX310 router that uses the slot/port format.
Configure a virtual router called boston that supports one end of the tunnel.
1.
host1#virtual-router boston
Configure a physical or loopback interface for the end of the tunnel on virtual router
2.
boston.
The IP address of this interface appears in the header of tunneled frames and is used
for forwarding traffic.
host1:boston#interface atm 12/0.5
host1:boston(config-if)#ip address 10.5.5.5 255.255.255.0
Configure the tunnel interface on virtual router boston.
3.
a.
Create the tunnel interface.
host1:boston(config)#interface tunnel gre:ChicagoTunnel
b.
Configure the source and destination points of the tunnel interface.
host1:boston(config-if)#tunnel source 10.5.5.5
host1:boston(config-if)#tunnel destination 10.6.6.6
c.
Set the MTU for the tunnel.
host1:boston(config-if)#tunnel mtu 8000
d.
Configure the IP address of the tunnel interface.
host1:boston(config-if)#ip address 10.7.7.7 255.255.255.0
Configure a virtual router called chicago that supports the other end of the tunnel.
4.
host1(config)#virtual-router chicago
Copyright © 2010, Juniper Networks, Inc.
Advertisement
Table of Contents
