| 1 |
.TH DCB-DCBX 8 "13 December 2020" "iproute2" "Linux" |
| 2 |
.SH NAME |
| 3 |
dcb-dcbx \- show / manipulate port DCBX (Data Center Bridging eXchange) |
| 4 |
.SH SYNOPSIS |
| 5 |
.sp |
| 6 |
.ad l |
| 7 |
.in +8 |
| 8 |
|
| 9 |
.ti -8 |
| 10 |
.B dcb |
| 11 |
.RI "[ " OPTIONS " ] " |
| 12 |
.B dcbx |
| 13 |
.RI "{ " COMMAND " | " help " }" |
| 14 |
.sp |
| 15 |
|
| 16 |
.ti -8 |
| 17 |
.B dcb dcbx show dev |
| 18 |
.RI DEV |
| 19 |
|
| 20 |
.ti -8 |
| 21 |
.B dcb dcbx set dev |
| 22 |
.RI DEV |
| 23 |
.RB "[ " host " ]" |
| 24 |
.RB "[ " lld-managed " ]" |
| 25 |
.RB "[ " cee " ]" |
| 26 |
.RB "[ " ieee " ]" |
| 27 |
.RB "[ " static " ]" |
| 28 |
|
| 29 |
.SH DESCRIPTION |
| 30 |
|
| 31 |
Data Center Bridging eXchange (DCBX) is a protocol used by DCB devices to |
| 32 |
exchange configuration information with directly connected peers. The Linux DCBX |
| 33 |
object is a 1-byte bitfield of flags that configure whether DCBX is implemented |
| 34 |
in the device or in the host, and which version of the protocol should be used. |
| 35 |
.B dcb dcbx |
| 36 |
is used to access the per-port Linux DCBX object. |
| 37 |
|
| 38 |
There are two principal modes of operation: in |
| 39 |
.B host |
| 40 |
mode, DCBX protocol is implemented by the host LLDP agent, and the DCB |
| 41 |
interfaces are used to propagate the negotiate parameters to capable devices. In |
| 42 |
.B lld-managed |
| 43 |
mode, the configuration is handled by the device, and DCB interfaces are used |
| 44 |
for inspection of negotiated parameters, and can also be used to set initial |
| 45 |
parameters. |
| 46 |
|
| 47 |
.SH PARAMETERS |
| 48 |
|
| 49 |
When used with |
| 50 |
.B dcb dcbx set, |
| 51 |
the following keywords enable the corresponding configuration. The keywords that |
| 52 |
are not mentioned on the command line are considered disabled. When used with |
| 53 |
.B show, |
| 54 |
each enabled feature is shown by its corresponding keyword. |
| 55 |
|
| 56 |
.TP |
| 57 |
.B host |
| 58 |
.TQ |
| 59 |
.B lld-managed |
| 60 |
The device is in the host mode of operation and, respectively, the lld-managed |
| 61 |
mode of operation, as described above. In principle these two keywords are |
| 62 |
mutually exclusive, but |
| 63 |
.B dcb dcbx |
| 64 |
allows setting both and lets the driver handle it as appropriate. |
| 65 |
|
| 66 |
.TP |
| 67 |
.B cee |
| 68 |
.TQ |
| 69 |
.B ieee |
| 70 |
The device supports CEE (Converged Enhanced Ethernet) and, respectively, IEEE |
| 71 |
version of the DCB specification. Typically only one of these will be set, but |
| 72 |
.B dcb dcbx |
| 73 |
does not mandate this. |
| 74 |
|
| 75 |
.TP |
| 76 |
.B static |
| 77 |
Indicates the engine supports static configuration. No actual negotiation is |
| 78 |
performed, negotiated parameters are always the initial configuration. |
| 79 |
|
| 80 |
.SH EXAMPLE & USAGE |
| 81 |
|
| 82 |
Put the DCB engine into the "host" mode of operation, and use IEEE-standardized |
| 83 |
DCB interfaces: |
| 84 |
|
| 85 |
.P |
| 86 |
# dcb dcbx set dev eth0 host ieee |
| 87 |
|
| 88 |
Show what was set: |
| 89 |
|
| 90 |
.P |
| 91 |
# dcb dcbx show dev eth0 |
| 92 |
.br |
| 93 |
host ieee |
| 94 |
|
| 95 |
.SH EXIT STATUS |
| 96 |
Exit status is 0 if command was successful or a positive integer upon failure. |
| 97 |
|
| 98 |
.SH SEE ALSO |
| 99 |
.BR dcb (8) |
| 100 |
|
| 101 |
.SH REPORTING BUGS |
| 102 |
Report any bugs to the Network Developers mailing list |
| 103 |
.B <[email protected]> |
| 104 |
where the development and maintenance is primarily done. |
| 105 |
You do not have to be subscribed to the list to send a message there. |
| 106 |
|
| 107 |
.SH AUTHOR |
| 108 |
Petr Machata <[email protected]> |