Veritas cluster is not starting

Hi, Atul

1.

  refer gabconfig manual:

     -c Configure the driver for use. Configuring the GAB driver
        enables client registrations and the joining of an
        already seeded group.

       -x Seed control port. This option affords protection from
        pre-existing network partitions. The control port (port
        a) propagates the seed to all configured systems. GAB
        must be seeded to enable the delivery of membership on
        client ports.

   -n system_count
        Count of systems in the cluster. A non-zero system count
        auto-seeds the cluster when all systems are present. The
        default is zero, for no auto-seeding.

===

Normally, while gab start, it run: gabconfig -c -nX

like if there is two node:

gabconfig -c -n2

But if while one node can't join, gab  will not start another the node .  

if you want manual start gab, use

gabconfig -a -x <<<tell  gab start, without check membership.

after gab start, you can use hastart to start   vcs.

2.  when oracle start outside  vcs, vcs start then, first it will probe all resources on each node, if it found oracle already online, it will mark oracle and related resources as online on the node, no other action required. It will not impact db .