Version:


Table of Contents

7.2.0
Download PDF
Copy Link

Appendix B - Troubleshooting

Confirming a member has joined the Fabric

When adding a new member, check that the member has joined the Fabric.

To confirm that a member has joined the Fabric:
  1. In the FortiAnalyzer Fabric supervisor CLI, enter the following command:

    diagnose test application fazsvcd 76 nodes

    This diagnostic shows all of the current members on the supervisor or on the member. Ensure that the Status for each member is up.

Member unable to join the Fabric

If the member does not join the Fabric, possible issues include:

  • Incorrect supervisor IP
  • Incorrect PSK
  • Encryption setting mismatch between supervisor/member
  • Incorrect Fabric name
  • The supervisor allowaccess setting described above does not include the soc-fabric setting
  • The supervisor is not reachable by the member, use ping to confirm
  • The supervisor/member is not running

The supervisor uses a mixture of synchronized data and data retrieved directly from the member. This data is retrieved through the Fabric from the JSONAPI service running on the member, so it is possible to view cached alert information while the member is not actually running.

Server error: Fabric member not available

Problem: When selecting an alert, the supervisor displays Server Error: Fabric member xxx is not available.

Description: The supervisor is not able to contact the member through the Fabric.

To troubleshoot a server error:
  1. Ensure that the member has booted and is running.
  2. Ensure that the member has connected to the Fabric using the following CLI command:

    diagnose test application fazsvcd 76 nodes

JSONAPI service reports error

Problem: When selecting an alert, the supervisor displays JSONAPI Service reports: <error message>.

Description: The member has joined the Fabric, but the JSONAPI service of the member cannot service the request.

To troubleshoot a JSON API service reports error:
  1. Ensure that the member has completely booted up.
  2. Determine if the member is performing some type of database rebuild which may prevent service availability.
  3. Access the members’ GUI to determine if it can use its own JSONAPI service.

Appendix B - Troubleshooting

Confirming a member has joined the Fabric

When adding a new member, check that the member has joined the Fabric.

To confirm that a member has joined the Fabric:
  1. In the FortiAnalyzer Fabric supervisor CLI, enter the following command:

    diagnose test application fazsvcd 76 nodes

    This diagnostic shows all of the current members on the supervisor or on the member. Ensure that the Status for each member is up.

Member unable to join the Fabric

If the member does not join the Fabric, possible issues include:

  • Incorrect supervisor IP
  • Incorrect PSK
  • Encryption setting mismatch between supervisor/member
  • Incorrect Fabric name
  • The supervisor allowaccess setting described above does not include the soc-fabric setting
  • The supervisor is not reachable by the member, use ping to confirm
  • The supervisor/member is not running

The supervisor uses a mixture of synchronized data and data retrieved directly from the member. This data is retrieved through the Fabric from the JSONAPI service running on the member, so it is possible to view cached alert information while the member is not actually running.

Server error: Fabric member not available

Problem: When selecting an alert, the supervisor displays Server Error: Fabric member xxx is not available.

Description: The supervisor is not able to contact the member through the Fabric.

To troubleshoot a server error:
  1. Ensure that the member has booted and is running.
  2. Ensure that the member has connected to the Fabric using the following CLI command:

    diagnose test application fazsvcd 76 nodes

JSONAPI service reports error

Problem: When selecting an alert, the supervisor displays JSONAPI Service reports: <error message>.

Description: The member has joined the Fabric, but the JSONAPI service of the member cannot service the request.

To troubleshoot a JSON API service reports error:
  1. Ensure that the member has completely booted up.
  2. Determine if the member is performing some type of database rebuild which may prevent service availability.
  3. Access the members’ GUI to determine if it can use its own JSONAPI service.