ITGURU Posted October 3, 2017 Posted October 3, 2017 I Have the following setup Core Switch > 1st Edge Switch > Second Edge switch linked from SFP port on 1st switch On the core switch I've tagged all VLANs the same as on the 1st edge switch, so I can connect the second edge switch straight back to the core rather than daisy chaining off the first. However, when I switch the link to the second switch back to the core switch, all VLANs are passing apart from 1. I've checked, double checked, triple checked the core switch source port and all VLANs are there for the port and tagged. It's the only change so the other end of the link switch hasn't been touched and still has the VLAN tagged that isn't working. Any ideas?
FN-GM Posted October 3, 2017 Posted October 3, 2017 On the first edge switch in the middle, do you have the problem VLAN setup on that switch? Even if none of the ports needed it you will need it on that switch to pass the traffic onto number 2.
ITGURU Posted October 3, 2017 Author Posted October 3, 2017 On the first edge switch in the middle, do you have the problem VLAN setup on that switch? Even if none of the ports needed it you will need it on that switch to pass the traffic onto number 2. Yes the VLAN is working fully when in the daisy chain configuration. However when the second switch it directly connected to the core, all over VLANs pass without an issue, there is just one (CCTV) which won't.
ITGURU Posted October 3, 2017 Author Posted October 3, 2017 What sort of switches are they? Fully Managed L2+ Just doesn't make any sense when I'm only changing the source port the switch is connected to! Going to try creating an IP interface on the remote edge switch and see if that pings to see if it's getting over the fibre uplink.
FN-GM Posted October 3, 2017 Posted October 3, 2017 Fully Managed L2+ I meant the make, Cisco, HP etc.
MicrodigitUK Posted October 3, 2017 Posted October 3, 2017 Your management VLAN (VLAN 1) should be untagged on your links between switches. All other VLANs should be tagged. Think of it like: VLAN 1 carries all of the other tagged VLANS across the links. That's how I was trained to do it in my CCNA and it always works for me with inter vendor support, Cisco, HP, Juniper, D-Link, Aruba, etc...
ITGURU Posted October 4, 2017 Author Posted October 4, 2017 Your management VLAN (VLAN 1) should be untagged on your links between switches. All other VLANs should be tagged. Think of it like: VLAN 1 carries all of the other tagged VLANS across the links. That's how I was trained to do it in my CCNA and it always works for me with inter vendor support, Cisco, HP, Juniper, D-Link, Aruba, etc... Yep - I've crossed check the port that the second switch was connected to on the first, and everything is EXACTLY the same VLAN and tagging wise on the core switch,.
MicrodigitUK Posted October 4, 2017 Posted October 4, 2017 Yep - I've crossed check the port that the second switch was connected to on the first, and everything is EXACTLY the same VLAN and tagging wise on the core switch,. Can you post a some snippets of the switch configurations?
ITGURU Posted October 4, 2017 Author Posted October 4, 2017 Can you post a some snippets of the switch configurations? VLAN 10 works fine, VLAN 80 doesn't. I'm connecting the second switch to Port 1:3
ITGURU Posted October 4, 2017 Author Posted October 4, 2017 I think it might be just the switch no saving the configuration as I've tried connecting to a different core switch and it works fine. I'll give it a reboot, and check the outcome when I can.
Davit2005 Posted October 4, 2017 Posted October 4, 2017 (edited) Use a different vlan for management that is tagged on uplinks not untagged. Picture scenario, you are adding a vlan to an uplink on remote switch and instead of doing tagged you type untagged, you are now disconnected from remote switch with no way of accessing without going to the phsyical location. The sort of mistake that happens and I've seen it. Edited October 4, 2017 by Davit2005
MicrodigitUK Posted October 4, 2017 Posted October 4, 2017 VLAN 10 works fine, VLAN 80 doesn't. I'm connecting the second switch to Port 1:3 [ATTACH=CONFIG]45623[/ATTACH] [ATTACH=CONFIG]45624[/ATTACH] [ATTACH=CONFIG]45625[/ATTACH] 1:3 is not untagged on the default (management) VLAN1. Try untagg VLAN1 both ends and see if it carries the two tagged VLANs 10 and 80 (these 2 are tagged on 1:3 and that is correct).
ITGURU Posted October 4, 2017 Author Posted October 4, 2017 1:3 is not untagged on the default (management) VLAN1. Try untagg VLAN1 both ends and see if it carries the two tagged VLANs 10 and 80 (these 2 are tagged on 1:3 and that is correct). 1:3 should work tagged, as the uplink port on the 1st switch to the second switch IS tagged. I've copied the exact configuration from the uplink port on the 1st switch to the port on the core switch.
MicrodigitUK Posted October 4, 2017 Posted October 4, 2017 That might work in some cases however it is not the correct way to do it. It can case problems with intervener and even the same vendor but different firmware!! Trust me Just give it a try and see what happens.
ITGURU Posted October 4, 2017 Author Posted October 4, 2017 As suspected it was the source core switch not taking notice of the configuration. After a reboot I checked the configuration, switched the fibre links and everything came online. The core switch has been up for quite a while 1 or 2 years probably since last reboot, and I've seen the same issue before on our phone system where software changes would take effect despite being set, and the answer was to reboot. Guess it pays to do a reboot now and again but with a core switch there isn't ever really any need to (apart from to fix this issue)
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now