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
IPv6 Network Layer
RMEs implement standard IPv6 services. The IPv6 layer forwards IPv6 datagrams between the mesh and serial interfaces. The IPv6
layer also uses the mesh interface to forward IPv6 datagrams across other communication modules.
• RMEs support both unicast and multicast forwarding. Layer-3 multicast is mapped to Layer-2 broadcast.
• RFC 768 User Datagram Protocol (UDP) is the recommended transport layer protocol over 6LoWPAN.
• TCP is not the preferred transport layer over 6LoWPAN and is generally not used by RMEs.
• The default IPv6 MTU is 1280 bytes. Higher layers might limit the size of link frames to a smaller value. As described in
6LoWPAN Adaptation, on page 14, the Cisco 6LoWPAN implementation supports an 800-byte MTU.
IPv6 Protocols
Cisco Resilient Mesh implements the following protocols to support IPv6:
• RFC 2460: Internet Protocol version 6
• RFC 4291: IP Version 6 Addressing Architecture
• RFC 6724: Default Address Selection for Internet Protocol Version 6 (IPv6)
• RFC 4861: Neighbor Discovery for IPv6
• RFC 4443: ICMP for the Internet Protocol Version 6 (IPv6)
• RFC 3315: Dynamic Host Configuration Protocol for IPv6
Autoconfiguration
RMEs implement a DHCPv6 client for IPv6 address autoconfiguration. RMEs also support arbitrary DHCPv6 options (that is, vendor
option 17) to allow additional stateless configuration information to be included in DHCPv6 replies from the server. Cisco Resilient
Mesh uses the DHCPv6 Rapid Commit option to reduce the traffic to only Solicit and Reply messages, so the DHCPv6 server must
support this option.
RMEs implement a DHCPv6 client, while the CGR implements a DHCPv6 Relay Agent. A joining node might not be within range
of a CGR and must use a neighboring communication module to make DHCPv6 requests.
On a RME, no DHCPv6 server address needs to be configured. The DHCPv6 client requests are sent to the DHCPv6 Relay Agent
on the CGR. The DHCPv6 Relay Agent forwards the DHCPv6 client messages to the DHCPv6 server.
RPL
RMEs perform routing at the network layer using the Routing Protocol for Low-Power and Lossy Networks (RPL):
• RFC 6550 RPL: IPv6 Routing Protocol for Low-Power and Lossy Networks (RPL) (to establish routes for delivering unicast
IPv6 datagrams to their destinations).
• RFC 6551: Routing Metrics Used for Path Calculation in Low-Power and Lossy Networks
• RFC 6553: The Routing Protocol for Low-Power and Lossy Networks (RPL) Option for Carrying RPL Information in Data-Plane
Datagrams
• RFC 6554: An IPv6 Routing Header for Source Routes with the Routing Protocol for Low-Power and Lossy Networks (RPL)
• RFC 6206: The Trickle Algorithm
16
REVIEW DRAFT - CISCO CONFIDENTIAL