When I test syslog I first ensure that the syslog parameters are provisioned correctly under Enterprise Parameters. This is where you can set the logging level and syslog host.
Then, I go to the CLI of one of the UCM nodes and use the command:
utils snmp test
That will test SNMP traps but it will also generate syslog messages. It will actually send a syslog message at each logging level. Example:
Apr 15 14:41:27 142.100.64.12 39: : : 0: Apr 15 18:51:05.567 UTC : %CCM_CALLMANAGER-TESTALARMCATALOG-6-TestAlarmInformational: Testing INFORMATIONAL_ALARM App ID:Cisco CallManager Cluster ID: Node ID:iecucm02
Apr 15 14:41:28 142.100.64.12 40: : : 1: Apr 15 18:51:05.571 UTC : %CCM_CALLMANAGER-TESTALARMCATALOG-0-TestAlarmEmergency: Testing EMERGENCY_ALARM App ID:Cisco CallManager Cluster ID: Node ID:iecucm02
Apr 15 14:41:29 142.100.64.12 41: : 0: Apr 15 18:51:05.567 UTC : %CCM_CALLMANAGER-TESTALARMCATALOG-6-TestAlarmInformational: Testing INFORMATIONAL_ALARM App ID:Cisco CallManager Cluster ID: Node ID:iecucm02
Apr 15 14:41:29 142.100.64.12 42: : : 2: Apr 15 18:51:05.575 UTC : %CCM_CALLMANAGER-TESTALARMCATALOG-1-TestAlarmAlert: Testing ALERT_ALARM App ID:Cisco CallManager Cluster ID: Node ID:iecucm02
Apr 15 14:41:30 142.100.64.12 43: : 1: Apr 15 18:51:05.574 UTC : %CCM_CALLMANAGER-TESTALARMCATALOG-0-TestAlarmEmergency: Testing EMERGENCY_ALARM App ID:Cisco CallManager Cluster ID: Node ID:iecucm02
Apr 15 14:41:31 142.100.64.12 44: : : 3: Apr 15 18:51:05.581 UTC : %CCM_CALLMANAGER-TESTALARMCATALOG-2-TestAlarmCritical: Testing CRITICAL_ALARM App ID:Cisco CallManager Cluster ID: Node ID:iecucm02
Apr 15 14:41:32 142.100.64.12 45: : 2: Apr 15 18:51:05.580 UTC : %CCM_CALLMANAGER-TESTALARMCATALOG-1-TestAlarmAlert: Testing ALERT_ALARM App ID:Cisco CallManager Cluster ID: Node ID:iecucm02
Apr 15 14:41:33 142.100.64.12 46: : 3: Apr 15 18:51:05.582 UTC : %CCM_CALLMANAGER-TESTALARMCATALOG-2-TestAlarmCritical: Testing CRITICAL_ALARM App ID:Cisco CallManager Cluster ID: Node ID:iecucm02
Apr 15 14:41:34 142.100.64.12 47: : : 5: Apr 15 18:51:05.583 UTC : %CCM_CALLMANAGER-TESTALARMCATALOG-5-TestAlarmNotice: Testing NOTICE_ALARM App ID:Cisco CallManager Cluster ID: Node ID:iecucm02
Apr 15 14:41:34 142.100.64.12 48: : : 6: Apr 15 18:51:05.583 UTC : %CCM_CALLMANAGER-TESTALARMCATALOG-4-TestAlarmWarning: Testing WARNING_ALARM App ID:Cisco CallManager Cluster ID: Node ID:iecucm02
Apr 15 14:41:34 142.100.64.12 49: : 5: Apr 15 18:51:05.583 UTC : %CCM_CALLMANAGER-TESTALARMCATALOG-5-TestAlarmNotice: Testing NOTICE_ALARM App ID:Cisco CallManager Cluster ID: Node ID:iecucm02
Apr 15 14:41:34 142.100.64.12 50: : : 7: Apr 15 18:51:05.583 UTC : %CCM_CALLMANAGER-TESTALARMCATALOG-3-TestAlarmError: Testing ERROR_ALARM App ID:Cisco CallManager Cluster ID: Node ID:iecucm02
Apr 15 14:41:34 142.100.64.12 51: : 6: Apr 15 18:51:05.583 UTC : %CCM_CALLMANAGER-TESTALARMCATALOG-4-TestAlarmWarning: Testing WARNING_ALARM App ID:Cisco CallManager Cluster ID: Node ID:iecucm02
Apr 15 14:41:34 142.100.64.12 52: : : 8: Apr 15 18:51:05.584 UTC : %CCM_CALLMANAGER-TESTALARMCATALOG-6-TestAlarmWindows: Testing INFORMATIONAL_ALARM App ID:Cisco CallManager Cluster ID: Node ID:iecucm02
Apr 15 14:41:34 142.100.64.12 53: : 7: Apr 15 18:51:05.584 UTC : %CCM_CALLMANAGER-TESTALARMCATALOG-3-TestAlarmError: Testing ERROR_ALARM App ID:Cisco CallManager Cluster ID: Node ID:iecucm02
Apr 15 14:41:34 142.100.64.12 54: : 8: Apr 15 18:51:05.584 UTC : %CCM_CALLMANAGER-TESTALARMCATALOG-6-TestAlarmWindows: Testing INFORMATIONAL_ALARM App ID:Cisco CallManager Cluster ID: Node ID:iecucm02
HTH
-Bill (@ucguerrilla)
