| Design
& Plan for AIS |
|
Read the AIS documentation
|
|
|
What you need
|
Access to the following systems and information is required
to complete AIS installation:
- (Optional) Dedicated JUNOScope Linux or Solaris software
server with appropriate permissions and requirements
- (Optional) JUNOScope software installer file
- (Optional) JUNOScope URL, AIS username and password added
to JUNOScope for AIM, IP address for device-to-JUNOScope FTP connectivity,
and devices managed
- Dedicated AIM Linux or Solaris server with appropriate
permissions and requirements
- (Optional) FTP or file server for device archive locations
- NFS mounted to AIM host
- FTP login and password
- Clarify site ID and credentials
- AIM authorization codes and serial number sent by Juniper
Networks
- Juniper Networks software download site URL and credentials
- AIM installer file
- AI-Scripts bundle file
- AI-Scripts installation, configuration, and verification
(automatic or manual)
- AIM installation, set up, and verification
- Juniper License Management System (LMS) URL and credentials
- Juniper J-Care Technical Services contact information
|
|
What to install
|
- (Optional) JUNOScope 9.0 Software or later
- AI-Scripts 1.1 or later
- AIM 1.1 or later
- AIM License File
|
|
Security considerations
|
- Set up firewall rules to allow outbound traffic from the
AIM server to JSS on TCP port 443.
- The local DNS should resolve support.net and services.juniper.net.
- Determine the level of device configuration filtering
required for JMBs in archive locations. See Configuring General Settings
|
|
Determine AIS engagement model
|
- Direct-Customer AIS Engagement Model—The AIS direct
customer installs AIS software elements (AI-Scripts and AIM).
- Partner-Deployed AIS Engagement Model—The AIS Partner
installs AIM software elements (AI-Scripts and AIM) to manage multiple
users. The AIM server is used as an aggregation point for JMBs from
many customers. The partner administers the AIM server and users (customers)
have read-only access to AIM.
- Partner End-User Deployed AIS Engagement Model—AIM
is installed on each user’s network and accessed remotely by
the partner through a Web client. There is no AIM at the partner location.
Each user’s AIM communicates directly with JSS.
|
|
What organizations need AIS
|
- Customers or sites that need AIS
- Which devices are to be associated with the site ID and
Juniper credentials (to define an organization)?
- Number of, and names for, device groups
|
|
What devices need AIS
|
- Juniper Networks devices meet the AI-Scripts system requirements,
see AI-Scripts System Requirements.
- Where will the archive locations for event and intelligence
Juniper Message Bundles (JMBs) for each device be configured?
|
|
What users will use AIS
|
List the AIM users, including:
- Needed permissions
- Needed user groups
- Associations with device groups
- Initial reaction policies
- Initial alert registrations
|
