Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

6500 HSRP failover

Hi Commnity,

We have two cisco 6500 swtiches. Switch A is a active state of HSRP and Switch B in stanby state, After 2 days we are going have go-live test for Switches failove redudancy.

Please see the sample HSRP confiuration for both switches

SWTICH A

interface Vlan 100
description << RECEPTION>>
ip address 10.1.2.254 255.255.255.0
ip route-cache flow
standby delay minimum 20 reload 25
standby 3 ip 10.1.2.1
standby 3 priority 110
standby 3 preempt delay minimum 380

SWITCH B

interface Vlan3
description << RECEPTION>>
ip address 10.1.2.253 255.255.255.0
ip route-cache flow
standby delay minimum 20 reload 25
standby 3 ip 10.1.2.1
standby 3 priority 95
standby 3 preempt delay minimum 380

SWITCH A# sh stanby brief

Interface   Grp      Prio      P     State        Active addr     Standby addr    Group addr

Vl3            3        110      P     Active       local              10.1.2.253        10.1.2.1

SWITCH B #

Interface   Grp      Prio      P     State        Active addr     Standby addr    Group addr

Vl3            3        95        P     Standby    local               local       10.1.2.1

If there is any misconfiguration, your sugesstion will be highly appreciated.

53 REPLIES
Hall of Fame Super Blue

Re: 6500 HSRP failover

Looks okay to me. Just remember there will be delays in failing over and failing back again because you have delay timers but it shoudl all work fine.

Jon

New Member

Re: 6500 HSRP failover

Thanks for your reply.

You mean to say that it will take 380 seconds for standby to cover the failover.

Re: 6500 HSRP failover

it would be great if you set interface tracking on your uplinks to your core router/s. see helpful link below.

http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a0080094e8c.shtml

New Member

Re: 6500 HSRP failover

Hi

For testing purpose I shut down vlan interface by using the command shut

but stanby switch was not able to take over.


output of sh stanby brief command on stanby switch

Vl19        19  95   P Active   local           unknown         10.1.18.1

output of sh stanby brief command on previously active swithc

Vl19        19  110  P Init     unknown         unknown         10.1.18.1

Please help me Why does it happen ?

New Member

Re: 6500 HSRP failover

You may want to verify the two switches are linked together with layer 3..

New Member

Re: 6500 HSRP failover

Yes. The two switches are connected to each other and it is trunk.

New Member

Re: 6500 HSRP failover

Do you have any of the switchports set to Vlan 19 and a system connected to that port?

ie; switchport access vlan 19, switchport mode access

Sometimes the vlan does not come up completely if not.

Also, doing some HSRP debugs would probably give some clues..

http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a0080094a91.shtml#enhanced

---Mike

New Member

Re: 6500 HSRP failover

Yes I have systems to switchport and they are configrured in that vlan ie switcport access vlan 19.

however that vlan is up

The issue I am facing right now is

When I shutdown the vlan 19 and after doing that systems in this vlan cannot ping any other device but i can ping virtual ip

Hall of Fame Super Blue

Re: 6500 HSRP failover

samirshaikh52 wrote:

Hi

For testing purpose I shut down vlan interface by using the command shut

but stanby switch was not able to take over.


output of sh stanby brief command on stanby switch

Vl19        19  95   P Active   local           unknown         10.1.18.1

output of sh stanby brief command on previously active swithc

Vl19        19  110  P Init     unknown         unknown         10.1.18.1

Please help me Why does it happen ?

This output shows that it has worked ie.

the standby is active for that vlan and you get the "unknown" because you have shutdown the interface on the other switch.

This is exactly what you would expect to see so can you clarify exactly what problems you are having ?

Jon

New Member

Re: 6500 HSRP failover

But presently I am facing this issue

After shuting down the vlan interface 19, the systems in this vlan cannot reach other device.However I can ping the vip from the system.

New Member

Re: 6500 HSRP failover

Please try to help me I am trying to solve this issue last two

days.

New Member

Re: 6500 HSRP failover

Another thing you may want to check is to make sure that vlan is included in the trunk between both switches and not pruned...

New Member

Re: 6500 HSRP failover

I have double checked the vlan is included with the trunk and its not pruned.

New Member

Re: 6500 HSRP failover

The only other things that I can think of is to clear arp on both switches and verify the hosts

have the correct ip settings, especially the mask.

New Member

Re: 6500 HSRP failover

I am 100% sure with ip settings on the pc..it is ok

and i have check arp cache.

Really this problem is driving me crazy.

Would you like to see STP config, if anything related to this issue.

Hall of Fame Super Blue

Re: 6500 HSRP failover

samirshaikh52 wrote:

But presently I am facing this issue

After shuting down the vlan interface 19, the systems in this vlan cannot reach other device.However I can ping the vip from the system.

We need fair bit more info. Can you -

1) provide the config of vlan 19 off both switches

2) provide "sh int trunk" from the 6500 switches and indicate which trunk is the one connecting the 2 6500 switches.

the device you are pinging from -

1) if it is windows can you provide the output of "ipconfig /all"

the switch that this device is connected to -

1) can you provide output of "sh int trunk" indicating which trunk links are connected to the 6500 switches.

I will need all of the above info.

Jon

New Member

Re: 6500 HSRP failover

Clear arp instead of checking could take care of arp poisining

I think I would also try to minimize the hsrp config to just:

standby ip x.x.x.x

otherwise, what Jon says

New Member

Re: 6500 HSRP failover

Hi jon,


1. config of vlan 19

interface Vlan19
ip address 10.1.19.254 255.255.255.0
ip route-cache flow
standby 19 ip 10.1.19.1
standby 19 timers 5 15
standby 19 priority 110
standby 19 preempt

2. output of sh int trunk

Core A

Port        Mode    Encapsulation        Status      Native Vlan

Gi2/23    desirable    n-isl                 trunking      1

Port                  Vlans Allowed

Gi2/23               1-29,40,100-103

Port                 Vlans in spanning tree forwarding state and not pruned

Gi2/23              1-29,40,100-103

Core B

Port        Mode    Encapsulation        Status      Native Vlan

Gi2/23    desirable    n-isl                 trunking      1

Port                  Vlans Allowed

Gi2/23               1-29,40,100-103

Port                 Vlans in spanning tree forwarding state and not pruned

Gi2/23              1-29,40,100-103

3. ouput of ipconfig /all


Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) 82567LM-3 Gigabit Network Connec
tion
   Physical Address. . . . . . . . . : 00-23-7D-49-A5-BE
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 10.1.19.10(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 10.1.19.1
   DNS Servers . . . . . . . . . . . : 10.1.2.2
                                               10.1.2.4
   NetBIOS over Tcpip. . . . . . . . : Enabled

4. sh int trunk

Port      Mode         Encapsulation  Status        Native vlan
Gi1/1     desirable    n-802.1q       trunking      1
Gi1/2     desirable    n-isl          trunking      1
Gi1/3     desirable    n-isl          trunking      1
Gi1/4     desirable    n-isl          trunking      1
Gi1/5     desirable    n-isl          trunking      1
Gi1/6     desirable    n-isl          trunking      1
Gi1/7     desirable    n-isl          trunking      1
Gi1/8     desirable    n-isl          trunking      1
Gi1/9     desirable    n-isl          trunking      1
Gi1/10    desirable    n-isl          trunking      1
Gi1/11    desirable    n-802.1q       trunking      1
Gi1/12    desirable    n-isl          trunking      1
Gi1/13    desirable    n-isl          trunking      1
Gi1/14    desirable    n-isl          trunking      1
Gi1/15    desirable    n-isl          trunking      1
Gi1/16    desirable    n-isl          trunking      1
Gi1/17    desirable    n-isl          trunking      1
Gi1/18    desirable    n-isl          trunking      1
Gi1/19    desirable    n-isl          trunking      1
Gi1/20    desirable    n-isl          trunking      1
Gi1/21    desirable    n-isl          trunking      1
Gi1/22    desirable    n-isl          trunking      1
Gi1/23    desirable    n-isl          trunking      1
Gi1/24    desirable    n-isl          trunking      1
Gi2/1     desirable    n-isl          trunking      1
Gi2/2     desirable    n-isl          trunking      1
Gi2/3     desirable    n-802.1q       trunking      1
Gi2/4     desirable    n-isl          trunking      1
Gi2/5     desirable    n-802.1q       trunking      1
Gi2/6     desirable    n-802.1q       trunking      1
Gi2/23    desirable    n-isl          trunking      1
Gi2/24    desirable    n-802.1q       trunking      1

Port      Vlans allowed on trunk
Gi1/1     1-4094
Gi1/2     1-4094
Gi1/3     1-4094
Gi1/4     1-4094
Gi1/5     1-4094
Gi1/6     1-4094
Gi1/7     1-4094
Gi1/8     1-4094
Gi1/9     1-4094
Gi1/10    1-4094
Gi1/11    1-4094
Gi1/12    1-4094
Gi1/13    1-4094
Gi1/14    1-4094
Gi1/15    1-4094
Gi1/16    1-4094
Gi1/17    1-4094
Gi1/18    1-4094
Gi1/19    1-4094
Gi1/20    1-4094
Gi1/21    1-4094
Gi1/22    1-4094
Gi1/23    1-4094
Gi1/24    1-4094
Gi2/1     1-4094

Port      Vlans allowed on trunk
Gi2/2     1-4094
Gi2/3     1-4094
Gi2/4     1-4094
Gi2/5     1-4094
Gi2/6     1-4094
Gi2/23    1-4094
Gi2/24    1-4094

Port      Vlans allowed and active in management domain
Gi1/1     1-29,40,100-103
Gi1/2     1-29,40,100-103
Gi1/3     1-29,40,100-103
Gi1/4     1-29,40,100-103
Gi1/5     1-29,40,100-103
Gi1/6     1-29,40,100-103
Gi1/7     1-29,40,100-103
Gi1/8     1-29,40,100-103
Gi1/9     1-29,40,100-103
Gi1/10    1-29,40,100-103
Gi1/11    1-29,40,100-103
Gi1/12    1-29,40,100-103
Gi1/13    1-29,40,100-103
Gi1/14    1-29,40,100-103
Gi1/15    1-29,40,100-103
Gi1/16    1-29,40,100-103
Gi1/17    1-29,40,100-103
Gi1/18    1-29,40,100-103
Gi1/19    1-29,40,100-103
Gi1/20    1-29,40,100-103
Gi1/21    1-29,40,100-103
Gi1/22    1-29,40,100-103
Gi1/23    1-29,40,100-103
Gi1/24    1-29,40,100-103
Gi2/1     1-29,40,100-103
Gi2/2     1-29,40,100-103
Gi2/3     1-29,40,100-103
Gi2/4     1-29,40,100-103
Gi2/5     1-29,40,100-103
Gi2/6     1-29,40,100-103
Gi2/23    1-29,40,100-103
Gi2/24    1-29,40,100-103

Port      Vlans in spanning tree forwarding state and not pruned
Gi1/1     1-29,40,100-103
Gi1/2     1-29,40,100-103
Gi1/3     1-29,40,100-103
Gi1/4     1-29,40,100-103
Gi1/5     1-29,40,100-103
Gi1/6     1-29,40,100-103
Gi1/7     1-29,40,100-103
Gi1/8     1-29,40,100-103
Gi1/9     1-29,40,100-103
Gi1/10    1-29,40,100-103
Gi1/11    1-29,40,100-103
Gi1/12    1-29,40,100-103
Gi1/13    1-29,40,100-103
Gi1/14    1-29,40,100-103
Gi1/15    1-29,40,100-103
Gi1/16    1-29,40,100-103
Gi1/17    1-29,40,100-103
Gi1/18    1-29,40,100-103

Port      Vlans in spanning tree forwarding state and not pruned
Gi1/19    1-29,40,100-103
Gi1/20    1-29,40,100-103
Gi1/21    1-29,40,100-103
Gi1/22    1-29,40,100-103
Gi1/23    1-29,40,100-103
Gi1/24    1-29,40,100-103
Gi2/1     1-29,40,100-103
Gi2/2     1-29,40,100-103
Gi2/3     1-29,40,100-103
Gi2/4     1-29,40,100-103
Gi2/5     1-29,40,100-103
Gi2/6     1-29,40,100-103
Gi2/23    1-29,40,100-103
Gi2/24    1-29,40,100-103

Hall of Fame Super Blue

Re: 6500 HSRP failover

Okay that all looks okay but one thing -

in your previous post of "sh standby brief" after shutting the active interface the VIP is 10.1.18.1

whereas in the most recent output it is 10.1.19.1

Can you clarify ?

Jon

New Member

Re: 6500 HSRP failover

It is 10.1.19.1

During the testing I made some changes.

Hall of Fame Super Blue

Re: 6500 HSRP failover

So have you tested it with both set to 10.1.19.1 ??

The switch that the device is connected to has a lot of trunk links. How it is connected to the core switches and how is it connected to other switches.

More importantly can you run this command on that switch and both 6500 switches -

sh spantree vlan 19

Jon

New Member

Re: 6500 HSRP failover

I have takene the output of sh spanning-tree vlan 19 on core A and B and access switch

Please see the attached

Thanks for your efforts

Hall of Fame Super Blue

Re: 6500 HSRP failover

Thanks, but i'm confused again.

Your switch shows these links -

Gi1/0/8             Desg FWD 100       128.8    P2p
Gi1/0/16            Desg FWD 19        128.16   P2p
Gi1/0/49            Root FWD 4         128.49   P2p
Gi1/0/50            Altn BLK 4         128.50   P2p

but from previous output where you posted "sh int trunk" (no 4 in the list of outputs) from the access switch none of these ports are present. So what did you post before ? What switch was that ?

You need to make the information consistent or else it is very hard to help you.

From the above outputs which is the connection back to the 6500 - presumably gi1/0/49 ? Can you confirm that is the connection back to the 6500 switch and also can you post "sh int trunk" from this device.

Jon

New Member

Re: 6500 HSRP failover

No 4 in the previous post was the complete output of sh int trunk for CORE A


This links was for the access switch.

Gi1/0/8             Desg FWD 100       128.8    P2p
Gi1/0/16            Desg FWD 19        128.16   P2p
Gi1/0/49            Root FWD 4         128.49   P2p
Gi1/0/50            Altn BLK 4         128.50   P2p


Here it is the output of sh int trunk on access switch

Port        Mode             Encapsulation  Status        Native vlan
Gi1/0/49    on               802.1q         trunking      1
Gi1/0/50    on               802.1q         trunking      1

Yes. Gi1/0/49 is the connection port to CORE A

and Gi1//0/50 is the connection to CORE B

Port        Vlans allowed on trunk
Gi1/0/49    1-4094
Gi1/0/50    1-4094

Port        Vlans allowed and active in management domain
Gi1/0/49    1-29,40,100-103
Gi1/0/50    1-29,40,100-103

Port        Vlans in spanning tree forwarding state and not pruned
Gi1/0/49    1-29,40,100-103
Gi1/0/50    none

Hall of Fame Super Blue

Re: 6500 HSRP failover

Okay, thanks for that.

There is nothing wrong as far as i can see with your config for vlan 19 assuming you have tested using 10.1.9.1 on both switches. So assuming it is not a problem with vlan 19 -

But presently I am facing this issue

After shuting down the vlan interface 19, the systems in this vlan cannot reach other device.However I can ping the vip from the system.

what device are you trying to reach in one of the other vlans ?

So your source device is vlan 19, what are device are you trying to get to ie. what vlan is it in ? We may well have to go through a similiar process for this vlan as well if that's okay with you ?

So firstly, what vlan is the other device in, what switch is it connected to, how is this switch connected to the 6500 switches ?

Jon

New Member

Re: 6500 HSRP failover

I am trying to reach a device which is in vlan 2 and it is connected switch located in othe floor.

I have no problem to provide more info.

Big thanks for your efforts

Hall of Fame Super Blue

Re: 6500 HSRP failover

samirshaikh52 wrote:

I am trying to reach a device which is in vlan 2 and it is connected switch located in othe floor.

I have no problem to provide more info.

Big thanks for your efforts

Okay this switch, is it also connected to 6500 switches ? If so -

1) when you shutdown the active HSRP gateway for vlan 19 so it fails over to the other 6500 where is the active gateway for vlan 2 ie. is it on the switch with the shutdown vlan 19 interface or is it on the switch with the now active vlan 19 interface.

2) Can you post "sh int trunk" from this other switch with vlan 2.

3) can you post "sh spantree vlan 2" from 6500 switches and this other switch.

Note i'm assuming that vlan 2 is also routed on the 6500 switch, if it isn't before providing the above outputs can you confirm where it is routed from.

Jon

New Member

Re: 6500 HSRP failover

Yes this switch is also connected to both CORE A and CORE B

1. It is on the switch with shutdown interface vlan 19

2.sh int trunk from the other switch

Port        Mode             Encapsulation  Status        Native vlan
Gi1/0/49    on               802.1q         trunking      1
Gi1/0/50    on               802.1q         trunking      1

Port        Vlans allowed on trunk
Gi1/0/49    1-4094
Gi1/0/50    1-4094

Port        Vlans allowed and active in management domain
Gi1/0/49    1-29,40,100-103
Gi1/0/50    1-29,40,100-103

Port        Vlans in spanning tree forwarding state and not pruned
Gi1/0/49    1-29,40,100-103
Gi1/0/50    none



AND VLAN 2 is routed on CORE A

3. CORE A - sh spanning-tree vlan 2

VLAN0002
  Spanning tree enabled protocol ieee
  Root ID    Priority    8192
             Address     001a.e3f5.4402
             This bridge is the root
             Hello Time   2 sec  Max Age 20 sec  Forward Delay 15 sec

  Bridge ID  Priority    8192
             Address     001a.e3f5.4402
             Hello Time   2 sec  Max Age 20 sec  Forward Delay 15 sec
             Aging Time 300

Interface        Role Sts Cost      Prio.Nbr Type
---------------- ---- --- --------- -------- -------------------------
Gi1/1            Desg FWD 4         128.1    P2p
Gi1/2            Desg FWD 4         128.2    P2p
Gi1/3            Desg FWD 4         128.3    P2p
Gi1/4            Desg FWD 4         128.4    P2p
Gi1/5            Desg FWD 4         128.5    P2p
Gi1/6            Desg FWD 4         128.6    P2p
Gi1/7            Desg FWD 4         128.7    P2p
Gi1/8            Desg FWD 4         128.8    P2p
Gi1/9            Desg FWD 4         128.9    P2p

Interface        Role Sts Cost      Prio.Nbr Type
---------------- ---- --- --------- -------- -------------------------

Gi1/10           Desg FWD 4         128.10   P2p
Gi1/11           Desg FWD 4         128.11   P2p
Gi1/12           Desg FWD 4         128.12   P2p
Gi1/13           Desg FWD 4         128.13   P2p
Gi1/14           Desg FWD 4         128.14   P2p
Gi1/15           Desg FWD 4         128.15   P2p
Gi1/16           Desg FWD 4         128.16   P2p
Gi1/17           Desg FWD 4         128.17   P2p
Gi1/18           Desg FWD 4         128.18   P2p
Gi1/19           Desg FWD 4         128.19   P2p
Gi1/20           Desg FWD 4         128.20   P2p
Gi1/21           Desg FWD 4         128.21   P2p
Gi1/22           Desg FWD 4         128.22   P2p
Gi1/23           Desg FWD 4         128.23   P2p
Gi1/24           Desg FWD 4         128.24   P2p
Gi2/1            Desg FWD 4         128.129  P2p
Gi2/2            Desg FWD 4         128.130  P2p
Gi2/3            Desg FWD 4         128.131  P2p
Gi2/4            Desg FWD 4         128.132  P2p
Gi2/6            Desg FWD 4         128.134  P2p
Gi2/7            Desg FWD 4         128.135  P2p
Gi2/8            Desg FWD 4         128.136  P2p
Gi2/23           Desg FWD 4         128.151  P2p

CORE- sh spanning-tree vlan 2

VLAN0002
  Spanning tree enabled protocol ieee
  Root ID    Priority    8192
             Address     001a.e3f5.4402
             Cost        4
             Port        151 (GigabitEthernet2/23)
             Hello Time   2 sec  Max Age 20 sec  Forw

  Bridge ID  Priority    16384
             Address     001a.e3f5.5402
             Hello Time   2 sec  Max Age 20 sec  Forw
             Aging Time 300

Interface        Role Sts Cost      Prio.Nbr Type
---------------- ---- --- --------- -------- --------
Gi1/1            Desg FWD 4         128.1    P2p
Gi1/2            Desg FWD 4         128.2    P2p
Gi1/3            Desg FWD 4         128.3    P2p
Gi1/4            Desg FWD 4         128.4    P2p
Gi1/5            Desg FWD 4         128.5    P2p
Gi1/6            Desg FWD 4         128.6    P2p
Gi1/7            Desg FWD 4         128.7    P2p
Gi1/8            Desg FWD 4         128.8    P2p

Interface        Role Sts Cost      Prio.Nbr Type
---------------- ---- --- --------- -------- --------

Gi1/9            Desg FWD 4         128.9    P2p
Gi1/10           Desg FWD 4         128.10   P2p
Gi1/11           Desg FWD 4         128.11   P2p
Gi1/12           Desg FWD 4         128.12   P2p
Gi1/13           Desg FWD 4         128.13   P2p
Gi1/14           Desg FWD 4         128.14   P2p
Gi1/15           Desg FWD 4         128.15   P2p
Gi1/16           Desg FWD 4         128.16   P2p
Gi1/17           Desg FWD 4         128.17   P2p
Gi1/18           Desg FWD 4         128.18   P2p
Gi1/19           Desg FWD 4         128.19   P2p
Gi1/20           Desg FWD 4         128.20   P2p
Gi1/21           Desg FWD 4         128.21   P2p
Gi1/22           Desg FWD 4         128.22   P2p
Gi1/23           Desg FWD 4         128.23   P2p
Gi1/24           Desg FWD 4         128.24   P2p
Gi2/1            Desg FWD 4         128.129  P2p
Gi2/2            Desg FWD 4         128.130  P2p
Gi2/3            Desg FWD 4         128.131  P2p
Gi2/4            Desg FWD 4         128.132  P2p
Gi2/5            Desg FWD 4         128.133  P2p
Gi2/6            Desg FWD 4         128.134  P2p
Gi2/23           Root FWD 4         128.151  P2p
Gi2/24           Desg FWD 4         128.152  P2p

Hall of Fame Super Blue

Re: 6500 HSRP failover

Okay, nothing obvious.

When you shutdown the vlan 19 interface and failover you cannot ping a device in vlan 2 from a device in vlan 19.

Can you ping the vlan 2 VIP from the device in vlan 19 when the vlan 19 interface has failed over ?

Also it's getting a bit late here in UK so i'll have to pick this one up tomorrow.

Edit - can you also post the L3 vlan interface configuration from both 6500 switches for -

vlan 19 ( i know you've posted before but please again)

vlan 2

Jon

4014
Views
0
Helpful
53
Replies
CreatePlease login to create content