User Guide for Cisco Unified Service Monitor Cisco Unified Communications Management Suite Corporate Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
CONTENTS Audience Conventions vii vii Product Documentation viii Related Documentation viii Obtaining Documentation ix Cisco.
Contents Updating Image Files on Cisco 1040s 1-14 Moving a Cisco 1040 1-15 Deleting a Cisco 1040 1-15 Using the Cisco 1040 Web Interface 1-15 Viewing the Configuration File on the TFTP Server Archiving Cisco 1040 Call Metrics 1-16 Generating a Cisco 1040 Unreachable Trap CHAPTER 2 1-16 1-17 Data Management and System Administration 2-1 Managing Service Monitor Data 2-1 Backing Up and Restoring the Service Monitor Database 2-1 Starting a Database Backup 2-2 Restoring the Database 2-2 Changing the P
Contents APPENDIX A MIBs Used and SNMP Traps Generated APPENDIX B Licensing A-1 B-1 Licensing Overview B-1 Verifying Service Monitor License Status Licensing Scenarios B-2 Licensing Process B-3 Obtaining a PAK B-3 Obtaining a License File B-3 Registering a License File B-3 Licensing Reminders B-4 Evaluation Version: Before Expiry License Size Exceeded B-4 APPENDIX C B-1 B-4 Service Monitor Support for SNMP MIBs C-1 System Application MIB Implementation C-1 System Application Resource MIB Tab
Contents User Guide for Cisco Unified Service Monitor vi OL-9351-01
Preface This manual describes Cisco Unified Service Monitor (Service Monitor) and provides instructions for using and administering it. Audience The audience for this document includes: • IP communications and IP telephony management personnel. • Administrative personnel monitoring the overall service levels of their organization. • Network engineering personnel who evaluate and design IP network infrastructures.
Preface Product Documentation Caution Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data. Product Documentation Note We sometimes update the printed and electronic documentation after original publication. Therefore, you should also review the documentation on Cisco.com for any updates. Table 1 describes the product documentation that is available.
Preface Obtaining Documentation Table 2 Related Documentation Document Title Available Formats Release Notes for Cisco Unified Operations Manager 1.1 • Quick Start Guide for Cisco Unified Operations Manager 1.1 • Installation Guide for Cisco Unified Operations Manager • User Guide for Cisco Unified Operations Manager • Release Notes for CiscoWorks Common Services 3.0.3 (Includes CiscoView 6.1.
Preface Documentation Feedback Product Documentation DVD The Product Documentation DVD is a comprehensive library of technical product documentation on a portable medium. The DVD enables you to access multiple versions of installation, configuration, and command guides for Cisco hardware and software products. With the DVD, you have access to the same HTML documentation that is found on the Cisco website without being connected to the Internet. Certain products also have .
Preface Obtaining Technical Assistance A current list of security advisories, security notices, and security responses for Cisco products is available at this URL: http://www.cisco.com/go/psirt To see security advisories, security notices, and security responses as they are updated in real time, you can subscribe to the Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed. Information about how to subscribe to the PSIRT RSS feed is found at this URL: http://www.cisco.
Preface Obtaining Technical Assistance Cisco Technical Support & Documentation Website The Cisco Technical Support & Documentation website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, at this URL: http://www.cisco.com/techsupport Access to all tools on the Cisco Technical Support & Documentation website requires a Cisco.com user ID and password.
Preface Obtaining Additional Publications and Information Severity 1 (S1)—An existing network is down, or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation. Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operations are negatively affected by inadequate performance of Cisco products.
Preface Obtaining Additional Publications and Information • Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL: http://www.cisco.com/ipj • Networking products offered by Cisco Systems, as well as customer support services, can be obtained at this URL: http://www.cisco.com/en/US/products/index.
C H A P T E R 1 Using Cisco Unified Service Monitor The following topics are included: • Getting Started with Service Monitor, page 1-1 • Managing Cisco 1040s, page 1-5 • Archiving Cisco 1040 Call Metrics, page 1-16 • Generating a Cisco 1040 Unreachable Trap, page 1-17 Getting Started with Service Monitor Cisco Unified Service Monitor (Service Monitor), a member of the Cisco Unified Communications Management Suite, analyzes data that it receives from Cisco 1040 Sensors (Cisco 1040s) installed in y
Chapter 1 Using Cisco Unified Service Monitor Getting Started with Service Monitor Figure 1-1 Service Monitor Deployment 2 3 Cisco Unified Service Monitor Cisco Unified Operations Manager 1 IP 141960 IP Cisco 1040 1 Cisco 1040 monitors actual voice calls. 3 2 Service Monitor evaluates MOS values and sends SNMP traps when a threshold is violated. Service Monitor also sends an SNMP trap when a Cisco 1040 is unreachable. — — Operations Manager presents alert information.
Chapter 1 Using Cisco Unified Service Monitor Getting Started with Service Monitor Setting Up Service Monitor Step 1 From the Service Monitor home page, select Setup. The Setup page appears. Step 2 Update data described in the following table. GUI Element Description/Action Auto Registration radio buttons Select one of the following: • Enable—As a Cisco 1040 joins the network, it automatically registers with a Service Monitor using information provided in the default configuration file.
Chapter 1 Using Cisco Unified Service Monitor Getting Started with Service Monitor GUI Element Description/Action Trap Forwarding Parameters SNMP Community String Enter the SNMP community string for the trap receivers. Default is public. Trap Receiver n and Port fields Enter up to 4 trap receivers: (where n is a number from • Trap Receiver n—Enter the IP address or DNS name of a server.
Chapter 1 Using Cisco Unified Service Monitor Managing Cisco 1040s The image file directory path and TFTP server IP address are displayed on the Setup page; see Setting Up Service Monitor, page 1-3. Note • If you have configured multiple instances of Service Monitor to use the same TFTP server, and automatic registration is enabled, all Cisco 1040s register to the same primary Service Monitor.
Chapter 1 Using Cisco Unified Service Monitor Managing Cisco 1040s Understanding the Cisco 1040 Sensor Details Page Step 1 From the Service Monitor home page, select Cisco 1040 Sensor Management. The Cisco 1040 Sensor Details page displays information listed in the following table. GUI Element Description/Action Exports data from the Cisco 1040 Sensor Details page to a CSV or PDF file. See Exporting Data to a CSV or PDF File, page 1-6.
Chapter 1 Using Cisco Unified Service Monitor Managing Cisco 1040s Step 1 Select one radio button: CSV (comma-separated values file) or PDF. Step 2 Browse to the location where you want to store the file and click OK. Viewing Details for a Specific Cisco 1040 The Cisco 1040 Sensor Detail dialog box opens, displaying the Cisco 1040 Sensor Information table described here. Field Description/Action Exports data from the Cisco Information table to a CSV or PDF file.
Chapter 1 Using Cisco Unified Service Monitor Managing Cisco 1040s Field Description/Action Image File Name Name of the image file installed on the Cisco 1040. Note If there is a more recent image file available on the TFTP server, you must edit the configuration file for the Cisco 1040, specifying the filename for the more recent image, you must copy the updated configuration file to the TFTP server, and you must reset the Cisco 1040.
Chapter 1 Using Cisco Unified Service Monitor Managing Cisco 1040s configuration file to the TFTP server. See Copying Image and Configuration Files to the TFTP Server, page 1-4. Thereafter, every time that you reset the Cisco 1040, it uses QOV.CNF to register to a Service Monitor. There can be only one default configuration file on the TFTP server. The default configuration file specifies the primary Service Monitor.
Chapter 1 Using Cisco Unified Service Monitor Managing Cisco 1040s GUI Element Description/Action Cisco 1040 Sensor ID Accept the default initial letter and enter a 3-digit number. A Cisco 1040 Sensor ID consists of a letter and a 3-digit number, for example: A100. Note Image Filename If you enter an existing Cisco 1040 Sensor ID, Service Monitor displays an error message; in this case, you should enter a different 3-digit number. Enter the binary image filename.
Chapter 1 Using Cisco Unified Service Monitor Managing Cisco 1040s Editing the Configuration for a Specific Cisco 1040 Note Do not edit a Cisco 1040 configuration file using a text editor. Edit a Cisco 1040 configuration file using this procedure only. This procedure updates the configuration file for a Cisco 1040. After you edit the configuration file, you must copy it to the TFTP server and reset the Cisco 1040. Step 1 From the Service Monitor home page, select Cisco 1040 Sensor Management.
Chapter 1 Using Cisco Unified Service Monitor Managing Cisco 1040s Step 4 Click OK. Step 5 Copy the configuration file from the image file directory on the server where Service Monitor is installed to the TFTP server. When you plug the Cisco 1040 in and when you reset it, it will load this configuration file. Note The image file directory path and the TFTP server address are displayed on the Setup page; Setting Up Service Monitor, page 1-3.
Chapter 1 Using Cisco Unified Service Monitor Managing Cisco 1040s Note The image file directory path and the TFTP server address are displayed on the Setup page; Setting Up Service Monitor, page 1-3.) Understanding Cisco 1040 Failover to a Secondary or Tertiary Service Monitor This topic explains how a Cisco 1040 determines that a primary Service Monitor is unreachable and how the Cisco 1040 fails over to a secondary or tertiary Service Monitor.
Chapter 1 Using Cisco Unified Service Monitor Managing Cisco 1040s Setting the Time on Cisco 1040s Note Make sure that Windows Time service is properly configured and running on the server where Service Monitor is installed. This procedure takes the current time from the server where Service Monitor is installed and uses it to set the time on each Cisco 1040 that you select. Step 1 From the Service Monitor home page, select Cisco 1040 Sensor Management.
Chapter 1 Using Cisco Unified Service Monitor Managing Cisco 1040s Note Step 3 The image filename format is SvcMon_.img. For example, SvcMonAA2_24.img. Modify the configuration for each Cisco 1040, entering the new image filename; see Editing the Configuration for a Specific Cisco 1040, page 1-11. Moving a Cisco 1040 Step 1 (Optional.
Chapter 1 Using Cisco Unified Service Monitor Archiving Cisco 1040 Call Metrics • MAC Address—Cisco 1040 MAC address. • Time stamp—Current time on the Cisco 1040. • Status—Status of the Cisco 1040; one of the following: – operational—Cisco 1040 is receiving RTP streams, analyzing data, and sending data to Service Monitor. – not communicating with receiver—The Service Monitor is unreachable.
Chapter 1 Using Cisco Unified Service Monitor Generating a Cisco 1040 Unreachable Trap You can use the data for further analysis or you can turn archiving off. (Service Monitor does not send the archived data to other applications.) Table 1-1 lists the format for call metrics data files.
Chapter 1 Using Cisco Unified Service Monitor Generating a Cisco 1040 Unreachable Trap User Guide for Cisco Unified Service Monitor 1-18 OL-9351-01
C H A P T E R 2 Data Management and System Administration This section contains the following topics: • Managing Service Monitor Data, page 2-1 • Managing Log Files, page 2-3 • Configuring Users (ACS and Non-ACS), page 2-5 • Starting and Stopping Service Monitor Processes, page 2-8 • Using SNMP to Monitor Service Monitor, page 2-8 • Changing the Hostname on the Service Monitor Server, page 2-10 • Changing the IP Address on the Service Monitor Server, page 2-13 Managing Service Monitor Data C
Chapter 2 Data Management and System Administration Managing Service Monitor Data Starting a Database Backup Use this procedure to perform an immediate backup or a scheduled backup of the Service Monitor database. Step 1 Click the CiscoWorks link in the upper righthand corner of the Service Monitor home page. A new window opens. Step 2 In the Common Services pane, select Server > Admin > Backup, click Help, and follow the instructions.
Chapter 2 Data Management and System Administration Managing Log Files Table 2-1 Service Monitor Backup Directory Structure (continued) Option Description Usage Notes directory What is being stored Suite applications (if applicable). filename Specific file Files include database (.db). that has been For Service Monitor, the following file is listed directly under backed up generationNumber/suite: qovr.
Chapter 2 Data Management and System Administration Managing Log Files Maintaining the History Log File The history log file, ServiceMonitorHistory.log, contains records of Cisco 1040 events such as Cisco 1040 reset, configuration update, and errors. The history log file accumulates records and grows in size. If the file becomes too large, you should rename it to enable Service Monitor to start a fresh history log file. Note Service Monitor does not back up the history log file.
Chapter 2 Data Management and System Administration Configuring Users (ACS and Non-ACS) Table 2-2 lists Service Monitor log files by function or module. If you request assistance, the Technical Assistance Center (TAC) might ask you to send them some of these log files. Table 2-2 Service Monitor Log Files by Module Function/Module Log Files Data Handler DataHandler.log DataHandler_stdout.log DataHandler_sterr.log dhError.log LicenseCheck.log ServiceMonitorHistory.log tftpmanager.log trapgen.
Chapter 2 Data Management and System Administration Configuring Users (ACS and Non-ACS) Step 1 Click the CiscoWorks link in the upper righthand corner of the Service Monitor home page. A new window opens. Step 2 Select Common Services > Server > Reports > Permission Report > Generate Report. Step 3 Scroll down until you find Cisco Unified Service Monitor.
Chapter 2 Data Management and System Administration Configuring Users (ACS and Non-ACS) By default, the CiscoWorks Local login module authentication scheme has five roles in the ACS mode. They are listed here from least privileged to most privileged: Help Desk User with this role has the privileges to access network status information from the persisted data. User does not have the privilege to contact any device or schedule a job that will reach the network.
Chapter 2 Data Management and System Administration Starting and Stopping Service Monitor Processes Starting and Stopping Service Monitor Processes To start and stop Service Monitor processes, select the CiscoWorks link from the upper righthand corner of the Service Monitor home page, select Common Services > Server > Admin > Processes, and click Help for instructions. Table 2-3 provides a complete list of Service Monitor-related processes.
Chapter 2 Data Management and System Administration Using SNMP to Monitor Service Monitor Determining the Status of Windows SNMP Service Windows SNMP service is a Windows component that you can add or remove when you want to. To enable SNMP queries against the MIB that Service Monitor supports, SNMP service must be installed and enabled. You can verify the status of Windows SNMP service as follows. Step 1 Open the Windows administrative tool Services window.
Chapter 2 Data Management and System Administration Changing the Hostname on the Service Monitor Server Note To start SNMP service after you enable it, right-click SNMP Service and select Start. Configuring Security for SNMP Queries To improve security, the SNMP set operation is not allowed on any object ID (OID). You should also modify the credentials for SNMP service to not use a default or well-known community string. Note You do not need to restart SNMP service to modify credentials for it.
Chapter 2 Data Management and System Administration Changing the Hostname on the Service Monitor Server Step 1 Change the hostname on the server as follows: a. Stop the daemon manager by entering the following command: net stop crmdmgtd Step 2 b. Change the hostname at My Computer > Properties > Computer Name > Change. c. Prevent the daemon manager service from restarting after reboot.
Chapter 2 Data Management and System Administration Changing the Hostname on the Service Monitor Server perl dbpasswd.pl dsn=cmf npwd=newpassword where newpassword is the new password. Remember this password. You will need it to complete Step 9. Note Step 9 To ensure that devices added before you changed the hostname are properly classified in Device Center, enter the following command: dbisqlc -c "uid=cmfDBA;pwd=dbpassword;eng=cmfEng;dsn=cmf;dbf=NMSROOT\databases\cmf\cmf.
Chapter 2 Data Management and System Administration Changing the IP Address on the Service Monitor Server Step 3 Reset the Cisco 1040s. See Resetting a Cisco 1040, page 1-13. Step 4 If Service Monitor is configured to send traps to Operations Manager: • If Operations Manager is installed on the same server as Service Monitor, set up Service Monitor to send traps to the new hostname or IP address. See Setting Up Service Monitor, page 1-3.
Chapter 2 Data Management and System Administration Changing the IP Address on the Service Monitor Server User Guide for Cisco Unified Service Monitor 2-14 OL-9351-01
A P P E N D I X A MIBs Used and SNMP Traps Generated MIBS Used Service Monitor uses the CISCO-SYSLOG-MIB to generate SNMP traps. SNMP Traps Generated Cisco Unified Service Monitor (Service Monitor) generates the following traps: • MOS violation • Cisco 1040 unreachable Trap details are provided as name-value pairs in clogHistMsgText field of the clogMessageGenerated notification. Table A-1 lists details of the MOS violation SNMP trap.
Appendix A Table A-1 MIBs Used and SNMP Traps Generated MOS Violation Trap Details (continued) TAG Description Value F Primary cause of call degradation J: Jitter P: Packet Loss G Actual packet loss in the previous minute H Actual jitter in msec in the previous minute Table A-2 lists details of the Cisco 1040 unreachable SNMP trap.
A P P E N D I X B Licensing This appendix provides licensing information for Cisco Unified Service Monitor (Service Monitor). It contains the following sections: • Licensing Overview, page B-1 • Licensing Reminders, page B-4 Licensing Overview Licensing ensures that you possess a licensed copy of Service Monitor and enables you to increase the number—up to 50—of Cisco 1040s that Service Monitor supports.
Appendix B Licensing Licensing Overview Column Description Name Abbreviated product name—For Service Monitor, this is SM. Version Product version—A.b.c, where A is the major version number, b is the minor version number, and c is the service pack number. For example, SM 1.1.0 indicates version 1.1 without service packs. Size Limit—Number of Cisco 1040s that Service Monitor supports. Note Status Service Monitor supports a maximum of 50 Cisco 1040s.
Appendix B Licensing Licensing Overview Licensing Process For information on when it is appropriate to use this process, see Licensing Scenarios, page B-2. To license Service Monitor, do the following: 1. Obtain a Product Authorization Key (PAK)—You need a PAK, along with the MAC address of the server where you will install Service Monitor, to obtain a license file. See Obtaining a PAK, page B-3. 2.
Appendix B Licensing Licensing Reminders Note Step 2 Note If you copy a folder that contains the license file to the Service Monitor server, be sure to provide read permission for casuser on the folder as well as on the license file. Enter the license file location: a. Click the CiscoWorks link from the upper righthand corner of the Service Monitor home page. b. Select Common Services > Server > Admin > Licensing. For more information, click Help.
Appendix B Licensing Licensing Reminders is:10 07-Feb-2006|12:55:08.570|ERROR|LicenseCheck|Thread-3|Purchase incremental License to support more Cisco 1040 sensors 07-Feb-2006|12:55:08.570|ERROR|LicenseCheck|Thread-3|Auto registration disabled until space available 07-Feb-2006|12:55:08.617|ERROR|LicenseCheck|Thread-3|Due to lack of sufficient license will drop sensor:MacAddress:001120FFCF5E Id:A111 IPAddress:172.20.4.72 PrimaryReceiver:171.69.69.
Appendix B Licensing Licensing Reminders User Guide for Cisco Unified Service Monitor B-6 OL-9351-01
A P P E N D I X C Service Monitor Support for SNMP MIBs Service Monitor implements the system application MIB using SNMP v2 and supplies an an SNMP subagent. You can use simple SNMP queries to monitor the health of applications in the Cisco Unified Communications Management suite that supports the MIBs. For information about configuring your system to use SNMP to manage Service Monitor and other Cisco Unified applications, see Using SNMP to Monitor Service Monitor, page 2-8.
Appendix C Service Monitor Support for SNMP MIBs System Application MIB Implementation Installed Packages Table 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. Table C-1 sysApplInstallPkgTable Cisco Unified Communications Management Suite Usage MIB Row Entry Description from the MIB sysApplInstallPkgIndex Part of the index for this table.
Appendix C Service Monitor Support for SNMP MIBs System Application MIB Implementation Table C-2 sysApplInstallElmtTable MIB Row Entry Description from the MIB Cisco Unified Communications Management Suite Usage sysApplInstallPkgIndex Part of the index for this table. This value identifies the installed software package for the application of which this process is a part. Value from sysApplInstallPkgTable, Table C-1. sysApplInstallElmtIndex Unique number across the applications. Running number.
Appendix C Service Monitor Support for SNMP MIBs System Application MIB Implementation Table C-3 sysApplRunTable MIB Row Entry Description from the MIB Cisco Unified Communications Management Suite Usage sysApplInstallPkgIndex Part of the index for this table. This value identifies the installed software package for the application of which this process is a part. Value from sysApplInstallPkgTable, Table C-1. sysApplRunIndex Running number. Part of the index for this table.
Appendix C Service Monitor Support for SNMP MIBs System Application MIB Implementation Table C-4 sysApplElmtRunTable (continued) Cisco Unified Communications Management Suite Usage MIB Row Entry Description from the MIB sysApplElmtRunInstallID Part of the index for this table. The value of this object Value from is the same value as sysApplInstallElmtIndex for the sysApplInstallElmtTable, application element of which this entry represents a Table C-2. running instance.
Appendix C Service Monitor Support for SNMP MIBs System Application MIB Implementation Table C-6 sysApplElmtPastRunTable MIB Row Entry Description from the MIB sysApplElmtPastRunInvocID Part of the index for this table. Identifies the invocation of an application of which this process is a part. sysApplElmtPastRunIndex Part of the index for this table. A unique value for each process running on the host. sysApplElmtPastRunInstallID Part of the index for this table.
Appendix C Service Monitor Support for SNMP MIBs System Application MIB Implementation Process Map The sysApplMapTable contains one entry for each process currently running on the system. Table C-8 provides the index mapping from a process identifier to the invoked application, installed element, and installed application package. Table C-8 sysApplMapTable MIB Row Entry Description from the MIB sysApplElmtRunIndex Process identification number.
Appendix C Service Monitor Support for SNMP MIBs System Application MIB Implementation Sample MIB Walk for System Application MIB This example shows abridged output from a MIB walk of the SYS-APPL-MIB on a system where Cisco Unified Operations Manager and Service Monitor are installed. ***** SNMP QUERY STARTED ***** 1: sysApplInstallPkgManufacturer.1 (octet string) Copyright (c) 2004 by Cisco Systems, Inc. [43.6F.70.79.72.69.67.68.74.20.28.63.29.20.32.30.30.34.20.62.79.20.43.69.73.63.6F.20.5 3.79.73.74.
Appendix C Service Monitor Support for SNMP MIBs System Application MIB Implementation 33: sysApplInstallElmtName.2.21 (octet string) GPF [47.50.46 (hex)] 34: sysApplInstallElmtName.2.22 (octet string) INVDbEngine [49.4E.56.44.62.45.6E.67.69.6E.65 (hex)] 35: sysApplInstallElmtName.2.23 (octet string) IVR [49.56.52 (hex)] 36: sysApplInstallElmtName.2.24 (octet string) IPIUDbEngine [49.50.49.55.44.62.45.6E.67.69.6E.65 (hex)] 37: sysApplInstallElmtName.2.25 (octet string) IPSLAServer [49.50.53.4C.41.53.65.
Appendix C Service Monitor Support for SNMP MIBs System Application MIB Implementation 209: sysApplInstallElmtSizeHigh.1.1 (integer) 0 258: sysApplInstallElmtSizeLow.1.1 (integer) 0 307: sysApplInstallElmtRole.1.1 (integer) required(3) 356: sysApplInstallElmtModifyDate.1.1 (octet string) 2005-8-30,21:18:32 [07.D5.08.1E.15.12.20 (hex)] 357: sysApplInstallElmtModifyDate.1.2 (octet string) 2005-8-30,21:18:32 [07.D5.08.1E.15.12.20 (hex)] 405: sysApplInstallElmtCurSizeHigh.1.
Appendix C Service Monitor Support for SNMP MIBs System Application MIB Implementation 1111: sysApplElmtPastRunTimeEnded.0.0.1132 (octet string) 2005-9-27,15:43:42 [07.D5.09.1B.0F.2B.2A (hex)] 1158: sysApplElmtPastRunName.0.0.1132 (octet string) D:\PROGRA~1\CSCOpx\bin\cwjava.exe [44.3A.5C.50.52.4F.47.52.41.7E.31.5C.43.53.43.4F.70.78.5C.62.69.6E.5C.63.77.6A.61.76.6 1.2E.65.78.65 (hex)] 1206: sysApplElmtPastRunParameters.0.0.
Appendix C Service Monitor Support for SNMP MIBs System Application MIB Implementation User Guide for Cisco Unified Service Monitor C-12 OL-9351-01
A P P E N D I X D Configuring Service Monitor with Cisco Secure ACS This section describes how to configure Service Monitor with Cisco Secure ACS: • Before You Begin: Integration Notes, page D-1 • Configuring Service Monitor on Cisco Secure ACS, page D-3 • Verifying the Service Monitor and Cisco Secure ACS Configuration, page D-3 Before You Begin: Integration Notes Note You can integrate Service Monitor with Cisco Secure ACS only if they are installed on separate systems because Service Monitor mus
Appendix D Configuring Service Monitor with Cisco Secure ACS Before You Begin: Integration Notes For example: You have configured threeService Monitor servers with a Cisco Secure ACS, and you have created a role in Cisco Secure ACS for Service Monitor (say, SMSU). This role is shared by licensed versions of Service Monitor running on all three servers. • A user can have different access privileges for different Cisco Unified Communications Management Suite applications.
Appendix D Configuring Service Monitor with Cisco Secure ACS Configuring Service Monitor on Cisco Secure ACS Configuring Service Monitor on Cisco Secure ACS After you complete setting the CiscoWorks server to ACS mode with Cisco Secure ACS, perform the following tasks on Cisco Secure ACS: 1. Click Shared Profile Components to verify that the Cisco Unified Service Monitor (Service Monitor) application entry is present. 2.
Appendix D Configuring Service Monitor with Cisco Secure ACS Verifying the Service Monitor and Cisco Secure ACS Configuration – You should not be able to add Cisco 1040s for Service Monitor to manage, and you should not be able to delete them.
INDEX files A AAA mode 2-5, D-2 ACS mode backing up 2-1 data format 1-17 deleting authentication 2-5 users, configuring 2-7 significance of 2-7 adding SNMP, using to manage Service Monitor queries, configuring for 2-10 system application MIB log file, viewing archiving call metrics 1-3 1-9 default configuration 2-8 security, configuring for queries enabling 2-10 deleting 1-15 failover 1-13 vii 1-12 ID format audience for this document viii Cisco 1040 administering Service
Index using ACS mode log files 2-6 copying files to TFTP server 2-3 1-4 H D hostname, changing 2-10, 2-13 database password, changing 2-3, 2-11 debugging, enabling I 2-3 deleting image file Cisco 1040 1-15 copying to TFTP server files from TFTP server DHCP, configuring 1-15 1-5 disabling directory 1-3 updating 1-14 IP address, changing automatic registration 1-3 call metrics archiving 1-3 debugging 2-13 K 2-3 DNS, configuring documentation 1-4 1-5 keepalive 1-13 vii
Index manual M 1-9 license, Service Monitor managing log files 2-3 B-3 resetting MIBs Cisco 1040 system application, log file used by Service Monitor 2-10 1-13 roles, user A-1 Cisco Secure ACS, configuring MOS Cisco Secure ACS, modifying threshold, configuring violation trap 2-7 2-6 1-3 1-17, A-1 S security N certificate non-ACS mode SNMP queries authentication 2-5 users, configuring 2-10 Service Monitor CiscoWorks Local Login module 2-5 hostname, changing 2-5 IP address,
Index starting trap receivers Service Monitor configuring 1-2 Service Monitor processes Operations Manager 2-8 stopping Service Monitor processes port 2-8 syslog file 1-4 1-4 1-4 troubleshooting syslog messages 2-3 handling, during peak usage service 2-3 typographical conventions in this document 2-3 vii 2-3 system administration database password U 2-3 system application MIB sample MIB walk updating image files C-8 users system application MIB implementation resource MIB table
