Configuring ipv6 session enforce check – Brocade Multi-Service IronWare Switching Configuration Guide (Supporting R05.6.00) User Manual

Page 860

Advertising
background image

830

Multi-Service IronWare Switching Configuration Guide

53-1003036-02

IPv6 Over IPv4 tunnels in hardware

19

The tos-value variable specifies a TOS value for the outer IP header. Possible values are 1 - 255.
The default value is 0.

Configuring IPv6 session enforce check

You can enable the IPv6 session enforce check by using the ipv6-session-enforce-check command.
When an IPv6 packet arrives and this feature is enabled, the system tries to match the IPv6 packet
source and destination address pair with the tunnel configured destination and source pair. If the
pairs do not match, the packet is dropped in hardware.

To configure the IPv6 session enforce check, go to the IP tunnel policy context and enter the
ipv6-session-enforce-check command.

Brocade(config)#ip-tunnel-policy

Brocade(config-ip-tunnel-policy)#ipv6-session-enforce-check

Syntax: [no] ipv6-session-enforce-check

To disable the IPv6 session enforce check, use the no form of this command. This command is
disabled by default. You might have to write the configuration to memory and reload the system
when the configuration of this command is changed because a one-time creation of a
source-ingress CAM partition is necessary. The system prompts you if the memory write and reload
are required.

The first-time execution of certain commands necessitates the creation of a source-ingress CAM
partition, after which you write to memory and reload. These commands are
gre-session-enforce-check, ipv6-session-enforce-check, and accounting-enable. After this CAM
partition is created, it is not necessary to follow either of the other two commands with a memory
write and reload.

NOTE

The ipv6-sessions-enforce-check is not supported for 6to4 automatic tunnels.

Configuring a maximum MTU value for a tunnel interface

This command allows you to set an MTU value for packets entering the tunnel. Packets that exceed
either the default MTU value of 1480 bytes or the value that you set using this command are sent
back to the source.

The following command allows you to change the MTU value for packets transiting “tunnel 1”.

Brocade(config)# interface tunnel 1

Brocade(config-tnif-1)tunnel mtu 1500

Syntax: [no] tunnel mtu packet-size

The packet-size variable specifies the maximum MTU size in bytes for the packets transiting the
tunnel.

NOTE

To prevent packet loss after the 20 byte IP header is added, make sure that any physical interface
that is carrying IPv6 tunnel traffic has an IP MTU setting at least 24 bytes greater than the tunnel
MTU setting.

Advertising