| CPUG | |
| The Check Point User Group | |
| A Resource For The Check Point Community. Fast. Useful. Independent. | |
|
| |||||||
![]() |
| | LinkBack | Thread Tools | Display Modes |
| |||
| DEAR , I am using r60 cluster firewall , SIc communication fail often , what wiil the root cause of SIC , SIC test also fail , get error CPD NOT running TCP connectivity is fail from SmartCenter server to IP "X.X.X.X, Port 18191 Regards d31jan |
| |||
| hi is ur smart server center behind a nat environment or is ur smart server behind a firewall before it can reach the cluster object. i had the same problem with when my smart server was behind a another checkpoint firewall. i had to do static nat and select for vpn-1 control connections only. tell us more abt ur topology we will be able to help u out better. regards sebastan |
| |||
| Dear , I am using 1) Enforcement Module 1 (Primary) : Secure Platform NGX R60 Build 269 (2) Enforcement Module 2 (Secondary) : Secure Platform NGX R60 Build 269 (3) Management Server (Windows 2003 Sever ): NGX R60_HFA_02 NO my smart server is not behind a firewall before it can reach the cluster object. 1 To aceess management server from lan one rule is create. Problem detail: There is temporary disconnection between Enforcement module's and Management server during this period we are not able to ping or reach on open ports from enforcement module to Management & vice versa. However there is no communication problem during this period except the subject matter. Towards the resolution of the problem we have even changed the switch port of the Management server but the problem persist. The problem gets resolved automatically after some time and it start to function smoothly Observation: During the issue if we unload the policy on the enforcement module we are able to ping the Enforcement Module from Management and vice versa. Regards D31jan |
| |||
| I had the same problem recently immediately after an upgrade. I upgraded the Secondary member of a cluster first. I wanted th ensure that it was working correctly before upgrading the Primary. I would change the CP version in the Checkpoitn cluster object to the Secondary's version and then reset SIC. It would work initially then as soon as I click the TEST button, or go to Smart Update (for the license), SIC would break. To fix the issue I had to break the cluster. The other option would have been to upgrade both members together. In your case, if both members are running the same Checkpoint version, confirm that the version in the CLuster object is correct. |
![]() |
| Thread Tools | |
| Display Modes | |
| |