I have worked with the Nexus 1000v product and wanted to share my thoughts on it. I want to explain in this blog what this product is and what it does. The Nexus 1000v can be virtual or a hardware appliance and is considered to be a virtual switch that runs in VMware. The major benefit to this product is the visibly you get when running in a virtual environment. Remember in the virtual environment the network engineer has a cloudy vision of what’s going, because the built-in switch within VMware does not get that technical it just works. This is fine for most people but not all, especially the network technicians we want that visibly and the Nexus 1000v does that and more!
The Nexus replaces the built-in switch in VMware and installs a virtual machine called the VSM (Virtual Supervisor Module) and depending on the configuration you can have two VSMs for redundancy. These VSMs can be either virtual or a hardware appliance (Nexus 1010) Depending on how many ESX hosts you have in your environment each of them will have VEM (Virtual Ethernet Module) which are the work horses and provide packet forwarding. The VSMs and VEMs make up a single Nexus 1000v switch, which appears to be a single modular switch to the network technician. Each VSM can have a maximum of 64 VEMs (or 64 physical ESX hosts)
It has always been that server administrators deal with the operating system and the applications running on that server. While the network administrators manage the switches and related policies. The link between the server and switch usually a cable separates these roles, until virtual came along and smashed these roles together usually the server administrator has to deal with it. With the Nexus 1000v these roles are now separate in the virtual environment with added functionality like PVLANs, receive rate limiting, QoS, Access Control Lists (ACLs), DHCP snooping, SPAN, ERSPAN, AAA, NetFlow, SNMP and many other features that are not available with the VMware vSwitch. Check out this marketing video that summarizes the Nexus 1000v.
I hope this information is helpful, check back in a couple of weeks or so because I want to go through the process of setting up the Nexus 1000v, understanding some basic terminology of the Nexus 1000v and go over the CLI. Anybody that is familiar with Cisco IOS CLI will find that the NX-OS is almost the same. 🙂
- Nexus 1000V Responding to Scale Requirements with 10,000+ Ports per Virtual Switch (blogs.cisco.com)
- Cisco Nexus ports stretched to take 40GE and 100GE loads (go.theregister.com)
- Nexus 1000V Updates Bring Scalability and Cloud Readiness to the Network (blogs.cisco.com)
- IBM launched a Nexus 1000V competitor (ioshints.info)