There is no info in kexec-kdump-howto.txt which explains how to
configure kdump in clustered environment to avoid being fenced off
while saving core.
add a help link in kexec-kdump-howto.txt so that somebody can get to
Signed-off-by: Arthur Zou <zzou(a)redhat.com>
kexec-kdump-howto.txt | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/kexec-kdump-howto.txt b/kexec-kdump-howto.txt
index 7ffeab9..8b6212e 100644
@@ -98,6 +98,10 @@ parameter, which is expected. You may be able to get by with less than
testing with only 64M has proven unreliable of late. On ia64, as much as 512M
may be required.
+If using kdump in cluster environment, please refer to kdump-in-cluster-
+environment.txt or https://access.redhat.com/site/articles/67570
to get more
+information to avoid being fenced off while saving core.
Now that you've got that reserved memory region set up, you want to turn on
the kdump init script: