You will want to connect them using a LAG port configured as a VLAN trunk port.
Never heard of a level 2 or 3 LAG if your referring to layer 2 or layer 3 then a LAG is technically only layer 2. Depending on the hardware you might be able to assign an IP to a LAG making it layer 3 port but you would only do that if you were using it as a router interface.
You just want a normal port-channel between the two switches to carry your VLAN traffic. Pretty easy to do. 1. Create a LAG. 2. Add interfaces to LAG. 3. Configure LAG as a trunk port. 4. Add allowed VLANs to LAG trunk. 5. Connect switch1 lag interfaces to switch2 lag interfaces.
If you need specific commands for doing it Ill have to find the manual for those switches. I have never used that particular model of PowerConnect. After you get that done you should probably do some testing to make sure it works like you want.
Current I only have 4 GigE interfaces in the LAG between my 6248s but if I start running an iSCSI SAN I would probably add another 4 or use 10GigE interfaces. Given you have a total of 6 GigE interfaces on your SAN I would probably use at least 4 GigE interfaces in the LAG if you can.
I think you have a pretty standard config then. Two ports from controller1 to switch1 with one port to switch2 then two ports from controller2 to switch2 and one port to switch1. An odd number of ports seems weird. As long as all of them are capable of moving traffic you should be good to go if one of them in say a management port then it might have some problems.
Currently the switches do are not connected. I red an article which said, that in order to utilize EQ's load balancing, the scwithes should be interconnected. Only options awailabel in this switch iare one normal port or using LAG over several ports. Should this be done? And if so, should it be level 2 or 3 LAG?
OK, thanks. I think I have it now correctly configured. User guide does not know the word trunk (it is difficult when different vendors use same term for different purposes), but CLI guide seems to use is for connecting interfaces and lags to vlans.
Can you also give me advice how I should do following:
I have two vlans, 1 and 900 and all ISCSI traffic should stay in vlan 900 and 1 is used solely to management. If I put port 1 to vlan 1 and rest to vlan 900 all is well, exept I can not get trough to egaullogic management, which should be in vlan 1. But I use all interfaces of EQL to iscsi-interfaces and EQL does not support tagging for my understanding. So how I can get management traffic from port 1 to go to and only to eq's management interface. And also make sure that iscsi-traffic does not go trough port 1.
JustinY
1 Rookie
•
117 Posts
1
July 17th, 2010 18:00
You will want to connect them using a LAG port configured as a VLAN trunk port.
Never heard of a level 2 or 3 LAG if your referring to layer 2 or layer 3 then a LAG is technically only layer 2. Depending on the hardware you might be able to assign an IP to a LAG making it layer 3 port but you would only do that if you were using it as a router interface.
You just want a normal port-channel between the two switches to carry your VLAN traffic. Pretty easy to do.
1. Create a LAG.
2. Add interfaces to LAG.
3. Configure LAG as a trunk port.
4. Add allowed VLANs to LAG trunk.
5. Connect switch1 lag interfaces to switch2 lag interfaces.
If you need specific commands for doing it Ill have to find the manual for those switches. I have never used that particular model of PowerConnect. After you get that done you should probably do some testing to make sure it works like you want.
Current I only have 4 GigE interfaces in the LAG between my 6248s but if I start running an iSCSI SAN I would probably add another 4 or use 10GigE interfaces. Given you have a total of 6 GigE interfaces on your SAN I would probably use at least 4 GigE interfaces in the LAG if you can.
JustinY
1 Rookie
•
117 Posts
0
July 14th, 2010 17:00
I dont know much about Equallogic equipment. Do you have dual controllers or a single controller? I could not clearly tell from your question.
aleskinen
6 Posts
0
July 15th, 2010 02:00
I have dual controllers, both having 3 ethernet interfaces.
JustinY
1 Rookie
•
117 Posts
0
July 15th, 2010 11:00
I think you have a pretty standard config then. Two ports from controller1 to switch1 with one port to switch2 then two ports from controller2 to switch2 and one port to switch1. An odd number of ports seems weird. As long as all of them are capable of moving traffic you should be good to go if one of them in say a management port then it might have some problems.
aleskinen
6 Posts
0
July 16th, 2010 03:00
Currently the switches do are not connected. I red an article which said, that in order to utilize EQ's load balancing, the scwithes should be interconnected. Only options awailabel in this switch iare one normal port or using LAG over several ports. Should this be done? And if so, should it be level 2 or 3 LAG?
aleskinen
6 Posts
0
July 19th, 2010 02:00
OK, thanks. I think I have it now correctly configured. User guide does not know the word trunk (it is difficult when different vendors use same term for different purposes), but CLI guide seems to use is for connecting interfaces and lags to vlans.
Can you also give me advice how I should do following:
I have two vlans, 1 and 900 and all ISCSI traffic should stay in vlan 900 and 1 is used solely to management. If I put port 1 to vlan 1 and rest to vlan 900 all is well, exept I can not get trough to egaullogic management, which should be in vlan 1. But I use all interfaces of EQL to iscsi-interfaces and EQL does not support tagging for my understanding. So how I can get management traffic from port 1 to go to and only to eq's management interface. And also make sure that iscsi-traffic does not go trough port 1.