This website uses cookies essential to its operation, for analytics, and for personalized content. By continuing to browse this site, you acknowledge the use of cookies. For details on cookie usage on our site, read our Privacy Policy
An additional confirmation. We failed our HA pair back where Primary IP & Serial match Expedition primary and logs are processing correctly.
... View more
The difference between the first time and second time is which firewall in the HA pair is active vs configuration in Expedition. If the firewall configured as primary in Expedition generated the logs then everything works as expected. However, if the logs were generated by the device in HA Serial # field, then logs are process but listed as unprocessed.
Logs already processed but still listed as new
... View more
More detail for this issue. A fresh Expedition VM was built using New Expedition Installation Procedure.
Added Device to Expedition using Active IP & Serial. CSV's processed correctly and shows as processed.
Deleted Device in Expedition and Deleted Connections.parquet FILES.
Added Device to Expedition using Passive IP & Serial + HA Serial (currently active). CSV's are processed but still show as pending in UI
Looking in the pandbRBAC.device_logs table the logs are listed as processed with the HA Serial. It seems the logic is not working correctly to flag logs sent from the HA Serial as processed.
... View more
After upgrading to Expedition 1.1.50 Devices show CSV Pending after log processing completes successfully. Additionally, Apache Spark URL does not appear on the M. Learning tab Processing status bar when Spark is processing the CSV. Also the grey message bar always displays: The '/PALogs/NTXIRT00-IG0?-H_traffic_*' cannot be accessed. '
Finally, Once log processing completes the Traffic tab displays traffic for the log that was imported however Devices shows the CSV is still pending
.
... View more