Adding a license key
# rpm -i VRTScutil-5.0.33.00-RU3_GENERIC.noarch.rpm
# rpm -i VRTSatClient-4.3.28.0-0.ppc.rpm
# rpm -i VRTSatServer-4.3.28.0-0.ppc.rpm
SLES10/ppc64, required RPMS
# rpm -i VRTSvlic-3.02.33.4-0.ppc64.rpm
# rpm -i VRTSperl-5.10.0.1-SLES10.ppc64.rpm
# rpm -i VRTSspt-5.5.00.0-GA.noarch.rpm
# rpm -i VRTSllt-5.0.33.00-RU3_SLES10.ppc64.rpm
# rpm -i VRTSgab-5.0.33.00-RU3_SLES10.ppc64.rpm
# rpm -i VRTSvxfen-5.0.33.00-RU3_SLES10.ppc64.rpm
# rpm -i VRTSvcs-5.0.33.00-RU3_SLES10.ppc64.rpm
# rpm -i VRTSvcsag-5.0.33.00-RU3_SLES10.ppc64.rpm
# rpm -i VRTSvcsdr-5.0.33.00-RU3_SLES10.ppc64.rpm
# rpm -i VRTScutil-5.0.33.00-RU3_GENERIC.noarch.rpm
# rpm -i VRTSatClient-4.3.28.0-0.ppc.rpm
# rpm -i VRTSatServer-4.3.28.0-0.ppc.rpm
After you have installed all RPMs on each cluster node, use the
command to add the VCS license key on each system:
# cd /opt/VRTS/bin
# ./vxlicinst -k XXXX-XXXX-XXXX-XXXX-XXXX-XXX
Checking licensing information on the system
Use the
utility to display information about all Veritas licenses on a
vxlicrep
system. For example, enter:
# cd /opt/VRTS/bin
# ./vxlicrep
From the output, you can determine the license key, the type of license, the product
for which it applies, and its expiration date, if any. Demo keys have expiration
dates, while permanent keys and site keys do not.
Adding and removing cluster nodes
Adding a node to a cluster
vxlicinst
125
Need help?
Do you have a question about the Veritas Cluster Server and is the answer not in the manual?
Questions and answers