supervisor takeover

[start_up]

our site occur five times supervisor failover once a month since last year(11.18.2013) [BELOW] our failure chassis information ************************************************************************** SW_1#sh redundancy states my state = 13 -ACTIVE peer state = 8 -STANDBY HOT Mode = Duplex Unit = Secondary Unit ID = 1 Redundancy Mode (Operational) = Stateful Switchover Redundancy Mode (Configured) = Stateful Switchover Split Mode = Disabled Manual Swact = Enabled Communications = Up client count = 22 client_notification_TMR = 240000 milliseconds keep_alive TMR = 9000 milliseconds keep_alive count = 1 keep_alive threshold = 18 RF debug mask = 0x0 SW_1#show mod Chassis Type : WS-C4507R Mod Redundancy role Redundancy mode Redundancy status ----+-------------------+-------------------+------------------- 1 Active Supervisor SSO Active 2 Standby Supervisor SSO Standby hot *********************************************************************************************** Q1) my state = 13 -ACTIVE peer state = 8 -STANDBY HOT Mode = Duplex Unit = Secondary Unit ID = 1 what's meaning?? unit = secondary i think it is Active supervisor's state. so it will be primary. ex) Mod Redundancy role Redundancy mode Redundancy status ----+-------------------+-------------------+------------------- 1 Active Supervisor SSO Standby hot 2 Standby Supervisor SSO Active 1 module is always primary 2 module is alway secondary IS IT TRUE OR NOT. ANSWER ANY INFORMATION PLZ.. TEHN what's problem. (SUPERVISOR OR CHASSIS)

[Renan Abreu]

Hi start_up,

     You post got confusing, can you past again the commands and the question?

[Bilal Nawaz]

Hi Sorry for the off topic, however this is the outcome of the post (all text in line) from a mobile device no matter how hard you try. Well at least this is what I experienced.