• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

dvSwitch Connectivity

J

jenuster

Limp Gawd
Joined
Mar 8, 2011
Messages
154
Tried to migrate my vm networking from vswitch to dvswitch and for some reason when I migrate my virtual machines to the dvswitch, I lose connectivity to the VM's only. I still retain access to the host and the host can ping the iscsi network.

So I created a new dvSwitch, created portgroup and migrated vmkernel and my iscsi vswitch's to the dvswitch. Then I moved the virtual machines. Any idea what I might be doing wrong?
 
Hmm.I tried to set the vlan ID to allow all (4094), but then I lost all connectivity to the host. Had to restore the standard switch from the console. I'm going to delete the dvswitch and try to set this up from scratch again.
 
Uh... You only set it to ALL like that if the Guest OS is going to do the tagging. If you want all (and have the dVSwitch do the tagging..by far most common) you set a range, like 1-4094.
 
Ah, that makes sense. Anyway I couldn't get back to the host for some reason. Even after restoring to the standard switch, I could not log onto the host. Connecting to the host via vsphere client, I kept on getting stuck on "loading inventory". I also tried to unlink the vmnic from the newly created vswitch and assign it back to my original two vswitches..that did not work either. So I'm going to just reset the ESXi host and try to setup the dvswitch again, but I don't think the vlan tagging was the issue (until I stupidly added the 4094).
 
All set. Just recreated everything and it worked flawlessly. Not sure what was going the first time. Thanks for everyones help. Next step: trying to get the Cisco 1000v configured.
 
So I receive an error when I run the Nexus 1000V GUI install stating that there are no switches present on the selected inventory items.

Looks like I can revert back to the virtual switches and then run the installer again or set up the 1000V manually. Cisco actually has some good documentation on this.
 
1) I went ahead and installed the VEM modules on each host via CLI. The VEM agent is running on both hosts.

2) Created new plugin for 1000V and registered the plugin


3) Now in terms of connecting the VSM to VCenter, I went and ahead and applied the following commands:

switch(config)# svs connection vc
switch(config-svs-conn)# protocol vmware-vim
switch(config-svs-conn)# remote ip address 192.168.1.151
switch(config-svs-conn)# vmware dvs datacenter-name ?
LINE Datacenter name in VC with path (e.g. DCName,
DCFolder/DCName)
switch(config-svs-conn)# vmware dvs datacenter-name Home Lab
switch(config-svs-conn)# connect
ERROR: Failed to create vmware dvs because svs-domain not configured.

Here is the Svs domain config:

svs-domain
domain id 0
control vlan 0
packet vlan 0
svs mode L2


Any ideas?
 
Did you go through the initial setup config when the VSM boots to set your VLANs and domain ID? If not you need to do that manually. Appears they aren't configured.
 
You were right. Although I went through the initial setup, the changes did not reflect on the nexus. I ended up moving back to virtual switches from DVS and then using the GUI to set everything up (I was pulling my hair out trying to do everything manually). Once you get it done the first time, then you realize it's not that bad of a setup.
 
You must log in or register to reply here.
Back
Top