That won't always work though. If there are pieces of the config that are hardware dependent, such as COS, etc., you won't get an alert without identical hardware to evaluate it on. For basic config items it would be fine of course.
Jeff On Jan 14, 2011, at 1:58 PM, Tim Eberhard <[email protected]> wrote: > Olives are great for these types of scripts. An olive vmware machine can be > hosted on anything and just be used for config verification. > > Hope this helps, > > -Tim Eberhard > > On Jan 14, 2011, at 3:40 PM, Nvvk Brnn <[email protected]> wrote: > >> Hi: >> >> I have some perl scripts that generate Juniper configs. >> I need to verify that these configs are Juniper compatible (as there could >> be bugs in my scripts) >> >> I have 2 options. >> 1) Copy the generated config to a juniper router, load merge config and then >> commit to see if there are errors. >> (We will actually see errors while doing a load merge) >> >> 2) This is the option that I want to pursue (in the interest of time as I >> have lots of verification to do) >> An offline config parser that will tell me if I have a valid Juniper config. >> Do we know which daemon in juniper does >> this config parsing? >> >> I could start a shell on the juniper and copy the binaries to a remote >> machine and start playing with them, but wanted to see if >> someone has any similar experience. >> >> Thanks, >> >> N >> _______________________________________________ >> juniper-nsp mailing list [email protected] >> https://puck.nether.net/mailman/listinfo/juniper-nsp > > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
