Unsolved
This post is more than 5 years old
3 Posts
0
16249
February 6th, 2012 19:00
Stacked 6248 pair - Cannot ping from one switch to the other in same VLAN
I have two 6248 switches stacked with a very simple config:
Two VLANs 2 and 3. Each VLAN has same ports across both switches.
VLAN 2 is for VM Network, Network Management, and vmotion
VLAN 3 is for iSCSI traffic.
I have my first ESXi 5 server management network port connected to the master switch. With a laptop connected to the stby switch in the same VLAN, it cannot ping the management network IP. When connected to the same switch and VLAN, a ping is successful.
As I understand it, all data should traverse the stacking ports without any special config. Any insight would be appreciated.
No Events found!
sketchy00
203 Posts
0
February 7th, 2012 07:00
I just spun up a stack of 6248's on my LAN network this weekend, and have a pair of 6224's for my dedicated iSCSI network, so I feel I can comment on this.
You are right, there will not need to be any special steps to pass the data between switches. The stacking modules essentially extend the circuiting.
You might want to re-evaluate your approach how you have your VLANs set up for your ESX network. You can't/shouldn't have your VM network, Service Console, and VMotion ride over the same VLAN. Same ports, sure, but not the same VLAN. You don't mention how many NIC ports you have on each host, but lets assume 6. Here is one way to set them up.
Switch
2 pairs for Service Console Network. Tagged
2 pairs for vMotion Network. Tagged
2 pairs for your VM network. Untagged
ESX:
1st vSwitch (vSwitch0)
Two physical adapters associated with it.
VMkernal Portgroup. Set to be tagged traffic for Service Console
Management Porgroup. Set to be tagged VM traffice for management
VMotion Porgroup. Set to be tagged VMotion traffic
2nd vSwitch (vSwitch1)
Two physical adapters associated with it
2 VMKernal Ports for iSCSI traffic (untagged)
1 VM Port group if you use guest attached volumes (untagged)
3rd vSwitch (vSwitch)
1 VM Portgroup for your LAN traffic used by your VMs. (untagged)
If you have an opportunity, you will find most best practices suggest complete seperating your iSCSI traffic onto seperate switches. The laundry list of reasons for doing so is long, and will save you lots of headache later.
itforme.wordpress.com/.../reworking-my-powerconnect-6200-switches-for-my-iscsi-san
dfolwell
3 Posts
0
February 8th, 2012 04:00
The solution was simple, but annoying. A reload was required. Typical Dell fashion.
My VMware config is simple because of limited NIC ports; 6.
VLAN2 has the Management Network, vmotion and VM Network. (see the config below before frowning)
VLAN3 for iSCSI
all untagged
VLAN2
vSwitch0 - vmnic0 and 1
Management Network - vmnic0 with vmnic1 as standby
vmotion - vmnic1 and vmnic0 as standby
vSwitch1 - vmnic2 and 3
VM Network
VLAN3
vSwitch2 - vmnic4
iSCSI-0
vSwitch3 - vmnic5
iSCSI-1
MPIO configured with Round Robin
Storage is an Equallogic PS4100.
Just keeping it simple.
sketchy00
203 Posts
0
February 8th, 2012 07:00
No worries. By the initial question, it was a bit tough to tell what your environment might have actually looked like. Good to hear it is working for you.
vedru
1 Message
0
July 15th, 2012 21:00
Not sure if you are still monitoring this thread, but I appear to be having same issue and was wondering if you could post what that simple but annoying solution was?