|
| 1 | +--- |
| 2 | +title: Script to enable Kdump in SAP HANA (Large Instances)| Microsoft Docs |
| 3 | +description: Script to enable Kdump in SAP HANA (Large Instances) HLI Type I, HLI Type II |
| 4 | +services: virtual-machines-linux |
| 5 | +documentationcenter: |
| 6 | +author: prtyag |
| 7 | +manager: hrushib |
| 8 | +editor: |
| 9 | + |
| 10 | +ms.service: virtual-machines-linux |
| 11 | + |
| 12 | +ms.topic: article |
| 13 | +ms.tgt_pltfrm: vm-linux |
| 14 | +ms.workload: infrastructure |
| 15 | +ms.date: 03/30/2020 |
| 16 | +ms.author: prtyag |
| 17 | +ms.custom: H1Hack27Feb2017 |
| 18 | + |
| 19 | +--- |
| 20 | + |
| 21 | +# Enable Kdump service |
| 22 | + |
| 23 | +This document describes the details on how to enable Kdump service on Azure HANA Large |
| 24 | +Instance(**Type I and Type II**) |
| 25 | + |
| 26 | +## Supported SKUs |
| 27 | + |
| 28 | +| Hana Large Instance type | OS vendor | OS package version | SKU | |
| 29 | +|-----------------------------|--------------|-----------------------|-------------| |
| 30 | +| Type I | SuSE | SLES 12 SP3 | S224m | |
| 31 | +| Type I | SuSE | SLES 12 SP4 | S224m | |
| 32 | +| Type I | SuSE | SLES 12 SP2 | S72m | |
| 33 | +| Type I | SuSE | SLES 12 SP3 | S72m | |
| 34 | +| Type I | SuSE | SLES 12 SP2 | S96 | |
| 35 | +| Type I | SuSE | SLES 12 SP3 | S96 | |
| 36 | +| Type II | SuSE | SLES 12 SP3 | S384 | |
| 37 | +| Type II | SuSE | SLES 12 SP3 | S576m | |
| 38 | +| Type II | SuSE | SLES 12 SP3 | S384xm | |
| 39 | +| Type II | SuSE | SLES 12 SP4 | S384xm | |
| 40 | + |
| 41 | +## Prerequisites |
| 42 | + |
| 43 | +- Kdump service uses `/var/crash` directory to write dumps, make sure the partition corresponds to this directory has sufficient space to accommodate dumps. |
| 44 | + |
| 45 | +## Setup details |
| 46 | + |
| 47 | +- Script to enable Kdump can be found [here](https://github.com/Azure/sap-hana/blob/master/tools/enable-kdump.sh) |
| 48 | + |
| 49 | +- Run this script on HANA Large Instance using the below command |
| 50 | + |
| 51 | + > [!NOTE] |
| 52 | + > sudo privilege needed to run this command. |
| 53 | +
|
| 54 | + ```bash |
| 55 | + sudo bash enable-kdump.sh |
| 56 | + ``` |
| 57 | + |
| 58 | +- If the command outputs Kdump is successfully enabled, please reboot the system to apply the change, then the Kdump is successfully enabled. Reboot the system to apply changes. |
| 59 | + |
| 60 | +- If the command output is Failed to do certain operation, Exiting!!!!, then Kdump service is not enabled. Refer to section [Support issue](#support-issue). |
| 61 | + |
| 62 | +## Test Kdump |
| 63 | + |
| 64 | +> [!NOTE] |
| 65 | +> Below operation will trigger a kernel crash and system reboot. |
| 66 | + |
| 67 | +- Trigger a kernel crash |
| 68 | + |
| 69 | + ```bash |
| 70 | + echo 1 > /proc/sys/kernel/sysrq |
| 71 | + echo c > /proc/sysrq-trigger |
| 72 | + ``` |
| 73 | + |
| 74 | +- After the system reboots successfully, check the `/var/crash` directory for kernel crash logs. |
| 75 | + |
| 76 | +- If the `/var/crash` has directory with current date, then the Kdump is successfully enabled. |
| 77 | + |
| 78 | +## Support issue |
| 79 | + |
| 80 | +If the script fails with an error or Kdump isn't enabled, raise service request with Microsoft support team with following details. |
| 81 | +
|
| 82 | +* HLI subscription ID |
| 83 | +
|
| 84 | +* Server name |
| 85 | +
|
| 86 | +* OS vendor |
| 87 | +
|
| 88 | +* OS version |
| 89 | +
|
| 90 | +* Kernel version |
0 commit comments