Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Announcement: Try the Ask AI chatbot for answers to your technical questions about Juniper products and solutions.

close
header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Overlapping IP Addresses

date_range 27-Mar-21

An overlapping IP address is an IP address that is assigned to more than one device or logical unit, such as an event source type, on a network. Overlapping IP address ranges can cause significant problems for companies that merge networks after corporate acquisitions, or for Managed Security Service Providers (MSSPs) who are bringing on new clients.

JSA must be able to differentiate events and flows that come from different devices and that have the same IP address. If the same IP address is assigned to more than one event source, you can create domains to distinguish them.

For example, let's look at a situation where Company A acquires Company B and wants to use a shared instance of JSA to monitor the new company's assets. The acquisition has a similar network structure that results in the same IP address being used for different log sources in each company. Log sources that have the same IP address cause problems with correlation, reporting, searching, and asset profiling.

To distinguish the origin of the events and flows that come in to JSA from the log source, you can create two domains and assign each log source to a different domain. If required, you can also assign each event collector and flow processor to the same domain as the log source that sends events to them.

To distinguish the origin of the events and flows that come in to JSA from the log source, you can create two domains and assign each log source to a different domain. If required, you can also assign each event collector, flow processor, or data gateway to the same domain as the log source that sends events to them.

To view the incoming events by domain, create a search and include the domain information in the search results.

footer-navigation