Ipv6 over ipv4 tunnels in hardware, Ipv6 over ipv4, Tunnels in hardware – Brocade BigIron RX Series Configuration Guide User Manual

Page 250: Configuring a manual ipv6 tunnel

Advertising
background image

172

BigIron RX Series Configuration Guide

53-1002484-04

Configuring IP parameters

7

4 45.4.1.0/24 80.8.1.2 tunnel 2 0/0 D

5 63.148.1.0/24 DIRECT eth 2/11 0/0 D

6 70.7.1.0/24 DIRECT eth 2/14 0/0 D

7 80.8.1.0/24 70.7.1.1 eth 2/14 1/1 S

8 110.110.2.0/24 63.148.1.1 eth 2/11 1/1 S

9 189.100.1.0/24 110.110.2.12 tunnel 1 0/0 D

The show interface tunnel command displays the status and configuration information for a tunnel
interface as shown in the following.

BigIron RX# show interface tunnel 1

Tunnel1 is up, line protocol is up

Hardware is Tunnel

Tunnel source 63.148.1.2

Tunnel destination is 110.110.2.12

Tunnel mode gre ip

Tunnel loopback is 1/3

No port name

MTU 1476 Bytes

Syntax: show interface tunnel <number>

The <number> parameter indicates the tunnel interface number for which you want to display
information.

IPv6 over IPv4 tunnels in hardware

To enable communication between the isolated IPv6 domains using the IPv4 infrastructure, you
can configure IPv6 over IPv4 tunnels.

Brocade supports the following IPv6 over IPv4 tunneling in hardware mechanisms:

Manually configured tunnels

In general, a manually configured tunnel establishes a permanent link between routers in IPv6
domains. A manually configured tunnel has explicitly configured IPv4 addresses for the tunnel
source and destination.

This tunneling mechanism requires that the router at each end of the tunnel run both IPv4 and IPv6
protocol stacks. The routers running both protocol stacks, or dual-stack routers, can interoperate
directly with both IPv4 and IPv6 end systems and routers.

Configuring a manual IPv6 tunnel

You can use a manually configured tunnel to connect two isolated IPv6 domains. You should deploy
this point-to-point tunnel mechanism if you need a permanent and stable connection.

Configuration notes

The tunnel mode should be ipv6ip indicating that this is ipv6 manual tunnel

Both source and destination addresses needs to be configured on the tunnel.

On the remote side we need to have exactly opposite source or destination pair.

The tunnel destination should be reachable through the ipv4 backbone.

The ipv6 address on the tunnel needs to be configured for the tunnel to come up

Both static and dynamic IPv6 routing protocols on top of the tunnel are supported

The tunnel source can be ip address or interface name

Advertising