research(LLDP): is it running before anyone configures it, and what does show lldp say when it is not? #1552

Merged
jaylouisw merged 1 commit from rev/1115-2201 into main 2026-11-15 23:02:46 +00:00
Owner

Question

On a real Cisco-style access switch, what is the administrative default state of LLDP, and what does show lldp print before LLDP has been enabled?

Verdict

Unresolved as a single rule. No engine change.

Evidence

  • Catalyst 2960 12.2(44)SE and Catalyst 9600 17.18 default tables: LLDP global state - Disabled, transmit/receive disabled, holdtime 120 s, timer 30 s, reinit 2 s.
  • Catalyst 9000 field notice shows both halves of the observable on IOS-XE: C9300#show lldp -> % LLDP is not enabled; C9500-1#show lldp -> the four-line Global LLDP Information: block (Status: ACTIVE, 30 s, 120 s, 2 s).
  • NX-OS (feature lldp) and IOS-XR: same "disabled by default" / % LLDP is not enabled.
  • Arista EOS: lldp run enables it, yet the CVX chapter states "LLDP is enabled by default on Arista switches" - a contradiction inside one vendor's docs.
  • Practitioner transcript: a Catalyst 3750 found LLDP globally enabled out of the box.

What PacketForge does today

Simulator.announceLldp() (engine/simulator.js:2317) announces from every cabled port unconditionally; show lldp is aliased onto the neighbour table (engine/cli.js:3672-3688), so the status view cannot be expressed. The advertised hold time (120 s, engine/lldp.js:12) does match the documented one.

Why no code

Off-by-default would answer every "what is plugged in?" with % LLDP is not enabled, and the default differs per vendor; the evidence does not settle which default the catalogue should carry. The note records what is known, inferred, unresolved, and the three-command capture (factory-default 9200/9300 before and after lldp run, plus show running-config | include lldp on an EOS box) that would settle it.

Gates

  • node scripts/syntax-check.js - 324 files, all OK
  • npm test - 254 suites, 9267 assertions, 0 failed
## Question On a real Cisco-style access switch, what is the administrative default state of LLDP, and what does `show lldp` print *before* LLDP has been enabled? ## Verdict **Unresolved as a single rule.** No engine change. ## Evidence - Catalyst 2960 12.2(44)SE and Catalyst 9600 17.18 default tables: `LLDP global state - Disabled`, transmit/receive disabled, holdtime 120 s, timer 30 s, reinit 2 s. - Catalyst 9000 field notice shows both halves of the observable on IOS-XE: `C9300#show lldp` -> `% LLDP is not enabled`; `C9500-1#show lldp` -> the four-line `Global LLDP Information:` block (`Status: ACTIVE`, 30 s, 120 s, 2 s). - NX-OS (`feature lldp`) and IOS-XR: same "disabled by default" / `% LLDP is not enabled`. - Arista EOS: `lldp run` enables it, yet the CVX chapter states "LLDP is enabled by default on Arista switches" - a contradiction inside one vendor's docs. - Practitioner transcript: a Catalyst 3750 found LLDP globally *enabled* out of the box. ## What PacketForge does today `Simulator.announceLldp()` (engine/simulator.js:2317) announces from every cabled port unconditionally; `show lldp` is aliased onto the neighbour table (engine/cli.js:3672-3688), so the status view cannot be expressed. The advertised hold time (120 s, engine/lldp.js:12) does match the documented one. ## Why no code Off-by-default would answer every "what is plugged in?" with `% LLDP is not enabled`, and the default differs per vendor; the evidence does not settle which default the catalogue should carry. The note records what is known, inferred, unresolved, and the three-command capture (factory-default 9200/9300 before and after `lldp run`, plus `show running-config | include lldp` on an EOS box) that would settle it. ## Gates - `node scripts/syntax-check.js` - 324 files, all OK - `npm test` - 254 suites, 9267 assertions, 0 failed
research(LLDP): is it running before anyone configures it, and what does show lldp say when it is not?
All checks were successful
CI / Classify the change (pull_request) Successful in 17s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 21s
CI / Test (Node 18) (pull_request) Successful in 3m29s
CI / Test (Node 20) (pull_request) Successful in 3m20s
CI / Server smoke test (pull_request) Successful in 38s
CI / Docker build (pull_request) Successful in 28s
CI / Test (Node 22) (pull_request) Successful in 3m9s
f535ac8e62
Cisco's default tables (2960 12.2(44)SE, 9600 17.18), the NX-OS and IOS-XR guides and a
Catalyst 9000 field notice all say LLDP is disabled by default and that `show lldp` answers
`% LLDP is not enabled` - and that `show lldp` on an enabled box is a four-line status block,
not the neighbour table. A practitioner transcript on a 3750 found it enabled out of the box,
and Arista's own manual says both 'use lldp run' and 'LLDP is enabled by default'.

PacketForge announces from every cabled port unconditionally (engine/simulator.js:2317) and
aliases `show lldp` onto the neighbour table (engine/cli.js:3672). The 120 s hold time it
advertises is the documented one. No engine change: the evidence does not settle a single
default, and off-by-default would empty every neighbour table in the tool.

Records what is known, inferred, unresolved, and the three-command capture that would settle it.
jaylouisw scheduled this pull request to auto merge when all checks succeed 2026-11-15 23:02:30 +00:00
jaylouisw force-pushed rev/1115-2201 from f535ac8e62
All checks were successful
CI / Classify the change (pull_request) Successful in 17s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 21s
CI / Test (Node 18) (pull_request) Successful in 3m29s
CI / Test (Node 20) (pull_request) Successful in 3m20s
CI / Server smoke test (pull_request) Successful in 38s
CI / Docker build (pull_request) Successful in 28s
CI / Test (Node 22) (pull_request) Successful in 3m9s
to 332a0855dc
All checks were successful
CI / Classify the change (pull_request) Successful in 17s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 24s
CI / Test (Node 18) (pull_request) Successful in 3m32s
CI / Test (Node 20) (pull_request) Successful in 3m14s
CI / Server smoke test (pull_request) Successful in 30s
CI / Docker build (pull_request) Successful in 24s
CI / Test (Node 22) (pull_request) Successful in 3m4s
2026-11-15 23:02:33 +00:00
Compare
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/packetforge!1552
No description provided.