- CheckMates
- :
- Products
- :
- Quantum
- :
- Management
- :
- Re: R80.20 -> R80.40 issue: gateway
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
R80.20 -> R80.40 issue: gateway
Just completed the R80.40 upgrade from 80.20 on (9) clusters and all went well using the blink upgrade...except one gateway.
In a 4800 appliance cluster, one gateway upgraded fine, the other is having major stability issues. Used the blink upgrade that was based on JFA48, and then added JFA 77. The member with stability issues had no errors during the upgrade, after a boot will run OK for a day or two, and then become "disconnected" from management (per smartview monitor). While it's "disconnected", i can SSH to it - a "cphaprob stat" shows that it's currently in standby - the member thinks it's fine. I've noticed that confd and cpviewd will spike up to 95% cpu for a sustained period and then drop back down to normal. I found these in the /var/log message file, not sure if it's salient:
Aug 29 13:30:00 2020 XXX snmpd: Error: Timeout waiting for response from database server.
Aug 29 13:30:39 2020 XXX monitord[10490]: Error: Timeout waiting for response from database server.
Aug 29 13:31:00 2020 XXX snmpd: Error: Timeout waiting for response from database server.
Aug 29 13:31:40 2020 XXX monitord[10490]: Error: Timeout waiting for response from database server.
Aug 29 13:38:32 2020 XXX snmpd: Error: Timeout waiting for response from database server.
Aug 29 13:39:11 2020 XXX monitord[10490]: Error: Timeout waiting for response from database server.
Aug 29 13:39:32 2020 XXX snmpd: Error: Timeout waiting for response from database server.
Aug 29 13:40:12 2020 XXX monitord[10490]: Error: Timeout waiting for response from database server.
Aug 29 13:40:32 2020 XXX snmpd: Error: Timeout waiting for response from database server.
Aug 29 13:47:04 2020 XXX snmpd: Error: Timeout waiting for response from database server.
Aug 29 13:47:43 2020 XXX monitord[10490]: Error: Timeout waiting for response from database server.
Aug 29 13:48:04 2020 XXX snmpd: Error: Timeout waiting for response from database server.
Aug 29 13:48:44 2020 XXX monitord[10490]: Error: Timeout waiting for response from database server.
Aug 29 13:49:04 2020 XXX snmpd: Error: Timeout waiting for response from database server.
Aug 29 13:55:36 2020 XXX snmpd: Error: Timeout waiting for response from database server.
Aug 29 13:56:15 2020 XXX monitord[10490]: Error: Timeout waiting for response from database server.
Aug 29 13:56:36 2020 XXX snmpd: Error: Timeout waiting for response from database server.
Aug 29 13:57:16 2020 XXX monitord[10490]: Error: Timeout waiting for response from database server.
Aug 29 13:57:36 2020 XXX snmpd: Error: Timeout waiting for response from database server.
Aug 29 14:04:08 2020 XXX snmpd: Error: Timeout waiting for response from database server.
Aug 29 14:04:47 2020 XXX monitord[10490]: Error: Timeout waiting for response from database server.
Aug 29 14:05:08 2020 XXX snmpd: Error: Timeout waiting for response from database server.
Aug 29 14:05:48 2020 XXX monitord[10490]: Error: Timeout waiting for response from database server.
Aug 29 14:06:08 2020 XXX snmpd: Error: Timeout waiting for response from database server.
Aug 29 14:12:40 2020 XXX snmpd: Error: Timeout waiting for response from database server.
Aug 29 14:13:19 2020 XXX monitord[10490]: Error: Timeout waiting for response from database server.
Aug 29 14:13:40 2020 XXX snmpd: Error: Timeout waiting for response from database server.
Aug 29 14:14:20 2020 XXX monitord[10490]: Error: Timeout waiting for response from database server.
Aug 29 14:14:40 2020 XXX snmpd: Error: Timeout waiting for response from database server.
A reboot brings the device back fine, and then a day or two later, we're back in the same situation.
Any ideas would be appreciated.
Thanks
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Good afternoon. Was there a resolution to this? We are having identical problems with a Smart-1 5050, R80.30. The only difference is the power cords must be reseated. A warm reboot or shutdown -r does not help. Thank you for any info you can provide. I do have a case open with TAC.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Those messages are consistent with confd spiking in CPU usage and recommend a TAC case ASAP.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Good afternoon. Was there a resolution to this? We are having identical problems with a Smart-1 5050, R80.30. The only difference is the power cords must be reseated. A warm reboot or shutdown -r does not help. Thank you for any info you can provide. I do have a case open with TAC.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Checkpoint had me try multiple troubleshooting steps which didn't resolve the issue. they RMA'd the device.
