Created on ‎01-27-2025 02:06 AM Edited on ‎01-27-2025 02:07 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
New serial number received
Hi,
So our fortigate cluster restarted last night. We got the following messages over SNMP :
FortiGate: Device has been replaced (new serial number received)
FortiGate: System name has changed (new name: xxx-fw1-n1.xxx.net)
FortiGate: xxx-fw1 has been restarted (uptime < 10m)
This also meant one of our VPN tunnels went down and which generated an alarm. What might have happened here?
Solved! Go to Solution.
- Labels:
-
FortiGate
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
This looks like a fail-over.
Some possible reasons are: manual restart, hardware failure, interface down (if interface monitoring is enabled), or firmware update (in case auto firmware update is enabled).
You may need to check the system logs on both nodes for more information.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When you say cluster restarted, do you mean it failed over? If so, the new serial number is of the old backup node.
Regarding VPN tunnels flap, its expected with cluster failover.
Suraj
- Have you found a solution? Then give your helper a "Kudos" and mark the solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Suraj,
Yeah, it seems it did fail over due to an automatic update. Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
This looks like a fail-over.
Some possible reasons are: manual restart, hardware failure, interface down (if interface monitoring is enabled), or firmware update (in case auto firmware update is enabled).
You may need to check the system logs on both nodes for more information.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Aek,
Yeah it did fail over due to an automatic firmware update. We didn't know it was turned on, probably happened after last firmware update, so I've turned it off again. Thanks!
