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
120 Chapter 5: Spanning Tree Protocol BMD00113, September 2009
FDB Update
Use the FDB update option to notify other devices on the network about updates to the Forwarding
Database (FDB). When you enable FDB update (/cfg/l2/hotlinks/sndfdb ena), the
switch sends multicasts of addresses in the forwarding database (FDB) over the active interface, so
that other devices on the network can learn the new path. The Hot Links FBD update option uses the
station update rate (/cfg/l2/update <packets per second>) to determine the rate at which to
send FDB packets.
Configuration Guidelines
The following configuration guidelines apply to Hot links:
Only uplink ports and inter-switch links can be configured as 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
(/cfg/l2/mrst/off).
When Hot Links is turned on, UplinkFast must be disabled (/cfg/l2/upfast d).
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
Use the following CLI commands to configure Hot Links.
>> # /cfg/l2/hotlink/trigger 1 ena (Enable Hot Links Trigger 1)
>> Trigger 1# master/port 20 (Add port to Master interface)
>> Master# ../backup/port 21 (Add port to Backup interface)
>> Backup# ../..
>> Hot Links# on (Turn on Hot Links)
>> Hot Links# apply (Make your changes active)
>> Hot Links# save (Save for restore after reboot)