Supported Platforms
Related Documentation
- EX Series
- Example: Configuring an FCoE Transit Switch
- Example: Configuring DCBX to Support an iSCSI Application
- Understanding Data Center Bridging Capability Exchange Protocol for EX Series Switches
- EX, QFX Series
- dcbx
- QFX Series
- Configuring DCBX Autonegotiation
- Example: Configuring DCBX Application Protocol TLV Exchange
- Understanding DCB Features and Requirements
show dcbx neighbors
Syntax
Release Information
Command introduced in Junos OS Release 11.1 for the QFX Series.
Command introduced in Junos OS Release 11.3 for EX Series switches.
Description
Display information about Data Center Bridging Capability Exchange protocol (DCBX) neighbor interfaces.
Options
none | — | Display information about all DCBX neighbor interfaces. |
interface-name | — | (Optional) Display information for the specified interface. |
terse | — | Display the specified level of output. (On the EX Series switch, ETS values appear in the output but are not applicable to the switch; ignore these values.) |
Required Privilege Level
view
Related Documentation
- EX Series
- Example: Configuring an FCoE Transit Switch
- Example: Configuring DCBX to Support an iSCSI Application
- Understanding Data Center Bridging Capability Exchange Protocol for EX Series Switches
- EX, QFX Series
- dcbx
- QFX Series
- Configuring DCBX Autonegotiation
- Example: Configuring DCBX Application Protocol TLV Exchange
- Understanding DCB Features and Requirements
List of Sample Output
show dcbx neighbors interface (QFX Series, DCBX Version 1.01 Mode)show dcbx neighbors interface (QFX Series, IEEE DCBX Mode)
show dcbx neighbors terse (QFX Series)
show dcbx neighbors (EX4500 Switch: FCoE Interfaces on Both Local and Peer with PFC Configured Compatibly)
show dcbx neighbors (EX4500 Switch: DCBX Interfaces on Local and Peer Are Configured Compatibly with iSCSI Application)
Output Fields
Table 1 lists the output fields for the show dcbx neighbors command. Output fields are listed in the approximate order in which they appear.
Table 1: show dcbx neighbors Output Fields
Field Name | Field Description | ||
---|---|---|---|
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:
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:
| ||
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:
| ||
Operational State | (DCBX Version 1.01 only) Operational state of the feature: enabled or disabled. | ||
Local- | 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:
| ||
Willing | Willingness of the local interface to learn the PFC configuration from the peer using DCBX:
| ||
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:
| ||
Operational State | PFC operational state on the interface:
| ||
Maximum Traffic Classes capable to support PFC | Largest number of traffic classes the local interface supports for PFC:
| ||
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:
| ||
Operational Mode | (QFX Series) PFC operational mode for each 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:
| ||
Willing | Willingness of the peer to learn the PFC configuration from the local interface using DCBX:
| ||
Error | (DCBX Version 1.01 only) Configuration compatibility error status:
| ||
Operational State | PFC operational state 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:
| ||
Maximum Traffic Classes capable to support PFC | Largest number of traffic classes the peer supports for PFC:
| ||
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:
| ||
Feature: Application | State information for the DCBX application. | ||
Protocol-State | (DCBX Version 1.01 only) DCBX protocol state synchronization status:
| ||
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:
| ||
Willing | (DCBX Version 1.01 only) Willingness of the local interface to learn the FCoE interface state from the peer using DCBX:
| ||
Error | (DCBX Version 1.01 only) Configuration compatibility error status:
| ||
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:
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:
| ||
Willing | (DCBX Version 1.01 only) Willingness of the peer to learn the FCoE interface state from the local interface using DCBX:
| ||
Error | (DCBX Version 1.01 only) Configuration compatibility error status:
| ||
Appl-Name | Name of the application:
| ||
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:
| ||
Feature: ETS | (QFX Series only) Enhanced Transmission Selection (ETS) DCBX state information. | ||
Protocol-State | (DCBX Version 1.01 only) ETS protocol state synchronization status:
| ||
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:
| ||
TLV Type | (IEEE DCBX only) Type of ETS TLV:
| ||
Willing | Willingness of the local interface to learn the ETS state from the peer using DCBX:
| ||
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:
| ||
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. | ||
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. | ||
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:
| ||
TLV Type | (IEEE DCBX only) Type of ETS TLV:
| ||
Willing | Willingness of the peer to learn the ETS state from the local interface using DCBX:
| ||
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:
| ||
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. | ||
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. | ||
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:
| ||
App | (QFX Series, terse option only) DCBX TLV advertisement state for any other application:
| ||
ETS | (QFX Series, terse option only) Local DCBX TLV advertisement state for ETS:
| ||
ETS Rec | (QFX Series, terse option only) DCBX TLV peer advertisement state for ETS (state received from the connected DCBX peer):
Note: When the DCBX mode is DCBX version 1.01, no peer information is displayed. | ||
Version | (QFX Series, terse option only) The DCBX version used on the interface and whether the DCBX version was autonegotiated or explicitly configured:
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. |
Sample Output
show dcbx neighbors interface (QFX Series, DCBX Version 1.01 Mode)
user@switch> show dcbx neighbors interface xe-0/0/0
Interface : xe-0/0/0.0 - Parent Interface: ae0.0 Active-application-map: app-map-1 Protocol-Mode: IEEE-DCBX Protocol-State: in-sync Local-Advertisement: Operational version: 1 sequence-number: 130, acknowledge-id: 102 Peer-Advertisement: Operational version: 1 sequence-number: 102, acknowledge-id: 130 Feature: PFC, Protocol-State: in-sync Operational State: Enabled Local-Advertisement: Enable: Yes, Willing: No, Error: No Maximum Traffic Classes capable to support PFC: 8 Code Point Admin Mode Operational Mode 000 Disabled Disable 001 Disabled Disable 010 Disabled Disable 011 Enabled Enable 100 Enabled Enable 101 Disabled Disable 110 Disabled Disable 111 Disabled Disable Peer-Advertisement: Enable: Yes, Willing: No, Error: No Maximum Traffic Classes capable to support PFC: 8 Code Point Admin Mode 000 Disabled 001 Disabled 010 Disabled 011 Enabled 100 Enabled 101 Disabled 110 Disabled 111 Disabled Feature: Application, Protocol-State: in-sync Local-Advertisement: Enable: Yes, Willing: No, Error: No Appl-Name Ethernet-Type Socket-Number Priority-Map Status FCoE 0x8906 00001110 Enabled iSCSI 3260 10000000 Enabled Peer-Advertisement: Enable: Yes, Willing: Yes, Error: No Appl-Name Ethernet-Type Socket-Number Priority-Map Status FCoE 0x8906 N/A 00001110 Enabled Feature: ETS, Protocol-State: in-sync Operational State: Enabled Local-Advertisement: Enable: Yes, Willing: No, Error: No Maximum Traffic Classes capable to support PFC: 8 Code Point Priority-Group 000 0 001 7 010 7 011 7 100 0 101 1 110 1 111 7 Priority-Group Percentage B/W 0 40% 1 5% Peer-Advertisement: Enable: Yes, Willing: No, Error: No Maximum Traffic Classes capable to support PFC: 8 Code Point Priority-Group 000 0 001 7 010 7 011 7 100 0 101 1 110 1 111 7 Priority-Group Percentage B/W 0 40% 1 5%
show dcbx neighbors interface (QFX Series, IEEE DCBX Mode)
user@switch> show dcbx neighbors interface xe-0/0/0
Interface : xe-0/0/0.0 - Parent Interface: ae0.0 Active-application-map: app-map-1 Protocol-Mode: IEEE-DCBX Version Feature: PFC Local-Advertisement: Willing: No Mac auth Bypass Capability: No Operational State: Enabled Maximum Traffic Classes capable to support PFC: 8 Code Point Admin Mode 000 Disabled 001 Disabled 010 Disabled 011 Enabled 100 Enabled 101 Disabled 110 Disabled 111 Disabled Peer-Advertisement: Willing: No Mac auth Bypass Capability: No Operational State: Enabled Maximum Traffic Classes capable to support PFC: 8 Code Point Admin Mode 000 Disabled 001 Disabled 010 Disabled 011 Enabled 100 Enabled 101 Disabled 110 Disabled 111 Disabled Feature: Application Local-Advertisement: Appl-Name Ethernet-Type Socket-Number Priority-field FCoE 0x8906 00001110 iSCSI 3260 10000000 Peer-Advertisement: Appl-Name Ethernet-Type Socket-Number Priority-field FCoE 0x8906 N/A 00001110 Feature: ETS Local-Advertisement: TLV Type: Configuration/Recommendation Willing: No Credit Based Shaper: No Maximum Traffic Classes supported: 3 Code Point Priority-Group 000 0 001 7 010 7 011 7 100 0 101 1 110 1 111 7 Priority-Group Percentage B/W 0 40% 1 5% Priority-Group Transmission Selection Algorithm 0 Enhanced Transmission Selection 1 Enhanced Transmission Selection Peer-Advertisement: TLV Type: Configuration Willing: No Credit Based Shaper: No Code Point Priority-Group 000 0 001 7 010 7 011 7 100 0 101 1 110 1 111 7 Priority-Group Percentage B/W 0 40% 1 5% Priority-Group Transmission Selection Algorithm 0 Enhanced Transmission Selection 1 Enhanced Transmission Selection Peer-Advertisement: TLV Type: Recommendation Code Point Priority-Group 000 0 001 7 010 7 011 7 100 0 101 1 110 1 111 7 Priority-Group Percentage B/W 0 40% 1 5% Priority-Group Transmission Selection Algorithm 0 Enhanced Transmission Selection 1 Enhanced Transmission Selection
show dcbx neighbors terse (QFX Series)
user@switch> show dcbx neighbors terse
Interface Parent PFC App ETS ETS Version Interface Rec xe-0/0/8.0 - Advt Advt Advt Advt IEEE (Auto) xe-0/0/9.0 - Disabled Disabled Disabled 1.01 xe-0/0/11.0 ae0.0 Advt Advt Advt Advt IEEE (Auto) xe-0/0/12.0 ae0.0 Advt Advt Advt Advt IEEE (Auto) xe-0/0/32.0 - Advt Advt Advt Not Advt IEEE xe-0/0/36.0 - Advt Advt Advt Advt IEEE
show dcbx neighbors (EX4500 Switch: FCoE Interfaces on Both Local and Peer with PFC Configured Compatibly)
user@switch> show dcbx neighbors interface xe-0/0/14
Interface : xe-0/0/14.0 - Parent Interface: ae0.0 Protocol-State: in-sync Local-Advertisement: Operational version: 0 sequence-number: 6, acknowledge-id: 6 Peer-Advertisement: Operational version: 0 sequence-number: 6, acknowledge-id: 6 Feature: PFC, Protocol-State: in-sync Operational State: Enabled Local-Advertisement: Enable: Yes, Willing: No, Error: No Maximum Traffic Classes capable to support PFC: 6 Code Point Admin Mode 000 Disabled 001 Disabled 010 Disabled 011 Enabled 100 Disabled 101 Disabled 110 Disabled 111 Disabled Peer-Advertisement: Enable: Yes, Willing: No, Error: No Maximum Traffic Classes capable to support PFC: 6 Code Point Admin Mode 000 Disabled 001 Disabled 010 Disabled 011 Enabled 100 Disabled 101 Disabled 110 Disabled 111 Disabled Feature: Application, Protocol-State: in-sync Local-Advertisement: Enable: Yes, Willing: No, Error: No <<< Error bit will not be set as there is no miss configuration between local and peer. Appl-Name Ethernet-Type Socket-Number Priority-Map Status FCoE 0x8906 00001000 Enabled Peer-Advertisement: Enable: Yes, Willing: No, Error: No Appl-Name Ethernet-Type Socket-Number Priority-Map Status FCoE 0x8906 00001000 Enabled
show dcbx neighbors (EX4500 Switch: DCBX Interfaces on Local and Peer Are Configured Compatibly with iSCSI Application)
user@switch> show dcbx neighbors interface xe-0/0/14
Interface : xe-0/0/14.0 - Parent Interface: ae0.0 Protocol-State: in-sync Active-application-map: iscsi-map Local-Advertisement: Operational version: 0 sequence-number: 9, acknowledge-id: 12 Peer-Advertisement: Operational version: 0 sequence-number: 12, acknowledge-id: 9 Feature: PFC, Protocol-State: in-sync Operational State: Enabled Local-Advertisement: Enable: Yes, Willing: No, Error: No Maximum Traffic Classes capable to support PFC: 6 Code Point Admin Mode 000 Disabled 001 Disabled 010 Disabled 011 Enabled 100 Disabled 101 Disabled 110 Disabled 111 Disabled Peer-Advertisement: Enable: Yes, Willing: No, Error: No Maximum Traffic Classes capable to support PFC: 6 Code Point Admin Mode 000 Disabled 001 Disabled 010 Disabled 011 Enabled 100 Disabled 101 Disabled 110 Disabled 111 Disabled Feature: Application, Protocol-State: in-sync Local-Advertisement: Enable: Yes, Willing: No, Error: No Appl-Name Ethernet-Type Socket-Number Priority-Map Status FCoE 0x8906 00001000 Enabled iscsi 3260 00100000 Enabled Peer-Advertisement: Enable: Yes, Willing: No, Error: No Appl-Name Ethernet-Type Socket-Number Priority-Map Status FCoE 0x8906 00001000 Enabled iscsi 3260 00100000 Enabled
Published: 2012-07-31
Supported Platforms
Related Documentation
- EX Series
- Example: Configuring an FCoE Transit Switch
- Example: Configuring DCBX to Support an iSCSI Application
- Understanding Data Center Bridging Capability Exchange Protocol for EX Series Switches
- EX, QFX Series
- dcbx
- QFX Series
- Configuring DCBX Autonegotiation
- Example: Configuring DCBX Application Protocol TLV Exchange
- Understanding DCB Features and Requirements