Jason_Fant
Joined 8 years ago
User Profile
User Widgets
Contributions
Re: Monitoring Cisco UCCX
Attached (hopefully attached) is a Zip with the datasources I use. Some were from LM Dev's and others I wrote. EDIT:::: Here's a link to download it since I can't attach ZIPs here. https://1drv.ms/u/s!Ak3nIowLj9hMhewrrVqpjGeyrnph_g?e=16ZKXc FYI, I use a system.category of "CiscoUCCX" for all my UCCX Devices to make sure they get these datasources applied. I don't have a propertysource that gets this information automatically and set that property. Use these at your own risk and tweak the thresholds to make it work in your environment. · Cisco_UCCX_AgentStats - This is supposed to show the AgentStats but sometimes doesn’t work. · Cisco_UCCX_Applications – This will get a list of applications installed on UCCX and let you know if they are enabled or not. · Cisco_UCCX_Campaigns – same as applications but pulls in Campaigns. · Cisco_UCCX_DBPurgeConfigurationStatus - Monitors last database purge status. · Cisco_UCCX_Processes – Monitors UCCX processes running. · Cisco_UCCX_Reporting_Engine_Stats – This one I’ve had issues trying to query. UCCX AXL interface throws some weird errors with SSL and issues with DNS names vs. IPs. · Cisco_UCCX_Service_Status – Monitors service status. · Cisco_UCCX_System_Stats – Monitors system stats and performance. · Default_UCCX_Properties – We use this to make sure the device is setup with all the right properties to make these other Datasources work correctly. It makes sure SSH creds are there and the UCCX logins for the AXL interface are there and work. We also use this to help us know that the creds we have WORK and if a password change happens, it alarms and lets us know so we can adjust monitoring and keep everything working. · UCCX_Backup_Status – This monitors the backup status using SSH creds. Tweak the thresholds is your jobs are not daily OR take more than 24 hours to run. · UCCX_Primary_Node – This monitors the Primary node status. We’ve had issues where primary node failed over and never failed back causing issues within the cluster.0Views0likes0CommentsRe: Monitoring Cisco UCCX
Hey guys, just saw your posts! I'm out sick but I would be happy to share what I've built out. Some of it was SNMP stuff and other datasources use the AXL interface to get status. I also use SSH stuff to help with checking backups. Let me get all that stuff together and see how I can share it to the community. Give me a week or so till I'm back in the office to get you that stuff. Thanks, Jason2Views0likes0CommentsRe: Cisco Call Manager Backup Status
I had a couple people on the forums here help me put this together so I can't take full credit for this! This is what I use to monitor Backup Status on the Publisher only. I want to make it run a little better but I haven't had time to make it better. You are more than welcomed to use it and see if it helps and tweak it to however you see fit...it's all XML, so copy and paste into notepad and save as "CUCM_Backup_Status-.xml" and then you can IMPORT it. Default threshold is for 24hours but can be adjusted per Publisher you monitor. There are 3 properties you need set on the device. for the system.categories property, you need "CUCMPublisher". I use that to help me identify which server is the publisher in the cluster.....I don't want backup status on any subscribers cause a failed backup job could create multiple alarms for 1 job failure. The other two are your ssh.user and .pass creds for CUCM CLI. -EDIT- Oh yea! I forgot to mention that it also checks to make sure a Backup Job is even setup! We've had issues where customers didn't know backup jobs weren't configured, so we monitor for that as well! ? -EDIT- Enjoy!!! ?34Views0likes0CommentsRe: Script EventSource to grab Traps?? Is it possible?
I too would like that ability. While the traps is somewhat functional, I'd like to be able to take the trap and write some scripting to replace some of the OIDs in the message of the trap to what their names actually are within the MIB. Something like this: Enterprise OID: 1.3.6.1.4.1.231.7.2.1.21.2.3 Message: 1.3.6.1.4.1.231.7.2.1.21.1.3.2: SYS1 1.3.6.1.4.1.231.7.2.1.3.1.1.1: 1 1.3.6.1.4.1.231.7.2.1.3.1.1.10: ADVISORY 1.3.6.1.4.1.231.7.2.1.3.1.1.11: -- 1.3.6.1.4.1.231.7.2.1.3.1.1.12: -- 1.3.6.1.4.1.231.7.2.1.3.1.1.13: -- 1.3.6.1.4.1.231.7.2.1.3.1.1.14: 1615802432 1.3.6.1.4.1.231.7.2.1.3.1.1.2: 0 1.3.6.1.4.1.231.7.2.1.3.1.1.3: 0 1.3.6.1.4.1.231.7.2.1.3.1.1.4: 2147481553 1.3.6.1.4.1.231.7.2.1.3.1.1.5: F4066 1.3.6.1.4.1.231.7.2.1.3.1.1.6: M4 1.3.6.1.4.1.231.7.2.1.3.1.1.7: NO ACT 1.3.6.1.4.1.231.7.2.1.3.1.1.8: BPA 1.3.6.1.4.1.231.7.2.1.3.1.1.9: CP enterpriseOid: 1.3.6.1.4.1.231.7.2.1.21.2.3 To this: Enterprise OID: 1.3.6.1.4.1.231.7.2.1.21.2.3 Message: hicomErrTrpMnemonic: SYS1 hicomErrorPabxId: 1 hicomErrorSubevent: ADVISORY hicomErrorCardRef: -- hicomErrorBoardVersion: -- hicomErrorFwType: -- hicomErrorTimDat: 1615802432 hicomErrorAlGroup: 0 hicomErrorAlSubId: 0 hicomErrorSerialNo: 2147481553 hicomErrorMsgId: F4066 hicomErrorPriority: M4 hicomErrorAction: NO ACT hicomErrorAbsMod: BPA hicomErrorEvent: CP enterpriseOid: 1.3.6.1.4.1.231.7.2.1.21.2.30Views1like0Comments