The router or routers you select determine which tabs display.

Note	Listed below are all the possible tabs. You can select to view the Map option from the List view.

Each of the tab views above displays different sets of device properties. For example, the Default view displays basic device properties, and the Cellular-GSM view displays device properties particular to the cellular network.

For information on how to customize router views, see Customizing Device Views.

For information about the device properties that display in each view, see Device Properties.

For information about common actions performed in these views (for example, adding labels and changing device properties), see Common Device Operations.

At the top, upper-right-hand corner of the screen, select root or user name, and click Preferences option. To view the routers in Map view, select the Enable map checkbox.

Note	The additional options (not seen in the Setting User Preferences for User Interface Display) are found as selectable options on the User Preferences page (Servers, Show PAN ID in Hexadecimal).

To view the routers in the Map view, navigate to DEVICES > FIELD DEVICES, choose the router and click Map.

Note	You can view any RPL tree by clicking the device in Map view, and closing the information pop-up window.

The RPL tree connection displays data traffic flow as blue or orange lines, as follows:

• Orange lines indicate that the link is an uplink: data traffic flows in the up direction on the map.

• Blue lines indicate that the link is a downlink: data traffic flows in the down direction on the map.

When you want to upload router device files to be managed by IoT FND, go to CONFIG > DEVICE FILE MANAGEMENT within the application. At that page, select Actions > Upload to get to the Upload File to Routers page. This page provides you the ability to:

• Search for a router device file by its name such as CGR1120/K9+JAF1648BBCK to upload.

• Search by an abbreviated Device file string such as CGR120/K9+JAF or BBCK to display a range of routers available to upload.

The number of router files available to upload (based on your search criteria) displays and all listed routers are selected (checked boxes) by default. You can define the number of routers that display, by using the drop-down menu on that page. Options are 10 (default), 50, 100 and 200. You can remove the check mark next to any router, that you do not want to upload.

After you have finalized the list to upload, click Upload.

IoT Field Network Director allows you to manage the following embedded access point (AP) attributes on and IR829 ISRs. The embedded Access Points on the IR829 routers are identified as AP800 in the FND user interface.

Note	IoT Field Network Director can only manage APs when operating in Autonomous mode.

You can perform and manage the following aspects for AP800s in FND:

• Discovery

• AP configuration

• Periodic inventory collection

• Firmware update of APs when operating in Autonomous Mode

• Event Management over SNMP

Note	Not all IR800 routers have embedded APs. . The IR829 ISR features matrix is here.

You must define a specific firmware image to use during ZTD.

You can only define a unified image (k9w8 - factory shipped) for update via ZTD

To refine the list of displayed routers, use the built-in router filters under ROUTERS in the Browse Devices pane or saved custom searches in the Quick View pane (right pane). For example, to display all operational routers, click the Up group under ROUTERS in the Browse Devices pane. Click a filter to insert the corresponding search string in the Search Devices field. For example, clicking the Up group under ROUTERS inserts the search string status:up in the Search Devices field.

At the DEVICES > Field Devices page, use the Browse Devices pane to display routers that belong to one of the groups (such as CGR1000) listed under ROUTER.

Use the Browse Devices pane to display the router devices that belong to one of the groups listed under ROUTER TUNNEL

When you open the DEVICES > Field Devices page in Default view, IoT FND lists All FAN Devices such as Routers, Endpoints (meters, gateways), and IoT Gateway and their basic device properties.

When you select an ENDPOINT device or group in the Browse Devices pane, IoT FND provides tabs to display additional endpoint property views:

Note	Listed below are all the possible tabs (left to right as they appear on the screen).

Each one of these views displays a different set of device properties.

For information on how to customize endpoint views, see Customizing Device Views.

For information about the device properties displayed in each view, see Device Properties.

For information about the common actions in these views (for example, adding labels and changing device properties) that also apply to other devices, see Common Device Operations.

You can view available defined configuration groups for mesh endpoints at the CONFIG > Device Configuration page.

You can use the Browse Devices pane to display the mesh endpoint devices that belong to one of the groups listed under ENDPOINTS.

You can generate any of the following predefined system reports within IoT FND to help troubleshoot issues with an endpoint such as GATEWAY-IR500, EXTENDER-IR500, METER-CGMESH, or any third-party METERS. A Troubleshoot page is displayed for each supported endpoint.

To generate a troubleshooting report for endpoints:

1. Choose DEVICES > Field Devices > Browse Devices tab > ENDPOINT .

2. Click the device on the right pane to view the device information.

3. On the Device Info page, click the Troubleshoot tab.

4. Under the Get Report section of the Troubleshoot page, select the report type. The troubleshooting report types available are All TLVs, Connectivity, General, Register, and Routing.

   Note	Based on the report type selected, the check boxes are auto-selected on the Troubleshoot page; indicating that the report displayed is only for the selected parameters.

5. Click Get Report. A report appears on the Report Output page.

   

6. Click the Report icon to export the report in CSV format. The following figure displays a troubleshooting report generated for General report type.

   

This section explains how you can add, update, or delete OOS devices using a CSV file and the subsequent impact on the license count during the process.

Note	The devices should have "outofservice" status in the CSV file to perform any action such as add, update, or delete in IoT FND.

You can add, update, or delete OOS devices using IoT FND NB API using the CSV file. The NB API used is SOAP (Simple Object Access Protocol) UI.

Note	The devices should have "outofservice" status in the CSV file to perform any action such as add, update, or delete in IoT FND.

• Adding OOS devices does not consume license. However, license should be available for the devices. If there is a request for adding new devices, then the devices in OOS state move to Unmanaged state on priority to accommodate new devices.

• Updating a device state to OOS state frees up the license count. You can update any Managed device state to OOS state. But this action prompts for license enforcement and reinstatement.

• Deleting OOS devices does not change the license count.

For more information, refer to the topic, Add, Update, or Delete OOS Devices Using CSV — IoT FND NB API.

This section explains how the license is managed for OOS devices in IoT FND.

Cisco IoT FND enables you to ping and traceroute OOS devices of router, endpoint, or gateway on the Device Info page (DEVICES > Field Devices > Browse Devices).

The following actions are not supported for OOS device state:

• In the Device Info page, you can ping or traceroute OOS devices like any other device state. However, the actions such as Refresh Metrics, Reboot, Sync Config Membership, Sync Firmware Membership, Block Mesh Device, Erase Node Certificates, or Create Work Order are not supported.

• In the CONFIG > DEVICE CONFIGURATION page, when you use Push Configuration option on OOS devices, an error message appears.

  

• In the CONFIG > Firmware Update page, when you use the upload or install image option on OOS devices, an error message appears.

  

• In the CONFIG > Device File Management page, if the upload file contains OOS devices, an error message appears.

  Note	You are not allowed to delete the existing file that has OOS devices now.

  

• In the Operations > Events page, you can view only existing events for the OOS devices. The generated event provides information on when the device moved to OOS state.

  Note	You cannot generate events for the devices that are currently in OOS state.

  Note	The Get Report option (in the Troubleshoot tab) is not supported for OOS devices.

  To filter existing OOS device events, refer to Viewing OOS Devices Using Filters.

  

• In the ADMIN > System Management > Audit Trail page, you can view the audit trail for OOS devices. The audit trail provides information on when the device moved to OOS state from Managed state and the other way round.

  

The EST service is located between a Certification Authority (CA) and a client. EST uses Hypertext Transfer Protocol (HTTP) to provide an authenticated and authorized channel for Simple Public Key Infrastructure (PKI) Requests and Responses.

EST also operates with the following protocols and authentication methods:

• Constrained Application Protocol (COAP) web transfer protocol for use with constrained nodes and constrained networks such as low-power, lossy networks.

• TLS/SSL Handshake between Registration Authority (RA) and CA.

• Datagram Transport Layer Security (DTLS) protocol is the preferred method for securing CoAP messages when the Nodes do not have any IPv6 (IP) addresses configured. DTLS uses UDP. It is based on Transport Layer Security (TLS).

• Trust Anchor is explicitly configured on the client or server for use during EST TLS authentication.

IC3000 supports edge computing and communicates with IoT FND through the IOx application, Cisco Fog Director which is accessible via IOT FND.

When the IC3000 starts up, it registers with IoT FND. FND then pushes the configuration to the device. Information pushed includes: metric periodic profile interface settings, user management settings and the heartbeat time interval of the device.

Initial communication occurs by establishing a secure HTTPs session. This connection is then upgraded to a WebSocket connection after initial setup.

Using the WebSocket protocol allows the client and server to talk to each other as well as operate independently of each other as shown in the image below. The client does not need to make a request to connect to the server (see left side of network diagram).

Once established, the client and server communicate over the same TCP connection for the lifecycle of the WebSocket connection.

You can perform the following actions for an IC3000 device type on demand:

• Refresh Metrics

• Reboot

Device Category: GATEWAY (in Browse Devices pane). To view the IC3000 Gateway details:

1. Choose DEVICES > Field Devices

2. Select a IC3000 device under GATEWAY in the left-pane. The device info for the gateway appears as shown in the image below. At the Device Info page, you can Refresh Metrics and Reboot the IC3000.

For details on the IC3000 Devices, refer to the Cisco IC3000 Industrial Compute Gateway Deployment Guide.

IoT FND employs Profile-based configuration for IR510s. This allows you to define a specific Profile instance (configuration) that you can assign to multiple IR500 configuration groups. Table 6. Pre-defined Profiles for IR510 lists the supported Profile types.

Note the following about the Profiles:

• Each Profile type has a default profile instance. The default Profile instance cannot be deleted.

• You can create a Profile instance and associate that profile with multiple configuration groups on the IR510.

• A ‘None’ option is available for all the Profile types that indicates that the configuration does not have any settings for that Profile type. 

• When a configuration push is in progress for a configuration group, all the associated Profiles will be locked (lock icon displays) and Profiles cannot be updated or deleted during that time.

• A lock icon displays for a locked Profile.

To create a new profile:

1. Choose CONFIG > DEVICE CONFIGURATION > Config Profiles tab.

2. Click the + (plus icon) at the top of the configuration panel to open the Add Profile entry panel.

3. Enter a Name for the new profile and select the Profile Type from the drop-down menu.

4. Click Add button. A new entry for the Profile entry appears in the left pane under the Profile Type sub-heading.

To delete a profile:

1. Choose CONFIG > DEVICE CONFIGURATION > Config Profiles tab.

2. Select the Profile name (excluding Default-Profile) that you want to delete. Click on the trash icon to remove the Profile.

3. In the pop up window that appears, click Yes to confirm deletion.

To rename a profile:

1. Choose CONFIG > DEVICE CONFIGURATION > Config Profiles tab.

2. Select the Profile name (excluding Default-Profile) that you would to rename. Click on the pencil icon to open the Rename Profile pop up window.

3. Make your edit and click OK. New name appears in the left pane.

To clone a profile:

1. Choose CONFIG > DEVICE CONFIGURATION > Config Profiles tab.

2. Select the Profile name that you want to clone. Click on the overlapping squares icon to open the Clone Profile pop up window.

3. Enter a Name for the new profile (unique from the existing profile name).

4. Click OK button. A new Profile entry appears in the left pane under the same Profile Type sub-heading.

Configuration Notes:

• Set DSCP (QoS) markings for all interfaces - Ethernet, DTE and DCE. Options: Low Priority (0), Normal Priority (10), Medium Priority (18).

• DSCP is applied on interfaces. Default values for DCE and DTE are Low Priority (0). There are no default values for Ethernet. Traffic will flow unmarked if you do not configure any value on the Configuration Template.

• Only one Raw Socket session can flow through DCE and DTE interfaces at a time. The DSCP value will be the same throughout.

• You can view Profile details in the Configuration Group Template page as shown in the image below.

• You can save configuration templates and push the configuration to all devices in the Configuration Group.

• Any of the Profile associations within a Configuration Group are optional. For example, a Configuration Group may not require Serial DCE settings, so you may select ‘None’ for Serial DCE settings.

In the Browse Devices pane, both NMS and Database servers appear under the All Server Devices heading.

In single NMS or Database server deployments, only one server appears under the NMS and/or Database Servers heading. In cluster deployments, multiple NMS servers appear under the NMS Servers heading. To filter the list pane:

• To display all NMS servers, click Devices > Servers in the top-level menu and then select NMS Servers within the Browse Devices pane. In single NMS server deployments, only one server appears under the NMS Servers heading. In cluster deployments, multiple NMS servers appear under the NMS Servers heading.

• To display all Database servers, click Devices > Servers in the top-level menu and then select Database Servers within the Browse Devices pane. In single-server deployments, only one database server appears under Database Servers. If a secondary database is configured, it also appears under the same entry.

Note	By default, only those NMS and Database Servers in an Up state display.

To display details on the Fog Director, click Devices > Services in the top-level menu and then select Application Management Servers. Details include: Host System Information, Host Disk Information and Service Information. Graphs display details on CPU usage and memory usages.

Assets represent non-Cisco equipment that is associated with an FND-managed Cisco device.

You can view Assets associated with specific routers (DEVICES > Field Devices) at the Device Detail pages of CGR1000, IR800, and SBR (Cisco 5921).

You can view a summary of all assets being tracked for all devices at the DEVICES > Assets page.

You can perform the following actions on Assets at the DEVICES > Assets page, using Bulk Operation:

• Add Assets: Use to upload a CSV file of assets to FND. A history of past file uploads displays at the bottom of the page.

  Example of Asset content in CSV file:

  assetName,assetType,deviceEid,assetDescription,vin,
  hvacNumber,housePlate,attachToWO
  asset1,RDU,00173bab01300000,Sample description,value1, value2, value3,no

  Note	Asset Name and Asset Type are the mandatory fields in the CSV file. All other fields are optional.

• Change Asset Property (CSV file): Use to make changes to existing assets.

• Remove Assets (CSV file): Use to remove specific assets.

• Add Files to Assets (zip/tar file): Use to append additional information to Asset content.

Guidelines for Adding or Associating an Asset with a Device:

• One or more assets can be mapped to a particular device.

• A limit of five assets can be associated to a single device, and there is also a limit of five files per asset.

• An asset can be mapped to only one device at any point in time.

• To select all devices listed on a page, check the check box next to Name.

• To select devices across all pages, click Select All.

• To select a group of devices, check the check boxes of individual devices listed on a page and across pages. The count increments with every device selected, and selections on all pages are retained.

IoT FND lets you customize device views. For List views you can:

• Add and delete tabs

• Specify the properties to display in the columns for each view (see Device Properties by Category for available properties)

• Change the order of columns

To change the sorting order of devices, click the arrowhead icon in the column heading to list the entries in an ascending (upward pointing) or descending manner (downward pointing).

You use labels to create logical groups of devices to facilitate locating devices and device management.

IoT FND keeps detailed information about every device in the system. To access detailed information about a device, click its name or EID.

Depending on your deployment, the number of devices managed by IoT FND can be very large (IoT FND supports up to 10 million devices). To facilitate locating and displaying devices in Map View and List view, IoT FND provides filters and lets you add customized filters. Filters are listed in the Browse Devices and Quick View tabs.

In IoT FND, you can perform the bulk import device actions.

IoT FND uses groups to manage devices in bulk. When you add routers to IoT Field Network Director, IoT FND automatically adds them to the appropriate default ROUTER configuration groups, for example, default-cgr1000 or . When you add MEs (meters and range extenders), IoT FND adds them to the default ENDPOINT configuration group, default-cgmesh.

You can enable GPS traps to trigger an event if the router moves a distance threshold, after a time threshold, or both. For example, you can configure stationary, pole-top CGR monitoring for a distance threshold, to detect movement from theft or pole incident; for mobile routers, set both thresholds to determine distance over time. The recommended distance threshold is 100 feet (30 m).

To enable GPS traps, uncomment these lines in the default configuration template.

<#-- 
Enable the following configurations to generate events that track if the router 
moves by a certain distance (unit configurable) or within a certain time (in minutes) 
-->
<#-- cgna geo-fence interval 10 -->
<#-- cgna geo-fence distance-threshold 100 -->
<#-- cgna geo-fence threshold-unit foot -->
<#-- cgna geo-fence active -->

Note	Because GPS traps only generate Informational logs, we recommend that you create a rule-based event with high severity (such as CRITICAL) to inform the administrator of router movement. An example of this type of rule definition is: configGroup:name eventName:deviceLocChanged (see Creating a Rule)

For Cisco IOS routers you configure SNMP v3 Informational Events to replace the default SNMP v3 traps. For Cisco IOS routers, converting these SNMP v3 traps to SNMP v3 Informational Events sends an acknowledgment to the router for every event received from the router. The router then verifies that the trap was received by IoT FND. To enable SNMP v3 Informational Events, uncomment the following lines in the default configuration file and push the new configuration file to all router(s) in the group:

<#-- Enable the following configurations for the nms host to receive informs 
instead of traps -->
<#-- no snmp-server host ${nms.host} traps version 3 priv ${far.adminUsername} -->
<#-- snmp-server engineID remote ${nms.host} ${nms.localEngineID} -->
<#-- snmp-server user ${far.adminUsername} cgnms remote ${nms.host} v3 auth sha 
${far.adminPassword} priv aes 256 ${far.adminPassword} -->
<#-- snmp-server host ${nms.host} informs version 3 
priv ${far.adminUsername} -->

The following are the prerequisites to support dual WPAN in IR8100:

• The dual WPAN interfaces are configured with: different PAN IDs and IPv6 prefixes, and same SSID or different SSID.

• Both WPANs must be in Active-Active state and in either WiSUN or CRMESH mode.

  Note	Mix of stack modes is not supported.

Select DEVICES > FIELD DEVICES. The FAN view is visible where all the devices are listed. You can view WPAN related information in this Field Device page.

Note

If WPAN is not inserted in slot 1, then all the columns appear empty. If the WPAN is inserted in either slot 2 or slot 3, you can view WPAN related parameters by adding them. For more information, see Adding Device Views. This displays the respective parameters related to WPAN inserted in either slot 2 or slot 3.

• In the FAN device view, you can view PANID 2 and PANID 3 columns in the Inventory tab that indicates the meshPanID parameter of WPAN that is inserted in either slot 2 or slot 3.

  Note	If the WPAN module is not inserted in the respective slot, the corresponding column appears empty. The PANID 2 and PANID 3 columns appear empty for other devices.

  

• To add user configurable parameters for both the WPAN interfaces:

  • Upload a csv file from the device list page. For more information on uploading csv, see Changing Device Properties in Bulk.

  • After uploading, navigate to DEVICES > FIELD DEVICES > Browse Devices tab > IR8100. Click Mesh Config tab to view the uploaded values. or

    

    Navigate to DEVICES > FIELD DEVICES > Browse Devices tab > IR8100. Click the device on the right pane to view the device information. Go to Config Properties tab to view the Mesh Link Config details displayed for both the WPANs with the parameters suffixed according to the slot number.

    

In the DEVICES > FIELD DEVICES page, select Router group in the Browse Devices tab.The Mesh Count column indicates the number of endpoints connected in the WPAN 0/1/0 inserted in slot 1. By default, the Mesh Count column is displayed. The mesh count 2 and mesh count 3 columns indicate the number of endpoints that are connected to WPAN 0/2/0 and WPAN 0/3/0. The mesh count 2 and mesh count 3 columns can be added in the Field Device page by choosing them to be in the default view. For more information, see Adding Device Views.

In the DEVICES > FIELD DEVICES page, select IR8100 under Router category in the Browse Devices tab.

In the Inventory tab, the IR8100 device view displays the parameters for the WPAN inserted in slot 1 by default. The Mesh tab and Mesh Config tab show the existing properties related to WPAN inserted in slot 1.

Additional WPAN parameters are included for the WPANs that are inserted in other slots. You can view the additional attributes by customizing your default view. To add a new tab or edit the existing default view:

• Click + to create a new tab and add WPAN related fields. or

• Click the drop-down list near the Mesh tab or Mesh Config tab to edit the current view and add WPAN specific fields. This helps to view WPAN related details specific to WPAN 0/2/0 or WPAN 0/3/0. For more information, see Customizing Device Views.

  

Choose CONFIG > Device Configuration > ROUTER > Default-Ir8100.

• Group Members tab—The table is updated with four more columns for representing the user configured parameters such as meshPrefixConfig2, meshPrefixLengthConfig2, meshPanIdConfig2, meshAddressConfig 2 metrics. The existing parameter represents for first WPAN and the parameters with suffix represents the configured parameter for the second WPAN.

  

• Edit Configuration Template tab—The page allows you to define user configurable parameters in the template. FND maps the defined parameters to the WPAN parameter value configured through CSV. To configure the user configurable parameters:

  • Navigate to Edit Configuration Template tab.

  • Enter the parameter values in the template and click the disk icon. The WPAN specific user configurable parameters are displayed in the Running Config tab in the device details page as well.

  Note	You can change device properties by clicking the Change Device Properties button above the devices pane.

• Export Templates Keys CSV—In the Device Configuration page, click Export Template Keys as CSV button. The WPAN related user configurable parameters are exported in a csv file.

In the dashboard, scroll down to view the Devices with interfaces enabled but down dashlet. Under the interface filter option, both the WPANs are listed. Set the filter with Type as ir8100 and Interface as WPAN x|y|z. FND displays the status of the respective interface. Click on the needle of the gauge chart to show the devices for which the selected interfaces are enabled but down in the Field Devices page. For more information, see Pre-defined Dashlets.