Overview
The customer was unable to retrieve records for a specific IP address within a certain date range from the PRI IPLOGGER URL, despite the data being present in the backend. The root cause of the issue was that the IP address the customer was searching for was present as a Destination IP in the backend records, not as a Public IP. This discrepancy was causing the search function to fail.
Recording: Explaining the issue
Ticket: 4089952
Solution
To resolve this issue, the customer should search for the IP address as a Destination IP instead of a Public IP. Here are the steps to do so:
- Identify the IP address you are searching for in the Header
- Identify the Header.
- Check the position of the IP address in the IPL solution. If it is in the fifth position, it is a Destination IP.
- Search for the IP address as a Destination IP instead of a Public IP.
- Once you apply the correct search parameters, you should be able to successfully fetch the report for the given IP.
Summary
When fetching records from the PRI IPLOGGER URL, it's important to know whether the IP address you're searching for is a Public IP or a Destination IP. If you're unable to retrieve records, it may be because you're searching for the IP address in the wrong category. Adjusting your search parameters should resolve the issue.
FAQ
-
What is the difference between a Public IP and a Destination IP?
A Public IP is an IP address that is used to identify a network to the outside world, while a Destination IP is the IP address that a packet is sent to. -
How can I tell if an IP address is a Public IP or a Destination IP?
You can tell by checking the position of the IP address in the IPL solution. The Public IP should be in the second or third position, while the Destination IP is in the fifth position. -
What should I do if I'm still unable to fetch records after adjusting my search parameters?
If you're still unable to fetch records after adjusting your search parameters, please contact customer support for further assistance.
Comments
0 comments
Article is closed for comments.