The following issues exist in the current AI-Scripts release:
The AI-Scripts Juniper Message Bundle (JMB) does not include chassis-re-disk-module media information on the Routing Engine,
such as the flash drive and hard drive, in the JMB. (PR 279109)
J Series Routers or SRX Series Service Gateways running
JUNOS for J Series and SRX Series devices in cluster node configurations
must have AI-Scripts installed on each node separately. There is no
method for installing the AI-Scripts on both nodes simultaneously
with a single install command. (PR 409931/410417)
Use JUNOScope 9.0R2 or later, in conjunction with AI-Scripts
1.1R2, to automatically install AI-Scripts to multiple devices at
once.
To upgrade from AI-Scripts 1.0R2 to 1.1R2, follow these
steps:
Delete the existing scripts by using the request system scripts delete CLI command.
At the [edit groups juniper-ais event-options
destinations] hierarchy level, change and commit the event-options
destinations name as follows :
user@host# [edit groups
juniper-ais event-options destinations]
user@host# rename juniper-junoscope
to juniper-aim
Sometimes a device running AI-Scripts may not appear in
the AIM Console. To view the device in AIM, do the following:
From the device to the archive location, make
an sFTP or scp connection.
For a secure connection, ensure that the host authenticity
to the AIM server is established. For example,
root@staging-sw1% scp test25 jadmin@66.129.225.17:/opt/jmb-archives1/
The authenticity of host '66.129.225.17 (66.129.225.17)' can't be
established. RSA key fingerprint is 40:16:92:af:d5:7e:54:4f:ad:f7:c8:9a:9a:90:1f:95.
Are you sure you want to continue connecting (yes/no)? yes Warning:
Permanently added '66.129.225.17' (RSA) to the list of known hosts.
jadmin@66.129.225.17's password:
Intelligence JMBs (iJMBs) may not appear in an AIM archive
location, and therefore may not appear in AIM Intelligence Manager.
To resolve this issue, follow these steps:
Log in to the device as root user.
Connect to the AIM server using an SSH connection.
Accept the security authentication.
Change the archive directory (for example, /var/aim/jmb-archives4/) permissions from the default of 755
to 733 to allow JMB files to be written using the following command:
chmod 733 jmb-archives4
To confirm directory permissions, use the following
command:
