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-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,9 +21,9 @@ ms.custom: H1Hack27Feb2017
21
21
This document describes the details on operating system upgrades on the HANA Large Instances.
22
22
23
23
>[!NOTE]
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.
24
+
>The OS upgrade is customer's 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
-
During HLI unit provisioning, the Microsoft operations team install the operating system.
26
+
During HLI unit provisioning, the Microsoft operations team installs the operating system.
27
27
Over the time, you are required to maintain the operating system (Example: Patching, tuning, upgrading etc.) on the HLI unit.
28
28
29
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.
@@ -47,12 +47,12 @@ The following are the few common known issues during the upgrade:
47
47
- On SKU Type II class SKU, the software foundation software (SFS) is removed after the OS upgrade. You need to reinstall the compatible SFS after the OS upgrade.
48
48
- Ethernet card drivers (ENIC and FNIC) rolled back to older version. You need to reinstall the compatible version of the drivers after the upgrade.
49
49
50
-
# SAP HANA on Azure Large Instance (Type I) Recommended SLES Configuration
50
+
# SAP HANA Large Instance (Type I) Recommended SLES Configuration
51
51
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
+
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. Following instructions outline recommendations that address network performance, system stability, and optimal HANA performance.
53
53
54
54
## Compatible enic/fnic driver versions
55
-
In order to have proper network performance and system stability, it is advised that customers maintain versions of the eNIC and fNIC drivers below. Servers are delivered to customers with compatible versions. However, in some cases versions can get rolled back to the default eNIC and fNIC driver versions when OS/Kernel patching is performed.
55
+
In order to have proper network performance and system stability, it is advised to ensure that the OS specific appropriate version of eNIC and fNIC drivers are installed as depicted in following compatibility table. Servers are delivered to customers with compatible versions. Note that, in some cases, during OS/Kernel patching, drivers can get rolled back to the default driver versions. Ensure that appropriate driver version is running post OS/Kernel patching operations.
56
56
57
57
58
58
| OS Vendor | OS Package Version | eNIC Driver | fNIC Driver |
@@ -76,7 +76,7 @@ Customer operating system configuration can drift from the recommended settings
76
76
77
77
## SUSE HLIs GRUB UPDATE FAILURE
78
78
SAP on Azure HANA Large Instances (Type I) can be in a non-bootable state when updated. The below procedure fixes this issue.
79
-
### Steps for Execution
79
+
### Execution Steps
80
80
```
81
81
82
82
* Execute multipath -ll command.
@@ -87,9 +87,9 @@ SAP on Azure HANA Large Instances (Type I) can be in a non-bootable state when u
87
87
```
88
88
89
89
## Disable EDAC (The Error Detection And Correction):
90
-
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.
90
+
The Error Detection And Correction (EDAC) module helps in detecting and correcting memory errors. However, the underlying hardware for SAP HANA 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.
91
91
92
-
### Steps for Execution
92
+
### Execution Steps
93
93
94
94
```
95
95
* Check if EDAC module is enabled. If an output is returned in below command, that means the module is enabled.
@@ -113,7 +113,7 @@ A reboot is required to take changes in place. Execute "lsmod" command and verif
113
113
```
114
114
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.
115
115
116
-
### Steps for Execution
116
+
### Execution Steps
117
117
118
118
```
119
119
* Add these parameters to the GRB_CMDLINE_LINUX line in the file /etc/default/grub
0 commit comments