Hi Joel, Yes that is correct. The CLI was introduced for 1(3.x) to 1(4) upgrade. What version of the VSM are you running? Thanks, Sachin ... View more

Do you have "no shut" in the port-profile to make the profile active? Could you post the running config snippets? ... View more

Hi Sanjeev, Is the module showing as up in the VSM when you execute 'show module'? Is you ESX management VLAN allowed on the access port profile and on the uplink? Is it created on the switch? Do you have system VLANs for your control, packet connectivity? For your ESX mgmt connectivity? Thanks, Sachin ... View more

Hello, Are there any specific features which you are especially interested in running? The SV1(4) release has introduced several new features to the product. However, both releases SV1(3c) and SV1(4) have gone through extensive testing to ensure stability. Here is a link to the release notes documenting the features, limitations and caveats of each release: http://www.cisco.com/en/US/products/ps9902/prod_release_notes_list.html Hope this helps! Sachin ... View more

Hi Jean, Based on the port profile names, I am guessing that the VSM is on the VEM with InfraAccess-VSM-Control and InfraAccess-VSM-Packet as the control and packet port groups for the VSM VM. If so, the vlans on these port profiles 901/900 should be defined as system vlans as well. Hope this helps Thanks, Sachin ... View more

Could you post the port profile config for your uplink/veth profiles, svs connection and svs domain if possible? Also could you paste the output of vemcmd show version on the host. thanks, sachin ... View more

Is your VSM running on the N1KV port profiles vlan-22 and vlan-23 for the control and packet interface? If so, you'll have to make both of those system vlans in the port profile as well. Also have you added your pnic to the uplink port profile from the DVS networking view on the host? Thanks, sachin ... View more