used with NSO, it is recommended to use CDB as it has
been optimized for NSO and the transactional nature of
the solution.
With the Cisco NSO service manager, users develop
YANG models of the services they want deployed in the
network, such as IPTV or MPLS VPNs. At this stage, the
service model also has to be mapped to the
corresponding device configuration model. This is done
either through configuration templates that map service
parameters into device configuration parameters or
programmatically by building the mapping logic with
Java or Python code. The lifecycle of the services defined
in NSO is managed by a FASTMAP algorithm. As
services get created, modified, and deleted, FASTMAP
dynamically reacts and adjusts the configuration of the
devices in the network to reflect the status of the service
models. In addition, FASTMAP enables the following
functions:
Service dry-run: NSO calculates what the device changes would be if
the service model were to be pushed on the devices in the network.
Service check-sync: The service configuration is verified to be in
sync with the actual device configuration. Device configuration drift can
be detected this way.
Service re-deploy: Device configurations can be redeployed to
restore a service on the network.The NSO device manager manages the network devices
by using YANG data models and NETCONF. For devices
that natively implement NETCONF and YANG models,
the device manager is automatic; devices that do not
support NETCONF are integrated in the platform with
NEDs. NEDs that support different vendor CLIs as well
as SNMP configuration and hundreds of other
southbound management options come with Cisco NSO
by default. If needed, custom NEDs can be developed to
address any device management protocol that is not
already included with the default installation.
Distributed atomic transactions are used for all
configuration changes on all the devices in the network.