Alarm codes 1

[GMinTX]

I have looked on the Avaya support site for Modular Messaging and can't find a document that gives error codes and reasons/fix. I have a major alarm with the following info.

App = VM
Resource Type = SERVER
Alarm Code = 900
Alarm Lvl = MAJ

Much appreciated if someone could point me in the direction of any alam Doc's that would explain this type of alarm to me.

 

[ken07734]

Home > Maintenance > Reviewing system logs > Viewing MSS logs > VM (Voice Messaging) alarms
VM (Voice Messaging) alarms

The alarms on this page are generated by the VM application and indicate a problem with the voice messaging system. The VM alarms are organized as follows:

VM alarms (excluding SOFTWARE alarms)
VM SOFTWARE alarms
VM alarms (excluding SOFTWARE alarms)
ADMIN 0
ALARM_ORIG 0
AUD_BKUP 0
AUDIT 0
AUDIT 1
AUDIT 3
AUDIT 100
AUDIT 101
AUDIT 102
AUDIT 103
AUDIT 104
AUD_RESTOR 0
MSGING_FS 0
MSGING_FS 1
MSGING_FS 2
MSGING_FS 3
MSGING_FS 4
MSGING_FS 5
MSGING_FS 6
MSGING_FS 7
NET_CONN 0
REORGDB 0
REORGDB 1
RPCTEST 001
SERVER 900
SERVER 901
TRAFIXFAIL 0


VM SOFTWARE alarms
SOFTWARE 0
SOFTWARE 1
SOFTWARE 2
SOFTWARE 100
SOFTWARE 101
SOFTWARE 201
SOFTWARE 202
SOFTWARE 203
SOFTWARE 204
SOFTWARE 601
SOFTWARE 6000
SOFTWARE 6001
SOFTWARE 6600
SOFTWARE 6603
SOFTWARE 6604
SOFTWARE 6611
SOFTWARE 6614
SOFTWARE 6615
SOFTWARE 6616
SOFTWARE 6617
SOFTWARE 6618
SOFTWARE 6619
SOFTWARE 6622
SOFTWARE 6623
SOFTWARE 6624
SOFTWARE 6625
SOFTWARE 6626
SOFTWARE 7701
SOFTWARE 7702
SOFTWARE 7703
SOFTWARE 7704
SOFTWARE 7705
SOFTWARE 7706
SOFTWARE 7707
SOFTWARE 7708
SOFTWARE 7709
SOFTWARE 7710
SOFTWARE 7712
SOFTWARE 7713
SOFTWARE 7715
SOFTWARE 7716
SOFTWARE 7718
SOFTWARE 7721
SOFTWARE 7723
SOFTWARE 7724
SOFTWARE 7725


VM ADMIN 0
Description:
The public LAN is not configured. The system will not start until the public LAN has been properly administered.

Repair procedure:
Use the installation documentation to administer the public LAN interface.
Reboot the system.
VM ALARM_ORIG 0
Description:
This alarm indicates a test of Alarm Origination. The remote support center is conducting this test.

Repair procedure:
No corrective action is necessary.

VM AUD_BKUP 0
Description:
Portions of the system data backup failed.

Note: The system is providing service, and the current backup is valid. However, future backups may fail.



Repair procedure:
Contact your remote support center.

VM AUDIT 0
Description:
The nightly subscriber data audit failed.

Repair procedure:
Contact your remote support center.

VM AUDIT 1
Description:
The delivery data audit failed.

Note: This alarm is probably related to the mailing lists audit.



Repair procedure:
Contact your remote support center.

VM AUDIT 3
Description:
The database (vm) audit failed. This condition can occur after a move from one switch to another or after a power outage.

Repair procedure:
Contact your remote support center.

VM AUDIT 100
Description:
Portions of the weekly database (dmnet) audit failed. The system is providing service. This service, however, might be limited or inconsistent.

Repair procedure:
Contact your remote support center.
VM AUDIT 101
Description:
The weekly data audit failed.

Repair procedure:
Contact your remote support center.
VM AUDIT 102
Description:
The weekly delivery data audit failed.

Repair procedure:
Contact your remote support center.
VM AUDIT 103
Description:
Portions of the weekly database (mbdata) audit failed.

Repair procedure:
Contact your remote support center.
VM AUDIT 104
Description:
Portions of the weekly database (swxln) audit failed.

Repair procedure:
Contact your remote support center.
VM AUD_RESTOR 0
Description:
A system-data restore failed. The messaging application will not initialize.

Repair procedure:
Contact your remote support center.
VM MSGING_FS 0
Description:
The system logs this alarm when the voice storage space used is at 90% capacity or greater. The system automatically resolves this alarm when the space usage drops below 85%.

Note: This condition causes serious subscriber problems.



Repair procedure:
Contact your remote support center.
VM MSGING_FS 1
Description:
The system data space used reached 80% capacity. The system automatically resolves this alarm when the space usage drops below 75%. If the space usage does not decrease, this alarm can escalate to a VM MSGING_FS 0 alarm.

Repair procedure:
Note: After each step, check for resolved alarms to see if you have freed enough space.



Decrease the maximum number of activity log entries by doing the following:
From the MSS Messaging Administration menu, select Messaging Administration > Activity Log Configuration.
The system displays the Configure Subscriber Activity Log page.

Decrease the number in the Maximum Number of Activity Log Entries field.
Click Save to save the information.
Ask subscribers to delete unneeded messages.
Reduce message retention time by doing the following:
From the MSS Messaging Administration menu, select Messaging Administration > Classes-of-Service.
The system displays the Manage Classes-of-Service page.

Select the class of service (COS) to modify. It is strongly recommended that you modify the COS that applies to most subscribers.
Click Edit the Selected COS.
On the Edit a Class-of-Service screen, under Message Retention Settings, decrease the number of days that Incoming New Messages, Incoming Old Messages, and Unopened Messages are retained.
Click Save.
If the alarm is still active, contact your remote support center.
VM MSGING_FS 2
Description:
The file count reached 80% capacity. This alarm can escalate to VM MSGING_FS 0. The system automatically resolves this alarm when the file count used goes below 75%.

Repair procedure:
Note: After each step, check for resolved alarms to see if you have freed enough space.



Ask subscribers to delete unneeded messages.
Remove unused local and remote subscribers:
From the MSS Messaging Administration menu, select Messaging Administration > Messaging Attributes.
The system displays the Configure Subscriber Management page.

Next to Local Subscribers for this machine, click Manage.
On the Manage Local Subscribers page, highlight the name of the subscriber you want to remove.
Click Delete the Selected Subscriber.
Repeat steps c and d to remove all unused subscribers.
To delete remote subscribers, click Back.
From the Managing Subscribers screen, click Manage next to Remote Subscribers for the subscriber's remote system.
The system displays the Manage Remote Subscribers page.

Highlight the name of the remote subscriber you want to remove.
Click Delete the Selected Subscriber.
Repeat steps f through i to remove all unused remote subscribers.
Reboot the system to allow it to reclaim unused resources.
If the alarm is still active, contact your remote support center.
VM MSGING_FS 3
Description:
An attempt to restart the messaging application failed because the messaging system database is corrupted. The system is not providing service.

Repair procedure:
Contact your remote support center.
VM MSGING_FS 4
Description:
The messaging system data files are corrupted. Although the system is providing service, subscribers might have trouble sending or receiving messages.

Repair procedure:
Contact your remote support center.
VM MSGING_FS 5
Description:
The messaging system data files are corrupted. Although the system is providing service, subscribers may have trouble sending or receiving messages.

Repair procedure:
Contact your remote support center.
VM MSGING_FS 6
Description:
The messaging system database might be corrupted. Although the system is providing service, this condition could lead to severe problems.

Repair procedure:
Contact your remote support center.
VM MSGING_FS 7
Description:
The system is experiencing possible file system corruption. Although the system is providing service, this condition could lead to severe problems. Nightly and manual backups usually fail while this alarm is active.

Repair procedure:
Contact your remote support center.
VM NET_CONN 0
Description
A digital networking connection failure has occurred.

Repair procedure:
To repair the alarm:

From the MSS Messaging Administration menu, select Messaging Administration > Networked Machines.
The system displays the Manage Networked Machines page.

Verify that the IP Address field contains the correct system IP address.
If necessary, enter the correct IP address in the IP Address field.
Delete any unnecessary administered networked machines. For example, delete any unnecessary test machines. See Deleting networked machines for more information.
If this alarm persists, reboot the system.
VM REORGDB 0
Description:
The system logs this alarm when an initialization fails. System initialization is suspended while the database is reorganized. This error can occur in the following circumstances:

Power supply is interrupted.
The system restarts for a maintenance reason.
Someone presses the Reset switch on the front of the unit.
The system automatically resolves this alarm after it reorganizes the database and completes initialization.

Caution!
Do not press the Reset switch. Wait for the system to reorganize the database and initialize.


Repair procedure:
Wait for the alarm to automatically clear. This can take up to 2 hours.
If the alarm does not clear after this length of time, contact your remote support center.
VM REORGDB 1
Description:
The system logs this alarm when a database repair fails. This alarm occurs in the following circumstances:


Power supply is interrupted.
The system restarts for a maintenance reason.
Someone presses the Reset switch on the front of the unit.
The system automatically resolves this alarm after it reorganizes the database and reinitializes.

Repair procedure:
Contact your remote support center to restore the database from a previous backup.
VM RPCTEST 001
Description:
The operating system's RPC processes are not running and cannot be restarted. The two servers may not be able to exchange information, so service may not be available.

Repair procedure:
Contact your remote support center.
VM SERVER 900
Description:
A trusted server exceeded the administered inactivity timeout period. To see the current inactivity timeout settings for a trusted server:

From the MSS Messaging Administration menu, select Messaging Administration > Trusted Servers.
The system displays the Manage Trusted Servers page.

Select the trusted server and click Edit the Selected Trusted Server.
Repair procedure:
Contact your remote support center.

 

[ken07734]

I thought I had only pasted the alarm code, it looks like I pasted a whole lot more, sorry. just look at the bottom for the VM SERVER 900. Hope this helps.

 

[GMinTX]

Thanks for the information Ken, much appreciated.