Hi Alain,

  For the VSM-VEM communication issue, please refer the troubleshooting doc on CCO: http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_0_4_s_v_1_2/troubleshooting/configuration/guide/trouble_5modules.html

The VSM's 3 vnics are for control, management and packet traffic respectively. To do this, you will need to create port-groups on the vSwitch of the ESX host hosting the VSM VM (in your case, esx3), and assign them to the 3 vnics.

You can refer to the installation guide present here: http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_0_4_s_v_1_2/install/software/guide/n1000v_install_software.html

Some details on creation of the 3 port-groups:

For eg: say control vlan is 1, packet vlan 2 and mgmt vlan is 3. Then on the vSwitch on ESX3 do the following:

- in the Networking view of ESX3, click on 'Properties' for vSwitch0 (or any other vswitch you are using for VSM traffic).

- In the window that opens, click on 'Add'.

- Select 'Virtual Machine' (which will be default)

- Click on Next

- Specify a Network label(name) for the port-group and specify the vlan (see attached port-group-creation-for-VSM.gif)

- Click on Next and Finish.

- Similarly create for packet vlan (and management if it is different from the VM Network subnet)

- Assign the 3 vnics of the VSM in the exact order of control port-group, management and packet.

Note: Please ensure that the vmnic0 of the vSwitch0 (or the physical nic associated to the vswitch) to be a trunk allowing the above vlans at the other end.

Hope this helps,

Thanks,

Vinutha