Interface

Name of the interface.

Parent Interface

Name of the link aggregation group (LAG) interface to which the DCBX interface belongs.

Active-application-map

Name of the application map applied to the interface.

Protocol-Mode

(QFX Series) DCBX protocol mode the interface uses:

• IEEE DCBX Version—The interface uses IEEE DCBX mode.
• DCBX Version 1.01—The interface uses DCBX version 1.01.

Note: On interfaces that use the IEEE DCBX mode, the show dcbx neighbors interface interface-name operational command does not include application, PFC, or ETS operational state in the output.

Protocol-State

(DCBX Version 1.01 only) DCBX protocol state synchronization status:

• in-sync—The local interface received an acknowledge message from the peer to indicate that the peer received a state change message sent by the local interface.
• ack-pending—The local interface has not yet received an acknowledge message from the peer to indicate that the peer received a state change message sent by the local interface.

Local-Advertisement

(DCBX Version 1.01 only)

Status of advertisements that the local interface sends to the peer.

Operational version

Version of the DCBX standard used.

sequence-number

Number of state change messages sent to the peer.

If the interface Protocol-State value is in-sync, this number should match the acknowledge-id number in the Peer-Advertisement section.

If the interface Protocol-State value is ack-pending, this number does not match the acknowledge-id number in the Peer-Advertisement section.

acknowledge-id

Number of acknowledge messages received from the peer.

If the Protocol-State value is in-sync, this number should match the sequence-number value in the Peer-Advertisement section.

If the Protocol-State value is ack-pending, this number does not match the sequence-number value in the Peer-Advertisement section.

Peer-Advertisement

(DCBX Version 1.01 only)

Status of advertisements that the peer sends to the local interface.

Operational version

Version of the DCBX standard used.

sequence-number

Number of state change messages the peer sent to the local interface.

If this number matches the acknowledge-id number in the Local-Advertisement field, this indicates that the local interface has acknowledged all of the peer’s state change messages and is synchronized.

If this number does not match the acknowledge-id number in the Local-Advertisement field, this indicates that the peer has not yet received an acknowledgment for a state change message from the local interface.

acknowledge-id

Number of acknowledge messages the peer has received from the local interface.

If this number matches the sequence-number value in the Local-Advertisement field, this indicates that the peer has acknowledged all of the local interface’s state change messages and is in synchronization.

If this number does not match the sequence-number value in the Local-Advertisement field, this indicates that the peer has not yet sent an acknowledgment for a state change message from the local interface.

Feature: PFC

Priority-based flow control (PFC) feature DCBX state information.

Protocol-State

(DCBX Version 1.01 only)

DCBX protocol state synchronization status:

• ack-pending—The local interface has not yet received an acknowledge message from the peer to indicate that the peer received a PFC state change message sent by the local interface.
• in-sync—The local interface received an acknowledge message from the peer to indicate that the peer received a PFC state change message sent by the local interface.
• not-applicable—PFC autonegotiation is disabled.

Operational State

(DCBX Version 1.01 only)

Operational state of the feature: enabled or disabled.

Local-
Advertisement

Status of advertisements that the local interface sends to the peer.

Enable

(DCBX Version 1.01 only)

State that the local interface advertises to the peer:

• Yes—The feature is enabled.
• No—The feature is disabled.

Willing

Willingness of the local interface to learn the PFC configuration from the peer using DCBX:

• Yes—The local interface is willing to learn the PFC configuration from the peer.
• No—The local interface is not willing to learn the PFC configuration from the peer.

Mac auth Bypass Capability

(IEEE DCBX only)

(QFX Series) Media access controller (MAC) authentication bypass provides access to devices based on MAC address authentication. This is not supported, so the only value seen in the local advertisement field is no.

Error

(DCBX Version 1.01 only)

Configuration compatibility error status:

• No—No error detected. Local and peer configuration are compatible.
• Yes—Error detected. Local and peer configuration are not compatible.

Operational State

PFC operational state on the interface:

• Enabled—PFC is enabled on the interface
• Disabled—PFC is disabled on the interface

Maximum Traffic Classes capable to support PFC

Largest number of traffic classes the local interface supports for PFC:

• 6 (EX Series switches)
• 8 (QFX Series)

Code Point

PFC code point, which is specified in the 3-bit class-of-service field in the VLAN header.

Admin Mode

PFC administrative state for each code point on the local interface:

• Enabled—PFC is enabled for the code point.
• Disabled—PFC is disabled for the code point.

Operational Mode

(QFX Series) PFC operational mode for each code point:

• Enable—PFC is enabled on the code point.
• Disable—PFC is disabled on the code point.

Peer-Advertisement

Status of advertisements that the peer sends to the local interface.

Enable

(DCBX Version 1.01 only)

State that the peer advertises to the local interface:

• Yes—The feature is enabled.
• No—The feature is disabled.

Willing

Willingness of the peer to learn the PFC configuration from the local interface using DCBX:

• Yes—The peer is willing to learn the PFC configuration from the local interface.
• No—The peer is not willing to learn the PFC configuration from the local interface.

Error

(DCBX Version 1.01 only)

Configuration compatibility error status:

• No—No error detected. Local and peer configuration are compatible.
• Yes—Error detected. Local and peer configuration are not compatible.

Operational State

PFC operational state on the interface:

• Enabled—PFC is enabled on the interface
• Disabled—PFC is disabled on the interface

Mac auth Bypass Capability

(IEEE DCBX only)

(QFX Series) Media access controller (MAC) authentication bypass provides access to devices based on MAC address authentication. Although the QFX Series does not support this feature, the connected peer might support it. This field reports the peer state:

• Yes—The connected peer supports MAC authentication bypass.
• No—The connected peer does not support MAC authentication bypass.

Maximum Traffic Classes capable to support PFC

Largest number of traffic classes the peer supports for PFC:

• 6 (EX Series switches)
• 8 (QFX Series)

Code Point

PFC code point, which is specified in the 3-bit class-of-service field in the VLAN header.

Admin Mode

PFC administrative state for each code point on the peer:

• Enabled—PFC is enabled for the code point.
• Disabled—PFC is disabled for the code point.

Feature: Application

State information for the DCBX application.

Protocol-State

(DCBX Version 1.01 only)

DCBX protocol state synchronization status:

• in-sync—The local interface received an acknowledge message from the peer to indicate that the peer received an FCoE state change message sent by the local interface.
• ack-pending—The local interface has not yet received an acknowledge message from the peer to indicate that the peer received an FCoE state change message sent by the local interface.
• not-applicable—The local interface is set to no-auto-negotiation (autonegotiation is disabled). If the interface is associated with an FCoE forwarding class, the interface advertises FCoE capability even if the connected peer does not advertise FCoE capability.

Local-Advertisement

Status of advertisements that the local interface sends to the peer.

If the local interface is set to no-auto-negotiation (autonegotiation is disabled), the local advertisement portion of the output is not shown.

Enable

(DCBX Version 1.01 only)

State that the local interface advertises to the peer:

• Yes—The feature is enabled.
• No—The feature is disabled.

Willing

(DCBX Version 1.01 only)

Willingness of the local interface to learn the FCoE interface state from the peer using DCBX:

• Yes—The local interface is willing to learn the FCoE interface state from the peer.
• No—The local interface is not willing to learn the FCoE interface state from the peer.

Error

(DCBX Version 1.01 only)

Configuration compatibility error status:

• No—No error detected. The local and peer configuration are compatible.
• Yes—Error detected. The local and peer configuration are not compatible.

Appl-Name

Name of the application:

Ethernet-Type

(DCBX Version 1.01 only)

Ethernet type (EtherType) of the application. For example, 0x8906 indicates the EtherType for the FCoE application. Either the EtherType (for Layer 2 applications) or the Socket Number (for Layer 4 applications) of the application is displayed in the output.

Socket-Number

Destination port socket number of the application, if applicable. Either the EtherType (for Layer 2 applications) or the Socket Number (for Layer 4 applications) of the application is displayed in the output.

Priority-Field or Priority-Map

Priority assigned to the application.

For EX Series switches, the priority of the FCoE application is determined by the PFC congestion notification profile that has been configured and associated with the FCoE interface. For other applications, the priority is based on the application map.

Status

(DCBX Version 1.01 only)

Local status when autonegotiation is enabled:

• Enabled—The application feature is enabled on both the local interface and the peer interface. (The local configuration and the peer configuration match.)
• Disabled—The local configuration and the peer configuration do not match.

Note: If there is a configuration mismatch in one application between the switch and the peer, all the other applications including FCoE are disabled.

Peer-Advertisement

Status of advertisements that the peer sends to the local interface.

Enable

(DCBX Version 1.01 only)

State that the peer advertises to the local interface:

• Yes—The feature is enabled.
• No—The feature is disabled.

Willing

(DCBX Version 1.01 only)

Willingness of the peer to learn the FCoE interface state from the local interface using DCBX:

• Yes—The peer is willing to learn the FCoE interface state from the local interface.
• No—The peer is not willing to learn the FCoE interface state from the local interface.

Error

(DCBX Version 1.01 only)

Configuration compatibility error status:

• No—No error detected. Local and peer configuration are compatible.
• Yes—Error detected. Local and peer configuration are not compatible.

Appl-Name

Name of the application:

• FCoE—Fibre Channel over Ethernet

Ethernet-Type

Ethernet type (EtherType) of the application. For example, 0x8906 indicates the EtherType for the FCoE application. Either the EtherType (for Layer 2 applications) or the Socket-Number (for Layer 4 applications) of the application is displayed in the output.

Socket-Number

Destination port socket number of the application, if applicable. Either the EtherType (for Layer 2 applications) or the Socket Number (for Layer 4 applications) of the application is displayed in the output.

Priority-Field or Priority-Map

Priority assigned to the application.

Status

(DCBX Version 1.01 only)

Peer interface status:

• Enabled—The application feature is enabled on both the local interface and the peer interface. (The local configuration and the peer configuration match.)
• Disabled—The local configuration and the peer configuration do not match.

Feature: ETS

Enhanced Transmission Selection (ETS) DCBX state information.

Protocol-State

(DCBX Version 1.01 only)

ETS protocol state synchronization status:

• in-sync—The local interface received an acknowledge message from the peer to indicate that the peer received an ETS state change message sent by the local interface.
• ack-pending—The local interface has not yet received an acknowledge message from the peer to indicate that the peer received an ETS state change message sent by the local interface.

Operational State

(DCBX Version 1.01 only)

Operational state of the feature, enabled or disabled.

Local-Advertisement

Status of advertisements that the local interface sends to the peer.

Enable

(DCBX Version 1.01 only)

State that the local interface advertises to the peer:

• Yes—The feature is enabled.
• No—The feature is disabled.

TLV Type

(IEEE DCBX only)

Type of ETS TLV:

• Configuration—Advertises the Configuration TLV, which communicates the local ETS configuration to the peer but does not ask the peer to use the configuration.
• Recommendation—Advertises the Recommendation TLV, which communicates the local ETS configuration to the peer, and if the peer is “willing,” configures the peer interface to match the local ETS configuration.
• Recommendation-or-Configuration—Advertises both TLVs.

Willing

Willingness of the local interface to learn the ETS state from the peer using DCBX (EX Series switches always advertise No for this field):

• Yes—Local interface is willing to learn the ETS state from the peer.
• No—Local interface is not willing to learn the ETS state from the peer.

Credit Based Shaper

(IEEE DCBX only)

Alternative method of flow control to buffer-to-buffer credit. The QFX Series does not support a credit-based shaper, so the value of this field is always No.

Error

(DCBX Version 1.01 only)

Configuration error status:

• No—No error. This should always be the switch ETS error state.
• Yes—Error detected.

Maximum Traffic Classes capable to support PFC

(DCBX Version 1.01 only)

Largest number of traffic classes the local interface supports for PFC.

Maximum Traffic Classes supported

(IEEE DCBX only)

Largest number of traffic classes the local interface supports for ETS. (EX Series switches support only one traffic class for ETS. However, a different value might be shown for this field.)

Code Point

PFC code point, which is specified in the 3-bit class-of-service field in the VLAN header.

Priority-Group

Class-of-service (CoS) priority group (forwarding class set) identification number.

Percentage B/W

Configured minimum percentage of link bandwidth allocated to the priority group. Only explicitly configured values appear in this output column. If the link bandwidth is the default percentage, it is not shown. (EX Series switches allocate 100% of link bandwidth to the default priority group, group 7.)

Transmission Selection Algorithm

(IEEE DCBX only)

The transmission selection algorithm used by the interface. The QFX Series supports ETS but does not support using the credit-based shaper algorithm, so the only value shown in this field is ETS.

Peer-Advertisement

Status of advertisements that the peer sends to the local interface.

Enable

(DCBX Version 1.01 only)

State that the peer advertises to the local interface:

• Yes—The feature is enabled.
• No—The feature is disabled.

TLV Type

(IEEE DCBX only)

Type of ETS TLV:

• Configuration—Advertises the Configuration TLV, which communicates the local ETS configuration to the peer but does not ask the peer to use the configuration.
• Recommendation—Advertises the Recommendation TLV, which communicates the local ETS configuration to the peer, and if the peer is “willing,” configures the peer interface to match the local ETS configuration.
• Configuration/Recommendation—Advertises both TLVs.

Willing

Willingness of the peer to learn the ETS state from the local interface using DCBX:

• Yes—Peer is willing to learn the ETS state from the local interface.
• No—Peer is not willing to learn the ETS state from the local interface.

Credit Based Shaper

(IEEE DCBX only)

Alternative method of flow control to buffer-to-buffer credit. The QFX Series does not support a credit-based shaper, so the value of this field is always No.

Error

(DCBX Version 1.01 only)

Configuration error status of the peer:

• No—No error in peer ETS TLV.
• Yes—Error in peer ETS TLV.

Maximum Traffic Classes capable to support PFC

(DCBX Version 1.01 only)

Largest number of traffic classes the local interface supports for PFC.

Maximum Traffic Classes supported

(IEEE DCBX only)

Largest number of traffic classes the local interface supports for ETS. (EX Series switches support only one traffic class for ETS. However, a different value might be shown for this field.)

Code Point

PFC code point, which is specified in the 3-bit class-of-service field in the VLAN header.

Priority-Group

CoS priority group (forwarding class set) identification number.

Percentage B/W

Configured minimum percentage of link bandwidth allocated to the priority group. (EX Series switches allocate 100% of link bandwidth to the default priority group, group 7.)

Transmission Selection Algorithm

(IEEE DCBX only)

Transmission selection algorithm used by the interface. The QFX Series supports ETS but does not support using the credit-based shaper algorithm, so the only value shown in this field is ETS.

PFC

(QFX Series, terse option only) DCBX TLV advertisement state for PFC:

• Disabled—PFC configuration matches the configuration on the connected peer and PFC is disabled
• Enabled—PFC configuration matches the configuration on the connected peer and PFC is enabled
• Not Advt—Interface does not advertise PFC to the connected peer

ETS

(terse option only) Local DCBX TLV advertisement state for ETS:

• Advt—Interface advertises ETS TLVs
• Disabled—ETS is disabled on the interface (interface does not advertise ETS)

ETS Rec

(terse option only) DCBX TLV peer advertisement state for ETS (state received from the connected DCBX peer):

• Advt—Peer interface advertises ETS TLVs
• Not Advt—Peer interface does not advertise ETS

Note: When the DCBX mode is DCBX version 1.01, no peer information is displayed.

Version

(terse option only) The DCBX version used on the interface and whether the DCBX version was autonegotiated or explicitly configured:

• IEEE—The interface uses IEEE DCBX.
• 1.01—The interface uses DCBX version 1.01.

When the DCBX version used is the result of autonegotiation, the term (Auto) appears next to the version. For example, IEEE (Auto) indicates that the interface autonegotiated with the connected peer to use IEEE DCBX. Autonegotiation is enabled by default.