Enterprise branch offices today have a device per function - router, firewall, wan acceleration, etc. To add another function, add another device. This is expensive to buy, and expensive to operate. It may require several truck rolls, as devices are added to provide new functions, and as devices reach end of life, and need to be replaced. This also impedes managed services providers. This can be made a lot simpler and cheaper by virtualising the branch. This reduces the number of physical devices to ship, install, operate, and maintain to one (plus redundancy)
However, virtualising the branch introduces different complexity. You still need to ship the CPE that will host your virtual network functions, and provide management/monitoring for this device. You want to avoid even that initial truck roll, so ideally the CPE is deployed with Plug-and-Play. Then you need to spin up the virtual network functions (VNF) for your router, firewall, wan acceleration, etc. Each VNF needs to be given a startup (day-0) configuration, with certain site-specific parameters, and licenses need to be applied. The VNFs need to be connected together in the correct topology, in a so-called service chain.
This calls for automation. The Cisco Network Services Orchestrator (NSO) with the vBranch Core Function Pack (CFP) bundle provides the functionality to
automatically deploy ENFV CPE devices with Plug-and-Play
define the VNFs and service chains for each CPE device
provide day-0 configuration and licenses for each VNF
support Cisco as well as 3rd party VNFs
Then, optionally, you can also use NSO for service lifecycle management, managing any additional configuration. This has the benefit of making sure that in the case of VNF recovery, that the VNF comes back up not only with the day-0 configuration, but also recovers any additional service configuration.
NSO with vBranch CFP is available as part of Cisco Virtual Managed Services (VMS) for Managed Services Providers. This provides a complete management solution. NSO and vBranch CFP are also available by themselves for more customised deployments.
I'm looking to implement the reactive fastmap pattern by having a vpn service request a vpn id. I understand the high level concept of writing and reading operational data and having a CDB subscriber to re-deploy the service once the id has been allocated...
Hello, I've created with ncs-netsim 2 devices by following the next steps: 1. ncs-netsim add-to-network ./packages/cisco-iosxr-cli-7.21/ 2 ASR_lf2. ncs-netsim start ASR_lf03. ncs-netsim start ASR_lf14. ncs-netsim ...
We're in the process of renaming a number of devices across our network. When renaming the devices in NSO this seems to present challenges for any services that are already deployed on them. I'm opening this thread to explore gather opinions and suggestio...
I have a python service that is called through RESTCONF, and ran into an issue where the service was failing to create certain instances, but did not log any details of the failure in the service python vm log. When I re-created the issue through the NCS ...
I am compiling the resource-manager in python3 and I am getting a python syntax issue
Traceback (most recent call last):
File "/Users/kkotari/nso-188.8.131.52/lib/pyang/bin/pyang", line 411, in <module>