Release Notes for Cisco Resilient Mesh Release 6.2.47

12/19/2025

CR-Mesh Release 6.2.47

Performance

Optimize Itron CE Meter readrate

Improves Itron Collection Engine(CE) meter readrate performance, For more information refer, CSCwj01674

Ease of use

Set Wi-SUN as default stack mode

Itron meter boots by default in Wi-SUN stack mode when stack mode is not explicitly configured in boot config.bin. For more information see, CSCws36096

CSCwj01674

Improves Itron Collection Engine(CE) meter readrate performance,

CSCws36096

Itron meter boots by default in Wi-SUN stack mode when stack mode is not explicitly configured in boot config.bin.

CSCvz38077

Symptom: Fail to refresh pub key via EST when OFDM WPAN and Itron node are working in PHY mode 2. Conditions: This issue occurs when: CG-mesh stack mode with phymode 2 OFDM WPAN in Release 6.2 + Itron node in Release 5.6 or 6.2 802.1x certificate length is too long (more than 700 bytes) Workaround: Use certificate less than 700 bytes.

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.

Cisco 1000 Series Connected Grid Router

Cisco IOS Release 15.9(3)M4 or later

Cisco Catalyst IR8100 Heavy Duty Series Routers

Cisco IOS-XE Release 17.6.1a or later

Cisco IR530

cg-mesh-node-6.2MR-6247-RELEASE-ir530-55443e5.bin

Cisco IR510

cg-mesh-dagw-6.2MR-6247-RELEASE-ir510-55443e5.bin

WPAN FSK module

cg-mesh-bridge-ITRDPKG-6.2MR-6247-itron30-55443e5.bin

WPAN OFDM module

cg-mesh-bridge-6.2MR-6247-ir510-55443e5.bin

Cisco IoT FND

Cisco IoT FND Release 4.9.0 or later

IOx

1.6.1.3

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

CR-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.

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

CoAP Simple Management Protocol

CR-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 RMEs 30 (meters), CSMP service is exposed via both CoAP RFC port (UDP 61628) and Draft port (UDP 61624). But communication with Cisco IoT FND will continue to be on RFC port for all the RMEs.

Power outage notification

CR-Mesh supports timely and efficient reporting of power outages and restorations.

In the event of a power outage, CR-Mesh enters power-outage notification mode and the node stops listening for traffic to conserve energy. CR-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 CR-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 Endpoints

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