CPP II Health Status

Each Call Server has a health count (stat health or stat cpu in LD 135) depending on the hardware it see's. The total is therefore system dependent, though both cores should normally be equal. If a core has problems with hardware or network connectivity then it's health count will go down. If one core is "healthier" than the other a CPU switch over will occur, as the side with the highest health count must always be active. Each ELAN device has a count of 2. Two Signaling Servers are required for health monitoring to work.

Add up to get total Health for each side:

Core status:

STAT CPU in LD 135 gets the status and core numbers for both CPs. Possible responses are:

• ENBL - CP is running
• IDLE - CP is in standby
• DSBL - CP is disabled

If the status is DSBL, one of the following OOS reasons is printed:

• 0 - CP card local bus parity threshold exceeded
• 1 - CP card sanity timeout threshold exceeded
• 10 - Secondary CP is not accessible
• 16 - Secondary CP has a major fault

This command also prints out the results of the latest self-test, and the position of the MAINT/NORM switch.

In a Side-by-side configuration of Core/Net modules, Core/Net 1 is always on the left. Core/Net 0 is always on the right.

TTY Output Example:

STAT CPU in LD 135, issued from the active core/CPU. If not redundant, the standby CPU health count may be inaccurate. Below, the health count is the same for each CPU, so both cores see the same hardware and the system is presumed healthy.

>ld 135
CCED000
.stat cpu

cp 1 16 PASS -- ENBL

TRUE REDUNDANT
DISK STATE = REDUNDANT
HEALTH  = 24                               - health count
VERSION = Jul 16 2006, 15:34:02
 Side = 1, DRAM SIZE = 512 MBytes


cp 0 16 PASS -- STDBY

TRUE REDUNDANT
DISK STATE = REDUNDANT
HEALTH  = 24                               - health count
VERSION = Jul 16 2006, 15:34:02
 Side = 0, DRAM SIZE = 512 MBytes

See High Speed Pipe for more details on STAT CPU output, CPU Maintenance, and LD 135 commnads.

---