Skip to content

Commit b482219

Browse files
authored
Update os-upgrade-hana-large-instance.md
1 parent 4b09260 commit b482219

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/virtual-machines/workloads/sap/os-upgrade-hana-large-instance.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ The following are the few common known issues during the upgrade:
5252
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.
5353

5454
### Compatible eNIC/fNIC driver versions
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.
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.
5656

5757

5858
| OS Vendor | OS Package Version | eNIC Driver | fNIC Driver |
@@ -80,7 +80,7 @@ SAP on Azure HANA Large Instances (Type I) can be in a non-bootable state after
8080

8181

8282
* Execute `multipath -ll` command.
83-
* Get the LUN ID whose size is approximately 50G or use the command : `fdisk -l | grep mapper`
83+
* Get the LUN ID whose size is approximately 50G or use the command: `fdisk -l | grep mapper`
8484
* Update `/etc/default/grub_installdevice` file with line `/dev/mapper/<LUN ID>`. Example: /dev/mapper/3600a09803830372f483f495242534a56
8585
* Please note that LUN ID varies from server to server.
8686

0 commit comments

Comments
 (0)