I would like to do some upgrades on the server. I need to know which components I should shut down first and which should be shut down last, as well as the order for booting them up. This includes the supervisor, worker, collectors, and NFS.
Thanks.
Solved! Go to Solution.
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
Ok, that is easy then.
If the upgrade will take more than 2 - 3 hours and you have a cluster architecture, start by shutting down the collectors first and then workers and finally the Supervisor.
If the upgrade will take less than 2 - 3 hours you can leave the collectors on.
From there upgrade any RAM or CPUs required and boot the infrastructure, Supervisor first, then workers and then collectors.
Check services with phstatus and the logs on the supervisor and workers for any errors.
The systems should be able to pick up any changes in RAM and CPU without any intervention.
Hope it helps.
S
Hi @Jesisidabuliu ,
The document at https://docs.fortinet.com/document/fortisiem/7.1.4/upgrade-guide/505373/upgrading-to-fortisiem-7-1-x provides all necessary information you have requested above.
S
Hi Sioannou,
I'm not going to upgrade the version; I just want to upgrade my server hardware. I'd like to know the steps for switching off and switching back on, specifically which to switch off first and which to switch back on first.
Hi @Jesisidabuliu ,
Is the environment virtualised?
If not, will you be migrating the disks across, are you upgrading your NFS storage hardware as well?
S
Hi @sioannou ,
Supervisor, worker, and collector are deployed in a VM ESXi. I'm just going to upgrade the memory of the server.
Ok, that is easy then.
If the upgrade will take more than 2 - 3 hours and you have a cluster architecture, start by shutting down the collectors first and then workers and finally the Supervisor.
If the upgrade will take less than 2 - 3 hours you can leave the collectors on.
From there upgrade any RAM or CPUs required and boot the infrastructure, Supervisor first, then workers and then collectors.
Check services with phstatus and the logs on the supervisor and workers for any errors.
The systems should be able to pick up any changes in RAM and CPU without any intervention.
Hope it helps.
S
Thank you so much @sioannou.
After everything is up, is there any command to check if the NFS is connected properly?
Hi, you don't need to shutdown Collectors first. Collectors are able to ingest and buffering logs if there are no connection with Workers or Supervisor. Therefore, the rigth procedure is:
Stop the backend processes on Workers:
phtools --STOP ALL
# phshowVersion.sh
# phstatus
Yes,
Commands as follows:
1) first check the mounting point "cat /etc/fstab" check your nfs mounting points.
2) Execute command "watch -n 1 nfsiostat"
The command above will show you your Read/Write and error count to the NFS storage.
Make sure no errors are present and that the read and write times are within acceptable limits.
S
I appreciate your answer. Thank you so much! @sioannou
Welcome to your new Fortinet Community!
You'll find your previous forum posts under "Forums"
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.