- play_arrow What's New for Administrators
- play_arrow Overview of JSA Administration
- play_arrow User Management
- play_arrow License Management
- play_arrow JSA Set Up Tasks
- JSA Set Up Tasks
- Network Hierarchy
- Automatic Updates
- Manual Updates
- Configuring System settings
- IF-MAP Server Certificates
- SSL Certificates
- IPv6 Addressing in JSA Deployments
- Advanced Iptables Rules Examples
- Data Retention
- System Notifications
- Custom Offense Close Reasons
- Configuring a Custom Asset Property
- Index Management
- Restrictions to Prevent Resource-intensive Searches
- App Hosts
- Checking the Integrity Of Event and Flow Logs
- Adding Custom Actions
- Managing Aggregated Data Views
- Accessing a GLOBALVIEW Database
- play_arrow Event Data Processing in JSA
- Event Data Processing in JSA
- DSM Editor Overview
- Properties in the DSM Editor
- Property Configuration in the DSM Editor
- Opening the DSM Editor
- Configuring a Log Source Type
- Configuring Property Autodetection for Log Source Types
- Configuring Log Source Autodetection for Log Source Types
- Configuring DSM Parameters for Log Source Types
- Custom Log Source Types
- Custom Property Definitions in the DSM Editor
- Event Mapping
- Exporting Contents from the DSM Editor
- play_arrow Using Reference Data in JSA
- play_arrow User Information Source Configuration
- play_arrow Juniper Networks X-Force Integration
- play_arrow Managing Authorized Services
- play_arrow Backup and Recovery
- play_arrow Flow Sources Management
- play_arrow Remote Networks and Services Configuration
- play_arrow Server Discovery
- play_arrow Domain Segmentation
- play_arrow Multitenant Management
- Multitenant Management
- User Roles in a Multitenant Environment
- Domains and Log Sources in Multitenant Environments
- Provisioning a New Tenant
- Monitoring License Usage in Multitenant Deployments
- Rules Management in Multitenant Deployments
- Network Hierarchy Updates in a Multitenant Deployment
- Retention Policies for Tenants
- play_arrow Asset Management
- play_arrow Configuring JSA to Forward Data to Other Systems
- Forward Data to Other Systems
- Adding Forwarding Destinations
- Configuring Forwarding Profiles
- Configuring Routing Rules to Forward Data
- Using Custom Rules and Rule Responses to Forward Data
- Configuring Routing Rules to Use the JSA Data Store
- Viewing Forwarding Destinations
- Viewing and Managing Forwarding Destinations
- Viewing and Managing Routing Rules
- play_arrow Event Store and Forward
- play_arrow Security Content
- play_arrow SNMP Trap Configuration
- play_arrow Protect Sensitive Data
- play_arrow Log Files
- play_arrow Event Categories
- play_arrow Common Ports and Servers Used by JSA
- play_arrow RESTful API
Network Interface Management
In addition to the default management interface, you can add extra network interfaces to your JSA appliances to provide alternative network connectivity.
Use extra network interfaces for the following purposes:
Provide a dedicated crossover connection between high-availability (HA) peers. You configure a crossover connection during HA setup.
Provide a dedicated data collection interface for inbound events or external flow sources. TCP-based data sources must be in the same subnet as the data collection interface.
Use a regular network interface card for:
Data collection (logs/flows(NetFlow/s Flow))
Web UI
Backup/restore (not limited to iSCSI but can be NFS)
WinCollect configurations that are connected to a non-managed port are not supported.
Configuring Network Interfaces
On the navigation menu (
), click Admin.
In the System Configuration section, click System and License Management.
From the Display menu, click Systems.
Select the host for which you want to configure network interfaces.
Click Actions >View and Manage System, and click the Network Interfaces tab.
To edit a network interface, follow these steps:
Select the device that you want to edit, and click Edit.
In the Role list, select the role for the device:
Choose Regular when the device is used for:
Data collection (logs/flows(NetFlow/s Flow))
Web UI
Backup/restore (not limited to iSCSI but can be NFS)
This interface must have an IP address. The subnet of the interface cannot be the same subnet used by the management interface.
Choose Monitor when the device is a JSA Flow Processor that is used for packet collection. This interface does not require an IP address.
Choose Disabled to prevent the device from being used for any network connectivity.
To apply the configuration to the active HA node, click Apply this interface configuration and IP address to the active HA node.
This option is used only when HA is added to this system.
Click Save.