Fixed. For edges with static IP network settings, portal now displays the updated NTP and DNS server settings as specified. Previously the settings were updated in the edge instance, but not in the portal. 
Fixed. In the "System Health" widget in the edge instance details page, the message now no longer wraps and is displayed in a single line. 
Fixed. For ECDN edges version 1.4.x, the portal now displays the IP address, instead of the "Waiting for DHCP server..." message.
Fixed. For ECDN edges version 1.4.x with static IP address settings, portal now displays the NTP and DNS values, instead of "Waiting for DHCP server..." message. 
New "Update remotely" option added for propagating configuration changes - only applicable for version 2.0 and higher of ECDN edge virtual appliance.
To propagate configuration changes from ECDN web portal to edge server instances, a new default option "Update remotely" has been added under "Select update method" on Step 4 "Complete setup" page. By choosing this option, the edge server instance can auto-download the new configuration settings from the ECDN backend and restart the service(s) in the edge. It can take up to 5 minutes to restart the affected services.
The option to manually update is still available, but we recommend you use the new "Updated remotely" method, as it eliminates the effort where you had to first download a virtual-cd image file (.ISO) containing the new configuration settings, attach it to the edge instance virtual machine, and reboot it to update the settings. If you do choose the manual update option, until the changes are successfully applied in the edge server instance, the portal will display a "Pending manual update" alert. You will have two options: You can either download the virtual-cd image file (.ISO), or you can discard the changes.
During the remote update method of propagating changes to the edge,the web portal now displays a new "Pending update" status (along with time when update started) in "System health" widget on edge server instance details page to indicate that configuration changes still need to be propagated to the remote edge server instance.
Recovery from errors during propagation of configuration settings.
In the web portal, after you make configuration changes, there was always the possibility that the new values could cause the edge server instance to lose network connectivity to the ECDN backend services. Example: Incorrect values for network settings like IP addresses, netmask, gateway, etc. among other reasons.
The web portal now detects delays (> 5 minutes) in getting acknowledgement from the remote edge server instance. When this timeout occurs, a "Pending update failure" alert is displayed in the portal, along with two options: You may discard the changes, or you may further edit the configuration settings.
Meanwhile, the remote edge server instance now reverts to the last known "working" values of the configuration settings, and attempts to reconnect to the ECDN backend.
New Remote assistance checkbox - Users now have control to enable/disable the VPN tunnel connection to ECDN backend.
When configuring an edge server instance, in Step 3 "Configure edge server" page, a new checkbox labelled "Enabled" has been added under the heading "Remote assistance". This checkbox now gives you the control to decide when to enable a VPN tunnel between the edge server instance and an ECDN backend service end point at terminator.ecdn-ustream.com.
When you need additional help in debugging and fixing your ECDN edge server instances, the support team can now remotely login and troubleshoot for you, once the VPN tunnel connection is established.
Once the troubleshooting session is complete, you can disable the checkbox and terminate the VPN tunnel connection. Prior to this release, all edge instances on boot established an ssh connection. Now you have control. The default value for remote assistance checkbox is "Enabled".
Note: To immediately establish the remote assistance VPN tunnel, you must choose the "Update remotely" update method on Step 4 "Complete setup" page.
Display the status of various service daemons:
In the edge server details page, in the Services section, we now display the status of all service daemons running in the edge server instance. The convention is:
Green: Service is enabled, and the service daemon is running.
Grey: Service has been disabled.
Red: Service is enabled, but there is problem with the service daemon. If this happens, restart the edge server. If that does not resolve the problem, contact our Support team.
The additions are:
Metrics service: Sends metrics to ECDN backend
SNMP polling: This is the SNMP agent service daemon.
Log forwarding: This service forwards system logs to your logging servers.
Remote assistance: This is the VPN tunnel service daemon. Note: This status does not reflect the state of the VPN tunnel connection.
More useful network related data about the edge server instance is now displayed on edge details page, and Step 4 "Complete setup" page of "Change configuration".
Under the Netmask, Gateway, DNS servers, NTP servers heading, instead of displaying "Not set" we now display "Waiting for data from server..." to indicate that we are waiting for the edge instance to upload its network configuration details.
All new configuration setting values are highlighted in a different color. The highlights are removed when the changes are successfully propagated to the edge server instance.
The "System health" widget that indicates the overall health of the edge server instance, now shows "Poor" status when the edge server instance is under load. It indicates that the edge server may be at capacity, and may need additional hardware resources. Under the "Performance" heading, a count of resources that have exceeded alert thresholds is displayed. Hovering over the count in the message brings up a popup that displays the details of which resources triggered the alert. The aggregate status is based on the values of the following resources and their corresponding thresholds. The status changes from healthy "Good" to "Poor" when:
Memory: When used memory exceeds 80% of the memory assigned to the edge server instance.
RootFS: When the usage exceeds 80% of configured capacity. Used by the caching service to store the video content.
Connections: When this number exceeds 2000. Used to indicate the number of player clients connected to this edge server instance.
Edge server list page:
When data is not received from the DHCP servers, the portal now displays "Waiting..." instead of the incorrect "127.0.0.1" placeholder.
The status of edge instances that do not report heartbeat is now shown in as a grey dot indicator.
Location details page:
In the "Edge servers" widget, we now display the health status details popup when your cursor hovers over the aggregate health status dot indicator in the "Health" column.
We have reduced the delay in the display of the performance status on the edge server instance details page, in the "System health" section at the top of the page.
Remote update configuration capability for propagating configuration changes.
Remote assistance checkbox to control the VPN tunnel connection.
Enhanced reporting of health status of various service daemons running inside the edge server instance.
Changed edge server instance health status heartbeat reporting frequency to 10 seconds (previous value was 20 seconds).
"Hardware resources" settings, and "Software and Configuration" settings are now reported periodically once every 60 seconds. Previously they were only reported once at boot time.
All edge server instances, by default, now automatically failover to IBM Cloud Video content origin servers, if there is an outage in any external 3rd party CDN vendor service.
Edge server instances now cache the DNS responses, thereby reducing the calls to customer's DNS servers, and makes the ECDN edge service more resilient against DNS outages. The TTL values received from your DNS servers are not changed.
Reduced the amount of memory set aside as buffer to enable caching service garbage collection. Previously this was a percentage of memory assigned to the virtual appliance. Now it is a fixed amount. With this change, more memory is available to cache the video content.
ECDN backend services
Fixed. Empty version strings of ECDN servers were not properly handled resulting in runtime errors. 
Added a new download.deepcaching.com backend endpoint to the ECDN backend. Edge server instances will download the configuration changes from this endpoint. Please whitelist outgoing HTTPS connections in your firewall towards this endpoint.
Edge instances undergoing reboots and configuration setting updates are not able to send heartbeat confirmation to the ECDN backend. When no heartbeats are received for > 2 minutes, that instance is now marked as unavailable to serve video traffic.
Fixed the defect where ECDN portal would not show any metrics in the "Player and buffering" graph for edge servers that had any upper case letters in their hostnames.
Portal should disable the "Update remotely" option under "Select update method" in Step 4 of "Change configuration" page, for offline edge instances. An edge instance is considered offline when ECDN backend does not receive heartbeat messages for > than 1 minute from it.