File: dumpconf.8

package info (click to toggle)
s390-tools 2.16.0-2
  • links: PTS
  • area: main
  • in suites: bookworm
  • size: 8,344 kB
  • sloc: ansic: 132,159; sh: 9,751; cpp: 8,359; perl: 2,519; makefile: 2,000; asm: 1,022
file content (214 lines) | stat: -rw-r--r-- 4,181 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
.\" Copyright 2017 IBM Corp.
.\" s390-tools is free software; you can redistribute it and/or modify
.\" it under the terms of the MIT license. See LICENSE for details.
.\"
.TH DUMPCONF 8 "Sept 2011" "s390-tools"

.SH NAME
dumpconf \- Configure panic and PSW restart actions for Linux on System z

.SH SYNOPSIS
.br
\fBdumpconf\fR [start|stop|status]
.br
\fBdumpconf\fR [-h|-v]

.SH DESCRIPTION
\fBdumpconf\fR reads the /etc/sysconfig/dumpconf file
and establishes the action to be taken if a kernel panic occurs
or PSW restart is triggered.

The following keywords can be used in the dumpconf file:

.TP
\fB  - ON_PANIC:\fR
Shutdown action in case of a kernel panic or a PSW restart. Possible values
are 'dump', 'reipl', 'dump_reipl', 'stop' and 'vmcmd':
.br

dump: Trigger dump according to the configuration in /etc/sysconfig/dumpconf.
.br

reipl: Trigger re-IPL according to the configuration under /sys/firmware/reipl.
.br

dump_reipl: First trigger dump according to the configuration in
/etc/sysconfig/dumpconf, then trigger re-IPL according to the configuration
under /sys/firmware/reipl.
.br

stop: Stop Linux and enter disabled wait (default).
.br

vmcmd: Trigger CP command according to the 'VMCMD_X' configuration in
/etc/sysconfig/dumpconf.

.TP
\fB  - DUMP_TYPE:\fR
Type of dump device. Possible values are 'ccw', 'fcp' and 'nvme'.

.TP
\fB  - DEVICE:\fR
Device number of dump device.

.TP
\fB  - WWPN\fR
WWPN for SCSI dump device.

.TP
\fB  - LUN\fR
LUN for SCSI dump device.

.TP
\fB  - FID\fR
Function ID for NVMe dump device.

.TP
\fB  - NSID\fR
Namespace ID for NVMe dump device.

.TP
\fB  - BOOTPROG:\fR
Boot program selector.

.TP
\fB  - BR_LBA:\fR
Boot record logical block address.

.TP
\fB  - VMCMD_1, VMCMD_2 ... VMCMD_8:\fR
Up to eight CP commands, which are executed in case of a kernel panic
or PSW restart.

.TP
\fB - DELAY_MINUTES:\fR
Number of minutes the activation of dumpconf is to be delayed. If this keyword
is omitted, the default is zero, which means that
dumpconf activates immediately during system startup.
Specify a non-zero delay time only if you specified
shutdown action "reipl" or "dump_reipl".
These actions might cause a reboot loop
if the Linux kernel crashes persistently during (or shortly after) each reboot.

A non-zero delay time causes dumpconf to sleep in the background until the
delay time has expired. In this case messages are written to /var/log/messages.
By default (DELAY_MINUTES is omitted or zero) dumpconf runs in the foreground
and informational messages are written to sysout, while
error messages are written to syserr.

Example: If you specified DELAY_MINUTES=10 and
your Linux system crashes within 10 minutes after the reboot,
then dumpconf is not yet active and the default action (stop) is triggered.

.SH COMMANDS
.TP
\fBstart\fR
Enable configuration defined in /etc/sysconfig/dumpconf.

.TP
\fBstop\fR
Disable dump configuration.

.TP
\fBstatus\fR
Show current configuration.

.SH OPTIONS
.TP
\fB-h\fR or \fB--help\fR
Print usage information, then exit.

.TP
\fB-v\fR or \fB--version\fR
Print version information, then exit.

.SH PSW Restart
PSW Restart can be triggered by the operator under z/VM with the CP
command "#cp system restart" and under LPAR on the HMC with
"Recovery/PSW Restart".

.SH EXAMPLES:
The following are examples of the /etc/sysconfig/dumpconf file:
.br

#
.br
# Example configuration for a CCW dump device (DASD)
.br
#
.br
ON_PANIC=dump_reipl
.br
DUMP_TYPE=ccw
.br
DEVICE=0.0.1234
.br
DELAY_MINUTES=5
.br

#
.br
# Example configuration for an FCP dump device (SCSI Disk)
.br
#
.br
ON_PANIC=dump
.br
DUMP_TYPE=fcp
.br
DEVICE=0.0.2345
.br
WWPN=0x5005076303004712
.br
LUN=0x4713000000000000
.br
BOOTPROG=0
.br
BR_LBA=0
.br

#
.br
# Example configuration for an NVMe dump device (NVMe Disk)
.br
#
.br
ON_PANIC=dump
.br
DUMP_TYPE=nvme
.br
FID=0x0300
.br
NSID=0x0001
.br
BOOTPROG=0
.br
BR_LBA=0
.br

#
.br
# Example configuration for CP commands
.br
#
.br
ON_PANIC=vmcmd
.br
VMCMD_1="MESSAGE * Starting VMDUMP"
.br
VMCMD_2="VMDUMP"
.br
VMCMD_3="IPL 3456"

#
.br
# Example config for re-IPL
.br
#
.br
ON_PANIC=reipl
.br
DELAY_MINUTES=5

.SH SEE ALSO
Linux on System z: Using the Dump Tools