The following resources are required for a standalone Cisco Enterprise NFVIS:

• Atleast one CPU core

• 2 GB RAM

• 20 GB storage

Note	More memory and disk space are required to be added to the system, depending on VM deployments.

The Cisco Enterprise NFVIS upgrade image is available as a .nfvispkg file. Currently, downgrade is not supported.

For more details on the software upgrade, see the Upgrading Cisco Enterprise NFVIS section in the Cisco Enterprise Network Function Virtualization Infrastructure Software Configuration Guide.

Note	NFVIS 3.6.2 supports upgrade from NFVIS 3.5.1-FC4, NFVIS3.5.2-FC2, or NFVIS 3.6.1-FC3 to NFVIS 3.6.2-FC3.

The following are the only supported programs and platforms for Cisco ENFV and any other program or platform will not be supported.

Supported Platforms and Firmware

The following table table lists only the supported platforms and firmware for Cisco ENFV

Note	The listed platforms will be installed with HUU 3.1.4 and CIMC 3.1 (4.20170327095406).

Platform	Firmware	Version
ENCS 5406, ENCS 5408, and ENCS 5412	BIOS	1.2
	CIMC	3.1(4.20170327095406)
	HUU	3.1.4
	WAN Port Driver	1.63, 0x80000e2f
	LAN Port Driver	5.04 0x800027d4 1.1256.0
	FPGA	1.5
UCS-E160S-M3/K9	BIOS	UCSEM3_1.0 (Build Date: 05/27/2016)
	CIMC	3.1 (4.20170327095406)
	HUU	3.1.4
UCS-E140S-M2/K9	BIOS	UCSES.1.5.0.5 (Build Date: 02/03/2016)
	CIMC	3.1 (4.20170327095406)
	HUU	3.1.4
UCS-E160D-M2/K9	BIOS	UCSED.2.5.0.3 (Build Date: 04/10/2015)
	CIMC	3.1 (4.20170327095406)
	HUU	3.1.4
UCS-E180D-M2/K9	BIOS	UCSED.2.5.0.3 (Build Date: 04/10/2015)
	CIMC	3.1 (4.20170327095406)
	HUU	3.1.4
UCS-C220-M4	BIOS	UCSED.2.5.0.3 (Build Date: 04/10/2015)
	CIMC	3.1 (4.20170327095406)
	HUU	3.1.4

• Cisco Enterprise NFV Portal—A graphical interface that helps you configure almost all features.

• Cisco Network Plug-n-Play Support—A unified approach to provision enterprise networks comprised of Cisco routers, switches, and wireless devices with a near zero touch deployment experience.

• Managing VM Operations—Start, stop, and restart VMs as required using the Cisco Enterprise NFV Portal or REST or NETCONF APIs.

• VM Lifecycle Management—You can register VMs, deploy VMs, and create multiple flavors of a VM using APIs or the Cisco Enterprise NFVIS Portal.

• VM Network Management and Monitoring

• VM OVA Packaging—Supports deployment of VMs through uploading of OVA packages for Cisco supplied VMs, third party VMs, and for supported Windows and Linux operating systems. OVA packages must be created according to the Cisco Enterprise NFVIS packaging specification. For detailed information, see the following Cisco document:

  http://www.cisco.com/c/en/us/td/docs/routers/nfvis/user_guide/nfvis-config-guide/nfvis-user-guide_chapter_0110.html

• Service Chaining of VMs—A set of network services in the form of VMs connecting virtual networks. Cisco Enterprise NFVIS supports service chaining of two or more VMs by connecting two or more virtual networks where the VM is running in L2 bridge mode. Service chaining is also implemented by one VM configured to perform packet diversion to another VM.

• Self-signed and Third Party Certificates—You can use the default self-signed certificate or generate CM certificates.

• Single WAN IP Deployment—A single WAN IP deployment can be considered when the Cisco ENCS is preconfigured at the corporate main office with the service provider's WAN IP address, and shipped to the branch office for quick deployment.

• Switched Port Analyzer (SPAN) Session—This feature helps you analyze network traffic passing through interfaces or VLANs by using SPAN sessions.

• vBranch High Availability—This solution uses the Hot Standby Router Protocol (HSRP), a default gateway redundancy, which allows the network to recover from the failure of the device acting as the default gateway for the LAN side end points.

• Resetting Factory Default

• Event Notifications—Cisco Enterprise NFVIS generates event notifications for key events. A NETCONF client can subscribe to these notifications for monitoring the progress of configuration activation and the status change of the system and VMs.

• Packet Capture Support—This feature helps to capture all packets being transmitted and received over physical and virtual network interface controllers (physical port and vNIC) for analysis.

• The Cisco Enterprise NFVIS portal cannot be used to configure the switch firmware version running on the Cisco 5400 ENCS. The Cisco ENCS switch can be configured using the switch CLIs or APIs.

• The current switch firmware version in Cisco Enterprise NFVIS 3.5.1 running on the Cisco 5400 ENCS requires to run the commit command for each switch CLI to avoid configuration inconsistency between the host and the switch device.

  
  nfvis# config terminal
  Entering configuration mode terminal
  nfvis(config)# switch
  nfvis(config-switch)# vlan 100
  nfvis(config-switch-vlan)# commit
  Commit complete.
  nfvis(config-switch-vlan)# exit
  nfvis(config-switch)# interface vlan 100
  nfvis(config-switch-if)# ip address 192.168.1.1 255.255.255.0
  nfvis(config-switch-if)# commit
  Commit complete.
  nfvis(config-switch-if)# end
  

The open and resolved bugs for a release are accessible through the Cisco Bug Search Tool. This web-based tool provides you with access to the Cisco bug tracking system, which maintains information about bugs and vulnerabilities in this product and other Cisco hardware and software products. Within the Cisco Bug Search Tool, each bug is given a unique identifier (ID) with a pattern of CSCxxNNNNN, where x is any letter (a-z) and N is any number (0-9). The bug IDs are frequently referenced in Cisco documentation, such as Security Advisories, Field Notices and other Cisco support documents. Technical Assistance Center (TAC) engineers or other Cisco staff can also provide you with the ID for a specific bug. The Cisco Bug Search Tool enables you to filter the bugs so that you only see those in which you are interested.

In addition to being able to search for a specific bug ID, or for all bugs in a product and release, you can filter the open and/or resolved bugs by one or more of the following criteria:

• Last modified date

• Status, such as fixed (resolved) or open

• Severity

• Support cases

You can save searches that you perform frequently. You can also bookmark the URL for a search and email the URL for those search results.