Do you have devices in your network which are not compliant with your network standards?
If the answer to this question is “yes” then you may have an easy solution through NSO (Network Service Orchestrator). Cisco CX team has developed an NSO-based package that can report and fix non-standard configuration on device(s) in your network.
What are the supported Platforms
This package uses built-in NSO compliance reporting feature and adds necessary enhancements. Currently out of the box, Cisco ASR-9001 platform has been validated. More platforms (including multivendor OS) can easily be validated by just defining golden templates for those platforms/vendors.
Open architecture: Generic platform to support reporting and resolving configuration issues. More device vendors can be easily added.
Extensible YANG model: Existing YANG model can be extended to support customizations.
Multiple templates support: Can generate reports for multiple golden templates.
Devices compliant support: Option is available to make device(s) compliant against given golden templates.
Bulk device(s) support: You can identify and fix golden configuration in bulk for same or different devices.
Watch the video where Imran Baig, Solution Architect, explains how this package works. Full source code of this package is available here.
I'm a new bee , while trying to integrate, was able to proceed till on boarding the device to NSO. Right now, got stuck at "sync" status with "unsupported"
Hi, i have some problems with a ZTE C300 OLT device.When i tried to sync the device, get stucked at loging: admin@ncs# devices device olt_zte_c300 sync-from
info Failed to connect to device olt_zte_c300: connection refused: Timeout after...
Hi:I installed nso-22.214.171.124 with nso-4.7.1-cisco-sae-core-fp-1.0.1 because I want to do a templace to configure ITD for nexus. Packages seem to be installed:
admin@ncs# show packages package oper-status packages package cisco-extension-frameworkoper-status...
I'm testing the NSO HA - BGP Anycast (L3) method, everything works as explained in the tailf_hcc.pdf except failover-master.
The SLAVE moves to MASTER, not to FAILOVERMASTER, and the failover-master templates is not applied to slave's quagga device...