7 Replies Latest reply on Oct 5, 2018 6:57 AM by philbibby@f2s.com

    Alerts on the age of the most recent NCM backup?


      Is there a way to create an alert on the age of the most recent NCM config backups?

      we had a massive failure with our ASA today, but luckily (or so I thought) we had been getting backups of their configs every single day.

      but when i went to look at the most recent one it looks like the NCM job, for whatever reason stopped taking backups on 9/1. I

      just want to be notified if there is an issue with these jobs not running correctly, to avoid another disaster in the future...

        • Re: Alerts on the age of the most recent NCM backup?

          You can configure NCM to send you an e-mail each time a backup job fails.  Your task then becomes to open the e-mail every time it's sent to you, and then troubleshoot the error.  If NCM fails to backup your ASA even once, you'd have an alert, and know you have something on your to-do list.


          From my NCM alert e-mails:




          +++++++++++++++(e-mail begins)+++++++++++++++++++++

          Network Configuration Manager

            Scheduled Job




            Job Engine:


          10:00:03 AM : Started  running-config Backup Job :
          JobDescription_(long cryptic name)


            Download Configs
          from Devices

            149 devices


            Devices : 149

            Errors  : 4


          (Device name and IP address):

          ERROR: Cannot download running-config :
          Connection Refused by (IP address of node)


          (List of failed devices' names and their IP addresses appears below, as well as successfully completed nodes.)

          +++++++++++++++++++++++(e-mailed alert ends)++++++++++++++++++++


          To set this up, or to verify you have it configured correctly for notifications of NCM backup job failures:



          Find the job that does your running-config backup.



          In the "Enter Notification Details" tab:

          Verify you have the circled items selected and filled in with the correct information:


          In the "Add Job Specific Details" section, choose the config type and add any notifications you want:



          Review the job.  Verify your nodes are selected, notification is enabled, and Click Finish.



          You should now receive an e-mail every time the job runs and one or more nodes fails to backup successfully.  The only thing left is for you to follow through and troubleshoot every time a node backup fails.






          If you worry that you might not have received the information you need, you can run a report to show the status of all devices' config backup.  Just open "All Reports" and search for "backup".

          Select the report you wish to view and run it.


          The far right column lists the last successful running config of every device:


          It's easy to export to Excel and sort on the last column, or simply scroll down through the list and see any devices that were not backed up recently.


          3 of 3 people found this helpful
            • Re: Alerts on the age of the most recent NCM backup?

              *facepalm* i forgot about that setting, and over thought the solution again thanks for the help!

              • Re: Alerts on the age of the most recent NCM backup?

                Thank you for this post almost made my own for something similar. Looking for a way to have in the default report NCM has for nightly backups to have the last successful so I can have a better idea of new issues rather than known ones. Not sure it's possible yet and think that would take tinkering with things I shouldn't yet.

                  • Re: Alerts on the age of the most recent NCM backup?

                    There are some alternate options, if you don't want to rely solely on the process I provided initially.


                    1.  Go to your NPM My Dashboards > Configs > Config Summary.  It should already be configured for some useful information, but you can customize the page to what you don't see present already.


                    Here's mine:   The image in the upper left makes seeing what's not backed up very simple.



                    I've found that image so useful that I added it to NPM's front page default fiew, along with the other things I find most useful:



                    But I still rely on those daily reports in my e-mail to see which devices did NOT backup last night.




                    2.  There are at least two Reports available that can tell you the status of any device's backup for Startup-config and Running-config:


                    When you run them, you'll see that last time each device was successfully backed up:



                    Better still, you can use this report in a schedule, adjust it to only show those devices that haven't been backed up in X Days, e-mail it regularly / automatically to anyone you need on a scheduled basis, and even export it to Excel or PDF.  Once I have it in Excel I sort by the last Running Backup date column and see if anything's out of line.




                    3.  Make your own reports with NPM's Web-based Report Builder, or with the on-server Report-Writer application.


                    Here's hoping one of these is right for you!