|
This command will only work on the HA controller FortiIsolator node, and in case there are multiple HA controller nodes, will work on the current main one.
To obtain the command output:
- Run the show status on the Registry FortiIsolator node via console to identify the current main HA controller FortiIsolator node:
> show
**********84753424adeb47d584f5d71fcc8fd5f8 Configured parameters**********
[IP Address]
INTERFACE IP
-------------------- --------------------
internal 10.10.10.206/24
external 10.10.20.206/24
mgmt 10.10.30.206/24
ha 10.10.40.206/24
[Routing Entries]
DESTINATION GATEWAY INTERFACE
-------------------- -------------------- --------------------
0.0.0.0/0 10.10.20.254 external
0.0.0.0/0 10.10.30.254 mgmt
Primary DNS Server : 8.8.8.8
Secondary DNS Server : 8.8.4.4
hostname : 84753424adeb47d584f5d71fcc8fd5f8
Running Mode : Run
Host Type : Registry
Host Role : worker_controller
Access Name : registry
Registry VIP : 10.10.40.206
Main Controller Node : 9bea1a0a610d4d3d8cc5f9bc91c2a32c < ---- Main contoroller hostname
Main Controller IP : 10.10.40.3 < --- Main controller HA IP address
Portal IP : 10.10.30.3
Firmware Version : v3.0.0 build0117(GA)
date time : 2025-09-05 14:30:10 UTC
- Log in to the main HA controller FortiIsolator using console and confirm its hostname:
> show
**********9bea1a0a610d4d3d8cc5f9bc91c2a32c Configured parameters**********
[IP Address]
INTERFACE IP
-------------------- --------------------
internal 10.10.10.3/24
external 10.10.20.3/24
mgmt 10.10.30.4/24
ha 10.10.40.3/24
[Routing Entries]
DESTINATION GATEWAY INTERFACE
-------------------- -------------------- --------------------
0.0.0.0/0 10.10.20.254 external
0.0.0.0/0 10.10.30.254 mgmt
Primary DNS Server : 8.8.8.8
Secondary DNS Server : 8.8.4.4
hostname : 9bea1a0a610d4d3d8cc5f9bc91c2a32c < ---- Hostname for the main FortiIsolator HA controller
Running Mode : Run
Host Type : Controller_HA
Host Role : controller
Access Name : HA-Controller-1
Registry VIP : 10.10.40.206
Main Controller Node : 9bea1a0a610d4d3d8cc5f9bc91c2a32c
Main Controller IP : 10.10.40.3
Portal IP : 10.10.30.3
Hostname Host Type Internal IP
---------------------------------------- -------------------- --------------------
9bea1a0a610d4d3d8cc5f9bc91c2a32c Controller_HA 10.10.10.3
8a9a7e9421ed4260b6181a5b99c5bc95 Controller_HA 10.10.10.207
f0d5325eebb843b6b1cc0e70f10bd692 Worker 10.10.10.5
0711b056e5cf41f1a5478c7b352b83d1 Worker 10.10.10.2
359537be5c7f4f8ebf8d3b52135072fb Worker 10.10.10.4
Firmware Version : v3.0.0 build0117(GA)
date time : 2025-09-05 14:33:39 UTC
- Run the command on the main HA controller FortiIsolator node:
> fnsysctl kubectl get pod
- Wait for one minute before collecting the results:
> fnsysctl result
fnsysctl_kubectl='get pod'
NAME READY STATUS RESTARTS AGE
fis-auth-0 1/1 Running 0 23d
fis-cli-5fdc849d89-lgl2x 1/1 Running 0 23d
fis-controller-0711b056e5cf41f1a5478c7b352b83d1-fc7d4bd88-6nx5f 1/1 Running 0 23d
fis-db-san-jose-0 1/1 Running 0 23d
fis-gui-d7c59596c-6bpkn 1/1 Running 0 23d
fis-isolator-san-jose-0 1/1 Running 572 (25m ago) 23d
fis-isolator-san-jose-1 1/1 Running 572 (25m ago) 23d
fis-isolator-san-jose-2 1/1 Running 572 (25m ago) 23d
fis-isolator-san-jose-3 1/1 Running 571 (25m ago) 23d
fis-isolator-san-jose-4 1/1 Running 571 (25m ago) 23d
fis-log-7766758ccb-8wsft 1/1 Running 0 23d
fis-office-6c6fdc5fcd-qpp6d 1/1 Running 0 23d
fis-postgres-0 1/1 Running 0 23d
fis-update-0 1/1 Running 0 23d
fis-wf-0 1/1 Running 0 23d
fis-x-j948p 1/1 Running 0 23d
fis-x-ntqw2 1/1 Running 0 23d
fis-x-r9hx5 1/1 Running 0 23d
Related documents:
Introduction
Overview
|
