Question on volume state

Command is incorrect ... to start a volume , you need to use

# vxvol -g <diskgroup> start <vol>

With above command, volume should come in "Enabled Active" state. This is the working state of a volume, if you have filesystem already on volume, you should be able to mount it using mount command.

There are 2 states of any virtual object, state & kstate (kernel state), that is why you see two states i.e Enabled & Active.

Basis on some of your past queries. may be this is worth reading

http://www.symantec.com/docs/TECH18795

http://www.symantec.com/docs/TECH194469

Also, there is lot to read in vxvol man page

https://sort.symantec.com/public/documents/sfha/6.1/solaris/manualpages/html/man/volume_manager/html/man1m/vxvol.1m.html

G

Please go back to the top of the page you are quoting from:

A volume may be initialized by running the vxvol command if the volume was created by the vxmake command and has not yet been initialized, or if the volume has been set to an uninitialized state.

Fact is this comand is still there for the old style 'bottom-up' creation of volumes.
In all honesty, I have only used the vxmake command when I was first introduced to VxVM more than 15 years ago.
Another use for vxmake is to rebuild volumes from 'vxprint' output. (This is how we did it before we had vxconfigbackup and vxconfigrestore)

BUT ... there is honestly no longer a need for volume creation using 'bottom-up' method.

Use vxassist - it will create a volume with a single command. No need for these vxvol commands.
And use vxconfigbackup and -restore to rebuild/recreate volumes.

PS: 
Have you looked yet for Storage Foundation and Cluster training in your area?

In addition to Marianne's clean explanation, if you were concerned about below command

# vxvol [-g diskgroup] init enable volume

you are referring to a external website & that too for 4.1 versio however if you look at same command from the latest man page

This would explain what you are looking for.

G