runtime[].counters has two shapes (drops/ports missing on idle devices) and hands out the engine's live record #1329
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#1329
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 last block of the state payload built by hand on the way out:
Two faults in one line, measured on a CX 6000 with two hosts after a ping:
drops(withbyReasonandunported) andports; thefallback had neither. So in the same payload, the device that had done something carried its drop reasons and the
idle device carried
undefined— a client summing drops across a lab read NaN on exactly the devices most likelyto be quiet, and nothing distinguished "no drops" from "not counted".
family after #1323 (link endpoints) and #1325 (layout).
What must be true instead
bytesIn/Out,packetsIn/Out,flowsOpened/Refused,drops {total, byReason, unported},ports { port -> {packetsIn/Out, bytesIn/Out, transport*, drops} }, andcounted;countedseparates "nothing has ever crossed this device" from a zero it measured;Two distinctions the payload cannot express but a reader needs, so they belong in the docs: the device totals count
transport payload while the port tallies count every frame (a switch that only forwards has port tallies and
zero device packets), and a link state change flushes learned entries (#1256).