question

[Marc Powell]

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Hugo van der Kooij
> Sent: Tuesday, April 18, 2006 1:44 PM
> To: Nagios Users Mailinglist
> Subject: Re: [Nagios-users] question
> 
> On Tue, 18 Apr 2006, Guillermo Bellettini wrote:
> 
> > Hi there, do you have anu idea how to upgrade Net Saint 0.0.7 to
Nagios
> 2.2?
> 
> I suggest you print the old configs and start to write them from
scratch.
> 
> If you have 1000's of service you may make it worth to write a custom
> migration script. But if you are around a 100 or less then I would not
> bother to try to automate it.

Andreas Ericsson has written a script called object_config_fix.php found
at http://oss.op5.se/nagios/ that I found useful in my migration from
nagios-1.0 to 2.0. 

To get from Netsaint style configs I would suggest starting with the
convertcfg program found in the contrib. directory. That will convert
old style Netsaint object files to the Nagios-1.0 template format. From
there you can either manually edit to update them to the nagios-2.0
format (essentially updating changed macros and moving contact_groups
from hostgroup to host definitions) or playing around with Andreas's
script to do that for you. I had to tweak it a little bit to get it to
work with my configs but now it's working great while I run both in
parallel.

--
Marc


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null