About Cisco NFV SD-Branch Support in Cisco vManage
Note |
The documentation set for this product strives to use bias-free language. For purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on standards documentation, or language that is used by a referenced third-party product. |
Cisco Network Function Virtualization Software-Defined Branch (NFV SD-Branch) features in Cisco vManage are a collection of capabilities that allow you to use Cisco vManage as a single centralized orchestrator to manage both the Cisco NFV hardware platforms powered by Cisco NFVIS hypervisor software, and the virtualized network function (VNF) based network services that run as guest virtual machines (VMs). SD-Branch in Cisco vManage provides a three-step user experience of design, deploy and monitor that enables you to deploy networking services efficiently across all sites within your enterprise network infrastructure.
The Cisco vManage portal supports:
- Design - A network architect can graphically create a parameterized network design template that captures the enterprise networking standards and best practices including WAN circuits and VNF service chains.
- Deploy - A network operator can use the pre-defined network design templates to deploy and configure network devices and services in multiple locations in an automated and secure manner without making any design decisions.
- Monitor - A network auditor can monitor and manage both the hardware platforms and the virtualized network services VMs that are running on them, without the fear of making accidental configuration changes.
Note |
Cisco NFV SD-Branch features in Cisco vManage are only supported for greenfield deployments of the ENCS 5400 Series and the C8200-uCPE platforms. |
Resolved and Open Bugs
About the Cisco Bug Search Tool
Use the Cisco Bug Search Tool to access open and resolved bugs for a release.
The tool allows you to search for a specific bug ID, or for all bugs specific to a product and a release.
You can filter the search results by last modified date, bug status (open, resolved), severity, rating, and support cases.
Resolved Bugs for NFVIS SD-Branch Release 4.7.1
Bug ID |
Description |
---|---|
Device template push fail after ISRv comes up and online |
|
vBranch: VM stuck at REBOOTING/STOPPING after VNF restart/stop (when "ip host" in add-on CLI) |
|
Unexpected redirect to previous provisioned branch variable page on saving |
Open Bugs for NFVIS SD-Branch Release 4.7.1
Bug ID |
Description |
---|---|
vBranch Single IP: VM is shut after upgrade/reload VM. For upgrade, VM rollback after start manually |
|
ENCS loss control connection after push ND template to device with "dns-server" command |
|
NFVIS 4.6/vManage-20.6.1 vBranch - Need to push config twice as vnf install did not begun on its own |
|
vBranch: NFVIS does not roll back configuration when control connection loss after template push |
|
After deploy Topo5 C8Kv in shut state with Error: Crypto device is not available for this deployment |
|
Device is online. Failed to attach configuration template : internal error. |
|
OIB DayN: "Manage Network Design" button is disabled when add service. Need wait for task completed |
|
ND template attach Failed to load config for tenant0 |
|
ENCS GE0-0/GE0-1 showing up as either Fibre or TP when no cables connected |
|
vBranch: NFVIS upgrade shows "Failed to establish netconf session with device" in vManage Task Log |
|
vBranch: After provision, vEdge/ISRv Out of Sync - Failed to Sync-from Failed to connect to device |
|
vBranch: NFVIS upgrade shows "Failed to establish netconf session with device" in vManage Task Log |
Important Notes
-
In NFVIS Release 4.7.1 and vManage Release 20.7.1, the image download behavior is enhanced. Image download is part of the image configuration, and the download is a part of the service attach. Image download also supports caching and download retry. As part of the enhancement, the status of the image download and the registration can only be viewed by using the show vm_lifecycle update images command.
Software Upgrade
Note |
NFVIS 4.1.1 release or later on ENCS 5400 devices are supported on Cisco SD-Branch solution. |
For more details on the NFVIS software upgrade, see Upgrade Cisco NFVIS.
For more details on Cisco vManage software upgrade, see Cisco vManage Software Upgrade.
System Requirements
The following resources are required for a standalone Cisco Enterprise NFVIS:
-
For a system that has 16 or less CPU cores, one CPU core is reserved for NFVIS. For a system that has more than 16 CPU cores, 2 CPU cores are reserved for NFVIS.
-
20 GB storage
Note |
More memory and disk space are required to be added to the system, depending on VM deployments. |
Supported Programs and Platforms
Supported Platforms and Firmware
The following table lists the only supported platforms and firmware for Cisco ENFV
Platform |
Firmware |
Version |
---|---|---|
ENCS 5406, ENCS 5408, and ENCS 5412 |
BIOS |
ENCS54_3.04 |
CIMC |
3.2.(13.8) |
|
WAN Port Driver |
5.4.0-5-k CISCO |
|
LAN Port Driver |
1.4.22.7-11-ciscocsx |
|
C8200-UCPE-1N8 |
BIOS |
C8200-UCPE_1.04 |
Aikido FPGA |
0x6F |
|
Logic FPGA |
4.6.0 |
|
MCU |
240.52 |
Guest VNFs
For the list of supported VNFs that can be orchestrated through Cisco vManage, see the Guest VNFs section of NFVIS 4.7.1 Release Notes.