Veritas OperationsManager 5.0 Release Notes · Veritas™ Operations Manager Release Notes ... For information regarding the latest HOWTO articles, ... CIFS shares from NetApp and

Veritas™ Operations Manager5.0 Release Notes

November 2012

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

Product version: 5.0

Documentation version: 5.0 Rev 4

Legal NoticeCopyright © 2012 Symantec Corporation. All rights reserved.

Symantec, the Symantec Logo, Veritas, and Veritas Storage Foundation are trademarks orregistered trademarks of Symantec Corporation or its affiliates in the U.S. and othercountries. Other names 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 theThird Party LegalNoticeAppendixto this Documentation or TPIP ReadMe File accompanying this Symantec product for moreinformation on the Third Party Programs.

The product described in this document is distributed under licenses restricting its use,copying, distribution, and decompilation/reverse engineering. No part of this documentmay be reproduced in any form by any means without prior written authorization ofSymantec Corporation and its licensors, if any.

THEDOCUMENTATIONISPROVIDED"ASIS"ANDALLEXPRESSORIMPLIEDCONDITIONS,REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TOBELEGALLYINVALID.SYMANTECCORPORATIONSHALLNOTBELIABLEFORINCIDENTALOR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINEDIN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software andDocumentation are deemed to be commercial computer softwareas defined in FAR12.212 and subject to restricted rights as defined in FARSection 52.227-19"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights inCommercial Computer Software or Commercial Computer Software Documentation", asapplicable, and any successor regulations. Any use, modification, reproduction release,performance, display or disclosure of the Licensed Software andDocumentation by theU.S.Government shall be solely in accordance with the terms of this Agreement.

Symantec Corporation350 Ellis StreetMountain View, CA 94043

http://www.symantec.com

http://www.symantec.com

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

Symantec’s support offerings include the following:

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

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

■ Upgrade assurance that delivers software upgrades

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

■ Premium service offerings that include Account Management Services

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

www.symantec.com/business/support/

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

Contacting Technical SupportCustomers with a current support agreement may access Technical Supportinformation at the following URL:


Before contacting Technical Support, make sure you have satisfied the systemrequirements that are listed in your product documentation. Also, you should beat the computer onwhich theproblemoccurred, in case it is necessary to replicatethe problem.

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

■ Product release level



■ Hardware information

■ Available memory, disk space, and NIC information

■ Operating system

■ Version and patch level

■ Network topology

■ Router, gateway, and IP address information

■ Problem description:

■ Error messages and log files

■ Troubleshooting that was performed before contacting Symantec

■ Recent software configuration changes and network changes

Licensing and registrationIf yourSymantecproduct requires registrationor a licensekey, access our technicalsupport Web page at the following URL:


Customer serviceCustomer service information is available at the following URL:


Customer Service is available to assist with non-technical questions, such as thefollowing types of issues:

■ Questions regarding product licensing or serialization

■ Product registration updates, such as address or name changes

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

■ Latest information about product updates and upgrades

■ Information about upgrade assurance and support contracts

■ Information about the Symantec Buying Programs

■ Advice about Symantec's technical support options

■ Nontechnical presales questions

■ Issues that are related to CD-ROMs, DVDs, or manuals



Support agreement resourcesIf youwant to contact Symantec regarding an existing support agreement, pleasecontact the support agreement administration team for your region as follows:

[email protected] and Japan

[email protected], Middle-East, and Africa

[email protected] America and Latin America

About Symantec ConnectSymantec Connect is the peer-to-peer technical community site for Symantec’senterprise customers. Participants can connect and share informationwith otherproduct users, including creating forum posts, articles, videos, downloads, blogsand suggesting ideas, as well as interact with Symantec product teams andTechnical Support. Content is rated by the community, and members receivereward points for their contributions.

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

DocumentationYour feedback on product documentation is important to us. Send suggestionsfor improvements and reports on errors or omissions. Include the title anddocument version (located on the second page), and chapter and section titles ofthe text on which you are reporting. Send feedback to:

[email protected]

For information regarding the latest HOWTO articles, documentation updates,or to ask a question regarding product documentation, visit the Storage andClustering Documentation forum on Symantec Connect.

https://www-secure.symantec.com/connect/storage-management/forums/storage-and-clustering-documentation

mailto:[email protected]



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




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

Chapter 1 Overview of this release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

About Veritas Operations Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15About Management Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16About the managed host ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16About standalone (unmanaged) host ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

What's new in Veritas Operations Manager 5.0? ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Support for Veritas Operations Manager Advanced features on

Management Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Ability to compress files on managed hosts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Support for reclaiming thin storage .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Ability to configure performance metering .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Enhanced performance charts with linear trend data ... . . . . . . . . . . . . . . . . . 20Ability to define Recovery Plan .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Support for importing type definitions for clusters ... . . . . . . . . . . . . . . . . . . . 21Improved discovery and visualization of all applications .... . . . . . . . . . . . 21Support for configuring a vCenter server on a non-default

port ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Selective discovery of VMware ESX servers and IBM LPAR

servers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Support for multi-pathing discovery in VMware

environment .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Support for discovering Microsoft Hyper-V virtualization

technology and storage correlation discovery for LDomandLPAR .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Symantec Performance Value Unit information for IBM LPARand kernel-based virtual machines (KVM) .... . . . . . . . . . . . . . . . . . . . . . . . . . 22

Automatic assignment of price tiers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Support for additional discovery in Storage Insight Add-on .... . . . . . . . 22Veritas Operations Manager Storage Insight SDK Add-on .... . . . . . . . . . . 23Support for listing the configured enclosure using the

command-line interface ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Support for service management using the command-line

interface ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Contents

Support for new operations in Veritas Operations ManagerAdd-on for Storage Foundation Administration 5.0 ... . . . . . . . . . . . . . 24

Improved monitoring of Veritas Volume Replicatorreplications .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Support for Microsoft Exchange Server 2010 discovery .... . . . . . . . . . . . . . 25Support for specifying path for temporary work area while

upgrading Management Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Add-on user's guides combined into a single guide .... . . . . . . . . . . . . . . . . . . . 25

Issues fixed in the Veritas Operations Manager 5.0 release ... . . . . . . . . . . . . . . . 26

Chapter 2 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Operating system requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Third-party required libraries ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

32-bit SNIA Common HBA API required on Windows hosts ... . . . . . . . . . 32System resource requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

About the frequency of managed host informationdiscovery .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

About space estimation for data logs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Supported hardware .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Web browser requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Network and firewall requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39About the consumption of the managed host components ... . . . . . . . . . . . . . . . . 40

Chapter 3 Software limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Veritas OperationsManager 5.0managed host not supported on AIXin Network Installation Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

No coexistence of managed host and CommandCentral StorageManagement Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Live statistics for initiators are not supported on HP-UX(2001078) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

No support for creating large file systems on HP-UX managed hostsusing the prebundled Add-on for Storage FoundationAdministration (2858041) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Performance charts are not supported in certain cases for multipleobjects that belong to different hosts (2023666) ... . . . . . . . . . . . . . . . . . . . . . . . . 45

Performance graphs cannot be viewed for Windows managedhosts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Volume layout not discovered for LDM-managed volumes mountedwithout a drive letter ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Backup and restore limitations in Veritas Operations Manager5.0 ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Contents8

VeritasOperationsManager does not support the discovery of LDomsand Zones together on the same host (2281088) ... . . . . . . . . . . . . . . . . . . . . . . . . 46

Veritas Operations Manager Add-on for Storage FoundationAdministration 5.0 limitations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Deployment-related limitations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Windows Management Server high availability configuration

limitations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Solaris Zones virtualization support limitations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Discovery limitations for virtualization support ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Log on to console fails on Internet Explorer if Management Server

host name has the underscore (_) character ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48VCS configuration check reports violations only if at least one node

in the cluster is running Veritas Cluster Server (2117417) ... . . . . . . . . . . 48Limitations related to the correlation between the disks and the disk

groups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49No support to online and offline multiple virtual machines using the

Virtual Business Service start and stop operations(2177421) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Virtual Business Service start operation does not validate the servicegroup's resource criticality (2169223) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Discovery of VMware VirtualCenter server or ESX server is notcase–sensitive (2567318) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Core density may not get calculated properly on HP-UX11iv2hosts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Tier information is not displayed for somedevices in a FASTmanagedstorage group (2795204) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

IBMSystemStorageDS enclosure discovery is not supported throughHiCommand Server 7 in Veritas Operations Manager(2708346) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Correlation between NAS file system and Storage Pools is notdisplayed for EMC VNX storage enclosures (2804423) ... . . . . . . . . . . . . . . . . 51

CIFS shares from NetApp and Celerra arrays that are mapped to aWindows host are not discovered (2752493) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Performance charts may not be displayed for EMC Symmetrix arrayports and adapters ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Inconsistency in storage calculation is observed for unclaimedVPLEXextents (2844028) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Chapter 4 Known issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Management Server issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Delayed discovery of VMware VirtualCenter server by Control

Hosts in Veritas Operations Manager (2342314) ... . . . . . . . . . . . . . . . . . . 53

9Contents

Log on to the Veritas Operations Manager console may fail onFirefox (1939352) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Authentication broker crashes while performing LDAPauthentication (2017319) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

XPRTLD daemon fails when Veritas Operations Manager startsbecause of the corruptATpem files in the VRTSsfmhpackage(2145925) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Status of all SF Manager 2.x hosts is shown as healthy on anupgraded Veritas Operations Manager 5.0 setup(2009372) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Uninstalling Management Server removes the managed hostpackage from a Storage Foundation for Windows host ... . . . . . . . . . 58

UpgradeofManagementServer inHighAvailability environmentfails with database upgrade errors (2853154) ... . . . . . . . . . . . . . . . . . . . . . 58

Veritas Operations Manager displays stale application status(2564572) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Mountpointmay appear as garbled characters, if encoding is notsupported (2377238) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Manual refresh ofHMCserver andVMwareVirtualCenter serverrequired after migration of virtual machines(2605533) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Microsoft ExchangeServer 2007 toVCS service group correlationis not present in the first discovery cycle of VeritasOperations Manager (2604162) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Coexistence of ApplicationHA Console and Veritas OperationsManagerManagement Server in theApplicationHAConsoleupgrade scenario (2581661) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Performance metering of a VMware ESX server may not workproperly after failover (2814844) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Management Server cannot be configured on a Windows hostwith Russian locale (2676438) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Managed host issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Issue related to upgrading the managed hosts (from 3.x to 5.0)

that have LUNs from IBM XIV storage array (2367519) ... . . . . . . . . 62Quick I/O cache value is not enabled after performing the storage

provisioning operation on AIX managed hosts(2131183) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Cannot replace or recover a disk removed from a UNIX host(2317671) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

After the replace disk operation, the faulted disk status remainsas replaceable (2353612) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

ThinLUNson thehosts that runStorageFoundation forWindows5.1 SP1 are not discovered as thin (2513466) ... . . . . . . . . . . . . . . . . . . . . . . 63

Contents10

CPUcount incorrect formanagedhosts onWindowsServer 2003(2437565) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Remote switch operation fails between secure clusters (2530605) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Adding an agentless host to a Linux-based control hostfails ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Add host operation fails for HP-UX managed hosts(2601265) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Some performance charts are not available for VMware ESXserver version 4.1 managed through vCenter server 5.0(2800239) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Cannot add a managed host to Management Server using theIPv6 address of the host (2816487) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Cannot add a Windows 2008 64-bit host that has both IPv4 andIPv6 networks enabled to Management Server(2712982) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Incorrect statistics returned by DMP if Storage Foundationversion is prior to 5.0 MP3 (2796418) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Incorrect name displayed for one performance graph forenclosures (2854125) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Issues in the Add Host(s) wizard while adding agentless hosts toManagement Server domain (2856380) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Agentless discovery issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Agentless configuration of hosts using IPv6 addresses fails

(2414252) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Agentless configuration ofWindows hosts running non-English

locale fails (2484139) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Configuration fails for agentless hostwith user name containing

DBCS characters (2427619) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67fstab information displayed incorrectly for file systems on Linux

agentless host (2418023) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Agentless discovery fails if a host has volume names, mount

point names, or disk label names that contain equals(=)sign(2590669) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Volume group and logical volume information can beinconsistent, if Volume group is created on shared disks(2567056) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Failed EMC PowerPath paths are not displayed for agentlessWindows 2008 hosts (2611064) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Storage Provisioning Add-on issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Avolume ismigrated to any available enclosure if no target array

is specified (2143010) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Storage Insight Add-on issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

11Contents

Thevxlist utility does not display the information on the physicaldisks for the LUNs (2219286) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Cannot configure an EMC CLARiiON enclosure on a Windowscontrol host using a security file (2221574) ... . . . . . . . . . . . . . . . . . . . . . . . . 68

NetApp enclosures are not discovered after the Storage InsightAdd-on is upgraded to version 5.0 ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Reports generated by pre-existing schedules display erroneousdata after installing or upgrading to Storage InsightAdd-on5.0 (2823297) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Performancemetering of enclosuresmaynotworkproperly afterfailover (2814844) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Information on FAST managed storage groups for EMCSymmetrix VMAX enclosures is not discovered periodically(2842124) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Array group information is incorrect in Enclosure StorageSummary chart for Hitachi arrays (2820150) ... . . . . . . . . . . . . . . . . . . . . . . 71

Password file option does not work while configuring HP EVAenclosures on Windows hosts (2757601) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

EMC Celerra enclosure details are not discovered for users withread-only access rights, and Imported Administrator orOperator role ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Network File System on Solaris cannot be discovered if the FullyQualified Host Name is used in vfstab file but not used formounting the file system (2747735) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

VBS Availability Add-on issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72VeritasOperationsManager does not validate if the cluster node

ismanaged by theManagement Server during theVBS startoperation (2566050) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Disabling fault management for Virtual Business Services doesnot display the dependency as Soft in the console(2725638) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Scripting Add-on issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73PostManagement Server upgrade, the ScriptingAdd-onuses the

current time of theManagement Server to run the previousscripts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Scripting Add-on runs the Perl scripts successfully only whenthe Perl executable installed with Veritas OperationsManager is used (2589815) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Storage Insight SDK Add-on issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Edit and Test operations on Storage Insight Plug-in are not

supported using Internet Explorer on 64-bitWindows hosts(2826079) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

LDom Capacity Management Add-on issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Contents12

Capacity planning cannot be enabled or disabled from theOrganization Entities view (2827450) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Other issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Duplicate entries for the disks that are part of a virtual machine

(2481982) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Composite business entities donot inherit all user configurations

done for the child business entities (2349751) ... . . . . . . . . . . . . . . . . . . . . 75Symantec ApplicationHA Console single sign-on breaks after

Veritas Operations Manager 5.0 managed host installationor upgrade on ApplicationHA hosts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Appendix A Documentation addenda and errata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Addenda and errata for Veritas Operations Manager 5.0 onlinehelp .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77About multi-pathing discovery in the VMware

environment .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77About the virtualization technologies supported by Veritas

Operations Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78About Microsoft Hyper-V virtualization discovery in Veritas

Operations Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Virtual machine discovery in Microsoft Hyper-V .... . . . . . . . . . . . . . . . . . . . . . . 78Storage mapping discovery in Microsoft Hyper-V .... . . . . . . . . . . . . . . . . . . . . 79Navigation changes to the virtualizationmanagement option on

Veritas Operations Manager console ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Viewing information on the storage assigned to virtualmachines

from a virtualization server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Viewing the overview of enclosure information .... . . . . . . . . . . . . . . . . . . . . . . . 81Viewing an enclosure’s array port paths ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Viewing an enclosure's array port disks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Viewing an enclosure's array port volumes .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Viewing an enclosure's array port databases ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83About Veritas Operations Manager performance graphs .... . . . . . . . . . . . 84Pre-requisite commands to view performance graphs for a

resource ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Errata for Veritas Operations Manager Storage Insight Add-on for

Deep Array Discovery and Mapping 5.0 online help .... . . . . . . . . . . . . . . . . . . 86Configuring deep discovery for EMC Symmetrix storage

enclosures ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Configuring deep discovery for EMC VPLEX storage

enclosures ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Viewing all virtual volumes for the EMC VPLEX enclosure ... . . . . . . . . . . 87

13Contents

Viewing the virtual volumes of a device for the EMC VPLEXenclosure ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Viewing the overview of the EMC VLPEX enclosure ... . . . . . . . . . . . . . . . . . . . 87Viewing the device configurations for storage enclosures ... . . . . . . . . . . . 87Viewing the tier configuration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Viewing the overview of a NetApp enclosure ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Viewing the LUNs on a NetApp enclosure ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Viewing all the virtual disks on an HP EVA enclosure ... . . . . . . . . . . . . . . . . 89Viewing the disks associated with a virtual disk on an HP EVA

enclosure ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Viewing the physical disks of a virtual disk on an HP EVA

enclosure ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Viewing the performance graphs for an array port ... . . . . . . . . . . . . . . . . . . . . 89

Addenda and errata for Veritas Operations Manager Add-on forStorage Foundation Administration 5.0 online help .... . . . . . . . . . . . . . . . . . . 91Volume attributes panel options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Create a new file system panel options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Creating volumes .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Errata for Veritas Operations Manager Storage Insight SDK Add-on5.0 online help .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94About Veritas Operations Manager Storage Insight SDK Add-on

5.0 ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Operational workflow to create Storage Insight Plug-in ... . . . . . . . . . . . . . . 95About installing Storage Insight SDK Add-on 5.0 ... . . . . . . . . . . . . . . . . . . . . . . 95About discovering array information using Storage Insight SDK

Add-on .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Creating a Storage Insight plug-in ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Appendix B Getting help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Veritas Operations Manager on the Web .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Getting help .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Using the product documentation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Contents14

Overview of this release

This chapter includes the following topics:

■ About Veritas Operations Manager

■ What's new in Veritas Operations Manager 5.0?

■ Issues fixed in the Veritas Operations Manager 5.0 release

About Veritas Operations ManagerVeritas Operations Manager by Symantec gives you a single, centralizedmanagement console for the Veritas Storage Foundation and High Availabilityproducts. You can use it to monitor, visualize, and manage storage and clusterresources, and generate reports about them. Veritas Operations Manager letsadministrators centrally manage diverse datacenter environments.

You can also use Veritas Operations Manager to manage the hosts, which do nothave Storage Foundation and High Availability products installed on them.

In Veritas Operations Manager, you can establish user credentials such thatauthorized users can access the product to perform sensitive management tasks,and other users can perform only a basic set of functions.

A typical Veritas Operations Manager deployment consists of the following:

■ Management ServerSee “About Management Server” on page 16.

■ Managed hostsSee “About the managed host” on page 16.

For more information on managing security roles and users accounts, see theVeritas Operations Manager Management Server Administrator's Guide.

1Chapter

About Management ServerIn a centrallymanaged deployment, youmust configure one host asManagementServer. Management Server receives information about all the resources in itsdomain. When you log on to Management Server, you can gain access to theresources on different hosts within the centrally-managed deployment.

When you install Management Server, the Web server component is installedautomatically.

You can use the Web server on Management Server to access the managed hostsin the centrallymanaged deployment. You log on to theManagement Server URLand Web server port 14161 (for example, https://myhost.example.com:14161).

See “About Veritas Operations Manager” on page 15.

About the managed hostA typical VeritasOperationsManager deployment consists ofManagement Serverand at least one managed host.

Typically, a managed host is a production server on which you install and runStorage Foundation andHighAvailability product components. A typical site canhave thousands of hosts using some or all of the Storage Foundation and HighAvailability products. You can also use Veritas Operations Manager to managehosts onwhich Storage Foundation, or Storage Foundation andHighAvailability,are not installed.

In Veritas Operations Manager, Management Server is also configured as amanaged host. You can manage Management Server itself as part of a centralmanagement domain.

In a centrally managed deployment, the managed hosts relay information aboutstorage network resources and applications toManagement Server.ManagementServer merges the data it receives from the managed hosts within its database.Using this merged data, the Veritas Operations Manager console can presentcentralized views and reports.


About standalone (unmanaged) hostA standalone (unmanaged) host is a Storage Foundation host that has beenconfigured so it does not belong to a central management domain.

To manage individual Storage Foundation hosts, you can install and use theJava-based Veritas Enterprise Administrator. This console lets youmanage hostsusing the Storage Foundation products installed on them.

Overview of this releaseAbout Veritas Operations Manager

16

If you want a standalone host to participate in the central management domain,youmust update it by installing theVeritasOperationsManagerhostmanagementpackage.

Note: You can convert any standalone host to a managed host. However, becauseManagement Server is also a managed host, you cannot configure it to be astandalone host.


What's new in Veritas Operations Manager 5.0?This release of Veritas Operations Manager includes the following new featuresand enhancements.

■ Support for Veritas Operations Manager Advanced features on ManagementServerSee “Support for Veritas Operations Manager Advanced features onManagement Server” on page 19.

■ Ability to compress files on managed hostsSee “Ability to compress files on managed hosts” on page 19.

■ Support for reclaiming thin storageSee “Support for reclaiming thin storage” on page 19.

■ Ability to configure performance meteringSee “Ability to configure performance metering” on page 20.

■ Enhanced performance charts with linear trend dataSee “Enhanced performance charts with linear trend data” on page 20.

■ Ability to define Recovery PlanSee “Ability to define Recovery Plan” on page 21.

■ Support for importing type definitions for clustersSee “Support for importing type definitions for clusters” on page 21.

■ Improved discovery and visualization of all applicationsSee “Improved discovery and visualization of all applications” on page 21.

■ Support for configuring a vCenter server on a non-default portSee “Support for configuring a vCenter server on a non-default port”on page 21.

■ Selective discovery of VMware ESX servers and IBM LPAR servers

17Overview of this releaseWhat's new in Veritas Operations Manager 5.0?

See “Selective discovery of VMware ESX servers and IBM LPAR servers”on page 21.

■ Support for multi-pathing discovery in VMware environmentSee “Support formulti-pathingdiscovery inVMware environment”onpage 22.

■ Support for discovering Microsoft Hyper-V virtualization technology andstorage correlation discovery for LDom and LPARSee “Support for discoveringMicrosoftHyper-V virtualization technology andstorage correlation discovery for LDom and LPAR” on page 22.

■ SymantecPerformanceValueUnit information for IBMLPARandkernel-basedvirtual machinesSee “Symantec Performance Value Unit information for IBM LPAR andkernel-based virtual machines (KVM)” on page 22.

■ Automatic assignment of price tiersSee “Automatic assignment of price tiers” on page 22.

■ Support for additional discovery in Storage Insight Add-onSee “Support for additional discovery in Storage Insight Add-on” on page 22.

■ Veritas Operations Manager Storage Insight SDK Add-onSee “Veritas Operations Manager Storage Insight SDK Add-on” on page 23.

■ Support for listing the configured enclosures using the command-line interfaceSee “Support for listing the configured enclosure using the command-lineinterface” on page 23.

■ Support for service management using the command-line interfaceSee “Support for service management using the command-line interface”on page 23.

■ Support for newoperations inVeritasOperationsManagerAdd-on for StorageFoundation Administration 5.0See “Support for new operations in Veritas Operations Manager Add-on forStorage Foundation Administration 5.0” on page 24.

■ Improved monitoring of Veritas Volume Replicator replicationsSee “Improved monitoring of Veritas Volume Replicator replications”on page 25.

■ Support for Microsoft Exchange Server 2010 discoverySee “Support for Microsoft Exchange Server 2010 discovery” on page 25.

■ Support for specifying path for temporary work area while upgradingManagement ServerSee “Support for specifying path for temporary work area while upgradingManagement Server” on page 25.

Overview of this releaseWhat's new in Veritas Operations Manager 5.0?

18

■ Add-on user's guides combined into a single guideSee “Add-on user's guides combined into a single guide” on page 25.

Support for Veritas Operations Manager Advanced features onManagement Server

VeritasOperationsManagerManagementServer supports a fewVeritasOperationsManager Advanced features, that can temporarily be used under a demo licenseof Veritas Operations Manager Advanced. To obtain a permanent license, youneed to accept the End User's License Agreement (EULA) for Veritas OperationsManager Advanced. These features include:

■ Discovery of hosts that do not have Veritas Storage Foundation and HighAvailability (SFHA) products installed on them

■ Discovery of hosts via agentless method

■ Discovery of network-attached storage (NAS)

Ability to compress files on managed hostsVeritas Operations Manager Management Server now lets you set up filecompression on amanagedhost at the file system (mount point) level.This featureis supported for VxFS file systems with Veritas Storage Foundation 6.0 or lateron the managed host.

The file compression feature lets you do the following:

■ Select directories for compression

■ Set up a schedule for running the compression process on the host

■ Compress or uncompress directories on demand

■ View a report of space saved by file compression

Support for reclaiming thin storageUsing Veritas Operations Manager Management Server console, you can reclaimthin storage. This feature requires VxFS file system, Storage Foundation version6.0 or later. Also, using Veritas Operations Manager Management Server consoleyou can determine how much storage can be reclaimed before performing thisoperation.


Ability to configure performance meteringUsing Veritas OperationsManager 5.0, lets you gather performance statistics forthe VMware vCenter server, the VMware ESX server, and the managed host. Youcan also disable performance statistics gathering if required.

If Storage Insight Add-on 5.0 is installed and the discovery host is upgraded toVeritas Operations Manager managed host version 5.0, performance statisticsgathering is automatically enabled for storage enclosures that were previouslyconfigured.

Performance statistics are collected only for the following storage enclosures:

■ EMC CLARiiON

■ EMC Symmetrix

■ IBM XIV

■ NetApp

Enhanced performance charts with linear trend dataNew enhanced performance charts are now available in Veritas OperationsManager along with the linear trend data. You can view performance charts forthe following resources:

■ volume

■ host

■ disk

■ initiator

■ file system

■ multipathing path

■ enclosure

■ array ports

■ adapter

Performance charts for disks and volumes are available only if they are managedbyVeritasVolumeManager. Performance charts formultipathingpaths, initiators,and enclosures are available if they are managed by physical hosts running DMPor VMware ESX servers running VxDMP.


20

Ability to define Recovery PlanRecovery Plans consist of the steps that need to be run when a disaster orcontingency arises. VeritasOperationsManager provides the ability to create andstore Recovery Plans, to manually run a plan, and to monitor and log its progressand status.

Using the Veritas Operations Manager console, you can perform the followingtasks:

■ Create a Recovery Plan.

■ Edit a Recovery Plan.

■ Delete a Recovery Plan.

■ Run a Recovery Plan.

Support for importing type definitions for clustersIn Veritas Operations Manager, you can now import custom resource typesdefinition into a cluster configuration. For example, youmay need to import typedefinitions when you install an Independent Software Vendor (ISV) agent on aVeritasCluster Server (VCS) cluster.OnWindows, the typedefinitions are importedby default, however on UNIX, the administrator needs to explicitly import thedefinitions.

Improved discovery and visualization of all applicationsVeritas Operations Manager now provides complete visibility into the differentapplications that are discovered fromphysical or virtualmachines. Thediscoveryincludes the applications that Symantec ApplicationHA discovers on differentvirtualization technologies (such as VMware, KVM, LPAR, and LDOM). You canview applications for the entire domain, or for selected business entities.

Support for configuring a vCenter server on a non-default portIn Veritas Operations Manager 5.0, you can configure a vCenter server on anon-default port. You can specify the fully-qualified name of the vCenter serveror its IP address, and theport number onwhich the vCenterWeb service is running.

Selective discovery of VMware ESX servers and IBM LPAR serversIn the previous release, when you configured a vCenter server or an HMC server,Veritas Operations Manager discovered all the ESX servers under the vCenterserver, or all the LPAR servers under the HMC server. In Veritas Operations


Manager 5.0, you can selectively enable or disable discovery for some of the ESXservers or LPAR servers.

Support for multi-pathing discovery in VMware environmentVeritas Operations Manager now supports multi-pathing discovery for the diskpathsunderVMwarenativemulti-pathing (NMP), EMCPowerPath/Virtual Edition,and Symantec VxDMP on ESX servers. However, path maintenance operations(enable or disable path) are supported only on Symantec VxDMP.

Support for discovering Microsoft Hyper-V virtualization technologyand storage correlation discovery for LDom and LPAR

Veritas Operations Manager supports the discovery of following virtualizationtechnologies:

■ Microsoft Hyper-V servers, Hyper-V virtual machines, and their server andstorage correlation.

■ Storage correlation discovery for Logical partition (LPAR), VIO server, andVIO clients.

■ Storage correlation discovery for Oracle VM Server for SPARC (LDoms).

Symantec Performance Value Unit information for IBM LPAR andkernel-based virtual machines (KVM)

In Veritas Operations Manager 5.0, you can calculate the Symantec PerformanceValue Unit (SPVU) for the Symantec products that run on IBM LPAR and KVM.

Automatic assignment of price tiersYou can now assign price tiers to a single host, or multiple hosts, automaticallyin Veritas Operations Manager using the uploaded price tier information.

Support for additional discovery in Storage Insight Add-onVeritas OperationsManager now lets you enable deep discovery for the followingenclosures using Storage Insight Add-on:

■ HP Enterprise Virtual Arrays (EVA)

■ IBM System Storage DS

■ EMC Celerra


22

■ EMC VNX and Unified Storage

■ EMC VPLEX

■ 3PAR

Additionally, Storage InsightAdd-onnowalso supports network attached storage(NAS) discovery for NetApp enclosures, and Fully Automated Storage Tiering(FAST) support on EMC Symmetrix VMAX enclosures.

Veritas Operations Manager Storage Insight SDK Add-onYou can use Veritas Operations Manager Storage Insight SDK Add-on to createcustomized array-specific add-ons. This feature is useful if the storage discoveryfor an array is not supported throughStorage InsightAdd-on. The customadd-onsare called Storage Insight plug-ins. You can specify the array objects to bediscovered, discovery script, andprovide theuniquedevice identifier for the arraysand logical disks for end-to-end correlation from the LUNs to the storage arrays.You can install Storage Insight SDK Add-on on any host that has the VRTSsfmhpackage installed on it. The host may or may not be configured to a ManagementServer domain.

Support for listing the configured enclosure using the command-lineinterface

In Veritas Operations Manager 5.0, you can list all the enclosures that areconfigured throughVeritasOperationsManager Storage InsightAdd-on forDeepArray Discovery andMapping using the command-line interface. You can use thearrayinfo option of the vomadm command to list the enclosures.

Support for service management using the command-line interfaceIn Veritas Operations Manager 5.0, you can use the service option of the vomadmcommand to manage the various services using the command-line interface. Youcan start a service, stop a service, restart a service, or display the status of aservice. You can also use the command to display the version of the VeritasOperations Manager packages that are installed on Management Server(VRTSsfmcs and VRTSsfmh).


Support for new operations in Veritas Operations Manager Add-on forStorage Foundation Administration 5.0

In Veritas Operations Manager Add-on for Storage Foundation Administration,the following operations have been enhanced to improve user experience andauditing over previous implementations:

Disk group operations:

■ Create a volume.

■ Import a disk group.

■ Recover a disk group.

■ Destroy a disk group.

■ Remove a disk from a disk group.

■ Rename a disk.

■ Resize a disk.

■ Initialize a disk.

■ Disconnect or deactivate a disk.

Volume operations:

■ Disassociate a snapshot.

■ Re-attach a snapshot.

■ Recover a volume.

■ Stop a volume.

■ Reactivate a volume.

■ Restore a volume.

■ Create a file system.

File system operations:

■ Enable a change log.

■ Disable a change log.

■ Synchronize a change log.

■ Remove a change log.

■ Defrag a file system.


24

Improved monitoring of Veritas Volume Replicator replicationsInVeritasOperationsManager 5.0, you canmonitor anyReplicatedVolumeGroup(RVG) for replications that lag behind in terms of log usage (SRL usage), or interms of data size. You can define high and low threshold levels for raising analert that is displayed in the Veritas Operations Manager console.

Support for Microsoft Exchange Server 2010 discoveryVeritas Operations Manager now supports the discovery and management ofMicrosoft Exchange Server 2010 hosts that are configured in your datacenter.

Support for specifying path for temporary work area while upgradingManagement Server

ManagementServerupgrade requires additional disk space to create the temporaryfiles.while upgrading toVeritasOperationsManager 5.0, if youdonothave enoughdisk space in your current database directory, you are prompted to provide thepath for a temporary working area having enough disk space. This temporaryworking area is used to create the temporary files.

Add-on user's guides combined into a single guideThe user's guides for the add-ons listed below are now combined into a singleguide titledVeritasOperationsManagerManagementServerAdd-onsUser'sGuide.

■ Add-on for ApplicationHA Management

■ Add-on for Storage Foundation Administration

■ Add-on for VCS Administration

■ Add-on for Veritas Cluster Server User Password Management

■ Add-on for Veritas Volume Replicator Bandwidth reporting

■ Distribution Manager Add-on

■ LDom Capacity Management Add-on

■ Package Anomaly Add-on

■ Scripting Add-on

■ Storage Insight Add-on

■ Storage Insight SDK Add-on

■ Storage Provisioning Add-on


■ Thin Provisioning Reclamation Add-on

Issues fixed in the Veritas Operations Manager 5.0release

Table 1-1 lists the Management Server issues that have been fixed in the VeritasOperations Manager 5.0 release.

Table 1-1 Management Server issues fixed in Veritas Operations Manager 5.0

DescriptionIncident

VMware virtual machine storage mapping information is not populated ifthe virtual machine name contains a single quote.

2510591

Inconsistent behavior when you configure the LDAP domain if the LDAPserver does not respond or server name is invalid.

2024598

Operating system-based authentication domains are removed after yourefresh the authentication broker in a Windows Management Server-HAsetup.

2362587

Veritas Operations Manager prompts you to overwrite the search queryeven when you save the query for the first time.

2299458

Certain views in Veritas Operations Manager are not displayed properlyafter Management Server upgrade.

2133867

Pagination issue is observed in the Host table of Business entity overviewpage.

2369071

VMware virtualizationdiscovery fails if the vCenter server uses non-defaultHTTPS port.

2611025

Error in installing add-ons after upgrading certainManagement Server-HAsetups.

2603669

vomsc command does not work properly in Management Server HA-DRsetup.

2605531

Table 1-2 lists the managed host issues that have been fixed in the VeritasOperations Manager 5.0 release.

Overview of this releaseIssues fixed in the Veritas Operations Manager 5.0 release

26

Table 1-2 Managed host issues fixed in Veritas Operations Manager 5.0

DescriptionIncident

Addition of agentless Solaris managed host may fail for some arpconfigurations.

2581177

Removal of agentless host while refresh is in progress results in a badconfiguration state.

2480954

Incorrect error message is displayed while configuring agentless UNIXhosts without enough free space in the /var/tmp directory.

2428471

Timezone and GMToffset informationare not displayed for hosts that areconfigured using agentless discovery.

2294669

Incorrect discovery state displayed for agentless hosts that are refreshed2578260

Managedhosts stop communicatingwithManagement Server afterVeritasCluster Server is installed.

2341920

Cannot add amanaged host with pure IPv6 address toManagement Serverthat supports IPv4 and IPv6.

2137308

Information on the disks and the LUNs for a Windows host where StorageFoundation forWindows is newly installed are not displayed on the console.

2345887

ExchangeServer information is not displayed aftermanagedhost upgrade.1976615

27Overview of this releaseIssues fixed in the Veritas Operations Manager 5.0 release

Overview of this releaseIssues fixed in the Veritas Operations Manager 5.0 release

28

System requirements


■ Operating system requirements

■ Third-party required libraries

■ System resource requirements

■ Supported hardware

■ Web browser requirements

■ Network and firewall requirements

■ About the consumption of the managed host components

Operating system requirementsTable 2-1 provides an overview of Veritas Operations Manager operating systemrequirements for Management Server:

2Chapter

Table 2-1 Veritas Operations Manager operating system requirements forManagement Server

NotesOperating system supported

x86 64-bit is the supported architecture.

32-bit glibc and libgcc packages mustbe installed.

Korn shell (KSH)must be installed.

Red Hat Enterprise Linux 5.0

Red Hat Enterprise Linux 5.1 Update 1








Red Hat Enterprise Linux 6



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

SUSE Linux Enterprise Server 10


SPARC is the supported architecture.

Note: Solaris 11 SPARC is not supported.

Note:VeritasOperationsManager 5.0 is thelast major version of the product to supportSolaris as a platform for ManagementServer. Symantec recommends that youdeploy Veritas Operations Manager 5.0Management Server on Linux or Windowsto simplify the upgrade process to upcomingVeritas Operations Manager 6.x versions.

Solaris 10

x86 64-bit is the supported architecture.Windows 2003

Windows 2008

Windows 2008 R2

Table 2-2 provides an overview of Veritas Operations Manager operating systemrequirements for managed hosts:

System requirementsOperating system requirements

30

Table 2-2 Veritas Operations Manager operating system requirements formanaged hosts having Storage Foundation or Storage Foundationand High Availability products

NotesOperating system supported

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

AIX 5.2

AIX 5.3

AIX 6.1 (only for hosts with StorageFoundation 5.0 MP3, or later)

AIX 7.1 (only for Storage Foundation 5.1 SP1PR1 hosts)

PA RISC is the supported architecture.HP-UX 11.11 (only for Storage Foundation3.5 hosts)

HP-UX 11.23

HP-UX 11.31

On Red Hat Enterprise Linux 4.0, StorageFoundation 5.0 is supported on 64-bit Xeon,x86.

32-bit glibc and libgcc packages mustbe installed.


RedHat Enterprise Linux 5.0Update 2 (onlyfor hosts with Storage Foundation 5.0 MP3,or later)

Red Hat Enterprise Linux 6


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


SUSE Linux Enterprise Server 10 (only forhosts with Storage Foundation 5.0 MP3, orlater)

SUSE Linux Enterprise Server 11 (only forhosts with Storage Foundation 5.0 MP3, orlater)

Solaris 8

Solaris 9

Solaris 10

Solaris 11

Supported on x86, x64, and IA64.Windows Server 2003

Windows Server 2008

Windows 2008 R2

31System requirementsOperating system requirements

Veritas Operations Manager operating system requirements for the managedhosts that do not have Storage Foundation or Storage Foundation and HighAvailability products:

■ AIX 5.2, or later

■ HP-UX 11.23, or later

■ Red Hat Enterprise Linux 4.x, or later

■ SUSE Linux Enterprise Server 9, or later

■ Solaris 9

■ Solaris 10

■ Solaris 11

■ Windows Server 2003

■ Windows Server 2008

■ Windows Server 2008 R2

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

www.symantec.com/techsupp/

See “System resource requirements” on page 33.

Third-party required librariesThis section lists third-party libraries required to runVeritasOperationsManager:

■ 32-bit SNIA Common HBA API required on Windows hosts

32-bit SNIA Common HBA API required on Windows hostsFor proper discovery of Fibre Channel attached devices—including discovery ofHBAand its target ports—VeritasOperationsManager requires installation of the32-bit SNIA Common HBA API on all Windows managed hosts running HBAcontrollers.

The Common HBA API is typically available as part of your HBA vendor’s driverkit, or you can download it from your HBA vendor’s site.

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

System requirementsThird-party required libraries

32

www.symantec.com/techsupp/

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

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

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

HKEY_LOCAL_MACHINE\SOFTWARE\SNIA\HBA\hba_model

On64-bit platforms,VeritasOperationsManager requires 32-bit libraries installedas a pre-requisite. For more information, see your HBA vendor documentation.

System resource requirementsThe amount ofmemory and disk space that Veritas OperationsManager requiresare listed in this section. The requirements are in addition to the resources thatother software applications running on the host use.

For Management Server:

■ CPU required: Dual processor for every 1000 managed hosts.

■ Memory required:

■ 4GB for every 1000 managed hosts.

■ Add 4GB of memory if Management Server is used for the deep discoveryof enclosures using the Storage Insight Add-on.

■ Add 4GB of memory if Management Server is used for the discovery ofvirtualization infrastructure.

■ Disk space required: 15GB of disk space for every 1000 managed hosts.

For a managed host:

■ CPU required: 1 <5%

■ Virtual memory required: 1GB

■ Disk space required: 2GB

For Control Host (that has Control Host Add-on):

■ CPU required: Dual processor for agentless discovery of every 1000 managedhosts.

■ Memory required:

■ 4GB for agentless discovery of every 1000 managed hosts.

■ Add 4GB of memory if Control Host is used for the discovery ofvirtualization infrastructure.

33System requirementsSystem resource requirements

■ Disk space required: 15GB of disk space for agentless discovery of every 1000managed hosts.

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

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

See “About the frequency of managed host information discovery” on page 34.

See “Operating system requirements” on page 29.

About the frequency of managed host information discoveryThe following table describes the frequency of the managed host informationupdates in the Management Server database. The discovery on each managedhost is divided into families to focus on a particular functional area:

Discovered informationFrequencyin minutes

Family

The operating system, packages, andnetworking for the host.

Typically,most of the information that is related to this familydoes not change frequently.

1440Host

Volume Manager, File Systems, and the related storagenetwork.

30SF

Veritas Cluster Server and the related information.60VCS

Oracle, DB2, MSSQL, and Sybase databases and their storagedependencies.

60DB

The licenses that are installed on the hosts.1440LDR

Configuration status and external faults.5NR

Third-party volume management information.360Native

Oracle Solaris zones and their storage dependencies.120Zones

Oracle Solaris LDoms, and related CPU and memoryinformation.

120LDoms

KVMs, and their correlation with the host.120KVM

Virtual machines and storage discovery.120Hyper-V

Hosts, guests, and storage information.360LPAR

System requirementsSystem resource requirements

34


Discovered informationFrequencyin minutes

Family

ESXservers, virtualmachines, and their storagedependencies.

Note: This information is discovered only when the ControlHostAdd-on is installed on amanagedhost that is designatedas the control host.

360VMware

The following information on the hosts that are configuredon the control host for agentless:

■ The IP addresses, operating system, and the usage of theCPU and memory

■ The host bus adapters (HBAs) on the host

■ The disks on the hosts and their correlationwith the arrayLUNs and multipathing

■ The volumes and the volumegroups on thenativeVolumeManager

■ The mount points of the file systems and the correlationof the file systems with the disks

■ In a VMware guest environment, the correlation of theguest with the virtual machine and the correlation of thestorage in the guest with the storage exported from theESX server.

Note: This information is discovered only when the ControlHostAdd-on is installed on amanagedhost that is designatedas the control host.

360Agentless

Note:Thediscovery for the Storage Foundation andVeritas Cluster Server familiesis event driven and scheduled. This means that the discovery is triggered whenconfiguration changes occur on the managed hosts. As a result, this informationmust be updated in the Veritas Operations Manager database in the followingupdate. If configuration changes are not detected on the managed hosts, thecommunication between the managed host and Management Server is restrictedto the heartbeat communication that occurs every five minutes. You can connectamanaged host tomultipleManagement Servers. The performance of amanagedhost is not affected in this scenario because the discovery happens only once.Reporting of the state as per the host configuration is done based on the numberof Management Servers to which the managed host reports.



About space estimation for data logsIn Veritas OperationsManager, historical performance data of various resourcesis collected in a fixed-size binary file. The older data is overwritten as new dataarrives in a circular round robin array. The number of metrics, frequency of datainsertion, number of objects, and the roll-up databases affect the size of binaryfile. The higher resolution data is compressed to a lower resolution data.

For more information on performance metering statistics, see the VeritasOperations Manager Management Server Administrator's Guide.

Table 2-3 describes the space estimation for data logs for the various resources.For estimationpurposes, the data in theNumber of resources column is accordingto the standard environment. Themetrics collected columnrepresents thenumberof metrics collected for each resource. For example, in case of DMP paths, thetotal number of metrics collected is four: bytes read, bytes written, read average,and write average.

Data logs for host, DMP (path, controller, enclosure), volume, disk and file systemare stored on the managed host. The data logs for VMware host, VxDMP (path,controller, enclosure) are stored on the Control Host. For storage array (port,controller, enclosure), data log for 1 day is stored on the discovery host, where asall the other logs are stored on Management Server.

Table 2-3 Space estimation for data logs

Size in KBfor asingleobject

Size in KBDurationofcollection

Interval ofcollection

Metricscollected

Numberofresources

Name ofresource

24241 day5 minutes51Host,VMwareESXserver,andVirtualMachine

29291 month2 hours51

30301 year1 day51

19189671 day5 minutes41000Multipathingpaths

24234771 month2 hours41000

431711 day5 minutes94Initiator


1074281 year1 day184

System requirementsSystem resource requirements

36

Table 2-3 Space estimation for data logs (continued)

Size in KBfor asingleobject

Size in KBDurationofcollection

Interval ofcollection

Metricscollected

Numberofresources

Name ofresource

19761 day5 minutes44Enclosure

281 month2 hours84

461901 year1 day84

1414231 day5 minutes3100File system

1817841 year1 day3100

2323486 hours1 minute4100VxVMVolume

1918981 day5 minutes4100


2423791 year1 day4100

2323486 hours1 minute4100VxVMDisk

1918981 day5 minutes4100


2323791 year1 day4100

93041 day30 minutes232Storagearray -Array port 237511 month2 hours432

247611 year1 day432

9761 day30 minutes28Storagearray -Adapter 231881 month2 hours48

241901 year1 day48

551 day30 minutes11Storagearray-Enclosure 12121 month2 hours21

12121 year1 day21


Note: IfVeritasOperationsManager is configured inhighavailability environment,storage array port, controller, and enclosure logs are saved on a shared disk. IfControl Host Add-on 5.0 is installed on Management Server, then, VMware ESXserver and virtual machines logs are saved on a shared disk.

Supported hardwareThe followingTechNotes contain theHardwareCompatibility List (HCL) forVeritasOperations Manager 5.0 and Storage Foundation products on UNIX:

■ Storage Foundation 5.0 for UNIX:http://www.symantec.com/business/support/index?page=content&id=TECH47620



The followingTechNotes contain theHardwareCompatibility List (HCL) forVeritasOperations Manager 5.0 and Storage Foundation products on Windows:

■ Storage Foundation 5.0 for Windows:http://www.symantec.com/business/support/index?page=content&id=TECH50141





Web browser requirementsTheVeritasOperationsManager console is a graphical user interface that displaysreports and other information for users of the Storage Foundation productsthrough a standard Web browser.

The Web browsers that the Veritas Operations Manager console supports are:

■ Internet Explorer versions 6.x to 9.x

■ Firefox 3.x, or later

Additional considerations for supported Web browsers:

System requirementsSupported hardware

38

http://www.symantec.com/business/support/index?page=content&id=TECH47620






■ Your browser must support JavaScript 1.2, or later.

■ If you use pop-up blockers (includingYahooToolbar orGoogle Toolbar), eitherdisable themor configure them to accept pop-ups from theVeritasOperationsManager Web server to which you connect.

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

■ For Internet Explorer, when popup-blocker is turned on, make sure that thefilter level is set to Medium or lower.

■ For Internet Explorer, ensure that the site is incuded in the list of trusted sites.If you cannot add the site to the list of trusted sites, enable the Binary andscript Behaviors option in security settings.

■ You must install Adobe Flash plug-in version 10, or later.

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

■ The Web console host must be able to access Veritas Operations ManagerManagement Server.

■ Veritas Operations Manager must support the Web browser.



Network and firewall requirementsIf you are managing hosts within multiple domains, update the network settingsto resolve the host from all domains.

You need to ensure that the localhost can be resolved from the host.

If localhost cannot be resolved from the host, update your network settings toenable it.

For Veritas Operations Manager Management Server HA, you need to configurefirewall settings for both the virtual and the physical IP of all cluster nodes.

VeritasOperationsManageruses thedefault ports as shown inTable 2-4 to transferinformation.

39System requirementsNetwork and firewall requirements

Table 2-4 Default ports in a Veritas Operations Manager installation

Effect if blockedPurposeInitiatorProtocolPort

Managed hostcannot be addedto theManagementServer domain

ManagementServercommunicationswith themanagedhosts

ManagementServer

TCP5634

Managed hostcannot be addedto theManagementServer domain

Managed host tosend heartbeats;also used toupload the datafromthemanagedhost toManagementServer

Note: It isrecommendedthat youkeepport5634 openbetweenmanagedhosts forscalability andperformanceoptimization.

managed hosts

Users cannotaccess the Webconsole

Run the VeritasOperationsManager console

Web consoleTCP14161



About the consumption of the managed hostcomponents

The managed host components of Veritas Operations Manager consume certainamount of CPU, memory, and network bandwidth for various functions.

Various processes and services in Veritas Operations Manager impose differentamount of load on the managed hosts. The processes and services and theirconsumption on the managed host are as follows:

System requirementsAbout the consumption of the managed host components

40

■ UNIX -Uses theXPRTLD,VXDCLID, sfmh-discovery.pl daemons. TheCPUandthe memory consumption for these daemons is minimal on a managed host.

■ Windows - Uses the XPRTLD daemon. The CPU and thememory consumptionfor this daemon is minimal on a managed host.

■ Discovery - The discovery in Veritas Operations Manager is ephemeral.Therefore, theCPUand thememory consumption for thediscovery isminimalon a managed host.

The network bandwidth consumption for the managed hosts is primarily relatedto the heartbeats that occur every five minutes. The heartbeat operation sendsdata that has a size of less than 1KB to Management Server. The data reportingoccurs only if there is a configuration change on the storage objects that areassociated to the managed host. Certain amount of network bandwidth is alsoused for the data replication.

See “About the frequency of managed host information discovery” on page 34.

41System requirementsAbout the consumption of the managed host components

System requirementsAbout the consumption of the managed host components

42

Software limitations


■ VeritasOperationsManager5.0managedhostnot supportedonAIX inNetworkInstallation Manager

■ No coexistence of managed host and CommandCentral Storage ManagementServer

■ Live statistics for initiators are not supported on HP-UX (2001078)

■ No support for creating large file systems on HP-UX managed hosts using theprebundled Add-on for Storage Foundation Administration (2858041)

■ Performance charts are not supported in certain cases for multiple objectsthat belong to different hosts (2023666)

■ Performance graphs cannot be viewed for Windows managed hosts

■ Volume layout not discovered for LDM-managed volumes mounted without adrive letter

■ Backup and restore limitations in Veritas Operations Manager 5.0

■ Veritas Operations Manager does not support the discovery of LDoms andZones together on the same host (2281088)

■ Veritas Operations Manager Add-on for Storage Foundation Administration5.0 limitations

■ Deployment-related limitations

■ Windows Management Server high availability configuration limitations

■ Solaris Zones virtualization support limitations

■ Discovery limitations for virtualization support

3Chapter

■ Log on to console fails on Internet Explorer if Management Server host namehas the underscore (_) character

■ VCS configuration check reports violations only if at least one node in thecluster is running Veritas Cluster Server (2117417)

■ Limitations related to the correlation between the disks and the disk groups

■ No support to online and offline multiple virtual machines using the VirtualBusiness Service start and stop operations (2177421)

■ Virtual Business Service start operation does not validate the service group'sresource criticality (2169223)

■ Discovery of VMware VirtualCenter server or ESX server is not case–sensitive(2567318)

■ Core density may not get calculated properly on HP-UX11iv2 hosts

■ Tier information is not displayed for some devices in a FASTmanaged storagegroup (2795204)

■ IBM System Storage DS enclosure discovery is not supported throughHiCommand Server 7 in Veritas Operations Manager (2708346)

■ Correlation between NAS file system and Storage Pools is not displayed forEMC VNX storage enclosures (2804423)

■ CIFS shares from NetApp and Celerra arrays that are mapped to a Windowshost are not discovered (2752493)

■ Performance chartsmay not be displayed for EMC Symmetrix array ports andadapters

■ Inconsistency in storage calculation is observed for unclaimedVPLEX extents(2844028)

Veritas Operations Manager 5.0 managed host notsupported on AIX in Network Installation Manager

InstallationofVeritasOperationsManager 5.0managedhost onAIXusingNetworkInstallation Manager (NIM) is not supported.

Software limitationsVeritas Operations Manager 5.0 managed host not supported on AIX in Network Installation Manager

44

No coexistence of managed host andCommandCentral Storage Management Server

Do not install Veritas Operations Manager managed host on a host that hasCommandCentral Storage Management Server installed on it. Even if theinstallation succeeds, the operation to add the host to the Management Serverdomain fails.

Live statistics for initiators are not supported onHP-UX (2001078)

You cannot view live statistics for initiators in the performance charts on theHP-UX hosts that have Veritas Volume Manager 5.0, or earlier releases.

No support for creating large file systems on HP-UXmanaged hosts using the prebundled Add-on forStorage Foundation Administration (2858041)

In Veritas OperationsManager 5.0, you cannot create a file systemwith a file sizegreater than 2 GB on an HP-UX managed host using the prebundled Add-on forStorage Foundation Administration.

To create a file system with a file size greater than 2 GB on an HP-UX managedhost, use the Administer link on the view for the host. This link is activated onlyif you have installed and enabledVeritas OperationsManager Add-on for StorageFoundation Administration for Active Administration of UNIX hosts.

Performance charts arenot supported in certain casesfor multiple objects that belong to different hosts(2023666)

Performance charts are not supported formultiple disks, volumes, or file systemsthat belong to different hosts that are not shared as part of a CVM/CFSconfiguration. However, you can view performance charts for multiple disks,volumes, or file systems fromdifferent hosts that are shared as part of a CVM/CFSconfiguration.

45Software limitationsNo coexistence of managed host and CommandCentral Storage Management Server

Performance charts are also not supported for multiple initiators that belong todifferent hosts. However, you can viewperformance charts formultiple initiatorsfrom the same host.

Performance graphs cannot be viewed for Windowsmanaged hosts

InVeritasOperationsManager, you cannot viewperformance graphs forWindowsmanaged hosts.

Volume layout not discovered for LDM-managedvolumes mounted without a drive letter

Veritas OperationsManager does not discover the layout for the volumes that aremounted without a drive letter on a Windows host (that does not have StorageFoundation for Windows installed on it) when the volume manager type isMicrosoft LDM. As a result, the Layout column for this volume is displayed asUnknown on the Veritas Operations Manager console.

Backup and restore limitations in Veritas OperationsManager 5.0

On UNIX, the vom_bkup.pl backup script cannot be used to back up and restorean existing Management Server in high-availability configuration for disasterrecovery.

OnWindows, the vom_bkup.pl backup script can backup an existingManagementServer in high-availability configuration. However, you cannot use the backupscript to restore the high-availability configuration. This feature is currently notsupported. To restore the backed up data, contact Symantec Technical Support.

Veritas Operations Manager does not support thediscovery of LDoms and Zones together on the samehost (2281088)

Veritas Operations Manager does not support the discovery of LDoms and Zonesif they co-exist on the sameSolaris host. In a configurationwhere both the LDomsand the Zones co-exist, Veritas Operations Manager discovers LDoms.

Software limitationsPerformance graphs cannot be viewed for Windows managed hosts

46

Veritas Operations Manager Add-on for StorageFoundation Administration 5.0 limitations

The Storage Foundation operations that you can perform using the VeritasOperations Manager Add-on for Storage Foundation Administration are notsupported on the managed hosts that have the VRTSsfmh package versions lowerthan 4.0.

The Veritas Operations Manager Add-on for Storage Foundation Administrationdoes not support all the Storage Foundation operations. For the list of supportedoperations, refer to theVeritas OperationsManagerManagement Server Add-onsUser's Guide.

Deployment-related limitationsYou cannot upgrade Veritas Operations Manager Management Server fromversions prior to 3.1 to version 5.0.

For upgrading from versions prior to 3.1, do one of the following:

■ Upgrade to version 3.1 or 4.x, and then to version 5.0.

■ Remove your previous installation and perform a fresh installation of VeritasOperations Manager 5.0. You need to reconfigure all your existing managedhosts to the new Management Server installation.

Windows Management Server high availabilityconfiguration limitations

Veritas Operations Manager supports only the Windows Server versions 2008(64-bit) and 2008 R2 (64-bit) for configuring theWindowsManagement Server inhigh availability environment.

Veritas Operations Manager does not support configuring the disaster recoveryfeature on a Windows Management Server high availability configuration.

Solaris Zones virtualization support limitationsYoumust install the VRTSsfmh package on the Global Zone. You cannot install theVRTSsfmh package on the non-Global Zones.

Solaris Zones virtualization inVeritasOperationsManager doesnot support slices.Veritas Operations Manager supports only full disks.

47Software limitationsVeritas Operations Manager Add-on for Storage Foundation Administration 5.0 limitations

Solaris Zones virtualization in Veritas Operations Manager does not supportdiscovery of secure Oracle, DB2, and Sybase database instances running in thenon-Global Zones.

Discovery limitations for virtualization supportVeritas Operations Manager has the following discovery limitations forvirtualization support:

■ Veritas Operations Manager does not support storage discovery for the LinuxKernel Virtual Machine (KVM) environment.

■ Forvirtualizationenvironments likeKVM,LDOM,andLPAR,VeritasOperationsManager displays only the Power ON state of a virtual machine.

■ For the Linux-based LPAR guest virtual machines that are configured on anLPARserver,which is in turnmanagedby anHMCserver, the operating systemand the operating system version are not discovered.

Log on to console fails on Internet Explorer ifManagement Server host name has the underscore(_) character

When you install or upgrade Management Server to 5.0 on a Windows 2003 host,and attempt to log on to the console using Internet Explorer, the log on may fail.The failure occurs if the console is launched using the Management Server hostname, and the host name contains the underscore (_) character.

Internet Explorer does not allow the underscore (_) character in the host name.Do not install Management Server on such a host.

VCS configuration check reports violations only if atleast onenode in the cluster is runningVeritas ClusterServer (2117417)

VCS configuration policy check in Veritas Operations Manager does not reportany violations if Veritas Cluster Server is not running on any of the systems inthe cluster. Also, if the cluster has a single system and Veritas Cluster Server isnot runningon that system, theVCSconfiguration checkdoesnot report violations.

Software limitationsDiscovery limitations for virtualization support

48

Limitations related to the correlation between thedisks and the disk groups

The following limitations exist in Veritas Operations Manager 5.0, which arerelated to the correlation between the disks and the disk groups:

■ You cannot view the disk information in the file system details view, or in thedisk group details view, when one partition of a disk contains a file systemthat is mounted on it, and the other partition belongs to a disk group.

■ You cannot view the disk information in the details view of one of the diskgroups, when two partitions of a disk belong to two disk groups.

No support to online and offline multiple virtualmachines using theVirtual Business Service start andstop operations (2177421)

This issue is applicable to the hybrid service groups and parallel service groupsthat are configured on the virtual machines in a Virtual Business Service (VBS).For the VBS start and stop operations, the VBS Availability Add-on does not startor stopmultiple virtual machines. You can online or offline the service groups onall systems. However, you cannot start or stop all virtual machines. Currently,the VBS Availability Add-on is not intended to start or stop multiple virtualmachines.

Virtual Business Service start operation does notvalidate the service group's resource criticality(2169223)

Using VBS Availability Add-on, when you start a Virtual Business Service (VBS),the start operationdoesnot validatewhether the service grouphas anynon-criticalresource. So, the operation does not detect any fault that occurs while bringingthese resources online, nor does it detect if such resources are already faultedwhen the VBS start is attempted. If such faults exist, Veritas OperationsManagerwaits for the VBS to start completely, and, eventually times out aborting the VBSstart operation. You can choose to abort the operation. As a preventive step,configure all the resources of a service group as critical.

49Software limitationsLimitations related to the correlation between the disks and the disk groups

Discovery of VMware VirtualCenter server or ESXserver is not case–sensitive (2567318)

While discoveringVMwareVirtualCenter server or ESX server, VeritasOperationsManager cannot distinguish between twoormore virtual diskswhosenamesdifferonly in case. Only one of such disks is discovered in Veritas Operations Manager.

Core density may not get calculated properly onHP-UX11iv2 hosts

Core density(#cores/physical processor) discovered on HP-UX 11.23 managedhosts may not be correct due to CLI-related limitations. Incorrect value of coredensity makes the LDR unable to calculate Symantec Performance Value Unit(SPVU) information for such hosts. The user can assign the SPVU manually forthe hosts.

Tier information is not displayed for some devices ina FAST managed storage group (2795204)

In a FAST managed storage group for an EMC Symmetrix VMAX enclosure, thetier information is not displayed for devices that are not part of the tiers associatedto the policy of that storage group. In the FAST Managed Devices view for thestorage group, theVendorTierName is displayed asOutOfPolicy, and theVendorTier Type and the Tier Protection are displayed as Unknown.

IBM System Storage DS enclosure discovery is notsupported through HiCommand Server 7 in VeritasOperations Manager (2708346)

Hitachi HiCommand Server supports the management and discovery of a varietyof array vendors, and models including IBM System Storage DS arrays. However,Veritas Operations Manager 5.0 does not discover IBM System Storage DSenclosures using HiCommand Server 7.

Software limitationsDiscovery of VMware VirtualCenter server or ESX server is not case–sensitive (2567318)

50

Correlation between NAS file system and StoragePools is not displayed for EMCVNXstorageenclosures(2804423)

For the EMC VNX storage enclosure, Veritas Operations Manager does not showthe correlation between the NAS Filesystem and Storage Pools, and vice versa.

CIFS shares from NetApp and Celerra arrays that aremapped to a Windows host are not discovered(2752493)

Veritas Operations Manager does not discover Common Internet File System(CIFS) shares from NetApp and Celerra arrays, that are mapped to a Windowshost by a non-system account user.

Performance charts may not be displayed for EMCSymmetrix array ports and adapters

Since SYMCLI reports point-in-time statistics samples for EMC Symmetrix arrayports and adapters, if an array port or an adapter is not serving IO during thestatistics collection then, the performance charts for these objects may not bedisplayed. The message “Performance statistics is not available” is displayed.

Inconsistency in storage calculation is observed forunclaimed VPLEX extents (2844028)

This issue is observed forEMCVPLEXenclosures that are configuredusingStorageInsight Add-on. If there are any unclaimed VPLEX extents, you might observe adiscrepancy between the Physical Un-configured data reported by the waterfallchart, and the used capacity reported under the Storage Volumes tab of VPLEXnode. The discrepancy is not present if the extents are used by any VPLEX device.

51Software limitationsCorrelation between NAS file system and Storage Pools is not displayed for EMC VNX storage enclosures (2804423)

Software limitationsInconsistency in storage calculation is observed for unclaimed VPLEX extents (2844028)

52

Known issues


■ Management Server issues

■ Managed host issues

■ Agentless discovery issues

■ Storage Provisioning Add-on issues

■ Storage Insight Add-on issues

■ VBS Availability Add-on issues

■ Scripting Add-on issues

■ Storage Insight SDK Add-on issues

■ LDom Capacity Management Add-on issues

■ Other issues

Management Server issuesThe following issues relate to Veritas Operations Manager Management Server.

Delayed discovery of VMware VirtualCenter server by Control Hostsin Veritas Operations Manager (2342314)

InVeritasOperationsManager, thediscoveryof someof theVMwareVirtualCenterservers using Control Hosts takes a long time to complete. This issue occursbecause some of the datastores that are associated with the VirtualCenter serverdo not respond on time, which results in timeout.

4Chapter

Workaround:

From the VMware SDK log, you can identify the datastores that cause the delayin the discovery ofVirtualCenter server. In theVirtualCenter server that containsthe datastore, navigate toAdministration>vServerSettings>TimeoutSettingsand set the timeout to a lower value.

Log on to the Veritas Operations Manager console may fail on Firefox(1939352)

When you try to log on to theVeritas OperationsManager console on Firefox, youmay get the following error:

Secure Connection Failed

An error occurred during a connection to <system>

Peer reports it experienced an internal error.

(Error code: ssl_error_internal_error_alert)

Workaround:

Perform any one of the following modifications on the configuration settings forFirefox:

■ Disable TLS

■ Enable SSL 2 encryption protocols

To disable TLS in Firefox

1 In Firefox, select Tools > Options.

2 In the Options dialog box, click Advanced.

3 In theAdvancedpanel, under theEncryption tab, clear theUseTLS1.0 checkbox.

To enable SSL 2 encryption protocols in Firefox

1 In Firefox, in the address bar, type about:config and press Enter.

2 On this page, use Filter to search for the security.enable_ssl2 setting.

3 Select the security.enable_ssl2 setting and do one of the following to setthe value to true:

■ Double-click the security.enable_ssl2 setting.

■ Right-click the security.enable_ssl2 setting and then click Toggle.

4 Restart Firefox.

Known issuesManagement Server issues

54

Authentication broker crashes while performing LDAP authentication(2017319)

On a host in which LDAP is configured with PAM and TLS is enabled, theauthentication broker may crash while performing LDAP authentication.

Workaround:

Perform the following changes.

■ Disable start_tls.

■ Remove PAM from authsequence.

To disable the start_tls parameter

◆ In the /etc/ldap.conf file, after ssl start_tls add the following line:

ssl no

To remove PAM from authsequence

◆ In the EAT_DATA_DIR/root/.VRTSat/profile/VRTSatlocal.conf file, deletepam from the following entry:

"DefaultAuthSequence"="pam unixpwd nis nisplus"

XPRTLD daemon fails when Veritas Operations Manager starts becauseof the corrupt AT pem files in the VRTSsfmh package (2145925)

TheXPRTLDdaemon failswhenVeritasOperationsManager starts, if theATpemfiles (the certificate files in the VRTSsfmh package) is corrupt.

Workaround:

To repair the corrupt AT pem files on UNIX:

1 Stop the XPRTLD daemon by using the following command:

/opt/VRTSsfmh/adm/xprtldctrl stop

2 Delete all the files in the directory /var/VRTSat_lhc/ by using the followingcommand :

rm -rf /var/VRTSat_lhc/*

3 Take a backup of the credentials in the/var/VRTSat/.VRTSat/profile/certstore/directory, byusing the followingcommand:

mv /var/VRTSat/.VRTSat/profile/certstore/*.0 /tmp/backupcreds/

55Known issuesManagement Server issues

4 In the directory, delete the pem files by using the following commands:

■ rm

/var/VRTSat/.VRTSat/profile/certstore/keystore/PubKeyFile.pem

■ rm

/var/VRTSat/.VRTSat/profile/certstore/keystore/PrivKeyFile.pem

5 Restart any running shared broker process by using the following command:

/opt/VRTSat/bin/vxatd

6 Authenticate the local host to create a self-signed certificate by using thefollowing commands:

export EAT_HOME_DIR=/opt/VRTSsfmh

export EAT_DATA_DIR=/var/opt/VRTSsfmh/sec

cd $EAT_HOME_DIR/bin

./vssat authenticate -d localhost

7 Start the XPRTLD daemon by using the following command:

/opt/VRTSsfmh/adm/xprtldctrl start

To repair the corrupt AT pem files on Windows:

1 Stop the XPRTLD daemon by using the following command:

net stop xprtld

2 Delete all the files in the following directory:

%ALLUSERSPROFILE%\Application

Data\VERITAS\Security\Authentication\VRTSat_lhc

3 Take a backup of the credential in the following directory:

AT_PROFILE_DIR\certstore\* c:\temp\*

You can get the AT Profile directory from the following locations:

■ For 64-bit Windows:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VERITAS\Security\Authentication\Credential

Manager\Profiles\SYSTEM\ ProfileDir

■ For 32-bit Windows:HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\Security\Authentication\Credential

Manager\Profiles\SYSTEM\ProfileDir

4 Delete the following pem files:

■ AT_PROFILE_DIR\certstore\keystore\PubKeyFile.pem


56

■ AT_PROFILE_DIR\certstore\keystore\PrivKeyFile.pem

5 Restart any running shared broker process by using the following commands:

■ sc stop vrtsat

■ sc start vrtsat

6 Authenticate the local host to create a self-signed certificate by using thefollowing commands:

set EAT_HOME_DIR=%PROGRAMFILES%\VERITAS\VRTSsfmh

set EAT_DATA_DIR=%ALLUSERSPROFILE%\Symantec\VRTSsfmh\sec

cd %EAT_HOME_DIR%\bin

vssat authenticate -d localhost

7 Start the XPRTLD daemon by using the following command:

net start xprtld

Status of all SF Manager 2.x hosts is shown as healthy on an upgradedVeritas Operations Manager 5.0 setup (2009372)

When you view the status of hosts on an upgraded Veritas Operations Manager5.0 console that has SF Manager 2.xmanaged hosts, the status of all the hosts isshown as healthy even though some of the hosts have reported faults.

Workaround:

You need to upgrade the 2.xmanaged hosts to Veritas Operations Manager 5.0and then clean up the 2.x faults.

To clean up the 2.x faults

1 Create a file a.sql that has the following contents:

call HABDBSYNC.SP_ccsf_db_cleanup_21_faults();

2 Run the following:

export LD_LIBRARY_PATH=/opt/VRTSsfmcs/asa11/lib32:$LD_LIBRARY_PATH

/opt/VRTSsfmh/bin/xdbadm -f ./a.sql -c /var/opt/VRTSsfmcs/conf -o

/etc/vx/VRTSsfmcs/.odbc.ini -d SFMdb3 -v


Uninstalling Management Server removes the managed host packagefrom a Storage Foundation for Windows host

When you uninstall Veritas Operations Manager Management Server from aStorage Foundation for Windows host, the managed host package is removedfrom thehost. So, you cannot add thehost to anotherManagement Server domain.

Workaround:

Install Veritas Operations Manager host management on the host. Afterinstallation, you can add the host to a Management Server domain.

Upgrade of Management Server in High Availability environment failswith database upgrade errors (2853154)

When you upgrade Management Server in High Availability environment toVeritasOperationsManager 5.0, the upgrademay fail with errors related to faileddatabase upgrade. The issue occurs when the SFM_Services service group freezeis delayed, which in turn takes the SFM_Services_Mount resource offline.

Workaround:

You need to perform the following tasks and restart the upgrade:

■ Clear the faults on SFM_Services and SFM_Xprtld service groups.

■ Unfreeze SFM_Services, SFM_Xprtld and SFM_SStore service groups.

■ Bring the SFM_Services, SFM_Xprtld and SFM_SStore service groups online.

■ Freeze SFM_Services service group. Make sure the freeze is complete beforeyou restart the upgrade.

To clear the faults on service groups and freeze the SFM_Services service group

1 In theVeritasOperationsManager console, selectManage>ServiceGroups.

2 Select SFM_Services and SFM_Xprtld service groups. Click Actions abovethe service groups list and select Clear Fault.

3 In the Clear Fault for Service Groups page, click OK to confirm the action.

4 In the Result page, verify that the operation was successful. Click OK.

5 Select the SFM_Services, SFM_Xprtd, and SFM_SStore service groups. ClickActions above the service groups list and select Unfreeze.

In the Unfreeze Service Group page, click OK to confirm the action.


7 Select the SFM_Services, SFM_Xprtd, and SFM_SStore service groups. ClickActions above the service groups list and select Online.


58

8 In the Online Service Groups page, click OK to confirm the action.


10 Select the SFM_Services service group. ClickActions above the service groupslist and select Freeze.

11 In the Freeze Service Group page, click OK to confirm the action.


Veritas Operations Manager displays stale application status (2564572)This issue occurs with the virtual machines where Symantec ApplicationHA isconfigured to monitor applications. In ApplicationHA, if the virtual machineauto-recovery is configured, the virtual machine is restored if the applicationbeing monitored fails to start after a configurable number of attempts. If thevirtual machine auto-recovery is triggered, the last successful virtual machinesnapshot is restored from the backup. It also restores the applications runningon the virtual machine. However, Veritas Operations Manager fails to discoverthe restored application status, and continues to display the application as faulted.

Workaround:

To display the current application status, refresh theVeritasOperationsManagerconsole.

Mountpoint may appear as garbled characters, if encoding is notsupported (2377238)

For Japanese locale, Veritas Operations Manager supports discovery in threenative encodings: shiftjis on Windows, eucJP on UNIX, and utf8 on UNIX. If themountpoint is created using any other encoding, Veritas Operations Managercannot discover it properly and themountpointmay appear as garbled charactersin the Veritas Operations Manager console.

Manual refresh of HMC server and VMware VirtualCenter serverrequired after migration of virtual machines (2605533)

This issue is applicable to VMware vCenter Server and HMC configurations inVeritas Operations Manager. It is observed when you migrate a VMware virtualmachine from one ESX server to another ESX server (both servers are under thesameVMware vCenter Server), or an LPARvirtualmachine fromone LPAR serverto another LPAR Server (both LPAR servers are under same HMC).


Post migration, the changes are not reflected immediately on Veritas OperationsManager console. The changes are reflected only after the scheduled automaticscan is performed.

Workaround:

You need to manually refresh the configuration to see the changes.

To manually refresh the configuration:

1 Go to Settings > Virtualization.

2 Select the HMC server or VMware VirtualCenter server.

3 Click Actions > Refresh Configuration.

Microsoft Exchange Server 2007 to VCS service group correlation isnot present in the first discovery cycle of Veritas Operations Manager(2604162)

In the first discovery cycle ofVeritasOperationsManager, the correlation betweenthe Microsoft Exchange Server and the VCS service group is not complete, andno data is available.

Workaround:

Two options are available to resolve the issue:

■ Perform the host refresh from the Veritas OperationsManager console. Here,the managed host has VCS and Exchange Server installed on it.

■ Wait until the next discovery cycle, which is approximately six hours.

Coexistence of ApplicationHA Console and Veritas Operations ManagerManagement Server in the ApplicationHA Console upgrade scenario(2581661)

This issue is observed for the coexistence scenario of ApplicationHA Console(SymantecApplicationHA5.1 SP2or SymantecApplicationHA6.0) and theVeritasOperations Manager Management Server version 3.1.x. When you upgrade theApplicationHA console, the VRTSsfmh package is also upgraded. As a result, thereis a version mismatch between the VRTSsfmh package and VRTSsfmcs package.Since the VRTSsfmcs package is at a lower version, it is incompatible with theVRTSsfmh package. This results in broken functionality of Veritas OperationsManager Management Server.

Workaround:


60

You need to upgrade Veritas Operations ManagerManagement Server to version4.0 RU1, or later.

Performance metering of a VMware ESX server may not work properlyafter failover (2814844)

If Management Server is configured in high availability environment, and ifControl Host Add-on is installed then, performance metering of VMware ESXserver may not work properly after failover, until the next discovery cycle.

The following may occur until the next discovery cycle:

■ Performance metering does not start for the VMware ESX server.

■ Performance charts for which the duration is selected as Live, do not showany information.

■ Incorrect error messages may be displayed in the performance chart.

Workaround:

You need to manually refresh the VMware ESX server discovery.

To manually refresh the VMware ESX server discovery

1 In the Veritas OperationsManager console, select Settings > Virtualization.

2 In the Virtualization Management view, select the VMware ESX server andclick Actions > Refresh Configuration.

3 In the Refresh Virtualization Configuration wizard panel, review theconfirmation message and click OK.

Management Server cannot be configured on a Windows host withRussian locale (2676438)

On a host that has Windows Server 2008 or Windows Server 2008 R2 installedwith Russian locale, you can install Management Server but cannot configure it.

Managed host issuesThe following issues relate to host management.

61Known issuesManaged host issues

Issue related to upgrading the managed hosts (from 3.x to 5.0) thathave LUNs from IBM XIV storage array (2367519)

This issue is related to all managed hosts having IBM XIV enclosure connected tothem.Whenyouupgrade themanagedhosts fromversion 3.x to 5.0, on theVeritasOperations Manager console, two entries are displayed for the same enclosure.The first entry is a dangling object, which has no association with any of theobjects. The other entry hasDisk, LUNs, array port , and the initiators associationssetup, and is reported correctly.

It is to protect the deletion information for the shared objects.

Workaround:

After upgrading the managed host to Veritas Operations Manager 5.0, thediscrepancy of dangling object is automatically cleaned up by the scheduled runof a stored procedure. It runs at 3:00 AM every morning on the ManagementServer.

Quick I/O cache value is not enabled after performing the storageprovisioning operation on AIX managed hosts (2131183)

If you use a VxFS file system-based storage provisioning template on which theQuick I/O cache (CQIQ) value is set as 'Yes' to provision storage on AIX managedhost, the storage provisioning operation is successfully completed. However,cache I/O does not get updated appropriately. The 'qio_cache_enable' value invxtunefs output remains '0'.

Workaround:

On AIX platform, the tune VxFS parameters are not set properly. You can use thevxtunefs from the managed node.

Cannot replace or recover a disk removed from a UNIX host (2317671)Using the Veritas Operations Manager Add-on for Storage FoundationAdministration, you can replace or recover a faulted disk. But, using this add-on,you cannot replace or recover a disk that is removed using the rmdisk commandon a UNIX host.

Workaround:

To replace or recover a disk that is removedusing the rmdisk commandonaUNIXhost, use the CLI, Veritas Enterprise Administrator console, or the Add-on forStorage Foundation Administration for UNIX.

Known issuesManaged host issues

62

After the replace disk operation, the faulted disk status remains asreplaceable (2353612)

In Veritas Operations Manager, after you perform Replace Disk operation, thefaulted disk status does not change. It still displays the state as in Use(Replaceable). The state will change if the disk is removed, or initialized.

Workaround:

Youneed touse the command-line interface (CLI), VeritasEnterpriseAdministratorconsole, or the Storage Foundation Administration for Unix Add-on to performthis operation.

Thin LUNs on the hosts that run Storage Foundation for Windows 5.1SP1 are not discovered as thin (2513466)

In Veritas Operations Manager, the thin LUNs on the hosts that run StorageFoundation for Windows version 5.1 SP1 are not discovered as thin.

Workaround:

Download the hot fix for Storage Foundation for Windows version 5.1 SP1 fromthe following location, and run it on the host:

https://sort.symantec.com/patch/detail/4697

After the successful installation, restart the host.

CPU count incorrect for managed hosts on Windows Server 2003(2437565)

The CPU count that is displayed for Windows Server 2003 managed hosts on theVeritas OperationsManager console, does notmatch the actual CPU count on thehost. The figure that is displayed is the count of cores andnot the count of physicalCPUs.

The issue occurs due to aWindows Server 2003 operating system issue. Formoreinformation, visit the Microsoft Web site.

http://support.microsoft.com/kb/932370

Remote switch operation fails between secure clusters (2530605 )If you try to switch global service groups between clusters, that are configured insecure mode, the operation fails and following error message is displayed:

VCS WARNING V-16-1-50824


https://sort.symantec.com/patch/detail/4697


Command (hagrp -switch servicegroupname

targetsystemname targetclustername failed

At least Group Operator

privilege required on remote cluster targetclustername

Workaround:

Veritas Operations Manager uses the Veritas Storage Foundation MessagingService to run Veritas Cluster Server commands. By default, this service runs inthe Local System account context. Configure this service to run in the DomainAdministrator account context and then perform the switch operation. Changethe service account on each of the managed hosts in the clusters.

To change the service account context:

1 Open the Windows Services MMC snap-in.

2 Right-click Veritas Storage Foundation Messaging Service and then clickProperties.

3 Click the Log On tab and do the following:

■ ClickThisaccount, clickBrowse, and in theSelectUserdialog box, specifya user account that has Domain Administrator privileges.

■ Click OK.

4 Type the user account password in the Password and Confirm passwordfields. Click OK.

5 Proceed with the service group operations.

Adding an agentless host to a Linux-based control host failsIf a control host is Linux-based and does not have the 32-bit libgcc packageinstalled on it, you cannot add agentless hosts to the control host.

Workaround:

Install the 32-bit libgcc package on the control host.

Add host operation fails for HP-UX managed hosts (2601265)In the Veritas Operations Manager, if you try to add the HP-UX managed hostthrough agent, sometimes the operation fails. The following error message isdisplayed:

CS host is not reachable from managed host.

Workaround:

Known issuesManaged host issues

64

Restart the XPRTLD process on the managed host that you want to add, and thenadd the host.

Some performance charts are not available for VMware ESX serverversion 4.1 managed through vCenter server 5.0 (2800239)

In Veritas Operations Manager Available Memory and Used Swap performancecharts are not available for VMware ESX server version 4.1, which is discoveredthrough the vCenter server version 5.0.

Cannot add a managed host to Management Server using the IPv6address of the host (2816487)

You cannot add a managed host to Management Server using the IPv6 address ofthe host.

Workaround:

Add the host to Management Server using its hostname.

Cannot add a Windows 2008 64-bit host that has both IPv4 and IPv6networks enabled to Management Server (2712982)

You cannot add aWindows 2008 64-bit host that has both IPv4 and IPv6networksenabled, to a Veritas OperationsManagerManagement Server domain. The issueoccurs when the TCP/IP ports of the host are in a TIME_WAIT status because ofa Windows operating system issue.

Workaround:

Download theWindows operating systemhot fix from the following location, andrun it on the host:


After the successful installation, restart thehost and add it toManagement Server.

Incorrect statistics returned by DMP if Storage Foundation version isprior to 5.0 MP3 (2796418)

The performance statistics returned by Dynamic Multipathing (DMP) paths isincorrect if Storage Foundation version is prior to 5.0 MP3 on a managed host.The I/Odisplayed in theBytesRead/Writtenperformance graphs for the initiator,multipathing path, and enclosure is greater than the actual I/O.



Incorrect name displayed for one performance graph for enclosures(2854125)

InVeritasOperationsManager, the name of theAverageBytesRead/WrittenforHostperformance graph for an enclosure is incorrect. The graph does not displayaverage bytes read and written for a host. It displays the bytes read and writtenfor a host.

Issues in the Add Host(s) wizard while adding agentless hosts toManagement Server domain (2856380)

In Veritas Operations Manager, in the Add Host(s) wizard for agentlessconfiguration, while adding virtual machines, following issues are encounteredin the Browse Virtual Machines panel:

■ If you select the check box that automatically selects all the virtual machineslisted in the panel, and click OK, the span tag details are displayed along withthe virtual machine name in the Host field in the Add Host(s) wizard panel.

■ An incomplete list of virtual machines is displayed.

Workaround:

You can manually remove the span tag that is appended to the virtual machinename in the Host field in the AddHost(s) wizard panel. Or, in the BrowseVirtualMachines panel, you can select each check box individually.

There is no workaround to view the complete list of virtual machines.

Agentless discovery issuesThe following issues relate to the agentless discovery of hosts.

Agentless configuration of hosts using IPv6 addresses fails (2414252)Configuration of agentless hosts using IPv6 addresses does not work. You mustspecify thehost nameor IPv4 address of thehost that youwant to configure usingagentless discovery.

Agentless configuration of Windows hosts running non-English localefails (2484139)

If you configure aWindowshost using agentless discovery running anon-Englishlocale, the configuration fails with the "Failed to determine free space on theremote host" error message. You cannot configure Windows hosts running

Known issuesAgentless discovery issues

66

non-English locales using agentless discovery. These hosts must be configuredusing an agent.

Configuration fails for agentless host with user name containing DBCScharacters (2427619)

If you configure a host using agentless discovery that has a user name containingcharacters from Double Byte Character Set (DBCS), the configuration fails. Thisgenerally occurs with user names for locales other than English.

fstab information displayed incorrectly for file systems on Linuxagentless host (2418023)

Information about whether file systems are in fstab is displayed incorrectly forLinux hosts configured using agentless discovery.

Agentless discovery fails if a host has volume names, mount pointnames, or disk label names that contain equals(=) sign(2590669)

Agentless discovery of Windows hosts fails if a host has disk label name, volumename, or file systemmount point name containing equals sign(=). If you configuresuch hosts for agentless discovery in Veritas Operations Manager, no disks,volumes and file systems information is reported for such hosts.

Workaround:

To fix this issue:

1 Change the names of such volumes, mount points, or disk labels to removethe '=' sign.

2 Remove such hosts from Veritas Operations Manager.

3 Re-configure the agentless discovery of the host.

Volume group and logical volume information can be inconsistent, ifVolume group is created on shared disks (2567056)

If volume group of a Logical VolumeManager is created on the disk, that is sharedon multiple hosts, the Volume group and Logical volume is accessible to all thehosts. As a result, the last configured or discoveredHost overwrites the propertiesof the volume group and logical volume .

67Known issuesAgentless discovery issues

Failed EMC PowerPath paths are not displayed for agentless Windows2008 hosts (2611064)

On the Paths tab for a disk's view, the failed EMC PowerPath paths are notdisplayed for agentless Windows 2008 hosts. Only the paths that are enabled areshown.

Storage Provisioning Add-on issuesThe following issues relate to the Storage Provisioning Add-on.

A volume is migrated to any available enclosure if no target array isspecified (2143010)

If you do not specify the enclosure while performing the volume migrationoperation, the view that lists the status of volume migrations displays no valuein the Target array column. However, the volume migration task is performedsuccessfully by selecting any available enclosure.

Storage Insight Add-on issuesThe following issues relate to the Storage Insight Add-on.

The vxlist utility does not display the information on the physical disksfor the LUNs (2219286)

If a LUN is masked to the host that is added to multiple Management Servers, thevxlist -l lun commandon the host does not get the information on the physicaldisks (PDEVs).

Cannot configure an EMC CLARiiON enclosure on a Windows controlhost using a security file (2221574)

You cannot configure an EMC CLARiiON enclosure on a Windows control hostusing a security file.

Workaround:

To configure an EMC CLARiiON using a security file, choose a UNIX control hostinstead of a Windows control host.

Known issuesStorage Provisioning Add-on issues

68

NetApp enclosures are not discovered after the Storage Insight Add-onis upgraded to version 5.0

TheNetApp enclosures that are configured using Storage Insight Add-on version4.x are not discovered after the add-on is upgraded to version 5.0.

Workaround:

Edit the configuration, and enable NAS discovery for NetApp enclosure.

OnVeritas OperationsManager console, navigate to Settings > Enclosure. Selectthe NetApp enclosure, and click Actions > Edit Device Configurations. On theConfigure Device panel, select the Enable NAS discovery checkbox.

Reports generated by pre-existing schedules display erroneous dataafter installing or upgrading to Storage Insight Add-on 5.0 (2823297)

InVeritasOperationsManager, after you install or upgrade to the Storage InsightAdd-on5.0, the pre-existing schedules for theAllEnclosures andAllLUNs reportscontinue to be active, but the reports that are generated display erroneous data.These pre-existing schedules are not displayed in theSchedules table in the reportview.

Workaround:

You need to manually disable the existing schedules and create new schedulesfor the All Enclosures and the All LUNs reports.

To disable and recreate schedules

1 In the Veritas Operations Manager console, click Settings > Schedules.

2 In the Schedules view, select the schedules that youwant to disable and clickActions > Delete.

3 In the subsequent wizard panels, review the details and click OK to disablethe schedules.

4 Click Reports. In the Reports view, identify the report for which you wantto create a schedule and click Schedule.

5 In the subsequentwizard panels, enter the details and clickFinish to recreatethe schedule.

Performance metering of enclosures may not work properly afterfailover (2814844)

If Management Server is configured in high availability environment, and if theenclosure is discovered through Storage Insight Add-on then, performance

69Known issuesStorage Insight Add-on issues

metering of the enclosure may not work properly after failover, until the nextdiscovery cycle.

The following may occur until the next discovery cycle:

■ Performance metering does not start for the enclosure.

■ Performance charts for which the duration is selected as Live, do not showany information.

■ Incorrect error messages may be displayed in the performance chart.

Workaround:

You need to manually refresh the enclosure discovery.

To manually refresh the enclosure discovery

1 In the Veritas Operations Manager console, select Manage > Enclosures.

2 In the Enclosures view, select the enclosure and click Actions > RefreshEnclosure.

3 In the Refresh Enclosure confirmantion panel, click OK.

Information on FAST managed storage groups for EMC SymmetrixVMAX enclosures is not discovered periodically (2842124)

When an EMC Symmetrix VMAX enclosure is configured using Storage InsightAdd-on, the storage distribution information for a FAST managed storage groupacross different FAST tiers,maynot get discovered aspart of theperiodic discoverycycle.

The information is discovered only if any add, remove, commit, resume, suspend,or split action has occurred on the following since the last discovery:

■ Snapshots

■ Configuration changes

■ Device masking

■ BCV

■ Clones

■ RDF

Workaround:

Refresh the enclosure from the Veritas Operations Manager console to view theupdated information for FAST managed storage groups.

Known issuesStorage Insight Add-on issues

70

To refresh the EMC Symmetrix VMAX enclosure


2 In the Enclosures view, select the EMC Symmetrix VMAX enclosure. ClickActions > Refresh Enclosure.

Array group information is incorrect in Enclosure Storage Summarychart for Hitachi arrays (2820150)

When you view the Enclosure Summary chart for Hitachi, the array group barmay extend beyond the physical bar. This issue occurs when you create arraygroups with shared physical devices (PDEVs).

Password file option does not work while configuring HP EVAenclosures on Windows hosts (2757601)

This issue is applicable to the deep array discovery of HP EVA enclosures usingStorage InsightAdd-on 5.0. OnWindowshostwhere the Storage Scripting SystemUtility (SSSU) CLI utility version is prior to 9.4, the password file option does notwork while configuring HP EVA enclosures.

Workaround:

Install SSSUCLI utility version 9.4, or later, on theWindowshost. Then, configurethe HP EVA enclosure, and use the password file option.

EMC Celerra enclosure details are not discovered for users withread-only access rights, and Imported Administrator or Operator role

This issue is applicable to the deep array discovery of EMCCelerra enclosure usingStorage Insight Add-on 5.0. If the user with read-only privilege, and ImportedAdministrator orOperator role, attempts to configure the enclosure, the enclosuredetails are not retrieved during the array discovery.

Workaround:

Assign the nasadmin role to the user.

71Known issuesStorage Insight Add-on issues

Network File System on Solaris cannot be discovered if the FullyQualified Host Name is used in vfstab file but not used for mountingthe file system (2747735)

If Network File System (NFS) on Solaris is mounted without providing the FullyQualified Host Name (FQHN) but the /etc/vfstab file contains FQHN, the NFSfile system cannot be discovered in Veritas Operations Manager 5.0.

VBS Availability Add-on issuesThe following issues relate to the Veritas OperationsManager Add-on for VirtualBusiness Services:

Veritas Operations Manager does not validate if the cluster node ismanaged by the Management Server during the VBS start operation(2566050)

When you perform the Virtual Business Service (VBS) start operation, VeritasOperations Manager does not check whether Management Server manages thecluster node. Veritas Operations Manager brings the service group online usingthe -any option on the available systems for that service group.

Workaround:

Although there is no functional loss, it is recommended that you add all the clusternodes to the Management Server domain.

Disabling fault management for Virtual Business Services does notdisplay the dependency as Soft in the console (2725638)

If the service group dependency for a Virtual Business Service is set to Firm orRestart, then disabling fault management changes the dependency to Soft.However, the dependency is still displayed as Firm or Restart in the console.

Workaround:

To display the correct dependency type, you need to reconfigure the service groupdependencies as Soft in the console.

To reconfigure the service group dependency

1 In theVeritasOperationsManager console, clickManage>BusinessEntities.

2 In the Business Entities view, do one of the following:

Known issuesVBS Availability Add-on issues

72

■ Select the Virtual Business Service for which you want to set the servicegroup dependency as Soft. Click Actions > VBS Availability > ConfigureService Group Dependencies.

■ Right-click the Virtual Business Service for which you want to set theservice group dependency as Soft, to display the shortcut menu. SelectVBS Availability > Configure Service Group Dependencies.

3 In theVirtualBusinessServicestartorderwizardpanel, for eachdependency,select Soft in the Dependency Type drop-down list.

4 Clear the Enable Fault Management checkbox.

5 Click Next.

6 In theVirtualBusinessServiceconfigurationsummarywizardpanel, reviewthe changes that you have made for the Virtual Business Service.

7 Click Finish.

Scripting Add-on issuesThe following issues relate to the Scripting Add-on.

Post Management Server upgrade, the Scripting Add-on uses thecurrent time of the Management Server to run the previous scripts

This issue is related to the ScriptingAdd-on and the upgrade ofVeritasOperationsManager Management Server to version 5.0. Post Management Server upgrade,if you try to reschedule the old scripts with the new time, the Scripting Add-onuses the current time of the upgraded Management Server to run the scripts.

Workaround:

Upgrade the Scripting Add-on to version 5.0.

Scripting Add-on runs the Perl scripts successfully only when the Perlexecutable installed with Veritas Operations Manager is used(2589815)

For the Perl scripts, it is recommended that you use the Perl executable that isinstalled with Veritas Operations Manager. For the Windows platforms, it is thedefault for scripts with the .pl extension. For UNIX platforms, using the Perlexecutable from other paths may result in errors if the script does not handle thePerl 5 library path properly. This recommendation does not affect shell, bat, orother executable scripts that are available with the Scripting Add-on.

73Known issuesScripting Add-on issues

Workaround:

To run the script successfully, ensure that the Perl executable location is specifiedas follows:

#!/opt/VRTSsfmh/bin/perl

Storage Insight SDK Add-on issuesThe following issues relate to the Storage Insight SDK Add-on.

Edit and Test operations on Storage Insight Plug-in are not supportedusing Internet Explorer on 64-bit Windows hosts (2826079)

This issue is observed ona64-bitWindowshostwhere Storage Insight SDKAdd-onis installed.Using Internet Explorer, you cannot upload theStorage Insight Plug-infile (.sfa). So, the Edit and Test operations cannot be performed in InternetExplorer.

Workaround:

You need to use other Web browsers to edit and test the Storage Insight Plug-in.For example, Mozilla Firefox or Google Chrome.

LDom Capacity Management Add-on issuesThe following issues relate to the LDom Capacity Management Add-on.

Capacity planning cannot be enabled or disabled from the OrganizationEntities view (2827450)

In the Organization Entity view, you cannot enable or disable capacity planningfor entities, even thoughVeritasOperationsManager LDomCapacityManagementAdd-on is installed.

Workaround:

You can use the Business Entities view to enable and disable capacity planningfor organization entities.

To view the Business Entites view, select Manage > Business Entites.

Known issuesStorage Insight SDK Add-on issues

74

Other issuesThis section lists additional issues that cannot be categorized in the rest of theVeritas Operations Manager known issues sections.

Duplicate entries for the disks that are part of a virtual machine(2481982)

If a virtual machine that runs Storage Foundation has non RDM disks on it andthe enclosure-based naming scheme is enabled for the disks, Veritas OperationsManager displays the disks twice on the Hosts > Disks tab. This issue occursbecause the disks are discovered by VxVM and the operating system on theenclosures.

Workaround:

Change the disk naming scheme to c#t#d#.

Composite business entities do not inherit all user configurations donefor the child business entities (2349751)

In Veritas Operations Manager, a composite business entity inherits some of theobjects and the corresponding configurations of its child business entities. It doesnot inherit the following:

■ Start and stop order of the service groups that were configured using theVeritas Operations Manager Virtual Business Services Availability Add-on

■ Virtual machine auto start and stop settings for the business entity that wereconfigured using the Veritas Operations Manager Virtual Business ServicesAvailability Add-on

■ LDom capacity planning settings that were configured using the VeritasOperations Manager LDom Capacity Management Add-on

Workaround:

You need to re-configure these settings for the composite business entity.

Symantec ApplicationHA Console single sign-on breaks after VeritasOperations Manager 5.0 managed host installation or upgrade onApplicationHA hosts

When Veritas Operations Manager 5.0 managed host is installed or upgraded ona host that has either Symantec ApplicationHA 5.1 Service Pack 2 or Symantec

75Known issuesOther issues

ApplicationHA 6.0 installed on it, the ApplicationHA Console single sign-on failsto work.

There is no workaround for the issue.

Known issuesOther issues

76

Documentation addendaand errata

This appendix includes the following topics:

■ Addenda and errata for Veritas Operations Manager 5.0 online help

■ Errata for Veritas OperationsManager Storage Insight Add-on forDeepArrayDiscovery and Mapping 5.0 online help

■ Addenda and errata for Veritas Operations Manager Add-on for StorageFoundation Administration 5.0 online help

■ Errata for Veritas OperationsManager Storage Insight SDKAdd-on 5.0 onlinehelp

Addenda and errata for Veritas Operations Manager5.0 online help

This section contains the errata and the additional information that is not includedin the online help for Veritas Operations Manager 5.0.

About multi-pathing discovery in the VMware environmentIn this section, the information discovered for each disk should read as:

For each disk you can discover the following information:

■ Total number of paths, and number of active paths.

■ The details about the path.

AAppendix

■ The information about the multipathing applications. The multipathingapplications can be VMware native multipathing (NMP), EMCPowerPath/Virtual Edition, or Symantec VxDMP.

About the virtualization technologies supported by Veritas OperationsManager

In this section, the information related to discovery of stand-alone ESX serversis removed because Veritas Operations Manager does not support the directdiscovery (without VMware vCenter Server) of ESX servers.

The updated section should read as:

In theVMware virtualization technology, a designatedControlHost discovers theVMware vCenter Server in the datacenter. This discovery displays those ESXservers that VMware vCenter Server manages, and the virtual machines that areconfigured on the ESX servers.

About Microsoft Hyper-V virtualization discovery in Veritas OperationsManager

In this section, the information discovered for Microsoft Hyper-V virtualizationtechnology should read as:

Hyper-V is ahypervisor-basedvirtualization technology fromMicrosoft for x86-64systems. You can use Veritas Operations Manager to discover Hyper-V host andvirtualmachine-related information if theHyper-V role is enabled on themanagedhost. Veritas Operations Manager uses Hyper-V WMI API for the discovery.

Hyper-V discovery can be grouped into the following categories:

■ Virtual machine discovery: Hyper-V virtual machine discovery by VeritasOperations Manager, and its correlation with the Hyper-V server.

■ Exported storage discovery: Discovery of storage that is provisioned to theguests, and its correlation with the virtual machine and Hyper-V server.

Virtual machine discovery in Microsoft Hyper-VIn this section, the information related to agent and agentless discoveries ofHyper-V virtual machines is added.

The following information is added:

Agent and agentless discoveries of Hyper-V virtual machines are supported.However, for the agentless method, the discovered information is limited. Todiscovermore information about the configured virtualmachines, agent discovery

Documentation addenda and errataAddenda and errata for Veritas Operations Manager 5.0 online help

78

method should be used. It provides detailed information about the virtualmachines.

The limitation of virtual machine discovery is listed below:

■ Hyper-V discovery is not supported on agentless Hyper-V Server (parentpartition) to which the Hyper-V virtual machines are associated.

Storage mapping discovery in Microsoft Hyper-VFor the storagemappingdiscoveryofMicrosoftHyper-Vvirtualization technology,agent or agentless guest are supported. The updated section should read as:

Veritas OperationsManager discovers the storage provisioned to the guests fromthe host's local storage, or storage area network (SAN). The Hyper-V guest (withor without VRTSsfmh package), when added to Veritas Operations ManagerManagement Server domain, provides storage mapping discovery. These detailsare displayed on theStorageMapping tab onVeritasOperationsManager console.

Additional storage attributes are also displayed on the page. For example, size,type of the storage (VHD or passthrough disk), and the storage container (volumeon the host where virtual storage is provisioned). The storage device handles onthe guest will be mapped to the corresponding VHD or passthrough diskprovisioned from host. Veritas Operations Manager also discovers the snapshotdisks provisioned to the VMS.

Storage mapping discovery prerequisites are listed below:

■ The Hyper-V server must be running Microsoft Windows Server 2008 R2, orlater operating system.

■ WindowsManagement Instrumentation (WMI) should be runningon theguest.

Navigation changes to the virtualization management option on VeritasOperations Manager console

For virtualization management tasks on Veritas Operations Manager console,navigational changes are introduced.

For the following tasks, the user navigation is updated:

■ Configuring the virtualization discovery in Veritas Operations Manager

■ Editing the virtualization discovery in Veritas Operations Manager

■ Refreshing the virtualization discovery in Veritas Operations Manager

■ Removing the virtualization discovery in Veritas Operations Manager

For these procedures, the updated user navigation should read as:

79Documentation addenda and errataAddenda and errata for Veritas Operations Manager 5.0 online help

In the Veritas Operations Manager console, select Settings > Virtualization.

Viewing information on the storage assigned to virtual machines froma virtualization server

The updated description for the Target Name field should read as:

For agentlessconfiguration

For agent configurationVirtualization technology

Target Name field isavailable.


Microsoft Hyper-V

Target Name field is notavailable.


LDom

Target Name field is notavailable.


LPAR

Not supported for zones as Global zone discovers theproperties. Therefore, agent is not required on the guestcomputer (non-global zone).

Zone

For KVM, storage mapping is not supported. The TargetName field is blank even if the VRTSsfmh package ispresent.

Kernel-based VirtualMachine (KVM)



VMware

The updated description for the Target Type field should read as:



TargetType field is available.TargetType field is available.Microsoft Hyper-V

TargetType field is available.TargetType field is available.LDom

Target Type field is notavailable.

TargetType field is available.LPAR

TheTarget Type field is available irrespective ofVRTSsfmhpackage installation on the guest machines. That is, foragent and agentless configuration, this field is available.

Zone

For KVM, storage mapping is not supported. The TargetType field is blank even if theVRTSsfmh package is present.

Kernel-based VirtualMachine (KVM)


80



TargetType field is available.TargetType field is available.VMware

Viewing the overview of enclosure informationThe information related to the IP Address field is added. It should read as:

IP Address: It displays the IP address of the configured enclosure.

Viewing an enclosure’s array port pathsIn this topic, the navigation path to view EMC VPLEX enclosure's array port pathhas been added.

The modified topic should read as:

Viewing an enclosure’s array port pathsAdministrators can view the enclosure’s array ports. For each array port withinthe enclosure, administrators can further determine any array port dependencies.

Administrators can view an enclosure’s array port paths, which represent theconnection from the host to the LUNs. Administrators can also determine thepath status on both the primary and the secondary hosts. Dynamic Multipathing(DMP) requires path information for load balancing and failover on both primaryand the secondary hosts.

By using the icons at the top right of the table, you can customize columns, printthe table, or export its contents to a CSV file.

To view an enclosure’s array port paths


2 Click on an enclosure.

3 If the enclosure is an EMC VPLEX enclosure, do the following. For otherenclosures, skip to step 4.

■ Click the Nodes tab.

■ Click on a node.

Skip to step 5.

4 Click the Array Ports tab.

5 Click on an array port.


6 Click the Paths tab.

7 In the array port’s Paths view, review the information.

Viewing an enclosure's array port disksIn this topic, the navigation path to view EMCVPLEX enclosure's array port diskshas been added.


Viewing an enclosure’s array port disksAdministrators can view the enclosure’s array ports. For each array port withinthe enclosure, administrators can further determine any array port dependencies.

You can identify where the disk is located, any disk groups, the disk status (forexample, healthy or offline), its size, and dynamic multipathing connections.


To view an enclosure’s array port disks






Skip to step 5.


5 In the enclosure’s Array Ports view, click on an array port.

6 Click the Disks tab.

7 In the array port’s Disks view, review the data.

Viewing an enclosure's array port volumesIn this topic, the navigation path to view EMC VPLEX enclosure's array portvolumes has been added.



82

Viewing an enclosure’s array port volumesFor each enclosure, administrators can view the enclosure’s array ports. For eacharray port within the enclosure, administrators can further determine any arrayport dependencies.

The array port’s volume view shows the volume’s status, its layout, snapshotinformation, size, and percentage of storage used.


To view an enclosure’s array port volumes






Skip to step 5



6 Click the Volumes tab.

7 In the array port’s Volumes view, review the data.

Viewing an enclosure's array port databasesIn this topic, the navigation path to view EMC VPLEX enclosure's array portdatabases has been added.


Viewing an enclosure’s array port databasesFor eachenclosure in theVeritasOperationsManager environment, administratorscan view the enclosure’s array ports. For each array port within the enclosure,administrators can further determine any array port dependencies.

The array port’s database view displays the status of the database instance, thetype of database, and the host on which the database resides.



To view an enclosure’s array port databases




■ Click on Nodes tab.


Skip to step 5.



6 Click the Databases tab.

7 In the array port’s Databases view, review the information:

About Veritas Operations Manager performance graphsThis topic is modified as below:

About Veritas Operations Manager performance graphsInstall Control Host Add-on 5.0 on a managed host to view the performance ofthe following objects by using interactive graphs:

■ Host

■ Volume

■ File system

■ Disk

■ Multipathing path

■ Initiators

■ Enclosure

■ Array port

■ Adapter

You can select an object and view graphs for multiple performance parameters.These graphs are line charts. The lines that represent the performanceparametersare rendered in different colors. The X-axis represents the time duration and theY-axis represents the performance parameter. Linear trend line is displayed for


84

every performance parameter. The linear trend line is plotted by fitting a line onthe historical data. Linear trend is not available for live charts.

Performance charts for volume and disk are available if they are managed byVxVM. Performance charts for multipathing path, initiator, and enclosure areavailable only if they are managed by physical hosts running DMP or VMwareESX servers running VxDMP.

On the performance graph, you can perform the following actions:

■ Specify the duration for which youwant to view the performance of the objectthat you have selected.

■ Move the mouse pointer over the line chart to view the performance data. Atool tip is displayed corresponding to the positon of the mouse pointer on thegraph.

■ Click the desired legend to temporarily hide or display the line graph.

Pre-requisite commands to view performance graphs for a resourceThis topic is modified as below:

Pre-requisite commands to view performance graphs for aresourceTableA-1 lists thepre-requisite commands that are required to viewperformancegraphs for a host.

Table A-1 Pre-requisite commands for a host

Pre-requisite commandsChart name

Solaris/Linux: vmstat

AIX: svmon

HP-UX: swapinfo

Available Memory

VMware Guest/ESX: SWPR/S

Solaris: sar

AIX: vmstat

HPUX: vmstat

Linux: sar

Swap in Rate


Table A-1 Pre-requisite commands for a host (continued)

Pre-requisite commandsChart name

Solaris/AIX: swap

Linux: cat /proc/swaps

HP-UX: swapinfo

VMware: vSphere APIs

Used Swap

vxlistSize/Used

Users having Host\CIM\CIM Interactionprivileges on aVMware vCenter server,can view the performance graphs for enclosure, multipathing path, and initiatorfor an ESX server running VxDMP.

Users having Host\Configuration\Change Settings privileges on a vCenterserver, can view the Available Memory, CPU Utilization, Swap in Rate, and theUsed Swap performance graphs for VMware ESX servers and virtual machines.

Errata for VeritasOperationsManager Storage InsightAdd-on for Deep Array Discovery and Mapping 5.0online help

This section contains the errata and the additional information that is not includedin the online help for Storage Insight Add-on 5.0.

Configuring deep discovery for EMC Symmetrix storage enclosuresIn this section, the SymCLI version for FAST managed storage groups in a EMCSymmetrix VMAX enclosure is incorrectly mentioned as SymCLI Version 7.1, orlater.

This should read:

To discover FASTmanagedStorageGroups in aEMCSymmetrixVMAXenclosure,you must use SymCLI Version 7.3.1.0.

Configuring deep discovery for EMC VPLEX storage enclosuresIn this section, the modified introduction should read:

Documentation addenda and errataErrata for Veritas Operations Manager Storage Insight Add-on for Deep Array Discovery and Mapping 5.0 online help

86

After Storage Insight Add-on performs the deep array discovery, you can viewthe following additional information on the overview page of the EMC VPLEXenclosure:

■ Virtual Volumes

■ Storage Volumes

■ RAID Groups

Viewing all virtual volumes for the EMC VPLEX enclosureTheDiskGroup column in this view is not applicable to the EMCVPLEX enclosureand hence does not display any information.

The description should read as:

Disk Group: This information is not displayed for EMC VPLEX enclosure.

Viewing the virtual volumes of a device for the EMC VPLEX enclosureThe Consumed Size column is not applicable to the EMC VPLEX enclosure andhence does not display any information.

The description should read as:

Consumed Size: This information is not displayed for EMC VPLEX enclosure.

Viewing the overview of the EMC VLPEX enclosureIn this topic, the modified introduction should read:

TheEnclosureStorageSummarywaterfall chart lets youview the storage capacityof the enclosure in terms of its physical storage size (configured, spare, andunconfigured), its device (addressable, overhead, and available) and virtual volumesize (allocated, administrative, and unallocated). You can view the storagedistribution by configuredRAID level in theStorageDistributionbyRAIDLevelschart. This chart shows storage capacity distribution based on the particular RAIDLevel.

Viewing the device configurations for storage enclosuresThe following fields are updated:

■ The Device Manager field is available for all new supported arrays. Thedescription for the Device Manager field should read as:Device Manager: Specifies the name or the IP address of the server that youhave specified when you configured the deep discovery for the enclosure.

87Documentation addenda and errataErrata for Veritas Operations Manager Storage Insight Add-on for Deep Array Discovery and Mapping 5.0 online help

■ The State column is not available on the device configuration page.

■ The description for the Scope field should read as:Scope: It displays the device configuration scope.

Viewing the tier configurationInformation related to the RefreshTierDefinitionoption is added to the existingoptions list. The updated information should read as:

■ Define a new tier by creating rules.

■ Modify an existing tier definition.

■ Delete a tier definition.

■ Change the order of the tiers in this view.

■ Refresh tier definition.

Viewing the overview of a NetApp enclosureUnder the EnclosureStorageSummary section, network attached storage (NAS)related information is added. The updated content should read as:

TheEnclosureStorageSummarysection lets you view the following information:

■ Physical configured storage

■ Physical spare storage

■ Physical unconfigured storage

■ Aggregate and Traditional volumes - NAS capacity

■ Aggregate and Traditional volumes - SAN capacity

■ Aggregate and Traditional volumes - Overhead capacity

■ Logical NAS used storage

■ Logical NAS free storage

■ Logical allocated storage

■ Logical unallocated storage

Thin pools and LUNs related information is removed for NetApp enclosure.

Viewing the LUNs on a NetApp enclosureInformation related to Parent Volume field is added. It should read as:


88

Parent Volume: Displays the parent volume of the LUN.

Viewing all the virtual disks on an HP EVA enclosureThe following information is removed as it is not applicable to the virtual disksof HP EVA enclosure:

LUSE: The LUN unit size expansion (LUSE) value for the virtual disk.

Viewing the disks associated with a virtual disk on an HP EVA enclosureThe following fields are updated:

■ SourceDevice is removed as it is not applicable to the disks that are associatedwith a virtual disk.

■ Information related to the thin reclaimable size of the disk is added. It shouldread as:Thin Reclaimable Size: Displays the thin reclaimable size of the disk.

Viewing the physical disks of a virtual disk on an HP EVA enclosureThe following fields are added:

■ Is Spare: Indicates if the physical disk is spare.

■ Is Shared: Indicates if the physical disk is shared between different RAIDgroups.

Viewing the performance graphs for an array portIn this topic, the navigation path to view the performance graphs for an EMCVPLEX enclosure's array port has been added.


Viewing the performance graphs for an array portIn Veritas Operations Manager Storage Insight Add-on for Deep Array Discoveryand Mapping, you can view the performance of a Fibre Channel array port in aninteractive graph.

For NetApp array, performance graph is displayed only if the port is online andlocal to the array.

You can specify one of the following durations for which the performance graphscan be rendered:

89Documentation addenda and errataErrata for Veritas Operations Manager Storage Insight Add-on for Deep Array Discovery and Mapping 5.0 online help

■ Six hours

■ 24 hours

■ One week

■ One month

■ One year

■ Live

You can view the following performance graphs for an array port:

■ The IO Operations per second graph displays the number of input outputoperations per second and the trend for the selected array port for the specifiedduration.

■ The IO Throughput per second graph displays the data read and written (inKB) per second and the trend for the selected array port for the specifiedduration.

To view the performance graphs for an array port

1 In the Veritas Operations Manager console, click Manage > Enclosures.

2 In the Enclosures view, click the enclosure.

3 If the enclosure is a EMC VPLEX enclosure, to the following. For otherenclosures, skip to step 4.



Skip to step 5.


5 In the Array Ports view, do one of the following:

■ Click the name of the array port. Click the Performance tab.

■ Check the check box for the array port and on the top of the Array Portstable, click Actions > Performance.

■ Right-click the array port to display the shortcut menu, selectPerformance.

6 On the performance graphs, in theDuration drop-down list, click the desiredtime duration to change the view of the performance graphs.

7 Click the desired legend to temporarily hide (or display) the line graph.


90

Addenda and errata for Veritas Operations ManagerAdd-on for Storage Foundation Administration 5.0online help

This section contains the errata and the additional information that is not includedin the online help for Add-on for Storage Foundation Administration 5.0.

Volume attributes panel optionsIn this section, added the following volume attribute:

Select the Create Snapshot Cache Volume checkbox tocreate the snapshot cache volume as a cache for a snapshot.Specify the values for the attributes on the snapshot cachevolume.

Create Snapshot CacheVolume

Create a new file system panel optionsIn this section, the File SystemOptions tables for vxfs, ext2, ext3, ufs andhfs havebeen modified.


Create a new file system panel optionsUse this wizard panel to create a new file system.

Use the File System Options panel to set options when creating a file system.

Table A-2 File System Options for vxfs

DescriptionField

Select the block size from the followingoptions:

■ Block size values: 1024, 2048, 4096, 8192

Block size

Select this checkbox if the vxfs file systemcontains files greater than 2 GB.

Support large file size (Greater than 2 GB)

Select this checkbox if you want to specifythe activity logging area size. If checked, youneed to provide a value for the log size.

Specify activity logging area size

Define any other file system option.Additional Options

91Documentation addenda and errataAddenda and errata for Veritas Operations Manager Add-on for Storage Foundation Administration 5.0 online help

Table A-3 File System Options for ext2, ext3, ufs and hfs

DescriptionField

Select the allocation unit from the followingoptions:

■ Allocation unit values: 1024, 2048, 4096,8192

Allocation unit size

Select the block size from the followingoptions:

■ Block size values: 1024, 2048, 4096, 8192

Block size

Define any other file system option.Additional Options

Use the Mount Options wizard panel to set options when mounting a file system.

The volume name and file system type are displayed.

If the file system has an entry in the file system table, checkMount using optionsin file system table to use the stored mount options. You cannot use this wizardpanel to change the options. To change options, youmust remount the file system.

Table A-4 Mount Options

DescriptionField

Enter the mount point for the file system.The mount point must be an absolutepathname, that is, it must begin with /.

Mount point

Select this checkbox tomount the file systemread-only.

Read only

Select this checkbox to allow setuid requests.Honor setuid

Select this checkbox to automatically updatethe file system table when the file system ismounted.

Add to file system table

Select this checkbox tomount the file systemat boot time.

Mount at boot

Specify the fsck pass when the file system ismounted at boot time.

fsck pass

Select to view advanced mount detailoptions.

Advanced mount options

Documentation addenda and errataAddenda and errata for Veritas Operations Manager Add-on for Storage Foundation Administration 5.0 online help

92

Creating volumesIn this section, the create volume procedure steps have been updated.

The modified topic should read as follows:

Creating volumesIn the Veritas Volume Manager, using this operation, you can create a volume ona host. When you invoke the create volume wizard, it asks you for informationon the disks to use, the required layout, size, mirrors, logging, and the file systemoptions.

When you create a VxVM volume, you can either manually select disks or letVxVM select the disks for you.

An error page is displayed if the selected disk group is not a VxVM disk group.

Toperform this operationyoumusthave the administrative privilege on thehost.

This operation can be performed from the following views:

■ Host Details View > Actions

■ Host Details View > Disk Groups

To create a VxVM volume from the actions view

1 In the Veritas Operations Manager console, click Manage > Hosts.

2 In the list of hosts, click on a host to go to its view.

3 Click Actions on the top left hand of the page. Select Create Volume.

4 In the Create Volume wizard panel, choose an option of disk selection. ClickNext.

If you manually select the disks from the disk group, click Next to view theDisk Selection wizard panel. Select disks create the volume. Click Next.

5 In the Volume Attributes wizard panel, specify the attributes of the newvolume. Click Next.

6 In the Volume Attributes wizard panel, if you select the Create SnapshotCacheVolume check box to create the volume as a cache for a snapshot, thenspecify the values for the attributes of the new volume.

7 If you want to create a file system on the volume, select Create file system.Click Next. Specify the file system and mount options.

8 In the Create Volume Summary panel, verify the details of the new volumecreated. Click Finish.

93Documentation addenda and errataAddenda and errata for Veritas Operations Manager Add-on for Storage Foundation Administration 5.0 online help

To create a VxVM volume in the context of disk groups

1 In the Veritas Operations Manager console, click Manage > Hosts.

2 In the list of hosts, click on a host to go to its view.

3 Click Disk Groups and do one of the following:

■ Select the disk group from the list. Right-click on any of the selected rowsand select Create Volume.

■ Select the disk from the list. Click Actions > Create Volume.

4 In the Create Volume wizard panel, choose an option of disk selection. ClickNext.

If you manually select the disks from the disk group, click Next to view theDiskSelectionwizard panel. Select the disks to create the volume. ClickNext.

5 In the Volume Attributes wizard panel, specify the attributes of the newvolume. Click Next.

6 In the Volume Attributes wizard panel, if you select the Create SnapshotCacheVolume check box to create the volume as a cache for a snapshot, thenspecify the values for the attributes of the new volume.

7 If you want to create a file system on the volume, select Create file system.Click Next. Specify the file system and mount options.

8 In the Create Volume Summary panel, verify the details of the new volumecreated. Click Finish.

Errata for VeritasOperationsManager Storage InsightSDK Add-on 5.0 online help

This section contains the errata and the additional information that is not includedin the online help for Veritas Operations Manager Storage Insight SDK Add-on5.0.

About Veritas Operations Manager Storage Insight SDK Add-on 5.0This topic should read as:

Veritas Operations Manager provides deep discovery information for storagearrays from multiple vendors. This discovery is enabled through Storage InsightAdd-on. For the list of supported enclosures, refer to the Veritas OperationsManager Hardware and Software Compatibility List (HSCL)

Documentation addenda and errataErrata for Veritas Operations Manager Storage Insight SDK Add-on 5.0 online help

94

If the storage discovery for an array is not supported through Storage InsightAdd-on, you can use Veritas Operations Manager Storage Insight SDK Add-on(Storage Insight SDK Add-on) to add support for the array in Veritas OperationsManager. You can use Storage Insight SDK Add-on to create customizedarray-specific add-ons. The custom add-ons are called Storage Insight plug-ins.The Storage Insight plug-in, when installed on a Veritas Operations ManagerManagement Server, enables Veritas Operations Manager to perform the deepdiscovery for the array.

Operational workflow to create Storage Insight Plug-inThis topic should read as:

Storage Insight SDKAdd-on deployment and Storage Insight plug-in creation aretwo requiredprocesses to discover the enclosure informationusingStorage Insightplug-in.

Deploy Storage Insight SDK Add-on on a managed host, and use Storage InsightSDK Add-on console to create array-specific Storage Insight plug-in. Upload andinstall Storage Insight plug-in toVeritasOperationsManagerManagementServer.After you have installed the Storage Insight plug-in successfully, use StorageInsight Add-on to discover enclosure properties.

About installing Storage Insight SDK Add-on 5.0The topic should read as:

Storage Insight SDK Add-on can be installed only on a managed host. Navigateto Settings > Deployment on Veritas Operations Manager console to install theadd-on.

For more information on installing add-ons using Veritas Operations Managerconsole, refer toVeritasOperationsManagerManagementServerAdministrator'sGuide.

About discovering array information using Storage Insight SDK Add-onThis topic should read as:

This process includes the following steps:

■ Download Storage Insight SDK Add-on.

■ Install Storage Insight SDK Add-on on a managed host.

■ Create discovery script and additional scripts, provide enclosure capabilitiesthat youwant to discover, select the device identifiers, provide other enclosuredetails, and create the Storage Insight plug-in.

95Documentation addenda and errataErrata for Veritas Operations Manager Storage Insight SDK Add-on 5.0 online help

■ Upload the Storage Insight plug-in to the Veritas Operations ManagerManagement Server.

■ Use Storage Insight Add-on to configure and discover array properties.

Creating a Storage Insight plug-inThe introductory paragraph should read as:

You can use Storage Insight SDK Add-on to create array plug-ins for the arraysthat are currently not supported by Storage Insight Add-on.

Documentation addenda and errataErrata for Veritas Operations Manager Storage Insight SDK Add-on 5.0 online help

96

Getting help

This appendix includes the following topics:

■ Veritas Operations Manager on the Web

■ Getting help

■ Using the product documentation

Veritas Operations Manager on the WebFor comprehensive, up-to-date information about Veritas Operations Manager,visit the Symantec Web site:

http://go.symantec.com/vom

Getting helpIf an issue arises while you use the products, refer to the product documentationand online help. If necessary, report it to Symantec.

For technical assistance, visit

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

This site provides access to resources such asTechNotes, product alerts, softwaredownloads, hardware and software compatibility lists, and the customer emailnotification service. Use the Knowledge Base Search feature to access additionalproduct information, including current and past releases of productdocumentation.

Using the product documentationThe following guides provide information about Veritas Operations Manager:

BAppendix

http://go.symantec.com/vom

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

■ Veritas Operations Manager Management Server Administrator's Guide

■ Veritas Operations Manager Management Server Getting Started Guide

■ Veritas Operations Manager Management Server Installation Guide

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

For information about the third-party software that is used in this product, seethe Veritas Operations Manager Management Server Third-Party LicenseAgreements.

The latest version of the product documentation is available on the SORT Website at the following URL:

https://sort.symantec.com/documents

For the late breaking news that is related to this release, use the followingTechNote:


Getting helpUsing the product documentation

98

https://sort.symantec.com/documents


Documents

Veritas OperationsManager 5.0 Release Notes · Veritas™ Operations Manager Release Notes ... For information regarding the latest HOWTO articles, ... CIFS shares from NetApp and