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
130 Chapter 7: Link Layer Discovery Protocol BMD00113, September 2009
Time-to-Live for Transmitted Information
The transmitted LLDP information is held by remote systems for a limited time. A time-to-live
parameter allows the switch to determine how long the transmitted data should be held before it
expires. The hold time is configured as a multiple of the configured transmission interval.
where multiplier is a value between 2 and 10. The default value is 4, meaning that remote systems
will hold the port’s LLDP information for 4 x the 30-second msgtxint value, or 120 seconds,
before removing it from their MIB.
Trap Notifications
If SNMP is enabled on the GbE2c (see “Using Simple Network Management Protocol” on
page 31), each port can be configured to send SNMP trap notifications whenever LLDP
transmissions are sent. By default, trap notification is disabled for each port. The trap notification
state can be changed using the following commands:
In addition to sending LLDP information at scheduled intervals, LLDP information is also sent
when the GbE2c detects relevant changes to its configuration or status (such as when ports are
enabled or disabled). To prevent the GbE2c from sending multiple trap notifications in rapid
succession when port status is in flux, a global trap delay timer can be configured.
The trap delay timer represents the minimum time permitted between successive trap notifications
on any port. Any interval-driven or change-driven trap notices from the port will be consolidated
until the configured trap delay expires.
The minimum trap notification interval can be configured using the following command:
where interval is the minimum number of seconds permitted between successive LLDP
transmissions on any port. The range is 1 to 3600. The default is 5 seconds.
>> # /cfg/l2/lldp/msgtxhld <multiplier>
>> # /cfg/l2/lldp/port <n>/snmptrap ena
(Send SNMP trap notifications)
or
>> # /cfg/l2/lldp/port <n>/snmptrap dis (Do not send trap notifications)
>> # /cfg/l2/lldp/notifint <interval>