When trying to add new meta-disks to an exiting array off of an E10000, the 
following command was run :

# apdisk -u -p pln0 -a pln2

but resulted with the following error :

apdisk: bad major


Domain messages contained similar errors :

Jul 23 10:45:01 spitfire apd[2176]: apd_scsi_update: ap error bad major
Jul 23 11:49:10 spitfire apd[2176]: apd_scsi_update: ap error bad major
Jul 23 14:44:09 spitfire apd[2176]: apd_scsi_update: ap error bad major


According to the manpage, this should have worked:

         -u -p primary_path -a alternate_path

               Update existing  database  entries  for  the  disk
               pathgroup  identified  by  the primary path (e.g.,
               pln0). Disk targets that are no longer  accessible
               through  one  or  more  paths are removed, and new
               disk targets are added. To  update  the  meta-disk
               device   nodes   execute  drvconfig -i ap_dmd  and
               apconfig -R. See apconfig(1M) in this document and
               drvconfig(1M) in man Pages(1M): System Administra-
               tion Commands of the SunOS Reference Manual.

Without deleting the current meta-disk, use the following command :

apdisk -c -p pln0 -a pln2   (creates meta devices for the alternate pathing)
apdb -C                     (commits the changes made with apdisk)
apconfig -S                 (should now show the new disks)
drvconfig -i ap_dmd         (creates the physical devices)
apconfig -R                 (creates the dev links)

If Veritas is currently up and running, then do the following for 
Veritas to see the new disks:

vxdctl stop
vxconfigd -m enable
(doing a vxdctl enable should also allow veritas to then see the new disks)

You should now be able to run vxdiskadm and be able to initialize the 
disk for use under the control of Veritas.