2 Replies Latest reply on Jul 5, 2011 11:08 PM by Steve Welsh

    Ignoring first line in config when comparing running configs for OCCAM blades.

    netsupp

      Dear Support,

      I have an issue similar to the Ignoring first line in config when comparing running configs thread.  I have downloaded the new script that is posted on the site and it has not made any difference to the backup issue.

      Just wondering if there is a newer script that I can install to resolve the issue of CatTools thinking that everytime the running config is generated it seems to think its a new configuration, the only item that has changed is the compile time of the running configuration.

      Regards,

      Network Support

        • Re: Ignoring first line in config when comparing running configs for OCCAM blades.

          Hi Netsupp--

          FYI, thwack is not exclusively a support forum so what you write here on thwack may or may not go directly to our Support team.

          For immediate attention from Support, open a support ticket here.

          When you open a support ticket, would you:

          --Reference this thread to Support.
          --Post back here with a case number.
          --Post any solutions you get from Support.


          Many thx,

          M

          • Re: Ignoring first line in config when comparing running configs for OCCAM blades.
            Steve Welsh

            Hi Netsupp--

            Does CatTools think that the config is a NEW config with each run, or is it telling you that the config has CHANGED?

            If NEW, then it suggests that the original config file in the \Configs folder either:

            a) doesn't exist

            b) exists, but CatTools cannot access it to diff against the temp config file just pulled from the device; or

            c) you have used a filename variable http://www.kiwisyslog.com/help/cattools/act_filenamevariables.htm - such as %DateISO% in the 'Current config file' field within the activity setup.  This will effectively generate a different filename for every day you run the config backup activity.  Because the filename variables values are determined at runtime; CatTools will then be looking for a file with the current date in the filename, however your backup on disk is named with yesterday's date.  Because CatTools can't find the file, it therefore thinks that this must be the first time the device was backed up.

            The other date/time filename variables will also cause similar issues as they change.  Variables such as %BaseFile% are static in terms of the current device you are backing up, so do not have this issue.

             

            If the issue is that the CatTools is always reporting config has changed, then you'll need to raise a support ticket so we can get some diagnostics and PuTTY captures from you.

            Regards,

            Steve