Jun 212012
 

When following the Cisco Cheat sheet for deploying the Nexus 1000v for deploying the Nexus 1000v in L3 mode, make sure one of the first commands you run (or when applying your config) is ‘feature LACP’ without it you cannot activate your LACP port channel.

image

I set up something similar to the above, the port-channel is between the server ports and the 5k (2ks acting as fabric extenders) and setup to load balance using LACP. This is design was only recently supported by Cisco as previously you would have had to load balance traffic on the port channel via MAC-Pinning.

This annoying little oversight caused me an hour of grief on a customer site as the port-channel on the 5k and 1k would not become active until this feature was enabled.

To enable this feature:

n1000v# config t

n1000v(config)# feature lacp

http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_4/command/reference/n1000v_cmds_f.html#wp1404742

Post to Twitter

Sep 152011
 

Using Hyper-V’s extensible switch framework the Nexus 1000v, as when Windows 8 is released, can now be used to create advanced virtual networking features within a Microsoft Hyper-V environment. VM-FEX (Hypervisor Bypass) will also available, its worth noting you have to be running Hyper-V on Cisco UCS utilising the VIC converged network card to get VM-FEX.

Check out the official announcement:

http://www.cisco.com/en/US/solutions/collateral/ns340/ns517/ns224/ns955/ns963/solution_overview_c22-687087.html

Its fair to say allot of people simply haven’t considered Hyper-V due to the lack of Nk1V support so it will be interesting if this any impact on VMware’s dominance.

Post to Twitter

Mar 252011
 

Rather non descriptive and annoying error when setting up a 1000v for the first time. You can also see the “HTTP/1.1 400 Bad Request” along with the error message.

Cause:

Incorrect port

Or

You are connecting to a ESX server and no the vCenter server.

Resolution:

Change the port in vCenter to port 80.

‘Administration -> vCenter Server Settings  -> Ports’

image

Or

Point it to the correct vCenter server.

Post to Twitter

Jun 172010
 

Someone asked me recently what are the differences between Distributed Virtual Switch and the Cisco Nexus 1000v?

As I have only used the 1000v in lab environments my highlevel knowledge was a little rusty.

This is what I found as being available in the 1000v and not the VDS:

  • With the Nexus 1000v you get a IOS interface that will allow network managers to manage the virtual network infrastructure with the same  features as they already use to manage the physical network.
  • Port profile – As that VM moves from server to server with VMotion, the port profile follows it. All security and network configurations, stay with the VM as it travels from server to server. Enabling security policies you would traditionally find in the physical servers to be applied to VMs
  • QOS (Quality Of Service)
  • Switched Port Analyser
  • Authentication.
  • And many more…

Much more on the features of the 1000v can be found http://www.cisco.com/en/US/products/ps9902/index.html

The VDS is a big step forward from the single vSwitch model with features like:

  • Central Management
  • Network Aware Vmotion
  • Private VLANS

More info on VDS: http://www.vmware.com/products/vnetwork-distributed-switch/

Post to Twitter

Twitter links powered by Tweet This v1.8.3, a WordPress plugin for Twitter.