Configuration and Maintenance Guide for Cisco Unified MeetingPlace Express Release 1.2
Maintaining the Cisco Unified MeetingPlace Express System
Downloads: This chapterpdf (PDF - 282.0KB) The complete bookPDF (PDF - 5.53MB) | Feedback

Maintaining the Cisco Unified MeetingPlace Express System

Table Of Contents

Maintaining the Cisco Unified MeetingPlace Express System

Information About SNMP

Requirements for SNMP

Displaying SNMP Community Strings

Adding an SNMP Community String

Editing an SNMP Community String

Deleting an SNMP Community String

Displaying SNMP Notification Destinations

Adding an SNMP Notification Destination

Editing an SNMP Notification Destination

Deleting an SNMP Notification Destination

Information About Backing Up and Restoring Data

About Backing Up the Database

About Cleaning Up the Database Backup Files

About Archiving the Database Backup Files and Other External Files

Requirements for the SSH/rsync Archiving Method

Restrictions for the FTP Archiving Method

Requirements for the FTP Archiving Method

About Archiving Recordings

About Restoring the Data

Configuring Backups

Sending E-Mail Blasts

About File Cleanup

Cleaning Up Voice Files


Maintaining the Cisco Unified MeetingPlace Express System


Revised: October 18, 2006, OL-11374-01

Topics in this section include:

Information About SNMP

Information About Backing Up and Restoring Data

Sending E-Mail Blasts

About File Cleanup

The content in this chapter applies only to the Cisco Unified MeetingPlace Express system and not to the Cisco Unified MeetingPlace Express VT system.

Information About SNMP

You can use SNMP to monitor the Cisco Unified MeetingPlace Express application the same way you manage other devices on the network.


Note SNMP monitoring of the hardware server is not supported.


By using an SNMP management tool and configuring it appropriately, you can obtain network status information and gain access to the Cisco Unified MeetingPlace Express system.


Note There are two versions of SNMP: version 1 is the older version and version 2 is the newer version. Cisco Unified MeetingPlace Express works with both versions.


The Cisco Unified MeetingPlace Express SNMP feature requires the non-standard Management Information Bases (MIBs) that are listed in the "Requirements for SNMP" section.


Caution Cisco Unified MeetingPlace Express does not support SNMP without the Cisco non-standard MIBs loaded onto your SNMP monitoring package.

Once the non-standard MIBs are in place, the SNMP feature supports all standard MIB II queries and a set of Cisco Unified MeetingPlace Express MIB traps. The MIB II queries include information such as the Cisco Unified MeetingPlace Express server name, location, and contact name, plus various statistics regarding the network interface.

The Cisco Unified MeetingPlace Express system uses traps to report certain events. Table 15-1 describes the conditions that generate Cisco Unified MeetingPlace Express traps.

Table 15-1 Cisco Unified MeetingPlace Express SNMP Traps 

This Alarm
Is Generated Whenever

Server startup

The server restarts or crashes (cold start).

Major software alarm

A major software failure occurs.

Minor software alarm

A minor software failure occurs.


Each major and minor software notification includes an integer alarm code that indicates which software module and server reported the alarm.


Note Normally, each alarm instance generates a separate notification. In some cases, however, one specific incident could trigger multiple types of alarms.


Topics in this section include:

Requirements for SNMP

Displaying SNMP Community Strings

Adding an SNMP Community String

Editing an SNMP Community String

Deleting an SNMP Community String

Displaying SNMP Notification Destinations

Adding an SNMP Notification Destination

Editing an SNMP Notification Destination

Deleting an SNMP Notification Destination

Requirements for SNMP

To support SNMP, you must import these non-standard MIBs into your network management server or SNMP monitoring package:

CISCO-CDP-MIB.my: Cisco Discovery Protocol

CISCO-SMI.my: Cisco Enterprise Structure of Management Information

CISCO-TC.my: Cisco MIB Textual Conventions

CISCO-VTP-MIB.my: Cisco Voice Technology Protocol MIB

CISCO-LATITUDE-MIB.my: Cisco Latitude MIB

You can download these MIB files from ftp://ftp-sj.cisco.com/pub/mibs/v2/.

Displaying SNMP Community Strings

A community string is the clear-text password you use to access the SNMP MIBs. Access privileges for the community string provide security by restricting the ability to alter the Cisco Unified MeetingPlace Express system.

Follow these steps to display all SNMP community strings, including the default community string for Cisco Unified MeetingPlace Express, which is called meetingplace-public.

Procedure


Step 1 Log in to Cisco Unified MeetingPlace Express.

Step 2 Click Administration at the top of the page.

Step 3 On the left side of the page:

a. Click Maintenance.

b. Click SNMP.

c. Click Community Strings.


Related Topics

About This Page: SNMP Community Strings, page C-134

Adding an SNMP Community String

Editing an SNMP Community String

Deleting an SNMP Community String

Information About SNMP

Adding an SNMP Community String

Follow these steps to add an SNMP community string to the Cisco Unified MeetingPlace Express database.

Procedure


Step 1 Log in to Cisco Unified MeetingPlace Express.

Step 2 Click Administration at the top of the page.

Step 3 On the left side of the page:

a. Click Maintenance.

b. Click SNMP.

c. Click Community Strings.

Step 4 On the SNMP Community Strings page, click Add New.

Step 5 On the Add SNMP Community String page, enter the name of the new community string in the Community String field.

Step 6 Choose one of the following:

Accept SNMP packets from any host

Accept SNMP packets only from these hosts

Step 7 If you choose Accept SNMP packets only from these hosts, enter the IP addresses from which you will accept packets in the Host IP address field and click Insert.

Step 8 Choose the level of access privileges for this community string from the drop-down list.

Step 9 Click Add New.

Step 10 Verify that the new community string appears in the SNMP Community Strings page.


Related Topics

About This Page: SNMP Community Strings, page C-134

About This Page: Edit SNMP Community String, page C-55

Displaying SNMP Community Strings

Editing an SNMP Community String

Deleting an SNMP Community String

Information About SNMP

Editing an SNMP Community String

Follow these steps to edit an existing SNMP community string.

Procedure


Step 1 Log in to Cisco Unified MeetingPlace Express.

Step 2 Click Administration at the top of the page.

Step 3 On the left side of the page:

a. Click Maintenance.

b. Click SNMP.

c. Click Community Strings.

Cisco Unified MeetingPlace Express displays all SNMP community strings on the SNMP Community Strings page.

Step 4 To edit a community string, click its underlined name.

Step 5 Change any of the values in the fields, which are described in the "Fields on the Edit SNMP Community String Page" section on page C-55.

Step 6 Click Save.


Related Topics

About This Page: SNMP Community Strings, page C-134

About This Page: Edit SNMP Community String, page C-55

Displaying SNMP Community Strings

Adding an SNMP Community String

Deleting an SNMP Community String

Information About SNMP

Deleting an SNMP Community String

Follow these steps to delete an existing SNMP community string.


Note You cannot delete the default community string for Cisco Unified MeetingPlace Express, which is called meetingplace-public.


Procedure


Step 1 Log in to Cisco Unified MeetingPlace Express.

Step 2 Click Administration at the top of the page.

Step 3 On the left side of the page:

a. Click Maintenance.

b. Click SNMP.

c. Click Community Strings.

Cisco Unified MeetingPlace Express displays all SNMP community strings on the SNMP Community Strings page.

Step 4 Do one of the following:

Check the check box in the same row as the community string that you want to delete. You can select multiple community strings.

To delete every community string, click the check box at the top of the column, next to the Community string name header. All check boxes that are not grayed out are checked.

Step 5 Click Delete Selected.

Step 6 When the confirmation pop-up window appears, click OK.

Step 7 Verify that any community strings that you deleted do not appear on the SNMP Community Strings page.


Related Topics

About This Page: SNMP Community Strings, page C-134

Displaying SNMP Community Strings

Adding an SNMP Community String

Editing an SNMP Community String

Information About SNMP

Displaying SNMP Notification Destinations

The system sends a message to the IP address specified in the notification destination whenever a trap or inform condition occurs. A trap reports certain events while an inform condition allows one network management application to send trap information to another.

Follow these steps to display all SNMP notification destinations.

Procedure


Step 1 Log in to Cisco Unified MeetingPlace Express.

Step 2 Click Administration at the top of the page.

Step 3 On the left side of the page:

a. Click Maintenance.

b. Click SNMP.

c. Click Notification Destinations.

Cisco Unified MeetingPlace Express displays all SNMP notification destinations on the SNMP Notification Destinations page.


Related Topics

About This Page: SNMP Notification Destinations, page C-136

Adding an SNMP Notification Destination

Editing an SNMP Notification Destination

Deleting an SNMP Notification Destination

Information About SNMP

Adding an SNMP Notification Destination

Follow these steps to add an SNMP notification destination to the Cisco Unified MeetingPlace Express database.

Procedure


Step 1 Log in to Cisco Unified MeetingPlace Express.

Step 2 Click Administration at the top of the page.

Step 3 On the left side of the page:

a. Click Maintenance.

b. Click SNMP.

c. Click Notification Destinations.

Step 4 On the SNMP Notification Destinations page, click Add New.

Step 5 Enter or change the values in the fields on the Add SNMP Notification Destination page.

Step 6 Click Add New.

Step 7 Verify that the new notification destination appears on the SNMP Notification Destination page.


Related Topics

Fields on the Add SNMP Notification Destination Page, page C-8

Displaying SNMP Notification Destinations

Editing an SNMP Notification Destination

Deleting an SNMP Notification Destination

Information About SNMP

Editing an SNMP Notification Destination

Follow these steps to edit an existing SNMP notification destination:

Procedure


Step 1 Log in to Cisco Unified MeetingPlace Express.

Step 2 Click Administration at the top of the page.

Step 3 On the left side of the page:

a. Click Maintenance.

b. Click SNMP.

c. Click Notification Destinations.

Step 4 On the SNMP Notification Destinations page, click the underlined IP address of the notification destination that you want to edit.

Step 5 Enter or change the values in the fields on the Edit SNMP Notification Destination page.

Step 6 Click Save.

Step 7 Verify that the notification destination contains the updated information on the SNMP Notification Destinations page.


Related Topics

Fields on the Edit SNMP Notification Destination Page, page C-57

Displaying SNMP Notification Destinations

Adding an SNMP Notification Destination

Deleting an SNMP Notification Destination

Information About SNMP

Deleting an SNMP Notification Destination

Follow these steps to delete an SNMP notification destination.

Procedure


Step 1 Log in to Cisco Unified MeetingPlace Express.

Step 2 Click Administration at the top of the page.

Step 3 On the left side of the page:

a. Click Maintenance.

b. Click SNMP.

c. Click Notification Destinations.

Step 4 On the SNMP Notification Destinations page, do one of the following:

To delete one notification destination, check the check box in the same row as the notification destination. You may select multiple notification destinations.

To delete every notification destination, check the check box at the top of the column, next to the Destination IP address header. All check boxes are checked.

Step 5 Click Delete Selected.

Step 6 When the confirmation pop-up window appears, click OK.

Step 7 Verify that any notification destinations that you deleted do not appear on the SNMP Notification Destinations page.


Related Topics

About This Page: SNMP Notification Destinations, page C-136

Displaying SNMP Notification Destinations

Adding an SNMP Notification Destination

Editing an SNMP Notification Destination

Information About SNMP

Information About Backing Up and Restoring Data

The Cisco Unified MeetingPlace Express backup and restore functions ensure that the system can recover with minimal data loss in case of a database or system failure or corruption. Topics in this section include:

About Backing Up the Database

About Cleaning Up the Database Backup Files

About Archiving the Database Backup Files and Other External Files

About Restoring the Data

Configuring Backups

About Backing Up the Database

There are three types of database backups:

L0 (Level 0) backup. This is the most common database backup. This is a complete backup of the database, both physical and logical, and it is sufficient to restore data from it.

L1 (Level 1) backup. The L1 backup is an incremental backup. It contains a backup of all the data that has been changed since the last L0 backup. It takes much less disk space than an L0 backup; however, it cannot be used for a full restore. If the system fails, you must use both the L0 and L1 backup files to restore data.

L2 (Level 2) backup. The L2 backup is incremental to the L1 backup, so it needs both the L0 and the L1 backups to restore data.

Cisco Unified MeetingPlace Express uses a combination of L0, L1, and L2 backups and uses an Informix command called ontape for the backup mechanism.

The database backup file is physically located on the system disk, which is the same physical device on which the rest of the Cisco Unified MeetingPlace Express system exists. The system disk can contain up to three automatically-created L0 backups: the current L0, plus the previous one or two L0 backups. The L1 and L2 backups are also kept there. All the older backups are removed from the system disk during the cleanup process.


Caution Use caution if you manually modify the backup files on the local disk or in the archive location. For successful data restoration, the three levels of backup files must be present in the correct order. For example, if the correct L0 and L2 backup files are present while the appropriate L1 backup file is missing, then the data cannot be restored.

You can enable or disable an automatic backup. If the automatic backup is enabled, an L0 backup happens twice a week, every Monday and Thursday at 11:00PM, local server time. The L1 backup is run each day at 1:00AM, local server time, while the L2 backups are done daily at 4:00AM, 8:00AM, 12:00PM, 4:00PM, and 8:00PM, local server time. The schedule is stored in the crontab file.


Note Advanced system administrators can change the frequency of the automatic backups by editing the crontab file. Be careful when modifying the cron schedule, which determines the order of the backups.


If automatic backup is disabled, then make sure that you run only one backup at a time. For information about manual backups, see the Troubleshooting Guide for Cisco Unified MeetingPlace Express.

The automatic backup process also incorporates archiving (if enabled) and cleanup. This ensures that if there is a database corruption or disk failure, in the worst case, less than four hours of data is lost.

Related Topics

Information About Backing Up and Restoring Data

Configuring Backups

About This Page: Configure Backup, page C-34

About Cleaning Up the Database Backup Files

The cleanup process occurs before every scheduled backup in the crontab file. During the cleanup process, the following files are deleted:

Backup files older than seven days.

Unusable files, such as L1 and L2 backup files that are older than the oldest remaining L0 backup file.


Note If you disable automatic backups, the cleanup process continues to run as scheduled in the crontab file. Therefore, if you want to keep backup files that are older than seven days, then you must archive them.


Related Topics

Information About Backing Up and Restoring Data

About Archiving the Database Backup Files and Other External Files

Configuring Backups

About This Page: Configure Backup, page C-34

About Archiving the Database Backup Files and Other External Files

Archiving is the process of storing database backup files and other critical files to a remote system over the network. Archiving makes a remote copy of all the backup files and the required external files, such as voice recordings. If a newly archived file has the same name as an existing archived file, the new file overwrites the old file.


Note Backup files and archives do not include backup configuration settings, SNMP configuration settings, SMTP configuration settings, and the custom logo or graphic.


Maintaining the archive and maintaining the remote system used for storing the archive is the responsibility of the system administrator.

Automatic archiving can be enabled or disabled. When enabled, it is initiated by and happens after the automatic database backup.

Related Topics

Requirements for the SSH/rsync Archiving Method

Restrictions for the FTP Archiving Method

Requirements for the FTP Archiving Method

About Archiving Recordings

Information About Backing Up and Restoring Data

Configuring Backups

About This Page: Configure Backup, page C-34

Requirements for the SSH/rsync Archiving Method

The remote server to which you archive files must support rsync and SSH connections. For example:

To archive to a UNIX or Linux server, SSH service and rsync must be enabled on that server. Both SSH service and rsync are included in most UNIX and Linux distributions.

To archive to a Windows-based server, both an SSH server and an rsync utility must be installed on that server.

Related Topics

About Archiving the Database Backup Files and Other External Files

Restrictions for the FTP Archiving Method

The FTP archiving method does not use a secure connection to transfer files to the remote server. We recommend that you use the secure SSH/rsync archiving method instead of the FTP archiving method, if possible.

The FTP archiving method enables the Cisco Unified MeetingPlace Express server to transfer backup files and other critical files to the remote server; FTP clients cannot transfer files to the Cisco Unified MeetingPlace Express server.

Related Topics

About Archiving the Database Backup Files and Other External Files

Requirements for the FTP Archiving Method

Requirements for the FTP Archiving Method

Make sure that the remote host login credentials provide the permissions required to create new directories within in the directory specified in the Pathname location of archive field.

For example, if you enter "pub" in the Pathname location of archive field, then the following directories are automatically created when the archiving script runs:

pub/compressed_backup

pub/licenses

pub/custom

Related Topics

About Archiving the Database Backup Files and Other External Files

Restrictions for the FTP Archiving Method

About Archiving Recordings

As external files, meeting recordings and voice recordings of user names are not included in the L0, L1, or L2 backup files. Nevertheless, meeting recordings are archived and can be restored on your system.

End users may also download meeting recordings, rename them, and save them on their PCs. For instructions on downloading meeting recordings, see the User Guide for Cisco Unified MeetingPlace Express.

Related Topics

About Restoring the Data

About Archiving the Database Backup Files and Other External Files

Information About Backing Up and Restoring Data

About Restoring the Data

Restoring the data recreates 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 Unified 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.

Related Topics

Information About Backing Up and Restoring Data

Configuring Backups

About This Page: Configure Backup, page C-34

Configuring Backups

This section describes how to configure the parameters for the automatic backups that the system performs. For information about manually backing up, archiving, or restoring data, see the Troubleshooting Guide for Cisco Unified MeetingPlace Express.

Before You Begin

If you plan to enable archiving, read these sections:

Requirements for the SSH/rsync Archiving Method

Restrictions for the FTP Archiving Method

Requirements for the FTP Archiving Method

Procedure


Step 1 Log in to Cisco Unified MeetingPlace Express.

Step 2 Click Administration at the top of the page.

Step 3 On the left side of the page:

a. Click Maintenance.

b. Click Configure Backup.

Step 4 Configure the fields on the Configure Backup page.

Step 5 Do one of the following:

To save these values without running the backup program, click Save.

To save these values and run the backup process, click Save and Run Backup.

To save these values and run the archive process, click Save and Run Archiving.


Related Topics

Fields on the Configure Backup Page, page C-34

Information About Backing Up and Restoring Data

Sending E-Mail Blasts

This topic describes how to send an e-mail blast, which is an e-mail message that is sent to either a pre-defined user group or to all end users.

Procedure


Step 1 Log in to Cisco Unified MeetingPlace Express.

Step 2 Click Administration at the top of the page.

Step 3 On the left side of the page:

a. Click Maintenance.

b. Click E-Mail Blast.

Step 4 Enter or change the values in the fields on the E-Mail Blast page.

Step 5 Click Send.


Related Topics

Fields on the E-Mail Blast Page, page C-60

Information About E-Mail Notification Templates and Language Property Files, page 14-2

About File Cleanup

Use the File Cleanup feature to delete directories that contain voice files, such as meeting recordings and recorded user names, for end users who have been removed from your Cisco Unified MeetingPlace Express database.


Note Because of the large amount of voice storage available in the Cisco Unified MeetingPlace Express system, this feature is rarely used. Perform a file cleanup only if your system runs low on voice storage; for example, if you have problems recording meetings or user names or if the prompt reports that voice storage is full.


Related Topics

Cleaning Up Voice Files

Cleaning Up Voice Files

Follow this procedure to clean up unused voice files in your Cisco Unified MeetingPlace Express database.

Procedure


Step 1 Log in to Cisco Unified MeetingPlace Express.

Step 2 Click Administration at the top of the page.

Step 3 On the left side of the page:

a. Click Maintenance.

b. Click File Cleanup.

Step 4 On the File Cleanup page, click Execute to start the file cleanup process.


Related Topics

About This Page: File Cleanup, page C-68

About File Cleanup