Specifications
274 Implementing IBM System Networking 10Gb Ethernet Switches
Hot Links has up to 25 triggers. A trigger is a pair of Layer 2 interfaces, each containing an
individual port, trunk, or LACP adminkey. One interface is the Master, and the other is a
Backup. While the Master interface is set to the active state and forwards traffic, the Backup
interface is set to the standby state and blocks traffic until the Master interface fails. If the
Master interface fails, the Backup interface is set to active and forwards traffic. After the
Master interface is restored, it moves to the standby state and blocks traffic until the Backup
interface fails. You may select a physical port, static trunk, or an LACP adminkey as a Hot
Link interface.
Configuration guidelines
The following configuration guidelines apply to Hot Links:
Ports that are configured as Hot Link interfaces must have STP disabled.
When Hot Links is turned on, MSTP, RSTP, and PVRST must be turned off.
When Hot Links is turned on, UplinkFast must be disabled.
A port that is a member of the Master interface cannot be a member of the
Backup interface.
A port that is a member of one Hot Links trigger cannot be a member of another
Hot Links trigger.
An individual port that is configured as a Hot Link interface cannot be a member of a trunk.
Configuring Hot Links
Run the following commands to configure Hot Links:
Enable Hot Links Trigger 1 by running the following command:
Switch(config)# hotlinks trigger 1 enable
Add a port to the Master interface by running the following command:
Switch(config)# hotlinks trigger 1 master port 1
Add a port to a Backup interface by running the following command:
Switch(config)# hotlinks trigger 1 backup port 2
Turn on Hot Links by running the following command:
Switch(config)# hotlinks enable
6.5.5 VRRP
The VRRP feature is not supported in VFSM stacking mode and is not needed because the
stacking members act as a single environment.
For high availability at the aggregation layer, VRRP is implemented in AGG-1 and AGG-2
switches to provide gateway redundancy for SRV-3,
VRRP enables redundant router configurations within a LAN, providing alternative router
paths for a host to eliminate single points of failure within a network. Each participating
VRRP-capable routing device is configured with the same virtual router IPv4 address and ID
number. One of the virtual routers is elected as the Master, based on a number of priority
criteria, and assumes control of the shared virtual router IPv4 address. If the Master fails, one
of the backup virtual routers takes control of the virtual router IPv4 address and actively
process traffic addressed to it.
For detailed information about VRRP concepts and components, see the 2.7.6, “Virtual
Router Redundancy Protocol” on page 82.