AI-Scripts run on Juniper Networks J-series, M-series, MX-series, T-series, EX-series, and SRX-series devices. Ensure that all devices on which you install AI-Scripts are running JUNOS Release 9.0 or later. For the latest AI-Scripts information, see the AI-Scripts Release Notes located at http://www.juniper.net/support/.
Each AI-Script install package supports at least 3 previous years of JUNOS software releases.
It does not matter whether AI-Scripts or AIM is installed first. However, for both, it is necessary to know the archive location (archive-site destination) used for devices to send incident and intelligence JMBs and for AIM to retrieve this data. You can add the archive location to the device JUNOS configuration for both AI-Scripts and AIM after the initial installation, but the components are not usable until the archive location is configured.
There are two ways to install AI-Scripts:
AI-Script install packages are versioned as follows:
For example:
Using a Web browser, go to the following location:
Log in to the Juniper Networks authentication system using the username and password supplied by Juniper Networks. To download the software, you must have a service contract and an access account. If you do not have an access account, complete the registration form at the Juniper Networks Web site, https://www.juniper.net/registration/Register.jsp.
Download the AI-Scripts install package.
If you are installing an AI-Scripts install package manually, move the package to the /var/sw/pkg directory on the device. If you do not move the AI-Scripts install package to the device, you have to use FTP or SCP in conjunction with the request system scripts add command.
If you will use the JUNOScope software to automatically install a package to a group of devices at once, download the AI-Scripts install package to the same server as Advanced Insight Manager (AIM).
AI-Scripts are installed on a device hard disk in the following location:
AI-Scripts are installed on a device flash drive in the following location:
 |
Note: If you configure the load-scripts-from-flash option, the system reads event-scripts from the /config/scripts/ directory. Otherwise the system reads AI-Scripts from the /var/db/scripts/ directory. The /var/run/scripts directory will always point to the right scripts directory. |
For the latest AI-Scripts installation information, see the AI-Scripts Release Notes and AIS User Guide
No, AIM does not need JUNOScope. However, you can optionally install AI-Scripts on JUNOS 9.0 or later devices that are managed by JUNOScope, then import these devices into AIM using JUNOScope Settings.
This configuration determines the AIS archive location where JMBs are deposited for a device.
The AI-Script installer creates this script to activate AI-Scripts on the device.
Transient changes are configuration changes made by commit scripts that do NOT appear in the committed configuration (except with a special command).
This configuration applies the configuration group juniper-ais.
|
Note: If you configure the load-scripts-from-flash option, the system reads AI-Scripts from /config/scripts/ directory. Otherwise the system reads AI-Scripts from the /var/db/scripts/ directory. The /var/run/scripts directory will always point to the right scripts directory. |
groups {
juniper-ais {
system {
scripts {
commit {
allow-transients;
file jais-activate-scripts.slax {
optional;
}
}
load-scripts-from-flash;
}
}
event-options {
destinations {
juniper-junoscope {
archive-sites {
"ftp://anonymous@10.7.0.124/aimdemo";
}
. . .
system {
scripts {
commit {
allow-transients;
file jais-activate-scripts.slax {
optional;
}
}
}
}
event-options {
event-script {
file problem-event-pfecrash.slax;
file problem-event-dcrash.slax;
file intelligence-event-main.slax;
file SPD_EVLIB_CREATE_FAILURE.slax;
file SPD_DAEMONIZE_FAILED.slax;
file RPD_TASK_FORK.slax;
. . . }
destinations {
juniper-junoscope {
archive-sites {
"ftp://anonymous@10.7.0.124/aimdemo";
}
}
}
}
Yes, install the AI-Scripts on each Routing Engine.
Use the show configuration groups juniper-ais|display commit-scripts command:
system {
scripts {
commit {
allow-transients;
file jais-activate-scripts.slax {
optional;
}
}
}
}
event-options {
event-script {
file problem-event-pfecrash.slax;
file problem-event-dcrash.slax;
file intelligence-event-main.slax;
file SPD_EVLIB_CREATE_FAILURE.slax;
file SPD_DAEMONIZE_FAILED.slax;
file RPD_TASK_FORK.slax;
. . . }
destinations {
juniper-junoscope {
archive-sites {
"ftp://anonymous@10.7.0.124/aimdemo";
}
}
}
}
The event-options/event-script section should have a long list of *.slax files if the AI-Scripts are activated correctly.
Check the following:
user@host> show log messages | match
transferSep 20 00:50:13 ex-vc-1 root: transfer-file: Transferred /tmp/evt_op_aEpNja
- user@host> show configuration groups juniper-ais
event-options destinations
- juniper-aim {
- archive-sites {
- "ftp://anonymous@172.19.59.174/sv_aimdemo2";
- }
- }
or the directory configured in AIM setting under Organizations >> Device Group >> Local Location.
An iJMB is generated within 5 minutes after AI-Scripts installation.
The show version CLI operational command displays the version of the AI-Script install package that is installed on a device.
The JMB contains the output of the show version CLI command to indicate the version of the AI-Script install package installed on a device. You can view the JMB in AIM Incident Manager or Intelligence Manager.
