Fortinet black logo
7.2.0

Troubleshooting

Troubleshooting

Verify License Key Configuration

The High Availability feature is included in BASE, PLUS and PRO licenses.

For more information on licensing, refer to the License Upgrade Guide in the Document Library.

License Entitlements

The license can be verified using the command get system license.

Example:

> get system license
EFFECTIVE:
serial = xxxxx
type = NetworkControlApplicationServer
level = PRO
count = 100000
expiration = 31622400000
expired = false
mac = 00:50:56:98:34:73
uuid = 4218e64a-d8f1-39e3-471f-46e2c5f027df
certificates = [xxxx]

To view both Primary and Secondary Server licenses at once, log in to the Secondary Server CLI and type

get system license -key APPLIANCE -key PRIMARY 

Example (Output of system with Primary Server in control):

> get system license -key EFFECTIVE -key APPLIANCE -key PRIMARY -key MANAGER
EFFECTIVE:      <--- Key of server in control (Primary Server)
serial = xxxxx
type = NetworkControlApplicationServer
level = PRO
count = 100000
expiration = 31622400000
expired = false
mac = 00:50:56:98:34:73
uuid = 4218e64a-d8f1-39e3-471f-46e2c5f027df
certificates = [xxxx]

APPLIANCE:   <--- Secondary Server
serial = xxxxxx
type = NetworkControlApplicationServer
level = PRO
count = 100000
expiration = 31622400000
expired = false
mac = 00:50:56:98:5E:B3
uuid = 4218c883-093b-5e28-f895-bee88bc3202d
certificates = [xxxx]
PRIMARY:    <--- Primary Server
serial = xxxxx
type = NetworkControlApplicationServer
level = PRO
count = 100000
expiration = 31622400000
expired = false
mac = 00:50:56:98:34:73
uuid = 4218e64a-d8f1-39e3-471f-46e2c5f027df
certificates = [xxxx]

Validating Processes CLI

Log in to each appliance and type

diagnose tail -F output.processManager

The following message indicates Primary is in control:

Primary Server: (Primary) Primary In Control Idle(false)

Secondary Server: (Secondary) Primary In Control Idle(false)

Troubleshooting

Verify License Key Configuration

The High Availability feature is included in BASE, PLUS and PRO licenses.

For more information on licensing, refer to the License Upgrade Guide in the Document Library.

License Entitlements

The license can be verified using the command get system license.

Example:

> get system license
EFFECTIVE:
serial = xxxxx
type = NetworkControlApplicationServer
level = PRO
count = 100000
expiration = 31622400000
expired = false
mac = 00:50:56:98:34:73
uuid = 4218e64a-d8f1-39e3-471f-46e2c5f027df
certificates = [xxxx]

To view both Primary and Secondary Server licenses at once, log in to the Secondary Server CLI and type

get system license -key APPLIANCE -key PRIMARY 

Example (Output of system with Primary Server in control):

> get system license -key EFFECTIVE -key APPLIANCE -key PRIMARY -key MANAGER
EFFECTIVE:      <--- Key of server in control (Primary Server)
serial = xxxxx
type = NetworkControlApplicationServer
level = PRO
count = 100000
expiration = 31622400000
expired = false
mac = 00:50:56:98:34:73
uuid = 4218e64a-d8f1-39e3-471f-46e2c5f027df
certificates = [xxxx]

APPLIANCE:   <--- Secondary Server
serial = xxxxxx
type = NetworkControlApplicationServer
level = PRO
count = 100000
expiration = 31622400000
expired = false
mac = 00:50:56:98:5E:B3
uuid = 4218c883-093b-5e28-f895-bee88bc3202d
certificates = [xxxx]
PRIMARY:    <--- Primary Server
serial = xxxxx
type = NetworkControlApplicationServer
level = PRO
count = 100000
expiration = 31622400000
expired = false
mac = 00:50:56:98:34:73
uuid = 4218e64a-d8f1-39e3-471f-46e2c5f027df
certificates = [xxxx]

Validating Processes CLI

Log in to each appliance and type

diagnose tail -F output.processManager

The following message indicates Primary is in control:

Primary Server: (Primary) Primary In Control Idle(false)

Secondary Server: (Secondary) Primary In Control Idle(false)