LAN Routing
cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to connect 3 x 2910al switches via trunks connected via wireless bridge links

 
Jagman33
Occasional Visitor

Unable to connect 3 x 2910al switches via trunks connected via wireless bridge links

I have three 2910 switches located in three separate locations, One is configured as a router where the main PC equipment and DVR recorders are located, a second is at a mid point building which has one wireless link to switch one plus a fibre link. Switch three has several Vlans configured and is connected to switch two via wireless ethernet bridges (Freespace FS2000) 300Mb links. Each Vlan has several CCTV cameras with digital encoders and again wireless linked to switch three.

The idea is that the 50 plus cameras linked through the vlans connect to the NVR recorders where switch one is located.

These switches were setup and tested together on the bench before being deployed in the field, the testing just used cat 5 patch cables to simulate the truck connections and the cameras by plugging in IP configured encoders onto switch three Vlans. Each Vlans is configured as a separate IP subnet range. The trunks are configured with spanning tree so only one link should pass the traffic and switch to the other link in the event of failure.

 

The problem is the switches do not link up through the wireless links switch 3 to 2, switch 2 to 1 works through the fibre link ok but cannot get to switch 3 from switch 1. The wireless links are working OK as I can use a monitor program to inspect. Spoke with wireless provider who said their link should be transparent. Tried removing one link to overcome spanning tree but to no avail. Must have tried every permutation going and now grasping at straws.

Any help would be appreciated. Can attach the switch config file if required.

5 REPLIES
paulgear
Esteemed Contributor

Re: Unable to connect 3 x 2910al switches via trunks connected via wireless bridge links

Config files and the output of 'show spanning-tree' and 'show interfaces brief' would be a good start at working out what's going on...

Regards,
Paul
Jagman33
Occasional Visitor

Re: Unable to connect 3 x 2910al switches via trunks connected via wireless bridge links

Hi Paul,

I was unable to get on-site today to investigate the spanning tree or interface information. However I show the config detail for each switch below.

 

SWITCH 1 (Main routing switch)

 

; J9148A Configuration Editor; Created on release #W.14.38

hostname "Stockton 2910 POE Switch"
ip access-list extended "100"
   10 permit ip 192.168.100.0 0.0.0.255 192.168.1.201 0.0.0.0
   20 permit ip 192.168.100.0 0.0.0.255 192.168.1.202 0.0.0.0
   30 permit ip 192.168.100.0 0.0.0.255 192.168.1.203 0.0.0.0
   40 deny ip 0.0.0.0 255.255.255.255 192.168.1.203 0.0.0.0
   50 deny ip 0.0.0.0 255.255.255.255 192.168.1.202 0.0.0.0
   60 deny ip 0.0.0.0 255.255.255.255 192.168.1.201 0.0.0.0
   70 permit ip 0.0.0.0 255.255.255.255 0.0.0.0 255.255.255.255
   exit
module 1 type J9148A
interface 1
   ip access-group "100" in
exit
interface 2
   ip access-group "100" in
exit
interface 3
   ip access-group "100" in
exit
interface 4
   ip access-group "100" in
exit
interface 5
   ip access-group "100" in
exit
interface 6
   ip access-group "100" in
exit
interface 7
   ip access-group "100" in
exit
interface 8
   ip access-group "100" in
exit
interface 9
   ip access-group "100" in
exit
interface 10
   ip access-group "100" in
exit
interface 11
   ip access-group "100" in
exit
interface 12
   ip access-group "100" in
exit
interface 13
   ip access-group "100" in
exit
interface 14
   ip access-group "100" in
exit
interface 15
   ip access-group "100" in
exit
interface 16
   ip access-group "100" in
exit
interface 17
   ip access-group "100" in
exit
interface 18
   ip access-group "100" in
exit
interface 19
   ip access-group "100" in
exit
interface 20
   ip access-group "100" in
exit
interface 21
   ip access-group "100" in
exit
interface 22
   ip access-group "100" in
exit
interface 23
   ip access-group "100" in
exit
interface 24
   ip access-group "100" in
exit
interface 25
   ip access-group "100" in
exit
interface 26
   ip access-group "100" in
exit
interface 27
   ip access-group "100" in
exit
interface 28
   ip access-group "100" in
exit
interface 29
   ip access-group "100" in
exit
interface 30
   ip access-group "100" in
exit
interface 31
   ip access-group "100" in
exit
interface 32
   ip access-group "100" in
exit
interface 33
   ip access-group "100" in
exit
interface 34
   ip access-group "100" in
exit
interface 35
   ip access-group "100" in
exit
interface 36
   ip access-group "100" in
exit
interface 37
   ip access-group "100" in
exit
interface 38
   ip access-group "100" in
exit
interface 39
   ip access-group "100" in
exit
interface 40
   ip access-group "100" in
exit
interface 41
   ip access-group "100" in
exit
interface 42
   ip access-group "100" in
exit
interface 43
   ip access-group "100" in
exit
interface 44
   ip access-group "100" in
exit
interface 45
   ip access-group "100" in
exit
interface 46
   ip access-group "100" in
exit
trunk 47 Trk3 Trunk
trunk 48 Trk4 Trunk
ip default-gateway 192.168.1.203
ip routing
vlan 1
   name "DEFAULT_VLAN"
   untagged 1,11-19,21-46,Trk3-Trk4
   ip address 192.168.1.203 255.255.255.0
   no untagged 2-10,20
   exit
vlan 2
   name "sub10"
   untagged 2
   ip address 192.168.10.1 255.255.255.0
   tagged Trk3
   exit
vlan 3
   name "sub20"
   untagged 3
   ip address 192.168.20.1 255.255.255.0
   tagged Trk3
   exit
vlan 4
   name "sub30"
   untagged 4
   ip address 192.168.30.1 255.255.255.0
   tagged Trk3
   exit
vlan 5
   name "sub40"
   untagged 5
   ip address 192.168.40.1 255.255.255.0
   tagged Trk3
   exit
vlan 6
   name "sub50"
   untagged 6
   ip address 192.168.50.1 255.255.255.0
   tagged Trk4
   exit
vlan 7
   name "sub60"
   untagged 7
   ip address 192.168.60.1 255.255.255.0
   tagged Trk4
   exit
vlan 8
   name "sub70"
   untagged 8
   ip address 192.168.70.1 255.255.255.0
   tagged Trk4
   exit
vlan 9
   name "sub80"
   untagged 9
   ip address 192.168.80.1 255.255.255.0
   tagged Trk4
   exit
vlan 10
   name "sub90"
   untagged 10
   ip address 192.168.90.1 255.255.255.0
   tagged Trk4
   exit
vlan 100
   name "management"
   untagged 20
   ip address 192.168.100.1 255.255.255.0
   tagged Trk4
   exit
gvrp
snmp-server community "public" unrestricted
spanning-tree
spanning-tree Trk3 priority 4
spanning-tree Trk4 priority 4

 

SWITCH 2 (Midpoint switch)

 

; J9146A Configuration Editor; Created on release #W.14.38

hostname "ELM 2910 POE Switch"
module 1 type J9146A
trunk 21 Trk1 Trunk
trunk 22 Trk2 Trunk
trunk 23 Trk3 Trunk
trunk 24 Trk4 Trunk
vlan 1
   name "DEFAULT_VLAN"
   untagged 1,11-19,Trk1-Trk4
   ip address 192.168.1.202 255.255.255.0
   no untagged 2-10,20
   exit
vlan 2
   name "sub10"
   untagged 2
   tagged Trk1,Trk3
   no ip address
   exit
vlan 3
   name "sub20"
   untagged 3
   tagged Trk1,Trk3
   no ip address
   exit
vlan 4
   name "sub30"
   untagged 4
   tagged Trk1,Trk3
   no ip address
   exit
vlan 5
   name "sub40"
   untagged 5
   tagged Trk1,Trk3
   no ip address
   exit
vlan 6
   name "sub50"
   untagged 6
   tagged Trk2,Trk4
   no ip address
   exit
vlan 7
   name "sub60"
   untagged 7
   tagged Trk2,Trk4
   no ip address
   exit
vlan 8
   name "sub70"
   untagged 8
   tagged Trk2,Trk4
   no ip address
   exit
vlan 9
   name "sub80"
   untagged 9
   tagged Trk2,Trk4
   no ip address
   exit
vlan 10
   name "sub90"
   untagged 10
   tagged Trk4
   no ip address
   exit
vlan 100
   name "management"
   untagged 20
   tagged Trk2,Trk4
   no ip address
   exit
gvrp
snmp-server community "public" unrestricted
spanning-tree
spanning-tree Trk1 priority 4
spanning-tree Trk2 priority 4
spanning-tree Trk3 priority 4
spanning-tree Trk4 priority 4

 

SWITCH 3 (Camera end switch)

 

; J9146A Configuration Editor; Created on release #W.14.38

hostname "Bayheath 2910 POE Switch"
module 1 type J9146A
trunk 23 Trk1 Trunk
trunk 24 Trk2 Trunk
ip default-gateway 192.168.1.203
vlan 1
   name "DEFAULT_VLAN"
   untagged 1,15-19,21-22,Trk1-Trk2
   ip address 192.168.1.201 255.255.255.0
   no untagged 2-14,20
   exit
vlan 2
   name "sub10"
   untagged 2
   tagged Trk1
   no ip address
   exit
vlan 3
   name "sub20"
   untagged 3
   tagged Trk1
   no ip address
   exit
vlan 4
   name "sub30"
   untagged 4
   tagged Trk1
   no ip address
   exit
vlan 5
   name "sub40"
   untagged 5
   tagged Trk1
   no ip address
   exit
vlan 6
   name "sub50"
   untagged 6-10
   tagged Trk2
   no ip address
   exit
vlan 7
   name "sub60"
   untagged 11-12
   tagged Trk2
   no ip address
   exit
vlan 8
   name "sub70"
   untagged 13
   tagged Trk2
   no ip address
   exit
vlan 9
   name "sub80"
   untagged 14
   tagged Trk2
   no ip address
   exit
vlan 100
   name "management"
   untagged 20
   tagged Trk2
   no ip address
   exit
gvrp
snmp-server community "public" unrestricted
spanning-tree
spanning-tree Trk1 priority 4
spanning-tree Trk2 priority 4

paulgear
Esteemed Contributor

Re: Unable to connect 3 x 2910al switches via trunks connected via wireless bridge links

A couple of minor points (unlikely to be causing your issues):

  • "ip default-route" is only used when routing is off; to set the default route when routing is on, use "ip route 0.0.0.0 0.0.0.0 192.168.1.203"
  • Trunks in ProCurve are not like trunks in Cisco - there's no point in defining them if you're only going to have one link in them (unless you're planning to expand them to more than one link later); Cisco trunk == ProCurve tagged port; ProCurve trunk == Cisco EtherChannel/PAgP
  • There's no point tagging all of your inter-switch links when you've got GVRP turned on; GVRP is a more usable equivalent to Cisco's VTP - it will tag all of the VLANs you're using on your inter-switch links, and automatically prune the ones that aren't needed.

Probably the big issue is that you're setting the priority of your trunks, but not your switches. This means that you don't know which switch will get elected as the root, and you can't accurately predict which links will get blocked as a result.  (Use "show spanning-tree" on each switch to see.)  You need to set the priority of the core switch to 0, then set your other switches appropriately to ensure that the correct one will be elected if the core goes down.

 

Get those command outputs, and i'm sure we'll get to the bottom of this pretty quickly.

Regards,
Paul
Jagman33
Occasional Visitor

Re: Unable to connect 3 x 2910al switches via trunks connected via wireless bridge links

Hi Paul,

Thanks for the information and comments.

It has been rather manic and still not made it back to site to extract the information.

However, I have spoke to collegue today who has come across a similar problem and seemed to recall that the issue is with the Freespace FS2000 wireless links which have in-built spanning tree which conflicts with the router spanning tree and additionally arp cache refresh rates.

 

It may be that I rethink the switch configuration to remove the trunks and only use one wireless link between the 2nd and 3rd switch on perhaps the default vlan.

 

regards,

John

paulgear
Esteemed Contributor

Re: Unable to connect 3 x 2910al switches via trunks connected via wireless bridge links

Hi John,

 

I'm not familiar with the Freespace FS2000 or its STP implementation, but if it's a relatively new product, it's quite likely that its STP implementation is fully standards-compliant.  I think setting switch STP priorities explicitly to ensure you have the desired root bridge is the most important next step.

Regards,
Paul