Connect Powerconnect M6348 with Powerconnect 2748

Thanks Josh

So I put port 1-4 on 5324 in LAG 1 (Trunk) and port 33-34 on M6348 in LAG 2 (Trunk) and connect them together?

And If I then have two 5324 and two M6348 I should make fire LAGS then?

Just need to understand it correctly :)

What about my connection with the ISCSI

Port 10-15 on 5324 is ACCESS PVID 10 and connected to the ISCSI and Port 19-20 is set to Trunk and connected to M6220 (No LAG)

And port 1-4 on M6220 is ACCESS PVID 10, and port 17-18 is set to Trunk (No Lag) and are connected to port 19-20 on 5324

Thanks

Thomas

Great, I will create the LAGS between them then.

If I connect a computer directly to the 5324 and make the connected port ACCESS  PVID 10, then I can ping.

If I do the same to the M6220 I can't ping. So thinking there is something with the configuration between them. The ports I have connected from the 5324 to the M6220 is trunk in both ends.

Is this correct? Should it be LAG since there is more than one cable connected between them?

Thanks

Thomas

Yes, that's right Thomas, make 4 LAGs. For the iSCSI can you ping the MD3000i from either the M6220 or the 5324?

Ok, I will try to make LAG on those as well.

For the ports that goes to the blade servers should them be ACCESS or something else?

It shouldn't have to be a LAG, but it might help.

The ports to the blade servers should be access. Does VLAN 10 on the 5324 have an IP address? Can you ping that from a blade? the blades can ping each other on VLAN 10 right? I think the issue is something with the trunk between the M6220 and the 5324 since if you connect something directly to the 5324 it works.

Ok, then I at least have all port correctly configured for the ISCSI, it's only the connection between the switches then most likely.

I can ping between the blades on vlan 10

No vlan 10 doesn't have any ip on the 5324, maybe that's what's missing?

For that vlan we don't use any gateway either.

You shouldn't need an IP for the VLAN, we could just use it for testing purposes to see if traffic is getting that far. So for now try giving it an IP and see if that is pingable, I think it will fail and that will prove that it is the connection between the switches that is the problem.

Added an IP to the vlan on both 5324 switches, but couldn't ping those from the blades.

Did the same on M6220, and pinged from the blades successfully to the management ip's on vlan 10.

So vlan 10 works fine between the blades and to the M6220 but not between m6220 and the 5324 switches.

The configuration between them are:

two ports on each 5324 is set to Trunk and PVID 1

two ports on each M6220 is set to Trunk and PVID 1

At this time there is LAG configured for these ports.

Thanks

Thomas

Is it an LACP or a static LAG?

I guess it is a LACP if I don't choose anything when creating the LAG? Or when can I check it?

When you created it did you use the command channel-group mode on or active? active is LACP, on is static.

Did use the web interface for creating them so I guess that's with LACP active then.?

Yeah, that should be active, which means it is possible that the link isn't forming correctly. If you are on site can you see if there are link lights, if not you may want to try turning off the LAG and seeing if the M6220 can ping the 5324 then.