Manual Chapter : LLDP Attributes

Applies To:

Show Versions Show Versions

BIG-IP AAM

  • 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0

BIG-IP APM

  • 17.0.0, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0

BIG-IP Analytics

  • 17.0.0, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0

BIG-IP Link Controller

  • 17.0.0, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0

BIG-IP LTM

  • 17.0.0, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0

BIG-IP PEM

  • 17.0.0, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0

BIG-IP AFM

  • 17.0.0, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0

BIG-IP DNS

  • 17.0.0, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0

BIG-IP ASM

  • 17.0.0, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.0.1, 16.0.0, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0
Manual Chapter

LLDP Attributes

The
LLDP Attributes
setting is one of two settings related to LLDP that you can configure for a specific interface. You use this interface setting to specify the content of an LLDP message being sent or received. Each LLDP attribute that you specify with this setting is optional and is in the form of Type, Length, Value (TLV).
Chassis ID
Identifies the chassis containing the IEEE 802 LAN station associated with the transmitting LLDP agent. This TLV applies to VIPRION platforms only.
Port Description
Contains an alpha-numeric string that describes the interface. If RFC 2863 is implemented, use the
ifDescr
object for this field.
System Name
Contains an alpha-numeric string that indicates the systems administratively-assigned name. The value of the
System Name
field in the LLDP message should be the system's fully qualified domain name (FQDN). If implementations support IETF RFC 3418, use the
sysName
object for this field.
System Description
Contains an alpha-numeric string that is the textual description of the network entity. The
System Description
field in the LDDP message should include the full name and version identification of the system's hardware type, software operating system, and networking software. If implementations support IETF RFC 3418, use the
sysDescr
object for this field.
System Capabilities
The primary functions of the system and whether these primary functions are enabled.
Port VLAN ID
Allows a VLAN bridge port to advertise the port's VLAN identifier (PVID) that is associated with untagged or priority tagged frames (see IEEE 802.1Q-1998, 8.4.4).
VLAN Name
Allows an IEEE 802.1Q-compatible IEEE 802 LAN station to advertise the assigned name of any VLAN with which it is configured. The
VLAN Name
field in the LLDP message must contain the VLANs name. If implementations support IETF RFC 2674, use the
dot1QVLANStaticName
object for this field.
Port and Protocol VLAN ID
Allows a bridge port to advertise a port and protocol VLAN ID. The
Port and Protocol VLAN ID
field in the LLDP message must contain the PPVID number for this IEEE 802 LAN station. If the port is not capable of supporting port and protocol VLANs and/or the port is not enabled with any port and protocol VLAN, the PPVID number should be zero.
Protocol Identity
Allows an IEEE 802 LAN station to advertise particular protocols that are accessible through the port. The
Protocol Identity
field in the LLDP message must contain the first n octets of the protocol after the Layer 2 addresses (for example, starting with the Ethertype field) that the sender needs to advertise. The value of n is determined by the need for the protocol to disambiguate itself. The protocol information string must include enough octets to allow the receiver to correctly identify the protocol and its version. To advertise Spanning Tree protocols, for example, the Protocol Identity field must include at least eight octets: IEEE 802.3 length (two octets), LLC addresses (two octets), IEEE 802.3 control (one octet), Protocol ID (two octets), and the protocol version (one octet).
PAC/PHY Config Status
Identifies the following information: The duplex and bit-rate capability of the sending IEEE 802.3 LAN node that is connected to the physical medium. The current duplex and bit-rate settings of the sending IEEE 802.3 LAN node. Whether these settings are the result of auto-negotiation during link initiation or of manual set override action.
Link Aggregation
A bit map of the link aggregation capabilities and the current aggregation status of the link.
Max Frame Size
Indicates the maximum frame size capability of the implemented MAC and PHY. This value must be an integer indicating the maximum supported frame size in octets, as determined by the following: If the MAC/PHY supports only the basic MAC frame format as defined in 3.1.1 of IEEE Std 802.3-2002, set this to 1518. If the MAC/PHY supports an extension of the basic MAC frame format for tagged MAC frames as defined in IEEE 802.3-2002, set this to 1522. If the MAC/PHY supports an extension of the MAC frame format that is different from either of the above, set this to the maximum value supported.
Product Model
The BIG-IP product model.
Management Address
An address associated with the local LLDP agent used to reach higher layer entities. This TLV might also include the system interface number that is associated with the management address, if known. If the BIG-IP system is configured with two management IP addresses (IPv4 and IPv6), both IP addresses are included in the content of the LLDP message.