You import CLI Configlets in the XML format to add CLI Configlets
from a local computer to the Junos Space Network Management Platform
database. You can also import multiple CLI Configlets in a single
CLI Configlet XML file. Starting
with Junos Space Network Management Platform Release 15.2R1, you can
also import CLI Configlets from a Git repository to the Junos Space
Network Management Platform database.
Note: To select and import multiple CLI Configlet XML files
from the local computer:
Use the Mozilla Firefox or Google Chrome Web browser.
Currently, Internet Explorer does not support the selection of multiple
files.
Import multiple XML files in the TAR format.
Using a Git repository to import CLI Configlets creates a snapshot
of the CLI Configlet Git repository on Junos Space Platform. You can
synchronize CLI Configlets from the Git repository with the snapshot
on Junos Space Platform and import CLI Configlets from the Git snapshot
even if no active connection exists with the Git repository. For more
information about Git repository management on Junos Space Platform,
see Git Repositories in Junos Space Overview.
Junos Space Platform validates the CLI Configlets for
the following during import:
If Junos Space Platform detects a conflict during import and
you choose to overwrite the CLI Configlet, the conflicting CLI Configlet
is saved with an incremented version number in the domain and all
subdomains.
To import a CLI Configlet to Junos Space Platform:
- On the Junos Space Network Management Platform user interface,
select CLI Configlets > Configlets.
The Configlets page is displayed.
- Click the Import CLI Configlet icon on the toolbar.
The Import CLI Configlet page is displayed.
- Import CLI Configlets from a local computer or the Git
snapshot of the CLI Configlet Git repository.
Note: The fields on the Junos Space user interface to import
CLI Configlets from a Git repository are displayed only if an active
Git repository is configured on Junos Space Platform.
To import one or more CLI Configlets from the local computer:
Click the Import from files option button.
The Import CLI Configlet page displays the fields to import
a CLI Configlet from the local computer.
From the Import from files expandable area, click Browse and select the CLI Configlet file in the XML or TAR
format.
(Optional) To view a sample XML CLI Configlet file, click
the View Sample XML hyperlink.
A browser pop-up window is displayed.
You can download the sample XML file to the local computer.
To import one or more CLI Configlets from the Git snapshot:
Click the Import from git option button.
The Import CLI Configlet page displays the fields to import
the CLI Configlets from the Git snapshot.
The Import from git expandable area displays the URL to the
active CLI Configlet Git repository and the time when the Git snapshot
on Junos Space Platform was last synchronized with the Git repository.
From the Git Branch drop-down list, select
the branch on the Git snapshot from which the CLI Configlets should
be imported.
By default, the first branch in the Git snapshot is selected.
(Optional) To synchronize the Git snapshot on Junos Space
Platform with the active CLI Configlet Git repository, click Sync Now.
If the synchronization is successful, the Last Sync field is
updated and you can import the latest CLI Configlets.
By default, the Git snapshot on Junos Space Platform synchronizes
with the active CLI Configlet Git repository every hour.
Note: If Junos Space Platform cannot connect to the CLI Configlet
Git repository, an error message is displayed in a pop-up window.
Click OK to close the pop-up window.
(Optional) To view a sample XML CLI Configlet file, click
the View Sample XML hyperlink.
A browser pop-up window is displayed.
You can download the sample XML file to the local computer.
- Click Next.
The Import Configlets page that appears displays the CLI Configlets
from the selected Git branch or the local computer, in a table. Table 1 displays the columns in the table.
If you imported CLI Configlets in the TAR format, Junos Space
Platform displays the CLI Configlets in the TAR file on the Import
Configlets page.
Table 1: Import Configlets pageColumn
|
Description
|
Configlet
|
Name of the CLI Configlet
|
Conflict State
|
State of the CLI Configlet: NEW, CONFLICT, or NO_CONFLICT
The column displays NEW if the CLI Configlet does not exist
in Junos Space Platform.
If you are importing a CLI Configlet from the Git snapshot,
the column displays NO_CONFLICT when the CLI Configlet you are importing
was earlier imported from the same branch of the Git snapshot.
If you are importing a CLI Configlet from the local computer,
the column displays CONFLICT when:
If you are importing a CLI Configlet from the Git snapshot,
the column displays CONFLICT when:
The CLI Configlet was created and modified in Junos Space
Platform and is currently imported from the Git snapshot.
The CLI Configlet was earlier imported from the Git snapshot
and modified in Junos Space Platform (The Git Version column displays
a warning icon).
The CLI Configlet was earlier imported from a different
branch of the Git snapshot.
|
Domain
|
Domain with which the CLI Configlet is associated
The column is empty if the CLI Configlet does not exist in Junos
Space Platform.
|
Latest Version
|
Latest version of the identical CLI Configlet that is
currently stored in the Junos Space Platform database
The column is empty if the CLI Configlet does not exist in Junos
Space Platform.
|
Git Version
|
Commit ID of the CLI Configlet in the Git repository
when the CLI Configlet was last imported to Junos Space Platform from
the Git snapshot.
A Warning icon is displayed if the CLI Configlet was modified
in Junos Space Platform after importing the CLI Configlet from the
Git snapshot.
The column is empty if the CLI Configlet does not exist
in Junos Space Platform or if the CLI Configlet was never imported
from the Git snapshot.
|
Git Branch
|
Git branch from which the CLI Configlet was last imported
The column is empty if the CLI Configlet does not exist in Junos
Space Platform or if the CLI Configlet was never imported from the
Git snapshot.
|
Last Commit
|
Commit ID of the last commit operation of the CLI Configlet
in the selected branch of the Git repository
The column is empty if the CLI Configlet is imported from a
local computer.
|
- (Optional) To stop importing CLI Configlets that display
a CONFLICT state, select the Exclude conflicting configlets from
import check box.
All CLI Configlets displaying the Conflict state CONFLICT are
removed from the Import Configlets page. The Import Configlets page
displays only those CLI Configlets that will be imported to the Junos
Space Platform database.
Note: If some CLI Configlets cannot be imported, a warning message
is displayed in a pop-up window with the list of CLI Configlets that
are not selected for import. Click OK to close the pop-up
window.
- Click Finish.
Note: If you import CLI Configlets displaying the CONFLICT state,
a warning message is displayed. Click OK to import the
CLI Configlets. These CLI Configlets are imported with an incremented
version number.
The Import Configlets Job Information dialog box is displayed.
- Click the Job ID link to view the
job results.
Note: If the fields in the CLI Configlet XML file contains invalid
values, the job results display the CLI Configlets that were not imported
due to invalid values.
You are directed to the Job Management page with a filtered
view of the job.
- To return to the Configlets page, click OK.
When the job is complete, the CLI Configlets are imported to
Junos Space Platform.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.
15.2R1
Starting
with Junos Space Network Management Platform Release 15.2R1, you can
also import CLI Configlets from a Git repository to the Junos Space
Network Management Platform database.
15.2R1
Starting with
Junos Space Network Management Platform Release 15.2R1, CLI Configlets
can also be imported in TAR (containing XML files) format.