Release Notes
Release Notes
Release Notes
July 2015
Legal Notice
Copyright 2015 Symantec Corporation. All rights reserved.
Symantec, the Symantec Logo, the Checkmark Logo, Veritas, the Veritas Logo, InfoScale,
CommandCentral, NetBackup, Enterprise Vault, and LiveUpdate are trademarks or registered
trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other
names may be trademarks of their respective owners.
The product described in this document is distributed under licenses restricting its use, copying,
distribution, and decompilation/reverse engineering. No part of this document may be
reproduced in any form by any means without prior written authorization of Symantec
Corporation and its licensors, if any.
THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED
CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED
WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR
NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH
DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL
NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION
WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE
INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE
WITHOUT NOTICE.
The Licensed Software and Documentation are deemed to be commercial computer software
as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19
"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights in
Commercial Computer Software or Commercial Computer Software Documentation", as
applicable, and any successor regulations. Any use, modification, reproduction release,
performance, display or disclosure of the Licensed Software and Documentation by the U.S.
Government shall be solely in accordance with the terms of this Agreement.
Symantec Corporation
350 Ellis Street
Mountain View, CA 94043
http://www.symantec.com
Technical Support
Symantec Technical Support maintains support centers globally. Technical Supports
primary role is to respond to specific queries about product features and functionality.
The Technical Support group also creates content for our online Knowledge Base.
The Technical Support group works collaboratively with the other functional areas
within Symantec to answer your questions in a timely fashion. For example, the
Technical Support group works with Product Engineering and Symantec Security
Response to provide alerting services and virus definition updates.
Symantecs support offerings include the following:
A range of support options that give you the flexibility to select the right amount
of service for any size organization
For information about Symantecs support offerings, you can visit our website at
the following URL:
www.symantec.com/business/support/index.jsp
All support services will be delivered in accordance with your support agreement
and the then-current enterprise technical support policy.
Hardware information
Operating system
Network topology
Problem description:
Customer service
Customer service information is available at the following URL:
www.symantec.com/business/support/
Customer Service is available to assist with non-technical questions, such as the
following types of issues:
customercare_apj@symantec.com
semea@symantec.com
supportsolutions@symantec.com
Documentation
Your feedback on product documentation is important to us. Send suggestions for
improvements and reports on errors or omissions. Include the title and document
version (located on the second page), and chapter and section titles of the text on
which you are reporting. Send feedback to:
doc_feedback@symantec.com
For information regarding the latest HOWTO articles, documentation updates, or
to ask a question regarding product documentation, visit the Storage and Clustering
Documentation forum on Symantec Connect.
https://www-secure.symantec.com/connect/storage-management/
forums/storage-and-clustering-documentation
Release Notes
This document includes the following topics:
Introduction
Fixed issues
Known issues
Limitations
Documentation
Introduction
This document provides important information about this Symantec High Availability
Agent Pack release. Review this entire document before installing and configuring
the agents.
For more information about Symantec High Availability Agent Pack, refer to the
Getting Started Guide, which is available on the Symantec Operations Readiness
Tools (SORT) site: https://sort.symantec.com/agents.
For important updates regarding this release, see the Late-Breaking News TechNote
on the Symantec Technical Support Web site:
http://www.symantec.com/docs/TECH46455
Note: This document does not contain information about the Symantec High
Availability agents for Microsoft applications on Windows. For information about
these agents, see the Symantec Cluster Server Agent Pack Readme. The Readme
is available on the VCS Agent Details page on SORT and also in the agent ZIP file.
Release Notes
Changes introduced in this release
Note: For information about ApplicationHA agents on Windows, see the Symantec
Application HA Agent Pack Readme. The Readme is available on the ApplicationHA
Agent Details page on SORT and also in the agent ZIP file.
Application agents
Table 1-1 lists the changes in the VCS Application agents in this Agent Pack release.
Table 1-1
Application agents
Application
SAP HANA
IBM WebSphere MQ
Docker
The agent for SAP NetWeaver now supports SAP ERP, based on
SAP NetWeaver 7.x with SAP Kernel 7.20 DCK, on the AIX and
Solaris operating systems.
Replication agents
Table 1-2 lists the changes in the VCS Replication agents in this Agent Pack release.
Release Notes
Fixed issues
Table 1-2
Replication agents
Application
EMC RecoverPoint
EMC SRDF
Application
SAP HANA
Note: For configuring SAP NetWeaver agent with ApplicationHA 6.2, you need to
install SAP NetWeaver (VRTSsapnw04), SAP NetWeaver 7.1, 7.2, 7.3, 7.4
(VRTSsapwebas71), and SAP NetWeaver with HA-API support (VRTSsapnw)
agents.
Fixed issues
This section describes the incidents that are fixed in this Agent Pack release.
Application agents
Table 1-4 lists the issues that are fixed in the VCS Application agents.
Release Notes
Fixed issues
Table 1-4
Incident
Description
3800334
IBM WebSphere MQ
Operating systems: AIX, Linux, and Solaris
Symptom: When the non-default MQInstallationPath is configured,
the clean entry point does not kill all the instance-related processes.
Description: The clean entry point does not set the MQInstallationPath
path provided by the user. The agent, therefore, attempts to use the
default path but does not find the correct location of the endmqm
command.
Resolution: Symantec has modified the IBM WebSphere MQ agent
to use the correct command path provided by the user. Hence, the
endmqm command is executed successfully.
3778297
IBM WebSphere
Operating system: Windows
Symptom: The Symantec High Availability agent for WebSphere
does not decrypt the WebSphere Application Server admin password,
which is specified in the StopOptions attribute. This attribute is used
when the admin security is enabled for a profile.
Description: If admin security is enabled for the WebSphere
Application Server profile, then the username and password for that
profile are needed to stop the server. The WebSphere agent uses
the StopOptions attribute to provide additional parameters to the
StopServer script. The agent does not decrypt password specified
in the StopOptions attribute. However, the password should be
decrypted and provided to the StopServer utility.
Resolution: Symantec has modified the High Availability agent for
WebSphere to decrypt the admin password specified in the
StopOptions attribute. The modified agent decrypts the password
when used in an encrypted format and uses as it is when specified
in the plain text format.
Release Notes
Fixed issues
Table 1-4
Incident
Description
3801190
IBM WebSphere
Operating system: Windows
Symptom: Symantec High Availability Agent for WebSphere does
not support non-default profile location on Windows.
Description: Agent assumes the default profile path based on the
profile name. It may lead to the profile not found error.
Resolution: Symantec has modified the WebSphere agent on
Windows to support non-default Application Server profile installation.
New agent checks if the ServerProfile attribute contains full path to
Application Server Profile or just the profile name. If the ServerProfile
attribute contains only the profile name, the default profile location
is considered, else, the full path specified is used.
3792205
SAP HANA
Operating system: Linux
Symptom: In a three replicated, single-node SAP HANA database
instances, when the node faults, the takeover operation is performed
on the local cluster node as well as on the GCO node.
Description: If the service groups have an online local hard
dependency, then during the takeover operation, the nodes of the
local cluster and the GCO node trigger the preonline and become
Primary.
Resolution: Symantec has provided a hot fix for engine to resolve
this issue. For more information about the hot fix, refer to the
Symantec Operations Readiness Tools (SORT) Web site:
https://sort.symantec.com/agents.
Replication agents
Table 1-5 lists the issue that is fixed in the VCS Replication agent.
10
Release Notes
Known issues
Table 1-5
Incident
Description
3790947
EMC MirrorView
Operating systems: AIX, Linux, Solaris, and Windows
Symptoms: Unable to promote async consistency group.
Description: When the EMC MirrorView agent monitors the asynchronous
consistency group, failover to remote cluster fails since the agent keeps
waiting to synchronize the consistency group instead of initiating
synchronization.
Resolution: The EMC MirrorView agent source is now changed to handle
the synchronization for asynchronous consistency group.
3785315
Hitachi TrueCopy
Operating systems: AIX, Linux, and Solaris
Symptom: After the failover of the HTC resource, the extended attributes
are not updated.
Description: After the failover of the HTC resource, the extended attributes
of the disks associated with disk group are not updated.
Resolution: Symantec has modified the HTC agent to issue a vxdisk
scandisk command for the device associated with the device group, so
that the extended attributes are updated for those disks.
Known issues
This section lists the known issues that are applicable in this agent pack release.
11
Release Notes
Known issues
12
Symantec has added two new attributes, namely StopOptions and StartOptions,
to support multiple instances in WebSphere MQ. The types file has been modified
for the WebSphere MQ 6.2.1.0 agent. Syntax error is seen in the agent log, if the
StopOptions and StartOptions attributes are not present in the WebSphereMQTypes.cf
file.
Workaround: If VCS is already stopped, then copy the latest WebSphereMQTypes.cf
file from the /etc/VRTSagents/ha/conf/WebSphereMQ location to the
/etc/VRTSvcs/conf/config/ location.
If VCS is running, then execute the following commands in sequence:
#haagent -stop WebSphereMQ -force -sys <SYS>
#haagent -display WebSphereMQ
#rpm -e VRTSmq6
#rpm -ivh VRTSmq6-6.2.1.0-GENERIC.noarch.rpm
#haconf -makerw
#haattr -add WebSphereMQ StartOptions -string
#haattr -add WebSphereMQ StopOptions -string "%-i
#hatype -modify WebSphereMQ ArgList ResLogLevel State IState
QueueManager CommandServer MQUser MQVer StartOptions
StopOptions EnvFile SecondLevelMonitor MonitorProgram
MonitorListener CleanIPC MQInstallationPath DisabledProcesses
#haconf -dump -makero
#haagent -start WebSphereMQ -sys <SYS>
Listener for Queue Manager may not be configured if you do not select the
Monitor Listener for the Queue Manager check box (3678386)
Symptom: On the Queue Manager selection panel, if you click Next without
selecting the Monitor Listener for the Queue Manager check box, you might not
be able to return to that panel to configure monitoring for a queue manager listener.
This issue occurs on the Windows operating system.
Release Notes
Known issues
Support for only one listener associated with each queue manager
(3678391)
Symptom: The Symantec High Availability Configuration wizard supports only one
listener associated with each queue manager.
Workaround: Manually add the listener resource in the Queue Manager service
group using the ha commands.
Probe the CiscoUCS resources after the ucsha -stop command fails using
the following command:
# hares -probe <resource_name> -sys <system_name>
Check the state of the CiscoUCS resource using the following command:
# hares -state <resource_name>
13
Release Notes
Known issues
User's attempt to add a disk to a VxVM disk group may fail (3683553)
Symptom: The user's attempt to add a disk to a VxVM disk group, after the
replication roles have changed from Secondary to Primary, might fail.
This issue occurs because of a stale VxVM cache and a VxVM rule that does not
permit a user to add a primary disk to a disk group that contains secondary disks.
Note: This issue is applicable for VCS versions prior to VCS 6.2.
Workaround: To resolve this issue, use the Symantec preonline trigger; contact
Symantec Technical Support to obtain the Symantec preonline trigger.
14
Release Notes
Known issues
Fire drill fails with the error message on Windows operating system with
SFW HA (3123099)
Symptom: On the Windows operating system with SFW HA versions 6.0 or 6.0.1,
fire drill might fail with the following error message:
ERROR: Disk group: No Disk found with matching tag SIRemote-*
File conflict error message displayed while installing the replication agent
package in an SFCFS environment (2392131)
Symptom: The replication agents currently ship action entry points on the
CVMVolDg resource, which is part of the VRTScavf package. This package is part
of the SFCFS package set. The VRTScavf package also ships the same action
entry points. As a result, while installing the replication agent package in an SFCFS
environment, the installer might display file conflict error messages. This problem
occurs on the AIX, HP-UX, Linux, and Solaris operating systems.
Workaround: Symantec recommends installing the replication agent package with
the appropriate force option so as to overwrite the conflicting files installed by the
VRTScavf package.
EMC MirrorView
This section describes the known issues in Symantec High Availability agent for
EMC MirrorView.
15
Release Notes
Known issues
If the disk access records are not refreshed on running this command, contact
Symantec Technical Support.
EMC SRDF
This section describes the known issues in the Symantec High Availability agent
for EMC SRDF.
Silver fire drill configuration may fail with SFHA 6.1 and SFCFS HA 6.1
(3337677)
Symptom: Silver fire drill configuration may fail with SFHA 6.1 and SFCFS HA 6.1.
The Diskgroup agent resource in the fire drill service group may not be able to
import the fire drill diskgroup. This is due to a change in the VxVM semantics for
importing a clone DiskGroup. The import command may fail with the error:
VxVM vxdg ERROR V-5-1-16514 Disk group mera_dg_fd: import failed:
DG import duplicate clone detected.
Please refer to system log for details.
Workaround: Perform the following steps for the fire drill to succeed:
Run the following script to clear the clone_disk flag on the fire drill devices:
/usr/sbin/vxdisk listtag |grep <DeviceGroup> |while read x y;
do echo disk: [$x]; vxdisk set $x clone=off; done
where FiredrillSG is the name of the fire drill service group, and system is the
system on which the fire drill service group must be brought online.
16
Release Notes
Known issues
Find the disks that correspond to the fire drill luns, and run the vxdisk path
command to find the corresponding VxVM disks.
Run the command vxdisk rm disk1 disk2 ... to delete the vmdisks
corresponding to the fire drill luns.
Run the appropriate SYMCLI command to split the devices from their sources
and to make the fire drill luns read-write enabled.
Some of the resources might not come online when a service group has
multiple SRDFSnap resources (3231314)
Symptom: When a service group has multiple SRDFSnap resources, some of the
resources might not come online.
The symcfg discover command locks the Symmetrix configuration database,
causing this command to fail for other agents.
Workaround: Run the following command to set the NumThreads attribute of the
SRDFSnap agent to 1:
$hatype -modify SRDFSnap NumThreads 1
The DiskGroup resource may not come online on an AIX LPAR with SYMAPI
servers configured (3683665)
Symptom: The DiskGroup resource may not come online on an AIX LPAR with
SYMAPI servers configured.
If the host on which the SRDF agent is running is an AIX LPAR, then SymapiServer
is required for managing the replication since the Gatekeeper devices cannot be
mapped to the LPARs. If the LPAR is rebooted while the underlying SRDF devices
are in R2 (secondary) mode, and the VCS service group is subsequently switched
to go online on the same LPAR, the DiskGroup resource may not go online. This
problem occurs only on the AIX operating system.
Workaround: Perform the following steps:
Find the disks that correspond to the SRDF R2 luns, and run the vxdisk path
command to find the corresponding VxVM disks.
Run the vxdisk rm disk1 disk2 command to delete the selected vmdisks.
17
Release Notes
Known issues
VxVM disk group might not get imported after failover to DR site in some
conditions (3235270)
Symptom: VxVM disk groups might not get imported after a failover to the DR site
in the following conditions:
If FlashCopy and Global Copy volumes are attached to the same host.
IBM SVCCopyServices
This section describes the known issues in the Symantec High Availability agent
for IBM SVCCopyServices.
The application service group fails to come online at the DR site after
running the Silver fire drill (3686814)
Symptom: After you run the Silver fire drill, the application service group fails to
come online at the disaster recovery site.
Workaround: After running the Silver fire drill for SVCCopyServices at the disaster
recovery site, the replication target is resynchronized from the primary when the
fire drill service group is taken offline. If a disaster happens before the
resynchronization is complete, restore the replication target from the snapshot.
After the resynchronization from the primary or restore from the snapshot is
complete, you must discard the snapshot to bring the application service group
online at the disaster recovery site.
18
Release Notes
Known issues
The Oracle Data Guard Broker resource comes online on the first RAC node,
but might fail to come online on the remaining RAC nodes (3612692)
Symptom: In an Oracle RAC configuration, the Oracle Data Guard Broker resource
comes online on the first RAC node, but might fail to come online on the remaining
RAC nodes. This issue occurs when the DGMGRL status on the primary database
is ERROR.
Workaround: Run the show configuration DGMGRL command and resolve the
error. You can then bring the resource online.
Oracle GoldenGate
This section describes the known issues in the Symantec High Availability agent
for Oracle GoldenGate.
19
Release Notes
Known issues
In the remote cluster, remove the lock on the trail file on the remote system. To
do this, temporarily rename the file and then revert to the original file name.
Restart the Replicat process in the remote cluster. To do this, run the
StopReplicat action function and then run the StartReplicat action function.
NetAppSnapMirror
This section describes the known issue in the Symantec High Availability agent for
NetAppSnapMirror.
The online operation of CSG fails while bringing the CSG online (3681398)
Symptom: While bringing the Composite Service Group (CSG) online, if the primary
cluster is not available, then the online operation of the CSG fails.
Workaround: Follow the below procedure after the Oracle Data Guard resource
has been configured. Oracle Data Guard resource is a part of the CSG. Assign an
additional role for the VCSOne client user to view the cluster objects and for proper
working of the Oracle Data Guard resource.
20
Release Notes
Known issues
Log on to the Policy Master (PM) server. Run the following command to list
the system users that are configured on the PM:
Policy_Master# hauser -list sys
Run the following command to display the object roles assigned to the VCS
One client user:
Policy_Master#hauser -value -sys
<vcsone_client_hostname>@VCSONE_USERS@<cluster_name> ObjectRoles
If the output is blank, then run the following command to set the object role
(ServerFarmObjectGuest) for the user:
Policy_Master# hauser -addrole
<vcsone_client_hostname>@VCSONE_USERS@<cluster_name>
ServerFarmObjectGuest
Documentation errata
This section provides a list of errors found in the documentation of the application,
database, and replication agents.
The documentation for the following section is missing in the Installing, upgrading,
and removing the agent chapter of a few agents.
Installing the agent in a Solaris 10 brand zone
To install the <agent name> in a brand zone on Solaris 10:
21
Release Notes
Limitations
To install the agent package in the non-global zone, run the following
command from the global zone:
# pkgadd -R zone-root/root -d . <agent package name>
Limitations
This section describes the limitations of agents in this release.
Documentation
The following sections contain useful information about the Symantec High
Availability Agent Pack documentation.
22
Release Notes
Documentation
Getting help
Visit http://www.symantec.com/business/support/assistance_care.jsp for product
assistance. Use the Knowledge Base search feature to access resources such as
TechNotes, product alerts, software downloads, hardware compatibility lists, and
our customer email notification service. If you encounter an error when using a
product, include the error number preceding the message when contacting Technical
Services. You can also use the error number to search for information in TechNotes
or documents on the Web site.
23