BLADE OS™ Application Guide HP GbE2c Ethernet Blade Switch for c-Class BladeSystem Version 5.1 Advanced Functionality Software
Table Of Contents
- Contents
- Figures
- Tables
- Preface
- Part 1: Basic Switching
- Accessing the Switch
- The Management Network
- Local Management Using the Console Port
- The Command Line Interface
- Remote Management Access
- Client IP Address Agents
- Securing Access to the Switch
- Setting Allowable Source IP Address Ranges
- RADIUS Authentication and Authorization
- TACACS+ Authentication
- LDAP Authentication and Authorization
- Secure Shell and Secure Copy
- Configuring SSH/SCP Features on the Switch
- Configuring the SCP Administrator Password
- Using SSH and SCP Client Commands
- SSH and SCP Encryption of Management Messages
- Generating RSA Host and Server Keys for SSH Access
- SSH/SCP Integration with Radius Authentication
- SSH/SCP Integration with TACACS+ Authentication
- End User Access Control
- Ports and Trunking
- Port-Based Network Access Control
- VLANs
- Spanning Tree Protocol
- RSTP and MSTP
- Link Layer Discovery Protocol
- Quality of Service
- Accessing the Switch
- Part 2: IP Routing
- Basic IP Routing
- Routing Information Protocol
- IGMP
- OSPF
- OSPF Overview
- OSPF Implementation in BLADE OS
- OSPF Configuration Examples
- Remote Monitoring
- Part 3: High Availability Fundamentals
- High Availability
- Layer 2 Failover
- Server Link Failure Detection
- VRRP Overview
- Failover Methods
- BLADE OS Extensions to VRRP
- Virtual Router Deployment Considerations
- High Availability Configurations
- High Availability
- Part 4: Appendices
- Index
BLADE OS 5.1 Application Guide
244 Chapter 14: High Availability BMD00113, September 2009
BLADE OS Extensions to VRRP
This section describes VRRP enhancements that are implemented in BLADE OS.
BLADE OS supports a tracking function that dynamically modifies the priority of a VRRP router,
based on its current state. The objective of tracking is to have, whenever possible, the master
bidding processes for various virtual routers in a LAN converge on the same switch. Tracking
ensures that the selected switch is the one that offers optimal network performance. For tracking to
have any effect on virtual router operation, preemption must be enabled.
BLADE OS can track the attributes listed in Table 24:
Each tracked parameter has a user-configurable weight associated with it. As the count associated
with each tracked item increases (or decreases), so does the VRRP router's priority, subject to the
weighting associated with each tracked item. If the priority level of a standby is greater than that of
the current master, then the standby can assume the role of the master.
See “Configuring the Switch for Tracking” on page 245 for an example on how to configure the
switch for tracking VRRP priority.
Table 24 VRRP Tracking Parameters
Parameter Description
Number of IP interfaces on the switch
that are active (“up”)
/cfg/l3/vrrp/track/ifs
Helps elect the virtual routers with the most
available routes as the master. (An IP interface is
considered active when there is at least one active
port on the same VLAN.) This parameter influences
the VRRP router's priority in virtual interface
routers.
Number of active ports on the same
VLAN
/cfg/l3/vrrp/track/ports
Helps elect the virtual routers with the most
available ports as the master. This parameter
influences the VRRP router's priority in virtual
interface routers.
Number of virtual routers in master
mode on the switch
/cfg/l3/vrrp/track/vr
Useful for ensuring that traffic for any particular
client/server pair is handled by the same switch,
increasing routing efficiency. This parameter
influences the VRRP router's priority in virtual
interface routers.