Cisco Blogs

5 Questions about the Nexus 1010

July 30, 2011 - 2 Comments

Here are a few questions we regularly see about the Nexus 1010.

Why do I need a Nexus 1010?

There are many advantages to running a dedicated piece of hardware for your 1000v implementations. A few that jump off the page are:

  • Dedicated hardware which includes lights out and out of band management.
  • Offloading of up to 4 VSMs (Virtual Service Blades) and 1 NAM (Network Analysis Module) for increased scalability. Each VSM can manage 64 Virtual Ethernet Modules (VEMs)
  • HA at both the software layer and hardware layer incorporating virtual service blade, chassis level and network level redundancy.

Is it more difficult to setup a Nexus 1010 and deploy the 1000v?

Actually, the Nexus 1010 requires a fewer number of steps for 1000v deployment. The whole process is basically 4 steps.

  • Create Virtual Service Module (VSM) as a Virtual Service Blade (VSB) on the 1010
  • Register the certificate as plug-in for vCenter
  • Define your ethernet and vethernet port-profiles 
  • Install VEM using vCenter

What’s the best way to access the CLI?

The Nexus 1010 is position just like any other switch and has the same access methods available. The typical options are telnet or a terminal server. The 1010 runs  NX-OS.

What is the best configuration for the control, packet, management and data information?

We get this one a lot. There are current 4 published deployment configurations.

  • Nexus 1010 uplink type 1: Ports 1 and 2 carry Management, Control and Data traffic. This option is best for simplistic 1000v only deployments.
  • Nexus 1010 uplink type 2: Ports 1 and 2 carry Management and Control; Ports 3-6 carry Data traffic. This option is recommended when a NAM deployment is being considered.
  • Nexus 1010 uplink type 3: Ports 1 and 2 carry Management; Ports 3-6 carry Control and Data traffic. Best for multiple VSM implementations requiring maximum bandwidth.
  • Nexus 1010 uplink type 4: Ports 1 and 2 carry Management; Ports 3 and 4 carry Control, Ports 5 and 6 carry Data traffic. Best for implementations that require traffic separation.

How hard is it to upgrade the Nexus 1010?

The process to upgrade the 1010 is not very different from a traditional switch. There are some additional steps to consider when using HA implementations.  Check the Nexus 1010 install and configuration guide for step by step procedures.

In an effort to keep conversations fresh, Cisco Blogs closes comments after 60 days. Please visit the Cisco Blogs hub page for the latest content.


  1. What are your thoughts on the pros and cons of a 1000v/1010 solution versus a VM-FEX/VIC solution? Unless there’s significant east-west traffic in the blade chassis, it seems to me that it makes more sense to pull all the switching out to an actual hardware switch instead of doing it in software… Which is Cisco’s position against Vyatta anyway, right?

    • Thanks for the comment. Here is my take on the positioning. The 1010/1000v is positioned differently than the VM-FEX solution. 1000v is targeted for customers with larger VM to server density where the environment may contain mixed vendor implementations at the server and 1st hop network junction. 1000v also offers additional features and allows Nexus 1010 integration. While VM-FEX aims to consolidate virtual and physical switch management points while increasing performance. VM-FEX also reduces trunked physical ports and provides server administrators a deployment option to ensure consistency. I cannot speak about Vyatta, since I am not familiar with their products.