Brocade Multi-Service IronWare Routing Configuration Guide (Supporting R05.6.00) - Manual (Page 845)

Multi-Service IronWare Routing Configuration Guide 817
53-1003033-02
VRRP-E Extension for Server Virtualization
Packets from the local subnet of the virtual
IP address
If VRRP-E Extension for Server Virtualization is enabled, any packets coming from the local subnet
of the virtual IP address will be routed to the VRRP-E master router. This is for the routes whose
next-hop gateway is the master router at the Backup router. These routes are routed to the WAN
instead of switching them to the master router. The new behavior includes all the packets sent to
the virtual IP address that were intended for the master router, such as Telnet, ping and traceroute
packets. With VRRP-E Extension for Server Virtualization enabled these packets are now routed
instead of switched. Traceroute output will show one extra hop for the source IP subnet that
displays the Backup router interface IP address.
The following is an example of the traceroute command output with VRRP-E Extension for Server
Virtualization enabled.
The following is an example of the traceroute command output without VRRP-E Extension for Server
Virtualization enabled:
IPv4 VRF support
VRRP-E Extension for Server Virtualization supports IPv4 VRF forwarding.
Configuration considerations
Since the VRRP-E Extension for Server Virtualization enabled port will route all the traffic sent to
the VRRP-E MAC, ACL and PBR features configured on the port will be applied to this traffic.
VRRP-E Extension for Server Virtualization can be dynamically enabled or disabled before or after
VRRP-E is activated. No system reload is required.
Although it is not required, it is recommended that interfaces on different routers with the same
VRID have the same short-path-forwarding configuration. This will ensure that the short-path
forwarding behavior is still retained after the failover. Different VRIDs can be configured differently.
Review the SYSLOG to prevent issues such as the following.
When the VRRP master is being reconfigured from VRRP-e to VRRP, the ve interface IPv6
address is removed and then re-added, at the time of re-adding the address. This happens to
be the virtual IPv6 address of the VRRP-e, and it will trigger a fault due to the failed duplicate
address detection since the VRRP Backup still running VRRP-e. The error is shown on SYSLOG
although the "ipv6 address ..." command is not completely rejected. This results in a VRRP
operation error. Watch for a "duplucate address error" in SYSLOG and make the necessary
configuration adjustment as required.
C:\ >traceroute 10.10.10.254
Tracing route to 10.10.10.254 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 10.10.10.25
2 <1 ms <1 ms <1 ms 10.10.10.254
Trace complete.
C:\ >traceroute 10.10.10.254
Tracing route to 10.10.10.254 over a maximum of 30 hops
1 8 ms 8 ms 8 ms 10.10.10.254
Trace complete.