Table Of Contents
Troubleshooting Cisco MeetingPlace Express
About Your Passwords
Recovering the root Password
Recovering the mpxadmin Password
Recovering the System Administrator Password Used in the End-User Interface and the Administration Console
About Accessing the System
Accessing the System after Uploading the Wrong SSL Certificate or Key
About Backing Up, Archiving, and Restoring Data
Backing Up Data
Archiving Data
Restoring Data
About Common Telephone Errors
Tips for Failed Calls
Fixing Undetected Key Presses
Fixing Failed Incoming Calls
Fixing Dropped Calls
Fixing Dead Air During Calls
Fixing Dropped Packets
About Swapping Out a Disk Drive
Swapping Out a Disk Drive on a Cisco MCS 7825
Swapping Out a Disk Drive on a Cisco MCS 7835
Helpful Information
File Locations
Exception Codes
Module Numbers and Corresponding System Component
Troubleshooting Cisco MeetingPlace Express
This chapter contains the following troubleshooting topics:
•
About Your Passwords
•About Accessing the System
•About Backing Up, Archiving, and Restoring Data
•About Common Telephone Errors
•About Swapping Out a Disk Drive
•Helpful Information
After reviewing this chapter, if you still have problems with Cisco MeetingPlace Express, contact Cisco TAC. See the Guide to Cisco MeetingPlace Express Documentation and Support for information on contacting Cisco TAC.
About Your Passwords
These sections describe procedures for resetting your passwords:
•Recovering the root Password
•Recovering the mpxadmin Password
•Recovering the System Administrator Password Used in the End-User Interface and the Administration Console
Recovering the root Password
If you forget the password that you created for the root account, follow these steps to reset it:
Procedure
Step 1 From a PC, go to Cisco.com and find the appropriate recovery CD image file. There are four recovery files and all are .iso files:
•For Cisco MCS 7825I-3.0-IPC1 and Cisco MCS 7825-I1-RC1, the file is called MCS7825IRecoveryBootImage.iso
•For Cisco MCS 7825H-3.0-IPC1 and Cisco MCS 7825-H1-RC1, the file is called MCS7825HRecoveryBootImage.iso
•For Cisco MCS 7835-I1-RC1 and Cisco MCS 7835I-3.0-IPC1, the file is called MCS7835IRecoveryBootImage.iso
•For Cisco MCS 7835-H1-RC1 and Cisco MCS 7835H-3.0-IPC1, the file is called MCS7835HRecoveryBootImage.iso
Step 2 Burn a CD-ROM with the recovery CD image file. The file must be burned as a CD image and not as a regular file, or else it will not work.
Step 3 Go to the Cisco MCS server where your Cisco MeetingPlace Express application is loaded.
Step 4 Insert the CD-ROM that you just burned into the Cisco MCS server CD-ROM drive.
Step 5 Reboot the server.
Step 6 At the prompt, enter linux single. This tells the server to boot up in single user mode.
Step 7 At the prompt, enter /root/.security/unimmunize.sh.
Step 8 At the prompt, enter passwd root. This tells the server to set a new password for the user called root.
Step 9 At the New password: prompt, enter a new password. For security purposes, the password is displayed as asterisks.
Note You may see a message that the password you entered is bad. Ignore this message.
Step 10 At the Retype new password: prompt, re-enter the same password again.
Step 11 At the prompt, enter /root/.security/immunize.sh.
Step 12 At the prompt, enter eject.
This ejects the CD-ROM from the CD-ROM drive.
Step 13 At the prompt, enter reboot. This reboots the server.
The Cisco MeetingPlace Express operating system login page is displayed.
Step 14 At the username prompt, enter root.
Step 15 At the password prompt, enter the new password that you created in Step 9.
The system should display the Cisco MeetingPlace Express operating system desktop.
Recovering the mpxadmin Password
Note Follow this same procedure to change the mpxadmin password, too.
If you forget the password that you created for the mpxadmin account, follow these steps to reset it:
Procedure
Step 1 Log in to the Cisco MeetingPlace Express operating system as the root user.
Step 2 At the password prompt, enter the root password. (If you have forgotten the root password, first follow the steps in the "Recovering the root Password" section.)
The Cisco MeetingPlace Express operating system desktop appears.
Step 3 Right-click on the desktop.
Step 4 From the menu, select New Terminal. This brings up a terminal session.
Step 5 At the prompt, enter /root/.security/unimmunize.sh.
Step 6 At the prompt, enter passwd mpxadmin. This tells the server to set a new password for the user called mpxadmin.
Step 7 At the New password prompt, enter a new password. For security purposes, the password is displayed as asterisks.
Note You may see a message that the password you entered is bad. Ignore this message.
Step 8 At the Retype new password prompt, re-enter the same password again.
Step 9 At the prompt, enter /root/.security/immunize.sh.
Step 10 On the desktop, click RedHat > Network Services.
Step 11 Click Log out.
Recovering the System Administrator Password Used in the End-User Interface and the Administration Console
If you forget the password that you created for the system administrator account, which is used in the Administration Center, follow these steps to reset it:
Procedure
Step 1 Log in to the Cisco MeetingPlace Express operating system as the mpxadmin user.
Step 2 At the password prompt, enter the mpxadmin password. (If you have forgotten the mpxadmin password, first follow the steps in the "Recovering the mpxadmin Password" section.)
The Cisco MeetingPlace Express operating system desktop appears.
Step 3 Right-click on the desktop.
Step 4 From the menu, select New Terminal. This brings up a terminal session.
Step 5 At the prompt, enter userutil -p admin <newpassword>, where newpassword is the new password. This tells the server to set a new password for the End-User Interface and Administration Center user called admin.
Step 6 On the desktop, click RedHat > Network Services.
Step 7 Click Log out.
About Accessing the System
This section describes what to do if you have problems accessing the Cisco MeetingPlace Express system.
Accessing the System after Uploading the Wrong SSL Certificate or Key
To have SSL work with the Cisco MeetingPlace Express application, you must upload SSL certificates and enable SSL. See the Administrator's Configuration and Maintenance Guide for Cisco MeetingPlace Express Release 1.1 for information about doing this. However, if you enter the wrong certificate or private key name and enable SSL, you cannot access the Cisco MeetingPlace Express application and you are locked out. Follow these steps to access the application:
Procedure
Step 1 Open a web browser and navigate to http://<localhostname>:8080, where localhostname is your local hostname.
The Cisco MeetingPlace Express application opens.
Step 2 Log in to Cisco MeetingPlace Express.
Step 3 At the top of the page, click Administration.
Step 4 On the left side of the page:
a. Click Certificate Management.
b. Click Disable SSL.
Step 5 Disable SSL by clicking Disable SSL.
Step 6 Restart the Cisco MeetingPlace Express system by clicking Restart Now.
This updates the web conferencing configuration files and after the system restarts you should be able to correctly access the Cisco MeetingPlace Express application.
Open a web browser and navigate to http://<localhostname>, where localhostname is your local hostname.
Step 7 Log in to Cisco MeetingPlace Express.
Step 8 At the top of the page, click Administration.
Step 9 On the left side of the page:
a. Click Certificate Management.
b. Click Enable SSL.
Step 10 Enter the correct certificate or private key names.
Step 11 Click Upload Certificates.
Step 12 The system displays a dialog box stating that this will restart the server and to only proceed if you are sure. Click OK to upload the certificates, update the configuration, and restart the server.
If your system still does not enable SSL, the system may have overwritten the private keys that were created on the system during the initial Certificate Signing Request (CSR) generation. (This can happen if you generated new CSRs.) In this situation, the recovery steps are as follows:
Procedure
Step 1 Log in to Cisco MeetingPlace Express.
Step 2 At the top of the page, click Administration.
Step 3 On the left side of the page:
a. Click Certificate Management.
b. Click Generate CSRs.
Step 4 Enter information in the fields.
Step 5 Click Generate CSRs.
The system generates new private keys and stores them in the /usr/local/enrollment directory.
Step 6 Send the new CSRs to the CA so that they can reissue the SSL certificates.
Step 7 After you receive the SSL certificates from the CA, go to the Enable SSL page and upload them.
About Backing Up, Archiving, and Restoring Data
This section describes how to manually perform the following functions:
•Backing Up Data
•Archiving Data
•Restoring Data
Backing Up Data
Backing up data is the process of saving database files somewhere else so that they are available in case of a system failure.You can use the Cisco MeetingPlace Express Administration Center to configure the system to automatically back up data. However, if you want to manually back up data, follow these steps:
Note If automatic backup is disabled:
•Only run one backup at a time.
•Backups should be made in the correct order, so first do a L0 backup, then L1, then L2. You cannot do a L2 backup immediately after running a L0 backup.
•Be careful when modifying the cron schedule. The cron schedule determines the order of the backups.
Procedure
Step 1 Log in to the Cisco MeetingPlace Express operating system as the mpxadmin user.
Step 2 At the password prompt, enter the mpxadmin password.
The Cisco MeetingPlace Express operating system desktop appears.
Step 3 Right-click on the desktop.
Step 4 From the menu, select New Terminal. This brings up a terminal session.
Step 5 Manually back up the data by entering the following:
sudo $MP_DATABASE/db-maintenance/backup.sh
Step 6 On the desktop, click RedHat > Network Services.
Step 7 Click Log out.
Archiving Data
Archiving is the process of storing database backup files to a remote system over the network, together with other critical external files. You can use the Cisco MeetingPlace Express Administration Center to configure the system to automatically archive data. However, if you want to manually archive data, follow these steps:
Procedure
Step 1 Log in to the Cisco MeetingPlace Express operating system as the mpxadmin user.
Step 2 At the password prompt, enter the mpxadmin password.
The Cisco MeetingPlace Express operating system desktop appears.
Step 3 Right-click on the desktop.
Step 4 From the menu, select New Terminal. This brings up a terminal session.
Step 5 Manually archive the data by entering the following:
sudo $MP_DATABASE/db-maintenance/archive.sh
Step 6 On the desktop, click RedHat > Network Services.
Step 7 Click Log out.
Restoring Data
Restoring data recreates the database server data from backed-up storage spaces and logical log files. You may need to restore your data if you need to replace a failed disk that contains database server data, if there is a logic error in a program that has corrupted the database, if you need to move your database server data to a new computer, or if a user accidentally corrupts or destroys data.
To restore data up to the time of the failure, you must have at least one L0 backup. The restore is done using the Informix command called ontape. Cisco MeetingPlace Express provides a script called restore.sh that guides you through the restore process. The script is in the $MP_DATABASE/db-maintenance directory.
Caution You can only restore a database that is from the same version of the Cisco MeetingPlace Express product. You cannot restore a database from a previous version.
The names of the databases that you are restoring from and restoring to must be the same.
Follow these steps to restore data:
Procedure
Step 1 Log in to the Cisco MeetingPlace Express operating system as the mpxadmin user.
Step 2 At the password prompt, enter the mpxadmin password.
The Cisco MeetingPlace Express operating system desktop appears.
Step 3 Right-click on the desktop.
Step 4 From the menu, select New Terminal. This brings up a terminal session.
Step 5 Shut down the Cisco MeetingPlace Express application by entering the following:
mpx_sys stop
Step 6 Restore the data by entering the following:
sudo $MP_DATABASE/db-maintenance/restore.sh
Step 7 On the desktop, click RedHat > Network Services.
Step 8 Click Log out.
About Common Telephone Errors
Here are some common errors you may encounter:
•Tips for Failed Calls
•Fixing Undetected Key Presses
•Fixing Failed Incoming Calls
•Fixing Dropped Calls
•Fixing Dead Air During Calls
•Fixing Dropped Packets
Tips for Failed Calls
The following tips should always be used when troubleshooting failed calls:
•Look for network congestion about the time of the call. This can be found via router and switch statistics.
•Ensure that the Cisco MeetingPlace Express system is set to full-duplex with 100 Mbps network speed.
•Ensure that the local switch port for the Cisco MeetingPlace Express system has the same auto-negotiation setting as the Cisco MeetingPlace Express system. You can run the mii-tool command from the CLI to see the current link setting.
•If Cisco MeetingPlace Express and the local switch (or router) are configured correctly, make sure that the network on the other side of the switch or router is also set to 100 Mbps, full duplex.
•Ensure that the Cisco MeetingPlace Express system is not connected to a multiple-device Ethernet bus. The system works best if micro-segmented to use a single switch port rather than share a bus with other devices. Sharing a bus can cause excessive collisions which reduce bandwidth and cause unpredictable bandwidth availability.
•If there is still congestion, you may have to take standard congestion reduction measures such as these:
–Reduce traffic in the local LAN by adding more switches and distributing the network devices between them.
–Reduce the number of devices on the local LAN (and thus the traffic) by adding more routers to create more (but smaller) LANs. There might also be unused ports on the local router in which case more routers are not needed.
–Change network device settings to reduce unnecessary traffic such as adding Access Control Lists (ACLs) to the local router to filter out irrelevant traffic.
•Get a trace of network traffic. This trace should be taken as close to the eth0 port as possible.
•Some phones provide network error statistics about how many bad frames have been received. See if the particular phone has these statistics. If so, see if the phone has registered the reception of a large number of bad frames.
•Verify the configuration of the device that routes calls to Cisco MeetingPlace Express.
•Check for any firewalls between the phone and Cisco MeetingPlace Express that may prevent calls.
Fixing Undetected Key Presses
If you think that the Cisco MeetingPlace Express system is not detecting you when you press the keys on your phone, try these steps:
Procedure
Step 1 Log in to the Cisco MeetingPlace Express operating system as the root user.
Step 2 At the password prompt, enter the root password.
The Cisco MeetingPlace Express operating system desktop appears.
Step 3 Right-click on the desktop.
Step 4 From the menu, select New Terminal. This brings up a terminal session.
Step 5 At the CLI, enter the following:
eventlog -b<mmddhhmm> -e<mmddhhmm>
For the start time (the -b value), enter a time shortly before the call failed. For the stop time (the -e value), enter a time shortly after the call failed.
Step 6 Check the DID/DNIS and input events to determine which port is yours.
Step 7 Look later in the trace to see if DTMFs sent from your phone were being detected. If they are not detected, then check the following:
•Verify that the telephony network is using RFC 2833 digits or out-of-band digits. (The Cisco MeetingPlace Express system does not support in-band digits.)
•Network congestion might be preventing the RFC 2833 digits or out-of-band digits from reaching the system.
•Check if G.729 coders are being used somewhere in your network, instead of G.711. G.729 will seriously corrupt in-band digits (DTMF) causing these digits to either be lost or changed. If this is happening and RFC 2833 is not a good choice, consider converting to a pure G.711 network.
Fixing Failed Incoming Calls
If you are not able to receive incoming calls, do the following:
Procedure
Step 1 Log in to the Cisco MeetingPlace Express operating system as the root user.
Step 2 At the password prompt, enter the root password.
The Cisco MeetingPlace Express operating system desktop appears.
Step 3 Right-click on the desktop.
Step 4 From the menu, select New Terminal. This brings up a terminal session.
Step 5 At the CLI, enter the following:
eventlog -b<mmddhhmm> -e<mmddhhmm>
For the start time (the -b value), enter a time shortly before the call failed. For the stop time (the -e value), enter a time shortly after the call failed.
Step 6 Determine if the Cisco MeetingPlace Express system registered the call signaling packets.
•If the system registered the call, look for a reason in the trace log why the call was disconnected. Enter one of these commands:
eventlog -b<mmddhhmm> -e<mmddhhmm> -v
eventlog -b<mmddhhmm> -e<mmddhhmm> -G -v
•If the system did not register the call in the trace log, the problem might be a configuration problem on the device that routes calls to Cisco MeetingPlace Express. Also, check if any firewalls may be preventing the call from reaching the system.
Fixing Dropped Calls
If calls are connected to the system, but then disconnect during the call, do the following:
Procedure
Step 1 Log in to the Cisco MeetingPlace Express operating system as the root user.
Step 2 At the password prompt, enter the root password.
The Cisco MeetingPlace Express operating system desktop appears.
Step 3 Right-click on the desktop.
Step 4 From the menu, select New Terminal. This brings up a terminal session.
Step 5 At the CLI, enter the following:
eventlog -b<mmddhhmm> -e<mmddhhmm>
For the start time (the -b value), enter a time shortly before the call failed. For the stop time (the -e value), enter a time shortly after the call failed.
Step 6 Check for a "far end disconnect event." If you see this, the disconnect may have been initiated outside of the Cisco MeetingPlace Express system. Check for errors on the devices between the phone and the Cisco MeetingPlace Express system.
Step 7 If you do not see a "far end disconnect event," the Cisco MeetingPlace Express system hung up on you first. Review the trace log to try to determine why the system hung up on you.
Step 8 If your system uses Cisco CallManager contact the Cisco CallManager network administrator to get a call session trace indicating why Cisco CallManager sent the disconnect event to you.
Fixing Dead Air During Calls
If you think that your call has been disconnected, but your phone still shows that the call is active, follow these steps:
Procedure
Step 1 If you are in a meeting, enter #21 to hear a roll call of all meeting participants.
Do you hear anything?
•If yes, you have at least one-way audio (that is, you can hear but not speak).
•If you do not hear anything, either there is no audio either way or Cisco MeetingPlace Express cannot detect your DTMF keypresses.
Step 2 Provide this information to your network administrator and try to get a call session trace from Cisco CallManager.
Fixing Dropped Packets
If you determine that packets are being dropped (as determined by RTCP statistics) or delivered with errors and then dropped at the endpoints, consider changing the following call configuration parameters:
Procedure
Step 1 Log in to Cisco MeetingPlace Express.
Step 2 At the top of the page, click Administration.
Step 3 On the left side of the page:
a. Click System Configuration.
b. Click Call Configuration.
c. Click Audio Parameters.
Step 4 In the Default G.711 packet size (milliseconds) field, enter 10.
A smaller packet size reduces the damaging effect of a lost packet. However, network traffic increases slightly.
Step 5 Set the Voice activity detect field to yes.
This reduces outgoing packets to callers. The Cisco MeetingPlace Express system only transmits packets if someone is actively speaking during a meeting. However, there might be a slight delay when someone starts speaking causing part of their initial syllable to not be heard.
Step 6 Determine how to configure the phones in your organization to use Voice Activity Detect (VAD). This way, the phones only send packets to the Cisco MeetingPlace Express system when the phone detects sound on your handset or headset.
Step 7 Set the Maximum jitter buffer (milliseconds) field to 250.
This is the maximum value allowed. This higher value introduces more delays into conversations, but also reduces packet loss due to sudden surges in traffic.
Step 8 To maximize bandwidth, have the network administrator check that the your Cisco MeetingPlace Express system and the local switch that your system connects to are both running in 100 Mbps full duplex mode.
About Swapping Out a Disk Drive
This section describes how to swap out a hard-disk drive on your Cisco MCS server. Each Cisco MCS server has multiple hard-disk drives so it is possible to continue using the Cisco MeetingPlace Express system if a hard-disk drive fails. However, there will be no redundancy and if the system goes down, you can lose your operating system, application, and data.
Before You Begin
Step 1 Determine the model number of your Cisco MCS server.
Step 2 Determine which hard-disk drive on your Cisco MCS server has failed.
Step 3 Order the replacement hard-disk drive. The replacement hard-disk drive must be the same model as the one it is replacing.
Swapping Out a Disk Drive on a Cisco MCS 7825
All versions of the Cisco MCS 7825 (Cisco MCS 7825-H1-RC1, Cisco MCS 7825-I1-RC1, Cisco MCS 7825H-3.0-IPC1, and Cisco MCS 7825I-3.0-IPC1) have front-accessible, simple-swap SATA hard-disk drives. The SATA hard-disk drives are accessible through openings in the front bezel of the server. If a hard-disk drive fails, schedule server downtime, power down the server, and replace the failed SATA drive by removing it (each drive is equipped with a front latch that positively mates the drive to the server) and replacing it with an unconfigured spare hard-disk drive.
Follow these steps to change the disk:
Procedure
Step 1 Turn off the server and all peripheral devices.
Step 2 Disconnect the power cord and all external cables.
Step 3 Remove the bad hard-disk drive.
Step 4 Insert the new hard-disk drive.
Step 5 Connect the power cord and all external cables.
Step 6 Turn on the power.
Step 7 Reinstall the Cisco MeetingPlace Express operating system and restore the application and your data from a backup.
Swapping Out a Disk Drive on a Cisco MCS 7835
All versions of the Cisco MCS 7835 (Cisco MCS 7835-H1-RC1, Cisco MCS 7835-I1-RC1, Cisco MCS 7835H-3.0-IPC1, and Cisco MCS 7835I-3.0-IPC1) support up to six Small Computer System Interface (SCSI) hot-plug hard drives (or five hot-plug hard drives and one hot-plug tape drive) that are configured using RAID 1. These are hot-swappable SCSI drives, so you can change them without powering down the server.
Follow these steps to change a hard-disk drive if it fails:
Procedure
Step 1 Remove the bad hard-disk drive.
Note You do not need to turn off the power on your system.
Step 2 Insert the new hard-disk drive.
The system automatically synchronizes the new disk with no interruption.
Helpful Information
This section contains information that may be useful for system administrators.
File Locations
System administrators use several files. Table 6-1 lists the locations of several common files.
Table 6-1 File Locations
Location
|
Description
|
/lat/bin
|
Contains most of the executable files
|
/var/mp
|
Contains most of the stderr and stdout files
|
/opt/cisco/meetingplace_express/application/logs
|
Contains most of the logs
|
/opt/cisco/meetingplace_express/application/versions
|
Contains a directory for each version installed
|
/opt/cisco/meetingplace_express/uninstaller
|
Contains the uninstall script
|
/opt/cisco/meetingplace_express/database/db-maintenance
|
Contains the backup, archive, and restore database scripts
|
Exception Codes
The Cisco MeetingPlace Express system generates exception codes whenever there is an internal problem. There are many exception codes and they are not all documented here. Instead, only those exception codes that are meaningful and that you can possibly fix are included.
To find these error codes, run the errorlog CLI command.
Table 6-2 contains the most frequently seen and important exception codes for the Cisco MeetingPlace Express system.
Note Some exception codes are listed as a decimal number and others as a hexadecimal number. For clarification, both code numbers are listed.
Table 6-2 Important Exception Codes in Cisco MeetingPlace Express
Code (Dec)
|
Code
(Hex)
|
Severity
|
Display Text
|
Comments
|
131157
|
0x20055
|
MAJOR
|
Time has been set backwards. Some resource reservations may be lost.
|
The system clock has been set back to at least the previous month since the last time the Cisco MeetingPlace Express application was running. This can result in loss of some resource reservation records.
Recommended Action:
Verify the system clock. Always shut down the Cisco MeetingPlace Express application before changing the clock.
|
131192
|
0x20078
|
MAJOR
|
The CS is behind ## seconds. Conf ##, Next Event ##, Time ##
|
The conference management software has fallen behind processing conference life cycle events. This can indicate the system is overloaded. It can be a normal result of a system being down for a while. Repeated alarms about a failure to catch up may indicate a software defect.
Recommended Action:
No action required.
|
131198
|
0x2007E
|
INFO
|
No ports left to extend meeting. Erc ##,Now ##, Length ##, Ports ##
|
The Cisco MeetingPlace Express system was unable to extend a meeting due to lack of available voice ports.
Recommended Action:
No action required.
|
196686
|
0x3004E
|
MINOR
|
Too many conference events. Next event = ##, Conf = ##, Max events = ##
|
Probably indicates too many people entering or leaving a meeting at the same time, overloading the ability of the Cisco MeetingPlace Express system to queue up entry or exit announcements.
Recommended Action:
No action required.
|
196848
|
0x300F0
|
MINOR
|
Allocation of access ports to units has been fixed. Thank you!
|
A "too many access ports" condition (see error message 0x300F1) has been resolved.
Recommended Action:
No action required.
|
196849
|
0x300F1
|
MINOR
|
Too many access ports compared to licenses ##.
|
The configured number of voice ports exceeds the number of valid licenses, where ## is the configured value. This may be caused by the license being temporary expired.
Recommended Action:
No action required.
|
196943
|
0x3014F
|
WARN
|
FLEXLM: Failed to connect to license server; status = ##.
|
The license manager is not running, probably because no valid licenses are installed.
Recommended Action:
No action required.
|
196944
|
0x30150
|
MINOR
|
No conferencing licenses are installed.
|
The system has no valid licenses installed for either voice or web conferencing.
The system defaults to six voice conferencing licences.
Recommended Action:
Obtain and install licenses.
|
196946
|
0x30152
|
WARN
|
Unexpected LDAP response.
|
An unexpected response from the LDAP server, possibly indicating an incompatibility between systems.
Recommended Action:
No action required.
|
196950
|
0x30156
|
MINOR
|
Password authentication mechanism failure.
|
The password authentication feature is not working.
Recommended Action:
Check for an LDAP configuration problem or an LDAP server failure.
|
196953
|
0x30159
|
MINOR
|
Password authentication failure; may need to configure or application restart.
|
The password authentication feature is not working.
Recommended Action:
Check for an LDAP configuration problem or an LDAP server failure. Try restarting the application.
|
196959
|
0x3015F
|
INFO
|
No voice conferencing licenses are installed.
|
The system has a web conferencing license installed but no voice conferencing license.
Recommended Action:
Install voice conferencing licenses.
|
458788
|
0x70024
|
MAJOR
|
Module timed out on "are you there" query, class=##
|
One of the major software modules (identified by the class number) failed to respond to a query from the system integrity manager (SIM). This restarts the system.
Recommended Action:
Report all such occurrences to Cisco TAC for problem diagnosis.
|
458889
|
0x70089
|
WARN
|
Stopping exception log due to flooding.
|
The exception logging process stops logging if incoming messages exceed a certain rate. This prevents the logging mechanism from stealing critical resources when the system is overloaded.
Recommended Action:
No action required.
|
458890
|
0x7008A
|
INFO
|
Lost ## exception events; logging resumed.
|
The exception logging process dropped the indicated number of messages due to overload. Normal logging has now resumed.
Recommended Action:
No action required.
|
458916
|
0x700A4
|
MAJOR
|
System crashed: restarted by the integrity manager.
|
Alarm generated as the system comes back up; triggered by a flag set during a reboot initiated by the system integrity manager (SIM).
Recommended Action:
No action required.
|
1572903
|
0x180027
|
INFO
|
CPGS: Too many conference participants; can't create voice file.
|
The cumulative number of guest participants in a meeting has exceeded the system's ability to store name recordings for that meeting. The user name is not being recorded. This normally happens only during stress testing.
Recommended Action:
No action required.
|
1572914
|
0x180032
|
MINOR
|
CPGS: No space available for recording
|
Start of recording failed due to lack of disk space.
Recommended Action:
Purge old recordings.
|
2097190
|
0x200026
|
WARN
|
NMPAgent received late response (class=##, code=##)
|
The telephony or scheduling part of the system is running very slow, possibly due to overload.
Recommended Action:
No action required.
|
2162708
|
0x210014
|
MINOR
|
POC: Invalid email address for scheduler (##)
|
The meeting scheduler does not have a valid e-mail address; cannot send e-mail to that user. ## is the unique user ID of the scheduler.
Recommended Action:
No action required.
|
2162710
|
0x210016
|
WARN
|
POC: E-mail not sent. Client is not authenticated.
|
E-mail rejected by e-mail exchanger due to authentication failure. Likely an SMTP configuration problem.
Recommended Action:
No action required.
|
2162712
|
0x210018
|
WARN
|
POC: E-mail not sent. SMTP servers are unavailable.
|
Failed to connect to an SMTP e-mail exchanger. The exchanger may be down or there may be a problem with the SMTP configuration.
Recommended Action:
No action required.
|
2162713
|
0x210019
|
WARN
|
POC: E-mail not sent. Address format is invalid.
|
A recipient's e-mail address was rejected due to an invalid format.
Recommended Action:
No action required.
|
2162714
|
0x21001A
|
WARN
|
POC: SMTP server failed to deliver e-mails due to unknown recipient.
|
The SMTP e-mail exchanger rejected a recipient's e-mail address as unknown.
Recommended Action:
No action required.
|
2260993
|
0x228001
|
MINOR
|
Connection to web conferencing service restored.
|
Successfully reconnected to the web conferencing server.
Recommended Action:
No action required.
|
2260994
|
0x228002
|
MINOR
|
Error connecting to web conferencing service. Trying again...
|
Trying to reconnect to the web conferencing server.
Recommended Action:
None needed as long as the "Connection to web conferencing service restored" message is logged subsequent to this message.
If that message is not logged, then the system may need to be restarted or serviced.
|
2260995
|
0x228003
|
MINOR
|
Lost connection to web conferencing service. Trying again...
|
Trying to reconnect to the web conferencing server.
Recommended Action:
None needed as long as the "Connection to web conferencing service restored" message is logged subsequent to this message.
If that message is not logged, then the system may need to be restarted or serviced.
|
Module Numbers and Corresponding System Component
Some error messages refer to a module number but do not give the name of the corresponding system component.
The following is an example of an error message:
11/11 15:13:37.13 MAJ 0x70041 0/2, "siupdown.cc", 265 (0x8, 0, 0, 0)
Restarting due to software module failure, module = 8
In the second line of this example, it says module = 8, which, based on Table 6-3, indicates that the error was caused by the Voice User Interface.
Table 6-3 converts the module numbers to system component names.
Table 6-3 Module Numbers and Names
Internal Error Number
|
System Component
|
Module Number
|
Description
|
0
|
IMC_CLASS_NULL
|
0
|
|
1024
|
IMC_CLASS_COMMON
|
1
|
Common functions
|
2048
|
IMC_CLASS_SIM
|
2
|
System Integrity Manager (SIM)
|
3072
|
IMC_CLASS_CP
|
3
|
Call processing
|
4096
|
IMC_CLASS_SM
|
4
|
Switch manager
|
5120
|
IMC_CLASS_CS
|
5
|
Conference scheduler = ERC_BAD
|
6144
|
IMC_CLASS_WS
|
6
|
Workstation server
|
7168
|
IMC_CLASS_EXC
|
7
|
Exception handler (in SIM)
|
8192
|
IMC_CLASS_VUI
|
8
|
Voice user interface
|
9216
|
IMC_CLASS_DB
|
9
|
The database server
|
10240
|
IMC_CLASS_VUI_TESTER
|
10
|
VUI tester program
|
11264
|
IMC_CLASS_TRACE
|
11
|
SIM trace server
|
12288
|
IMC_CLASS_WF
|
12
|
Workstation front end
|
13312
|
IMC_CLASS_UTIL
|
13
|
Any command line utility
|
14336
|
IMC_CLASS_LSH
|
14
|
Shell facility
|
15360
|
IMC_CLASS_DBQ
|
15
|
Database query server
|
16384
|
IMC_CLASS_EMAIL_MSG
|
16
|
Class to support an error range
|
17408
|
IMC_CLASS_SNMPD
|
17
|
Class to support SNMP daemon control
|
18432
|
IMC_CLASS_PO
|
18
|
Post office server
|
19456
|
IMC_CLASS_PO_TESTER
|
19
|
Post office server tester program
|
20480
|
IMC_CLASS_SIM_MU
|
20
|
Multi-unit SIM session control
|
21504
|
IMC_CLASS_FAXGW
|
21
|
Fax gateway
|
22528
|
IMC_CLASS_WEBGW
|
22
|
Web publisher (overlaps with pegs)
|
22528
|
IMC_CLASS_PEGS
|
22
|
Peg server (part of SIM)
|
23552
|
IMC_CLASS_SDBS
|
23
|
Shadow database server
|
24576
|
IMC_CLASS_SDBS_TESTER
|
24
|
Shadow database server tester program
|
25600
|
IMC_CLASS_GWSIMGR
|
25
|
|
26624
|
IMC_CLASS_GWSIMAGENT
|
26
|
|
27648
|
IMC_CLASS_STREAMGW
|
27
|
Streaming gateway
|
28672
|
IMC_CLASS_CCA
|
28
|
Call control agent
|
29696
|
IMC_CLASS_MPDIRSVC
|
29
|
Directory services
|
30720
|
IMC_CLASS_MERGED
|
30
|
PCI conversion/merge daemon
|
31744
|
IMC_CLASS_GSCOPE
|
31
|
Gyroscope application
|
32768
|
IMC_CLASS_NMPAGENT
|
32
|
NMPAgent
|
33792
|
IMC_CLASS_TWATCH
|
33
|
Trigger watch
|
34816
|
IMC_CLASS_POCLIENT
|
34
|
Post office client
|
Feedback
