Stan,
Without seeing configs it's a little hard to diagnose, but two things come
to mind. Preempt on HSRP. Are you using it? Second, it sounds like you
have layer two redunancy, so spanning tree should have a link in Blocking
mode. When you test a failure, this link will start forwarding (how quickly
depends on a few things) so your HSRP may flap back and forth until things
settle down(converge). You need to use HSRP "track" to force the priorities
to be correct in a failed state. You may also need to tweek the HSRP
timers.
I'm about to embark on a very large implementation just like you describe.
I pray it goes smoothly.
Rodgers Moore
""Rossetti, Stan"" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Could someone tell me if they have seen this problem before or have any
> suggestions.
>
> Scenario:
>
> We have 2 6509 switches with msfc cards in each on the 1st floor and 4th
> floor of a building. We have redundant links between the switches and
each
> switch has redundant sup 1 cards with the msfc blades. We also have 2
more
> 6509 switches on the 2nd and 3rd floors of the same building. The first
> floor switch is connected to the outside world through a 7206 router.
There
> are multiple vlan across each switch that are connected to the user
through
> several 3500 series switches on each floor. When we first turned HSRP on,
> the msfc1 vlans did not come up. We get Cisco online and they said we had
a
> bad msfc card. So we switched over to the redundant msfc card (msfc2).
The
> vlans came up and hsrp between the switches was working (exchange hello
> packets and send standby info). Each vlan knew of the other vlan standby
> router and ip address. To run a test we disabled our connection to the
> outside world to localize any problems and brought up continuous ping
> sessions between the switches and vlans on the 1st and 4th. Next we shut
> down the 1st floor switch. (Note: The 1st floor switch has the higher
> priority). The network went down and hsrp did no swap over to the standby
> switch. Additionally, when we disconnect the cable between the 1st floor
> and 4th floor switch we see duplicate ip address errors. We saw the same
> duplicate ip errors the last time we disconnected the cable between the
1st
> and 4th floor switches, but that was before we had hsrp installed.
>
> Some other useful info:
>
> About 3 weeks ago, before we installed the 1st floor switch the 4th floor
> switch acted as the interface to the outside world through the msfc card
> that cisco now says is bad. Then we installed the 1st floor switch and
move
> all connections through the 1st floor switch. Essentially the 1st floor
> switch became the interface to the outside world with redundant link to
the
> 4th floor and 2nd floor switch. When we did this the vlan could not talk
to
> each other. Which means that we could ping the msfc card from the outside
> world but not the 6509 switch. Internally, we could ping the 6509 switch,
> but not the outside world. To isolate the problem we removed the
connection
> to the 1st and 4th floor switches like we did above and everything came
up,
> but we saw the same duplicate ip address errors. We did a hardware reset
of
> the switch and reconnected the 1st and 4th floor switches and everything
> started working correctly. Any ideas? This make no sense to me and
> installing HSRP should not be an 8 ordeal.
>
>
>
> Thanks,
>
> Stan Rossetti
>
>
> Russia Services Group
> Email: [EMAIL PROTECTED]
> Phone: (256) 544-5031
> Beeper: 544-1183 pin # 0112
>
> <<...>>
>
>
>
> _________________________________
> FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
