Managing Firmware Upgrades

This section describes managing firmware upgrade settings in IoT FND, and includes the following sections:

blank.gifRouter Firmware Updates

blank.gifConfiguring Firmware Group Settings

blank.gifWorking with Router Firmware Images

blank.gifPerforming CG-OS to Cisco IOS Migrations

blank.gifWorking with Resilient Mesh Endpoint Firmware Images

Use IoT FND to upgrade the firmware running on routers (CGR1000s, C800s, IR800s), AP800s and Cisco Resilient Mesh Endpoints (RMEs) such as meters and range extenders. IoT FND stores the firmware binaries in its database for later transfer to routers in a firmware group through an IoT FND and IoT-DM file transfer, and to RMEs using IoT FND.

Cisco provides the firmware bundles as a zip file. For Cisco IOS, software bundles include hypervisor, system image and IOx images (for example, Guest-OS, Host-OS).

For Cisco CG-OS, IoT FND automatically unzips the kickstart and system images included in the bundle. Firmware system images are large (approximately 130 MB); kickstart images are approximately 30 MB. Every firmware bundle includes a manifest file with metadata about the images in the bundle. You can pause, stop, or resume the upload process.

Router Firmware Updates

IoT FND updates router firmware in two steps:

1.blank.gif Uploads the firmware image from IoT FND to the router. Firmware images upload to the flash:/managed/images directory on the router. Note: In some cases the router might be in a Firmware Group. Refer to Configuring Firmware Group Settings

Because of their large size, firmware-image uploads to routers take approximately 30 minutes, depending on interface speeds.

2.blank.gif Installs the firmware on the device and reloads it.

During the firmware install the boot parameters on the routers are updated according to the new image file and the router is reloaded after enabling the cg-nms-register cgna profile.

Note: You must initiate the firmware installation process. IoT FND does not automatically start the upload after the image upload.

When a router contacts IoT FND for the first time to register and request tunnel provisioning, IoT FND rolls the router back to the default factory configuration (ps-start-config) before uploading and installing the new firmware image.

Note: This rollback requires a second reload to update the boot parameters in ps-start-config and apply the latest configuration. This second reload adds an additional 10–15 minutes to the installation and reloading operation.

Upgrading Guest OS Images

Depending on CGR factory configuration, a Guest OS (GOS) may be present in the VM instance. You can install or upgrade Cisco IOS on the CONFIG > Firmware Update page (see Router Firmware Updates). The GOS, hypervisor, and Cisco IOS all upgrade when you perform a Cisco IOS image bundle installation or update.

After after any Cisco IOS install or upgrade, when IoT FND discovers a GOS, it checks if the initial communications setup is complete before it performs the required setup. The CGR must have a DHCP pool and GigabitEthernet 0/1 interface configured to provide an IP address and act as the gateway for the GOS. The new GOS image overwrites existing configurations. IoT FND has an internal backup and restore mechanism that ports existing apps to the upgraded Guest OS (see Monitoring a Guest OS).

See the Cisco 1000 Series Connected Grid Routers Configuration Guides documentation page for information on configuring the CGR.

Note: If IoT FND detects a non-Cisco OS installed on the VM, the firmware bundle will not upload and the Cisco reference GOS will not install.

Upgrading WPAN Images

At the CONFIG > Firmware Update page, you can upload the independent WPAN images (IOS-WPAN-RF, IOS-WPAN-PLC, IOS-WPAN-OFDM, IOS-WPAN-IXM) to IoT FND using the Images sub-tab (left-hand side) and Upload Image button like other image upgrades. This process is known as a non-integrated WPAN firmware upgrade.

Note: The WPAN firmware image integrated with the IOS CGR image option is still supported.

Also, if only the WPAN firmware upgrade from the image bundled with IOS image is desired (for example, when the WPAN firmware upgrade option was not checked during IOS upgrade), the “Install from Router” option is also provided under respective WPAN image types (IOS-WPAN-RF or IOS-WPAN-PLC).

For detailed steps, go to Working with Router Firmware Images.

Changing Action Expiration Timer

You can use the cgnms_preferences.sh script to set or retrieve the action expiration timer value in the IoT FND database:

/opt/cgms
/bin/cgnms_preferences setCgrActionExpirationTimeout 50
 

Valid options are:

blank.gifset <pkg>actionExpirationTimeoutMins<value>

where,

blank.gif <pkg> is the preference package (required for set and get operations).

blank.gif actionExpirationTimeoutMins is the preference key (required for set and get operations).

blank.gif <value> is the preferred value, in minutes (required for set and setCgrActionExpirationTimeout operations).

blank.gifsetCgrActionExpirationTimeout <value>

blank.gifget <pkg>actionExpirationTimeoutMins

blank.gif getCgrActionExpirationTimeout

Example

In the following example, the action timer value is retrieved, set, the current value retrieved again, the value removed, and a null value retrieved:

[root@userID-lnx2 cgms]#./dist/cgms-1.x/bin/cgnms_preferences.sh getCgrActionExpirationTimeout
2013-08-12 22:38:42,004:INFO:main:CgmsConnectionProvider: registered the database url for CG-NMS: [jdbc:oracle:thin:@localhost:1522:cgms]
5
[root@userID-lnx2 cgms]#./dist/cgms-1.x/bin/cgnms_preferences.sh setCgrActionExpirationTimeout 50
2013-08-12 22:38:51,907:INFO:main:CgmsConnectionProvider: registered the database url for CG-NMS: [jdbc:oracle:thin:@localhost:1522:cgms]
Successfully set the preferences.
[root@userID-lnx2 cgms]#./dist/cgms-1.x/bin/cgnms_preferences.sh getCgrActionExpirationTimeout
2013-08-12 22:38:58,591:INFO:main:CgmsConnectionProvider: registered the database url for CG-NMS: [jdbc:oracle:thin:@localhost:1522:cgms]
50
[root@userID-lnx2 cgms]#./dist/cgms-1.x/bin/cgnms_preferences.sh get com.cisco.cgms.elements.ciscocgr actionExpirationTimeoutMins
2013-08-12 22:39:12,921:INFO:main:CgmsConnectionProvider: registered the database url for CG-NMS: [jdbc:oracle:thin:@localhost:1522:cgms]
50
[root@userID-lnx2 cgms]#./dist/cgms-1.x/bin/cgnms_preferences.sh set com.cisco.cgms.elements.ciscocgr actionExpirationTimeoutMins 15
2013-08-12 22:39:23,594:INFO:main:CgmsConnectionProvider: registered the database url for CG-NMS: [jdbc:oracle:thin:@localhost:1522:cgms]
Successfully set the preferences.
[root@userID-lnx2 cgms]#./dist/cgms-1.x/bin/cgnms_preferences.sh get com.cisco.cgms.elements.ciscocgr actionExpirationTimeoutMins
2013-08-12 22:39:29,231:INFO:main:CgmsConnectionProvider: registered the database url for CG-NMS: [jdbc:oracle:thin:@localhost:1522:cgms]
15

Resilient Mesh Endpoint Firmware Updates

When you instruct IoT FND to upload a firmware image to the members of an RME firmware group or subnet, IoT FND pushes the image to the group members in the background and tracks the upload progress to ensure that the devices receive the image.

A Resilient Mesh Endpoint (RME) stores three firmware images:

blank.gifUploaded image: Image most recently uploaded.

blank.gifRunning image: Image that is currently operational.

blank.gifBackup image: It serves as a golden (fallback) image for the RME if there is an issue with the running image.

Note: You can initiate up to 3 firmware downloads simultaneously.

Mesh Firmware Migration (CG-OS CG4 platforms only)

Note: Mesh Firmware Migration to Cisco Resilient Mesh is not supported for CGRs running CG-OS version CG4(4).

IoT FND allows you to update earlier versions of CGR firmware to allow Cisco Resilient Mesh networking using the following IoT FND North Bound APIs:

blank.giffindEidByIpAddress

blank.gifstartReprovisionByEidList

blank.gifstartReprovisionByEidListAbridged

blank.gifstartReprovisionByGroup

blank.gifstartReprovisionByGroupAbridged

See the North Bound API User Guide for the Cisco IoT Field Network Director, Releases 3.x and 4.x for usage information.

Configuring Firmware Group Settings

This section describes how to add, delete, and configure firmware groups, and includes the following topics:

blank.gifAdding Firmware Groups

blank.gifAssigning Devices to a Firmware Group

blank.gifRenaming a Firmware Group

blank.gifDeleting Firmware Groups

Note: Upload operations only begin when you click the Resume button.

When you add routers or RMEs to IoT FND, the application sorts the devices into the corresponding default firmware group: default- <router> or default-cgmesh. Use these groups to upload and install firmware images on member devices. Add firmware groups to manage custom sets of devices. You can assign devices to firmware groups manually or in bulk. Before deleting a firmware group, you must move all devices in the group to another group. You cannot delete non-empty groups.

Note: When creating firmware groups note the guidelines:

blank.gifCGRs, IR800s, and C800s can coexist on a network; however, for firmware management, they cannot belong to the same firmware group.

blank.gifIR500s and other RMEs devices can coexist on a network; however, for firmware management, they cannot belong to the same group.

The Groups tab on the CONFIG > Firmware Update page displays various device metrics.

IoT FND displays this information about the image on the routers in the selected firmware group:

Field
Description

Selected Firmware Image

The name of the current image zip archive or the image being uploaded to group members.

Current Action

The name of the firmware action being performed.

Current Status

The status of the image uploading. Possible statuses are:

blank.gifImage Loading, Upload Paused, Upload Stopped, Upload Finished, Upload Stopping, Upload Pausing

blank.gifScheduling Reload, Reload Paused, Reload Stopped, Reload Scheduling Finished, Reload Stopping, Reload Pausing

blank.gifSetting Backup, Backup Paused, Backup Stopped, Backup Finished, Backup Stopping, Backup Pausing

Written/Devices

Specifies how many devices received or installed the image out of the total number of devices in the group.

For example, 1/3 means that one device received the firmware image out of 3 devices in the group.

Error/Devices

Specifies how many devices failed to receive or install the image out of the total number of devices in the group. For example, 2/3 means that two out of the three devices in the group failed to install the image.

Tip: Click the Error/Devices link (1 in Firmware Update Page – Viewing Errored Devices) to view the devices that are in the errored state.

For every router in the group, IoT FND displays this information:

Field
Description

Status

Device status of the (for example, Up, Down, or Unheard).

Name

EID of the device.

IP Address

IP address of the device.

Firmware Version

Version of the firmware image installed on the device.

Activity

Device activity.

Update Progress

Firmware image updating progress. A progress of 100% indicates that the image uploading is complete.

Last Firmware Status Heard

The last time the firmware status was heard.

Error Message

Error message if image upload failed.

Error Details

Displays error details for the selected device.

Tip: At the Firmware Update page, click the Error/Devices link (not shown) in Firmware Update Page – Viewing Errored Devices to apply a filter. Click the Clear Filter to revert to an unfiltered view of the selected device group.

Figure 1 Firmware Update Page – Viewing Errored Devices

 

 

421815.jpg

 

Adding Firmware Groups

To add a firmware group:

1.blank.gif Choose CONFIG > Firmware Update.

2.blank.gif Click the Groups tab.

 

 

421814.jpg

 

3.blank.gif In the Groups pane, select one of the following: Default-cgr1000, Default-c800, Default-ir500, Default-ir800, Default-cgmesh or Default-sbr.

4.blank.gif Click + next to Firmware Groups heading in the Groups pane to Add Group.

5.blank.gif In the Add Group dialog box, enter the name of the firmware group. Device Category options depend on the device type you select in step In the Groups pane, select one of the following: Default-cgr1000, Default-c800, Default-ir500, Default-ir800, Default-cgmesh or Default-sbr.

 

6.blank.gif Click Add.

The new group label appears under the corresponding device type in the Firmware Groups pane.

To assign devices to the new group, see Assigning Devices to a Firmware Group.

Assigning Devices to a Firmware Group

This section describes moving devices, and includes the following topics:

blank.gifMoving Devices to Another Group Manually

blank.gifMoving Devices to Another Group In Bulk

Moving Devices to Another Group Manually

To manually move devices to a group:

1.blank.gif Choose CONFIG > Firmware Update.

2.blank.gif Click the Groups tab.

3.blank.gif In the Firmware Groups pane, select the desired firmware group based on device type.

Note: If this is an ENDPOINT firmware group, click the Devicesblank.gif tab above the main pane.

 

421813.jpg

4.blank.gif Check the check boxes of the devices that you want to move.

5.blank.gif Click Change Firmware Group. to open a pop up window.

 

6.blank.gif From the Firmware Group drop-down menu, choose the firmware group to which you want to move the devices or enter a new group name.

7.blank.gif Click Change Firmware Group.

8.blank.gif Click Close.

Moving Devices to Another Group In Bulk

To move devices from one group to another in bulk:

1.blank.gif Create a CSV or XML file listing devices that you want to move using the format shown in the following examples:

 

DeviceType/EID for CGRs:

eid
CGR1120/k9+JS1
CGR1120/k9+JS2
CGR1120/k9+JS3

EID only for mesh endpoints:

eid
00078108003c1e07
00078108003C210b

EID only for IR800s

eid
ir800

EID only for ISR 800s:

eid
C819HGW-S-A-K9+FTX174685V0
C819HGW-S-A-K9+FTX174686V0
C819HGW-S-A-K9+FTX174687V0

EID only for IR500s:

eid
da1
da2

da3

 

Note: Each file can only list one device type.

2.blank.gif Choose CONFIG > Firmware Update.

3.blank.gif Click the Groups tab.

4.blank.gif Click Assign devices to Firmware Group button (found above Groups tab).

 

5.blank.gif In the window that appears, click Browse and locate the device list CSV or XML file.

6.blank.gif From the Group drop-down menu, choose the destination group.

7.blank.gif Click Assign to Group.

IoT FND moves the devices listed in the file from their current group to the destination group.

8.blank.gif Click Close.

Renaming a Firmware Group

To rename a firmware group:

1.blank.gif Choose CONFIG > Firmware Update.

2.blank.gif Click the Groups tab.

3.blank.gif In the Firmware Groups pane, select the firmware group to rename.

4.blank.gif Move the cursor over the group and click the Edit Group Name pencil icon.

 

421737.jpg

5.blank.gif In the Rename Group window, enter the new name and then click OK.

 

Note: When you enter an invalid character entry (such as, @, #, !, or +) within the Rename Group field, IoT FND displays a red alert icon, highlights the field in red, and disables the OKblank.gif button.

Deleting Firmware Groups

Note: Before deleting a firmware group, you must move all devices in the group to another group. You cannot delete non-empty groups.

To delete a firmware group:

1.blank.gif Choose CONFIG > Firmware Update.

2.blank.gif Click the Groups tab.

3.blank.gif In the Firmware Groups pane, select a firmware group to display a list of all possible firmware images for that group in the right pane.

4.blank.gif Check the box next to the firmware group that you want to delete.

5.blank.gif Click Clear Selection that appears above the entry (yellow bar).

 

6.blank.gif To confirm deletion, click Yes.

7.blank.gif Click OK.

Working with Router Firmware Images

This section describes how to add router firmware images to IoT FND and how to upload and install the images on routers, and includes the following topics:

blank.gifViewing Firmware Image Files in IoT FND

blank.gifAdding a Firmware Image to IoT FND

blank.gifUploading a Firmware Image to a Router Group

blank.gifCanceling Router Firmware Image Upload

blank.gifPausing and Resuming Router Firmware Image Uploads

blank.gifInstalling a Firmware Image

blank.gifStopping Firmware Image Installation

blank.gifPausing and Resuming Router Firmware Image Installation

Viewing Firmware Image Files in IoT FND

You can display firmware image information from the Images pane in the CONFIG > Firmware Update page. Select ROUTER or ENDPOINT to display all firmware images for those devices in the IoT FND database. Select the firmware image type to refine the display (see CONFIG > Firmware Update Images Pane).

Figure 2 CONFIG > Firmware Update Images Pane

 

421738.jpg

For every image in the list, IoT FND provides this information:

 

Field
Description

Name

The filename of the firmware image bundle.

Version

The version of the firmware bundle. Click the arrowhead icon to switch between ascending and descending listing of the firmware version.

Hardware ID

The hardware family to which you can download this image.

Size

The size of the firmware bundle.

Active Download?

The active firmware using the firmware image.

Adding a Firmware Image to IoT FND

Before you can upload and install a firmware image on a device, add the image file (as a zip archive) to IoT FND. IoT FND stores the image in its database.

Note: Do not unzip the image file. IoT FND unzips the file.

To add a firmware image to IoT FND:

1.blank.gif Choose CONFIG > Firmware Update.

2.blank.gif Click the Images tab (CONFIG > Firmware Update Images Pane).

3.blank.gif In the Images pane, select ROUTER, ENDPOINT or GATEWAY, and the type of device group.

4.blank.gif Click the + icon to select an image found to the right of the Firmware Images heading.

5.blank.gif Click Browse to locate the firmware image. Select the image, then click Add File.

6.blank.gif Click Upload.

The image appears in the Firmware Images panel (CONFIG > Firmware Update Images Pane).

 

 

blank.gifTo delete an image, click Delete link shown at far-right of entry. Click Yes to confirm.

Firmware images with a download in progress (with Yes in the Active Download? column) cannot be deleted.

blank.gifTo upload the firmware image to devices in a group, select the group (from Groups listing on CONFIG > FIRMWARE UPDATE page) and then click Upload Image. See Uploading a Firmware Image to a Router Group.

Uploading a Firmware Image to a Router Group

When you upload a firmware image to router firmware group members, IoT FND pushes the image to the group members in the background and tracks the upload progress to ensure that the devices receive the image.

On routers, firmware image upload and installation requires 200 MB of free disk space. IoT FND stores image files in the.../managed/images directory on the router.

Note: If there is not enough disk space on the router for the firmware image, the IoT FND initiates disk cleanup process on the router and removes the following files, sequentially, until there is enough disk space to upload the new image:

blank.gifUnused files in the.../managed/images directory that are not currently running or referenced in the before-tunnel-config, before-registration-config, express-setup-config, and factory-config files for IOS CGRs; golden-config, ps-start-config, express-setup-config, or factory-config for CG-OS CGRs

blank.gifUnused.gbin and.bin files from the bootflash directory in CG-OS CGRs

If there is still not enough space, you must manually delete unused files on the router.

To upload a firmware image to router group members:

1.blank.gif Choose CONFIG > Firmware Update.

2.blank.gif Click the Groups tab.

3.blank.gif In the Groups pane, select the router firmware group that you want to update.

Note: CGR groups can include devices running Cisco IOS and CG-OS. Therefore, Cisco IOS software images only upload to devices running Cisco IOS (C5921s, IR800s, ISR800s, CGR1000s); only CGRs accept CG-OS images.

IoT FND displays the firmware image type applicable to the router:

Image
Type
Applicable Device

ACTD-CGR

cgr1000

Cisco IOS CGRs running Guest OS

CDMA

all

Cisco IOS CGRs, IR800s, and ISR800s

CGOS

cgr1000

Cisco IOS CGRs running Guest OS

ENDPOINT

IR500

Cisco IR500

GSM

all

Cisco IOS CGRs, IR800s, and ISR800s

IOS-CGR

cgr1000

Cisco IOS CGRs (CGR 1240 and CGR 1120)

IOS-ESR

c5921

Cisco 5921 ESR (C5921)

IOS-IOx

cgr1000

Cisco IOS CGRs (CGR 1240 and CGR 1120) universal image

IOS-C800

c800

Cisco 800 Series ISR connected devices.

IOS-AP800

ap800

Cisco 800 Series Access Points.

IOS-IR800

ir800

Cisco 800 Series ISRs.

IOS-IR807

ir800

Image (Cisco IOS only) loads to IR807 within the IR800 firmware group.

IOS-WPAN-IXM

ir800

LoRaWAN IXM module when operating as an interface for Cisco IR809.

IOS-WPAN-RF

cgr1000

Cisco IOS-CGR

IOS-WPAN-PLC

cgr1000

Cisco IOS-CGR

IOx-CGR

cgr1000-ioxvm

Cisco IOS-CGR

IOx-IR800

ir800

Cisco 800 Series ISRs.

LMAC

lmac

Local MAC connected devices.

LORAWAN

lorawan

Cisco IR829-GW

4.blank.gif Click Upload Image to open the entry panel.

5.blank.gif From the Select Type: drop-down menu, choose the firmware type for your device.

6.blank.gif From the Select an Image: drop-down menu, choose the firmware bundle to upload.

For some software bundles, you also have the option to select one or more of the following options (as noted in parenthesis next to the options listed below):

blank.gifInstall Guest OS from this bundle (IOS-CGR, IOS-IR800)

blank.gifClean LoRaWAN application data on the install (LORAWAN)

blank.gifInstall WPAN firmware from this bundle (IOS-CGR)

7.blank.gif Click Upload Image.

8.blank.gif Click OK.

IoT FND starts the upload process. After the image uploads, install the image as described in Installing a Firmware Image.

Canceling Router Firmware Image Upload

You can stop the image upload process to firmware router groups at any time. Stopping the upload can take a few minutes. When you cancel the image upload, the image upload process immediately stops currently running tasks, and blocks all queued tasks.

Note: Running tasks do not complete, leaving partial files on the disk and sets the firmware group status to CANCELING until you complete the upload operation.

To stop firmware image uploading to a group:

1.blank.gif Choose CONFIG > Firmware Update.

2.blank.gif Click the Groups tab.

3.blank.gif In the Groups pane, select the firmware group.

4.blank.gif Click Cancel.

5.blank.gif Click Yes.

Pausing and Resuming Router Firmware Image Uploads

You can pause the image upload process to router firmware groups at any time, and resume it later.

Note: The image upload process does not immediately pause; all queued (but not running) operations pause, but currently running tasks complete. The status changes to PAUSING until the active operations complete.

To pause firmware image upload:

1.blank.gif Choose CONFIG > Firmware Update.

2.blank.gif Click the Groups tab.

3.blank.gif In the Groups pane, select the firmware group.

4.blank.gif Click Pause.

The Status column displays PAUSING until the active upload operations complete. No new upload operations start until you click the Resume button.

5.blank.gif Click Yes.

To resume the upload process, click Resume.

Note: If a IoT FND server goes down while the firmware image is being uploaded to devices, the server resumes the upload process for the scheduled devices after the server comes up. For IoT FND server clusters, if one server goes down during the upload process, another server in the cluster resumes the process.

Installing a Firmware Image

To install an image on devices in a router firmware group:

1.blank.gif Choose CONFIG > Firmware Update.

2.blank.gif Click the Groups tab.

3.blank.gif In the Groups pane, select the firmware group.

Note: IoT FND recognizes devices as firmware-specific, and uploads the proper image to selected devices.

4.blank.gif In the Images pane, select a device subgroup (such as IOS-CGR, IOS-WPAN-RF, CDMA) to refine the display to those device types.

This step above is necessary because IoT FND recognizes devices as firmware-specific and ensures the system uploads the proper image to selected devices.

5.blank.gif At the CONFIG > Firmware Update page, click the Groups tab; and, then Install Image on the Firmware Upgrade tab.

IoT FND sends commands to install the uploaded image and make it operational.

6.blank.gif Click Yes.

IoT FND starts the installation or reloading process.

Note: If you restart IoT FND during the image installation process, IoT FND restarts the firmware installation operations that were running prior to IoT FND going offline.

You can pause or stop the installation operation as described in:

blank.gifStopping Firmware Image Installation

blank.gifPausing and Resuming Router Firmware Image Installation

Note: The firmware installation operation can time out on some routers. If routers are not heard from for more than an hour, IoT FND logs error messages.

Stopping Firmware Image Installation

You can stop firmware image installation at any time. When you stop image installation, the running version of the firmware remains in place.

Note: Stopping the installation cancels all queued tasks. Currently running tasks complete.

To stop firmware image installation to devices in a firmware group:

1.blank.gif Choose CONFIG > Firmware Update.

2.blank.gif Click Groups.

3.blank.gif In the Groups pane, select the firmware group.

4.blank.gif In the Firmware Upgrade window, click Cancel button.

5.blank.gif Click Yes to confirm action.

Pausing and Resuming Router Firmware Image Installation

You can pause the firmware image installation process at any time.

Note: Pausing the installation pauses all queued tasks. Currently running tasks complete.

To pause firmware image installation to devices in a firmware group:

1.blank.gif Choose CONFIG > Firmware Update.

2.blank.gif In the Groups pane, select the firmware group.

3.blank.gif In the Firmware Upgrade window, click Pause button.

4.blank.gif Click Yes to confirm action.

You can resume the installation process by clicking Resume.

Performing CG-OS to Cisco IOS Migrations

You can upgrade CGRs from CG-OS to IOS in bulk or by device. The migration package is in the IoT Field Network Director installation package, and is available in the Select IOS Image menu.

Note: The Migration to IOS button is disabled if all CGRs in the group are IOS.

BEFORE YOU BEGIN

For CG-OS CGRs that you are migrating, modify the device configuration properties CSV or XML file to include the following IOS properties (see Changing Device Configuration Properties):

EXAMPLE BOOTSTRAP PROPERTIES

This example preserves tunnels during migration:

enable
!
configure terminal
!
!
!
interface GigabitEthernet2/2
no switchport
ip address 66.66.0.75 255.255.0.0
duplex auto
speed auto
no shut
!
crypto key generate rsa label LDevID modulus 2048
!
hostname IOS-IOT1
!
enable password cisco
!
aaa new-model
!
!
aaa authentication login default local
aaa authorization exec default local
!
!
aaa session-id common
clock timezone PDT -8 0
!
!
no ip domain lookup
ip domain name ios.com
ip host nms.sgbu.cisco.com 55.55.0.5
ip host ps.sgbu.cisco.com 55.55.0.8
ip cef
ipv6 unicast-routing
ipv6 cef
!
!
!
crypto pki profile enrollment NMS
enrollment url http://55.55.0.17/certsrv/mscep/mscep.dll
!
crypto pki trustpoint LDevID
enrollment mode ra
enrollment profile NMS
serial-number none
ip-address none
password
fingerprint 1D33B1A88574F11E50F5B758EF217D1D51A7C83F
subject-name CN=mig.ios.com/serialNumber=PID:CGR1240/K9 SN:JAF1712BCAP
revocation-check none
rsakeypair LDevID 2048
!
!
!
license accept end user agreement
license boot module cgr1000 technology-package securityk9
license boot module cgr1000 technology-package datak9
!
!
!
username admin password 0 cisco
username cg-nms-administrator privilege 15 secret Sgbu123!
!
!
do mkdir flash:archive
#await Create directory filename
#send_CR
!
!
archive
path flash:archive/
maximum 8
!
!
!
no ip http server
ip http authentication local
ip http secure-server
ip http secure-ciphersuite aes-128-cbc-sha aes-256-cbc-sha dhe-aes-128-cbc-sha dhe-aes-256-cbc-sha
ip http secure-client-auth
ip http secure-port 8443
ip http secure-trustpoint LDevID
ip http max-connections 2
ip http timeout-policy idle 600 life 86400 requests 3
ip http client connection timeout 5
ip http client connection retry 5
ip http client source-interface GigabitEthernet2/2
ip http client secure-ciphersuite aes-128-cbc-sha aes-256-cbc-sha dhe-aes-128-cbc-sha dhe-aes-256-cbc-sha
!
ip route 0.0.0.0 0.0.0.0 66.66.0.8
!
!
privilege exec level 2 dir /recursive
privilege exec level 2 dir
privilege exec level 2 show memory statistics
privilege exec level 2 show memory
privilege exec level 2 show inventory
privilege exec level 2 show platform hypervisor
privilege exec level 2 show platform led summary
privilege exec level 2 show platform led
privilege exec level 2 show processes cpu
privilege exec level 2 show processes
privilege exec level 2 show environment temperature
privilege exec level 2 show environment
privilege exec level 2 show module
privilege exec level 2 show version
privilege exec level 2 show logging
privilege exec level 2 show platform
privilege exec level 2 show
!
!
wsma agent exec
profile exec
!
wsma agent config
profile config
!
!
wsma profile listener exec
transport https path /wsma/exec
!
wsma profile listener config
transport https path /wsma/config
!
cgna profile cg-nms-tunnel
add-command show hosts | format flash:/managed/odm/cg-nms.odm
add-command show interfaces | format flash:/managed/odm/cg-nms.odm
add-command show ipv6 dhcp | format flash:/managed/odm/cg-nms.odm
add-command show ipv6 interface | format flash:/managed/odm/cg-nms.odm
add-command show version | format flash:/managed/odm/cg-nms.odm
interval 10
url https://ps.sgbu.cisco.com:9120/cgna/ios/tunnel
active
!
!
cgna exec-profile CGNA-default-exec-profile
add-command event manager run no_config_replace.tcl flash:/before-tunnel-config cg-nms-tunnel 1 0
interval 1
exec-count 1
!
event manager environment ZTD_SCEP_CGNA_Profile cg-nms-tunnel
event manager environment ZTD_SCEP_LDevID_trustpoint_name LDevID
event manager directory user policy "flash:/managed/scripts"
event manager policy tm_ztd_scep.tcl type system authorization bypass
event manager policy no_config_replace.tcl type system authorization bypass
event manager environment ZTD_SCEP_Enabled TRUE
!
!
do write memory
!
do reload in 005
#await Proceed with reload?
#send_CR
!
crypto pki authenticate LDevID
!
end
 

 

Note: You can only migrate from CG4(3) to the minimum IOS image for that device. Refer to Table 1 for minimum IOS image requirements.

To add CGR IOS images to IoT Field Network Director and upload and install the migration image on CGRs:

1.blank.gif Select CONFIG > Firmware Update, and click the Migration to IOS tab.

 

421736.jpg

 

2.blank.gif In the Groups pane, select a CGR (or a group of CGRs) running CGOS4(5) software.

3.blank.gif Select the Cisco IOS software image to upload to the CGR(s), and click Upload Image (right-pane).

 

4.blank.gif Click OK to begin the upload.

 

Upload progress appears in the device list.

5.blank.gif Upload the following properties files (see Installing Cisco IoT FND in the Cisco IoT FND Installation Guide, 4.2.x.)

:

blank.gifconfig

blank.giftunnel provisioning

blank.gifbootstrap

blank.gifruntime configuration

6.blank.gif Click the Migrate To IOS button.

 

7.blank.gif Click Yes to confirm and begin the migration process.

 

The Update Progress displays as a percentage during the software image upload. If an upload fails, error messages and error details also appear for the software image. You can cancel, pause, or resume the migration process.

Tip: If any routers fail to upgrade, restart migration on the group. IoT Field Network Director skips routers that were successfully upgraded.

Interface Names After Migration

IoT Field Network Director preserves metrics for the various interfaces and associated properties during migration. CG-OS-to-IOS Interface Migration Map maps CG-OS interfaces to the corresponding IOS interfaces to preserve metrics.

Table 1 CG-OS-to-IOS Interface Migration Map

CG-OS Interface
Corresponding IOS Interface

Wifi2/1

Dot11Radio2/1

Ethernet2/1

GigabitEthernet2/1

Ethernet2/2

GigabitEthernet2/2

Ethernet2/3

FastEthernet2/3

Ethernet2/4

FastEthernet2/4

Ethernet2/5

FastEthernet2/5

Ethernet2/6

FastEthernet2/6

Wpan4/1

Wpan4/1

Serial1/1

Async1/1

Serial1/2

Async1/2

Cellular3/1

Cellular3/1

N/A

GigabitEthernet0/1

Working with Resilient Mesh Endpoint Firmware Images

This section describes how to add Resilient Mesh Endpoint (RME) firmware images to IoT FND, and how to upload and install the images on routers, and includes the following topics:

blank.gifUploading a Firmware Image to a Resilient Mesh Endpoint Group

blank.gifViewing Mesh Device Firmware Image Upload Logs

blank.gifViewing Mesh Endpoint Firmware Update Information

Note: IR500s and other RME devices can coexist on a network; however, for firmware management they cannot belong to the same group.

Note: RME devices can report BL/Boot Loader image types to IoT FND, but IoT FND cannot upload boot loader images to devices.

Uploading a Firmware Image to a Resilient Mesh Endpoint Group

To upload a firmware image to mesh endpoint group members:

1.blank.gif Choose CONFIG > Firmware Update.

2.blank.gif Click the Groups tab (left pane).

3.blank.gif Select the firmware group to update.

4.blank.gif In the right panel, select Firmware Management and the click Upload Image button and an entry panel appears.

a.blank.gif From the Select Type drop-down menu, choose the firmware type for your device.

IoT FND can upload these image types to ENDPOINT devices.

Image Type
Description

RF

RFLAN connected devices.

PLC

Power line communication devices.

BBU

Devices with battery back up.

LMAC

Local MAC connected devices.

PLC-RF

PLC-Radio Frequency devices.

IOx-IR500

IR500 devices.

b.blank.gif From the Select an Image drop-down menu, choose the firmware bundle to upload.

c.blank.gif Click Upload Image.

d.blank.gif Check the appropriate box based on the Selected Type and Image:

blank.gifInstall Guest OS from this bundle

blank.gifClean LoRaWAN application data on install?

blank.gifinstall WAPN firmware from this bundle:

e.blank.gif Click OK.

IoT FND adds the image to the list of images in the Firmware Management pane and starts the upload process in the background. A bar chart displays the upload progress (percent complete). You can filter the display by Subnet, PanId or Group.

 

425817.jpg

 

 

 

 

 

 

 

1

Sync membership button

Click button to sync the group members in the same firmware group.

For every image in the list, IoT FND displays the following information:

Column
Description

Image

Image name.

Uploaded

Specifies the number of devices that uploaded the image. Click the number to display a list of these devices.

Running

Specifies the number of devices running this image. Click the number to display a list of these devices.

Backup

Specifies the number of devices using this image as a backup. Click the number to display a list of these devices.

Boot Loader

Specifies the boot loader image version.

LMAC

Specifies the LMAC image version.

BBU

Specifies the BBU image version.

Status

Specifies the status of the upload process.

Scheduled Reload

Specifies the scheduled reload time.

Actions

Provides two actions:

blank.gifSchedule Install and Reload icon—Schedule the installation date and time of the loaded image and the rebooting of the endpoint.

blank.gifSet as Backup icon—Set the image as the backup image.

Setting the Installation Schedule

To set the installation schedule:

1.blank.gif Click the Schedule Install and Reload button under the Actions heading.

2.blank.gif Specify the date and time for the installation of the image and the rebooting of the device.

 

347188.tif

3.blank.gif Click Set Reboot Time.

blank.gifTo set the selected image as the firmware image backup, click the Set as Backup button.

4.blank.gif Click Yes.

blank.gifTo sync the group members in the same firmware group, click Sync Membership (1).

blank.gifTo view member devices, click the Devices tab.

blank.gifTo view log files for the group, click the Logs tab.

Viewing Mesh Device Firmware Image Upload Logs

To view the firmware image upload logs for mesh devices:

1.blank.gif Choose CONFIG > Firmware Update.

2.blank.gif Click the Groups tab (left-pane).

3.blank.gif Under the Firmware Groups heading of the Groups pane, select the Default-cgmesh firmware group.

4.blank.gif Click the Logs tab (right-pane).

Viewing Mesh Endpoint Firmware Update Information

You can view the endpoint firmware update process down to the subnet level for greater visibility. To view details of firmware updates for mesh endpoint devices (by Subnet, Pan Id or Group) in a table or histogram, during the upgrade process or after the firmware upgrade completes, follow these steps:

Note: For Subnet and Pan Ids, you must enter the value in the text box provided:

1.blank.gif Choose CONFIG > Firmware Update.

2.blank.gif Click the Groups tab.

3.blank.gif Under the Groups heading, select a mesh devices group (such as Default-cgmesh or Default-ir500).

4.blank.gif Click the Firmware Management tab (right-pane).

421740.jpg

 

 

Field
Description

(Top, Left Panel)

Upload Image radio button

Select the software image type and image type from the drop-down menus and. click Upload Image radio button to begin the firmware upload.
Note: By default, all subnets listed at the bottom of the screen will receive the image upload.

To exclude a subnet from the firmware upload, check the box (such as 1 or 2) next to that subnet. For more details, see PAN ID definition below.

Current Status

Status of the firmware upload (for example, Image Loading or Upload Finished).

blank.gifImage Loading, Upload Paused, Upload Stopped, Upload Finished, Upload Stopping, Upload Pausing

blank.gifScheduling Reload, Reload Paused, Reload Stopped, Reload Scheduling Finished, Reload Stopping, Reload Pausing

blank.gifSetting Backup, Backup Paused, Backup Stopped, Backup Finished, Backup Stopping, Backup Pausing

Image

Firmware image name.

Uploaded/Devices

Number of completed, successful firmware updates against the total devices that will receive the updates.

Error/Devices

Number of devices the operation failed (error) against the total devices in the group.

Not Synced/Devices

Number of firmware group membership non-synchronized devices against the total number of devices in the group.

(Right Panel) Histogram

% Completed

Visual status of upload percentage completed.

Filter by

Filter and display results by: Subnet, Pan ID, Group

(Bottom Panel)

All or RF

All displays information about all images in the Running, uploaded and backup slot as well as the BBU and PLC information for all device images (RF mesh, IR500 WPAN Range Extender and WPAN Range Extender with BBU and PLC) in the group; and the schedule reload and status information.

RF displays information regarding RF mesh images in the Running, uploaded and backup slots as well as the schedule reload and status information.

Image

Displays image file name and provides the completion percentage of the firmware upload (0 to 100) with respect to the following states:

blank.gifUploaded, Running, Backup, Bootloader, LMAC, BBU, Status, Sched Reload

Clear filter

Click radio button to clear selected firmware image update results.

PAN ID

Identifies the Personal Area Network Identifier for a group of endpoints (nodes).

To exclude a group of nodes from a new firmware upload, you must select the Pan ID check box next to that group of nodes before selecting the Upload Image radio button in the Firmware Management pane.

Note: The check boxes next to the PAN IDs are not visible during a firmware upload.

Note: You can sort PAN IDs in an ascending or descending manner or filter by PAN ID to define which PAN ID displays in the window by selecting the downward arrow to the right of the column. Select Clear Filter to leave that view.

Note: To see a listing of all nodes within a subnet, select the Device tab.

Subnet Prefix

Identifies the IPv6 subnet prefix for the endpoint. To view all of the nodes within a given subnet, select the Devices tab.

Note: You can filter by Subnet by entering a portion of the subnet (for example, 200b:0:0) by selecting the downward arrow to the right of the column. Select Clear Filter to leave that view.

Nodes in Group

Number of nodes within the group. In the screen shot above, there are a total of 25 nodes within the group, which are split across two different subnets (8 nodes in 200b:0:0:0:0:0:0:0 and 17 nodes in 200c:0:0:0:0:0:0:0).

Total in Subnet

Number of nodes with the subnet. In the screen shot above, there are 19 nodes in the subnet.

Upload status

Number of nodes out of the total nodes that have been successfully upgraded with the new firmware.

Last message sent

Display of latest message relevant to the current firmware update process within the given PAN.

 

 

Viewing Mesh Device Firmware Information

To view the firmware information for mesh devices:

1.blank.gif Choose CONFIG > Firmware Update.

2.blank.gif Click the Groups tab.

3.blank.gif In the Groups pane under the Firmware Groups heading, select a Mesh devices group.

4.blank.gif Click the Devices tab.

 

425816.jpg

 

 

 

For every device in the group, IoT FND displays the following Device Info:

Field
Description

Status

Status of the device (for example, Up, Down, or Unheard).

Name

EID of the device.

IP Address

IP address of the device.

Firmware Version

Version of the firmware image running on the device.

Backup Version

Version of the firmware image used as a backup.

Uploaded Version

Version of the firmware image loaded on the device.

Boot Loader Version

Version of bootloader loaded on the device.

LMAC Version

Version of Local MAC connected device.

BBU Version

Displays BBU version if present on device.

Member Synced?

Whether the device is in sync with the rest of the group.

Activity

Firmware image upload activity.

Update Progress

Firmware image upload progress. An update progress of 100% indicates that the upload is complete.

Last Firmware Status Heard

Last time the firmware status was heard.

Scheduled Reload Time

The time set for upload image reloads.

Error Message

Error message if image upload failed.