Welcome to Infoblox NetMRI Community Sign in | Join | Help
in Search

Export all configs for a group without passwords

Last post 03-08-2010 9:50 AM by elijah. 2 replies.
Page 1 of 1 (3 items)
Sort Posts: Previous Next
  • 03-05-2010 7:46 PM

    Export all configs for a group without passwords

    I have a vendor asking for a copy of our switch and router config files.  I'm OK with giving tehm most of hte info, but would like to have the passwords stripped out the files.  Like the way the "show tech" does. 

    Is there any way to do this?  Or do I need to just export all the files, then strip out the passwords manually?

    Thank You

  • 03-06-2010 1:04 PM In reply to

    Re: Export all configs for a group without passwords

    I've not seen an automated way to do that yet.  It would be nice to have a CCS script that could be run when needed.

  • 03-08-2010 9:50 AM In reply to

    Re: Export all configs for a group without passwords

    If you have a command that outputs just what you want, this should be something you can script and save the output using the Archive command in your script.

    For more info on this you can look in the included documentation under Configuration Management>Job Management side tab>Script Reference>CCS data archive and export (excerpt below)


    CCS data archive and export

    The CCS Data Archive / Export feature enables you to archive and export any information available via the CLI. Data archiving is accomplished using the ARCHIVE keyword. Archived data can then be exported from NetMRI using HTTP.

    The ARCHIVE keyword

    The ARCHIVE keyword is supported in the Action/Trigger-Commands sections of a CCS file and can be used to save the output of various CLI commands into one or more files. The keyword can be followed by an optional file name and should precede all commands for which the output should be archived. For example:

    Action-Commands:
    ARCHIVE (config.txt): show running-config

    would store the output of the show running-config command in the file config.txt.

    Output from multiple commands can be stored in the same file, for example:

    Action-Commands:
    ARCHIVE (config.txt): show running-config
    ARCHIVE (config.txt): show startup-config

    would store the output of the commands show running-config and show startup-config in the file config.txt.

    Variables can be used to specify the name of the file dynamically, for example:

    Action-Commands:
    ARCHIVE (config-$ipaddress.txt): show running-config

    would store the output of the show running-config command in the file config-10.10.10.1.txt, assuming the script was currently running against the device 10.10.10.1.

    At the end of a job, files created using the ARCHIVE keyword are placed in a single .zip file. You can view the files and download the .zip file in the Files tab in the Job Viewer.

    It is important to dynamically specify file names. For example, if a job runs against two devices and the script specifies a static file name, both jobs would use the same file name. At the end of the job, only one file would be contained in the .zip file because of the file name collision (i.e., there is no directory structure contained in the .zip file).

    CCS Data Export

    Besides being accessible through the Files tab in the Job Viewer, the most recent archive .zip file is placed in a global location where it can be accessed via an HTTP transaction. Details on this transaction are as follows:

    Request Info
    URL:  /netmri/ccs/tx/common/GetArchive.tdf
    Parameters:  N/A

    Response Info
    Content-Type:  application/zip
    Content-Disposition:  NetMRI_CCS_Archive.zip
    Content:  The most recent ARCHIVE .zip file

    Use this mechanism to export the most recent archive .zip file to an external application or server on a scheduled basis using a tool such as wget.

    Technical Support Engineer
    Netcordia, Inc.
    410-266-6161 option 3
Page 1 of 1 (3 items)