SWAN Concentrator and WAN Subsystem Troubleshooting Guide

Troubleshooting Tips for the SWAN Concentrator
and the WAN Subsystem
SWAN Concentrator and WAN Subsystem Troubleshooting Guide—426992-008
6-3
CLIP Dump Detection and Recovery
CLIP Dump Detection and Recovery
When a task running on the CLIP faces an exception and cannot continue normal
execution, the CLIP initiates a complete dump of its memory to the host. After
completing the CLIP dump, the CLIP starts normal execution and the LINEs recover
automatically.
Considerations
•
A CLIP dump is initiated automatically when any task on the CLIP faces an
exception and the task cannot continue normal execution. This dump request from
the CLIP is unsolicited.
•
A CLIP dump can also be initiated manually using the WANDUMP utility; however,
this is not normally required.
•
The corresponding WANBoot process for that CLIP needs to be UP and the
SERVER state of the CLIP needs to be in a STARTED state for a CLIP dump to
occur.
•
WANBoot receives the CLIP dump and places it in the $SYSTEM.ZWANDUMP
subvolume.
•
In G06.07 and later RVUs, a BOOTP EMS message indicates that the dump has
been initiated.
•
A TRAPMUX EMS message with a specific trap number of 1245195 indicates the
cause of the dump.
•
When the dump is complete, an EMS message is displayed that the dump has
been received.
•
Normally, an automatically initiated CLIP dump is considered to be a defect in one
of the tasks in the CLIP and needs to be fixed. Contact your HP service provider
for resolution of this problem with this information:
°
The CLIP dump file from $SYSTEM.ZWANDUMP subvolume
°
The EMS messages during the time when the dump was collected
°
The SCF INFO ADAPTER, SUB ALL display
°
The SCF STATUS ADAPTER, SUB ALL display
°
VPROCs of WANMGR, ConMgr, WANBoot, and the CLIP firmware
°
Additional information as requested by your service provider