You will need first to check the SNMP OID’s with your systems (see the UPS tutorial ) and enable on CCM hosts the SNMP string and checks. All the checks that I have done for this tutorial are from the file CISCO-CCM-MIB.my
Step 1: check the SNMP service activation on you’re devices and activate-it if is disabled:
If you have access to the command line here’s how for CCM express edition you need to access the terminal and do:
· enable
· config terminal
· snmp-server community xxxxxx RO
· snmp-server community xxxxxx RW
· exit
· write memory
More details here: http://www.ciscosystems.com/en/US/docs/voice_ip_comm/cucme/mib/reference/guide/ccme_mib.html
For the CCM you will need to check the start of the SNMP service:
· Choose Start > Settings > Control Panel.
· Double-click Administrative Tools.
· Double-click Services.
· Right-click SNMP Service.
· From the toolbar, choose Start Service.
To configure the SNMP service go to Cisco Unified Serviceability:
· Click the SNMP menu and select the appropriate version of SNMP to your network (here we are going to use the version 1).
· Once there, select a server and search the configuration (yes, click the find button)
· Add a new SNMP community string by clicking the add new button.
· Complete the required fields (community string name, click accept SNMP packets from only these hosts – your Nagios sever – and set the community string to ReadOnly) and click ok.
More details here: http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/service/5_0_1/ccmsrva/sasrvact.html
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/service/5_0_1/ccmsrva/sasnmpv1.html
Now you should now have an active SNMP service on your machine (CCME or CCM).
Step 2. The declaration of the CCM hosts.
The default host configuration is:
define host{
use CCM-host
host_name CCM001
alias Cisco Call manager 6
address 192.168.1.1
}
Here the CCM-host is a template that can be declared as you wish. I have put all the hosts in the group Cisco-VoIP-callmangers so we will make the check with this target.
And now the service declaration:
###############################################################################
###############################################################################
#
# SERVICE DEFINITIONS
#
###############################################################################
###############################################################################
define service{
use CCM-service
hostgroup_name Cisco-VoIP-callmangers
service_description Rejected Phones
check_command check_snmp!-C snmp-server_read_community_string -o .1.3.6.1.4.1.9.9.156.1.5.7.0 -c 1 -l “Rejected Phones: “
icon_image phone.png
}
define service{
use CCM-service
hostgroup_name Cisco-VoIP-callmangers
service_description Registered Phones
check_command check_snmp!-C snmp-server_read_community_string -o .1.3.6.1.4.1.9.9.156.1.5.5.0 -l “Registered Phones: “
icon_image phone.png
}
define service{
use CCM-service
hostgroup_name Cisco-VoIP-callmangers
service_description UnRegistered Phones
check_command check_snmp!-C snmp-server_read_community_string -o .1.3.6.1.4.1.9.9.156.1.5.6.0 -w 50 -l “UnRegistered Phones: “
icon_image phone.png
}
define service{
use CCM-service
hostgroup_name Cisco-VoIP-callmangers
service_description Last event
check_command check_snmp!-C snmp-server_read_community_string -o .1.3.6.1.4.1.232.9.2.3.2.1.4.115
}
define service{
use CCM-service
hostgroup_name Cisco-VoIP-callmangers
service_description Up Time
check_command check_snmp!-o .1.3.6.1.2.1.1.3.0 -C snmp-server_read_community_string
icon_image time_server5.png
}
define service{
use generic-info
hostgroup_name Cisco-VoIP-callmangers
service_description CCM Version
check_command check_snmp!-C snmp-server_read_community_string -o .1.3.6.1.4.1.9.9.156.1.1.2.1.4.1 -l “CCM Version: “
}
define service{
use generic-info
hostgroup_name Cisco-VoIP-callmangers
service_description System description
check_command check_snmp!-o .1.3.6.1.2.1.1.1.0 -C snmp-server_read_community_string -l “System description: “
}
And here is the final view in Nagios:
For older models (older then version 6) this are the OID’s that I have found on the net (I don’t know if they are working but you can try and drop me a comment):
· for incoming calls .1.3.6.1.2.1.10.20.1.3.3.1.1.1
· for outgoing calls .1.3.6.1.2.1.10.20.1.3.3.1.3.1
· Registered phones: .1.3.6.1.4.1.9.9.156.1.5.5.0
· Unregistered Phones: .1.3.6.1.4.1.9.9.156.1.5.6.0
· Rejected Phones: .1.3.6.1.4.1.9.9.156.1.5.7.0
· Active Phones: .1.3.6.1.4.1.9.9.156.1.5.1
· Inactive Phones: .1.3.6.1.4.1.9.9.156.1.5.2
Mihai out.
Note: Copying this article to your website is strictly NOT allowed.
Thanks, I will try this.
Here a link to a list with CCM related OIDs:
http://support.ipmonitor.com/mibs/CISCO-CCM-MIB/oids.aspx
regards,
c
Great article. Thanks you!
Thanks, this worked for me after I started the snmp service on my server and created a V1 community string.
What’s the deal with ccmRegisteredPhones producing a zero? It’s doing that to me as well but I know I have ~100 phones registered.
Nevermind,
I changed my community string to snmp V2 and it started getting the correct numbers. Thanks again!