11-28-2017 10:33 PM - edited 03-01-2019 01:22 PM
Hi folks,
I've recently deployed a HyperFlex 2.1 with the recommended setup (using different VLANs for all mgmt and data networks) which works perfectly fine. Customer is using some VMs on VLAN1 (I know it's not recommended and should be some other VLAN instead) and changing it kinda hard at the moment. I created a vSwitch port group for VLAN1 on vCenter, i added VLAN1 to vNIC Templates on UCSM and make sure VLAN1 is also on trunk ports between FIs and upstream switch.
When i put a VM to VLAN1 port-group on vCenter, i can see that VM's MAC address registered to FI's by checking the MAC address table from CLI, same MAC address is also in upstream switch's MAC address table too. But VM can not ping it's default gateway and therefor can not be reached from anywhere.
I know very well that VLAN1 can not be used during the installation of HX DP but is there anything prevents us to use VLAN1 after the installation?
All comments are welcomed!
Cheers!
Solved! Go to Solution.
02-01-2018 04:56 PM
VLAN 1 is the default native VLAN in a UCS domain
VLAN 1 cannot be pruned out of the FIs
However, it is not automatically added to the vNIC Template vm-network-a and vm-network-b
Add VLAN 1 to both vNIC templates and set is as native if it's the native VLAN on the UCS domain
In VMware vSphere, when creating the port group, be sure that it does not have any VLANs assigned, i.e. None (0)
This will ensure that it uses the native VLAN allowed on the vmnics (vmnic4, vmnic5)
12-17-2017 11:13 PM
Well I don't think you can utilize vlan 1 before or after Hyperflex deployment
Since Cisco do not allow to use vlan 1 (native) for deployment (not secure)
02-01-2018 04:56 PM
VLAN 1 is the default native VLAN in a UCS domain
VLAN 1 cannot be pruned out of the FIs
However, it is not automatically added to the vNIC Template vm-network-a and vm-network-b
Add VLAN 1 to both vNIC templates and set is as native if it's the native VLAN on the UCS domain
In VMware vSphere, when creating the port group, be sure that it does not have any VLANs assigned, i.e. None (0)
This will ensure that it uses the native VLAN allowed on the vmnics (vmnic4, vmnic5)
02-12-2018 11:43 PM
Hi Clifford, sorry for the late response but yes, as you said it's possible to use VLAN1 after the installation, it was another network issue that prevented VM to ping it's default gateway but now everything works perfectly fine. Thank you for the explanation.
02-15-2018 10:52 AM
You're welcome, Burak
02-15-2018 11:32 AM
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