Dell MX7000 - Blade's iDRAC configured and accessible. ESXi on same VLAN not accessible.

[eptesicus]

I'm scratching my head on this one.

I have a Dell MX7000 in my lab that I just got. It has 7x MX740c blades, and a single MX9116N switch. Since I only have 1x MX9116N switch at the moment, SmartFabric is not available. "Old school" CLI management on this one for now... All firmware is current to the most recent Dell validated versions.

iDRAC of the blade in sled 7 has an IP of 10.0.50.27, and ESXi (v8, using the Dell image) is 10.0.50.17, with vLAN 50 tagged in ESXi (tried with and without tagging it). iDRAC does not have the vLAN tagged. I have also tried configuring ESXi to be on another VLAN with no luck. Also booting into Ubuntu, I can't access the network either.

The problem... I can't access or ping ESXi. I can't even ping ESXi from the MX9116N switch.

Here's my MX9116N config: MX9116N Config - Pastebin.com

Here's an export of my template for all the blades: MX740c Optimized - Low Noise - Template - Pastebin.com

 

[Mike75020000]

I come from a primarily Cisco network engineering background, so, I may be way off base.

Looking at your configs, I see the SVI (layer 3) for vlan50. But. I don't see it's layer 2 brethren in your configs. (reminder, i'm cisco background, and in cisco, you have to have both)

Consider something like

Conf t
vlan 50
name (description maybe?) v50_MGMTPhysical


then put your two IDRACs interfaces in switchport mode access, and use the layer 2 tag on the physical interface that you're connecting your idracs to.

 

[Mike75020000]

Also, on switches, you can <usually> ping from a certain interface.

Get your layer 2 tag set up as described above (ish)

Put your two idrac physical interfaces in switchport mode access, switchport access vlan 50

THEN, if you're still having troubles, consider pinging from your SVI for Vlan.

On cisco switches, some form of: ping 10.0.50.27 source interface vlan 50 (use your question marks on the CLI, to help you with this command)

 

[eptesicus]

Thanks for the reply!

My understanding is that there's no VLAN database configuration like the Cisco world, and the entries starting on line 86 of the switch config are the equivalent.

Also, here's my output of 'show vlan'.


VII-MXFABA01# show vlan
Codes: * - Default VLAN, M - Management VLAN, R - Remote Port Mirroring VLANs,
@ - Attached to Virtual Network, P - Primary, C - Community, I - Isolated,
S - VLAN-Stack VLAN
Q: A - Access (Untagged), T - Tagged
NUM Status Description Q Ports
* 1 Inactive A Eth1/1/17:1,1/1/18:1,1/1/19:1-1/1/19:4,1/1/20:1-1/1/20:4,1/1/21:1-1/1/21:4,1/1/22:1-1/1/22:4,1/1/23:1-1/1/23:4,1/1/24:1-1/1/24:4,1/1/25:1-1/1/25:4,1/1/26:1-1/1/26:4,1/1/27:1-1/1/27:4,1/1/28:1-1/1/28:4,1/1/29:1-1/1/29:4,1/1/30:1-1/1/30:4,1/1/31:1-1/1/31:4,1/1/32:1-1/1/32:4,1/1/33:1-1/1/33:4,1/1/34:1-1/1/34:4,1/1/35-1/1/38,1/1/39:1,1/1/40:1,1/1/41:1-1/1/41:4,1/1/42:1-1/1/42:4,1/1/43,1/1/44:1,1/71/9-1/71/16,1/72/9-1/72/16,1/73/1-1/73/16,1/74/1-1/74/16,1/75/1-1/75/16,1/76/1-1/76/16,1/77/9-1/77/16,1/78/1-1/78/16,1/79/1-1/79/16,1/80/1-1/80/16,1/81/1-1/81/16,1/82/1-1/82/16
A Po1,13
50 Active v50_MGMTPhysical T Eth1/1/1-1/1/16,1/1/41:1-1/1/41:4,1/1/42:1-1/1/42:4,1/71/1-1/71/8,1/72/1-1/72/8,1/77/1-1/77/8
T Po1,13
51 Active v51_MGMTVirtual T Eth1/1/1-1/1/16,1/1/41:1-1/1/41:4,1/1/42:1-1/1/42:4,1/71/1-1/71/8,1/72/1-1/72/8,1/77/1-1/77/8
T Po1,13
52 Active v52_vMotion T Eth1/1/1-1/1/16,1/1/41:1-1/1/41:4,1/1/42:1-1/1/42:4,1/71/1-1/71/8,1/72/1-1/72/8,1/77/1-1/77/8
T Po1,13
53 Active v53_vSAN T Eth1/1/1-1/1/16,1/1/41:1-1/1/41:4,1/1/42:1-1/1/42:4,1/71/1-1/71/8,1/72/1-1/72/8,1/77/1-1/77/8
T Po1,13
54 Active v54_iSCSI T Eth1/1/1-1/1/16,1/1/41:1-1/1/41:4,1/1/42:1-1/1/42:4,1/71/1-1/71/8,1/72/1-1/72/8,1/77/1-1/77/8
T Po1,13
60 Active v60_MGMTUser T Eth1/1/1-1/1/16,1/1/41:1-1/1/41:4,1/1/42:1-1/1/42:4,1/71/1-1/71/8,1/72/1-1/72/8,1/77/1-1/77/8
T Po1,13
70 Active v70_DL T Eth1/1/1-1/1/16,1/1/41:1-1/1/41:4,1/1/42:1-1/1/42:4,1/71/1-1/71/8,1/72/1-1/72/8,1/77/1-1/77/8
T Po1,13
80 Active v80_Web T Eth1/1/1-1/1/16,1/1/41:1-1/1/41:4,1/1/42:1-1/1/42:4,1/71/1-1/71/8,1/72/1-1/72/8,1/77/1-1/77/8
T Po1,13
90 Active v90_Remote T Eth1/1/1-1/1/16,1/1/41:1-1/1/41:4,1/1/42:1-1/1/42:4,1/71/1-1/71/8,1/72/1-1/72/8,1/77/1-1/77/8
T Po1,13
100 Active v100_Guest T Eth1/1/1-1/1/16,1/1/41:1-1/1/41:4,1/1/42:1-1/1/42:4,1/71/1-1/71/8,1/72/1-1/72/8,1/77/1-1/77/8
T Po1,13
110 Active v110_Wiferino T Eth1/1/1-1/1/16,1/1/41:1-1/1/41:4,1/1/42:1-1/1/42:4,1/71/1-1/71/8,1/72/1-1/72/8,1/77/1-1/77/8
T Po1,13
120 Active v120_IOT T Eth1/1/1-1/1/16,1/1/41:1-1/1/41:4,1/1/42:1-1/1/42:4,1/71/1-1/71/8,1/72/1-1/72/8,1/77/1-1/77/8
T Po1,13
130 Active v130_Cams T Eth1/1/1-1/1/16,1/71/1-1/71/8,1/72/1-1/72/8,1/77/1-1/77/8
T Po1,13
150 Active v150_Test T Eth1/1/1-1/1/16,1/71/1-1/71/8,1/72/1-1/72/8,1/77/1-1/77/8
T Po1,13
192 Active v192_TempGeneric T Eth1/1/1-1/1/16,1/71/1-1/71/8,1/72/1-1/72/8,1/77/1-1/77/8
T Po1,13
200 Active v200_Backups T Eth1/1/1-1/1/16,1/1/41:1-1/1/41:4,1/1/42:1-1/1/42:4,1/71/1-1/71/8,1/72/1-1/72/8,1/77/1-1/77/8
T Po1,13
4004 Active T Mgmt1/1/1
M 4020 Active A Mgmt1/1/1



You bring up a good point about pinging from the interface...

As mentioned before, pinging iDRAC from the switch (same as if I'm pinging from my workstation), SUCCEEDS:
VII-MXFABA01# ping 10.0.50.27 -c 4
PING 10.0.50.27 (10.0.50.27) 56(84) bytes of data.
64 bytes from 10.0.50.27: icmp_seq=1 ttl=64 time=0.216 ms
64 bytes from 10.0.50.27: icmp_seq=2 ttl=64 time=0.255 ms
64 bytes from 10.0.50.27: icmp_seq=3 ttl=64 time=0.286 ms
64 bytes from 10.0.50.27: icmp_seq=4 ttl=64 time=0.283 ms

--- 10.0.50.27 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 73ms
rtt min/avg/max/mdev = 0.216/0.260/0.286/0.028 ms

Pinging iDRAC from the VLAN 50 interface, FAILS:
VII-MXFABA01# ping -I vlan50 10.0.50.27 -c 4
ping: Warning: source address might be selected on device other than br50.
PING 10.0.50.27 (10.0.50.27) from 10.0.50.8 br50: 56(84) bytes of data.

--- 10.0.50.27 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 76ms

Pinging iDRAC from what I believe is the blade's interface from the switch, FAILS:

VII-MXFABA01# ping -I ethernet1/1/13 10.0.50.27 -c 4
ping: Warning: source address might be selected on device other than e101-013-0.
PING 10.0.50.27 (10.0.50.27) from 10.0.50.8 e101-013-0: 56(84) bytes of data.

--- 10.0.50.27 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 55ms



Now, if I ping ESXi management from the switch, again, it FAILS:

VII-MXFABA01# ping 10.0.50.17 -c 4
PING 10.0.50.17 (10.0.50.17) 56(84) bytes of data.
From 10.0.50.8 icmp_seq=1 Destination Host Unreachable
From 10.0.50.8 icmp_seq=2 Destination Host Unreachable
From 10.0.50.8 icmp_seq=3 Destination Host Unreachable
From 10.0.50.8 icmp_seq=4 Destination Host Unreachable

--- 10.0.50.17 ping statistics ---
4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 68ms


Pinging ESXi management from the VLAN 50 interface, SUCCEEDS:

VII-MXFABA01# ping -I vlan50 10.0.50.17 -c 4
ping: Warning: source address might be selected on device other than br50.
PING 10.0.50.17 (10.0.50.17) from 10.0.50.8 br50: 56(84) bytes of data.
64 bytes from 10.0.50.17: icmp_seq=1 ttl=64 time=0.459 ms
64 bytes from 10.0.50.17: icmp_seq=2 ttl=64 time=0.439 ms
64 bytes from 10.0.50.17: icmp_seq=3 ttl=64 time=0.515 ms
64 bytes from 10.0.50.17: icmp_seq=4 ttl=64 time=0.459 ms

--- 10.0.50.17 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 71ms
rtt min/avg/max/mdev = 0.439/0.468/0.515/0.028 ms


Pinging ESXi management from what I believe is the blade's interface from the switch, FAILS:

VII-MXFABA01# ping -I ethernet1/1/13 10.0.50.17 -c 4
ping: Warning: source address might be selected on device other than e101-013-0.
PING 10.0.50.17 (10.0.50.17) from 10.0.50.8 e101-013-0: 56(84) bytes of data.
^C
--- 10.0.50.17 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 72ms




My networking abilities need work and my brain is spent. I'm not sure what to do with this information. Haha.

 

[eptesicus]

I just realized that the iDRAC is a "dedicated" NIC and is not set to one of the two NICs that ESXi would be using, which I suppose explains why I can access and ping iDRAC... I guess I don't know where/how/why/whatever to get the server OS to get networking working...

http://imgur.com/a/ZWhKKU9

 

[eptesicus]

Curiously, I changed the iDRAC NIC there to LOM1, and of course lost access and dropped ping.

 

[Mike75020000]

Heres to hoping you have a crash cart nearby?

 

[eptesicus]

Heres to hoping you have a crash cart nearby?

Well, since it's all virtual and iDRAC isn't a physical port, I'm just redeploying my template in the chassis to that blade to reconfigure everything.