| CPUG | |
| The Check Point User Group | |
| A Resource For The Check Point Community. Fast. Useful. Independent. | |
|
| |||||||
![]() |
| | LinkBack | Thread Tools | Display Modes |
| |||
| Hi I remember in 4.1 for state sync you used to do put keys between the interfaces. So, in NG & NGX put keys have been replaced by sic. If sic failed on the member of a cluster would the state tables continue being kept up to date. Not sure wether sic only covers management to gateway communication or sync to sync. I guess if it doesnt cover sync to sync what did checkpoint use to replace the putkeys. Thanks "Birmingham" |
| |||
| It does cover sync and any other management protocols. All SIC is is TLS/SSL encryption. So if you are failing SIC it tends to mean communication between the hosts isn't working correctly |
| |||
| So are you saying that if sic was reset / or got corrupted on a member of a cluster the state tables would not be able to be kept syncronised between the two members of the cluster....because the other member of the cluster whose sic might be ok would not recognise the other member. I guess i am saying sic normally sets up a secure channel between management and gateway but does it also allow a secure channel between gateway and gateway for state table sync. |
![]() |
| Thread Tools | |
| Display Modes | |
| |