14
lldp [ agent { nearest-customer | nearest-nontpmr } ] tlv-enable
basic-tlv management-address-tlv [ ipv6 ] [ ip-address ] | interface
loopback
interface-number ]
{ In Layer 2/Layer 3 aggregate interface view:
lldp agent { nearest-customer | nearest-nontpmr } tlv-enable
basic-tlv management-address-tlv
[ ipv6 ] [ ip-address ]
By default:
{ The nearest bridge agent and nearest customer bridge agent advertise the management
address TLVs.
{ The nearest non-TPMR bridge agent does not advertise the management address TLV.
The device supports only the numeric encoding format for IPv6 management addresses.
5. Set the encoding format of the management address to string.
{ In Layer 2/Layer 3 Ethernet interface view or management Ethernet interface view:
lldp [ agent { nearest-customer | nearest-nontpmr } ]
management-address-format string
{ In Layer 2/Layer 3 aggregate interface view:
lldp agent
{ nearest-customer | nearest-nontpmr }
management-address-format string
The default management address encoding format is numeric.
Setting the encapsulation format for LLDP frames
About setting the LLDP frame encapsulation format
Earlier versions of LLDP require the same encapsulation format on both ends to process LLDP
frames. To successfully communicate with a neighboring device running an earlier version of LLDP,
the local device must be set with the same encapsulation format.
Procedure
1. Enter system view.
system-view
2. Enter interface view.
interface interface-type interface-number
3. Set the encapsulation format for LLDP frames to SNAP.
{ In Layer 2/Layer 3 Ethernet interface view or management Ethernet interface view:
lldp [ agent { nearest-customer | nearest-nontpmr } ] encapsulation
snap
{ In Layer 2/Layer 3 aggregate interface view:
lldp agent { nearest-customer | nearest-nontpmr } encapsulation
snap
{ In IRF physical interface view:
lldp encapsulation snap
By default, the Ethernet II encapsulation format is used.
To Next Page
Loading...
Need help?
General