HP 6120XG ProCurve Series 6120 Blade Switches Management and Configuration Gui - Page 334
Options for Reading LLDP Information Collected by the Switch
View all HP 6120XG manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 334 highlights
Configuring for Network Management Applications LLDP (Link-Layer Discovery Protocol) Data Type Configuration Options Default Description 1The Packet Time-to-Live value is included in LLDP data packets. (Refer to "Changing the Time-to-Live for Transmitted Advertisements" on page 13-48.) 2Subelement of the Chassis ID TLV. 3Subelement of the Port ID TLV. 4Subelement of the Remote-Management-Address TLV. 5Subelement of the System Capability TLV. 6Populated with data captured internally by the switch. For more on these data types, refer to the IEEE P802.1AB Standard. Remote Management Address. The switch always includes an IP address in its LLDP advertisements. This can be either an address selected by a default process, or an address configured for inclusion in advertisements. Refer to "IP Address Advertisements" on page 13-43. Debug Logging. You can enable LLDP debug logging to a configured debug destination (Syslog server and/or a terminal device) by executing the debug lldp command. (For more on Debug and Syslog, refer to the "Troubleshooting" appendix in this guide.) Note that the switch's Event Log does not record usual LLDP update messages. Options for Reading LLDP Information Collected by the Switch You can extract LLDP information from the switch to identify adjacent LLDP devices. Options include: ■ Using the switch's show lldp info command options to display data collected on adjacent LLDP devices-as well as the local data the switch is transmitting to adjacent LLDP devices (page 13-44). ■ Using an SNMP application that is designed to query the Neighbors MIB for LLDP data to use in device discovery and topology mapping. 3400/6400 only? ■ Using the walkmib command to display a listing of the LLDP MIB objects LLDP and LLDP-MED Standards Compatibility The operation covered by this section is compatible with these standards: ■ IEEE P802.1AB ■ RFC 2922 (PTOPO, or Physical Topology MIB) 13-42