From 4a1fb0acb1e4fb20356ad3496f15aa5cb065e336 Mon Sep 17 00:00:00 2001 From: Vincent Bernat Date: Wed, 12 Jun 2019 22:10:56 +0200 Subject: [PATCH] lldpd: document expectation for LLDP-MED device configuration When using class II and class III endpoints, some additional TLVs are mandatory. This is not enforced by lldpd. See #335. --- src/daemon/lldpd.8.in | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/src/daemon/lldpd.8.in b/src/daemon/lldpd.8.in index f8878049..9534ebb0 100644 --- a/src/daemon/lldpd.8.in +++ b/src/daemon/lldpd.8.in @@ -243,15 +243,21 @@ blacklisted (with .Em !* ) , the system name is used as a chassis ID instead. .It Fl M Ar class -Enable emission of LLDP-MED frame. The class should be one of the -following value: +Enable emission of LLDP-MED frame. Depending on the selected class, +the standard defines which set of TLV should be transmitted. See +section 10.2.1. Some devices may be strict about this aspect. The +class should be one of the following value: .Bl -tag -width "0:XX" -compact .It Sy 1 Generic Endpoint (Class I) .It Sy 2 -Media Endpoint (Class II) +Media Endpoint (Class II). In this case, the standard requires to +define at least one network policy through +.Nm lldpcli . .It Sy 3 -Communication Device Endpoints (Class III) +Communication Device Endpoints (Class III). In this case, the standard +requires to define at least one network policy through +.Nm lldpcli . .It Sy 4 Network Connectivity Device .El -- 2.39.5