The canvas and inspector still call an unplugged port healthy #1238
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#1238
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?
What happens
#1237 made
show ip interface briefandshow interfacesreport whether a port can carry a frame, withthe reason. The web UI still reports only "shut down or not", in three places:
web/canvas.js:379· administratively downwheniface.enabled === falseweb/faceplate.js:477administratively downwhen downweb/app.js:1586(administratively down)wheniface.enabled === falseSo an unplugged port on the canvas — the one you are looking at when a link will not come up — is
described as healthy, exactly as the CLI used to.
Expected
The same three answers the CLI now gives, with the reason stated:
administratively down— shut here;down (no cable)— no link on this port;down (peer shut down)— cabled, but the far port is shut;up.A cable being present is something the canvas already knows: it draws the links. The port model needs the
same up/down answer the engine's
Device.ifaceStatus()gives, and the two must agree — the same disciplineas
test/fabric-agreement.test.js, which exists because a second implementation of a rule is a secondchance to disagree.
Scope
Presentation only; nothing about which ports carry frames changes. Needs tests over the canvas's own link
model (it has no
Topology), including the faceplate and the inspector footer.