Vcs Notes 51sp1 Aix

8/21/2019 Vcs Notes 51sp1 Aix

1/66

Veritas Cluster Server

Release Notes

AIX

5.1 Service Pack 1


2/66

Veritas Cluster Server Release Notes

Thesoftware describedin this book is furnishedundera license agreement and may be used

only in accordance with the terms of the agreement.

Product version: 5.1 SP1

Document version: 5.1SP1.3

Legal Notice

Copyright 2013 Symantec Corporation. All rights reserved.

Symantec, the Symantec Logo, the Checkmark Logo, Veritas, Veritas Storage Foundation,

CommandCentral, NetBackup,EnterpriseVault,and LiveUpdateare 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 DOCUMENTATIONIS PROVIDED"ASIS" ANDALL 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 LEGALLYINVALID. SYMANTECCORPORATION SHALL NOTBELIABLEFORINCIDENTAL

OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,

PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINEDIN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

The LicensedSoftwareand Documentation are deemed to be commercial computer software

as defined in FAR12.212 andsubjectto restricted rights as defined in FARSection 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 theLicensedSoftware andDocumentation by the U.S.

Government shall be solely in accordance with the terms of this Agreement.


3/66

Symantec Corporation

350 Ellis Street

Mountain View, CA 94043

http://www.symantec.com
http://www.symantec.com/http://www.symantec.com/


4/66

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. Forexample,theTechnicalSupport 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 Telephone and/or Web-based support that provides rapid response and

up-to-the-minute information

Upgrade assurance that delivers software upgrades

Global support purchased on a regional business hours or 24 hours a day, 7

days a week basis

Premium service offerings that include Account Management Services

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.

Contacting Technical Support

Customers with a current support agreement may access Technical Support

information at the following URL:

www.symantec.com/business/support/contact_techsupp_static.jsp

Before contacting Technical Support, make sure you have satisfied the systemrequirements that are listed in your product documentation. Also, you should be

at the computer on which the problem occurred, in case it is necessary to replicate

the problem.

When you contact Technical Support, please have the following information

available:

Product release level
http://www.symantec.com/business/support/index.jsphttp://www.symantec.com/business/support/contact_techsupp_static.jsphttp://www.symantec.com/business/support/contact_techsupp_static.jsphttp://www.symantec.com/business/support/index.jsp


5/66

Hardware information

Available memory, disk space, and NIC information

Operating system Version and patch level

Network topology

Router, gateway, and IP address information

Problem description:

Error messages and log files

Troubleshooting that was performed before contacting Symantec

Recent software configuration changes and network changes

Licensing and registration

If your Symantec product requires registrationor a license key, accessourtechnical

support Web page at the following URL:

www.symantec.com/business/support/

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:

Questions regarding product licensing or serialization

Product registration updates, such as address or name changes

General product information (features, language availability, local dealers)

Latest information about product updates and upgrades

Information about upgrade assurance and support contracts

Information about the Symantec Buying Programs

Advice about Symantec's technical support options

Nontechnical presales questions

Issues that are related to CD-ROMs or manuals
http://www.symantec.com/business/support/http://www.symantec.com/business/support/http://www.symantec.com/business/support/http://www.symantec.com/business/support/


6/66

Support agreement resources

If you want to contact Symantec regarding an existing support agreement, please

contact the support agreement administration team for your region as follows:

[email protected] and Japan

[email protected], Middle-East, and Africa

[email protected] America and Latin America

Documentation

Product guides are available on the media in PDF format. Make sure that you are

using the current version of the documentation. The document version appears

on page 2 of each guide. The latest product documentation is available on the

Symantec website.

https://sort.symantec.com/documents

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:

[email protected]

For information regarding the latest HOWTO articles, documentation updates,

or to ask a question regarding product documentation, visit the Storage andClustering Documentation forum on Symantec Connect.

https://www-secure.symantec.com/connect/storage-management/

forums/storage-and-clustering-documentation

About Symantec Connect

Symantec Connect is the peer-to-peer technical community site for Symantecs

enterprise customers. Participants can connect and share information with other

product users, including creating forum posts, articles, videos, downloads, blogs

and suggesting ideas, as well as interact with Symantec product teams and

Technical Support. Content is rated by the community, and members receivereward points for their contributions.

http://www.symantec.com/connect/storage-management
mailto:[email protected]:[email protected]:[email protected]://sort.symantec.com/documentsmailto:[email protected]://www-secure.symantec.com/connect/storage-management/forums/storage-and-clustering-documentationhttps://www-secure.symantec.com/connect/storage-management/forums/storage-and-clustering-documentationhttp://www.symantec.com/connect/storage-managementhttp://www.symantec.com/connect/storage-managementhttps://www-secure.symantec.com/connect/storage-management/forums/storage-and-clustering-documentationhttps://www-secure.symantec.com/connect/storage-management/forums/storage-and-clustering-documentationmailto:[email protected]://sort.symantec.com/documentsmailto:[email protected]:[email protected]:[email protected]


7/66

Release Notes

This document includes the following topics:

About this document

Component product release notes

About Veritas Cluster Server

About Symantec Operations Readiness Tools

Important release information

Changes in version

VCS system requirements

Features no longer supported

Fixed issues

Known issues

Software limitations

Documentation errata

Documentation

About this documentThis document provides important information about Veritas Cluster Server (VCS)

version 5.1 SP1 for AIX. Review this entire document before you install VCS.

The information in the Release Notes supersedes the information provided in the

product documents for VCS.


8/66

This is Document version: 5.1SP1.3 of the Veritas Cluster ServerRelease Notes.

Before you start, ensure that you are using the latest version of this guide. The

latest product documentation is available on the Symantec Web site at:

http://www.symantec.com/business/support/overview.jsp?pid=15107

Component product release notesIn addition to reading thisRelease Notes document, review the component product

release notes before installing the product.

Product guides are available at the following location in PDF formats:

/product_name/docs

Symantec recommends copying the files to the /opt/VRTS/docs directory on your

system.

This release includes the following component product release notes:

Veritas Storage Foundation Release Notes(5.1 SP1)

About Veritas Cluster ServerVeritasCluster Server by Symantec (VCS) is a clustering solution that eliminates

downtime, facilitates server consolidation and failover, and effectively manages

a wide range of applications in heterogeneous environments.

About VCS agents

VCS bundled agents manage a clusters key resources. The implementation and

configuration of bundled agents vary by platform.

For more information about bundled agents, refer to the Veritas Cluster Server

Bundled AgentsReferenceGuide.

The Veritas High Availability Agent Pack gives you access to agents that provide

high availability for various applications, databases, and third-party storage

solutions. The Agent Pack is available through SymantecTM

Operations ReadinessTools (SORT).

For more information about SORT, seehttps://sort.symantec.com/home.

For information about agents under development and agents that are available

through Symantecconsulting services, contact yourSymantecsales representative.

Release NotesComponent product release notes

8
http://www.symantec.com/business/support/overview.jsp?pid=15107https://sort.symantec.com/homehttps://sort.symantec.com/homehttp://www.symantec.com/business/support/overview.jsp?pid=15107


9/66

VCS provides a framework that allows for the creation of custom agents. Create

agents in situations where the Veritas High Availability Agent Pack, the bundled

agents, or the enterprise agents do not meet your needs.

For more information about the creation of custom agents, refer to the VeritasCluster ServerAgent Developer's Guide. You can also request a custom agent

through Symantec consulting services.

About compiling custom agents

Custom agents developed in C++ must be compiled using the IBM C for AIX

Compiler Version 7.0. Use the -brtl flag for runtime linking with the framework

library.

About Symantec Operations Readiness ToolsSymantecOperations Readiness Tools (SORT) is a set of Web-based tools and

services that lets you proactively manage your Symantec enterprise products.

SORT automates and simplifies administration tasks, so you can manage your

data center more efficiently and get the most out of your Symantec products.

SORT lets you do the following:

Collect, analyze, and report on server configurations across UNIX or Windows

environments. You can use this data to do the following:

Assess whether your systems are ready to install or upgrade Symantec

enterprise products

Tune environmental parameters so you can increase performance,

availability, and use

Analyze your current deployment and identify the Symantec products and

licenses you are using

Upload configuration data to the SORT Web site, so youcanshare information

with coworkers, managers, and Symantec Technical Support

Compare your configurations to one another or to a standard build, so you can

determine if a configuration has "drifted"

Search for and download the latest product patches

Get notifications about the latest updates for:

Patches

Hardware compatibility lists (HCLs)

Array Support Libraries (ASLs)

Release NotesAbout Symantec Operations Readiness Tools


10/66

Array Policy Modules (APMs)

High availability agents

Determine whetheryour Symantec enterprise product configurations conformto best practices

Search and browse the latest product documentation

Look up error code descriptions and solutions

Note:Certain features of SORT are not available for all products.

To access SORT, go to:

http://sort.symantec.com

Important release information The latest product documentation is available on the Symantec Web site at:

http://www.symantec.com/business/support/overview.jsp?pid=15107

For important updates regarding this release, review the Late-Breaking News

TechNote on the Symantec Technical Support website:

http://entsupport.symantec.com/docs/334998

For the latest patches available for this release, go to:

http://sort.symantec.com/

Changes in versionThis section lists the changes for Veritas Cluster Server.

Changes related to the installation

The product installer includes the following changes.

Rolling upgrade support

To reduce downtime, the installer supports rolling upgrades. A rolling upgrade

requires little or no downtime. A rolling upgrade has two main phases. In phase

1, the installer upgrades kernel packages on a subcluster. In phase 2, non-kernel

packages are upgraded.

All high availability products support a rolling upgrade. You can perform a rolling

upgrade from 5.1 or from any RPs to the current release.

Release NotesImportant release information

10
http://sort.symantec.com/http://www.symantec.com/business/support/overview.jsp?pid=15107http://entsupport.symantec.com/docs/334998http://sort.symantec.com/http://sort.symantec.com/http://entsupport.symantec.com/docs/334998http://www.symantec.com/business/support/overview.jsp?pid=15107http://sort.symantec.com/


11/66

You can perform a rolling upgrade using the script-based or Web-based installer.

See theVeritas Cluster Server InstallationGuide.

Installer-related changes to configure LLT private links, detectaggregated links, and configure LLT over UDP

For all high availability products, the installer provides the following new features

in this release to configure LLT private links during the VCS configuration:

The installer detects and lists the aggregated links that you can choose to

configure as private heartbeat links.

The installer provides an option to detect NICs on each system and network

links, and sets link priority to configure LLT over Ethernet.

The installer provides an option to configure LLT over UDP.See theVeritas Cluster Server InstallationGuide.

Installer changes related to I/O fencing configuration

In VCS 5.1 or SFHA 5.1, the installer started I/O fencing in disabled mode even if

you had not chosen to configure I/O fencing. In 5.1 SP1, if you did not choose to

configure I/O fencing during the product configuration, then the installer does

not start I/O fencing in disabled mode in VCS and SFHA clusters.

However, if you upgrade VCS or SFHA from 5.1 to 5.1SP1, the installer retains

the I/O fencing configuration from the previous version.

Installer supports configuration of non-SCSI3 based fencing

You cannow configure non-SCSI3 based fencing for VCS clusterusing the installer.


Web-based installer supports configuring VCS cluster in securemode

You can now configure the VCS cluster in secure mode using the Web-based

installer.


The installer can copy CPI scripts to any given location using-copyinstallscripts option

The installer can copy CPI scripts to given location using -copyinstallscripts

option. This option is used when customers install SFHA products manually and

Release NotesChanges in version


12/66

require CPI scripts stored on the system to perform product configuration,

uninstallation, and licensing tasks without the product media.


Web-based installer supports configuring disk-based fencingfor VCS

You can now configure disk-based fencing for the VCSclusterusing theWeb-based

installer.


The Web-based installer supports adding nodes

The Web-based installer has increased parity with the script-based installer. Itnow supports the ability to add nodes to a cluster. It also supports configuring

secure clusters and fencing configuration.

The installer provides automated, password-less SSHconfiguration

When you use the installer, it enables SSH or RSH communication among nodes.

It creates SSH keys and adds them to the authorization files. After a successful

completion, the installer removes the keys and system names from the appropriate

files.

When you use the installer for SSH communications, meet the following

prerequisites:

The SSH (or RSH) daemon must be running for auto-detection.

You need the superuser passwords for the systems where you plan to install

VCS.

The installer can check product versions

You can use the installer to identify the version (to the MP/RP/SP level depending

on the product) on all platforms. Activate the version checker with ./installer

-version system_name.

Depending on the product, the version checker can identify versions from 4.0

onward.

Upgrade changes

The following lists the upgrade changes in this release.


12


13/66

Supported paths for VCS upgrades that do not require a nodereboot

When using the installer program to perform any of the typical upgrade listed in

the following upgrade matrix, a node reboot is not required.

Upgrade matrix:

5.0MP3 to 5.1SP1

5.1 to 5.1 SP1

5.1RP1 to 5.1SP1

5.1RP2 to 5 .1SP1

For supported upgrade matrix, refer to theVeritas Cluster Server Installation

Guide.

Upgrades that follow any other upgrade paths require a reboot.

Packaging updates

The following lists package changes in this release.

VRTScutil package is no longer supported

The VRTScutil package is obsolete. VCS 5.1SP1 does not support VRTScuitl

package. If VRTScutil package is already installed, the VCS installer removes this

package during product upgrades.

New VRTSamf package

VRTSamf is a new package introduced in this release. The Asynchronous

Monitoring Framework (AMF) module, along with the VCS Agent Framework

(AGFW) and resource agents provides a way to avoid polling for resource state

changes. TheAMF module allows the agent to register whichresources to monitor

and when to wait. The module provides the agent with immediate notification so

that action can be taken at the time of the event. AMF enables the VCS agents to

monitor a large number of resources with a minimal effect on performance.

VRTSacclib package is no longer shipped with VCS 5.1SP1

The VRTSacclib package was available with VCS 5.1. The package is not shipped

with VCS 5.1SP1. The latest VRTSacclib package can be accessed from the Agent

Pack release.



14/66

Changes to the VCS engine

The HAD can exchange messages up to 64KB size

The size of the messages that HAD supports is increased from 16KB to 64KB. The

messages canbe exchangedbetween differentHADprocesses (running on different

systems) or between CLI and HAD processes.

Refer to the following list for the message, object, attribute, and attribute values:

1. Maximum message size = 64KB

2. Maximum object name size = 1KB

3. Maximum attribute name size = 1KB

4. Maximum scalar attribute value size = 4KB

5. Maximum single key (of key-value pair) size = 4KB

6. Maximum single value (of key-value pair) size = 4KB

7. Maximum size of single element of vector or keylist pair = 4KB

8. Maximum user Name size = 1KB

9. Maximum password size = 255b

10. Maximum password encrypted size = 512b

Note:Points 2 through 10 were already supported in 5.1 release.

CPUThresholdLevel attribute is editable

You can configure the Critical, Warning, Note and Info levels. The values must

be in descending order.

For Example: {Critical = 100, Warning = 90, Note = 90, Info = 80} is correct value;

whereas {Critical = 100, Warning = 90, Note = 100, Info = 80} is not correct value.

Support for intelligent monitoring of VCS resources using IMF

VCS now supports intelligent resource monitoring in addition to poll-based

monitoring. Intelligent Monitoring Framework (IMF) is an extension to the VCS

agent framework. You canenable or disable the intelligent monitoring functionality

of VCS agents as needed.

The benefits of intelligent monitoring over poll-based monitoring are as follows:

Faster notification of resource state changes.


14


15/66

Reduction in VCS system utilization which enables VCS to effectively monitor

a large number of resources.

See theVeritas Cluster ServerAdministrator'sGuidefor more information.

The following agents are IMF-aware in VCS 5.1 SP1:

Mount

Process

Application

Oracle

Netlsnr

CFSMount

CVMVxconfigd

CFSfsckd

New attributes

The following sections describes the attributes introduced in VCS 5.1SP1, VCS

5.1, and VCS 5.0MP3.

Attributes introduced in VCS 5.1SP1

Application Agent attributes

EnvFile: This attribute specifies the environment file that must be sourced

before running StartProgram, StopProgram, MonitorProgram or CleanProgram.

UseSUDash: This attribute specifies that the agent must runsu - user -c

orsu user -c while runningStartProgram,

StopProgram,MonitorProgramorCleanProgram.

RemoteGroup agent attribute

ReturnIntOffline: This attribute can take one of the following three values.

These values are not mutually exclusive and can be used in combination with

one another. You must set IntentionalOffline attribute to 1 for the

ReturnIntOffline attribute to work.

RemotePartial: Makes RemoteGroup resource to return IntentionalOffline

when the remote service group is in ONLINE|PARTIAL state.

RemoteOffline: Makes RemoteGroup resource to return IntentionalOffline

when the remote service group is in OFFLINE state.



16/66

RemoteFaulted: Makes RemoteGroup resourceto return IntentionalOffline

when the remote service group is in OFFLINE|FAULTED state.

DiskGroup agent attribute

Reservation: Determines if you want to enable SCSI-3 reservation. For more

information, please refer toBundled AgentsReferenceGuide.

In order to support SCSI-3 disk reservation, you must be sure that the disks

are SCSI-3 compliant. Since all the disks are not SCSI-3 compliant, reservation

commandsfail on such disk groups. TheReservation attributehelps in resolving

this issue. The Reservation attributecan have one of the following threevalues:

ClusterDefault: The disk group is imported with or without SCSI-3

reservation, based on the cluster-level UseFence attribute.

SCSI3: The disk group is imported with SCSI-3 reservation.

NONE: The disk group is imported without SCSI-3 reservation. The agent

does not care about the cluster-level UseFence attribute.

Note:This attribute must be set to NONE for all resources of type DiskGroup

in case of non-SCSI-3 fencing.

IPMultiNICB agent attribute

Options: Value of this attribute is used as the option for the ifconfig command.

For example, if value of this attribute is set tometric 2 then metric 2 option

is set on the interface while bringing IPMultiNICB resource online.

LVMVG agent attribute

ModePermSyncFlag: This attribute is added to get the mode and permissions

without activating the volume group. The default value of ModePermSyncFlag

is 1. To skip the activation of the volume group before before preserving mode

and permissions, set the value of ModePermSyncFlag attribute to 0 (zero).

NFSRestart agent attribute

Lower: Defines the position of the NFSRestart resource in the service group.

The NFSRestart resource below the Share resource needs a value of 1. TheNFSRestart resource on the top of the resource dependency tree has a Lower

attribute value of 0.

RVGPrimary agent attribute

BunkerSyncTimeOut: The timeout value in seconds that signifies the amount

of time that a SecondaryRVG can wait for the synchronization from the bunker

host to complete before taking over the Primary role.


16


17/66

NotifierSourceIP agent attribute

NotifierSourceIP: : Lets you specify the interface that the notifier must use to

send packets. This attribute is string/scalar. You must specify an IP address

that is either DNS resolvable or appears in the/etc/hostsfile.

SambaServer agent attributes

PidFile: The absolute path to the Samba daemon (smbd) Pid file. This attribute

is mandatory if you are using Samba configuration file with non-default name

or path.

SocketAddress: The IPv4 address where the Samba daemon (smbd) listens for

connections. This attribute is mandatory if you are configuring multiple

SambaServer resources on a node.

ASMInst agent attributes

MonitorOption: Enables or disables health check monitoring.

NetBios agent attribute

PidFile: The absolute path to the Samba daemon (nmbd) PidFile. This attribute

is mandatory if you are using Samba configuration file with non-default name

or path.

Sybase agent attribute

Run_ServerFile: The attribute specifies the location of the RUN_SERVER file

for a Sybase instance. If this attribute is not specified, the default location of

this file is accessed while starting Sybase server instances.

Cluster-level attributes

AutoAddSystemToCSG: Indicates whether the newly joined or added systems

in the cluster become a part of the SystemList of the ClusterService service

group if the service group is confirmed. The value 1 (default) indicates that

the new systems are added to SystemList of ClusterService. The value 0

indicates that the new systems are not added to SystemList of ClusterService.

CounterMissTolerance: If GlobalCounter does not update in

CounterMissTolerance intervals of CounterInterval, then VCS reports about

this issue depending on the CounterMissAction (that is, CounterMissTolerance* CounterInterval) time has elapsed since last update of GlobalCounter then

CounterMissAction is performed. The default value of CounterMisstolerance

is 20.

CounterMissAction: The action mentioned in CounterMissAction is performed

whenever the GlobalCounter is not updated for CounterMissTolerance intervals

of CounterInterval.

The two possible values of CounterMissAction are LogOnly and Trigger.



18/66

LogOnly logs the message in Engine Log and SysLog. Trigger invokes a trigger

which has a default action of collecting the comms tar file. The Default value

of Trigger is LogOnly.

PreferredFencingPolicy: The I/O fencingrace policy to determine the survivingsubcluster in the event of a network partition. Valid values are Disabled,

System, or Group.

Disabled: Preferred fencing is disabled.The fencing driverfavors the subcluster

with maximum number of nodes during the race for coordination points.

System: Thefencing drivergives preference to the system that is more powerful

than others in terms of architecture, number of CPUs, or memory during the

racefor coordinationpoints. VCS usesthe system-levelattribute FencingWeight

to calculate the node weight.

Group: The fencing driver gives preference to the node with higher priority

service groups during therace forcoordination points. VCS uses thegroup-levelattribute Priority to determine the node weight.

Resource type attributes

IMF: Determines whether the IMF-aware agent must perform intelligent

resource monitoring.

It is an association attribute with three keys Mode, MonitorFreq, and

RegisterRetryLimit.

Mode: Defines whether to perform IMF monitoring based on the state of

the resource. Mode can take values 0, 1, 2, or 3. Default is 0.

MonitorFreq: Specifies the frequency at which the agent invokes themonitor agent function. Default is 1.

RegisterRetryLimit: Defines the maximum number of times the agent

attempts to register a resource. Default is 3.

IMFRegList: Contains a list of attributes. The values of these attributes are

registered with the IMF module for notification. If an attribute defined in

IMFRegList attribute is changed then the resource, if already registered, is

unregistered from IMF. If IMFRegList is not defined and if any attributedefined

in ArgList is changed the resource is unregistered from IMF.

AlertOnMonitorTimeouts: Indicatesthe number of consecutive monitor failuresafter which VCS sends an SNMP notification to the user.

WPAR agent attribute

ResourceSet: A resource set is used to define a subset of processors in the

system. If a resource set is specified for a workload partition, it can use the

processors within the specified resource set only. The value of the ResourceSet

attribute is the name of the resource set created using themkrsetcommand.


18


19/66

If set, the agent configures the WPAR to use only the resource set specified

by this attribute.

WorkLoad: Allows modification of resource control attributes of WPAR -

shares_CPU and shares_memory. This attribute has two keys, CPU and MEM.The key CPU is used to specify the number of processor shares that are available

to the workload partition. The key MEM is used to specify the number of

memory shares that are available to the workload partition.

Attributes introduced in VCS 5.1

VCS 5.1 introduced the following new attributes. See the Veritas Cluster Server

Administrators Guidefor more information.

Resource type attributes:

ContainerOpts: Specifies the behavior of the agent in a container environment.

CleanRetryLimit: Number of times to retry the clean function before moving

a resource to ADMIN_WAIT state.

EPClass: Enables you to control the scheduling class for the agent functions

(entry points) except the online entry point.

EPPriority: Enables you to control the scheduling priority for the agent

functions (entry points) except the online entry point.

FaultPropogation: Specifies if VCS should propagate the fault up to parent

resources and take the entire service group offline when a resource faults.

OnlineClass: Enables you to control the scheduling class for the online agent

function (entry point).

OnlinePriority: Enables you to control the scheduling priority for the online

agent function (entry point).

Service group level attribute:

ContainerInfo: Specifies information about the container that the service group

manages.

Cluster level attributes:

CID: The CID provides universally unique identification for a cluster.

DeleteOnlineResource: Defines whether you can delete online resources.

HostMonLogLvl: Controls the behavior of the HostMonitor feature.

Attributes introduced in VCS 5.0 MP3

VCS 5.0MP3 introduced the following attributes.



20/66

Resource type attributes:

FaultPropagation: Specifies if VCS should propagate the fault up to parent

resources and take the entire service group offline when a resource faults.

AgentFile: Complete name and path of the binary for an agent. Use when the

agent binaries are not installed at their default locations.

AgentDirectory: Complete path of the directory in which the agent binary and

scripts are located. Usewhen the agent binaries arenot installedat their default

locations.

Cluster level attributes:

DeleteOnlineResource: Defines whether you can delete online resources.

HostMonLogLvl: Controls the behavior of the HostMonitor daemon. Configure

this attribute when you start the cluster. You cannot modify this attribute ina running cluster.

EngineShutdown: Provides finer control over the hastop command.

BackupInterval:Time periodin minutes after whichVCSbacks up configuration

files.

OperatorGroups: List of operating system user account groups that have

Operator privileges on the cluster.

AdministratorGroups: List of operating system user account groups that have

administrative privileges on the cluster.

Guests: List of users that have Guest privileges on the cluster.

System level attributes:

EngineVersion: Specifiesthe major, minor, maintenance-patch, and point-patch

version of VCS.

Service group level attributes:

TriggerResFault: Defines whether VCS invokes the resfault trigger when a

resource faults.

AdministratorGroups: List of operating system user account groups that have

administrative privileges on the service group. OperatorGroups: List of operating system user account groups that have

Operator privileges on the service group.

Guests: List of users that have Guest privileges on the service group.

Changes to bundled agents

This section describes changes to the bundled agents for VCS.


20


21/66

New bundled agent

VolumeSet agent: The VolumeSet agent brings online, takes offline, and

monitors a Veritas Volume Manager (VxVM) volume set. Use this agent to

make a volume set highly available.

Support for Veritas dynamic multi-pathing

The following agent supports Veritas Dynamic Multi-Pathing (DMP):

LVMVG agent

About the ReturnIntOffline attribute of RemoteGroup agent

The ReturnIntOffline attribute can take one of three values: RemotePartial,

RemoteOffline, and RemoteFaulted.These values are not mutually exclusive and can be used in combination with one

another. You must set the IntentionalOffline attribute of RemoteGroup resource

to 1 for the ReturnIntOffline attribute to work.

About the RemotePartial option

Select the RemotePartial value of this attribute when you want the RemoteGroup

resource to return an IntentionalOffline when the remote service group is in an

ONLINE | PARTIAL state.

About the RemoteOffline optionSelect the RemoteOffline value of this attribute when you want the RemoteGroup


OFFLINE state.

About the RemoteFaulted option

Selectthe RemoteFaulted value of this attribute when youwant theRemoteGroup


OFFLINE | FAULTED state.

Configuring RemoteGroup resources in parallel service groupsWhen a RemoteGroup resource is configured inside parallel service groups, it can

come online on all the cluster nodes,including the offline nodes. Multiple instances

of the RemoteGroup resource on cluster nodes can probe the state of a remote

service group.



22/66

Note:The RemoteGroup resource automatically detects whether it is configured

for a parallel service group or for a failover service group. No additional

configuration is required to enable the RemoteGroup resource forparallel service

groups.

A RemoteGroup resource in parallel service groups has the following

characteristics:

The RemoteGroup resource continues to monitor the remote service group

even when the resource is offline.

The RemoteGroup resource does not take the remote service group offline if

the resource is online anywhere in the cluster.

After an agent restarts, the RemoteGroup resource does not return offline if

the resource is online on another cluster node.

The RemoteGroup resource takes the remote service group offline if it is the

only instance of RemoteGroup resource online in the cluster.

An attempt to bring a RemoteGroup resource online has no effect if the same

resource instance is online on another node in the cluster.

Changes to SambaServer and NetBios agents

The SambaServer and NetBios agents contain the following changes:

VCS SambaServer and NetBios agents now support multiple resource instances

on a node.

These agents now support non default Samba configuration file and pid file

names.

For more information about bundled agents, refer to the Veritas Cluster Server

Bundled AgentsReferenceGuide.

Changes to Disk Group agents

The clean entry point in AIX can produce the system dump.

The clean entry point in AIX can now forcefully produce a system dump when asystem fails over to another node. To investigate the system failure, the system

dump is produced using the following command:# sysdumpstart -p


22


23/66

Changes to database agents

Changes to the Oracle agent

Oracle agent now supports IMF monitoring.

Changes to the Sybase agent

The Sybase agent supports a new optional attribute Run_ServerFile. The

attribute specifies the location of the RUN_SERVER file for a Sybase instance.

If this attribute is not specified, the default location of the RUN_SERVER file

is accessed while starting Sybase server instances.

The VCS agent binaries for Sybase are now a part of VRTSvcsea package. This

package also includes the VCS agent binaries for DB2 and Oracle.

The agent supports a new attribute WaitForRecovery. If this attribute is

enabled, during the online function, the agent waits until recovery is completed

and all databases that can be made online are brought online.

Changes to LLTThis release includes the following new features and changes to LLT:

LLT startup time through the LLT init script is now optimized to use a constant

time. LLT takes less than 16 seconds to start irrespective of the number of

links specified in /etc/llttab file.In the previous releases, LLT took around (5 * number_of_links_specified

_in_the_/etc/llttab_file) seconds to start.

The lltstat command includes the following new options:

lltstat -nv active

This command filters the output oflltstat -nvto display the status of

only the active nodes in the cluster.

lltstat -nv configured

This command filters the output oflltstat -nvto display the status of

only the configured nodes in the cluster. Configured nodes include activenodes and any additional nodes which are listed in the /etc/llthosts file.

See thelltstatmanual page for more information.

Support for different link speeds for LLT links

LLT now removes the restriction to use private NICs with same media speed.

You can now use different media speed for the private NICs and configure the

NICs with lesser speed as low-priority links to enhance LLT performance.



24/66

Support for destination-based load balancing

LLT now also provides destination-based load balancing where the LLT link

is chosen based on thedestinationnode id and theport. With destination-based

load balancing, LLT sends all the packets of a particular destination on a link.See theVeritas Cluster Server InstallationGuideand theVeritas Cluster Server

Administrator's Guidefor more details.

Changes to GABThis section lists the new features and changes related to GAB in this release.

GAB logging daemon

GAB implements a distributed network protocol. For situations when GAB

decides to take the drastic action of killing its userland client process or

panicking a node to resolve an issue, data from the affected node alone maynot suffice for a meaningful support analysis. The new gablogd daemon

attempts to address this issue. GAB starts this daemon by default at GAB

configuration time.

See theVeritas Cluster ServerAdministrator'sGuidefor more information.

Changes to I/O fencing

This section covers the new features and changes related to I/O fencing in this

release.

Support for preferred fencing

Traditional fencing prevents a split-brain condition by allowing only one of

multiple sub-clusters to continue its operation in case a network partition disrupts

regular communication between nodes. The preferred fencing feature gives

preference to one sub-cluster over other sub-clusters in determining the surviving

sub-cluster. This preference is based on factors such as which of the sub-clusters

is running higher priority applications or the total importance of nodes which

form that sub-cluster or both.

See theVeritas Cluster Server InstallationGuideand theVeritas Cluster Server


Support for Non-SCSI3 fencing

In environments that do not support SCSI-3, non-SCSI-3 fencing provides

reasonable data protection by causing the winning side to delay by a configurable

amount (loser_exit_delay, default 55). Additionally, Symantec has enhanced the

fencing component to help panic the losing side quickly. Together, these


24


25/66

enhancements help narrow down the window of potential data corruption

drastically.

See theVeritas Cluster Server InstallationGuideand theVeritas Cluster Server


Enhancements to server-based fencing

This release includes the following enhancements and new features related to

server-based fencing:

Single CP-server based fencing

Support to use a single highly available CP server that is configured on an

SFHAcluster to provide server-based fencing support for multiple application

clusters

Support for CP server on AIX and HP-UX

CP server now supports AIX and HP-UX in addition to Linux and Solaris

operating systems.

Support to migrate between fencing modes when the clusteris running

The vxfenswap utility now supports migrating between disk-based and

server-based fencing configurations in a cluster that is running.

See theVeritas Cluster ServerAdministrator'sGuidefor more details.

Changes to global clustering

VCS global clustering monitors and manages the replication jobs and clusters at

each site. In the event of a site outage, global clustering controls the shift of

replication roles to the Secondary site, bring up the critical applications and

redirects client traffic from one cluster to the other.

Before Release 5.1SP1, if there was a disaster at the Primary site or a network

disruption, the applications were taken offline on the original Primary and failed

over to the Secondary. When the original Primary returned or the network

disruption was corrected, you had the following options:

Manually resynchronize the original Primary with the data from the new

Primary, once the original Primary comes back up. The applications are only

active on the new Primary site.

Automatically resynchronize the original Primary with the data from the new

Primary, once the original Primary comes back up. The applications are only

active on the new Primary site.



26/66

Beginning in Release 5.1SP1, you have a third option. Applications can be active

on both the original Primary and Secondary sites. After the original Primary

returns or the network disruption is corrected, you have the option of specifying

which site is the Primary going forward. This option is called the primary-electfeature, and it is enabled through the VCS global clustering.

The key difference between the primary-elect feature and the other options is

that if a network disruption occurs, applications continue to run on the Primary

site and they are also failed over to the Secondary. This feature lets you maintain

application availability on both sites while the network is down.

VCS system requirementsThis section describes system requirements for VCS.

The following information applies to VCS clusters. The information does not apply

to SF Oracle RAC installations.

VCS requires that all nodes in the cluster usethe same processor architecture and

run the same operating system.

All nodes in the cluster must run the same VCS version. Each node in the cluster

may run a different version of the operating system, as long as the operating

system is supported by the VCS version in the cluster.

See Hardware compatibility liston page 26.

See

Supported AIX operating systems

on page 26.

Hardware compatibility list

The compatibility list contains information about supported hardware and is

updated regularly. For the latest information on supported hardware go to the

following URL:

http://www.symantec.com/docs/TECH74012

Before installing or upgrading Veritas Cluster Server, review the current

compatibility list to confirm the compatibility of your hardware and software.

Supported AIX operating systems

This section lists the supported operating systems for this release of Veritas

products.

Product installation scripts verify the required update levels. The installation

process terminates if the target systems do not meet the maintenance level

requirements.

Release NotesVCS system requirements

26
http://www.symantec.com/docs/TECH74012http://www.symantec.com/docs/TECH74012


27/66

The minimum system requirements for this release are as follows:

For Power 6 or earlier processors at one of the following levels:

AIX 6.1 TL2

AIX 5.3 at one of the following levels:

TL7 with SP6 or later

TL8 with SP4 or later

For Power 7 processors at one of the following levels:

AIX 6.1 TL5 with Service Pack 1 or later

AIX Version 5.3 executing in POWER6 or POWER6+ compatibility at the

following levels:

TL11 with Service Pack 2 or later

TL10 with Service Pack 4 or later

For important updates regarding this release, review the Late-Breaking News

TechNote on the Symantec Technical Support website:

http://entsupport.symantec.com/docs/334998

Supported software for VCSVCS supports the following volume managers and file systems:

Logical Volume Manager (LVM)

Journaled File System (JFS) and Enhanced Journaled File System (JFS2) on

LVM

Veritas StorageFoundation (SF): Veritas Volume Manager (VxVM) withVeritas

File System (VxFS)

VCS 5.1 SP1 supports the following versions of SF:

SF 5.1 SP1

VxVM 5.1 SP1 with VxFS 5.1 SP1

SF 5.1

VxVM 5.1 with VxFS 5.1

Note:VCS supports the previous version of SF and the next version of SF to

facilitate product upgrades.

Release NotesVCS system requirements
http://entsupport.symantec.com/docs/334998http://entsupport.symantec.com/docs/334998


28/66

Supported VCS agents

Table 1-1lists the agents for enterprise applications and the software that the

agents support.

Table 1-1 Supported software for the VCS agents for enterprise applications

AIX versionApplication

version

ApplicationAgent

AIX 5.3, AIX 6.18.1, 8,2, 9.1,

9.5, 9.7

DB2 Enterprise

Server Edition

DB2

AIX 5.3, AIX 6.111gR1,

10gR2, 11gR2

OracleOracle

AIX 5.3, AIX 6.112.5.x, 15.xSybase AdaptiveServer Enterprise

Sybase

See theVeritas Cluster Server InstallationGuidefor the agent for more details.

For a list of the VCS application agents and the software that the agents support,

see theVeritas Cluster Server Agents Support Matrixat Symantec website.

Features no longer supported

No longer supported agents and componentsVCS no longer supports the following:

Configuration wizards

Disk agent

ServiceGroupHB agent.

This release does not support disk heartbeats. Symantec recommends using

I/O fencing.

VRTSWebApp

Oracle 8.0.x, Oracle 8.1.x, and Oracle 9i - not supported by the updated Oracle

agent.

VCS documentation package (VRTSvcsdc)

The VCS documentation package (VRTSvcsdc) is deprecated. The software

disc contains the documentation for VCS in Portable Document Format (PDF)

in thecluster_server/docsdirectory.

Release NotesFeatures no longer supported

28
http://www.symantec.com/business/products/agents_options.jsp?pcid=1019&pvid=20_1http://www.symantec.com/business/products/agents_options.jsp?pcid=1019&pvid=20_1


29/66

Symantec recommends copying pertinent documents from the disc to your

system directory /opt/VRTS/docs for reference.

hahbsetup tool. This tool is removed as no supported feature requires this

tool.

VRTScutil package. This package is no longer supported.

Fixed issuesThis section covers the incidents that are fixed in this release.

This release includes fixed issues from the 5.1 Service Pack (SP) 1 Rolling Patch

(RP) 2 release. For the list of fixed issues in the 5.1 SP1 RP2 release, see the Veritas

Storage Foundation and High Availability Solutions 5.1 SP1 RP2 Release Notes.

See the corresponding Release Notes for a complete list of fixed incidents related

to that product.

LLT, GAB, and I/O fencing fixed issues

Table 1-2lists the fixed issues for LLT, GAB, and I/O fencing.

Table 1-2 LLT, GAB, and I/O fencing fixed issues

DescriptionIncident

[GAB] In a large cluster, cascaded lowest node failures result in GAB panicduring sequence space recovery.

1908938

[GAB] Prevent 'gabconfig -c' while port 'a' is in the middle of iofence

processing.

1840826

[LLT] LLT unload may fail but should not cause hang/panic on AIX when

clients are registered.

2096584

[LLT] Removing the LLT links from a single node in a four-node cluster

causes other nodes to panic.

1861439

1849527

[LLT] The dlpiping utility exits with an error similar to "dlpiping: sendECHO_REQ failed."

2066020

[LLT] The hastart command fails to start HAD on one of the nodes with

message GabHandle::open failed errno = 16 in syslog after HAD is stopped

on all the nodes in the cluster simultaneously.

2005045

[LLT] The lltconfig -T query command displays a partially incorrect

output

1859023

Release NotesFixed issues


30/66

Table 1-2 LLT, GAB, and I/O fencing fixed issues(continued)

DescriptionIncident

[Fencing] The vxfenswap and the vxfentsthdw utilities fail when rsh orssh communication is not set to the same node.

1846387

2084121

[Fencing] The vxfentsthdw utility should detect storage arrays which

interpret NULL keys as valid for registrations/reservations.

1922413

[Fencing] The vxfenswap utility has an incorrect usage message for -n

option

1847517

[Fencing]The vxfentsthdw utility uses scpto communicate with the local

host.

1992560

[Fencing] The vxfenclearpre utility displays error messages1512956

[VxCPS] For a four-node cluster,the installer fails to configure server-based

fencing whichuses three CP servers as itscoordination points. The process

fails while registering the CP clients on the third CP server.

2143933

[VxCPS] Need strict host name matching in coordination point installer.2151166

Bundled agents fixed issues

Table 1-3lists the fixed issues for bundled agents.

Table 1-3 Bundled agents fixed issues

DescriptionIncident

The index number of the virtual interfaces

changes after a failover. As a result

applications using the interfaces may face

communication failure.

251704

Application agent does not pass the value of

CleanReason to the script that the Agent

executes as per thevalue of the CleanProgramattribute.

252354

In a frozen local service group, if a resource

goes offline outside VCS control, a

RemoteGroup resource also goes offline.

2001039


30


31/66

Table 1-3 Bundled agents fixed issues(continued)

DescriptionIncident

The OS determines the interface that thenotifier uses to send packets. The user must

be optionally able to specify the interface.

This is an enhancement.

2019904

If you upgrade to VCS 5.1, Application

resources may go to the FAULTED state.

2045972

A resource fails to come online if the number

of disks that you add to the volume group are

more than the number of disks that the

volume group already has.

2111972

VCS engine fixed issues

Table 1-4lists the fixed issues for VCS engine.

Table 1-4 VCS engine fixed issues

DescriptionIncident

If the OnlineRetryLimit and PreOnline attributes are set for

a group, then the group does not fail over in case of a fault.

254693

At unfreeze of a failover group, VCS does not evaluate the

group for Concurrency violation.

970971

A global group goes online on a remote site despite a

concurrency violation. This behavior is observed if a related

group resource goes intentionally online on the remote site.

1074707

VCS must log an alert message to increase the value of the

ShutdownTimeout attribute on a multi-CPU computer.

1472734

If the GlobalCounter attribute does not increase at the

configured interval, VCS must report the failure.

1634494

When a parent group completely faults in a system zone, an

online-local-hard (OLH) child group fails over to another

system. This behavior is observed only if the child group is

marked for manual failover in campus cluster. That is, the

value of the AutoFailover attribute for the group is equal to

2.

1859387



32/66

Table 1-4 VCS engine fixed issues(continued)

DescriptionIncident

The Subject line of the SMTP notification email must containthe Entity name. This is an enhancement.

1861740

When hashadow attempts to restart the High Availability

Daemon (HAD) module, if the

/var/VRTSvcs/lock/.hadargs file does not exist,

hashadow gets the SIGSEGV signal.

1866434

VCS sets theMonitorOnly attribute of theresources in a frozen

service group to 0. This behavior occurs even if the

ExternalStateChange attribute is not set to OfflineGroup for

a resource that goes intentionally offline.

1874261

If a resource, with the ExternalStateChange attribute set to

OfflineGroup, goes intentionally offline, VCS sets the

MonitorOnly attribute of all resources in a frozen service

group to 0. VCSmust setthe MonitorOnly attributeonly when

required.

1874533

The hares command lets you have the "." special character

in a resource name.

1915908

Notifier Agent is unable to get the local IP address in the

linked-based IPMP.

1958245

If a service group faults during failover, then VCS may not

honorthe Prerequisites/Limitsattributes on the targetsystem.

1971256

The notifier command must letyou specify theoriginating

source IP address. This is an enhancement.

2022123

If you override a static attribute for a resource with an empty

type definition, then VCS dumps duplicate entries for the

attribute in the configuration file.

2061932

After a child group autostarts, VCS does not bring a

partially-online parent to ONLINE state.

2081725

If you configure an online-local dependency between two

parallel groups, then the parent service group does not

AutoStart on all nodes.

2083232

If the VCS configuration includes a file with an absolute

pathname, then you cannot load templates from the cluster

manager GUI.

2084961


32


33/66

Table 1-4 VCS engine fixed issues(continued)

DescriptionIncident

In rare cases, VCStriesto bring online a failover service groupthat is already online on another node.

2111296

If you add a script-based WAN heartbeat, the heartbeat agent

generates a core file and fails to report status.

2128658

Enterprise agents fixed issues

Table 1-5lists the fixed issues for enterprise agents.

Table 1-5 Enterprise agents fixed issues

DescriptionIncident

The Sybase agent offline script must support the databases

that require a longer time to shut down. This is an

enhancement.

776230

When the monitor entry function encounters an invalid

process ID (PID) in a PID file, the function fails to detect the

exit status of the process. This behavior occurs if the PID has

an empty line below it. The function also accordingly fails to

detect the correct state of a failed DB2 Connect instance.

2117378

VCS 5.1 RP1 fixed issues

Table 1-6 Veritas Cluster Server 5.1 RP1 fixed issues

DescriptionFixed

issues

vxfenconfig -l reports multiple (duplicate) paths after phased upgrade on

the first sub-cluster.

1967207

Change in LLT delivery thread's priority limits.1946367

The haalert command hangs if the engine is not in running state.1941647

vxfentsthdw must detect storage arrays which interpret NULL keys as valid

for registrations/reservations.

1922411

ASMagent connects as sysdba instead of sysasm for 11gR2.1916004



34/66

Table 1-6 Veritas Cluster Server 5.1 RP1 fixed issues(continued)

DescriptionFixed

issues

The hares command lets you create resources which has the "." special

character

1915909

Port h halting system due to internal protocol error on gab_sf_dlv_gaps().1915016

Race script is killed if it exceeds the script time-out.1900450

If ExternalStateChange is not set to OfflineGroup, do not set MonitorOnly

to 0 .

1874267

LLT must display an error message if an attempt is made to configure more

than 8 links (LLT_MAX_LINK) under LLT.

1870424

System panics due to depleted memory during GAB broadcast stress and

reboot node 0.

1855196

Resource coordpoint becomes FAULTED from time to time.1839091

VCS 5.1 RP2 fixed issues

Table 1-7 Veritas Cluster Server 5.1 RP2 fixed issues

DescriptionFixed

issues

Issue occurs while accessing a freed pointer in vxfend.1986311

Memory leaks occur in llt_dlpi_setup and llt_closenode paths.2011416

Notifier faces issues in binding to a specific source IP address.2019899

Issue occurs while executing the lltconfig a set 1 link1

command .

2031931

LLT links go off/on repeatedly after configuring LLT over udp in IPv6.2059631

HAD dumps a core file while deleting a resource.2069689

HAD gets stuck in a tight loop when HACLI forks and membership changes.2070743

VCS dumps core under heavy load system which results in node panic.2077396

GAB driver must be enhanced to prevent gabconfig -c while port 'a' is

in the middle of iofence processing. Else, system may panic.

2086251


34


35/66


DescriptionFixed

issues

Node panics after running the GTX tc.2086280

RemoteGroup resource must support remote groups that are a parallel SG.2102777

RFC check with DNS agent must be disabled..2083268

Issue occursin llt_opennode(), check p_registeredand p_unregistering under

port lock.

2083181

Cluster goes in jeopardy after upgrade from 5.1 to 5.1RP2.2100421

MemCPUAllocator agent breaks if CPURequired attribute is not declared in

the AIX 6.1 Virtualised environment.

2108816

nfs_lock_$RESNAME file is not removed after system crash and monitor

complains.

2087190

vxfenclearpre cannot clear keys fromcoordinator disks and data disks when

there's a preexisting split brain.

2110465

Some VCS nodes in a group are online and some are not.2111294

LVMVG goes not come online.2116161

Issueoccurs in Oracle detailed monitoring whensending SNMP notification

on WARN signal.

2119570

DB2 resource generated excessive logging in engine_A.log.2120020

HAD must bring online the failover service group only if it is offline on all

nodes after the service group is unfrozen.

2125442

Memory leak occurs in MultiNICB agent.2126871

Partial parent group must auto-start after child comes online, and service

group must fail over after node panic.

1937834

Heartbeating logic betweeen engine and agfw must improve duringsnapshotting and during steady cluster operations.

2066967

Under heavy load, HADmay wait indefinitelyin waitpid() when user requests

to run some command through "hacli". This may cause GAB to kill HAD.

2071549

Overriding static attribute for any resource with empty type definition

creates duplicate entries in main.cf

2077363

Parallel group in PARTIAL state autostarts in case of engine restart.2077375



36/66


DescriptionFixed

issues

NFSRestart agent must remain online if HAD is forcefully stopped and

restarted.

2079617

nfs splitbrain test: Delay forced import of disk group agent to avoid errors

to client nodes.

2079622

ClusterService Group autopopulates system list2079664

Memory leak occurs when running the hareg -group command.2080703

A stack overflow occurs when a file name is very long.2084977

The vxcpserv process memory keeps growing when you run cpsadm

commands.

2089182

RemoteGroupresource appears OFFLINEeven after applying patch for issue

1834858.

2102764

vxfenclearpre cannot clear keys fromcoordinator disks and data disks when

there is a preexisting split brain.

2110465

Known issuesThis section covers the known issues in this release.

See the corresponding Release Notes for a complete list of known issues related

to that product.

See Documentationon page 64.

Hang or crash issue in frmalloc recursive lock acquisition

Recursive calls to xmalloc causes hang or crash in frmalloc recursive lock

acquisition. This issue is reported on AIX 6.1.

Workaround: To resolve the issue, install the following APARs before installing

VCS:

APAR IZ65498AIX 6.1 TL4

APAR IZ64768AIX 6.1 TL4

For versions earlier than AIX 6.1 TL4, contact IBM for a suitable APAR.

Release NotesKnown issues

36


37/66

NFS cluster I/O fails when storage is disabled

The I/O from the NFS clusters are saved on a shared disk or a shared storage.

When the shared disks or shared storage connected to the NFS clusters are

disabled, the I/O from the NFS Client fails and an I/O error occurs.

Workaround: If the application exits (fails/stops), restart the application.

Issues related to installation

This section describes the known issues during installation and upgrade.

Installation precheck can cause the installer to throw a licensepackage warning (2320279)

If the installation precheck is attempted after another taskcompletes (for examplechecking the descriptionor requirements) the installer throws the license package

warning. The warning reads:

VRTSvlic not installed on system_name

Workaround:

The warning is due to a software error and can be safely ignored.

While configuring authentication passwords through the

Veritas product installer, the double quote character is notaccepted (1245237)

The Veritas product installer prompts you to configure authentication passwords

when you configure Veritas Cluster Server (VCS) as a secure cluster, or when you

configure Symantec Product Authentication Service (AT) in authentication broker

(AB) mode. If you use the Veritas product installer to configure authentication

passwords, the double quote character (\") is not accepted. Even though thisspecial

character is accepted by authentication, the installer does not correctly pass the

characters through to the nodes.

Workaround:There is no workaround forthis issue. When entering authentication

passwords, do not use the double quote character (\").

Errors observed during partial upgrade of SFHA

While upgrading the VCS packages during an SFHA upgrade from 5.0 MP3 RP2

to 5.1SP1, CPI failed to uninstall the I/O fencing packages (VRTSvxfen, VRTSllt,

and VRTSgab). [1779129]

Workaround



38/66

Before upgrading SFHA from 5.0 MP3 RP2 to 5.1SP1, you must apply the I/O

fencing hotfix 5.0MP3RP2HF2.

Manual upgrade of VRTSvlic package loses keyless productlevels (2115662)

If you upgrade theVRTSvlicpackage manually, the product levels that were set

usingvxkeylessmay be lost. The output of the vxkeyless displaycommand

will not display correctly.

To prevent this, perform the following steps while manually upgrading the

VRTSvlic package.

To manually upgrade the VRTSvlic package

1. Note down the list of products configured on the node for keyless licensing.

# vxkeyless display

2. Set the product level to NONE.

# vxkeyless set NONE

3. Upgrade the VRTSvlic package.

# installp -u VRTSvlic

This step may report a dependency, which can be safely overridden.

# installp -acgX -d pathname VRTSvlic

4. Restore the list of products that you noted in step 1.

# vxkeyless set product[|,product]

Issues with keyless licensing reminders after upgradingVRTSvlic (2141446)

After upgrading from 5.1 to 5.1SP1, some keyless licenses may be left in the

system. As a result, you may see periodicremindersbeinglogged if theVOMserver

is not configured.

This happens if you were using keyless keys before upgrading to 5.1SP1. Afterthe upgrade, you install real keys and runvxkeyless set NONE. In this case, the

keyless licenses may not be completely removed and you see warning messages

being logged after two months (if VOM server is not configured). This does not

result in any functionality impact.

To resolve this issue, perform the following steps:


38


39/66

1. Note down the list of products configured on the node for keyless licensing.

Runvxkeyless displayto display the list.

2. Set the product level toNONEwith the command:

# vxkeyless set NONE

3. Findand delete the keyless licenses left over in the system. To dothis, perform

the following steps for every key stored in /etc/vx/licenses/lic:

Verify if the key hasVXKEYLESSfeature Enabled using the following

command:

# vxlicrep -k | grep VXKEYLESS

Delete the key if and only ifVXKEYLESSfeature is Enabled.

Note: When performing the search, do not include the .vxlic extension as

part of the search string.

4. Restore the previous list of products with the command:

# vxkeyless set product1[|,product]

Installer is unable to split a cluster that is registered with oneor more CP servers

Splitting a cluster that uses server-based fencing is currently not supported.[2110148]

You can split a cluster into two and reconfigure VCS on the two clusters using the

installer. For example, you can split a clusterclus1intoclus1Aandclus1B.

However, if you use the installer to reconfigure the VCS, the installer retains the

same cluster UUID ofclus1in bothclus1Aandclus1B. If bothclus1Aandclus1B

use the same CP servers for I/O fencing, then the CP server allows registration

only from the cluster that attempts to register first. It rejects the registration

from the cluster that attempts next. Thus, the installer reports failure during the

reconfiguration of the cluster that uses server-based fencing.

Workaround: None.



40/66

The installer enters an infinite loop because the cluster isalready running in secure mode while configuring server-basedfencing (2166599)

During server-based fencing configuration with a secure cluster, if vxfen fails to

start and you retry server-based fencing configuration, the installer keeps asking

to enter another system to enable security after you manually start VCS.

Workaround:When vxfen fails to start in customized mode for server-based

fencing with a secure cluster, do not choose to retry configuring fencing, choose

the default option, then vxfen starts in disabled mode. You can also retry fencing

configuration using-fencingoption.

System moves to low system resources while bringing large

number process resources online (2061338)When large number of resource like Process resources (1500 in number) is

configured on a Linux system (kernel version 2.6.18-92.el5)than agent gets killed.

The reason for is fork failure and fork return with an error number 513. A bug

against Red Hat "Issue #822253" exits. Red Hat has confirmed that this is their

issue. This issue does't appear on kernel version 2.6.18-194.el5 which they claim

to have the fix for this issue.

Operational issues for VCS

Connecting to the database outside VCS control using sqlplustakes too long to respond

Connecting to start the database outside VCS control, using sqlplus takes more

than 10 minutes to respond after pulling the public network cable. [704069]

Issues with configuration of resource values

If you configure a resource that has more than 425 values in its ArgListValues,

the agent managing that resource logs a message such as:

VCS WARNING V-16-2-13806 Thread(1437547408) ArgListValues overflow;

Cannot append values more than upper limit of (425).

Normally, the number of values inArgListValues for a resource must not exceed

425. However, in case of a keylist, association or vector type of attribute appears

in the ArgList for a resource-type. Since these attributes can take multiple values,

there is a chance for the resource values in ArgListValuesto exceed 425.


40


41/66

The CmdServer process may not start in IPv6 environments insecure clusters

In an IPv6 environment on secure clusters, the CmdServer process may not start.

In addition, security may not function correctly. If it does not start on a particular

node, modify that node's /etc/hosts file so that the localhost resolves to ::1.

Workaround: In the /etc/hosts file, add the following:

::1 localhost

Issues related to the VCS engine

Systems with multiple CPUs and copious memory shut-down

time may exceed the ShutdownTimeout attributeThe time taken by the system to go down may exceed the default value of the

ShutdownTimeout attribute for systems that have a large numbers of CPUs and

memory. [1472734 ]

Workaround: Increase the value of the ShutdownTimeout attribute based on your

configuration.

The hacf -cmdtocf command generates a broken main.cf file

Thehacf -cmdtocfcommand used with the-dest option removes the include

statements from the types files. [1728738]

Workaround: Addinclude statements in the main.cf files that are generated using

thehacf -cmdtocfcommand.

VCS Engine logs messages when it eventually connects to aremote cluster

Description: In a global cluster, if a local cluster fails to connect with a remote

clusterin the first attempt but succeeds eventually, then you may see thefollowing

warning messages in the engine logs. [2110108]

VCS WARNING V-16-1-10510 IpmHandle: pen Bind Failed.

unable to bind to source address 10.209.125.125. errno = 67

Workaround: There is currently no workaround for this issue. This issue has no

impact on any functionality.



42/66

Agent framework can rejecthares -actioncommand

When a probed resource is disabled and later enabled then, the agent framework

can rejecthares -actioncommand till the agent successfully monitors the

resource.

New nodes get added to SystemList and AutoStartListattributes of ClusterService even if AutoAddSystemToCSG isdisabled

The AutoAddSystemToCSG attribute determines whether the newly joined or

added systems in a cluster become part of the SystemList of the ClusterService

service group if the service group is configured. The value 1 (default) indicates

that the new systems are added to SystemList of ClusterService.

AutoAddSystemToCSG has an impact only when you execute the hasys

addcommand or when a new node joins the cluster. [2159139]

However, when you use the installer to add a new node to the cluster, the installer

modifies the SystemList and AutoStartList attributes irrespective of whether

AutoAddSystemToCSG is enabled or disabled. The installer adds the new system

to the SystemList and AutoStartList. To add nodes, the installer uses the following

commands that are not affected by the value of AutoAddSystemToCSG:

# hagrp modify ClusterService SystemList add newnode n

# hagrp modify ClusterService AutoStartList add newnode

Workaround

The installer will be modified in future to prevent automatic addition of nodes to

SystemList and AutoStartList.

As a workaround, use the following commands to remove the nodes from the

SystemList and AutoStartList:

# hagrp modify ClusterService SystemList delete newnode

# hagrp modify ClusterService AutoStartList delete newnode

Issues related to the bundled agentsVCS resources may time out if NFS server is down

The VCS resources may time out if the server NFS mounted file system and the

NFS server is down or inaccessible. This behavior is exclusive to AIX platform.

Workaround: You must unmount the NFS mounted file system to restore the

cluster to sane condition.


42


43/66

Issues related to the VCS database agents

OracleTypes.cf needs updates for WPAR support (2163956)

To support the Oracle and the Netlsnr agents in WPAR environment, you must

modify the OracleTypes.cf file to include the following attributes in both Netlsnr

and Oracle type:

static int ContainerOpts{}

= { RunInContainer=1, PassCInfo=0 }

Workaround: To modify the OracleTypes.cf for WPAR support

1 Stop VCS on all nodes.

# hastop -all -force

2 Edit the OracleTypes.cf file on one of the nodes. Add the following line toNetlsnr and Oracle type:

static int ContainerOpts{}

= { RunInContainer=1, PassCInfo=0 }

3 Start VCS on the node with modified configuration:

# hastart

4 After VCS has started on the node, start VCS on other cluster nodes:

# hastart

VCS agent for Oracle: Health check monitoring is not supportedfor Oracle database 11g R1 and 11g R2 (1985055)

Health check monitoring is not supported for Oracle database 11g R1 and 11g R2.

Workaround: Set MonitorOption attribute for Oracle resource to 0.

VCS agent for Oracle: Health check monitoring does not workwith Oracle 10.2.0.4

The health check monitoring in Oracle agent does not work with Oracle 10.2.0.4

due to incompatibility of the health check APIs provided by Oracle. [2101570]

Resolution: Disable health check monitoring by setting the MonitorOption attribute

to 0 (zero).



44/66

VCS agent for Oracle: Make sure that the ohasd has an entryin the init scripts

Make sure that the ohasd process has an entry in the init scripts so that when the

process is killed or the machine is rebooted, this automatically restarts the

process.[1985093]

Workaround: Respawn ofohasdprocess. Add the ohasd processin

the/etc/inittab file to ensure that this process is automatically restarted when

killed or the machine is rebooted.

VCS agent for Oracle: Intentional Offline does not work

Due to issues with health check monitoring, Intentional Offline does not work for

VCS agent for Oracle.

The ASMInstAgent does not support having pfile/spfile for theASM Instance on the ASM diskgroups

The ASMInstAgent does not support having pfile/spfile for the ASM Instance on

the ASM diskgroups.

Workaround:

Have a copy of the pfile/spfile in the default $GRID_HOME/dbs directory to make

sure that this would be picked up during the ASM Instance startup.

VCS agent for ASM: Health check monitoring is not supportedfor ASMInst agent

The ASMInst agent does not support health check monitoring.

Workaround: Set the MonitorOption attribute to 0.

Concurrency violation due to process startup on failover nodeis not detected when detail monitoring is set for Oracleresources [2917558]

Inside a failover service group, when the administrator starts an Oracle resourceon a node and if the Oracle instance is online on any other node within the cluster,

the instance would come up.However, the database does not getmounted. In such

circumstances, this startup attempt is detected by basic monitoring. If detail

monitoring is enabled, this startup attempt does not get detected.

Workaround: No workaround.


44


45/66

Issues related to the agent framework

Agent framework cannot handle leading and trailing spaces

for the dependent attribute

Agent framework does not allow spaces in the target resource attribute name of

the dependent resource.

Workaround

Do not provide leading and trailing spaces in the target resource attribute name

of the dependent resource.

The agent framework does not detect if service threads hang

inside an entry pointIn rare cases, the agent framework does not detect if all service threads hang

inside a C entry point. In this case it may not cancel them successfully. [1511211]

Workaround: If the service threads of the agent are hung, send a kill signal to

restart the agent. Use the following command: kill -9 hung agent's pid. The

haagent -stopcommand does not work in this situation.

The ArgListValues attribute values for dependent resourcesmay not populate correctly when a target resource is deletedand re-added

For resource attributes, deleting a resource prevents a dependent attributes value

from refreshing in the dependent resources value.

For example, you have resource (rD), which depends on a resources attribute

value (rT:Attr_rt). When you delete the target resource (rT), and re-add it (rT), the

dependent resource (rD) does not get the correct value for the attribute (Attr_rt).

[1539927]

Workaround: Set the value of the reference attribute (target_res_name) to an

empty string.

# hares -modify rD target_res_name ""

WhererDis thename of the dependent resource, and target_res_nameis the name

of the reference attribute that contains the name of the target resource.

Set the valueof thereference attribute (target_res_name) tothe nameof the target

resource (rT).

# hares -modify rD target_res_name rT



46/66

Agent performance and heartbeat issues

Depending on the system capacity and the number of resources configured under

VCS, the agent may not get enough CPU cycles to function properly. This can

prevent the agent from producing a heartbeat synchronously with the engine. Ifyou notice poor agent performance and an agent's inability to heartbeat to the

engine, check for the following symptoms.

Navigate to /var/VRTSvcs/diag/agents/ and look for files that resemble:

FFDC_AGFWMain_729_agent_type.log FFDC_AGFWTimer_729_agent_type.log core

FFDC_AGFWSvc_729_agent_type.log agent_typeAgent_stack_729.txt

Whereagent_typeis the type of agent, for example Application or FileOnOff. If

you find these files, perform the next step.

Navigate to /var/VRTSvcs/log/ and check the engine_*.log file for messages thatresemble:

2009/10/06 15:31:58 VCS WARNING V-16-1-10023 Agent agent_type

not sending alive messages since Tue Oct 06 15:29:27 2009

2009/10/06 15:31:58 VCS NOTICE V-16-1-53026 Agent agent_type

ipm connection still valid

2009/10/06 15:31:58 VCS NOTICE V-16-1-53030 Termination request sent to

agent_type agent process with pid 729

Workaround: If you see that both of the above criteria are true, increase the value

of the AgentReplyTimeout attribute value. (Up to 300 seconds or as necessary.)[1853285]

Issues related to global clusters

Clusters are stuck in INIT and LOST_CONN states after enablingAT after cluster migration to IPv6

Clusters arestuck in INIT and LOST_CONN states after enabling Symantec Product

Authentication Service (AT) for the first time without secure WAC.

[1836428/1847556]Workaround: Reboot theclusters or restart VCSon both theclusters.Thecommand

hastop -allmay not stop WAC. In this case, you have to manually kill WAC.


46


47/66

The engine log file receives too many log messages on thesecure site in global cluster environments

When the WAC process runs in secure mode on one site, and the other site does

not use secure mode, the engine log file on the secure site gets logs every five

seconds. [1539646]

Workaround: The two WAC processes in global clusters must always be started

in eithersecureor non-secure mode. Thesecure and non-secureWACconnections

will flood the engine log file with the above messages.

Application group attempts to come online on primary sitebefore fire drill service group goes offline on the secondarysite

The application service group comes online on the primary site while the fire drillservice group attempts to go offline at the same time, causing the application

group to fault. (2107386)

Workaround:Ensure that the fire drill service group is completely offline on the

secondary site before the application service group comes online on the primary

site.

Issues related to LLT

This section covers the known issues related to LLT in this release.

LLT port stats sometimes shows recvcnt larger than recvbytes

With ea

Vcs Notes 51sp1 Aix

Documents

Transcript of Vcs Notes 51sp1 Aix