Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Storage and Availability Management

New Release: Veritas Operations Manager (VOM) 3.0

Created: 10 May 2010 • Updated: 11 Jun 2014 • 5 comments
Fahima's picture
+2 2 Votes
Login to vote

Veritas Operations Manager centralizes visibility and control, ensures availability , scales operations, optimizes storage and maintains compliance across your server and storage assets.

Veritas Operations Manager (VOM) 3.0 release includes:

  • Central Management Server on Solaris, Linux & Windows
  • Managed Hosts for Solaris SPARC, Solaris x86, Redhat Linux, Linux on pSeries, HP 11.11, HP 11.23, HP 11.31, Windows, AIX which support all SFHA versions from 4.0+ (Including supporting HP 3.5 read-only)
  • Storage Templates & Volume Migration Add-on
  • Unix Active Management Add-on
  • Windows Active Management Add-on

Key Features:

  • Brand New Dashboard, focusing on Risks and health of your environment
  • Storage Provisioning using Templates
  • Advanced Volume Migration
  • VCS Operations
  • More detailed VCS visualization
  • Performance monitoring and statistics
  • Scheduler: For Reports and Policy Check
  • 20+ new reports
  • Better security configuration
  • Fault Management with detailed analysis for root cause
  • Spanking new user interface based on Highlander, with easier navigation, better searching and filtering
  • Activity monitoring
  • Pre-bundled License Deployment Reporter functionality
  • Pre-bundled Policy Check (was Health Check)

OS Versions:  
Management Server

  • RHEL 4 Update 3, 5 and 5.1
  • SUSE Linux 9 and 10
  • Solaris SPARC 10
  • Windows 2003 x64 and Windows 2008 x64

Managed Hosts

  • Solaris SPARC
  • Solaris x86
  • AIX
  • HP-UX 11.11 , 11.23 and 11.31 (HP -UX 11.11 for SF 3.5)
  • RedHat Linux (x86_64)
  • SuSE Linux (x86_64)
  • Windows 32-bit and 64-bit

Veritas Operations Manager Connect Technical Video Screencasts:

Data Sheet:

End of Life Announcement for Storage Foundation Manager and Veritas Cluster Server Management Console:

Hardware Compatibility List (HCL) for Veritas Operations Manager 3.0 and Storage Foundation 5.1 products on UNIX:

Hardware Compatibility List (HCL) for Veritas Operations Manager 3.0 and Storage Foundation products on Windows:

Release Notes:

Late Breaking News:

Installation and Configuration Guide(s):

 System Administration Guide(s):

Users Guide(s):

Comments 5 CommentsJump to latest comment

cnelson47's picture

customer is deploying VOM 3.0 and has been succesful for all the hosts,until they experienced issues with a Linux server running RHEL 5 64 bit server.Getting permission denied errors. Tries to refresh the host from the console and also gets the permission errors. Any thoughts on where to look first. Deployed a linux 4.1 with no issues.

Login to vote
Kimberley's picture

Please post your question in the forums - you should receive a response there, whereas people might not see your question here in the blog section.

Thanks for participating in the community!

Login to vote
HarryJung's picture

have cust who run his policy (including all signatures)
Now have 1 warning message below which I couldn't explained to him

Root Validity vcsp1n1 Volume rootdg is not a valid Root Volume

volume is ok and root file system was mounted from this volume

dg rootdg       default      default  17000    1280457694.27.vcsp1n1
dm rootdisk     c0t0d0s2     auto     74743    585825000 -

dm rootmirror   c0t1d0s2     auto     74743    585825000 -

v  rootvol      -            ENABLED  ACTIVE   4200000  ROUND     -        root
pl rootvol-01   rootvol      ENABLED  ACTIVE   4200000  CONCAT    -        RW
sd rootdisk-01  rootvol-01   rootdisk 0        4200000  0         c0t0d0   ENA
pl rootvol-02   rootvol      ENABLED  ACTIVE   4200000  CONCAT    -        RW
sd rootmirror-01 rootvol-02  rootmirror 0      4200000  0         c0t1d0   ENA

df -k
/dev/vx/dsk/bootdg/rootvol 2057671  673139 1322802    34%    /

So what caused the root validity warning messages ?

Thanks in advance. 

Login to vote
g_lee's picture

Just wondering - why is it testing rootdg as a root volume? shouldn't it be rootvol? That would be my first thought anyway (ie: instead of specifying rootvol as the Root Volume, rootdg has been entered instead, hence it complains it's not valid since it's not a volume??)

hope that helps

P/S: deleted earlier comment as it was duplicate / you'd corrected the typo in your second post :)

If this post has helped you, please vote or mark as solution

Login to vote
HarryJung's picture

Thanks for you input.
But cust simply select all signatures,eg, not specified rootdg as root volume or any inputs to all signatures.
It seems the built-in "Root validity" signature picked up rootdg as root volume and complained ( I watched it from webex session)

Also there're lots of DMP/DDL warnings

DMP/DDL Enclosure Claim vcsp1n2 APM for ASL is not properly configured

I explained cust that this was due to the relevant apm was not loaded as below;
#vxdmpadm listapm all output
Filename           APM Name           APM Version  Array Types       State
dmpCLARiiON        dmpCLARiiON            1        CLR-A/P           Not-Active <<<<<< not loaded
dmpCLARiiON        dmpCLARiiON            1        CLR-A/PF         Not-Active <<<<<< not loaded

Is this correct ?

In general, can we have any scripts/techical documents for the each signature for troubleshooting purpose ?

Some warning messages are self-explanatory but some are not so difficult to troubleshoot.

Thanks in advance.

Login to vote