Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 26 subscribers
  • Views 420 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

What might be the Diff in SG105 vs. SG210 - emulation in VB 6.1 (210 enters failsafe mode)

juergenb52

Hi,

I wanted to test drive some Migrations from XG 17.5 to XG 18.0 for our life system (a SG210 with a running XG 17.5).
Because Migration is not working for a backup from XG 17.5 (that is running on a SG 210 device).

The backup still has traces of a SG210 Device and will not be imported by a XG in Hyper-V.

So, this doesn´t work and i wanted to test this in a emulate system.

So, i created two Virtual Appliance to emulate a SG105 and a SG210 with similar Hardware Information. 

I installed HW-17.5.14_MR-14-711.iso on both VM´s.

For the SG105 the install is fine and i get a login to XG 17.5.14 console.
For the SG210 the install is fine and i get a login to XG 17.5.14 console, but soon the XG enters failsafe mode.

Besides that i don´t have any NIC´s detected (second problem).

Does anyone have an idea, why the installation in a emulated SG210 enters failsafe mode and for a SG105 (or XG105) not?

What might i miss in the emulated SG210 VM?

Is there any log file showing why it enters failsafe mode?

I know that this is all not supported, but it´s for testing purpose only.

Regards

 

Jürgen



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

    Hello Jurgen,

    Thank you for contacting the Sophos Community.

    You could check the reason of the failure by running:

    failsafe> show failure-reason

    Sophos Firewall Virtual Security Appliance boots up in Failsafe Mode in any of the following scenarios:

    If number of vCPUs allotted is more than the purchased license
    vRAM size is lower than minimum required: 1 GB
    Assigned vNICs less than minimum required: 3 interfaces
    Auxiliary Disk size less than minimum required: 80 GB
    If Auxiliary Disk not found
    Attaching an unformatted disk
    The virtual appliance goes into Failsafe Mode if any of its following services fail:

    Configuration Database
    Signature Database
    Firewall Framework
    Logging Daemon
    Network Daemon
    Firewall Rules

    You can find more info in this link

    https://community.sophos.com/kb/en-us/125178

    Regards,

Reply
  • 0

    Hello Jurgen,

    Thank you for contacting the Sophos Community.

    You could check the reason of the failure by running:

    failsafe> show failure-reason

    Sophos Firewall Virtual Security Appliance boots up in Failsafe Mode in any of the following scenarios:

    If number of vCPUs allotted is more than the purchased license
    vRAM size is lower than minimum required: 1 GB
    Assigned vNICs less than minimum required: 3 interfaces
    Auxiliary Disk size less than minimum required: 80 GB
    If Auxiliary Disk not found
    Attaching an unformatted disk
    The virtual appliance goes into Failsafe Mode if any of its following services fail:

    Configuration Database
    Signature Database
    Firewall Framework
    Logging Daemon
    Network Daemon
    Firewall Rules

    You can find more info in this link

    https://community.sophos.com/kb/en-us/125178

    Regards,

Children
No Data