DCB-DCBX(8)
๐ DCB-DCBX โ show / manipulate port DCBX (Data Center Bridging eXchange)
okay bestie, sit down, we're talking DCBX today and honestly? it's giving โจnetwork magicโจ. this is the dcb-dcbx page from the Linux dcb family, and i'm gonna walk you through it like we're texting at 2am. ๐ฆ
๐ธ NAME ๐ธ
dcb-dcbx โ show / manipulate port DCBX (Data Center Bridging eXchange)
๐ SYNOPSIS ๐
dcb [ OPTIONS ] dcbx { COMMAND | help }
dcb dcbx show dev DEV
dcb dcbx set dev DEV [ host ] [ lld-managed ] [ cee ] [ ieee ] [ static ]
โจ DESCRIPTION โจ
so Data Center Bridging eXchange (DCBX) is a protocol that DCB devices use to exchange configuration info with the peers they're directly connected to. like, gossiping but make it infrastructure. ๐ฌ
the Linux DCBX object is literally just a 1-byte bitfield of flags. that's it. one lil byte. and those flags say two things:
- whether DCBX is implemented in the device or in the host
- which version of the protocol should be used
and dcb dcbx is your key to the per-port Linux DCBX object. ๐
there are two principal modes of operation:
- host mode โ the DCBX protocol is implemented by the host LLDP agent, and the DCB interfaces are used to propagate the negotiated parameters to capable devices.
- lld-managed mode โ the configuration is handled by the device, and the DCB interfaces are used for inspection of negotiated parameters, and can also be used to set initial parameters.
both valid, both iconic, depends on your vibe. ๐
๐ PARAMETERS ๐
when you use dcb dcbx set, the keywords below turn on their corresponding configuration. the keywords you don't mention on the command line are considered disabled. when you use show, every enabled feature shows up as its own keyword. slay.
hostlld-managedโ the device is in the host mode of operation, and respectively, the lld-managed mode of operation, as described above. in principle these two keywords are mutually exclusive, butdcb dcbxallows setting both and lets the driver handle it as appropriate. (yes, both. it's fine. the driver's got it. ๐)ceeieeeโ the device supports CEE (Converged Enhanced Ethernet) and, respectively, the IEEE version of the DCB specification. typically only one of these will be set, butdcb dcbxdoes not mandate this. live your truth.staticโ indicates the engine supports static configuration. no actual negotiation is performed โ negotiated parameters are always the initial configuration.
๐ EXAMPLE & USAGE ๐
put the DCB engine into the "host" mode of operation, and use IEEE-standardized DCB interfaces:
# dcb dcbx set dev eth0 host ieee
show what was set:
# dcb dcbx show dev eth0
host ieee
look at her go. ๐ญ๐
โญ EXIT STATUS โญ
exit status is 0 if the command was successful, or a positive integer upon failure. no in-between, we don't do ambiguity here.
๐ซถ SEE ALSO ๐ซถ
๐ REPORTING BUGS ๐
found a bug? report it to the Network Developers mailing list <netdev@vger.kernel.org> โ that's where the development and maintenance is primarily done. and good news bestie: you do not have to be subscribed to the list to send a message there. just send it. periodt. ๐จ
๐ AUTHOR ๐
Petr Machata <me@pmachata.org>
and that's the whole page, no cap. this one shipped as part of iproute2, dated 13 December 2020 โ go forth and configure your DCBX flags, you absolute icon. ๐ โจ๐
๐ฆ where this page comes from
- alpine 3.24: iproute2-doc 7.0.0-r0 ยท GPL-2.0-or-later
- arch rolling: iproute2 7.2.0-1
- arch rolling: iproute2 7.3.0-1 ยท GPL-2.0-or-later
- centos-stream 10: iproute 7.0.0-2.el10 ยท GPL-2.0-or-later AND NIST-PD
- nixos 26.05: iproute2 7.0.0
- nixpkgs unstable: iproute2 7.2.0
- ubuntu stonking: iproute2 7.2.0-1ubuntu1 ยท GPL-2.0-only
- ๐ girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms