Release Notes for IoT Field Network Director, Release 4.9.x
These release notes contain the latest information about using the user interface for IoT Field Network Director (IoT FND), Release 4.9.x to configure and manage IPv6 mesh endpoints, Cisco 1000 Series Connected Grid Routers (CGR1120 or CGR1240), Cisco 800 Series Integrated Services Routers (C800), Cisco LoRaWAN IXM Gateway, Cisco 500 WPAN Industrial Routers (IR500), Cisco 5921 (ESR5921) Embedded Service Routers, and Cisco 800 Series Industrial Integrated Services Routers (IR807, IR809, and IR829), Cisco Industrial Compute Gateway IC3000, Cisco 1101 Integrated Services Router, and Cisco Catalyst IR8100 Heavy-Duty Series Router.
IoT Field Network Director (IoT FND) is a software platform that helps to enable a clear separation between communications network management and operational applications such as distribution management systems, outage management systems, and meter data management in utilities. Use the software to manage a multi-service network of routers or a combination of routers and endpoint devices deployed with end-to-end security for your specific use case.
IoT FND is highly secure, scalable, and modular. Its pluggable architecture can enable network connectivity to a multi-vendor ecosystem of legacy and next-generation IoT devices.
Cisco IoT FND Documentation
Listed below are the user documents that support this release:
-
Cisco IoT FND Deployment on an Open Virtual Appliance, VMware ESXi 5.5/6.0/6.5
-
Cisco IoT Field Network Director Installation Guide-Oracle Deployment, Releases 4.3.x and Later
Please refer to the Cisco IoT Field Network Director data sheet for an extensive list of the product capabilities and the required licenses to support specific platforms management by the FND application.
![]() Note |
IoT FND was previously named Connected Grid Network Management System (CG-NMS) for releases 2.x and 1.x. |
Conventions
This document uses the following conventions.
Conventions | Indication |
---|---|
bold font |
Commands and keywords and user-entered text appear in bold font. |
italic font |
Document titles, new or emphasized terms, and arguments for which you supply values are in italic font. |
[ ] |
Elements in square brackets are optional. |
{x | y | z } |
Required alternative keywords are grouped in braces and separated by vertical bars. |
[ x | y | z ] |
Optional alternative keywords are grouped in brackets and separated by vertical bars. |
string |
A nonquoted set of characters. Do not use quotation marks around the string or the string will include the quotation marks. |
courier font |
Terminal sessions and information the system displays appear in courier font. |
< > |
Nonprinting characters such as passwords are in angle brackets. |
[ ] |
Default responses to system prompts are in square brackets. |
!, # |
An exclamation point (!) or a pound sign (#) at the beginning of a line of code indicates a comment line. |
![]() Note |
Means reader take note. Notes contain helpful suggestions or references to material not covered in the manual. |
![]() Caution |
Means reader be careful. In this situation, you might perform an action that could result in equipment damage or loss of data. |
![]() Warning |
IMPORTANT SAFETY INSTRUCTIONS |
Provided for additional information and to comply with regulatory and customer requirements.
About Cisco IoT FND
The IoT Field Network Director (IoT FND) is a software platform that helps to enable a clear separation between communications network management and operational applications such as distribution management systems, outage management systems, and meter data management in utilities.
Through the browser-based interface, use the software to manage a multi-service network of routers or a combination of routers and endpoint devices such as:
-
The IP 67-rated Cisco Catalyst IR8100 Heavy-Duty Series routers is a modular, secure, rugged and outdoor router that is suitable for harsh physical environments. It has multiple WAN (LTE, LTE-Advanced, LTE Advanced Pro, 5G Sub-6GHz1, RJ45/SFP Ethernet) and storage options. The router supports wireless and wired connectivity such as 5G, public, or private LTE, Wi-SUN, LoRaWAN, and has more connectivity options making it more adaptable. It runs on Cisco IOS XE and Cisco IOS XE provides both autonomous and controller (SD-WAN) mode support.
-
Cisco 1101 Series Integrated Services Routers (ISRs) with Cisco IOS XE Software combine Internet access, comprehensive security, and wireless services (LTE Advanced 3.0 wireless WAN and 802.11ac wireless LAN) in a single, high-performance device. The Cisco 1101 Series ISRs are well-suited for deployment as Customer Premises Equipment (CPE) in enterprise branch offices, in service provider managed environments as well as smaller form factor and M2M use cases.
-
Cisco 800 Series Industrial Integrated Services Routers (IR800s) are ruggedized small-form factor cellular routers for mobile/vehicle applications. IR829 includes Wi-Fi providing connectivity in non-carpeted IT spaces, industrials, utilities, transportation, infrastructure, industrial M2M application, asset monitoring, Smart Grid, and utility applications. These devices are referred to as FARs in this document and identified by product ID (for example, IR800) on the Field Devices page. You can use IoT FND to manage the following IR800 models: IR809 and IR829.
-
Cisco 800 Series Integrated Services Routers (C800s) are used in most networks as edge routers or gateways to provide WAN connectivity (cellular, satellite over Ethernet, and Wi-Fi) to an end device (energy-distribution automation devices, other verticals such as ATMs, and mobile deployments). These devices are referred to as FARs in this document and identified by product ID (for example, C800 or C819) on the Field Devices page.
-
Cisco 500 Series Wireless Personal Area Network (WPAN) Industrial Routers (IR500) supply RF mesh connectivity to IPv6 and serial Internet of Things (IoT) devices (for example, recloser control, cap bank control, voltage regulator controls, and other remote terminal units).
![]() Note |
CGRs, C800, IR800s, IR500s and other types of mesh endpoint devices can coexist on a network, but cannot be in the same device group (see Creating Device Groups and Working with Mesh Endpoint Firmware Images) or firmware management group. Refer to the following sections in the IoT Field Network Director User Guide for more information on: “Creating Device Groups”, “Working with Mesh Endpoint Firmware Images” and “Configuring Firmware Group Settings”. |
-
The Cisco Wireless Gateway for LoRaWAN (IXM-LPWA-800, IXM-LPWA-900) can be a standalone product that connects to Ethernet switches or routers or connects to LAN ports of the Cisco 800 Series Industrial Integrated Services Routers. This gateway can be configured as a radio interface of the Cisco Industrial Routers 809 and 829. One or multiple gateways are connected to the LAN port(s) of the IR809 or IR829 via Ethernet or VLANs with encrypted links. Through this configuration, it provides LoRaWAN radio access while the IR809 or IR829 offer backhaul support for Gigabit Ethernet (electrical or fiber), 4G/LTE, or Wi-Fi.
-
Cisco Interface Module for LoRaWAN is an extension module for the industrial routers, Cisco IR809 and IR829, and serves as a carrier-grade gateway for outdoor deployments. The module provides unlicensed low-power wide area (LPWA) wireless connectivity for a range of Internet of Things (IoT) use cases such as asset tracking, water and gas metering, street lighting, smart parking/building/agriculture, and environment monitoring. There are two models supported, which are differentiated by their band support (863-870 MHz ISM or 902-928 MHz ISM). The module is identified by product ID (for example, IXM-LORA-800-H-V2).
-
Cisco 800 Series Access Points are integrated with C800 and IR829 platforms. These access points are referred to as FARs in this document and identified by product ID (for example, AP800).
-
Cisco ASR 1000 Series Aggregation Services Routers (ASRs), Cisco 8000 Series Routers, and Cisco 4000 Series Integrated Service Routers (ISRs) are referred to as head-end routers or HERs in this document.
-
Cisco IPv6 RF mesh endpoints (smart meters and range extenders).
![]() Note |
CGRs, C800, IR800s, IR500s, and other types of mesh endpoint devices can coexist on a network, but cannot be in the same device group or firmware management group. |
The software features enterprise-class fault, configuration, accounting, performance, and security (FCAPS) functionality, as defined in the OSI Network Management reference model.
Cisco IoT FND Features and Capabilities
-
Configuration Management — Cisco IoT FND facilitates configuration of large numbers of Cisco FAR, HER, gateways, and endpoints. Use Cisco IoT FND to bulk-configure devices by placing them into configuration groups, editing settings in a configuration template, and then pushing the configuration to all devices in the group.
-
Device Management — Cisco IoT FND displays easy-to-read tabular views of extensive information generated by devices, allowing you to monitor your network for errors. Cisco IoT FND provides integrated Geographic Information System (GIS) map-based visualization of FAN devices such as routers and smart meters.
-
Firmware Management — Cisco IoT FND serves as a repository for Cisco CGR, Cisco C800s, Cisco IR800, IR500, and mesh endpoint firmware images. Use Cisco IoT FND to upgrade the firmware on groups of similar devices by loading the firmware image file onto the Cisco IoT FND server, and then uploading the image to the devices in the group. Once uploaded, use IoT FND to install the firmware image directly on the devices.
-
Zero Touch Deployment — Ease of deployment at scale with Zero-Touch Deployment (ZTD) of gateways and routers.
-
Tunnel Provisioning — Protects data exchanged between Cisco ASRs and Cisco CGRs and C800s, and prevents unauthorized access to Cisco CGRs to provide secure communication between devices. Cisco IoT FND can execute CLI commands to provision secure tunnels between Cisco CGRs, Cisco C800s, Cisco IR800s and Cisco ASRs. Use Cisco IoT FND to bulk-configure tunnel provisioning using groups.
-
IPv6 RPL Tree Polling — The IPv6 Routing Protocol for Low-power and Lossy Networks (RPL) finds neighbors and establishes routes using ICMPv6 message exchanges. RPL manages routes based on the relative position of the endpoint to the CGR that is the root of the routing tree. RPL tree polling is available through the mesh nodes and CGR periodic updates. The RPL tree represents the mesh topology, which is useful for troubleshooting. IoT FND maintains a periodically updated snapshot of the RPL tree.
-
Dynamic Multipoint VPN and Flex VPN — For Cisco C800 devices and Cisco IR800 devices, DMVPN and Flex VPN do not require IoT FND to apply device-specific tunnel configuration to the HER during tunnel provisioning. HER tunnel provisioning is only required for site-to-site VPN tunnels.
-
Dual PHY Support — IoT FND can communicate with devices that support Dual PHY (RF and PLC) traffic. IoT FND identifies CGRs running Dual PHY, enables configuration to masters and slaves, and collects metrics from masters. IoT FND also manages security keys for Dual PHY CGRs. On the mesh side, IoT FND identifies Dual PHY nodes using unique hardware IDs, enables configuration pushes and firmware updates, and collects metrics, including RF and PLC traffic ratios.
-
Device Location Tracking — IoT FND displays real-time location and device location history for CGR 1000, C800, IR1101, IR8100, IR800, and N2450 devices.
-
Diagnostics and Troubleshooting — The IoT FND rule engine infrastructure provides effective monitoring of triage-based troubleshooting. Device troubleshooting runs on-demand device path trace and ping on any CGR, Cisco C800, Cisco IR800, range extender, or meter (mesh endpoints).
-
High Availability — To ensure uninterrupted network management and monitoring, you can deploy the Cisco IoT FND solution in a High Availability (HA) configuration. By using clusters of load-balanced IoT FND servers and primary and standby IoT FND databases, Cisco IoT FND constantly monitors the health of the system, including connectivity within clusters and server resource usage. If a server cluster member or database becomes unavailable or a tunnel fails, another takes its place seamlessly. Additionally, you can add reliability to your IoT FND solution by configuring redundant tunnels between a Cisco CGR and multiple Cisco ASRs.
-
Power Outage Notifications — Cisco Resilient Mesh Endpoints (RMEs) implement a power outage notification service to support timely and efficient reporting of power outages. In the event of a power outage, CGEs perform the necessary functions to conserve energy and notify neighboring nodes of the outage. FARs relay the power outage notification to IoT FND, which then issues push notifications to customers to relate information on the outage.
-
Audit Logging — Logs access information for user activity for audit, regulatory compliance, and Security Event and Incident Management (SEIM) integration. This simplifies management and enhances compliance by integrated monitoring, reporting, and troubleshooting capabilities.
-
North Bound APIs — Eases integration of existing utility applications such as outage management system (OMS), meter data management (MDM), trouble-ticketing systems, and manager-of-managers.
-
Role-Based Access Controls — Integrates with enterprise security policies and role-based access control for AMI network devices.
-
Event and Issue Management — Fault event collection, filtering, and correlation for communication network monitoring. IoT FND supports a variety of fault-event mechanisms for threshold-based rule processing, custom alarm generation, and alarm event processing. Faults display on a color-coded GIS-map view for various endpoints in the utility network. This allows operator-level custom, fault-event generation, processing, and forwarding to various utility applications such as an outage management system. Automatic issue tracking is based on the events collected.
New Features in Cisco IoT FND 4.9.1
The table summarizes the new and updated features included in this release and tells you where they are documented.
![]() Important |
IoT FND 4.9.1 release is only for FND+Postgres+Influx OVA deployments. |
Features |
Description |
||
---|---|---|---|
Postgres 12.12 rpm upgrade |
The Postgres 12.12 rpm upgrade is automated in IoT FND 4.9.1 release and based on the OS installed, it will update the libraries. Upgrading IoT FND OVA . |
||
Postgres scale support upto 15K |
Starting with this release, IoT FND OVA supports 15K routers with Postgres/Influx DB. For more information on the specifications, refer to Postgres-Only Deployments. |
||
Obfuscate password except root and user with permission "Manage Device Credentials" |
The Show Device Password option in the User Preferences setting allows the root user and the user with permission "Manage Device Credentials" to show or hide the password in the Device Details page. For more information, refer to Setting Preferences for the User Interface. |
||
Support for device firmware upgrade/downgrade during PnP workflow |
|
||
Configurable tunnel reprovisioning timeout added to cgms.properties file. |
Tunnel reprovisioning jobs get timed out in 240 minutes. However, if necessary, you can configure the tunnel reprovisioning timeout value in the cgms.properties file:
|
New Features in Cisco IoT FND 4.9.0
The table summarizes the new and updated features that are included in this release and tells you where they are documented in the User Guide.
Features |
Description |
---|---|
This feature supports multi-tenancy where the user can subscribe/unsubscribe for events or outages for a particular domain. The following APIs use domain as a parameter to support for multi-tenancy:
|
|
IoT FND manages the following C8000 device types:
|
|
IoT FND provides the latitude and longitude information for N2450 using the GPS coordinates. The geo-tracking information appears on the Device Listing and Device Details pages of N2450. |
System Requirements
The following table lists the hardware and software versions associated with this release.
Component | Minimum Hardware Requirement | Software Release Requirements | ||||||
---|---|---|---|---|---|---|---|---|
Cisco IoT FND application server (or comparable system that meets the hardware and software requirements) |
|
|
||||||
Cisco IoT FND TPS proxy |
|
|
||||||
Database server for IoT FND Scalable to 25 routers/10,000 endpoints with minimum hardware requirement. See Resource Management Guidelines for additional scale sizes. |
|
|
||||||
Cisco IoT FND—RA |
|
|
||||||
Cisco IoT FND Client |
The client must meet the following minimum requirements to connect to the IoT FND application server and view IoT FND displays:
|
Supported browsers:
|
||||||
Cisco Prime Network Registrar (used as a DHCP server) |
Server must have the following minimum requirements:
|
The following software environment must exist before installing Prime Network Registrar:
|
||||||
Hardware Security Module (HSM) |
Luna SA appliance, with client software installed on the IoT FND application servers |
Luna SA appliance:
Luna SA client software:
|
||||||
Software Security Module (SSM) |
|
|
![]() Note |
If deploying a IoT FND server cluster, all nodes in the cluster should run on similar hardware. Additionally, all nodes must run the same version of IoT FND. |
Systemctl Command Support for RHEL Version 8.x
If the RHEL version is 8.x or later, then use systemctl
command instead of the service
command as given in the table.
RHEL Version |
Command |
---|---|
8.x |
|
7.x |
|
RHEL Version |
Command |
---|---|
8.x |
|
7.x |
|
RHEL Version |
Command |
---|---|
8.x |
|
7.x |
|
RHEL Version |
Command |
---|---|
8.x |
|
7.x |
|
Supported Device Types in IoT FND
The following device types are supported in the IoT FND:
Device Types | Software Release Requirements | ||
---|---|---|---|
FAR |
|||
1. Cisco IR8140 Heavy-Duty Series Router |
Cisco IOS XE Release 17.09.01 |
||
2. Cisco 1101 Series Industrial Integrated Services Routers (IR1101) |
Cisco IOS XE Release 17.09.01 |
||
3. Cisco CGR1000 Series Connected Grid Router (CGR1120 and CGR1240) |
Cisco IOS Release 15.9(3)M6 |
||
4. Cisco 5921 (ESR5921) Embedded Services Routers |
Cisco IOS Release 15.8(3)M2 |
||
5. Cisco 800 Series Industrial Integrated Services Router (IR800) |
Cisco IOS Release 15.9(3)M6 |
||
6. Cisco 800 Series Integrated Services Router (C800) |
Cisco IOS Release 15.8(3)M2 |
||
7. Cisco 800 Series Access Points (AP800) are integrated with C800 and IR829 platforms. |
|
||
HER | |||
1. Cisco 8000 Series Routers |
|
||
2. Cisco ASR 1001 or 1002 Aggregation Services Router (ASR) serving as a head-end router |
Cisco IOS XE Release 16.9.3 for Flex tunnels (IOS) |
||
3. Cisco 4000 Series Integrated Service Router (ISR) |
|
||
|
|||
Compute Gateway | |||
Cisco IC3000 Industrial Compute Gateway |
Firmware version —1.4.1 |
||
Mesh Endpoints |
|
||
Cisco 500 Series Wireless Personal Area Network (WPAN) Industrial Routers (IR500) |
The firmware versions supported for the following router series are:
|
||
LoRaWAN | |||
Long Range Wide Area Network (LoRaWAN) Interface Module for Cisco 800 Series Industrial Integrated Services Routers (IR800) |
LoRa/IXM-LPWA—Firmware version is 2.3.0 |
Resource Management Guidelines
Virtual machine (VM) configuration workload characterization is important. When using multiple VMs on the same physical host, allocate resources so that individual VMs do not impact the performance of other VMs. For example, to allocate 4 VMs on a 8-CPU host, do not allocate all 8 CPUs to ensure that one (or more) VM does not use all resources.
Oracle Database Server
The following table lists example Oracle database server usage profiles for important resource parameters such as CPU, memory, and disk space.
Nodes
(Routers/Endpoints) |
CPU
(Virtual Cores) |
Memory
(RAM GB) |
Disk Space
(GB) |
---|---|---|---|
25/10,000 |
2 |
16 |
100 |
50/50,000 |
4 |
16 |
200 |
500/500,000 |
8 |
32 |
500 |
1,000/1,000,000 |
12 |
48 |
1000 |
2,000/2,000,000 |
16 |
64 |
1000 |
6,000/6,000,000 |
20 |
96 |
1000 |
8,000/8,000,000 |
32 |
160 |
2000 |
IoT FND Application Server
The following lists example IoT FND Application server usage profiles for important resource parameters such as CPU, memory, and disk space.
Nodes
(Routers/Endpoints) |
CPU
(Virtual Cores) |
Memory
(RAM GB) |
Disk Space
(GB) |
---|---|---|---|
25/10,000 |
2 |
16 |
100 |
50/50,000 |
4 |
16 |
200 |
500/500,000 |
4 |
16 |
250 |
1,000/1,000,000 |
8 |
16 |
250 |
2,000/2,000,000 1 |
8 |
16 |
500 |
5,000/5,000,000 1 |
8 |
16 |
500 |
6,000/6,000,000 |
8 |
16 |
500 |
8,000/8,000,000 |
8 |
32 |
500 |
-
Clustered installations.
![]() Note |
RAID 10 is mandatory for deployments of 2 million endpoints and above. |
![]() Note |
Four application servers are recommended for 8,000/ 8,000,000 routers/endpoints. |
![]() Note |
IoT FND can process approximately 90 CSMP packets per second per node. |
For Router Only Deployments
Information in the following tables is relevant to Router Only deployments.
Oracle-Only Deployments
Nodes
IR800/LoRa Modules |
CPU
(Virtual Cores) |
Memory
(RAM GB) |
Disk Space
(GB) |
---|---|---|---|
10,000/30,000 |
4 |
24 |
100 |
Nodes
IR800/LoRa Modules |
CPU
(Virtual Cores) |
Memory
(RAM GB) |
Disk Space
(GB) |
---|---|---|---|
10,000/30,000 |
6 |
32 |
500 |
Postgres-Only Deployments
Routers | CPU
(Virtual Cores) |
Memory
(RAM GB) |
Disk Space
(GB) |
---|---|---|---|
15,000 |
16 |
48 |
500 |
OpenSSH Version
Since IoT FND is supported on a variety of Red Hat Enterprise Linux (RHEL) 5 Update releases, the OpenSSH version that comes with a given release might be an older version with known security holes. Consequently, we recommend ensuring that OpenSSH on the RHEL IoT FND server is up to date. On initial installation, upgrade the OpenSSH package in the IoT FND server to RHEL version 8.6.
Documentation Updates
Cisco IoT Field Network Director Post-Installation Guide, Release 4.3.x and later — This guide is no longer available as the chapters of this guide are moved to the following guides:
-
Managing Tunnel Provisioning — Cisco IoT Field Network User Guide, Release 4.8.x
-
Managing High Availability Installations — Cisco IoT Field Network Director Installation Guide - Oracle Deployment, Releases 4.3.x and Later
IoT FND Release Upgrade Matrix
This section provides IoT FND upgrade information based on the current and target releases.
Target Release | You Can Upgrade to the Target Release (Left column) from the Following Releases (Right Column) | |||
---|---|---|---|---|
4.9.2-4
|
4.9.0-62 4.8.1-72 4.8.0-130 (ISO), 4.8.0-133 (OVA) |
4.7.2-8 4.7.1-60 4.7.0-100 |
||
4.9.1-8
|
4.9.0-62 4.8.1-72 4.8.0-130 (ISO), 4.8.0-133 (OVA) |
4.7.2-8 4.7.1-60 4.7.0-100 |
||
4.9.0-62 |
4.8.1-72 4.8.0-130 (ISO), 4.8.0-133 (OVA) |
4.7.2-8 4.7.1-60 4.7.0-100 |
||
4.8.1-72 |
4.8.0-130 (ISO), 4.8.0-133 (OVA) |
4.7.2-8 4.7.1-60 4.7.0-100 |
||
4.8.0-130 (ISO) 4.8.0-133 (OVA) |
4.7.2-8 4.7.1-60 4.7.0-100 |
4.6.2-16 4.6.1-61 |
||
4.7.2-8 |
4.7.1-60 4.7.0-100 |
4.6.1-61 |
||
4.7.1-60 |
4.7.0-100 |
4.6.1-61 |
||
4.7.0-100 |
4.6.1-61 |
4.5.1-11 |
||
4.6.1-61 |
4.5.1-11 |
4.4.4-9 4.4.3-4 4.4.2-11 4.4.1-10 4.4.0-79 |
||
4.5.1-11 |
4.4.2-11 4.4.1-10 4.4.0-79 |
4.3.2-7 4.3.1-7 4.3.0-133 |
||
4.4.xxx |
4.3.1-7 4.3.0-133 |
4.2.0-123 |
||
4.3.xxx |
4.2.0-123 |
4.1.1-64.1.0-257 |
||
4.2.0-123 |
4.1.0-257 |
4.0.0-299 |
![]() Note |
Sometimes, firmware images are not displayed in GUI while upgrading the IoT FND from earlier versions to 4.8.x. To resolve this issue, we recommend that you clear the browser cache. |
![]() Note |
Target Release versions allow upgrades from the two prior major releases and its maintenance releases unless the maintenance release was released after the target version. |
If the current version is not within the two prior versions of the target release, then multiple upgrade hops are required to get to the target release. Use the table above to plan the upgrade paths.
The system must be upgraded to each intermediate version(s) followed by starting the IoT FND application and allowing it to stabilize. This allows the IoT FND application to perform necessary modifications of databases during startup. The ability to log on to IoT FND is the best indication of completion of these startup modifications.
Example:
If your network is running IoT FND 4.4.0-79 and your Target Release is 4.8.0-130, then your best upgrade path is:
-
Upgrade 4.4.0-79 to 4.6.1-61 and then upgrade to 4.7.0-100.
Recommended steps for the multi-hop upgrade are:
-
Backup IoT FND 4.4.0-79 database.
-
Perform an upgrade to IoT FND 4.6.1-61 using the upgrade instructions in the Installation Guide.
-
Start IoT FND 4.6.1-61 and login to the IoT FND user interface and perform a quick sanity check.
-
Stop IoT FND 4.6.1-61 services.
-
Backup IoT FND 4.6.1-61 database.
-
Upgrade to IoT FND 4.8.0-130 using the upgrade instructions in the Installation Guide.
-
Start IoT FND 4.8.0-130 and log into the GUI.
Hardware Security Module (HSM) Upgrade Table
For Cisco IoT-FND Release 4.6.2 and greater, within the IoT-FND image bundle, there are new subfolders for the jar and API files: /opt/cgms/safenet/LunaX.
![]() Note |
LunaProvider.jar and libLunaAPI files contain the HSM library patch for the defect CSCvs83557. |
The table below lists the HSM client versions that are tested and recommended for the corresponding Cisco IoT FND software versions. However, FND application software is backward compatible with HSM client versions. For example, FND version 4.7.1 is compatible with older versions of HSM client such as 5.4, 6.3.
HSM Upgrade TableFND Software Release | HSM Client | HSM Software |
---|---|---|
4.7.1 to 4.9.x |
10.2 |
7.4 |
4.6 |
7.3 with software patch |
7.4 |
4.5 |
7.3 with software patch |
7.3 |
4.4 |
7.3 with software patch |
7.0 |
Install SUDI Certificate with 2099 expiry in FND and TPS keystore
SUDI 2099 has to be installed in FND and TPS for compatibility with newer versions of images for devices.
Limitations and Restrictions
Cisco recommends that you review this section before you begin working with IoT FND. These are known limitations, and there is not always a workaround for these issues. Some features might not work as documented, and some features might be affected by recent changes to the software.
Feature | IoT FND Releases | Upgrade Impact | ||
---|---|---|---|---|
LDevID: Auto-Renewal of Certs and Saving Configuration |
4.9.1 |
By default, this feature is disabled. However, if required, you can enable the feature. For information on enabling the feature, refer to LDevID: Auto-Renewal of Certs and Saving Configuration. |
||
4.9.0 |
By default, this feature is disabled. Workaround: We recommend the users "NOT to enable" this feature because it could break the FAR connectivity with FND. |
|||
CSMP-Request tool support for L+G endpoints |
4.9.0 onwards |
Owing to L+G platform limitation, CSMP-Request tool fails for L+G endpoints when passing single TLV. Workaround: We recommend that you use minimum two TLVs in the CSMP-Request tool for the L+G endpoints. |
||
Firmware Upgrade during PnP |
4.4 to 4.9.0 |
The PnP workflow supports device upgrade only if the target image version is higher than the running (current) image version. If the target image runs the same or lower version, then the device upgrade is skipped during the PnP workflow.
|
||
External DHCP support for tunnel provisioning |
Applicable for all IoT FND releases |
External DHCP is not supported for tunnel provisioning in the Postgres-OVA deployment. |
Caveats
This section presents the open and resolved caveats in Cisco IoT FND releases and information on using the Bug Search Tool to view details on those caveats.
Open Caveats
The section lists the open caveats in Cisco IoT FND Release 4.9.x.
Caveat ID | Description |
---|---|
Incorrect CRC error message still displayed when the bootstrap state is 'Installing Firmware Image'. | |
Post PnP reset, the "auto-enroll 90 regenerate" is not seen in the LDevID trustpoint. |
|
FND cpu spikes if "router with top Ethernet and cellular BW" dashlet added in the dashboard. |
Caveat ID | Description |
---|---|
IR8140 Dual WPAN refresh mesh key values are not shown in UI. |
|
LDevID autorenewal related CLIs should not be applied after "Reset bootstrap state". |
|
[PG - OVA] Failed to download log in FND UI |
Resolved Caveats
This section lists the resolved caveats in Cisco IoT FND Release 4.9.x.
Caveat ID | Description | ||
---|---|---|---|
Adding the support of GPS onboard on IR8140 as part of ODM file. |
|||
FND does not update missing ODM file during metric update. Workaround: Refer to the Troubleshooting Steps to Upload ODM File.
|
Caveat ID | Description |
---|---|
PnP and upgrade or downgrade during PnP fails from 17.7.1 due to missing SUDI2099. |
|
Field Area Router bootstrap with target firmware fails. |
|
FND: Vacuum not releasing space as it is supposed to. |
|
FND: Indexes from dead tuples not vacuumed. |
|
Vacuuming is not happening properly because of idle in transactions postgres queries. |
|
[PG - OVA] Failed to download log in FND UI. |
|
LDevID autorenewal related CLIs should not be applied after "Reset bootstrap state". |
Caveat ID | Description |
---|---|
IR8140 WPAN and CAM Refresh mesh key flow is not working during registration. |
|
FND is not refreshing IR8140 router mesh key when it reaches the Key Refresh Time. |
|
FND 4.8.1 OVA: java.lang.integer cannot be cast to java.math.BigDecimal. |
|
Upgrade from FND OVA 4.5.1 to higher causes userpropertyTypes.xml file and values to be overwritten. |
Accessing the Bug Search Tool
You can use the Bug Search Tool to find information about caveats for this release, including a description of the problems and available workarounds. The Bug Search Tool lists both open and resolved caveats.
To access the Bug Search Tool, you need valid Cisco credentials (user ID and password).
To search using a specific bug ID, use the following URL: https://tools.cisco.com/bugsearch/bug/<BUGID>.
End of Life Bulletins for IoT FND Releases
The following IoT FND releases are End of Life (EOL):
End of Sale and End of Life Bulletin for IoT Device Manager
Related Products
This section provides links to the Cisco IoT FND related products: