Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 8 replies
  • Subscribers 26 subscribers
  • Views 741 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

IPSEC Failover group not created

MMASLOUH
Hello,
After I set up the ipsec failover group I got a message
"The operation wil take time to complete. The status can be viewed from the "Log viewer" but nothing created in the end."
Failover group is empty:
The sophos support stop responding, we feel angry about that and we start thinking to move to watchguard or fortigate next year.


This thread was automatically locked due to age.
Parents
  • FormerMember
    0 FormerMember

    Hi ,

    Thank you for reaching out to the Community! 

    We sincerely apologize for the inconvenience! Could you please provide the support case number for this issue you reported? I will help you out with the follow-up. 

    What is the current firmware version on your firewall, and did you notice any spike in resource utilization? 

    Also, just for testing, try to log out from the firewall and login, then try to configure the IPsec connection group.

    Thanks,

  • 0 in reply to FormerMember

    Hi

    The firmware version is: SFOS 17.5.14 MR-14-1

    The resources utilization seems fine.

    I tired to restart the device but i get the same problem.

  • FormerMember
    0 FormerMember in reply to MMASLOUH

    Hi ,

    Could you please replicate the issue and collect the following logs from your firewall. 

    SSH into the XG firewall by following this KBA: Sophos XG Firewall: How to SSH to the firewall using PuTTY utility

    • To connect using SSH, you may use any SSH client to connect to port 22 of the SFOS device.
    • Select option 5 Device Management.
    • Select option 3 Advanced Shell.

    Run the following command to collect applog: tail -f /log/applog.log 

    Run the following command to collect garner: tail -f /log/garner.log 

    You also need to put the CSC service in debugging and collect csc logs. 

    Run the following command to put the csc service in debug: csc custom debug

    Note: Run the same command to remove the service from debugging. 

    Run the following command to collect csc logs: tail -f /log/csc.log 

    Thanks,

Reply
  • FormerMember
    0 FormerMember in reply to MMASLOUH

    Hi ,

    Could you please replicate the issue and collect the following logs from your firewall. 

    SSH into the XG firewall by following this KBA: Sophos XG Firewall: How to SSH to the firewall using PuTTY utility

    • To connect using SSH, you may use any SSH client to connect to port 22 of the SFOS device.
    • Select option 5 Device Management.
    • Select option 3 Advanced Shell.

    Run the following command to collect applog: tail -f /log/applog.log 

    Run the following command to collect garner: tail -f /log/garner.log 

    You also need to put the CSC service in debugging and collect csc logs. 

    Run the following command to put the csc service in debug: csc custom debug

    Note: Run the same command to remove the service from debugging. 

    Run the following command to collect csc logs: tail -f /log/csc.log 

    Thanks,

Children