Restart global timers, Ibed in, Configuring ipv6 session enforce check – Brocade Multi-Service IronWare Switching Configuration Guide (Supporting R05.6.00) User Manual
Page 755
![background image](/manuals/361635/755/background.png)
Multi-Service IronWare Switching Configuration Guide
725
53-1003036-02
Restart global timers
19
To clear statistics for a specific tunnel, include the ID of that tunnel.
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.
NOTE
The Brocade NetIron CES and Brocade NetIron CER devices currently do not support the
ip-tunnel-policy command or IPv6 tunnels.
To configure the IPv6 session enforce check, go to the IP tunnel policy context and enter the
ipv6-sessionenforce-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.
The system might prompt you to write the configuration to memory and reload the system. If the
system has not yet allocated a source-ingress CAM partition, it prompts you to write the results of
the current configuration to memory and reload the system.
The first-time execution of certain commands can prompt the allocation of a source-ingress CAM
partition that is required by certain features. These commands are gre-session-enforce-check,
ipv6-session-enforce-check, and accounting-enable. After this CAM partition is allocated, you do
not need to do the memory write and reload after the first-time execution of the other two
commands.
NOTE
The ipv6-sessions-enforce-check command is not supported for 6to4 automatic tunnels.
Restart global timers
Restart contains two global timers that:
•
Limit the amount of time used for re-syncing routes between the backup Management module
and Interface modules (LPs) within the same chassis
•
Allow a buffer time for protocols to converge and solve dependencies among each other
If the protocol-based restart features are configured when a Management module (MP) performs a
switchover to the its backup, routes are maintained on the LPs through the protocol-based restart
processes for a specified period of time while the new MP learns the network routes. Once the MP
learns all of its routes, the routes from the MP are synced with the routes on the LPs.
The two timers introduced here are called the max-hold-timer and the protocols-converge-timer.