Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
0
Fre q u e n tly As ke d Qu e s tio n s
Product version: 5.0
Documentation version: 5.0 Rev 0
Contents
Support for Veritas Operations Manager Advanced features on Management Server ....................... 8
Ability to compress files on managed hosts ......................................................................................................... 8
Support for reclaiming thin storage ........................................................................................................................ 8
Ability to configure performance metering ......................................................................................................... 8
Enhanced performance charts with linear trend data ..................................................................................... 9
Ability to define Recovery Plan ................................................................................................................................. 9
Support for importing type definitions for clusters....................................................................................... 10
Improved discovery and visualization of all applications ........................................................................... 10
Support for configuring a vCenter server on a non-default port .............................................................. 10
Selective discovery of VMware ESX servers and IBM LPAR servers ....................................................... 10
Support for multi-pathing discovery in VMware environment................................................................. 10
Support for discovering Microsoft Hyper-V virtualization technology and storage correlation
discovery for LDom and LPAR ............................................................................................................................... 10
Symantec Performance Value Unit information for IBM LPAR and kernel-based virtual machines
(KVM) ............................................................................................................................................................................... 11
Automatic assignment of price tiers .................................................................................................................... 11
Support for additional discovery in Storage Insight Add-on ...................................................................... 11
Veritas Operations Manager Storage Insight SDK Add-on .......................................................................... 11
Support for listing the configured enclosures using the command-line interface ............................ 12
Support for service management using the command-line interface ..................................................... 12
Support for new operations in Veritas Operations Manager Add-on for Storage Foundation
Administration 5.0 ...................................................................................................................................................... 12
Improved monitoring of Veritas Volume Replicator replications ............................................................ 13
Support for Microsoft Exchange Server 2010 discovery ............................................................................. 13
Support for specifying path for temporary work area while upgrading Management Server ..... 13
General ................................................................................................................................................................................. 14
2012 Symantec
Networking ......................................................................................................................................................................... 22
What protocol is used for VOM? ............................................................................................................................ 22
What are the networking requirements? What firewall ports need to be opened? .......................... 22
What kind of network traffic can be expected if VOM is deployed? ........................................................ 22
What kind of SNMP support is there in VOM?.................................................................................................. 22
2012 Symantec
Security ................................................................................................................................................................................ 25
Infrastructure .................................................................................................................................................................... 27
Is xprtld a Web server? ............................................................................................................................................. 27
Why does VOM use a separate Web server for the console when xprtld is also a Web server? .. 27
What is xprtlc ? ............................................................................................................................................................. 27
What is fault.pl?............................................................................................................................................................ 27
What is xdist? ................................................................................................................................................................ 27
What is xinfo?................................................................................................................................................................ 28
What is xclusinfo?........................................................................................................................................................ 28
What is vomsc? ............................................................................................................................................................. 28
Can I access the VOM database directly?............................................................................................................ 28
Reporting ............................................................................................................................................................................. 29
What reports does VOM offer? ............................................................................................................................... 29
Is VOM able to create comparisons between reports? ................................................................................. 29
Patches ................................................................................................................................................................................. 31
2012 Symantec
2012 Symantec
Licensing .............................................................................................................................................................................. 38
VOM Management Entitlement Report ............................................................................................................... 38
2012 Symantec
What are the VOM components which are part of ApplicationHA support?........................................ 42
Which ApplicationHA versions are supported by this add-on? ................................................................ 42
Which are the virtualization technologies supported by Add-on for ApplicationHA Management?
............................................................................................................................................................................................ 42
Can I deploy ApplicationHA on the virtual machine from VOM using Deployment Manager? ..... 42
What type of management operations can I do from the ApplicationHA tab? .................................... 42
In the ApplicationHA tab, I am able to click on "Configure Application Monitoring" to launch the
wizard and I can see input fields, but I am unable to configure the application. What might be
the reason? ..................................................................................................................................................................... 42
Can I configure VCS support for ApplicationHA from VOM? ...................................................................... 43
What are the pre-requisites to perform the enable/disable ApplicationHA infrastructure
operation? ...................................................................................................................................................................... 43
How do I know the configuration status of VCS support for ApplicationHA on a node?................. 43
How do I know the infrastructure host that manages the ApplicationHA virtual machine? ......... 43
Why is the Infrastructure Host link missing in the summary panel of my ApplicationHA virtual
machine? ......................................................................................................................................................................... 43
Troubleshooting Information...................................................................................................................................... 44
Management Server (MS)......................................................................................................................................... 44
Managed host (MH) .................................................................................................................................................... 45
[Page 6 of 45]
2012 Symantec
Legal Notice
Copyright 2012 Symantec Corporation. All rights reserved.
Symantec, the Symantec logo, Veritas, and Veritas Storage Foundation are trademarks or registered trademarks of Symantec Corporation or its
affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.
This Symantec product may contain third party software for which Symantec is required to provide attribution to the third party (Third Party
Programs). Some of the Third Party Programs are available under open source or free software licenses. The License Agreement accompanying the
Software does not alter any rights or obligations you may have under those open source or free software licenses. Please see the Third Party Legal
Notice Appendix to this Documentation or TPIP ReadMe File accompanying this Symantec product for more information 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 document may be reproduced in any form by any means without prior written authorization of Symantec Corporation
and its licensors, if any.
THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING
ANY IMPLIED WARRANTY OF MERCHANT ABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT
TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR
INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE
INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.
The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12.212 and subject to restricted
rights as defined in FAR Section 52.227-19 "Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights in Commercial
Computer Software or Commercial Computer Software Documentation", as applicable, and any successor regulations. Any use, modification,
reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in
accordance with the terms of this Agreement.
Symantec Corporation
350 Ellis Street
Mountain View, CA 94043
http://www.symantec.com
[Page 7 of 45]
2012 Symantec
Discovery of hosts, that do not have Veritas Storage Foundation and High Availability (SFHA)
products installed on them.
Discovery of hosts via agentless method Discovery of network-attached storage (NAS).
Using Veritas Operations Manager Management Server console, you can reclaim thin storage. This
feature requires VxFS file system, Storage Foundation version 6.0 or later. Also, using Veritas
Operations Manager Management Server console you can determine how much storage can be
reclaimed before performing this operation.
Ability to configure performance metering
Veritas Operations Manager 5.0 lets you gather performance statistics for the VMware vCenter
server, the VMware ESX server, and the managed host. You can also disable performance statistics
gathering if required.
If Storage Insight Add-on 5.0 is installed and the discovery host is upgraded to Veritas Operations
Manager managed host version 5.0, performance statistics gathering is automatically enabled for
storage enclosures that were previously configured.
[Page 8 of 45]
2012 Symantec
Performance statistics are collected only for the following storage enclosures:
EMC CLARiiON
EMC Symmetrix
IBM XIV
NetApp
volume
host
disk
initiator
file system
multi-pathing path
enclosure
array ports
adapter
Performance charts for disks and volumes are available only if they are managed by Veritas
Volume Manager. Performance charts for multi-pathing paths, initiators, and enclosures are
available if they are managed by physical hosts running DMP or VMware ESX servers running
VxDMP.
Ability to define Recovery Plan
Recovery Plans consist of the steps that need to be run when a disaster or contingency arises.
Veritas Operations Manager provides the ability to create and store Recovery Plans, to manually
run a plan, and to monitor and log its progress and status.
Using the Veritas Operations Manager console, you can perform the following tasks:
[Page 9 of 45]
2012 Symantec
Veritas Operations Manager now provides complete visibility into the different applications that
are discovered from physical or virtual machines. The discovery includes the applications that
Symantec ApplicationHA discovers on different virtualization technologies (such as VMware, KVM,
LPAR, and LDOM). You can view applications for the entire domain, or for selected business
entities.
Support for configuring a vCenter server on a non-default port
In Veritas Operations Manager 5.0, you can configure a vCenter server on a non-default port. You
can specify the fully-qualified name of the vCenter server or its IP address, and the port number
on which the vCenter Web service is running.
Selective discovery of VMware ESX servers and IBM LPAR servers
In the previous release, when you configured a vCenter server or an HMC server, Veritas
Operations Manager discovered all the ESX servers under the vCenter server, 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 ESX servers or LPAR servers.
Support for multi-pathing discovery in VMware environment
Veritas Operations Manager now supports multi-pathing discovery for the disk paths under
VMware native multi-pathing (NMP), EMC PowerPath/Virtual Edition, and Symantec VxDMP on
ESX servers. However, path maintenance operations (enable or disable path) are supported only
on Symantec VxDMP.
Microsoft Hyper-V servers, Hyper-V virtual machines, and their server and storage
correlation.
Storage correlation discovery for Logical partition (LPAR), VIO server, and VIO clients.
[Page 10 of 45]
2012 Symantec
Symantec Performance Value Unit information for IBM LPAR and kernel-based virtual
machines (KVM)
In Veritas Operations Manager 5.0, you can calculate the Symantec Performance Value Unit (SPVU)
for the Symantec products that run on IBM LPAR and KVM.
Automatic assignment of price tiers
You can now assign price tiers to a single host, or multiple hosts, automatically in Veritas
Operations Manager using the uploaded price tier information.
Support for additional discovery in Storage Insight Add-on
Veritas Operations Manager now lets you enable deep discovery for the following enclosures using
Storage Insight Add-on:
Additionally, Storage Insight Add-on now also 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-on
You can use Veritas Operations Manager Storage Insight SDK Add-on to create customized arrayspecific add-ons. This feature is useful if the storage discovery for an array is not supported
through Storage Insight Add-on. The custom add-ons are called Storage Insight plug-ins. You can
specify the array objects to be discovered, discovery script, and provide the unique device
identifier for the arrays and 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 VRTSsfmh package
installed on it. The host may or may not be configured to a Management Server domain.
[Page 11 of 45]
2012 Symantec
In Veritas Operations Manager 5.0, you can use the service option of the vomadm command to
manage the various services using the command-line interface. You can start a service, stop a
service, restart a service, or display the status of a service. You can also use the command to
display the version of the Veritas Operations Manager packages that are installed on Management
Server (VRTSsfmcs and VRTSsfmh).
Support for new operations in Veritas Operations Manager Add-on for Storage Foundation
Administration 5.0
In Veritas Operations Manager Add-on for Storage Foundation Administration, the following
operations have been enhanced to improve user experience and auditing over previous
implementations:
Disk group operations:
Create a volume.
Initialize a disk.
Volume operations:
Disassociate a snapshot.
Re-attach a snapshot.
Recover a volume.
Stop a volume.
[Page 12 of 45]
2012 Symantec
Reactivate a volume.
Restore a volume.
Veritas Operations Manager now supports the discovery and management of Microsoft Exchange
Server 2010 hosts that are configured in your datacenter.
Support for specifying path for temporary work area while upgrading Management Server
Management Server upgrade requires additional disk space to create the temporary files. While
upgrading to Veritas Operations Manager 5.0, if you do not have enough disk space in your current
database directory, you are prompted to provide the path for a temporary working area having
enough disk space. This temporary working area is used to create the temporary files.
[Page 13 of 45]
2012 Symantec
General
What is Veritas Operations Manager (VOM)?
Veritas Operations Manager is a comprehensive business solution for monitoring, operating, and
reporting on datacenter environments using Veritas Storage Foundation, Veritas Cluster Server,
Veritas Dynamic Multi-Pathing, Veritas Dynamic Multi-Pathing for VMware, and Symantec
ApplicationHA. It combines the power of its predecessors namely Storage Foundation Manager,
VCS Management Console, VCS Java Console, and Veritas Enterprise Administrator into a single
powerful solution.
What documentation resources are available for Veritas Operations Manager (VOM)?
The following documentation resources are available for Veritas Operations Manager (VOM):
Online Help - The VOM online help is installed with the product. To access the online help, click
the 'Help' link at the top right of the Veritas Operations Manager console.
Guides The VOM user documentation is available on https://sort.symantec.com/documents
Does Veritas Operations Manager need anything installed on the managed host (MH) to
work with Storage Foundation (SF) 5.x?
Yes. Every version of SF that Veritas Operations Manager manages requires the same VRTSsfmh
package to be installed. However, this package is bundled with SF 5.1, and later versions.
Does Veritas Operations Manager require the Veritas Enterprise Administrator (VEA)?
VEA is only required on the managed host (MH) to support SNMP traps, to run administration
commands like create volume, and for Windows and HP-UX 3.5 discovery. VOM does not require
VEA on the MH, but those features will not be available.
[Page 14 of 45]
2012 Symantec
Frequency in
minutes
1440
SF
30
LDR
NR
Native
Zones
LDoms
1440
5
360
120
120
VCS
DB
KVM
Hyper-V
LPAR
VMware
60
60
120
120
360
360
Discovered information
Agentless
360
[Page 15 of 45]
2012 Symantec
Note:
*Additionally, Veritas Storage Foundation and Veritas Cluster Server families are also event driven.
For example, when a DMP path is disabled, or a Service Group is detected offline, it will trigger a
discovery cycle so that the information is quickly updated in the VOM Management Server Database.
It provides a near real-time reporting for Storage Foundation and VCS configurations.
With the exception of a small heartbeat communication occurring every 10 minutes, no additional
data is sent across to the MS unless changes to the configuration are detected. Please refer to the
VOM Administrators Guide for more information on VOM MH discovery.
Does VOM display localized (i.e. Japanese or Chinese) File System mount points?
Yes. The standard encoding VOM uses is UTF-8. Any other encoding that is used requires that the
xprtld daemon on the managed host be run under the locale/encoding that the mount point names
were created. English, Japanese, Simplified Chinese, and all UTF-8 locales are generally supported.
Does VOM support other non-Symantec Volume Managers and File Systems?
Yes. VOM discovers Logical Volume Manager (LVM) information on Linux, HP-UX, and AIX
managed hosts, as well as ZFS information on Solaris. VOM provides discovery of this information
only, no administrative options are currently available.
VOM also supports discovery of VxFS as well as many other native file systems including EXT3,
ReiserFS, HFS, UFS, JFS, JFS2, NTFS, and ZFS.
Does VOM support other non-Symantec Multi-pathing Solutions?
Yes. Besides support for Veritas DMP, VOM also supports discovery of EMC PowerPath, Microsoft
MPIO, and HP Native multipathing.
However, the DMP Management feature supports only Veritas DMP and Veritas DMP for VMware.
[Page 16 of 45]
2012 Symantec
What Veritas Cluster Server Management Console (VCSMC) functionality is not available in
VOM 4.1?
Yes, this can be adjusted from the Web Server Settings panel in the VOM Console under Settings >
General.
It is not recommended to set a large timeout as that may increase the memory utilization on the
MS. If many people log on to VOM simultaneously and do not explicitly log off, it could cause out of
memory errors.
When should I create Virtual Business Service (VBS) or Organization type Business
Entities?
VBS type Business Entities should be created when, as an administrator, you want to show
associated objects and faults with the base that you have defined. This type is more resource
[Page 17 of 45]
2012 Symantec
If you want to create Business Entities mainly to organize your hosts, to give user administrative
access, or scope reports and operations, then, you should create Business Entities of the
Organization type. This is a group of logically associated hosts (e.g. by Admin, by Team, by
Datacenter/Lab). Organization type Business Entities are less resource intensive than the VBS
variety, and can include potentially 1000s of base hosts.
Both types can be used to define Security Groups (Authorization) as well as scope reports and
operations.
Which VRTSsfmh package version is bundled with each VOM release? Which SFHA release
is each VRTSsfmh package version bundled with?
SFHA release that it is bundled with
VOM release VRTSsfmh version
2.1 (SFM)
2.1.198.0
SFHA AIX, Solaris, Linux 5.1
2.1.210.0
SFHA Windows 5.1SP1
2.1RP1 (SFM) 2.1.229.0
SFHA Linux 5.0MP4
SFHA Unix 5.1RP1
SFHA Linux and Solaris 5.1RP2
3.0
3.0.357.0
3.0.358.0
SFHA Windows 5.1 SP2
ApplicationHA VMware Linux 5.1
ApplicationHA VMware Windows 5.1SP1
3.0 RU
3.0.357.0
3.0 RP1
3.0.402.0
3.1
3.1.429.0
SFHA Solaris, AIX 5.1SP1
ApplicationHA VMware Linux 5.1SP2
3.1RP1
3.1.830.0
SFHA HP, Linux 5.1SP1 & 5.1SP1RP1
SFHA AIX, Solaris, Linux 5.1SP1RP2
ApplicationHA VMware Windows 5.1SP2
4.0
4.0.1097.0
4.0RU1
4.0.1598.0
ApplicationHA VMware 6.0
4.1
4.1.119.0
SFHA Unix, Windows 6.0
ApplicationHA Unix 6.0
[Page 18 of 45]
2012 Symantec
By default, the VOM installation creates the database in the /var directory on the MS. It is
recommended that you change this to its own partition or volume. If possible, it is recommended
that this be put on a striped mirror to improve performance. The recommended size depends on
the amount of resources that will be managed. It is recommended that you allocate 10 GB of disk
space for every 1000 managed hosts.
How much space is required for a VOM managed host (MH)?
2 GB disk space is adequate.
Can Veritas Cluster Server Management Console (VCSMC) and VOM coexist?
Yes. Both can be installed on the same host.
If I update, will I lose all the historical information in Veritas Cluster Server Management
Console (VCSMC)?
Yes. Since there is no explicit upgrade from VCSMC to VOM, no historical information would be
shown in VOM. However, because VCSMC and VOM can co-exist, you can still use VCSMC for any
historical data.
[Page 19 of 45]
2012 Symantec
The current release of Management Server supports upgrade from version 3.1, or later.
From which versions of MH can I directly upgrade to 5.0 MH?
The current release of VRTSsfmh package supports upgrades from version 2.x, or later. However,
if a host has VRTSsfmh 2.0 package, it is recommended that you upgrade the VRTSsfmh package to
5.0 before managing the host using a 5.0 Management Server.
Why does VOM give me the option to set the Management Server (MS) host name during
configuration?
VOM suggests the MS host name and IP address on the configuration page. You need to verify
whether the host name/IP address is accessible from all intended managed hosts.
The AutoConfigure option lets you add a managed host to the VOM Management Server domain
with minimal user interaction.
This script is downloadable from Settings -> Host. In the Manage Hosts view, select the
AutoConfigure tab, and click Download.
The script can also be created using the gendeploy.pl utility on VOM Management Server:
Unix/Linux MS:
[Page 20 of 45]
2012 Symantec
You can copy the script (addvommh.pl in this example) that is downloaded from Management
Server OR created using gendeploy.pl to all the managed hosts that you want to add to the domain.
After you copy the script, you have to run it on each host you wish to add. These hosts must have
the VRTSsfmh package installed before you run the script.
Unix/Linux MH:
chmod +x addvommh.pl
./addvommh.pl
The gendeploy generated script (vommh.pl in this example) has the VOM MS hostname embedded
in it. This is the name used to contact the MS during MH configuration. In case VOM MS is not
reachable from the MH via this default name, an alternate hostname/IP address can be specified
for the VOM MS using the domain option to vommh.pl. This option is available only for MH version
4.0RU1, or later.
The host-mgmt option of the vomadm utility can be used to remove a single host, or multiple
hosts, from VOM. It is currently supported only for hosts that are configured as Agents (hosts that
have the VRTSsfmh package installed):
Unix: /opt/VRTSsfmh/bin/vomadm host-mgmt remove
See the Veritas Operations Manager Management Server Administrators Guide for more
information.
[Page 21 of 45]
2012 Symantec
Networking
What protocol is used for VOM?
VOM uses an HTTPS-based protocol. Essentially, it uses Web services as the underlying message
exchange format.
What are the networking requirements? What firewall ports need to be opened?
All communication between managed hosts (MH) and VOM Management Server (MS) occurs
through port tcp/5634. If you have a firewall in your environment, this port needs to be opened
(bi-directional). For the user interface, you need to open port 14161 between the client desktop
on which the Web browser runs, and the MS. NO other port is required.
The MS host name needs to be resolvable from the MH. It is recommended that DNS be used for
this. If the host name is not resolvable, you can specify a valid IP address. However, this may affect
the usability of the product, as the IP is displayed as the Host name in the VOM console.
What kind of network traffic can be expected if VOM is deployed?
Managed hosts (MH) send an HTTP request (ping) every 10 minutes to the Management Server
(MS) indicating that it is UP. This request has less than 1 KB of payload. When there is a change
detected on the MH, the MH sends an HTTP POST to the MS indicating the change. However, only
differences (diffs) are sent. So, in an environment that does not change, there is no traffic other
than the 10-min pings from each managed host. When there is a change, the payload size depends
on the amount of change, which is never more than a full (initial) discovery of that host. On MHs
with 15,000 LUNs and about 2,000 file systems and volumes, the full discovery payload can be as
large as a few megabytes.
What kind of SNMP support is there in VOM?
SNMP trap support is limited in VOM. It does require that VEA be installed and running on the
managed host, because it is the source of events that are sent to SNMP server. VOM ships with an
SNMP MIB as part of the Management Server package. You can select the specific events to be
forwarded. See the rule manager under the "Monitor" tab in the console, and refer to
https://sort.symantec.com/documents.
[Page 22 of 45]
2012 Symantec
Virtual machines
Can VOM manage Storage Foundation that is running in a VMware virtual machine?
Yes. VOM supports Storage Foundation for Windows that is running on a VMware virtual machine.
Since in most cases VMware does not expose the HBA directly to the guests, VOM would not be
able to discover the array port of any LUNs nor the HBA ports. However, VOM displays the
enclosure information for any raw device mapped LUNs. Non-RDM disks are plain old SCSI disks
since they are abstracted from the guest.
I added vCenter to VOM; can I see end-to-end storage correlation from virtual machine to
LUN?
End-to-end storage correlation requires deep array discovery using Storage Insight Add-on for
those enclosures connected to the ESX server. This will provide storage correlation from VMDK
file to datastore, and to LUNs in the enclosure. To correlate a disk in virtual machine to VMDK file,
you need to add the virtual machine to Management Server by installing agent or agentless.
Can I perform Virtualization discovery through vCenter using a non-default port?
The default vCenter port is 443 which is used by VOM for Virtualization discovery. However if
vCenter is configured on a non-default port, one can specify the port number after vCenter IP /
hostname so that VOM will use the same for discovery.
For example, MYvCenter.mydomain.com:65535
[Page 23 of 45]
2012 Symantec
Add-ons
What is a VOM add-on?
VOM add-ons allow the extension of the base functionality that is included in VOM. Refer to
http://go.symantec.com/vom for more information about the available add-ons.
Do add-ons install anything on the managed host (MH)?
It depends on the add-on. Some add-ons are installed only on Management Server, while others
are installed on both the MH and MS. The MH components are installed automatically as part of
the add-on install.
Since older versions of Storage Foundation Manager (SFM) add-ons are not compatible with
VOM, is there an upgrade path available for these add-ons?
Storage Foundation Administration for UNIX: New version is available for download
Storage Foundation Administration for Windows: New version is available for download
Storage Reclamation and SF Product Version Reports: These are now included in the base
VOM product
Volume Migration: This has been replaced with Add-on for Storage Provisioning which is
available for download.
Are newer versions of Add-ons that were shipped for VOM 4.1 available?
Yes. See the VOM 5.0 add-ons download page.
[Page 24 of 45]
2012 Symantec
Security
What privilege or account do you need on a managed host (MH)?
To add a host into a domain, you need to know the root user and password of the MH. Once a host
is added, a secure channel is setup between the MS and the MH using PKI/PKCS mechanisms. After
the host is added to the domain, the password for the root user can be changed, and it does not
affect the operation of VOM.
Does xprtld allow for PAM, Active Directory, or LDAP-based authentication?
This is allowed for xprtld running on Management Server (MS). For the managed host, VOM allows
native OS authentication for end users.
What is a Security Group?
A security group associates the authentication group and the authentication domain with a
predefined role. For the Admin role, you can associate Business Entities with the security group to
limit the authorized scope of a particular user.
What should be specified in the name of a security group?
This should be the name of the security group that you want to create. Make sure that the name of
the authentication group and the name that you specify for the security group are the same.
Authentication group can be an OS group, LDAP/Authentication Domain group, or PAM/NIS
group.
How are privileges given on a cluster (Cluster administrator/operators) from VOM?
The cluster admin/operator roles are mapped to admin/operator roles on the business entity for a
cluster group type in VOM. See the VOM documentation for more details.
How can I limit the visibility of the out-of-band storage information (Storage Insight Addon)?
You can use security groups to turn on, or turn off, the Storage Access privilege. Only users who
have this privilege can configure, view, and run reports on the out-of-band storage information.
See documentation for more information.
[Page 25 of 45]
2012 Symantec
Click the Administer link in the details page of the managed host on which the SF objects are
located. This takes you to the summary page of the objects that can be managed. Click on any
object category in that page and select the desired object.
[Page 26 of 45]
2012 Symantec
Infrastructure
Is xprtld a Web server?
Yes. It is a modified embedded Web server based on the popular open source shttpd that listens
on port 5634. It only does authenticated SSL. It also has a built-in role-based authorization
mechanism.
Anything with the URL containing "admin" can only be accessed by the root user or an OS account
with admin privilege. All scripts within agent directory under <sfmh_bin_dir>/web/agent can be
accessed from other managed hosts as "root". These scripts are hardened and use Perl with Taint
mode turned on.
Why does VOM use a separate Web server for the console when xprtld is also a Web server?
The xprtld Web server is a stripped down version of Web server which can only handle HTTP
requests. VOM uses Apache Tomcat for the console as it provides the necessary servlet containers
for the Java-based Web application to function.
What is Xprtlc ?
Xprtlc, also known as Xprtl Client, is a CLI interface that communicates with xprtld.
What is fault.pl?
There are several aspects of the system that VOM monitors as part of the VRTSsfmh package that
is installed on the managed host (MH). However, this is not all encompassing. Users of VOM can
choose to add their own discovery and exception detection scripts to augment our offering.
Fault.pl lets you indicate if a host is faulted or at-risk, and it shows up in the VOM dashboard. A
simple HTTP server monitoring script that runs off of cron can call fault.pl if it stops running, and
clear it when it starts running again. See the VOM documentation for more details.
What is xdist?
xdist is a powerful command that lets you push a script to managed hosts in the Management
Server domain, and run it. Typical use cases can include provisioning a server, updating a patch on
multiple computers, or detecting compliance-related anomalies in your environment. This
command can only be run as root on Management Server, and it runs commands as root on the
target systems. It is secure and arbitrary commands cannot be called unless you bypass it using
your own scripts. It uses a white listing mechanism for authorized commands similar to how sudo
operates. See the VOM documentation for more details.
[Page 27 of 45]
2012 Symantec
xclusinfo interfaces with the VOM database and extracts information pertaining to the clusters and
their associated objects that are discovered in the datacenter.
What is vomsc?
The vomsc script lets you start, stop, or restart one or more Veritas Operations Manager services
on a UNIX-based or a Windows-based Management Server. If Management Server is configured for
HA, it is recommended that you use this script to prevent unintentional failovers. You can also use
the script to check the status of one or more services. The change in the state of the services is
temporary. When the host is restarted, all the services are started again.
You can use the vomsc script to view the version of the VRTSsfmcs package and the VRTSsfmh
package that is installed on the Management Server host.
Can I access the VOM database directly?
No, VOM does not support this feature.
[Page 28 of 45]
2012 Symantec
Reporting
What reports does VOM offer?
VOM offers reports in five different categories:
Storage Utilization: Reports on storage allocation, file system usage, resource mapping, data
protection, thin pool usage, enclosure storage allocation by host, solid-state disks, and
enclosure storage capacity.
Storage Reclamation: Reports to help uncover configured but unused storage infrastructure,
such as underutilized LUNs and file systems, LUNs not part of a disk group, Thin Provisioned
LUNS, and LUNs that are connected to multiple hosts.
Activity/Trend: Reports that focus on cluster-related data such as uptime analysis, cluster
activity, service group activity, resource activity, uptime analysis, failover summary, as well as
resource fault trending.
Environment: Reports that provide an overview of the product usage and versions deployed
as well as underutilized licenses. Virtual IP usage displays all the virtual IP addresses
configured under VCS. Also includes reports on license lifecycle, product usage, underutilized
licensed, and patches.
Inventory: Reports that provide an overview of the status of different SF/HA components
deployed and configured in the environment, such as clustered hosts not monitored by VCS,
disks with single or no paths.
All reports can be scheduled to run across the entire domain managed by VOM, or for a Business
Entity.
Is VOM able to create comparisons between reports?
VOM does not have an explicit feature for this, but data from the different reports can be exported
for further analysis.
[Page 29 of 45]
2012 Symantec
Performance Statistics
What performance-related data does VOM track?
For hosts, VOM tracks available memory and average CPU load. For Disks, Volumes, File Systems,
and FC Initiators it monitors read and write statistics.
Where are performance statistics stored?
The performance statistics data is not stored in the Management Server (MS) database, but on the
managed host (MH) in the /var/opt/VRTSsfmh/stats/ directory. If the MS is not running, VOM
continues to collect historic performance statistics on each MH.
[Page 30 of 45]
2012 Symantec
Patches
Is VOM able to show which SF/HA patches a specific host requires?
VOM integrates with Symantec Operations Readiness Tool (SORT) to retrieve the latest
information about hot fixes, point patches, and release patches on a per-server basis. This
information provides a system administrator an efficient way to manage patches so that the server
environments are up-to-date.
The information includes details on the criticality of the patch, whether the patch installation
requires application downtime, whether the patch has kernel components, whether the patch
installation requires system reboot, and the number of customers who have downloaded the
patch. This information has to be present with the patch on SORT for VOM to show it.
Is VOM able to show available and applicable VOM patches and add-ons?
VOM will show the applicable VOM patches and the add-ons that are available on SORT. It does so
based on the environment (MS and MH) being managed by Management Server.
The information includes details on the criticality of the patch, whether the patch installation
requires application downtime, and the number of customers who have downloaded the patch.
This information has to be present with the patch on SORT for VOM to show it.
My network does not allow for direct Internet access. Can I still access the Symantec
Operational Readiness Tool (SORT) functionality?
Yes. VOM Management Server supports the use of a proxy server to connect to SORT.
Can I use VOM to deploy any type of patches including Veritas Storage Foundation patches?
Currently, you can use the package/patch functionality for VOM-specific updates and VBS
packages, and not for general-purpose usage.
[Page 31 of 45]
2012 Symantec
DR fire drill is executed by bringing the fire drill (FD) service group online on the GCO clusters. An
option is provided to take the FD service group offline after successfully bringing it online. DR fire
drill can be scoped to a service group, a cluster, or a Business Entity.
To be able to run DR fire drills, a single VOM instance must manage all the GCO clusters.
Can I create fire drill service groups in VOM?
No. Currently, VOM does not support creating fire drill service groups.
What platforms are supported for HA and DR fire drills?
HA fire drill is supported only on UNIX platforms as the action entry points (.VFDs) are not
available on Windows.
DR fire drill is supported on all platforms.
Can I schedule fire drill runs?
Yes, both HA fire drills and DR fire drills can be scheduled. There is no default schedule as in
VCSMC, and it has to be set up manually. Existing schedules can be viewed and edited using the
Policies > Fire Drills > Schedules tab in the console.
How do I see the results of fire drill runs?
There are several locations in the VOM console where this is shown:
1) In the VOM console, under Policies > Fire Drills, the HA and DR fire drill tabs give the list of ALL
ongoing and completed runs.
[Page 32 of 45]
2012 Symantec
[Page 33 of 45]
2012 Symantec
Volumes
File Systems
Type of Operation
Creating disk groups
Adding disks to a disk group
Recovering the faulted disks
Replacing a faulted disk
Removing disk from a disk group
Renaming disks in a disk group
Resizing disks in a disk group
Initializing disks
Recovering a disk group
Deporting a disk group
Importing a disk group
Destroying a disk group
Disconnecting a disk
Creating volumes
Configuring instant volume snapshots
Configuring space-optimized snapshots for volumes
Configuring break-off mirror snapshots for volumes
Resizing volumes
Adding mirrors to volumes
Removing the mirrors of a volume
Restoring data from the snapshots of volumes
Refreshing the snapshot of a volume
Configuring a schedule for a volume snapshot refresh
Adding a snapshot volume to a refresh schedule
Modifying the refresh schedule for a volume snapshot
Removing the schedule for a volume snapshot refresh
Deleting volumes
Dissociating snapshot
Reattaching a snapshot
Stopping a volume
Recovering a volume
Reactivating a volume
Restoring a volume
Creating file systems
Mounting a non clustered file system on a host
Mounting a clustered file system on a host
[Page 34 of 45]
2012 Symantec
How do the centralized Storage Foundation operations differ from the operations available
through the UNIX and the Windows Administration add-ons?
Navigating through the Administer link to perform various operations on Disks, Disk groups,
Volumes and File systems is not required any more. Now, the Storage Foundation operations are
available on the Veritas Operations Manger console itself.
The UNIX and Windows administration add-ons use Veritas Enterprise Administrator (VEA) to
perform various Storage Foundation operations. But, the centralized Storage Foundation
operations are executed using the Storage Foundation CLIs. Therefore, there is no dependency on
VEA in UNIX. However, on Windows, since the Storage Foundation CLIs use VEA, there is an
indirect dependency.
Why is this delivered as a pre-bundled add-on?
The approach has been to provide the basic SFHA administration capabilities in Veritas
Operations Manager "out-of-the-box" without having to download and install an add-on. So, this
add-on is pre-bundled with the base Veritas Operations Manager installation. However, if you
want to "switch-off" the Storage Foundation operation capability, you can do that. When you
disable the add-on, the operations are not available on the Veritas Operations Manager console.
After you disable the add-on, a Web server restart may be needed to make the changes effective.
[Page 35 of 45]
2012 Symantec
SFHA on Windows:
SFHA on Unix/Linux:
ApplicationHA on VMware:
ApplicationHA on Unix:
Which file systems are supported for the mount and the unmount operations?
Mount operation
o File systems that are created on VxVM volumes
Unmount operation
[Page 36 of 45]
2012 Symantec
[Page 37 of 45]
2012 Symantec
Licensing
VOM Management Entitlement Report
VOM Management Entitlement Report provides detailed information about hosts that require
'VOM Advanced licenses'. The number of hosts that require the Veritas Operations Manager
Advanced license is calculated based on following set of rules:
[Page 38 of 45]
2012 Symantec
1. Download VBS Availability 5.0 Add-on from the Symantec Web site to a temporary directory
on a local computer.
2. Log in to Veritas Operations Manager console from that computer. Upload and install the addon on Management Server using the Deployment Manager.
3. VBS Availability Add-on requires VRTSsfmh 5.0 on the cluster nodes.
How are the VBS-backend components deployed?
The VRTSvbs package contains the VBS back-end components. This package is available by default
with SFHA 6.0, SFWHA 6.0 and ApplicationHA 6.0 (UNIX).
VOM MS is critical from the point of view of VBS configuration, but not for its operation. A VBS
cannot be created or edited without VOM. After a VBS is created, it will continue to operate even if
VOM MS is down. The VBS backend CLIs can be used for performing the operations and finding
status.
What is the purpose of the Enable fault management operation?
When you enable fault management, several tasks such as setting up credentials, pushing out the
VBS definition and so on, occur in the background. The tasks affect all the nodes of all the clusters
in that particular VBS. To enable fault management, certain pre-requisites must be met.
[Page 39 of 45]
2012 Symantec
How can I know if all the nodes have been properly configured for VBS to work?
You can create a policy check using the new signature added for VBS. Run it for selected VBSs
and see if there are any violations reported. If any violation is reported, the VBS may not work
properly and it should be fixed.
You can use the new fault that has been added for VBS. The topic id is event.alert.vom.vcs.
vbs.package.notinstalled, which stands for VRTSvbs package is not installed. Create a rule
that will act on this alert. Choose the notification type that you want. This rule will help in
reducing one of the factors that could affect the proper functioning of VBS.
If the VBS configuration goes out of synch, how does one correct it?
Run the following command on VOM MS:
[Page 40 of 45]
2012 Symantec
VOM uses XDist to push the data from MS to the cluster nodes. XDist has an in-built retry
mechanism that sends the data even if the target host is down, and comes back up later.
Where are the various log files stored for this feature?
The log files can be found at the following locations:
[Page 41 of 45]
2012 Symantec
Can I deploy ApplicationHA on the virtual machine from VOM using Deployment Manager?
No. ApplicationHA needs to be manually installed on the virtual machine.
[Page 42 of 45]
2012 Symantec
How do I know the configuration status of VCS support for ApplicationHA on a node?
The status is displayed under the ApplicationHA Infrastructure status attribute in the summary
panel of the host details page.
How do I know the infrastructure host that manages the ApplicationHA virtual machine?
This information is available under the Infrastructure Host attribute in the summary panel of the
ApplicationHA virtual machine host detail page.
Why is the Infrastructure Host link missing in the summary panel of my ApplicationHA
virtual machine?
Check if you have added the KVM/LDOM server host to VOM MS domain.
For IBM LPAR, check if you have configured and added the HMC managing the physical server
hosting the LPARs to VOM MS/control host. Also, check if all the LPARs that are part of
ApplicationHA infrastructure have been added to VOM MS.
Check if the virtual machine resource on the infrastructure VCS host is Online.
Further troubleshooting will be required if all the above checks are successful.
[Page 43 of 45]
2012 Symantec
Troubleshooting Information
Management Server (MS)
Configuration/Setup URL: https://<MS host name>:5634/
Web Console URL: https://<MS host name>:14161/
Ports that are required to be opened:
TCP 5634
TCP 14161
[Page 44 of 45]
2012 Symantec
Windows:
General: %AllUsersAppData%\Symantec\VRTSsfmcs\logs
MS database installation and upgrade script:
%AllUsersAppData%\Symantec\VRTSsfmcs\config_db
Unix/Linux installer log file: %TEMP%
Managed host (MH)
MH Log Files:
Unix/Linux: /var/opt/VRTSsfmh/logs
Windows: %AllUsersAppData%\Symantec\VRTSsfmh\logs
2012 Symantec