Prerequisites Virtual environment:
- Customer must have a backup, and this backup must be taken off the existing all-in-one
- When working with a Virtual machine, it is suggested that the customer creates all new VM's and leaves the existing all-in-one turned off
- Create a new VM for the application server(AS)*
- Create a new VM for the database (DB)*
- Create a new VM for the data collector (DC)*
- Each VM will need an IP address and new hostname, it is recommended that the DC is set with the existing IP for the all-in-one this way the end devices will not need to be changed.
Prerequisites new Physical hardware:
- Customer must have a backup, and this backup must be taken off the existing all-in-one
- New hardware Application server setup and reachable via the console*
- New hardware Database server setup and reachable via the console*
- New hardware Data collector server setup and reachable via the console*
- Each physical host will need an IP address and new hostname it is recommended that the DC is set with the existing IP for the all-in-one this way the end devices will not need to be changed.
*FMOS-System-Requirements
https://supportcenter.firemon.com/hc/en-us/articles/360004577474-FMOS-System-Requirements-
RISK
- The Customer must be aware that during this process firemon will not be working.
- The Customer is responsible for all backups, and ensuring data is kept safe.
The process to complete the move from all-in-one to fully distributed install:
Database server
- Take a backup of the existing firemon install.
- fmos backup <name of file>
- Ensure that the file is copied off the existing machine
- Complete a fresh install of a Database only server by installing the desired ISO file.
- New IP address (Note this down as you will need it later)
- New Hostname utilising customers FQDN. Case sensitive, and must match on all devices(example Firemondb.network.local.net)
- Note down the username and password set during install
- Copy the backup file back to the DB server into /var/tmp
- On the DB server Complete the restore process:
- fmos restore <backupfile>
Application Server
- Complete a fresh install of the new Application Server, but DO NOT join it yet.
- New IP address (Record this as you will need it)
- New Hostname utilising customers FQDN. Case sensitive, and must match on all devices(example FiremonAS.network.local.net)
- Note down the username and password set during install
- Open the Database Server Control Panel by entering this in your browsers URL bar: https://DatabaseServerIP:55555 *
*Note: This shares a login with the CLI user you created during setup - From the blue menu bar, select SecMgr.
- Underneath that select DB.
- Update the property Shared Filesystem Hosts by entering one or more of the following (separated by a space):
- Input the new IP address of the AS
- Stage the Changes.
- Apply the Configuration.
- Log into the Application Server's CLI and run
- fmos ecosystem join FQDNofDBServer
** if any issues at this point, ensure that DB and AS have full communication on ports, 22, 443, ping **
Data collector
- Setup the new Data Collector server, but DO NOT join it to the Application Server.
- log into the Data Collector's CLI and run:
fmos ecosystem join FQDNofAppServer
Separate Data collector already in place
- On the existing datacollector ensure that the DC can ping the FQDN of the new AS FiremonAS.network.local.net
- log into the Data Collector's CLI and run:
- fmos ecosystem switchover FiremonAS.network.local.net
- fmos ecosystem refresh
- fmos redeploy all
At this point, your server should be up and running with the data that existed in your all-in-one. The reason we have to do it this way is to ensure that the new servers have the correct roles assigned.
Comments
0 comments
Article is closed for comments.