Veritas Cluster Server Release Notes · 2012-09-21 · Release Notes This document includes the...

Veritas™ Cluster ServerRelease Notes

Solaris

5.1 Service Pack 1

Veritas™ Cluster Server Release NotesThe software described in this book is furnished under a license agreement andmay be usedonly in accordance with the terms of the agreement.

Product version: 5.1 SP1

Document version: 5.1SP1.1

Legal NoticeCopyright © 2012 Symantec Corporation. All rights reserved.

Symantec, the Symantec logo, Veritas, Veritas Storage Foundation, CommandCentral,NetBackup, Enterprise Vault, and LiveUpdate are trademarks or registered trademarks ofSymantec corporation or its affiliates in the U.S. and other countries. Other names may betrademarks 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 documentmay be reproduced in any form by any means without prior written authorization ofSymantec Corporation and its licensors, if any.

THEDOCUMENTATIONISPROVIDED"ASIS"ANDALLEXPRESSORIMPLIEDCONDITIONS,REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TOBELEGALLYINVALID.SYMANTECCORPORATIONSHALLNOTBELIABLEFORINCIDENTALOR 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 Licensed Software andDocumentation are deemed to be commercial computer softwareas defined in FAR12.212 and subject to restricted rights as defined in FARSection 52.227-19"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights inCommercial Computer Software or Commercial Computer Software Documentation", asapplicable, and any successor regulations. Any use, modification, reproduction release,performance, display or disclosure of the Licensed Software andDocumentation by theU.S.Government shall be solely in accordance with the terms of this Agreement.

Symantec Corporation350 Ellis StreetMountain View, CA 94043

http://www.symantec.com

http://www.symantec.com

Technical SupportSymantec Technical Support maintains support centers globally. TechnicalSupport’s primary role is to respond to specific queries about product featuresand functionality. TheTechnical Support group also creates content for our onlineKnowledge Base. The Technical Support group works collaboratively with theother functional areas within Symantec to answer your questions in a timelyfashion. For example, theTechnical Support groupworkswithProductEngineeringand Symantec Security Response to provide alerting services and virus definitionupdates.

Symantec’s support offerings include the following:

■ A range of support options that give you the flexibility to select the rightamount of service for any size organization

■ Telephone and/or Web-based support that provides rapid response andup-to-the-minute information

■ Upgrade assurance that delivers software upgrades

■ Global support purchased on a regional business hours or 24 hours a day, 7days a week basis

■ Premium service offerings that include Account Management Services

For information about Symantec’s support offerings, you can visit our Web siteat the following URL:

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

All support services will be delivered in accordance with your support agreementand the then-current enterprise technical support policy.

Contacting Technical SupportCustomers with a current support agreement may access Technical Supportinformation 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 beat the computer onwhich theproblemoccurred, in case it is necessary to replicatethe problem.

When you contact Technical Support, please have the following informationavailable:

■ Product release level

http://www.symantec.com/business/support/index.jsp

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

■ 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 registrationIf yourSymantecproduct requires registrationor a licensekey, access our technicalsupport Web page at the following URL:

www.symantec.com/business/support/

Customer serviceCustomer 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 thefollowing 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/

Support agreement resourcesIf youwant to contact Symantec regarding an existing support agreement, pleasecontact 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

DocumentationProduct guides are available on the media in PDF format. Make sure that you areusing the current version of the documentation. The document version appearson page 2 of each guide. The latest product documentation is available on theSymantec Web site.

https://sort.symantec.com/documents

Your feedback on product documentation is important to us. Send suggestionsfor improvements and reports on errors or omissions. Include the title anddocument version (located on the second page), and chapter and section titles ofthe 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 ConnectSymantec Connect is the peer-to-peer technical community site for Symantec’senterprise customers. Participants can connect and share informationwith otherproduct users, including creating forum posts, articles, videos, downloads, blogsand suggesting ideas, as well as interact with Symantec product teams andTechnical Support. Content is rated by the community, and members receivereward points for their contributions.

http://www.symantec.com/connect/storage-management

mailto:[email protected]



https://sort.symantec.com/documents




http://www.symantec.com/connect/storage-management

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 aboutVeritas Cluster Server (VCS)version 5.1 SP1 for Solaris. Review this entire document before you install VCS.

The information in the Release Notes supersedes the information provided in theproduct documents for VCS.

This is Document version: 5.1SP1.1 of the Veritas Cluster Server Release Notes.Before you start, ensure that you are using the latest version of this guide. Thelatest 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 thisReleaseNotes document, review the component productrelease 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/docsdirectory on yoursystem.

This release includes the following component product release notes:

■ Veritas Storage Foundation Release Notes (5.1 SP1)

About Veritas Cluster ServerVeritas™Cluster Server by Symantec (VCS) is a clustering solution that eliminatesdowntime, facilitates server consolidation and failover, and effectively managesa wide range of applications in heterogeneous environments.

About VCS agentsVCS bundled agents manage a cluster’s key resources. The implementation andconfiguration of bundled agents vary by platform.

For more information about bundled agents, refer to the Veritas Cluster ServerBundled Agents Reference Guide.

The Veritas High Availability Agent Pack gives you access to agents that providehigh availability for various applications, databases, and third-party storagesolutions. The Agent Pack is available through SymantecTM Operations ReadinessTools (SORT).

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

For information about agents under development and agents that are availablethroughSymantec consulting services, contact yourSymantec sales representative.

Release NotesComponent product release notes

8


https://sort.symantec.com/home

VCS provides a framework that allows for the creation of custom agents. Createagents in situations where the Veritas High Availability Agent Pack, the bundledagents, or the enterprise agents do not meet your needs.

For more information about the creation of custom agents, refer to the VeritasCluster Server Agent Developer's Guide. You can also request a custom agentthrough Symantec consulting services.

About compiling custom agentsCustom agents developed in C++ must be compiled using Forte Developer 6compilers. The following is the layout of libvcsagfw.so in usr/lib:

/usr/lib/libvcsagfw.so --> . /libvcsagfw.so.2

If you use custom agents compiled on older compilers, the agents may not workwith VCS 5.1SP1. If your custom agents use scripts, continue linking toScriptAgent. Use Script50Agent for agents written for VCS 5.0 and above.

About Symantec Operations Readiness ToolsSymantec™ Operations Readiness Tools (SORT) is a set of Web-based tools andservices that lets you proactively manage your Symantec enterprise products.SORT automates and simplifies administration tasks, so you can manage yourdata 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 acrossUNIX orWindowsenvironments. You can use this data to do the following:

■ Assess whether your systems are ready to install or upgrade Symantecenterprise products

■ Tune environmental parameters so you can increase performance,availability, and use

■ Analyze your current deployment and identify the Symantec products andlicenses you are using

■ Upload configuration data to the SORTWeb site, so you can share informationwith coworkers, managers, and Symantec Technical Support

■ Compare your configurations to one another or to a standard build, so you candetermine if a configuration has "drifted"

■ Search for and download the latest product patches

■ Get notifications about the latest updates for:

9Release NotesAbout Symantec Operations Readiness Tools

Patches■

■ Hardware compatibility lists (HCLs)

■ Array Support Libraries (ASLs)

■ Array Policy Modules (APMs)

■ High availability agents

■ Determinewhether your 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:


■ For important updates regarding this release, review the Late-Breaking NewsTechNote on the Symantec Technical Support website:http://entsupport.symantec.com/docs/334829

■ 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 installationThe product installer includes the following changes.

Rolling upgrade supportTo reduce downtime, the installer supports rolling upgrades. A rolling upgraderequires little or no downtime. A rolling upgrade has two main phases. In phase

Release NotesImportant release information

10

http://sort.symantec.com/


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

http://sort.symantec.com/

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

All high availability products support a rolling upgrade. You can performa rollingupgrade from 5.1 or from any RPs to the current release.

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

See the Veritas Cluster Server Installation Guide.

Installer-related changes to configure LLT private links, detectaggregated links, and configure LLT over UDPFor all high availability products, the installer provides the followingnew featuresin this release to configure LLT private links during the VCS configuration:

■ The installer detects and lists the aggregated links that you can choose toconfigure as private heartbeat links.

■ The installer provides an option to detect NICs on each system and networklinks, and sets link priority to configure LLT over Ethernet.

■ The installer provides an option to configure LLT over UDP.


Installer changes related to I/O fencing configurationIn VCS 5.1 or SFHA 5.1, the installer started I/O fencing in disabled mode even ifyou had not chosen to configure I/O fencing. In 5.1 SP1, if you did not choose toconfigure I/O fencing during the product configuration, then the installer doesnot 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 retainsthe I/O fencing configuration from the previous version.

Installer supports configuration of non-SCSI3 based fencingYoucannowconfigurenon-SCSI3 based fencing forVCS cluster using the installer.


Web-based installer supports configuringVCS cluster in securemodeYou can now configure the VCS cluster in secure mode using the Web-basedinstaller.


11Release NotesChanges in version

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 andrequire 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 VCSYou cannowconfigure disk-based fencing for theVCS cluster using theWeb-basedinstaller.


The Web-based installer supports adding nodesThe Web-based installer has increased parity with the script-based installer. Itnow supports the ability to add nodes to a cluster. It also supports configuringsecure clusters and fencing configuration.

The installer provides automated, password-less SSHconfigurationWhen 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 successfulcompletion, the installer removes the keys and systemnames fromthe appropriatefiles.

When you use the installer for SSH communications, meet the followingprerequisites:

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

■ You need the superuser passwords for the systems where you plan to installVCS.

The installer can check product versionsYou canuse the installer to identify the version (to theMP/RP/SP level dependingon 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.0onward.

Release NotesChanges in version

12

Upgrade changesThe following lists the upgrade changes in this release.

Supported paths for VCS upgrades that do not require a noderebootWhen using the installer program to perform any of the typical upgrade listed inthe 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 the Veritas Cluster Server InstallationGuide.

Upgrades that follow any other upgrade paths require a reboot.

Packaging updatesThe following lists package changes in this release.

New VRTSamf packageVRTSamf is a new package introduced in this release. The AsynchronousMonitoring Framework (AMF) module, along with the VCS Agent Framework(AGFW) and resource agents provides a way to avoid polling for resource statechanges. TheAMFmodule allows the agent to registerwhich resources tomonitorand when to wait. The module provides the agent with immediate notification sothat action can be taken at the time of the event. AMF enables the VCS agents tomonitor a large number of resources with a minimal effect on performance.

VRTSacclib package is no longer shipped with VCS 5.1SP1The VRTSacclib package was available with VCS 5.1. The package is not shippedwith VCS 5.1SP1. The latest VRTSacclib package can be accessed from the AgentPack release.

New virtualization featuresThis release introduces the following virtualization features.


Awareness of the Solaris Resource MonitorThis release introduces a new model which enables VCS to work with SolarisProjects. A service group-level attribute named ContainerInfo and a type-levelstatic attribute named ContainerOpts work together to provide Solaris ResourceMonitor (SRM) support.

See the Veritas Cluster Server Administrator's Guide.

Changes to the VCS engine

The HAD can exchange messages up to 64KB sizeThe size of themessages that HAD supports is increased from 16KB to 64KB. Themessages canbe exchangedbetweendifferentHADprocesses (runningondifferentsystems) 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.

Support for intelligent monitoring of VCS resources using IMFVCS now supports intelligent resource monitoring in addition to poll-basedmonitoring. Intelligent Monitoring Framework (IMF) is an extension to the VCSagent framework.Youcanenable ordisable the intelligentmonitoring functionalityof VCS agents as needed.

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

■ Faster notification of resource state changes.


14

■ Reduction in VCS systemutilizationwhich enables VCS to effectivelymonitora large number of resources.

See the Veritas Cluster Server Administrator's Guide for more information.

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

■ Mount

■ Process

■ Application

■ Oracle

■ Netlsnr

■ CFSMount

■ CVMVxconfigd

■ CFSfsckd

New attributesThe following sections describes the attributes introduced in VCS 5.1SP1, VCS5.1, and VCS 5.0MP3.

Attributes introduced in VCS 5.1SP1Application Agent attributes

■ EnvFile: This attribute specifies the environment file that must be sourcedbefore runningStartProgram,StopProgram,MonitorProgramorCleanProgram.

■ UseSUDash: This attribute specifies that the agent must run su - user -c

<program> or su user -c <program> while running StartProgram,StopProgram, MonitorProgram or CleanProgram.

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 withone another. You must set IntentionalOffline attribute to 1 for theReturnIntOffline attribute to work.

■ RemotePartial: Makes RemoteGroup resource to return IntentionalOfflinewhen the remote service group is in ONLINE|PARTIAL state.

■ RemoteOffline:MakesRemoteGroup resource to return IntentionalOfflinewhen the remote service group is in OFFLINE state.


■ RemoteFaulted:MakesRemoteGroup resource to return IntentionalOfflinewhen the remote service group is in OFFLINE|FAULTED state.

DiskGroup agent attribute

■ Reservation: Determines if you want to enable SCSI-3 reservation. For moreinformation, please refer to Bundled Agents Reference Guide.In order to support SCSI-3 disk reservation, you must be sure that the disksare SCSI-3 compliant. Since all the disks are not SCSI-3 compliant, reservationcommands fail on suchdiskgroups.TheReservationattributehelps in resolvingthis issue. TheReservation attribute canhave one of the following three values:

■ ClusterDefault: The disk group is imported with or without SCSI-3reservation, 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 agentdoes not care about the cluster-level UseFence attribute.

Note: This attribute must be set to NONE for all resources of type DiskGroupin case of non-SCSI-3 fencing.

IP agent attribute

■ ExclusiveIPZone: When an IP resource has to be configured for exclusive IPzone, set the value of this attribute to 1 (one). It also requires a validContainerInfo to be configured in the service group. The IP resourcemonitorsvirtual IP address on interface inside the exclusive IP zone.

IPMultiNICB agent attribute

■ Options:Value of this attribute is used as the option for theifconfig command.For example, if value of this attribute is set to “deprecated” then “deprecated”option is set on the interface while bringing IPMultiNICB resource online.

NFS agent attribute

■ CleanRmtab: To clear the /etc/rmtab file before starting the mount daemon,set the value of CleanRmtab to 1.

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 Lowerattribute value of 0.

NIC agent attribute


16

■ ExclusiveIPZone: When the NIC resource is to be configured for exclusive IPzone, set the value of this attribute to 1 (one). It also requires a validContainerInfo to be configured in the service group. NIC resource monitorsnetwork interface inside the exclusive IP zone.

RVGPrimary agent attribute

■ BunkerSyncTimeOut: The timeout value in seconds that signifies the amountof time that a SecondaryRVGcanwait for the synchronization from thebunkerhost to complete before taking over the Primary role.

NotifierSourceIP agent attribute

■ NotifierSourceIP: : Lets you specify the interface that the notifier must use tosend packets. This attribute is string/scalar. You must specify an IP addressthat is either DNS resolvable or appears in the/etc/hosts file.

SambaServer agent attributes

■ PidFile: The absolute path to the Samba daemon (smbd) Pid file. This attributeismandatory if you are using Samba configuration file with non-default nameor path.

■ SocketAddress: The IPv4 address where the Samba daemon (smbd) listens forconnections. This attribute is mandatory if you are configuring multipleSambaServer resources on a node.

Zone agent attributes

■ RunFsck: If the value of this attribute is 1, the Zone agent checks the systemconsistency for vxfs file systems. It uses the fsck -y command on all vxfs filesystems that are defined in the zones's xml file. This file is located in/etc/zones. Adjust the Zone agent default OnlineTimeout value so that zoneagent has sufficient time to run the fsck command before it brings the zoneonline.

■ DetachZonePath: If disabled, Zone agent skips detaching the Zone root duringzone resource offline and clean. DetachZonePath is enabled (1) by default.

■ ForceAttach: If disabled, the Zone agent attaches the ZonePath without the -Foption during zone resource online. ForceAttach is enabled (1) by default.

Oracle agent attributes

■ DBAUser: Database/ASM user with sysdba/sysasm permissions respectively.

■ DBAPword: The encrypted value of the password of DBAUser.

ASMInst agent attributes

■ MonitorOption: Enables or disables health check monitoring.

NetBios agent attribute


■ PidFile: The absolute path to the Samba daemon (nmbd) PidFile. This attributeismandatory if you are using Samba configuration file with non-default nameor path.

Sybase agent attribute

■ Run_ServerFile: The attribute specifies the location of the RUN_SERVER filefor a Sybase instance. If this attribute is not specified, the default location ofthis file is accessed while starting Sybase server instances.

Cluster-level attributes

■ AutoAddSystemToCSG: Indicates whether the newly joined or added systemsin the cluster become a part of the SystemList of the ClusterService servicegroup if the service group is confirmed. The value 1 (default) indicates thatthe new systems are added to SystemList of ClusterService. The value 0indicates that the new systems are not added to SystemList of ClusterService.

■ CounterMissTolerance: If GlobalCounter does not update inCounterMissTolerance intervals of CounterInterval, then VCS reports aboutthis issue depending on theCounterMissAction (that is, CounterMissTolerance* CounterInterval) time has elapsed since last update of GlobalCounter thenCounterMissAction is performed. The default value of CounterMisstoleranceis 20.

■ CounterMissAction: The actionmentioned inCounterMissAction is performedwhenever theGlobalCounter isnotupdated forCounterMissTolerance intervalsof CounterInterval.The two possible values of CounterMissAction are LogOnly and Trigger.LogOnly logs themessage in Engine Log and SysLog. Trigger invokes a triggerwhich has a default action of collecting the comms tar file. The Default valueof Trigger is LogOnly.

■ PreferredFencingPolicy: The I/O fencing race 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 fencingdriver favors the subclusterwith maximum number of nodes during the race for coordination points.System:The fencingdriver gives preference to the systemthat ismorepowerfulthan others in terms of architecture, number of CPUs, or memory during therace for coordinationpoints.VCSuses the system-level attributeFencingWeightto calculate the node weight.Group: The fencing driver gives preference to the node with higher priorityservice groupsduring the race for coordinationpoints.VCSuses the group-levelattribute Priority to determine the node weight.

Resource type attributes


18

■ IMF: Determines whether the IMF-aware agent must perform intelligentresource monitoring.It is an association attribute with three keys Mode, MonitorFreq, andRegisterRetryLimit.

■ Mode: Defines whether to perform IMF monitoring based on the state ofthe 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 agentattempts to register a resource. Default is 3.

■ IMFRegList: Contains a list of attributes. The values of these attributes areregistered with the IMF module for notification. If an attribute defined inIMFRegList attribute is changed then the resource, if already registered, isunregistered from IMF. If IMFRegList is not defined and if any attribute definedin ArgList is changed the resource is unregistered from IMF.

■ AlertOnMonitorTimeouts: Indicates thenumberof consecutivemonitor failuresafter which VCS sends an SNMP notification to the user.

Attributes introduced in VCS 5.1VCS 5.1 introduced the following new attributes. See the Veritas Cluster ServerAdministrator’s Guide for 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 movinga 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 agentfunctions (entry points) except the online entry point.

■ FaultPropogation: Specifies if VCS should propagate the fault up to parentresources and take the entire service group offline when a resource faults.

■ OnlineClass: Enables you to control the scheduling class for the online agentfunction (entry point).

■ OnlinePriority: Enables you to control the scheduling priority for the onlineagent function (entry point).

Service group level attribute:


■ ContainerInfo: Specifies information about the container that the service groupmanages.

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 MP3VCS 5.0MP3 introduced the following attributes.

Resource type attributes:

■ FaultPropagation: Specifies if VCS should propagate the fault up to parentresources and take the entire service group offline when a resource faults.

■ AgentFile: Complete name and path of the binary for an agent. Use when theagent binaries are not installed at their default locations.

■ AgentDirectory: Complete path of the directory in which the agent binary andscripts are located.Usewhen the agent binaries arenot installed at their defaultlocations.

Cluster level attributes:

■ DeleteOnlineResource: Defines whether you can delete online resources.

■ HostMonLogLvl: Controls the behavior of theHostMonitor daemon. Configurethis attribute when you start the cluster. You cannot modify this attribute ina running cluster.

■ EngineShutdown: Provides finer control over the hastop command.

■ BackupInterval: Timeperiod inminutes afterwhichVCSbacksupconfigurationfiles.

■ OperatorGroups: List of operating system user account groups that haveOperator privileges on the cluster.

■ AdministratorGroups: List of operating systemuser account groups that haveadministrative privileges on the cluster.

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

System level attributes:

■ EngineVersion: Specifies themajor,minor,maintenance-patch, andpoint-patchversion of VCS.

Service group level attributes:


20

■ TriggerResFault: Defines whether VCS invokes the resfault trigger when aresource faults.

■ AdministratorGroups: List of operating systemuser account groups that haveadministrative privileges on the service group.

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

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

Changes to bundled agentsThis section describes changes to the bundled agents for VCS.

New bundled agent■ Project agent: This agent brings Solaris projects online, takes them offline,

and monitors them.

■ Disk agent: This agent is used to monitor a physical disk or a slice that isexported to LDoms.

■ VolumeSet agent: The VolumeSet agent brings online, takes offline, andmonitors a Veritas Volume Manager (VxVM) volume set. Use this agent tomake a volume set highly available.

Support for Solaris projectsThe following agents now support Solaris projects:

■ Process agent

■ Application agent

Support for Veritas dynamic multi-pathingThe following agent supports Veritas Dynamic Multi-Pathing (DMP):

■ Zpool agent

About the ReturnIntOffline attribute of RemoteGroup agentThe ReturnIntOffline attribute can take one of three values: RemotePartial,RemoteOffline, and RemoteFaulted.

These values are notmutually exclusive and can be used in combination with oneanother. You must set the IntentionalOffline attribute of RemoteGroup resourceto 1 for the ReturnIntOffline attribute to work.


About the RemotePartial option

Select the RemotePartial value of this attribute when youwant the RemoteGroupresource to return an IntentionalOffline when the remote service group is in anONLINE | PARTIAL state.

About the RemoteOffline option

Select the RemoteOffline value of this attributewhen youwant the RemoteGroupresource to return an IntentionalOffline when the remote service group is in anOFFLINE state.

About the RemoteFaulted option

Select theRemoteFaulted value of this attributewhenyouwant theRemoteGroupresource to return an IntentionalOffline when the remote service group is in anOFFLINE | FAULTED state.

Configuring RemoteGroup resources in parallel service groupsWhen aRemoteGroup resource is configured inside parallel service groups, it cancomeonline onall the cluster nodes, including the offlinenodes.Multiple instancesof the RemoteGroup resource on cluster nodes can probe the state of a remoteservice group.

Note: The RemoteGroup resource automatically detects whether it is configuredfor a parallel service group or for a failover service group. No additionalconfiguration is required to enable theRemoteGroup resource for parallel servicegroups.

A RemoteGroup resource in parallel service groups has the followingcharacteristics:

■ The RemoteGroup resource continues to monitor the remote service groupeven when the resource is offline.

■ The RemoteGroup resource does not take the remote service group offline ifthe resource is online anywhere in the cluster.

■ After an agent restarts, the RemoteGroup resource does not return offline ifthe resource is online on another cluster node.

■ The RemoteGroup resource takes the remote service group offline if it is theonly instance of RemoteGroup resource online in the cluster.

■ An attempt to bring a RemoteGroup resource online has no effect if the sameresource instance is online on another node in the cluster.


22

Support for Exclusive IP zone in networking agentsNIC and IP agents support Exclusive IP zone. This attribute is added to both NICand IP agents.

For more details, See “New attributes” on page 15.

Changes to SambaServer and NetBios agentsThe SambaServer and NetBios agents contain the following changes:

■ VCSSambaServer andNetBios agents nowsupportmultiple resource instanceson a node.

■ These agents now support non default Samba configuration file and pid filenames.

For more information about bundled agents, refer to the Veritas Cluster ServerBundled Agents Reference Guide.

Changes to database agents

Changes to the Oracle agent■ Oracle agent now supports IMF monitoring.

■ The VCS agent for Oracle is Solaris Project (SRM)-aware.TheOracle resource is anSRM-aware resourcewhichhas apredefined, defaultvalue for theContainerOpts attribute. TheContainerOpts attribute determineswhether the SRM-aware resource can run under Solaris Project. It alsodetermines whether the container information that is defined in the servicegroup’s ContainerInfo attribute is passed to the resource.See the Veritas Storage Foundation and High Availability SolutionsVirtualization Guide.

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 fileis accessed while starting Sybase server instances.

■ The VCS agent binaries for Sybase are now a part of VRTSvcsea package. Thispackage also includes the VCS agent binaries for DB2 and Oracle.

■ The agent supports a new attribute WaitForRecovery. If this attribute isenabled, during the online function, the agentwaits until recovery is completedand 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 nowoptimized to use a constanttime. LLT takes less than 16 seconds to start irrespective of the number oflinks 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 activeThis command filters the output of lltstat -nv to display the status ofonly the active nodes in the cluster.

■ lltstat -nv configuredThis command filters the output of lltstat -nv to display the status ofonly the configured nodes in the cluster. Configured nodes include activenodes and any additional nodes which are listed in the /etc/llthosts file.

See the lltstat manual page for more information.

■ Support for different link speeds for LLT linksLLT 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 theNICs with lesser speed as low-priority links to enhance LLT performance.

■ Support for destination-based load balancingLLT now also provides destination-based load balancing where the LLT linkis chosenbased on the destinationnode id and the port.With destination-basedload balancing, LLT sends all the packets of a particular destination on a link.

See the Veritas Cluster Server Installation Guide and the Veritas Cluster ServerAdministrator's Guide for more details.

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

■ GAB logging daemonGAB implements a distributed network protocol. For situations when GABdecides to take the drastic action of killing its userland client process orpanicking a node to resolve an issue, data from the affected node alone maynot suffice for a meaningful support analysis. The new gablogd daemonattempts to address this issue. GAB starts this daemon by default at GABconfiguration time.See the Veritas Cluster Server Administrator's Guide for more information.


24

Changes to I/O fencingThis section covers the new features and changes related to I/O fencing in thisrelease.

Support for preferred fencingTraditional fencing prevents a split-brain condition by allowing only one ofmultiple sub-clusters to continue its operation in case a network partition disruptsregular communication between nodes. The preferred fencing feature givespreference to one sub-cluster over other sub-clusters in determining the survivingsub-cluster. This preference is based on factors such as which of the sub-clustersis running higher priority applications or the total importance of nodes whichform that sub-cluster or both.

See the Veritas Cluster Server Installation Guide and the Veritas Cluster ServerAdministrator's Guide for more details.

Enhancements to server-based fencingThis release includes the following enhancements and new features related toserver-based fencing:

■ Single CP-server based fencingSupport to use a single highly available CP server that is configured on anSFHAcluster to provide server-based fencing support formultiple applicationclusters

Support to migrate between fencing modes when the clusteris runningThe vxfenswap utility now supports migrating between disk-based andserver-based fencing configurations in a cluster that is running.

See the Veritas Cluster Server Administrator's Guide for more details.

Changes to global clusteringVCS global clustering monitors and manages the replication jobs and clusters ateach site. In the event of a site outage, global clustering controls the shift ofreplication roles to the Secondary site, bring up the critical applications andredirects client traffic from one cluster to the other.

Before Release 5.1SP1, if there was a disaster at the Primary site or a networkdisruption, the applications were taken offline on the original Primary and failed


over to the Secondary. When the original Primary returned or the networkdisruption was corrected, you had the following options:

■ Manually resynchronize the original Primary with the data from the newPrimary, once the original Primary comes back up. The applications are onlyactive on the new Primary site.

■ Automatically resynchronize the original Primarywith the data from the newPrimary, once the original Primary comes back up. The applications are onlyactive on the new Primary site.

Beginning in Release 5.1SP1, you have a third option. Applications can be activeon both the original Primary and Secondary sites. After the original Primaryreturns or the network disruption is corrected, you have the option of specifyingwhich 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 isthat if a network disruption occurs, applications continue to run on the Primarysite and they are also failed over to the Secondary. This feature lets you maintainapplication availability on both sites while the network is down.

VCS system requirementsThis section describes system requirements for VCS.

The following information applies toVCS clusters. The information does not applyto SF Oracle RAC installations.

VCS requires that all nodes in the cluster use the sameprocessor architecture andrun the same operating system.

For example, in a cluster with nodes running Solaris, all nodes must run SolarisSPARC or Solaris x64.

All nodes in the cluster must run the same VCS version. Each node in the clustermay run a different version of the operating system, as long as the operatingsystem is supported by the VCS version in the cluster.

See “Hardware compatibility list” on page 26.

See “Supported Solaris operating systems” on page 27.

Hardware compatibility listThe compatibility list contains information about supported hardware and isupdated regularly. For the latest information on supported hardware go to thefollowing URL:

Release NotesVCS system requirements

26

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

Before installing or upgrading Veritas Cluster Server, review the currentcompatibility list to confirm the compatibility of your hardware and software.

Supported Solaris operating systemsThis release of theVeritas products is supported on the followingSolaris operatingsystems:

■ Solaris 9 (32-bit and 64-bit, SPARC) with Update 7, 8, and 9SymantecVirtualStore is only supported on Solaris 9 (SPARCPlatform64-bit).

Note: In the next major release, Veritas products will not support Solaris 9.

■ Solaris 10 (64-bit, SPARC or x86_64) with Update 6, 7, 8, and 9Solaris 10 (SPARC and x86_64) with Update 9 requires VRTSvxvm patch142629-08 (SPARC) or 142630-08 (x86_64)SymantecVirtualStore is only supported onSolaris 10 (SPARCorX86Platform64-bit).

For the most up-to-date list of operating system patches, refer to the ReleaseNotes for your product.

For important updates regarding this release, review the Late-Breaking NewsTechNote on the Symantec Technical Support website:


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

■ Veritas Storage Foundation (SF): VeritasVolumeManager (VxVM)withVeritasFile 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

27Release NotesVCS system requirements

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


Note: VCS supports the previous version of SF and the next version of SF tofacilitate product upgrades.

Supported VCS agentsTable 1-1 lists the agents for enterprise applications and the software that theagents support.

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

Solaris versionApplicationversion

ApplicationAgent

SPARC: Solaris 9, 10;

x64: Solaris 10

8.1, 8,2, 9.1,9.5, 9.7

DB2 EnterpriseServer Edition

DB2


x64: Solaris 10

11gR1,10gR2,11gR2

OracleOracle


x64: Solaris 10

12.5.x, 15.xSybase AdaptiveServer Enterprise

Sybase

See the Veritas Cluster Server Installation Guide for the agent for more details.

For a list of the VCS application agents and the software that the agents support,see the Veritas Cluster Server Agents Support Matrix at Symantec website.

Features no longer supported

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

■ Configuration wizards

■ CampusCluster agent

■ NFSLock agent.Use the NFSRestart agent to provide high availability to NFS lock records.

■ nfs_restart trigger.Use the NFSRestart agent to provide high availability to NFS lock records.

■ ServiceGroupHB agent.

Release NotesFeatures no longer supported

28

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

This release does not support disk heartbeats. Symantec recommends usingI/O fencing.

■ SANVolume agent

■ VRTSWebApp

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

■ VCS documentation package (VRTSvcsdc)The VCS documentation package (VRTSvcsdc) is deprecated. The softwaredisc contains the documentation for VCS in Portable Document Format (PDF)in the cluster_server/docs directory.Symantec recommends copying pertinent documents from the disc to yoursystem directory /opt/VRTS/docs for reference.

■ hahbsetup tool. This tool is removed as no supported feature requires thistool.

■ 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 SP1RP2 release, see theVeritasStorage Foundation and High Availability Solutions 5.1 SP1 RP2 Release Notes.

See the corresponding Release Notes for a complete list of fixed incidents relatedto that product.

LLT, GAB, and I/O fencing fixed issuesTable 1-2 lists 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 iofenceprocessing.

1840826

29Release NotesFixed issues

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

DescriptionIncident

[LLT] Removing the LLT links from a single node in a four-node clustercauses 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 withmessage “GabHandle::open failed errno=16” in syslog afterHAD is stoppedon all the nodes in the cluster simultaneously.

2005045

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

1859023

[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 whichinterpret NULL keys as valid for registrations/reservations.

1922413

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

1847517

[Fencing] Thevxfentsthdwutility uses scp to communicatewith the localhost.

1992560

[Fencing] The vxfenclearpre utility displays error messages1512956

[VxCPS] For a four-node cluster, the installer fails to configure server-basedfencingwhichuses three CP servers as its coordinationpoints. The processfails while registering the CP clients on the third CP server.

2143933

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

[VxCPS] The hamsg command does not load localized messages defined inthe VRTSvcsCPS.bmc file.

1886802

Bundled agents fixed issuesTable 1-3 lists the fixed issues for bundled agents.

Release NotesFixed issues

30

Table 1-3 Bundled agents fixed issues

DescriptionIncident

The IPMultiNICB agent does not support theOutsourcing Source Packet Address (OSPA)functionality. OSPA can be configured byusing the ndd ip_enable_group_ifs

command.

246635

The index number of the virtual interfaceschanges after a failover. As a resultapplications using the interfaces may facecommunication failure.

251704

Application agent does not pass the value ofCleanReason to the script that the Agentexecutes as per the value of theCleanProgramattribute.

252354

MultiNICB monitor does not store the PID ina cookie and traverses /procdirectory in everymonitor cycle. This leads to high CPU load incases where there are a lot of other processesrunning on the system.

426856

MultiNICB agent improperly deprecates thebase interface even when the CheckConfigattribute is set to 0.

1967957

If you restart HAD, online Share resourcesmay go offline.

1969191

In a frozen local service group, if a resourcegoes offline outside VCS control, aRemoteGroup resource also goes offline.

2001039

For a MultiNICB resource, if you change thevalue of the Device attribute, the resourcegoes into UNKNOWN state.

2016492

Share Agent reports an ONLINE resource asOFFLINE after hashadow restarts the HighAvailability Daemon (HAD) module.

2017266

MultiNICBdoesnot check if any interface outof its control is configured in the same subnet.

2019198


Table 1-3 Bundled agents fixed issues (continued)

DescriptionIncident

The OS determines the interface that thenotifier uses to send packets. The user mustbe optionally able to specify the interface.This is an enhancement.

2019904

If you upgrade to VCS 5.1, Applicationresources may go to the FAULTED state.

2045972

The Application agent tries to delete anuninitialized pointer during a clean entrypoint, and dumps a core file.

2064974

MountAgent doesnot unmount any loopbackmounts before taking them offline.

2101510

Local zone VxFSmounts that need FSCK (thefile system check command) cause the zoneto not come online.

2101530

Zone agent does not verify multi-usermilestone.

2101559

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

Table 1-4 VCS engine fixed issues

DescriptionIncident

If the OnlineRetryLimit and PreOnline attributes are set fora group, then the group does not fail over in case of a fault.

254693

At unfreeze of a failover group, VCS does not evaluate thegroup for Concurrency violation.

970971

A global group goes online on a remote site despite aconcurrency violation. This behavior is observed if a relatedgroup resource goes intentionally online on the remote site.

1074707

VCS must log an alert message to increase the value of theShutdownTimeout attribute on a multi-CPU computer.

1472734

If the GlobalCounter attribute does not increase at theconfigured interval, VCS must report the failure.

1634494


32

Table 1-4 VCS engine fixed issues (continued)

DescriptionIncident

If you configure theVxATunder ServiceManagement Facility(SMF) as well as under VCS, and run the shutdown -i6 -g0

-y command, then SMF marks VCS to be in MAINTENANCEstate.

1765594

In the Japanese locale, some messages do not appropriatelyappear.

1829709

When a parent group completely faults in a system zone, anonline-local-hard (OLH) child group fails over to anothersystem. This behavior is observed only if the child group ismarked for manual failover in campus cluster. That is, thevalue of the AutoFailover attribute for the group is equal to2.

1859387

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

1861740

When hashadow attempts to restart the High AvailabilityDaemon (HAD) module, if the/var/VRTSvcs/lock/.hadargs file does not exist,hashadow gets the SIGSEGV signal.

1866434

VCS sets theMonitorOnly attribute of the resources in a frozenservice group to 0. This behavior occurs even if theExternalStateChange attribute is not set to OfflineGroup fora resource that goes intentionally offline.

1874261

If a resource, with the ExternalStateChange attribute set toOfflineGroup, goes intentionally offline, VCS sets theMonitorOnly attribute of all resources in a frozen servicegroup to 0.VCSmust set theMonitorOnly attribute onlywhenrequired.

1874533

The hares command lets you have the "." special characterin a resource name.

1915908

Notifier Agent is unable to get the local IP address in thelinked-based IPMP.

1958245

If a service group faults during failover, then VCS may nothonor thePrerequisites/Limits attributes on the target system.

1971256


Table 1-4 VCS engine fixed issues (continued)

DescriptionIncident

A non-root user is unable to see the output of the hastatus-sum command, if you set the default scheduling class to FairShare Scheduler.

1979656

Thenotifier commandmust let you specify the originatingsource IP address. This is an enhancement.

2022123

If you override a static attribute for a resource with an emptytype definition, then VCS dumps duplicate entries for theattribute in the configuration file.

2061932

In a branded zone, the hastatus -sum command does notwork.

2081676

After a child group autostarts, VCS does not bring apartially-online parent to ONLINE state.

2081725

If you configure an online-local dependency between twoparallel groups, then the parent service group does notAutoStart on all nodes.

2083232

If the VCS configuration includes a file with an absolutepathname, then you cannot load templates from the clustermanager GUI.

2084961

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

2111296

If you add a script-basedWANheartbeat, the heartbeat agentgenerates a core file and fails to report status.

2128658

Enterprise agents fixed issuesTable 1-5 lists the fixed issues for enterprise agents.

Table 1-5 Enterprise agents fixed issues

DescriptionIncident

The Sybase agent offline script must support the databasesthat require a longer time to shut down. This is anenhancement.

776230


34

Table 1-5 Enterprise agents fixed issues (continued)

DescriptionIncident

When a user other than the user that installed the Oracledatabase starts the Oracle agent inside a container, the agentdoes not report the correct state of resources.

1916021

The Oracle agent monitor inside a zone does not work whenOracle directories inside the zone are NFS / NAS mounted .

1954724

When a user other than the user that installed the Oracledatabase starts theASMInst agent inside a container, the agentdoes not report the correct state of resources.

1972780

[Pri:2][Case:320-128-825][Datalink Corp][VCS Oracle agentunable to determine the online state of oracle database in localzone]

2101542

[ 312-019-554 for X M RADIO ]: Netlsnr offline got 'lost'2101553

[VCS][240-903-088][BT] WebLogic/ WebSphereMQ issuingtoo many hares commands

2101581

When the monitor entry function encounters an invalidprocess ID (PID) in a PID file, the function fails to detect theexit status of the process. This behavior occurs if the PID hasan empty line below it. The function also accordingly fails todetect 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

DescriptionFixedissues

In a zone, if there are multiple IPMultiNICB resources on the same subnet,issues occur with the source address of IP packets.

1975424

ASMInstAgent Monitor problem inside a zone where the Oracle homedirectory is NFS / NAS mounted inside the zone.

1972789

ASMInstAgent does not detect the state of the instance correctly inside localzones.

1972770

Postpatch script throws an error while installing in the non-global zonethough LLT and GAB are hollow packages.

1968572


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


ASMInstAgent dumps core.1962548

Oracle Agent Monitor problem occurs inside a zone where the Oracle homedirectory is NFS / NAS mounted inside the zone.

1954723

ASMDGAgent should disable and enable diskgroups in offline and onlineEPs for 11g R2.

1950427

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

vxfentsthdw should detect storage arrays which interpret NULL keys asvalid for registrations/reservations.

1922411

Changes made to Oracle agent via incident 1722109 do not honourContainerName attribute.

1916022

ASMagent connecting as sysdba instead of sysasm for 11gR21916004

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

1915909

Group stuck at OFFLINE|STOPPING state when there is no IP address to becleaned in IPMultiNICB.

1911287

If ExternalStateChange is not set to OfflineGroup, do not set MonitorOnlyto 0 .

1874267

LLT should give error if an attempt is made to configure more than 8 links(LLT_MAX_LINK) under LLT

1870424

IPMultiNICB:Resource does not come online when failing over from apanicked node.

1848114

GCO failover does not work when a user name includes "!".1504123

VCS 5.1 RP2 fixed issues

Table 1-7 Veritas Cluster Server 5.1 RP2 fixed issues


Partial parent group comes online after the child service group autostartsand an issue occurs in a service group failover after a node panics.

1937834


36



IPMultiNICB resource goes offline after mpathd failback.1952087

MultiNICB agent sets base interface DEPRECATED and NOFAILOVER flagseven if CheckConfig is set to 0.

1967955

SNMP Traps receiver displays trimmed output.1969999

Isssue occurs with Mount Agent handling loopback mounts.1970639

Issue occurs while executing the hastatus -sum command for a non-rootuser with FSS.

1979662

Memory leak occurs in LTT during unloading.1980252

Enhanced NFS agent must clear /etc/rmtab before starting mountd.1982648

Issue occurs while accessing a freed pointer in vxfend.1986311

Message ID errors occur in the Samba family of agents.2009127

Memory leaks occur in llt_dlpi_setup and llt_closenode paths.2011416

MultiNICB agent displays Unknown status after changing existing NICdevice.

2016490

MultiNICB agent faces issueswhen running thehaping command for IPv6addresses.

2017344

MultiNICB agent checks for interface out of its control which is configuredin same subnet.

2019202

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

New attribute must support fsck during zone boot for vxfs file systems forZone agent.

2021018

Share agent brings resource offline when HAD is restarted by hashadow.2025380

Errors occur in dlpiping utility while working in server mode.2031922

Issue occurs while executing the lltconfig –a set 1 link1

<ip-address> command .2031931

Application agent floodsengine log with "Container is not up" messages.2035239

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




Application agent deletes anuninitialized pointer during a clean entry point.2064973

HAD is killed in a heavily loaded system .2066986

Unwanted Solaris patch messages are logged into engine log while zoneresource goes online.

2077022

Parallel group in PARTIAL state autostarts when engine restarts.2077375

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

The halogin command fails when you bring a zone resource online forbranded zones.

2078802

Zone resource takes a long time to go down when the zone root file systemis forcefully unmounted .

2079596

Zone agent does not fault when its zone root no longer exists.2079601

Fencing support required for non SCSI-3 capable environments .2079854

Mismatching ContainerInfo displayed at group level and resource level.2079868

Zone agentmust removeUserNames addedduring online to allow successful_had snapshot of remote node(s).

2079977

The hastatus -sum command faces issues in a branded zone .2081674

The hastart command faces issue which fails with error messageGabHandle::open failed errno = 16.

2081741

GAB driver must be enhanced to prevent gabconfig -c while port 'a' isin the middle of iofence processing. Else, system may panic.

2086251

Thegabfd static array contains a stale entry if open succeeds and registrationfails.

2086273

Node panics after running the GTX tc.2086280

CP server which gets killed when CP client of higher version attempts tocommunicate with CPServer running version 5.1.

2089193

Packaging issue occurs in VCS where shutting down a branded zone fails.2092199

Zone agent must not run the zlogin halogin command if the user isalready created or if /.vcspwd file is already present.

2092201


38



TheNetlsnr agent issue occurs inside a zonewhere the agent fails tomonitorlistener if the Oracle home directory is NFS/NAS mounted inside the zone.

2096212

Zone agent must not detach zone root by adding attribute DetachZonePathwhich defaults to 1.

2097029

Zone agent must handle Sun bug 6757506 where zoneadm list fails causingZone resource to fault.

2102776

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

RFC check with DNS agent must be disabled..2083268

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

LVMVG goes not come online.2116161

Issue occurs inOracle detailedmonitoringwhen sendingSNMPnotificationon 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 allnodes 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 servicegroup must fail over after node panic.

1937834

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

2066967

Underheavy load,HADmaywait indefinitely inwaitpid()whenuser requeststo run some command through "hacli". This may cause GAB to kill HAD.

2071549

Overriding static attribute for any resource with empty type definitioncreates duplicate entries in main.cf

2077363

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

NFSRestart agent must remain online if HAD is forcefully stopped andrestarted.

2079617

nfs splitbrain test: Delay forced import of disk group agent to avoid errorsto 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 cpsadmcommands.

2089182

RemoteGroup resource appearsOFFLINE even after applying patch for issue1834858.

2102764

vxfenclearpre cannot clear keys fromcoordinator disks and data diskswhenthere 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 relatedto that product.

See “Documentation” on page 67.

NFS cluster I/O fails when storage is disabledThe 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 aredisabled, 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 installationThis 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 task completes (for examplechecking the description or requirements) the installer throws the license packagewarning. The warning reads:

Release NotesKnown issues

40

VRTSvlic not installed on system_name

Workaround:

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

Manual installation or uninstall of kernel component packagesand patches require boot archive updatesAfter manually installing and uninstalling the packages or the patchescorresponding to kernel components such as LLT, GAB, and VXFEN, make sureto update the boot archive. [2159242]

■ In case of primary boot environment, run the following command:

# bootadm update-archive

■ In case of an alternate root environment, run the following command:

# bootadm update-archive -R [altrootpath]

See the bootadm manual page for Solaris.

While configuring authentication passwords through theVeritas product installer, the double quote character is notaccepted (1245237)TheVeritas product installer prompts you to configure authentication passwordswhen you configure Veritas Cluster Server (VCS) as a secure cluster, or when youconfigure Symantec ProductAuthenticationService (AT) in authentication broker(AB) mode. If you use the Veritas product installer to configure authenticationpasswords, the double quote character (\") is not accepted. Even though this specialcharacter is accepted by authentication, the installer does not correctly pass thecharacters through to the nodes.

Workaround:There isnoworkaround for this issue.Whenenteringauthenticationpasswords, do not use the double quote character (\").

Errors observed during partial upgrade of SFHAWhile upgrading the VCS packages during an SFHA upgrade from 5.0 MP3 RP2to 5.1SP1, CPI failed to uninstall the I/O fencing packages (VRTSvxfen, VRTSllt,and VRTSgab). [1779129]

Workaround

41Release NotesKnown issues

Before upgrading SFHA from 5.0 MP3 RP2 to 5.1SP1, you must apply the I/Ofencing hotfix 5.0MP3RP2HF2.

Manual upgrade of VRTSvlic package loses keyless productlevels (2115662)If you upgrade the VRTSvlic package manually, the product levels that were setusing vxkeyless may be lost. The output of the vxkeyless display commandwill not display correctly.

To prevent this, perform the following steps while manually upgrading theVRTSvlic 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.

# pkgrm VRTSvlic

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

# pkgadd -d VRTSvlic.pkg

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 thesystem.As a result, youmay see periodic reminders being logged if theVOMserveris not configured.

This happens if you were using keyless keys before upgrading to 5.1SP1. Afterthe upgrade, you install real keys and run vxkeyless set NONE. In this case, thekeyless licenses may not be completely removed and you see warning messagesbeing logged after two months (if VOM server is not configured). This does notresult in any functionality impact.

To resolve this issue, perform the following steps:


42

1. Note down the list of products configured on the node for keyless licensing.Run vxkeyless display to display the list.

2. Set the product level to NONE with the command:

# vxkeyless set NONE

3. Find anddelete the keyless licenses left over in the system.Todo this, performthe following steps for every key stored in /etc/vx/licenses/lic:

■ Verify if the key has VXKEYLESS feature Enabled using the followingcommand:# vxlicrep -k <license_key> | grep VXKEYLESS

■ Delete the key if and only if VXKEYLESS feature is Enabled.

Note:When performing the search, do not include the .vxlic extension aspart of the search string.

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

# vxkeyless set product1[|,product]

Upgradeor uninstallationofVCSmayencountermoduleunloadfailuresWhen you upgrade or uninstall VCS, some modules may fail to unload with errormessages similar to the following messages:

fdd failed to stop on node_name

vxfs failed to stop on node_name

The issue may be observed on any one or all the nodes in the sub-cluster.

Workaround: After the upgrade or uninstallation completes, follow theinstructions provided by the installer to resolve the issue.

Installer is unable to split a cluster that is registered with oneor more CP serversSplitting 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 theinstaller. For example, you can split a cluster clus1 into clus1A and clus1B.

However, if you use the installer to reconfigure the VCS, the installer retains thesame cluster UUID of clus1 in both clus1A and clus1B. If both clus1A and clus1B


use the same CP servers for I/O fencing, then the CP server allows registrationonly from the cluster that attempts to register first. It rejects the registrationfrom the cluster that attempts next. Thus, the installer reports failure during thereconfiguration of the cluster that uses server-based fencing.

Workaround: None.

The installer enters an infinite loop because the cluster isalready running in securemodewhile configuring server-basedfencing (2166599)During server-based fencing configuration with a secure cluster, if vxfen fails tostart and you retry server-based fencing configuration, the installer keeps askingto enter another system to enable security after you manually start VCS.

Workaround:When vxfen fails to start in customized mode for server-basedfencing with a secure cluster, do not choose to retry configuring fencing, choosethe default option, then vxfen starts in disabled mode. You can also retry fencingconfiguration using -fencing option.

System moves to low system resources while bringing largenumber process resources online (2061338)When large number of resource like Process resources (1500 in number) isconfigured 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 bugagainst Red Hat "Issue #822253" exits. Red Hat has confirmed that this is theirissue. This issue does't appear on kernel version 2.6.18-194.el5 which they claimto have the fix for this issue.

Installed 5.0 MP3 without configuration, then upgrade to 5.1SP1, installer can not continue (2016346)If you install 5.0MP3 without configuration, you cannot upgrade to 5.1SP1. Thisupgrade path is not supported.

Workaround: Uninstall 5.0 MP3, and then install 5.1 SP1.

Operational issues for VCS

Issues with configuration of resource valuesIf you configure a resource that has more than 425 values in its ArgListValues,the agent managing that resource logs a message such as:


44

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

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

Normally, the number of values in ArgListValues for a resourcemust not exceed425. However, in case of a keylist, association or vector type of attribute appearsin theArgList for a resource-type. Since these attributes can takemultiple values,there is a chance for the resource values in ArgListValues to exceed 425.

The CmdServer process may not start in IPv6 environments insecure clustersIn an IPv6 environment on secure clusters, the CmdServer processmay not start.In addition, securitymaynot function correctly. If it does not start on a particularnode, 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

Missing host names in engine_A.log fileThe GUI does not read the engine_A.log file. It reads the engine_A.ldf file, getsthe message id from it, and then queries for the message from the bmc file of theappropriate locale (Japanese or English). The bmc file does not have systemnamespresent and so they are read as missing. [1736295]

Systems with multiple CPUs and copious memory shut-downtime may exceed the ShutdownTimeout attributeThe time taken by the system to go down may exceed the default value of theShutdownTimeout attribute for systems that have a large numbers of CPUs andmemory. [1472734 ]

Workaround: Increase the value of the ShutdownTimeout attribute based onyourconfiguration.

Parent group faulting in zone 1 results in the child group beingautomatically failed over to zone 2Parent group faulting in zone 1 results in the child group being automaticallyfailed over to zone 2. [1859387]


Errormessages displayedwhile uninstalling VCS 5.1SP1 patch(2128536)Description: The followingmessagesmaybedisplayedwhile uninstalling theVCS5.1SP1 patch.

Pkgadd failed. See /var/tmp/<*.log> for details

Patchrm is terminating.

WARNING: patchrm returned <7> for global zone

Done!

Resolution:This is an ignorable error/warningmessageand thepatch isuninstalledsuccessfully.

VCS Engine logs messages when it eventually connects to aremote clusterDescription: In a global cluster, if a local cluster fails to connect with a remotecluster in the first attempt but succeeds eventually, then youmay see the followingwarning 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 noimpact on any functionality.

Agent framework can reject hares -action command

When a probed resource is disabled and later enabled then, the agent frameworkcan reject hares -action command till the agent successfully monitors theresource.

New nodes get added to SystemList and AutoStartListattributes of ClusterService even if AutoAddSystemToCSG isdisabledThe AutoAddSystemToCSG attribute determines whether the newly joined oradded systems in a cluster become part of the SystemList of the ClusterServiceservice group if the service group is configured. The value 1 (default) indicatesthat 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 newnode to the cluster, the installermodifies the SystemList and AutoStartList attributes irrespective of whether


46

AutoAddSystemToCSG is enabled or disabled. The installer adds the new systemto the SystemList andAutoStartList. To addnodes, the installer uses the followingcommands 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 toSystemList and AutoStartList.

As a workaround, use the following commands to remove the nodes from theSystemList and AutoStartList:

# hagrp –modify ClusterService SystemList –delete newnode

# hagrp –modify ClusterService AutoStartList –delete newnode

Issues related to the bundled agents

Entry points that run inside a zone are not cancelled cleanlyCancelling entry points results in the cancellation of only the zloginprocess. Thescript entrypoints that run inside a zone are forkedoff using thezlogin command.However, thezlogin command forks off ansh command,which runs in the contextof the Solaris zone. This shell process and its family do not inherit the group idof the zlogin process, and instead get a new group id. Thus, it is difficult for theagent framework to trace the children or grand-children of the shell process,which translates to the cancellation of only the zlogin process. [1179695]

Workaround: Oracle must provide an API or a mechanism to kill all the childrenof the zlogin process that was started to run the entry point script in thelocal-zone.

Solaris mount agent fails to mount Linux NFS exporteddirectoryThe Solaris mount agent mounts the mount directories. At this point, if it triesto mount a Linux NFS exported directory, the mount fails showing the followingerror:

nfs mount: mount: <MountPoint>: Not owner

This is due to system NFS default version mismatch between Solaris and Linux.


The workaround for this is to configure MountOpt attribute in mount resourceand set vers=3 for it.

Example

root@north $ mount -F nfs south:/test /logo/

nfs mount: mount: /logo: Not owner

root@north $

Mount nfsmount (

MountPoint = "/logo"

BlockDevice = "south:/test"

FSType = nfs

MountOpt = "vers=3"

)

The zpool command runs into a loop if all storage paths froma node are disabledThe Solaris Zpool agent runs zpool commands to import and export zpools. If allpaths to the storage are disabled, the zpool command does not respond. Instead,the zpool export command goes into a loop and attempts to export the zpool. Thiscontinues till the storage paths are restored and zpool is cleared. As a result, theoffline and clean procedures of Zpool Agent fail and the service group cannot failover to the other node.

Workaround: Youmust restore the storagepaths and run the zpool clear commandfor all the pending commands to succeed. This will cause the service group to failover to another node.

VolumeSet messages do not display in the engine log onJapanese localeTheVolumeSetmessages donot get displayed in the engine log on Japanese locale.

Workaround: None.

Issues related to the VCS database agents

VCSagent forOracle: Health checkmonitoring is not supportedfor Oracle database 11g R1 and 11g R2 (1985055)Health checkmonitoring is not supported for Oracle database 11g R1 and 11g R2.

Workaround: Set MonitorOption attribute for Oracle resource to 0.


48

VCS agent for Oracle: Health check monitoring does not workwith Oracle 10.2.0.4The health check monitoring in Oracle agent does not work with Oracle 10.2.0.4due to incompatibility of the health check APIs provided by Oracle. [2101570]

Resolution:Disablehealth checkmonitoringby setting theMonitorOptionattributeto 0 (zero).

VCS agent for Oracle: Make sure that the ohasd has an entryin the init scriptsMake sure that the ohasd process has an entry in the init scripts so that when theprocess is killed or the machine is rebooted, this automatically restarts theprocess.[1985093]

Workaround: Respawn of ohasd process. Add the ohasd process inthe/etc/inittab file to ensure that this process is automatically restarted whenkilled or the machine is rebooted.

VCS agent for Oracle: Intentional Offline does not workDue to issues with health checkmonitoring, Intentional Offline does not work forVCS agent for Oracle.

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

Workaround:

Have a copy of the pfile/spfile in the default $GRID_HOME/dbs directory tomakesure that this would be picked up during the ASM Instance startup.

VCS agent for ASM: Health check monitoring is not supportedfor ASMInst agentThe 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 anode and if theOracle instance is online on any other nodewithin the cluster,the instancewould comeup.However, the database doesnot getmounted. In suchcircumstances, this startup attempt is detected by basic monitoring. If detailmonitoring is enabled, this startup attempt does not get detected.

Workaround: No workaround.

Issues related to the agent framework

English text while using 'hares -action' command (1786742)Description: The output of hares –action is displayed in English text and not inyour configured locale.

Resolution: No resolution.

Agent framework cannot handle leading and trailing spacesfor the dependent attributeAgent framework does not allow spaces in the target resource attribute name ofthe dependent resource.

Workaround

Do not provide leading and trailing spaces in the target resource attribute nameof the dependent resource.

The agent framework does not detect if service threads hanginside an entry pointIn rare cases, the agent framework does not detect if all service threads hanginside 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 torestart the agent. Use the following command: kill -9 hung agent's pid. Thehaagent -stop command does not work in this situation.


50

The ArgListValues attribute values for dependent resourcesmay not populate correctly when a target resource is deletedand re-addedFor resource attributes, deleting a resource prevents a dependent attribute’s valuefrom refreshing in the dependent resource’s value.

For example, you have resource (rD), which depends on a resource’s attributevalue (rT:Attr_rt).When you delete the target resource (rT), and re-add it (rT), thedependent 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 anempty string.

# hares -modify rD target_res_name ""

Where rD is the nameof the dependent resource, and target_res_name is the nameof the reference attribute that contains the name of the target resource.

Set the value of the reference attribute (target_res_name) to the nameof the targetresource (rT).

# hares -modify rD target_res_name rT

Agent performance and heartbeat issuesDepending on the system capacity and the number of resources configured underVCS, the agent may not get enough CPU cycles to function properly. This canprevent the agent from producing a heartbeat synchronously with the engine. Ifyou notice poor agent performance and an agent's inability to heartbeat to theengine, 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

Where agent_type is the type of agent, for example Application or FileOnOff. Ifyou 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 valueof the AgentReplyTimeout attribute value. (Up to 300 seconds or as necessary.)[1853285]

Issues related to Live Upgrade

The VRTSvcsea package removal fails while removing it fromthe alternate disk during live upgrade (2096925)Description: This is because the pre-remove script of VRTSvcsea checks if any ofthe following agent is running:

■ ASMDG

■ ASMInst

■ Db2udb

■ Netlsnr

■ Oracle

■ Sybase

■ SybaseBk

Therefore, even if agents are running from the first disk, we cannot remove thepackage from second disk.

Resolution: Stop any of the running agents before removing the package.

Live Upgrademay fail on Solaris 9 if packages and patches arenot current (2052544)Live Upgrade may fail on a Solaris 9 host if a VxFS file system is in /etc/vfstab.

Workaround:On theSolaris 9host, install the LiveUpgradepackages SUNWlucfg,SUNWluu, and SUNWlur from a Solaris 10 image. After you install the packages,install the latest Live Upgrade patch.

For more information on required packages and patches, visit the following siteand search on "Live Upgrade requirements."

http://wikis.sun.com


52

http://wikis.sun.com

Issues related to VCS in Japanese localesThis section covers the issues that apply to VCS 5.1 in a Japanese locale.

The GetSafeMsg() returns error when one of the parametersis already localizedSome log messages that use the date-string parameter may not print correctly innon-English locales. [1715258, 1825966]

The gcoconfig script displays error messages in EnglishThe gcoconfig script incorrectly displays English error messages. [1416136 ]

The hahbsetup command displays messages and warnings inEnglishThe hahbsetup command incorrectly displaysmessages andwarnings in English.[1652562]

The hares -action command displays output in EnglishThe hares -action command incorrectly displays output in English. [1786747]

Listener startup message on ja_JP.PCK locale may not bedisplayed correctly in the engine log (2075471)Description: When you start the listener resource in VCS on ja_JP.PCK locale, thelsnrctl start command output is not shown correctly in the engine log. Thishappens because the converted output from the command generates specialcharacters which are not handled by halog command.

Resolution: You can ignore this message as it does not have any functionalityimpact for the listener resource.

Issues related to global clusters

The engine log file receives too many log messages on thesecure site in global cluster environmentsWhen the WAC process runs in secure mode on one site, and the other site doesnot use secure mode, the engine log file on the secure site gets logs every fiveseconds. [1539646]


Workaround: The two WAC processes in global clusters must always be startedin either secure or non-securemode. The secure andnon-secureWACconnectionswill 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 secondarysiteThe application service group comes online on the primary sitewhile the fire drillservice group attempts to go offline at the same time, causing the applicationgroup to fault. (2107386)

Workaround: Ensure that the fire drill service group is completely offline on thesecondary site before the application service group comes online on the primarysite.

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

LLT port stats sometimes shows recvcnt larger than recvbytesWith each received packet, LLT increments the following variables:

■ recvcnt (increment by one for every packet)

■ recvbytes (increment by size of packet for every packet)

Both these variables are integers. With constant traffic, recvbytes hits and rollsover MAX_INT quickly. This can cause the value of recvbytes to be less than thevalue of recvcnt. [1788315]

This does not impact the LLT functionality.

LLTmay incorrectly declare port-level connection for nodes inlarge cluster configurationsWhenports get registered andunregistered frequently on the nodes of the cluster,LLT may declare that a port-level connection exists with another peer node. Thisoccurs in some corner cases even though a port is not even registered on the peernode. [1809827]

Issues related to I/O fencingThis section covers the known issues related to I/O fencing in this release.


54

All nodes in a sub-cluster panic if the node that races for I/Ofencing panicsAt the time of a network partition the lowest node in each sub-cluster races forthe coordination points on behalf of that sub-cluster. If the lowest node is unableto contact a majority of the coordination points or the lowest node itselfunexpectedly panics during the race, then all the nodes in that sub-cluster willpanic. [1965954]

CoordinationPoint agentdoesnotprovidedetailed logmessagefor inaccessible CP serversThe Coordination Point agent does not log detailed information of the CP serversthat are inaccessible.WhenCP server is not accessible, the agent does notmentionthe UUID or the virtual IP of the CP server in the engine log. [1907648]

Preferred fencing does notwork as expected for large clustersin certain casesIf you have configured system-based or group-based preferred fencing policy,preferred fencing does not work if all the following cases are true:

■ The fencing setup uses customized mode with one or more CP servers.

■ The application cluster has more than eight nodes.

■ The node weight for a single node (say galaxy with node id 0) is more than thesum total of node weights for the rest of the nodes.

■ Anetwork fault occurs and the cluster partitions into twowith the single node(galaxy) on one part and the rest of the nodes on the other part.

Under such circumstances, for group-based preferred fencing, the single nodepanics even though more high priority services are online on that node. Forsystem-based preferred fencing, the single node panics even thoughmoreweightis assigned to the node. [2161816]

See the Veritas Cluster Server Administrator's Guide for more information onpreferred fencing.

Server-based I/O fencing fails to start after configuration onnodes with different locale settingsOn each (application cluster) node, the vxfen module retrieves and stores the listof the UUIDs of coordination points. When different nodes have different localesettings, the list of UUIDs on one (application) node does not match with that of


the other (application) nodes.Hence, I/O fencingdoesnot start after configuration.[2112742]

Workaround: Start I/O fencing after fixing the locale settings to use the samevalues on all the (application) cluster nodes.

Reconfiguring VCS with I/O fencing fails if you use the sameCP serversWhen you reconfigure an application cluster that uses server-based I/O fencing(customized fencing mode), the installer does not remove the application clusterinformation from the CP servers before the reconfiguration. As a result, if youreconfigure the application cluster and choose to configure I/O fencing incustomizedmodeusing the sameCP servers, then reconfiguration of server-basedfencing for the application cluster fails. [2076240]

Workaround: Manually remove the application cluster information from the CPservers after you reconfigure VCS but before you reconfigure server-based I/Ofencing for the application cluster.

See the Veritas Cluster Server Administrator's Guide for instructions to removethe application cluster information from the CP servers.

CP server cannot bind to multiple IPs (2085941)Coordination point server (CP server) binds only to a single virtual IP and listenson the same. Application clusters cannot access the CP server if it fails to establishconnection to this virtual IP. Therefore, if the connection fails because of thesubnet in which the virtual IP of the CP server exists, you cannot access the CPserver even if there is another subnet throughwhich the client can connect to theCP server over a different IP.

Resolution: No known resolution for this issue.

Delay in rebooting Solaris 10 nodes due to vxfen servicetimeout issuesWhen you reboot the nodes using the shutdown -i6 -g0 -y command, thefollowing error messages may appear:

svc:/system/vxfen:default:Method or service exit

timed out. Killing contract 142

svc:/system/vxfen:default:Method "/lib/svc/method/vxfen stop"

failed due to signal Kill.


56

This error occurs because the vxfen client is still active when VCS attempts tostop I/O fencing. As a result, the vxfen stop service times out anddelays the systemreboot. [1897449]

Workaround: Perform the following steps to avoid this vxfen stop service timeouterror.

To avoid the vxfen stop service timeout error

1 Stop VCS. On any node in the cluster, run the following command:

# hastop -all

2 Reboot the systems:

# shutdown -i6 -g0 -y

VXFEN service goes to maintenance mode when restarted ifthe VCS engine is runningOn Solaris 10, if you restart the vxfen service when the VCS engine is running,then the vxfen service goes intomaintenancemode. Youmust stop theVCS enginebefore you restart or disable the vxfen service, and then enable the vxfen service.[2116219]

Issues related to Symantec Product Authentication Service with VCSThis section covers the known issues related to Symantec Product AuthenticationService (AT) in this release.

The vcsat and cpsat commands may appear to be hungThe following commandsmay appear to be hung when you invoke them from thecommand shell:

■ /opt/VRTScps/bin/cpsat

■ /opt/VRTSvcs/bin/vcsat

This issue occurs when the command requires some user interaction. [1841185]

Workaround:

■ To fix the issue for vcsat, run the commands as follows:

# export EAT_HOME_DIR=/opt/VRTSvcs

# /opt/VRTSvcs/bin/vssatvcs command_line_argument

# unset EAT_HOME_DIR


■ To fix the issue for cpsat, run the commands as follows:

# export EAT_HOME_DIR=/opt/VRTScps

# /opt/VRTScps/bin/vssatcps command_line_argument

# unset EAT_HOME_DIR

VCS may report AT error during system rebootWhen you reboot the systems using the shutdown –i6 –g0 -y command, VCSreports the following AT error in the /var/adm/messages file and the/var/VRTSvcs/log/engine_A.log file, and VCS faults the VxSS servicegroup.[1765594]

VCS ERROR V-16-1-13067 (host_name) Agent is calling clean

for resource (vxatd) because the resource became OFFLINE

unexpectedly, on its own.

VxSS State s245sf2 |OFFLINE|FAULTED|

VxSS State s245sf3 |ONLINE|

Workaround: This error occurs due to a timing issue and this message may besafely ignored.

Veritas Cluster Server agents for Veritas Volume Replicator knownissues in 5.1 SP1

No known issues exist for Veritas Storage Foundation Cluster File System in the5.1SP1 release.

Issues with bunker replayWhen ClusterFailoverPolicy is set to Auto and the AppGroup is configured onlyon some nodes of the primary cluster, global cluster immediately detects anysystem fault at the primary site andquickly fails over theAppGroup to the remotesite. VVRmight take longer to detect the fault at the primary site and to completeits configuration changes to reflect the fault.

This causes the RVGPrimary online at the failover site to fail and the followingmessage is displayed:

RVGPrimary:RVGPrimary:online:Diskgroup bunkerdgname

could not be imported on bunker host hostname. Operation

failed with error 256 and message VxVM

VVR vradmin ERROR V-5-52-901 NETWORK ERROR: Remote server

unreachable...


58

Timestamp VCS ERROR V-16-2-13066 (hostname) Agent is calling

clean for resource(RVGPrimary) because the resource

is not up even after online completed.

Resolution: To ensure that global clustering successfully initiates a bunker replay,Symantec recommends that you set the value of the OnlineRetryLimit attributeto a non-zero value for RVGPrimary resource when the primary site has a bunkerconfigured.

Issues related to AMF driver

AMF driver fails to unload with the Mount Agent runningIfMountAgent uses IMF tomonitormounts of typeVxFS, thenyou cannot unloadAMF driver as long as Mount Agent is running. [2262747]

Workaround: Stop the mount agent before you unload the AMF driver.

Issues related to IMF

Could not register process and skipping inactive eventmessages seen in engine log (2700482)You may see the following error messages in the engine log:

2012/02/12 20:08:55 VCS ERROR V-16-10001-20565

Application:app1:imf_register:Could not register process

(/ApplicationTest/app_test_start) as part of resource (app1), errno <17>

Where errno <17> indicates that the event is already registered with AMF.

However, at this stage the amfstat output does not show this event as registered.After running the amfstat command, the following messages are logged inamfconfig –p dbglog.

809261 proff_event.c:240 AMF_TR skipping inactive

event (30017f3c740) 809261 proff_event.c:327 AMF_TR The number

of proff events changed between ioctls ask_cnt=1 I=0

Once VCS gets into this state, IMF registration for the particular resource doesnot succeed, unless the AMF driver is unconfigured and reconfigured. However,traditional monitoring continues for that resource and the overall functionalityremains unaffected.

Workaround: No workaround.


Software limitationsThis section covers the software limitations of this release.


Limitations related to the VCS engine

VCSdeletes user-definedVCSobjects that use theHostMonitorobject namesIf you had defined the following objects in the main.cf file using the reservedwords for theHostMonitor daemon, then VCS deletes these objects when the VCSengine starts. [1293092]

■ Any group that you defined as VCShmg along with all its resources.

■ Any resource type that youdefined asHostMonitor alongwith all the resourcesof such resource type.

■ Any resource that you defined as VCShm.

Limitations related to the bundled agents

Programs using networked services may stop responding ifthe host is disconnectedPrograms using networked services (for example, NIS, NFS, RPC, or a TCP socketconnection to a remote host) can stop responding if the host is disconnected fromthe network. If such a program is used as an agent entry point, a networkdisconnect can cause the entry point to stop responding and possibly time out.

For example, if the host is configured to useNISmaps as a client, basic commandssuch as ps -ef can hang if there is network disconnect.

Symantec recommends creating users locally. To reflect local users, configure:

/etc/nsswitch.conf

Limitations of the DiskGroup agentVolumes in disk group are started automatically if the Veritas Volume Managerdefault value of AutoStartVolumes at system level will be set to ON irrespectiveof the value of the StartVolumes attribute defined inside the VCS. SetAutoStartVolumes to OFF at system level if you do not want to start the volumesas part of import disk group.

Release NotesSoftware limitations

60

Mount resources can cause core dumpsDue to a known Solaris issue, certain system calls create memory leaks that canlead to a coredump.Thishappens in situationswhere theMount resource's FSTypeattribute has a value of nfs, and is exacerbated when the resource is for anon-global zone and the value of the SecondLevelMonitor attribute is 1. [1827036]

Volume agent clean may forcibly stop volume resourcesWhen the attribute FaultOnMonitorTimeouts calls the Volume agent clean entrypoint after a monitor time-out, the vxvol -f stop command is also issued. Thiscommand forcibly stops all volumes, even if they are still mounted.

False concurrency violation when using PidFiles to monitorapplication resourcesThe PID files created by an application contain the PIDs for the processes thatare monitored by Application agent. These files may continue to exist even aftera node running the application crashes. On restarting the node, the operatingsystem may assign the PIDs listed in the PID files to other processes running onthe node.

Thus, if the Application agent monitors the resource using the PidFiles attributeonly, the agentmaydiscover the processes running and report a false concurrencyviolation. This could result in some processes being stopped that are not underVCS control.

Volumes in a disk group start automatically irrespective of thevalue of the StartVolumes attribute in VCSVolumes in a disk group are started automatically if the value of the system levelattribute autostartvolumes in Veritas Volume Manager is set to On, irrespectiveof the value of the StartVolumes attribute in VCS.

Workaround

If you do not want the volumes in a disk group to start automatically after theimport of a disk group, set the autostartvolumes attribute to Off at the systemlevel.

Limitations related to IMF■ IMF registration on Linux for “bind” file system type is not supported.

■ In case of SLES11 SP1:

61Release NotesSoftware limitations

IMF should not be enabled for the resourceswhere the BlockDevice can getmounted on multiple MountPoints.

■

■ If FSType attribute value is nfs, then IMF registration for “nfs” file systemtype is not supported.

Limitations related to the VCS database agents

DB2 RestartLimit valueWhen multiple DB2 resources all start at the same time with no dependencies,they tend to interfere or race with each other. This is a known DB2 issue.

The default value for the DB2 agent RestartLimit is 3. This higher value spreadsout the re-start of theDB2 resources (after a resource online failure), which lowersthe chances of DB2 resources all starting simultaneously. [1231311]

Limitation with intentional offline functionality of VCS agentfor OracleThe Oracle resource never faults after an intentional offline.

Intentional offline functionality of VCS agent for Oracle requires you to enablehealth check monitoring. The agent uses Oracle's Health Check API to find thestate of the database. If the API returns a graceful shutdown for the database,then the agent marks the resource state as INTENTIONAL OFFLINE. Later if theOracle agent's online function does not succeed, the agent does not mark theresource as FAULTED. The state remains as INTENTIONALOFFLINE because theagent receives the database state from the API as graceful shutdown during eachmonitor cycle. [1805719]

Limitations related to global clusters■ Cluster address for global cluster requires resolved virtual IP.

The virtual IP addressmust have aDNS entry if virtual IP is used for heartbeatagents.

■ Total number of clusters in a global cluster configuration can not exceed four.

■ Cluster may not be declared as faulted when Symm heartbeat agent isconfigured even when all hosts are down.The Symm agent is used to monitor the link between two Symmetrix arrays.When all the hosts are down in a cluster but the Symm agent is able to see thereplication link between the local and remote storage, it would report the


62

heartbeat as ALIVE. Due to this, DR site does not declare the primary site asfaulted.

Engine hangs when you perform a global cluster upgrade from 5.0MP3in mixed-stack environments

If you try to upgrade a mixed stack VCS environment (where IPv4 and IPv6 arein use), from 5.0MP3 to 5.1SP1, HAD may hang.

Workaround: When you perform an upgrade from 5.0MP3, make sure no IPv6addresses are plumbed on the system.[1820327].

Use VCS installer to install or upgrade VCS when the zone root is onVxFS shared storage

You must use the VCS installer program to install or upgrade VCS when the zoneroot is on Veritas File System (VxFS). [1215671]

Systems in a cluster must have same system locale settingVCS does not support clustering of systems with different system locales. Allsystems in a cluster must be set to the same locale.

VxVM site for the disk group remains detached after node reboot incampus clusters with fire drill

When you bring the DiskGroupSnap resource online, the DiskGroupSnap agentdetaches the site from the target disk group defined. The DiskGroupSnap agentinvokesVCS action entry points to runVxVMcommands to detach the site. Thesecommands must be run on the node where the disk group is imported, which isat the primary site.

If you attempt to shut down the nodewhere the fire drill service group or the diskgroup is online, the node goes to a LEAVING state. The VCS engine attempts totake all the service groups offline on that node and rejects all action entry pointrequests. Therefore, theDiskGroupSnapagent cannot invoke the action to reattachthe fire drill site to the target disk group. The agent logs a message that the nodeis in a leaving state and then removes the lock file. The agent’s monitor functiondeclares that the resource is offline. After the node restarts, the disk group sitestill remains detached. [1272012]

Workaround:

You must take the fire drill service group offline using the hagrp -offline

command before you shut down the node or before you stop VCS locally.


If the node has restarted, youmustmanually reattach the fire drill site to the diskgroup that is imported at the primary site.

If the secondary node has crashed or restarted, you must manually reattach thefire drill site to the target disk group that is imported at the primary site usingthe following command: /opt/VRTSvcs/bin/hares -action $targetres joindg

-actionargs $fdsitename $is_fenced -sys $targetsys.

Limitations with DiskGroupSnap agentThe DiskGroupSnap agent has the following limitations:

■ If youuse theBronze configuration for theDiskGroupSnap resource, you couldend up with inconsistent data at the secondary site in the following cases:[1391445]

■ After the fire drill service group is brought online, a disaster occurs at theprimary site during the fire drill.

■ After the fire drill service group is taken offline, a disaster occurs at theprimary while the disks at the secondary are resynchronizing.

Symantec recommends that you use the Gold configuration for theDiskGroupSnap resource.

Cluster Manager (Java console) limitationsThis section covers the software limitations for Cluster Manager (Java Console).

Use the VCS 5.1 Java Console to manage clustersCluster Manager (Java Console) from versions lower than VCS 5.1 cannot be usedto manage VCS 5.1SP1 clusters. Symantec recommends using the latest versionof Cluster Manager.

See the Veritas Cluster Server Installation Guide for instructions on upgradingCluster Manager.

Run Java Console on a non-cluster systemSymantec recommendsnot runningClusterManager (JavaConsole) for anextendedperiod on a node in the cluster. The Solaris version of the Java Virtual Machinehas amemory leak that cangradually consume thehost system’s swap space. Thisleak does not occur on Windows systems.


64

Cluster Manager does not work if the hosts file contains IPv6entriesVCS Cluster Manager fails to connect to the VCS engine if the /etc/hosts filecontains IPv6 entries.

Workaround: Remove IPv6 entries from the /etc/hosts file.

VCS Simulator does not support I/O fencingWhen running the Simulator, be sure the UseFence attribute is set to the default,“None”.

The operating system does not distinguish between IPv4 and IPv6packet counts

In a dual-stack configuration, when you use packet counts and the IPv6 networkis disabled, the NIC agent might not detect a faulted NIC. It might not detect afault because while the IPv6 network is down its packet count still increases. Thepacket count increases because the operating systemdoesnot distinguish betweenthe packet counts for IPv4 and IPv6 networks. The agent then concludes that theNIC is up. If you are using the same NIC device for IPv4 as well as IPv6 resources,set PingOptimize to 0 and specify a value for theNetworkHosts attribute for eitherthe IPv6 or the IPv4 NIC resource. [1061253]

Limitations related to I/O fencingThis section covers I/O fencing-related software limitations.

Stopping systems in clusters with I/O fencing configuredThe I/O fencing feature protects against data corruption resulting from a failedcluster interconnect, or “split brain.”See theVeritasClusterServerAdministrator'sGuide for a description of the problems a failed interconnect can create and theprotection I/O fencing provides.

I/O fencing uses SCSI-3 PR keys to implement data protection. Keys are placedon I/O fencing coordinator points and on data disks. The VCS administratormustbe aware of several operational changes needed when working with clustersprotected by I/O fencing. Specific shutdown procedures ensure keys are removedfrom coordinator points and data disks to prevent possible difficulties withsubsequent cluster startup.

Using the reboot commandrather than theshutdowncommandbypasses shutdownscripts and can leave keys on the coordinator points and data disks. Depending


on the order of reboot and subsequent startup events, the cluster may warn of apossible split brain condition and fail to start up.

Workaround: Use the shutdown -r command on one node at a time and wait foreach node to complete shutdown.

Documentation errataThe following sections, if present, cover additions or corrections for Documentversion: 5.1SP1.1 of the product documentation. These additions or correctionsmay be included in later versions of the product documentation that can bedownloaded from the Symantec Support website and the Symantec OperationsReadiness Tools (SORT).

See the corresponding Release Notes for documentation errata related to thatcomponent or product.


See “About Symantec Operations Readiness Tools” on page 9.

Veritas Cluster Server Installation GuideIn theUpgradingusingLiveUpgrade chapter, use the vxlustart command insteadof the vcslustart command in all instances.

Veritas Cluster Server Administrator's GuideThis section covers the documentation errata in the Veritas Cluster ServerAdministrator's Guide.

Correction for setting up a disaster recovery fire drillTopic: Setting up a disaster recovery fire drill

Issue: The content below is incorrect:

After the fire drill service group is taken offline, reset the value of theReuseMntPtattribute to 1 for all Mount resources.

Use the following corrected information:

After the fire drill service group is taken offline, reset the value of theReuseMntPtattribute to 0 for all Mount resources.

Release NotesDocumentation errata

66

DocumentationProduct guides are available on the documentation disc in PDF formats. Symantecrecommends copyingpertinent information, suchas installationguides and releasenotes, from the disc to your system's /opt/VRTS/docs directory for reference.

Documentation setTable 1-8 lists the documents for Veritas Cluster Server.

Table 1-8 Veritas Cluster Server documentation

File nameTitle

vcs_install_51SP1_sol.pdfVeritas Cluster Server Installation Guide

vcs_notes_51SP1_sol.pdfVeritas Cluster Server Release Notes

vcs_admin_51SP1_sol.pdfVeritas Cluster Server Administrator’s Guide

vcs_bundled_agents_51SP1_sol.pdfVeritas Cluster Server Bundled Agents ReferenceGuide

vcs_agent_dev_51sp1pr4.pdfVeritas Cluster Server Agent Developer’s Guide

vcs_vvr_agent_51SP1_sol.pdfVeritas Cluster Server Agents for Veritas VolumeReplicator Configuration Guide

vcs_dynamic_reconfig_51SP1_sol.pdfVeritas Cluster Server ApplicationNote: DynamicReconfiguration for Oracle Servers

sfha_virtualization_51SP1_sol.pdfVeritas Storage Foundation andHighAvailabilitySolutions Virtualization Guide

vcs_db2_agent_51SP1_sol.pdfVeritas Cluster Server Agent for DB2 Installationand Configuration Guide

vcs_oracle_agent_51SP1_sol.pdfVeritasClusterServerAgent forOracle Installationand Configuration Guide

vcs_sybase_agent_51SP1_sol.pdfVeritasClusterServerAgent forSybase Installationand Configuration Guide

Table 1-9 lists the documentation for Veritas Volume Replicator.

67Release NotesDocumentation

Table 1-9 Veritas Volume Replicator documentation

File nameDocument title

vvr_admin_51SP1_sol.pdfVeritasVolumeReplicatorAdministrator’sGuide

vvr_planning_51SP1_sol.pdfVeritas Volume Replicator Planning and TuningGuide

vvr_advisor_users_51SP1_sol.pdfVeritas Volume Replicator Advisor User's Guide

Table 1-10 lists the documentation for Symantec Product Authentication Service(AT).

Table 1-10 Symantec Product Authentication Service documentation

File nameTitle

vxat_notes.pdfSymantecProductAuthenticationServiceReleaseNotes

vxat_admin.pdfSymantec Product Authentication ServiceAdministrator's Guide

Manual pagesThemanual pages forVeritas StorageFoundation andHighAvailability Solutionsproducts are installed in the /opt/VRTS/man directory.

Set the MANPATH environment variable so the man(1) command can point to theVeritas Storage Foundation manual pages:

■ For the Bourne or Korn shell (sh or ksh), enter the following commands:

MANPATH=$MANPATH:/opt/VRTS/man

export MANPATH

■ For C shell (csh or tcsh), enter the following command:

setenv MANPATH ${MANPATH}:/opt/VRTS/man

See the man(1) manual page.

Release NotesDocumentation

68

Date post:	28-Mar-2020
Category:	Documents
Upload:	others
View:	1 times
Download:	0 times

Veritas Cluster Server Release Notes · 2012-09-21 · Release Notes This document includes the...

Documents