Veritas Operations Manager 3.

1
Frequently Asked Questions

Product version: 3.1

Documentation version: 3.1.1

Contents
Legal Notice ...................................................................................................................................................................... 1
General................................................................................................................................................................................ 2
Installation ........................................................................................................................................................................ 5
Networking ....................................................................................................................................................................... 6
Virtual Machines ............................................................................................................................................................. 7
Add-ons .............................................................................................................................................................................. 8
Security............................................................................................................................................................................... 8
Administer Link for Host Operations ..................................................................................................................... 9
Infrastructure................................................................................................................................................................ 10
Reporting ........................................................................................................................................................................ 11
Performance Statistics............................................................................................................................................... 12
Patches............................................................................................................................................................................. 12
VCS Fire Drill ................................................................................................................................................................. 13
Troubleshooting Information ................................................................................................................................. 14
Managed Host (MH) ................................................................................................................................................... 15

Legal Notice
The software described in this document is furnished under a license agreement and may be used only in accordance with the terms of the
agreement.

Copyright © 2010 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
merchantability, fitness for a particular purpose or non-infringement, are disclaimed, except to the extent that such disclaimers are held to
belegallyinvalid.symanteccorporationshallnotbeliableforincidental 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.

Document Date: 9/28/2010 [1/15] ©2010 Symantec

 Veritas Operations Manager 3.1
Frequently Asked Questions

General
What is Veritas Operations Manager (VOM)?

Veritas Operations Manager is a comprehensive business solution for monitoring, operating, and
reporting on data center environments using Storage Foundation and Veritas Cluster Server. 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.

Where is the Veritas Operations Manager (VOM) User Guide?

All VOM user documentation is online and accessed by clicking the 'Help' link at the top right from
within the Veritas Operations Manager interface.

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

Does Veritas Operations Manager interfere with Storage Foundation's functionality?

No.

Does Veritas Operations Manager require the Veritas Enterprise Administrator (VEA)?

VEA is only required on the Managed Host (MH) to support SNMP traps, running 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.

How frequently is Managed Host (MH) information updated to the VOM Central
Management Server (CMS) Database?

The discovery on each MH is broken down into families to focus on a particular functional area
that VOM discovers information about.

Frequency
Family Information Discovered
(minutes)
Basic host details about the operating system,
licenses, packages, and networking. It is assumed
HOST 1440
that most information relating to this family does
not change very frequently.

Document Date: 9/28/2010 [2/15] ©2010 Symantec

 Veritas Operations Manager 3.1
Frequently Asked Questions

All aspects of Volume Manager, File Systems, and

SF 30*
related storage network information.
VCS 60* VCS and its related information.
Oracle, DB2, MSSQL, and Sybase databases and their
DB 15
storage dependencies.
NR 5 Configuration status and external faults.
NATIVE 360 3rd Party Volume Management information.

*SF and VCS families are also event driven, so discovery is triggered when configuration change
events occur. Because of this information should be update into the VOM central database in near
real time.

With the exception of a small heartbeat communication occurring every 10 minutes, no additional
data is sent across to the CMS 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 will discover 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.
For Windows, it discovers both Basic and Dynamic Volumes.
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 Multipathing Solutions?

Yes. Besides support for Veritas DMP, VOM also supports discovery of EMC PowerPath, Microsoft
MPIO, and HP Native multipathing.
However, the DMP Management only supports Veritas DMP.

Does VOM support other Clustering Solutions?

Yes. VOM also supports discovery of Microsoft Cluster Server (MSCS).

What Veritas Cluster Server Management Console (VCSMC) functionality is missing in VOM
3.1?

Document Date: 9/28/2010 [3/15] ©2010 Symantec

 Veritas Operations Manager 3.1
Frequently Asked Questions

 Site concept: replaced by Business Entity concept

 Tagging: Region, Line of Business, Department: replaced by Extended Attributes
 Readiness views
 Migrate site workflow: Migrate cluster is available, replaced by Business Entity Operations
Add-on
 Recover site workflow: replaced by Business Entity Operations Add-on
 DR Alert and coordinated action to recover: Alerting available thru faults but not
actionable, coordinated action to recover can accomplished through the Business Entity
Operations Add-on
 Simulator Support
 Dropped Features (not targeted for future releases)
o Attribute reports for Clusters/groups/resources: details shown in general VOM
views
o Failure Summary: info shown in Uptime Analysis Report
o Fault Trending: info shown in Uptime Analysis Report
o Group Activity: info shown in Resource Activity Report
o Agent Inventory/ Agent Usage
o Heartbeat report

Can I adjust the session inactivity timeout?

Yes, this can be adjusted from the Web Server Settings panel in the VOM Console under Settings-
>Management Server.

It is not recommended to set a large timeout as that could increase the memory utilization on the
CMS. If many people are logging onto VOM simultaneously and not explicitly logging off it could
cause out of memory errors to occur.

When should I create Application or Organization type Business Entities?

In VOM 3.0 all Business Entities were of the Application type. These 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 intensive as it will automatically discover associated objects, so while
there are no hard limits it should be limited to specifying less than 100 base objects.

If you are looking 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
Application variety and can include potentially 1000s of base hosts.

Both types can be used for defining Security Groups (Authorization) as well as the scoping of
Reports and Operations.

Document Date: 9/28/2010 [4/15] ©2010 Symantec

 Veritas Operations Manager 3.1
Frequently Asked Questions

Installation
How much space is required for the VOM Central Management Server (CMS) database?

By default, the VOM installation puts the database in /var on the CMS. It is a good idea to change
this to its own partition or volume. If possible, it is recommended that this be put on a striped
mirror for performance. The recommended size depends on the amount of resources that will be
managed. Currently we recommend 10 GB of disk space for every 1000 Managed hosts.

How much space is required for a VOM Managed Host (MH)?

2 Gigabytes should be more than enough no matter how big the host is.

I am running Storage Foundation Manager (SFM) or Veritas Cluster Server Management

Console (VCSMC). How can I upgrade?

Upgrade to VOM is only supported from SFM 2.x and VOM 3.0. Users of VCSMC or SFM 1.x will
need to start with a fresh install of VOM.

Can a VOM Managed Host (MH) be managed by a SFM 2.x Central Management Server (CMS)
as well as by a VOM CMS?

No. A VOM MH requires a VOM CMS.

Can Veritas Cluster Server Management Console (VCSMC) and VOM co–exist?

Yes. They can both be installed on the same server.

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.

Is VOM backward compatible with SFM 2.x MH?

Yes. Discovery will still work. However, new VOM features and details will not be seen for these
MHs. In addition, VCS operation support was added only in VOM 3.0, implying that managed hosts
also need to be running sfmh package version 3.0 or above.

Document Date: 9/28/2010 [5/15] ©2010 Symantec

 Veritas Operations Manager 3.1
Frequently Asked Questions

Why does VOM give me the option to set the Central Management Server (CMS) hostname
during configuration?

VOM will suggest the CMS hostname and IP address on the configuration page.
Customers are required to verify this hostname/IP is accessible from all intended managed hosts.

Is Central Management Server (CMS) HA supported for Windows CMS?

No, this is not supported at this time.

What is AutoConfigure and gendeploy.pl?

The AutoConfigure option allows you to add a managed host to the VOM Management Server
domain with minimal user interaction.

This script is downloadable from Settings -> Host Management. In the Manage Hosts view, select
the AutoConfigure tab, and click Download.

The script can also be created using the gendeploy.pl utility on the VOM Management Server:

Unix/Linux CMS:
/opt/VRTSsfmh/bin/gendeploy.pl --out addvommh.pl

Windows CMS (VRTSsfmh install directory may vary):

cd “C:\Program Files\Veritas\VRTSsfmh\bin”
perl gendeploy.pl --out addvommh.pl

You can copy the script (addvommh.pl for this example) that is downloaded from the 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 with to add. These hosts must have
the VRTSsfmh package installed before you run the script.

Unix/Linux MH:
chmod +x addvommh.pl
./addvommh.pl

Windows MH (VRTSsfmh install directory may vary):

cd "C:\Program Files\Veritas\VRTSsfmh\bin”
perl addvommh.pl

Networking
What protocol is used for VOM?

Document Date: 9/28/2010 [6/15] ©2010 Symantec

 Veritas Operations Manager 3.1
Frequently Asked Questions

VOM uses a 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 the VOM Central Management Server (CMS)
goes 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 (where the web browser runs) and the CMS. NO other port is required.
The CMS's hostname needs to be resolvable from the MH. It is recommended that DNS be used for
this. If the hostname is not resolvable, you can specify a valid IP address, however this may impact
the usability of the product as the IP is what will be displayed for the Host name in the VOM Web
Console.

What kind of network traffic can be expected if VOM is deployed?

Managed Hosts (MH) send an HTTP request (a.k.a. ping) to the Central Management Server (CMS)
indicating that it is alive every 10 minutes. This request is a very simple request with less than 1
Kilobyte of payload (max). When there is a change detected on the MH, the MH sends a HTTP
POST to the CMS indicating the change. However, only differences (diffs) are sent. So, in a static
(not changing environment) 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 MHes with 15,000 LUNs and a 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?

There is limited SNMP trap support 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 Central Management Server package. You can select the specific events
to be forwarded. Please look at the rule manager under the "Monitor" tab, and refer to the VOM
documentation for more details.

Virtual Machines
Can VOM manage Storage Foundation for Windows (SFW) running in a VMware virtual
machine?

Yes. 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 will still give you
the Enclosure information for any raw device mapped LUNs. Non-RDM disks are plain old SCSI
disks since they are abstracted from the guest.

Document Date: 9/28/2010 [7/15] ©2010 Symantec

 Veritas Operations Manager 3.1
Frequently Asked Questions

Can the VOM Central Management Server (CMS) be installed on a virtual machine?

Yes, all it requires is an Operating System that is in the list supported by VOM CMS. If using
VMware, please note that VOM requires a 64 bit Operating System for Linux and Windows. The
VOM CMS can also be installed in its own Zone or LDOM.

Add-ons
What is a VOM Add-on?

VOM Add-ons allow the extension of the base functionality included in VOM. Please refer to
http://go.symantec.com/vom for more information about available Add-ons.

Do Add-ons install anything on the Managed Host (MH)?

It depends on the Add-on. There are Add-ons that install purely on the CMS. However, there are
also add-ons like that install pieces on both MH and CMS. The installation of the MH components is
done automatically as part of the add-on install. The user does not have to do anything special to
the MH for this.

Since older versions of Storage Foundation Manager (SFM) add-ons are not compatible with
VOM, is there an upgrade for these add-ons for VOM available?

Storage Foundation Administration for Unix: New version will be available for download

Storage Foundation Administration for Windows: New version will be available for download

Storage Reclamation and SF Product Version Reports: These are now included in the base VOM
product

Volume Migration: This will be replaced with Storage Template and Volume Migration which will
be available for download.

Are newer versions of Add-ons that were shipped for VOM 3.0 available?

Yes. Please go to the VOM 3.1 Add-on download page.

Security
What privilege or account do you need on Managed Host (MH)?

For adding 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 CMS and the MH using PKI/PKCS mechanisms.

Document Date: 9/28/2010 [8/15] ©2010 Symantec

 Veritas Operations Manager 3.1
Frequently Asked Questions

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 the Central Management Server (CMS). For the Managed
Host, VOM allows native OS authentication for end users.

What is a Security Group?

Security Groups provide a simple authorization mechanism to users of VOM. 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. Please see the VOM documentation for more details.

How do I ensure that the out-of-band storage information (Storage Insight Add-on) is
visible to a specific set of users and not everyone who can login to VOM?

Security groups allow for turning on or off the “Storage Access” privilege which only if enabled will
allow access to storage views and operations. Only users who have this privilege can configure,
view and run reports on the out-of-band storage information.

See documentation for more information.

Administer Link for Host Operations

Why do I see the Administer link on the Host detail page as RED instead of GREEN even after
I add a managed host successfully to the VOM Central Management Server (CMS)?

After the host is added to the CMS successfully the discovery process takes a minimum of 5
minutes to update the database with the discovered details of the added host. As there is some

Document Date: 9/28/2010 [9/15] ©2010 Symantec

 Veritas Operations Manager 3.1
Frequently Asked Questions

time lag between addition of the host and discovery completion, the admin link will show up as
RED until the discovery has completed. Please try refreshing the page after 5 minutes, and you
should be able to see the admin link as GREEN.

How do I perform operations on Storage Foundation (SF) objects such as Disk Groups or
Volumes?

Click on Administer link in the details page of the Host where the SF objects are located. This will
take 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.

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
/opt/VRTSsfmh/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 web 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
request. We use apache tomcat for the web 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’s communicates with xprtld.

What is fault.pl?

There are several aspects of the system that VOM monitors as part of VRTSsfmh package that is
installed on the Managed Host (MH). However, this is obviously not all encompassing. Users of
VOM can choose to add their own discovery and exception detection scripts to augment our
offering. Fault.pl allows you to indicate if a host is faulted or at-risk and it will show up as such in
the VOM dashboard. A simple http server monitoring script that runs off of cron can just call
fault.pl if it stops running and clear it when it starts running again. Please refer to the VOM
documentation for more details.

Document Date: 9/28/2010 [10/15] ©2010 Symantec

 Veritas Operations Manager 3.1
Frequently Asked Questions

What is xdist?

xdist is a powerful command that allows you to push a script to managed hosts in the VOM domain
and execute them. Typical use cases could include provisioning a server, updating a patch on
multiple machines, or detecting compliance related anomalies in your environment. This
command can only be executed as root on the central management server and it will execute
commands as root on the target systems. It is quite secure and arbitrary commands cannot be
called unless you bypass it using your own scripts. It utilizes a white listing mechanism for
authorized commands similar to how sudo operates. Please refer to the VOM documentation for
more details.

What is xinfo?

xinfo allows you the options to get information about the state of the VOM infrastructure. Please
refer to the VOM documentation for more details.

What is xclusinfo?

xclusinfo interfaces with the VOM database and extracts information pertaining to the clusters and
their associated objects that are discovered in the data center.

Can I access the VOM Central Database directly?

No. This is not supported at this time.

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.

Trend/Activity: 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.

Document Date: 9/28/2010 [11/15] ©2010 Symantec

 Veritas Operations Manager 3.1
Frequently Asked Questions

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 per Business
Entity.

Is VOM able to create comparisons/differentials between reports?

VOM doesn’t have a specific feature for this, but data from the different reports can be exported
for further analysis.

Performance Statistics
What performance related data is tracked by VOM?

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?

This data is not stored in the Central Management Server (CMS) Database but on the Managed
Host (MH) at /var/opt/VRTSsfmh/stats/. If the VOM CMS is not running, VOM will continue to
collect historic performance statistics on each MH.

Are performance graphs supported on Windows Managed Hosts?

No, this is not supported at this time.

Patches
Is VOM able to proactively show which SF/HA patches are required by a specific host?

VOM offers integration with Veritas Operations Services (VOS) from Symantec, from where it
retrieves the latest information about hotfixes, point patches, and release patches on a per-server
basis. This provides a system administrator an efficient way to manage patches so server
environments are up-to-date.

Document Date: 9/28/2010 [12/15] ©2010 Symantec

 Veritas Operations Manager 3.1
Frequently Asked Questions

My network does not allow for direct internet access. Can I still access the Veritas
Operations Services (VOS) functionality?

Yes. The VOM Central Management Server has support for using a proxy server to connect.

Using VOM, can I deploy any type of patches including Veritas Storage Foundation patches?

Currently the package/patch functionality is used only for VOM specific updates and not for
general purpose usage.

VCS Fire Drill

How is HA fire drill executed?

HA fire drill is executed by invoking the action entry points (.VFD) on the cluster nodes. These are
bundled and shipped with VCS. HA fire drill can be scoped to a service group, cluster or Business
Entity.

Can HA fire drill functionality use the VOS checks?

No. We are evaluating how to consume the VOS checks in VOM.

How is DR fire drill executed?

DR fire drill is executed by on-lining the fire drill (FD) service group on the GCO clusters. An
option is provided to offline the FD service group after successful online. DR fire drill can be
scoped to a service group, cluster or Business Entity.

Can I create fire drill service groups in VOM?

No. Currently VOM does not provide a wizard to create the fire drill service group.

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 and DR fire drills can be scheduled. There is no default schedule like VCSMC had, and
it has to be setup manually. Existing schedules can be viewed and edited thru Policies > Fire Drills
> Schedules tab.

Document Date: 9/28/2010 [13/15] ©2010 Symantec

 Veritas Operations Manager 3.1
Frequently Asked Questions

How do I see the results of fire drill runs?

There are several locations in the VOM Console that this is shown:
1) In the VOM UI, under Policies > Fire Drills, the HA and DR fire drill tabs will give the list of ALL
ongoing and completed runs.
2) Fire drill tab on the service group, cluster and Business Entity detail pages will show the same
information scoped to the selection.
3) Monitor > Tasks will provide the details of the fire drill tasks.

Troubleshooting Information
Central Management Server (CMS)

Configuration/Setup URL: https://<cms hostname>:5634/

Web Console URL: https://<cms hostname>:14161/

Ports required to be opened:

TCP 5634
TCP 14161

VOM Processes running on CMS For Unix/Linux:

/opt/VRTSsfmcs/asa11/bin64s/../bin64/dbsrv11
/opt/VRTSsfmh/bin/xprtld
/opt/VRTSsfmcs/esmweb/jre/bin/java
/opt/VRTSsfmcs/sec/bin/sfmsecd

Commands to start/stop VOM processes on CMS on Unix/Linux:

xprtld: /opt/VRTSsfmh/adm/xprtldctrl <start | stop>
Web console: /opt/VRTSsfmcs/cweb/sfmw <start | stop | restart >
Database: /opt/VRTSsfmcs/config/adm/vxsfmcsdb <start | stop | stop_force>
Authentication: /opt/VRTSsfmcs/sec/bin/sfmsecdctrl <start | stop>

VOM services running on CMS For windows:

Veritas Operations Manager Authentication Service
Veritas Operations Manager Service
Veritas Storage Foundation Messaging Service
SQL Anywhere - SFM3_<hostname>

CMS Log File Locations:

Unix/Linux:

Document Date: 9/28/2010 [14/15] ©2010 Symantec

 Veritas Operations Manager 3.1
Frequently Asked Questions

General: /var/opt/VRTSsfmcs/logs
CMS database installation/upgrade script: /var/VRTSsfmcs/config_db
CMS/HA installation script: /var/VRTSsfmcs/SFMha_dir
Unix/Linux installer log file: /tmp
DB engine: /var/VRTSsfmcs/SFMdb3.dblog

Windows:
General: %AllUsersAppData%\Symantec\VRTSsfmcs\logs
CMS database installation/upgrade script:
%AllUsersAppData%\Symantec\VRTSsfmcs\config_db
Unix/Linux installer log file: %TEMP%

Managed Host (MH)

Port required to be opened:

TCP 5634

VOM processes running on MH:

/opt/VRTSsfmh/bin/xprtld
/opt/VRTSsfmh/bin/sfmh-discovery.pl
/opt/VRTSsfmh/bin/vxdclid

Commands to start/stop VOM processes on Unix/Linux MH:

xprtld: /opt/VRTSsfmh/adm/xprtldctrl <start | stop>
sfmh-discovery: /opt/VRTSsfmh/adm/vxvmdiscovery-ctrl.sh <start | stop>
vxdclid: /opt/VRTSsfmh/etc/vxdcli.sh <start | stop | restart>

VOM services running on windows MH:

Veritas Storage Foundation Messaging Service

MH Log Files:
Unix/Linux: /var/opt/VRTSsfmh/logs
Windows: %AllUsersAppData%\Symantec\VRTSsfmh\logs

Document Date: 9/28/2010 [15/15] ©2010 Symantec