Cisco Unified MeetingPlace Express, Release 2.x -- How to Work With SNMP

From DocWiki

Jump to: navigation, search

Main page: Cisco Unified MeetingPlace Express, Release 2.x


You can use SNMP to monitor the Cisco Unified MeetingPlace Express application the same way you manage other devices on the network. However, the system does not support SNMP monitoring of the hardware.


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. 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.


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: Cisco Unified MeetingPlace Express SNMP Traps describes the conditions that generate Cisco Unified MeetingPlace Express traps.


Contents

Table: 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. Normally, each alarm instance generates a separate notification. In some cases, however, one specific incident could trigger multiple types of alarms.


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 and Deleting an SNMP Community String

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


Procedure
  1. Log in to Cisco Unified MeetingPlace Express and click Administration.
  2. Click Maintenance > SNMP > Community Strings.
  3. To delete a community string, 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.
  1. Click Delete Selected.
  2. When the confirmation pop-up window appears, click OK.


Related Topics


Adding and Editing an SNMP Community String

Procedure
  1. Log in to Cisco Unified MeetingPlace Express and click Administration.
  2. Click Maintenance > SNMP > Community Strings.
  3. To add a new community string, click Add New. To edit a community string, click its underlined name.
  4. Enter or change values in the fields.
  5. Click Add New or Save.
  6. Using an SSH client, log in as the user called mpxadmin.
    Note: See the Configuration and Maintenance Guide for Cisco Unified MeetingPlace Express Release 2.x for complete information about logging in using SSH.
  7. Change to the root user by entering su and enter the root password.
  8. Restart the SNMP services for changes to take effect by typing /etc/init.d/mpx_snmp restart
Related Topics


Displaying and Deleting an SNMP Notification Destination

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.


Procedure
  1. Log in to Cisco Unified MeetingPlace Express and click Administration.
  2. Click Maintenance > SNMP > Notification Destinations.
  3. To delete a notification destination, 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.
  4. Click Delete Selected.
  5. When the confirmation pop-up window appears, click OK.


Related Topics


Adding and Editing an SNMP Notification Destination

Procedure
  1. Log in to Cisco Unified MeetingPlace Express and click Administration.
  2. Click Maintenance > SNMP > Notification Destinations.
  3. Click Add New or click the underlined IP address of the notification destination that you want to edit.
  4. Enter or change the values in the fields.
  5. Click Add New or Save.


Related Topics

Rating: 0.0/5 (0 votes cast)

Personal tools