![]() ![]() Richard Kentsays HP has a good heart that they don't mind supporting obsolete versions. ![]() Supported Checkpoint NG Versions (of SmartCenter Server only We are NOT concerned about Enforcement modules e.g: Firewalls as we can ONLY get the logs from the management server in the Checkpoint architecture). IMPORTANT CHECKS BEFORE PROCEEDING WITH INTEGRATION:ġ. Method Used: OPSEC SSLCA (Easy & secure integration option for Checkpoint) Treat it as a ready reckoner OR when you are stuck even after following the steps in the guide (as so many faced due to the heavy technical content of the document ) This post in no way overrides the original HP document SmartConnector for CheckPoint OPSEC NG Has anyone encountered something similar ?Īnd finally, would there be any way to make a dashboard that would keep track of the CMA's sending logs ? I change absolutely nothing to the configuration, but it works. But if I go into the configuration, remove a CMA ( regardless if it's one that lost its connection or not ) save the new configuration, re-add it and save again the configuration. ![]() One CMA will loose it's connection, if I restart the connector, the connection won't go back up. At some point, haven't found if there was a correlation somewhere. ![]() Successfully updated parameters of connector ĭoes anyone knows why ? And if there is a way to fix it ?Ģ) This error is really concerning because we lose logs. |#| 100�ssfully updated parameters of connector ) The informations are good, when running the connectors I get the logs from every " Unable to connect " which is annoying, because I can't know if I made a mistake or no, and the verification is soooo long because every tests " fails " :Īre the values correct ?yĬonnector table parameters did not pass the verification with error Unable to connect to the Lea Server I don't have a conapp so I do everything in CLI.ġ) Everytime I create / modify a connector, by adding / removing / modifying a CMA when validating that the values are correct, the software tries a connection to every CMA. I'm running these connectors on RHEL 6.4 or 6.6, same errors aswell and tried with SMC 7.2.2, 7.3.0 and, same errors. I've been struggling with checkpoint connectors for a while now and haven't been able to find any solutions on any of these problems. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |