11-02-2010 04:49 AM
11-02-2010 05:20 AM
Could also be a non-set rescue config. Issue these commands in operation mode and we will know more:
> show chassis alarm > show system alarm
The Axiom of Choice is obviously true, the well-ordering principle obviously false, and who can tell about Zorn's lemma?
11-03-2010 03:52 AM
i have save rescue and also monitor as per ur efforts , find there is utm license alarm only no more then this.
i have posted the config and monitored config also plz details it and reply with solution.ok hope you will efforts me.
11-03-2010 07:13 AM
I think that the amber HA light is indicative of a problem with the HA control links. If you look at the statistics, it would seem that there is a fairly large difference between the heartbeats sent and the heartbeats received. Have you checked the cabling to ensure that you do not have a bad cable here? I think that the rescue config, license alarms, etc. would result in an alarm LED being lit, but the HA light should only be impacted by HA events.
11-03-2010 11:09 AM
That light will stay amber - and the priority will be 0, when you check the chassis cluster status - until all monitored interfaces are up. The majority of your interfaces are down, and that's why you see the light.
11-04-2010 08:31 AM
Just to add that when I look at your UTM policies , it seems that the UTM is never hit as it is placed below the generic policy. Please change the order of the policies .
11-07-2010 11:14 AM
If you want to be sure, there is a nice (but hidden) command: show chassis cluster information
This will show you lots of details about the cluster status, the status of the LED and the reason is one of them:
Chassis cluster LED information:
Current LED color: Amber
Last LED change reason: Monitored objects are down