4-8
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
Chapter 4 Simple Network Management Protocol
SNMP/R MIBs
For more information about MIBs and troubleshooting, refer to the following chapters:
• Chapter 7, “Cisco Management Information Base”
• Chapter 8, “Industry-Standard Management Information Base”
• Chapter 9, “Vendor-Specific Management Information Base”
SNMP/R MIBs
When SNMP/R binaries spike the CPU, collect the following logs and information for analysis:
• Note the processes that are experiencing high CPU usage.
• Check to see if any SNMP polling is occurring and get the polling interval of the application.
• Note the SNMP versions by using the show packages active snmp command.
• Execute the show process using-most cpu command and collect the output.
• Collect the Perfmon logs by executing the file get activelog /cm/log/ris/csv/ command.
• Collect the traces for SNMP Master Agent, and other binaries experiencing high CPU.
• Send the above information to Support for further troubleshooting.
When the SNMP Master Agent does not start, check to see if port 161 is open. If the port is open, collect
the SNMP Master Agent traces for further analysis.
When migrating from Windows to Linux Cisco Unified CM, the ccmH323DevRmtCM1InetAddress has
been defined as OctetString in Cisco Unified CM Release 5.x and later. So, the IP Address displays as
Hexadecimal instead of the dotted decimal format as displayed in Cisco Unified CM Release 4.x.
Comments to this Manuals