Receiving an error message:warning,this host is not entitled to run storage foundation/cluster server

Problem

Storage foundation 5.1, will throw the nagware message that "this host is not entitled to run storage foundation", if the system is not  managed by Mangement server or  no permanent license installed.

 

 

Error Message

Aug 19 08:55:45 hostxyz  syslog[6007]: [ID 702911 daemon.warning] WARNING V-365-1-1 This host is not entitled to run Veritas Storage Foundation/Veritas Cluster Server. As set forth in the End User License Agreement (EULA) you must complete one of the two options set forth below. To comply with this condition of the EULA and stop logging of this message, you have 5 days to either:  - make this host managed by a Management Server (see http://go.symantec.com/sfhakeyless for details and free download), or add a valid license key matching the functionality in use on this host using the command 'vxlicinst' and validate using the comm and 'vxkeyless set NONE'.

 

Cause

Starting Storage Foundation 5.1, keyless licensing has been introduced which allows systems to use SF product without a license key (both temporary/permanent). However, system log will be logged with the nagware message similar to"vxvm:vxconfigd: WARNING V-365-1-1 This host is not entitled to run Veritas Storage Foundation/Veritas Cluster Server."

To address the `nagware' messages, you can either install a valid permanent license or make this host managed by a Managerment Server.

 

Solution

As described in the nagware message, either make this host managed by a Management server or if  the permanent license is avaiable, perform the below:

1. Install the license key 
# vxlicinst -k key

2. Remove the keyless license
# vxkeyless set NONE

3. Refresh VxVM and  cluster licensing information
# vxdctl license init

4.  Referesh the VCS license if the system is part of cluster

# hasys -updatelic -all

# haclus -updatelic


5. If the system is part of VCS and CmdServer is running you may still see the message from CmdServer, then please restart CommandServer as per below.
Procedure to restart the CmdServer:
i.) Kill the CmdServer process on all the nodes within the cluster.
ii.) Restart the CmdServer on all the nodes, as follows:
# export PATH=$PATH:/opt/VRTSvcs/bin:
# CmdServer 


 


Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)