Guest

Cisco Unified MeetingPlace

MeetingPlace Audio Server Hardware Troubleshoot Procedure

MeetingPlace Audio Server Hardware Troubleshoot Procedure

Document ID: 116723

Updated: Nov 19, 2013

Contributed by Andrew Martin, Cisco TAC Engineer.

   Print

Introduction

This document describes the process used in order to troubleshoot the MeetingPlace Audio Server for Cisco Unified MeetingPlace Releases 6.1 and earlier.

Background

The MeetingPlace Audio Server is the main component of Cisco Unified MeetingPlace Releases 6.1 and earlier. This server manages meetings, handles VoIP and digital telephony, provides audio conferencing and mixing, contains the main database, and communicates with all other MeetingPlace components.

There are two hardware models:

  • MeetingPlace 8112 Chassis
  • MeetingPlace 8106 Chassis

Note: These servers use different replacement parts, with the exception of the Multi-Access (MA) blade and Smart blade.

Identify a MeetingPlace Audio Server 8112 or 8106 Chassis

This section describes the process used in order to identify a 8112 or a 8106 MeetingPlace Audio Server chassis.

Physical Inspection

You can identify the two chassis with an inspection of the physical appearances. This section describes how to do this.

8112 Audio Server

The 8112 Audio Server chassis has 12 vertical slots for telephony blades.

Here is the front view:

116723-technote-product-01.png

Here is the back view:

 116723-technote-product-02.png

8106 Audio Server

The 8106 Audio Server chassis has six horizontal telephony blades.

Here is the front view:

 116723-technote-product-03.png

Command Line Query

In order to identify these chassis with the CLI, enter the hwconfig command:

mtgplace:tech$ hwconfig
Cabinet:                Motorola CPX8216T
Bus architecture:       CompactPCI
Processor card: SMM5370LATUDE S/N=7644474
    Processor: Pentium III, Model 8, 700 MHz
    Memory: 512MB
    Temperature: 29C
    Voltages: 3.32V, 5.02V, 12.06V
Power Supplies:
    PS1: OK, fan is OK
    PS2: OK, fan is OK
    PS3: OK, fan is OK
SCSI Adapter: NCR 810
    DISK 1: 36000MB (SEAGATE ST373207LW REV=0005)
    DISK 2: 36000MB (SEAGATE ST373207LW REV=0005)
Ethernet: Intel 8225x PCI 10/100 (0001af195607)
    *** MAC Address ***
Modem: Absent or unrecognized
MultiAccess Blades:
    Slot 16: AC TP1610-4 S/N=1334228 REV=0 AC0
Smart Blades:
    Slot 1: NMS CG6000C S/N=1107389834 REV=5894-B8 MSC0 PRC0

On the 8112 chassis, this command output shows the Cabinet type, and three separate power supplies:

Cabinet:                Motorola CPX8216T

Power Supplies:
    PS1: OK, fan is OK
    PS2: OK, fan is OK
    PS3: OK, fan is OK

On the 8106 chassis, this command output shows the Cabinet type, and one power supply indicator:

Cabinet:                ELMA 4U
Power Supplies: OK

LED Light Identification

Here is a list of the top panel LEDs, and what they indicate:

  • System in Service - When illuminated, this light indicates that the system is in-service.
  • Component Out-of-Service - When illuminated, this light indicates that there is a component out-of-service. Check the alarm table.
  • System Out-of-Service - When illuminated, this light indicates that the system is out-of-service. This light illuminates red on the 8112 chassis.
  • Telco Major Alarm - When illuminated, this light indicates that there is a problem with Telco that might affect service. Check the alarm table.
  • Telco Minor Alarm - When illuminated, this light indicates that there is a minor problem with Telco problem that does not affect service. Check the alarm table.
  • Telco Critical Alarm - This light is not used.

Log in to the CLI

Complete these steps in order to log in to the CLI:

  1. Use Telnet, and log in to the Audio Server.

    • Ensure that the username is always admin.
    • If a hard drive is replaced,you might need to access the system with the default password, which is cisco.

  2. Change the admin password with the passwd command:

    mtgplace:tech$ passwd
    Changing password for admin
    Enter current password: cisco
    Enter new password: cisco123
    Retype new password: cisco123
  3. Complete these steps if the admin user account password is lost:

    1. Connect to the Audio Server either through the console port or with a monitor and keyboard that are plugged directly in to the CPU card. (Reference the Connecting and Setting Up Your Laptop Computer Cisco article for more details about this.)
    2. When prompted for the user name, enter pwreset. The admin password is now set to the default cisco:

      Release 6.1.1, Jul 16, 2013user name: pwresetuser name: adminPassword: cisco

    Note: Password recovery does not work when you use Telnet or Secure Shell (SSH) in order to connect with the Audio Server.

Hard Drives

Here are some important notes about the 8112 and 8106 hard drives:

  • MeetingPlace 8112 and 8106 chassis have two hard drives.
  • The hard drives contain all of the data for MeetingPlace, such as the MeetingPlace software, the configuration settings, the users, and the meetings.
  • The operating system and MeetingPlace software run on only one active hard drive, while data is routinely backed up to the other hard drive.   

Disk Backups

This section describes the disk backup process for the two MeetingPlace chassis. Here are some important notes:

  • When data is backed up from the active hard drive to the inactive hard drive, the process is referred to as a disk backup. It is important to understand that disk backups are not the same as remote or gateway backups.
  • If automatic disk backups are enabled, the active hard drive copies data to the secondary hard drive once an hour by default.
  • In order to enable disk backups and to ensure that the data matches between the two hard drives, enter the save command.
  • The two hard drives should essentially be mirrored, with these exceptions:

    • Meeting recordings
    • Recorded profile names

      Note: These are split between the two disks, so half will be lost if a drive is replaced.

    • In order to check if automatic disk backups are enabled, enter the sysconfig command:

      mtgplace:tech$ sysconfig
      Root: 1a
      Database: 1c
      Temporary files: 2b
      Prompts: 1f
      Voice files: 1g
      Voice files: 2g

      The current configuration matches the saved configurationDisk backups are enabled

      If you have not saved, then the last two lines show as:

      The current configuration matches the saved configuration
       WARNING: Disk backups are disabled. Run "save" to enable.
  • Complete these steps in order to view logs for disk backups:

    1. Connect via Telnet to the Audio Server as the admin user.
    2. Enter su, and enter the password of the day. You might need to generate the password of the day with the Password utility.
    3. Enter cat /usr/adm/diskbackup.log. This is the latest disk backup log, which shows when the backup last occurred, and if it was successful.
    4. In order to view the log from the previous disk backup, enter cat /usr/adm/diskbackup.log.old. It is important to know that this is not the same as a backup.log, which is for remote backups to the MeetingPlace Backup Gateway.

Disk Partitions

The operating system and MeetingPlace software run on only one active hard drive, which is on the root partition. The database runs on another partition that might be the same hard drive where the application runs.

Enter the sysconfig command in order to check the hard drive on which the application (Root) and database runs, and if a disk backup is performed regularly:

mtgplace:tech$ sysconfig
Root: 1a
Database: 1c
Temporary files: 2b
Prompts: 1f
Voice files: 1g
Voice files: 2g

The current configuration matches the saved configurationDisk backups are enabled

The value 1 in front of the partition letter (1c, for example) indicates that MeetingPlace runs off of the first (top) hard disk. The value 2 indicates the second (bottom) hard drive.

Note: Voice files are always saved on both hard drives, because they are not mirrored.

 116723-technote-product-04.png  

Save and Revert

Here are some important notes about the save and revert process:

  • If the system is down, it has an option to save the Data Base (DB) immediately (save -d).
  • If the system is up, only application files and prompts are saved immediately, and the rest is saved at the regular scheduled time (ten minutes after the hour).
  • For each software upgrade, automatic saves are disabled. After the server runs stable for a week, enter a save command.
  • If needed, you can revert to the previous version with the revert command (you must save after a revert).
  • Enter the sysconfig command in order to verify if disk backup is enabled.  

Revert

Enter the revert command in order to force MeetingPlace to boot to a different hard disk. The system must be in a down state first. In order to ensure this, enter the down command:

mtgplace:csc$ down
Are you sure (y/n)? y
Checking to see if the system is loaded...
The System Integrity Manager is not running.
The system is already down.
The system is DOWN.

mtgplace:csc$ revert
Root file system options:
 1) Disk 1 part "a" Rel 6.0.4 Wed Sep 5 09:45:34 2008 (current)
 2) Disk 2 part "a" Rel 6.0.2 Wed Jun 4 09:36:26 2008
 q) Quit
Choice? [q] 2
The root file system will be switched

Database file system options:
 1) Disk 1 part "c" Rel 6.0.4 (DB=6.0.0) 09:45:34 2008 (current)
 2) Disk 2 part "c" Rel 6.0.2 (DB=6.0.0) 09:36:26 2008
 3) Disk 2 part "e" Rel 6.0.2 (DB=6.0.0) 09:36:26 2008
Choice? [q]2
The database file system will be switched
You have selected a different database file system (2e)

Proceed (y/[n])? y
DONE
NOTE: Changes take effect after the next restart
mtgplace:csc$ restart enable
Are you sure (y/n)? y  

Boot Process

Here are some important notes in order to help you understand the boot process:

  • MeetingPlace 8112 and 8106 chassis must have a hard drive in the bottom slot (slot 2) in order to boot.
  • After the system detects a hard drive in the bottom slot, the system loads the operating system and MeetingPlace software from either one of the two hard drives.

    • Enter the sysconfig command in order to show the hard drive from which the operating system, MeetingPlace software, and DB are loaded.
    • Enter the revert command in order to change the hard drive from which the operating system, MeetingPlace software, and DB load.

      Note: You cannot determine the hard drive from which the operating system, MeetingPlace software, and DB load until they are actually loaded.

  • If there is no hard drive in the top slot (slot 1), then the server loads the operating system, MeetingPlace software, and DB from the bottom hard drive.
  • If there is no hard drive in the bottom slot (slot 2), then the server does not boot.  

Troubleshoot

If the system is down and cannot boot, the most common issue is a hardware fault with one of the hard drives. In order to identify a faulty hard drive, check for these issues:

  • The system powers on, but does not boot.
  • The server continuously reboots.
  • There is no console log, or there is a strange error on the console.
  • There is an error message similar to this:
    Command: <sdncr.la/lynx.os>cannot open device sdncr.la
  • There is disk corruption identified from a variety of errors.

    • Enter the alarm command, and check for recent errors with RAIMA or fsopenfile.cc.
    • The system out-of-service LED displays red on the 8112 chassis.

Note: For additional information about about alarms, reference the Cisco Unified MeetingPlace Release 6.1 - About Alarms article.

If you replace the hard disk and it does not recover the system, continue to troubleshoot the cards, blades, and any power-related issues.

Find the Faulty Hard Drive

Use these two procedures in order to identify the faulty hard drive.  

Procedure 1

  1. Turn the MeetingPlace Server off.
  2. Remove Drive 1 (top drive).
  3. Turn the MeetingPlace Server on.

The system tries to boot to Drive 2. This procedure works if Drive 1 is the problem. MeetingPlace always boots to the bottom drive (drive 2). If there is no hard drive in the bottom slot, the system does not boot. However, after the boot, it might run the DB load, operating system, and MeetingPlace software on the other hard drive.  

Procedure 2

If the previous procedure does not work, complete these steps:

  1. Turn the MeetingPlace Server off.
  2. Remove both drives.
  3. Reassign the Small Computer System Interface (SCSI) ID for Drive 1 so that it becomes Drive 2 and has SCSI ID 1. (For the 8112 chassis only.)
  4. Plug the former Drive 1 in to the lower-right slot (Drive 2). Leave the upper-right slot (Drive 1) empty.
  5. Turn the MeetingPlace Server on. This procedure works if Drive 2 is the problem. 

SCSI ID for MeetingPlace 8112 Chassis Hard Drives

Hard drives for the MeetingPlace 8112 chassis have SCSI IDs that must be configured correctly, while the 8106 chassis do not have SCSI IDs. All disk drives are shipped from the factory with SCSI IDs set to zero.

The hard drive on the top (Drive 1) is SCSI ID 0. The hard drive on the bottom (Drive 2) is SCSI ID 1. Replacement hard drives should include a tool that is used in order to turn this SCSI ID. However, you might also use a key, coin, screw driver, or fingernail in order to turn this dial.

 116723-technote-product-05.png  

Replace a Failed Disk Drive

This section describes the processes used in order to replace a failed disk drive on either of the MeetingPlace chassis previously described.  

MeetingPlace 8106 Chassis

Complete these steps in order to replace a failed disk drive on the 8106 chassis:

Note: Reference the Hard Disk Replacement Procedure for the Cisco MeetingPlace 8106 Cisco article for more details.

  1. Use a Phillips screwdriver in order to remove the screw that secures the disk drive to the chassis. This screw is located in the front-left area of the disk drive.
  2. Use a Phillips screwdriver in order to loosen the screw in the latching mechanism (to the right of the red tab). The latching mechanism is located in the front-right area of the disk drive.
  3. Push the red tab inside the latching mechanism in, and pull the black handle out. The disk drive pops out of the connector in the drive bay.
  4. Slide the disk drive out of the drive bay.
  5. When you reinsert the new disk drive, there are slide rails that it must slide into.

Note: There are no SCSI IDs for the 8106 chassis.  

MeetingPlace 8112 Chassis

Note: Reference the Hard Disk Replacement Procedure for the Cisco MeetingPlace 8112 Cisco article for more details.

There are two different form factors for disk drives on the 8112 chassis: The original form factor has a brass-colored key in the front, while the newer form factor has a key-lock system in the front:

 116723-technote-product-06.png

Inspect the front of the MeetingPlace 8112 Audio Server in order to determine the type of disk drive form factor that is installed.

Due to a manufacturing change, the disk drives for the MeetingPlace 8112 Audio Server now use a new carrier that no longer just slides into the 8112 chassis. New replacement disks drives for an MeetingPlace 8112 Audio Server result in the newer form factor.

If the MeetingPlace 8112 Audio Server chassis contains the original form factor, with the brass-colored keys, the replacement disk drive might not fit without additional actions. Additional steps are contained within the 8112 Audio Server Replacement Drive Guide PDF.

When a Return Material Authorization (RMA) is opened with Cisco for the hard drive replacement, it is required that a Field Engineer (FE) is dispatched with the parts needed in order to perform this procedure. Cisco Technical Assistance Center (TAC) might need to send the 8112 Audio Server Replacement Drive Guide document to the FE or Cisco on-site resource in order to ensure that they have the correct information.

If the 8112 chassis contains the original form factor, and a replacement disk drive also contains the original form factor:

  1. Press the brass-colored key in, in the upper-left area of the disk drive, and turn it counterclockwise one-quarter turn. This releases the disk drive from the drive bay.
  2. Slide the disk drive out of the drive bay.

Note: This should be a yellow dial, and you should be able to change this with a small screw driver or your keys.

The drive on the top has SCSI ID 0, and the drive on the bottom has SCSI ID 1.

Additional Troubleshoot Steps

Enter the hwconfig command in order to ensure that the system detects the new disk drive.

mtgplace:tech$ hwconfig
Cabinet: Motorola CPX8216T
Bus architecture: CompactPCI
Processor card: SMM5370LATUDE S/N=7644474
    Processor: Pentium III, Model 8, 700 MHz
    Memory: 512MB
    Temperature: 29C
    Voltages: 3.32V, 5.02V, 12.06V
Power Supplies:
    PS1: OK, fan is OK
    PS2: OK, fan is OK
    PS3: OK, fan is OK
SCSI Adapter: NCR 810
    DISK 1: 36000MB (SEAGATE ST373207LW REV=0005)
    DISK 2: 36000MB (SEAGATE ST373207LW REV=0005)

Ethernet: Intel 8225x PCI 10/100 (0001af195607)
 *** MAC Address ***
Modem: Absent or unrecognized
MultiAccess Blades:
    Slot 16: AC TP1610-4 S/N=1334228 REV=0 AC0
Smart Blades:
    Slot 1: NMS CG6000C S/N=1107389834 REV=5894-B8 MSC0 PRC0

Enter the swstatus command in order to verify the MeetingPlace version and if all modules start successfully. You can use this command periodically while the system is comes up. It might take up to 15 minutes for all modules to start.

mtgplace:tech$ swstatus
Conference server 6.0.4 S/N:
System status: Operating
System mode: Coming up
Temperature: Unknown
Power supply: OK

MODULE NAME STATUS VERSION
SIM UP "09/29/08 06:38 MPBUILD-R6_0_4_4"
LSH UP "09/29/08 06:14 MPBUILD-R6_0_4_4"
SNMPD UP "09/29/08 06:55 MPBUILD-R6_0_4_4"
DBSERVER UP "09/29/08 06:19 MPBUILD-R6_0_4_4"
DBQSERVER UP "09/29/08 06:19 MPBUILD-R6_0_4_4"
POSERVER DOWN "09/29/08 06:31 MPBUILD-R6_0_4_4"
CPSERVER DOWN "09/29/08 06:29 MPBUILD-R6_0_4_4"
CONFSCHED DOWN "09/29/08 06:37 MPBUILD-R6_0_4_4"
WSSERVER DOWN "09/29/08 06:39 MPBUILD-R6_0_4_4"
VOICESERVER DOWN "09/29/08 06:50 MPBUILD-R6_0_4_4"
GWSIMMGR DOWN "09/29/08 07:03 MPBUILD-R6_0_4_4"

mtgplace:tech$ swstatus
Conference server 6.0.4 S/N:
System status: Operating
System mode: Up
Temperature: 41
Power supply: OK

MODULE NAME STATUS VERSION
SIM UP "09/29/08 06:38 MPBUILD-R6_0_4_4"
LSH UP "09/29/08 06:38 MPBUILD-R6_0_4_4"
SNMPD UP "09/29/08 06:38 MPBUILD-R6_0_4_4"
DBQSERVER UP "09/29/08 06:38 MPBUILD-R6_0_4_4"
DBSERVER UP "09/29/08 06:38 MPBUILD-R6_0_4_4"
POSERVER UP "09/29/08 06:38 MPBUILD-R6_0_4_4"
CPSERVER UP "09/29/08 06:38 MPBUILD-R6_0_4_4"
CONFSCHED UP "09/29/08 06:38 MPBUILD-R6_0_4_4"
WSSERVER UP "09/29/08 06:38 MPBUILD-R6_0_4_4"
VOICESERVER UP "09/29/08 06:38 MPBUILD-R6_0_4_4"
GWSIMMGR UP "09/29/08 06:38 MPBUILD-R6_0_4_4"

UNIT SITE STATUS RUN LEVEL UNIT KIND LAST ATTACH
  16 0 OK UP GATEWAY 07/10/13 11:00:15
  17 0 OK UP GATEWAY 07/10/13 11:01:11
  18 0 OK UP GATEWAY 07/10/13 11:01:08


If one hard drive is replaced, the system might boot to the new hard drive instead of the old hard drive. Connect to the Audio Server via MeetingPlace in order to determine if users and meetings are retained. Enter the swstatuscommand in order to check if the new version matches the previous version.

If the Audio Server boots to the wrong hard drive:

  • Enter the down command in order to shut down all MeetingPlace services.
  • Enter the revert command in order to boot to the other hard drive.
  • Enter the boot choices for the root file system and the DB.
  • Enter the restart enable command in order to restart the server.
mtgplace:csc$ down
Are you sure (y/n)? y
Checking to see if the system is loaded...
The System Integrity Manager is not running.
The system is already down.
The system is DOWN.

mtgplace:csc$ revert
Root file system options:
 1) Disk 1 part "a" Rel 6.0.4 Wed Sep 5 09:45:34 2008 (current)
 2) Disk 2 part "a" Rel 6.0.2 Wed Jun 4 09:36:26 2008
 q) QuitChoice? [q] 2
The root file system will be switched

Database file system options:
 1) Disk 1 part "c" Rel 6.0.4 (DB=6.0.0) 09:45:34 2008 (current)
 2) Disk 2 part "c" Rel 6.0.2 (DB=6.0.0) 09:36:26 2008
 3) Disk 2 part "e" Rel 6.0.2 (DB=6.0.0) 09:36:26 2008
Choice? [q]2
The database file system will be switched
You have selected a different database file system (2e)

Proceed (y/[n])? y
DONE
NOTE: Changes take effect after the next restart
mtgplace:csc$ restart enable
Are you sure (y/n)? y

The root file system and the DB choices show as (current), which indicates that those are the current active partitions or hard drives. Choose a different partition for each in order to boot to another hard disk.

If both disks are replaced or all data is lost, restore the DB backup, if available. Enter the restore command in order to restore the data from a MeetingPlace Backup Gateway.

Note: When you restore the data on the MeetingPlace Audio Server, the Audio Server version must be the same version as when the backup was taken. If both hard drives were replaced, you might need to upgrade the MeetingPlace Audio Server software to the same version of the previous system.

Reference these documents for further details:

mtgplace: tech$ gwstatus
Gateway SIM Status/Mon Dec 1 16:45:22 2003
________________________________________________
Remote Units
Unit 16 Severname 2 v5.2.0.13 Ok 12/01/03 16:45:20
Unit 17 Severname 2 v5.2.0.13 Ok 12/01/03 16:44:57
Unit 18 Severname 2 v5.2.0.14 Ok 12/01/03 16:45:15
Gateways:
Unit 16 IP Gateway v5.2.0.12 Ok 12/01/03 07:56:50
Unit 16 MPBackup v5.2.0.5 Ok 12/01/03 16:45:14
Unit 17 DataConf:GCC v4.3.0.100 Ok 12/01/03 16:44:56
Unit 17 DataConf:GW v4.3.0.100 Ok 12/01/03 16:44:20
...
Unit 18 MPBackup v5.2.0.5 Ok 12/01/03 16:45:03

You can only restore from a Backup Gateway if the MeetingPlace modules are all started, which can be confirmed with the swstatus command.

In this example, the restore command is entered, 2 is selected in order to restore from a file that is located on a network drive, and y is entered in order to begin the restore process:

MPServer: tech$ restore 
Restore database from?
1) Local file
2) Remote file
q) (Quit Restore)
Enter choice: 2
Remote source if from a remote file
restore.gateway: started
Thu Oct 23 18:20:23 PDT 2003
restore.gateway will bring down the MeetingPlace applications and
 OVERWRITE the current contents of the database.
First step: just copy the backup files to this server?
Proceed (y/[n])? y
restore.gateway: detailed output is saved in /usr/adm/restore.log
 for reference

This sample output shows that there are two backup gateway servers from which to choose, unit 19 and unit 21:

Available units for backup:
1) unit 19
2) unit 21
Pick an available gateway
Enter choice [1-2]:

After a backup gateway server is selected, a list of available backup files appears:

Checking available backup files on this unit...
Backup location is C:/Program Files/Latitude/MeetingPlace Backup/BACKUP
Available backup files:
1) file name: BU_0001af03b786_20031007121534.tgz
Date of Backup: 10/07/2003 at 12:14:14
File size: 6450211 bytes
2) file name: BU_0001af03b786_20031008121515.tgz
Date of Backup: 10/08/2003 at 12:14:55
File size: 6451990 bytes
3) file name: BU_0001af03b786_20031009121543.tgz
Date of Backup: 10/09/2003 at 12:15:23
File size: 6450275 bytes
Pick an available file
Enter choice [1-3 or <cr> to abort]:

As the next example shows, the system must be downed in order to complete the backup process:

Down the system and complete the backup?
Proceed (y/[n])? y

After you replace one hard drive, you might have to rerecord your name when you join a meeting. If you continue to encounter problems with recordings or  recorded names, you might need to enter the vfptrfix -f command.

You might also receive an error message that tells you the system is out of recording space. If this is the case, complete this process in order fix the pointer to the recordings if you restore the DB, and the recording no longer exists or only partially exists:

  1. Schedule a maintenance window for at least two hours.
  2. Enter the su command.
  3. Enter the password of the day.
  4. Enter the down command.
  5. Enter the vfptrfix -f -v command.
  6. Enter the restart enable command.
mtgplace:csc$ down
Are you sure (y/n)? y
Checking to see if the system is loaded...OK System DOWN procedure hasbeen initiated.
The system is DOWN.
mtgplace:csc$ vfptrfix -f -v
Running vfptrfix...
Initializing the file system...
Getting the disk configuration status...
Checking file system internal consistency...(may take a while)...
Checking voice file pointers in database...
CsConf *Processed 451 Conferences* - CsConfPart&& *Processed 14547 Conf
part*
- CsConfAtt&# *Processed 216 Conf Attachments* - CsUser&#&& *Processed
1260 Users* - CsPrompt& *Processed 7853 Prompts* - CsTimeZone
*Processed 319
Time zones* - CsCAPrompt *Processed 25 FlexMenuCAPrompt* - CsUserList
*Processed
29 UserList* - CsRemoteServer *Processed 14 RS* -
Checking file system validation status...
Committing the changes to the database...
mtgplace:csc$ restart enable
Are you sure (y/n)? y

You might receive this error message:

ERROR: Invalid disk label / CPU combination
BOOT disk = 0001af0d981b; ALT disk = INVALID; CPU = 0001af127478
ERROR: Disk mount failed; manual intervention required

In older versions of MeetingPlace, you might need to delete the /.label file if you only insert one drive (this is not common). Complete these steps in order to delete the file:

  1. Connect to the Audio Server as admin via Telnet.
  2. Enter the su command, and enter the password of the day.
  3. Enter rm /.label and y when prompted.  

Blades/Line Cards

This section describes the various blades and line cards.

CPU Card

The CPU card is required in order for the Audio Server to function. It contains the Ethernet connectivity that is used in order to maintain and configure the server. The CPU card has its own IP address that is used in order to connect it to the MeetingTime, Telnet access, and MeetingPlace Gateway Servers.

Here is the front view: 

116723-technote-product-07.png

Here is the back view:

116723-technote-product-08.png

If you replace the CPU card, you must obtain new licenses. Licenses are bound to the MAC address of the Ethernet port on the CPU card. If a full chassis is replaced with an RMA, it comes with a replacement CPU card.  

Identify a Faulty CPU Card

Before you attempt to identify a faulty CPU card, first determine if a hard drive is at fault. After you progress through the hard drive recovery procedure, these issues might indicate a faulty CPU card:

  • There is no output from the console or monitor ports.
  • The server does not boot.
  • The Ethernet port does not respond after you check the speed and duplex of the switch.
  • The console port does not respond. 

Replace the CPU Card

Note: For a more detailed procedure, reference the CPU Replacement Procedure for the Cisco MeetingPlace 8100 Series Cisco article.

Here is the general procedure that is used in order to replace a faulty CPU card:

  1. If possible, obtain the MAC address of the old CPU card; enter the getether command, or locate the previous license file.
  2. Remove all network, modem, and SCSI cables.
  3. Power down the server.
  4. Replace the CPU card front and back.
  5. Reconnect all network, modem, and SCSI cables.
  6. Power up the system.
  7. Obtain and install new software licenses.

After you replace the CPU card, you must install the license keys for the new replacement CPU card. All software options are keyed off of the unique Ethernet MAC address of the CPU card. In order to obtain the MAC address of the CPU card, enter the getether command. Request for a new license to be generated through the Licensing TAC team.

mtgplace:tech$ getether
0001af666607

When you install new software licenses, Cisco recommends that you load the license keys individually in MeetingTime. This ensures that the licenses are valid as soon as the > key is pressed. After the new keys are installed, restart the system with the restart enable command.

Note: Reference the Cisco Unified MeetingPlace, Release 6.x -- About Loading License Keys article for additional details  

Network Interface Card (NIC) Settings

The speed and duplex settings for Ethernet ports on the Audio Server are hard-set and cannot be changed. The appropriate speed and duplex settings must be configured on the connected switch ports:

  • For the CPU card, the settings are auto/auto, respectively.
  • For the MA blade, the settings are 100/full, respectively. 

MA Blade

Here is an example of an MA blade:

 116723-technote-product-09.png

Here are some important notes about MA blades:

  • MA blades appear as either TP1610 or TP1610-4 in the blade and hwconfig command outputs.

    • The MA-16 versions (TP1610) have 16 spans, and up to 480 IP ports.
    • The MA-4 versions (TP1610-4) have four spans, and up to 120 IP ports.

  • The T1 PRI and E1 use the second (9-16) connector on the MA-4 blade.
  • There are, at most, two MA blades per 81xx system.
  • MA blades still require Smart blades for conferencing.
  • MA blades requires one IP address per 240 IP ports. 

Identify a Faulty MA Blade

Before you attempt to identify a faulty MA blade, first determine if a hard drive is at fault. If the MeetingPlace Audio Server does not fully boot as shown in swstatus command output, it might indicate a faulty MA blade. If this is the case, complete these steps:

  • Power down the Audio Server.
  • Remove the front and back for all MA blades and Smart blades (the CPU card should still be connected).
  • Power on the Audio Server, and see if all services start properly.
  • If all services start properly, power down the server, and reinsert the blades one at a time.
  • If the services do not start after the MA blades are reinserted, attempt to reconfigure the blades and ports via the blade command (see the Additional Steps section for more details). This requires another restart of the server with the restart enable command.
  • If the services still do not start, then this indicates a faulty MA blade.
mtgplace:tech$ swstatus
Conference server 6.0.4 S/N: not set
System status: Operating
System mode: Coming up
Temperature: Unknown
Power supply: OK

MODULE NAME STATUS VERSION
SIM UP "09/29/08 06:38 MPBUILD-R6_0_4_4"
LSH UP "09/29/08 06:14 MPBUILD-R6_0_4_4"
SNMPD UP "09/29/08 06:55 MPBUILD-R6_0_4_4"
DBSERVER UP "09/29/08 06:19 MPBUILD-R6_0_4_4"
DBQSERVER UP "09/29/08 06:19 MPBUILD-R6_0_4_4"
POSERVER DOWN "09/29/08 06:31 MPBUILD-R6_0_4_4"
CPSERVER DOWN "09/29/08 06:29 MPBUILD-R6_0_4_4"
CONFSCHED DOWN "09/29/08 06:37 MPBUILD-R6_0_4_4"
WSSERVER DOWN "09/29/08 06:39 MPBUILD-R6_0_4_4"
VOICESERVER DOWN "09/29/08 06:50 MPBUILD-R6_0_4_4"
GWSIMMGR DOWN "09/29/08 07:03 MPBUILD-R6_0_4_4"

This might also be stuck while STARTING one of the services (especially CPSERVER):

MODULE NAME          STATUS     VERSION
SIM UP "03/19/12 09:52 MPBUILD-R6_1_1_5"
LSH UP "03/19/12 09:28 MPBUILD-R6_1_1_5"
SNMPD UP "03/19/12 10:09 MPBUILD-R6_1_1_5"
DBQSERVER UP "03/19/12 09:33 MPBUILD-R6_1_1_5"
DBSERVER UP "03/19/12 09:33 MPBUILD-R6_1_1_5"
POSERVER DOWN "03/19/12 09:44 MPBUILD-R6_1_1_5"
CPSERVER STARTING "03/19/12 09:42 MPBUILD-R6_1_1_5"
CONFSCHED DOWN "03/19/12 09:50 MPBUILD-R6_1_1_5"
WSSERVER DOWN "03/19/12 09:53 MPBUILD-R6_1_1_5"
VOICESERVER DOWN "03/19/12 10:03 MPBUILD-R6_1_1_5"
GWSIMMGR DOWN "03/19/12 10:20 MPBUILD-R6_1_1_5"

UNIT SITE STATUS RUN LEVEL UNIT KIND LAST ATTACH

If there is continued VoIP connectivity with MeetingPlace after you verify the switch port settings, you might have to adjust the speed and duplex settings. The speed and duplex settings for Ethernet ports on the MA blade are hard-set and cannot be changed; the appropriate speed and duplex settings must be configured on the connected switch ports. For the MA blade, the settings should be 100/full, respectively.  

Replace an MA Blade

Reference the Blade Replacement Procedure for the Cisco MeetingPlace 8100 Series Cisco article for information about how to replace an MA blade.  

Additional Steps

If all MA blades and Smart blades are removed for troubleshoot purposes, you might need to remove all blade/port configuration via the blade command: Enter the blade command, and then enter Modify blade in order to remove each blade. Begin with the first MA blade listed.

When prompted to enter the Type, enter the word none.

mtgplace:tech$ blade

Slot Card Type CardId Ports
---- ---- ---- ------ -----
 1 CG6000C SB 0
 2 no card
 3 no card
 4 no card
 5 no card
 6 no card
 11 no card
 12 no card
 13 no card
 14 no card
 15 no card
 16 TP1610-4 IP 0 0-94 (10.86.76.191)
 
***** B L A D E C O N F I G M E N U *****

        1) View blade details
        2) Modify blade
        x) Exit program

Enter command: 2
Enter blade slot [1..16]: 16

Type [IP]: none

Slot Card Type CardId Ports
---- ---- ---- ------ -----
 1 CG6000C SB 0
 2 no card
 3 no card
 4 no card
 5 no card
 6 no card
 11 no card
 12 no card
 13 no card
 14 no card
 15 no card
 16 TP1610-4

***** B L A D E C O N F I G M E N U *****

        1) View blade details
        2) Modify blade
        x) Exit program

Enter command: 2
Enter blade slot [1..16]: 1

  Type [SB]: none

Slot Card Type CardId Ports
---- ---- ---- ------ -----
 1 CG6000C
 2 no card
 3 no card
 4 no card
 5 no card
 6 no card
 11 no card
 12 no card
 13 no card
 14 no card
 15 no card
 16 TP1610-4

***** B L A D E C O N F I G M E N U *****

        1) View blade details
        2) Modify blade
        x) Exit program

Enter command: x

Restart the system for any changes to take effect
mtgplace:tech$ restart enable

After an MA blade or both hard drives are replaced, you might need to reconfigure the ports. The system might not boot properly if the blade and port configurations do not match, or if they exceed the current MA blade and Smart blade hardware. For example, if 120 ports are configured, but there is only one Smart blade capable of 96 ports, the CPSERVER module might not start.

Note: For additional details, reference the Cisco Unified MeetingPlace, Release 6.x -- About Configuring the Blades article.  

Blade Configuration Commands

Here is a list of useful blade configuration commands:

  • blade -i96 -t96 - Enter this command in order to configure a blade on a 6-port IP, and 96-port T1 system.:
  • blade -i96 -e96 - Enter this command in order to configure a blade on a 96-port IP, and 96-port E1 system.
  • blade -t96 -r1 -r2 - Enter this command in order to configure a blade on a 96-port T1 system (this reserves Slots 1 and 2 for later provisioning).

After you configure the ports automatically, finish the configuration of the MA blade:

mtgplace:tech$ blade -i 120
This will reset many DB tables, are you sure? (y/n): y

Configuring 96 IP ports

Restart the system for changes to take effect

mtgplace:tech$ blade

Slot Card Type CardId Ports
---- ---- ---- ------ -----
 1 CG6000C SB 0
 2 CG6000C SB 1
 3 no card
 4 no card
 5 no card
 6 TP1610 IP 0 0-119 (No IP address)

***** B L A D E C O N F I G M E N U *****
1) View blade details
2) Modify blade
x) Exit program


Enter command: 2
Enter blade slot [1..6]: 6

  Type [IP]:
  Card type [TP1610]:
  Port Group [ 1]:
  Number of Ports [ 96]:
  1st Port [ 0]:
  IP Address [0] [0.0.0.0]: 14.114.2.3
  IP Address [1] [0.0.0.0]:
  Subnet Mask [0.0.0.0]: 255.255.255.0
  Default Gateway [0.0.0.0]: 14.114.2.1
  Base UDP Port [0] [16390]:
  Base UDP Port [1] [16390]:
  Jitter Buffer Minimum Size [100]:
  Jitter Buffer Optimization [ 7]:
  IP Precedence [0]: unused
  Type of Service (TOS) [ 0]: unused
  DSCP / DiffServ [unused]: 46
  RTCP Interval [default]:

Slot Card Type CardId Ports
---- ---- ---- ------ -----
 1 CG6000C SB 0
2 CG6000C
 3 no card
 4 no card
 5 no card
6 TP1610 IP 0 0-119 (14.114.2.3)

***** B L A D E C O N F I G M E N U *****

1) View blade details
2) Modify blade
x) Exit program

Enter command: x

Restart the system for any changes to take effectmtgplace:tech$ restart enable

You might receive this message while you configure the MA blade:

*****   B L A D E   C O N F I G   M E N U   *****

1) View blade details
2) Modify blade
x) Exit program

Enter command: 2
Enter blade slot [1..6]: 6

  Type [IP]:
  Card type [TP1610-4]:

** Warning: Configured value does not match card type installed (TP1610)
** Hardware needs to match configuration before next restart, or else
** system will fail to come up.

If you receive this message, manually enter TP1610 for the Card type. If this is a Shadow server, you must convert it to stand-alone before you configure the new blades.

Note: All blade configuration changes require a restart via the restart enable command in order to take effect.

After a hard drive or MA blade is replaced, and the blades are reconfigured, you might need to enter the port configuration in MeetingTime. Complete these steps in order to enter the port configuration:

  1. Open MeetingTime, and click Registration Book.
  2. Navigate to the Configure tab, and click Server Configuration.
  3. Verify that these settings match the licensed ports, and edit if necessary:

    • Access Ports (accessports)
    • Conference Ports (confports)
    • Full Web Conferencing Ports (dataconf)
  4. Restart the server via the restart enable command in order for changes to take effect.


116723-technote-product-10.png  

Smart Blade

Here is an example of a Smart blade:

116723-technote-product-11.png

Note: The image is outdated; the Ethernet ports on this card are no longer used.

Here are some important notes about Smart blades:

  • Smart blades appear as NMS CG6000C in blade and hwconfig command outputs.
  • The physical Digital Signal Processor (DSP) resides in the Smart blades.
  • There are 96 ports on each card.
  • Smart blade interfaces only support T1-Channel Associated Signaling (CAS) connections. 

Identify a Faulty Smart Blade

If you notice static or dead-air consistently on specific ports, this might indicate a hardware failure on the Smart blade. Typically, there are issues on eight or four ports in a row, since there are eight ports for each DSP.  

Replace a Smart Blade

In order to replace a faulty Smart blade, reference the Blade Replacement Procedure for the Cisco MeetingPlace 8100 Series Cisco article.  

Power Issues

This section describes power issues that you might encounter with fuses, power supplies, and fan trays. 

Fuses

If the server does not power up at all, and no LED lights illuminate, this indicates a blown fuse. There is no part number for the fuse in order to RMA, so you must RMA the entire chassis.

However, you can purchase a new fuse at a local electronics store, such as RadioShack. The Cisco MeetingPlace 8106 chassis uses two 4-amp, 250-volt, AGC-type fuses that have a 0.25-inch diameter and are 1.25-inches long. Reference the Fuse Replacement Procedure for the Cisco MeetingPlace 8106 Cisco article for additional details.  

Power Supplies

In order to identify power supply issues, check for any burning smells or smoke. If you identify smoke or burning, have the chassis turned off immediately, and check for physical damage to all components. Check the chassis back plane on both sides.

Faulty power supplies might also be indicated by alarms or by a red LED light on the power supply. The 8112 chassis has three power supplies that appear in the hwconfig command output. The 8106 chassis has two power supplies, but they appear as one in the hwconfig command output. Reference the Power Supply Replacement Procedure for the Cisco MeetingPlace 8112 or the Power Supply Replacement Procedure for the Cisco MeetingPlace 8106 article for additional details.

 116723-technote-product-12.png  

Fan Trays

Faulty fan trays might be indicated by alarms or by a red LED. For additional details, reference the Fan Tray Replacement Procedure for the Cisco MeetingPlace 8106 Cisco article.  

Related Information

Updated: Nov 19, 2013
Document ID: 116723