@@ -25,15 +25,15 @@ Instance(**Type I and Type II**)
25
25
## Supported SKU
26
26
| Hana Large Instance Type | OS Vendor | OS Package Version | SKU |
27
27
| -----------------------------| --------------| -----------------------| -------------|
28
- | Type 2 | SuSE | SLES 12 SP3 | S384 |
29
- | Type 2 | SuSE | SLES 12 SP3 | S576m |
30
28
| Type 1 | SuSE | SLES 12 SP3 | S224m |
31
29
| Type 1 | SuSE | SLES 12 SP4 | S224m |
32
30
| Type 1 | SuSE | SLES 12 SP3 | S96 |
33
31
| Type 1 | SuSE | SLES 12 SP4 | S96 |
32
+ | Type 2 | SuSE | SLES 12 SP3 | S384 |
33
+ | Type 2 | SuSE | SLES 12 SP3 | S576m |
34
34
35
35
## Pre-requisites
36
- - Kdump service uses /var directory to write logs, make sure the partition correspond to this directory has sufficient
36
+ - Kdump service uses ` /var/crash ` directory to write logs, make sure the partition corresponds to this directory has sufficient
37
37
space to accommodate logs.
38
38
39
39
## Setup details
@@ -50,15 +50,15 @@ bash enable-kdump.sh
50
50
echo 1 > /proc/sys/kernel/sysrq
51
51
echo c > /proc/sysrq-trigger
52
52
```
53
- - After the system reboots successfully, check the ` /var/crash directory ` for kernel crash logs.
53
+ - After the system reboots successfully, check the ` /var/crash ` directory for kernel crash logs.
54
54
- If the ` /var/crash ` has directory with current date, then the Kdump is successfully enabled.
55
55
56
- ### Support issue
57
- In case, if the script fails with some error or Kdump isn't enabled. Raise a ticket with Microsoft Operations team by opening a support ticket.
56
+ ## Support issue
57
+ If the script fails with an error or Kdump isn't enabled, raise a ticket with Microsoft Operations team by opening a support ticket.
58
58
59
- Include in your ticket:
59
+ Include in ticket:
60
60
61
- * Your HLI subscription ID.
62
- * Your server name.
61
+ * HLI subscription ID.
62
+ * server name.
63
63
* OS name
64
64
* OS version
0 commit comments