Configuring a tunnel interface – Brocade Multi-Service IronWare Switching Configuration Guide (Supporting R05.6.00) User Manual
Page 745
Multi-Service IronWare Switching Configuration Guide
715
53-1003036-02
GRE IP tunnel
19
Configuring a tunnel interface
To configure a tunnel interface, use a the following command.
Brocade(config)# interface tunnel 1
Brocade(config-tnif-1)
Syntax: [no] interface tunnel tunnel id
The tunnel-id variable is numerical value that identifies the tunnel being configured.
Possible range is from 1 to the maximum configured tunnels in the system.
Configuring a source address or source interface for a tunnel interface
To configure a source address for a specific tunnel interface, enter the following command.
Brocade(config)# interface tunnel 1
Brocade(config-tnif-1)tunnel source 10.0.8.108
To configure a source interface for a specific tunnel interface, enter the following command.
Brocade(config)# interface tunnel 100
Brocade(config-tnif-100)tunnel source ethernet 3/1
Syntax: [no] tunnel source ip-address | port-no
You can specify either of the following:
The ip-address variable is the source IP address being configured for the specified tunnel.
The port-no variable is the source slot or port of the interface being configured for the specified
tunnel. When you configure a source interface, there must be at least one IP address configured on
that interface. Otherwise, the interface will not be added to the tunnel configuration and an error
message like the following will be displayed: Error - Tunnel source interface 3/1 has no configured
ip address.
It can be a physical or virtual interface (ve).
Configuring a destination address for a tunnel interface
To configure a destination address for a specific tunnel interface, enter the following command.
Brocade(config)# interface tunnel 1
Brocade(config-tnif-1)tunnel destination 10.108.5.2
Syntax: [no] tunnel destination ip-address
The ip-address variable is destination IP address being configured for the specified tunnel.
NOTE
If GRE is configured with a tunnel destination reachable over LAG ports, load balancing will only work
with the following LAG types: server LAG or LACP with server LAG. Traffic cannot be load-balanced
across multiple ports of a switch LAG.
NOTE
Traffic from a GRE tunnel entering a MPLS tunnel is not supported.