SG500-28 InterVLAN Routing not working

[itservice]

Hi there,

I need your help to get InterVLAN Routing working on a SG500-28 Stack with 2 Units.

I think I am missing something with how the port type needs to be set ( trunk or access ) and how the VLAN tagging ( tagged / untagged ) has to be on specific port to get routing working?!?


Can I route between VLANs if the ports are all trunk and all VLANs are tagged or do I need to have one untagged?

Port 1 Trunk VLAN 100 TAGGED
Port 2 Trunk VLAN 200 TAGGED 

both have IPs and I can ping the IP from the client and from the Switch I can ping the Client but NOT from Client to Client.
Traceroute stops with IP of VLAN100 when I want to route into VLAN200 and vice versa.

Switch is in router mode

Thanks for advice!

[Ingrid Aragon]

Thomas, I am one of the engineers from the Small Business team.

The SG500 is capable of doing what you are needing InterVLAN, I am afraid that you might have something wrong with the configuration on the switch.

To have communications between two VLANs you need to have IP ROUTE enable on the switch, let's confirm:
1- IP Configuration > Management and IP interfaces > IPv4 interface > Make sure that IPv4 Routing is enabled.
2- Double check the IPv4 Interface Table.

Now let's verify the VLANs configuration.
Rules:
1- If a port is joining one VLAN > Port can be setup as ACCESS or TRUNK.
2- If a port is joining more than one VLAN > Port can be setup as TRUNK or GENERAL.

So with that said, take a moment to review the VLAN/Port configuration that you have on your device. I would also recommend to review the ACLs, remember that this switch supports Ingress ALC only, so you would have to apply an ACL to the ingress port of the requestor.

I hope you find this information helpful.

[itservice]

Hi Ingrid,

thanks for the answer and help ... 

Currently I am reviewing my setup with two laptops instead and it seems to run without any trouble ... but yes I am pretty sure I am missing something.

1. I do not have ACL up to now.
2. All the ports in the different VLANs are setup as trunk ... 

Question 1 ... If I only have one port configured as trunk that is member of VLAN 100 and member of VLAN 200 and both tagged can I route from the VLAN 100 into VLAN 200 over that port and vice versa?

Question 2 ... Is there a difference if the only port within a VLAN is tagged or untagged for Inter VLAN routing to work? ( port is setup as trunk ).

Thanks!

Thomas

[Ingrid Aragon]

Thomas, your issue is that you are using computers that only recognize untagged packets. If you only have Tagged VLANs you won't be able to have communication between the 2 Tagged VLANs, there should be an Untagged VLAN automatically created by the switch (VID: 4095). Therefore, your computers are listing the Untagged VLAN instead of the Tagged VLAN that you setup. Try changing the VLANs as Untagged and confirm if you have communication.

[itservice]

Hi Ingrind,

thanks for that tip but I installed original Intel Network drivers into the OS of the laptops so that I can set up Network Iinterface with VLAN tagging on Laptops to check wether there is a difference on the port configuration being with / without tagging.

I can confirm that with the two laptops being in differend VLANs and having IP of VLAN as default gateway can communicate regarding of both being untagged or tagged or one untagged one tagged ... 

So I guess that I do have a routing problem with my ISP and to verify that I asked these two questions ...

The two VLANs where the two laptops are currently connected to also have one trunk port with both VLANs tagged configured. Laptops can reach both firewall interfaces and everything is fine so far.

There is a third VLAN where I do have a ISP router connected to as trunk untagged and I can reach the VLAN IP from firewall & laptops but not ISP router ... 
The default-gateway entry on the SG500 points to that ISP router ... 

ISP assured that he has configured routes on the router to send all to my IP of the VLAN where the router is connected to but it seems that he does not ... 

Thats why I asked the two questions Ingrid ... to verify that my setup is right and that there is no limitation on Inter VLAN routing wether the ports of the VLANs are tagged or untagged and wehter the ports are trunk or general ... 

Thomas

[Ingrid Aragon]

I would like to check your current configuration, I will send you an internal email to the email address that is associated with your CCOID.

[ryanruet]

Hello Ingrid Aragon,

i have 550XG as core switch and SG500 as access switch. Specification said both supports RIPv2. can i communication both switch by rip routing? what is the easy way for intervlan routing? I can rip routing in packet tracer layer 3 switch and invervlan routing as well. But in this switch i am facing problem. Please help me...

[Ingrid Aragon]

Sure, let me do my best to help you :)

Is confirmed that RIPv2 is enabled on this switch models. Find attached the chapter that covers this topic.

I would like to understand better your issue, so please elaborate:

• What exactly is your issue?
• What are you trying to achieve?
• What is your topology?
• Firmware versions installed on this units.
• Logs

Any information that can help me to understand your issue.

[ryanruet]

Thanks for your reply. However, RIPv2 work right now. but new problem arise.

i connect SG550XG to SG500X by sfp supported module for 10G. but it is not connecting. Is there any special command for using fiber connectivity?

OM4 Multi-mode 50/125µm, Duplex, LC 

SFP-10G-SR

SG550XG >> interface  te1/0/9 

ip address 192.168.3.1 255.255.255.0

I/F Status  admin/oper 

up/up

SG500X >> interface  te1/1/1

ip address 192.168.3.2 255.255.255.0

I/F Status  admin/oper 

up/down

Both case negotiation disabled.