Unsolved
This post is more than 5 years old
30 Posts
0
694
August 26th, 2008 05:00
Dynamic Model: Instrumenation are lost after restart of domain
Hello
We have done some dynamic modeling within EMC Smarts to monitore log files on unix servers. Therefore we create an instance of instrumentation class. After each restart of the domain the instance of the instrumenation is lost and we have to rediscover this server again.
Does anybody has an idea how to make this instance persistant?
Regards,
Christian
We have done some dynamic modeling within EMC Smarts to monitore log files on unix servers. Therefore we create an instance of instrumentation class. After each restart of the domain the instance of the instrumenation is lost and we have to rediscover this server again.
Does anybody has an idea how to make this instance persistant?
Regards,
Christian
No Events found!
FredericMeunier_0588be
143 Posts
0
August 26th, 2008 09:00
this is the standard behavior in any Smarts InCharge domain manager. I think you should stick with it to be consistent with the complete solution. The instrumentation is (re)created at reconfigure time, after a discovery by default (and can be restarted anytime).
Unfortunately, it seems there is no standard way to plug an ASL in the reconfigure process, as it is possible in other discovery steps. One solution to trig on the reconfigure step is to have a subscriber which subscribe to "reconfigureStatus" and launch your ASL scripts when the reconfigure stops.
--Fred
***APG v4.1 is now available with new out of the box reports for Smarts InCharge health***
Frederic Meunier
Solutions Watch4Net Inc
APG & Smarts InCharge integration
http://www.watch4net.com
kfosburg
1 Rookie
•
18 Posts
0
August 26th, 2008 10:00
I'm not sure I understand your answer... wouldn't the instrumentation instance be recreated after the reconfigure? A reconfigure is run automatically at startup unless specifically suppressed with the noreconfigure option...
Have to rediscover after a restart would be pretty painful...
Karl
FredericMeunier_0588be
143 Posts
0
August 26th, 2008 11:00
sorry if I was not clear.
Yes, the reconfigure is done right after the repository load at startup, in order to recreate the complete instrumentation at this stage of the DM life. This is the standard InCharge design to recreate the instrumentation (not load it). The reconfigure (which takes time, has impact and should be monitored carefully) is also done after each discovery, because (from my understanding of this non documented process), for example, some of the index used in the instrumentation (SNMP) could have changed and thus should be recreated with the correct index. It also can be started from the GUI or the CLI (dmctl).
Now regarding specifically the request: I don't know any solution to make the default reconfigure process recreate automatically the instrumentation of new models' instances. You can plug ASL scripts at some specific discovery process steps, but not at the reconfigure step. So for that, you have 1 solution: use a subscriber (which subscribe to ICF_PolicyManager::*::reconfigureStatus) which start your instrumentation right after the "out-of-the-box" reconfigure is done. In this case, whenever the reconfigure stop (at startup, after a discovery, manually, ...), your instrumentation will be recreate using your ASL.
Regards,
--Fred