Hi,
for weeks OmniVista (for an OXE 9.0) shows regularky (hourly) the message below. I´m just asking myself, what it actually wants to tell me? What is going wrong? Do you have any ideas?
No. 4572
Managed Object
Event Type Quality of Service Alarm
Notification Date 12/15/09 09:42:22 PM
Probable Cause Unknown
Severity Major
Reception Date 12/15/09 09:43:01 PM
Notification ID 34101
Additional Text Alarm : SET resources quantity critical
Information Diagnostic Fault ID: 2140
Diagnostic "Alarm : P1 resources quantity critical
P1 : Resource category
Maintenance incident
The number of elements of P1 category present in the system is lower than the
minimum satisfactory threshold (Standard for Quality of Service).
On lack of trunk resource, the alarm relay is activated as well as a station
alarm if it is configured (Alarm 3 by default).
Check the boards which contain some equipment of the category concerned are
correctly slotted in.
"
Remark
Information Diagnostic Fault ID: 2140
-
Pixel.Nine
-
Decoder
Hej Kinne,
You might want to check your GA (s) (gateway application processing unit)2140 is probebly a "resource problem" in your system.
Check your GA, the expansion modules, are they in service?
Telnet to your system and type: " config x " ( x = the GA number) and then check if the MEX and the GA's are "in service".
It is possible that the mem in the GA hangs, shut the GA down and pull the powerplug and put it back.
This might help getting the GA working oke again.
I had the same fault codes 2140 & 2141 some time ago.
It took some time finding out what the problem was.
Changed soms modules, but the GA did not want to work (out of service) and no reply to a ping to the ip adres.
Solved it by full reset and my system works oke again.
Best regards!
Decoder
You might want to check your GA (s) (gateway application processing unit)2140 is probebly a "resource problem" in your system.
Check your GA, the expansion modules, are they in service?
Telnet to your system and type: " config x " ( x = the GA number) and then check if the MEX and the GA's are "in service".
It is possible that the mem in the GA hangs, shut the GA down and pull the powerplug and put it back.
This might help getting the GA working oke again.
I had the same fault codes 2140 & 2141 some time ago.
It took some time finding out what the problem was.
Changed soms modules, but the GA did not want to work (out of service) and no reply to a ping to the ip adres.
Solved it by full reset and my system works oke again.
Best regards!
Decoder
That says it all.Kinne wrote: Additional Text Alarm : SET resources quantity critical
It is trying to say that 75% of sbs are out of service.Kinne wrote: what it actually wants to tell me?
Is it a demo system?
If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.
-
Kinne
>It is trying to say that 75% of sbs are out of service
Not directly. It says <75% are in service.
Trust me - I've tested it.
The OXE generates Alarms when a percentage of sets or trunks goes out of service.
The System Option is named "% sets out of serv. trig. an alarm" and is located under System - Other System Param. - System Parameters.
The value is in % and idicated how many sets must be IN SERVICE!
If the value is going below that value, the incident 2140 is generated.
If the value is growing, the incident 2141 is generated.
The Value can be managed for sets and trunks separately.
Not directly. It says <75% are in service.
Trust me - I've tested it.
The OXE generates Alarms when a percentage of sets or trunks goes out of service.
The System Option is named "% sets out of serv. trig. an alarm" and is located under System - Other System Param. - System Parameters.
The value is in % and idicated how many sets must be IN SERVICE!
If the value is going below that value, the incident 2140 is generated.
If the value is growing, the incident 2141 is generated.
The Value can be managed for sets and trunks separately.
-
Decoder

