Connect Powerconnect M6348 with Powerconnect 2748

Thanks for your reply.

We have the VLAN 1 and 150 created on both the 2748 and M6348 switch.

No the ports aren't setup as LAG, maybe that's why I can't get it to work?

On the M610 blade we have installed Hyper-V and have virtual machines, these are assigned to different VLAN on virtual machine level and not host level.

Plugging all of those ports from one switch to another, without a LAG, is are going to create a loop, which will disable some of the ports. I would start out with one cabled connection from the M6348 to the 2748.

Checkout this article:

social.technet.microsoft.com/.../1306.hyper-v-configure-vlans-and-vlan-tagging.aspx

With some quick searching I am sure you can find some similar articles. It talks about VLAN tagging form within hyper V. I would run through the checklist and make sure the virtual environment is setup correctly.

I have a few questions, to get a better understanding of your topology.

You have your servers connected to Trunk ports. Are these servers setup to send out tagged traffic from multiple VLANs?

Ports 33-35, are they setup as a LAG?

What VLANs do you have created? What traffic is intended for which VLAN?

Thanks for your feedback, I will look over the article and look at LAG setup for the connection between the switches.

Update:

Needed to change the 2748 to a 5324 since it was something wrong with it, it didn't respond all the time and booted when it wanted.

I have created LAG 1 and 2 on the 5324 and the same on M6348 and M6220, but can't connect to the blade servers or ISCSI

Port 24 is the port I have connected to my firewall where my computer is connected.

Port 1 and 2 is to the blade server on port 33-34

Port 8-12 is the ISCSI connection between M3000i and M6220 switch on port 17

Config for 5324

interface port-channel 1

switchport mode trunk

exit

interface port-channel 2

switchport mode general

exit

interface ethernet g24

switchport mode general

exit

vlan database

vlan 10,150

exit

interface port-channel 2

switchport general pvid 10

exit

interface vlan 10

name "ISCSI VLAN"

exit

interface vlan 150

name "Internet Powertech"

exit

interface range ethernet g(1-4)

channel-group 1 mode on

exit

interface range ethernet g(8-12)

channel-group 2 mode on

exit

interface vlan 1

ip address 10.145.19.2 255.255.255.0

exit

ip default-gateway 10.145.19.1

username Administrator password 569a34adc229bf323b44c594f27b71b2 level 15 enc

rypted

ip ssh server

Config for M6348

!Current Configuration:

!System Description "PowerConnect M6348, 5.1.1.7, VxWorks 6.6"

!System Software Version 5.1.1.7

!System Operational Mode "Simple"

!

configure

mode simple

slot 2/0 1    ! PowerConnect M6348

stack

member 2 1    ! PCM6348

exit

port-aggregator group 2

no add interface Gi2/0/38-40

exit

!

port-aggregator group 1

add interface Gi2/0/38-40

exit

!

port-aggregator group 2

interface Gi2/0/2

switchport general allowed vlan add 1-208

--More-- or (q)uit

exit

interface Gi2/0/18

switchport general allowed vlan add 1-208

exit

exit

username "root" password e6e66b8981c1030d5650da159e79539a privilege 15 encrypted

line telnet

login authentication defaultList

enable authentication enableList

password 569a34adc229bf323b44c594f27b71b2 encrypted

exit

line ssh

login authentication defaultList

enable authentication enableList

exit

snmp-server engineid local 800002a2035c260aa7dcaf

snmp-server agent boot count 1

exit

M6220

!Current Configuration:

!System Description "PowerConnect M6220, 3.1.5.4, VxWorks 6.5"

!System Software Version 3.1.5.4

!System Operational Mode "Normal"

!

configure

stack

member 1 1

member 2 1

exit

ip address none

username "root" password e6e66b8981c1030d5650da159e79539a level 15 encrypted

!

interface ethernet 1/g1

mtu 9216

exit

!

interface ethernet 1/g2

mtu 9216

exit

!

interface ethernet 1/g3

mtu 9216

exit

!

interface ethernet 1/g4

mtu 9216

exit

!

interface ethernet 1/g5

mtu 9216

exit

!

interface ethernet 1/g6

mtu 9216

exit

!

interface ethernet 1/g7

mtu 9216

exit

!

interface ethernet 1/g8

mtu 9216

exit

!

interface ethernet 1/g9

mtu 9216

exit

!

interface ethernet 1/g10

mtu 9216

exit

!

interface ethernet 1/g11

mtu 9216

exit

!

interface ethernet 1/g12

mtu 9216

exit

!

interface ethernet 1/g13

mtu 9216

exit

!

interface ethernet 1/g14

mtu 9216

exit

!

interface ethernet 1/g15

mtu 9216

exit

!

interface ethernet 1/g16

mtu 9216

exit

!

interface ethernet 1/g17

channel-group 2 mode on

spanning-tree portfast

mtu 9216

exit

!

interface ethernet 1/g18

spanning-tree portfast

mtu 9216

exit

!

interface ethernet 1/g19

spanning-tree portfast

mtu 9216

exit

!

interface ethernet 1/g20

spanning-tree portfast

mtu 9216

exit

!

interface ethernet 1/xg1

spanning-tree portfast

mtu 9216

exit

!

interface ethernet 1/xg2

spanning-tree portfast

mtu 9216

exit

!

interface ethernet 1/xg3

spanning-tree portfast

mtu 9216

exit

!

interface ethernet 1/xg4

spanning-tree portfast

mtu 9216

exit

!

interface ethernet 2/g1

mtu 9216

exit

!

interface ethernet 2/g2

mtu 9216

exit

!

interface ethernet 2/g3

mtu 9216

exit

!

interface ethernet 2/g4

mtu 9216

exit

!

interface ethernet 2/g5

mtu 9216

exit

!

interface ethernet 2/g6

mtu 9216

exit

!

interface ethernet 2/g7

mtu 9216

exit

!

interface ethernet 2/g8

mtu 9216

exit

!

interface ethernet 2/g9

mtu 9216

exit

!

interface ethernet 2/g10

mtu 9216

exit

!

interface ethernet 2/g11

mtu 9216

exit

!

interface ethernet 2/g12

mtu 9216

exit

!

interface ethernet 2/g13

mtu 9216

exit

!

interface ethernet 2/g14

mtu 9216

exit

!

interface ethernet 2/g15

mtu 9216

exit

!

interface ethernet 2/g16

mtu 9216

exit

!

interface ethernet 2/g17

channel-group 2 mode on

spanning-tree portfast

mtu 9216

exit

!

interface ethernet 2/g18

spanning-tree portfast

mtu 9216

exit

!

interface ethernet 2/g19

spanning-tree portfast

mtu 9216

exit

!

interface ethernet 2/g20

spanning-tree portfast

mtu 9216

exit

!

interface ethernet 2/xg1

spanning-tree portfast

mtu 9216

exit

!

interface ethernet 2/xg2

spanning-tree portfast

mtu 9216

exit

!

interface ethernet 2/xg3

spanning-tree portfast

mtu 9216

exit

!

interface ethernet 2/xg4

spanning-tree portfast

mtu 9216

exit

!

interface port-channel 2

switchport mode general

switchport general pvid 10

exit

exit

NOTE: If I reset the 5324 and every port is access I can access the blade servers and ISCSI but this isn't recommended configuration?

Thanks in advance from a real noob on this topic but hope to learn :)

New update:

I have now achieved the connection through LAG 1, so that I can access the blades.

For LAG 2 I haven't managed to configure the M6220 correctly it seems.

Any suggestion on what I have configured wrong?

What I have configure now is:

On my two powerconnect 5324 switches I have LAG 1 and LAG 2

Port 1-4 is assigned to LAG 1, all ports are set to trunk. LAG 1 is set to trunk

Port 8-12 is assigned to LAG 2, all ports are set to general and VLAN ID is 10, LAG 2 is set to general and VLAN ID 10

Both switches has VLAN 1, VLAN 10 and VLAN 150 configured on them.

On my M6348 switches I have configured LAG 1

All ports on the switch is assigned to LAG 1

These switches are simple mode enabled on

On my M6220 switches I have configured LAG 2

Port 1-4 and 17 is assigned to LAG 2 - Port 17 is connected to my 5324 switch.

Port 1-4 and 17 is set to General and VLAN ID 10, LAG 2 is set to General and VLAN ID 10

At the moment only one of this is connected to my 5324 switch

At the moment I have connection to the blade servers, but I can't connect to the ISCSI server that is connected to the LAG 2 and VLAN ID 10.

Appreciate all feedbacks on what I have configured wrong or other suggestion to improve my settings.

Thanks

Does the MD3000i plug directly into the switch? Or does it plug into a server, then that server plugs into the switch?

If the MD3000i plugs directly into the switch, you wont use any LAG for that connection, as each controller will have it's own IP address.

If the MD3000i plugs into a server, that server can have a team configured for the connection from the server to the switch.

The MD3000i is connected directly to the switch.

I have removed LAG 2 and just set the ports as General with PVID 10

Should the ports on both end be Access and in VLAN 10 or General and PVID 10 (tagged or untagged?)

Thanks for the your help so far Daniel.

For the MD3000i the ports should be access mode, because they are only sending and receiving untagged frames.

Here are the manuals for the MD3000i, they include a setup guide, hardware guide, cli guide, best practices, etc. They will be your best resource for configuring the MD3000i.

www.dell.com/.../manuals

Thanks, I will try that later today.

The switch to switch connections should be Trunk mode, or general mode. The reason you set it to Trunk or General mode is so that the link can carry traffic from multiple VLANs.

Hi

Now I have tested more and reset all the switches to make sure everything is correct. But still I get "Destination host unreachable" on the Hyper-V Host.

My connection is like this

Blade connection

2 x Dell Powerconnect 5324 (Port 1 and 2 (Trunk and LAG 1)->  2 x Dell M6348 (Port 33 and 34, Trunk and LAG 1))

All ports on M6348 is set to Trunk (Port 1-32)

This works, I can ping the blades and they get ip from DHCP, only thing is that it often drops on ping when I have connected both of the 5324 and M6348 switches. Should I have two lags here? One for each of the switches?

ISCSI Connection

2 x Dell powerconnect 5348

Port 7-12 is Access PVID 10 and is connected to the M3000i, and Port 19 and 20 is trunk and connected to the M6220 switch on the M1000e

2 x M6220 switch

Port 17 and 18 is set to Trunk, and port 1-4 is set to Access PVID 10

This configuration doesn't work at all, If trying to ping the ips of the M3000i we get the error: "Destination hos unreachable", we don't have any nic teaming on the Hyper-V for now.

-Thomas

The 5324 and the M6348 have to be on seperate LAGs, only stacked switches can share a LAG, otherwise they do not know what is happening on the other half of the LAG.