Fortinet Document Library

Version:

Version:


Table of Contents

Administration Guide

Download PDF
Copy Link

Querying autoscale clusters for FortiGate VM

When a FortiGate VM secondary device is added to a cluster, the new secondary member can query the cluster about its autoscale environment. FortiManager can then run this query on the new secondary member to update its autoscale record.

To view cluster information from a secondary member:

# diagnose sys ha checksum autoscale-cluster

Cluster information sample

Sample cloud topology:

FGT_BYOL; primary; 10.0.0.6; FGVM04TM00000066

FGT_BYOL; secondary; 10.0.0.7; FGVM00000000056

FGT_PAYG; secondary; 10.0.0.4; FGTAZ000000000CD

FGT_PAYG; secondary; 10.0.0.5; FGTAZ0000000003D

From the secondary device, you can see cluster checksums and the primary device:

# diagnose sys ha checksum autoscale-cluster

================== FGTAZ000000000CD ==================

is_autoscale_master()=0

debugzone

global: 56 49 b3 02 f2 b7 5b 82 ec 2d c2 1a ff 80 8c 79

root: bf 18 cf 83 1e 04 c3 04 4c e4 66 bc 38 fe 3a dc

all: 77 06 d0 89 6e 06 c0 86 17 98 53 72 33 85 ae ff

checksum

global: 56 49 b3 02 f2 b7 5b 82 ec 2d c2 1a ff 80 8c 79

root: bf 18 cf 83 1e 04 c3 04 4c e4 66 bc 38 fe 3a dc

all: 77 06 d0 89 6e 06 c0 86 17 98 53 72 33 85 ae ff

================== FGVM04TM00000066 ==================

is_autoscale_master()=1

debugzone

global: 56 49 b3 02 f2 b7 5b 82 ec 2d c2 1a ff 80 8c 79

root: bf 18 cf 83 1e 04 c3 04 4c e4 66 bc 38 fe 3a dc

all: 77 06 d0 89 6e 06 c0 86 17 98 53 72 33 85 ae ff

checksum

global: 56 49 b3 02 f2 b7 5b 82 ec 2d c2 1a ff 80 8c 79

root: bf 18 cf 83 1e 04 c3 04 4c e4 66 bc 38 fe 3a dc

all: 77 06 d0 89 6e 06 c0 86 17 98 53 72 33 85 ae ff

================== FGVM00000000056 ==================

is_autoscale_master()=0

debugzone

global: 56 49 b3 02 f2 b7 5b 82 ec 2d c2 1a ff 80 8c 79

root: bf 18 cf 83 1e 04 c3 04 4c e4 66 bc 38 fe 3a dc

all: 77 06 d0 89 6e 06 c0 86 17 98 53 72 33 85 ae ff

checksum

global: 56 49 b3 02 f2 b7 5b 82 ec 2d c2 1a ff 80 8c 79

root: bf 18 cf 83 1e 04 c3 04 4c e4 66 bc 38 fe 3a dc

all: 77 06 d0 89 6e 06 c0 86 17 98 53 72 33 85 ae ff

================== FGTAZ0000000003D ==================

is_autoscale_master()=0

debugzone

global: 56 49 b3 02 f2 b7 5b 82 ec 2d c2 1a ff 80 8c 79

root: bf 18 cf 83 1e 04 c3 04 4c e4 66 bc 38 fe 3a dc

all: 77 06 d0 89 6e 06 c0 86 17 98 53 72 33 85 ae ff

checksum

global: 56 49 b3 02 f2 b7 5b 82 ec 2d c2 1a ff 80 8c 79

root: bf 18 cf 83 1e 04 c3 04 4c e4 66 bc 38 fe 3a dc

all: 77 06 d0 89 6e 06 c0 86 17 98 53 72 33 85 ae ff

To get ha sync information from the secondary device:
# get test hasync 50
autoscale_count=69. current_jiffies=41235125
    10.0.0.6, timeo=31430, serial_no=FGVM04TM19001766
    10.0.0.7, timeo=31430, serial_no=FGVM04TM19008156
    10.0.0.5, timeo=31430, serial_no=FGTAZR7UZRKKNR3D

Querying autoscale clusters for FortiGate VM

When a FortiGate VM secondary device is added to a cluster, the new secondary member can query the cluster about its autoscale environment. FortiManager can then run this query on the new secondary member to update its autoscale record.

To view cluster information from a secondary member:

# diagnose sys ha checksum autoscale-cluster

Cluster information sample

Sample cloud topology:

FGT_BYOL; primary; 10.0.0.6; FGVM04TM00000066

FGT_BYOL; secondary; 10.0.0.7; FGVM00000000056

FGT_PAYG; secondary; 10.0.0.4; FGTAZ000000000CD

FGT_PAYG; secondary; 10.0.0.5; FGTAZ0000000003D

From the secondary device, you can see cluster checksums and the primary device:

# diagnose sys ha checksum autoscale-cluster

================== FGTAZ000000000CD ==================

is_autoscale_master()=0

debugzone

global: 56 49 b3 02 f2 b7 5b 82 ec 2d c2 1a ff 80 8c 79

root: bf 18 cf 83 1e 04 c3 04 4c e4 66 bc 38 fe 3a dc

all: 77 06 d0 89 6e 06 c0 86 17 98 53 72 33 85 ae ff

checksum

global: 56 49 b3 02 f2 b7 5b 82 ec 2d c2 1a ff 80 8c 79

root: bf 18 cf 83 1e 04 c3 04 4c e4 66 bc 38 fe 3a dc

all: 77 06 d0 89 6e 06 c0 86 17 98 53 72 33 85 ae ff

================== FGVM04TM00000066 ==================

is_autoscale_master()=1

debugzone

global: 56 49 b3 02 f2 b7 5b 82 ec 2d c2 1a ff 80 8c 79

root: bf 18 cf 83 1e 04 c3 04 4c e4 66 bc 38 fe 3a dc

all: 77 06 d0 89 6e 06 c0 86 17 98 53 72 33 85 ae ff

checksum

global: 56 49 b3 02 f2 b7 5b 82 ec 2d c2 1a ff 80 8c 79

root: bf 18 cf 83 1e 04 c3 04 4c e4 66 bc 38 fe 3a dc

all: 77 06 d0 89 6e 06 c0 86 17 98 53 72 33 85 ae ff

================== FGVM00000000056 ==================

is_autoscale_master()=0

debugzone

global: 56 49 b3 02 f2 b7 5b 82 ec 2d c2 1a ff 80 8c 79

root: bf 18 cf 83 1e 04 c3 04 4c e4 66 bc 38 fe 3a dc

all: 77 06 d0 89 6e 06 c0 86 17 98 53 72 33 85 ae ff

checksum

global: 56 49 b3 02 f2 b7 5b 82 ec 2d c2 1a ff 80 8c 79

root: bf 18 cf 83 1e 04 c3 04 4c e4 66 bc 38 fe 3a dc

all: 77 06 d0 89 6e 06 c0 86 17 98 53 72 33 85 ae ff

================== FGTAZ0000000003D ==================

is_autoscale_master()=0

debugzone

global: 56 49 b3 02 f2 b7 5b 82 ec 2d c2 1a ff 80 8c 79

root: bf 18 cf 83 1e 04 c3 04 4c e4 66 bc 38 fe 3a dc

all: 77 06 d0 89 6e 06 c0 86 17 98 53 72 33 85 ae ff

checksum

global: 56 49 b3 02 f2 b7 5b 82 ec 2d c2 1a ff 80 8c 79

root: bf 18 cf 83 1e 04 c3 04 4c e4 66 bc 38 fe 3a dc

all: 77 06 d0 89 6e 06 c0 86 17 98 53 72 33 85 ae ff

To get ha sync information from the secondary device:
# get test hasync 50
autoscale_count=69. current_jiffies=41235125
    10.0.0.6, timeo=31430, serial_no=FGVM04TM19001766
    10.0.0.7, timeo=31430, serial_no=FGVM04TM19008156
    10.0.0.5, timeo=31430, serial_no=FGTAZR7UZRKKNR3D