[NEBULA] NSG urgent patch has been released!
Dear Nebula users,
On November 18th, a new NSG firmware patch has been released on Nebula Control Center fixing an issue identified in previous firmware released (October 28th). The issue causes the device loosing connection with Nebula under some unstable network cases; while the network functionalities keep running, the device is incorrectly displayed online on NCC and no statistics data or settings are being updated. Rebooting the NSG is required to reestablish the communication with Nebula again.
Make sure your device is properly connected to NCC and proceed to perform a firmware upgrade through the Firmware management page. Please be reminded that upgrading the firmware will imply a reboot of the device, therefore, an interruption on your network.
For more information about the new firmware version and its patch, please check our release note.
Comments
-
Thanks for the information.
Could you give us more information about the following topic:
Non-Nebula VPN peers support IKEv2 and VPN Tunnel Interface for Azure static route support.
Thanks in advance.
0 -
Hi @Alfonso
Azure supports two types of VPNs:
- Policy based VPN : Requires IKEv1 and allows spoke sites to reach hub (Azure) site only. Supported by Nebula from day 1.
- Route based VPN: Requires IKEv2 and allows spoke sites to reach hub or other spoke sites. Supported by Nebula on last major release.
Nebula now supports IKEv2 and VTI creation to achieve the connection with Azure Route based VPN. You can find it in Security Gateway> Site-to-Site VPN> Non-Nebula VPN peers> IPSec policy.
Hope it helps you!
Bayardo
1 -
Hello @Alfonso
Sure, I'm working on it will update to FAQ once finish the handbook.?
1 -
Thank you both very much.
0 -
Tried the update on two NSG 50 and two NSG100.
Three have updated after a physical reboot, but one, despite two reboots, still remains on the previous version - any ideas?
0 -
Hi @CommsCo after rebooting the NSG, can you see statistic data being updated on NCC?
0 -
Yes, but still no update to the firmware.
0 -
0
-
Hello all,
Update the status, the root cause is because the DNS fail to resolve the firmware server domain name, the issue gone after change the DNS server IP. case closed☺️
/Chris
0
Categories
- All Categories
- 415 Beta Program
- 2.4K Nebula
- 144 Nebula Ideas
- 94 Nebula Status and Incidents
- 5.6K Security
- 237 USG FLEX H Series
- 267 Security Ideas
- 1.4K Switch
- 71 Switch Ideas
- 1.1K Wireless
- 40 Wireless Ideas
- 6.3K Consumer Product
- 247 Service & License
- 384 News and Release
- 83 Security Advisories
- 29 Education Center
- 10 [Campaign] Zyxel Network Detective
- 3.2K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 83 About Community
- 71 Security Highlight