Issues of Nexus 1000v

Similar Questions

• Nexus 1000v deployment issues

  I'm working on the Cisco Nexus 1000v deployment to our ESX cluster. I have read the Cisco "Start Guide" and the "installation guide" but the guides are good to generalize your environment and obviously does not meet my questions based on our architecture.

  This comment in the "Getting Started Guide" Cisco makes it sound like you can't uplink of several switches on an individual ESX host:

  «The server administrator must assign not more than one uplink on the same VLAN without port channels.» Affect more than one uplink on the same host is not supported by the following:

  A profile without the port channels.

  Port profiles that share one or more VLANS.

  After this comment, is possible to PortChannel 2 natachasery on one side of the link (ESX host side) and each have to go to a separate upstream switch? I am creating a redundancy to the ESX host using 2 switches but this comment sounds like I need the side portchannel ESX to associate the VLAN for both interfaces. How do you manage each link and then on the side of the switch upstream? I don't think that you can add to a portchannel on this side of the uplink as the port channel protocol will not properly negotiate and show one side down on the side ESX/VEM.

  I'm more complicate it? Thank you.

  Do not portchannel, but it is possible the channel port to different switches using the pinning VPC - MAC mode. On upstream switches, make sure that the ports are configured the same. Same speed, switch config, VLAN, etc (but no control channel)

  On the VSM to create a unique profile eth type port with the following channel-group command

  port-profile type ethernet Uplink-VPC

  VMware-port group

  switchport mode trunk

  Automatic channel-group on mac - pinning

  no downtime

  System vlan 2.10

  enabled state

  What that will do is create a channel port on the N1KV only. Your ESX host will get redundancy but your balancing algorithm will be simple Robin out of the VM. If you want to pin a specific traffic for a particular connection, you can add the "pin id" command to your port-type veth profiles.

  To see the PIN, you can run

  module vem x run vemcmd see the port

  n1000v-module # 5 MV vem run vemcmd see the port

  LTL VSM link PC - LTL SGID Vem State Port Admin Port

  18 Eth5/2 UP UP FWD 1 305 vmnic1

  19 Eth5/3 UP UP FWD 305 2 vmnic2

  49 Veth1 UP UP 0 1 vm1 - 3.eth0 FWD

  50 Veth3 UP UP 0 2 linux - 4.eth0 FWD

  Po5 305 to TOP up FWD 0

  The key is the column SGID. vmnic1 is SGID 1 and vmnic2 2 SGID. Vm1-3 VM is pinned to SGID1 and linux-4 is pinned to SGID2.

  You can kill a connection and traffic should swap.

  Louis

• Replacement of failing on Nexus 1000v VEM

  I was curious how others accomplish the replacement of a failed ESXi host who is an on the Nexus 1000v VEM. I did this procedure once and it seemed endless. The goal is to make the swap of the transparent to the Nexus 1000v (VEM even #, just different VMware UUID)

  -Transition to the standard vSwitches home

  -Remove the switch distributed via vCenter host (host of right click and delete)

  -Swap physically on the chassis

  -Find the UUID for new host (got esxcfg-info)

  -Install new MEC in the 1000v with this UUID

  -Host of replacement over 1000v that assumes the number of Vincent who was installed just to migrate

  Ben,

  Note - 1000v in relationship issues are better posted in the «Server network» forum  This forum is specific to the UCS.

  https://supportforums.Cisco.com/community/NetPro/data-center/server-network?view=discussions

  The procedure that you use is the right.  Another method is to remove the host of 1000v with elegance, then issue a 'no vem X"that removes the MEC does record from the MSM.  Exchange your hosts, then add back to the 1000v.  Is there a reason that you need the same UUID?

  Kind regards

  Robert

• UCS environment vSphere 5.1 upgrade to vSphere 6 with Nexus 1000v

  Hi, I've faced trying to get the help of TAC and internet research on the way to upgrade to our UCS environment, and as a last thought resort, I would try a post on the forum.

  My environment is an environment of UCS chassis with double tracking, tissue of interconnections, years 1110 with pair HA of 1000v 5.1 running vsphere.  We have updated all our equipment (blades, series C and UCS Manager) for the supported versions of the firmware by CISCO for vSphere 6.

  We have even upgraded our Nexus 1000v 5.2 (1) SV3(1.5a) which is a support for vSphere version 6.

  To save us some treatment and cost of issuing permits and on our previous vcenter server performance was lacking and unreliable, I looked at the virtual migration on the vCenter 6 appliance.  There is nowhere where I can find information which advises on how to begin the process of upgrading VMWare on NGC when the 1000v is incorporated.  I would have thought that it is a virtual machine if you have all of your improved versions to support versions for 6 veil smooth.

  A response I got from TAC was that we had to move all of our VM on a standard switch to improve the vCenter, but given we are already on a supported the 1000v for vSphere version 6 that he left me confused, nor that I would get the opportunity to rework our environment being a hospital with this kind of downtime and outage windows for more than 200 machines.

  Can provide some tips, or anyone else has tried a similar upgrade path?

  Greetings.

  It seems that you have already upgraded your components N1k (are VEM upgraded to match?).

  Are your questions more info on how you upgrade/migration to a vcenter server to another?

  If you import your vcenter database to your new vcenter, it shouldn't have a lot of waste of time, as the VSM/VEM will always see the vcenter and N1k dVS.  If you change the vcenter server name/IP, but import the old vcenter DB, there are a few steps, you will need to ensure that the connection of VSM SVS corresponds to the new IP address in vcenter.

  If you try to create a new additional vcenter in parallel, then you will have problems of downtime as the name of port-profiles/network programming the guestVMs currently have will lose their 'support' info if you attempt to migrate, because you to NIC dVS standard or generic before the hosts for the new vcenter.

  If you are already on vcenter 6, I believe you can vmotion from one host to another and more profile vswitch/dVS/port used.

  Really need more detail on how to migrate from a vcenter for the VCA 6.0.

  Thank you

  Kirk...

• 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

• What does Nexus 1000v Version number Say

  Can any body provide long Nexus 1000v version number, for example 5.2 (1) SV3 (1.15)

  And what does SV mean in the version number.

  Thank you

  SV is the abbreviation of "Swiched VMware"

  See below for a detailed explanation:

  http://www.Cisco.com/c/en/us/about/Security-Center/iOS-NX-OS-reference-g...

  The Cisco NX - OS dialing software

  Software Cisco NX - OS is a data-center-class operating system that provides a high thanks to a modular design availability. The Cisco NX - OS software is software-based Cisco MDS 9000 SAN - OS and it supports the Cisco Nexus series switch Cisco MDS 9000 series multilayer. The Cisco NX - OS software contains a boot kick image and an image of the system, the two images contain an identifier of major version, minor version identifier and a maintenance release identifier, and they may also contain an identifier of reconstruction, which can also be referred to as a Patch to support. (See Figure 6).

  Software NX - OS Cisco Nexus 7000 Series and MDS 9000 series switches use the numbering scheme that is illustrated in Figure 6.

  Figure 6. Switches of the series Cisco IOS dial for Cisco Nexus 7000 and MDS 9000 NX - OS

  

  For the other members of the family, software Cisco NX - OS uses a combination of systems independent of the platform and is dependent on the platform as shown in Figure 6a.

  Figure 6 a. software Cisco IOS NX - OS numbering for the link between 4000 and 5000 Series and Nexus 1000 switches virtual

  

  The indicator of the platform is N for switches of the 5000 series Nexus, E for the switches of the series 4000 Nexus and S for the Nexus 1000 series switches. In addition, Nexus 1000 virtual switch uses a designation of two letters platform where the second letter indicates the hypervisor vendor that the virtual switch is compatible with, for example V for VMware. Features there are patches in the platform-independent code and features are present in the version of the platform-dependent Figure 6 a above, there is place of bugs in the version of the software Cisco NX - OS 4.0(1a) are present in the version 4.0(1a) N1(1a).

• The Nexus 1000V loop prevention

  Hello

  I wonder if there is a mechanism that I can use to secure a network against the loop of L2 packed the side of vserver in Vmware with Nexus 1000V environment.

  I know, Nexus 1000V can prevent against the loop on the external links, but there is no information, there are features that can prevent against the loop caused by the bridge set up on the side of the OS on VMware virtual server.

  Thank you in advance for an answer.

  Concerning

  Lukas

  Hi Lukas.

  To avoid loops, the N1KV does not pass traffic between physical network cards and also, he silently down traffic between vNIC is the bridge by operating system.

  http://www.Cisco.com/en/us/prod/collateral/switches/ps9441/ps9902/guide_c07-556626.html#wp9000156

  We must not explicit configuration on N1KV.

  Padma

• Cisco Nexus 1000V Virtual Switch Module investment series in the Cisco Unified Computing System

  Hi all
  I read an article by Cisco entitled "Best practices in Deploying Cisco Nexus 1000V Switches Cisco UCS B and C Series series Cisco UCS Manager servers" http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9902/white_paper_c11-558242.html

  A lot of excellent information, but the section that intrigues me, has to do with the implementation of module of the VSM in the UCS. The article lists 4 options in order of preference, but does not provide details or the reasons underlying the recommendations. The options are the following:

  ============================================================================================================================================================
  Option 1: VSM external to the Cisco Unified Computing System on the Cisco Nexus 1010

  In this scenario, the virtual environment management operations is accomplished in a method identical to existing environments not virtualized. With multiple instances on the Nexus 1010 VSM, multiple vCenter data centers can be supported.
  ============================================================================================================================================================

  Option 2: VSM outside the Cisco Unified Computing System on the Cisco Nexus 1000V series MEC

  This model allows to centralize the management of virtual infrastructure, and proved to be very stable...
  ============================================================================================================================================================

  Option 3: VSM Outside the Cisco Unified Computing System on the VMware vSwitch

  This model allows to isolate managed devices, and it migrates to the model of the device of the unit of Services virtual Cisco Nexus 1010. A possible concern here is the management and the operational model of the network between the MSM and VEM devices links.
  ============================================================================================================================================================

  Option 4: VSM Inside the Cisco Unified Computing System on the VMware vSwitch

  This model was also stable in test deployments. A possible concern here is the management and the operational model of the network links between the MSM and VEM devices and switching infrastructure have doubles in your Cisco Unified Computing System.
  ============================================================================================================================================================

  As a beginner for both 100V Nexus and UCS, I hope someone can help me understand the configuration of these options and equally important to provide a more detailed explanation of each of the options and the resoning behind preferences (pro advantages and disadvantages).

  Thank you
  Pradeep

  No, they are different products. vASA will be a virtual version of our ASA device.

  ASA is a complete recommended firewall.

• 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 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

• VXLAN on UCS: IGMP with Catalyst 3750, 5548 Nexus, Nexus 1000V

  Hello team,

  My lab consists of Catalyst 3750 with SVI acting as the router, 5548 Nexus in the vpc Setup, UCS in end-host Mode and Nexus 1000V with segmentation feature enabled (VXLAN).

  I have two different VLAN for VXLAN (140, 141) to demonstrate connectivity across the L3.

  VMKernel on VLAN 140 guests join the multicast fine group.

  Hosts with VMKernel on 141 VLAN do not join the multicast group.  Then, VMs on these hosts cannot virtual computers ping hosts on the local network VIRTUAL 140, and they can't even ping each other.

  I turned on debug ip igmp on the L3 Switch, and the result indicates a timeout when he is waiting for a report from 141 VLAN:

  15 Oct 08:57:34.201: IGMP (0): send requests General v2 on Vlan140

  15 Oct 08:57:34.201: IGMP (0): set the report interval to 3.6 seconds for 224.0.1.40 on Vlan140

  15 Oct 08:57:36.886: IGMP (0): receipt v2 report on 172.16.66.2 to 239.1.1.1 Vlan140

  15 Oct 08:57:36.886: IGMP (0): group record received for group 239.1.1.1, mode 2 from 172.16.66.2 to 0 sources

  15 Oct 08:57:36.886: IGMP (0): update EXCLUDE group 239.1.1.1 timer

  15 Oct 08:57:36.886: IGMP (0): add/update Vlan140 MRT for (*, 239.1.1.1) 0

  15 Oct 08:57:38.270: IGMP (0): send report v2 for 224.0.1.40 on Vlan140

  15 Oct 08:57:38.270: IGMP (0): receipt v2 report on Vlan140 of 172.16.66.1 for 224.0.1.40

  15 Oct 08:57:38.270: IGMP (0): group record received for group 224.0.1.40, mode 2 from 172.16.66.1 to 0 sources

  15 Oct 08:57:38.270: IGMP (0): update EXCLUDE timer group for 224.0.1.40

  15 Oct 08:57:38.270: IGMP (0): add/update Vlan140 MRT for (*, 224.0.1.40) by 0

  15 Oct 08:57:51.464: IGMP (0): send requests General v2 on Vlan141<----- it="" just="" hangs="" here="" until="" timeout="" and="" goes="" back="" to="">

  15 Oct 08:58:35.107: IGMP (0): send requests General v2 on Vlan140

  15 Oct 08:58:35.107: IGMP (0): set the report interval to 0.3 seconds for 224.0.1.40 on Vlan140

  15 Oct 08:58:35.686: IGMP (0): receipt v2 report on 172.16.66.2 to 239.1.1.1 Vlan140

  15 Oct 08:58:35.686: IGMP (0): group record received for group 239.1.1.1, mode 2 from 172.16.66.2 to 0 sources

  15 Oct 08:58:35.686: IGMP (0): update EXCLUDE group 239.1.1.1 timer

  15 Oct 08:58:35.686: IGMP (0): add/update Vlan140 MRT for (*, 239.1.1.1) 0

  If I do a show ip igmp interface, I get the report that there is no joins for vlan 141:

  Vlan140 is up, line protocol is up

  The Internet address is 172.16.66.1/26

  IGMP is enabled on the interface

  Current version of IGMP host is 2

  Current version of IGMP router is 2

  The IGMP query interval is 60 seconds

  Configured IGMP queries interval is 60 seconds

  IGMP querier timeout is 120 seconds

  Configured IGMP querier timeout is 120 seconds

  Query response time is 10 seconds max IGMP

  Number of queries last member is 2

  Last member query response interval is 1000 ms

  Access group incoming IGMP is not defined

  IGMP activity: 2 joints, 0 leaves

  Multicast routing is enabled on the interface

  Threshold multicast TTL is 0

  Multicast designated router (DR) is 172.16.66.1 (this system)

  IGMP querying router is 172.16.66.1 (this system)

  Multicast groups joined by this system (number of users):

  224.0.1.40 (1)

  Vlan141 is up, line protocol is up

  The Internet address is 172.16.66.65/26

  IGMP is enabled on the interface

  Current version of IGMP host is 2

  Current version of IGMP router is 2

  The IGMP query interval is 60 seconds

  Configured IGMP queries interval is 60 seconds

  IGMP querier timeout is 120 seconds

  Configured IGMP querier timeout is 120 seconds

  Query response time is 10 seconds max IGMP

  Number of queries last member is 2

  Last member query response interval is 1000 ms

  Access group incoming IGMP is not defined

  IGMP activity: 0 joins, 0 leaves

  Multicast routing is enabled on the interface

  Threshold multicast TTL is 0

  Multicast designated router (DR) is 172.16.66.65 (this system)

  IGMP querying router is 172.16.66.65 (this system)

  No group multicast joined by this system

  Is there a way to check why the hosts on 141 VLAN are joined not successfully?  port-profile on the 1000V configuration of vlan 140 and vlan 141 rising and vmkernel are identical, except for the different numbers vlan.

  Thank you

  Trevor

  Hi Trevor,

  Once the quick thing to check would be the config igmp for both VLAN.

  where did you configure the interrogator for the vlan 140 and 141?

  are there changes in transport VXLAN crossing routers? If so you would need routing multicast enabled.

  Thank you!

  . / Afonso

• Configuration of the channel of port on nexus 1000V

  Hello

  I'm new on nexus 1000V, the configuration is as follows, UCS chassis with 4 blades full-width connected to 2 FI 6248UP.

  each FI's uplink to a n5k (no mail ORDER).

  is there any configuration model the nexus 1000v? How to configure port-channel?

  Thank you.

  Hello

  We recommend using mac pinning ("channel-group auto mode on mac - pinning") when N1KV is used on the blades of the UCS.

  Next doc provides good overview on best practices.

  Best practices in deploying Cisco Nexus 1000V switches in the Cisco UCS B and C series series Cisco UCS Manager servers

  http://www.Cisco.com/en/us/prod/collateral/switches/ps9441/ps9902/white_paper_c11-558242.html

  HTH

  Padma

• 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

• Authentication of connection Cisco AAA to shelf (MS IAS) Nexus 1000v

  Hey

  I have a link, I'll add to my radius for the logon server.

  On a sw IOS, I need to do more

  Number of attribute change to '1 '.
  Set the Format of the attribute to "String".
  Type "shell: priv-lvl = 15" in the value of the attribute field

  But should I put in the "shell", so I'll work on a Nexus 1000v

  Shell: roles = "network-admin".

  (or replace any role to assign the user to network-admin)

• 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!