11-13-2014 06:40 AM - edited 03-07-2019 09:29 PM
We were trying some things to get multiple VLANs to pass through some wireless bridges. In the confusion, we have misconfigured the port and locked ourselves out of the far switch, lol. The local switch has VLAN1 (default), VLAN2 (data), and VLAN3 (voice). None of the VLANs are shutdown and the switch has an interface for both VLAN2 and VLAN3. The remote switch also has VLAN1, VLAN2, and VLAN3 (and it has an interface for VLAN2 and VLAN3). However, VLAN1 is shutdown. The port used to connect it to the local switch has always been using VLAN2. In the midst of some changes, that port got changed to VLAN1 :( We can no longer access the remote switch at all. It does still show up in cdp neighbors on the local switch (although it says VLAN1 mismatch). Is there anyway we can get back into the remote switch without having someone go on site and perform a power cycle? Thanks.
11-14-2014 06:15 AM
The remote switch has its port like this now:
interface FastEthernet0/12
switchport trunk native vlan 2
switchport mode trunk
spanning-tree bpdufilter enable
spanning-tree bpduguard enable
And we are back to the same problem - VLAN2 traffic will pass through, but VLAN3 won't. Neither switch can see the other's VLAN3 SVI...
11-14-2014 01:06 PM
The wireless bridges are Planet Networking WNAP-6305 units. I don't see any VLAN settings in them at all. They do make a 'better' model called WNAP-6308. These units do have VLAN settings. So it might just be a limit of the bridges themselves. However, I was hoping that while you might not be able to make VLAN changes in the bridges, they could still pass the traffic through...
11-14-2014 01:51 PM
Any bridge I've ever worked with normally would pass vlan tags unaltered without any configuration to the bridge. If you specify the tags in the bridge, it's possible that it's disabling that functionality. At this point, the switchport is configured to allow vlan 2 untagged and all of the others tagged. I would contact Planet Networking to see if they can help with passing the vlan....
11-14-2014 03:10 PM
I attempted to call them earlier today, but apparently the only support number is in Taiwan. I sent an email to their Tech Support team. I will let you know what they say.
11-15-2014 02:57 AM
Hello
if the switch you are connected to support clustering you can gain access via l2 and amend you changes
conf t
Cluster enable stan
sh cluster candidates
cluster member 10 mac-address (xxxxxxx) password xxxxx
sh cluster members
rc 10
res
paul
11-18-2014 03:47 AM
Paul,
Thanks for the info. I will remember that for future reference.
11-18-2014 03:48 AM
Here is the email from Planet Networing:
About your inquiry:
*********************************************************************************
I have two WNAP-6305 bridges connecting two Cisco switches. The Cisco switches are configured for trunking, but only one VLAN is being passed through the bridges. Every other bridge that I've worked with will allow all VLANs to pass through. Is there a way to allow that with these units?
*********************************************************************************
Answer:
*********************************************************************************
The WNAP-6305’s SDK didn’t support tagged VLAN, so only the default VLAN can be passed through the WDS bridge.
We’ll suggest you use WNAP-6350.
11-18-2014 03:50 AM
Well, that helps :) If you replace them, then you'll be able to pass your vlan 3 with no issues...
HTH,
John
11-18-2014 04:01 AM
Yes, glad we found the 'solution' - although, it wasn't what I hoped for, haha.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide