The canvas and inspector still call an unplugged port healthy #1238

Closed
opened 2026-11-09 17:11:16 +00:00 by jaylouisw · 0 comments
Owner

What happens

#1237 made show ip interface brief and show interfaces report whether a port can carry a frame, with
the reason. The web UI still reports only "shut down or not", in three places:

Site What it says today
web/canvas.js:379 tooltip: status + · administratively down when iface.enabled === false
web/faceplate.js:477 port title: pushes administratively down when down
web/app.js:1586 inspector footer: (administratively down) when iface.enabled === false

So 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 discipline
as test/fabric-agreement.test.js, which exists because a second implementation of a rule is a second
chance 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.

## What happens #1237 made `show ip interface brief` and `show interfaces` report whether a port can carry a frame, with the reason. The web UI still reports only "shut down or not", in three places: | Site | What it says today | |---|---| | `web/canvas.js:379` | tooltip: status + `· administratively down` when `iface.enabled === false` | | `web/faceplate.js:477` | port title: pushes `administratively down` when down | | `web/app.js:1586` | inspector footer: `(administratively down)` when `iface.enabled === false` | So 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 discipline as `test/fabric-agreement.test.js`, which exists because a second implementation of a rule is a second chance 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.
Sign in to join this conversation.
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#1238
No description provided.