SWAN Concentrator and WAN Subsystem Troubleshooting Guide

Troubleshooting the SWAN Concentrator and WAN
Subsystem
SWAN Concentrator and WAN Subsystem Troubleshooting Guide—426992-008
1-3
What to Do if You Can't Solve a Problem
If you receive an error message, see Section 7, Error and Informational Messages
With Recovery Actions to help you diagnose and recover from the error.
What to Do if You Can't Solve a Problem
If you cannot solve a SWAN concentrator or WAN subsystem problem, contact the
Global Mission Critical Solution Center (GMCSC) for an analysis of the problem. For
more information about the GMCSC or how to contact them, see:
http://h20219.www2.hp.com/services/w1/en/always-on/servers-nonstop-support.html
In some cases, it might also be appropriate to trace a communications line and provide
trace information to the GMCSC.
Gathering Files for GMCSC Analysis
Before gathering files for analysis, you might want to contact the GMCSC to determine
the best procedure for analyzing the problem. If information needs to be gathered, the
following information can be useful for analysis:
•
A readme file that describes what you were doing at the time the error occurred
and just prior to that time. Include this information (as appropriate):
°
VPROC information for WANMgr, ConMgr, WANBoot, and the SWAN
communications line interface processor (CLIP) firmware.
°
Current version of the operating system, service processor (SP) firmware, and
related applications.
°
SCF INFO for $ZZWAN.* (include ADAPTER, SERVER, and PATH objects).
°
SCF STATUS for $ZZWAN.* (include ADAPTER, SERVER, and PATH objects).
°
EMS logs for the period when the problem occurred.
°
Associated TCP/IP configuration for the listed SWAN ADAPTERS.
°
Any CLIP dump file found in $SYSTEM.ZWANDUMP.
°
Any other information required by the GMCSC or Development for analysis.
Note. There is currently no officially released trace facility for the WAN subsystem processes
and objects.