Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

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

Re-enable the Mgmt Port after Backup/Restore from a device that didn't have one

Hi,

I'm currently preparing our new XGS3300 to migrate from our XG310 which is soon end of life.

I've done a Config Backup from the XG310 and applied it to the XGS3300 which was successful apart from the XGS3300 MGMT Port is now disabled.

Is there anyway I can re-enable the Dedicated MGMT Port from the Front Panel or Console/Advanced Shell?

I was hoping to setup the XGS3300 together with it's HA partner via the MGMT port before shutting down the XG310 pair and moving the cables.

Any help appreciated

Thanks,

Craig



This thread was automatically locked due to age.
  • Hello,

    Thank you for contacting Sophos Community!

    You review below:

    docs.sophos.com/.../index.html

    Mayur Makvana
    Technical Account Manager | Global Customer Experience

    Sophos Support Videos | Knowledge Base  |  @SophosSupport | Sign up for SMS Alerts |
    If a post solves your question please use the 'Verify Answer' button.

  • Yes, I already review the document, this assumes you can get into the device, because the MGMT port has been disabled by the backup restore from the XG310, which didn't have a MGMT port, the MGMT port is now disabled.

    I only have the MGMT port plugged in currently as I don't want the restored backup on the new XGS3300 to interfere with my currently running XG310s

    So, I need to re-enable it from the console/adavanced shell and assign an IP address to it

    Craig

  • how did you locally manage the XG before? this "old" interface should still exist. Eventually on a different port.  the mgmt interface will just appear in the interface list and can be configured as per your needs.

  • They were managed from the Lan Interface, via the LAN IP address as a dedicated MGMT port didn't exist on the XG310s

    I like the idea of having a separate MGMT interface on the XGS3300 as this was how the out of the box setup/restore process was done through, the MGMT port also didn't show up in the SFOS 20 MR2 port mapping function else I would have remapped it there.

    I can't plug the LAN port of the newly restored XGS3300 in as it will conflict with my XG310 LAN interfaces.

    Craig

  • can't you just plug your notebook to the local LAN port of the machine?

  • I could if I had a fibre port on it, our LAN port is mapped to a SFP port.

    I'll have to use the console to change the LAN IP of the XGS3300 I think, so I can plug it into the network. It's a bit of a ballache to have to do to re-nable the MGMT port, which is why I was hoping to setup the MGMT port via the Console/Advanced Shel

  • an idea: on XG310 - if you have: activate a free interface for admin management, backup and restore again on XGS.

  • I've managed to do it by temporarily changing the LAN IP from the console to something other than that on the running X310 pair, once in I configured the MGMT interface from there, did the same on the other new XGS3300 after it did the same thing during the backup restore. I've got them configured in HA now, just need to change the LAN IP back when I switch off the X310 pair.

    So I've worked around the issue now

    Thanks for your suggestions!

  • Did you try the new Backup / Restore Wizard in SFOSv20.0 MR2? 

    __________________________________________________________________________________________________________________

  • Yes, I did, firstly with the XGS3300s in HA configuration and watching the dedicated video. This failed and the config didn't apply.

    So needed to factory reset the devices.

    Second attempt using the Wizard, I restored to just one XGS3300 without the HA, this worked, but as my original post says, it disables the MGMT port. There is no prevision to manage what happens to the MGMT port during the wizard so it just got deactivated.

    Anyway. I've worked around the issue now as detailed in my last reply to LHerzog above.