Unsolved
1 Message
0
753
November 1st, 2021 10:00
vxrail with external vcenter on separate vlan
We are installing a new vxrail cluster using an existing Customer-Supplied vcenter server.
The Vcenter is currently using VLAN402, whereas the new vxrail cluster management network will use VLAN404.
During the deployment wizard, when we specify the vcenter VLAN ID as 402 we receive a Validation error. It seems that the wizard will not allow deployment unless the vcenter server is in the same vlan 404 as the ESXI and VXrail manager.
Changing the Vcenter VLAN is not an option for us due to customer security restrictions.
We have not found any documentation or KB that specifies that the Vcenter must be in the same VLAN as the ESXi and Vxrail manager.
However we cannot proceed with the new cluster install..
has anyone encountered this? is there a workaround?
No Events found!
DELL-Naoyuki K
4 Operator
•
1.9K Posts
0
November 1st, 2021 11:00
I think External vCenter can be placed on different VLAN/Subnet from management network of VxRail.
The requirement is that VxRail component such as VxRail Manager and ESXi can reach external vCenter.
If it resides in the same subnet, it should be in the same VLAN in many case (not always depends on the network environment)
If it's in different subnet, it is required to setup default gateway, routing, name resolution and so forth, in order to make sure that both can reach each other.