Expand Management Programming Manual

EVENT MANAGEMENT
147: ZEXP-EVT-CSS-STATUS-PROBE-ERR
ZEXP-TKN-CLIP-STATUS corresponds to the value param3 in the text
message.
Event-Message Text
The following correspondences exist between values in the text
message and tokens in the event message.
Value Token
-------- --------------------
ldev ZEMS-TKN-LDEV
ccu ZEMS-TKN-CU
path ZEXP-TKN-CIU-PATH
param3 ZEXP-TKN-CLIP-STATUS
The value param4 in the text message is not meaningful for this
event, and thus there is no token in the event message that
corresponds to this value.
Probable Cause
The CSM received a status probe response from the CLIP indicating
that the CLIP is in the boot state instead of the run state,
either because it was powered off and then on again or because of
some internal software or hardware problem. The Communications
Access Process (CAP) attempts to download the CLIP again. If the
CAP cannot do so on the primary path, it attempts a download on
another path.
Recommended Action
Decode the CLIP status byte in ZEXP-TKN-CLIP-STATUS to determine
which error occurred. If the CLIP does not restart
automatically, try to restart it manually by using the LOAD LINE
command in SCF or the CONTROL LINE, LOAD command in CMI. If
the problem persists and if the CLIP status indicates a software
problem, take a CLIP dump. Note the CLIP status value and
contact your Tandem representative.
8-69