Technical Specs
Table Of Contents
- Cisco Connected Grid WPAN Module for CGR 1000 Series Installation and Cisco Resilient Mesh Configuration Guide (Cisco IOS)
- Cisco Connected Grid WPAN Module for CGR 1000 Series Installation and Cisco Resilient Mesh Configuration Guide (Cisco IOS)
- Hardware Overview
- WPAN Antennas, Connectors, and Cables
- Installing and Removing the Module
- Technical Specifications
- Information About Cisco Resilient Mesh and WPAN
- Configuring Cisco Resilient Mesh and the WPAN Module
- Configuring the WPAN Interface
- Configuring the CGM WPAN OFDM Module
- Configuring Adaptive Modulation
- Configuring Group Multicast
- Configuring RPL
- Configuring IPv6
- Configuring PON RPL
- Configuring the Power Outage Server
- Configuring QoS
- Configuring Cisco Resilient Mesh Security
- Configuring IPv6 Multicast Agent
- Configuring Dual-PHY WPAN
- Configuring DTLS Relay for EST
- Configuring Wi-SUN Mode
- Verifying Connectivity to the CGR
- show Command Examples
- Debugging the WPAN Module
- Sample Router Configuration
- Sample CGR and ASR Configuration
- Checking and Upgrading the WPAN Firmware Version
- Related Documentation
- Obtaining Documentation and Submitting a Service Request
EST provides an operation for the client to retrieve a bundle of CA certificates from the server, including 802.1x CA and the NMS
certificate, as well as the EST-related certificates.
EST supports the enrollment operation of client generating its own private key. With client-side key generation, the client sends a
/sen (simpleenroll) request with the CSR. The EST server processes the request and if it is valid, returns the client certificate in a
PKCS7 Response. The certificate will include the public key from the CSR.
During bootstrapping this enrollment process is performed twice. First the client authenticates with the Manufacturer IDevID and
enrolls the Utility IDevID. After that it authenticates with the Utility IDevID and enrolls the Utility LDevID. The Utility LDevID is
then used for the 802.1X authentication.
Power Outage Notification
Cisco Resilient Mesh supports timely and efficient reporting of power outages. 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. Communication modules, unaffected by the
power outage, gather and forward the information to a CGR.
When power outage happens, if the outage node’s backup power is adequate, its Power Outage Notification (PON) message will be
sent as broadcast once. Any node receiving the PON message will delete this parent based on the hold up time if it exists. Such node
is called powered outage node.
If the outage node’s backup power is limited, its PON message will be sent as broadcast three times. Any node receiving the PON
message will delete this parent directly if the route exists and forward it to the outage server. Such node is called normal outage
node.
Under outage mode, powered outage node will still send its PON and relay children’s PONs to its parent as unicast. However, normal
outage node is in deep sleep mode until the next broadcast transmission. Receiving and unicasting transmission is disabled.
To improve the PON success rate, PON RPL instance is introduced in Wi-SUN mode in the Cisco Resilient Mesh Release 6.2.
• If node's PON RPL instance is valid and at least one parent is available, parent should be the preferred parent of PON RPL
instance.
• If node's PON RPL instance has no available parent, parent should be the preferred parent from Core RPL instance.
• If node's PON RPL instance has no available parent, the node must drop the packet from PON RPL instance.
To configure PON RPL, see Configuring PON RPL, on page 35.
To configure outage server address, see Configuring the Power Outage Server, on page 35.
Software Upgrade
You can perform firmware upgrades through the CGR CLI (Cisco IOS). WPAN firmware is not upgraded automatically when the
CGR is upgraded to a new image integrated with new WPAN firmware.
You can upgrade the WPAN to the firmware version integrated in the CGR image, or you can upgrade to a custom WPAN firmware
other than the one integrated in current CGR image. For more information, see Checking and Upgrading the WPAN Firmware Version,
on page 81.
Performance
RMEs support the following performance-enhancing features:
23
REVIEW DRAFT - CISCO CONFIDENTIAL










