Why does Spectrum use the Writenet from the OLD-Cisco-SYS-Mib in NCM when the device supports the Cisco-Config-Copy-Mib?
Article ID: 217372
Updated On:
Products
Issue/Introduction
We have recently had a request to capture and store the configs for Cisco SF220 switches. Reading the Cisco documentation for these switches it states that they do support the Cisco-Config-Copy-Mib.
However when Spectrum attempts to capture the config for one of these it attempts to write to 1.3.6.1.4.1.9.2.1.55 (writeNet), which is the OLD-Cisco-SYS-MIB, and the capture fails.
Is there any reason config capture will not work for the SF220 and is there a way to change the behavior for these switches to use the Cisco-Config-Copy-Mib instead of the OLD-Cisco-SYS-MIB?
Environment
Release : 20.2.x, 10.x
Component : Spectrum APP / NCM
Cause
Cisco devices that are not certified in Spectrum will use the 1.3.6.1.4.1.9.2.1.55 (writeNet) if the firmware is below version 12. There is currently no option to change this.
Resolution
When Spectrum checks the firmware version for Cisco devices if the firmware revision is less then 12, then NCM will automatically default to using the older Writenet (OLD-Cisco-SYS-MIB) instead of the current capture Cisco-Config-Copy-Mib. This is by Spectrum NCM design,
If the device is able to use SSH, then we can either use OpenSSH device family or the NCM SSH Self Certification tool.
The only other option is to have the device officially certified in Spectrum
Additional Information
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/spectrum/10-4-2/managing-network/network-configuration-manager/network-configuration-manager-configurations/network-configuration-manager-extension-utility.html
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/spectrum/10-4-2/managing-network/network-configuration-manager/network-configuration-manager-self-certification.html
Feedback
