Importing Schedule Information

You can import device information from another Junos Scope server, or you can use the provided sample XML import file export-import-sample.xml as a guide.

Note: Use only utc-milliseconds in the <start-time> element. This is the number of milliseconds since the epoch January 1, 1970. The <start-time> element text is ignored. The <period> element text can be every minute, every 5 minutes, every 15 minutes, every 30 minutes, every hour, every 6 hours, every 12 hours, every day, every 2 days, every week, every two weeks, every month, or every year.

Importing device information is useful when you do not want to enter setup information manually.

Importing access method or authentication information is useful when you want to use existing access method and authentication data that you have exported from another Junos Scope software server instead of adding that information manually.

To import schedules information, follow these steps:

  1. In the Junos Scope main window, click Settings > Schedules. The Schedules dialog box appears.
  2. Click Import. The Import Schedules dialog box appears.
    Image import-schedules.gif
  3. In the File text box, either browse to or type the name of the XML file that you want to import. For example, you can import the default schedules.xml export file from another Junos Scope server or use the provided sample export-import-sample.xml XML file on the Junos Scope server to generate a file to import.
  4. To support synchronizing Junos Scope settings imported from multiple servers, select an import method to be used if a conflict occurs between existing records stored in the Junos Scope server and imported records. The available import method options include:
    • Ignore—(Default) An existing record stored in the Junos Scope server takes precedence over any imported record. The imported record is ignored and the existing record is not affected. Any imported record that does not exist in the Junos Scope server is inserted.
    • Merge—If a record exists in the Junos Scope server and also exists in the imported record, the imported record merges with the existing record and is augmented as necessary. If an imported record is in conflict with an existing record, the imported record takes precedence over the existing record. The existing record is merged with the imported record; however, the fields of imported record take precedence over the fields of the existing record. Any imported record that does not exist in the Junos Scope server is inserted.
    • Override—All records in the Junos Scope server are deleted, then all imported records are inserted. Before the override operation occurs, a message window appears with the following confirmation prompt: “ The import with override option will delete all the existing records. Do you want to continue?” Select Yes or No to continue.
  5. Click Import. The Import status dialog box appears.
    Image schedules-import-confirm.gif

    The dialog box indicates the number of records imported successfully and unsuccessfully. The Details column provides a description for records that fail import.

  6. Click OK. The imported data is listed in the Groups dialog box.