Hi, sorry, I can't owing to the environment classification (I'll get in trouble) but, if I elaborate, there may be a step I have missed out. Currently the Manager is the only device visible in Smart Console.
Both gateways are reachable and I have previously had them registered as normal gateways in Smart Console, SIC is possible. There's no policies in Smart Console yet.
When they registered in Smart Console I have tried to create 2 new VSX gateways using the Checkpoint Gateway Installation WIzard. It gets all the way to the end but then throws a SIC error. This doesn't make sense given they have already been through SIC in that process and it has stated that trust is initialised.
Anyway, this is a copy of the screenshot (lifted from google images) of what I got when I just tried to create a VSX cluster, introducing the gateways to Smart Console at the same time.
[I WILL POST AN IMAGE IN A SUBSEQUENT MESSAGE - THE FORUM IS NOT HAPPY WITH ME 🙂 )
Owing to it failing I cancelled however it has already converted the gateways to VSX and I can no longer access them by SSH, but I can still SIC to them. They currently do NOT appear in Smart Console as I cancelled the wizard. Even though I can SIC to them I can't introduce them to the manager again as VSX gateways because they still say:
"Installing default policy - [policy name] on [gateway name]
Policy installation failed on gateway. Cluster policy installation failed: See SK125152)
Failed to install default policy on... etc. etc
It then lists reasons why a policy install might fail.
I haven't manually created a policy, however, the VSX Gateway wizard creates one to push as part of the add wizard.
Sorry for all the waffle, if I could share screenshots I would.
I hope this is a bit more informative but if not, no problem. I will get hold of our support vendor... was just looking here for an answer if possible. I know it's difficult to expect with limited information. Sorry.