[c-nsp] Supervisor Failover - Speed question
Michael Lee
fwissue at gmail.com
Wed Apr 8 21:53:52 EDT 2009
did you try enable nsf if it is possible? there are some limitation on
mpls-te
On Wed, Apr 8, 2009 at 4:44 PM, Paul Stewart <paul at paulstewart.org> wrote:
> Hi there.
>
>
>
> We have 7606's with dual Sup720-3BXL. I'm investigating how to get the
> fastest possible failover if/when a supervisor fails.
>
>
>
> Current config looks like this:
>
>
>
> my state = 13 -ACTIVE
>
> peer state = 8 -STANDBY HOT
>
> Mode = Duplex
>
> Unit = Primary
>
> Unit ID = 5
>
>
>
> Redundancy Mode (Operational) = sso
>
> Redundancy Mode (Configured) = sso
>
> Redundancy State = sso
>
> Maintenance Mode = Disabled
>
> Communications = Up
>
>
>
> client count = 78
>
> client_notification_TMR = 30000 milliseconds
>
> keep_alive TMR = 9000 milliseconds
>
> keep_alive count = 0
>
> keep_alive threshold = 18
>
> RF debug mask = 0x0
>
>
>
> --
>
>
>
> redundancy
>
> keepalive-enable
>
> mode sso
>
> main-cpu
>
> auto-sync running-config
>
>
>
>
>
>
>
> Is there any way to get a failover to less than 30 seconds an example? We
> find currently it's 2-3 minutes for failover it seems..
>
>
>
> Thanks,
>
>
>
> Paul
>
>
>
> _______________________________________________
> cisco-nsp mailing list cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
More information about the cisco-nsp
mailing list