Hi Absalah,

The physical layout of what you have should be good, the only thing to confirm would be the chassis midplane model. If you can PM me the service tag of the chassis, I can confirm that piece as well. As for VLAN config, that could potentially be an issue. The MXL 10/40 GbE does have layer 3 functionality, but if it is possible, I would test without VLANs. This way you can try to isolate pieces of the config. 

Thanks for your reply, here is the ST of the chassis: {{Svc tag removed by Moderator}}

That chassis does have the second revision backplane. With that being the case the physical configuration should be good. Testing without VLANs would be the next thing I test, just as a simplified configuration.

I do not believe you would need a portchannel for this.

VLAN1 and untagged should be fine, so I would leave it alone. I thought you were saying that you were using tagged traffic.

It can, depending on what driver is being used. I've seen the E1000 driver cause a number of issues, for example. If you are not using the Dell customized ESXi .iso file, you might use that on one of the nodes as a test, so that you know the drivers are available.

Server profiles are going to affect out of band settings, like BIOS and iDRAC configuration. I would focus on getting a node communicating first, then create a profile off of the working node to apply to the others.

Thanks Dylan, now i have some questions regarding this:

Do I have to create a portchannel between the nexus and the io module?

I only have vlan 1 (default) on the mxl with all internal tengig interfaces in it as untagged, do I need to change this setup?

Would the driver of the NIC that is installed with the ESXi be responsible for the problem?

Do I need to apply server profiles to the blades before i try the communication?

Thanks,