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
128 Chapter 7: Link Layer Discovery Protocol BMD00113, September 2009
The LLDP information to be distributed by the GbE2c ports, and that which has been collected from
other LLDP stations, is stored in the switch’s Management Information Base (MIB). Network
Management Systems (NMS) can use Simple Network Management Protocol (SNMP) to access
this MIB information. LLDP-related MIB information is read-only.
Changes, either to the local switch LLDP information or to the remotely received LLDP information,
are flagged within the MIB for convenient tracking by SNMP-based management systems.
For LLDP to provide expected benefits, all network devices that support LLDP should be consistent
in their LLDP configuration.
Enabling or Disabling LLDP
Global LLDP Setting
By default, LLDP is enabled on the GbE2c. To turn LLDP off or on, use the following commands:
Transmit and Receive Control
The GbE2c can also be configured to transmit or receive LLDP information on a port-by-port basis.
By default, when LLDP is globally enabled on the switch, GbE2c ports transmit and receive LLDP
information (see the tx_rx option below). To change the LLDP transmit and receive state, the
following commands are available:
To view the LLDP transmit and receive status, use the following commands:
>> # /cfg/l2/lldp/off (Turn LLDP off globally)
or
>> # /cfg/l2/lldp/on (Turn LLDP on globally)
>> # /cfg/l2/lldp/port <n> (Select a switch port)
>> LLDP Port# admstat tx_rx (Transmit and receive LLDP)
>> LLDP Port# admstat tx_only (Only transmit LLDP)
>> LLDP Port# admstat rx_only (Only receive LLDP)
>> LLDP Port# admstat disabled (Do not participate in LLDP)
>> # /cfg/l2/lldp/cur (View LLDP status of all ports)
or
>> # /cfg/l2/lldp/port <n>/cur (View status of the selected port)