- About this Document
-
- About Cisco Enterprise NFVIS
- Installing Cisco Enterprise NFVIS Using the KVM Console
- Setting Up System Configuration
- Cisco Network Plug-n-Play Support
- VM Life Cycle Management
- VM Deployment Scenarios
- SPAN Session or Port Mirroring
- Configuring Packet Capture
- VM Image Packaging
- Upgrading Cisco Enterprise NFVIS
- Configuring vBranch High Availability
- Cisco ENCS Single WAN IP Deployment Scenarios
- Resetting to Factory Default
- Event Notifications
- Syslog Support
- SNMP Support on NFVIS
- About RADIUS
- ENCS Switch Portal Configuration
- Configuring Secondary IP and Source Interface
- Ports and Port Channels
- MSTP for ENCS 5400 8-Port Switch
- ENCS 5400 Switch LLDP
- Secure Overlay and Single IP Configuration
- Dual WAN Support
- Switch Port Security
SRIOV Support
Beginning with 3.9.1 release, NFVIS supports single root Input/Output virtualization (SR-IOV) for Colo mode in CloudDock solution. Colo is a stack of compute and networking fabric to bring up multiple networking functions and service chain them to connect branch users to hybrid cloud or data center.
SR-IOV is statically enabled on NFVIS Colo image with a CSP 2100 Product Identifier (PID). When enabling SR-IOV virtual functions on a physical network interface card (pNIC), the following rules are applicable:
-
SR-IOV is enabled only on Niantic NICs and onboard Niantics does not support SR-IOV.
-
Each pNIC allows 32 virtual functions. If the NIC is connected to 1G, two virtual functions are created.
-
ifconfig eth0 allmulti command is enabled so that the specified interface receives all multicast packets on the network.
-
Virtual Ethernet Port Aggregator (VEPA) mode is enabled.
-
The naming convention is: <interface name>-SRIOV-1,<interface name>-SRIOV-2 ,<interface name>-SRIOV-3,<interface name>-SRIOV-4
VLAN's segregate traffic within a network. VLANs keep traffic from different networks separated when traversing shared links and devices within a topology. This process is known as VLAN tagging.
Vlan tagging Rules for SR-IOV are:
-
Access mode can have upto one VLAN. If it does not have a VLAN, a VLAN tag is assigned. The default is VLAN tag 1.
-
In trunk mode VLAN tags are not allowed.
-
The VLAN tags assigned to a network are distrubuted to the virtual functions only when a VM is deployed using the VLAN tagged SR-IOV network.