您的当前位置：首页正文

VCS3.5

来源：知库网

™

VERITAS Cluster ServerRelease Notes

Solaris

3.5

July 200230-000803-011

Disclaimer

The information contained in this publication is subject to change without notice.VERITAS Software Corporation makes no warranty of any kind with regard to thismanual, including, but not limited to, the implied warranties of merchantability andﬁtness for a particular purpose. VERITAS Software Corporation shall not be liable forerrorscontainedhereinorforincidentalorconsequentialdamagesinconnectionwiththefurnishing, performance, or use of this manual.

Copyright © 1998-2002 VERITAS Software Corporation. All rights reserved. VERITAS,VERITAS SOFTWARE, the VERITAS logo, VERITAS Cluster Server, and all otherVERITAS product names and slogans are trademarks or registered trademarks of

VERITASSoftwareCorporationintheUSAand/orothercountries.Otherproductnamesand/or slogans mentioned herein may be trademarks or registered trademarks of theirrespective companies.

VERITAS Software Corporation350 Ellis St.

Mountain View, CA 94043Phone 650–527–8000Fax 650–527–2908www.veritas.com

Contents

Package Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1Hard-Copy Documentation Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2VERITAS Documentation Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3Manual Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4Supported Hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6Unsupported Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8Supported Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8Requirements for the VCS Graphical User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8Required Patches for Configuration Editor and Cluster Manager. . . . . . . . . . . . . . . . . .8Installing or Upgrading to VCS 3.5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9Migrating from FirstWatch or VERITAS-HA to VCS. . . . . . . . . . . . . . . . . . . . . . . . . . . . .9Obtaining License Keys for VCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9New Features in VCS 3.5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10Bundled Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12Enterprise Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13Custom Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14Software Limitations in VCS 3.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15Known Issues in VCS 3.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19Features Introduced in Previous Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21Software Fixes and Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

iii

ivVERITAS Cluster Server 3.5 Release Notes

VCS 3.5 Release Notes

This document provides important information regarding VERITAS Cluster Server™

(VCS) version 3.5 for Solaris 2.6 (32-bit) and Solaris 7, 8, and 9 (32-bit and 64-bit). Pleasereview this entire document before installing VCS.

Package Contents

TherearemultipleCDsinthisVERITASproductdistribution.VCSisonVERITASStorageSolutions 3.5Disc 1.

VCS Packages

The following packages for VCS are in thecluster_server/pkgs directory:

xxxxxxxxxxxxx

VRTScscm, VCS Cluster Manager (Java Console)VRTSgab, Group Membership and Atomic BroadcastVRTSllt, Low Latency TransportVRTSperl, Perl for VRTSvcsVRTSvcs, VERITAS Cluster ServerVRTSvcsag, VCS Bundled AgentsVRTSvcsmg, VCS Message CatalogsVRTSvcsmn, VCS Manual Pages

VRTSvcsor, VCS Oracle Enterprise ExtensionVRTSvcsw, Cluster Manager (Web Console)VRTSvlic, VERITAS License UtilitiesVRTSweb, VERITAS Web GUI EngineVRTSvcsdc, VCS Documentation.

VCS Documentation

Documentation for VCS is in thecluster_server/docs directory in PortableDocument Format (PDF):

xxxxxxxx

vcs_adg.pdf,Agent Developer’s Guidevcs_barg.pdf,Bundled Agents Reference Guidevcs_ig.pdf,Installation Guidevcs_ug.pdf,User’s Guide

vcs_appnote_rdc.pdf,Application Note: Replicated Data Cluster for VCSvcs_appnote_e10kdr.pdf,Application Note: Sun Enterprise 10000 DynamicReconﬁguration

vcs_appnote_a3x00.pdf,Application Note: Sun StorEdge 3x00 Disk Arrayvcs_appnote_a5000.pdf,Application Note: Sun StorEdge 5000 Disk Array

Release Notes for VCS are in thecluster_server/release_notes directory:

vcs_notes.pdf,Release Notes in PDF format

VERITAS recommends copying the release notes from the CD to the

/opt/VRTSvcs/docs directory so that they are available on your systemfor reference.

Hard-Copy Documentation Set

Copies of VERITAS software guides are available for purchase through the VERITASDocStore™ athttp://www.veritas.com/docstore.The following guides for VCS 3.5 on Solaris are available:

xxxxx

Installation GuideUser’s Guide

Agent Developer’s GuideBundled Agents Reference GuideRelease Notes

2VERITAS Cluster Server 3.5 Release Notes

VERITAS Documentation Online

Visit the website for VERITAS Cluster Server for UNIX:

http://support.veritas.com/menu_ddProduct_CLUSTERSERVER.htm

to download VERITAS Cluster Server documentation from current and previous releases.

Manual Pages

The manual pages for theVRTSllt,VRTSgab, andVRTSvcs are installed in

/opt/VRTS/man. Set theMANPATH environment variable so theman(1) command canpoint to the VCS manual pages.

For Bourne or Korn shell (sh orksh), type:

#MANPATH=$MANPATH:/opt/VRTS/man#export MANPATH

For C shell (csh ortcsh), type:

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

For more information, refer to theman(1) manual page.

Technical Support

Contacting Technical Support

For assistance with any VERITAS product, contact Technical Support:

U.S. and Canada: call 1-800-342-0652.

Europe, the Middle East, or Asia: visit the Technical Support Web site athttp://support.veritas.com for a list of each country’s contact information.Software updates, TechNotes, product alerts, and hardware compatibility lists are alsoavailable fromhttp://support.veritas.com.

To learn more about VERITAS and its products, visithttp://www.veritas.com.

Using VRTSexplorer

TheVRTSexplorer program can help VERITAS Technical Support engineers diagnosetechnicalproblemsassociatedwithVERITASproducts.Youcaninstallthisprogramfromthe VERITAS CD or download it from the VERITAS FTP site. For more information,consult the README ﬁle in theVRTSexplorer directory on the VERITAS CD.

To install VRTSexplorer from the VERITAS CD1.Log in as root.

2.Place the VERITAS CD into a CD-ROM drive connected to your system and enter:

#mount -o ro /dev/cdrom /mnt

3.Move to the/support directory and install theVRTSspt package:

#cd /mnt/cluster_server/support#pkgadd -d . VRTSspt

The program is installed in the/opt/VRTSspt directory.

4VERITAS Cluster Server 3.5 Release Notes

Technical Support

To download VRTSexplorer from the VERITAS FTP site

1.Use a web browser or theftp program to download theVRTSexplorer program

from the following URL:

ftp://ftp.veritas.com/pub/support/vxexplore.tar.Z

Save the ﬁle to the/opt/VRTSspt directory. Create the directory/opt/VRTSspt ifit does not exist.

2.Log in as root on the affected system, and use the following commands to extract the

contents of the downloaded ﬁle to the directory/opt/VRTSspt:

#cd /opt/VRTSspt

#zcat vxexplore.tar.Z | tar xvf -

wTo run the VRTSexplorer program, enter:

1.Run theVRTSexplorer program from the VRTSexplorer directory by entering the

following command:

#/opt/VRTSspt/VRTSexplorer/VRTSexplorer

VRTSexplorer prompts you for a destination directory for the information that itcollects.

2.Press Return to accept the default directory/tmp, or enter a path name of your own

choice.

VRTSexplorer writes information to a compressed tar ﬁle named

VRTSexplorer_casenumber_hostname.tar.Z in the speciﬁed directory.

3.Use the ﬁle upload facility of your web browser, or theftp program, to transfer the

VRTSexplorer output ﬁle to the VERITAS Technical Support anonymous FTP site:

ftp://ftp.veritas.com/incoming

4.When you call VERITAS Technical Support, provide the name of the ﬁle you

transferred to the FTP site.

Alternatively, if you have already been assigned a call ID number by VERITAS

TechnicalSupport,emailsupport@veritas.comandincludeyourcaseIDnumberin the subject line.

Supported HardwareServersxxxxxxSun workgroup servers: Ultra5S and Ultra10SSun entry-level servers: Enterprise 220R, 250, 420R, and 450; Sun Fire 280R and V880Sunmidrangeservers:SunFire3800,4800,4810,and6800;SunEnterprise3x00,4x00,5x00, and 6500Sun high-end servers: Enterprise 10000; Sun Fire 12K and 15KSun rack-optimized servers: Netra T1 AC200, Netra 20, Netra t 1120 and 1125,Netra t 1400 and t 1405.Fujitsu Siemens Primepower 200, 400, 600, 650, 800, 850, 1000, and 2000For information on additional supported hardware, contact your VERITAS salesrepresentative.NoteVCS cannot access or control data cached by special-purpose hardware, such asPrestoserve NVRAM. If a VCS server fails, data cached in this manner may be lost.Network Interfaces (Controllers)xxxxxxSBus Quad FastEthernet adapter (for private network, SBus architectures)PCI Bus Quad FastEthernet adapter (for private network, PCI Bus architectures)HME built-in or SunSwift (PCI/SBus)Sun Gigabit Ethernet 2.0 adapterSun Gigabit Ethernet 3U CompactPCI adapterSun GigaSwift Ethernet adapterNoteYou must use external disk controllers for shared disk subsystems, and networkindependent hubs for each heartbeat link.Switchesxx6

Brocade SilkWorm 2800 (Firmware versions 3.0, 2.4.1, 2.2.1c)QLogic SANbox2 (Firmware version 1.3.25.0)VERITAS Cluster Server 3.5 Release Notes

Supported Hardware

Disk Subsystems

The following disk subsystems are supported. The list is subject to change as testing ofother systems takes place.

xxxxxxxxxxxxxxxxxx

Baydel O/ESR 2000

Compaq StorageWorks MA8000, EMA12000

CLARiiON Alpine 4400/4500/4700 series, CLARiiON DAER, CLARiiON DGEMC CLARiiON FC4700

EMC Symmetrix 3000, 3830, 5000, 8430, 8530Hitachi Data Systems 5700 (DF 350), 5800Hitachi Data Systems 7700E, 9200, 9910, 9960HP XP256, XP512

IBM ESS 2105-E20, 2105-F20Imperial MG-4000 RM

LSI Logic MetaStor E4400, E4600MTI 3500 (SCSI), MTI ss-1200-SCSISolid Data Systems ULTRA 800U E800UD2STK 9140/9145

Sun StorEdge MultiPackSun StorEdge A1000 and D1000Sun StorEdge A3000

Sun StorEdge A3500 storage subsystem. For information on how to conﬁgure thisStorEdge disk array, see theVCS Application Note for Sun StorEDGE A3500 Disk Array,included with the VCS documentation set.

Sun StorEdge A5000 storage subsystem. For information on how to conﬁgure thisStorEdge disk array, see theVCS Application Note for Sun StorEDGE A5000 Disk Array,included with the VCS documentation set.Sun StorEdge A5100, A5200Sun StorEdge T3 arrayXioTech Magnitude

xxx

For information on additional supported disk subsystems, contact your VERITAS salesrepresentative.

Unsupported Hardware

CLARiiON SCSI disk array SP split-bus conﬁgurations are no longer supported.

Supported Software

Solaris 2.6 (32-bit), and 7, 8, and 9 operating systems (32-bit and 64-bit)For each platform, we recommend applying the latest Solaris operating systempatches available from Sun. See the following site:

http://sunsolve.Sun.COM

xxx

VERITAS Volume Manager™ (VxVM) 3.1.1P2, 3.1.1P3, 3.2, and 3.5VERITAS File System™ (VxFS) 3.3.x, 3.4P2, and 3.5VERITAS Global Cluster Manager 1.2, 3.5

Requirements for the VCS Graphical User Interface

The minimum requirements on Solaris clients are Ultra5 or greater, 128MB RAM, and1280x1024 display resolution. The color depth of the monitor must be at least 8-bit (256colors), though 24-bit is recommended.

The minimum requirements on Windows 2000 clients are Pentium II, 300MHz, 64MBRAM, and 800x600 display resolution. The color depth of the monitor must be at least8-bit (256 colors), and the graphics card must be able to render 2D images.The following supported Internet browsers have been tested:

Internet Explorer 5.0, 5.5, and 6.0Netscape 4.5, 4.6, and 4.7x

Required Patches for Conﬁguration Editor and ClusterManager

Patches from Sun for Java 2 Standard Edition (J2SE) are required to use the automatedofﬂine conﬁguration tool, Conﬁguration Editor; the Java-based graphical user interface,Cluster Manager (Java Console); and the web-based graphical user interface, ClusterManager (Web Console). Apply the patches for J2SE that are required for your Solarisoperating system. Patches are available from Sun at:

http://java.sun.com/j2se/1.3/install-solaris-patches.html

8VERITAS Cluster Server 3.5 Release Notes

Installing or Upgrading to VCS 3.5

RefertotheVERITASClusterServer3.5InstallationGuideforinstructionsonhowtoinstallVCS 3.5 and how to upgrade to VCS 3.5 from earlier versions of VCS. TheVCS 3.5Installation Guide is in the/docs directory ofVERITAS Storage Solutions 3.5Disc 1.

Migrating from FirstWatch or VERITAS-HA to VCS

Migrating from supported versions of FirstWatch or VERITAS-HA requires consultingservices. VERITAS consultants have the tools and documentation to expedite migrationfrom either of these products. Contact your sales representative for more information.

Obtaining License Keys for VCS

VCS is a licensed software product. For information on obtaining licence keys for VCS,refer to theVERITAS Storage Solutions 3.5 Product License and Installation Guide or theVCS 3.5 Installation Guide.

New Features in VCS 3.5

The features described below are introduced in VCS version 3.5.

Web Console Features

myVCS. The myVCS page provides a single view of consolidated information aboutservice groups, resources, systems, and logs. Users deﬁne the contents and format ofmyVCS.

Cluster Query. Cluster Query enables users to run SQL-like queries about states,attribute values, and other details of cluster conﬁguration. Users can cascade theresult of one query into another to get a combined query result.

Enhanced Service Group Operations. Two new operations have been added to theServiceGrouppage.UserswithAdministratorprivilegescannowenableallresourcesusing the Enable Resources link or disable all resources using the Disable Resourceslink. Service Group operations are now organized to display differently, dependingon the privileges assigned to a user. All available operations are visible and enabledfor users logged in as Administrator. Users logged in as Operator see only theoperations they are permitted to access.

Ofﬂine Propagate. A new operation on the Resource page enables users to ofﬂine aresource and all the resources it is dependent on. This operation is available to bothAdministrators and Operators on the Resource page for a parent resource.

Resource Dependency Table. From the Resource Dependency page, users can nowlink to a tabular display of resource dependencies.

Integration with VCS Trafﬁc Director. The VCS Web Console provides preliminaryintegration with the Trafﬁc Director Web Console. If a domain in the Trafﬁc Directorenvironment is conﬁgured as a service group in the VCS conﬁguration, users cannavigatefromtheGroupSummarypageofthisgroupintheVCSWebConsoletothecorresponding conﬁguration page in the Trafﬁc Director Web Console.

Java Console Features

Enhanced Graphs in Service Group View and Resource View.Users can now moveservice groups and resources by dragging them to a new position in the graph. Alllinks are visible and usable, with overlapping links displayed as curves. A new Linkbutton enables users to link nodes by clicking on them in the graph view. ClusterManager saves changes made to the graphs for display the next time a user logs on.Notiﬁer Conﬁguration Wizard. The new Notiﬁer wizard simpliﬁes conﬁguration ofSNMP and SNTP notiﬁcation.

10VERITAS Cluster Server 3.5 Release Notes

New Features in VCS 3.5

LogDesk.UserssetlogmessageﬁltersinanewEditFiltersdialogbox.TheLogDeskshows only the messages indicated by the ﬁlters applied. A new search string ﬁlterenables users to view all logs containing a speciﬁed string.

Cluster Query. Users can run SQL-like queries about the cluster conﬁguration.Cluster Query is accessed from the toolbar of Cluster Explorer.

Theignoreparent Option

Theignoreparent option enables a resource to be taken ofﬂine even if its parent

resourcesintheservicegroupareonline.Atthecommandline,-ignoreparentisanewoption to thehares command. A check box for this feature is available in CommandCenter.

The UnableToRestartHad Event Trigger

The new UnableToRestartHad event trigger is invoked when hashadow is unable torestartHAD.

Change in Behavior: Previously, hashadow logged a message and terminated when itcould not restartHAD. The default behavior of the new trigger is to restartHAD on thesystem where the trigger is invoked. See theVCS3.5 User’s Guide for more information.

FsckOpt Attribute

ChangeinBehavior:TheFsckOptattributeisnowarequiredattributeoftheMountagentandmustbeusedtospecifybehaviorforthefsckcommand.Previously,FsckOptwasanoptional attribute of the Mount Agent. See theVCS3.5 User’s Guide for more information.

Application Agent

Change in Behavior: The Monitor and Clean entry points now check to ensure that

processesspeciﬁedintheMonitorProcesslistarerunningwiththeuserIDspeciﬁedintheUser attribute. See theVCS3.5 User’s Guide for more information.

New Bundled Agents

The following bundled agents were added in the VCS 3.5 Release. For details, refer to theVERITAS Cluster Server Bundled Agents Reference Guide.

IPMultiNICB Agent

MultiNICB AgentVRTSWebApp Agent

New Attributes

Cluster Attributes-PanicOnNoMem

xService Group Attributes-PreonlineTimeout

xSystem Attributes--CPUUsage

CPUUsageMonitoring

xResource Type Attributes-NameRule

Bundled Agents

The following agents are included with VCS. For information on any of the agents listedbelow, refer to theVCS 3.5 Bundled Agents Reference Guide.--------ApplicationDiskReservationFileOnOffIPMultiNICMultiNICANICProcessShare

--------

DiskElifNoneFileOnOnlyIPMultiNICBMultiNICBNotiﬁerMngrProxyVolume

--------

DiskGroupFileNoneIPMountNFSPhantomServiceGroupHBVRTSWebApp

12VERITAS Cluster Server 3.5 Release Notes

Enterprise AgentsEnterprise AgentsEnterprise agents are sold separately. Contact your VERITAS sales representative fordetails about these agents, additional agents under development, and agents available aspart of an Edition or through VERITAS Consulting Services.NoteBefore conﬁguring an enterprise agent with VCS 3.5, verify that you have the latestversion of the agent.Supported Enterprise AgentsVCS enterprise agents listed below are onVERITAS Storage Solutions Disc 3. Refer to this tablefor supported application and operating system versions. VCS agents support a speciﬁedapplication version on Solaris 9 if the application vendor supports that version on Solaris 9.SupportedVCS AgentAgentversionVCS version1.32.03.5OSApplication2.6789iPlanet(Sun ONE)3.5nssAdministration ServerMessaging ServerMessaging MultiplexorDirectory ServerWeb ServerProxy ServerSOCKS Server5.0, 5.1, 5.25.0, 5.1, 5.25.0, 5.14.1, 6.03.63.68.0.x,8i,9iR1,9iR211.x–11.9.212.0,12.5F700, F8003.1, 3.2, 3.4 4.57.1 EE7.1–9.213.5ssssOracleServPointSybaseNetAppNetBackupDB2InformixQuickLog2.0.12.01.3.11.3.11.31.31.31.3ssssssssssssssssssssssssOraclesssssssssssssssssssssssssttsttttServPoint NAS for Oracle1.1, 1.2Sybase Adaptive ServerNetApp File ServersNetBackupDB2 Enterprise EditionInformix Dynamic ServerQuickLogfeatureofVxFSs – supported conﬁguration n – not supported t – not available for testing at time of release13

End of Life Enterprise AgentsEnd of Life VCS Enterprise Agents are listed in the table below.End of LifeVCS AgentAgentversionVCS version1.32.03.5OSApplication2.678ApacheFirewallPCNetlinkSIMSSuiteSpotVFR1.31.31.31.31.31.3ssssssssssssccnnccApache Web ServerCheckPoint VPN-1/Firewall-1PC NetLinkSun Internet Mail ServerNetScape SuiteSpotFile Replicatorn – not supported1.3.x4.11.14.03.53.0.2sssssssssssssnsssss – supported conﬁgurationc – available through consultingCustom AgentsCompiling Custom AgentsCustom agents developed in C++ must be compiled using SUNWspro 5.0 or ForteDeveloper 6 compilers. Note that an agent framework library is available for use withcustom agents compiled with SUNWspro 4.x compilers.The following is the layout oflibvcsagfw.soin/usr/lib:/usr/lib/libvcsagfw.so --> /usr/lib/libvcsagfw.so.2(compatible with SUNWspro5.0 and Forte Developer 6 compilers)/usr/lib/libvcsagfw.so.1(compatible with SUNWspro 4.x)All the agents developed on VCS 1.3 and 2.0 will continue to work since they link withlibvcsagfw.so.1. If SUNWspro 4.x is used to compile a new custom agent,libvcsagfw.so should link tolibvcsagfw.so.1 during link time. After the agent isdeveloped, relinklibvcsagfw.so tolibvcsagfw.so.2.Upgrading Custom AgentsCustom agents developed prior to VCS 1.3 must be upgraded before they can be usedwith VCS 3.5. See theVCS3.5 Agent Developer’s Guide for instructions on how to upgradecustom agents.14

VERITAS Cluster Server 3.5 Release Notes

Software Limitations in VCS 3.5

The following limitations apply to VCS version 3.5.

Cluster Manager (Java Console)

Java Console for VCS 3.5 is Required

Cluster Manager (Java Console) from VCS versions earlier than 2.0 cannot be used tomanage VCS 3.5 clusters. VERITAS recommends always using the latest version of

Cluster Manager. See theVERITAS Cluster Server 3.5 Installation Guide for instructions onupgrading to the VCS 3.5 version of Cluster Manager.

Running Java Console on a Non-Cluster System is Recommended

VERITAS strongly recommends not running Cluster Manager (Java Console) for an

extendedperiodonasysteminthecluster.TheSolarisversionoftheJavaVirtualMachinehas a memory leak that can gradually consume the host system’s swap space. This leakdoes not occur on Windows systems.

Print Option in Java Console Help Requires Conﬁgured Printer

ASolarissystemrunningClusterManager(JavaConsole)musthaveaprinterconﬁgurediftheprintingoptionistobeused.IfaprinterisnotconﬁguredtothesystemonwhichtheJava Console runs, the Java Console may hang when the “Print” button is clicked in theonline JavaHelp. This is a known problem related to components of JavaHelp.

UpgradesfromVCS2.0orBelowUsingtheinstallvcsUtility

When upgrading from versions of VCS before 2.0, you must manually conﬁgure ClusterManager (Web Console), SNMP, and SMTP in themain.cf ﬁle. Refer to theVCS 3.5

InstallationGuideforinformationonconﬁguringtheseintheClusterServiceservicegroup.

System Names in VCS

The name of a system speciﬁed in the VCS conﬁguration ﬁle,main.cf, must not use thefully qualiﬁed form, that is, it must not include periods. The name inmain.cf must beconsistent with the name used in/etc/nodename and/etc/llthosts. If the namelisted in/etc/nodename is fully qualiﬁed, VCS uses only the ﬁrst segment of the name.If you create the ﬁle/etc/VRTSvcs/conf/sysname such that it contains the systemname to be used bymain.cf, VCS uses it to verify the system name.

Undocumented Commands, Command Options, and Libraries

VCS contains undocumented commands and command options intended for VERITASdevelopment use only. Undocumented commands are not supported by VERITAS. Perllibrarieslocatedunder/opt/VRTSvcs/lib/perl5/.VCSagntfwareforVERITASuseonly and are not supported.

EngineLogMessagesReportAllWebConsoleUsersas“root”

With VCS 3.5, the engine log messages for the Web Console do not distinguish amongusers. Messages report all users as “root.”

GCM 1.x Is Not Supported on VCS 3.5

Clusters running VCS 3.5 for Solaris do not support GCM versions 1.1 and 1.2. To useGCMwithVCS3.5,upgradetoGCM3.5.RefertotheVERITASGlobalClusterManager3.5Release Notes for the upgrade procedure. Note that you must uninstall GCM 1.1 or 1.2before you upgrade to VCS 3.5.

Link to VCS Trafﬁc Director from the TDService Group in VCS

Navigation to VCS Trafﬁc Director from the TDService Group Summary page in VCSCluster Manager (Web Console) takes users to the Domain Summary page of the ﬁrstdomain in the domain list.

Theinstallvcs Utility on Solaris 2.6 Requires Solaris Patch

If you are runninginstallvcs on Solaris 2.6 you must have the latest Solaris operatingsystem patch update installed. Obtain it fromhttp://www.sun.com/patches.

Using Agents in NIS

Programs using networked services (for example, NIS, NFS, RPC, or a TCP socket

connectiontoaremotehost)canhangifthehostisdisconnectedfromthenetwork.Ifsuchaprogramisusedasanagententrypoint,anetworkdisconnectcancausetheentrypointto hang and possibly timeout. For example, if the host is conﬁgured to use NIS maps as aclient,basiccommandssuchasps-efcanhangifthereisnetworkdisconnect.VERITASrecommends creating users locally and that /etc/nsswitch.conf reﬂect local users.

16VERITAS Cluster Server 3.5 Release Notes

Software Limitations in VCS 3.5

MultiNicB Agent on Solaris 8 Requires Solaris Patch

If you are running MultiNicB Agent on Solaris 8 you must have Solaris patch update 210/00. Obtain it fromhttp://www.sun.com/patches.

Networking Agents Do Not Support IPv6 Protocol

The VCS 3.5 bundled IP, NIC, IPMultiNICB, and MultiNICB agents do not support theIPv6 enhanced IP protocol made available in Solaris 8.

Volume Agent Clean May Forcibly Stop Volume Resources

When the attribute FaultOnMonitorTimeouts calls the Volume agentclean entry pointafter a monitor timeout, thevxvol -f stop command is also issued. This commandforcibly stops all volumes, even if they are still mounted.

Custom Agents

Releases before VCS 1.1 included the librarieslibvcsprimitives.a and

libvcscommon.a. Agent developers had to link with the agent framework library(libvcsagfw.so orlibvcsagfw.a) andlibvcsprimitives.a. (The library

libvcscommon.awasnotrequired.)Inthecurrentrelease,theonlyVCSlibraryrequiredforcustomagentsistheagentframeworklibrary.TheVRTSvcspackagedoesnotincludelibvcsprimitives.a andlibvcscommon.a. Agent developers using C++ mustchange their makeﬁles to delete any references to these two libraries.

Custom agents must be developed using the SUNWspro 4.0, 4.2, or 5.0 C++ compilers.You must specify the-compat ﬂag when compiling and linking with the 5.0 compiler.Other C++ compilers are not supported.

NFS Locking

NFS lock failover is not yet supported.

EMC Does Not Support GAB Disk Objects

EMC disk arrays do not support the creation of GAB disk objects, and therefore do notsupport the creation of disk heartbeat regions or service group heartbeat regions.

Group Dependency Limitations

Online Local Firm Dependency Violation

Iftheparentgroupandthechildgroupareonlineonnode1,andifthechildgroupfaults,VCS begins to take the parent group ofﬂine. However, this occurs at the same time thechildgroupisfailingovertonode2.Iftheparentgroupfailstogocompletelyofﬂineandthe child group goes online on node 2, thus resulting in a dependency violation.Online Remote Firm Dependency Violation

Iftheparentgroupisonlineonnode1andthechildgroupisonlineonnode2andfaults,thechildgroupselectsnode1asitsfailovertarget,buttheparentgroupfailstogoofﬂineon node 1, thus resulting in a dependency violation.No Failover for Some Instances of Parent Group

Inservicegroupsinwhichthegroupdependencyisconﬁguredasparallelparent/failoverchild, online global, remote soft or ﬁrm, the parent group may not online on all nodesafter a child group faults.

18VERITAS Cluster Server 3.5 Release Notes

Known Issues in VCS 3.5

The following issues have been reported for VCS version 3.5.

Cluster Manager or myVCS May Generate Null Pointer Error

YoucannotlogintotheWebConsoleorconﬁguremyVCSifCmdServerisnotrunningonthesystemsinthecluster.Themessage“Error500-NullPointerException”appearsinthebrowser.

Workaround: Verify that the CmdServer process is running on the cluster systems usingtheps -ef | grep CmdServer command. If CmdServer is not running, start it bytyping/opt/VRTSvcs/bin/CmdServer at the command line. Once CmdServer isrunning, you can log in to Cluster Manager or conﬁgure myVCS.

CurrentLimit is Not Updated Correctly for Persistent Resource

CurrentLimit, the system attribute that describes the current limit of load a system canhandle, does not decrement correctly when a group containing a persistent resource goesfromafaultedstatetoanonlinestate.ThisissueislimitedtoconﬁgurationsusingServiceGroup Workload Management.

MultiNICB Agent Generates Error Message if UseMpathd = 1

When the value of the UseMpathd attribute of MultiNICB is set to 1, you may receive anerror message resembling the following:

Lock file /var/VRTSvcs//lock/MultiNICB/NoMpathd indicates that

another resource of this type has incompatible UseMpathd attribute.The agent will not function properly.

Thisknownproblemdoesnotaffectthebasicfunctioningoftheagent,butthemessageislogged during every monitor cycle.

Workaround: Manually create a/var/VRTSvcs/lock/MultiNICB/NoMpathd ﬁle onthe system. If the MultiNICB agent is restarted, you must manually create this ﬁle again.

Erroneous Message in Engine Log File

When VCS tries to mount avxfs ﬁle system for the ﬁrst time, you may receive amisleading message resembling the following:

/dev/vx/dsk/sharedg/vol03 is not a vxfs file system

Before VCS can mount avxfs ﬁle system for the ﬁrst time, thefsck utility needs to run.The message shown above is displayed,fsck is run, and the ﬁle system is mounted.

License Key May Fail in Upgrade to Foundations or EditionsLicense keys for Foundation Suite or Edition products that include VCS 3.5 as acomponent may not generate a valid VCS 3.5 key. This issue has been observed duringupgrades from VCS 2.0 using some Foundation Suite or Edition 3.5 license keys.Workaround: Locate the directory/var/adm/VRTSshrd. If the directory exists, do thefollowing:1.Rename the directory to/var/adm/VRTSshrd.old.2.Install the Foundation Suite or Edition 3.5 license key again.3.Install VCS 3.5.Engine May Hang in Leaving StateWhen the commandhares-online is issued for a parent resource when a childresourcefaults,andthehares-onlinecommandisfollowedbythecommandhastop-local on the same node, then the engine transitions to theLEAVINGstate and hangs.Workaround: Issue the command hastop-local-force.Volume Agent May HangUnderextremeconditions,thevolumeagentmayhang.Thisbehaviorhasbeenobservedunder the following circumstances:xFailover was set to 0 for the JNI Fibre Channel driver (JNIfcaPCI). Note this isnotfailoverforVCS.ThereisavariablefortheJNIdrivercalled“failover,”whichdeﬁnesthe number of seconds after the target is declared ofﬂine, and before it is declaredfailedandallpendingcommandsareﬂushedbacktotheapplication.Thisvalueissetin the ﬁle/kernel/drv/fca-pci.conf. Setting failover to 0 means that the targetis never declared failed.Fibre cable was disconnected from the switch (to simulate failure of the Fibre drives).xNoteWhenfailoverforJNIdriverwassetto30seconds,VCSagentbehaviorwasnormal.Ingeneral,anagentcanhangwhenitattemptstocancelaservicethreadexecutingaC++entry point that has timed out if that entry point has issued a blocking call that is not avalid cancellation point.Size of Cluster Manager Text May Vary in Netscape BrowserThe Netscape browser on Solaris may unexpectedly change the display size of the text inClusterManagerpages.ThisknownbehavioroftheNetscapebrowseronSolarissystemsmay occur upon refresh of a page or during navigation between pages.20

VERITAS Cluster Server 3.5 Release Notes

Features Introduced in Previous Releases

Introduced in VCS 2.0

The features described below were introduced with VCS version 2.0. They are providedhere for users who are upgrading to VCS 3.5 from versions earlier than VCS 2.0.

Web-Based Graphical User Interface

Web Console

VCS 2.0 introduced a Web-based graphical user interface, VCS Cluster Manager (WebConsole). Using the Web Console, you can remotely monitor a cluster and perform basicoperations on its components, including service groups, systems, resources, and resourcetypes. The Web Console provides context sensitive help. TheVERITAS Cluster Server 3.5User’s Guide describes how to use the Web Console.Apache Software Copyright Notice

This product includes software developed by the Apache Software Foundation(http://www.apache.org/).

The Apache Software License, Version 1.1

Copyright (c) 1999 The Apache Software Foundation. All rights reserved.Redistribution and use in source and binary forms, with or without modiﬁcation,are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice,this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyrightnotice, this list of conditions and the following disclaimer in the

documentation and/or other materials provided with the distribution.3. The end-user documentation included with the redistribution, if any,must include the following acknowledgement:

\"This product includes software developed by the ApacheSoftware Foundation (http://www.apache.org/).\"

Alternately, this acknowledgement may appear in the software itself, if andwherever such third-party acknowledgements normally appear.

4. The names \"The Jakarta Project\not be used to endorse or promote products derived from this software without

prior written permission. For written permission, please contact apache@apache.org.

5. Products derived from this software may not be called \"Apache\" normay \"Apache\" appear in their names without prior written permissionof the Apache Group.

THIS SOFTWARE IS PROVIDED ‘‘AS IS’’ AND ANY EXPRESSED OR IMPLIED

WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIESOF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATIONOR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTLIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF

USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED ANDON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAYOUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITYOF SUCH DAMAGE.

=================================================================This software consists of voluntary contributions made by many individualson behalf of the Apache Software Foundation. For more information on theApache Software Foundation, please see.

User Privileges

VCS supports assigning user privileges for making changes to cluster and group

conﬁgurations. Users designated as Cluster Administrators and Group Administratorsare allowed to make all necessary changes from the command line interface or the VCSCluster Manager graphical user interface. Users designated as Cluster Operators andGroup Operators are allowed to operate clusters and groups without making changes tothe conﬁguration. For details about the VCS privilege feature, see theVERITAS ClusterServer 3.5 User’s Guide.

Event Notiﬁcation

SNMP and SMTP Messages

VCS contains support for notiﬁcation of signiﬁcant predeﬁned events. A notiﬁer daemontransmits messages about these events from VCS to SNMP consoles or to SMTP servers.Administratorscanconﬁgurethedestinationandlevelofseverityofthemessages.SeetheVERITAS Cluster Server 3.5 User’s Guide.

Thehanotify command is used to specify user-deﬁned events, which VCS forwardsusing the notiﬁer daemon. This command enables developers of custom agents tocustomize event notiﬁcation. A VCS bundled agent, NotiﬁerMngr, can provide highavailability for the notiﬁer daemon. See theVCS3.5 Bundled Agents Guide.

VERITAS Cluster Server 3.5 Release Notes

Features Introduced in Previous ReleasesSNMP Copyright NoticeSNMP support in VCS is based on CMU SNMP v2 under the following copyright:Copyright 1989, 1991, 1992 by Carnegie Mellon UniversityAll Rights ReservedPermission to use, copy, modify, and distribute this software and its documentation forany purpose and without fee is hereby granted, provided that the above copyright noticeappear in all copies and that both that copyright notice and this permission notice appearin supporting documentation, and that the name of CMU not be used in advertising orpublicity pertaining to distribution of the software without speciﬁc, written priorpermission.CMU DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE,INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS,IN NO EVENT SHALL CMU BE LIABLE FOR ANY SPECIAL, INDIRECT ORCONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTINGFROMLOSSOFUSE,DATAORPROFITS,WHETHERINANACTIONOFCONTRACT,NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR INCONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.Workload BalancingYou can conﬁgure dynamic workload balancing at the system level. At the group level,youcanstaticallyconﬁguregrouploadwithsystemcapacityintheVCSconﬁgurationﬁle,main.cf. See theVERITAS Cluster Server 3.5 User’s Guide for more information onworkload balancing.VCS Java Console Features Added in VCS 2.0The Java Console introduced several new features in VCS 2.0. Cluster Monitor providesclear tree views of resource groups, systems, and resource types, detailed properties andstatus views of cluster objects, and an enhanced view of VCS logs. The Java Consoleprovides for management of user privileges. Also included are enhanced online help,internationalization support, improved keyboard navigation, and selectable fonts andicons to improve accessibilityNoteThe Java Console requires a Colors setting of 256 colors or greater; it does not runwith a Colors setting of 16.VCSConﬁgurationEditor,whichisinstalledalongwiththeJavaConsole,enablesuserstocreate or modify the VCS conﬁguration ﬁlemain.cf ofﬂine on the local system.23

ClusterService Service Group

VCS creates a ClusterService service group to ensure that cluster functions remain highlyavailable.ThisservicegroupincludestheVCSWebConsole,thevirtualIPaddressthatisconﬁgured for the Web Console on all systems in the cluster, and the VCS Notiﬁer

component,whichincludesresourcesforSNMPandSMTPnotiﬁcation.SeetheVERITASClusterServer3.5InstallationGuideforinformationoncreationoftheClusterServicegroup.

Single-Node Support

AsinglesystemrunningVCSissupported.SeetheVERITASClusterServer3.5InstallationGuideforinformationonhowtoinstallandconﬁgureasingle-nodecluster.AsinglenodewithVCScanmonitorandrestartcomplexapplications.Inaddition,asingle-nodeclustercan be conﬁgured with VERITAS Global Cluster Manager.

Licensing

VCSrequiresalicensetouse.CustomerscanobtainlicensekeysfromVERITASCustomerSupport. Permanent license keys are required to run purchased products. Demo licensesare also issued for product evaluation purposes.

Typically,usersmustprovidelicensekeyswheninstallingVCS,whetherduringaninitialinstallation or during an upgrade.

Preonline IP Check

You can enable a preonline check of a failover IP address by setting the service groupattributePreOnlineto1.Whenenabled,thecheckprovidesprotectionagainstasplit-braincondition.RefertotheVERITASClusterServerUser’sGuideformoreinformationonusingthe preonline IP check.

Command for Displaying Log Data Files

Thehamsg(1M) command enables the display of messages contained in log data ﬁles(LDFs) in supported languages. Log data ﬁles enable language-independent logging forthe VCS logging system. By using the query options ofhamsg, you can customize thedisplay of messages by message Tag, VCS component, message ID, and more. See theVERITAS Cluster Server User’s Guide,and thehamsg(1M) manual page.

24VERITAS Cluster Server 3.5 Release Notes

Features Introduced in Previous Releases

Heartbeat Status Attributes

The status of the link heartbeat and the status of the disk heartbeat are now alwaysmonitored by the VCS engine. The status is reﬂected in the two new attributes,LinkHbStatus and DiskHbStatus. The commandshaclus -enable|-disableLinkMonitoring are discontinued.

Password Encryption

Password encryption changed in VCS 2.0 to provide greater security. On all UNIX

platforms, passwords are encrypted using a random salt and are not visible in the outputof the commands: haclus-display,hauser-display, andhaclus-valueUserNames, andhareg-clus. Only the root user can access ﬁles containing the

encrypted form of a password. On Solaris, VCS considers and veriﬁes only the ﬁrst eightcharacters of passwords.

IfyouupgradefromaversionofVCSbefore2.0,werecommendthatyouchangetheuserpasswords for greater security, even though the new encryption scheme is backwardcompatible.

Service Group with Disabled Resources

VCS can bring online a service group containing disabled resources provided all theenabled resources have been probed. In versions before VCS 2.0, all of a service group’sresources would have to be probed before it could come online; a disabled resource,which could not be probed, prevented a service group from coming online even when itcontained enabled resources.

Scheduling Class and Priority Conﬁguration

VCS 2.0 added the ability to specify SRM as a scheduling class (on the Solaris platformonly) for VCS Processes. See the VERITAS Cluster Server Agent Developer’s Guide.

The ResStateChange Event Trigger

VCS 2.0 introduced the ResStateChange event trigger. This trigger is invoked whenspeciﬁc state changes occur.See VERITAS Cluster Server 3.5 User’s Guide for moreinformation.

Sun eri Device Driver Supported

Support for theSUNW eri network interface device and Suneri FastEthernet devicedriver was added in VCS 2.0.

Multiple Sybase Resources Per Group

The VCS enterprise agent for Sybase places no restriction on the number of Sybasedatabase server resources that can be deﬁned within a given service group.

Compatibility of VCS 1.3.0 Enterprise Agents with VCS 2.0

Existing enterprise agents running on VCS version 1.3.0 run on VCS version 2.0.

Bundled Agent Introduced in VCS 2.0

NotiﬁerMngr agent was introduced with VCS 2.0. It provides high availability for thenotiﬁer daemon. For details, refer to theVCS3.5 Bundled Agents Reference Guide.

Attributes Introduced in VCS 2.0

The following attributes were added for the 2.0 release of VCS. For details on currentattributes, refer to theVERITAS Cluster Server 3.5 User’s Guide.

Cluster Attributes---------------AdministratorsOperators

AllowNativeCliUsersClusterLocationClusterOwnerClusterTypeHacliUserLevelNotifierVCSModeEvacuateHacliUserLevelLocationLockMemoryQueueSeverity

26VERITAS Cluster Server 3.5 Release Notes

Features Introduced in Previous Releases

Service Group Attributes----------AdministratorsOperators

AutoStartIfPartialAutoStartPolicyEvacuatingGroupOwnerLoadLocationPrerequisites

TriggerResStateChange

xSystem Attributes----------CapacityLinkHbStatusDiskHbStatusLimitsLocation

LoadTimeCounterLoadTimeThresholdLoadWarningLevelRemaining CapacitySystemOwner

xResource Type Attributes--LogFileSizeLogTags

Introduced in VCS 1.3.0

ThefeaturesdescribedbelowwereintroducedwiththeearlierVCSversion1.3.0.Theyareprovided here for users who are upgrading to VCS 3.5 from versions earlier than VCS1.3.0.

Scheduling Class and Conﬁguration Support

You can conﬁgure the scheduling class and priority of the VCS engine, the processes

createdbytheengine,VCSagents,andthescriptprocessescreatedbytheagent.FormoreinformationseethechapteronadvancedtopicsVERITASClusterServer3.5User’sGuideorthe chapter on setting parameters in theVERITAS Cluster Server Agent Developer’s Guide.

Revised Naming Convention for Log Files

The naming convention for engine log ﬁles and agent log ﬁles changed in VCS 1.3.0 toengine_A.log; for agent log ﬁles,agent_A.log.

Event Notiﬁcation Triggers

VCS provides a method for notifying the administrator of important events such as aresourceorsystemfault.Thismethodisknownaseventnotiﬁcation,oreventtriggers.Thisfeature also enables the administrator to take speciﬁc actions in response to particularevents. For more information, see the chapter on advanced topics in theVERITAS ClusterServer 3.5 User’s Guide.

Change in Behavior: The location of the PreOnline trigger changed in VCS 1.3.0. See thechapter on event triggers in theVERITAS Cluster Server 3.5 User’s Guide for details.

Actions on Concurrency Violations

Whenaconcurrencyviolationoccurs,theViolationeventtriggertakesthefailoverservicegroupofﬂineonthesystemthatcausedtheviolation.Fordetails,seethechapteroneventtriggers in theVERITAS Cluster Server 3.5 User’s Guide.

AutoRestart Attribute

Setting the AutoRestart attribute enables a service group to be brought back onlinewithout manual intervention when a persistent resource goes online after fault and

servicegroupisnolongerfaulted.FormoreinformationontheAutoRestartattribute,seethe chapter on VCS attributes in theVERITAS Cluster Server 3.5 User’s Guide.

28VERITAS Cluster Server 3.5 Release Notes

Features Introduced in Previous Releases

AutoStartList

Change in Behavior: Beginning with 1.3.0, you must deﬁne the service group attributeSystemList before setting the attribute AutoStartList. For more information, see thechapter on VCS attributes in theVERITAS Cluster Server 3.5 User’s Guide.

Type Dependencies

VCSprovidesamethodforestablishingdependenciesbetweenresourcesaccordingtotheresource type. Resource-type dependencies are speciﬁed by the user on a per-group basisin themain.cf ﬁle. Rather than specifying the resource dependencies one by one, youcan specify that all resources of a particular type depend on all resources of another typewithin the service group. For more information, see theVERITAS Cluster Server 3.5 User’sGuide.

Service Group Dependencies

You may specify “soft” or “ﬁrm” group dependencies regardless of local, global, orremote restrictions.For details, see the chapter on service group dependencies in theVERITAS Cluster Server 3.5 User’s Guide.

Change in Behavior: Before VCS version 1.3.0, local dependencies were ﬁrm, global andremote were soft. By default, all are dependencies are now ﬁrm. For instructions onconﬁguring soft dependencies, see the chapter on service group dependencies in theVERITAS Cluster Server 3.5 User’s Guide.

AutoDisabling

Change in Behavior: When VCS does not know the status of a service group on a

particular system, it autodisables the service group on that system. Autodisabling occursunder the following conditions:

xxxx

When GAB is running on the system but the VCS engine is not.

When all resources within the service group are not probed on the system.When a particular system is visible through disk heartbeat only.

When a system is running with only one network heartbeat active (in jeopardy).

For more information, see the chapter on troubleshooting in theVERITAS Cluster Server3.5 User’s Guide and the manual page forgabconfig.

Additional Considerations for Stopping VCS

When VCS is stopped by options other than-force on a system with online service

groups,thegroupsrunningonthesystemaretakenofﬂineandremainofﬂine.Fordetails,see the chapter on administering VCS from the command line in theVERITAS ClusterServer 3.5 User’s Guide.

Bundled Agents Introduced with VCS 1.3.0

ThefollowingagentswereincludedwiththeVCS1.3.0releaseofVCS.Fordetails,refertotheVCS 3.5 Bundled Agents Reference Guide.

ApplicationDiskReservation

Attributes Introduced with VCS 1.3.0

The following attributes were added for the 1.3.0 release of VCS. For details, see thechapter on attributes in theVERITAS Cluster Server 3.5 User’s Guide.

xxxx

OfﬂineMonitorIntervalGUIIPAddrResourceOwnerSysInfo

Script for Updating Custom Agents

You may update custom agents that have been created before VCS 1.3.0 using a scriptprovidedin$VCS_HOME/bin/vcs_upg.pl.Fordetails,seetheaccompanyingReadMeﬁle$VCS_HOME/vcs_upg.readme.

Revised Clean Entry Point for Custom Agents

WithVCS1.3.0,thecleanentrypoint,whenimplemented,iscalledautomaticallywhenaresourcefaults.Theofflineentrypointisnolongerusedforfaultcleanup.Ifaresourcefaults unexpectedly andclean is not implemented, the fault may not be cleaned up

properly.Thisinformationappliesonlytocustomagents.Fordetails,seetheAppendixintheVERITAS Cluster Server Agent Developer’s Guide.

30VERITAS Cluster Server 3.5 Release Notes

Software Fixes and EnhancementsSoftware Fixes and EnhancementsVCS 3.5Incident Number724267558977639DescriptionMessages produced by hastatus are not clear to user.Solaris DiskGroup agent should detect state of vxconﬁgd.Ifnoderunningnotiﬁerispoweredoff,thennotiﬁerexitswithDISCONNECTmessage on node to which it is failed over.Ofﬂine local dependency does not online child after hastop -local -evacuate.The GAB broadcast message may hang. Mount Agent Online should not run FSCK with the \"-y\" option by default.The GAB command shows error message in Japanese environment.If hacli command cannot be run, it should exit with non zero value.NFS agent monitor procedure times out with CVM setup.Problemwithgabdiskiftwodiskregionsareconﬁguredonthesamepartition.Violation trigger script man leave service group PARTIAL, not OFFLINE.Add new’hagrp -ofﬂine’ option to return error unless all resources are probedCommands may hang if cluster is not seeded.Problem with logging EAGAIN of ioctl( ) in Application Agent.IfAllowNativCliUsersissetto1,thewebguipermitsloginwithassignedVCSprivileges, ignoring the password.When LANG variable is set to null, ha commands do not execute.Notiﬁer should handle ’command not implemented’ response from SMTPserver when performing VRFY.Switch partial group as partial if PreOnline is disabled, and as full online ifPreOnline is enabled.Processagentdoesn’tofﬂinetheresourceifthearglistcontainsthepathname.31

78228, 58902782507863579096797178005280317811928119982908, 2479683145, 774958359383988, 7662584605, 830988488185278VCS 3.5Incident Number853818580385966, 8502587753, 81091881448835788881906239079692150DescriptionNIC Agent faults when netstat -in returns very large number.HAD crashes while changing scope of Enabled attribute for a resource to local.The command hastop -local -evacuate may not fail over all groups.GAB panic when IOs hanging in the sd layer.Change to GAB 15 second timeout value.HAD crashes when halog -add is issued with very large ’parameter’.Web GUI unable to connect toHADif hostname is changed.Service group cannot failover with PreOnline enabled.The hastop -local called by init 6 hangs when an agent process is terminated.Rare case whereHAD on one node is IOfenced durning a node fault with SunFire 6800s and EMC storageThe preonline_ipc script does not correctly determine broadcast address.Service group cannot fail over with PreOnline enabled if it has online remoteﬁrm dependency.Agents using framework compiled with new compiler may core dump.Failing ifconﬁg operations due to concurrency issues of ifconﬁg in Solaris 6, 7.Group cannot failover with RestartLimit under some conditionPossible memory leak in had when disk heartbeat conﬁgured.92236929679300993356944819460695109, 85615, 85567Address areas in code that may drop ActiveCount below 0.9605396155, 95008MultiNICA with PingOptimize set to 0 left sytem in an unusable state.Group prerequisites should not prevent re-onlining a faulted non-criticalresource that belongs to the same service group.ProbesPending is set incorrectly when user speciﬁes Enabled attribute withlocal scope. Command is rejected but resource is counted in ProbesPending.9747832VERITAS Cluster Server 3.5 Release Notes

Software Fixes and EnhancementsVCS 3.5Incident Number98283, 95313DescriptionWhennodenameinterfaceisbroughtdown,notiﬁercannotdeliverSNMPandSMTP messages via another interface.With SMTP server down time, SNMP messages are delivered every 4 minutes.When lowest node with one link remaining is halted, failover occurs.With VCS2.0P2, online remote parent group cannot go online after reboot.Add ability to ofﬂine a resource without ofﬂining dependent resources.Node joining cluster does not get severity conﬁgured for notiﬁer if notiﬁer isalready running on another node in the cluster.986469865798868, 95983100070, 89989101451VCS 2.0Incident Number44343DescriptionProvide an option to “hastop-local -evacuate” so that group won’t failover; add an Evacuate group level attribute.Enhancements to VCS agent logging requested by customer.VCS Conﬁguration Editor should be usable ofﬂine (on standaloneworkstation).Link monitoring should be enabled by default.“Others” category could be removed in Logs screen in GUI.System panics when modunloading GAB.Servicegroupscanbeofﬂinedonfrozensystem.Manpageforhasyscorrected.When using Application agent, MonitorProgram can be created on local disk.Documentation corrected.Absolute path fortypes.cf ﬁle not considered during dump.Incorrectly setting the ‘set-node number’ in thellttab ﬁle can cause splitbrain on forced failovers.MultiNICA can returnONLINE incorrectly.5097552233528455555858377603066078963198674976887233

VCS 2.0Incident Number7105372462DescriptionSystem panics in llt_timer_handler().DiskGroup clean script takes no action and returns success if monitor timesout.VCS1.3.0P3Incident NumberDescription50678Entrypoints now receive dependent attributes properly. Snapshots fordependent types are now performed synchronously after the snapshot of thedependent resource.The commandhagrp -link no longer core dumps when issued withoutarguments.The commandhagrp -link now returns a message when trying to link agroup to itself.Thehagetcf utility now gathers all log ﬁles.Thegabdiskutilitynolongerpanicsduetobadalignmenton64-bitsystems.Macro adjusted to correct alignment error.The commandhastop -local no longer gives core dump whenLinkMonitoring is enabled.Framework now monitors ﬂushed resources according to the intervaldesignated in the MonitorInterval attribute.NumRetries attribute is now local.Engine no longer hangs when GAB returns an error. Speciﬁcally, GAB nowstopsitselfuponreceiptofasend/receiveerror.Additionaldebuginformationfor errors is also included.The ServiceGroupHB agent now uses fullpath when referring togabconfigin its ofﬂine script.Entry points adjusted to prevent overﬂow of ﬁle offset on GAB device.The commandhacli no longer hangs in a single server mode.511265112951713518815196952176525475288152920534825409934VERITAS Cluster Server 3.5 Release Notes

Software Fixes and EnhancementsVCS1.3.0P3Incident NumberDescription5541956188568975721457398574575788058061Scheduling class support modiﬁed to allow support of SHR class.(cfs) GAB module no longer panics while unloading.“GAB unavailable” message no longer displays on boot.The commandlltstat -L no longer causes panic.Thenfs_trigger now has correct path name.Invocation ofhalog now has correct path name.Application agent no longer experiences memory leak.GroupinPARTIALstatenolongergoesONLINEwhennon-AutoStartsystemis restarted.Agent framework now sets FD_CLOEXEC ﬂag for open fds instead of closingthem.All documentation sources are now explaining resstatechange trigger use inthe same way.OfﬂineMonitorInterval is no longer getting reset to the defaultha hacf.GAB work threads are now started at conﬁguration time to avoid possiblepanic ingabconfig.An initial white space in/etc/llthosts is properly ignored.Thenfs-restart no longer continuously invokesmountd andnfsd.Console messages now appear with link tags.Thelltconfig command no longer accepts start/stop options.AutoStart group attribute is now saved tomain.cf in a dump.GAB no longer panics due to incorrect locking order.Problem of node ownership resolved for ServiceGroupHB:gabdiskx.Thegabdisk now retries for EBUSY.35

5948260593611256351263568642176448665119, 5721965205 66152, 658446660867342VCS 1.3.0Incident Number30153DescriptionExecutingthecommandhaconf-dumponasystemwhose/tmpdirectoryisfull caused the engine process to crash on that system.Quick unregister and re-register of GAB no longer causes system halt.Mount agent clean script now deﬁnes$df.Persistent non-critical resources are treated like other non-critical resources(for example, they do not necessarily fault the service group at resource fault).VCS Sybase agent started the database but did not report it as online if a verylong path is used.Clean script for the VCS enterprise agent for Oracle now functions properly.Previously,the“if”blockforstringcomparisonuseda“!=”insteadof“ne”.Asa result, theif block was not executed in any condition. Now if the result oftheif block execution is false, the oracle instance is shutdown.VCS now sends an SNMP trap when a heartbeat is disconnected.The command to take a child group ofﬂine was not rejected if parent groupwas online.Deleting aType attribute caused the corresponding agent to hang.Agents no longer create and remove a temp ﬁle for each script execution.Agents monitor ofﬂine resources less frequently.Stale data in lock ﬁle no longer prevents VCS from terminating a hung agent.Addedlogictohandletheintervalduringwhichagroupistakenofﬂineatthesametimearesourcethatwasnotwaitingtogoonlinetimesout(forexample,after faulting and restarting).User could not modify anyAssoc type attribute from Attribute View panel. Occasionally, the commandhalog -a caused halog to core dump.The event trigger ResNotOff was ﬁred inconsistently.Agent scripts no longer get SIGPIPE when writing tostdout orstderr.3191732238336353755737734386934310545301453104532145548460714617746492465444766336VERITAS Cluster Server 3.5 Release Notes

因篇幅问题不能全部显示，请点此查看更多更全内容

查看全文