Failover between two V2110 is not working
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎10-16-2017 10:37 AM
Hello the Hub !
I have two V2110 controllers running in availability pair mode.
Today the primary V2110 suddenly stopped working - don't know why (probably it was the power issue).
The bad thing is that AP's and clients didn't switched to secondary V2110.
I have tested this configuration before and we had good failover behaviour.
There was no change in configuration since then.
I have repeating log massege (major severity):
Config Manager has experienced an error which has prevented it from properly processing a request. CM will continue running, however this error may be an indicator of a larger system
problem. Error Details:Error updating table [/var/controller/data/db/phyport.bin] id [2]
- could it be related somehow to failover behaviour ?
The software is 10.11.05.0005.
Did anyone experience something like that ?
REGARDS
Robert
I have two V2110 controllers running in availability pair mode.
Today the primary V2110 suddenly stopped working - don't know why (probably it was the power issue).
The bad thing is that AP's and clients didn't switched to secondary V2110.
I have tested this configuration before and we had good failover behaviour.
There was no change in configuration since then.
I have repeating log massege (major severity):
Config Manager has experienced an error which has prevented it from properly processing a request. CM will continue running, however this error may be an indicator of a larger system
problem. Error Details:Error updating table [/var/controller/data/db/phyport.bin] id [2]
- could it be related somehow to failover behaviour ?
The software is 10.11.05.0005.
Did anyone experience something like that ?
REGARDS
Robert
6 REPLIES 6
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎11-22-2017 08:36 AM
With remote support from GTAC, we tried repairing file system with FSCK in rescue mode, however same error showed up. We then redeployed a new V2110 and upgraded it to version 10.31.07.0002, rehosted the licenses, and got the configuration imported from the original controller.
The new V2110 is now operating without the errors.
Many thanks to Ryan Careno from GTAC team !
The new V2110 is now operating without the errors.
Many thanks to Ryan Careno from GTAC team !
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎11-10-2017 12:57 PM
Hi Robert - Just want to make sure the Virtual Server itself is OK? Nothing wring with the ports there?
Please also include the tech support files from both V2110s when you open the Case.
Please also include the tech support files from both V2110s when you open the Case.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎11-10-2017 12:40 PM
Upgrading to 10.31.07.0002 didn't solve the problem.
The error message is still present, I am going to create GTAC case.
The error message is still present, I am going to create GTAC case.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎10-17-2017 04:28 AM
Thank you guys,
I'll put new version nad check.
Regards,
Robert
I'll put new version nad check.
Regards,
Robert
