ZXWR RNC-BSC-SYS/GSM&UMTS&MW-3000-SCDMA-RNC-To solve Log server unavailable problem in RNC Product ZXWR RNC/GU-BSC/GU-SYS/GU Network Management Version VR3.09.30.06P02-B4.00.200n2 Equipment Hardware Version V3.09.30.06 Equipment Software Version V3.09.30.06 Board Hardware Version Board Software Version Incident Error Code Page Views 11 Author Parab Ulhas Dattaram Knowledge No. WHH20111213561648 Incident Description (Incident Phenomena) IN RNC there was alarm occurred as "Log server unavailable" and "control plane communication abnormal between board and its home module". Networking Environment Problem Cause Analysis Log Server process was stopped. Solution IN RNC there was alarm occurred as Log server unavailable and control plane communication abnormal between board and its home module.

Query SBCX board status in configuration management. It was showing in Error state.

Login Log Server through Main SBCX board using either internal IP or External IP Main Server IP: 97.146.10.69 Internal IP of Log server is 128.0.37.1

Check file LogPro_log.txt from path / home/zte/LogService/logfile/ using cat command [zte@rzsbcx10 logfile]$ cat LogPr_log.txt Following error was occurred at the time of log server went to error state.

Check the Log server processs : [zte@rzsbcx10 logfile]$ ps ef | grep zte Following processes were absent i . SysCtrlProc: system main control process ii . CommProc: communication process iii . LogProc: log process iv . FatProc: fault collection agent process Go to path : /home/zte/LogService/epld/2.6.9

Check the user and use the same user to load epld by using scriptepld_load [root@rzsbcx10 2.6.9]# ./epld_load Go to the path /home/zte/LogService/bin and execute startup script of log server.(Note:check owner of file before executing script as above) # cd /home/zte/LogService/bin # chmod 755 startsys # nohup ./startsys & Again check log server processes: Above figure shows SysCtrlProc, CommProc, LogProc, FatProc processes started. Checked the alarm in RNC. Alarm found disappeared.