Thread Info
  • State Verified Answer
  • +3 person also asked this people also asked this
  • Locked Locked
  • Replies 109 replies
  • Answers 1 answer
  • Subscribers 83 subscribers
  • Views 68239 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

XG Firewall v18 MR-3: Feedback and experiences

twister5800

Hi all,

Shall we start this new thread with the looks and feels of XG v18 MR-3?

community.sophos.com/.../xg-firewall-v18-mr3



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

    I'm unable to upgrade MR3. this pops up when I try to upgrade:

    Firmware downgrade also replaces the current configuration with the earlier one. An upgrade replaces it with the default configuration. For details, go to the online help.

    As far as I can read, it's going to repalce current config with defaults. 

    Tested with two different XG210 setups. Both of them in HA. Updated single XG86 without a broblem. All this mentioned setups are/were running 18.0.1 MR-1.

Reply
  • 0

    I'm unable to upgrade MR3. this pops up when I try to upgrade:

    Firmware downgrade also replaces the current configuration with the earlier one. An upgrade replaces it with the default configuration. For details, go to the online help.

    As far as I can read, it's going to repalce current config with defaults. 

    Tested with two different XG210 setups. Both of them in HA. Updated single XG86 without a broblem. All this mentioned setups are/were running 18.0.1 MR-1.

Children
  • +1 in reply to Jarno Hynynen

    Thank you Jarno for your feedback. This is the known issue (NC-60615) - already fixed in the next MR.

    This *false alarm* alert message appears when XG is running in HA cluster; one uploads the next firmware (like you uploaded MR3); And later boots with the uploaded firmware. If one upload & boot together with the new firmware, this false alert won't appear.

    While resolving this issue in NC-60615, we have also made the alert message more meaningful and easier to understand. The existing message is confusing.

    For MR3 - we request you to ignore this alert and move further, it will migrate the configuration properly. We are also updating the known issue list with this behavior.

    Thanks again for your feedback.

  • 0 in reply to PMParth

    It seems not to be fixed in MR3, because when updating to MR4, it said the same thing. Can you confirm?

  • 0 in reply to giannki

    This has been fixed in MR4. The changes will be effective once you are on MR4.

Unfiltered HTML