Smarts NCM: Auto Discovery job for WS-C2960X-48LPS-L is failing; WARN:Pull of running failed; Unable to pull config file: running

Products

• VMware Smart Assurance

Issue/Introduction

Symptoms:


Auto discovery job for the model WS-C2960X-48LPS-L fails with the following error in GUI-

[running] Action failed...
Pulling configuration file 'running' for IDX 15724 with mechanism SNMP/TFTP and SNMPV2 ERR:Timeout setting snmpv2c:syntax(4):timeoutms(300000):retry(0):.1.3.6.1.4.1.9.2.1.55.170.252.17.198
WARN:Pull of running failed
Unable to pull config file: running
Configuration file 'running' for IDX 15724 failed with error code 'Unspecified Error' in 305 seconds [startup] Action failed...
Pulling configuration file 'startup' for IDX 15724 with mechanism SNMP/TFTP and SNMPV2 Device does not support CISCO-CONFIG-COPY-MIB; trying OLD-CISCO-SYSTEM-MIB ERR:Only running config pulls are supported WARN:Pull of startup failed Unable to pull config file: startup Configuration file 'startup' for IDX 15724 failed with error code 'Unspecified Error' in 4 seconds

It displays the following error in autodisc.log as well-

Unable to determine Oid for model 'WS-C2960X-48LPS-L'

Environment

VMware Smart Assurance - NCM

Cause

Even though Cisco catalyst stack C2960 series is documented to be supported, the specific model WS-C2960X-48LPS-L is not supported as per the latest DSR (22) Support Matrix. None of the C2960X series are documented to be certified in the released DSR Support Matrix's.

Resolution

The model WS-C2960X-48LPS-L can be discovered in NCM successfully after adding the entry separately in Cisco.models file along with it's associated system OID. 

Please follow the below steps to add the entry for WS-C2960X-48LPS-L in Cisco.models file in custompackage directory-

- Ensure you do not make any changes to the package Directory ($VOYENCE_HOME/package), or to any of the package directory contents.

- Copy the file to be modified from the directory structure under the package directory, to the directory structure under the custompackage directory. Create the directories under custompackage directory if they don t exist already.

cp $VOYENCE_HOME/package/cisco/Cisco.models $VOYENCE_HOME/custompackage/cisco/Cisco.models

- Open Cisco.models in custompackage directory and add the following device entry at the end of file and save it.

WS-C2960X-48LPS-L;         1.1208;      2

- Run mkmodelsxml.pl from $VOYENCE_HOME/custompackage/cisco/
/<VOYENCE_HOME>/tools/mkmodelsxml.pl < Cisco.models > CiscoModels.xml

- Copy/move the file CiscoModels.xml to $VOYENCE_HOME/custompackage/pkgxml/Cisco/

- Do a service voyence restart

- After that remove the devices and discover them.

NOTE: Permanent solution to the stated problem would be to raise a TASC request for the model WS-C2960X-48LPS-L separately. 

Additional Information

If the device with model WS-C2960X-48LPS-L does not get discovered after implementing the steps detailed in "Resolution", it might be because the model WS-C2960X-48LPS-L is also associated with the system OID 1.3.6.1.4.1.9.1.1696 as per the below Cisco site-

https://supportforums.cisco.com/discussion/11996561/cisco-catalyst-2960-x-and-cisco-prime-compatibility

As per Cisco guidelines, the exact system OID that the model WS-C2960X-48LPS-L associates with is not yet confirmed and is considered as a bug. Stated details about the bug can be verified in the below site-

https://quickview.cloudapps.cisco.com/quickview/bug/CSCup82940

Hence if the model WS-C2960X-48LPS-L is not discovered using the system OID 1.3.6.1.4.1.9.1.1208, then please use 1.1696 instead in the steps detailed in Resolution section.