Cisco Unified MeetingPlace

Document ID: 63670

Contents

Introduction
Prerequisites
      Requirements
      Components Used
      Conventions
Background Information
Disk Space Utilization Verification and Monitor
      Disk Space Utilization Verification
      Monitor
Configuration
NetPro Discussion Forums - Featured Conversations
Related Information

Introduction

This document describes how to verify current disk space utilization in the Cisco MeetingPlace Audio Server system. The document also describes how to monitor the space utilization with the Server Disk Capacity Monitoring utility.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

The information in this document is based on the MeetingPlace Server version 5.2 or later.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

For more information on document conventions, refer to the Cisco Technical Tips Conventions.

Background Information

The MeetingPlace Audio Server system utilizes disk space to perform various functions. Before you start a software upgrade, you should ensure that there is enough space on the MeetingPlace Audio Server system.

Server Disk Capacity Monitoring provides the MeetingPlace server with an ability to monitor disk usage. The utility raises alarms when disk usage reaches or exceeds a utilization threshold that you specify. This feature consists of two primary components: the monitor script and the configuration script. This document describes the behavior and user interfaces of these components.

Disk Space Utilization Verification and Monitor

The MeetingPlace Audio Server does not function properly if there is not enough disk space for task performance. The creation of logs during troubleshoot sessions is one cause of the lack of disk space. If you do not properly clean up the logs after each troubleshoot session, the logs accumulate and take up too much disk space. Another condition that can cause the issue is an unsuccessful upgrade.

Disk Space Utilization Verification

This procedure provides you with the current disk space utilization.

Complete these steps:

1. Connect to the Cisco MeetingPlace Audio Server system.

   Connect either with Telnet, with Secure Shell Protocol (SSH), or locally.

2. For the user name, enter one of these default user names:

   • For version 5.3, enter admin.

   • For version 5.2, enter tech.

3. For the password, enter the default password.

   If you have changed the default password, use the new password.

4. To log in to the command-line interface (CLI) as a superuser, enter su.

   The privilege level changes to CSC.

   The Cisco MeetingPlace Audio Server system prompts you for another password.

5. For this password, enter the Password of the Day (POD).

   Contact Cisco Technical Support to get the POD.

   Note: For more information on how to contact Cisco Technical Support, refer to the Obtaining Technical Assistance section of the document Guide to Cisco Conferencing Documentation and Support.

   The csc$ prompt appears.

6. Enter df.

   This code appears:

   meetingplace:csc$ df
   
   Filesystem     BlkSize   Blocks   Used      Free      %
   /dev/sdncr.0a  16384     31999    25289     6710      79%
   /dev/sdncr.1c  16384     320000   73017     246983    22%
   /dev/sdncr.0b  16384     51200    15136     36064     29%
   /dev/sdncr.0f  16384     63999    20459     43540     31%
   /dev/sdncr.0g  16384     1452991  1360105   92886     93%
   /dev/sdncr.1g  16384     1452991  1360106   92885     93%

7. Check the values in the % column.

   For the file /dev/sdncr.0a, which is the system partition, the value must be less than 90 before you perform an upgrade. For the file /dev/sdncr.0b, which is the temporary space partition, the value must be less than 65 before you perform an upgrade. If the values are higher, contact Cisco Technical Support for help with a directory cleanup.

   Note: For more information on how to contact Cisco Technical Support, refer to the Obtaining Technical Assistance section of the document Guide to Cisco Conferencing Documentation and Support.

Monitor

The monitor script, chkdiskcap.sh, checks block and inode utilizations against thresholds that /lat/etc/diskcap.conf specifies. Utilization and threshold values are in percentages. If utilization meets or exceeds a threshold, a major alarm occurs and an entry inserts in the exlog. The log entry indicates:

• The check operation type that caused the alarm

  Note: The type is either block or inode.

• The file system

  Note: The file system is an index, with the diskcap.conf file as a basis.

• The actual utilization

• The threshold specification

The script runs once daily via crontab. The script also runs whenever you run the configuration script and save data. The run time, according to the configuration, is at a time that is reasonably close to normal business hours; however, there is enough of a time buffer to allow for the resolution of overutilization issues. Currently, the run time is 7:10 a.m. (0710) local time. When the configuration script runs for the first time, the configuration script creates the initial crontab entry. Thereafter, whenever the configuration script runs and saves data, the script recreates the crontab entry.

One alarm can occur for each file system when the file system exceeds the threshold. Also, one alarm can occur for each check operation type. So, on a system with threshold specifications for three file systems, up to six alarms can conceivably occur sequentially. The six alarms occur if all three file systems exceed their thresholds for both blocks and inodes.

Configuration

The configuration script configdiskcap is an interactive, menu-driven utility which allows you to select file systems for monitor and to specify threshold values. This section provides a sample configuration.

After you complete the configuration, if you have saved data, the chkdiskcap.sh script runs and there is a recreation of the crontab entry.

bigrock:tech$ configdiskcap

+++++++++++++++++++++++++++++++++++
Disk Capacity Monitor Configuration
+++++++++++++++++++++++++++++++++++

Capacity values are utilization percentage thresholds.
A major alarm will be raised if a threshold is exceeded. 

Select a file system threshold to modify when prompted. 

Values must be between 60 and 99; a capacity
of 0 disables checking for that file system. 

   CAP% FILESYSTEM
   ==== ==========
1) 90   /
2) 0    /lat/db
3) 0    /tmp
4) 0    /lat/fs.1
5) 0    /lat/fs.2 

Select an item to modify, s to save and exit,
or q to quit without saving: 3
enter new value for /tmp : 65 

   CAP% FILESYSTEM
   ==== ==========
1) 90   /
2) 0    /lat/db
3) 65   /tmp
4) 0    /lat/fs.1
5) 0    /lat/fs.2 

Select an item to modify, s to save and exit,
or q to quit without saving: s 

Saving changes...done; exiting.

NetPro Discussion Forums - Featured Conversations

Related Information

• Voice Technology Support
• Voice and Unified Communications Product Support
• Recommended Reading: Troubleshooting Cisco IP Telephony
• Technical Support & Documentation - Cisco Systems