After installing or upgrading to Storage Foundation Suite 5.0 (tm), vxsvc fails to start with an error message that the server is not configured.

Article:TECH49821  |  Created: 2006-01-30  |  Updated: 2010-01-15  |  Article URL http://www.symantec.com/docs/TECH49821
Article Type
Technical Solution


Environment

Issue



After installing or upgrading to Storage Foundation Suite 5.0 (tm), vxsvc fails to start with an error message that the server is not configured.

Error




"The server is not configured. Unable to start the server.
Please configure before running."

Solution



After a new installation or an upgrade to Storage Foundation Suite 5.0 (tm), and the answer to the question "Are you ready to configure Storage Foundation now?" was no, an error occurs when attempting to connect to the host via the VERITAS Enterprise Administrator GUI, VEA. On the host, the module isisd fails to start and the above error occurs. If the system is installed using a method such as JumpStart, this question is not presented to answer, and therefore one of the below procedures must be followed to allow the VEA to connect to the host where Storage Foundation Suite (tm) 5.0 was installed.

There are two different methods to resolve the issue, and both are listed below. The first method is the preferred and is outlined in the VERITAS Storage Foundation (tm) Installation Guide 5.0 - Solaris. For more information about this guide, please refer to the Related Documents section below.

Solution 1:
For the VEA Server daemon, /opt/VRTSob/bin/vxsvc, to start, it needs to be configured so the proper management console can connect to it. The configuration options are to have the host managed by Storage Foundation Management Server (tm) Management, or to configure it in Stand Alone mode. To configure the VEA Server daemon, please follow the below directions:
Execute  the command "# installsf -configure". When the command "# installsf -configure" is executed, navigate through the prompts and answer "n" to the question "Enable Storage Foundation Management Server Management?". The Storage Foundation Manager Server (tm) (now called Storage Foundation Manager (tm) product is beyond the scope of this document. For more information on this product, please refer to the production documentation available in the Related Documents section below. Please see below for a the specific prompt regarding the configuration question that must be answered
# cd /opt/VRTS/install
# ./installsf -configure

             Veritas Storage Foundation 5.0 Configuration Program

<Snip>

Do you want to configure VCS on these systems at this time? [y,n,q] (y) n
<Snip>

Enable Storage Foundation Management Server Management? [y,n,q] (y) n


             Veritas Storage Foundation 5.0 Configuration Program

Verify the install systems Fully Qualified Hostnames.

   Configuring VEA in STANDALONE mode on "slapshot" ...................ok
   Configuring gridnode on "slapshot" .................................ok
   Registering gridnode on "slapshot" .................................ok
   Configuring actionagent on "slapshot" ..............................ok
   Stopping actionagent on "slapshot" .................................ok
   Registering actionagent on "slapshot" ..............................ok
   Stopping StorageAgent on "slapshot" ................................ok
   Registering StorageAgent on "slapshot" .............................ok
   Stopping VAILAgent on "slapshot" ...................................ok
   Registering VAILAgent on "slapshot" ................................ok
Do you want to start Veritas Storage Foundation processes now? [y,n,q] (y) y

             Veritas Storage Foundation 5.0 Configuration Program

   Starting SF: 100%

Startup completed successfully on all systems

   VxVM is already configured on slapshot; installsf cannot reset the default disk group.
<snip>


Solution 2: (tested with Solaris 10 and SF 5.0)
If the "installsf -configure" script cannot be run, or if the script is not in the /opt/VRTS/install folder (this may be due to fact that customer ran installsfrac instead of installsf), the below procedure can be followed to configure the VEA Server:

Verify first that the following packages are installed on the system.  If they are not, then they must be installed manually:

VRTSaa  
VRTSalloc      
VRTSccg
VRTSdcli        
VRTSddlpr      
VRTSdsa
VRTSfspro      
VRTSgapms      
VRTSmh  
VRTSpbx
VRTSsmf
VRTSvail        
VRTSvmpro      
VRTSvrpro      
SYMClma

Prepare your system for configuration by halting any VEA services that are currently running:
# ps -ef | egrep "vxsvc|vxpal"

-Stop 'vxsvc'
# /opt/VRTSob/bin/vxsvc -k

-Stop 'vxpal.<agentname>' processes
# /etc/init.d/vxpal.<agentname> stop                (/sbin/init.d/ on HP-UX)

Run the following commands to configure the appropriate agents on the server.  Please make sure that you have set the $vxHOSTNAME variable or manually modify all occurrences of $vxHOSTNAME to reflect the system's hostname.

# vxHOSTNAME="servername.domain.com"

You may safely ignore errors related to gridnode, VAIL, and actionagent as these are not required elements for a VEA / VxVM management environment.  The StorageAgent must be configured as this provides support for Volume Manager objects in the VEA environment.


Setup the VEA Registry:
# /opt/VRTSat/bin/vssregctl -f /etc/vx/vss/VRTSat.conf -s -b Security/Authentication/Client -k ConnectTimeout -v 20 -t int
# /opt/VRTSobc/pal33/bin/vxregctl /etc/vx/isis/Registry setvalue Software/VERITAS/VxSvc/CurrentVersion Mode REG_INT 1
# /opt/VRTSobc/pal33/bin/vxregctl /etc/vx/isis/Registry setvalue Software/VERITAS/VRTSobc/pal33/Agents/__defaults/Network/Params/Security VXPALSECURITY REG_SZ y
# /opt/VRTSobc/pal33/bin/vxregctl /etc/vx/isis/Registry setvalue Software/VERITAS/VRTSobc/pal33/Agents/__defaults/Network/Params/Security DomainController REG_SZ $vxHOSTNAME
# /opt/VRTSobc/pal33/bin/vxregctl /etc/vx/isis/Registry deletevalue Software/VERITAS/VRTSobc/pal33/Agents/__defaults/Network/Params/Security AuthenticationBroker
# /opt/VRTSobc/pal33/bin/vxregctl /etc/vx/isis/Registry setvalue Software/VERITAS/VRTSobc/pal33/Agents/__defaults Mode REG_INT 1_PLAT_RMR

# /opt/VRTSobc/pal33/bin/vxini -f /etc/default/csf_resolv.conf -i -s SECURITY -k PROTOCOL_TYPE -v high
# /opt/VRTSobc/pal33/bin/vxini -f /etc/default/csf_resolv.conf -i -s SECURITY -k DOMAIN_TYPE -v localhost
# /opt/VRTSobc/pal33/bin/vxini -f /etc/default/csf_resolv.conf -i -s DOMAIN_CONTROLLER -k domain -v $vxHOSTNAME


Configure VEA component agents:
# /opt/VRTSobc/pal33/install/cfgsecurity.sh -a root
# /opt/VRTSobc/pal33/install/cfgsecurity.sh -a gridnode -h $vxHOSTNAME -d -p -b
# /opt/VRTSobc/pal33/install/cfgsecurity.sh -a actionagent -h $vxHOSTNAME -d -p -b
# /opt/VRTSobc/pal33/install/cfgsecurity.sh -a StorageAgent -h $vxHOSTNAME -d -p -b

-If you do not have VAIL installed you can ignore the error messages while registering.
# /opt/VRTSobc/pal33/install/cfgsecurity.sh -a VAILAgent -h $vxHOSTNAME -d -p -b

# /opt/VRTSobc/pal33/install/veacfg.sh -k OBC -m SA -h $vxHOSTNAME

Now startup the processes necessary:

# /etc/init.d/vxpal.gridnode start
# /etc/init.d/vxpal.actionagent start
# /etc/init.d/vxpal.StorageAgent start

Verify processes started:
# ps -ef | grep vxpal
root     16198     1  0 07:04 pts/1    00:00:00 /opt/VRTSobc/pal33/bin/vxpal -a gridnode -x
root     16218     1  1 07:05 pts/1    00:00:00 /opt/VRTSobc/pal33/bin/vxpal -a StorageAgent -x
root     16328     1  3 07:06 pts/1    00:00:00 /opt/VRTSobc/pal33/bin/vxpal -a actionagent -x
root     16347 16083  0 07:06 pts/1    00:00:00 grep vxpal


Start the VEA server.
# /opt/VRTSob/bin/vxsvcctrl start

Cleanup the Environment
# unset vxHOSTNAME





Legacy ID



286164


Article URL http://www.symantec.com/docs/TECH49821


Terms of use for this information are found in Legal Notices