show ip interface brief reports up/up on a port with no cable #1237
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge#1237
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
show ip interface briefreports up / up for a port with no cable. This is the first table anyonecopies 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
Gi0is cabled to the other router andGi0/0/0is not:Gi0/0/0haspeer: null— there is no cable, no peer port, nothing that could carry a frame. Thesimulator will not move a packet across it. The table says up/up.
Worse,
show interfacescontradicts itself two lines apart:status: upandpeer: disconnectedcannot 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 briefsays everything is up" is a dead end — the operator goes looking for a routingor 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
R1 Gi0toR2 Gi0. LeaveR1 Gi0/0/0unconnected.show ip interface briefon R1.Expected
Status reflects whether the port can actually pass a frame:
shutdown)peeris null)show interfacesshould name the reason —down (no cable),down (peer shut down)— instead ofprinting
status: upbesidepeer: 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.