thanks for the response. I messed around quite a bit since posting this and eventually I managed to resolve the issue yesterday using the document linked above "Deployment of Dell M-Series blade switches in a Cisco Catalyst Network" <- This is a great read! A lot of my worries about adding power connect into our environment were removed because of this. I started again with my configs and was much more methodical in working through the process. Step 1: Create lag between 6224 and 6509, configure trunking and confirm working on something other than VLAN1 Step 2: Create lag between M6348's and 6224, configure as switchport general and tagg traffic Step 3: Configure Each blade interface as trunks It really was that simple. I got confused because from the 6224 I could ping everything on our network as long as it wasn't connected directly to the 6224. The reality was I hadn't been explicit enought with the port channel create between the Cisco and powerconnect.    
Hi, First a little background. Our network is primarily Cisco based and as such we run VTP. Recently we bought the following: On the existing network all management is performed on VLAN 1 (10.44.1.1/21). Existing VLANS include our training VLAN 32 (10.44.32.1/21). No stacking is in place at this point, all switches are stand alone. This is what I've done so far starting with a trunk from the existing cisco 6509 to the Dell 6224 Cisco 6509 - Link to Dell 6224 Dell 6224 Test 1 Dell m6348's Test 2
M6348 Configuration