Issue with routing/trunking between SG300-10 and Dell Powerconnect 5224

[lenellm86]

Hello,

I just purchased a SG300-10 switch and loaded the newest 1.27 firmware on it.  Setup my VLANS and trunks but I have this weird issue that I can't seem to figure out.  It may be something small I'm missing but regardless, I've been scratching at it all day and it's kicking me in the butt.  If someone can point me to the right direction or maybe something someone see's in my config that's flawed, I may have gotten the terminology/theory wrong, afterall, I just passed my CCNA:)

My setup:

I have the SG300-10 as my main switch and changed it over to L3 so it can be my main core in my small network.  On port 1, vlan 200 is setup as my native PVID untagged and I have it set to trunk vlan's 210(LAN network), 220 (management vlan) tagged over to a Dell powerconnect 5224 24port switch.  On port 1 of the Dell switch, I have it setup as a trunk there as well with the same setup (native PVID vlan set to 200 untagged, trunking 210 and 220 tagged).

I have virtual interfaces setup on the SG300 for each vlan (vlan 210 = 192.168.210.1/24, vlan 220 = 192.168.220.1/24) and on the Dell, since it's a L2 device, I changed the management vlan from 1 to 220 and set the IP to 192.168.220.2/24.

Now from the SG300 web interface, I can ping the Dell management IP (192.168.220.2/24)successfully and vice versa, can ping from the Dell web interface to any of the VLAN gateway IP's successfully (210.1 & 220.1) so from that testing, to me, it sounds like the Dell is communicating with the SG300.  I also have the default gateway of the Dell set to 192.168.220.1.

Server IP: 192.168.220.10/24

Workstation IP: 192.168.210.80/24

Now the dilemma:

I have a server plugged into the Dell switch port 2 (configured as "hybrid" since there is no access option, PVID set to 220, vlan set to 220 Untagged) and from the server, I can ping the dell management switch IP just fine and can ping the SG300 gateway IP's just fine as well.  On the SG300 switch, on port 2, I have plugged in a workstation (setup is access mode, vlan 210 untagged) that can't ping the server plugged into the dell switch.  From the workstation, I can ping all of the interfaces of the SG300 and also the dell management IP but I can't ping the server.

Any ideas anyone can provide is much appreciated!

edited vlans.

[Tom Watts]

Where does vlan 133 reside on the switches? What is the IP of the server and does the SX300 know about the subnet?

If you create vlan 133 on both switches, add it to the trunk between the switches and assign 133u to the port connecting to the server it should communicate fine.

-Tom
Please rate helpful posts

[lenellm86]

Eekk sorry Tom,

It must have been really late last night when I posted that:)  Ignore vlan 133, that was my old setup:)  I corrected the original post.

But to what you were explaining, that's exactly what I thought how it should be setup but for some reason, the workstation isn't pinging the server and there isn't any ACL's setup on both switches.

Also, just to add, on port 3 of the Dell switch, I have that set to trunk vlans 210T & 220T, PVID set to 200U going into a small server used as a vmware esxi host and I set the management virtual nic to 192.168.220.9/24 and from the workstation, I can even ping that just fine, just not the physical server behind the dell switch.  Seems like I can ping packets tagged 220 but on the port untagged, that's where I seem to think that's were the issue may be.

I can also post up configs later when I get home..    

[Tom Watts]

My setup:

I have the SG300-10 as my main switch and changed it  over to L3 so it can be my main core in my small network.  On port 1,  vlan 200 is setup as my native PVID untagged and I have it set to trunk  vlan's 210(LAN network), 220 (management vlan) tagged over to a Dell  powerconnect 5224 24port switch.  On port 1 of the Dell switch, I have  it setup as a trunk there as well with the same setup (native PVID vlan  set to 200 untagged, trunking 210 and 220 tagged).

Okay, this is all and fine

I  have virtual interfaces setup on the SG300 for each vlan (vlan 210 =  192.168.210.1/24, vlan 220 = 192.168.220.1/24) and on the Dell, since  it's a L2 device, I changed the management vlan from 1 to 220 and set  the IP to 192.168.220.2/24.

Okay, this should be no problem

Now  from the SG300 web interface, I can ping the Dell management IP  (192.168.220.2/24)successfully and vice versa, can ping from the Dell  web interface to any of the VLAN gateway IP's successfully (210.1 &  220.1) so from that testing, to me, it sounds like the Dell is  communicating with the SG300.  I also have the default gateway of the  Dell set to 192.168.220.1.

Alright, what happens if you ping the server IP from either switch?

Server IP: 192.168.220.10/24

Workstation IP: 192.168.210.80/24

How are the default gateway set?

Now the dilemma:

I  have a server plugged into the Dell switch port 2 (configured as  "hybrid" since there is no access option, PVID set to 220, vlan set to  220 Untagged) and from the server, I can ping the dell management switch  IP just fine and can ping the SG300 gateway IP's just fine as well.  On  the SG300 switch, on port 2, I have plugged in a workstation (setup is  access mode, vlan 210 untagged) that can't ping the server plugged into  the dell switch.  From the workstation, I can ping all of the interfaces  of the SG300 and also the dell management IP but I can't ping the  server.

Can either switch ping the work station?

But to what you were explaining, that's exactly what I thought how it  should be setup but for some reason, the workstation isn't pinging the  server and there isn't any ACL's setup on both switches.

Yep, works fine

Also,  just to add, on port 3 of the Dell switch, I have that set to trunk  vlans 210T & 220T, PVID set to 200U going into a small server used  as a vmware esxi host and I set the management virtual nic to  192.168.220.9/24 and from the workstation, I can even ping that just  fine, just not the physical server behind the dell switch.  Seems like I  can ping packets tagged 220 but on the port untagged, that's where I  seem to think that's were the issue may be.

This verifies the switches are well and good. If you're able to verify connectivity to different devices on the same scenario, the switches pass just fine. You may want to look in to firewall / security settings of the server and verify the above questions as well.

-Tom
Please rate helpful posts

[lenellm86]

See below:

Thomas Watts wrote:
My setup:
I have the SG300-10 as my main switch and changed it  over to L3 so it can be my main core in my small network.  On port 1,  vlan 200 is setup as my native PVID untagged and I have it set to trunk  vlan's 210(LAN network), 220 (management vlan) tagged over to a Dell  powerconnect 5224 24port switch.  On port 1 of the Dell switch, I have  it setup as a trunk there as well with the same setup (native PVID vlan  set to 200 untagged, trunking 210 and 220 tagged).
Okay, this is all and fine
I  have virtual interfaces setup on the SG300 for each vlan (vlan 210 =  192.168.210.1/24, vlan 220 = 192.168.220.1/24) and on the Dell, since  it's a L2 device, I changed the management vlan from 1 to 220 and set  the IP to 192.168.220.2/24.
Okay, this should be no problem
Now  from the SG300 web interface, I can ping the Dell management IP  (192.168.220.2/24)successfully and vice versa, can ping from the Dell  web interface to any of the VLAN gateway IP's successfully (210.1 &  220.1) so from that testing, to me, it sounds like the Dell is  communicating with the SG300.  I also have the default gateway of the  Dell set to 192.168.220.1.
Alright, what happens if you ping the server IP from either switch?
From the SG300 web console>Ping, I can ping successfully the server IP and also from the Dell console, I can ping it as well.  When I hooked up a laptop into port 8 on the SG300 and set the IP config as follows:
IP: 192.168.220.50/24
Gateway: 192.168.220.1
The port I set to access, 220U, I can access VLAN 220 devices like the dell switch IP, the server IP.
I then proceeded to change the port to VLAN 210U, then changed the IP to match the subnet on the LAN network (192.168.210.50/24, gateway set to 192.168.210.1) and when I ping the server, it says destination unreachable, but I can ping the gateway fine, 210.1, and can also ping virtual interface 220.1/dell switch 220.2.  
Seems like it can hit the virtual IP's on the 220 vlan but not the physical devices on 220 when a machine tries to go from vlan 210, that's where I'm getting at:)
Server IP: 192.168.220.10/24
Workstation IP: 192.168.210.80/24
How are the default gateway set?
Gateway is set to 220.1 and 210.1
Now the dilemma:
I  have a server plugged into the Dell switch port 2 (configured as  "hybrid" since there is no access option, PVID set to 220, vlan set to  220 Untagged) and from the server, I can ping the dell management switch  IP just fine and can ping the SG300 gateway IP's just fine as well.  On  the SG300 switch, on port 2, I have plugged in a workstation (setup is  access mode, vlan 210 untagged) that can't ping the server plugged into  the dell switch.  From the workstation, I can ping all of the interfaces  of the SG300 and also the dell management IP but I can't ping the  server. 
Can either switch ping the work station?
I'll have to check when I get home, but since from the above troubleshooting, the workstation was able to ping both switches, I'm assuming the switches can see the workstation.
But to what you were explaining, that's exactly what I thought how it  should be setup but for some reason, the workstation isn't pinging the  server and there isn't any ACL's setup on both switches.
Yep, works fine
Also,  just to add, on port 3 of the Dell switch, I have that set to trunk  vlans 210T & 220T, PVID set to 200U going into a small server used  as a vmware esxi host and I set the management virtual nic to  192.168.220.9/24 and from the workstation, I can even ping that just  fine, just not the physical server behind the dell switch.  Seems like I  can ping packets tagged 220 but on the port untagged, that's where I  seem to think that's were the issue may be. 
 This verifies the switches are well and good. If you're able to verify connectivity to different devices on the same scenario, the switches pass just fine. You may want to look in to firewall / security settings of the server and verify the above questions as well.
Firewall has been off:(
-Tom 
Please rate helpful posts

[lenellm86]

Another thing I should add, the workstation is behind a unmanaged gigabit switch but like I mentioned above, I even plugged in a laptop directly to the SG300 with the port set to VLAN 210U and it still didn't ping the server, but thought I should add that tiddbit.

[Tom Watts]

Can you verify to me the system ID (mac address) of the 300 switch and verify the MAC address being seen on the ICMP requests?

Also, for giggles, can you downgrade to the 1.1.2.0 firmware and factory reset the switch?

I have an odd feeling you might be getting a port MAC ID instead of the system MAC ID on your packets.

-Tom
Please rate helpful posts

[lenellm86]

Sure, I can do that.  Something new to do instead of me going over and over my theory thinking it was me that has screwed up on this.  But the setup sounds good though right?

[lenellm86]

An update:

I ran a wireshark from my laptop plugged into Port 8 on the SG300, set to vlan 210, and pinged the virtual interfaces for vlan 210/220 and the MAC addresses registering for the both VLAN gateways is indeed showing the system MAC ID and not the port MAC ID. 

Just for kicks, I setup 2 ports on the Dell switch side, 1 on vlan 210 and the other on vlan 220.  When I am on the port for vlan 210, I can ping all gateway virtual IP's on the SG300 just fine (uses the system MAC ID for the SG300) but still can't ping the server.

I then proceeded to change my IP and switch the cable to the port setup for vlan 220, I can ping all virtual gateway IP's for the SG300 fine as well, and also I can ping the server just fine.

I will no attempt to downgrade the firmware to see if that makes a difference...

[Tom Watts]

If you got the time right now, email me a phone number. I don't mind to check it out with you.

-Tom
Please rate helpful posts

[lenellm86]

Sorry just now got back online since I did what you asked and downgraded to firmware 1.1.1.8 (ok I was lazy to get the 1120:)) and it still didn't work.

Sure I will PM you my #.

[Tom Watts · Accepted solution]

Lenell, thanks for the call this evening. It looks like we found the problem. The NAS, although configured with a default gateway, the gateway is reporting 0.0.0.0. We also verified the NAS works from the same subnet to communicate but fails outside the subnet. Conversely, we verified 2 computers have no problems to communicate across the layer 3 VLANs.

I hope we got the right direction.

-Tom
Please rate helpful posts

[lenellm86]

Hey Tom,

Just an update, you were spot on.  The issue turned out to be the NAS box since there was an option right below the status of the nics (see pic below) which asks what default gateway to use, which can be the gateway set on either Ethernet 1 or 2.  If you remember, Ethernet 1, I just had an IP and subnet mask set, no gateway since it was configured from my old network, which used 1 flat subnet.  So basically, even though I set a gateway on Ethernet 2, the option below was pointing to use the gateway on Ethernet 1 which was set to nothing. 

Argh lesson learned, try another device!! Sorry I was quick to blame my config, I didn't even bother to try another machine:) So the conclusion, my config was correct all along, I just set my SG300 back to the config I had before, tried to ping now from one vlan to the other and it and pings fine! Trunk is working between SG300 and Dell switch.

Thanks again for your all your efforts! Excellent customer service!!