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
+29-32Lines changed: 29 additions & 32 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,85 +47,82 @@ 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 Large Instance (Type I) Recommended SLES Configuration
50
+
##SAP HANA Large Instance (Type I) Recommended SLES Configuration
51
51
52
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
-
## Compatible eNIC/fNIC driver versions
54
+
###Compatible eNIC/fNIC driver versions
55
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 |
## Commands for driver upgrade and to clean old rpm packages
65
+
###Commands for driver upgrade and to clean old rpm packages
66
66
```
67
-
* rpm -U driverpackage.rpm
68
-
* rpm -e olddriverpackage.rpm
67
+
rpm -U driverpackage.rpm
68
+
rpm -e olddriverpackage.rpm
69
69
```
70
70
71
-
*Commands to confirm:
71
+
####Commands to confirm:
72
72
```
73
-
* modinfo enic
74
-
* modinfo fnic
73
+
modinfo enic
74
+
modinfo fnic
75
75
```
76
76
77
-
##SUSE HLIs GRUB UPDATE FAILURE
77
+
### SuSE HLIs GRUB Update Failure
78
78
SAP on Azure HANA Large Instances (Type I) can be in a non-bootable state after upgrade. The below procedure fixes this issue.
79
-
### Execution Steps
79
+
####Execution Steps
80
80
81
81
82
-
* Execute multipath -ll command.
82
+
* Execute `multipath -ll` command.
83
83
* Get the LUN ID whose size is approximately 50G or use the command : `fdisk -l | grep mapper`
84
84
* Update `/etc/default/grub_installdevice` file with line `/dev/mapper/<LUN ID>`. Example: /dev/mapper/3600a09803830372f483f495242534a56
85
85
* Please note that LUN ID varies from server to server.
86
86
87
87
88
-
## Disable EDAC (The Error Detection And Correction):
88
+
###Disable EDAC (The Error Detection And Correction):
89
89
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.
90
90
91
-
### Execution Steps
92
-
91
+
#### Execution Steps
93
92
94
93
* Check if EDAC module is enabled. If an output is returned in below command, that means the module is enabled.
95
94
```
96
-
lsmod | grep -i edac
95
+
lsmod | grep -i edac
97
96
```
98
-
*Add the modules in `/etc/modprobe.d/blacklist.conf` file using any text editor.
97
+
*Blacklist the modules by appending the following lines to the file `/etc/modprobe.d/blacklist.conf`
99
98
```
100
-
#vim /etc/modprobe.d/blacklist.conf
101
-
blacklist sb_edac
102
-
blacklist edac_core
99
+
blacklist sb_edac
100
+
blacklist edac_core
103
101
```
104
102
A reboot is required to take changes in place. Execute `lsmod` command and verify the module is not present there in output.
105
103
106
104
107
-
## Kernel parameters
105
+
###Kernel parameters
108
106
Make sure the correct setting for `transparent_hugepage`, `numa_balancing`, `processor.max_cstate`, `ignore_ce` and `intel_idle.max_cstate` are applied.
109
107
110
108
```
111
-
* intel_idle.max_cstate =1
112
-
* processor.max_cstate=1
113
-
* transparent_hugepage=never
114
-
* numa_balancing=disable
115
-
* mce=ignore_ce
109
+
intel_idle.max_cstate =1
110
+
processor.max_cstate=1
111
+
transparent_hugepage=never
112
+
numa_balancing=disable
113
+
mce=ignore_ce
116
114
```
117
-
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 SUSE and ensure the correct setting is applied.
118
-
119
-
### Execution Steps
115
+
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 SuSE and ensure the correct setting is applied.
120
116
117
+
#### Execution Steps
121
118
122
119
* Add these parameters to the `GRB_CMDLINE_LINUX` line in the file `/etc/default/grub`
0 commit comments