DCBX configuration example

Network requirements

As shown in Figure 74, in a data center network, interface Ten-GigabitEthernet 1/0/1 of the access switch (Switch A) connects to the FCoE adapter of the data center server (DC server).

Configure Switch A to implement lossless FCoE and FIP frame transmission to DC server.

NOTE:

In this example, both Switch A and the DC server support DCBX Rev 1.01.

Figure 74: Network diagram

Configuration procedure

Enable LLDP and DCBX TLV advertising:

# Enable LLDP globally.

<SwitchA> system-view
[SwitchA] lldp global enable

# Enable LLDP and DCBX TLV advertising on interface Ten-GigabitEthernet 1/0/1.

[SwitchA] interface ten-gigabitethernet 1/0/1
[SwitchA-Ten-GigabitEthernet1/0/1] lldp enable
[SwitchA-Ten-GigabitEthernet1/0/1] lldp tlv-enable dot1-tlv dcbx
[SwitchA-Ten-GigabitEthernet1/0/1] quit

Configure APP parameters:

# Create Ethernet frame header ACL 4000.

[SwitchA] acl number 4000

# Configure ACL 4000 to permit FCoE frames (frame type is 0x8906) and FIP frames (frame type is 0x8914) to pass through.

[SwitchA-acl-ethernetframe-4000] rule permit type 8906 ffff
[SwitchA-acl-ethernetframe-4000] rule permit type 8914 ffff
[SwitchA-acl-ethernetframe-4000] quit

# Create a class named app_c, specify the operator of the class as OR, and use ACL 4000 as the match criterion of the class.

[SwitchA] traffic classifier app_c operator or
[SwitchA-classifier-app_c] if-match acl 4000
[SwitchA-classifier-app_c] quit

# Create a traffic behavior named app_b, and configure the traffic behavior to mark packets with 802.1p priority value 3.

[SwitchA] traffic behavior app_b
[SwitchA-behavior-app_b] remark dot1p 3
[SwitchA-behavior-app_b] quit

# Create a QoS policy named plcy, associate class app_c with traffic behavior app_b in the QoS policy, and apply the association to DCBX.

[SwitchA] qos policy plcy
[SwitchA-qospolicy-plcy] classifier app_c behavior app_b mode dcbx
[SwitchA-qospolicy-plcy] quit

# Apply the policy named plcy to the outgoing traffic of interface Ten-GigabitEthernet 1/0/1.

[SwitchA] interface ten-gigabitethernet 1/0/1
[SwitchA-Ten-GigabitEthernet1/0/1] qos apply policy plcy outbound
[SwitchA-Ten-GigabitEthernet1/0/1] quit

Configure ETS parameters:
# Configure the 802.1p-to-local priority mapping table to map 802.1p priority value 3 to local precedence 3. (This is the default mapping table. You can modify this configuration as needed.)
```
[SwitchA] qos map-table dot1p-lp
[SwitchA-maptbl-dot1p-lp] import 3 export 3
[SwitchA-maptbl-dot1p-lp] quit
```
# Configure the interface Ten-GigabitEthernet 1/0/1 to trust the 802.1p priority carried in packets.
```
[SwitchA] interface ten-gigabitethernet 1/0/1
[SwitchA-Ten-GigabitEthernet1/0/1] qos trust dot1p
```
# Enable byte-count WRR queuing on interface Ten-GigabitEthernet 1/0/1, and configure queue 3 on the interface to use SP queuing.
```
[SwitchA-Ten-GigabitEthernet1/0/1] qos wrr byte-count
[SwitchA-Ten-GigabitEthernet1/0/1] qos wrr 3 group sp
```
Enable interface Ten-GigabitEthernet 1/0/1 to automatically negotiate with its peer to decide whether to enable PFC, and enable PFC for 802.1 priority 3.
```
[SwitchA-Ten-GigabitEthernet1/0/1] priority-flow-control auto
[SwitchA-Ten-GigabitEthernet1/0/1] priority-flow-control no-drop dot1p 3
```

Verifying the configuration

# Display the data exchange result on the DC server through the software interface for the network adapter. This example uses the data exchange result for a QLogic adapter on the DC server.

------------------------------------------------------
DCBX Parameters Details for CNA Instance 0 - QLE8142
------------------------------------------------------

Mon May 17 10:00:50 2010

DCBX TLV (Type-Length-Value) Data
=================================
DCBX Parameter Type and Length
        DCBX Parameter Length: 13
        DCBX Parameter Type: 2

DCBX Parameter Information
        Parameter Type: Current
        Pad Byte Present: Yes
        DCBX Parameter Valid: Yes
        Reserved: 0

DCBX Parameter Data
        Priority Group ID of Priority 1: 0
        Priority Group ID of Priority 0: 2

        Priority Group ID of Priority 3: 15
        Priority Group ID of Priority 2: 1

        Priority Group ID of Priority 5: 5
        Priority Group ID of Priority 4: 4

        Priority Group ID of Priority 7: 7
        Priority Group ID of Priority 6: 6

        Priority Group 0 Percentage: 2
        Priority Group 1 Percentage: 4
        Priority Group 2 Percentage: 6
        Priority Group 3 Percentage: 0
        Priority Group 4 Percentage: 10
        Priority Group 5 Percentage: 18
        Priority Group 6 Percentage: 27
        Priority Group 7 Percentage: 31

        Number of Traffic Classes Supported: 8

DCBX Parameter Information
        Parameter Type: Remote
        Pad Byte Present: Yes
        DCBX Parameter Valid: Yes
        Reserved: 0

DCBX Parameter Data
        Priority Group ID of Priority 1: 0
        Priority Group ID of Priority 0: 2

        Priority Group ID of Priority 3: 15
        Priority Group ID of Priority 2: 1

        Priority Group ID of Priority 5: 5
        Priority Group ID of Priority 4: 4

        Priority Group ID of Priority 7: 7
        Priority Group ID of Priority 6: 6

        Priority Group 0 Percentage: 2
        Priority Group 1 Percentage: 4
        Priority Group 2 Percentage: 6
        Priority Group 3 Percentage: 0
        Priority Group 4 Percentage: 10
        Priority Group 5 Percentage: 18
        Priority Group 6 Percentage: 27
        Priority Group 7 Percentage: 31

        Number of Traffic Classes Supported: 8

DCBX Parameter Information
        Parameter Type: Local
        Pad Byte Present: Yes
        DCBX Parameter Valid: Yes
        Reserved: 0

DCBX Parameter Data
        Priority Group ID of Priority 1: 0
        Priority Group ID of Priority 0: 0

        Priority Group ID of Priority 3: 1
        Priority Group ID of Priority 2: 0

        Priority Group ID of Priority 5: 0
        Priority Group ID of Priority 4: 0

        Priority Group ID of Priority 7: 0
        Priority Group ID of Priority 6: 0

        Priority Group 0 Percentage: 50
        Priority Group 1 Percentage: 50
        Priority Group 2 Percentage: 0
        Priority Group 3 Percentage: 0
        Priority Group 4 Percentage: 0
        Priority Group 5 Percentage: 0
        Priority Group 6 Percentage: 0
        Priority Group 7 Percentage: 0

        Number of Traffic Classes Supported: 2

The output shows that the DC server will use SP queuing (priority group ID 15) for 802.1p priority 3.

DCBX Parameter Type and Length
        DCBX Parameter Length: 2
        DCBX Parameter Type: 3

DCBX Parameter Information
        Parameter Type: Current
        Pad Byte Present: No
        DCBX Parameter Valid: Yes
        Reserved: 0

DCBX Parameter Data
        PFC Enabled on Priority 0: No
        PFC Enabled on Priority 1: No
        PFC Enabled on Priority 2: No
        PFC Enabled on Priority 3: Yes
        PFC Enabled on Priority 4: No
        PFC Enabled on Priority 5: No
        PFC Enabled on Priority 6: No
        PFC Enabled on Priority 7: No

        Number of Traffic Classes Supported: 6

DCBX Parameter Information
        Parameter Type: Remote
        Pad Byte Present: No
        DCBX Parameter Valid: Yes
        Reserved: 0

DCBX Parameter Data
        PFC Enabled on Priority 0: No
        PFC Enabled on Priority 1: No
        PFC Enabled on Priority 2: No
        PFC Enabled on Priority 3: Yes
        PFC Enabled on Priority 4: No
        PFC Enabled on Priority 5: No
        PFC Enabled on Priority 6: No
        PFC Enabled on Priority 7: No

        Number of Traffic Classes Supported: 6

DCBX Parameter Information
        Parameter Type: Local
        Pad Byte Present: No
        DCBX Parameter Valid: Yes
        Reserved: 0

DCBX Parameter Data
        PFC Enabled on Priority 0: No
        PFC Enabled on Priority 1: No
        PFC Enabled on Priority 2: No
        PFC Enabled on Priority 3: Yes
        PFC Enabled on Priority 4: No
        PFC Enabled on Priority 5: No
        PFC Enabled on Priority 6: No
        PFC Enabled on Priority 7: No

        Number of Traffic Classes Supported: 1

The output shows that the DC server will use PFC for 802.1p priority 3.

prev	up	next
CDP-compatible LLDP configuration example	home	Configuring cut-through Layer 2 forwarding