configure lldp ports vendor-specific avaya-extreme dot1q-framing

configure lldp ports [all | port_list] [advertise | no-advertise] vendor-specific avaya-extreme dot1q-framing [tagged | untagged | auto]

Description

Configures the Link Layer Discovery Protocol port to advertise or not advertise the 802.1q framing configuration to its neighbors. The Avaya phone uses this proprietary LLDP TLV information. In addition to this LLDP TLV, you must enable LLLDP as well as configure both the LLDP MED capabilities TLV and the LLDP network policy TLV.

Syntax Description

all Specifies all ports on the switch.
port_list Specifies one or more ports or slots and ports.
advertise Specifies to send the information to neighbors.
no-advertise Specifies not to send the information to neighbors.
tagged Specifies to use tagging.

NOTE: This parameter applies only when you use the advertise parameter.

untagged Specifies not to use tagging.

NOTE: This parameter applies only when you use the advertise parameter.

auto Specifies following a predetermined sequence (see Usage Guidelines below).

NOTE: This parameter applies only when you use the advertise parameter.

Default

No advertise.

Usage Guidelines

Before configuring this LLDP TLV, you must take the following steps:

This TLV is used to exchange information about Layer 2 priority tagging between the network connectivity device (switch) and the Avaya phone.

If you configure the TLV to advertise tagging, the phone uses tagging information, which it retrieves from the configure lldp ports vendor-specific med policy application command. If you configure the TLV to advertise untagged, the phone does not use any tagging, including 802.1q priority tagging.

If you configure the TLV to advertise auto, the phone cycles through the following sequence until an action is successful:

Example

The following command configures al ports to advertise the dot1q framing as untagged to neighbors:

configure lldp ports all advertise vendor-specific avaya-extreme dot1q-framing untagged

History

This command was first available in ExtremeXOS 11.5.

Platform Availability