11-14-2016 11:24 AM - edited 03-01-2019 12:57 PM
OS (ESXi) installed on blades has no connectivity to network and cannot ping gateway. I have confirmed the necessary VLAN's on my north bound switchs are in place. I can access the UCS infra and KVM with no issues. UCS infra, blade kvm and ESX are on the same subnet. This is a generic UCS build with nothing special, end-host mod, 3.1(1g) etc... As far as ESX the correct NICs are added to management network with no VLAN specified.
Solved! Go to Solution.
11-14-2016 12:26 PM
The UCSM Vnics are essentially trunks. If you are not already doing so, you will want your VMware portgroup for your admin VMK traffic getting tagged in VMware with the correct admin vlan. You can set this from the DCUI. Also, make sure the vlan carrying your mgmt traffic is globally defined in the ucsm, and allowed on the vnic in the service profile.
Also, doesn't hurt to compare VMNIC mac addresses with the UCSM VNIC macs to make sure the VMNICs line up with the UCSM VNICs you think they do.
Thanks,
Kirk...
11-14-2016 12:26 PM
The UCSM Vnics are essentially trunks. If you are not already doing so, you will want your VMware portgroup for your admin VMK traffic getting tagged in VMware with the correct admin vlan. You can set this from the DCUI. Also, make sure the vlan carrying your mgmt traffic is globally defined in the ucsm, and allowed on the vnic in the service profile.
Also, doesn't hurt to compare VMNIC mac addresses with the UCSM VNIC macs to make sure the VMNICs line up with the UCSM VNICs you think they do.
Thanks,
Kirk...
11-14-2016 12:40 PM
I needed to set the specific vlan in my ESX, not left blank or 4095. Thanks
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide