Stuart Kendrick - 2016-09-13

I'm beginning to think that there is no generic way to identify ports in the err-disable state. Nor, more narrowly, any Cisco-specific way to identify err-disabled ports either.

Am I missing something, or is identifying err-disabled ports hard?

test-esx#sh int status | include err
Gi2/0/4 err-disabled 60 auto auto 10/100/1000BaseTX
Gi4/0/36 err-disabled 60 auto auto 10/100/1000BaseTX
test-esx#

guru> grep 10604 test-esx.walk
IF-MIB::ifDescr.10604 = STRING: GigabitEthernet2/0/4
[…]
IF-MIB::ifName.10604 = STRING: Gi2/0/4
[…]
IF-MIB::ifAdminStatus.10604 = INTEGER: up(1)
IF-MIB::ifOperStatus.10604 = INTEGER: down(2)
[…]
IF-MIB::ifStackStatus.0.10604 = INTEGER: active(1)
IF-MIB::ifStackStatus.10604.0 = INTEGER: active(1)
[…]
CISCO-VLAN-MEMBERSHIP-MIB::vmPortStatus.10604 = INTEGER: active(2)
[…]

Poking through MIB files … I guess I was hoping that ifAdminStatus would offer a “dynamically-down” status … but of course it does not:

ifAdminStatus OBJECT-TYPE
SYNTAX INTEGER {
up(1), -- ready to pass packets
down(2),
testing(3) -- in some test mode
}

I poked through CISCO-ERR-DISABLE-MIB and don’t see anything port-specific.

SwitchMap offers clues, notably the Speed of '10M' (plausible, but uncommon), plus the string "port is active, but no packets have been seen recently".

Gi2/0/4 60 Active 10M auto port is active, but no packets have been seen recently

Is this an unsolved problem?

--sk