SIC Failure when creating new virtual systems in VSX

[P_Williams]

I have been trying to create a new virtual system and virtual switch today, I have run into an issue though which I haven't in the past. 

For both I got

B-02: VSX configuration was applied successfully.
B-01: VSX configuration was applied successfully.
Virtual System Processing Completed Successfully
Establishing Trust with - B.....
The certificate is not valid.
Failed to establish trust with B......
Establishing Trust with - B.......
The certificate is not valid.
Failed to establish trust with B.......

Initiating trust with Virtual System operation has finished with warnings.
Make sure that all Virtual Systems/Routers are accessible from the management server,
and that you have a valid license. Edit the failed object and click OK.
If the problem persists contact Check Point Technical Support.
Initiating trust with Virtual System operation has finished with warnings.
Make sure that all Virtual Systems/Routers are accessible from the management server,
and that you have a valid license. Edit the failed object and click OK.
If the problem persists contact Check Point Technical Support.

Operation has finished with warnings.

And on the SMS I can see that the command cpca_client lscert -kind SIC

Subject = CN=B.........VSY-05,O=SMS-01........unyjpc
Status = Pending Kind = SIC Serial = 83632, OTP validity = none

Subject = CN=B.........VSW-03,O=SMS-01........unyjpc
Status = Pending Kind = SIC Serial = 66503, OTP validity = none

I am wondering if it is because there wasn't networking between the virtual devices when I initially created the devices that SIC then failed and now I just need to reset it? Or is there something else possibly wrong.

If I go to the vsenv <number> of the new created devices and cpconfig and choose (5) to reset SIC am I just resetting SIC for that VS or is it for whole environment?

[emmap]

If the VS is not in use yet it's probably best to just delete it and recreate it. 

That being said, this is the article for VS SIC reset.

https://support.checkpoint.com/results/sk/sk34098

[P_Williams]

Thank you for your reply, in deleting and reapplying the config I ran into the same issue. I did some zdebug captures as I applied the config and it is a routing issue between the SMS and one of the pre-existing virtual systems. I can see that the pre-existing virtual system is not advertising via BGP one of its directly connected networks. When I fix that I believe the problem will be resolved.