BigIron RX Series Configuration Guide
443
53-1001810-01
Overview of VRRP
17
Suppose interface e2/4 goes down. Even if interface e1/6 is still up, Host1 is cut off from other
networks. In conventional VRRP, Router1 would continue to be the Master router despite the
unavailability of the exit interface for the path the router is supporting. However, if you configure
interface e1/6 to track the state of interface e2/4, if e2/4 goes down, interface e1/6 responds by
changing Router1’s VRRP priority to the value of the track priority. In the configuration shown in
Figure 84
on page 441, Router1’s priority changes from 255 to 20. One of the parameters
contained in the Hello messages the Master router sends to its Backups is the Master router’s
priority. If the track port feature results in a change in the Master router’s priority, the Backup
routers quickly become aware of the change and initiate a negotiation for Master router.
In
Figure 84
on page 441, the track priority results in Router1’s VRRP priority becoming lower than
Router2’s VRRP priority. As a result, when Router2 learns that it now has a higher priority than
Router1, Router2 initiates negotiation for Master router and becomes the new Master router, thus
providing an open path for Host1’s traffic. To take advantage of the track port feature, make sure
the track priorities are always lower than the VRRP priorities. The default track priority for the router
that owns the VRID IP address(es) is 2. The default track priority for Backup routers is 1. If you
change the track port priorities, make sure you assign a higher track priority to the Owner of the IP
address(es) than the track priority you assign on the Backup routers.
Suppression of RIP advertisements for backed up interfaces
The Brocade implementation also enhances VRRP by allowing you to configure the protocol to
suppress RIP advertisements for the backed up paths from Backup routers. Normally, a VRRP
Backup router includes route information for the interface it is backing up in RIP advertisements.
As a result, other routers receive multiple paths for the interface and might sometimes
unsuccessfully use the path to the Backup rather than the path to the Master. If you enable the
Brocade implementation of VRRP to suppress the VRRP Backup routers from advertising the
backed up interface in RIP, other routers learn only the path to the Master router for the backed up
interface.
Authentication
For backward compatibility with RFC 2338,’s implementation of VRRP can use simple passwords to
authenticate VRRP packets. The VRRP authentication type is not a parameter specific to the VRID.
Instead, VRRP uses the authentication type associated with the interfaces on which you define the
VRID. For example, if you configure your router interfaces to use a simple password to authenticate
traffic, VRRP uses the same simple password and VRRP packets that do not contain the password
are dropped. If your interfaces do not use authentication, neither does VRRP.
NOTE
The MD5 authentication type is not supported for VRRP.
Forcing a master router to abdicate to a standby router
You can force a VRRP Master to abdicate (give away control) of a virtual router to a Backup by
temporarily changing the Master’s priority to a value less than the Backup’s. When you change a
VRRP Owner’s priority, the change takes effect only for the current power cycle. The change is not
saved to the startup configuration file when you save the configuration and is not retained across a
reload or reboot. Following a reload or reboot, the VRRP Owner again has priority 255.
Summary of Contents for Brocade DCX
Page 40: ...xl BigIron RX Series Configuration Guide 53 1001810 01 ...
Page 72: ...lxxii BigIron RX Series Configuration Guide 53 1001810 01 ...
Page 88: ...16 BigIron RX Series Configuration Guide 53 1001810 01 Searching and filtering output 1 ...
Page 300: ...228 BigIron RX Series Configuration Guide 53 1001810 01 Displaying IP information 7 ...
Page 318: ...246 BigIron RX Series Configuration Guide 53 1001810 01 Deploying a LAG 8 ...
Page 418: ...346 BigIron RX Series Configuration Guide 53 1001810 01 SuperSpan 12 ...
Page 482: ...410 BigIron RX Series Configuration Guide 53 1001810 01 MRP CLI example 14 ...
Page 506: ...434 BigIron RX Series Configuration Guide 53 1001810 01 Displaying VSRP information 15 ...
Page 582: ...510 BigIron RX Series Configuration Guide 53 1001810 01 Viewing Layer 2 ACLs 20 ...
Page 634: ...562 BigIron RX Series Configuration Guide 53 1001810 01 Troubleshooting ACLs 21 ...
Page 642: ...570 BigIron RX Series Configuration Guide 53 1001810 01 Trunk formation 22 ...
Page 746: ...674 BigIron RX Series Configuration Guide 53 1001810 01 Displaying RIP filters 24 ...
Page 808: ...736 BigIron RX Series Configuration Guide 53 1001810 01 Displaying OSPF information 25 ...
Page 938: ...866 BigIron RX Series Configuration Guide 53 1001810 01 Displaying MBGP information 27 ...
Page 950: ...878 BigIron RX Series Configuration Guide 53 1001810 01 Using secure copy 28 ...
Page 988: ...916 BigIron RX Series Configuration Guide 53 1001810 01 Clearing IS IS information 29 ...
Page 1054: ...982 BigIron RX Series Configuration Guide 53 1001810 01 Sample 802 1x configurations 33 ...
Page 1108: ...1036 BigIron RX Series Configuration Guide 53 1001810 01 sFlow 39 ...
Page 1190: ...1118 BigIron RX Series Configuration Guide 53 1001810 01 Displaying RIPng information 44 ...
Page 1270: ...1198 BigIron RX Series Configuration Guide 53 1001810 01 Displaying ACLs 47 ...
Page 1310: ...1238 BigIron RX Series Configuration Guide 53 1001810 01 Displaying OSPFv3 information 48 ...
Page 1382: ...1310 BigIron RX Series Configuration Guide 53 1001810 01 Commands That Require a Reload D ...
Page 1435: ...BigIron RX Series Configuration Guide 1363 53 1001810 01 VSRP E ...
Page 1436: ...1364 BigIron RX Series Configuration Guide 53 1001810 01 VSRP E ...