The state payload publishes bare MAC/ARP maps and no LLDP, while the console knows which entries are stale and why #1327
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#1327
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The runtime half of the state payload, after the config half (#1321, #1323, #1325). The console has printed
honest MAC, ARP and LLDP tables since #1253–#1255 — which port an entry was learned on, and whether that port can
still carry a frame — while the payload the browser reads published the raw maps:
So a switch with one live entry and one entry whose port was shut gave a client the same two strings, and the
neighbours the device has heard from were not in the payload at all. Measured on a CX 6000 with two hosts:
This is the Routes-table fault (#1300) in a different table: the fact is computed in the console, not in the engine,
so every other surface is left to restate it — or, as here, to not have it.
What must be true instead
Device.portCarrierNote()), fromifaceStatus()— the same rule thefront panel and the console already use for a port's state;
Device.macRows(topo)/arpRows(topo)/lldpRows(topo)return the rows as data: VLAN, MAC, port, note;address, MAC, port, honest age; neighbour, port, port ID, management address;
fullState()publishes them asruntime[d].mac,runtime[d].arpRows,runtime[d].lldp— arrays, empty ratherthan absent, so a client does not have to test for existence;
One consequence worth recording: a link state change flushes what was learned on that port (#1256), so
(down: link down)is unreachable in the MAC table — the entry is gone, not stale. The test says so, so nobodyrediscovers it.