New Version Available: Micro Edge with IPsec VPN

[csherman]

Today we officially released Micro Edge version 4.2 with IPsec VPN. IPsec VPN uses the advanced WAN routing capabilities of Micro Edge, so you can leverage the tunnel for routing based on link performance and availability, applications, protocols, networks, and other criteria. This updated version of IPsec also includes expanded options for encryption algorithms & ciphers.

Other updates include support for Japanese and German languages, an OpenWrt operating system update, the ability to deploy in the European ETM Dashboard, and updated branding.

Please see the changelog for a full list of updates in Micro Edge 4.2.

Pricing and Availability - Micro Edge version 4.2 is available as a free upgrade.

[nowebpresence]

Where did all the posts on this thread go?

[gravenscroft]

Where did all the posts on this thread go?

They were removed because they weren't germane to the announcement.

[hdc1234hdc]

One of my Micro edge E6 devices that was running 4.1 got the update with no issue. However, my other E6 that is running 4.0.1 doesn't show the update notification in the GUI, and clicking the Update Software in Command Center isn't making it happen. I've restarted the device several times today hoping it would show up. No Luck, Anything I can do? The upgrades page says I'm on the latest version. Thanks

[jcoffin]

Please DM me your UID and I can check what the issue is.

[hdc1234hdc]

I've tried sending you a private message through the forum and it's not showing any indication that the message was sent. Sent items show zero. I'm gonna try the send email option. Hopefully you get the UID.

[donhwyo]

They were removed because they weren't germane to the announcement.

Why not lock your announcements. Then people can open new threads. While you are at it why not remove old closure notices? LOL

[jcoffin]

I've tried sending you a private message through the forum and it's not showing any indication that the message was sent. Sent items show zero. I'm gonna try the send email option. Hopefully you get the UID.

All good. You should have a reply with the answer.

[gravenscroft]

Why not lock your announcements. Then people can open new threads.

There are plenty of ways in which constructive and relevant conversation could happen in regard to an announcement and we want to encourage that. It makes sense for that kind of discussion to be attached directly to the announcement.

While you are at it why not remove old closure notices? LOL

To paraphrase Dr McCoy: 'Blast it, Jim! I'm a forum admin, not a janitor.'

[htimsorea2001]

Running into some potential update issues. I have a group of 17 Micro edge devices, 6 went offline around 10 hours ago, the other 11 all have an uptime around 10 hours. The online devices (looking at cmd center) are running version 4.2 and the offline ones are showing 4.0.1. Trying to get someone at one of these remote locations to power cycle the e3 device. Unfortunately I have no way to login to any of these devices to further troubleshoot with cmd center and the VPNs not responding. Anyone else running into e3 devices going offline after the update?

Edit: checking the online devices they were all set to update today so likely all the offline devices are exactly the same too, so pointing more to some potential update issue.

[jcoffin]

E3s can have the db in a lock state due to purge cycles since they have a small drive. This causes it into a boot frozen state. Power cycle does restore the E3. I tend to reboot the E3 manually but manually upgrading.

[htimsorea2001]

Was able to get access to one by getting a tech onsite. Local login works and shows version 4.2. WAN showed online. Power-cycled the device, still doesn't show online in cmd center and wireguard VPN is down. Tried pinging out to the internet from behind the e3 and all pings fail so traffic isn't passing even after a reboot. Any ideas?

Edit: ssh into the appliance and try and ping and no luck there either.

Edit2: Found that the device was set to DHCP on the WAN and it wasn't getting a DHCP address. Had to statically set an IP and it worked. Neither WAN interfaces on the e3 would pull a DHCP address. Looking at the online devices that are working, they all have static IPs set on the WAN so possible there is a DHCP issue on the update?

[jcoffin]

Check if the correct nics are the wan Ethernet. I did see a swap of nics on upgrade once but couldn't reproduce it

[htimsorea2001]

NICs all looked good from looking at ifconfig aside from missing an IP address. Looked through config backups of some of the other offline devices and some have static IP addresses set so can no longer point the finger at a DHCP issue definitively. Have technician scheduled to go onsite tomorrow to tackle a few of the high priority devices so hopefully can get some more information then on the symptoms and solution.

[jcoffin]

It's not obvious from the gui. I had to unplug one nic at a time and see which gui interface disconnected to realize the interfaces had swapped nics