| Description | This article describes show N/A result at the get system status CLI command during below situations. |
| Scope | FortiPortal. |
| Solution |
Below is the scenario:
Scenario 1: After the FortiPortal scalable cluster is rebooted, it will take some time to make the FortiPortal scalable cluster online and sync first; otherwise, all FortiPortal members will show N/A at the get system status CLI command. Refer to the error image.
After all FortiPortal members reboot, all FortiPortal members will take roughly 30 minutes; after that, all FortiPortal members will show correct information at the get system status CLI command. Refer to the correct image.
Scenario 2: If the FortiPortal scalable cluster is unable to access the Internet to verify license information, all FortiPortal members will show N/A at the get system status CLI command. Refer to the error image.
After all FortiPortal members can access the Internet and have done license verification, all FortiPortal members will show correct information at the get system status CLI command. Refer to the correct image.
Scenario 3: If FortiPortal members are having issues forming a scalable cluster, all FortiPortal members will show N/A at the get system status CLI command. Refer to the error image.
After FortiPortal members can form a scalable cluster, all FortiPortal members will show N/A at the get system status CLI command. Refer to the correct image.
Error image:
Correct image:
|
