Operation Failed when try to save integration setting

Hi All,

I try to perform integration between ES and CC at my environment. Both connection is success but no logs sending out from ES to CC. When i try to modified and save the integration setting it throw me failed operation. anyone facing same issue here?

Hi,

Click <Update> to save your settings. > Multilevel menus and submenus. Go to [System] > [Network Interface] to configure the network interfaces.

Thanks

Hi,

I don't find it related to the save setting. I have save all the configuration and i don't found it related to the network interface setting as well. Got any more ideas?

HiHi,

Pls upgrade your CC(latest CCOM3.0.65 (Stable Version)) & pls check the license, Network Configuration & related port.

For your easy Ref, pls find below linking for "How to Correlate with Endpoint Secure to Simply the Operation"

https://community.sangfor.com/plugin.php?id=sangfor_databases:index&mod=viewdatabase&tid=4620

Regards,

Check the configuration: Verify that the integration settings for sending logs from ES to CC are correctly set up. Ensure that the required parameters such as endpoints, credentials, and mappings are accurate.

Verify connectivity: Ensure that there is network connectivity between the ES and CC components. Check if any firewalls or network restrictions are blocking the communication between the two systems.

Review logs and error messages: Examine the logs from both ES and CC to identify any error messages or warnings that could provide insights into the issue. Look for any specific error codes or messages that might indicate the cause of the problem.

Check permissions and access: Ensure that the user account or credentials being used for the integration have the necessary permissions and access rights in both ES and CC. Verify that the user has the appropriate privileges to send logs from ES to CC.

Update or reinstall components: If the integration settings cannot be modified or saved, it could indicate a potential issue with the software versions or configurations. Consider updating or reinstalling the ES and CC components to ensure you have the latest versions and that the installation is properly configured.

Seek support: If the issue persists, it might be helpful to reach out to the official support channels for both ES and CC. Provide them with the relevant details, error messages, and steps you have taken so far. They should be able to assist you further in resolving the issue.

Please update first the CC then check again

Check the Connection Status: Verify that the connection between ES and CC is still established and active. Ensure that the network connectivity between the two systems is functioning properly.

Verify Integration Settings: Double-check the integration settings in both ES and CC. Ensure that the correct endpoints, credentials, and configurations are provided. Make sure that the integration settings are saved correctly in both systems.

Log Monitoring and Indexing: Check the Elasticsearch logs to see if there are any error messages or warnings related to the integration. Verify that the logs you expect to be sent to CC are being properly indexed in Elasticsearch.

Debug Logging: Enable debug logging or increase the log verbosity level for the integration components (ES and CC). This can provide more detailed information about the issue and help in troubleshooting.

Review Error Messages: When you receive a "failed operation" error while modifying and saving the integration settings, look for any accompanying error messages or error codes. These can provide clues about the specific problem and help in finding a solution.

Test Configuration Changes: Try making small, incremental changes to the integration settings and saving them. This can help identify if there is a specific configuration parameter causing the issue. You can also try reverting back to a previously working configuration to see if the problem persists.

Consult Documentation and Support: Check the documentation for both ES and CC regarding the integration setup and troubleshooting. Look for any known issues, common pitfalls, or specific troubleshooting steps. If needed, reach out to the support channels of the respective products for further assistance.

Consider Firewall and Security Settings: Ensure that there are no firewall rules or security settings blocking the communication between ES and CC. Verify that the necessary ports are open and that any authentication or encryption requirements are properly configured.

The integration settings modification failed, possibly due to an incompatible configuration or a communication issue between Sangfor Endpoint Secure and Cyber Command.

Check the configuration: Verify that the integration settings for sending logs from ES to CC are correctly set up. Ensure that the required parameters such as endpoints, credentials, and mappings are accurate.

Verify connectivity: Ensure that there is network connectivity between the ES and CC components. Check if any firewalls or network restrictions are blocking the communication between the two systems.

Review logs and error messages: Examine the logs from both ES and CC to identify any error messages or warnings that could provide insights into the issue. Look for any specific error codes or messages that might indicate the cause of the problem.

Check permissions and access: Ensure that the user account or credentials being used for the integration have the necessary permissions and access rights in both ES and CC. Verify that the user has the appropriate privileges to send logs from ES to CC.

Update or reinstall components: If the integration settings cannot be modified or saved, it could indicate a potential issue with the software versions or configurations. Consider updating or reinstalling the ES and CC components to ensure you have the latest versions and that the installation is properly configured.

Seek support: If the issue persists, it might be helpful to reach out to the official support channels for both ES and CC. Provide them with the relevant details, error messages, and steps you have taken so far. They should be able to assist you further in resolving the issue.

Check the compatible configuration. Maybe there were errors on there.