Unable to create concurrent VG using C-SPOC

we were  trying to configured diskhb network. We
assigned disks and PVID on both nodes. But when tried to create a
concurrent VG using C-SPOC we couldnt see the disks.

lslpp -l bos.clvm.enh => Missing

Even if it is created as concurrent-capable, if we manually vary it on,
the VG will be varied on as non-concurrent. For varying it on as
concurrent, vary it off and then we need to add it to a RG and then
Synchronize and start cluster services.

But for creating a diskhb network we dont really need to varyon the VG.
Hence varyoff the VG on both nodes and just create the diskhb network.


I created diskhbvg concurrent one so I varied it on to check whether it
is really concurrent one or not and it looks like it is not so how to
fix it. Also how to create datavg as concurrent one which was failing
when we tried on that day




root@xxxxx-yyyy-zzzzz:/usr/es/sbin/cluster/utilities>lsvg datavg

VOLUME GROUP:       datavg                   VG IDENTIFIER:
00c7b77d00004c0000000126e7ed7801
VG STATE:           active                   PP SIZE:        64
megabyte(s)
VG PERMISSION:      read/write               TOTAL PPs:      1292 (82688
megabytes)
MAX LVs:            256                      FREE PPs:       1292 (82688
megabytes)
LVs:                0                        USED PPs:       0 (0
megabytes)
OPEN LVs:           0                        QUORUM:         2 (Enabled)
TOTAL PVs:          2                        VG DESCRIPTORS: 3
STALE PVs:          0                        STALE PPs:      0
ACTIVE PVs:         2                        AUTO ON:        no
Concurrent:         Enhanced-Capable         Auto-Concurrent: Disabled
VG Mode:            Non-Concurrent
MAX PPs per VG:     32768                    MAX PVs:        1024
LTG size (Dynamic): 256 kilobyte(s)          AUTO SYNC:      no
HOT SPARE:          no                       BB POLICY:      relocatable

lssrc -ls clstrmgrES => ST_INIT

 only after starting cluster services, the VG will be
varied on as concurrent.

Started cluster services, lsssrc -ls clstrmgrES => ST_STABLE. But
still he sees the VG in Non-concurrent mode.
found that he didnt varyoff the VG before starting cluster services.
Advised customer to bring the RG offline and then bring it online.

Now the VG is in concurrent mode.