AIS is a Juniper Networks product that provides reactive and proactive support for EX-series, J-series, M-series, MX-series, and T-series routing platforms (devices) in customer networks that have been configured for and are running Advanced Insight Scripts (AI-Scripts).
This section contains the following information:
AIS consists of three major elements (see Figure 1):
Figure 1: AIS Major Elements
Specialized AI-Script install packages must be installed on AIS-configured JUNOS devices running JUNOS 9.0 or later. AI-Scripts, running on devices, automatically do the following:
For more detailed information about AI-Scripts, seeInstalling and Understanding AI-Scripts.
The Advanced Insight Manager (AIM) application provides a gateway between JUNOS device archive locations and JSS. AIM provides the following features:
AIM runs in three modes:
For more information about using AIM, see Using Advanced Insight Manager.
The Juniper Data Collector is an AIM service that collects data from Juniper Networks devices running JUNOS 8.5 or earlier in archive locations for proactive monitoring in AIM. The Juniper Data Collector also collects data from non-JUNOS devices, such as E-series devices and Netscreen Firewall/VPN (ScreenOS) devices. Devices are added using AIM Settings > Organizations where you create directives device groups for adding Juniper Data Collector devices.
The Juniper Data Collector functions like Advanced Insight Scripts (AI-Scripts). However it only creates intelligence JMBs, not incidents.
In AIM Organizations, you add Juniper Data Collector devices as directives device groups. For more information about adding directive devices to AIM, see Creating a Directives Group.
JSS, using the Juniper Networks knowledge base, engineering expertise, and specialized tools, can create cases that you open using AIM. JSS sends case status to AIM. JSS receives intelligence information from devices on the network using AIM and sends intelligence updates and alerts for which you have registered to AIM.
All communication between AIM and JSS occurs over a secure channel, and each transaction is authenticated and verified by JSS.
Juniper Networks J-Care Technical Services provide several levels of technical support for devices on the network. When the customer purchases certain J-Care Technical Services levels, AIS is available (AI-Scripts and certain AIM features). Table 9 shows the levels of J-Care Technical Services provided and the associated AI-Scripts and AIM features that are offered.
Table 8: J-Care Technical Services and AIS Functionality
The AIM application requires base, feature (optional), and capacity licenses. AIM License Management displays the current license and services after the license file is imported. For more information about AIM licensing, see Using AIM License Management.
You can deploy AIS several ways depending on your customer support models:
You, the AIS direct customer, install AIS software elements (AI-Scripts and AIM), and subscribe to AIS services. See Advanced Insight Solutions Overview. See Installing and Understanding AI-Scripts. See Juniper Networks J-Care Technical Services and AIS Functionality. See Figure 2.
Figure 2: AIS Direct-Customer Engagement Model
The Juniper Networks partner installs AIM, with the Partner Controller license, to manage multiple end customers. The partner's AIM is used as an aggregation point for incidents from many customers. Each end customer installs AIM in their network. The end customers run AIM in the same way as it is run in the Direct Customer AIS engagement model, except instead of connecting directly to JSS, they connect to the Partner Controller AIM installation. The partner has the option of submitting cases on behalf of their end customers or handling them without engaging with JSS. All connections are through authenticated and encrypted protocols. Secure file transfers occur between the AIM end customer and partner installations. An HTTPS connection is made from the end customer AIM installation and the partner controller installation, as well as from the partner controller AIM installation and JSS. See Advanced Insight Solutions Overview. See Installing and Understanding AI-Scripts. See Juniper Networks J-Care Technical Services and AIS Functionality. See Figure 3.
Figure 3: AIS Partner-Deployed Engagement Model
AIM is installed on each end user’s network and accessed remotely by the partner through a Web client. There is no AIM at the partner location. Each end user’s AIM communicates directly with JSS. The partner can choose to administer each end user’s AIM individually or allow each end user to administer their own AIM. If the end user sends a case request to JSS (for example, if the end user has administrative privileges to their own AIM), the partner can view information by remotely logging in to an end user’s AIM. A firewall hole or tunnel between the end-customer AIM and JSS is necessary. The partner also needs access to the end-customer AIM. All connections are through authenticated and encrypted protocols. See Figure 4.
Figure 4: Partner End-Customer-Deployed Customer/Partner Engagement Model
(Optional) AIM integrates with the JUNOScope 9.0 or later software through an API to automatically install AI-Script installation package to multiple devices. JUNOScope is an element management tool, used to support devices on the network. The customer can import devices managed by JUNOScope using AIM JUNOScope settings, then specify on which devices to install AI-Script install packages through AIM Organizations settings. If AIM and JUNOScope are run on the same server, it is recommended that JUNOScope be installed before installing AIM.
