You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-machines/workloads/sap/os-upgrade-hana-large-instance.md
+9-8Lines changed: 9 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,8 @@ This document describes the details on operating system upgrades on the HANA Lar
23
23
>[!NOTE]
24
24
>The OS upgrade is customers responsibility, Microsoft operations support can guide you to the key areas to watch out during the upgrade. You should consult your operating system vendor as well before you plan for an upgrade.
25
25
26
-
At the time, of the HLI unit provisioning, the Microsoft operations team install the operating system. Over the time, you are required to maintain the operating system (Example: Patching, tuning, upgrading etc.) on the HLI unit.
26
+
At the time, of the HLI unit provisioning, the Microsoft operations team install the operating system.
27
+
Over the time, you are required to maintain the operating system (Example: Patching, tuning, upgrading etc.) on the HLI unit.
27
28
28
29
Before you do major changes to the operating system (for example, Upgrade SP1 to SP2), you need to contact Microsoft Operations team by opening a support ticket to consult.
29
30
@@ -48,10 +49,10 @@ The following are the few common known issues during the upgrade:
48
49
49
50
## SAP HANA on Azure Large Instance (Type I) Recommended SLES Configuration
50
51
51
-
Customer operating system configuration can drift from the recommended settings over time due to patching, system upgrades, and changes made by customers. Additionally, Microsoft identifies updates needed for existing systems to ensure they are optimally configured for the best performance and resiliency. Below given description and instructions outline recommendations that address network performance, system stability, and optimal HANA performance.
52
+
Customer operating system configuration can drift from the recommended settings over time due to patching, system upgrades, and changes made by customers. Additionally, Microsoft identifies updates needed for existing systems to ensure they are optimally configured for the best performance and resiliency. Below given instructions outline recommendations that address network performance, system stability, and optimal HANA performance.
52
53
53
54
### Compatible enic/fnic driver versions
54
-
In order to have proper network performance and system stability, it is advised that customers maintain versions of the enic and fnic drives below. Servers are usually delivered to customers with these versions, however, in some cases versions can get rolled back to the default enic and fnic versions when OS/Kernel patching is performed.
55
+
In order to have proper network performance and system stability, it is advised that customers maintain versions of the enic and fnic drives below. Servers are delivered to customers with these versions, however, in some cases versions can get rolled back to the default enic and fnic versions when OS/Kernel patching is performed.
55
56
56
57
57
58
| OS Vendor | OS Package Version | eNIC Driver | fNIC Driver |
@@ -74,7 +75,7 @@ Customer operating system configuration can drift from the recommended settings
74
75
```
75
76
76
77
#### SUSE HLIs GRUB UPDATE FAILURE
77
-
SAP on Azure HANA Large Instances (Type I) can be in a non-bootable state when updated. The below procedure fixes this.
78
+
SAP on Azure HANA Large Instances (Type I) can be in a non-bootable state when updated. The below procedure fixes this issue.
78
79
##### Steps to perform
79
80
```
80
81
* Take backup of file /etc/default/grub_installdevice
@@ -92,8 +93,8 @@ device_mapper+=$device_id
92
93
sed -i '/\/disk\/by-uuid/c '"$device_mapper"'' /etc/default/grub_installdevice
93
94
```
94
95
95
-
#### Disable EDAC:
96
-
The Error Detection And Correction (EDAC) module helps in detecting and correcting memory errors. However, the underlying hardware for SAP HNA on Azure Large Instances (Type I) is already preforming the same function. Having the same feature enabled at the hardware and Operating system (OS) levels can cause conflicts and can lead to occasional, unplanned shutdowns of the server. Therefore, it is recommended to disable the module from the OS.
96
+
#### Disable EDAC (The Error Detection And Correction ):
97
+
The Error Detection And Correction (EDAC) module helps in detecting and correcting memory errors. However, the underlying hardware for SAP HNA on Azure Large Instances (Type I) is already performing the same function. Having the same feature enabled at the hardware and Operating system (OS) levels can cause conflicts and can lead to occasional, unplanned shutdowns of the server. Therefore, it is recommended to disable the module from the OS.
97
98
98
99
##### Steps to perform
99
100
```
@@ -108,14 +109,14 @@ A reboot is required to have this reflected. Module should not be listed in ‘l
108
109
```
109
110
110
111
#### Kernel parameters
111
-
Please make sure the correct setting for transparent_hugepage, numa_balancing, processor.max_cstate and intel_idle.max_cstate are applied.
112
+
Make sure the correct setting for transparent_hugepage, numa_balancing, processor.max_cstate, and intel_idle.max_cstate are applied.
112
113
```
113
114
* intel_idle.max_cstate =1
114
115
* processor.max_cstate=1
115
116
* transparent_hugepage=never
116
117
* numa_balancing=disable
117
118
```
118
-
Incorrect settings have created both performance and instability issues in the past. Please follow SAP’s recommendation in your next maintenance window at the latest. Please check all your SAP HANA instances on SLES and ensure the correct setting is applied.
119
+
Incorrect settings have created both performance and instability issues in the past. Follow SAP’s recommendation in your next maintenance window at the latest. Check all your SAP HANA instances on SLES and ensure the correct setting is applied.
0 commit comments