This post is more than 5 years old
1 Rookie
•
78 Posts
0
49567
February 13th, 2015 06:00
M8024-k stack (pair) to M3048 stack (pair) Lags, VLANS and port groups?
Hi All
I am getting more confused by the minute. I have a pair of M8024-k blade switches in a M1000e enclosure, on the outside I have a pair of N3048 switches.
I seem to have the stacking working on the M8024-k but I found a config guide for Simple mode that says take port 17-20 out of the Port Aggregation group on the pair, and leave the stack ports and the internal ports in the PA group. When I do this they won't stay out of the group, whether I do it in the CLI or the GUI.
Does anyone have a config guide which shows how I can Trunk the 2 pairs together and allow 4 vlans as I keep coming up with no access to the blade servers in the enclosure? Do I have to come out of simple mode on the M8024-k to achieve this?
Any help gratefully received.
Jaxon62
1 Rookie
•
78 Posts
0
February 16th, 2015 05:00
Hi , Thank you for the information, the Channel-group is working correctly now. Did you mean for me to create the trunk on both switches or just the N3048? I can ping the M8024 gateway now, I couldn't before, but I am unable to ping the blade nic.
Jaxon62
1 Rookie
•
78 Posts
0
February 17th, 2015 04:00
Both stacks are set, I have added some routing and I can ping the VLAN interface addresses on M8024 stack from the N3048 and my desktop.
The VLANs basically pass through the M8024 from the VMware environment on the M620 blades also in the M1000e enclosure (that was why I started with Simple Mode). They pass to the rack switches as part of the environment is still physical, 7 servers on VLAN 170 and 3 on VLAN 32. I am using VLAN 11 for Virtual Management and VLAN 10 for Management.
I am unable to ping the ESX NIC from the M8024 and vice versa ( I have added the NIC to a VLAN and the 4065 VLAN and left it without - none of them seem to make a difference). The VLAN interface is x.x.11.241 and I can ping that from the 3048 and my desktop.
Jaxon62
1 Rookie
•
78 Posts
1
February 22nd, 2015 23:00
Hi Daniel C
Thank you for all your help but it looks like it was a hardware location problem, the M8024-k was in slots B1 and B2 which does not allow use of the 4 onboard NICs - therefore no connection to the switch for NIC 0. The switches in A1and A2 now result in NIC 0 being active and pings are working.
Thanks again for your time.