Distributed Edition

General

1. When I login, why "No Data Available" is shown?

   Check for the following reasons:
   Click on the current date in the Calendar. If data is displayed, then there could be some time difference between Central and Probe.
   If both Central and Probe are in different time zones, then you need to choose the appropriate time using Calendar.

2. Data collection is not happening?

   The possible reasons could be:
   The Central unable to contact Probe or the Probe status is down.

   a. If the Central is unable to contact Probe,

   1. The Probe added may not be of Distributed Servertype.
   2. The username and password configured for respective Probe may not have Administrative privilege.

    

   b. If the Probe status is down, check for the following conditions:

   1. Is the Probe running? Is the Port and Protocolinformation configured correct?
   2. Is the Central needs to pass through Proxy Server? If so, is the same has been configured?
   3. Are the Ports required areopened/allowed in Firewall(s)?

    

3. When Alert count is clicked, "Security Statistics" page is shown with "No Data Available" message?
   The possible reasons are listed below:
   

   • Time difference between Central and Probe.
   • All report page are fetched from Probe directly, but the generated alerts are fetched from Central. The generated alerts from all Probe are synchronized periodically (at 5 minutes interval). This could be the case where the generated alerts are yet to be synchronized.
   • If you have converted a standalone Firewall Analyzer installation to Probe, previously generated alerts will not be synchronized. Only new alerts will be synchronized

Probe Synchronization

1. After installing Probe, unable to start it. It says "Distributed Edition: Problem encountered while registering with Central."?
   This happens when Probe fails to establish contact with Central.
   The conditions under which communication could fail are listed below:

   • Central is not running in configured machine at given port.
   • Probe needs to pass through Proxy Server and it has not been configured. In case configured, check if values are valid.
   • Appropriate ports (8500 - default web server port), (8763 - default HTTPS port) are not opened in Firewall(s).
   • Build mismatch between Central and Probe.
2. Installed both Central and Probes, but when I login into Central, I see Collector Settings page only. Why?
   • This could be because the data collection for all the Probes added in the Central are yet to happen. By default, the data collection for aProbe is scheduled every 5 minutes.
   • No device/resource exists in Probe.
3. In Central, the status of the Probe is shown as "Down", even though I am able to view reports for devices in it?
   The status update of the Probe is performed at the end of every data collection cycle which is scheduled for every 5 minutes.

Secured Communication Mode (HTTPS)

1. What is the mode of communication between Central and Probe?
   By default, the mode of communication is through HTTP. There is also an option to convert it to secured mode of communication HTTPS. Refer the procedure in the below help link, to setup secure communication mode between Central and Probe.
2. I have changed the Probe communication mode to HTTPS, after installation. How to update this info in Central?
   Click on Settings tab > Collector Settings link in Central UI and click on the Editicon of specific Collector and select the appropriate protocol and configure the web server port details.