SWAN Concentrator and WAN Subsystem Troubleshooting Guide

Installing and Using the SWAN Tools
SWAN Concentrator and WAN Subsystem Troubleshooting Guide—426992-008
5-11
Dump Formats
•
A display of the task control block of each task running in the CLIP (both short and
long listings).
•
A memory dump of the required memory address along with the ASCII display and
configurable start address and size of memory to be printed.
From the QUEST2 output, you can:
•
Find out which task caused the exception.
•
Find out the error details of the exception.
•
Find out which offset within a SWAN software module caused the exception, and
therefore the exact line of source code which caused the exception, along with the
help of map files and list files.
•
Manually find the stack trace from the stack frame in the dump, along with the map
files and list files.
•
Find the status of various hardware components in SWAN 2 CLIP dumps.
Dump Formats
The CLIP dump has several formats. The SWAN CLIP dumps have a file format ID
from 1 to 4, and the SWAN 2 CLIP dumps have a file format ID equal to 101.
The 101-format of SWAN 2 CLIP dumps contains new sections that are not present in
the SWAN CLIP dumps. The SWAN 2 dumps contain a header block followed by data.
These sections are new to SWAN 2 CLIP dumps:
•
LAN buffers (SK region)
•
DPRAM Registers
•
Page table
•
SK-Data
QUEST2 Interfaces
QUEST2 provides two interfaces:
•
Command line interface
•
User interactive interface
Command Line Interface
In the command line interface, the commands can be given at the TACL (NSK) prompt
or at the $ (UNIX) prompt as command line arguments. In the command line interface,
the dump file name must be specified in the command each time QUEST2 command is
issued. In the command line interface, all parameters must be preceded by a dash (-).