redundent links between 2 3500yl switches using OSPF

[Andy_Burchell]

Hi Everyone,

I hope someone can help:

I have redundant  links between  two 3500 switch’s  1* 10 Mb and 1*100MB.

What I need to do is get the routers to use the 100MB by default but jump over to 10MB in the event of the 100MB line failing and then jumping back when the 100MB line comes back. I have drawn a diagram to show what I mean. It is ports 23 and 24 doing the routing.

Thanks ver much in advance:

Routed VIA OSPF
                                       |------------|     100MB (primary)   |--------------|
              Multiple Vlans    | HP 3500 |---------------------------| HP 3500   | Multiple VLANS
                                       |               |---------------------------|                 |
                                       | -----------|     10MB (backup)      |--------------|

With my current configuration, the ospf works ok, when both lines are connected the routing goes over the 100mb line fine, if that fails it jumps across to the 10mb instantly, but when the 100 mb comes back up it takes a while to jump back across (between 30sec – 1min).

I really need the swap back to be as quick as possible. It may all be fine but I am not a hp expert so could be missing a command or 2.

Below are my current configs for the 2 switches.

hostname "Site_A"

module 1 type J86xxA

interface 1

   name "802-1q_To_Data_1_Port49"

exit

interface 2

   name "802-1q_To_Data_1_Port50"

exit

interface 3

   name "802-1q_To_Data_2(NC)"

exit

interface 4

   name "802-1q_To_Data_2(NC)"

exit

interface 5

   name "802-1q_To_Voice_1_Port49"

exit

interface 6

   name "802-1q_To_Voice_1_Port50"

exit

interface 7

   name "802.1q_To_Voice_2(NC)"

exit

interface 8

   name "802.1q_To_Voice_2(NC)"

exit

interface 9

   name "Wireless_1"

exit

interface 10

   name "Wireless_2"

exit

interface 11

   name "802-1q_To_Server_1_Port23"

exit

interface 12

   name "802-1q_To_Server_1_Port24"

exit

interface 13

   name "802-1q_To_Server_2_Port23"

exit

interface 14

   name "802-1q_To_Server_2_Port24"

exit

interface 15

   name "SAN1"

exit

interface 16

   name "SAN2"

exit

interface 17

   name "Guest_Wifi_1"

exit

interface 18

   name "Guest_Wifi_2"

exit

interface 23

   name "Ospf_10MB"

   speed-duplex 10-full

exit

interface 24

   name "Ospf_100MB"

   speed-duplex 100-full

exit

trunk 1-2 Trk1 Trunk

trunk 3-4 Trk2 Trunk

trunk 5-6 Trk3 Trunk

trunk 7-8 Trk4 Trunk

trunk 11-12 Trk5 Trunk

trunk 13-14 Trk6 Trunk

ip routing

vlan 1

   name "DEFAULT_VLAN"

   untagged 9-10,15-22,Trk1-Trk6

   ip address 192.168.101.254 255.255.255.0

   no untagged 23-24

   exit

vlan 160

   name "Data"

   ip address 192.168.160.254 255.255.255.0

   tagged Trk1-Trk6

   exit

vlan 161

   name "Voice"

   ip address 192.168.161.254 255.255.255.0

   tagged Trk1-Trk6

   exit

vlan 162

   name "Wireless"

   ip address 192.168.162.254 255.255.255.0

   tagged Trk1-Trk6

   exit

vlan 163

   name "Server"

   ip address 192.168.163.254 255.255.255.0

   tagged Trk1-Trk6

   exit

vlan 164

   name "San"

   ip address 192.168.164.254 255.255.255.0

   tagged Trk1-Trk6

   exit

vlan 165

   name "Gst_Wireless"

   ip address 192.168.165.254 255.255.255.0

   tagged Trk1-Trk6

   exit

vlan 172

   name "10MB Link"

   untagged 23

   ip address 172.16.16.2 255.255.255.0

   exit

vlan 173

   name "100MB Link"

   untagged 24

   ip address 172.16.17.2 255.255.255.0

   exit

router ospf

   area backbone

   redistribute connected

   exit

snmp-server community "public" unrestricted

spanning-tree Trk1 priority 4

spanning-tree Trk2 priority 4

spanning-tree Trk3 priority 4

spanning-tree Trk4 priority 4

spanning-tree Trk5 priority 4

spanning-tree Trk6 priority 4

vlan 172

   ip ospf 172.16.16.2 area backbone

   ip ospf 172.16.16.2 cost 200

   exit

vlan 173

   ip ospf 172.16.17.2 area backbone

   ip ospf 172.16.17.2 cost 110

   exit

no autorun

password manager

-------------------------------------------------------------------------------------------

-------------------------------------------------------------------------------------------

hostname "Site_B"

module 1 type J86xxA

interface 1

   name "802-1q_To_Data_1_Prt49"

exit

interface 2

   name "802-1q_To_Data_1_Prt50"

exit

interface 3

   name "802-1q_To_Data_2_Prt49"

exit

interface 4

   name "802-1q_To_Data_2_Prt50"

exit

interface 5

   name "802-1q_To_Voice_1_Prt49"

exit

interface 6

   name "802-1q_To_Voice_1_Prt50"

exit

interface 7

   name "802-1q_To_Voice_2_Prt25"

exit

interface 8

   name "802-1q_To_Voice_2_Prt26"

exit

interface 9

   name "Wifi Connection"

exit

interface 10

   name "Wifi Connection"

exit

interface 11

   name "802-1q_To_Voice_1_Prt23"

exit

interface 12

   name "802-1q_To_Voice_1_Prt24"

exit

interface 13

   name "802-1q_To_Voice_2_Prt23"

exit

interface 14

   name "802-1q_To_Voice_2_Prt24"

exit

interface 15

   name "SAN"

exit

interface 16

   name "SAN"

exit

interface 17

   name "PUBLIC WIFI"

exit

interface 18

   name "PUBLIC WIFI"

exit

interface 20

   name "Firewall 1"

exit

interface 21

   name "Firewall 2"

exit

interface 22

   name "Existing LAN"

exit

interface 23

   name "OSPF_10MB"

   speed-duplex 10-full

exit

interface 24

   name "OSPF_100MB""

   speed-duplex 100-full

exit

trunk 1-2 Trk1 Trunk

trunk 3-4 Trk2 Trunk

trunk 5-6 Trk3 Trunk

trunk 7-8 Trk4 Trunk

trunk 11-12 Trk5 Trunk

trunk 13-14 Trk6 Trunk

ip routing

vlan 1

   name "DEFAULT_VLAN"

   untagged 19-21,Trk1-Trk6

   ip address 192.168.100.254 255.255.255.0

   no untagged 9-10,15-18,22-24

   exit

vlan 150

   name "Data"

   ip address 192.168.150.254 255.255.255.0

   tagged Trk1-Trk6

   exit

vlan 151

   name "Voice"

   ip address 192.168.151.254 255.255.255.0

   tagged Trk1-Trk6

   exit

vlan 152

   name "Wireless"

   untagged 9-10

   ip address 192.168.152.254 255.255.255.0

   tagged Trk1-Trk6

   exit

vlan 153

   name "Server"

   ip address 192.168.153.254 255.255.255.0

   tagged Trk1-Trk6

   exit

vlan 154

   name "San"

   untagged 15-16

   ip address 192.168.154.254 255.255.255.0

   tagged Trk1-Trk6

   exit

vlan 155

   name "Gst_Wireless"

   untagged 17-18

   ip address 192.168.155.254 255.255.255.0

   tagged Trk1-Trk6

   exit

vlan 54

   name "Old_Torquay_Lan"

   untagged 22

   ip address 192.168.54.245 255.255.255.0

   exit

vlan 172

   name "VLAN172"

   untagged 23

   ip address 172.16.16.1 255.255.255.0

   exit

vlan 173

   name "VLAN173"

   untagged 24

   ip address 172.16.17.1 255.255.255.0

   exit

router ospf

   area backbone

   redistribute connected

   exit

snmp-server community "public" unrestricted

spanning-tree Trk1 priority 4

spanning-tree Trk2 priority 4

spanning-tree Trk3 priority 4

spanning-tree Trk4 priority 4

spanning-tree Trk5 priority 4

spanning-tree Trk6 priority 4

vlan 172

   ip ospf 172.16.16.1 area backbone

   ip ospf 172.16.16.1 cost 200

   exit

vlan 173

   ip ospf 172.16.17.1 area backbone

   ip ospf 172.16.17.1 cost 110

   exit

no autorun

password manager

password operator

[altpes]

Hello,

I am wondering if it is STP that keeps interface down as the link comes back up - did you check logs to see when the interface is coming up? OSPF updates are sent every 1 second by default...

I guess the switches are not directly connected and that is why you can't trunk the two interfaces :) Otherwise why wouldn't you do so?

When next time 100M interface comes up - run "sh ip ospf interface" command to see what is the state of the both interfaces. And compare it with the status when 1. Both links are up and 2. When only 10M is operational...

Sorry, won't be able to reply right away as I am leaving for couple of weeks today and won't be checking the forum, but hope this will help or someone else would be able to help further...

Cheers,

Evgueni

[Andy_Burchell]

Hi,

Of course STP why did'nt I think of that :), I will go and  try your suggestions now and let you know.

Thanks

[Fredrik Lönnman]

OSPF timers are 10 sec hellos and 40 sec dead timeout by default. This can be tuned down to 1/4 secs for faster convergence.

[ISoliman]

configure the interfaces with "spanning-tree <ports> bpdu-filter" in both ends and "spanning-tree <ports> admin-edge-port>

This will remove the ports from the spanning-tree calculation and should remain in the forwarding state, also why not using equal cost load-balancing and make the connections active active ? you will have to alter the cost to make both links become equal.

[key2rajiv]

Can SOmeone help me in confguring the same with three HP 3500 YL switches . Here we have 3 sites all connected to each with two redundant links . A triangular n/w diagram . Say for eg - Three sites A, B & C .

I need to route the traffic from A to B via link 1 first , if it fails then via link 2 . In case both fails between A & B i need to route the traffic via C to reach B from A , using the two redundant links between B & C 

                                                   A

                                               /  /   \  \

                                              / /      \  \

                                             B--------C

                                               ----------

Please provide the OSPF configs & route i need to add for the following configuration to accomplish .