Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Troubleshooting AI-Scripts Installation Issues

    Problem

    Description: The installation of AI-Scripts on a device running Junos OS fails.

    Symptoms:

    • The AI-Scripts bundle is not being installed properly on the device.
    • During the installation of the event profile, the SLAX files are not copied to the device.
    • AI-Scripts installed on a device do not generate a JMB for a particular event.

    Solution

    Resolution

    Verifying the AI-Scripts Installation

    To verify that an AI-Scripts bundle is installed on a device running Junos OS:

    1. Log in to the device.
    2. Run the show version command.

      If the AI-Scripts bundle is installed on the device, the show version command lists the version of the AI-Scripts bundle installed on the device, as shown in the following sample:

      Hostname: mx-80-sn2
      Model: mx80-48t
      JUNOS Base OS boot [11.4R6-S2]
      JUNOS Base OS Software Suite [11.4R6-S2]
      JUNOS Kernel Software Suite [11.4R6-S2]
      JUNOS Crypto Software Suite [11.4R6-S2]
      JUNOS Packet Forwarding Engine Support (MX80) [11.4R6-S2]
      JUNOS Online Documentation [11.4R6-S2]
      JUNOS Routing Software Suite [11.4R6-S2]
      JUNOS AIS Script Suite [4.1R1.1]
      

      The presence of JUNOS AIS Script Suite in the output of the show version command indicates that AI-Scripts Release 4.1R1.1 is installed on the device.

    3. If you do not find JUNOS AIS Script Suite in the output of the show version command, see:

    Resolving Issues with Copying Event Scripts to Devices

    During the installation of an event profile on a device, the SLAX files are not copied to the devices and the Jobs status page displays an error as shown in Figure 1.

    Figure 1: Service Now Event Profile Install/Uninstall Status

    Service Now Event Profile
Install/Uninstall Status

    To copy event scripts to devices:

    1. Log in to the device running Junos OS.
    2. Execute the following command to check permissions for /var/db/scripts/commit, /var/db/scripts/event, and /var/db/scripts/op directories:
      # run file list /var/db/scripts/

      The permissions for the /var/db/scripts/commit, /var/db/scripts/event, and /var/db/scripts/op directories should be drwxrws---.

      drwxrws---   2 root  wheel   1024 Jan 30 15:27 commit
      drwxrws---   2 root  wheel  21504 Jan 30 15:27 event 
      drwxrws---   2 root  wheel   1024 Jan 30 15:26 op 
    3. If the permissions are not as shown in the preceding example, enter configuration mode and navigate to the /var/db/scripts directory.
    4. As root at the shell level, execute chmod 2770 to set the directory permissions as drwxrws--- for the /var/db/scripts/commit, /var/db/scripts/event, and /var/db/scripts/op directories.
    5. Retry installing the event scripts.

    Verifying the Event Scripts Installed on the Device

    To verify the event scripts installed on the device:

    1. Log in to the device.
    2. Execute the show configuration groups command as follows:
      show configuration groups juniper-ais | display commit-scripts

      The following output is displayed:

      system {
      	scripts {
      		op {
                  file ais-pt_attachment.slax;
                  file ais-rma_attachment.slax;
                  file ais_change_perm.slax;
                  file ais_core_perm.slax;
                  file on-demand.slax;
                  file remove-jais.slax;
                  file jais-commit-optimize.slax;
                  file ais_arc.slax;
                  file ais-attach-file.slax;
                  file stop-ais-now.slax;
                  file ais_signalSN.slax;
                  file ais_core_chm.slax;
                  file ais_all_chm.slax;
                  file att_signalSN.slax;
                  file ais-rsi-chk.slax;
                  file ais-rsi-delay.slax;
                  file ais-rsi-holdoff.slax;
                  file ais-param-set.slax;
                  file ais-sleep.slax;
                  file ais-error.slax;
                  file ais-health-report.slax;
                  max-datasize 256m;
      			}
      		}
      	}
      event-options {
          event-script {
              max-datasize 128m;
              file UI_CMDLINE_READ_LINE.slax;
              file UI_NETCONF_CMD.slax;
              file bios.slax;
              file bios-interval.slax;
              file ACCT_MALLOC_FAILURE.slax;
              file ACCT_XFER_POPEN_FAIL.slax;
              file ASP_PGCP_IPC_MSG_WRITE_FAILED.slax;
              file ASP_PGCP_IPC_PIPE_WRITE_FAILED.slax;
              file AUDITD_RADIUS_OPEN_FAILED.slax;
              file AUDITD_RADIUS_REQ_CREATE_FAILED.slax;
              file AUDITD_SOCKET_FAILURE.slax;
              file AUTHD_AUTH_CREATE_FAILED.slax;
              file AUTHD_SERVER_INIT_BIND_FAIL.slax;
              file AUTHD_SERVER_INIT_LISTEN_FAIL.slax;
              file AUTHD_SETSOCKOPT_FAILED.slax;
              file AUTHD_SOCKET_FAILED.slax;
              file AUTOCONFD_AUTH_NO_MEM.slax;
              file AUTOD_RECV_FAILURE.slax;
              file AUTOD_SEND_FAILURE.slax;
              file AUTOD_SOCKET_CREATE_FAILURE.slax;
              file AV_PATTERN_TOO_BIG.slax;
              file AV_PATTERN_WRITE_FS_FAILED.slax;
              file BFDD_READ_ERROR.slax;
              file BFDD_WRITE_ERROR.slax;
              file BOOTPD_HWDB_ERROR.slax;
              file CFMD_RTSOCK_OPEN_FAILURE.slax;
              file CHASSISD_BUS_DEVICE_OPEN_FAILURE.slax;
              file CHASSISD_CFEB_POWER_FAILURE.slax;
              file CHASSISD_CLOCK_FAILURE.slax;
              file CHASSISD_CMB_READBACK_ERROR.slax;
      			
      }
          destinations {
              juniper-aim {
                  archive-sites {
                      /var/tmp/;
                  }
              }
          }
      }
      

      If event scripts are installed on the device, and the AI-Scripts version is Release 5.0R1 or earlier, the show configuration groups juniper-ais command lists the event scripts (.slax files) from the AI-Scripts bundle that are installed on the device under event-options. If event scripts are not listed under event-options in the output, then either the event scripts are not installed on the device or if they are installed, the juniper-ais group is not applied to the device configuration.

      To verify that the juniper-ais group is applied to the device configuration, run the show configuration apply-groups command.

      show configuration apply-groups

      The following output is displayed for the command:

      ## Last commit: 2014-08-26 14:00:40 PDT by lab
      apply-groups [ re0 ASIA-ROUTING-REGION juniper-ais ];
      

      If the juniper-ais group is not listed in the output, issue the following command to apply the juniper-ais group:

      set apply-groups juniper-ais

      Verify that the juniper-ais group is applied to the device configuration by executing the show configuration groups juniper-ais command to list the event scripts installed on the device.

    Modified: 2017-02-22