SIC problem after upgrade

[starmen2000]

In the maintenance windows, we attempted to update our SMB cluster from R80.20 to R81.10. However, after the upgrade, we encountered some problems:

1. The connection between SmartConsole and the gateway was lost. On smartconsole cluster shows red.

2. The software version on the SMB appliance unexpectedly reverted to R80.10, and the appliance restarted.

3. When I checked the SMB Appliance through its web interface, I found a communication error known as SIC.

To address this issue, I followed the instructions provided in sk161532. While we managed to initialize the SIC on the SMB site successfully, the Smart Console site displayed an error message saying, "Operation error, if the problem persists, contact customer support. And Certificate authority does not recognize the entity. Either the entity has been revoked or it does not exist" error

Tac involved in the issue, but looks no hope.

Any advice, any experience?

[G_W_Albrecht]

Did you check SMB model/version in Smart Console? Also remember:

Important - Management Server version for Central Management:

• For 1530 / 1550 / 1570 / 1590 / 1570R / 1600 / 1800 appliances, you must be running R81.10 with Take 66 and higher, or R81.20.

• For 1535 / 1555 / 1575 / 1595 appliances, you must be running R81.10 with Take 99 and higher.

[starmen2000 · Accepted solution]

Issue was solved. Solution was to change management method on SMB Webgui from central to local and then again from local to central, reset sic, that s all. 

[R-Mina]

I have the same issue, but have no way to access the SMB WebUI since I cannot access the interfaces from outside the network that is now down.  I was able to backdoor into the network behind the SMB using a cellular backup circuit and can only access CLI.  Is there a way to set the SMW to local and then central from the CLI?

[JSchmidl]

I'm having the same issue. We can access the console through a management computer. Does the "set security-management mode" command still work on R81.10?

[R-Mina · Accepted solution]

Yes.  That is how I was able to resolve it via the backdoor CLI access:

set security-management mode locally-managed

and then

set security-management mode centrally-managed

Afterwards,

I was able to reset SIC and attach to Smart Console.