Two common issues:

- The VLANs are not on the Inter Switch Links (in case of two ToR switches)

- The initial state on the Nodes is not only one NIC connected to the standard switch, but more than one.

The best way is to work with support.

Hi Troy,

We have faced the same issue, have you found a troubleshooting method for this? and not resort to RASR reset? Or can you clarify or give examples on the issue you stated.

Thank you.

Hi,

I had the same issue before Christmas on 4.5..215, but only on some of the ESXi hosts in the cluster.

Fixed it manually.

Login to vSphere.

Remove the second physcal NIC from the existing standard vSwitch.

Add this as an uplink on the distrituted vSwitch.

Click "Try Agan".

Best of luck,

Kev

Hi All

I solved that case, I just give native vlan on my configuration switch.

I used :

- vlan 0 for management and vcenter ---> this should untagged traffic

- vlan 106 for Virtual VM Switch

Vxrail has 4 port:

port 0 : Management

Port 1 : Virtual Mechine

Port 2 : VSAN

Port 3 : VMotion

Management used port 0, and on my vxrail I used VLAN 0, that's mean untagged traffic, I need to connect with my existing network, so I set :

- Switchport mode trunk

- switchtrunk native vlan 130.

Vlan 130 just for management.

Virtual machine used port 1, as my vcenter also is virtual machine and used vlan 0 and the traffic pass through port 1 so I just give same configuration.

- switchport mode trunk

- switchport trunk native vlan 130

the rest of port I just set switchport mode trunk on my physical switch

Hi Kev,

Good day.

when you say vSphere, what node specifically? As we don't have vCenter set up yet.

Thank you for your response.

Step 38 might have multiple different sources. Just be sure you don't put the cluster into a non-supported mode. I would strongly advise to open an SR with VxRail Technical Support.

Revan-Simbolon  - VxRail default ports after installation differ on Quanta and Dell nodes. Yours looks like a Quanta, and vmk0 is MARVIN Management, while vmk1 is Management Network and set as the default Management IP. In addtion, both vmks are tagged for Management. On Dell nodes it is vmk0 & vmk2.

VxRail has prerequisites to be properly installed. Not meeting them will cause issues.

Good read for VxRail & Network: https://www.emc.com/collateral/guide/h15300-vxrail-network-guide.pdf

And I still strongly suggest opening an SR for any VxRail related issues for which you are not able to find a KB with solution.

Thanks Kev!!!  

Works perfectly