Cisco Systems OL-9351-01 Installed Packages, Installed Elements

C-2

User Guide for Cisco Unified Service Monitor

OL-9351-01

AppendixC Service Monitor Support for SNMP MIBs

System Application MIB Implementation

Installed Packages

Tabl e C-1 stores information for installed packages for Service Monitor and other applications in the

Cisco Unified Management Suite that support the system application MIB.

Installed Elements

For each entry in the installed packages table, Tabl e C-1, there can be many entries in the installed

element table, Tabl e C-2. The number of installed elements for a package correspond s to the number of

processes being monitored for that package.

Tabl e C-2 lists the contents of sysApplInstallElmtTable.

TableC-1 sysApplInstallPkgTable

MIB Row Entry Description from the MIB

Cisco Unified Communications

Management Suite Usage

sysApplInstallPkgIndex Part of the index for this table. An integer used

only for indexing purposes. Generally

monotonically increasing from 1 as new

applications are installed.

Running number for each application

registered with the SNMP subagent.

sysApplInstallPkgManufacturer The manufacturer of the software application

package.

Cisco Systems, Inc.

sysApplInstallPkgProductName The name assigned to the software application

package by the manufacturer.

Name provided when the application

was registered with the SNMP

subagent, such as Cisco Unified Service

Monitor 1.0.

Note Use this name to select an

application to watch.

sysApplInstallPkgVersion The version number assigned to the application

package by the manufacturer of the software.

Version number such as 1.0.2, where 1

is the major version, 0 is the minor

version, and 2 is the patch version or

incremental device update (IDU)

number.

sysApplInstallPkgSerialNumber The serial number of the software assigned by

the manufacturer.

“n/a”

sysApplInstallPkgDate The date and time this software application was

installed on the host.

—

sysApplInstallPkgLocation The complete pathname where the application

package is installed.

NMSROOT—Directory where Service

Monitor is installed. If you selected the

default directory during installation, it

is C:\Program~1\CSCOpx.

Contents

Main Page CONTENTS Page Page Page Preface Audience Conventions Product Documentation Related Documentation Obtaining Documentation Cisco.com Product Documentation DVD Ordering Documentation Documentation Feedback Cisco Product Security Overview Reporting Security Problems in Cisco Products Obtaining Technical Assistance Cisco Technical Support & Documentation Website Submitting a Service Request Definitions of Service Request Severity Obtaining Additional Publications and Information Page CHAPT ER Using Cisco Unified Service Monitor Getting Started with Service Monitor Starting Service Monitor 12 3 Setting Up Service Monitor Copying Image and Configuration Files to the TFTP Server Managing Cisco 1040s Understanding the Cisco 1040 Sensor Details Page Viewing Details for a Specific Cisco 1040 Registering Cisco 1040s to Service Monitors Understanding Automatic Registration and Configuration Files Configuring Service Monitors and Cisco 1040s when Multiple TFTP Servers Are in Use Adding a Cisco 1040 (Manual Registration) Page Editing the Configuration for a Specific Cisco 1040 Editing the Default Configuration (Automatic Registration) Understanding Cisco 1040 Failover to a Secondary or Tertiary Service Monitor Resetting a Cisco 1040 Setting the Time on Cisco 1040s Updating Image Files on Cisco 1040s Moving a Cisco 1040 Deleting a Cisco 1040 Using the Cisco 1040 Web Interface Viewing the Configuration File on the TFTP Server Archiving Cisco 1040 Call Metrics Generating a Cisco 1040 Unreachable Trap Page CHAPT ER Data Management and System Administration Managing Service Monitor Data Backing Up and Restoring the Service Monitor Database Starting a Database Backup Restoring the Database Changing the Password for the Service Monitor Database Managing Log Files Understanding Service Monitor Syslog Handling Maintaining the History Log File Managing Log Files and Enabling and Disabling Debugging Configuring Users (ACS and Non-ACS) Configuring Users Using Non-ACS Mode (CiscoWorks Local Login Module) Configuring Users Using ACS Mode Using Service Monitor in ACS Mode Modifying Roles and Privileges in Cisco Secure ACS Starting and Stopping Service Monitor Processes Using SNMP to Monitor Service Monitor Configuring Your System for SNMP Queries Determining the Status of Windows SNMP Service Installing and Uninstalling Windows SNMP Service Enabling and Disabling Windows SNMP Service Configuring Security for SNMP Queries Viewing the System Application MIB Log File Changing the Hostname on the Service Monitor Server Changing the Hostname, Rebooting the Server, and Regenerating the Certificate Page Reconfiguring Service Monitor after a Hostname Change Changing the IP Address on the Service Monitor Server Page A MIBs Used and SNMP Traps Generated Page B Licensing Licensing Overview Verifying Service Monitor License Status Licensing Scenarios Licensing Process Obtaining a PAK Obtaining a License File Registering a License File Licensing Reminders Evaluation Version: Before Expiry License Size Exceeded B-5 Page C Service Monitor Support for SNMP MIBs System Application MIB Implementation System Application Resource MIB Tables Installed Packages Installed Elements Package Status Information Element Status Information Status of Packages When They Ran Previously Status of Elements When They Ran Previously Scalar Variables Process Map C-8 Sample MIB Walk for System Application MIB C-9 C-10 C-11 Page D Configuring Service Monitor with Cisco Secure ACS Before You Begin: Integration Notes Page Configuring Service Monitor on Cisco Secure ACS Verifying the Service Monitor and Cisco Secure ACS Configuration Page INDEX A B C D E F H M N O P T U V W