FortiKoala
Staff
Created on 09-27-2018 07:37 AM Edited on 09-27-2024 08:37 AM By Anthony_E
Article Id
190414
Description
This article describes how to restore control to Primary Server(s) using the CLI. For instructions on resuming control using the Administration UI, see the related KB article below.
Scope
FortiNAC v6 and above
Solution
Contact support if assistance is needed.
Establish SSH sessions to all 4 Appliances (2 if NS500/550's). All SSH sessions should be open at once.
1. Change the Status from 2 to 1 on all 4 appliances.
On the Secondary Control Server:
On the Primary Control and Application Server the following commands can be run to monitor logs:
Establish SSH sessions to all 4 Appliances (2 if NS500/550's). All SSH sessions should be open at once.
1. Change the Status from 2 to 1 on all 4 appliances.
- Type cd /bsc/campusMgr/bin
- Type vi .networkConfig
- Change Status=2 to Status=1
- Save changes and exit file
- Repeat this on all 4 appliances
- Type shutdownNAC
- Wait 30 seconds
- Type shutdownNAC ‐kill
- Repeat this on all 4 appliances
On the Secondary Control Server:
- Type cd /bsc/campusMgr/master_loader/mysql
- Type ydb_dated_backup
- Type cd backup
- Locate the latest Database backup file
- Copy database backup to Primary Control Server (this command should work): Type
scp <filename of backup> cm1/bsc/campusMgr/master_loader/mysql/backup
On Primary Control Server
- Type cd /bsc/campusMgr/master_loader/mysql
- Type ydb_restore_full_backup <filename of backup>
- On Primary Control Server type startupNAC
- Allow about 10 minutes for the system to startup.
On the Primary Control and Application Server the following commands can be run to monitor logs:
cd /bsc/log
tail -f output.processManager
Look for the following line to appear (may take a minute before it shows up):
<hostname>(Master) Master In Control Idle(false) Total Memory……….
5.Start services on the Secondary system (will be in standby).
- On the Secondary Control Server run the following commands:
startupNAC
cd /bsc/logs
tail –f output.processManager.
Look for the following line to appear (may take a few minutes before it shows up):
<hostname>(Slave) Master In Control Idle(false) Total Memory……….
6. Log into the UI on the Primary system. On the Dashboard screen confirm, the Summary panel shows: Primary Servers as 'Running - In Control'. Secondary Servers as 'Running - Not In Control'.
Related article:
Labels:
Comments
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Think we can break down step 1 to 2 steps.
1. Enter the command: vi -c "%s/Status=2/Status=1/g|wq" /bsc/campusMgr/bin/.networkConfig
2. Repeat this on all 4 appliances