|
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 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:
VM AUDIT 0
Description:
The nightly subscriber data audit failed.
Repair procedure:
VM AUDIT 1
Description:
The delivery data audit failed.
|
Note: This alarm is probably related to the mailing
lists audit.
|
Repair procedure:
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:
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:
VM AUDIT 101
Description:
The weekly data audit failed.
Repair procedure:
VM AUDIT 102
Description:
The weekly delivery data audit failed.
Repair procedure:
VM AUDIT 103
Description:
Portions of the weekly database (mbdata) audit failed.
Repair procedure:
VM AUDIT 104
Description:
Portions of the weekly database (swxln) audit failed.
Repair procedure:
VM AUDIX_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:
VM AUDIX_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
AUDIX_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:
- Start at the Messaging Administration main
menu and select:
Logs
Configure Subscriber Activity Log
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 Messaging Administration main
menu, select:
Global Administration
Subscriber Management
Manage
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 AUDIX_FS 2
Description:
The file count reached 80% capacity. This alarm can escalate to
VM AUDIX_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 by doing the following:
- From the Messaging Administration main
menu, select:
Global Administration
Subscriber Management
- From the Managing Subscribers screen, 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, next to Remote Subscribers
for remote_machine_name, where remote_machine_name
is the name of the remote subscriber's system, click Manage.
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.
- When finished, click Return to Main.
- Reboot the system to allow it to
reclaim unused resources.
- If the alarm is still active, contact your remote support center.
VM AUDIX_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:
VM AUDIX_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:
VM AUDIX_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:
VM AUDIX_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:
VM AUDIX_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:
VM AUD_RESTOR 0
Description:
A system-data restore failed. The messaging application will not
initialize.
Repair procedure:
VM LDAP-upd01
Description:
The LDAP replication server (SLURPD process) received a timeout
on a request to a remote LDAP machine (the LDAP request to a remote
machine timed out and raised an alarm). The alarm is cleared after
a request to the same machine succeeds.
Repair procedure:
Check the administration and status of the remote LDAP machine
as follows:
- Start at the Messaging Administration main
menu and select:
Global Administration
Networked
Machine Management
- Make sure that the information of the remote machine is correct.
If not, select the remote machine and click Edit the Selected
Network Machine. The system displays the Edit Networked
Machine page. Update the information as necessary and click Save.
- To check the connection to the remote machine, click Test
LDAP Connection. The system displays the Test LDAP Connection
page. Select the remote machine and click Run Test.
If you cannot resolve the problem, contact your remote support center.
VM LDAP-upd02
Description:
The LDAP replication server (SLURPD process) failed to connect
to a remote LDAP machine. The alarm is cleared after a connect to
the same machine succeeds.
Repair procedure:
Check the administration and status of the remote LDAP machine
as follows:
- Start at the Messaging Administration main
menu and select:
Global Administration
Networked Machine Management
- Make sure that the information of the remote machine is correct.
If not, select the remote machine and click Edit the Selected
Network Machine. The system displays the Edit Networked
Machine page. Update the information as necessary and click Save.
- To check the connection to the remote machine, click Test
LDAP Connection. The system displays the Test LDAP Connection
page. Select the remote machine and click Run Test.
If you can't resolve the problem, contact your remote support center.
VM LDAP-upd03
Description:
The LDAP replication server (SLURPD process) failed to log in
to a remote LDAP machine (the LDAP server could not log in to a
remote machine and raised an alarm). The alarm is cleared after
a login to the same machine succeeds.
Repair procedure:
Check the administration and status of the remote LDAP machine
as follows:
- Start at the Messaging Administration main
menu and select:
Global Administration
Networked Machine Management
- Make sure that the information of the remote machine is correct.
If not, select the remote machine and click Edit the Selected
Network Machine. The system displays the Edit Networked
Machine page. Update the information as necessary and click Save.
- To check the connection to the remote machine, click Test
LDAP Connection. The system displays the Test LDAP Connection
page. Select the remote machine and click Run Test.
If you can't resolve the problem, contact your remote support center.
VM LDAPFAIL 0
Description:
An attempt to restart the LDAP Server on the message server failed.
Repair procedure:
VM NET_CONN 0
Description
A digital networking connection failure has occurred.
Repair procedure:
To repair the alarm:
- Verify the system IP address is correct:
- Start at the Messaging Administration main
menu and select:
Basic System Administration
TCP/IP Administration
Network
Addressing
The system displays the Network Addressing 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 remote machines. For example,
delete any unnecessary test machines. See Deleting
Remote 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:
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:
VM SERVER 900
Description:
A trusted server exceeded the administered inactivity timeout
period. To see the current inactivity timeout settings for a trusted
server, click Global Administration > Trusted Server
Management. The system displays the Manage Trusted Servers
page. Select the trusted server and click Edit the Selected
Trusted Server.
Repair procedure:
VM SERVER 901
Description:
A trusted server logged an alarm.
Repair procedure:
VM SOFTWARE 0
Description:
A messaging system process failed.
Repair procedure:
When this alarm occurs, the messaging application automatically
restarts. This alarm remains active during the restart and is resolved
when the application successfully restarts.
If the system does not successfully restart, contact your remote support center.
VM SOFTWARE 1
Description:
A messaging system process failed.
Repair procedure:
When this alarm occurs, the messaging application automatically
restarts. This alarm remains active during the restart and is resolved
when the application successfully restarts.
If the system does not successfully restart, contact your remote support center.
VM SOFTWARE 2
Description:
A messaging system process failed.
Repair procedure:
When this alarm occurs, the messaging application automatically
restarts. This alarm remains active during the restart and is resolved
when the application successfully restarts.
If the system does not successfully restart, contact your remote support center.
VM SOFTWARE 100
Description:
A messaging system process failed to restart.
Repair procedure:
VM SOFTWARE 101
Description:
Nonstandard system software is in use.
Repair procedure:
VM SOFTWARE 201
Description:
A messaging system process could not initialize. The system might
be providing limited service.
Repair procedure:
When this alarm occurs, the system automatically attempts to restart
the failed process. The alarm remains active until the process successfully
initializes, and then the alarm is automatically resolved.
If this alarm fails to resolve, contact your remote support center.
VM SOFTWARE 202
Description:
A messaging system process could not operate. The system might
be providing limited service.
Repair procedure:
When this alarm occurs, the system automatically attempts to restart
the failed process. The alarm remains active until the process successfully
initializes, and then the alarm is automatically resolved.
If this alarm remains active, contact your remote support center.
VM SOFTWARE 203
Description:
A messaging system process failed to initialize. The system might
be providing limited service.
Repair procedure:
VM SOFTWARE 204
Description:
A messaging system process failed too many times during operation.
The system might be providing limited service.
Repair procedure:
VM SOFTWARE 601
Description:
The system detected nonstandard system software in use.
Repair procedure:
VM SOFTWARE 6000
Description:
A messaging system process could not initialize. The system is
not providing service.
Repair procedure:
VM SOFTWARE 6001
Description:
A messaging system process failed to operate.
Repair procedure:
VM SOFTWARE 6600
Description:
The messaging system database automatic rebuild failed.
The system is not providing service. The messaging application
has automatically stopped its own operation and attempted a restart.
During this restart, the application operates database file checks
and performs a rebuild audit to correct any problems or discrepancies
detected. If the rebuild audit is not successful, this system generates
this alarm.
Repair procedure:
VM SOFTWARE 6603
Description:
The messaging application detected file damage during a restart.
The system stops the initialization and the software attempts
to fix the file problems. The system automatically resolves this
alarm after completing the fix and continues initialization.
Repair procedure:
VM SOFTWARE 6604
Description:
The system encountered problems while updating extension length
values. Although the system updated the extension length, the messaging
application could not update its internal tables. This alarm can
block administrators from adding new subscribers.
Repair procedure:
- Stop the messaging software (voice
system).
- Start the messaging software (voice
system) to synchronize the machine software and the messaging
application.
- If the alarm fails to resolve, contact your remote support center.
VM SOFTWARE 6611
Description:
The messaging application cannot communicate with the platform
software. The system is providing limited or interrupted service.
Repair procedure:
VM SOFTWARE 6614
Description:
The system failed to initialize the messaging application because
of insufficient system resources. The system is not providing
service.
Repair procedure:
VM SOFTWARE 6615
Description:
During system initialization, the traffic process is unable to
access one of its database files.
Repair procedure:
VM SOFTWARE 6616
Description:
The initialization process detected corrupt traffic data files.
The system automatically begins to correct the corruption.
Repair procedure:
VM SOFTWARE 6617
Description:
The message server detects that the LDAP Server is not responding.
Repair procedure:
The message server attempts to restart the LDAP Server. If the
LDAP Server is restarted, the alarm is resolved. If the LDAP Server
does not restart, minor alarm VM LDAPFAIL 0
is then raised.
VM SOFTWARE 6618
Description:
The system detected a database problem. Stopping and restarting
the messaging system automatically repairs the database.
Repair procedure:
VM SOFTWARE 6619
Description:
The messaging system's call processing detected a problem with
the LDAP server.
Repair procedure:
VM SOFTWARE 6622
Description:
The message server detects that the LDAP Update server is not
responding.
Repair procedure:
- The message server attempts to restart the LDAP replication
server if it is down.
- If the alarm is not cleared within 5 minutes, reboot
the system.
VM SOFTWARE 6623
Description:
The message server detects that the LDAP replication server (SLURPD
process) is not responding.
Repair procedure:
- The message server attempts to restart the LDAP replication
server if it is down.
- If the alarm is not cleared within 5 minutes, reboot
the system.
VM SOFTWARE 6624
Description:
The weekly audit detects inconsistencies in the LDAP index. This
may cause several problems, for example, LDAP searches may not retrieve
correct data. When the weekly audit finds such inconsistencies in
the LDAP database, it logs an event (VM0353) indicating the number
of problems found. You can find the specific problem in the file
/vm/repair-ldap-log.
Repair Procedure:
- If the problem has occurred due to incomplete subscriber information
(blank attributes), then use the Subscriber
Administration pages to correct the data.
- If the subscriber data is valid, then, stop all the services
on the message server (voice module), login as tsc, change
the user to vexvm (use su vexvm command), and
then run the lindex command (/ldap/home/ol/bin/lindex)
from the command line.
|
Important!
To fix the index inconsistencies, you must
stop all the services on the message server before running
the lindex command.
|
VM SOFTWARE 6625
Description:
The message server detects multiple Voice Mail Domains (VMDs) in
the LDAP database. Multiple VMDs in LDAP may cause several problems,
for example, mailboxes will not be accessible from the telephone
user interface (TUI) because they are assigned to the wrong VMD.
(See Note below.)
Repair procedure:
Administrators with command line access can use the following commands
to diagnose and resolve the problem:
- disp_vmd
- delete_vmd
- disp_sub_vmd
- chg_def_vmd
- chg_sub_vmd
Refer to the man pages of these commands for details on their usage.
|
Note:
Multiple Voice Mail Domains: Although Modular
Messaging supports only one VMD per message storage server
(MSS), it does not restrict you from adding multiple VMDs.
You may accidentally create multiple VMDs during an upgrade
or when there is a single MSS with multiple MAS. When you
create local subscribers, the system assigns them to a VMD.
Incase of multiple VMDs, the system may select the wrong VMD.
The LDAP database will then have subscribers assigned to a
VMD which is different from the VMD considered valid by the
MAS. In such a case, these subscribers may not be able to
access their mailboxes using the TUI.
|
VM SOFTWARE 7701
Description:
The system failed to locate all of the software needed to initialize
the messaging application. The system is not providing service.
This failure can occur after a power hit or when a disk error happens.
This alarm is also sent to the remote support center.
Repair procedure:
VM SOFTWARE 7702
Description:
The system found that messaging database files were missing during
initialization. The system is not providing service. This
failure can occur after a power hit or when a disk error happens.
Repair procedure:
VM SOFTWARE 7703
Description:
The system experienced an unexpected file check failure after
a messaging system restart or a reboot.
Repair procedure:
VM SOFTWARE 7704
Description:
The system restarts too often.
Because of another alarm, the messaging application has tried
to restart itself twice but has failed. The system is not
providing service.
Repair procedure:
VM SOFTWARE 7705
Description:
The maintenance software automatically shut down the messaging
application and attempted a restart.
This alarm can also indicate that the system attempted too many
restarts or that an unexpected error occurred during the shutdown.
The system is not providing service.
Repair procedure:
VM SOFTWARE 7706
Description:
The system rebooted too often.
Because of another alarm, the messaging application has tried
to restart itself but has failed. The system is not providing
service.
Repair procedure:
VM SOFTWARE 7707
Description:
The maintenance software automatically shut down the messaging
application and attempted a restart.
This alarm can also indicate that the system attempted too many
restarts or that an unexpected error occurred during shutdown. The
system is not providing service.
Repair procedure:
VM SOFTWARE 7708
Description:
The system rebooted too many times.
Because of another alarm, the messaging application has tried
to restart itself but has failed. The system is not providing
service.
Repair procedure:
VM SOFTWARE 7709
Description:
The maintenance software automatically shut down the messaging
application and attempted a restart.
This alarm can also indicate that the system attempted too many
restarts or that an unexpected error occurred during shutdown. The
system is not providing service.
Repair procedure:
VM SOFTWARE 7710
Description:
The maintenance software stopped messaging operation during a
restart. The system is not providing service.
Repair procedure:
VM SOFTWARE 7712
Description:
The maintenance software has automatically shut down the messaging
application and attempted a restart. The system is not providing
service.
Repair procedure:
VM SOFTWARE 7713
Description:
The system failed to create a new voice file system during initialization.
The system is not providing service.
Repair procedure:
VM SOFTWARE 7715
Description:
The trusted server notification feature failed. The system may
be providing only limited service.
Repair procedure:
VM SOFTWARE 7716
Description:
The system failed to find the external security password file.
Any usage of the old, external security password will fail.
Repair procedure:
VM SOFTWARE 7718
Description:
During system initialization, the messaging database integrity
check failed. The system is not providing service.
Repair procedure:
VM TRAFIXFAIL 0
Description:
The automatic file recovery procedure started by VM
SOFTWARE 6616 failed. The system will continue to provide service,
but traffic collection data is incomplete.
Repair procedure:
Top of page
|
