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. |
What's New
Feature |
Description |
Where Documented |
---|---|---|
Graphical Topology View |
Visual Representation of vBranch services or networks for the listed templates. |
|
Network Design Switch Configurations |
You can set additional LAN interface details to your device profile. |
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.
Open Bugs for NFVIS SD-Branch Release 4.4.1
Caveat ID Number |
Description |
---|---|
vBranch: Unable to delete circuits after deleting device profile |
|
Cannot enable DPDK when configuring on 1st push alongwith VM deployment from vManage |
|
ENCS with 16G mem : VM fail to come up remain shut when 4.2.1 to 4.4.1 upgrade |
|
vManage DNS setting may cause control connection down issue when use hostname/FQDN for vBond |
|
vManage show NFVIS upgrade success (4.2.1-FC3 to 4.4.1-64) before CIMC and BIOS upgrade |
|
PnP Cloud Connect: C8000V Software Devices stay in "Pending for publish" and end up in Error state |
|
OIB: without change any ND global parameters, vManage automatically push template to all sites again |
|
vManage config preview shows switch configuration for Tabei platform |
|
ZTP vBranch Solution: Tabei PIM LTE fail on PnP redirect when wan-br/wan2-br get DHCP IP and gateway |
|
Fail to delete C8000V and CSRNG PID devices in PnP Cloud Virtual Account |
|
Upgrade 20.3->20.4, ND Profile->LAN page does not show global vlan, spanning-tree and native-vlan |
|
VNF Install fail when use "Remote Server - vManage" for uploading VNF package |
|
PnP redirect fail due to PnP Server Error 3101 and message: Internal Error when vbond config changed |
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 vManage software upgrade, see 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_2.11 |
CIMC |
3.2(10.4) |
|
WAN Port Driver |
1.4.22.7-10-ciscocsx |
|
LAN Port Driver |
5.4.0-3-k CISCO |
Guest VNFs
For the supported VNFs that can be orchestrated through Cisco vManage, see the Guest VNFs section of NFVIS 4.4.x Release Notes.