- play_arrow What's New for Administrators
- play_arrow Overview of JSA Administration
- play_arrow User Management
- play_arrow License Management
- play_arrow System Management
- System Management
- System Health Information
- JSA Component Types
- Data Nodes
- Network Interface Management
- JSA System Time
- NAT-Enabled Networks
- Off-site Hosts Management
- Managed Hosts
- Configuration Changes in your JSA Environment
- Deploying Changes
- Restarting the Event Collection Service
- Shutting Down a System
- Restarting a System
- Collecting Log Files
- Changing the Root Password on Your JSA Console
- Resetting SIM
- 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 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
Flow Source Aliases Management
A flow source alias uses a virtual name to identify external flows that are sent to the same port on a flow processor. For example, the JSA Flow Processor can have a single NetFlow flow source that is listening on port 2055, and can have multiple NetFlow sources sending to the same JSA Flow Processor. By using flow source aliases, you can identify the different NetFlow sources based by their IP addresses.
When JSA Flow Processor receives traffic from a device that has an IP address but does not have a current alias, the JSA Flow Processor attempts a reverse DNS lookup. The lookup is used to determine the host name of the device.
You can configure the JSA Flow Processor to automatically create flow source aliases. When the JSA Flow Processor receives traffic from a device that has an IP address but does not have a current alias, it does a reverse DNS lookup to determine the host name of the device.
If the lookup is successful, the JSA Flow Processor adds this information to the database and reports the information to all JSA Flow Processor components in your deployment. If the lookup fails, JSA creates a default alias for the flow source based on the flow source name and the source IP address. For example, the default alias might appear as default_NetFlow_172.16.10.139.
Adding or a Flow Source Alias
Use the Flow Source Alias window to add a flow source alias.
On the navigation menu (
), click Admin.
In the Data Sources section, under Flows, click Flow Source Aliases.
Do one of the following actions:
To add a flow source alias, click Add and enter the values for the parameters.
To edit an existing flow source alias, select the flow source alias, click Edit, and update the parameters.
Click Save.
On the Admin tab, click Deploy Changes.
Note:If you rename a flow source alias, you must use the original name to perform a historical search.
Deleting a Flow Source Alias
Use the Flow Source Alias window to delete a flow source alias.
On the navigation menu (
), click Admin.
In the Data Sources section, under Flows, click Flow Source Aliases.
Select the flow source alias that you want to delete, and then click Delete.
On the Admin tab, click Deploy Changes.