SG 4 S-Series Update #17

Important notes:

1. Service downtime is expected as there is a forced automatic reboot after applying this update. For HA setup, service downtime will be longer than usual as ID2 HA service is brought down while patching ID1, and ID2 will reboot to recover the HA service only after ID1 has booted up; so the service downtime for HA setup will be as long as the time it takes to reboot ID1, and ID2 will only be ready to serve as the backup node after ID2 has rebooted.

2. In the event snapshot restore is required due to error in applying this update, you may proceed to restore the snapshot to recover the system. However after booting up after the snapshot restore, you will not be able to pull this update from the online update centre. Please contact ANTlabs Support; we will assist in making the update available to you.

3. This update will abort and not apply any of the conversion steps if any/both of the following conditions are met:
      • At least one VLAN on the gateway points to a locally-managed Location
      • Bandwidth is not managed by ASP

To overcome the blocking conditions, you must ensure the following:
      • All desired Locations are ported to ASP
      • All desired VLANs are configured on ASP and synced down to the gateway
      • At the gateway GUI, remove all VLANs that are not required and that are pointing to locally-managed Locations
            ◦ Hint: all ASP-managed locations have ACS_ prefixed to their names, while locally-managed locations probably do not.
               You may open the Location listing page to ascertain: locally-managed ones can be selected for deletion,
               while ASP-managed ones cannot.
      • Bandwidth settings are managed from ASP. Visit gateway GUI > ANTlabs Service Platform > Sync Settings.

After removing the blocking conditions, you may resume to apply this update. 

Prerequisites:

• • Your ASP must be upgraded to at least version 2.0.1
• • All policy items including plans, portals, bandwidth and VLANs must be migrated to ASP before applying the update.
  • ◦ If the gateway is sharing bandwidth limit by device, ASP must be first upgraded to 2.0.2, and the sharing bandwidth limit on the cloud for this gateway set to by-device, before applying this update.

This update converts this gateway to v5 (the SG 5 software version) Update 2. Hereafter, the gateway will fetch the SG 5 (v5) updates.

The gateway will automatically reboot upon successful application of this update.

Known issue: after the gateway has been converted to v5, downstream login via facebook will not work. You would need to apply Update 3 to fix this.

Notes for HA setup:

For HA setup, the recommended steps are:

1. 1. Apply update to ID1 first. ID1 will reboot. Note: as the HA mechanism in ID2 is temporarily disabled, there will be service down-time as ID2 will not take over as the active node while ID1 is rebooting.
2. 2. Once ID1 is up, on ID1 web-admin GUI’s HA page, wait until you see Peer is connected.
3. 3. Fail over to ID2. Note: some GUI pages will load with incorrect values as ID2 software is not up-to-date yet.
4. 4. Apply update to ID2. ID2 will reboot and ID1, the preferred master, will become the active node again.

SG 4 S-Series Update Release No. 17
Release Date: 27 Sep 2022
Update File Name: 17.SG4000S_base-sys-bulk11-20220506-01.pkg
File Size: 49 MB
(md5: 150fc05d88bfcb074661de7f2df7d16a)

IG 4 S-Series, SG Express 5100 v4/5200 v4 Update #17

Important notes:

1. Service downtime is expected as there is a forced automatic reboot after applying this update. For HA setup, service downtime will be longer than usual as ID2 HA service is brought down while patching ID1, and ID2 will only reboot to recover heartbeat after ID1 has booted up; so the service downtime for HA setup will be as long as the time it takes to sequentially reboot the two machines, one after the other.

2. In the event snapshot restore is required due to error in applying this update, you may proceed to restore the snapshot to recover the system. However after booting up after the snapshot restore, you will not be able to pull this update from the online update centre. Please contact ANTlabs Support; we will assist in making the update available to you.

Prerequisites:

• • Your ASP must be upgraded to at least version 2.0.1
• • All policy items including plans, portals, bandwidth and VLANs must be migrated to ASP before applying the update.
  • ◦ If the gateway is sharing bandwidth limit by device, ASP must be first upgraded to 2.0.2, and the sharing bandwidth limit on the cloud for this gateway set to by-device, before applying this update.

This update converts this gateway to v5 (the SG 5 software version) Update 2. Hereafter, the gateway will fetch the SG 5 (v5) updates.

The gateway will automatically reboot upon successful application of this update.

Known issue: after the gateway has been converted to v5, downstream login via facebook will not work. You would need to apply Update 3 to fix this.

Notes for HA setup:

For HA setup, the recommended steps are:

1. 1. Apply update to ID1 first. ID1 will reboot. Note: as the HA mechanism in ID2 is temporarily disabled, there will be service down-time as ID2 will not take over as the active node while ID1 is rebooting.
2. 2. Once ID1 is up, on ID1 web-admin GUI’s HA page, wait until you see Peer is connected.
3. 3. Fail over to ID2. Note: some GUI pages will load with incorrect values as ID2 software is not up-to-date yet.
4. 4. Apply update to ID2. ID2 will reboot and ID1, the preferred master, will become the active node again.

IG 4 S-Series, SG Express 5100 v4/5200 v4 Update Release No. 17
Release Date: 13 Sep 2022
Update File Name: 17.IG4000S_base-sys-bulk11-20220506-01.pkg
File Size: 49 MB
(md5: 4f272d6c7ce18784785a251f2a3aee83)

IG 4 S-Series Update #16

This update includes the following fixes:

• – Fix gateway not being able to connect to with an ASP remote access session as gateway has failed host key verification.

• – Fix gateway losing connectivity to the cloud when a server domain resolves to a different IP address. Fix cloud communication module to use per-connection handle DNS caching.

• – Fix posting wrong bill amount to Micros 1700/2000/3700/4700/8700 PMS with respect to whole number currency settings.

IG 4 S-Series Update Release No. 16
Release Date: 22 July 2022
Update File Name: 16.IG4000S_base-sys-hotfix-20220719-01.pkg
File Size: 1.3 MB
(md5: afdc7298614ef53b63b0db0b14f5e5d4)

IG 4 S-Series Update #15

This update includes the following enhancements:
• New PMS Support – Micros 1700/2000/3700/4700/8700
• Account Printer (AP 3100) module upgrade
   ◦ Dynamic VLAN support based on user-entered VLAN ID or Room Number
      ▪ Note: for Room Number user entry support, Room to VLAN mapping must be configured.
• DHCP module upgrade
   ◦ Allow user to configure default and max lease durations for per-VLAN DHCP scope
   ◦ Support for captive-portal DHCP option
• Report module upgrade
   ◦ Enhanced CSV export for PMS guest, checkout and billing logs, supporting large number of log entries
• DNS service upgrade
   ◦ IP resolution retry logic for the domain of the website displayed for sites blocked with Security Module
   ◦ Enhanced stability in the presence of BADVERS responses to Extended Mechanisms for DNS (EDNS) queries with unsupported version numbers
• Enhanced PAN module stability
• Cloud-related enhancement
   ◦ Speed up time it takes for cloud-managed settings to apply to gateway
• Improve HA failover timing

This update includes the following fixes:

• Plan module fixes
   ◦ Allow Form (Temp) temp to edit its QoS class
   ◦ Fix issue where plan bandwidth limits do not take effect properly after plan is saved, while Advanced QoS module is not activated
   ◦ Add Plan page fix so left feature menu can expand properly
   ◦ Fix issue in Add Plan page where Volume input gets hidden when changing plan type from Stored Volume to Unlimited
• API fixes
   ◦ plan_update to allow plan sharing to drop from more than 1 to 1
   ◦ account_update to update dynamic VLAN properly
• Status collector module to get the right physical IP values for the network interfaces. This fixes the issue where ASP displays the wrong value for WAN physical IP.

IG 4 S-Series Update Release No. 15
Release Date: 5 May 2022
Update File Name: 15.IG4000S_base-sys-bulk10-20220317-01.pkg
File Size: 14 MB
(md5: 2c8f8b805603bfb048e41b24cac49465)

IG 4 S-SERIES UPDATE #14

This update updates the gateway’s default (ezxcess.antlabs.com) SSL certificate.  The new SSL certificate’s expiry is 7 April 2023, 23:59 GMT.

Note:

The current default SSL certificate will expire on 15 Apr 2022, 23:59:59 GMT.  This update should be applied before the expiry date, especially for sites that use the default SSL certificate to serve out downstream login pages with HTTPS enabled, to avoid errors or security warnings.

IG 4 S-Series Update Release No. 14
Release Date: 22 Mar 2022
Update File Name: 14.IG4000S_base-sys-hotfix-20220316-01.pkg
(md5: 036a54f739a92f46fee9abd0be33f56e)

IG 4 S-SERIES UPDATE #13

This update includes the following enhancements:

• •  Enhance graph security before web-admin login
• •  Update ASP server configurator component to handle leading/trailing spaces in received server name

This update carries the following bug fixes:

• •  Fix issue where command query and health report to ASP does not work when unlicensed gateway is left running for more than 10 days and then licensed
• •  Fix issue where user fails to connect to a gateway with Remote Access turned on at ASP if gateway reboots after it has processed the remote access request
• •  Fix issue in DHCP server where NAK is not issued when DHCP Request is received asking for an IP outside of the configured scope
• •  Optimize use of memory in report maintenance module to fix logs not being backed up or deleted when there are many log entries

IG 4 S-Series Update Release No. 13
Release Date: 16 Feb 2022
Update File Name: 13.IG4000S_base-sys-bulk09-20220111-01.pkg
(md5: f88b73ddf8f66100eadb88b759da4f68)