Wondering if any on the Extreme side can provide a description of what the "vendor-specific" attribute of the commands refers to? I saw another config recently that actually listed Avaya as opposed to this more generic name and the generic form did not seem to work properly. Can't seem to find an accurate reference to it. Thanks in advance!

Mandatory TLVs: (Chassis ID, port ID, TTL and End LLDPDU) As long as a system is transmitting an LLDP frame, it MUSt contain these TLVs. By running the enable lldp <port> command, these TLVs are automatically advertised.

Optional TLVs: (Port description, systems name and description, management address and system capabilities). As the name states, these aren't required, but can be advertised in addition to the above TLVs. They can be individually added using the configure lldp advertise <optional-tlv> if configured globally for all ports OR configure lldp port <port-no> advertise <tlv> if configured on a per-port basis

Custom TLVs: Over the years the original LLDP standard has undergone some enhancements by either standards organizations ( i.e. ITU or the IEEE themselves (i.e. LLDP-MED, DCBX) or via vendors like Avaya (i.e.e Ayava TLVs for Extreme). All these customizations are bundled into what we simply call vendor specific attributes. The reason for this is, if you took a packet capture of the LLDP packet, you'll noticed that each of these custom TLVs will have the organization that developed the TLV at the beginning of the TLV (i.e IEEE 802.3 Power Via MDI, Media (TIA TR-41) Committee, Avaya). These would be configured via the configure lldp port <port-no> advertise vendor specific <type-of-vs-tlv> <tlv>