When you have the stacking cable and because you only have one procurve: setup a LAG that span both M6348(max 8 port per LAG) to the HP. Without stacking cable: 1. The way you have it done right now is correct. 2. you can setup 2 different LAG that connect to the HP, and 1 LAG between the M6348.  But you have to change the spanning-tree cost on one of the LAG between the HP and M6348 to 200000 so that this LAG will be the alternate or backup path. 
Hey there! I was looking for some assistance in what I'm doing wrong with our new switches. Now keep in mind I have never really dealt with trying to create LAGs. First I would like to explain the network a little: (2) PowerConnect M6348(1) M1000e blade enclosure(2) Blade servers (used for ESXi 4.1)(2) PS6000e iSCSI SANs with Module 7(1) Procurve switch (main)(2) Checkpoint UTM firewall (Active/Active cluster).   So the way it sits now is the firewalls are connected to the Procurve switch (main switch). Here is where I need assistance. I know we need to create a connection between the PowerConnect switches. So since we don't have the stacking cables yet I wanted to try it with LAG. I setup the LAG on both switches for ports 47 and 48. I connected them together. Now when I connect the procurve to one of the PowerConnect switches it takes down the network. How can I connect the two PowerConnect switches together since this is required for the redundancy of the PS6000e SANs and connect the procurve to them without creating any loops and the network going down?
M1000e with two PowerConnect M6348 modules [Assistance Needed]