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

Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 40 subscribers
  • Views 9025 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

Admin UI not showing, Gateway down

cmezza

Hello,

This morning I wanted to patch my vSphere server, after turning off all VMs, the patch wouldn't download because the XG was also off. I turned it back on to allow Update Manager to download the needed patch. That took too long, so I reset the XG VM until something showed up in the console (via vSphere)

I had initially turned off XG via the web admin console, I think it was done properly.

So now port 4444 doesn't give me anything on either side, I can only get the User Portal on the WAN side

I've tried resetting the network configuration in vain, I would love to send a few good commands via the CLI / Advanced console, but the documentation is lacking in that regard.

I just want to avoid resetting the *ù#  thing to factory defaults and have wasted a few week ends on it...



This thread was automatically locked due to age.
Parents
  • 0
    Ok, I was able to fix my problem: opening the SFOS console within the VM console, I typed 'system appliance_access enable' to gain access to the GUI from the WAN side.

    Everything seemed pretty normal, I just had the LAN PortC NIC (which replicates PortA) disconnected since I had no use for it. As soon as I virtually connected it the the LAN, the traffic was flowing again. A traceroute shows that it's being used instead of PortA. I disabled 'appliance_access', and can now access the Admin UI from the LAN.

    PortA 's IP remains the default gateway, eventhough the trafic goes through PortC now... Both ports are virtual on the same vSwitch.

    So: if I virtually broke something on PortA, how can I diagnose what's wrong with it, or should I replace it with a new virtual NIC and a new MAC address (if possible, without breaking it again...) ?
Reply
  • 0
    Ok, I was able to fix my problem: opening the SFOS console within the VM console, I typed 'system appliance_access enable' to gain access to the GUI from the WAN side.

    Everything seemed pretty normal, I just had the LAN PortC NIC (which replicates PortA) disconnected since I had no use for it. As soon as I virtually connected it the the LAN, the traffic was flowing again. A traceroute shows that it's being used instead of PortA. I disabled 'appliance_access', and can now access the Admin UI from the LAN.

    PortA 's IP remains the default gateway, eventhough the trafic goes through PortC now... Both ports are virtual on the same vSwitch.

    So: if I virtually broke something on PortA, how can I diagnose what's wrong with it, or should I replace it with a new virtual NIC and a new MAC address (if possible, without breaking it again...) ?
Children
Unfiltered HTML