Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
SFT Zones Critical Alarm
- Thread starter chode79
- Start date
Supernova99
Technical User
SFT zones are used on Per cabs (System Fail Transfer) and also on the very old SX2000S & SG basically it is a set of relays that can transfer analogue trunks to ONS extns
This alarm would be triggered if a system has programmed per cabs and also the system is in critical alarm.
You can mask the alarm via the maintenance command
set thr sft zone n n n
Share what you know - Learn what you don't
This alarm would be triggered if a system has programmed per cabs and also the system is in critical alarm.
You can mask the alarm via the maintenance command
set thr sft zone n n n
Share what you know - Learn what you don't
any time you do an upgrade, your alarm thresholds are reset to default.
as supernova mentioned, you possibly have a "phantom" per node for routing purposes.
simply reset the thresholds as he suggested.
you can do a "show fault alarm" in maintenace to see which cabinet is causing the alarm, that might indicate where to look if you don't have a phantom cabinet.
as supernova mentioned, you possibly have a "phantom" per node for routing purposes.
simply reset the thresholds as he suggested.
you can do a "show fault alarm" in maintenace to see which cabinet is causing the alarm, that might indicate where to look if you don't have a phantom cabinet.
- Thread starter
- #4
Thanks guys - I manipulated the threshold to get rid of the alarm just didnt know what the heck it was from. But you were right, I had a phantom ASU which was causing this alarm. Thanks again.
I got one more for ya.....now I have a SDS System Data alarm 0 out of 1. There is not a command to set the threshold for this one. Its throwing me a minor alarm. Is there any way of getting rid of this one?????? Thanks
I got one more for ya.....now I have a SDS System Data alarm 0 out of 1. There is not a command to set the threshold for this one. Its throwing me a minor alarm. Is there any way of getting rid of this one?????? Thanks
This is an SDS update error. Are you using SDS to distibute common data between 3300's?
To clear the alarm got to maintenance & diagnostics, logs, system data syncronization, shared data updates all. And you should see a pending change. This is what is causing the alarm as for what ever reason the update could not be applied. Make a note of what it is, then delete it. This will clear the alarm.
To clear the alarm got to maintenance & diagnostics, logs, system data syncronization, shared data updates all. And you should see a pending change. This is what is causing the alarm as for what ever reason the update could not be applied. Make a note of what it is, then delete it. This will clear the alarm.
Supernova99
Technical User
Be careful deleting SDS errors.
There is normally a very good reason why the error has occured. Sometimes on a large cluster, that has had some network disruption when SDS changes were made, can throw up errors when all systems are trying to update at the same time. This is normally a concurrent change error.
You can select the error and click on retry first, this normally clears the error.
There maybe other reasons where there are number clashes for e.g. ARS digits clashing with system speed calls on one of the systems. The SDS error will show what has caused the error.
Share what you know - Learn what you don't
There is normally a very good reason why the error has occured. Sometimes on a large cluster, that has had some network disruption when SDS changes were made, can throw up errors when all systems are trying to update at the same time. This is normally a concurrent change error.
You can select the error and click on retry first, this normally clears the error.
There maybe other reasons where there are number clashes for e.g. ARS digits clashing with system speed calls on one of the systems. The SDS error will show what has caused the error.
Share what you know - Learn what you don't
- Status
Similar threads
- Locked
- Question