Veritas Risk Advisor (VRA) is a data protection and downtime avoidance risk assessment solution that lets you diagnose disaster recovery and high availability (clustering) problems (also called “gaps”) and optimize data protection and reduce the risk of downtime.

VRA enables enterprises to effectively manage business continuity implementations to ensure that critical business data is protected. VRA automatically detects and alerts you to any potential gaps, best practice violations, or service level agreement (SLA) breaches.

What is Comparison Module

The Comparison module helps you identify the host configuration drifts hiding in your IT. Such drifts often fail cluster failover processes, and reduce the availability of your organization’s applications. In this module, you can create comparison groups that include hosts, clusters, or business entities, and easily track configuration differences between them.

The Comparison module uses worksheets and comparison groups.

Worksheet

A worksheet is a logical container of comparison groups. It also contains all suppressions and difference monitoring information. Worksheets are defined and saved at the user level, which means that each user has his/her own worksheet.

Comparison Groups

A comparison group is a dynamic group of hosts that you want to compare. The following types of comparison groups are available:

• Hosts
• Clusters
• Business Entities
• Golden Copy

Each group type behaves differently in terms of the group scope and comparison functionality.

You begin by creating a worksheet, and then by creating comparison groups. Once defined, comparison groups can be assigned to a worksheet.

Once the worksheets and comparison groups are created, you can compare the host configurations with the following options:

• Hardware
• Software
• Operating System
• Users and Groups
• OS Kernel Parameters / Limits

Learning More

For more information on working with Comparison Module, see “Using the Comparison module” in the Veritas Risk Advisor User’s Guide.

You can access the User’s Guide and other VRA documentation in the Documents area of the SORT website.

Veritas Risk Advisor (VRA) is a data protection and downtime avoidance risk assessment solution that lets you diagnose disaster recovery and high availability (clustering) problems (also called “gaps”) and optimize data protection and reduce the risk of downtime.

VRA enables enterprises to effectively manage business continuity implementations to ensure that critical business data is protected. VRA automatically detects and alerts you to any potential gaps, best practice violations, or service level agreement (SLA) breaches.

VRA’s Report Generator automatically generates detailed reports describing your configuration and the gaps that it detected from information extracted from the VRA database.

VRA allows you generate multiple reports at the same time.

Also you can export the content into the MS Word, PDF, and MS Excel format.

VRA Report Types

VRA has the following reports:

• Scan Status
• System Event Log
• Ticket Details
• Storage Allocation Optimization
• Unreplicated Data on Replicated Hosts
• NetApp Filer Replication Summary
• Unsynchronized Remote Replication
• Old Replicas
• Standby Pairs and so on

Report scheduling

VRA also lets you schedule when reports are automatically generated and sent to one or more email destinations that you configure. New reports automatically generate each time before they are sent. You may also choose to save the generated reports in the file system and access them later.

Learning More

For more information on working with Reports, see “VRA reporting” in the Veritas Risk Advisor User’s Guide.

You can access the User’s Guide and other VRA documentation in the Documents area of the SORT website.

Hello,

we have a 4 node VCS 5.1 cluster (EngineVersion 5.1.10.40) configured with I/O fencing.  2 of the nodes are for the applications and the other 2 for the DB.

Applications and the DB are configured to run only on the designated nodes.

We are testing a complete heartbeat failure by shutting down the switch. The fencing works properly and three nodes are rebooted.

We have observed a situation where 2 of the services was not started after both application nodes have rebooted. The service was in PARTIAL state.

mmsoap-rg    State                 lpdmc1p    |PARTIAL|
mmsoap-rg    State                 lpdmc2p    |OFFLINE|

smppc-rg     State                 lpdmc1p    |PARTIAL|
smppc-rg     State                 lpdmc2p    |OFFLINE|

Here it is their configuration:

group mmsoap-rg (
        SystemList = { lpdmc1p = 0, lpdmc2p = 1 }
        AutoStartList = { lpdmc1p, lpdmc2p }
        )

        IP mmsoap-lh-res (
                Device = bond0
                Address = "10.40.248.199"
                NetMask = "255.255.255.224"
                )

        LVMLogicalVolume opt-mmsoap-lv-res (
                VolumeGroup = mmsoap-vg
                LogicalVolume = opt-mmsoap-lv
                )

        LVMLogicalVolume var-opt-mmsoap-lv-res (
                VolumeGroup = mmsoap-vg
                LogicalVolume = var-opt-mmsoap-lv
                )

        LVMVolumeGroup mmsoap-vg-res (
                VolumeGroup = mmsoap-vg
                EnableLVMTagging = 1
                )

        Mount opt-mmsoap-mnt-res (
                MountOpt = "rw,noatime,nodiratime,nosuid,nodev"
                FsckOpt = "-y"
                BlockDevice = "/dev/mapper/mmsoap--vg-opt--mmsoap--lv"
                MountPoint = "/opt/mmsoap"
                FSType = ext3
                )

        Mount var-opt-mmsoap-mnt-res (
                MountOpt = "rw,noatime,nodiratime,nosuid,nodev"
                FsckOpt = "-y"
                BlockDevice = "/dev/mapper/mmsoap--vg-var--opt--mmsoap--lv"
                MountPoint = "/var/opt/mmsoap"
                FSType = ext3
                )

        NIC mmsoap-nic-res (
                Device = bond0
                )

        SicapApplication mmsoap-app-res (
                AppUser = mmsoap
                )

        requires group smppc-rg online global firm
        mmsoap-app-res requires mmsoap-lh-res
        mmsoap-app-res requires opt-mmsoap-mnt-res
        mmsoap-app-res requires var-opt-mmsoap-mnt-res
        mmsoap-lh-res requires mmsoap-nic-res
        opt-mmsoap-lv-res requires mmsoap-vg-res
        opt-mmsoap-mnt-res requires opt-mmsoap-lv-res
        var-opt-mmsoap-lv-res requires mmsoap-vg-res
        var-opt-mmsoap-mnt-res requires var-opt-mmsoap-lv-res

        // resource dependency tree
        //
        //      group mmsoap-rg
        //      {
        //      SicapApplication mmsoap-app-res
        //          {
        //          IP mmsoap-lh-res
        //              {
        //              NIC mmsoap-nic-res
        //              }
        //          Mount opt-mmsoap-mnt-res
        //              {
        //              LVMLogicalVolume opt-mmsoap-lv-res
        //                  {
        //                  LVMVolumeGroup mmsoap-vg-res
        //                  }
        //              }
        //          Mount var-opt-mmsoap-mnt-res
        //              {
        //              LVMLogicalVolume var-opt-mmsoap-lv-res
        //                  {
        //                  LVMVolumeGroup mmsoap-vg-res
        //                  }
        //              }
        //          }
        //      }

group smppc-rg (
        SystemList = { lpdmc1p = 0, lpdmc2p = 1 }
        AutoStartList = { lpdmc1p, lpdmc2p }
        )

        IP smppc-lh-res (
                Device = bond0
                Address = "10.40.248.200"
                NetMask = "255.255.255.224"
                )

        LVMLogicalVolume opt-smppc-lv-res (
                VolumeGroup = smppc-vg
                LogicalVolume = opt-smppc-lv
                )

        LVMLogicalVolume var-opt-smppc-lv-res (
                VolumeGroup = smppc-vg
                LogicalVolume = var-opt-smppc-lv
                )

        LVMVolumeGroup smppc-vg-res (
                VolumeGroup = smppc-vg
                EnableLVMTagging = 1
                )

        Mount opt-smppc-mnt-res (
                MountOpt = "rw,noatime,nodiratime,nosuid,nodev"
                FsckOpt = "-y"
                BlockDevice = "/dev/mapper/smppc--vg-opt--smppc--lv"
                MountPoint = "/opt/smppc"
                FSType = ext3
                )

        Mount var-opt-smppc-mnt-res (
                MountOpt = "rw,noatime,nodiratime,nosuid,nodev"
                FsckOpt = "-y"
                BlockDevice = "/dev/mapper/smppc--vg-var--opt--smppc--lv"
                MountPoint = "/var/opt/smppc"
                FSType = ext3
                )

        NIC smppc-nic-res (
                Device = bond0
                )

        SicapApplication smppc-app-res (
                AppUser = smppc
                )

        requires group mmg-rg online global firm
        opt-smppc-lv-res requires smppc-vg-res
        opt-smppc-mnt-res requires opt-smppc-lv-res
        smppc-app-res requires opt-smppc-mnt-res
        smppc-app-res requires smppc-lh-res
        smppc-app-res requires var-opt-smppc-mnt-res
        smppc-lh-res requires smppc-nic-res
        var-opt-smppc-lv-res requires smppc-vg-res
        var-opt-smppc-mnt-res requires var-opt-smppc-lv-res

        // resource dependency tree
        //
        //      group smppc-rg
        //      {
        //      SicapApplication smppc-app-res
        //          {
        //          Mount opt-smppc-mnt-res
        //              {
        //              LVMLogicalVolume opt-smppc-lv-res
        //                  {
        //                  LVMVolumeGroup smppc-vg-res
        //                  }
        //              }
        //          IP smppc-lh-res
        //              {
        //              NIC smppc-nic-res
        //              }
        //          Mount var-opt-smppc-mnt-res
        //              {
        //              LVMLogicalVolume var-opt-smppc-lv-res
        //                  {
        //                  LVMVolumeGroup smppc-vg-res
        //                  }
        //              }
        //          }
        //      }

The state of its resources:

#Resource     Attribute             System     Value
mmsoap-lh-res State                 lpdmc1p    OFFLINE
mmsoap-lh-res State                 lpdmc2p    OFFLINE

opt-mmsoap-lv-res State                 lpdmc1p    ONLINE
opt-mmsoap-lv-res State                 lpdmc2p    OFFLINE

var-opt-mmsoap-lv-res State                 lpdmc1p    ONLINE
var-opt-mmsoap-lv-res State                 lpdmc2p    OFFLINE

mmsoap-vg-res State                 lpdmc1p    OFFLINE
mmsoap-vg-res State                 lpdmc2p    OFFLINE

opt-mmsoap-mnt-res State                 lpdmc1p    OFFLINE
opt-mmsoap-mnt-res State                 lpdmc2p    OFFLINE

var-opt-mmsoap-mnt-res State                 lpdmc1p    OFFLINE
var-opt-mmsoap-mnt-res State                 lpdmc2p    OFFLINE

mmsoap-nic-res State                 lpdmc1p    ONLINE
mmsoap-nic-res State                 lpdmc2p    ONLINE

mmsoap-app-res State                 lpdmc1p    OFFLINE
mmsoap-app-res State                 lpdmc2p    OFFLINE

smppc-lh-res State                 lpdmc1p    OFFLINE
smppc-lh-res State                 lpdmc2p    OFFLINE

opt-smppc-lv-res State                 lpdmc1p    ONLINE
opt-smppc-lv-res State                 lpdmc2p    OFFLINE

var-opt-smppc-lv-res State                 lpdmc1p    ONLINE
var-opt-smppc-lv-res State                 lpdmc2p    OFFLINE

smppc-vg-res State                 lpdmc1p    OFFLINE
smppc-vg-res State                 lpdmc2p    OFFLINE

opt-smppc-mnt-res State                 lpdmc1p    OFFLINE
opt-smppc-mnt-res State                 lpdmc2p    OFFLINE

var-opt-smppc-mnt-res State                 lpdmc1p    OFFLINE
var-opt-smppc-mnt-res State                 lpdmc2p    OFFLINE

smppc-nic-res State                 lpdmc1p    ONLINE
smppc-nic-res State                 lpdmc2p    ONLINE

smppc-app-res State                 lpdmc1p    OFFLINE
smppc-app-res State                 lpdmc2p    OFFLINE

In the engine log I had the following messages related to them:

2016/04/05 02:27:45 VCS NOTICE V-16-1-10181 Group mmsoap-rg AutoRestart set to 1
2016/04/05 02:27:46 VCS INFO V-16-1-10304 Resource mmsoap-lh-res (Owner: Unspecified, Group: mmsoap-rg) is offline on lpdmc1p (First probe)
2016/04/05 02:27:46 VCS INFO V-16-1-10297 Resource opt-mmsoap-lv-res (Owner: Unspecified, Group: mmsoap-rg) is online on lpdmc1p (First probe)
2016/04/05 02:27:46 VCS NOTICE V-16-1-10233 Clearing Restart attribute for group mmsoap-rg on all nodes
2016/04/05 02:27:46 VCS INFO V-16-1-10297 Resource var-opt-mmsoap-lv-res (Owner: Unspecified, Group: mmsoap-rg) is online on lpdmc1p (First probe)
2016/04/05 02:27:46 VCS NOTICE V-16-1-10233 Clearing Restart attribute for group mmsoap-rg on all nodes
2016/04/05 02:27:46 VCS INFO V-16-1-10304 Resource opt-mmsoap-mnt-res (Owner: Unspecified, Group: mmsoap-rg) is offline on lpdmc1p (First probe)
2016/04/05 02:27:46 VCS INFO V-16-1-10304 Resource var-opt-mmsoap-mnt-res (Owner: Unspecified, Group: mmsoap-rg) is offline on lpdmc1p (First probe)
2016/04/05 02:27:47 VCS INFO V-16-1-10304 Resource mmsoap-app-res (Owner: Unspecified, Group: mmsoap-rg) is offline on lpdmc1p (First probe)
2016/04/05 02:27:48 VCS INFO V-16-1-10304 Resource mmsoap-vg-res (Owner: Unspecified, Group: mmsoap-rg) is offline on lpdmc1p (First probe)
2016/04/05 02:27:48 VCS NOTICE V-16-1-10438 Group mmsoap-rg has been probed on system lpdmc1p

if I manually onlined the group that was OK but I had to separately online both:

2016/04/05 05:58:03 VCS INFO V-16-1-50135 User root fired command: hagrp -online -any smppc-rg  localclus  from localhost
2016/04/05 05:58:03 VCS NOTICE V-16-1-10301 Initiating Online of Resource smppc-lh-res (Owner: Unspecified, Group: smppc-rg) on System lpdmc1p
2016/04/05 05:58:03 VCS NOTICE V-16-1-10301 Initiating Online of Resource smppc-vg-res (Owner: Unspecified, Group: smppc-rg) on System lpdmc1p
2016/04/05 05:58:03 VCS NOTICE V-16-1-10301 Initiating Online of Resource opt-smppc-mnt-res (Owner: Unspecified, Group: smppc-rg) on System lpdmc1p
2016/04/05 05:58:03 VCS NOTICE V-16-1-10301 Initiating Online of Resource var-opt-smppc-mnt-res (Owner: Unspecified, Group: smppc-rg) on System lpdmc1p
2016/04/05 05:58:04 VCS ERROR V-16-10031-14001 (lpdmc1p) LVMVolumeGroup:smppc-vg-res:online:Activation of volume group failed.
2016/04/05 05:58:05 VCS INFO V-16-1-10298 Resource opt-smppc-mnt-res (Owner: Unspecified, Group: smppc-rg) is online on lpdmc1p (VCS initiated)
2016/04/05 05:58:05 VCS INFO V-16-1-10298 Resource var-opt-smppc-mnt-res (Owner: Unspecified, Group: smppc-rg) is online on lpdmc1p (VCS initiated)
2016/04/05 05:58:06 VCS INFO V-16-1-10298 Resource smppc-vg-res (Owner: Unspecified, Group: smppc-rg) is online on lpdmc1p (VCS initiated)
2016/04/05 05:58:16 VCS INFO V-16-1-10298 Resource smppc-lh-res (Owner: Unspecified, Group: smppc-rg) is online on lpdmc1p (VCS initiated)
2016/04/05 05:58:16 VCS NOTICE V-16-1-10301 Initiating Online of Resource smppc-app-res (Owner: Unspecified, Group: smppc-rg) on System lpdmc1p
2016/04/05 05:58:16 VCS INFO V-16-1-0 (lpdmc1p) SicapApplication:???:???:Running preonline for resource smppc-app-res
2016/04/05 05:58:16 VCS INFO V-16-1-0 (lpdmc1p) SicapApplication:???:???:Preonline for resource smppc-app-res finished
2016/04/05 05:58:16 VCS INFO V-16-1-0 (lpdmc1p) SicapApplication:???:???:Starting resource smppc-app-res
2016/04/05 05:58:21 VCS INFO V-16-1-0 (lpdmc1p) SicapApplication:???:???:Resource smppc-app-res is started
2016/04/05 05:58:34 VCS INFO V-16-1-10298 Resource smppc-app-res (Owner: Unspecified, Group: smppc-rg) is online on lpdmc1p (VCS initiated)
2016/04/05 05:58:34 VCS NOTICE V-16-1-10447 Group smppc-rg is online on system lpdmc1p
2016/04/05 05:59:52 VCS INFO V-16-1-50135 User root fired command: hagrp -online -any mmsoap-rg  localclus  from localhost
2016/04/05 05:59:52 VCS NOTICE V-16-1-10301 Initiating Online of Resource mmsoap-lh-res (Owner: Unspecified, Group: mmsoap-rg) on System lpdmc1p
2016/04/05 05:59:52 VCS NOTICE V-16-1-10301 Initiating Online of Resource mmsoap-vg-res (Owner: Unspecified, Group: mmsoap-rg) on System lpdmc1p
2016/04/05 05:59:52 VCS NOTICE V-16-1-10301 Initiating Online of Resource opt-mmsoap-mnt-res (Owner: Unspecified, Group: mmsoap-rg) on System lpdmc1p
2016/04/05 05:59:52 VCS NOTICE V-16-1-10301 Initiating Online of Resource var-opt-mmsoap-mnt-res (Owner: Unspecified, Group: mmsoap-rg) on System lpdmc1p
2016/04/05 05:59:53 VCS ERROR V-16-10031-14001 (lpdmc1p) LVMVolumeGroup:mmsoap-vg-res:online:Activation of volume group failed.
2016/04/05 05:59:53 VCS INFO V-16-1-10298 Resource opt-mmsoap-mnt-res (Owner: Unspecified, Group: mmsoap-rg) is online on lpdmc1p (VCS initiated)
2016/04/05 05:59:53 VCS INFO V-16-1-10298 Resource var-opt-mmsoap-mnt-res (Owner: Unspecified, Group: mmsoap-rg) is online on lpdmc1p (VCS initiated)
2016/04/05 05:59:54 VCS INFO V-16-1-10298 Resource mmsoap-vg-res (Owner: Unspecified, Group: mmsoap-rg) is online on lpdmc1p (VCS initiated)
2016/04/05 06:00:02 VCS INFO V-16-1-10298 Resource mmsoap-lh-res (Owner: Unspecified, Group: mmsoap-rg) is online on lpdmc1p (VCS initiated)
2016/04/05 06:00:02 VCS NOTICE V-16-1-10301 Initiating Online of Resource mmsoap-app-res (Owner: Unspecified, Group: mmsoap-rg) on System lpdmc1p
2016/04/05 06:00:02 VCS INFO V-16-1-0 (lpdmc1p) SicapApplication:???:???:Running preonline for resource mmsoap-app-res
2016/04/05 06:00:03 VCS INFO V-16-1-0 (lpdmc1p) SicapApplication:???:???:Preonline for resource mmsoap-app-res finished
2016/04/05 06:00:03 VCS INFO V-16-1-0 (lpdmc1p) SicapApplication:???:???:Starting resource mmsoap-app-res
2016/04/05 06:00:09 VCS INFO V-16-1-0 (lpdmc1p) SicapApplication:???:???:Resource mmsoap-app-res is started
2016/04/05 06:00:21 VCS INFO V-16-1-10298 Resource mmsoap-app-res (Owner: Unspecified, Group: mmsoap-rg) is online on lpdmc1p (VCS initiated)
2016/04/05 06:00:21 VCS NOTICE V-16-1-10447 Group mmsoap-rg is online on system lpdmc1p

What can I do to have this service started automatically in such a case when the HB is lost and the nodes are rebooted due to fencing panic?

Thank you in advance,

Laszlo

Creating a subdisk manually, but it is thorwing error eventhough I put the correct offset.

bash-3.2# vxprint  -htg  appdg   |  grep   -i  appdisk4
dm appdisk4     disk_4       auto     65536    2031232  -
sd appdisk4-02  -            appdisk4 204800   409600   -         disk_4   ENA
sd appdisk4-03  -            appdisk4 614400   819200   -         disk_4   ENA
sd appdisk4-01  vol1-01      appdisk4 0        204800   0         disk_4   ENA
bash-3.2# vxmake -g appdg sd appdisk4-04 appdisk4,819200,1024000
VxVM vxmake ERROR V-5-1-10127 creating subdisk appdisk4-04:
        Subdisk appdisk4-04 would overlap subdisk appdisk4-03

I want to remove I/O fencing completely and start VCS (in test environment), but every time I fire hastart command, HAD tries to start I/O fencing driver and fails to start HAD. I have removed the registered key, disabled fencing in /etc/vxfenmode file and rebooted the system couple of times but couldn't start HAD.

Please advise.

OS- Solaris 10

VCS 5.1

Thanks,

Hi,

We have got NetBackup 7.5.0.6 running on Windows Server 2008 and currently backing up data on SAN Storage.

I want to enable deduplication on it.

Could you please provide me the best practice procedure to do so ?

Where the deduplication should be enabled on client or Server level and how it will be reflected on SAN storage?

Please adivse

Regards,

--Tarek--

Team,

Following is the server setup and need your valuable time & advise in setting up VCS between guests.

Control domain server ( t5220 Sparc with solaris 11 ) with two guests ldoms ( ldom1 & ldom2 ) both with solaris 11.

Control domain has two physical network interfaces (net0/net1) and these two interfaces are assigned to each ldom as virtual interfaces and configured with IPMP.

4 SAN storage LANs allocate to control domain and presented two disks ( 1 for OS & 1 for database ) to one each ldom..

I want to configure VCS between these two guest ldoms and whenever ldom1 goest down then the database has to be failed over to ldom2 & vice-versa..

I need your guidance in implementing VCS b/w two guests and heartbeat setup.

I know my requirement is weird as configuring VCS on a standalone box between two guests.

Regards,

Raji

It seems that i can't find more information about Veritas Cluster Server. Is it being bundled inside a package ? sorry. i am new to this stuff.

I would like to use Veritas Cluster Server to achieve high availability and automatic fail over for my applications.

These application are java applications with some services with the backend databases using Sybase

The java applications can be broken into 2 parts : web layer and application layer.

The underlying infrastructure will be in RHEL Linux for java applications and database (Sybase)

My question is : is VCS supporting seamless automatic failover for the java services including database services without requiring manual intervention ?

What i want to achieve is : after i setup active-passive for application layer, i expect the active node to automatically failover to passive node and immediately the passive node become active node

Does Veritas InfoScale Availability  compatible with Triple A Plus (http://www.bankandtechguide.com/company/52091/products/941/triple-a-plus) ?

The Triple A Plus application is deployed in Linux environment with Sybase Database on Linux and Java Application on Linux as well

This is a new system of infoscale v7 on RHEL v6.

Bidirectional port 5634  is open between the Infoscale  management Server (RHEL) and host. (solaris 10 -sparc).

Also one way port 22 is open from mgmt server to managed host.

Host has VRTSsfmh running and listening on port 5634:

solvcstst01:/etc/ssh {root}: ps -ef|grep xprtld
    root  3893     1   0   Mar 01 ?           0:47 /opt/VRTSsfmh/bin/xprtld -X 1 /etc/opt/VRTSsfmh/xprtld.conf
    root  7477 24284   0 08:28:34 pts/1       0:00 grep xprtld 

I've allowed (temporary) direct root login from the mgmt server to the managed host and entered those credentials.

Error when adding host from infoscale server: 

"Registration with Management Server failed"

Error log:

Add Host Log
------------
Started [04/12/2016 08:30:23]

[04/12/2016 08:30:23] [solvcstst01.vch.ca] type  rh solvcstst01.vch.ca cms 
[04/12/2016 08:30:23] [solvcstst01.vch.ca] creating task for Add host
[04/12/2016 08:30:24] [solvcstst01.vch.ca] Check if MH is pingable from MS and get vital information from MH
[04/12/2016 08:30:24] [solvcstst01.vch.ca] Output: {
"XPRTLD_VERSION" :  "5.0.196.0",
"LOCAL_NAME" : "solvcstst01.vch.ca",
"LOCAL_ADDR" : "139.173.8.6",
"PEER_NAME" : "UNKNOWN",
"PEER_ADDR" : "10.248.224.116",
"LOCAL_TIME" : "1460475024",
"LOCALE" : "UNKNOWN",
"DOMAIN_MODE" : "FALSE",
"QUIESCE_MODE" : "RUNNING",
"OSNAME" : "SunOS",
"OSRELEASE" : "5.10",
"CPUTYPE" : "sparc",
"OSUUID" : "{00020014-4ffa-b092-0000-000084fbfc3f}",
"DOMAINS" : {
    }
}

[04/12/2016 08:30:24] [solvcstst01.vch.ca] Return code: 0
[04/12/2016 08:30:24] [solvcstst01.vch.ca] Checking if MH version [5.0.196.0] is same or greater than as that of least supported MH version [5.0.0.0]
[04/12/2016 08:30:24] [solvcstst01.vch.ca] ADD_HOST_PRECONFIG_CHK
[04/12/2016 08:30:24] [solvcstst01.vch.ca] {"JOB":{"RETURNCODE":0,"ERROR":"Success","NAME":"add_host","OUTPUT":"ADD_HOST_PRECONFIG_CHK","STATE":"SUCCESS","PROGRESS":1}}
[04/12/2016 08:30:24] [solvcstst01.vch.ca] retrieving Agent password
[04/12/2016 08:30:24] [solvcstst01.vch.ca] ADD_HOST_INPUT_PARAM_CHK
[04/12/2016 08:30:24] [solvcstst01.vch.ca] {"JOB":{"RETURNCODE":0,"ERROR":"Success","NAME":"add_host","OUTPUT":"ADD_HOST_INPUT_PARAM_CHK","STATE":"SUCCESS","PROGRESS":6}}
[04/12/2016 08:30:24] [solvcstst01.vch.ca] user name is "root"
[04/12/2016 08:30:24] [solvcstst01.vch.ca] ADD_HOST_CONTACTING_MH
[04/12/2016 08:30:24] [solvcstst01.vch.ca] {"JOB":{"RETURNCODE":0,"ERROR":"Success","NAME":"add_host","OUTPUT":"ADD_HOST_CONTACTING_MH","STATE":"SUCCESS","PROGRESS":20}}
[04/12/2016 08:30:25] [solvcstst01.vch.ca] Output: HTTP/1.1 302 OK
Status: 307 Moved
Location: /admin/htdocs/cs_config.htm 


[04/12/2016 08:30:25] [solvcstst01.vch.ca] Return code: 768
[04/12/2016 08:30:25] [solvcstst01.vch.ca] Checking to see if CS is reachable from MH
[04/12/2016 08:30:25] [solvcstst01.vch.ca] Output: {
"XPRTLD_VERSION" :  "7.0.0.0",
"LOCAL_NAME" : "lvmvom01.healthbc.org",
"LOCAL_ADDR" : "10.248.224.116",
"PEER_NAME" : "solvcstst01.vch.ca",
"PEER_ADDR" : "139.173.8.6",
"LOCAL_TIME" : "1460475025",
"LOCALE" : "en_US.UTF-8",
"DOMAIN_MODE" : "TRUE",
"QUIESCE_MODE" : "RUNNING",
"OSNAME" : "Linux",
"OSRELEASE" : "2.6.32-573.22.1.el6.x86_64",
"CPUTYPE" : "x86_64",
"OSUUID" : "{00010050-56ad-1e25-0000-000000000000}",
"DOMAINS" : {
    "sfm://lvmvom01.healthbc.org:5634/" : {
        "admin_url" : "vxss://lvmvom01.healthbc.org:14545/sfm_admin/sfm_domain/vx",
        "primary_broker" : "vxss://lvmvom01.healthbc.org:14545/sfm_agent/sfm_domain/vx"
        }
    }
}

[04/12/2016 08:30:25] [solvcstst01.vch.ca] Return code: 0
[04/12/2016 08:30:25] [solvcstst01.vch.ca] CS host (lvmvom01.healthbc.org) is resolvable
[04/12/2016 08:30:25] [solvcstst01.vch.ca] Trying to figure out if host is already part of the domain
[04/12/2016 08:30:25] [solvcstst01.vch.ca] ADD_HOST_SEND_CRED_MH
[04/12/2016 08:30:25] [solvcstst01.vch.ca] {"JOB":{"RETURNCODE":0,"ERROR":"Success","NAME":"add_host","OUTPUT":"ADD_HOST_SEND_CRED_MH","STATE":"SUCCESS","PROGRESS":30}}
[04/12/2016 08:30:26] [solvcstst01.vch.ca] Output: SUCCESS

[04/12/2016 08:30:26] [solvcstst01.vch.ca] Return code: 0
[04/12/2016 08:30:28] [solvcstst01.vch.ca] push_exec command succeeded [/opt/VRTSsfmh/bin/getvmid_script]
[04/12/2016 08:30:29] [solvcstst01.vch.ca] ADD_HOST_INIT_DISCOVERY
[04/12/2016 08:30:29] [solvcstst01.vch.ca] {"JOB":{"RETURNCODE":0,"ERROR":"Success","NAME":"add_host","OUTPUT":"ADD_HOST_INIT_DISCOVERY","STATE":"SUCCESS","PROGRESS":75}}
[04/12/2016 08:30:29] [solvcstst01.vch.ca] Executing /opt/VRTSsfmh/bin/xprtlc -u "root" -t 1200 -j /var/opt/VRTSsfmh/xprtlc-payload-x2s4xFEb -l https://solvcstst01.vch.ca:5634/admin/cgi-bin/sfme.pl operation=configure_mh&cs-hostname=lvmvom01.healthbc.org&cs-ip=10.248.224.116&mh-hostname=solvcstst01.vch.ca&agent-password=******
[04/12/2016 08:30:32] [solvcstst01.vch.ca] Waiting for output from configure_mh----
[04/12/2016 08:30:32] [solvcstst01.vch.ca] ADD_HOST_INIT_DISCOVERY
[04/12/2016 08:30:32] [solvcstst01.vch.ca] {"JOB":{"RETURNCODE":0,"ERROR":"Success","NAME":"add_host","OUTPUT":"ADD_HOST_INIT_DISCOVERY","STATE":"SUCCESS","PROGRESS":80}}
[04/12/2016 08:30:33] [solvcstst01.vch.ca] Waiting for output from configure_mh----
[04/12/2016 08:30:33] [solvcstst01.vch.ca] ADD_HOST_INIT_DISCOVERY
[04/12/2016 08:30:33] [solvcstst01.vch.ca] {"JOB":{"RETURNCODE":0,"ERROR":"Success","NAME":"add_host","OUTPUT":"ADD_HOST_INIT_DISCOVERY","STATE":"SUCCESS","PROGRESS":80}}
[04/12/2016 08:30:45] [solvcstst01.vch.ca] Waiting for output from configure_mh----
[04/12/2016 08:30:45] [solvcstst01.vch.ca] ADD_HOST_INIT_DISCOVERY
[04/12/2016 08:30:45] [solvcstst01.vch.ca] {"JOB":{"RETURNCODE":0,"ERROR":"Success","NAME":"add_host","OUTPUT":"ADD_HOST_INIT_DISCOVERY","STATE":"SUCCESS","PROGRESS":80}}
[04/12/2016 08:30:56] [solvcstst01.vch.ca] Waiting for output from configure_mh----
[04/12/2016 08:30:56] [solvcstst01.vch.ca] ADD_HOST_INIT_DISCOVERY
[04/12/2016 08:30:56] [solvcstst01.vch.ca] {"JOB":{"RETURNCODE":0,"ERROR":"Success","NAME":"add_host","OUTPUT":"ADD_HOST_INIT_DISCOVERY","STATE":"SUCCESS","PROGRESS":80}}
[04/12/2016 08:30:56] [solvcstst01.vch.ca] Waiting for output from configure_mh----
[04/12/2016 08:30:56] [solvcstst01.vch.ca] ADD_HOST_INIT_DISCOVERY
[04/12/2016 08:30:56] [solvcstst01.vch.ca] {"JOB":{"RETURNCODE":0,"ERROR":"Success","NAME":"add_host","OUTPUT":"ADD_HOST_INIT_DISCOVERY","STATE":"SUCCESS","PROGRESS":80}}
[04/12/2016 08:30:57] [solvcstst01.vch.ca] Waiting for output from configure_mh----
[04/12/2016 08:30:57] [solvcstst01.vch.ca] ADD_HOST_INIT_DISCOVERY
[04/12/2016 08:30:57] [solvcstst01.vch.ca] {"JOB":{"RETURNCODE":0,"ERROR":"Success","NAME":"add_host","OUTPUT":"ADD_HOST_INIT_DISCOVERY","STATE":"SUCCESS","PROGRESS":80}}
[04/12/2016 08:30:57] [solvcstst01.vch.ca] Waiting for output from configure_mh----
[04/12/2016 08:30:57] [solvcstst01.vch.ca] ADD_HOST_INIT_DISCOVERY
[04/12/2016 08:30:57] [solvcstst01.vch.ca] {"JOB":{"RETURNCODE":0,"ERROR":"Success","NAME":"add_host","OUTPUT":"ADD_HOST_INIT_DISCOVERY","STATE":"SUCCESS","PROGRESS":80}}
[04/12/2016 08:30:57] [solvcstst01.vch.ca] Waiting for output from configure_mh----
[04/12/2016 08:30:57] [solvcstst01.vch.ca] ADD_HOST_INIT_DISCOVERY
[04/12/2016 08:30:57] [solvcstst01.vch.ca] {"JOB":{"RETURNCODE":0,"ERROR":"Success","NAME":"add_host","OUTPUT":"ADD_HOST_INIT_DISCOVERY","STATE":"SUCCESS","PROGRESS":80}}
[04/12/2016 08:30:58] [solvcstst01.vch.ca] Waiting for output from configure_mh----
[04/12/2016 08:30:58] [solvcstst01.vch.ca] ADD_HOST_INIT_DISCOVERY
[04/12/2016 08:30:58] [solvcstst01.vch.ca] {"JOB":{"RETURNCODE":0,"ERROR":"Success","NAME":"add_host","OUTPUT":"ADD_HOST_INIT_DISCOVERY","STATE":"SUCCESS","PROGRESS":80}}
[04/12/2016 08:30:58] [solvcstst01.vch.ca] fancy_die
[04/12/2016 08:30:58] [solvcstst01.vch.ca] CONFIGURE_MH_REG_FAILED
[04/12/2016 08:30:58] [solvcstst01.vch.ca] {"JOB":{"RETURNCODE":-1,"ERROR":"CONFIGURE_MH_REG_FAILED","NAME":"job_add_host","OUTPUT":"","STATE":"FAILED","PROGRESS":100}}{"RESULT":{"RETURNCODE":-1,"UMI":"V-383-50513-5760","ERROR":"CONFIGURE_MH_REG_FAILED","NAME":"add_host","TASKID":"{iHUXu2IK1ZRkTo7H}"}}
[04/12/2016 08:30:58] [solvcstst01.vch.ca] fancy_dead 

Veritas High Availability Agent Pack 1Q 2016 is now available on SORT: https://sort.veritas.com/agents.

Application Agents

• Added support for JBoss 8.x and 9.x. The JBoss Application Server 8.0 and later releases are now known as WildFly.
• Added support for Infomatica 9.5.1 on the AIX, Linux, and Solaris operating systems.
• Added support for SAP HANA SPS11.

Replication Agents

• Enhanced EMC SRDF/SRDFSnap agent to support TimeFinder Snap and TimeFinder Clone in the CVM environment.
• Enhanced EMC SRDF/SRDFSnap agent to support CVM/CFS (SFRAC) on the Solaris 11 SPARC operating system.
• Enhanced the HTC agent support on the Solaris x86 operating system.
• Enhanced the HP 3PAR RemoteCopy agent to support on the Solaris 11 SPARC operating system.
• Enhanced the HP 3PAR RemoteCopy agent to support in the CFS environment on the AIX, Linux, and Solaris operating systems.
• Added a new attribute known as VCSResLock, which ensures the serialized management in case of a parallel application on the AIX, Linux, and Solaris operating systems.

Important Fixes

• IBM WebSphere agent
  • Filter process pattern is updated in agent to find the appropriate WebSphere process.
• IBM Informix Dynamic Server
  • In the Solaris non-global zone, the agent now monitors the process whose PPID is the PID of the zone scheduler process.
  • Updated agent start operation, the oninit –yw command is used to start the Informix server. 
  • Updated agent stop operation,  the onshutdown.sh script is used to stop the Informix server.   
• Hitachi TrueCopy; HP XP Continuous Access
  • Updated agent to rescan all slave nodes before importing the shared DiskGroup during online.
  • If LinkMonitor attribute is set to 2, the agent logs messages when the state of the Hitachi TrueCopy instance changes from PAIR to NON-PAIR in every monitor cycle.
  • AllowAutoFailoverInterval functionality, which allows failover even if the SplitTakeover attribute is set to 0 in case FENCE level NEVER, is now supported in the GCO environment.

I want to switch the application to minos2，but I cannot select the system

No system，why？

root@minos1(/)# hastatus -sum

-- SYSTEM STATE
-- System               State                Frozen              

A  minos1               RUNNING              0                    

-- GROUP STATE
-- Group           System               Probed     AutoDisabled    State          

B  ClusterService  minos1               Y          N               ONLINE         
B  EMS             minos1               Y          N               ONLINE         
B  replication     minos1               Y          N               ONLINE         

-- REMOTE CLUSTER STATE
-- Cluster         State     

N  minos2          RUNNING   

-- REMOTE SYSTEM STATE
-- cluster:system       State                Frozen              

O  minos2:minos2        RUNNING              0                   

https://www.veritas.com/support/en_US/article.TECH...

Where to find these utilities?

preconvert/showconvert/doconvert

Hi ,

I am seeing below errror messages in dmpevent.log /var/adm/vx/dmpevents.log

Mon Mar 28 11:23:27.786: SCSI error occured on Path sdv: opcode=0x5f reported reservation conflict
 (status=0xc, key=0x0, asc=0x0, ascq=0x0)
 Mon Mar 28 11:23:27.788: SCSI error occured on Path sdv: opcode=0x5f reported reservation conflict
 (status=0xc, key=0x0, asc=0x0, ascq=0x0)
 Mon Mar 28 11:23:27.790: SCSI error occured on Path sdu: opcode=0x5f reported reservation conflict
 (status=0xc, key=0x0, asc=0x0, ascq=0x0)
 Mon Mar 28 11:23:27.792: SCSI error occured on Path sdu: opcode=0x5f reported reservation conflict
 (status=0xc, key=0x0, asc=0x0, ascq=0x0)
 Mon Mar 28 11:23:27.793: SCSI error occured on Path sdaa: opcode=0x5f reported reservation conflict
 (status=0xc, key=0x0, asc=0x0, ascq=0x0)

Please confirm the cause and impact of these messages.

Regards

S.

To VOM/VIOM reviewers,

Please accept this submission to the Veritas Community ideas for enhancements, that port 5634 from a managed host to managed host be explicitly defined.  

 Customers would like to understand and clarify the issues found in the manuals and guides reagrding ports 5634 from VOM and VIOM. Based on the documentation for VOM 6.x to 3.x and VIOM 7.x,;  VERITAS recommends that port 5634 remain open for updates to the database, configuration updates and heart beats of the nodes in the environmental configuration only from the managed hosts to managed server relationships and configurations.

References: 

3.x -> https://www.veritas.com/support/en_US/article.000011859

4.x -. http://www.symantec.com/content/en/us/enterprise/other_resources/b-vom_4_faq_OR.en-us.pdf

5.x - https://sort.symantec.com/public/documents/vom/5.0/windowsandunix/productguides/pdf/vom_ms_install_5_0.pdf

6.x - https://www.symantec.com/content/en/us/enterprise/faqs/b-vom_ms_faqs_6_0.en-us.pdf

7.x - http://origin-download.veritas.com/resources/content/live/DOCUMENTATION/8000/DOC8847/en_US/vbs_users.pdf

7.x - http://origin-download.veritas.com/resources/content/live/DOCUMENTATION/8000/DOC8877/en_US/vom_notes_7_0.pdf

======================

VERITAS techs were asked to clarify results from blocked port 5634, communicating from managed host to managed host . The VERITAS documents do not state a customer cannot block ports 5634 between managed hosts nodes, but after the port was disabled, there was a negative result for the impacted servers. The verbiage change should explicity update any statement which VERITAS recommends port 5634 stay open for all VOM/VIOM communications between Central Managed Hosts to Managed Hosts, and Managed Hosts to other Managed Hosts applicably and in good faith. 

RE: Update explicit definitions and recommendations to VOM/VIOM guides and manuals.

Please state potential problems, regarding using performance monitors, system communications and database updates if port 5634 is disabled only from a managed host to another managed host. 

===Performance========================

1. https://sort.veritas.com/public/documents/vom/7.0/...

2. https://sort.veritas.com/public/documents/vom/7.0/...

=====================

Hi,

I have the following set up on my cluster:

The main interface

eth0

And 2 vlan tagged interfaces

eth0.100

eth0.200

Each interface has been plumbed with an IP and I have a NIC resource set up to monitor them

Seeing as the server is a HP blade using virtual connect, I cannot use Mii to monitor the NICs so I need to use packet counting.

So the problem is if eth0 fails but eth0.100 and eth0.200 are still OK, the NIC resrouce for eth0 will not go into a faulted state as it is counting all packets that are received including the vlan tagged packets. Is there anything I can do to get around this other than writing my own agent?

All suggestions welcome,

Thanks,

Rossa.

Hello Team, 

I usually check /etc/llthosts to find which is masternode in CVM cluster i.e. 0- measn that is the master node. But vxdctl -c  mode gives a different nodes as master. I am little confused here that we do not need to look /etc/llthosts to find which is master node?. 

From vxclustadm nidmap i could see a CVm Nid and CM Nid colums with differnet numbers. How the cluster actually grep that info and works and if possible can you explain that. 

Thanks in advance. 

Thanks & Regards,

Ashok

Dear all,

we got a INFOSCALE FOUNDATION LNX 1 CORE ONPREMISE STANDARD PERPETUAL LICENSE CORPORATE. I have installed key using the vxlicinst -k <key> command. But when I want to check it using vxlicrep I'm getting this error for the given key:

vxlicrep ERROR V-21-3-1015 Failed to prepare report for key = <key>

We have Veritas Volume Manager 5.1 (VRTSvxvm-5.1.100.000-SP1_RHEL5 and VRTSvlic-3.02.51.010-0) running on RHEL 5.7 on 64 bits.

I've read that the next step is to run vxkeyless set NONE, but I'm afraid to run this until I cannot see the license reported correctly by vxlicrep.

What can I do to fix it?

Thank you in advance.

Kind regards,

Laszlo

Veritas will be participating at the OpenStack Summit Conference in Austin, Texas beginning on April 25^th, 2016.  Please join us to network with OpenStack industry peers and subject matter experts.  Or request a meeting with our on-site experts by sending a short email to events@veritas.com.  We’d love to discuss your storage man

Read More