This page lists publically-released patches for Veritas Enterprise Products.
For Product GA build, see Veritas Entitlement Management System(VEMS) by clicking the Veritas Support 'Licensing' option.
For information on private patches, contact Veritas Technical Support.
Veritas is making it easier to find all software installers and updates for Veritas products with a completely redesigned experience. NetBackup HotFixes and NetBackup Appliance patches are now also available at the new Veritas Download Center.
Patches for your product can have a variety of names. These names are based on product, component, or package names. For more information on patch naming conventions and the relationship between products, components, and packages, see the SORT online help.
infoscale-sles12sp2_x86_64-Patch-7.1.0.200
Sign in if you want to rate this patch.

 Basic information
Release type: Patch
Release date: 2017-05-11
OS update support: None
Technote: None
Documentation: None
Popularity: 738 viewed    46 downloaded
Download size: 82.32 MB
Checksum: 1065248768

 Applies to one or more of the following products:
InfoScale Availability 7.1 On SLES12 x86-64
InfoScale Enterprise 7.1 On SLES12 x86-64
InfoScale Foundation 7.1 On SLES12 x86-64
InfoScale Storage 7.1 On SLES12 x86-64

 Obsolete patches, incompatibilities, superseded patches, or other requirements:

This patch supersedes the following patches: Release date
infoscale-sles12sp2_x86_64-Patch-7.1.0.100 (obsolete) 2017-03-20
gab-sles12_x86_64-Patch-7.1.0.100 (obsolete) 2016-09-08
vxfen-sles12_x86_64-Patch-7.1.0.100 (obsolete) 2016-06-20

 Fixes the following incidents:
3879189, 3893802, 3896880, 3896902, 3897027, 3897035, 3902533, 3911958, 3911960, 3911963, 3911967, 3912415, 3912593, 3912642, 3913506, 3915630, 3915631, 3916082

 Patch ID:
VRTSglm-7.1.0.200-SLES12
VRTSgms-7.1.0.200-SLES12
VRTSodm-7.1.0.200-SLES12
VRTSveki-7.1.0.200-SLES12
VRTSllt-7.1.0.500-SLES12
VRTSgab-7.1.0.400-SLES12
VRTSvxfen-7.1.0.400-SLES12
VRTSamf-7.1.0.200-SLES12
VRTSdbac-7.1.0.200-SLES12
VRTSvxvm-7.1.0.200-SLES12
VRTSaslapm-7.1.0.200-SLES12
VRTSvxfs-7.1.0.300-SLES12

 Readme file  [Save As...]
                          * * * READ ME * * *
                       * * * InfoScale 7.1 * * *
                         * * * Patch 200 * * *
                         Patch Date: 2017-03-15


This document provides the following information:

   * PATCH NAME
   * OPERATING SYSTEMS SUPPORTED BY THE PATCH
   * PACKAGES AFFECTED BY THE PATCH
   * BASE PRODUCT VERSIONS FOR THE PATCH
   * SUMMARY OF INCIDENTS FIXED BY THE PATCH
   * DETAILS OF INCIDENTS FIXED BY THE PATCH
   * INSTALLATION PRE-REQUISITES
   * INSTALLING THE PATCH
   * REMOVING THE PATCH
   * KNOWN ISSUES


PATCH NAME
----------
InfoScale 7.1 Patch 200


OPERATING SYSTEMS SUPPORTED BY THE PATCH
----------------------------------------
SLES12 x86-64


PACKAGES AFFECTED BY THE PATCH
------------------------------
VRTSamf
VRTSaslapm
VRTSdbac
VRTSgab
VRTSglm
VRTSgms
VRTSllt
VRTSodm
VRTSveki
VRTSvxfen
VRTSvxfs
VRTSvxvm


BASE PRODUCT VERSIONS FOR THE PATCH
-----------------------------------
   * InfoScale Availability 7.1
   * InfoScale Enterprise 7.1
   * InfoScale Foundation 7.1
   * InfoScale Storage 7.1


SUMMARY OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
Patch ID: VRTSvxvm-7.1.0.200-SLES12
* 3912415 (3907800) VxVM package installation will fail on SLES12 SP2.
* 3912593 (3909944) System may hang with soft lockup issue while using SmartIO read cache
for VxVM (Veritas Volume Manager) volumes under heavy IO load.
* 3912642 (3913298) System may panic while running vxstat in CVM (Clustered
Volume Manager) environment.
Patch ID: VRTSvxfs-7.1.0.200-SLES12
* 3911967 (3911966) VxFS module failed to load on SLES12 SP2.
Patch ID: VRTSodm-7.1.0.200-SLES12
* 3911963 (3907933) ODM module failed to load on SLES12 SP2.
Patch ID: VRTSdbac-7.1.0.200-SLES12
* 3902533 (3913168) Veritas Oracle Real Application Cluster does not support SUSE Linux Enterprise
Server 12 Service Pack 2 (SLES 12 SP2).
Patch ID: VRTSamf-7.1.0.200-SLES12
* 3897035 (3896875) Veritas Infoscale Availability (VCS) does not support SUSE Linux Enterprise Server 
12 Service Pack 2 (SLES 12 SP2).
Patch ID: VRTSvxfen-7.1.0.400-SLES12
* 3897027 (3896875) Veritas Infoscale Availability (VCS) does not support SUSE Linux Enterprise Server 
12 Service Pack 2 (SLES 12 SP2).
Patch ID: VRTSvxfen-7.1.0.100-SLES12
* 3879189 (3878333) In SCSI-3 mode, I/O fencing fails to automatically refresh 
registrations on coordination disks.
Patch ID: VRTSgab-7.1.0.400-SLES12
* 3896902 (3896875) Veritas Infoscale Availability (VCS) does not support SUSE Linux Enterprise Server 
12 Service Pack 2 (SLES 12 SP2).
Patch ID: VRTSgab-7.1.0.100-SLES12
* 3893802 (3893801) In some cases, when a node joins a large cluster, few GAB
directed messages are delivered in the wrong order.
Patch ID: VRTSllt-7.1.0.500-SLES12
* 3896880 (3896875) Veritas Infoscale Availability (VCS) does not support SUSE Linux Enterprise Server 
12 Service Pack 2 (SLES 12 SP2).
Patch ID: VRTSgms-7.1.0.200-SLES12
* 3911960 (3907939) GMS module failed to load on SLES12 SP2.
Patch ID: VRTSglm-7.1.0.200-SLES12
* 3911958 (3907936) GLM module failed to load on SLES12 SP2.
Patch ID: VRTSveki-7.1.0.200-SLES12
* 3913506 (3913507) VEKI module failed to load on SLES12 SP2.
Patch ID: VRTSvxfs-7.1.0.300
* 3916082 (3916611) Rearranging the ->followlink() and ->putlink code and fixing memory leak issue in vx_followlink().
* 3915630 (3906548) Start up vxfs after local file system mounted with rw through systemd.
* 3915631 (3915578) vxfs module is failed to load after reboot.


DETAILS OF INCIDENTS FIXED BY THE PATCH
---------------------------------------
This patch fixes the following incidents:

Patch ID: VRTSvxvm-7.1.0.200-SLES12

* 3912415 (Tracking ID: 3907800)

SYMPTOM:
VxVM package installation will fail on SLES12 SP2.

DESCRIPTION:
Since SLES12 SP2 has lot of kernel changes, package
installation fails. Added code changes to provide SLES12 SP2 platform support
for VxVM.

RESOLUTION:
Added code changes to provide SLES12 SP2 platform support.

* 3912593 (Tracking ID: 3909944)

SYMPTOM:
System may hang with soft lockup issue while using SmartIO read cache
for VxVM (Veritas Volume Manager) volumes under heavy IO load with following stack:

_raw_spin_unlock_irqrestore
vol_cache_evac_start
voliod_iohandle
voliod_loop
kthread
ret_from_fork

DESCRIPTION:
When IO load is high, SmartIO cache evacuation thread may not progress till the
IO count on the cache object becomes zero. In turn, the IO threads on the
volumes may not progress further because the SmartIO cache evacuation thread
continuously gets rescheduled.
As these threads are waiting for each other to progress, a deadlock situation
may arise.

RESOLUTION:
The code is fixed to avoid the deadlock situation between the threads.

* 3912642 (Tracking ID: 3913298)

SYMPTOM:
While running vxstat in CVM (Clustered Volume Manager) environment, system may
panic with following stack:

machine_kexec
__crash_kexec
crash_kexec
oops_end
no_context
do_page_fault
page_fault
   [exception RIP: vol_cvm_io_stats_common+143]                        
__wake_up_common
__wake_up_sync_key
unix_destruct_scm
__alloc_pages_nodemask
volinfo_ioctl
volsioctl_real
vols_ioctl at
vols_unlocked_ioctl
do_vfs_ioctl
sys_ioctl
entry_SYSCALL_64_fastpath

DESCRIPTION:
The system panic occurs because while fetching the IO statistics from the VxVM
(Veritas Volume Manager) kernel, an illegal address in the IO stats data is
accessed which is not yet populated.

RESOLUTION:
The code is fixed to correctly populate the address in the IO stats data before
fetching the IO stats.

Patch ID: VRTSvxfs-7.1.0.200-SLES12

* 3911967 (Tracking ID: 3911966)

SYMPTOM:
VxFS module failed to load on SLES12 SP2.

DESCRIPTION:
Since SLES12 SP2 is new release therefore VxFS module failed to load
on it.

RESOLUTION:
Added VxFS support for SLES12 SP2.

Patch ID: VRTSodm-7.1.0.200-SLES12

* 3911963 (Tracking ID: 3907933)

SYMPTOM:
ODM module failed to load on SLES12 SP2.

DESCRIPTION:
Since SLES12 SP2 is new release therefore ODM module failed to load
on it.

RESOLUTION:
Added ODM support for SLES12 SP2.

Patch ID: VRTSdbac-7.1.0.200-SLES12

* 3902533 (Tracking ID: 3913168)

SYMPTOM:
Veritas Oracle Real Application Cluster does not work with SUSE Linux Enterprise
Server 12 Service Pack 2 (SLES 12 SP2) and is unable to load the vcsmm module .

DESCRIPTION:
Veritas Oracle Real Application Cluster did not support SUSE Linux Enterprise
Server versions released after SLES 12 SP1.

RESOLUTION:
Veritas Oracle Real Application Cluster support for SUSE Linux Enterprise Server
12 SP2 is now introduced.

Patch ID: VRTSamf-7.1.0.200-SLES12

* 3897035 (Tracking ID: 3896875)

SYMPTOM:
Veritas Infoscale Availability (VCS) does not support SUSE Linux Enterprise Server 
12 Service Pack 2 (SLES 12 SP2).

DESCRIPTION:
Veritas Infoscale Availability did not support SUSE Linux Enterprise Server
versions released after SLES 12 SP1.

RESOLUTION:
Veritas Infoscale Availability support for SUSE Linux Enterprise Server 12 SP2 is
now introduced.

Patch ID: VRTSvxfen-7.1.0.400-SLES12

* 3897027 (Tracking ID: 3896875)

SYMPTOM:
Veritas Infoscale Availability (VCS) does not support SUSE Linux Enterprise Server 
12 Service Pack 2 (SLES 12 SP2).

DESCRIPTION:
Veritas Infoscale Availability did not support SUSE Linux Enterprise Server
versions released after SLES 12 SP1.

RESOLUTION:
Veritas Infoscale Availability support for SUSE Linux Enterprise Server 12 SP2 is
now introduced.

Patch ID: VRTSvxfen-7.1.0.100-SLES12

* 3879189 (Tracking ID: 3878333)

SYMPTOM:
With I/O fencing in SCSI-3 mode, if you enable the auto-refresh feature on the 
CoordPoint agent, then I/O fencing fails to automatically refresh registrations 
on the coordination points. This results in vxfen group to remain in faulted 
state.

DESCRIPTION:
Even to refresh registration on coordination disks, the vxfenswap script 
expects inputs about coordination disk groups from the CoordPoint agent. The 
CoordPoint agent does not provide this information to the vxfenswap script.
This causes the vxfenswap script to fail and the vxfen group remains faulted 
until it is manually cleared.

RESOLUTION:
The I/O fencing program is modified such that in SCSI3 mode fencing, the 
vxfenswap script does not explicitly require the coordination disk group 
information for refreshing registration keys on disks.

Patch ID: VRTSgab-7.1.0.400-SLES12

* 3896902 (Tracking ID: 3896875)

SYMPTOM:
Veritas Infoscale Availability (VCS) does not support SUSE Linux Enterprise Server 
12 Service Pack 2 (SLES 12 SP2).

DESCRIPTION:
Veritas Infoscale Availability did not support SUSE Linux Enterprise Server
versions released after SLES 12 SP1.

RESOLUTION:
Veritas Infoscale Availability support for SUSE Linux Enterprise Server 12 SP2 is
now introduced.

Patch ID: VRTSgab-7.1.0.100-SLES12

* 3893802 (Tracking ID: 3893801)

SYMPTOM:
In large clusters, a node join for a gab port gets stuck.

DESCRIPTION:
When a node joins a cluster, a few GAB directed messages might be
delivered in the incorrect order to the GAB clients. This incorrect 
message order is because of a bug in code where the messages are added to the
GAB delivery queue in incorrect order.

RESOLUTION:
The program is modified to ensure that during a node join scenario,
the GAB directed messages are inserted in the various GAB queues in the correct
order.

Patch ID: VRTSllt-7.1.0.500-SLES12

* 3896880 (Tracking ID: 3896875)

SYMPTOM:
Veritas Infoscale Availability (VCS) does not support SUSE Linux Enterprise Server 
12 Service Pack 2 (SLES 12 SP2).

DESCRIPTION:
Veritas Infoscale Availability did not support SUSE Linux Enterprise Server
versions released after SLES 12 SP1.

RESOLUTION:
Veritas Infoscale Availability support for SUSE Linux Enterprise Server 12 SP2 is
now introduced.

Patch ID: VRTSgms-7.1.0.200-SLES12

* 3911960 (Tracking ID: 3907939)

SYMPTOM:
GMS module failed to load on SLES12 SP2.

DESCRIPTION:
Since SLES12 SP2 is new release therefore GMS module failed to load
on it.

RESOLUTION:
Added GMS support for SLES12 SP2.

Patch ID: VRTSglm-7.1.0.200-SLES12

* 3911958 (Tracking ID: 3907936)

SYMPTOM:
GLM module failed to load on SLES12 SP2.

DESCRIPTION:
Since SLES12 SP2 is new release therefore GLM module failed to load
on it.

RESOLUTION:
Added GLM support for SLES12 SP2.

Patch ID: VRTSveki-7.1.0.200-SLES12

* 3913506 (Tracking ID: 3913507)

SYMPTOM:
VEKI module failed to load on SLES12 SP2.

DESCRIPTION:
Since SLES12 SP2 is new release therefore VEKI module failed to load
on it.

RESOLUTION:
Added VEKI support for SLES12 SP2.

Patch ID: VRTSvxfs-7.1.0.300

* 3916082 (Tracking ID: 3916611)

SYMPTOM:
Rearranging the ->followlink() and ->putlink code. Fixing memory leak
issue in vx_followlink().

DESCRIPTION:
As in SLES12 SP2 the ->followlink() and ->putlink() calling
convention is changed. So writing a wrapper around existing followlink() and
putlink() code and making it such that the same code will run for SLES12 SP2 as
well as other Linux platforms. There was also a memory leak issue in
vx_followlink(), this change fixed it as well.

RESOLUTION:
Rearranged the ->followlink() and putlink() code.

* 3915630 (Tracking ID: 3906548)

SYMPTOM:
Read-only file system errors reported while loading drivers to start up vxfs 
through systemd.

DESCRIPTION:
On SLES system, vxfs starting up could be invoked by other systemd unit while 
root 
and local file system still not be mounted as read/write, in such case, Read-
only 
file system errors could be reported during system start up.

RESOLUTION:
Start up vxfs after local file system mounted with rw through systemd, also 
delay vxfs file system mounting by add "_netdev" mount option in /etc/fstab.

* 3915631 (Tracking ID: 3915578)

SYMPTOM:
vxfs module failing to load after reaboot with dmesg log:
[    3.689385] systemd-sysv-generator[518]: Overwriting existing symlink
/run/systemd/generator.late/vxfs.service with real service.
[    4.738143] vxfs: Unknown symbol ki_get_boot (err 0)
[    4.793301] vxfs: Unknown symbol ki_get_boot (err 0)

DESCRIPTION:
The vxfs module is dependent on the veki module. During boot time, 
the veki is not loaded before vxfs. So the vxfs module fails to load.

RESOLUTION:
During boot the veki should start before loading vxfs module.



INSTALLING THE PATCH
--------------------
Run the Installer script to automatically install the patch:
-----------------------------------------------------------
Please be noted that the installation of this P-Patch will cause downtime.

To install the patch perform the following steps on at least one node in the cluster:
1. Copy the patch infoscale-sles12_x86_64-Patch-7.1.0.200.tar.gz to /tmp
2. Untar infoscale-sles12_x86_64-Patch-7.1.0.200.tar.gz to /tmp/hf
    # mkdir /tmp/hf
    # cd /tmp/hf
    # gunzip /tmp/infoscale-sles12_x86_64-Patch-7.1.0.200.tar.gz
    # tar xf /tmp/infoscale-sles12_x86_64-Patch-7.1.0.200.tar
3. Install the hotfix(Please be noted that the installation of this P-Patch will cause downtime.)
    # pwd /tmp/hf
    # ./installVRTSinfoscale710P200 [<host1> <host2>...]

You can also install this patch together with 7.1 base release using Install Bundles
1. Download this patch and extract it to a directory
2. Change to the Veritas InfoScale 7.1 directory and invoke the installer script
   with -patch_path option where -patch_path should point to the patch directory
    # ./installer -patch_path [<path to this patch>] [<host1> <host2>...]

Install the patch manually:
--------------------------
Manual installation is not supported.


REMOVING THE PATCH
------------------
Manual uninstallation is not supported.


KNOWN ISSUES
------------
* Tracking ID: 3913711

SYMPTOM: DMP native support may failed to be enabled on SLES12 SP2 with following 
error:

# vxdmpadm settune dmp_native_support=on
VxVM vxdmpadm ERROR V-5-1-15690 Operation failed for one or more volume 
groups

VxVM vxdmpadm ERROR V-5-1-15686 The following vgs could not be migrated as 
error
in bootloader configuration file -

        <vg_name>

WORKAROUND: The work around for this issue is to ensure the default menu entry is set 
prior
to enabling DMP native support.
The default menu entry can be set using the command agrub2-set-default "SLES
12-SP2a.

* Tracking ID: 3913715

SYMPTOM: Root disk encapsulation is NOT supported on SLES12 SP2.

WORKAROUND: Currently there is NO work around for this issue.



OTHERS
------
NONE





Read and accept Terms of Service