Updates, Patches and Late Breaking News for the Release Notes for Storage Foundation and High Availability Solutions 6.2, 6.2.1

Article: 100014228
Last Published: 2021-08-05
Ratings: 0 0
Product(s): ApplicationHA, InfoScale & Storage Foundation

Problem


Late Breaking News (LBN) - Updates to the Release Notes for Storage Foundation and High Availability Solutions on Linux, Solaris, and AIX - 6.2, 6.2.1


Solution
 

Patches

Veritas highly recommends that you check for any patches needed for this release. For the latest patches, go to: https://sort.veritas.com/patch/finder.
 

Documentation

For the latest updated documentation, go to: https://sort.veritas.com/documents/.
 

Notifications

For the latest patch availability notifications, go to: https://sort.veritas.com/welcome/notifications.
 

alerts


The 'delayed allocation' (dalloc) feature of Veritas File System (VxFS) can cause silent data corruption.

For more information, see 000024251.

 

Updates

 

Impact of Meltdown (CVE-2017-5754) and Spectre (CVE-2017-5753 & CVE-2017-5715) on Veritas InfoScale, Storage Foundation High Availability (SFHA) solutions and Access
https://www.veritas.com/support/en_US/article.100041581

LLT module fails to start in Storage Foundation High Availability (SFHA) 6.2.1 on Red Hat Enterprise Linux 7.0 with kernel 3.10.0-327.3.1
For details, see the article at https://www.veritas.com/docs/000100594.
 

Support for Red Hat Enterprise Linux (RHEL) 7 and Oracle Linux (OL) 7
Veritas supports RHEL 7 and OL 7 with SFHA 6.2. The supported kernel version is 3.10.0-123.el7.


Support for Red Hat Enterprise Linux (RHEL) 7.1
Support for RHEL 7.1 has been introduced with SFHA 6.2.1, consult the following article for more information
https://www.veritas.com/docs/000024792


Support for Storage Foundation High Availability (SFHA) solutions on Red Hat Enterprise Linux (RHEL) 7.2
Consult the following article for support of SFHA on RHEL 7.2
https://www.veritas.com/docs/000099839

For more information, see the latest product Release Notes at https://sort.veritas.com/documents.
 

Support for Storage Foundation High Availability (SFHA) Solutions on Red Hat Enterprise Linux (RHEL) 7.3
Consult the following article for support of SFHA on RHEL 7.3
https://www.veritas.com/docs/000116172


Support for Storage Foundation High Availability (SFHA) Solutions on Red Hat Enterprise Linux (RHEL) 6.7
Storage Foundation and High Availability Solutions (SFHA) 6.2.1 by default does not support RHEL 6.7 due to an incompatibility with the kernel interface. Veritas has released a patch to address the issue.

For more information on the patch and where to obtain it, consult the following article:
https://www.veritas.com/support/en_US/article.000025669
 

Support for Storage Foundation High Availability (SFHA) Solutions on Red Hat Enterprise Linux (RHEL) 6.8
Refer to the following article for SFHA 6.2.1 support on RHEL 6.8
https://www.veritas.com/docs/000109319


Support for Storage Foundation High Availability (SFHA) solutions on Red Hat Enterprise Linux (RHEL) 6.9
Consult the following article for SFHA 6.2.1 support on RHEL 6.9
https://www.veritas.com/docs/000126038


Support for Storage Foundation High Availability (SFHA) Solutions on SuSE Linux Enterprise Server (SLES) 12
Support for SLES 12 was introduced on SFHA 6.2.1


Support for Storage Foundation High Availability (SFHA) Solutions on SuSE Linux Enterprise Server (SLES) 12 SP1
Consult the following article for SFHA 6.2.1 support on SLES 12 SP1
https://www.veritas.com/docs/000107832


Support for Storage Foundation High Availability (SFHA) Solutions on SuSE Linux Enterprise Server (SLES) 12 SP2
Consult the following article for SFHA 6.2.1 support on SLES 12 SP2
https://www.veritas.com/docs/000116665


Support for Oracle Solaris 11.3 SPARC and Support Repository Updates (SRUs) to 11.3.13.4
Veritas supports Oracle Solaris 11.3 SPARC and up to SRU 11.3.13.4 with SFHA 6.2.1 and a patch. The patch is required to enable Solaris 11.3 support. To obtain the patch, go to https://sort.veritas.com/patch/detail/11105.
SORT platform lookup: https://sort.veritas.com/platformlookup


Support for Oracle Solaris 11.2 and Support Repository Updates (SRUs) up to 11.2.15.5
Veritas supports Oracle Solaris 11.2 and SRUs up to 15.5 with SFHA Solutions 6.2 & 6.2.1.


Support for Oracle Solaris 11.2 kernel zones
Veritas supports Oracle Solaris 11.2 kernel zones (brand solaris-kz) only with Veritas Cluster Server (VCS) 6.2. Veritas currently does not support Oracle Solaris 11.2 kernel zones with Storage Foundation 6.2.


Support for Storage Foundation High Availability (SFHA) Solutions on Oracle VM for SPARC 3.2.x
Veritas supports Oracle VM for SPARC 3.2.x with SFHA solutions 6.2.1.


Single Root I/O virtualization (SR-IOV) FC support with Storage Foundation and High Availability 6.2.1 on Solaris
Storage Foundation and High Availability 6.2.1 supports Single Root I/O virtualization (SR-IOV).
For more information about SR-IOV support, see the Storage Foundation and High Availability Solutions Virtualization Guide - Solaris.


Support for Storage Foundation High Availability (SFHA) Solutions on AIX 7.1 TL4
Consult the following article for support of SFHA 6.2.1 on AIX 7.1 TL4
https://www.veritas.com/docs/000108294

 

Known Issues

[ Install - Linux ]: The installation process fails after performing a pre-check and the installer requests the user to install incorrect version of OS rpms (3878583)
If the operating system (OS) update version is not supported by the release, the installer checks if the P-patch for the OS update version exists. If the P-patch exists, the installer directly downloads the P-patch from SORT. But in  this scenario, the required OS rpms are not updated correctly and the installer prints incorrect version of OS rpms and asks the user to install those rpms. The installation fails because of the version mismatch.
Workaround: Exit the installation and re-run the installer with the required P-patch downloaded by the installer.
The downloaded patch is located in the following directory:
/opt/VRTS/install/repository/required_patch/
Run the following command:

./installmr -patch_path /opt/VRTS/install/repository/required_patch/<downloaded_patch>

[ DMP/VxVM ]: On Solaris 11 U2 SRU 15.5, the namingscheme parameter of vxddladm cannot be changed even when the value of dmp_native_support is off (3833983)

On Solaris 11 U2 SRU 15.4, the following error message is displayed if you change the disk namingscheme when the value of dmp_native_support is off:
VxVM vxddladm ERROR V-5-1-15950 Cannot change naming-scheme/persistence/lowercase/use_avid values as OS native support is enabled on some DMP devices.
Workaround: There is no workaround. Do not change namingscheme in 6.2.1.

 
[ DMP/VxVM ]: On Solaris 11 U2 SRU 15.5, the dmp_native_support value might not be changed (3795742)

On Solaris 11U2 SRU 15.4, the following messages are displayed if you try to change the value of dmp_native_support:
VxVM vxdmpadm ERROR V-5-1-15690 Operation failed for one or more zpools
VxVM vxdmpadm ERROR V-5-1-15686 The following zpool(s) could not be migrated as they are not healthy -  rpool
Workaround: There is no workaround. Upgrade to 7.0 or later release.


Problems un-mounting VxFS file systems on RHEL 6.6 when inotify APIs are used.

Consult this 000024054 for more information.
 

VxFS file systems using VxVM volumes will not mount at boot time on RHEL 7

VxFS file systems that are configured to mount with VxVM devices in /etc/fstab will not mount at boot time, due to an interoperability issue with RHEL 7 systemd.  This does not apply to CFS or VxFS file systems that are mounted by Veritas Cluster Server.  This issue is fixed in  SFHA  6.2.1, a workaround also exists:

Workaround:
After boot has completed, execute “mount –a” to mount the file systems that did not mount at boot time. This can be done manually or automatically via an additional boot script, at the end of the boot process.

Note: When adding VxFS  entries in /etc/fstab, use the “nofail” mount option. This avoids boot failure if the system daemon fails to find the VxVM volume devices.


Guidelines for setting the MTU for LLT interconnects in FSS environments

In Flexible Storage Sharing (FSS) environments, set the maximum transmission unit (MTU) to the highest value (typically 9000) supported by the NICs when LLT is configured over Ethernet or UDP for both high priority and low priority links. Ensure that the  switch is also set to 9000 MTU.
Note: MTU setting is not required for LLT over RDMA configurations.

For virtual NICs, all the components, the virtual NIC, the corresponding physical NIC, and the virtual switch must be set to 9000 MTU. If a higher MTU cannot be configured on the public link (because of restrictions on other components such as a public switch), do not configure the public link in LLT. LLT uses the lowest of the MTU that is configured among all high priority and low priority links.

For more information, see the latest product installation guide at https://sort.veritas.com/documents.


Storage plug-in for Oracle OEM 12c is available

Veritas has released a Storage plug-in to support Oracle Enterprise Manager (OEM) 12c in the Storage Foundation and High Availability 6.2 release.
The plug-in provides a graphical interface that allows you to:

  • manage Oracle database objects using SmartIO
  • create point-in-time copies (Storage Checkpoint, Database FlashSnap, Space-optimized Snapshot, and FileSnap) of Oracle databases using the SFDB features
  • view cluster-specific information

For downloading the plug-in and information on using it, go to: https://www.veritas.com/community/downloads/sfha-solutions-62-Veritas-storage-plug-oem-12c


[ DMP/VxVM ]: After the OS native support is enabled and the host is rebooted, the system continues to panic and cannot start (3787475)
The issue occurs only when the root disks are mirrored, and the OS native support is enabled with DMP.
This issue is specific to 6.2.1, Solaris (SPARC) 11.2 SRUs 9.5 or later updates only.

Workaround:
Refer to the Oracle Bug ID: 20896210 for workaround.
Contact Oracle support for assistance.

 

 

Was this content helpful?