Unsolved

This post is more than 5 years old

105 Posts

729

November 27th, 2007 04:00

master/Host agent rollout issues on Clusters

We are testing automated script rollout of master/host agents. The scripts work in the lab...ini file is populated and install logs are created. there is no connectivity to ECC there so we cannot test seeing the host automatically generated in ECC. When we attempt to run this on a prod cluster in our ECC environment the script doesn't appear to finish totally and the ini file is not populated nor are any install log files produced. Something special need to be done for clusters? the script is below..

scott
WriteToLog('I', "--------------------------");
WriteToLog('I', "Beginning Installation");
WriteToLog('I', "-------------------------- \n");

WriteToLog('I', "Creating directory $ENV{SystemDrive}\\ecc");
mkdir("$ENV{SystemDrive}\\ecc");


WriteToLog('I', "Copying setup.exe to directory $ENV{SystemDrive}\\ecc");
copy("setup.exe", "$ENV{SystemDrive}\\ecc\\setup.exe") or WriteToLog('E', "Cannot copy setup.exe to $ENV{SystemDrive}\\ecc $!\n");


WriteToLog('I', "Copying setup.exe to directory $ENV{SystemDrive}\\ecc");
copy("uninstall_master.bat", "$ENV{SystemDrive}\\ecc\\uninstall_master.bat") or WriteToLog('E', "Cannot copy setup.exe to $ENV{SystemDrive}\\ecc $!\n");

if(!-e "$ENV{SystemDrive}\\temp"){

WriteToLog('I', "Creating directory $ENV{SystemDrive}\\temp");
mkdir("$ENV{SystemDrive}\\temp");
}

$dir =$ENV{SystemDrive}."\\ecc";
WriteToLog('I', "Changing directory to $dir");
chdir($dir) || die "Cannot chdir to $ENV{SystemDrive}\\ecc ($!)";
my $setvar=$qoutes.$qoutes;
WriteToLog('I', "set perl5lib=$setvar");
`set perl5lib=$setvar`;

$cmd =$ENV{SystemDrive}."\\ecc\\setup.exe /s /v$qoutes/qn CMDLINE=TRUE INSTALLDIR=$ENV{SystemDrive}\\ecc SERVERHOSTNAME_ORIP=10.254.15.195 SERVERHOSTNAME_NAME=apsdbs02 /Liwrmo!veacup+ $ENV{SystemDrive}\\temp\\CmdLine.log ALLUSERS=2 INSTALLELEVATED=1 ADDLOCAL=ALL ARPNOMODIFY=1 TransformsSecure=0$qoutes";


WriteToLog('I', "\n executing command \n $cmd \n");
$retVal = `$cmd`;
if ($retVal)
{#record error
WriteToLog('E',$tmp);
}
else
{
WriteToLog('I', "Installation Successful");
WriteToLog('I', "For more innformation please review $ENV{SystemDrive}\\temp\\CmdLine.log");
}

$service=$qoutes."EMC ControlCenter Master Agent".$qoutes;
WriteToLog('I', "Starting $service.");
`net start $service`;


It translates to this:

mkdir("$ENV{SystemDrive}\\ecc");

copy("setup.exe", "$ENV{SystemDrive}\\ecc\\setup.exe");

copy("uninstall_master.bat", "$ENV{SystemDrive}\\ecc\\uninstall_master.bat");

mkdir("$ENV{SystemDrive}\\temp");

chdir($ENV{SystemDrive}."\\ecc");

`set perl5lib=""`;

`$ENV{SystemDrive}\ecc\setup.exe /s /v"/qn CMDLINE=TRUE INSTALLDIR=$ENV{SystemDrive}\ecc SERVERHOSTNAME_ORIP=10.254.15.195 SERVERHOSTNAME_NAME=apsdbs02 /Liwrmo!veacup+ $ENV{SystemDrive}\temp\CmdLine.log ALLUSERS=2 INSTALLELEVATED=1 ADDLOCAL=ALL ARPNOMODIFY=1 TransformsSecure=0"`;

`net start "EMC ControlCenter Master Agent"`;

59 Posts

December 3rd, 2007 12:00

I used software below to create the MSI package in about 1 minute. Just make sure you use it on a clean box that did not have the master agent install previously. Even when you uninstall the agent things are left behind and they will not get added to the package.

EMCO MSI Package Builder Professional

59 Posts

December 3rd, 2007 12:00

Wow! I wish I had time to write a script like this. If this is for a windows environment I would highly recommend using a MSI package. That is what I ended up doing and it worked like a champ. Then push it out with a group policy! I tried the PushMA.pl method that EMC recommends but I could not get it to work.

Are you sure it is working in the lab?
Is the "EMC ControlCenter Master Agent" service account being created and started?

As for your issue and I don't believe anything special has to be done in a clustered environment. Just make sure you don't install it on a clustered resource. The master and host agents can not be clustered resources.
No Events found!

Top