Checking the cluster status

You can use the following get and diagnose commands to show the status of the cluster and all of the devices in it.

1. Log into the primary FortiController CLI and enter the following command to view the system status of the primary FortiController.

   get system status
   Version: FortiController-5103B v5.0,build0024,140815
   Branch Point: 0024
   Serial-Number: FT513B3912000029
   BIOS version: 04000009
   System Part-Number: P08442-04
   Hostname: ch1-slot1
   Current HA mode: a-p, master
   System time: Sun Sep 14 08:16:25 2014
   Daylight Time Saving: Yes
   Time Zone: (GMT-8:00)Pacific Time(US&Canada)

2. Enter the following command to view the load balance status of the primary FortiController and its workers. The command output shows the workers in slots 3, 4, and 5, and status information about each one.

   get load-balance status
     ELBC Master Blade: slot-3
     Confsync Master Blade: slot-3
     Blades:
      Working: 3 [ 3 Active 0 Standby]
      Ready:   0 [ 0 Active 0 Standby
      Dead:    0 [ 0 Active 0 Standby]
     Total:    3 [ 3 Active 0 Standby]
   
      Slot 3: Status:Working   Function:Active
        Link:     Base: Up          Fabric: Up
        Heartbeat: Management: Good   Data: Good
        Status Message:"Running"
      Slot 4: Status:Working   Function:Active
        Link:     Base: Up          Fabric: Up
        Heartbeat: Management: Good  Data: Good
        Status Message:"Running"
      Slot 5: Status:Working   Function:Active
        Link:     Base: Up          Fabric: Up
        Heartbeat: Management: Good   Data: Good
        Status Message:"Running"

3. Enter the following command from the primary FortiController to show the HA status of the FortiControllers.

   The command output shows a lot of information about the cluster including the host names and chassis and slot locations of the FortiControllers, the number of sessions each FortiController is processing (in this case 0 for each FortiController) the number of failed workers (0 of 3 for each FortiController), the number of FortiController front panel interfaces that are connected (2 for each FortiController) and so on. The final two lines of output also show that the B1 interfaces are connected (status=alive) and the B2 interfaces are not (status=dead). The cluster can still operate with a single heartbeat connection, but redundant heartbeat interfaces are recommended.

   diagnose system ha status
   mode: a-p
   minimize chassis failover: 1
   ch1-slot1(FT513B3912000029), Master(priority=0), ip=169.254.128.121, uptime=4416.18, chassis=1(1)
        slot: 1
        sync: conf_sync=1, elbc_sync=1
        session: total=0,  session_sync=in sync
        state: worker_failure=0/3, intf_state=(port up:)=0
     force-state(0:none)    hbdevs: local_interface=        b1 best=yes
                local_interface=        b2 best=no
   
   ch2-slot1(FT513B3912000051), Slave(priority=2), ip=169.254.128.123, uptime=1181.62, chassis=2(1)
       slot: 1
       sync: conf_sync=1, elbc_sync=1, conn=3(connected)
       session: total=0,  session_sync=in sync
       state: worker_failure=0/3, intf_state=(port up:)=0
    force-state(0:none)    hbdevs: local_interface=        b1 last_hb_time= 4739.97   status=alive
               local_interface=        b2 last_hb_time=    0.00   status=dead
   
   ch2-slot2(FT513B3913000168), Slave(priority=3), ip=169.254.128.124, uptime=335.79, chassis=2(1)
       slot: 2
       sync: conf_sync=1, elbc_sync=1, conn=3(connected)
       session: total=0,  session_sync=in sync
       state: worker_failure=0/3, intf_state=(port up:)=0
    force-state(0:none)    hbdevs: local_interface=        b1 last_hb_time= 4739.93   status=alive
               local_interface=        b2 last_hb_time=    0.00   status=dead
   
   ch1-slot2(FT513B3914000006), Slave(priority=1), ip=169.254.128.122, uptime=4044.46, chassis=1(1)
       slot: 2
       sync: conf_sync=1, elbc_sync=1, conn=3(connected)
       session: total=0,  session_sync=in sync
       state: worker_failure=0/3, intf_state=(port up:)=0
    force-state(0:none)    hbdevs: local_interface=        b1 last_hb_time= 4740.03   status=alive
               local_interface=        b2 last_hb_time=    0.00   status=dead

4. Log into the chassis 1 slot 2 FortiController CLI and enter this command to view the status of this secondary FortiController.

   To log in with SSH: ssh admin@172.20.120.100 -p2202

   get system status
   Version: FortiController-5103B v5.0,build0024,140815
   Branch Point: 0024
   Serial-Number: FT513B3914000006
   BIOS version: 04000010
   System Part-Number: P08442-04
   Hostname: ch1-slot2
   Current HA mode: a-p, backup
   System time: Sun Sep 14 12:44:58 2014
   Daylight Time Saving: Yes
   Time Zone: (GMT-8:00)Pacific Time(US&Canada)

5. Enter the following command to view the status of this secondary FortiController and its workers.

   get load-balance status
   ELBC Master Blade: slot-3
     Confsync Master Blade: slot-3
     Blades:
        Working:  3 [  3 Active  0 Standby]
        Ready:    0 [ 0 Active 0 Standby]
        Dead:     0 [  0 Active  0 Standby]
       Total:     3 [  3 Active  0 Standby]
   
        Slot  3: Status:Working   Function:Active
          Link:      Base: Up          Fabric: Up
          Heartbeat: Management: Good   Data: Good
          Status Message:"Running"
        Slot  4: Status:Working   Function:Active
          Link:      Base: Up          Fabric: Up
          Heartbeat: Management: Good   Data: Good
          Status Message:"Running"
        Slot  5: Status:Working   Function:Active
          Link:      Base: Up          Fabric: Up
          Heartbeat: Management: Good   Data: Good
          Status Message:"Running"

6. Enter the following command from the FortiController in chassis 1 slot 2 to show the HA status of the FortiControllers. Notice that the FortiController in chassis 1 slot 2 is shown first.

   diagnose system ha status
   mode: a-p
   minimize chassis failover: 1
   ch1-slot2(FT513B3914000006), Slave(priority=1), ip=169.254.128.122, uptime=4292.69, chassis=1(1)
       slot: 2
       sync: conf_sync=1, elbc_sync=1
       session: total=0,  session_sync=in sync
       state: worker_failure=0/3, intf_state=(port up:)=0
   force-state(0:none)    hbdevs: local_interface=        b1 best=yes
               local_interface=        b2 best=no
   
   ch1-slot1(FT513B3912000029), Master(priority=0), ip=169.254.128.121, uptime=4664.49, chassis=1(1)
       slot: 1
       sync: conf_sync=1, elbc_sync=1, conn=3(connected)
       session: total=0,  session_sync=in sync
       state: worker_failure=0/3, intf_state=(port up:)=0
    force-state(0:none)    hbdevs: local_interface=        b1 last_hb_time= 4958.88   status=alive
               local_interface=        b2 last_hb_time=    0.00   status=dead
           
           ch2-slot1(FT513B3912000051), Slave(priority=2), ip=169.254.128.123, uptime=1429.99, chassis=2(1)
       slot: 1
       sync: conf_sync=1, elbc_sync=1, conn=3(connected)
       session: total=0,  session_sync=in sync
       state: worker_failure=0/3, intf_state=(port up:)=0
    force-state(0:none)    hbdevs: local_interface=        b1 last_hb_time= 4958.88   status=alive
               local_interface=        b2 last_hb_time=    0.00   status=dead
           
   ch2-slot2(FT513B3913000168), Slave(priority=3), ip=169.254.128.124, uptime=584.20, chassis=2(1)
       slot: 2
       sync: conf_sync=1, elbc_sync=1, conn=3(connected)
       session: total=0,  session_sync=in sync
       state: worker_failure=0/3, intf_state=(port up:)=0
    force-state(0:none)    hbdevs: local_interface=        b1 last_hb_time= 4958.88   status=alive
               local_interface=        b2 last_hb_time=    0.00   status=dead
           

7. Log into the chassis 2 slot 1 FortiController CLI and enter the following command to view the status of this secondary FortiController.

   To log in with SSH: ssh admin@172.20.120.100 -p2221

   get system status
   Version: FortiController-5103B v5.0,build0024,140815
   Branch Point: 0024
   Serial-Number: FT513B3912000051
   BIOS version: 04000009
   System Part-Number: P08442-04
   Hostname: ch2-slot1
   Current HA mode: a-p, backup
   System time: Sun Sep 14 12:53:09 2014
   Daylight Time Saving: Yes
   Time Zone: (GMT-8:00)Pacific Time(US&Canada)

8. Enter the following command to view the status of this secondary FortiController and its workers.

   get load-balance status
     ELBC Master Blade: slot-3
     Confsync Master Blade: N/A
     Blades:
        Working:  3 [  3 Active  0 Standby]
        Ready:    0 [  0 Active  0 Standby]
        Dead:     0 [  0 Active  0 Standby]
       Total:     3 [  3 Active  0 Standby]
   
        Slot  3: Status:Working   Function:Active
         Link:      Base: Up           Fabric: Up
          Heartbeat: Management: Good   Data: Good
          Status Message:"Running"
   
        Slot  4: Status:Working   Function:Active
          Link:      Base: Up          Fabric: Up
          Heartbeat: Management: Good   Data: Good
          Status Message:"Running"
   
        Slot  5: Status:Working    Function:Active
          Link:      Base: Up          Fabric: Up
          Heartbeat: Management: Good   Data: Good
          Status Message:"Running"

9. Enter the following command from the FortiController in chassis 2 slot 1 to show the HA status of the FortiControllers. Notice that the FortiController in chassis 2 slot 1 is shown first.

   diagnose system ha status
   mode: a-p
   minimize chassis failover: 1
   ch2-slot1(FT513B3912000051), Slave(priority=2), ip=169.254.128.123, uptime=1858.71, chassis=2(1)
       slot: 1
       sync: conf_sync=1, elbc_sync=1
       session: total=0,  session_sync=in sync
       state: worker_failure=0/3, intf_state=(port up:)=0
    force-state(0:none)    hbdevs: local_interface=        b1 best=yes
               local_interface=        b2 best=no
   
   ch1-slot1(FT513B3912000029), Master(priority=0), ip=169.254.128.121, uptime=5093.30, chassis=1(1)
       slot: 1
       sync: conf_sync=1, elbc_sync=1, conn=3(connected)
       session: total=0,  session_sync=in sync
       state: worker_failure=0/3, intf_state=(port up:)=0
    force-state(0:none)    hbdevs: local_interface=        b1 last_hb_time= 2074.15   status=alive
               local_interface=        b2 last_hb_time=    0.00   status=dead
   
   ch2-slot2(FT513B3913000168), Slave(priority=3), ip=169.254.128.124, uptime=1013.01, chassis=2(1)
       slot: 2
       sync: conf_sync=1, elbc_sync=1, conn=3(connected)
       session: total=0,  session_sync=in sync
       state: worker_failure=0/3, intf_state=(port up:)=0
    force-state(0:none)    hbdevs: local_interface=        b1 last_hb_time= 2074.15   status=alive
               local_interface=        b2 last_hb_time=    0.00   status=dead
   
   ch1-slot2(FT513B3914000006), Slave(priority=1), ip=169.254.128.122, uptime=4721.60, chassis=1(1)
       slot: 2
       sync: conf_sync=1, elbc_sync=1, conn=3(connected)
       session: total=0,  session_sync=in sync
       state: worker_failure=0/3, intf_state=(port up:)=0
    force-state(0:none)    hbdevs: local_interface=        b1 last_hb_time= 2074.17   status=alive
               local_interface=        b2 last_hb_time=    0.00   status=dead

10. Log into the chassis 2 slot 2 FortiController CLI and enter the following command to view the status of this secondary FortiController.

    To log in with SSH: ssh admin@172.20.120.100 -p2222

    get system status
    Version: FortiController-5103B v5.0,build0024,140815
    Branch Point: 0024
    Serial-Number: FT513B3913000168
    BIOS version: 04000010
    System Part-Number: P08442-04
    Hostname: ch2-slot2
    Current HA mode: a-p, secondary
    System time: Sun Sep 14 12:56:45 2014
    Daylight Time Saving: Yes
    Time Zone: (GMT-8:00)Pacific Time(US&Canada)

11. Enter the following command to view the status of the secondary FortiController and its workers.

    get load-balance status
      ELBC Master Blade: slot-3
      Confsync Master Blade: N/A
      Blades:
         Working:  3 [  3 Active  0 Standby]
         Ready:    0 [  0 Active  0 Standby]
         Dead:     0 [  0 Active  0 Standby]
        Total:     3 [  3 Active  0 Standby]
    
         Slot  3: Status:Working   Function:Active
           Link:      Base: Up           Fabric: Up
           Heartbeat: Management: Good   Data: Good
           Status Message:"Running"
    
         Slot  4: Status:Working   Function:Active
           Link:      Base: Up           Fabric: Up
           Heartbeat: Management: Good   Data: Good
           Status Message:"Running"
    
         Slot  5: Status:Working   Function:Active
           Link:      Base: Up          Fabric: Up
           Heartbeat: Management: Good   Data: Good
           Status Message:"Running"

12. Enter the following command from the FortiController in chassis 2 slot 2 to show the HA status of the FortiControllers. Notice that the FortiController in chassis 2 slot 2 is shown first.

    diagnose system ha status
     mode: a-p
     minimize chassis failover: 1
     ch2-slot2(FT513B3913000168), Slave(priority=3), ip=169.254.128.124, uptime=1276.77, chassis=2(1)
         slot: 2
         sync: conf_sync=1, elbc_sync=1
         session: total=0,  session_sync=in sync
         state: worker_failure=0/3, intf_state=(port up:)=0
      force-state(0:none)    hbdevs: local_interface=        b1 best=yes
                 local_interface=        b2 best=no
    
    ch1-slot1(FT513B3912000029), Master(priority=0), ip=169.254.128.121, uptime=5356.98, chassis=1(1)
         slot: 1
         sync: conf_sync=1, elbc_sync=1, conn=3(connected)
         session: total=0,  session_sync=in sync
         state: worker_failure=0/3, intf_state=(port up:)=0
      force-state(0:none)    hbdevs: local_interface=        b1 last_hb_time= 1363.89   status=alive
                 local_interface=        b2 last_hb_time=    0.00   status=dead
    
    ch2-slot1(FT513B3912000051), Slave(priority=2), ip=169.254.128.123, uptime=2122.58, chassis=2(1)
         slot: 
         sync: conf_sync=1, elbc_sync=1, conn=3(connected)
         session: total=0,  session_sync=in sync
         state: worker_failure=0/3, intf_state=(port up:)=0
      force-state(0:none)    hbdevs: local_interface=        b1 last_hb_time= 1363.97   status=alive
                 local_interface=        b2 last_hb_time=    0.00   status=dead
    
    ch1-slot2(FT513B3914000006), Slave(priority=1), ip=169.254.128.122, uptime=4985.27, chassis=1(1)
         slot: 2
         sync: conf_sync=1, elbc_sync=1, conn=3(connected)
         session: total=0,  session_sync=in sync
         state: worker_failure=0/3, intf_state=(port up:)=0
      force-state(0:none)    hbdevs: local_interface=        b1 last_hb_time= 1363.89   status=alive
                 local_interface=        b2 last_hb_time=    0.00   status=dead