First Published: March 21, 2024

Release Notes for Cisco Resilient Mesh Release 6.8

These release notes contain the latest information about using Cisco Resilient Mesh (CR-Mesh, formerly known as CG-Mesh) with IPv6 Resilient Mesh Endpoints (RMEs) such as meters and the Cisco IR500 Series WPAN Gateway Range Extenders.

Cisco Resilient Mesh is an embedded network stack for Smart Grid assets within a Neighborhood Area Network. Cisco Resilient Mesh provides end-to-end IPv6 communication and implements open-standard protocols at every layer in the network stack, including but not limited to IEEE 802.15.4e/g, 6LoWPAN, IPv6, RPL, UDP, and CoAP. In Smart Grid assets such as residential electric meters, the Cisco Resilient Mesh software functions within a dedicated Communications Module that connects to an Application Module through a PPP link.

From CR-Mesh Release 6.3, only Wi-SUN protocol stack is supported. In CR-Mesh Release 5.6, only classic CR-Mesh protocol stack is supported. CR-Mesh Release 6.2 supports both Wi-SUN and classic CR-Mesh stack, in which you can use the configuration option "stack mode" to choose CR-Mesh or Wi-SUN mode.


Note

IR509 are not supported from CR-Mesh Release 6.3 and later releases. IR529 are not supported from CR-Mesh Release 6.4 and later releases.


Note

For a detailed description of the Cisco Resilient Mesh software features, refer to Cisco Connected Grid WPAN Module for CGR 1000 Series Installation and Cisco Resilient Mesh Configuration Guide.

For configuration on Cisco Catalyst IR8140 Heavy Duty Series Routers, refer to Cisco Catalyst IR8140 Heavy Duty Series Router Software Configuration Guide

Release Notes for Cisco Resilient Mesh Release 6.8

These release notes contain the latest information about using Cisco Resilient Mesh (CR-Mesh, formerly known as CG-Mesh) with IPv6 Resilient Mesh Endpoints (RMEs) such as meters and the Cisco IR500 Series WPAN Gateway Range Extenders.

Cisco Resilient Mesh is an embedded network stack for Smart Grid assets within a Neighborhood Area Network. Cisco Resilient Mesh provides end-to-end IPv6 communication and implements open-standard protocols at every layer in the network stack, including but not limited to IEEE 802.15.4e/g, 6LoWPAN, IPv6, RPL, UDP, and CoAP. In Smart Grid assets such as residential electric meters, the Cisco Resilient Mesh software functions within a dedicated Communications Module that connects to an Application Module through a PPP link.

From CR-Mesh Release 6.3, only Wi-SUN protocol stack is supported. In CR-Mesh Release 5.6, only classic CR-Mesh protocol stack is supported. CR-Mesh Release 6.2 supports both Wi-SUN and classic CR-Mesh stack, in which you can use the configuration option "stack mode" to choose CR-Mesh or Wi-SUN mode.


Note

IR509 are not supported from CR-Mesh Release 6.3 and later releases. IR529 are not supported from CR-Mesh Release 6.4 and later releases.


Note

For a detailed description of the Cisco Resilient Mesh software features, refer to Cisco Connected Grid WPAN Module for CGR 1000 Series Installation and Cisco Resilient Mesh Configuration Guide.

For configuration on Cisco Catalyst IR8140 Heavy Duty Series Routers, refer to Cisco Catalyst IR8140 Heavy Duty Series Router Software Configuration Guide

System Requirements

If you plan to run Cisco Resilient Mesh Release 6.8, you must have the following required hardware and software components:

Platform

Minimum Cisco IOS Software Release Required

Cisco 1000 Series Connected Grid Router (CGR)

Cisco IOS Release 15.9(3)M4 or later

Cisco Catalyst IR8100 Heavy Duty Series Routers

Cisco IOS-XE Release 17.14.1 or later

Cisco IR530

cg-mesh-node-6.8-6800-RELEASE-ir530-aa08a7f.bin

Cisco IR510

cg-mesh-dagw-6.8-6800-RELEASE-ir510-aa08a7f.bin

WPAN FSK module

cg-mesh-bridge-ITRDPKG-6.8-6800-itron30-aa08a7f.bin

WPAN OFDM module

cg-mesh-bridge-6.8-6800-ir510-aa08a7f.bin

IoT Field Network Director

Release 4.10 or later

IOx

1.6.1.3

Supported Software Features

This section covers the supported software features.

Compromised Node Eviction

A compromised node is one where the device can no longer be trusted by the network and/or operators. Nodes within an IEEE 802.15.4 PAN must possess the currently valid Group Temporal Key (GTK) to send and receive link-layer messages. The GTK is shared among all devices within the PAN and is refreshed periodically or on-demand by communicating new GTKs to only trusted devices, and compromised nodes may be evicted from the network.

RPL

In its route-over architecture, Cisco Resilient Mesh performs routing at the network layer using the Routing Protocol for Low-Power and Lossy Networks (RPL).

Cisco Resilient Mesh requires a Cisco 1000 Series Connected Grid Router (CGR) or Cisco Catalyst IR8140 Heavy Duty Router (IR8140H) to provide connectivity to other IPv6 networks. The CGR or IR8140H (Field Area Router (FAR)) must serve as a RPL Directed Acyclic Graph (DAG) root and store information reported in DAO messages to forward datagrams to individual nodes within the mesh network.

6LoWPAN

The 6LoWPAN adaptation layer adapts IPv6 to operate efficiently over low-power and lossy links such as IEEE 802.15.4. The adaptation layer sits between the IPv6 and IEEE 802.15.4 layers and provides IPv6 header compression, IPv6 datagram fragmentation, and optimized IPv6 Neighbor Discovery.

Frequency Hopping

Cisco Resilient Mesh implements frequency hopping across 64 channels with 400-kHz spacing in the 902 to 928 MHz ISM band. The frequency-hopping protocol used by Cisco Resilient Mesh maximizes the use of the available spectrum by allowing multiple sender-receiver pairs to communicate simultaneously on different channels. The frequency hopping protocol also mitigates the negative effects of narrowband interferers.


Note

For IR510 and IR530 endpoints, high data rates 1.2Mbps with 31 channels are also supported.

FND Configuration

Cisco Resilient Mesh solution is managed and monitored by the Cisco IoT Field Network Director (FND), which provides the necessary backend network configuration, monitoring, event notification services, network stack firmware upgrade, as well as FND outage and meter registration. IoT FND also retrieves statistics on network traffic from the interface.


Note

For a detailed description on the Cisco Resilient Mesh CLI, refer to Cisco Connected Grid WPAN Module for CGR 1000 Series Installation and Cisco Resilient Mesh Configuration Guide (Cisco IOS).


Note

For more information on the IR8140H router configuration, refer to Cisco Catalyst IR8140 Heavy Duty Series Router Software Configuration Guide.


Note

IR510 and IR530 will be supported only with FND Release 4.1 or greater. Refer to the Cisco IoT Field Network Director User Guides for details.

CoAP Simple Management Protocol

Cisco Resilient Mesh implements the CoAP Simple Management Protocol (CSMP) for remote configuration, monitoring, and event generation over the IPv6 network. The CSMP service is exposed over both the mesh and serial interfaces. For backward compatibility on Itron 30 meters, CSMP service is exposed via both CoAP RFC port (61628) and Draft port (61624). But communication with FND will continue to be on RFC port for all the RMEs.

Power-outage Notification

Cisco Resilient Mesh supports timely and efficient reporting of power outages and restorations.

In the event of a power outage, Cisco Resilient Mesh enters power-outage notification mode and the node stops listening for traffic to conserve energy. Cisco Resilient Mesh triggers functions to conserve energy by notifying the communication module and neighboring nodes of the outage. The outage notification is sent using the same security settings as any other UDP/IPv6 datagram transmission.

In the event of a power restoration, a Cisco Resilient Mesh node sends a restoration notification using the same communication method as the outage notification. The communication modules unaffected by the power outage event deliver the restoration notification.

Registration of Endpoint

You can register and manage Cisco Resilient Mesh Endpoints (RMEs) such as meters using the IoT FND (which uses the CSMP protocol).

Limitations and Restrictions

Cisco recommends that you review this section before you begin working with the module. These are known limitations that will not be fixed, 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 router hardware or software.

  • CSCub49104

    Symptom: Output from show mesh-security session all does not show all current mesh security sessions.

    Conditions: This issue occurs in the output of the show mesh-security session all command.

    Workaround: To find out the mesh-key status of a meter, use the show mesh-security session mac <mac-address> command.

  • CSCvs69721

    Symptom: IR530 will hang if downgrading from 6.2 to 6.0.19 with unsupported phy modes configured.

    Conditions: This issue occurs when IR530 configured with phy mode 1 or 2 is downgraded from 6.2 to 6.0.19 (phy modes 1 and 2 are supported in 6.2 but not supported in 6.0.19).

    Workaround: The workaround is (1) creating a configuration file with supported phy modes in 6.0, or (2) changing phy mode to a supported phy mode in 6.0 before downgrade.

  • CSCvu31508

    Symptom: WiSUN: Demo mode not mapping to network scale after upgrade from 5.6.x to 6.3.

    Conditions: In 5.6.x, demo = True, after upgrade to 6.3.x the network scale is large.

    Workaround: The workaround is to configure the network scale manually and reboot after the upgrade.

  • CSCvv02636

    Symptom: Itron30 EST: reenroll 802.1x certificate failed after manufacture idevid cert is expired on 6.3

    Conditions: When itron30's 802.1x certificate in 5.6.x is close to lifetime, at this time, upgrade itron30 from 5.6.x to 6.3 or afterwards. After upgrade to 6.3 or afterwards, the 802.1x certificate is copied as Manufacture IDevid for EST use, and when this copied Manufacture IDevid is expired, itron30 node on 6.3 can not do bootstrap EST process.

    Workaround: Before upgrade from 5.6.x to 6.3, do reenrollment of 802.1x public key and provide a long lifetime to this cert, so that when itron30 boots up on 6.3, the copied Manufacture IDevID cert can also get a long lifetime. This could provide a long-term way for itron30 node to do EST in the future.

  • CSCvn79551

    Symptom: No EAP response after sending the first EAP fragment to IR529 or CGEREFx.

    Conditions: 1) Set the EAP fragment size to 1024 bytes on radius server. 2) Cert file of the server is larger than 1024 bytes. 3) Trigger mesh node to do authentication. After radius server sent the first EAP fragment to mesh node, mesh node didn't reply any information, thus the authentication failed to continue.

    Workaround: Modify the max EAP fragment size to 512 bytes on radius server.

  • CSCvn79799

    Symptom: Node can't get online after downgraded from 6.x to 6.0.19 when mesh mixed with 6.0 and 6.x.

    Conditions: The WPAN image is not downgraded.

    Workaround: Downgrade the WPAN image and all other nodes to 6.0.19 as well.

  • CSCvs56568

    Symptom: 6.2 bridge can not work with Wi-SUN 6.1 if enable PON RPL.

    Conditions: This issue occurs when WPAN image is 6.2, and RPL PON instance is set on CGR.

    Workaround: Disable RPL PON instance on CGR, or upgrade all ir5xx to 6.2 image.

  • CSCvs57388

    Symptom: Wi-SUN: Node cannot register to fnd when node and wpan version mismatch.

    Conditions: This issue occurs when node is in release 6.1 and CGR WPAN is in release 6.2. Same problem exists when node is in release 6.2 and WPAN is in release 6.1.

    Workaround: Use the same release image on node and CGR WPAN. When upgrade from 6.1 to 6.2 using FND, upgrade the node first and then upgrade WPAN.

  • CSCvs57488

    Symptom: After image upgrade to 6.2.16 or later, IR510 EUI may be changed. Node may get a new global ipv6 address. The old EUI/address in CGR RPL table and FND will not work anymore.

    Conditions: This issue occurs when upgrade image from 6.x (for example, 6.0.x or 6.1.x) to 6.2.16 or later. Some IR510 EUI may be changed, but not all of them have this issue.

    Workaround: Import the new EUI to the FND and remove the old EUI. Wait for the old address timeout on the CGR RPL table.

Caveats

This section addresses the Open and Resolved caveats that are relevant to Cisco Resilient Mesh. This section also provides information on how to use the Bug Tool Kit to find further details on the caveats.

Resolved Caveats

This section summarizes resolved caveats to the Cisco Resilient Mesh 6.8 release.

  • CSCwe03920

    CR-Mesh Serviceability enhancements for WPAN.

  • CSCwe29452

    ACK frame sequence number validation for DFE transmissions.

  • CSCwh99263

    FAN Router registration refresh request support.

  • CSCwd54796

    Incorrect LFN active key index in PC frame sent from FAN Router.

  • CSCwj34691

    WPAN hardware configs out-of-sync with IR8140 after the WPAN crash.

Accessing 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 Bug Search Tool, you need the following items:

  • Internet connection

  • Web browser

  • Cisco.com user ID and password

To access the Bug Search Tool, enter the following URL:

https://tools.cisco.com/bugsearch/search

Feature History

Feature

Cisco IOS Release

Feature information

Cisco Resilient Mesh firmware 6.8

Cisco IOS Release 15.9(3)M4 or later

Cisco Resilient Mesh enhancement.

Cisco Resilient Mesh firmware 6.8

Cisco IOS XE 17.14.1 or later

Cisco Resilient Mesh enhancement.

Related Documentation

Consult the following resources for related information about the Connected Grid WPAN Module for technical assistance.

Hardware Overview and Installation