In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!
switch trunk ports not passing data
Hi,
we have configured vlans on several sf 200-24 switches. Ports 1-11 are set to vlan id two and configured as access ports. ports 13-23 are set to vlan id 3 and also configured as access ports. ports 12, 24, G1 and G2 are set to vlan id 1 and remain as trunk ports. When we connect a router to port one on switch one and a computer to port one on switch two then connect the switches via a trunk port we get no internet connection. If we connect the switches using the same vlan on each switch we get connection.
It was our understanding that the trunk ports passed all vlan traffic by default. We did try setting the trunk ports to tagged but that didn't work.
The question: how do we configure the trunk ports so that they pass traffic for both vlans?
Thanks.
we have configured vlans on several sf 200-24 switches. Ports 1-11 are set to vlan id two and configured as access ports. ports 13-23 are set to vlan id 3 and also configured as access ports. ports 12, 24, G1 and G2 are set to vlan id 1 and remain as trunk ports. When we connect a router to port one on switch one and a computer to port one on switch two then connect the switches via a trunk port we get no internet connection. If we connect the switches using the same vlan on each switch we get connection.
It was our understanding that the trunk ports passed all vlan traffic by default. We did try setting the trunk ports to tagged but that didn't work.
The question: how do we configure the trunk ports so that they pass traffic for both vlans?
Thanks.
Asked:
-
4
3
2 Solutions
LVL 57
It appears that the SF200 family is a L2 only device. What device are you using as a router to route between the VLANs?
the current set up is the same as described we just don't have passwords for the switches to see how they are configured. it should work but we are missing something in the configuration.
As long as the ports are configured as trunks and you have allowed all VLAN's then the VLAN traffci will pass.
However this does assume that you are routing L3 traffic correct or that you firewall has multiple interface in all VLANs.
However this does assume that you are routing L3 traffic correct or that you firewall has multiple interface in all VLANs.
That means that it should be passing traffic from all VLAN's through those ports.
But again, you need to make sure that if a host on VLAN-X need to talk to a host on VLAN-Y you have router (L3 device) that is on both VLAN-X and VLAN-Y.
But again, you need to make sure that if a host on VLAN-X need to talk to a host on VLAN-Y you have router (L3 device) that is on both VLAN-X and VLAN-Y.
All resolved now, thanks for responding.
In the end it was the browser we were using to do the configuration. For whatever reason when looking at the port to vlan membership "join to vlan" config page no vlans showed up when in firefox or Chrome only IE.
We did not need to set anything on the routers only tag the desired trunk ports to the vlans.
thanks again.
In the end it was the browser we were using to do the configuration. For whatever reason when looking at the port to vlan membership "join to vlan" config page no vlans showed up when in firefox or Chrome only IE.
We did not need to set anything on the routers only tag the desired trunk ports to the vlans.
thanks again.
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.
One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.
Tackle projects and never again get stuck behind a technical roadblock.
Join Now