I have 4 nics, 2 nics service a vswitch with a service console and a VMkernel. The service console IP works fine but I have no network connectivity for the VMkernel on the same vswitch with a static IP. If I set the VMkernel for DHCP it gets a 169.x address. esxcfg-switch -l & esxcfg-nics -l show no problems.
Hello,
It seems both the NICs which you are using having a VLAN configured on the pSwitch.
Try to configure the vSwitch with only one NIC that having Service Console PortGroup and confirm the S.C having connectivity
Un-Link the NIC from the vSwitch and add the second NIC and confirm the S.C having connectivity.
If you have a connectivity on both NICs, then the problem in the pSwitch seems to be.
Do the above troubleshooting with VMKernel PortGroup and confirm there is a connectivity to the other host via vmkping command.
If doesn't work then make sure either there is a trunking in the pSwitch or not.
If you have trunking,make sure the pSwitch Port tagged.
Put the VLAN ID in the VMKernel PortGroup.
Put the VLAN ID in the Service Console PortGroup
If you are not sure, connect both VMKernel NICs to a Cross-over cable and try the connectivity testing.
Best Regards,
Hussain Al Sayed
If you find this information useful, please award points for "correct" or "helpful".
Is there definately a DHCP server on the network that those two NICs are plugged in? and if you give the VMkernel a static IP, are you doing it on the same subnet and VLAN (if applicable). When you give it a static IP, how do you confirm it doesn't have connectivity?
Maybe attach a screen shot of the Configuration --> Networking.
Are you using vmkping from the service console to deterine if you have VMKenel connectivity? Possibliy someone already has the IP address that you're trying to utilize for your VMKernel IP?
Datto
Hello,
It seems both the NICs which you are using having a VLAN configured on the pSwitch.
Try to configure the vSwitch with only one NIC that having Service Console PortGroup and confirm the S.C having connectivity
Un-Link the NIC from the vSwitch and add the second NIC and confirm the S.C having connectivity.
If you have a connectivity on both NICs, then the problem in the pSwitch seems to be.
Do the above troubleshooting with VMKernel PortGroup and confirm there is a connectivity to the other host via vmkping command.
If doesn't work then make sure either there is a trunking in the pSwitch or not.
If you have trunking,make sure the pSwitch Port tagged.
Put the VLAN ID in the VMKernel PortGroup.
Put the VLAN ID in the Service Console PortGroup
If you are not sure, connect both VMKernel NICs to a Cross-over cable and try the connectivity testing.
Best Regards,
Hussain Al Sayed
If you find this information useful, please award points for "correct" or "helpful".
misconfigured vlan on the physical switch. The strange part is that the service console on the same vlan as the VMKernel and the same vswitch did have connectivity.
Hello,
Thanks for posting back explaining how the problem get resolved.
Best Regards,
Hussain Al Sayed
If you find this information useful, please award points for "correct" or "helpful".