Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Configuring Global Settings

 

After installing Junos Space Service Now and configuring it to operate in a specific mode, you must configure the global settings to define purge time for device snapshots, incidents, log files, and BIOS attachments.

Starting in Service Now Release 16.1R1, the Submitted Incident Purge Time (in days) and Not Submitted Incident Purge Time (in days) fields are available on the Global Settings page to define the number of days after which incidents that are submitted to JSS and incidents that are not submitted to JSS can be purged respectively

Starting in Service Now Release 16.1R1, the Do not auto submit Incident which are older (in days) is available on the Global Settings page to prevent incidents older than the number of days specified in the field from being submitted to JSS by auto submit policies.

To configure Service Now global settings:

  1. From the Service Now navigation tree, select Administration > Global Settings.

    The Global Settings page appear as shown in Figure 1.

    Figure 1: Global Settings Page
    Global Settings Page
  2. Enter values for the global settings as described in Table 1.
  3. Click Save to save the global settings and update Service Now or click Cancel to navigate back to the Global Settings page without saving the entries.

    If you click the information icon displayed next to the Global Settings page heading, the Help page for configuring global settings is displayed.

Table 1 describes the fields displayed on the Global Settings page.

Table 1: Global Settings Parameters

Name

Description

Range/Length

Default

Outbound Email Address

E-mail address that the recipients of e-mails from Service Now see (for example, exampleservicenow@juniper.net)

Device Snapshot Purge Time (in days)

Number of days device snapshots of a device are stored in the Service Now database before they are deleted

0 indicates that device snapshots are never purged.

  • 0

  • 90

  • 120

  • 180

  • 365

180

Product Health Data Purge Time (in days)

The number of days the information about product health data (PHD) is stored in Service Now database.

0 indicates that the information about PHD is never deleted from the database.

  • 0

  • 30

  • 45

  • 60

  • 90

  • 120

  • 180

  • 365

30

Submitted Incident Purge Time (in days):

Number of days incidents submitted to JSS are stored in the Service Now database before they are deleted

0 indicates incidents submitted to JSS or Service Now partner are never purged.

  • 0

  • 30

  • 45

  • 60

  • 90

  • 120

  • 180

  • 365

365

Not Submitted Incident Purge Time (in days):

Number of days incidents that are not submitted to JSS are stored in the Service Now database before they are deleted

0 indicates incidents that are not submitted to JSS or Service Now partner are never purged.

  • 0

  • 30

  • 45

  • 60

  • 90

  • 120

  • 180

  • 365

365

Device Log File Purge Time (in days)

Number of days log files collected from devices are stored in the Service Now database before they are deleted.

1 – 365

30

Do not Auto Sbbmit Incident which are older (in days):

Number of days after which incidents are not submitted to JSS by using auto submit policies

1 – 365

3

Repeat Incident Dampening Period

The time period during which Service Now does not create new incidents on receipt of JMBs for the same event from a device.

In other words, if the same event occurs on a device multiple times during the specified time interval, Service Now creates an incident only for occurrences of the event on the device.

This value can be overridden by configuring a dampening period for each event in the Auto Submit Policy.

For information about the Auto Submit Policy, see Creating an Auto Submit Policy.

  • None—Always creates the incident.

  • Always—Does not create the incident after the first occurrence of the event on the selected devices.

  • 1hr – 12hr

  • 1 day – 5 days

  • 10 days

  • 15 days

  • 20 days

  • 25 days

  • 30 days

  • 45 days

  • 60 days

  • 90 days

  • 120 days

0

Share Service Now Profile Information

If this check box is selected, all Service Now-related information is shared with JSS or Service Now partner for tracking purposes.

This option is not available in Offline mode.

Service Now-related information is shared with JSS or Service Now partner.

Collect Log Files

If this check box is selected, log files are collected from all Service Now devices.

This behavior is overridden by log collection settings configured on individual Service Now devices.

Logs are collected from Service Now devices.

Connection Status

Status of the connection from Service Now to JSS or Service Now partner.

  • OK

  • No route to host

  • Connection refused

  • The Home Base server is temporarily unable to service your request

 
Release History Table
Release
Description
Starting in Service Now Release 16.1R1, the Submitted Incident Purge Time (in days) and Not Submitted Incident Purge Time (in days) fields are available on the Global Settings page to define the number of days after which incidents that are submitted to JSS and incidents that are not submitted to JSS can be purged respectively
Starting in Service Now Release 16.1R1, the Do not auto submit Incident which are older (in days) is available on the Global Settings page to prevent incidents older than the number of days specified in the field from being submitted to JSS by auto submit policies.