Cisco Nexus 1000 v vswitch

In the challenge of virtual network switching, we discussed the role of virtual network switches in virtual networks. In this article, we will discuss the use of the Cisco Nexus 1000 v Distributed Virtual Switch and how it enables network administrators to play a greater role in virtual network management.

Although virtual network management tools are useful in monitoring, security, and management of virtual networks, they do not return control of virtual networks to network administrators. One way to solve this problem is to implement the Cisco Nexus 1000v Distributed Virtual Switch vSwitch ).

The Cisco Nexus v Distributed Virtual Switch returns the virtual network management on a VM to the network administrator and helps achieve peace between the server and the network team. In addition to solving management issues, it also adds a number of advanced features and virtual networks within the host to achieve better virtualization. VMware vSwitch does not have the same functions as Nexus 1000v, including QoS, Switch Port Analyzer (SPAN), Encapsulated Remote SPAN (ERSPAN) netFlow, RADIUS and TACACS, access control list, packet capture/analysis, DHCP/IGMPv3 Snoop, and so on.

How Nexus v Distributed Virtual Switch works

The Cisco Nexus 1000v Distributed Virtual Switch consists of two components: a Virtual Supervisor Module (VSM) and a Virtual Ethernet Module (VEM ). VSM manages one or more VEM as logical switches and supports up to 64 VEM. All of these VEM configurations are implemented using the VSM and the NX-OS command line interface, which sends the configuration to all VEM.

VSM uses the port template configured for each VEM and then appears in the vCenter Server as a port group. VSM is integrated into vCenter Server, so all network configurations related to VEM are synchronized between them. The VSM is packaged into a virtual device and deployed to an ESX or ESXi host using the vSphere Client. Once deployed and started, VSM can be managed through a command line interface. VEM is installed on each ESX and ESXi host, and one VEM can only exist on one host. VEM runs as part of the VMKernel and uses an API to interact with the vCenter Server and virtual machine. VEM obtains all its configuration information from the VSM, and if it is disconnected from the VSM, it will continue to exchange traffic based on the last configuration.

The Cisco Nexus 1000v distributed virtual switch can be used on any physical switch, regardless of the manufacturer. This allows anyone who uses non-Cisco physical network devices to manage virtual networks with v.

Cisco vswitches Virtualize Virtual Network Management

Cisco recently proposed a new VSM named Nexus 1010v, which is the physical version of The VSM virtual device. 1010 v is an enhanced version of 1000 v VSM. It can contain 4 VSM instances and can manage up to 256 VEM instances. 1010v is a new choice for those who are not satisfied with running VSM on ESX and ESXi hosts as virtual devices. In addition, it helps detach VSM resources from the host to a physical device.

Assign a network team for Virtual Network Management

The Cisco Nexus v Distributed Virtual Switch returns the virtual network management to the network administrator so that they have full control over the entire network environment. It also ends disputes between server administrators and network administrators when deploying virtualization. However, it is usually not enough to return the control of the virtual network to the network administrator. Many network administrators are accustomed to handling physical networks, while virtualization is a brand new field for them. They generally have doubts about virtualization and have resistance.

Training everyone in the virtualization project is the best way to solve this problem. Network Administrator training includes the following steps:

◆ Explain the concept of virtual switch and virtual NIC, as well as their interaction with physical switches and physical NICs.

◆ Demonstrate the installation and configuration of a vswitch, how to install a virtual NIC on a VM, and how to connect the virtual NIC to a virtual switch.

◆ Explains how ESX uses Trunk Network Ports and how 802.1Q VLAN labels work in a virtual network environment.

◆ Explains the principles of virtual network security and how vswitches are isolated to prevent traffic leakage.

◆ Demonstrates NIC combination and fault recovery in a vswitch.