CUCM - 전화기간 네트워크 발생시 확인

확인
1. 전화기 <-> CUCM 간 네트워크로 전화기가 떨어지고 붙은 Log를 확인하는 방법


방법
1. RTMT 확인
2. RTMT - SysLog Viewer - 전화기가 붙은 CUCM 선택 - Application Logs - AlternateSyslog 확인
==> 전화기가 붙었다가 떨어진 Log를 확인할 수 있음


Download
1. Trace & Log Central - Select System Services/Application - Cisco RIS Data Collector PerfMonLog
2. Trace & Log Central - Select System Services/Application - EventViewer-Application Log
3. Device 상태가 왜 떨어졌는지에 대한 Log를 확인할 수 있으며
Reason 코드를 확인하여 어떤 이유로 떨어졌는지 확인이 필요


코드에 대한 설명은 아래 URL에서 확인
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/err_msgs/8_x/ccmalarms861.html


https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/err_msgs/8_x/ccmalarms851.html

예) REASON=13
13 KeepAliveTimeout - A KeepAlive message was not received. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops, and packet corruption. It is also possible to get this error if the Unified CM node is experiencing high CPU usage. Verify that the device is powered up and operating, verify that there is network connectivity between the device and Unified CM, and verify the CPU utilization is in the safe range (you can monitor this via the CPU Pegging Alert in RTMT).


REASON=15
15 CallManagerRestart - A device restart was initiated from Unified CM Administration, either due to an explicit command from an administrator or due to a configuration change such as adding, deleting or changing a directory number associated with the device. No action is necessary; the device will re-register automatically.

등등 코드별 오류를 확인 가능 

PerfMonLog 같은 경우 CSV로 해당 시간동안 CPU / 전화기 상태 / Memory 등
시간별 CUCM 상태를 History로 보여주는 자료이며


어느시간때 전화기가 떨어졌는지 대략적인 내용을 확인 할 수 있다