Interfaces display as Testing and Unknown

Document ID : KB000111993
Last Modified Date : 23/08/2018
Show Technical Document Details
Issue:
When we discover Cisco 38XX switches in Spectrum, the VLAN interfaces have a Status of testing and a OperStatus of UNKNOWN on the device interface tab. The L3 interfaces for the VLANs are showing correctly but the L2 vlans all show as testing/unknown. Why do these interfaces show as testing/unknown?
Resolution:
The way Spectrum and Performance Management determine these sort of status indicators is via the below two OIDs.  If the interfaces are not supposed to be showing as Testing & Unknown then you need to look into why the device is reporting the interfaces as such.
 
ifAdminStatus 1.3.6.1.2.1.2.2.1.7 OBJECT-TYPE
    SYNTAX INTEGER {
        up(1),
        down(2),
        testing(3)
        }
    ACCESS read-write
    STATUS mandatory
    DESCRIPTION
        "The desired state of the interface.  The testing(3) state
        indicates that no operational packets can be passed.  When a
        managed system initializes, all interfaces start with
        ifAdminStatus in the down(2) state.  As a result of either
        explicit management action or per configuration information
        retained by the managed system, ifAdminStatus is then
        changed to either the up(1) or testing(3) states (or remains
        in the down(2) state)."
    ::= { ifEntry 7 }
 
ifOperStatus 1.3.6.1.2.1.2.2.1.8 OBJECT-TYPE
    SYNTAX INTEGER {
        up(1),
        down(2),
        testing(3),
        unknown(4),
        dormant(5),
        notPresent(6),
        lowerLayerDown(7)
        }
    ACCESS read-only
    STATUS mandatory
    DESCRIPTION
        "The current operational state of the interface.  The
        testing(3) state indicates that no operational packets can
        be passed.  If ifAdminStatus is down(2) then ifOperStatus
        should be down(2).  If ifAdminStatus is changed to up(1)
        then ifOperStatus should change to up(1) if the interface is
        ready to transmit and receive network traffic; it should
        change to dormant(5) if the interface is waiting for
        external actions (such as a serial line waiting for an
        incoming connection); it should remain in the down(2) state
        if and only if there is a fault that prevents it from going
        to the up(1) state; it should remain in the notPresent(6)
        state if the interface has missing (typically, hardware)
        components."
    ::= { ifEntry 8 }