From e8e40f65711ce3b8226525647347e9eb4b5f321c Mon Sep 17 00:00:00 2001 From: Tao Liu Date: Dec 08 2021 00:59:31 +0000 Subject: fadump: improve fadump-howto.txt about remote dump target setup upstream: fedora related: bz2003832 conflict: none commit da6f381b081469fccf12110a398d03d1c0810b3f Author: Hari Bathini Date: Thu Feb 18 14:12:00 2021 +0530 fadump: improve fadump-howto.txt about remote dump target setup While fadump-howto.txt talks about what happens to network interface name on setting up a remote dump target in FADump mode, it doesn't explicitly specify the negative consequences of it. Make it explicit and provide a recommendation to overcome the same. Signed-off-by: Hari Bathini Acked-by: Kairui Song Signed-off-by: Tao Liu --- diff --git a/fadump-howto.txt b/fadump-howto.txt index 111586c..bc87644 100644 --- a/fadump-howto.txt +++ b/fadump-howto.txt @@ -224,12 +224,16 @@ Things to remember: dracut_args --add "network" 4) If FADump is configured to capture vmcore to a remote dump target using SSH - or NFS protocol, the network interface is renamed to kdump- - if is generic, for example, *eth#, or net#. This problem - occurs because the vmcore capture scripts in the initial RAM disk (initrd) - add the kdump- prefix to the network interface name to secure persistent - naming. As the same initrd is used for production kernel boot, the interface - name is changed for the production kernel too. + or NFS protocol, the corresponding network interface '' is + renamed to 'kdump-', if it is generic (like *eth# or net#). + It happens because vmcore capture scripts in the initial RAM disk (initrd) + add the 'kdump-' prefix to the network interface name to secure persistent + naming. And as capture kernel and production kernel use the same initrd in + case of FADump, the interface name is changed for the production kernel too. + This is likely to impact network configuration setup for production kernel. + So, it is recommended to use a non-generic name for a network interface, + before setting up FADump to capture vmcore to a remote dump target based on + that network interface, to avoid running into network configuration issues. Dump Triggering methods: