veritasstoragefoundation manager release notes release notes ......

Veritas Storage Foundation™Manager Release Notes

for Storage Foundation—AIX, HP-UX,Linux, Solaris, Windows

2.0

Storage Foundation Manager 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: 2.0

Documentation version: 2.0.3

Legal NoticeCopyright © 2009 Symantec Corporation. All rights reserved.

Symantec, the Symantec logo, Veritas, CommandCentral, NetBackup, SANPoint, SANPointControl, and Veritas Storage Foundation 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.

This Symantec product may contain third party software for which Symantec is requiredto provide attribution to the third party (“Third Party Programs”). Some of the Third PartyPrograms are available under open source or free software licenses. The LicenseAgreementaccompanying the Software does not alter any rights or obligations you may have underthose open source or free software licenses. Please see the Third Party Legal Noticedocumentation accompanying this Symantec product for more information on the ThirdParty Programs.

■ AIX is a registered trademark of IBM Corporation.

■ HP-UX is a registered trademark of Hewlett-Packard Development Company, L.P.

■ Linux is a registered trademark of Linus Torvalds.

■ Solaris is a trademark of Sun Microsystems, Inc.

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 in

Commercial Computer Software or Commercial Computer Software Documentation", asapplicable, and any successor regulations.

Symantec Corporation350 Ellis StreetMountain View, CA 94043

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 maintenance 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 Web-based support that provides rapid response andup-to-the-minute information

■ Upgrade assurance that delivers automatic software upgrade protection

■ Global support that is available 24 hours a day, 7 days a week

■ Advanced features, including Account Management Services

For information about Symantec’sMaintenance Programs, you can visit ourWebsite at the following URL:

www.symantec.com/techsupp/

Contacting Technical SupportCustomerswith a currentmaintenance agreementmay access Technical Supportinformation at the following URL:


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

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


Customer serviceCustomer service information is available at the following URL:


Customer Service is available to assist with the following types of issues:

■ Questions regarding product licensing or serialization

■ Product registration updates, such as address or name changes

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

■ Latest information about product updates and upgrades

■ Information about upgrade assurance and maintenance 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



Maintenance agreement resourcesIf you want to contact Symantec regarding an existing maintenance agreement,please contact the maintenance agreement administration team for your regionas follows:

[email protected] and Japan

[email protected], Middle-East, and Africa

[email protected] America and Latin America

Additional enterprise servicesSymantec offers a comprehensive set of services that allow you tomaximize yourinvestment in Symantec products and to develop your knowledge, expertise, andglobal insight, which enable you to manage your business risks proactively.

Enterprise services that are available include the following:

These solutions provide early warning of cyber attacks, comprehensive threatanalysis, and countermeasures to prevent attacks before they occur.

SymantecEarlyWarningSolutions

These services remove the burdenofmanaging andmonitoring security devicesand events, ensuring rapid response to real threats.

Managed Security Services

Symantec Consulting Services provide on-site technical expertise fromSymantec and its trustedpartners. SymantecConsultingServices offer a varietyof prepackaged and customizable options that include assessment, design,implementation,monitoring, andmanagement capabilities. Each is focused onestablishing andmaintaining the integrity and availability of your IT resources.

Consulting Services

Educational Services provide a full array of technical training, securityeducation, security certification, and awareness communication programs.

Educational Services

To access more information about Enterprise services, please visit our Web siteat the following URL:

www.symantec.com

Select your country or language from the site index.

[email protected]

[email protected]

[email protected]

www.symantec.com

Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 1 Overview of this release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Introduction to Storage Foundation Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13SF Manager installation options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Chapter 2 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Operating system requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Operating system updates required .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Third-party required libraries ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1732-bit SNIA Common HBA API on Windows hosts ... . . . . . . . . . . . . . . . . . . . . . 18

System resource requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Supported hardware .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Web browser requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Network and firewall requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Chapter 3 Software limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Installation and configuration limitations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23SF Manager does not discover HDS RAID600 enclosure ... . . . . . . . . . . . . . . 23SF Manager does not discover EMC DMX-3 enclosure ... . . . . . . . . . . . . . . . . 23Incremental backup and restore procedures are not

supported .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24SF Manager does not discover a X64 Sun SE3510 array

(1033610) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24SFManager database location cannot be specified as a directory

name that contains Japanese characters (1532409) ... . . . . . . . . . . . . . . 24High availability configuration limitations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

SF Manager operations hang during failover ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Dynamic Multipathing Add-on limitations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Unsupported managed hosts versions (1034396) ... . . . . . . . . . . . . . . . . . . . . . . . 25Volume Migration Add-on limitations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Volume migration not supported for volumes under CVM diskgroups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Contents

Storage Foundation Administration for Windows Add-onlimitations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Storage Foundation for Windows features that are not

supported .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Veritas Volume Replicator features that are not supported .... . . . . . . . . 26Storage Foundation forWindows versions supported by Storage

Foundation Administration for Windows Add-on .... . . . . . . . . . . . . . . . 26Considerations for Storage Foundation 4.x Windows managed

hosts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Graphical user interface issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Storage usage displays as zero for non-Veritas file types ... . . . . . . . . . . . . 27SENA arrays not displayed .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Unable to report LUN size correctly on AMS500 enclosure

(1027514) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Chapter 4 Known issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Managed host issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Add host operation may fail on a Storage Foundation 5.0 host

that has been upgraded to Storage Foundation 5.0MP3 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

HP-UX 11.11 hosts cannot be added to the Management Serverdomain .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Console display issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31WebGUI monitoring shows status as RUNNING and does not

change to FINISHED (1061587) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Collapse of tree control in theDMPorVolumeMigration add-ons

may trigger "Unresponsive Script" dialog (1057360) ... . . . . . . . . . . . . 31HBA information not displayed in the SF Manager Web Console

for Solaris 9 managed hosts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31SF Manager Web Console displays incorrect count of managed

hosts in the Management Server domain .... . . . . . . . . . . . . . . . . . . . . . . . . . . 32All Scheduled Tasks link appears erroneously in Summary view

for Storage Foundation 4.x for Windows hosts(1525967) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

SEGATE Fiber channel JBOD discovery not supported in SFManager 2.0 (1472420) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Action link does not work in Health Check reports spanningmultiple pages (1542015) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Tabular data spanning multiple pages cannot be viewed beyondpage 10 (1537636) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Error message displayed when the connection to SF Manager istimed out (1507878) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Contents8

Administer link is erroneously displayed for UDF file systems(1586223) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Links to annotations-related tasks erroneously displayed in theSearch view (1593642) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Resource Mapping report does not display external diskconnected to an array on a Windows managed host(1636114) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Veritas Cluster Server information not displayed for Windows2000-based managed hosts (1651121) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Veritas Cluster Server resources details not displayed forWindows 2003-based managed hosts (1705089) ... . . . . . . . . . . . . . . . . . . 34

File system drive paths not displayed for Windows-basedmanaged hosts (1709351) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Resource configuration issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35HBA and array discovery issues on x86-based Linux systems

(1068470) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35High availability configuration issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Veritas Cluster Server Management Console log on screen isdisplayed when the Administer link is clicked for acluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Managed host state appears faulty during Management Serverfailover (1455647) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Replication view in Web Console shows invalid secondary host(1511821) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Web Console does not display RVG information for Windowshosts after a disk group is deported (1542072) ... . . . . . . . . . . . . . . . . . . . . 37

Primary or secondary host name is not linked in the Replicationview (1542508) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Host name of the master node is not displayed with the textactive (1639342) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Dynamic Multipathing Add-on issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Exception error on DMP cases formanaged hosts in Faulty state

(1586481) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Health Check Add-on issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Health Check reports in the pending state are canceledwhen theWeb Server is started .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

License Deployment Reporter Add-on issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Updatedprice tier information is not displayed in theSFManager

Web Console (1586099) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Storage Foundation Administration for Windows Add-on issues ... . . . . . . . . 39

Storage Foundation Administration for Windows Add-on WebConsole help issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Storage Foundation Administration for Unix Add-on issues ... . . . . . . . . . . . . . . 39

9Contents

Incorrect disk format is displayed after a disk initialize operation(1599496) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Incorrect status of controller is displayed in the Web Console(1601591) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Error when the Administer link is selected for a StorageFoundation host that has SFManager 1.1.1 and SFManager2.0 installed .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Error onAdminister pagewhen the summary pages formultiplehosts are open (1544627) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Incorrect file system layout version displayed for file systemson Storage Foundation 5.0 MP3 hosts (1602556) ... . . . . . . . . . . . . . . . . . 41

Incorrect intent log size displayed for file systems on StorageFoundation 5.0 MP3 hosts (1602678) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Create volume set operation fails while adding a swap or a rootvolume to the volume set (1637115) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Creating a canned file placement policy fails on StorageFoundation 5.0 MP3 hosts (1447543) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Errors in the Web Console after the usage threshold is set on aStorage Foundation 5.0 MP3 host (1587097) ... . . . . . . . . . . . . . . . . . . . . . . . 42

CLI-based file systemoperation changes are not displayed in theWebConsole for anHP-UX11.31managedhostwithStorageFoundation 5.0 (1587933) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Erroneous wizard titles displayed for Volume Manager andVolume Replicator tasks (1602526) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Erroneous task names displayed on the PrimaryReplicatedDataSet view (1590623) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Volume Manager links from the Administer page may hang ona Linux-based Management Server (1536502) ... . . . . . . . . . . . . . . . . . . . . . 43

Cannot disable capacity monitoring for a root file system or anon-multi-device file systemonStorage Foundation5.0MP3hosts (1521996) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Other issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43VEA Java Console does not launch after SF Manager 2.0

Management Server installation on a Linux host(1383236) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Package checks onManagement Server andmanagedhosts showwarnings .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Logging out of SF Manager 1.1.1 causes SF Manager 2.0 sessionto end on Firefox .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

SF Manager root user cannot log on to the PAM domain on aLinux host (1591458) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Contents10

Appendix A Documentation addenda and errata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Addenda and errata for SF Manager Online Help .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Managing hosts in SF Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45New Security Group options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47About deploying SF Manager Add-ons .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Using SF Manager in high-availability environment .... . . . . . . . . . . . . . . . . . 49About configuring SF Manager in high availability

environment .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Prerequisites for configuring SFManager in the high availability

environment .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Configuring a new SF Manager installation in high availability

environment .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Log file locations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Addenda and errata for man pages ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Xdistc ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Appendix B Getting help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Using the product documentation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Commenting on product documentation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Displaying online help .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Understanding how to troubleshoot SF Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Error messages ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Other troubleshooting steps ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Contacting Symantec ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Using the support Web site ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Subscribing to email notification service ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Accessing telephone support ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Obtaining support by email ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Obtaining license information .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Purchasing products ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Providing feedback about the documentation .... . . . . . . . . . . . . . . . . . . . . . . . . . . 62

11Contents

Contents12

Overview of this release

This chapter includes the following topics:

■ Introduction to Storage Foundation Manager

■ SF Manager installation options

Introduction to Storage Foundation ManagerStorage Foundation Manager (SF Manager) provides the infrastructure and asingle console for administrators and operators tomonitor, visualize, andmanagetheir Storage Foundation products and generate reports about storage resources.

SF Manager also provides prepackaged add-ons to handle complex processes likemigrating volumes, managing DMPs, verifying connections, and implementingstorage tiering.

A centrally managed deployment consists of Storage Foundation ManagerManagement Server, and one or more managed hosts.

Management Server collects and manages information pertaining to the StorageFoundation products on the managed hosts. In a centrally managed deployment,users can connect to Management Server via a Web browser to manage aheterogeneous environment of Storage Foundation hosts.

Existing Storage Foundation software products, such asVeritasVolumeManager,Veritas File System, Veritas Volume Replicator, and infrastructure componentsthat are running on legacy hosts can participate in the centrally administereddeployment.

SF Manager provides the following benefits:

■ Collect and centralize information: Management Server collects informationabout the state of storage resources deployed throughout the network. Youcan generate various reports, analyze performance, and study storageutilization.

1Chapter

■ Single sign-on: You can log on to Management Server and view informationpertaining to Storage Foundation products on all the hosts participating incentralized management. You can perform management operations on thehosts to which you have access privileges.

■ Secure communication channels: All communication between any two hostsis conducted over a secure channel.

If you do not choose a centrally managed deployment, the host is configured asa standalone host, responsible for all of the agents installed on that host. In thistraditional, single-host mode, users can connect using either a Java console, or aWeb browser.

Note: The terms Central Management Server and Management Server refer tothe same SF Manager component, and are used interchangeably in thedocumentation and the Web Console.

SF Manager installation optionsYou can install SF Manager in the following ways:

■ If you choose to implement centralized management, then a typical fullinstallation of SF Manager consists of the following: a single ManagementServer, multiple managed hosts, and any number of Web Consoles.

■ If you prefer to implement the traditional single host management, then youhave two options: install a "thick" client, the Java-based Veritas EnterpriseAdministrator, or a light-weight Web Server that relies on a standard Webbrowser client; however, only the Java Console supports single hostmanagement of both 5.0 and 4.x hosts.

With each installation option, you can establish user credentials such thatauthorized users can access the product to perform sensitive management tasksand other users can perform only a more basic set of functions.

Overview of this releaseSF Manager installation options

14

System requirements


■ Operating system requirements

■ Third-party required libraries

■ System resource requirements

■ Supported hardware

■ Web browser requirements

■ Network and firewall requirements

Operating system requirementsTable 2-1 provides an overview of SF Manager operating system requirementsfor Management Server:

Table 2-1 SF Manager operating system requirements for Management Server

NotesOperating system supported

x86 64-bit is the supported architecture.Red Hat Enterprise Linux 4.0 Update 3

Red Hat Enterprise Linux 5.0

Red Hat Enterprise Linux 5.1 Update 1



x86 64-bit is the supported architecture.SUSE Linux Enterprise Server 9

SUSE Linux Enterprise Server 10

2Chapter

Table 2-1 SF Manager operating system requirements for Management Server(continued)


SPARC is the supported architecture.Solaris 10

x86 64-bit is the supported architecture.Windows 2003

Table 2-2 provides an overview of SF Manager operating system requirementsfor managed hosts:

Table 2-2 SF Manager operating system requirements for managed hosts


On AIX hosts, the xlC runtime environmentmust be version 7 or later. Use the lslpp-lc | grep xlC.rte command to verifythe version of the xlC runtime environment.

AIX 5.2

AIX 5.3

AIX6.1 (only forStorageFoundation5.0MP3hosts)

HP-UX 11.11 (only for Storage Foundation3.5 hosts)

HP-UX 11.23

HP-UX 11.31

On Red Hat Enterprise Linux 4.0, StorageFoundation 5.0 is supported only on 64-bitXeon and x86; Storage Foundation 4.1 issupported on x86 and Xeon (32- and 64-bit).


RedHat Enterprise Linux 5.0Update 2 (onlyfor Storage Foundation 5.0 MP3 hosts)

On SUSE Linux Enterprise Server 9, StorageFoundation 5.0 is supported only on 64-bitXeon and x86; Storage Foundation 4.1 issupported on x86 and Xeon (32- and 64-bit).

SUSE Linux Enterprise Server 9

SUSE Linux Enterprise Server 10 (only forStorage Foundation 5.0 MP3 hosts)

Solaris 8

Solaris 9

Solaris 10 SPARC

Solaris 10 x86

Windows 2000 Server is supported on x86andx64.Windows2003Server andWindows2008 Server is supported on x86, x64, andIA64.

Windows 2000 Server

Windows Server 2003

Windows Server 2008

System requirementsOperating system requirements

16

For the most complete, up-to-date platform support documentation for StorageFoundation (UNIX) and Storage Foundation HA for Windows, visit the SymantecTechnical Support Web site :


Operating system updates requiredOperating system updates are required to run SF Manager:

■ On HP-UX 11.11 hosts, install the PHCO_36006.CORE-SHLIBS,PHCO_24396.SYS-ADMIN, and PHSS_37517.CORE-SHLIBS patches.

■ On HP-UX 11.23 hosts, install the PHSS_31855 and PHSS_32228 patches.

■ On HP-UX 11.23 Itanium hosts, install the PHSS_35528 patch.

■ On HP-UX 11.31 Itanium hosts, install the PHSS_36311 patch.

■ OnSolaris hosts, install the SunWorkshopCompilers Bundled libC (SUNWlibC)(SPARC), version 5.10,REV=2004.11.22.

■ On Solaris 8 SPARC hosts, install the 108434-17, 108435-17, and 109147-07patches.

■ On Solaris 9 SPARC hosts, install the 111711-11 and 111712-11 patches.

■ On Solaris 10 hosts, install the 120182-02 patch.

■ For operating system updates to Windows hosts, refer to your StorageFoundation HA for Windows Release Notes.

■ The Symantec Web Server relies on the Java Runtime Engine (JRE) 1.5. Youshould ensure that your operating system has the necessary patches to runthe JRE. For more information, visit your operating system vendor’s Web site.

Note: The HP-UX Node and Host Name Expansion feature is not supported onSymantec products.

For themost complete, up-to-date documentationabout requiredoperating systemupdates, visit the Symantec Technical Support Web site for the latest StorageFoundation (UNIX) and Storage Foundation HA for Windows Release Notes.

Third-party required librariesThis section lists third-party libraries required to run SF Manager:

■ 32-bit SNIA Common HBA API on Windows hosts

17System requirementsThird-party required libraries


32-bit SNIA Common HBA API on Windows hostsFor proper discovery of Fibre Channel attached devices—including discovery ofHBA and its target ports—SF Manager requires installation of the 32-bit SNIACommon HBA API on all Windows managed hosts running HBA controllers.

The Common HBA API would be typically available as part of your HBA vendor’sdriver kit, or you can download it from your HBA vendor’s site.

Follow these steps to determine if the SNIA Common HBA API is already presenton your Windows host.

To verify that the 32-bit SNIA Common HBA API is installed on a Windows host

1 Open the registry editor on the managed host using the regedit command.

2 Check the following location to get the SNIA library information:

HKEY_LOCAL_MACHINE\SOFTWARE\SNIA\HBA\hba_model

On 64-bit platforms, SF Manager requires 32-bit libraries installed as apre-requisite. For more information, see your HBA vendor documentation.

System resource requirementsThe amounts of memory and disk space that SF Manager requires are in additionto the resources already consumed by other software on the host.

Table 2-3 provides the memory specifications and the disk space specificationsfor SF Manager components.

Table 2-3 System resources on SF Manager hosts

Disk space requiredMemoryrequired

CPU requiredComponent

Database only: 19GB (for 750hostsincluding DB backup)

Database only: 6GB (for 100 hosts)

Requires additional swap space ofat least 8GB to 16GB.

2GB (Less than50 managedhosts)

4GB (Over 50managed hosts)

Dual processor(Less than 50managed hosts)

Quad processor(Over 50managed hosts)

ManagementServer

System requirementsSystem resource requirements

18

Table 2-3 System resources on SF Manager hosts (continued)

Disk space requiredMemoryrequired

CPU requiredComponent

■ On UNIX hosts: 50MB in/var/opt for discovery statefiles; 50MB in /opt

■ On Windows hosts: 30MB inInstall_path\Veritas\VRTSsfmh;50MB in%COMMONAPPDATAFOLDER%\Symantec

See StorageFoundationdocumentation

See StorageFoundationdocumentation

Managed host

Read the following Symantec Technical Support TechNotes for the latestinformation on updates, patches, and software issues regarding this release:

http://seer.entsupport.symantec.com/docs/317227.htm

Supported hardwareThe followingTechNote contains theHardwareCompatibilityList (HCL) forStorageFoundation Manager 2.0 and Storage Foundation 5.0 products on UNIX:

http://support.veritas.com/docs/283161

The followingTechNotes contain theHardwareCompatibilityList (HCL) forStorageFoundation Manager 2.0 and Storage Foundation products on Windows:

■ Storage Foundation 5.0 for Windows:http://seer.entsupport.symantec.com/docs/286541.htm

■ Storage Foundation 5.1 for Windows:http://seer.entsupport.symantec.com/docs/302144.htm

Web browser requirementsThe Veritas Storage Foundation Manager Console is a graphical user interfacethat displays reports and other information for users of the Storage Foundationproducts through a standard Web browser.

The Web browsers that the Storage Foundation Manager Console supports are:

■ Internet Explorer 6.0 (or later)

■ Firefox 2.0 (or later)

Additional considerations for supported Web browsers:

■ Your browser must support JavaScript 1.2.

19System requirementsSupported hardware


http://support.veritas.com/docs/283161



■ If you are using pop-up blockers (including Yahoo Toolbar or Google Toolbar),either disable them or configure them to accept pop-ups from the Web Serverto which you will connect.

■ For Internet Explorer 6.0 onWindows 2003 (Server and Advanced Server), setthe default intranet zone security level to MEDIUM or lower.

Use the following criteria to identify the kind of system you need to run the WebConsole:

■ The Web Console host must be able to access SF Manager.

■ SF Manager must support the Web browser.

Network and firewall requirementsIf you are managing hosts within multiple domains, you will need to update theresolve.conf file on the Management Server host. This file resides by default inthe /etc directory.

For example:

search my.domain1.example.com my.domain2.example.com

SF Manager uses the default ports as shown in Table 2-4 to transfer information.

Table 2-4 Default ports in a SF Manager installation

Impact ifblocked

PurposeInitiatorProtocolPort

Managedhostwillnot be added tothe ManagementServer domain

ManagementServercommunicationswith themanagedhosts

ManagementServer

TCP5634

Managedhostwillnot be added tothe ManagementServer domain

Managed host tosend heartbeats;also used toupload the datafromthemanagedhost toManagementServer.

managed hosts

System requirementsNetwork and firewall requirements

20

Table 2-4 Default ports in a SF Manager installation (continued)

Impact ifblocked

PurposeInitiatorProtocolPort

Users will not beable to access theWeb Console

Run StorageFoundation WebConsole

Web ConsoleTCP14161

Managed hostswill not properlyauthenticate

During managedhost installs only,used to locate theAuthenticationService RootBroker

ManagementServer, managedhosts

TCP14545

21System requirementsNetwork and firewall requirements

System requirementsNetwork and firewall requirements

22

Software limitations


■ Installation and configuration limitations

■ High availability configuration limitations

■ Dynamic Multipathing Add-on limitations

■ Volume Migration Add-on limitations

■ Storage Foundation Administration for Windows Add-on limitations

■ Considerations for Storage Foundation 4.x Windows managed hosts

■ Graphical user interface issues

Installation and configuration limitationsThe following notes cover limitations pertaining to the tasks of installing orconfiguring SF Manager.

SF Manager does not discover HDS RAID600 enclosureThe SF Manager Web Console does not display information for a HDS RAID600enclosure. It also does not display information on the enclosure's associationswith other storage objects.

SF Manager does not discover EMC DMX-3 enclosureThe SF Manager Web Console does not display information for a EMC DMX-3enclosure. It also does not display information on the enclosure's associationswith other storage objects.

3Chapter

Incremental backup and restore procedures are not supportedSFM2.0 does not support incremental database backups or incremental databaserestore procedures. However, it does support full backup and restore databaseprocedures. If youwant to backup or restore the database, youwill need to backupor restore the entire database.

SF Manager does not discover a X64 Sun SE3510 array (1033610)Although it does support the device, the SF Manager Console does not displayinformation for the X64 Sun StorEdge 3510 array. The Console does not displayinformation on the array's association with additional storage objects. There isno workaround for this issue.

SF Manager database location cannot be specified as a directory namethat contains Japanese characters (1532409)

While configuring SF Manager on Management Server in Japanese locale, youcannot change the SFManager database location to a directoryname that containsJapanese characters. If you change the default database location to a directoryname that contains Japanese characters, the characters that are specified after /are not recognized and the database is created in the root (/) directory. After this,if you try to reconfigure SF Manager, the operation hangs.

High availability configuration limitationsThe following notes cover limitations pertaining to the tasks associated with SFManager in a high availability configuration.

SF Manager operations hang during failoverWhen a failover occurs, any ongoing SF Manager operations like migration ofvolumes will abort.

Dynamic Multipathing Add-on limitationsThe following notes cover limitations pertaining to the Dynamic MultipathingAdd-on.

Software limitationsHigh availability configuration limitations

24

Unsupported managed hosts versions (1034396)In the DMP Add-on Wizard's Path Selection panel, paths on HP-UX hosts withStorage Foundation3.5 installedwill not be selectable. Thesehostswill be qualifiedby an Unsupported MH label.

If you have HP-UX managed hosts that have Storage Foundation 3.5 installed onthem, you will need to upgrade them to Storage Foundation 4.0 before you canuse them in conjunction with the DMP Add-on.

Volume Migration Add-on limitationsThe followingnotes cover limitations pertaining to theVolumeMigrationAdd-on.

Volume migration not supported for volumes under CVM disk groupsYou cannot use the Volume Migration Add-on to migrate the volumes that areunder Cluster Volume Manager disk groups.

Storage Foundation Administration for WindowsAdd-on limitations

The following notes cover limitations pertaining to the Storage FoundationAdministration for Windows Add-on.

Storage Foundation for Windows features that are not supportedThe Storage Foundation Administration for Windows Add-on does not supportthe following features of Storage Foundation for Windows (SFW):

■ iSCSI and iSNS management

■ VxCache

■ VSS Snapshot Scheduling for Exchange or SQL

■ Set SMART monitoring or Ping Disk

■ Graph Historical Statistics information

■ Fast File Resync (FFR)

■ Subdisk operations

25Software limitationsVolume Migration Add-on limitations

Veritas Volume Replicator features that are not supportedThe Storage Foundation Administration for Windows Add-on does not supportthe following features of Veritas Volume Replicator:

■ Selecting a snap plex of a secondary volume during synchronized snapshots

■ Replicate volume option of the volume tasks

Storage Foundation for Windows versions supported by StorageFoundation Administration for Windows Add-on

The Storage Foundation Administration for Windows Add-on can be used tomanage the following Storage Foundation for Windows hosts:

■ Storage Foundation for Windows 4.3 hosts

■ Storage Foundation for Windows 5.xhosts

Considerations for Storage Foundation 4.x Windowsmanaged hosts

Keep these points in mind when centrally managing Storage Foundation 4.xWindows hosts:

■ On Storage Foundation 4.x hosts, the earlier generation of the Rule Manager(VRTSap) is installed. The Action Provider can continue to be used, even whencentrally managed with SF Manager.

■ Action Provider can manage alerts and task execution for the local host only;however, the Rule Manager can manage alerts and task execution from anyhost in the Management Server domain.

■ Only the Rule Manager can provide central administration of rules.Otherwise, Action Provider must be managed on each host, independently.

■ Managing and creation of rules for theVeritasActionProvider orActionAgentfor a standalone host is available only through the Veritas EnterpriseAdministrator (Java Console).

Graphical user interface issuesThe following notes pertain to issues you might encounter with SF Managerdisplays.

Software limitationsConsiderations for Storage Foundation 4.x Windows managed hosts

26

Storage usage displays as zero for non-Veritas file typesStorage Utilization shows file system usage is zero for: FAT, FAT32, and RAW.Only Veritas File System types are supported.

SENA arrays not displayedSFManager does not display SENA disk arrays on the Enclosure tab. Informationpertaining to SENA arrays in other views is not reliable.

Unable to report LUN size correctly on AMS500 enclosure (1027514)LUN size is not automatically updated on AMS500 enclosure, therefore theinformation displayed is incorrect. The LUN size is inaccurate because HBAexplorer provides incorrect information.

27Software limitationsGraphical user interface issues

Software limitationsGraphical user interface issues

28

Known issues


■ Managed host issues

■ Console display issues

■ Resource configuration issues

■ High availability configuration issues

■ Dynamic Multipathing Add-on issues

■ Health Check Add-on issues

■ License Deployment Reporter Add-on issues

■ Storage Foundation Administration for Windows Add-on issues

■ Storage Foundation Administration for Unix Add-on issues

■ Other issues

Managed host issuesThe following issues relate to host management and migration.

Add host operation may fail on a Storage Foundation 5.0 host that hasbeen upgraded to Storage Foundation 5.0 MP3

If you install SFManager 2.0 on aStorage Foundation 5.0 host, and thenupgradedto Storage Foundation 5.0 MP3, the add host operation on the host may fail.

4Chapter

WorkaroundThe add host operation fails if the xprtld and vxdclid processes are running aspart of the Storage Foundation5.0MP3 installation. Youneed to stop theprocessesand start them from the SF Manager installation.

To restart the xprtld and vxdclid processes from the SF Manager installation

1 Check whether the xprtld process is running as part of the StorageFoundation 5.0 MP3 installation.

# ps -eaf | grep xprtld

If the output of the command is /opt/VRTSdcli/xprtl/bin/xprtld/opt/VRTSdcli/xprtl/etc/xprtld.conf, the xprtld process is running aspart of the Storage Foundation installation.

2 Check whether the vxdclid process is running as part of the StorageFoundation 5.0 MP3 installation.

# ps -eaf | grep vxdclid

If the output of the command is /usr/sbin/vxdclid, the vxdclid process isrunning as part of the Storage Foundation installation.

3 If the xprtldprocess is running as part of theStorage Foundation installation,stop it.

# /opt/VRTSdcli/xprtl/adm/xprtldctrl stop

4 If the vxdclid process is running as part of the Storage Foundationinstallation, stop it.

# /etc/init.d/vxdcli.sh stop

5 Start the xprtld process from the SF Manager installation.

# /opt/VRTSsfmh/adm/xprtldctrl start

6 Start the vxdclid process from the SF Manager installation.

# /opt/VRTSsfmh/etc/vxdcli.sh start

You can now perform the add host operation on the host.

HP-UX 11.11 hosts cannot be added to the Management Server domainAfter you install the SF Manager managed host package (VRTSsfmh) on an HP-UX11.11 host, youmaynot be able to add the host to theManagement Server domain.This issue occurs when the xprtld process has not been started on the host.

Known issuesManaged host issues

30

WorkaroundInstall the HP-UX patch PHCO_24400, or a superseding patch, on the host.

After installing the patch, use the following command to start the xprtld process.

/opt/VRTSsfmh/adm/xprtldctrl start

You can now add the host to the Management Server domain.

Console display issuesThe following issues relate to displays in the Console.

WebGUI monitoring shows status as RUNNING and does not changeto FINISHED (1061587)

In SF Manager, when monitoring the status of tasks that are running on SF 4.x,SF 5.0, and SF 5.0 RP1 managed hosts (Monitoring > Tasks), the status of sometasks appears asRUNNINGand their Exit Status is blank. The status of these tasksnever changes to FINISHED, nor does the Exit Status update.

There is no workaround for this issue. This behavior is normal as tasks in aRUNNING state do not display an Exit Status.

Collapse of tree control in the DMP or Volume Migration add-ons maytrigger "Unresponsive Script" dialog (1057360)

Whenusing aFirefox browser, selectingExpandAll buttonmay result in awarningmessage, Unresponsive Script.

Depending on the client computer and the size of the data set, you may get thefollowing warning/error when using the expand all button to fully display theDMP or Volume Migration components:

■ Warning: Unresponsive ScriptA script on this page may be busy or it may have stopped responding. You canstop the script now or continue to see if the script will complete.

HBA information not displayed in the SF Manager Web Console forSolaris 9 managed hosts

For QLogic QLA2342 HBAs on Solaris 9 managed hosts, the HBA information isnot displayed in the SF Manager Web Console if the HBA API libraries are notinstalled.

31Known issuesConsole display issues

WorkaroundTo display the HBA information in the Web Console, you have to install the HBAAPI libraries. The HBA API libraries would be typically available as part of yourHBA vendor’s driver kit, or you can download them from your HBA vendor’s site.

SF Manager Web Console displays incorrect count of managed hostsin the Management Server domain

If you change the system time on a Management Server host, the Web Consolemaynot display the correct count ofmanagedhosts that exist in theManagementServer's domain.

WorkaroundYou have to stop and restart the SF Manager database to correct the problem.

To stop the database, run the following command:

/opt/VRTSsfmcs/config/adm/db_stop.sh

To restart the database, run the following command:

/opt/VRTSsfmcs/config/adm/db_start.sh

All Scheduled Tasks link appears erroneously in Summary view forStorage Foundation 4.x for Windows hosts (1525967)

In the Summary view for a Storage Foundation 4.x for Windows managed host,the All Scheduled Tasks link is erroneously displayed. You should ignore thislink as Storage Foundation 4.x does not support schedules.

SEGATE Fiber channel JBOD discovery not supported in SF Manager2.0 (1472420)

If the disks attached to amanaged host are part of a JBODenclosure, the enclosurename is displayed as None in the Summary view of the Disks attached to themanaged host.

There is no workaround for the issue.

Action link does not work in Health Check reports spanning multiplepages (1542015)

If the violations in a Health Check report span across multiple pages, the Actionlink is active only on the first page. On subsequent pages, the link does not work.

Known issuesConsole display issues

32

WorkaroundYou can either change the table settings to display all the violations in a singlepage, or you can refresh the page in the Web browser.

To change the table settings, click Table Settings in the right-hand corner abovethe table listing the violations. Set the Rows Per Page value and click OK.

Tabular data spanning multiple pages cannot be viewed beyond page10 (1537636)

In a Web Console view, if the tabular data spans across more than 10 pages andyou change the view when you are on any page beyond page 9, then, navigatingback to the first view displays page 10 and the icon to go to the next page appearsdisabled.

WorkaroundView any page between 1 to 9. The icon to go to the next page is now enabled.

Error message displayed when the connection to SF Manager is timedout (1507878)

While administering a managed host in the Web Console, if you are inactive fora period of time in any of the product views, your connection to SF Manager istimed out. If you click on any link in the view, you may see an error messageDomain list is empty, instead of the SF Manager log on page.

There is no workaround for this issue. You need to log on to SF Manager againand navigate to the view.

Administer link is erroneously displayed for UDF file systems (1586223)When you select a UDF file system in the File Systems view, the Administer linkis displayed. If you click theAdminister link, a null pointer exception error occurs.

There is no workaround for this issue. The Administer link is erroneouslydisplayed in the view. You cannot administer UDF file systems in StorageFoundation Manager 2.0.

33Known issuesConsole display issues

Links to annotations-related tasks erroneously displayed in the Searchview (1593642)

Whenyou search for hosts in the Search view, alongwith the search results, linksforperformingannotations-related tasks aredisplayed.The links that aredisplayedare Add a New Annotation and Add Existing Annotations.

The links are erroneously displayed. Storage Foundation Manager 2.0 does notsupport annotations.

Resource Mapping report does not display external disk connected toan array on a Windows managed host (1636114)

An external disk is not displayed in the Resource Mapping report when it isconnected to an array on a Windows managed host, that also has an iSCSI arraythat is attached to it.

There is no workaround for this issue.

Veritas Cluster Server information not displayed for Windows2000-based managed hosts (1651121)

If you have a Windows 2000-based managed host in your Management Serverdomain, which is a node in a Veritas Cluster Server (VCS) cluster, its VCS-relatedinformation is not displayed in the Web Console.


Veritas Cluster Server resources details not displayed for Windows2003-based managed hosts (1705089)

The Veritas Cluster Server (VCS) resources-related information may not bedisplayed in theWebConsole for a cluster that hasWindows 2003-basedmanagedhosts.

WorkaroundYou need to refresh the details of the managed host to be able to view the VCSresources-related information.

To refresh the details of a managed host

1 Select Settings > Host Management.

2 Under Managed Hosts, in the table that lists the managed hosts, select themanaged host that you want to refresh and do one of the following:

Known issuesConsole display issues

34

■ At the top of the table, click the Refresh Host option.

■ From the submenu, right-click the managed host and select the RefreshHost option.

3 In the message box to confirm the refresh operation, click OK.

File system drive paths not displayed for Windows-based managedhosts (1709351)

In theWeb Console, when you view the details of file systems forWindows-basedmanaged hosts, the details of the drive paths are not displayed when you selectthe Drive Paths tab.


Resource configuration issuesThe following issues relate to the use of SF Manager to configure and administerresources.

HBA and array discovery issues on x86-based Linux systems (1068470)HBA and array discovery may not work properly on x86-based Linux systems.The discovery informationmay be incomplete. This issue has been observed onlyon x86-based Linux systems with a 2.6.x kernel and a version 8.x QLogic HBAdriver.

WorkaroundBypass the HBA API library by renaming the /etc/hba.conf file before the nextdiscovery process. For example,

mv /etc/hha.conf /etc/hba.conf.orig

High availability configuration issuesThe following issues relate to SF Manager High availability configuration.

35Known issuesResource configuration issues

Veritas Cluster Server Management Console log on screen is displayedwhen the Administer link is clicked for a cluster

When you click the Administer link for a Veritas Cluster Server (VCS) cluster inthe SF Manager Web Console, the VCS Management Console log on screen isdisplayed instead of the cluster information.

WorkaroundYouneed tomanually add the details of theAuthentication Broker for the cluster,in the SF Manager configuration file. You also need to set up trust with theAuthentication Broker and restart the Web Server.

Add the following entry for the Authentication Broker for the cluster, to the/etc/default/broker_list.conf file, separated by a comma (,):

"vxss://brokername:brokerport" : { "type":"secondary", "domains" :

["brokername/unixpwd"] }

where, brokername is thehost nameof theAuthenticationBroker, and brokerportis the port used to connect to the Authentication Broker.

Run the following command to set up trust with the Authentication Broker:

# /opt/VRTSsfmcs/sec/bin/vssat setuptrust

Run the following command to restart the Web Server:

# /opt/VRTSsfmcs/cweb/sfmw restart

Log on to the SF Manager Web Console using the domain of the Authenticationbroker for the cluster.

The cluster information is now displayed when you click the Administer link forthe cluster.

Managed host state appears faulty during Management Server failover(1455647)

When a Management Server failover occurs in a high availability environment,all the managed hosts appear as faulty in the Web Console.

There is no workaround for this issue. The managed hosts states are restoredafter the failover is complete.

Known issuesHigh availability configuration issues

36

Replication view in Web Console shows invalid secondary host(1511821)

In SF Manager for high availability configuration, when the secondary host in acluster is not in theManagement Server domain, theReplication view in theWebConsole shows an invalid secondary host.


Web Console does not display RVG information for Windows hostsafter a disk group is deported (1542072)

After you deport a disk group on the primary host, secondary RVG informationis not displayed in the Web Console on Management Server.


Primary or secondary host name is not linked in the Replication view(1542508)

When a primary or a secondary host is added to the Management Server domainusing a virtual IP, and the virtual IP is used for replication, its actual host namemay not appear as a link in the Replication view of the Web Console.


Host name of the master node is not displayed with the text active(1639342)

In SF Manager for high-availability configuration, if the host name of the masternode is changed, the text active is not displayednext to thehost name in thehostslist.

WorkaroundYou need to rediscover the master node. On the master node, run the mh_ctl.plscript with the --rescan option.

/opt/VRTSsfmh/bin/mh_ctl.pl --rescan

Dynamic Multipathing Add-on issuesThe following issues relate to Dynamic Multipathing Add-on.

37Known issuesDynamic Multipathing Add-on issues

Exception error on DMP cases for managed hosts in Faulty state(1586481)

If amanagedhost reaches aFaulty state betweendisabling and reenabling a path,an exception error occurs while reenabling the path.

WorkaroundSF Manager requires the managed host to be in a Healthy state before you canenable or disable paths. You have to correct the Faulty state of themanaged host,and then reenable the path.

Health Check Add-on issuesThe following issues relate to Health Check Add-on.

Health Check reports in the pending state are canceled when the WebServer is started

If a Health Check report that you have created is in progress, and the Web Serveris restarted in cases like a failover, the report generation may get canceled.

There is noworkaround for this issue. You have to create theHealth Check reportagain.

License Deployment Reporter Add-on issuesThe following issues relate to License Deployment Reporter Add-on.

Updated price tier information is not displayed in the SF Manager WebConsole (1586099)

When you upload a price tier file in the StorageFoundationLicenseDeploymentSummary view, a message is displayed that indicates that the upload wassuccessful. However, the updated information is not displayed in theProduct-TierMapping view and the Tier-Host Mapping view.

WorkaroundYou have to create a directory to upload the price tier file.

Known issuesHealth Check Add-on issues

38

Under the /var/opt/VRTSsfmh/spool/addons/store directory, create theVRTSsfmldr-1.0/cms directory. In the Web Console, upload the price tier fileagain. The updated price tier information is now displayed in the views.

Storage Foundation Administration for WindowsAdd-on issues

The following issues relate to Storage Foundation Administration for WindowsAdd-on.

Storage Foundation Administration for Windows Add-on Web Consolehelp issues

The following issues exist in the Web Console help for the Storage FoundationAdministration for Windows Add-on:

■ Migrate help: Text erroneously makes a reference to bunker.

■ Pause Secondary operation help: The help for Pause Secondary from Primaryis erroneously displayed.

■ RDS Replication help: The help text is not displayed.

■ Summary tab of the Replicated Data Set page: The help text is not displayed.

WorkaroundUse the Using Veritas Volume Replicator online Help document and navigate tothe appropriate help topic.

Storage Foundation Administration for Unix Add-onissues

The following issues relate to StorageFoundationAdministration forUnixAdd-on.

Incorrect disk format is displayed after a disk initialize operation(1599496)

When you administer a UNIX host, if you initialize a disk and change its formatto either Simple or Sliced, Volume Manager (VxVM) changes the disk formatcorrectly. However, in the Console, the disk format still appears as CDS.


39Known issuesStorage Foundation Administration for Windows Add-on issues

Incorrect status of controller is displayed in the Web Console (1601591)When you administer a UNIX host, if you disable a controller, the controller stillappears enabled in the SF Manager Web Console. This issue occurs even whenthe disable operation is successful.


Error when the Administer link is selected for a Storage Foundationhost that has SF Manager 1.1.1 and SF Manager 2.0 installed

If you have a Storage Foundation host that has SFManager 1.1.1 and SFManager2.0 installed on it, an error may occur when you administer the host. When youclick theAdminister link for the host, youmay see the following error in theWebConsole:

Please check vea configuration or the state of vea processes on this

host.

WorkaroundYou need to remove the host from the 1.1.1 Management Server domain beforeyou can administer it using SF Manager 2.0.

To remove the managed host from the 1.1.1 Management Server domain

◆ On the managed host, run the tostandalone.pl script.

/opt/VRTSsfmh/bin/tostandalone.pl

Note: You can use the tostandalone.pl script to remove 1.1.1 ManagementServer also.

You can now administer the host using SF Manager 2.0.

Error on Administer page when the summary pages for multiple hostsare open (1544627)

In the SFManagerWebConsole, you canpress the Ctrl key and open the summarypage for multiple hosts in different tabs of the browser. Then, if you select theAdminister link for these hosts bymoving between the tabs quickly, youmay seean error on the Administer page. This issue may occur on the browsers thatsupport tabs, such as, Internet Explorer 7.0 or later, or Firefox 2.0 or later.

Known issuesStorage Foundation Administration for Unix Add-on issues

40

Incorrect file system layout version displayed for file systems onStorage Foundation 5.0 MP3 hosts (1602556)

When you select a Storage Foundation 5.0MP3 host to administer, and select FileSystems from the Administer page, the file systems on the host are displayed. Ifyou select a file system to view its properties, and select the Status link, the filesystem layout version may be incorrectly displayed as -1.


Incorrect intent log size displayed for file systems on StorageFoundation 5.0 MP3 hosts (1602678)

When you select a Storage Foundation 5.0MP3 host to administer, and select FileSystems from the Administer page, the file systems on the host are displayed. Ifyou select a file system to view its properties, and select theStatus link, the intentlog size may be incorrectly displayed as 4 GB.


Create volume set operation fails while adding a swap or a root volumeto the volume set (1637115)

When you select a Storage Foundation 5.0 MP3 host to administer, and select AllVolumes from the Administer page, the volumes on the host are displayed. Ifyou attempt to create a volume set on the host and add a swap or a root volumeto the volume set, the operation fails.

Volume Manager does not support addition of swap volumes or root volumes toa volume set.

Creating a canned file placement policy fails on Storage Foundation5.0 MP3 hosts (1447543)

When you select a Storage Foundation 5.0MP3 host to administer, and select FileSystems from the Administer page, the file systems on the host are displayed. Ifyou select a Multi-device File System (MDFS) and attempt to create a canned filesystem placement policy, the wizard panel displays a message that the operationhas been successfully fired. However, the operation fails.


41Known issuesStorage Foundation Administration for Unix Add-on issues

Errors in the Web Console after the usage threshold is set on a StorageFoundation 5.0 MP3 host (1587097)

When you select a Storage Foundation 5.0MP3 host to administer, and select FileSystems from the Administer page, the file systems on the host are displayed. Ifyou select a Multi-device File System (MDFS) and set the usage threshold for it,the information on the file systems for the host is no longer displayed in the WebConsole.


CLI-based file system operation changes are not displayed in the WebConsole for an HP-UX 11.31 managed host with Storage Foundation5.0 (1587933)

On an HP-UX 11.31 managed host with Storage Foundation 5.0, if you performany CLI-based file system operations such as creating or mounting a file system,the changes are not displayed in the Web Console.

WorkaroundYou need to refresh the Storage Agent in the VEA Console on the managed host.

To refresh the Storage Agent in the VEA Console

1 Launch the VEA Console on the managed host.

/opt/VRTSob/bin/vea

2 Right-click on Storage Agent and select Refresh or Rescan.

Erroneous wizard titles displayed for Volume Manager and VolumeReplicator tasks (1602526)

When you administer a managed host, if you perform any Volume Manager orVolume Replicator tasks, the titles on the wizard panels appear erroneous.


Erroneous task names displayed on the Primary Replicated Data Setview (1590623)

When you administer a managed host using a Linux-based Management Server,if you select the Primary tab on the Replicated Data Set view, erroneous tasknames appear on the list.

Known issuesStorage Foundation Administration for Unix Add-on issues

42


Volume Manager links from the Administer page may hang on aLinux-based Management Server (1536502)

If you have a Linux-based Management Server, and you administer a host, theWeb Console may hang if you select any link for Volume Manager on theAdminister page.

WorkaroundRestart the Web server to restore the Web Console.

/opt/VRTSsfmcs/cweb/sfmw restart

Cannot disable capacity monitoring for a root file system or anon-multi-device file system on Storage Foundation 5.0 MP3 hosts(1521996)

After you enable capacity monitoring for a root file system or a non-multi-devicefile system on a Storage Foundation 5.0 MP3 host, you cannot disable it. Whenyou attempt to disable it using the SetUsageThreshold operation, the operationfails.


Other issuesThis section lists additional issues that cannot be categorized as display,monitoring, or resource configuration issues.

VEA Java Console does not launch after SF Manager 2.0 ManagementServer installation on a Linux host (1383236)

WhenSFManager 2.0Management Server is installed on a Linuxhost, you cannotlaunch the VEA Java Console if Storage Foundation has not been installed.

WorkaroundYou must install Storage Foundation 5.0 before you use the VEA Java Console.

43Known issuesOther issues

Package checks on Management Server and managed hosts showwarnings

When you install and configure Management Server on a Linux host, you caninstall and add managed hosts to it. After these tasks are performed, if you run apackage check on Management Server or managed hosts for the VRTSsfmh or theVRTSsfmcs packages, some warnings may be reported.

These warnings are due to modified files and should be ignored as they do notaffect any functionality.

Logging out of SF Manager 1.1.1 causes SF Manager 2.0 session toend on Firefox

On a host that has Firefox as the Web browser, if you are connected to both SFManager 1.1.1 and to SF Manager 2.0, logging out of one version causes log outfrom the other version.

There is noworkaround for this issue. You have to log on to SFManager 2.0 again.

SF Manager root user cannot log on to the PAM domain on a Linuxhost (1591458)

In SF Manager Console, if you log on to the PAM domain as a root user on a Linuxhost, an authentication failure occurs and the log on fails.

WorkaroundYou need to create a new service file for the authentication broker , edit it, andchange the configuration settings.

First, copy the /etc/pam.d/login file to /etc/pam.d/vxatd.

Edit the /etc/pam.d/vxatd file. Remove the entry that contains the textpam_securetty.so.

To change the configuration setting, run the following command:

./vssregctl -l -s -b "Security\Authentication\Authentication

Broker\AtPlugins\pam" -k "ServiceName" -t string -v "vxatd"

To restart the authentication broker, run the following command:

/opt/VRTSsfmcs/sec/bin/sfmsecdctrl stop/start

Known issuesOther issues

44

Documentation addendaand errata

This appendix includes the following topics:

■ Addenda and errata for SF Manager Online Help

■ Addenda and errata for man pages

Addenda and errata for SF Manager Online HelpThis section contains the errata and the additional information that is not includedin the Online Help for SF Manager.

Managing hosts in SF ManagerIn this chapter, added the following section on addingUNIX-basedmanagedhoststo Management Server using gendeploy.pl.

Adding UNIX-based managed hosts to Management Serverusing gendeploy.pl

You can add a UNIX-based managed host to a Management Server domain withminimal user interaction. The gendeploy.pl script available on ManagementServer can be used to create a script that is run on the managed host to add thehost to the domain.

You can copy the script that is created using gendeploy.pl to all the UNIX-basedmanaged hosts that youwant to add to the domain. After you copy the script, youhave to run it on eachmanaged host. Amanaged host onwhich you run the scriptmust have the VRTSsfmh package installed on it.

AAppendix

See the Veritas Storage Foundation Manager Installation Guide for informationon installing SF Manager host management.

Note: You cannot add a Windows-based managed host to Management Serverusing gendeploy.pl.

To add a UNIX-based managed host to a UNIX-based Management Server usinggendeploy.pl

1 On Management Server, log on as root.

2 To change the directory, run the following command:

cd /opt/VRTSsfmh/bin

3 To create the script to add a managed host, run the following command:

./gendeploy.pl --out filename

where, filename is the name of the script that you specify.

4 Copy the script to the managed host.

5 On the managed host, run the following command to make the scriptexecutable.

chmod +x filename

6 To add the managed host to the Management Server domain, run the script.

./filename

7 In the Web Console, verify that the managed host has been added to theManagement Server domain.

To add a UNIX-basedmanaged host to aWindows-basedManagement Server usinggendeploy.pl

1 On Management Server, log on as a user with administrator privileges.

2 To change the directory, run the following commandat the commandprompt:

cd C:\Program Files\Veritas\VRTSsfmh\bin

3 To create the script to add a managed host, run the following command:

runperl.bat gendeploy.pl --out filename

where, filename is the name of the script that you specify.

4 Copy the script to the managed host.

Documentation addenda and errataAddenda and errata for SF Manager Online Help

46

5 On the managed host, run the following command to make the scriptexecutable.

chmod +x filename

6 To add the managed host to the Management Server domain, run the script.

./filename

7 In the Web Console, verify that the managed host has been added to theManagement Server domain.

New Security Group optionsAdded the following note about specifying the name of a security group on theWindows-based Management Server to the description of the Name field:

OnWindows-basedManagement Server, youmust enter the name of the securitygroup in the domain name\security group name format.

About deploying SF Manager Add-onsRemoved the following columns from the SFManager Add-ons deployment table:

■ Management Server platforms supported

■ Managed host platforms supported

Also, merged the Yes and the No sub-columns present in the following columns:

■ Whether you can install or deploy on Management Server

■ Managed host platforms supported

The updated table should read:

Table A-1 SF Manager Add-ons deployment

Whether you can install ordeploy on managed hosts

Whether you can install or deployon Management Server

SF ManagerAdd-ons

NoYes

(Deployed along with ManagementServer installation)

StorageFoundationManagerDynamicMultipathingAdd-on

47Documentation addenda and errataAddenda and errata for SF Manager Online Help

Table A-1 SF Manager Add-ons deployment (continued)



SF ManagerAdd-ons

NoYes

(Download fromtheSFManagerWebsite, upload to theAdd-onRepository,and deploy on Management Server.

Depending on the platform ofManagement Server, use thefollowing command to restart theWebserver:

■ Solaris and Red Hat Linux:/opt/VRTSsfmcs/cweb/sfmw

■ Windows:On theServices controlpanel, restart theVeritas StorageManager Service.)

StorageFoundationManagerVolumeMigrationAdd-on

NoYes

(Download fromtheSFManagerWebsite, upload to theAdd-onRepository,and deploy on Management Server.

Depending on the platform ofManagement Server, use thefollowing command to restart theWebserver:

■ Solaris and Red Hat Linux:/opt/VRTSsfmcs/cweb/sfmw

■ Windows:On theServices controlpanel, restart theVeritas StorageManager Service.)

StorageFoundationAdministrationfor WindowsAdd-on

NoYes

(Download fromtheSFManagerWebsite, upload to theAdd-onRepository,and deploy on Management Server.)

StorageFoundationAdministrationfor UnixAdd-on

Yes (You candeploy thisAdd-ononUNIX managed hosts)

Yes


StorageFoundationManagerHealth CheckAdd-on


48

Table A-1 SF Manager Add-ons deployment (continued)



SF ManagerAdd-ons

Yes (You candeploy thisAdd-ononUNIX managed hosts)

Yes


StorageFoundationManagerLicenseDeploymentReporterAdd-on

Using SF Manager in high-availability environmentIn this chapter, added the following sections:

■ Sample configuration: After you create the base service groups (SFM_Services)

■ Sample configuration: After you configure SF Manager in high availabilityenvironment

Sample configuration: After you create the base service groups(SFM_Services)The following is an example of SF Manager configuration after you create thebase service groups (SFM_Services):

include "types.cf"

cluster CMSHA_GCO_DR (

UserNames = { admin = chhB }

Administrators = { admin }

)

system London (

)

system Paris (

)

group SFM_Services (

SystemList = { London = 0, Paris = 1 }

AutoStartList = { London }

)


DiskGroup SFM_Services_DG (

Critical = 0

DiskGroup = hadg

)

IP SFM_Services_IP (

Critical = 0

Device = bge0

Address = "Ip_address"

)

Mount SFM_Services_MOUNT (

Critical = 0

MountPoint = "/hafs"

BlockDevice = "/dev/vx/dsk/hadg/havol"

FSType = vxfs

FsckOpt = "-y"

VxFSMountLock = 0

)

NIC SFM_Services_NIC (

Critical = 0

Device @London = bge0

Device @Paris = bge0

)

Volume SFM_Services_VOL (

Critical = 0

Volume = havol

DiskGroup = hadg

)

SFM_Services_DG requires SFM_Services_IP

SFM_Services_IP requires SFM_Services_NIC_proxy

SFM_Services_MOUNT requires SFM_Services_VOL

SFM_Services_VOL requires SFM_Services_DG

// resource dependency tree

//

// group SFM_Services

// {

// Mount SFM_Services_MOUNT


50

// {

// Volume SFM_Services_VOL

// {

// DiskGroup SFM_Services_DG

// {

// IP SFM_Services_IP

// {

// Proxy SFM_Services_NIC

// }

// }

// }

// }

// }

See “Sample configuration: After you configure SF Manager in high availabilityenvironment” on page 51.

Sample configuration: After you configure SF Manager in highavailability environmentThe following is an example of SF Manager configuration after you configure itin high availability environment:

include "types.cf"

cluster suse_cmsha_dr (

UserNames = { admin = IppJ }

Administrators = { admin }

)

system New York (

)

system Washington (

)

group SFM_Services (

SystemList = { New York = 0, Washington = 1 }

AutoStartList = { New York }

)

Application SFM_Services_DB (

User = root

StartProgram = "/opt/VRTSsfmcs/config/vcs/db/online"


StopProgram = "/opt/VRTSsfmcs/config/vcs/db/offline"

MonitorProgram = "/opt/VRTSsfmcs/config/vcs/db/monitor"

)

Application SFM_Services_SECD (

User = root

StartProgram = "/opt/VRTSsfmcs/config/vcs/secd/online.sh"

StopProgram = "/opt/VRTSsfmcs/config/vcs/secd/offline.sh"

CleanProgram = "/opt/VRTSsfmcs/config/vcs/secd/clean.sh"

MonitorProgram = "/opt/VRTSsfmcs/config/vcs/secd/monitor.sh"

)

Application SFM_Services_WEB (

User = root

StartProgram = "/opt/VRTSsfmcs/config/vcs/gui/online.sh"

StopProgram = "/opt/VRTSsfmcs/config/vcs/gui/offline.sh"

CleanProgram = "/opt/VRTSsfmcs/config/vcs/gui/clean.sh"

MonitorProgram = "/opt/VRTSsfmcs/config/vcs/gui/monitor.sh"

)

Application SFM_Services_XPRTLDD (

User = root

StartProgram = "/opt/VRTSsfmcs/config/vcs/xprtld_domain/online.sh"

StopProgram = "/opt/VRTSsfmcs/config/vcs/xprtld_domain/offline.sh"

MonitorProgram = "/opt/VRTSsfmcs/config/vcs/xprtld_domain/monitor.sh"

)

DiskGroup SFM_Services_DG (

Critical = 0

DiskGroup = hadg

)

IP SFM_Services_IP (

Critical = 0

Device @New York = eth0

Device @Washington = eth2

Address = "IP address"

)

Mount SFM_Services_Mount (

Critical = 0

MountPoint = "/hafs"

BlockDevice = "/dev/vx/dsk/hadg/havol"


52

FSType = vxfs

FsckOpt = "-n"

)

NIC SFM_Services_NIC (

Critical = 0

Device @New York = eth0

Device @Washington = eth2

)

Volume SFM_Services_VOL (

Critical = 0

DiskGroup = hadg

Volume = havol

)

SFM_Services_DB requires SFM_Services_Mount

SFM_Services_DG requires SFM_Services_IP

SFM_Services_IP requires SFM_Services_NIC

SFM_Services_Mount requires SFM_Services_VOL

SFM_Services_SECD requires SFM_Services_DB

SFM_Services_VOL requires SFM_Services_DG

SFM_Services_WEB requires SFM_Services_SECD

SFM_Services_XPRTLDD requires SFM_Services_DB


//

// group SFM_Services

// {

// Application SFM_Services_WEB

// {

// Application SFM_Services_SECD

// {

// Application SFM_Services_DB

// {

// Mount SFM_Services_Mount

// {


// {


// {



// {

// NIC SFM_Services_NIC

// }

// }

// }

// }

// }

// }

// }

// Application SFM_Services_XPRTLDD

// {

// Application SFM_Services_DB

// {

// Mount SFM_Services_Mount

// {


// {


// {


// {

// NIC SFM_Services_NIC

// }

// }

// }

// }

// }

// }

// }

group SFM_Xprtld (

SystemList = { New York = 0, Washington = 1 }

Parallel = 1

AutoStartList = { New York, Washington }

)

Application SFM_Services_XPRTLDS (

User = root

StartProgram = "/opt/VRTSsfmcs/config/vcs/xprtld_standalone/online.sh"

StopProgram = "/opt/VRTSsfmcs/config/vcs/xprtld_standalone/offline.sh"

MonitorProgram = "/opt/VRTSsfmcs/config/vcs/xprtld_standalone/monitor.sh"

)


54


//

// group SFM_Xprtld

// {

// Application SFM_Services_XPRTLDS

// }

See “Sample configuration: After you create the base service groups(SFM_Services)” on page 49.

About configuring SF Manager in high availability environmentAdded the followingnote in theAbout configuring SFManager in high availabilityenvironment section:

Windows-based Management Server does not support configuring SF Managerin high availability environment.

Prerequisites for configuring SF Manager in the high availabilityenvironment

The following prerequisite in this section is modified:

■ Youmust specify the database location. Youmust not use the database locationthat you want to use for the high availability configuration.You can either use the default database location /var/opt/VTRSsfmcs/db orspecify another location.

This should read:

■ You must specify the database location.You can either use the default database location /var/opt/VTRSsfmcs/db orspecify another location. If you specify the location other than the defaultdatabase location, you must make sure that it is not part of the shared filesystem that is used for failover. Later, the SF Manager HA script moves thedatabase to the shared file system.

Configuring a new SF Manager installation in high availabilityenvironment

In the To create the base service groups in VCS to ensure failover procedure,updated the table that lists the details about the base service groups:


The updated table should read:

Name of NIC.

In this procedure, we use the following:

■ eth0 as NIC for Linux ManagementServer.

■ hme0 as NIC for Solaris ManagementServer.

Resource types:

■ NIC

■ MultiNIC (On Solaris platform,MultiNICA)

■ MultiNICB

■ Proxy

Resource names:

■ SFM_Services_NIC

■ SFM_Services_MultiNIC

■ SFM_Services_MultiNICB

■ SFM_Services_Proxy

Original IP Address of NIC card.

Name of NIC. In this procedure, we use eth0as NIC.

Resource types:

■ IP

■ IPMultiNIC

■ IPMultiNICB

Resource names:

■ SFM_Services_IP

■ SFM_Services_IPMultiNIC

■ SFM_Services_IPMultiNICB (On Solarisplatform, MultiNICA)

Disk group that is specified for failover.Resource type:

■ DiskGroup

Resource name:

■ SFM_Services_DiskGroup

Disk group that is specified for failover.

Volume that is specified for failover.

Resource type:

■ Volume

Resource name:

■ SFM_Services_Volume


56

Mount Point name of the File System that isspecified for failover.

Complete path of the storage device that isspecified for failover.

Type of File System that is specified forfailover.

File check option (fsckpt = -n or -y)

Resource type:

■ Mount

Resource name:

■ SFM_Services_Mount

Log file locationsThe following directory name of the Windows log file locations in the Log filelocations section is incorrect:

%ALLUSERSPFOFILE%\

This should read:

%ALLUSERSPROFILE%\

Addenda and errata for man pagesThis section contains errata and additional information pertaining toman pages.

As a workaround, you can refer to the PDF output in Appendix A, "Command andconfiguration file reference" in the Veritas Storage Foundation ManagerAdministrator's Guide for the correct output for all of the man pages (CLIs).

XdistcIn the NOTES section, added the following text:

Windows-based Management Server does not support the xdistc command.

57Documentation addenda and errataAddenda and errata for man pages

Documentation addenda and errataAddenda and errata for man pages

58

Getting help

This appendix includes the following topics:

■ Using the product documentation

■ Displaying online help

■ Understanding how to troubleshoot SF Manager

■ Contacting Symantec

Using the product documentationThe following guides provide information about Storage Foundation Manager:

■ Veritas Storage Foundation Manager Administrator's Guide

■ Veritas Storage Foundation Manager Getting Started Guide

■ Veritas Storage Foundation Manager Installation Guide

For complete host operating system and system resource specifications, as wellas any known limitations or issues in this release, see the Veritas StorageFoundation Manager Release Notes.

Commenting on product documentationSubmit comments about theproductdocumentation to the followingemail address:

[email protected]

Please include the following information with your documentation comments:

■ The title and product version of the guide you are commenting on

■ The topic (if relevant) you are commenting on

■ Your comment

BAppendix

mailto:[email protected]

■ Your name

Displaying online helpSF Manager provides online help as well as UNIX manual pages.

To display online help

◆ Do one of the following:

■ In the Console, click the appropriate Help link or menu item.

■ In any dialog window, click the Help button.

On UNIX systems, you can use manual pages to find reference and usageinformation about product-specific commands.Whenyou install the product, thepkgadd command installs the nroff-tagged manual pages in the appropriatedirectories under /opt/VRTS/man. However, the install does not update thewindexdatabase.

To ensure that new manual pages display correctly, update your:

■ MANPATH environment variable to point to /opt/VRTS/man

■ windex database

Refer to thecatman(1M)manual page formore informationaboutupdatingwindex.

Understanding how to troubleshoot SF ManagerIf an issue arises while you are using SF Manager, you can contact SymantecTechnical Support or check other resources.

Error messagesIf you encounter a product error message, record the exact error message text.When contacting Symantec Technical Support, either by telephone or by visitingthe Veritas Technical Support Web site, be sure to provide this information.Symantec Technical Support will use the message text or number to determinewhether TechNotes or other information are available.

Other troubleshooting stepsIf an issue arises while you are using SF Manager, look at these resources:

■ Check the TechNotes and other resources on the Symantec Support Web site:http://www.symantec.com/enterprise/support/assistance_care.jsp

Getting helpDisplaying online help

60

http://www.symantec.com/enterprise/support/assistance_care.jsp

Contacting SymantecYou can contact Symantec on the Web, by email, or by telephone.

Using the support Web siteFor technical assistance with any Symantec product, visit the Symantec SupportWeb site:


From there you can:

■ Contact the Symantec Support staff and post questions to them

■ Get the latest software patches, upgrades, and utilities

■ View updated hardware and software compatibility lists

■ View Frequently Asked Questions (FAQ) pages for the products you are using

■ Search the knowledge base for answers to technical support questions

■ Receive automatic notice of product updates

■ Find out about training in the Storage Foundation products

■ Read current white papers related to the Storage Foundation products

Subscribing to email notification serviceSubscribe to the Symantec Email notification service to be informed of softwarealerts, newly published documentation, Beta programs, and other services.


Select a product and click E-mail Support at the bottomof the page. Your customerprofile ensures that you receive the latest Symantec technical informationpertaining to your specific interests.

Accessing telephone supportTelephone support is availablewith a valid support contract. To contact Symantecfor technical support, dial the appropriate phone number listed on the SupportGuide included in the product box and have your product license informationready for quick navigation to the proper support group.

61Getting helpContacting Symantec



Obtaining support by emailLicensed customers can use the following email address to obtain help withtechnical questions:

[email protected]

To obtain software updates by email, send your requests to the following emailaddress:

[email protected]

Obtaining license informationTo obtain license information, contact Symantec in one of the following ways:

■ U.S. and Canada telephone: 1-800-634-4747 option 3

■ Worldwide fax: +1-650-527-0952

■ Email: [email protected]

Purchasing productsFor help with purchasing Symantec products, visit the Symantec Web site:


You can also contact a Symantec product representative by email at the followingaddress:

[email protected]

To speak with a Symantec product representative by telephone, customers in theU.S. and Canada can call 1-800-327-2232.

Providing feedback about the documentationYour feedback on product documentation is important to us. Send suggestionsfor improvements and reports on errors or omissions to:

[email protected]

Include the following:

■ Title

■ Documentation version (located on the reverse of the title page)

■ Chapter and section titles of the text

Our goal is to ensure customer satisfaction by providing effective, qualitydocumentation.

Getting helpContacting Symantec

62


mailto:[email protected]

veritasstoragefoundation manager release notes release notes ......

Documents