The main window is displayed when you log in to the software using a Web browser on a client workstation. The main window includes the main command links to all of the various JUNOScope software modules. For more information about the parts of the JUNOScope main window, see Figure 16.
The JUNOScope software provides the following main modules. They appear as main command menus and as tabs in the JUNOScope software user interface. Each main menu has a set of submenus that correspond to administrator or user tasks.
The Looking Glass module provides a graphical user interface (GUI) for querying and viewing device status and troubleshooting information from connected devices, including router chassis, system management, Adaptive Services (AS) Physical Interface Card (PIC), Border Gateway Protocol (BGP), Intermediate System-to-Intermediate System (IS-IS), Open Shortest Path First (OSPF), Multiprotocol Label Switching (MPLS), and Resource Reservation Protocol (RSVP) status information. For more information about Looking Glass, see Using Looking Glass.
The JUNOScope software configuration management module lets users manage device configurations that are currently running on connected devices and configurations that have been archived or imported in the JUNOScope CVS repository.
The configuration management module lets you view and edit current device configurations using the Configuration Browser and the Configuration Editor.
(Configuration > Current >View) Provides a GUI for viewing the setup of the currently committed configuration that is running on a selected device. Use the Configuration Browser to view the configuration statement hierarchy in brief or detailed mode, including viewing statement inheritance. For more information, see Using the Configuration Browser.
(Configuration > Current > Edit) Provides a GUI for editing a configuration on a selected device. Use the Configuration Editor to modify the existing configuration. You can also use the Configuration Editor to commit the modified configuration, as well as discard any unwanted configuration changes. If a device has redundant Routing Engines, committed changes will be synchronized on both the master and backup. For more information, see Using the Configuration Editor.
The configuration management module lets you archive and import devices configurations into the JUNOScope CVS repository. The repository holds version of device configurations. Each device can have many different versions of a configuration in the repository. Once a device configuration version is stored in the JUNOScope repository, you can manipulate it, including tag, audit, compare, display, or restore.
(Configuration > Repository > Archive) Lets you download the active configuration file from a device or group of devices. The downloaded version of the configuration file is archived in the JUNOScope software CVS repository. You can save configuration archive operations and combine them with other operations, such as restore and inventory scan, to be run concurrently or sequentially in real time or at a scheduled interval. For more information, see Archiving and Manipulating Device Configurations.
(Configuration > Repository > Archive Tags) Lets you associate tags with a configuration version so you can compare it with another version. The comparison can be made with the active or current configuration or with a version from the JUNOScope CVS repository. For more information about tagging device configurations, see Setting Up Archived Configuration Tags and Auditing Configurations and Partial Configurations.
(Configuration > Repository > Audit Configurations) Lets you check for differences between device configuration versions in the JUNOScope CVS repository for one or more devices. For more information about auditing differences in device configurations, see Setting Up Archived Configuration Tags and Auditing Configurations and Partial Configurations.
(Configuration > Repository > Compare) Lets you compare the differences between the contents of two revisions of a configuration file that you select in JUNOScope. By default, the JUNOScope software compares the newer revision of a configuration file to an older one. You can also select to compare an older revision of a configuration file with a newer one. For more information, see Comparing Configuration Files.
(Configuration > Repository > Display) Displays the contents of a configuration file revision that you select in JUNOScope. For more information, see Displaying a Configuration File.
(Configuration > Repository > Transfer on Commit) Lets you configure devices to transfer its currently active configuration to JUNOScope each time a candidate configuration is committed. For more information, see Configuring the JUNOScope Server for Transfer on Commit.
(Configuration > Repository > Import) Lets you import into JUNOScope a portion or all of a device configuration that you have saved in ASCII file format to a file on the local file system. The imported configuration is stored in the CVS repository. You can then compare, display, or restore the imported configuration. For more information about importing configuration files, see Importing and Deleting Configuration Files.
(Configuration > Repository > Restore) Uploads an archived configuration file to the device from which it was archived or uploads an imported configuration to a selected device. JUNOScope locks the device configuration and loads the new configuration on the device, overriding or merging (discarding) the old configuration. JUNOscope issues a commit confirmed command and a commit-configuration JUNOScript XML tag command. If the target device has installed and configured dual Routing Engines, JUNOScope issues a commit synchronize command. JUNOScope then unlocks the configuration. If an error occurs, JUNOScope issues a rollback command, causing the configuration to revert to the last saved configuration.
You can save configuration restore operations and combine them with other operations, such as archive and inventory scan, to be run concurrently or sequentially in real time or at a scheduled interval.
For more information, see Restoring a Configuration File.
(Configuration > Repository > Delete) Lets you delete user imported configuration files from the JUNOScope CVS repository. For more information see Importing and Deleting Configuration Files.
(Configuration > Repository > Save) Lets you save archived configurations to a local file system. For more information see Archiving and Manipulating Device Configurations.
(Configuration > Repository > Edit) Lets you edit an archived configuration file. For more information see Archiving and Manipulating Device Configurations.
(Configuration > Repository > Scripts) Lets you Lets you manage JUNOS-based scripts. JUNOS-based scripts such as commit scripts, operation (op) scripts, and event scripts can be imported into the JUNOScope CVS repository from the local file system and deployed to a group of routers.You can also view, edit, compare, and disable these scripts. For more information see Managing JUNOS Scripts.
The Inventory Management System module consists of two main features: Scan and Reports.
If the Inventory Management System software module is not licensed for use, the JUNOScope software administrator should select not to install it. If this software module is not installed, it is disabled (unavailable) in the JUNOScope main window.
An external inventory application can connect to the Inventory Management System database and extract inventory data, such as hardware, software, licensed features, and inventory scan events, from the database by way of a Structured Query Language (SQL) interface. A unique username and password must be configured during the JUNOScope software installation to enable read-only access to the Inventory Management System database.
The Inventory Management System includes Demo reports generated from a demonstration database so you can learn how to use report features with having to actually scan device inventory on the production network.
The Scan feature scans the inventory of one or more selected devices for hardware, software feature licenses, and JUNOS Software and its installed packages. The Inventory Management System scans devices in real time or as part of a scheduled operation. You can save inventory scan operations and combine them with other operations, such as archive and restore, to be run concurrently or sequentially in real time or at a scheduled interval.
For more information about scanning inventory items on devices, see Scanning Inventory Data.
Once device inventory has been scanned and stored in the JUNOScope database, you can generate various predefined or user-specified reports. You can manipulate inventory reports using tools to sort, query, and configure columns. You can save custom inventory reports, including user-specified definitions and controls. All JUNOScope users can view and share saved inventory reports. The Inventory Management System displays reports in a browser in HTML, and can also be exported in Extensible Markup Language (XML), comma-separated values (CSV) text, Adobe PDF, and Microsoft Excel formats. For more information, see Using Inventory Reports.
The Inventory Management System repository allows you to schedule custom inventory reports to run at a specified time without intervention and to view archived custom inventory reports that have been run.
For more information about scheduling and viewing custom inventory reports, see Scheduling Custom Inventory Reports and Viewing Archived Inventory Reports.
Software Manager is a licensable module that controls the deployment and installation of JUNOS Software images in a network. Administrators can use Software Manager as the central management point from which to import, download and install software images in a controlled and auditable manner. Used with other JUNOScope features, such as the Task Manager, Scheduler and Inventory Manager, Software Manager allows the administrator to better control how and when JUNOS Software images are rolled out in a network. For more information about Software Manager, see Using the Software Manager.
Provisioning is a licensable module that enables you to provision MPLS and GRE tunnels as well as pseudowires for carrying legacy network traffic over MPLS and IP networks. To access Provisioning tab, you must have installed IP Backhaul manager license. Provisioning tab enables you to configure and provision MPLS and GRE tunnels, and to provision, filter, and test pseudowires. For more information about Provisioning, see .
The JUNOScope monitor operations component lets users perform the following tasks.
Display a schedule of pending operations that are configured. You can also delete operations. An operation appears in Manage Operations when you use the Configuration > Repository > Archive command and the Inventory Management > Scan command to set an archive schedule for a specified time and interval. An operation is not listed when you schedule an operation using the Now option. For more information, see Managing Operations.
Display the status of all JUNOScope operations run on all devices, groups, or selected devices. You can apply a filter to see only specific operations, such as operations run at a specific time or with a particular status. The JUNOScope operations are listed by device or group name on which the operation occurs, operation status, operation start time, last update time, and any message about the operation. Operation status includes pending, connecting, writing, success, or error. For more information, see Viewing and Maintaining Operation Status.
Display the records of all JUNOScope user authentication activities and privileged operations that are stored in the database. Authentication activities include user logins, login failures, logouts, and session timeouts. Privileged operations are changes of information in the system or network, including configuration commits, configuration archives, user account additions, user account deletions, password changes, device additions, device deletions, label association changes, and authentication information changes. User authentication activity and privileged operation audit records are also sent as system log messages to the system log server and to an optional RADIUS accounting server if one is configured.
Delete unwanted records from both the Status and Audit Log tables. The Status Log displays the records of all JUNOScope operations run on all devices, groups, or selected devices. The Audit Log table displays the records of all JUNOScope user authentication activities and privileged operations that are stored in the database. You can filter the records you don’t want by specified criteria.
The JUNOScope system settings component lets the administrator set up the software to work with the following information.
Specify the authentication information (login and password for accessing a device). The JUNOScope software administrator can chose to have sensitive data encrypted at export. For more information, see Setting Up Authentication Information.
Specify the access method (JUNOScript access protocol to connect to the JUNOScript server running on a device) configured on a device for remotely connecting to that device from the JUNOScope software. The JUNOScope software administrator can chose to have sensitive data encrypted at export. For more information, see Setting Up Access Methods.
Connect to and discover information about devices on the network. The JUNOScope software performs operations on devices, such as archive, display, compare, or restore. Additionally, the JUNOScope software scans devices for inventory information. You can associate a device with one or more text labels used to statically organize a group of devices for JUNOScope operations. For more information, see Setting Up Devices.
Group devices for performing immediate or scheduled operations using criteria, such as device name, model, hostname, comment, or label (see Labels). For more information, see Setting Up Groups.
Labels, in free text format, provide a way to statically associate a group of devices. A label must have a unique name, such as Edge; an optional category name, such as Router Type, so you can logically organize labels; and an optional comment to help you understand the label purpose. You can associate an existing label with one or more devices. You can use a label as a rule in the group criteria wizard for setting up groups of devices. For more information about setting up labels, see Setting Up Labels. For more information about associating a device with a label, see Setting Up Devices. For more information about using a label to create a group, see Setting Up Groups.
Specify the time or interval when you want the JUNOScope software to perform operations on one or more devices, such as archive, display, or compare a device configuration, or scan device hardware, software, or licensed feature inventory. For more information, see Setting Up Schedules.
Provides the following user authentication:
Set up RADIUS server host information so that users with RADIUS accounts can log in to JUNOScope. The JUNOScope administrator can also specify the port to which all user authentication activity and privileged operation audit records are sent. For more information, see Setting Up RADIUS Configuration.
Import or export required JUNOScope database data from or to another JUNOScope server.
The JUNOScope administrator can now export all JUNOScope data, with the following options for sensitive data:
The JUNOScope administrator can import sensitive data by supplying a key if the data was exported using the “ encrypt sensitive data and provide key at import time” method. Select an import method to be used if a conflict occurs between existing records stored in the JUNOScope server and imported records when synchronizing JUNOScope settings imported from multiple servers. The available import method options include ignore, merge, and override.
For more information, see Importing and Exporting All Settings Data.
You can save operations such as archive, restore, and inventory scan from devices on the network and reuse them to build compound operations. You can specify the order in which you want these compound operations to be executed. Reusing operations reduces production time and errors.
Use the Task Manager (Setting > Saved Operations) to create compound operations from archive, restore, or inventory operations that you save to reuse later. From Task Manager (the Saved Operations page), you can add compound operations, specify their execution order, run operations in real time or as part of an existing schedule, view simple operation settings. Edit the order in which compound operations run (concurrently or sequentially), and delete operations.