Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Exporting and Importing Configuration Views

 

You export Configuration Views from the Junos Space Network Management Platform database to your local computer so that copies of Configuration Views are locally available. Configuration Views are exported in the XML format. You import Configuration Views from your local computer to the Junos Space Platform database so that copies of Configuration Views are stored in the database. Configuration Views are imported in the XML format. You can also overwrite existing Configuration Views in the Junos Space Platform database. An audit log entry is created when you export or import a Configuration View.

Note

You cannot export the default Configuration View Default View from the Junos Space Platform database. If you select the Default View, the Export Configuration Views option is unavailable.

When you export multiple Configuration Views from Junos Space Platform, they are exported as a single XML file in the following format:

<configuration-views>

<configuration-view>configuration-view1</configuration-view>

<configuration-view>configuration-view2</configuration-view>

<configuration-view>configuration-view3</configuration-view>

<configuration-views>

Exporting Configuration Views

You export Configuration Views in the XML format to your local computer.

To export Configuration Views:

  1. On the Junos Space Network Management Platform user interface, select CLI Configlets > Configuration View.

    The Configuration View page that appears displays all the Configuration Views in the Junos Space Platform database.

  2. Select the Configuration Views that you want to export and select Export Configuration Views from the Actions menu.

    The Export Configuration Views dialog box is displayed.

  3. You can export only those Configuration Views you selected or all Configuration Views (except Default View) from the Junos Space Platform database.Note

    If the Configuration View you selected is script dependent, the local script-name field displays only the name of that local script that is referred to in the Configuration View.

    To export selected Configuration Views:

    1. Click Export Selected in the Export Configuration Views dialog box.

      The Export Configuration Views dialog box is displayed. When the job is completed, the Export Configuration Views dialog box indicates that the job is 100% complete.

    2. Click the Download link in the dialog box to export the Configuration Views.

      The Configuration Views are downloaded to the local computer.

    To export all Configuration Views:

    1. Click Export All on the Export Configuration Views dialog box.

      The Export Configuration Views dialog box is displayed. When the job is completed, the Export Configuration Views dialog box indicates that the job is 100% complete.

    2. Click the Download link in the dialog box to export the Configuration Views.

      The Configuration Views are downloaded to the local computer.

  4. (Optional) Click the progress bar in the Export Configuration Views dialog box to view the details of the job on the Job Management page.

    You are directed to the Job Management page.

To return to the Configuration View page, click the [X] icon in the Export Configuration Views dialog box.

Importing Configuration Views

You cannot import Configuration Views if they contain invalid data such as an invalid script name or an invalid device family. If one of the Configuration Views contain invalid data, the import job fails.

To import Configuration Views:

  1. On the Junos Space Network Management Platform user interface, select CLI Configlets > Configuration View.

    The Configuration View page that appears displays all the Configuration Views in the Junos Space Network Management Platform database.

  2. Click the Import Configuration Views icon on the toolbar.

    The Import Configuration Views page is displayed.

  3. (Optional) Click the View Sample Link on this page to view the valid format of the Configuration View XML file.
  4. Click Browse and select the Configuration View XML file.
  5. Click Import.Note

    You cannot import Configuration Views if they contain invalid data such as an invalid script name or an invalid device family. If one of the Configuration Views contain invalid data, an error message indicates the reason for the failure of the import job of the Configuration View.

    • If the Configuration View you are importing does not exist in the Junos Space Platform database, the Configuration View is imported to the database. When the Configuration View is imported, the Import Configuration Views dialog box is displayed.

      To accept the import of the Configuration View:

      1. Click OK.

        You are redirected to the Configuration Views page.

    • If a Configuration View with the same name exists in the Junos Space Platform database, the Configuration View Already Exists dialog box is displayed. You can overwrite the existing Configuration View or cancel the workflow.

      • To overwrite an existing Configuration View:

        1. Click OK.

          The Import Configuration View dialog box is displayed.

        2. Click OK.

          You are redirected to the Configuration Views page.

      • To avoid overwriting and cancel the workflow:

        1. Click Cancel.

          The Import Configuration View dialog box is displayed.

        2. Click OK.

          You are redirected to the Configuration Views page.