Avaya Support Forums

Avaya Support Forums (http://support.avaya.com/forums/index.php)
-   Messaging (http://support.avaya.com/forums/forumdisplay.php?f=4)
-   -   AAM Server Alarm - SOFTWARE VM 602 (http://support.avaya.com/forums/showthread.php?t=2120)

richwallot 09-18-2012 12:07 PM

AAM Server Alarm - SOFTWARE VM 602
This alarm is showing in the server - not messaging - messaging has no alarms.

I cannot find a reference to this alarm. Any one have an idea?


tilwa 09-28-2012 05:09 AM

This is known issue with Avaya Aura CMM 6.0. Check this link for the PSN for this issue. Upgrade to 6.2 SP0 should fix it.


richwallot 09-28-2012 08:08 AM

The PSN refers to CMM and this issue is in AAM though they may be similar fixes.

csteinh 09-28-2012 11:06 AM

I believe the 602 error is just a generic indication alarm that there are core files present. You would probably need to check to see what core files are present, their age, get them investigated if necessary or possibly upgrade as tilwa suggests.


richwallot 09-28-2012 11:12 AM

Can you define "core" software?

csteinh 10-01-2012 10:23 AM

I was referring to core files. When a program terminates in an unexpected way a core file containing info such as memory and register information is created to assist in troubleshooting the reason behind the termination. My understanding is that the 602 error is an indication that there are core files present.


markdennis 03-04-2013 07:55 AM

CMM 6.2 with SP2
I have just implemented the above and i to am getting the 602 alarm yet the voicemail works perfectly, i just cannot clear the alarm.

richwallot 03-04-2013 07:58 AM

This was resolved for us with a patch. Thanks.

briskj 06-05-2013 07:55 AM

I'm at CMM 6.2 SP2 and still have the Software VM 602 alarm in CM under messaging alarms, but there are none in the vm itself.
How can I clear this alarm? I already rebooted it.

sheasley 10-02-2013 01:41 PM

Core alarms are typically cleared when the core dump file is removed. It's best to report these to Avaya Support so they can investigate the maintenance log around the time of the fail and determine if the cause is a known issue.

All times are GMT -7. The time now is 10:33 AM.