Loading...
Loading...
Servers using a supported Linux version may require the Linux Device Mapper (DM) "multipath.conf" file to be modified. These settings are required to be optimally configured for Linux multipath to work with HPE MSA Storage systems.Supported Linux OS versions, as well as notes for storage system-specific multipath.conf modifications required can be found on theHPE Single Point of Connectivity Knowledge (SPOCK)website (Note: An HPE Passport account is required to sign in to this website).
This advisory applies to the following HPE MSA Storage systems:HPE MSA 1050 SAN StorageHPE MSA 2050 SAN StorageHPE MSA 2052 SAN StorageHPE MSA 1060 StorageHPE MSA 2060 StorageHPE MSA 2062 StorageHPE MSA 2070 StorageHPE MSA 2072 Storage
NOTE: The default Device Mapper configuration table may include the correct settings.To verify default Device Mapper configuration table includes the correct settings, execute either of the following commands:# multipath -t# multipathd show configSearch the output and verify if your HPE MSA is included. If this output does not include the latest MSA generation number in the product "MSA [12]0[4567]0 (SAN|SAS|FC|iSCSI)",update the multipath.conf file with the following settings to overwrite the default configuration table.Linux device mapper multipath should include the following settings, under the "Devices" section of the multipath.conf file:device {vendor "(HP|HPE)"product "MSA [12]0[4567]0 (SAN|SAS|FC|iSCSI)"path_grouping_policy "group_by_prio"prio "alua"failback "immediate"no_path_retry 18}Save the multipath.conf file. After the multipath.conf file modification, the server or Device Mapper needs to be restarted with the following command:#systemctl restart multipathd
Operating Systems Affected:Not Applicable
Click on a version to see all relevant bugs
Hewlett Packard Enterprise Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.