Skip to content

Commit d0e54e8

Browse files
authored
Merge pull request #2877 from anarkiwi/lldpdoc
Clarify LLDP beacon service comments about stacking and spanning tree.
2 parents 1360f3c + 4f65135 commit d0e54e8

File tree

1 file changed

+8
-4
lines changed

1 file changed

+8
-4
lines changed

docs/configuration.rst

+8-4
Original file line numberDiff line numberDiff line change
@@ -286,10 +286,14 @@ LLDP (DP)
286286

287287
LLDP beacons are configured in the dp and interface configuration blocks.
288288

289-
Note: the LLDP beacon service is specifically NOT to discover topology. It is
290-
intended to facilitate physical troubleshooting (e.g. a standard cable tester
291-
can display OF port information). A seperate system will be used to probe
292-
link/neighbor activity, addressing issues such as authenticity of the probes.
289+
LLDP beacons can be used to, among other things, facilitate physical
290+
troubleshooting (e.g. so that a standard cable tester can display port
291+
information), verify FAUCET stacking topology, and cue a phone to use
292+
the right voice VLAN.
293+
294+
NOTE: while FAUCET can receive and log LLDP from other devices, FAUCET
295+
does not do spanning tree those LLDP packets will have no influence
296+
on FAUCET's forwarding decisions.
293297

294298
The following attributes can be configured withing the 'lldp_beacon'
295299
configuration block at the dp level:

0 commit comments

Comments
 (0)