
Using
kdump
●
Starting
kdump
- Log on to the desired node and use the following command to start the
kdump
utility:
$
service kdump start
●
Stopping
kdump
- Log on to the desired node and use the following command to stop the
kdump
utility:
$
service kdump stop
●
Checking the status of
kdump
- Log on to the desired node and use the following command to check the
status of the
kdump
utility:
$
service kdump status
For more information, see the
kdump(8)
and
crash(8)
man pages.
4.14 Retrieve System Status Information Using the urika-check-
platform Command
Prerequisites
This procedure requires root access to the System Management Workstation (SMW).
About this task
The
urika-check-platform
command can be used to retrieve various pieces of information.
Procedure
1. Log on to the SMW as root.
2. Execute the
urika-check-platform
command, as shown in the following examples.
●
Various HSS checks, Rack controller, dANCs,
xtcli
status, and
xtcablecheck
using the
--hss
option:
#
urika-check-platform --hss
●
Get revision info of Rack Controller, iSCBs, dANCs, and compute nodes and HSS using the
--rev
option:
#
urika-check-platform --rev
If nodes are not listed then revision information is unavailable. Make
sure
/global/cray/mfg/self_update_fw/intel_fw_chk.sh
is installed properly on each node.
●
Check if Aries is routed:
#
urika-check-platform --aries
●
Test node connectivity using the
--testnodes
option. First perform the ping test. If the nodes can be
pinged, then ssh is attempted. If ssh succeeds then the Aries IP is resolved and displayed next to the
hostname with the subnet mask:
System Monitoring
S3016
103