CS1K Weekly Health Check
Check PBX core/server status:
- LD 135: stat cpu, stat health
- LD 117: stat ipmg, stat ss, stat serv
The following should be performed at least weekly!
1Log into the Call Server command line interface with username and password:
TTY 03 SCH MTC BUG 9:21 OVL111 IDLE 0 >logi admin PASS? xxxxxxxx WARNING: THE PROGRAMS AND DATA STORED ON THIS SYSTEM ARE LICENSED TO OR ARE THE PROPERTY OF NT/BNR AND ARE LAWFULLY AVAILABLE ONLY TO AUTHORIZED USERS FOR APPROVED PURPOSES. UNAUTHORIZED ACCESS TO ANY PROGRAM OR DATA ON SYSTEM IS NOT PERMITTED. THIS SYSTEM MAY BE MONITORED AT ANY TIME FOR OPERATIONAL REASONS. THEREFORE, IF YOU ARE NOT AN AUTHORIZED USER, DO NOT ATTEMPT TO LOGIN. OVL111 IDLE 0 . TTY #03 LOGGED IN admin 19:10 09/06/2019 >
2Having successfully logged in, go to load 135 by typing ld 135 and pressing enter.
Type the command: stat cpu and press enter (output below):
>ld 135 CCED000 .stat cpu cp 0 22 PASS -- ENBL ⇐ Call Processor 0 SYSTEM STATE = REDUNDANT DISK STATE = REDUNDANT HEALTH = 14 VERSION = Nov 16 2010, 14:42:29 Side = 0, DRAM SIZE = 1006 MBytes CP[0] located at IPMG [0 0 22] cp 1 22 PASS -- STDBY ⇐ Call Processor 1 SYSTEM STATE = REDUNDANT DISK STATE = REDUNDANT HEALTH = 14 VERSION = Nov 16 2010, 14:42:29 Side = 1, DRAM SIZE = 1006 MBytes CP[1] located at IPMG [0 1 22]
In the command output, look for the following fields:
- One CPU should be: PASS -- ENBL - this is your active core.
- On a HA system, the second CPU should be: PASS -- STDBY - this is your inactive core.
- For both core's, SYSTEM STATE & DISK STATE should be REDUNDANT.
- For both core's, HEALTH should be the same, eg: 14 - the value is system dependent.
3Next, still in load 135, type the command: stat health
.stat health Local (Side 0, Active, Redundant): Components without TIER 1 Health contribution: ================================================== cp 0 22:In Service ipb 0 22:In Service TIER 1 Health Count Breakdown: ===================================== sio8 0 22 1: 0002 sio8 0 22 2: 0002 fmd 0 22 1: 0008 eth 0 22 0: 0002 Local TIER 1 Health Total: 14 : Remote TIER 1 Health Total: 14 :
- Look for the field Local TIER 1 Health Total and ensure it is 14 (value for this system)
- Look for the field Remote TIER 1 Health Total and ensure it is 14 (value for this system)
Type 4 stars (****) to exit load 135
4Go to load 117 by typing ld 117 and press enter.
Type the command stat ipmg:
>ld 117 OAM000 => stat ipmg LAST REG LAST REG IPMG TYPE STATUS DATE TIME UPTIME 000 0 MGC REG 09/06/2018 08:57 395d,2h,2m 000 1 MGC REG 09/06/2018 08:57 395d,2h,2m 004 0 MGC REG 09/06/2018 08:57 395d,2h,2m 004 1 MGC REG 09/06/2018 08:57 395d,2h,2m 008 0 MGC REG 09/06/2018 08:57 395d,2h,2m 008 1 MGC REG 09/06/2018 08:57 395d,2h,2m :
Here you should notice all your media gateways, the exact number is specific to your system.
The REG DATE and uptimes should be similar, indicating no recent reboots or connection issues.
5Next, still in load 117, type the command: stat ss
=> stat ss NODE ELANIP LDR SRV PBXLINK HOSTNAME ID STATE 1610 10.10.10.15 YES Avaya CPDC LINK UP ss0.pbxbook.com APPS: LTPS VTRK IPCONF IPTONE IPMUS IPANN PBXLINK DATE: 09/06/2019 PBXLINK TIME: 19:15:10 : 1610 10.10.10.16 YES Avaya CPDC LINK UP ss1.pbxbook.com APPS: LTPS PBXLINK DATE: 09/06/2019 PBXLINK TIME: 19:15:10 :
For each server, look for the words LINK UP which indicates it is functioning (stat serv includes VGWs).
Exit a load by entering: end or ****
Always end the log in session with: logo
If all of this checks out then great! Your system is in good working order, if not, contact your next support tier.
Save your troubleshooting to a text file in Putty (or copy/paste) and attach it to your email to assist support.
Note: output from some commands above can be very long, these examples have been edited for clarity.