show ip interface brief reports up/up on a port with no cable #1237

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

What happens

show ip interface brief reports up / up for a port with no cable. This is the first table anyone
copies into a bug report when a link will not come up, and it is the one table that never says the link
is missing.

Measured on a two-router lab, where Gi0 is cabled to the other router and Gi0/0/0 is not:

Interface              IP-Address      OK? Method Status                Protocol
Gi0                   10.0.0.1/24     YES  manual  up                    up
Gi0/0/0               10.0.1.1/24     YES  manual  up                    up
Gi0/0/1               unassigned      YES  manual  up                    up

Gi0/0/0 has peer: null — there is no cable, no peer port, nothing that could carry a frame. The
simulator will not move a packet across it. The table says up/up.

Worse, show interfaces contradicts itself two lines apart:

Gi0/0/0 (ethernet, 1G), MAC 02:00:00:00:00:01
  status: up
  ip: 10.0.1.1/24
  peer: disconnected

status: up and peer: disconnected cannot both describe a working interface.

Why it matters

An interface status is the single most-used diagnostic in the tool. "My ping doesn't work, and
show ip interface brief says everything is up" is a dead end — the operator goes looking for a routing
or firewall problem that does not exist, because the actual fault (an unmade connection, or a port shut
at the far end) is invisible in the output.

Steps to reproduce

  1. Build a lab with two routers.
  2. Cable R1 Gi0 to R2 Gi0. Leave R1 Gi0/0/0 unconnected.
  3. show ip interface brief on R1.

Expected

Status reflects whether the port can actually pass a frame:

Condition Status Protocol
shut down here (shutdown) administratively down down
no cable (peer is null) down down
the cable exists but the far port is shut down down down
otherwise up up

show interfaces should name the reason — down (no cable), down (peer shut down) — instead of
printing status: up beside peer: disconnected.

Scope

Status reporting only. Which ports can carry a frame does not change. A device that is not part of a
topology has no cables to report on, so its ports keep their current status: the command cannot know
about a cable it was never told about.

## What happens `show ip interface brief` reports **up / up** for a port with no cable. This is the first table anyone copies into a bug report when a link will not come up, and it is the one table that never says the link is missing. Measured on a two-router lab, where `Gi0` is cabled to the other router and `Gi0/0/0` is not: ``` Interface IP-Address OK? Method Status Protocol Gi0 10.0.0.1/24 YES manual up up Gi0/0/0 10.0.1.1/24 YES manual up up Gi0/0/1 unassigned YES manual up up ``` `Gi0/0/0` has `peer: null` — there is no cable, no peer port, nothing that could carry a frame. The simulator will not move a packet across it. The table says up/up. Worse, `show interfaces` contradicts itself two lines apart: ``` Gi0/0/0 (ethernet, 1G), MAC 02:00:00:00:00:01 status: up ip: 10.0.1.1/24 peer: disconnected ``` `status: up` and `peer: disconnected` cannot both describe a working interface. ## Why it matters An interface status is the single most-used diagnostic in the tool. "My ping doesn't work, and `show ip interface brief` says everything is up" is a dead end — the operator goes looking for a routing or firewall problem that does not exist, because the actual fault (an unmade connection, or a port shut at the far end) is invisible in the output. ## Steps to reproduce 1. Build a lab with two routers. 2. Cable `R1 Gi0` to `R2 Gi0`. Leave `R1 Gi0/0/0` unconnected. 3. `show ip interface brief` on R1. ## Expected Status reflects whether the port can actually pass a frame: | Condition | Status | Protocol | |---|---|---| | shut down here (`shutdown`) | administratively down | down | | no cable (`peer` is null) | down | down | | the cable exists but the far port is shut down | down | down | | otherwise | up | up | `show interfaces` should name the reason — `down (no cable)`, `down (peer shut down)` — instead of printing `status: up` beside `peer: disconnected`. ## Scope Status reporting only. Which ports can carry a frame does not change. A device that is not part of a topology has no cables to report on, so its ports keep their current status: the command cannot know about a cable it was never told about.
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#1237
No description provided.