Release Notes for Cisco IC3000 Industrial Compute Gateway for Release 1.1.1
Remote Device Management Support
Reboot Button on Local Manager GUI
FND 4.5.1 and IOx 1.8 New Features
Obtaining Documentation and Submitting a Service Request
The following release notes support the Cisco IC3000. These release notes are updated to describe new features, limitations, troubleshooting, recommended configurations, caveats, and provide information on how to obtain support and documentation.
Release 1.1.1 adds in features to support IOx version 1.8 and FND version 4.5.1
This publication consists of the following sections:
■FND 4.5.1 and IOx 1.8 New Features
■ Caveats
Note : You must have a Cisco.com account to download the software.
New IC3000 devices will ship from the factory running version 1.1.1. Older devices that are running 1.0.1 and are upgrading to 1.1.1 need to consider how this affects their applications. Applications may need to be repackaged to run on IOx version 1.8 or they may fail to start.
The following features are included in this release.
Note : FND can support Virtual Machine deployment in tar and OVA format. Local Manager can only support Virtual Machine deployment in tar format.
The remote device management feature provides the user with the ability to enable or disable the remote access to the device configuration page from Cisco IOx Local Manager over a non-link local address.
More information can be found in the Cisco IC3000 Industrial Compute Gateway Deployment Guide.
The date, time and timezone can be set manually on the IC3000 via Local Manager (LM) GUI under the Device Configuration tab.
Note : This option is available via the LM in developer mode only. After modifying the date and time, the device should be reloaded to make sure that features depending on time and date function properly.
Previously, DNS configuration through only a DHCP server was supported. This is called auto DNS. Now there is a manual option to allow users to add DNS configuration. A user configured DNS configuration will co-exist with the configuration received through DHCP server, but given priority.
During the mode change from Auto to Manual and vice versa, DHCP on the interface will be not restarted. Therefore, no network disruption is introduced. Save and restore on a reload of user DNS configuration is supported.
■This feature is exposed to the user through FND and LM.
■3 name server entries total can be added either by the user or the DHCP server. If a user adds all 3 entries, then entries added from the DHCP server will not be added to the configuration.
■In the case where 3 name server entries added by the user are deleted, there may be no name server in the configuration. DHCP lease time will decide when entries by the DHCP server are updated again.
■The same assumptions are true for domain and search directives.
In a manual NTP configuration, the user can configure the NTP servers. The user configuration co-exists with the NTP configuration received by DHCP server.
The following NTP options can be set by the user:
■Polling interval includes max and min poll.
■NTP Authentication - User provides the id, type and value of the keys.
The device can be returned to the original factory configuration by using the reset button. The reset button is a small button accessed through a pinhole located on the front of the device. For the location, see the IC3000 Hardware Configuration Guide.
■Press 10 to 15 seconds - Device is reloaded.
■Press 30 to 35 seconds - All user configurations are removed and device is reloaded.
■Press 60 to 65 seconds - All user configurations are removed, all images are cleared except for the factory image, and the device is reloaded with the factory image.
FND 4.5.1 New Features shows details about the new features in FND release 4.5.1. For additional information see the Release Notes for IoT Field Network Director, Release 4.5.x
Table 1 FND 4.5.1 New Features
Provides a step-by-step path on how to configure specific items within the FND User Interface. Directions appear in pop-up windows that navigate you thru the configuration process. Once you are on the desired configuration pages (noted below), select Guided Tours from the User drop-down menu, upper-right hand corner, to display a window with the available tours. ■Add Devices (DEVICES > FIELD DEVICES) ■Device Configuration Group Management Note: The Guided Tour feature must be enabled by the first-time FND root user that logs into the FND system before you can use the feature. |
|||
Domain Name Support (DNS) Support in the IC3000 Local Manager (LM) User Interface |
You can configure and manage the following items for a DNS server in the IC3000 LM user interface: |
||
Oracle RAC supports clustering of multiple Oracle databases to appear as one to support high availability in the network. |
Real Application Clusters Administration and Deployment Guide |
||
On the Endpoint Inventory chart and Endpoint states Over Time Chart, there is a new state: Registering. |
|||
Zero Touch Deployment Enhancements for the Router Template for Greater Error Handling |
Error handling enhancements for the router template include: ■Automatic import of a SUDI certificate upon FND startup ■Error handling checks and validation of the following items: Bootstrap and Configuration templates, ZTD properties and Keystore ■Generating a sample csv file from the template ■Saving template version history ■A Tour wizard which validates configurations and settings used for bootstrapping |
The following are the new features for Cisco IOx Release 1.8.0. For additional information see Release Notes for Cisco IOx Release 1.8.0.
■All /myapps and /localapps APIs have been deprecated and a single unified API /apps has been provided for all apps related operations.
■Support to add authorized devices into Fog Director.
■Subscription for alerts call back feature.
■Support for installing any version of an app on a set of devices from Fog Director.
■App health monitoring inside containers.
■New appearance of apps dashboard on Fog Director.
■Support for importing ova files into Fog Director.
■Support for installing docker apps from Fog Director and Local Manager.
■Support for installing docker apps from the docker hub without any additional IOx metadata.
The following documentation is available:
■All of the Cisco IC3000 documentation can be found here:
https://www.cisco.com/c/en/us/support/routers/3000-series-industrial-compute-gateways/tsd-products-support-series-home.html
https://www.cisco.com/c/en/us/support/cloud-systems-management/iot-field-network-director/tsd-products-support-series-home.html
■Cisco IOx Documentation is found here:
https://www.cisco.com/c/en/us/support/cloud-systems-management/iox/tsd-products-support-series-home.html
Caveats describe unexpected behavior in Cisco IOS releases. Caveats listed as open in a prior release are carried forward to the next release as either open or resolved.
Caveats listed below are related to the IC3000 and do not include Field Network Director or IOx.
FND release notes are found here:
https://www.cisco.com/c/en/us/support/cloud-systems-management/iot-field-network-director/products-release-notes-list.html
IOx release notes are found here:
https://www.cisco.com/c/en/us/support/cloud-systems-management/iox/products-release-notes-list.html
Note : You must have a Cisco.com account to log in and access the Cisco Bug Search Tool. If you do not have one, you can register for an account.
For more information about the Cisco Bug Search Tool, see the Bug Search Tool Help & FAQ.
On re-installation of an application, FD sends the same runtime option which caused the failure during first try.
Conditions : Trigger docker app installation on a device with invalid/ black listed runtime options. For example: --name Application deploy failed with "Error while changing app state:App Activation error: Given option:'--name' is black listed!" Trigger a re-installation on the same failed device with the correct run time option -p 5201:5201. The browser console shows that ? action payload has correct run time option which was used.
Workaround #1 : Uninstall the application and install again with the correct runtime options. The list of run time options that are not supported can be found here:
https://developer.cisco.com/docs/iox/#!platform-information/cisco-ic3000-gateway
Workaround #2 : Retry and remove forever, then trigger the application installation with the correct run time options.
Factory reset operation fails to clean up and delete CAF partitions.
Symptoms : Pressing the factory reset button fails to delete applications. This occurs when Release 1.1.1 is not a factory image, or devices which were running a previous version of Release 1.0.1 as a factory image.
Workaround : Perform factory reset operation again when the device returns to 1.0.1 image by pressing the reset for more than 10 seconds.
For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html.
Subscribe to What’s New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.