all of my access switches are dual homed to both gateways, with the hsrp address as the gateway. Killing gateway 1 should have no effect other than a hsrp switchover...
If you have access host single homed to a given gateway then I would agree with you.. Larry Letterman Cisco Systems [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Michael L. Williams Sent: Tuesday, August 20, 2002 5:36 AM To: [EMAIL PROTECTED] Subject: Re: Multiple Supervisors 6509 Chassis; Native IOS [7:51654] Well, one good reason to have 2 sups in each chassis is that if one Sup does die, sure HSRP will kick in and the other 6500 will be the gateway, but only for the devices connected to the switch that's still "up".... all of the devices on the 6500 that had the Sup die will be down and down hard (unless there is some way that Layer 2 functions continue even tho the sup died which I can't imagine). With a second Sup, at least after about 2 minutes, all of those devices will have connectivity restored as well..... Mike W. "Larry Letterman" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > If you have two gateways(6509's) why goto the expense of two msfc's > in each chassis ? The failure should cause the hsrp to switch to the > secondary > 6509. Thats the way we run ours on our campus... > > > Larry Letterman > Cisco Systems > [EMAIL PROTECTED] > > > > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of > Michael L. Williams > Sent: Monday, August 19, 2002 7:23 PM > To: [EMAIL PROTECTED] > Subject: Re: Multiple Supervisors 6509 Chassis; Native IOS [7:51654] > > > When you have two Sups and you're running Native IOS, you cannot run HSRP > between them...as you mentioned, one sup is active and the other is standby > and there's about 90-120 seconds of downtime when one sup fails because the > other sup has to re-initialize the hardware (the standby sup (if you watch > from a console while it boots) actually boots part way.... it loads IOS but > then waits... when the other sup fails, it "finishes" the boot process by > initializing the blades and then running as normal) > > We have 2 6509s, and we run HSRP between the sups on them so that if there > is a sup failure, only the devices attached to the switch with the failed > sup are affected..... the others work fine because HSRP will keep at least > one MSFC up and running. > > If you use the following commands in global config mode, it will setup so > that when you make config changes on the primary sup and save them, that it > will automatically update the config on the backup sup too..... > > redundancy > main-cpu > auto-sync standard > > Mike W. > > "Maximus" wrote in message > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > This is how I learn: =) > > Running IOS on my 6509, I wanted to see the amount of downtime I would > cause > > by deliberately causing the primary SUP to fail by one executing a reload > on > > the primary module and two simply pulling the primary from the chassis. > > heeheehee > > > > What I found was the reload caused approximately 2 minutes downtime. This > > was because the entire chassis of course booted. The secondary module did > > however become the primary almost immediately following the reload > command. > > Now I figure that if I just removed the primary blade the system would > > failover immediately and not reboot my 10/100/1000 blades. To my > surprise, > > this resulted in again 1 minute and 50 seconds downtime and network > > connectivity was restored. BTW The blades also appeared to reboot. > > > > In terms of High Availability am I missing something? Considering these > > results what would deter me from just sticking to HSRP. I am a novice and > > looking for some constructive input. With that said note the following: > > > > IOS: > > Cisco Catalyst 6000 (R7000) processor with 112640K/18432K bytes of memory. > > R7000 CPU at 300Mhz, Implementation 39, Rev 2.1, 256KB L2, 1024KB L3 Cache > > ROM: System Bootstrap, Version 12.1(11r)E1, RELEASE SOFTWARE (fc1) > > BOOTLDR: c6sup2_rp Software (c6sup2_rp-JSV-M), Version 12.1(11b)E4, EARLY > > DEPLOYMENT RELEASE SOFTWARE (fc1) > > > > Hardware: > > Router>sh mod > > Mod Ports Card Type Model Serial > > No. > > --- ----- -------------------------------------- ------------------ ------ > -- > > --- > > 1 2 Cat 6k sup 1 Enhanced QoS (Standby) WS-X6K-SUP1A-2GE > > 2 2 Cat 6k sup 1 Enhanced QoS (Active) WS-X6K-SUP1A-2GE > > 4 16 16 port 1000mb GBIC ethernet WS-X6416-GBIC > > 9 48 48 port 10/100 mb RJ45 WS-X6348-RJ-45 > > > > Comments? > > -Maximus Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=51793&t=51654 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
