veritasstoragefoundation manager release notes · veritasstoragefoundation™ manager release notes...

Veritas Storage Foundation™Manager Release Notes

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

1.1.1

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.

Documentation version 1.1.1.0

Legal NoticeCopyright © 2008 Symantec Corporation. All rights reserved.

Symantec, the Symantec logo, Veritas, CommandCentral, NetBackup, SANPoint, SANPointControl, Storage Foundation, and Veritas Storage Foundation are trademarks or registeredtrademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Othernames may be trademarks 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 ANDWARRANTIES, INCLUDING ANY IMPLIEDWARRANTY 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 CONNECTIONWITH THE FURNISHING,PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINEDIN THIS DOCUMENTATION IS SUBJECT TO CHANGEWITHOUT NOTICE.

The Licensed Software andDocumentation are deemed to be commercial computer softwareas defined in FAR12.212 and subject to restricted rights as defined in FARSection 52.227-19"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights inCommercial Computer Software or Commercial Computer Software Documentation", asapplicable, and any successor regulations.

Symantec Corporation20330 Stevens Creek Blvd.Cupertino, CA 95014

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 the problemoccurred, 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 SF Manager .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13SF Manager Installation Options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Veritas Provider Access Layer agents ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter 2 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Operating system requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Operating system updates required .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Third-party required libraries ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Veritas Array Support Library (ASL) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1932-bit SNIA Common HBA API .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

System resource requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Supported hardware .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21SF Manager Web browser requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

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

Compatibility between versions of SF Manager .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Installation and configuration limitations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Installation steps for coexistence with Storage Foundation5.0 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

No coexistence with Storage Foundation 4.x ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Remote Authentication Broker must have Symantec Private

Branch Exchange (PBX) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Limited information available for SCSI HBAs in SF Manager

Console (932251/932270) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Patch version not discovered correctly for upgraded

packages .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25SF Manager does not discover HDS RAID600 enclosure .... . . . . . . . . . . . . . 25SF Manager does not discover EMC DMX-3 enclosure .... . . . . . . . . . . . . . . . 25Management Server host name cannot exceed sixteen characters

(1056296) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Contents

Incremental backup and restore procedures are notsupported .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

SF Manager does not discover a X64 Sun SE3510 array(1033610) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

No coexistence with Storage Foundation products that useDBED .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

SF Manager Add-ons limitations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26DMP Add-on: Unsupported managed hosts versions

(1034396) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Volume migration not supported for volumes under CVM disk

groups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Considerations for legacy managed hosts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Graphical user interface issues .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

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

(1027514) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Email report delivers the subject line incorrectly when entered

in Japanese .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

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

Install, uninstall, and upgrade issues .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29SF Manager must be installed in /opt (579111) ... . . . . . . . . . . . . . . . . . . . . . . . . . 29Authentication Service update on cluster cannot be reversed by

uninstall (609644) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Permissions on the /etc directory change during product

installation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Install SF Manager before local AB (765606) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Error during uninstall of SF 4.x managed host on UNIX

(1053093) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Directory update required for manual upgrade (764414) ... . . . . . . . . . . . . . 31WebGUI must be running when installing SF Manager on a

CommandCentral Storage Management Server (797344) ... . . . . . . 31Unable to uninstall rpm's when uninstallsfms script is run .... . . . . . . . . 31Incorrect version ofmanagedhost installs on 4.x SolarisOpteron

host (1061867) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Managed host information incorrect after upgrade

(1036861,1045676) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334.x Solaris managed host not working properly after upgrade to

Storage Foundation 5.0 (1073898) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Contents8

Unable to discover host after installing a CommandCentralStorage 5.0 managed host with array management(1080872) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

SF Manager configuration does not occur during ManagementServer installations on multiple hosts (1288698) ... . . . . . . . . . . . . . . . . . 34

SF Manager Web Console fails when SF Manager 1.1.1 andAuthentication Service 4.4 are installed on a single host ... . . . . . . 35

LDAPauthentication is not available after upgrade toSFManager1.1.1 ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

SFManagerhangswhenSFManagerAdd-ons are simultaneouslyinstalled .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Storage Foundation 4.x hostmanagement installation fails withmissing Perl package error on HP-UX 11.23 .... . . . . . . . . . . . . . . . . . . . . . . 36

Creating a clustered file system fails on HP-UX (1227276) ... . . . . . . . . . . 36When you uninstall SF Manager 1.1.1 managed host a Perl

warning message is displayed .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37SFManager packages do not get uninstalled on a host that have

been upgraded to SF Manager 1.1.1 ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Storage Manager agent is displayed in the joined_agents list ... . . . . . . . 38Core dump occurs while upgrading SF Manager Management

Server from version 1.1 to version 1.1.1 on a Solaris host(1440515) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

SFManagerHAsetup fails if Virtual IP is configured to a differenthost (1448221) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Add-ons fail to uninstall when SF Manager is upgraded fromversion 1.1 to version 1.1.1 (1447137) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Managed host and migration issues .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Error thrown while migrating host from standalone mode to

centrally managed mode (1057195) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Managed Host faulted in SF Manager Console after

CommandCentral Storage 5.0 install (1091038) ... . . . . . . . . . . . . . . . . . . . 39Console display issues .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Column sorting results in old data being displayed (595193,599053) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Unexpected results when sorting in the disks view of a shareddisk group (619104) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

CVM state not displayed for clusters (595876) ... . . . . . . . . . . . . . . . . . . . . . . . . . . 41Navigation path disrupted when refreshing multiple windows

(604681) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Empty application groups not displayed (608991) ... . . . . . . . . . . . . . . . . . . . . . 42Administer status shows incorrectly for faulted disk group

(618005) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Zero value displayed for Behind By (637563) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

9Contents

Disk Detail view does not accurately reflect volume information(645105) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Console displays incorrect volume information (645786, 645779,645768, 645757, 646422) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

SF Manager Console does not display the replication status(700823) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Report File Placements Results not displayed when locale isJapanese (898615) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

WebGUI monitoring shows status as RUNNING and does notchange to FINISHED (1061587) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Collapse of tree control in theDMPorVolumeMigration add-onsmay trigger "Unresponsive Script" dialog (1057360) ... . . . . . . . . . . . . 44

Report engine pie chart for "Report File Placement Results" donot display (898685) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Group names and descriptions truncated in Japanese version(930599) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Localized content displays unreadable text (1130097, 1117908,1117905, 1117858) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Cannot loadadd-on fromInternetExplorer 6.0 sp2using Japaneselanguage (1109166) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

SFW displays obsolete iSCSI host information in the Console(1178880) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

SF Manager Console displays incorrect status of ServiceGroups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Veritas Volume Replicator extensions and plug-ins are notdisplayed in the Web Console (1435804) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Managedhost that has beenmigrated to a differentManagementServer appears uninstalled (1447133) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Virtual host name does not get discovered on Solaris(1439672) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Monitoring issues .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Service groups are not displayed for managed hosts in a

cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Resource configuration issues .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

HBAand array discovery issues onOpteron-based Linux systems(1068470) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Symantec Database Server on a Management Server host doesnot restart after a crash on Linux (1068674) ... . . . . . . . . . . . . . . . . . . . . . . . 48

High availability configuration issues .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Add-ons can be installed or uninstalled onSlave nodes even after

SF Manager for HA is unconfigured (1447032) ... . . . . . . . . . . . . . . . . . . . . 49Add-on status of Slave node shown on Master node even after

SF Manager for HA is unconfigured .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Contents10

Database and add-ons related information is lost after youunconfigure HA .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Other issues .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49vxdompackage CLI does not support the "remove" option on

Linux platforms (1013808) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50CCG outage on Linux legacy managed host (619081) ... . . . . . . . . . . . . . . . . . . 50Login page results in blank page (stalls) (1062707) ... . . . . . . . . . . . . . . . . . . . . 50Man pages cannot be accessed when SF Manager/LMH is

uninstalled on a UNIX legacy managed host (792965) ... . . . . . . . . . . 50End Checkpoints shows "There is no started Checkpoint"

(641926) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Dual path status for disk is always shown as enabled

(1059390) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51VEA Java Console does not launch after SF Manager 1.1.1

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

The copyright year for the VRTSob package is erroneouslydisplayed as 2007 on Linux (1437325) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Chapter 5 Documentation addenda and errata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Addenda and errata for man pages .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53dbbackup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53gridcli .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54veaconfig ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54veainfo .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54vxdbms_start_db.pl ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54vxdeploy .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54vxdompackage .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55vxfinger ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55vxpal ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Veritas Storage Foundation Manager Administrator's Guideerrata .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Chapter 6 Accessibility features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Navigating the SF Manager Console ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Accessibility features in dialog boxes .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Appendix A Getting help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Using the product documentation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Commenting on product documentation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Displaying online help .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

11Contents

Understanding how to troubleshoot SF Manager .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Error messages .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Other troubleshooting steps .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

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

Contents12

Overview of this release

This chapter includes the following topics:

■ Introduction to SF Manager

■ SF Manager Installation Options

■ Veritas Provider Access Layer agents

Introduction to SF 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.SFManager also provides prepackaged add-ons to handle complex processes likemanaging DMPs.

A centrally managed deployment consists of the Storage Foundation Managerand one or more managed hosts.

Figure 1-1 provides an overview of the SF Manager components.

1Chapter

Figure 1-1 SF Manager architecture (high-level)

AuthenticationService HostSF Management Server Host

Web Server

DatabaseServer

Management Server

Web Browser

AuthenticationBroker

agent

SFMManaged Host(SF 5.0/VxPAL)

SFMManaged Host(SF 4.x/VEA 3.2)(UNIX-Linux Only)

agent

The Management Server collects and manages information pertaining to theStorage Foundation products on the managed hosts. In a centrally manageddeployment, users can connect to the Management Server via a Web browser tomanage a heterogeneous environment of Storage Foundation 5.0 and legacy (4.x)hosts.

Existing Storage Foundation software products, such asVeritasVolumeManager,Veritas File System, Veritas Volume Replicator, and infrastructure components

Overview of this releaseIntroduction to SF Manager

14

that are running on legacy hosts can participate in the centrally administereddeployment.

SF Manager provides the following benefits:

■ Collect and centralize information: The Management Server collectsinformation about the state of storage resources deployed throughout thenetwork. You can generate various reports, analyze performance, and studystorage utilization.

■ Single Sign-on: You can log on to theManagement Server andview 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 monitored by the Symantec ProductAuthentication Service.

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.

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, an external host hosting the Symantec ProductAuthenticationService,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 legacy (4.x) hosts.

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

Veritas Provider Access Layer agentsA number of VxPAL agents ship with SF Manager.

15Overview of this releaseSF Manager Installation Options

Table 1-1 provides an overview of these agents:

Table 1-1 Several VxPAL agents that ship with SF Manager

DescriptionAgent name

Runs on the Management Server and provides the end-user with theability to create rules triggered by VxPAL alerts. (Also known as theRule Manager.)

actionagent

Runs on managed hosts and performs Oracle and DB2 databasediscovery and management.

DBEDAgent

Runs on the Management Server and is a central coordinatorresponsible for distribution of requests and collecting results.

gridcentral

Runs onmanaged hosts and is responsible for file I/O and forking (orspawning) commands.

gridnode

Runs on managed hosts and provides management and monitoringfor Storage Foundation products.

StorageAgent

Runs on the Management Server and coordinates the managementand monitoring of StorageAgents in a domain.

StorageManager

Runs on managed hosts and used by DBEDAgent to perform deepmapping (mapping LUNs to their physical disks).

VailAgent

Overview of this releaseVeritas Provider Access Layer agents

16

System requirements


■ Operating system requirements

■ Third-party required libraries

■ System resource requirements

■ Supported hardware

■ SF Manager Web browser requirements

Operating system requirementsTable 2-1 provides an overview of SF Manager operating system requirements:

Table 2-1 SF Manager operating system requirements

NotesOperating Systems supportedComponent

OnRedHatEnterpriseLinux4.0, theManagementServer is supported on x86 64-bit platforms only;no support for IA64 or x86 32-bit platforms.

Red Hat Enterprise Linux 4.0

Solaris 8, 9, 10 SPARC

SUSE Linux Enterprise Server 9 Service Pack 3

ManagementServer

2Chapter

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

NotesOperating Systems supportedComponent

OnRedHat Enterprise Linux 4.0 and SUSE LinuxEnterprise Server 9, Storage Foundation 5.0 issupported only on 64-bit Xeon and Opteron; nosupport for Itanium.

On RedHat Enterprise Linux 4.0 and SUSE LinuxEnterprise Server 9, Storage Foundation 4.1 issupported on the following platforms: x86; Xeon(32- and 64-bit); Opteron (64-bit). No support forItanium.OnRedHatEnterprise Linux3.0, StorageFoundation 4.0 is supported only on x86 (32-bit).

AIX 5.2, 5.3

HP-UX 11.11 (only for Storage Foundation 3.5hosts), 11.23, 11.31

Red Hat Enterprise Linux 3.0, 4.0

Red Hat Enterprise Linux 5.0 Update 2 (only forStorage Foundation 5.0 MP3 hosts)

Solaris 7, 8, 9, 10 SPARC

Solaris 10 Opteron

SUSE Linux Enterprise Server 9

SUSELinuxEnterprise Server 10 (only for StorageFoundation 5.0 MP3 hosts)

Managedhosts

For the most complete, up-to-date platform support documentation for StorageFoundation (UNIX), visit the Symantec Technical Support web site:

www.symantec.com/techsupport

Operating system updates requiredOperating system updates are required on some platforms to run SF Manager.

■ HP-UX 11.23—PHSS_31855 and PHSS_32228

■ HP-UX 11.23 Itanium—PHSS_35528

■ HP-UX 11.31 Itanium—PHSS_36311

■ Solaris—SunWorkshop Compilers Bundled libC (SUNWlibC) (sparc), version5.10,REV=2004.11.22

■ Solaris 10—120182-02

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

System requirementsOperating system requirements

18

http://www.symantec.com/techsupport

For themost complete, up-to-date documentationabout requiredoperating systemupdates, visit the Symantec Technical Support web site for the latest StorageFoundation (UNIX) Release Notes.

Increasing semaphore limits on SolarisThe Veritas Provider Access Layer (VxPAL) and the Veritas EnterpriseAdministratorService requiremoreoperating systemsemaphores thanareusuallyset by default on Solaris. If you do not increase the semaphore limit, SF Managermay fail to operate properly.

To increase semaphore limits on Solaris

1 Open a UNIX console and log in as root on the target host.

2 Using a text editor, open: /etc/system

3 Locate a line similar to the following (if the line is not present, add it):

set semsys:seminfo_semmni=0x5

4 Edit the file to increase the semaphore limits. For example: set sminfo_semmnito 0x10.

5 Save the file and reboot the host.

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

■ Veritas Array Support Library (ASL)

■ 32-bit SNIA Common HBA API

Veritas Array Support Library (ASL)SFManager requires that the Veritas Array Support library be installed on legacymanaged hosts (Storage Foundation 4.x centrally-managed hosts).

For more information, see:

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

32-bit SNIA Common HBA APIFor 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 managed hosts running HBA controllers.

19System requirementsThird-party required libraries


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.

Table 2-2 provides more information about the 32-bit SNIA Common HBA API:

Table 2-2 Notes for SNIA Common HBA API

NotesOperatingSystem

The SNIA Common HBA API is not required on AIX.AIX

For HP OEMHBA cards, the Common HBA API is installed by defaulton HP-UX.

HP-UX

OnSolaris 9 and10, the SNIACommonHBAAPI is installed by default;however, the SUNWsan package is required.

The SNIA Common HBA API is installed as part of Solaris only forSUN OEM HBA cards. For other HBA cards, you must explicitlydownload them from your HBA vendor.

Solaris

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

To verify that the 32-bit SNIA Common HBA API is installed

1 Open a console and log on to the managed host running an HBA controller.

2 Type the following command:

cat /etc/hba.conf

hba.conf should show an entry for each type of HBA controller that is installed.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 required by SF Manager are in additionto the resources already consumed by other software on the host.

Table 2-3 provides memory and disk space specifications for SF Managercomponents.

System requirementsSystem resource requirements

20

Table 2-3 System resources SF Managerhosts

DiskSpaceRequiredMemory RequiredCPU RequiredComponent

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

Database only: 6GB(for 100 hosts)

a. Requires additionalswap space of at least8G–16G.

2GB (Less than 50managed hosts)

4GB (Over 50managed hosts)

Dual processor (Lessthan 50 managedhosts)

Quad processor (Over50 managed hosts)

ManagementServera

1GB (in/var/opt fordiscovery state files)

See StorageFoundationdocumentation


Managed host

50MB on /var, 50MBon /opt



SF 4.xmanagedhost

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/308269.htm

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


SF Manager Web browser requirementsYou can run the Storage Foundation Manager Console in a number of standardweb browsers.

Table 2-4 outlines browsers that are supported in this release:

21System requirementsSupported hardware

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


Table 2-4 Web browsers and their supported platforms

NetscapeNavigator 7.2(or later)

Mozilla 1.6 (orlater)

InternetExplorer 6.0(or later)

Firefox 1.0.7(or later)

OperatingSystem

XAIX

XHP-UX

XXXRed Hat

XSolaris

XXXSuSE

XXX aXWindows

a.For Internet Explorer 6 service pack 1, patch Q832894 must be applied.

Your browser must support either JScript 5.5 (provided with Microsoft InternetExplorer 6 or later) or JavaScript 1.2 (provided with Netscape Navigator 7.x).Additionally, for Internet Explorer, Secure Sockets Layer (SSL) 3.0 ActiveXscripting must be enabled.

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 Server towhichyouwill connect.Note that pop-upblocking is enabledbydefault inNetscape7.2.

Note: For Internet Explorer 6.0 on Windows 2003 (Server and Advanced Server),set the default Intranet zone security level to MEDIUM or lower.

System requirementsSF Manager Web browser requirements

22

Software limitations


■ Compatibility between versions of SF Manager

■ Installation and configuration limitations

■ SF Manager Add-ons limitations

■ Considerations for legacy managed hosts

■ Graphical user interface issues

Compatibility between versions of SF ManagerA version 1.0MP1Management Server is required formanaging version 1.0MP1legacy managed hosts, or 5.0 MP1 managed hosts. However, the 1.0 MP1Management Server can interact with managed hosts running both version 1.0and version 1.0 MP1.

When upgrading your system, therefore, we recommend that you upgrade theManagement Server first and then upgrade the managed hosts.

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

Installation steps for coexistence with Storage Foundation 5.0If you intend to run SF Manager on the same host with Storage Foundation 5.0,install the Storage Foundation code first.

3Chapter

After both products are installed, all agents except the Action Agent and gridagent must be registered manually with the local SF Manager.

To determine the list of installed agents, run the following command:

/opt/VRTSobc/pal33/bin/vxregctl /etc/vx/isis/Registry

enumkey Software/VERITAS/VRTSobc/pal33/Agents | grep -v

_defaults

To register an agent, run the following command:

/opt/VRTSobc/pal33/install/cfgsecurity.sh -a $agent -h $fqdn

-d $dc -p $pwd -b $ab

Where:

$agent is the name of the agent to be registered

$fqdn is the local fully qaulified domain name for the host

$dc is the same as $fqhn

$pwd is the vea_agent account password.

$ab is the authentication broker (AB) used by the SF Manager. The AB name canbe found in the file /etc/default/csf_resolv.conf.

No coexistence with Storage Foundation 4.xDo not install SF Manager on a host where Storage Foundation 4.x is installed.

Remote Authentication Broker must have Symantec Private BranchExchange (PBX)

The Management Server should be not be configured to use a remoteAuthentication Broker (AB) on which Symantec Private Branch Exchange (PBX)is not installed.

For example, the Management Server should share an AB with another Veritasproduct, such as NetBackup, only when the other product's AB has PBX installed.

Configure a separate AB that points to the existing root broker, and install PBXon the new AB.

Software limitationsInstallation and configuration limitations

24

Limited information available for SCSI HBAs in SF Manager Console(932251/932270)

Due to a limitation in this release of the product, the SF Manager Console doesnot display driver, firmware, vendor, or WWN information for SCSI HBAs.

No workaround is available at this time.

Patch version not discovered correctly for upgraded packagesAfter a patch has been applied to a package, the SF Manager Web Console doesnot display the new version number.

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.

Management Server host name cannot exceed sixteen characters(1056296)

Due to a limitation in the product's Sybase ASA database, the host name of theManagement Server host cannot exceed sixteen characters. If you install theManagement Server on a host whose host name exceeds sixteen characters, theSF Manager console (GUI) will not display.

There is no workaround for this problem at this time.

Incremental backup and restore procedures are not supportedSFM1.1.1 doesnot 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.

25Software limitationsInstallation and configuration limitations

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.

No coexistence with Storage Foundation products that use DBEDDonot install SFManager on ahostwhere any of the followingStorage Foundationproducts that use the Veritas Database Edition (DBED) are installed:

■ Veritas Storage Foundation for Oracle

■ Veritas Storage Foundation for DB2

■ Veritas Storage Foundation for Sybase

■ Veritas Storage Foundation for Oracle RAC

SF Manager Add-ons limitationsThe following notes cover limitations pertaining to the SF Manager Add-ons.

DMP Add-on: 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-UXmanaged 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 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.

Considerations for legacy managed hostsKeep these points inmindwhen centrallymanaging Storage Foundation 4.x hosts:

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

Software limitationsSF Manager Add-ons limitations

26

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

Storage usage displays as zero for non-Veritas file typesStorage Utilization shows file system usage is zero for: NTFS, FAT, FAT32, andRAW. 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.

Email report delivers the subject line incorrectly when entered inJapanese

When you attempt to email a report in the Japanese version of SF Manager onSolaris, the email's subject line will display garbled characters unless theManagement Server host's locale is to set to ja_JP.UTF-8. EUC and PCK are notsupported. For information about setting your locale, consult your Solarisdocumentation.

27Software limitationsGraphical user interface issues

Software limitationsGraphical user interface issues

28

Known issues


■ Install, uninstall, and upgrade issues

■ Managed host and migration issues

■ Console display issues

■ Monitoring issues

■ Resource configuration issues

■ High availability configuration issues

■ Other issues

Install, uninstall, and upgrade issuesThe following issues relate to SF Manager installation and uninstallation.

SF Manager must be installed in /opt (579111)In UNIX, the SFManager program codemust be installed in the /opt partition. If/opt contains insufficient space or does not exist, SFManager cannot be installed.

WorkaroundEnsure that /opt exists and has sufficient disk space.

See “System resource requirements” on page 20.

4Chapter

Authentication Service update on cluster cannot be reversed byuninstall (609644)

In UNIX, when Veritas Storage Foundation 4.x Host Management is installed ona Veritas Cluster Server (VCS) 4.x host in secure mode, the installation processwill update the Authentication Service (VRTSat). If you subsequently uninstallVeritas Storage Foundation 4.x Host Management on this host, it is not possibleto revert to the previous (4.x) version of the Authentication Service shipped withVCS 4.x.

SF Manager 1.1.1 does not require a clustered configuration. However, if you usea clustered configuration,we strongly recommend that youupgradeVCS toversion5.0 before installing SF Manager on the host.

Permissions on the /etc directory change during product installationBecause of a Solaris issue in the pkgadd command, the permissions on the /etcdirectory may change during the installation of Symantec product packages.Check after an installation procedure to see if this occurred. Use the chmodcommand to reset the permissions.

Install SF Manager before local AB (765606)If you intend to run SF Manager on the same host as the Authentication Broker(AB),we strongly recommend that you install theSFManager codebefore installingthe AB. This is because the AB installation requires that the VRTSpbx componentbe installed already.

It is possible to install and configure theABusing the Security Server Installationoptionon theSFManager installationmedium.However, this is not recommended,and the option is disabled for the beta release.

Error during uninstall of SF 4.x managed host on UNIX (1053093)When you uninstall a SF 4.x managed host on UNIX, the following error mayoccur:

Undefined subroutine &main::_com_cpi called at ./uninstall_lmh line

13

WorkaroundVerify that SF4.x VRTSperl and VRTScpi options are installed on the managedhost.

Known issuesInstall, uninstall, and upgrade issues

30

Directory update required for manual upgrade (764414)If you upgrade manually to SF Manager 1.0 MP1, it is necessary to update somedirectories using the command line. Navigate to the root directory and executethe following command to upgrade VRTScsdoc, VRTSaa, VRTScs and VRTSmh.

rpm --nodeps --nopostun VRTScsdoc*.rpm VRTSaa*.rpm

VRTScs*.rpm VRTSmh*.rpm

WebGUI must be running when installing SF Manager on aCommandCentral Storage Management Server (797344)

On a Solaris host that is being used as a CommandCentral Storage ManagementServer, the installation of SF Manager will fail unless the WebGUI is running.

To ensure that the WebGUI is running, execute the following sequence ofcommands before installing SF Manager:

cd /opt/VRTSweb/bin

./webgui stop force

./webgui restart

Unable to uninstall rpm's when uninstallsfms script is runThe following issues relate to running the uninstallsfms script after ugradingto SFM 1.1.1.

Problems removingpackageswhile uninstallingSFM1.1.1 afterupgrade from SFMS 1.0 (1006737)When the user uninstalls SFM1.1.1 after upgrading fromSFMS1.0, the followingSFMS1.0packagesarenot automatically removed fromthe system.Thesepackagesare theSYMClma,VRTSsmf,VRTSdcli,VRTSdsm,VRTSdcp,VRTSgcspr,VRTSat,VRTSpbxand VRTSicsco packages.

Workaround

You can manually remove the VRTSdsm, VRTSdcp and VRTSgcspr packages. Theremaining packages may still be in use and should be left on the system.

Potential problemswith packageswhile uninstalling SFM1.1.1after upgrade from SFMS 1.0 MP1 (1006737)When the user uninstalls SFM 1.1.1 after upgrading from SFMS 1.0 MP1, theVRTSdcli, VRTSdsm, VRTSdcp, and VRTSgcspr packages will be automatically

31Known issuesInstall, uninstall, and upgrade issues

removed during the upgrade. This may cause potential problems especially ifStorage Foundation is co-existing on the host because the VRTSdcli package ispart of current Storage Foundation installs.

The SFM 1.1.1 does not require the installation of the SYMClma and VRTSsmf

packages. If these packages are already installed on the system then they will notbe removed either.

Workaround

There is no workaround. All the necessary packages have already been removed.

Incorrect version of managed host installs on 4.x Solaris Opteron host(1061867)

If you attempt to install Storage Foundation Manager 4.x Host Management ona 4.x Solaris Opteron host, the install will succeed, but an incorrect version of amanaged host component (VRTSobc33) will be installed. This incorrect versionofVRTSobc33will prevent theOpteronmanagedhost fromperforming optimally,and you may experience unexpected results in SF Manager.

WorkaroundAfter you install Storage Foundation Manager 4.x Host Management on a 4.xSolaris Opteron host, install patch 125862-01.

To install patch 125862-01 on a Solaris Opteron managed host

1 On the host where you installed SF Manager, switch to the directory thatcontains the Solaris Opteron patches:

solaris-x86-64/legacy_managed_host/patches/

2 Copy 125862-01.tar.gz to a temporary directory on the 4.x Solaris Opteronhost.

3 On the 4.x Solaris Opteronhost, switch to the temporary directorywhere youcopied 125862-01.tar.gz and unzip the tar.gz file.

gunzip 125862-01.tar.gz

tar xvf 125862-01.tar

4 TheVxPAL processes should be stopped before installing the patch. View theVxPAL processes that are currently running.

ps -ef | grep vxpal


32

5 Stop each VxPAL process using the following command:

/opt/VRTSobc/pal33/bin/vxpal -a gridnode -c stop

6 Install the patch.

patchadd 125862-01

7 Start each VxPAL process that you stopped in step 5 using the followingcommand:

/opt/VRTSobc/pal33/bin/vxpal -a gridnode

Managedhost information incorrect after upgrade (1036861,1045676)After you upgrade theManagement Server from 1.0 to 1.1, information about thehost might not update properly in the Console. The host may be classified asuninstalled in the Console, or the product version may be reported incorrectly.

WorkaroundThe inconsistency will be corrected the next time theManagement Server is fullydiscovered. Instead ofwaiting for SFManager to discover theManagement Server,you can force SF Manager to discover the host. When you do this, the hostinformation will be updated in the Console.

To force SF Manager to discover the host:

1 On the Management Server, open an operating system console and log on asroot.

2 Change to the following directory:

/opt/VRTSmh/bin

3 Run the command:

./cmsf_ctl.pl --rescan

4.x Solarismanagedhost notworking properly after upgrade to StorageFoundation 5.0 (1073898)

If you upgrade a Storage Foundation 4.x Solaris managed host to StorageFoundation 5.0, the SFManagermanagedhost componentwill notwork properly.


WorkaroundBefore youupgrade thehost, youmust uninstall SFManager 4.x hostmanagementfrom thehost. After youuninstall 4.x hostmanagement, you canupgrade thehostto Storage Foundation 5.0 and add it back to the central management domain.

See the Veritas Storage Foundation Manager Installation Guide.

Unable to discover host after installing a CommandCentral Storage5.0 managed host with array management (1080872)

If you install aCommandCentral Storage5.0managedhostwitharraymanagementcapabilities on a Storage Foundation 5.0MP1 Linux or AIX host that is beingmanaged by SF Manager, SF Manager will not discover the host, because theDomain Controller, vxsvc no longer works.

This occurs because the CommandCentral Storage 5.0 installer updates a versionof a software package, VRTSobc33, that is incompatible with vxsvc. The softwarepackage update is required to run the managed host with array managementcapabilities.

If you want to install a CommandCentral Storage 5.0 managed host on a StorageFoundation 5.0MP1 Linux or AIX host that is being managed by SF Manager, donot install array management capabilities.

Formore information about installing amanagedhostwithout arraymanagementcapabilities, see the CommandCentral Storage Installation Guide.

SF Manager configuration does not occur during Management Serverinstallations on multiple hosts (1288698)

When you perform SFManagerManagement Server installations or upgrades onmultiple hosts, the hosts may have one of the following states:

■ SF Manager not installed

■ SF Manager 1.1 installed

Note:Management Server upgrade from SF Manager version 1.0 to version 1.1.1is not supported.

When hosts in different states are specified during installation or upgrade, SFManager configuration does not occur.


34

WorkaroundYoumust performManagement Server installation or upgrade separately for thehosts that have SF Manager installed, and those that do not have SF Managerinstalled. Also, for Management Server the hosts that have earlier versions of SFManager installed, perform the installation andupgrade separately for each earlierversion.

SF Manager Web Console fails when SF Manager 1.1.1 andAuthentication Service 4.4 are installed on a single host

Whenyou install SFManager 1.1.1 andSymantecProductAuthenticationService4.4 on a single host, SF Manager Web Console may fail to launch.

WorkaroundModify the /opt/VRTSweb/bin/vrtswebenv.sh file. Replace the line that beginswith CLASSPATH, with the following line:

CLASSPATH=${CLASSPATH}:${UUID_BIN}/UUIDWrapper.jar

Restart VRTSweb using the following command:

/opt/VRTSweb/bin/webgui restart

You can now launch the SF Manager Web Console.

LDAP authentication is not available after upgrade to SFManager 1.1.1After you upgrade to SF Manager 1.1.1, you cannot log on to SF Manager usingLDAP authentication.

WorkaroundRun the following command to configure SF Manager:

./opt/VRTS/install/installsfms -configure

You can now log on to SF Manager using LDAP authentication.

SF Manager hangs when SF Manager Add-ons are simultaneouslyinstalled

When you install the SF Manager Add-ons simultaneously, SF Manager hangs.


WorkaroundRun the following command to restart the SF Manager Web Console.

./opt/VRTScweb/sfmw restart

Launch the Web Console and log on to SF Manager.

Storage Foundation4.x hostmanagement installation failswithmissingPerl package error on HP-UX 11.23

When you install managed host code on a Storage Foundation 4.x host on HP-UX11.23, the installationmay fail if the Perl for Symantec (VRTSperl) package is notfound. A message is displayed that directs you to install the VRTSperl package.

WorkaroundYouhave to install the VRTSperlpackage before you install 4.x hostmanagement.

Run the following command to change the directory:

cd /ExtractDir/hpux/depot

where, ExtractDir is the path to the directory where you have extracted thedownloaded SF Manager zip file.

Run the following command to install the VRTSperl package:

swinstall -s $PWD VRTSperl

Run the SF Manager installer again to install 4.x host management.

Creating a clustered file system fails on HP-UX (1227276)On HP-UX, when you try to create a clustered file system in a shared disk groupusing SF Manager, the task fails with an error message that the volume cannotbe opened.

WorkaroundYou have to set the activation for the shared disk group before you create aclustered file system in it.

Run the following commands to set the activation:

# vxdg -g sharedg set activation=off

# vxdg -g sharedg set activation=sw


36

where, sharedg is the name of the shared disk group in which you want to createthe clustered file system.

You can now create the clustered file system in the shared disk group using SFManager.

When you uninstall SF Manager 1.1.1 managed host a Perl warningmessage is displayed

If you uninstall the SF Manager 1.1.1 managed host from Management Serverusing vxdompackage, the following Perl warning message is displayed:

/opt/VRTSmh/bin/vxvm- discovery.pl: not found

WorkaroundYou can ignore the message since the uninstall proceeds successfully.

SF Manager packages do not get uninstalled on a host that have beenupgraded to SF Manager 1.1.1

Whenyouuninstall SFManager 1.1.1 fromahost that is upgraded to version1.1.1from version 1.0, some of the SF Manager packages are not removed.

WorkaroundYoumustmanually uninstall any remaining rpms or packages after you uninstallSF Manager using the installer. However, this workaround is applicable only ifSF Manager is installed on the host.

Use one of the following commands to remove the remaining packages:

■ On Linux:rpm -e rpm_name

■ On Solaris:pkgrm package_name

Following are the rpms or packages that need to be manually removed:

■ On Linux:VRTSsmf, VRTSpbx, VRTSvdid, VRTSperl, VRTSicsco, VRTSatClient

■ On Solaris:VRTSat, VRTSsmf, VRTSpbx, VRTSvdid, VRTSperl, VRTSicsco


Storage Manager agent is displayed in the joined_agents listWhen you upgrade to SF Manager 1.1.1, the Storage Manager agent is displayedin the joined_agents list.

WorkaroundThis issue does not cause any problem in any functionality. The StorageManageragent is erroneously displayed in the command output.

Core dump occurs while upgrading SF Manager Management Serverfrom version 1.1 to version 1.1.1 on a Solaris host (1440515)

On a Solaris host, while upgrading SFManagerManagement Server from version1.1 to version 1.1.1, a core dump occurs.

WorkaroundThis issue does not cause any problem in any functionality.

SFManager HA setup fails if Virtual IP is configured to a different host(1448221)

SFManagerHA setup fails, if youuse the sameVirtual IP to configure SFManagerHAwhich is used to configure other host. The following errormessage is displayed:

Cluster setup in SFMS failed.

There is no workaround for this issue.

Add-ons fail to uninstall when SF Manager is upgraded from version1.1 to version 1.1.1 (1447137)

When you upgrade SF Manager from version 1.1 to version 1.1.1, you cannotuninstall the add-ons.

WorkaroundYou will need to manually set the add-ons store directory and force SF Managerto discover hosts before you uninstall the add-ons.


38

To set the add-ons store directory and force SF Manager to discover hosts

1 Set the store directory manually with the following command:

VRTScs_Home/bin/vxdeploy_setup.pl --storedir Store_dir_path

where, VRTScs_Home is the location of /opt/VRTScs/bin, and Store_dir_pathis the location of the add-ons store directory.

2 Force SF Manager to discover host with the following command:

VRTSmh_HOME/bin/cmsf_ctl.pl --rescan

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

Error thrown while migrating host from standalone mode to centrallymanaged mode (1057195)

While migrating host from standalone mode to centrally managed mode, thefollowing error is displayed.

Error: Information for VRTSmusfm was not found.

/opt/VRTSmusfm/bin/unsetup_catalog.sh:

/opt/VRTSmusfm/bin/unsetup_catalog.sh:

can not be found.

WorkaroundThere is no workaround.

Managed Host faulted in SF Manager Console after CommandCentralStorage 5.0 install (1091038)

If you install CommandCentral Storage5.0 onaStorageFoundation5.0MP1Solarishost that is being managed by SF Manager, the host will display as faulted in theConsole.

The host displays as faulted because the CommandCentral Storage 5.0 installerremoves a file (/etc/default/csf_resolv.conf) that is required by SFManagerto manage Storage Foundation 5.0MP1 hosts.

39Known issuesManaged host and migration issues

WorkaroundRun the installsf -configure command to create the csf_resolv.conf file onthe managed host.

To create the csf_resolv.conf file on the managed host

1 Open an operating system console and log in to theManagement Server hostas root.

2 At the command prompt, type the following command:

./installsf -configure hostname

where hostname is the fully qualified host name of the Management Server.

3 Verify that the csf_resolv.conf file was created.

By default, csf_resolv.conf, resides in:

/etc/default

4 Log in to the Console.

The host no longer displays as faulted.

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

Column sorting results in old data being displayed (595193, 599053)OnMicrosoft Internet Explorer 6.0, clicking columnheaders to sort data can resultin problems like the following:

■ Click a column header; recently-modified data in the column reverts to its oldvalue

■ Click another column header; data in the previous column reverts back to thenewer value

■ Click any column header; data no longer sorts in the correct order

Workaround1 In the Internet Explorer browser window, click Tools > Internet Options.

2 Select the General tab.

Known issuesConsole display issues

40

3 In the Temporary Internet Files section, click Settings.

4 Set Check for newer versions of stored pages to Every visit to the page.

Do not set this value to Automatically.

Unexpected results when sorting in the disks view of a shared diskgroup (619104)

When you sort on the Disk column within a shared disk groups disk view, itemswithin the column are not properly sorted.

WorkaroundThere is no workaround at this time.

CVM state not displayed for clusters (595876)In UNIX, SFManager version 1.1.1 displays the state of VCS clusters (for exampleRUNNING).However, it doesnot display theClusterVolumeManager (CVM) statefor these clusters (either ACTIVE or INACTIVE).

Workaround◆ To view the CVM state for a cluster, issue this command:

# /usr/sbin/vxdctl -c mode

The output typically will look like this (where hostname is the name of theCVMmaster node):

mode: enabled: cluster active - MASTER

master: hostname

Navigation path disruptedwhen refreshingmultiplewindows (604681)This problemcanoccurwhenyouareusing theConsole simultaneously inmultiplebrowser windows, and at least one of the windows is displaying a view accessedthrough theAdminister link. In this situation, the navigation path for thewindowaccessed through the Administer link can become disrupted when you use thebrowser's Refresh feature to refresh both windows. (The navigation path will bereplaced with the navigation path from the first window.)

41Known issuesConsole display issues

WorkaroundUse the browser's Back button to navigate to previously visited views.

Empty application groups not displayed (608991)If a user creates an application group and subsequently edits the group to removeall base objects, the group will not be included in:

■ Counts on the Dashboard and Inventory Summary views

■ Filters on the Application Groups view

Therefore, we recommend that you not create empty application groups (thosewith no base objects).

Administer status shows incorrectly for faulted disk group (618005)In UNIX, when you reach the object view for a faulted disk group by clickingthrough from a link in an application group's Faulted Bases table, the Administerstatus is incorrectly displayed as down (red icon) even when the managed host isworking properly. Clicking the Administer link to view the next level of detailswill work correctly.

When you reach the disk group's object view by navigating in any other way, theAdminister status icon is shown correctly.

Zero value displayed for Behind By (637563)In the Console on Windows, the Behind By column for replicated volumes showsa value of zero, even when there is a time lag between primary and secondaryvolumes.


Disk Detail view does not accurately reflect volume information(645105)

After you delete or add a volume on amanaged host, the SFManager informationshown in the disk detail view on the Volume tab does not update to reflect thecurrent information.


42

WorkaroundFollow the steps below to rescan the agentlet perl cmsf_drive.pl --family

SF.

1 Log into the Managed Host on which the volume was added or deleted.

2 From the command prompt, type set path=%program

files%\veritas\VRTSPerl\bin where%program files% represents theinstallation location of the Program Files directory.

3 Type the command perl cmsf_drive.pl --family SF to rescan and updatethe information on the SF Manager.

Console displays incorrect volume information (645786, 645779,645768, 645757, 646422)

The Console displays incorrect volume information.

WorkaroundUnder investigation. No workaround available at this time.

SF Manager Console does not display the replication status (700823)On the SF Manager Console, clicking the Application > Replication tab displaysblank fields instead of RDS views. Even when the secondary is lagging behind, novalue is displayed by the Behind by field.

WorkaroundCurrently, no workaround exists.

Report File Placements Results not displayed when locale is Japanese(898615)

After a file placement policy is created and enforced, the output for Report FilePlacement Results does not display when the locale on the Management Serverhost is Japanese. The message "Resource bundle is null" displays instead of theexpected pie charts.

WorkaroundTo display the file placement results, set the locale to English.


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.

WorkaroundThere is no workaround. This behavior is normal as tasks in a RUNNING state donot 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 pagemay be busy or it may have stopped responding. You canstop the script now or continue to see if the script will complete.

Report engine pie chart for "Report File Placement Results" do notdisplay (898685)

When displaying a single Tier in the "Report File Placement Results" view, theTier #-Before and Tier #-After pie charts do not display.When selecting All Tiers,the pie chart graphics display properly.


Groupnames anddescriptions truncated in Japanese version (930599)Themaximumfield length listed for groupnames (128 characters) anddescriptions(255 characters) in the online help applies only to the English version of theproduct. Thoughyoucanenter 128 characters for a groupnameand255 characters


44

for a group description in the Japanese version of the product, only the first 85characters in each field will display in the Groups tab of the Console.

WorkaroundWhen you enter a group name and description in the Japanese version of theproduct, do not exceed 85 characters.

Localized content displays unreadable text (1130097, 1117908,1117905, 1117858)

When CLI locale is set to EUC encoding, some commands display unreadable andmisaligned text.

WorkaroundTo display the CLI output correctly, use UTF-8 or PCK encoding.

Cannot load add-on from Internet Explorer 6.0 sp2 using Japaneselanguage (1109166)

When using Internet Explorer 6.0 sp2 with Japanese language selected, the DMPand Volume Migration add-on wizards do not run.

WorkaroundUse the web browser FireFox 2.0, or later, or choose English at log in to run theadd-on wizards.

SFWdisplays obsolete iSCSI host information in theConsole (1178880)After removing an iSCSI host, SFW fails to delete the host's information in theConsole. Storage Utilization reports will include data about these inactive iSCSIhosts. There is no workaround for this issue.

SF Manager Console displays incorrect status of Service GroupsIn the SF Manager Console, the status of the faulted Service Groups in a clusterappears as Faulted. When the faulted Service groups are changed to partiallyonline, the status in the Console remains as Faulted.

WorkaroundThere is no workaround for the issue.


Veritas Volume Replicator extensions and plug-ins are not displayedin the Web Console (1435804)

On a host that has Storage Foundation and SFManager installed, when you selecttheAdminister link in theSFManagerWebConsole, theVeritasVolumeReplicatorextensions and plug-ins are not displayed.

WorkaroundYou need to remove and reinstall the Veritas Volume Replicator Web Console(VRTSvrw) package on Management Server.

To remove and reinstall the Veritas Volume Replicator Web Console package

1 Run one of the following commands on Management Server to remove theVRTSvrw package:

■ On Linux: rpm -e VRTSvrw

■ On Solaris: pkgrm VRTSvrw

2 Run one of the following commands to change the directory:

■ On Linux: cd/ExtractDir/linux/storage_foundation_management_server/pkgs

■ On Solaris: cd/ExtractDir/solaris-sparc/storage_foundation_management_server/pkgs

where, ExtractDir is the path to the directory where you have extracted thedownloaded SF Manager zip file.

3 Run one of the following commands on Management Server to reinstall theVRTSvrw package:

■ On Linux: rpm -ivh VRTSvrw

■ On Solaris: pkgadd -d . VRTSvrw

After you have reinstalled the VRTSvrw package, run the following command torestart the Web Server:

/opt/VRTScweb/sfmw restart

In the SF Manager Web Console, verify that the Veritas Volume Replicatorextensions and plug-ins are displayed.


46

Managed host that has been migrated to a different ManagementServer appears uninstalled (1447133)

When youmigrate a managed host from oneManagement Server to another, themanaged host appears as uninstalled in the Web Console.

WorkaroundThemanaged host has not been uninstalled and erroneously appears uninstalledin the Web Console.

Virtual host name does not get discovered on Solaris (1439672)After SF Manager HA setup on Solaris, the virtual host name does not getimmediately discovered in theWeb Console. The virtual host name is discoveredwhen the next HOST discovery occurs.

WorkaroundRun the following command to force SF Manager to immediately discover thevirtual host name:

/VRTSmh_HOME/bin/cmsf_ctl.pl --rescan

Monitoring issuesThe following issues relate to the collection anddisplay of alerts and to theActionAgent.

Service groups are not displayed for managed hosts in a clusterSF Manager does not display the Service Groups for managed hosts that exist asnodes in a cluster.

WorkaroundMigrate the cluster node information to all views on Management Server usingthe following command on the managed host:

migrate standalone_mode -d domain_controller -p password

where domain_controller is the fully qualified host name of the currentManagement Server and password is the vea_agent password specified duringthe Management Server installation.

47Known issuesMonitoring issues

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

The following issues are related to

HBA and array discovery issues on Opteron-based Linux systems(1068470)

HBAand array discoverymaynotwork properly onOpteron-based Linux systems.The discovery informationmay be incomplete. This issue has been observed onlyon64-bitOpteron-basedLinux systemswith a 2.6.x kernel and a version8.xQLogicHBA driver.

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

Symantec Database Server on a Management Server host does notrestart after a crash on Linux (1068674)

When the Symantec Database Server (VxDBMS) on a Management Server hostcrashes, it does not restart automatically. This issue is specific to a ManagementServer installed on Linux.

WorkaroundExecute the following command to restart VxDBMS:

/etc/init.d/vxdbms3 start

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

Known issuesResource configuration issues

48

Add-ons can be installed or uninstalled on Slave nodes even after SFManager for HA is unconfigured (1447032)

After SFManager forHA is unconfigured, you can still install or uninstall add-onson the Slave node.


Add-on status of Slave node shown on Master node even after SFManager for HA is unconfigured

After SFManager forHA is unconfigured, theMaster node still shows the add-onsstatus of the Slave node.


Database and add-ons related information is lost after you unconfigureHA

The SF Manager cannot revert back to the exact original state, after youunconfigured HA as the Slave node becomes a standalone Management Serverand the database and add-ons related information is lost.

WorkaroundAfter you unconfigured HA, the Slave node becomes a standalone ManagementServer and the database and add-ons related information is lost. If you want touse SF Manager on the standalone Management Server, you must configure SFManager. Also, if youwant to perform any add-ons related task on the standaloneManagement Server, you must reinstall the add-ons.

To configure SF Manager on standalone Management Server

1 Change the directory to /opt/VRTS/install

2 Execute the command ./installsfms -configure

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

49Known issuesOther issues

vxdompackage CLI does not support the "remove" option on Linuxplatforms (1013808)

The vxdompackage CLI is used to upgrade a Storage Foundation 5.0 or 5.0 MP1managed host to an SF Manager 1.1.1 managed host.

For Linuxplatforms for theSFManager 1.1.1 release, the vxdompackage addoptionis supported for upgrading to a Linuxmanagedhost, but the vxdompackage removeoption is not supported.

CCG outage on Linux legacy managed host (619081)On legacy managed hosts running Linux, the Centralized Command Grid (CCG)might experience infrequent outages. When this happens, the host displays asfaulted in the Console. In spite of this, the host is active.

WorkaroundAs a short-term workaround, restart CCG on the affected hosts.

Login page results in blank page (stalls) (1062707)Attempting to log into the SF Manager console fails and results in blank page(stalls).

The SF Manager console (web server) stalls when:

■ The web server was running and vxsvc was restarted

■ The web server was running and vxsvc core was dumped

Theweb server does not respond because the user interface is not getting a socketexception.

WorkaroundIf the vxsvc has restarted (either manually or automatically after a core dump),restart the web server using the following command:

/opt/VRTScweb/sfmw restart

Man pages cannot be accessed when SF Manager/LMH is uninstalledon a UNIX legacy managed host (792965)

If legacy managed host (LMH) is installed and then uninstalled on a UNIX LMH,it is no longer possible to accessVEAprevious version'smanual pages (manpages).

Known issuesOther issues

50

Attempts to access the man pages may result in a message like the following:

File xxx is not owned by any package.


End Checkpoints shows "There is no started Checkpoint" (641926)After creating and starting a checkpoint, then selecting End Checkpoint, thefollowing error may display:

■ There is no started checkpoint.

This problem occurs if the selected locale of the host (Central server) is innon-English. In this case, the Checkpoint status gets localized.

Status, in the GUI is defined as a final static string whose value is in English. GUIexpects the value of the status to be in English, irrespective of the locale of thehost. Due to this mismatch, a list of started Checkpoint is not identified.

WorkaroundTo solve this problem, keep the locale of the host in English (at least, while creatingor ending the Checkpoint). The user can then browse through the SFM site in thedesired language.

If the locale of the Central server is in English, then the Checkpoint status returnsa value that is in English. TheGUI can then compare it with the final static stringsand identify the started Checkpoint.

Dual path status for disk is always shown as enabled (1059390)After disabling a dual or multiple path disk in amanaged host, the console statusdisplays an Enabled status.

To clarify, use the following steps to disable a disk path

To disable a disk path

1 Select a managed host, then click Administer.

2 Click the All Disks link in the Volume Manager section.

3 Select a disk to display.

4 Click the Paths tab.

51Known issuesOther issues

5 In the Disk Paths view, check the disk path to disable, then select Disablepath from the drop-down menu.

6 Confirm the action and click Finish to disable the path. A success messagedisplays to conclude the task.

7 The list of paths is refreshed but the status still shows Enabled for any dualor multiple path disks.

If you performed this procedure on a single path disk, the status will displaycorrectly.

WorkaroundUse the CLI to confirm that the disk path is disabled.

Enter the following command to list the disk path status:

■ vxdisk list <diskname>

where <diskname> is the name of the disk to verify.

This issue will be resolved by the DLL provider in the 5.0 MP2 release.

VEA JavaConsole does not launch after SFManager 1.1.1ManagementServer installation on a Linux host (1383236)

When SF Manager 1.1.1 Management Server is installed on a Linux host, youcannot launch theVEA Java Console if Storage Foundation has not been installed.

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

The copyright year for the VRTSob package is erroneously displayedas 2007 on Linux (1437325)

On Linux, when you use the rpm -qi VRTSob command to view the details of theVRTSob package, the copyright year is erroneously displayed as 2007. Thecopyright year for the VRTSob package is 2008.

Known issuesOther issues

52

Documentation addendaand errata


■ Addenda and errata for man pages

■ Veritas Storage Foundation Manager Administrator's Guide errata

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).

dbbackupUnder the NOTES section, after the su root command, the following commandis missing:

su root

. /opt/VRTSdbms3/vxdms_env.sh

Under the SEE ALSO section, the following cross-reference is missing:

vxdbms_start_db.pl(1M)

5Chapter

gridcli■ Under the NOTES section, the following is missing text that should precede

the bulleted items beginning with "The gridcli command is invoked to pusha file."The following shows an example usage pattern:

■ Under the OPTIONS section, the text for the --allhosts option should state:

Identifies all hosts in the grid.A registry setting must be added to run this command option. The followingcommand adds the registry setting:/opt/VRTSobc/pal33/bin/vxregctl/etc/vx/isis/Registry setvalue

Software/VERITAS/VRTSobc/pal33/Agents/gridcentral/Providers/gridcentral

"enable_run" REG_SZ "on"

/opt/VRTSobc/pal33/bin/vxpalctrl -a gridcentral -c restart

If the registry setting value is missing, it is interpreted as "off."

veaconfigUnder the OPTIONS section, right after the -r --role security_role option,before the bulleted list item, the following text is missing:

Storage Foundation Manager includes the following roles:

veainfoUnder theDIAGNOSTICS section, the following text ismissing before the bulletedlist item:

veainfo includes the followingusage problems and their respectiveworkarounds:

vxdbms_start_db.plUnder the NOTES section, after the bulleted list item, "Bourne shell and Kornshell:," the following command is missing:

. . /vxdbms_env.sh

vxdeployUnder the OPTIONS section, before the bulleted list items beginning with "Listall hosts and their platforms and operating system versions:," the following textis missing:

The vxdeploy --list option provides the following information:

Documentation addenda and errataAddenda and errata for man pages

54

For the --install option, after the text, "Installs the Add-on on the specifiedhost," the following text is missing:

Hosts can be specified using the following options:

Under the EXIT CODES section, after the text, "You can obtain the status ofintermediate deployment steps, which are updated in the SF Manager database,"the following text is missing:

When information for an Add-on is displayed, its corresponding status is alsodisplayed.

Prior to the first bulleted list item, "unavailable - Add-on failed to be uploadedwhen the installation operation started," the following text is missing:

Current states:

Prior to the first bulleted list item, "enable failed," the following text is missing:

Last Operation states:

vxdompackageUnder theDESCRIPTIONsection, prior to the "Upgrade fromaStorageFoundation5.0MP1host to a Storage Foundation5.0MP1hostwith aSFManager 1.1.1Veritasmanaged host," the following text is missing:

vxdompackage is used to upgrade or remove SF Manager 1.1.1 patches for thefollowing situations:

After the text, "When the central server is patched/upgraded, there are newmanaged host patches available at: /opt/VRTScs/adm/vxdom_images," thefollowing text is missing:

You can find platform-specific installable images at:

vxfingerUnder the DESCRIPTION section, prior to the first bulleted list item,"Fully-qualified user name," the following text is missing:

vxfinger displays the following information about each Veritas EnterpriseAdministrator (Java console) user connected to the Local Controller (vxsvc):

Under the NOTES section, after the text "Bourne shell and Korn shell," thefollowing command is missing:

. . /vxdbms_env.sh

55Documentation addenda and errataAddenda and errata for man pages

vxpalUnder the OPTIONS section, prior to the first bulleted list item, "stop," thefollowing text is missing:

control_cmd can be one of the following values:

Veritas Storage FoundationManager Administrator'sGuide errata

This section contains errata pertaining to theVeritas StorageFoundationManagerAdministrator's Guide.

In Figure 1-6, Web Server Architecture, replace Veritas Security Service (VxSS)with Symantec Product Authentication Service (SPAS). Symantec ProductAuthentication Service was formerly known as Veritas Security Service (VxSS).TheStorageFoundationManager documentation refers to SPASasAuthenticationService.

In Figure 4-1, SFManager authenticationdomains, replace the text SFMSManagedHost (SF 4.0/VEA 3.2) with SF Manager managed host (SF 4.x/VEA 3.2).

Documentation addenda and errataVeritas Storage Foundation Manager Administrator's Guide errata

56

Accessibility features


■ Navigating the SF Manager Console

■ Accessibility features in dialog boxes

Navigating the SF Manager ConsoleIn theSFManagerConsolewindow, you canuse your keyboard to view informationand perform operations by selecting a variety of different controls.

Examples of selectable controls include:

■ Tabs and subtabs

■ Navigational links at the top of the content pane

■ Column headings in tables

■ Hyperlinked objects in tables

■ Areas, such as bars in a graph, in graphical reports

■ Alert categories in the alerts list

■ Controls in the header such as Logout and Help

The current active control is enclosed with a rectangle formed by dotted lines.This area has focus. Use the Tab key to move focus from one control to another.

Following are general rules for navigating theConsole andperforming operations:

■ Press Tab to move the focus to the next active area, field, or control.

■ Press Shift+Tab to move the focus to the previous active area. In effect,Shift+Tab is the reverse of Tab.

■ Press Ctrl+Tab to move the focus to the top of the browser window.

6Chapter

■ Press Enter to activate the item that has focus. For example, after pressingTab to select a host in the Hosts summary pane, press Enter to display theobject view for that host.

■ In a drop-down list, press the arrow keys to move up and down the list.

■ When a checkbox has focus, press the Spacebar to select or deselect the box.

■ Normal accessibility features for yourWeb browser apply. In many browsers,for example, press Shift+F10 to display a context menu with which you canmove back to the previous page, print the current page, and perform otheroperations.

Accessibility features in dialog boxesIn SF Manager Console dialog boxes, the current active control has focus. As inthe Console window, you can use the Tab key to move focus from one control toanother.

When a radio button has focus, use the up and down arrow keys to move focus toa different radio button.

For example, in the following figure, Create New is selected and has focus. Toselect Edit Existing, press the down arrow key.

Figure 6-1 Example of radio button with focus

Accessibility featuresAccessibility features in dialog boxes

58

When a button has focus, press Enter to activate or select the button.

In the example above, press the Tab key to move focus to the Next button andthen press Next to move to the next dialog box.

When a drop-down list has focus, use the up and down arrow keys tomove amongthe selections and then press Enter to make your selection.

When a checkbox has focus, press the Spacebar to select or deselect the box.

When a text box has focus, use the keyboard to type text in the box.

With tree controls, the following accessibility features apply:

■ Use the Tab key to move from one tree node to another.

■ Press the Space key to expand and collapse tree nodes.

59Accessibility featuresAccessibility features in dialog boxes

Accessibility featuresAccessibility features in dialog boxes

60

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.

For information about third-party software that is used in this product, see theStorage Foundation Manager Third-Party License Agreements.

The latest version of the product documentation is available on the SymantecTechnical Support web site:

www.symantec.com/business/support/documentation.jsp?pid=52642

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

AAppendix

http://www.symantec.com/business/support/documentation.jsp?pid=52642

[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

■ 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 appropriateHelp link or menu item.

■ In any dialog window, click theHelp 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.

Getting helpDisplaying online help

62

mailto:[email protected]

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

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:

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

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.

63Getting helpContacting Symantec




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.

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]

Getting helpContacting Symantec

64


mailto:[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.

65Getting helpContacting Symantec

Getting helpContacting Symantec

66

veritasstoragefoundation manager release notes · veritasstoragefoundation™ manager release notes...

Documents