UNSOLVED
MXL switch and M620 connectivity issues
Hi all,
I'm fairly new to blade chassis/networking and have been tasked with setting up a M1000e with 12 blades with 4 mxl fabric switches splitting 4 VLANs across 2 VLT pairs (management & production in A2 & B1 / iSCSI & vMotion in A1 & B2). There's a port channel from fabric A2 & B1 to a TOR N4032 (which will be VLT paired as our new core network).
So far i have the management and production switches configured and i've got one blade server installed in slot 1 (m620). I see te 0/1 as up and on the default vlan (untagged) and both production and management (tagged).
Port Description Status Speed Duplex Vlan
Te 0/1 Up 10000 Mbit Full 1,405,410
Slot 1 has ESXi installed on it and if i run a ring test i get no responses from anything on the management or production VLANs.
If i check the mac address table on fabric B1 all i see is port channel (101) with no reference to the MAC address at te 0/1.
VlanId Mac Address Type Interface State
1 14:18:77:d9:16:b1 Dynamic Po 101 Active
1 14:18:77:d9:16:b2 Dynamic Po 101 Active
1 44:a8:42:3b:d0:23 Dynamic Po 101 Active
405 00:00:74:df:0a:3b Dynamic Po 101 Active
405 00:00:74:eb:79:64 Dynamic Po 101 Active
405 00:01:e8:8b:f0:be Dynamic Po 101 Active
405 00:0c:29:5c:d9:e3 Dynamic Po 101 Active
405 00:12:79:d6:a0:ea Dynamic Po 101 Active
405 00:12:79:d6:a0:eb Dynamic Po 101 Active
405 00:15:c5:ef:d9:ad Dynamic Po 101 Active
405 00:18:fe:69:fd:42 Dynamic Po 101 Active
405 00:19:b9:dd:dd:15 Dynamic Po 101 Active
405 00:19:b9:dd:dd:17 Dynamic Po 101 Active
405 00:19:b9:de:17:95 Dynamic Po 101 Active
405 00:19:b9:de:17:97 Dynamic Po 101 Active
405 00:1b:21:24:12:3b Dynamic Po 101 Active
405 00:20:4a:71:04:ae Dynamic Po 101 Active
405 00:20:4a:71:04:af Dynamic Po 101 Active
405 00:20:4a:71:04:b0 Dynamic Po 101 Active
405 00:20:4a:71:04:b1 Dynamic Po 101 Active
405 00:20:4a:71:04:b2 Dynamic Po 101 Active
405 00:20:4a:71:04:b3 Dynamic Po 101 Active
405 00:20:4a:71:04:b4 Dynamic Po 101 Active
I'm at a loss with why this would be. Does anyone have any ideas?
thanks
.
thanks again for the response Daniel.
I've done a bit more digging on this morning. If I don't configure the ESXi host with a VLAN it can ping the management interface of the TOR 4032 successfully.
If I enter the management VLAN again on the ESXi host I now see the interface displaying on the MXL switch mac address table, however I get no response from the 4032 (default gateway).
Any ideas? I'm stumped!
Thanks
Hi Daniel,
Sorry I've been away on holiday so just picking this back up now.
The host is tagged on both the Production (405) and Management (410) VLANs so I should be able to ping both these VLANs on the N4032. Both these VLANs have IP addresses on the N4032.
I still can't work this one out.
Hi Daniel,
Thanks for your help with this. I've finally managed to work out what the problem was. The switching on the MXLs was all fine, however there had been a native vlan configured on the port-channel on the N4032. As soon as I changed that so it wasn't on the management VLAN the whole thing came to life.
All working now!
thanks again.
Marky80
5 Posts
1076
0
Posted August 24th, 2016 09:00
Hi Daniel,
Thanks for your response.
The server has a daughter card in fabric A and a mezz card in fabric B (dual port). I've used
I have another port channel (100) for linking A2 and B1 together. Port channel 101 is being used to provide connectivity to our N4032 passing tagged management and production traffic.
As for the NIC config, I have selected port 1 on the mezz card in fabric b to be used for production and management.
If you need any other information please let me know.
thanks