RSA Admin

ESI 1.1.1 - redeploying/updating an existing ESI device

Discussion created by RSA Admin Employee on Mar 9, 2011
Latest reply on Apr 6, 2011 by RSA Admin

I was able to successfully deploy a new device several weeks ago using the DeployEventSourceSetup.vbs and restarting services, etc. However, after adding several more message Ids to the xml, repackaging the zip, and attempting to deploy, the xml under etc/devices/deviceName is not getting updated.

 

We have an LS test and prod env, so deployment from just the Asrv would be nice. I see a esiupdatelog.log in the logs directory with the following timely contents on each appliance:

INFO  09 03 2011 14:21:04,731 %NIC-6-701000: AutomaticUpdate, AutoUpdateMain, -, package, 2011039-141431, Detail: 1: 2011/03/09 14:21:04, Automatic update started.
INFO  09 03 2011 14:21:04,872 %NIC-6-701002: AutomaticUpdate, AutoUpdateMain, -, patch, 2011039-141431/deviceName_2011039-141431, Detail: 1: date_time: 2011/03/09 14:21:04, package_id: 2011039-141431, patch_id: deviceName_2011039-141431, started.
WARN  09 03 2011 14:21:04,872 %NIC-4-701009: AutomaticUpdate, AutoUpdateMain, -, patch, 2011039-141431/deviceName_2011039-141431, Detail: 1: package_id: 2011039-141431, patch_id: deviceName_2011039-141431, patch already applied.
INFO  09 03 2011 14:21:04,872 %NIC-6-701002: AutomaticUpdate, AutoUpdateMain, -, patch, 2011039-141431/service_2011039-141431, Detail: 1: date_time: 2011/03/09 14:21:04, package_id: 2011039-141431, patch_id: service_2011039-141431, started.
INFO  09 03 2011 14:21:15,294 %NIC-6-701021: AutomaticUpdate, RunCmd, -, runWSFScriptFile, ServiceStartStop.wsf, Detail: 1: NIC Alerter stopped.
INFO  09 03 2011 14:21:25,606 %NIC-6-701021: AutomaticUpdate, RunCmd, -, runWSFScriptFile, ServiceStartStop.wsf, Detail: 1: NIC App Server stopped.
INFO  09 03 2011 14:21:25,903 %NIC-6-701021: AutomaticUpdate, RunCmd, -, runWSFScriptFile, ServiceStartStop.wsf, Detail: 1: NIC Collector stopped.
INFO  09 03 2011 14:21:26,185 %NIC-6-701021: AutomaticUpdate, RunCmd, -, runWSFScriptFile, ServiceStartStop.wsf, Detail: 1: NIC Locator stopped.
INFO  09 03 2011 14:21:26,481 %NIC-6-701021: AutomaticUpdate, RunCmd, -, runWSFScriptFile, ServiceStartStop.wsf, Detail: 1: NIC Logger stopped.
INFO  09 03 2011 14:21:26,763 %NIC-6-701021: AutomaticUpdate, RunCmd, -, runWSFScriptFile, ServiceStartStop.wsf, Detail: 1: NIC Packager stopped.
INFO  09 03 2011 14:21:27,044 %NIC-6-701021: AutomaticUpdate, RunCmd, -, runWSFScriptFile, ServiceStartStop.wsf, Detail: 1: NIC Server stopped.
INFO  09 03 2011 14:21:38,685 %NIC-6-701021: AutomaticUpdate, RunCmd, -, runWSFScriptFile, ServiceStartStop.wsf, Detail: 1: NIC Web Server stopped.
INFO  09 03 2011 14:21:49,013 %NIC-6-701021: AutomaticUpdate, RunCmd, -, runWSFScriptFile, ServiceStartStop.wsf, Detail: 1: NIC Service Manager stopped.
INFO  09 03 2011 14:21:59,200 %NIC-6-701021: AutomaticUpdate, RunCmd, -, runWSFScriptFile, ServiceStartStop.wsf, Detail: 1: Sleep for some seconds.
INFO  09 03 2011 14:22:09,575 %NIC-6-701021: AutomaticUpdate, RunCmd, -, runWSFScriptFile, ServiceStartStop.wsf, Detail: 1: NIC Service Manager started.
INFO  09 03 2011 14:22:09,575 %NIC-6-701003: AutomaticUpdate, AutoUpdateMain, -, patch, 2011039-141431/service_2011039-141431, Detail: 1: date_time: 2011/03/09 14:22:09, package_id: 2011039-141431, patch_id: service_2011039-141431, completed successfully.
INFO  09 03 2011 14:22:09,575 %NIC-6-701001: AutomaticUpdate, AutoUpdateMain, -, package, 2011039-141431, Detail: 1: 2011/03/09 14:22:09, Automatic update completed.
 

So from the warning, it looks like the script thinks it has the same version or has already updated? Can I not update an existing device created with the ESI tool using the vbs script? Did I miss something in the overveiw or help? From the overview, it sounds like it should have work. Thanks!

Outcomes