Unsolved
This post is more than 5 years old
2 Posts
0
16283
June 28th, 2010 09:00
PowerConnect 5424 and md3000i VLAN configuration
I'm so confused. I'm sever admin and recently tasked with configuring switch. I understand networking from takin 2 semester of cisco certification class, but never configure a switch in real world before.
I have 2 PowerConnect 5424 and md3000i SAN. I need to configure the switch so that it has redundant path. I set up everything right, and the server can discover the SAN target with no problem. However, when i start configuring the VLAN, everything breaks. This is my configuration:
1 VLAN named iSCSI, the vlan id is 2. This VLAN's members are port 1-10. The IP of this VLAN is 192.168.2.1
port1 on the switch is connected to MD3000i configured with ip: 192.168.2.2. Port1 setting is as follow:
VLAN Mode: Access(options are General, Access, Ttunk, Customer) .
Customer Vlan: 2.
Frame Type: Admit All(can't change the value).
Ingress filtering: Enable(can't change value).
Reserve Vlan for internal use: NONE.
this works fine. i can ping the md3000i controller connected through port 1 from the switch command line console. server connected on port 3 can also discover the md3000i.
HOWEVER, if i check the option to enable VLAN on the md3000i web interface, and set the VLAN ID to 2. I can no longer ping the md3000i from my switch command line interface.
Can anyone tell me what i'm doing wrong?
bh1633
909 Posts
0
June 28th, 2010 10:00
When you set a switch port to be an access port, you are setting it to transmit untagged packets in the designated vlan and to classify untagged received packets to the designated vlan (in your case, vlan 2), and to drop untagged received packets. When you check that box on the ont MD300i and set the vlan to vlan 2, you are now telling the array to tag transmitted packets in vlan 2 and to accept packets tagged in vlan 2, and implicityly drop untagged packets.
Unless you are just dying to tag packets coming out of your array, I would uncheck the box so that it is transmitting and receiving untagged packets and know that the switch is taking care of the vlan assignment.
iisfan
2 Posts
0
June 28th, 2010 10:00
thank you so much for your answer BH1633. The reason why I did that is that in DELL's best practice documentation for md3000i, it recommends enabling VLAN all accross the entire iscsi SAN so that iscsi traffic and hyper-v live migration traffic are completely seperated. I'm having a hard time trying to accomplish this.
thanks again for your reply.