Design of Nexus 1000v - COS and vCenter

Hello everyone. First foray into the 1000V, so hoping someone can give an opinion as to whether my thoughts for the design of high level are on the right track?

Host servers have 4 Gb x 10 and 2 x 1 GB ports
ESXi 4.1, Enterprise Plus and 1000v a license for every host
We will use the devices 1010 need, so no VSM modules
10 GB ports will be allocated to the 1000v vDS
- Portprofiles created for vMotion and all required VLANS VM
- No requirement for IP storage
The ports of 1 GB on a standard vSwitch for VMkernel Port Management
- The thinking is that if the vCenter disconnects we can manage the vDS (I suppose that this nature applies to the 1000 v as the VMware vDS?), so it is best to have hosts on a network that we can always access and change if necessary
- 1010 devices are going to sit on this network (or be routable to/from it)
vCenter will be installed on a physical server
- No Heartbeat vCenter, so only one instance running
- Because of the dependence vCenter to 1000v port configuration, is probably a good idea to vCenter, such as a computer virtual connected to a port vDS for its virtual machine traffic?
- The physical vCenter will have connectivity to the management on every host and devices 1010 VMkernel port
- As an alternative, I guess we could put a VM port on the connections of 1 GB for vCenter, but who was going to start complicating the design and management

What is everything is OK good, or is it too conservative? Should we watch it again add 1 GB ports in links rising 1000v and with the VMkernel management as on a separate port profile and containing a virtualized vCenter (which is what I normally would use for new deployments).

Thanks in advance for any comments,

Steve

Hi Steve,.

Disclaimer clause - I work for Cisco and I consolidated pro network

There was a lot of similar questions already posted on the Cisco 1000v community. There are a lot of similar questions and suggestions already available: https://www.myciscocommunity.com/community/products/nexus1000v?view=discussions

Here's a recent post similar to yours.

https://www.myciscocommunity.com/thread/17624?TSTART=0

Regarding some of your design considerations, many of them come down to your level of comfort & expertise. With vCenter as a physical host allows you to keep out of your virtual environment, but you will lose the advatanges of the best use of the host and VMotion resources that make the host maintenance & limited downtime. With the vCenter as a virtual machine and running on the DVS, you'd probably the service profile, the VC is assigned to a vlan "system". This will ensure that your VC network connectivity is ALWAYS transmitted, even if the VSMs are offline and VEM accommodation the VC is reset. This added protection removes much of the risk of the VC running on the DVS it manages.

Regarding your VSM availability, if the two 1010 are falling, yes you are not able to make changes of configuration on the VSM. Once active & well configured, there shouldn't be many situations when the two VSMs are offline and you have an urgent need for an immediate configuration change. VEM guests can survive very well in mode without head (no present VSM) assuming that they are not restart before finding the VSM. Additional protection for important virtual connections for the management, storage and control IP traffic include the use of "system VLAN" as stated above.

With each adapter used comes additional management and the need for additional upstream switch ports. With 4 x 10 G of each host cards I would find it difficult to justify also connections of 1 G of utilzing, except if you opt for an "out of band" connections for your management on a vSwitch interfaces. If you are comfortable with the performance of all your virtual interfaces including management & VMotion on the DVS you can better pool your resources, but using only your adapters 10 G uplinks. By running all about the 1000v, you can easily apply QoS & limit the use of bandwidth by Port profiles - news just released version 1.4 of 1000v is incredibly easy to set up. Certainly worth a visit. See my post here for some of the new features in the 1000v: https://www.myciscocommunity.com/thread/17120?tstart=0

I hope this helps.

Kind regards

Robert

Tags: VMware

Similar Questions

Nexus 1000v, UCS, and Microsoft NETWORK load balancing

Hi all

I have a client that implements a new Exchange 2010 environment. They have an obligation to configure load balancing for Client Access servers. The environment consists of VMware vShpere running on top of Cisco UCS blades with the Nexus 1000v dvSwitch.

Everything I've read so far indicates that I must do the following:

1 configure MS in Multicast mode load balancing (by selecting the IGMP protocol option).

2. create a static ARP entry for the address of virtual cluster on the router for the subnet of the server.

3. (maybe) configure a static MAC table entry on the router for the subnet of the server.

3. (maybe) to disable the IGMP snooping on the VLAN appropriate in the Nexus 1000v.

My questions are:

1. any person running successfully a similar configuration?

2 are there missing steps in the list above, or I shouldn't do?

3. If I am disabling the snooping IGMP on the Nexus 1000v should I also disable it on the fabric of UCS interconnections and router?

Thanks a lot for your time,.

Aaron

Aaron,

The steps above you are correct, you need steps 1-4 to operate correctly. Normally people will create a VLAN separate to their interfaces NLB/subnet, to prevent floods mcast uncessisary frameworks within the network.

To answer your questions

(1) I saw multiple clients run this configuration

(2) the steps you are correct

(3) you can't toggle the on UCS IGMP snooping. It is enabled by default and not a configurable option. There is no need to change anything within the UCS regarding MS NLB with the above procedure. FYI - the ability to disable/enable the snooping IGMP on UCS is scheduled for a next version 2.1.
```
This is the correct method untill the time we have the option of configuring static multicast mac entries on

the Nexus 1000v.  If this is a feature you'd like, please open a TAC case and request for bug CSCtb93725 to be linked to your SR.
This will give more "push" to our develpment team to prioritize this request.
Hopefully some other customers can share their experience.
Regards,
```
Robert

How to check and confirm the Nexus 1000V secondary work if primary goes off

Hello
I installed Nexus 1000V Primarry and secondary on different ESXis
but I have to turn off the primary, how to ensure that the school will be in charge and usually have any disconnection
the module displays them and seem to be ok
any other checks to do before continuing?
Thank you
Use "show system redundancy status. You can also manually failover

http://www.Cisco.com/en/us/docs/switches/Datacenter/nexus1000/SW/4_2_1_s_v_1_4/high_availability/configuration/guide/n1000v_ha_3system.html

The output from the example:
```
n1000v# show system redundancy status
```
```
Redundancy role
---------------
administrative: primary
operational: primary
```
Redundancy mode
---------------
administrative: HA
operational: HA
```
This supervisor (sup-1)
-----------------------
Redundancy state: Active
Supervisor state: Active
Internal state: Active with HA standby
```
Another supervisor (sup-2)
```
------------------------
Redundancy state: Standby
Supervisor state: HA standby
Internal state: HA standby
```

Nexus 1000v

Hey guys,.
Hope this is the right place to post.
IM currently working on a design legacy to put in an ESXi 5 with Nexus 1000v solution and a back-end of a Cisco UCS 5180.
I have a few questions to ask about what people do in the real world about this type of package upward:
In oder to use the Nexus 1000v - should I vCenter? The reason why I ask, is there no was included on the initial list of the Kit. I would say to HA and vMotion virtual Center, but the clients wants to know if I can see what we have for now and licenses to implement vCenter at a later date.
Ive done some reading about the Nexus 1000v as Ive never designed a soluton with that of before. Cisco is recommended 2 VSM be implemented for redundancy. Is this correct? Do need me a license for each VSM? I also suppose to meet this best practice I need HA and vMoton and, therefore, vCenter?
The virtual machine for the VSM, can they sit inside the cluster?
Thanks in advance for any help.

In oder to use the Nexus 1000v - should I vCenter?

Yes - the Nexus 1000v is a type of switch developed virtual and it requires vcenetr

Ive done some reading about the Nexus 1000v as Ive never designed a soluton with that of before. Cisco is recommended 2 VSM be implemented for redundancy. Is this correct? Do need me a license for each VSM? I also suppose to meet this best practice I need HA and vMoton and, therefore, vCenter?

I'm not sure the VSMs but yes HA and vMotion are required as part of best practices

The virtual machine for the VSM, can they sit inside the cluster?

Yes they cane xist within the cluster.

Design/implementation of Nexus 1000V

Hi team,

I have a premium partner who is an ATP on Data Center Unified Computing. He has posted this question, I hope you can help me to provide the resolution.

I have questions about nexus 1KV design/implementation:

-How to migrate virtual switches often to vswitch0 (in each ESX server has 3 vswitches and the VMS installation wizard will only migrate vswicht0)? for example, to other vswitchs with other vlan... Please tell me how...
-With MUV (vmware update manager) can install modules of MEC in ESX servers? or install VEM manually on each ESX Server?
-Assuming VUM install all modules of MEC, MEC (vib package) version is automatically compatible with the version of vmware are?
-is the need to create port of PACKET-CONTROL groups in all THE esx servers before migrating to Nexus 1000? or only the VEM installation is enough?
-According to the manual Cisco VSM can participate in VMOTION, but, how?... What is the recommendation? When the primary virtual machines are moving, the secondary VSM take control? This is the case with connectivity to all virtual machines?
-When there are two clusters in a vmware vcenter, how to install/configure VSM?
-For the concepts of high availability, which is the best choice of design of nexus? in view of the characteristics of vmware (FT, DRS, VMOTION, Cluster)
-How to migrate port group existing Kernel to nexus iSCSI?... What are the steps? cisco manual "Migration from VMware to Cisco Nexus 1000V vSwitch" show how to generate the port profile, but
How to create iSCSI target? (ip address, the username/password)... where it is defined?
-Assuming that VEM licenses is not enough for all the ESX servers, ¿will happen to connectivity of your virtual machines on hosts without licenses VEM? can work with vmware vswitches?

I have to install nexus 1000V in vmware with VDI plataform, with multiple ESX servers, with 3 vswitch on each ESX Server, with several machinne virtual running, two groups defined with active vmotion and DRS and the iSCSI storage Center

I have several manuals Cisco on nexus, but I see special attention in our facilities, migration options is not a broad question, you you have 'success stories' or customers experiences of implementation with migration with nexus?

Thank you in advance.

Jojo Santos

Cisco partner Helpline presales

Thanks for the questions of Jojo, but this question of type 1000v is better for the Nexus 1000v forum:

https://www.myciscocommunity.com/Community/products/nexus1000v

Answers online. I suggest you just go in a Guides began to acquire a solid understanding of database concepts & operations prior to deployment.

jojsanto wrote:

Hi Team,

I have a premium partner who is an ATP on Data Center Unified Computing. He posted this question, hopefully you can help me provide resolution.

I have questions about nexus 1KV design/implementation:

-How migrate virtual switchs distint to vswitch0 (in each ESX server has 3 vswitches and the installation wizard of VMS only migrate vswicht0)?? for example others vswitchs with others vlan.. please tell me how...

[Robert] After your initial installation you can easily migrate all VMs within the same vSwitch Port Group at the same time using the Network Migration Wizard. Simply go to Home - Inventory - Networking, right click on the 1000v DVS and select "Migrate Virtual Machine Networking..." Follow the wizard to select your Source (vSwitch Port Groups) & Destination DVS Port Profiles

-With VUM (vmware update manager) is possible install VEM modules in ESX Servers ??? or must install VEM manually in each ESX Server?

[Robert] As per the Getting Started & Installation guides, you can use either VUM or manual installation method for VEM software install.

http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_0_4_s_v_1_3/getting_started/configuration/guide/n1000v_gsg.html

-Supposing of VUM install all VEM modules, the VEM version (vib package) is automatically compatible with build existen vmware version?

[Robert] Yes. Assuming VMware has added all the latest VEM software to their online repository, VUM will be able to pull down & install the correct one automatically.

-is need to create PACKET-MANAGEMENT-CONTROL port groups in ALL esx servers before to migrate to Nexus 1000? or only VEM installation is enough???

[Robert] If you're planning on keeping the 1000v VSM on vSwitches (rather than migrating itself to the 1000v) then you'll need the Control/Mgmt/Packet port groups on each host you ever plan on running/hosting the VSM on. If you create the VSM port group on the 1000v DVS, then they will automatically exist on all hosts that are part of the DVS.

-According to the Cisco manuals VSM can participate in VMOTION, but, how? .. what is the recommendation?..when the primary VMS is moving, the secondary VSM take control?? that occurs with connectivity in all virtual machines?

[Robert] Since a VMotion does not really impact connectivity for a significant amount of time, the VSM can be easily VMotioned around even if its a single Standalone deployment. Just like you can vMotion vCenter (which manages the actual task) you can also Vmotion a standalone or redundant VSM without problems. No special considerations here other than usual VMotion pre-reqs.

-When there two clusters in one vmware vcenter, how must install/configure VSM?

[Robert] No different. The only consideration that changes "how" you install a VSM is a vCenter with multiple DanaCenters. VEM hosts can only connect to a VSM that reside within the same DC. Different clusters are not a problem.

-For High Availability concepts, wich is the best choices of design of nexus? considering vmware features (FT,DRS, VMOTION, Cluster)

[Robert] There are multiple "Best Practice" designs which discuss this in great detail. I've attached a draft doc one on this thread. A public one will be available in the coming month. Some points to consider is that you do not need FT. FT is still maturing, and since you can deploy redundany VSMs at no additional cost, there's no need for it. For DRS you'll want to create a DRS Rule to avoid ever hosting the Primar & Secondary VSM on the same host.

-How to migrate existent Kernel iSCSI port group to nexus? .. what are the steps? in cisco manual"Migration from VMware vSwitch to Cisco Nexus 1000V" show how to generate the port-profile, but
how to create the iSCSI target? (ip address, user/password) ..where is it defined?

[Robert] You can migrate any VMKernel port from vCenter by selecting a host, go to the Networking Configuration - DVS and select Manage Virtual Adapters - Migrate Existing Virtual Adapter. Then follow the wizard. Before you do so, create the corresponding vEth Port Profile on your 1000v, assign appropriate VLAN etc. All VMKernel IPs are set within vCenter, 1000v is Layer 2 only, we don't assign Layer 3 addresses to virtual ports (other than Mgmt). All the rest of the iSCSI configuration is done via vCenter - Storage Adapters as usual (for Targets, CHAP Authentication etc)

-Supposing of the licences of VEM is not enough for all ESX servers,, ¿will happen to the connectivity of your virtual machines in hosts without VEM licences? ¿can operate with vmware vswitches?

[Robert] When a VEM comes online with the DVS, if there are not enough available licensses to license EVERY socket, the VEM will show as unlicensed. Without a license, the virtual ports will not come up. You should closely watch your licenses using the "show license usage" and "show license usage " for detailed allocation information. At any time a VEM can still utilize a vSwitch - with or without 1000v licenses, assuming you still have adapters attached to the vSwitches as uplinks.

I must install nexus 1000V in vmware plataform with VDI, with severals Servers ESX, with 3 vswitch on each ESX Server, with severals virtual machinne running, two clusters defined with vmotion and DRS active and central storage with iSCSI

I have severals cisco manuals about nexus, but i see special focus in installations topics, the options for migrations is not extensive item, ¿do you have "success stories" or customers experiences of implementation with migrations with nexus?

[Robert] Have a good look around the Nexus 1000v community Forum. Lots of stories and information you may find helpful.

Good luck!

Nexus 1000v and vMotion/VM traffic?

Hello
We are moving our servers of VM production to a new data center.
There is a willingness to use the ports of 2 x 10 giga on each ESX host for the uplinks (etherchannel) Nexus 1000v for vMotion traffic and traffic VM.
I don't know if that's even possible/supported? To devote nexus 1000v for vMotion and VM traffic ports at the same time? I think each guest will need an address unique IP for vMotion be able to operate.
Best regards
/ Pete
Info:
vCenter/ESXi - 5.0 Update 3

Yes - the characteristics of vmotion still apply if you use a virtual switch Standard or Distributed Virtual Switch as the Nexus 1000v - you should have a network for vmotion and each port vmkernel will need a unique IP address on the subnet of vmotion

Installation of Nexus 1000v / vCenter user privilege level

Good afternoon
I had a question about the necessary privilege concerning the installation of a Nexus 1000v.
Last week, we install last version of the Nexus1000v on ESXi 5.0.0 Releasebuild-721882 switch.
After a first installation, we noticed we could not establish the connection between the Nexus1000v and the vCenter [error = > the vCenter Extension key was not saved before use].
The key was present on the Nexus 1000v but was not registered under the vCenter MOB (Extension Manager).
We had to increase the privilege level of the service (to vCenter admin) account and re-install to get registred the extension key.
Cisco said that we must use vCenter user with administrator-level privileges to install the Nexus 1000v, but please find my questions:
1 / is it possible to install a Nexus 1000v with administrator privileges "Data center" (no admin vCenter). In general, what is the minimum level of privileges possible to install a Nexus 1000v?
2 / once the privilege is passed to vCenter admin and the installation, it is possible to reduce to a privilege of lower level without affecting the Nexus 1000v?
I'm a network guy, not a guy of sorry server if I'm unclear in my questions :-)
Thanks in advance for your answers.
Kind regards.
Kara

You cannot change the privilege level after the initial connection. He needs to remain at the same level of private.

One of the things to keep in mind is that there is a constant back and forth between the MSM and vCenter. We are pulling and pushing data into vcenter. Every time a VM vmotions, gets turned on, destroyed or changed requires communication between the MSM and vCenter.

Louis

Upgrade to vCenter 4.0 with Cisco Nexus 1000v installed

Hi all
We have vCenter 4.0 and ESX 4.0 servers and we want to upgrade to version 4.1. But also Nexus 1000v installed on the ESX Server and vCenter.i found VMware KB which is http://kb.vmware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1024641 . But only the ESX Server upgrade is explained on this KB, vCenter quid? Our vcenter 4.0 is installed on Windows 2003 64-bit with 64-bit SQL 2005.
We can upgrade vcenter with Nexsus plugin 1000v installed upgrading on-site without problem? And how to proceed? What are the effects of the plugin Nexus1000v installed on the server vcenter during update?
Nexus1000v 4.0. (version 4).sv1(3a) has been installed on the ESX servers.
Concerning

Mecyon,

Upgrading vSphere 4.0-> 4.1 you must update the software VEM (.vib) also. The plugin for vCenter won't change, it won't be anything on your VSM (s). The only thing you should update is the MEC on each host. See the matrix previously posted above for the .vib to install once you're host has been updated.

Note: after this upgrade, that you will be able to update regardless of your software of vSphere host or 1000v (without having to be updated to the other). 1000v VEM dependencies have been removed since vSphere 4.0 Update 2.

Kind regards

Robert

Nexus 1000v and vSwitch best practices

I am working on the design of our vDS Nexus 1000v for use on HP BL490 G6 servers. 8 natachasery is allocated as follows:
vmnic0, 1: management of ESXi, VSM-CTRL-PKT, VSM - MGT
vmnic2, 3: vMotion
vmnic4, 5: iSCSI, FT, Clustering heartbeats
vmnic6, 7: data server and Client VM traffic
Should I migrate all the natachasery to 1000v vDS, or should I let vmnic 0.1 on a regular vSwitch and others migrate to the vDS? If I migrate all the natachasery at the very least I would designate vmnic 0.1 as system so that traffic could elapse until the MSM could be reached. My inclination is to migrate all the natachasery, but I've seen elsewhere on comments in forums that the VSM associated networks and, possibly, the console ESX (i) are better let off of the vDS.
Thoughts?

Here is a best practice-how-to guide specific to 1000v & VC HP might be useful.

See you soon,.

Robert

How change 1010 Nexus and Nexus 1000v IP address

Hi Experts,

We run two VSM and a NAM in the Nexus 1010. The version of Nexus 1010 is 4.2.1.SP1.4. And the Nexus 1000v version is 4.0.4.SV1.3c. Now we need to change the IP address of management in the other. Where can I find the model SOP or config? And nothing I need to remember?

If it is only the mgmt0 you IP address change, you can simply enter the new address under the mgmt0 interface. It automatically syncs with the VC.

I guess you are trying to change the IP address of the VC and the management VLAN. One way to do this is:

-From the Nexus 1000v, disconnect the connection to the VC (connection svs-> without logging)

-Change the IP address of the VC and connect (connection-> remote ip address svs)

-Change the address for mgmt0 Nexus 1000v

-Change the mgmt VLAN on the 1010

-Change the address of the 1010 mgmt

-Reconnect the Nexus 1000v to VC (connection-> connect svs)

Therefore, to change the configuration of VLANS on the switch upstream, more connection to the VC as well.

Thank you

Shankar

VM - FEX and Nexus 1000v relationship

Hello

I'm new in the world of virtulaization and I need to know what the relationship between Cisco Nexus 1000v and Cisco VM - FEX? and when to use VM - FEX and when to use Nexus 1000v.

Concerning

Ahmed,

Nexus 1000v is a Distributed Switch that allows you to manage your VEM, see this relationship as a supervisor-LineCard relationship.

VM - FEX gives you the opportunity to bypass the vSwitch embarked on each host ESXi (VEM) for example.

With VM - FEX, you see the virtual machines as if they were directly connected to the Parent switch (N7K / 5K for example), making it the parent spend management (cause there is more no vSwitch in the middle).

This is a good topic that can be discussed and is difficult to summarize in a few lines, you read something in particular? any questions or doubts we can help clarify?

-Kenny

Nexus 1000v and vmkernel ports

What is the best practice to put on the nexus 1000v vmkernel ports? Is it a good idea to put all the ports of vms and vmkernel on nexus 1000v? switch or dvs or some vmkernel as management ports must be on a standard? If something happens to the 1000v, all management and vms will be unreachable.
any tips?

Yep, that's correct. Port system profiles don't require any communication between the MEC and VSM.

Question about license for Nexus 1000v and it time to stand not licensed ESXi

Hello
I have the license for 12 cpu that are 3 popular ESXi with 4 processors each
so if I add an another ESXi, which will support 60 days
I'm pretty sure but wanted confirmation
Thank you

What version do you use? 2.1 they went to a model free and advanced, depending on the features you need, you can be able to upgrade and continue without additional licenses.

No doubt, you can convert your current license VSG, contact your engineer.

http://blogs.Cisco.com/tag/nexus-1000V/

ESXi 5 and Nexus 1000v

Hello
I have an ESXi 5 but only NIC I am migrating the VSS for Nexus 1000v. I installed Nexus VEM correctly and do primary and secondary, VSMs configured uplink port groups all according to the guides from Cisco. When I try to add a host under the link, I have first to migrate the vnic0 for the Group of appropriate uplink ports and it then asks me to migrate the management port (I think it is vmk0) so if I create a group of ports on Nexus to migrate a management port or do not migrate at all I always lose connectivity to ESXi.
Can someone please share the configs of the Nexus 1000v and how to migrate properly vnic0 and vmk0 (with a single physical NETWORK adapter) so that I do not lose connectivity?
Thanks in advacne.
Remi

control is vlan 152 and package is 153.

You can make same vlan. We have supported using the same vlan for the control and the package for several years now.

Louis

Problems to install the plugin extension of Nexus 1000v vCenter file "invalid URI: the URI is empty.

Hi all
I try to install the Cisco Nexus 1000v switch in my training lab.
When I get to the stage where I add the Extension XML file to the vSphere Plugin Manager, I get an error stating that "invalid URI: the URI is empty.
When I open the cisco_nexus_1000v_extension.xml file, obviously, there is something missing in the & lt; URL & gt; & lt; / url & gt; section.
Issues related to the:
1 has anyone successfully installed the Nexus 1000v switch?
2. If Yes, can you put the file extension xml so I can look at and compare?
3. How can I delete the old file with extension of the Plug-ins available from the plugin Manager section? At the moment he is stuck on download and install...
Thank you, Randy

Mine is working

do not worry about the error, mine still has the error when you click Download, all he has to do is see the upward

Follow the steps on the site of cisco http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_0/install/software/guide/install_n1000v.html

If you want to delete the plugin and get a new use of one the steps here http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_0/troubleshooting/configuration/guide/trouble_3install.html

I followed the guides and got mine working

can not post my xml because it is at home and I'm at work

Chris

Design of Nexus 1000v - COS and vCenter

Similar Questions

Maybe you are looking for