Updates, Patches and Late Breaking News for the Release Notes for Veritas InfoScale 7.0 and 7.0.1

Updates, Patches and Late Breaking News for the Release Notes for Veritas InfoScale 7.0 and 7.0.1

  • Article ID:100015596
  • Last Published:
  • Product(s):InfoScale & Storage Foundation

Problem

Late Breaking News (LBN) - Updates to the Release Notes for Veritas InfoScale 7.0 and 7.0.1, on AIX, Linux, and Solaris

Solution

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

Updates

Support for Oracle Solaris 11.2.15.5.1
Veritas InfoScale 7.0 and 7.0.1 supports Oracle Solaris 11.2.15.5.1.
For more information on the supported operating systems, see the Veritas InfoScale Release Notes.


Support for Veritas InfoScale on Red Hat Enterprise Linux (RHEL) 6.7
Veritas InfoScale 7.0 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 Veritas InfoScale on red Hat Enterprise Linux (RHEL) 6.8
Consult this article for support of RHEL 6.8
https://www.veritas.com/docs/000109319


Support for Veritas InfoScale on red Hat Enterprise Linux (RHEL) 6.9
Consult this article for support of RHEL 6.9
https://www.veritas.com/docs/000126038
 

Support for Veritas InfoScale on Red Hat Enterprise Linux (RHEL) 7.3
Consult the following article for support of infoScale on RHEL 7.3:
https://www.veritas.com/docs/000116172
 

Support for Veritas InfoScale on SuSE Linux Enterprise Server (SLES) 12 SP2
Consult the following article for support of infoScale on SLES12SP2:
https://www.veritas.com/docs/000116665


Single Root I/O virtualization (SR-IOV) FC support with Veritas InfoScale 7.0 on Solaris
Veritas InfoScale 7.0 supports Single Root I/O virtualization (SR-IOV).
For more information about SR-IOV support, see the Veritas InfoScale Virtualization Guide - Solaris.
 

Documentation

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

Notifications

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

Known Issues

dmp_native_support issues with latest Solaris sparc 11.2 SRUs on turning dmp_native_support=off [3847384]

On 15.4SRU and 12.6 SRU for Solaris 11.2, when dmp_native support is ‘on’, the following two issues occur: 

  1. Turning of dmp_native_support ‘on’ and ‘off’ requires reboot. System gets panic during the reboot as a part of setting dmp_native_support off.
  2. Sometimes, system comes up after reboot when dmp_native_support is set to ‘off’. In such case, panic is observed when system is restarted after uninstalling SF and it fails to boot up. For both of the issues, the same error message is displayed:

panic[cpu0]/thread=20012000: read_binding_file: \
/etc/name_to_major file not found

A SR(3-11640878941) ticket has been opened with Oracle SR to track this issue. 

Workaround:
Before enabling dmp_native_support feature, remove the following code from the vxdmproot script which is located at /etc/vx/bin directory.

# Operation: Disable
# Remove /etc/system from $ARCHIVE_FILES
exists=`grep -c "etc/system" $ARCHIVE_FILES`
if [ $exists -gt 0 ]; then
         tempfile=`mktemp /tmp/$PROGNAME.XXXX`
         grep -v -w "etc/system" $ARCHIVE_FILES > $tempfile
         rm $ARCHIVE_FILES; mv $tempfile $ARCHIVE_FILES;
fi

# Remove /etc/name_to_major from $ARCHIVE_FILES
exists=`grep -c "etc/name_to_major" $ARCHIVE_FILES`
if [ $exists -gt 0 ]; then
          tempfile=`mktemp /tmp/$PROGNAME.XXXX`
          grep -v -w "etc/name_to_major" \
                          $ARCHIVE_FILES > $tempfile
          rm $ARCHIVE_FILES; mv $tempfile $ARCHIVE_FILES;
fi



Interrupted lazy unmounts can result in a system panic on all the Linux platforms 
Applicable to: RHEL 6, RHEL 7, SLES 11, and SLES 12 for Veritas  InfoScale Foundation 7.0, Veritas  InfoScale Storage 7.0, and Veritas  InfoScale Enterprise 7.0
If a lazy unmount process is interrupted, the system may panic resulting in a reboot. For example, if the terminal used to start the process is disconnected, the system may panic and will require a reboot. 
The following error message is displayed when the panic occurs:
BUG: unable to handle kernel NULL pointer dereference
Workaround:
There is no workaround available. The issue will be fixed in the 7.0.0.100 patch release.


The notify sink resource and generic application resource moves to OFFLINE|UNKNOWN state after VCS upgrade
If you use the Veritas high availability wizard to configure an application for monitoring, and later upgrade to VCS 7.0, then the notify sink resource goes to the OFFLINE|UNKNOWN state.
If you used the wizard to configure an application for monitoring with the generic agent, then the generic application resource also goes to the OFFLINE|UNKNOWN state.
This issue occurs because some file paths are modified in Veritas InfoScale 7.0.

Workaround:
Perform the following steps:

1. To resolve the file path issue for the notify sink resource, modify the PathName attribute of the VCSNotifySinkRes resource by using the following commands:
  • Enable editing for the high availability configuration.
# /opt/VRTSvcs/bin/haconf -makerw
  • Resolve the file path issue.
# /opt/VRTSvcs/bin/hares -modify VCSNotifySinkRes PathName /opt/VRTSvcs/portal/vcs_wizards/admin/notify_sink
  • Disable editing for the high availability configuration.
# /opt/VRTSvcs/bin/haconf -dump -makero
 
2. To resolve the file path issue for the (generic) application resource, execute the following commands: 
  • Determine the path to the program that the generic agent uses to monitor the application resource.
# /opt/VRTSvcs/bin/hares -value ResourceName MonitorProgram
Where ResourceName is the name of the monitored application resource  An output along the following lines appears.

/opt/VRTSvcs/bin/Application/getServiceStatus PathToMonitorProgram
Where ​PathToMonitorProgram is the file path to the monitor program that the generic agent uses to monitor the application. 

Note: The output also includes some arguments, which are part of PathToMonitorProgram. Ensure that you specify both the path and the arguments when you specify the value of PathToMonitorProgram in the following commands.

  • Make the high availability configuration editable.
# /opt/VRTSvcs/bin/haconf -makerw
  • Resolve the file path issue.

# /opt/VRTSvcs/bin/hares -modify ResourceName MonitorProgram "/opt/VRTSvcs/bin/Application/getServiceStatus.wiz PathToMonitorProgram"

  • Disable editing for the high availability configuration.

#  /opt/VRTSvcs/bin/haconf -dump -makero



Inter Process Messaging (IPM) protocol used for secure communication is deprecated [3850654]
Veritas’ proprietary secure communication protocol, IPM-based secure communication, which is used for secure communication between CP server and VCS clusters, is deprecated in version 7.0.
CP servers on release 7.0 support the following communication protocols:

  • Communication between InfoScale Availability clusters on releases prior to 6.1 and CP servers on release 7.0 happens over IPM protocol.
  • Communication between InfoScale Availability clusters on releases 6.1 or higher and CP servers on release 7.0 happens over HTTPS protocol.

In future releases, the IPM protocol may not be supported for CP server and InfoScale Availability clusters. If you want to run a future release version of CP server, Veritas recommends upgrading InfoScale Availability clusters to release version 6.1 or higher.

Was this content helpful?