NonStop Operations Guide for H-Series and J-Series RVUs

1 \CYCLONE (206) 363 200K ( 0, 287)
1 363 READY
2 \SNAX (118) 353 200K ( 5, 333)
1 353 READY
3 \TESS (194) 554 200K ( 8, 279)
1 554 READY
4 \TSII [phone]K ( 2, 265)
1 556 READY
5 \ESP (163) 365 200K ( 1, 274)
1 365 READY
6 \SVLDEV [phone]K ( 7, 265)
1 538 READY
.
.
.
27 \SIERRA (012) 183 10K ( 4, 290)
1 183 READY
28 \PRUNE (175) 677 200K ( 5, 334)
1 677 READY
29 \OPMAN (252) 276 790K ( 5, 294) NPT
1 276 READY
30 \SOCIAL [phone]K ( 8, 280)
1 165 READY
31 \NCCORP2 (080) 295 790K ( 8, 264)
1 295 READY
32 \CS8 (152) 323 -- -- -----
1 323 NOT READY (124)
33 \CORE (241) 324 -- -- -----
1 324 NOT READY (124)
34 \SUNTEC [phone]K ( 5, 293) NPT
1 367 READY
35 \CS8 (152) 368 -- -- -----
1 368 NOT READY (124)
Tracing a Communications Line
Use the SCF TRACE command to trace the operation of a communications line. The line continues
normal operation while being traced, but it passes all its message traffic to a trace procedure.
Tracing enables you to see the history of a communications line, including its internal processing.
You can display trace files by using the commands available in the PTrace program. For information
about PTrace, refer to the PTrace Reference Manual. For information about configuring a trace by
using the SCF TRACE command, refer to the configuration and management manual for the
communications subsystem you want to trace.
Recovery Operations for Communications Subsystems
Some general troubleshooting guidelines are:
• Monitor exception conditions generated by the HP manageability tools.
• Examine the contents of the event message log for the subsystem. For example, the WAN
subsystem or Kernel subsystem might have issued an event message that provides information
about the process failure. Event messages returned by the WAN subsystem and SWAN
concentrator are described in the WANMGR and TRAPMUX sections of the Operator Messages
Manual, respectively.
• HP provides a comprehensive library of troubleshooting guides for the communications
subsystems. Attempt to analyze the problems and restart the process or object using the
commands described in the appropriate manual listed in “Related Reading for Communications
Subsystems” (page 99). If you are unable to start a required process or object, contact your
service provider.
98 Communications Subsystems: Monitoring and Recovery