.svg?sv=2022-11-02&spr=https&st=2024-12-23T05%3A53%3A27Z&se=2024-12-23T06%3A03%3A27Z&sr=c&sp=r&sig=Cu7J2v6a20xg3rfim2JjSPrWUN%2F%2Fa8haR2sZNaYlAck%3D){kind=logo}
Configuring the LLDP Trace Options
- 24 Apr 2023
- 1 Minute to read
- Contributors
- Print
- PDF
Configuring the LLDP Trace Options
- Updated on 24 Apr 2023
- 1 Minute to read
- Contributors
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
By default, only Critical trace is enabled.
- View the default trace option by executing the following command.
your product# debug lldp
LLDP critical debugging is on
- Enable all trace options by executing the following command.
your product# debug lldp all
- View the trace option by executing the following command.
your product# debug lldp
LLDP all debugging is on
- Disable all traces by executing the following command.
your product# no debug lldp all
- View the trace option by executing the following command.
your product# debug lldp
Note: After disabling all traces, no traces are displayed.
- Enable Packet Dump, Neighbor Update, and VLAN Name TLV traces by executing the following command.
your product# debug lldp pkt-dump neigh-updt tlv vlan-name
View the trace option by executing the following command.
your product# debug lldp
LLDP packet dump debugging is on
LLDP Neighbor Update debugging is on
LLDP Vlan Name tlv debugging is on
- Disable Neighbor Update trace by executing the following command.
your product# no debug lldp neigh-updt
- View the trace option by executing the following command.
your product# debug lldp
LLDP packet dump debugging is on
LLDP Vlan Name tlv debugging is on
Note: Neighbor Update trace is not displayed.
© 2024 Cisco and/or its affiliates. All rights reserved.
For more information about trademarks, please visit: Cisco trademarks
For more information about legal terms, please visit: Cisco legal terms
For legal information about Accedian Skylight products, please visit: Accedian legal terms and tradmarks
Was this article helpful?