After editing the $SPECROOT/lib/SDPM/partlist/VNMSHD.idb file to AUTOBOOTSTART and AUTORESTART equal to "Y", the $SPECROOT/vnmsh/VnmShd will not start.

Products

• DX NetOps
• CA Spectrum

Issue/Introduction

After editing the $SPECROOT/lib/SDPM/partlist/VNMSHD.idb file to AUTOBOOTSTART and AUTORESTART equal to "Y", the $SPECROOT/vnmsh/VnmShd will not start.

Environment

Release : Any

Component: Applications

Cause

The VnmShd will automatically start when a user runs the $SPECROOT/vnmsh/connect command. It is not meant to start when processd starts.

Resolution

To resolve the issue:

- Set the $SPECROOT/lib/SDPM/partlist/VNMSHD.idb file back to the default AUTOBOOTSTART and AUTORESTART equal to "N" as seen below:

PARTNAME;VNMSHD;
APPNAME;SPECTRUM CLI Daemon;
WORKPATH;$SPECROOT/vnmsh;
LOGNAMEPATH;$WORKPATH/VNMSHD.OUT;
#ADMINPRIVS;N;
AUTORESTART;N;
AUTOBOOTSTART;N;
#STATEBASED;N;
NUMPROCS;1; // one per host
RETRYTIMEOUT;0; // seconds
#TICKETUSER;spectrum;
RETRYMAX;0;     // retries
STARTPRIORITY;30;
SERVERPROCESS;Y;
ARGV;$SPECROOT/vnmsh/VnmShd<CSEXE>;

- Shutdown all Spectrum processes as normal including processd

- Check for a VnmShd running. If found, kill it

- Check for an left over rtt files located in the $SPECROOT/lib/SDPM/runtime directory. If any are found after shutting processd down, delete them

- Start processd

- Start the SpectroSERVER process

- Log into the system as the user that owns the Spectrum installation

- If on Windows, start a bash shell by running "bash -login"

- cd to the $SPECROOT/vnmsh directory and run the following command to start a CLI session

./connect

- If successful, you should now notice a VnmShd process running