Volume Manager reports error:

Cause

After upgrading from VxVM 2.0 or 2.1 to 2.3, when attempting to run vxva, the volume manager GUI, you get the message:

        Volume Manager reports error:
           Configuration daemon can't speak protocol version

This message indicates that there is a version mismatch between the version of the volume manager daemon (vxconfigd) and the GUI (vxva) you are trying to run. For example, you are running the 2.3 version of vxconfigd, and trying to run an old (2.1) version of vxva.

The most likely reason for this to happen is because the you are using the wrong path for vxva. For vxva versions 2.1 and below, the binary was found in /opt/vxva/bin, but starting with 2.1.1, the location was changed to /opt/SUNWvxva/bin.

If you did not remove the old SUNWvxva package before installing the new 2.3 version (which is a normal thing; you don't NEED to remove the old package), you probably still have the old /opt/vxva/bin in your $PATH, and thus, you're attempting to run the older version of vxva.

Action

Run the newer vxva program: /opt/SUNWvxva/bin/vxva. If that does work and you do not get the error message, simply remove /opt/vxva/bin/vxva from your path statement or remove the old version of vxva and create a symbolic link to the new version with the following two commands:

 
# rm /opt/vxva/bin/vxva 
# ln -s /opt/SUNWvxva/bin/vxva /opt/vxva/bin/vxva