CG Mesh Debugging Tips

Document created by mathaker on May 29, 2014Last modified by mathaker on Sep 18, 2014
Version 4Show Document
  • View in full screen mode

This document briefly describes steps regarding debugging when mesh network does not form as expected. Debugging procedure typically includes below:

  • Check Physical Connectivity
  • Check the FAR
  • Check the Node

Check Physical Connectivity

For PLC, make sure that the wiring is done properly between the FAR and the Nodes ---  they should communicate on the same AC line.

For RF-mesh, make sure the nodes are in physical proximity of the FAR, but not too close as the receiver may get saturated.  2 meters may be a good distance.

Check the FAR

  • Check the FAR  configuration ( typical configuration for non-secure network).  Type at the FAR console:

plc-3# show run

And look for the following lines:

feature dhcp

interface Ethernet2/2

ipv6 address 2001:a:b:c::930/64

ipv6 dhcp relay destination 2001:a:b:c::100  <-- this is the dhcp server ipv6 address, make sure it is pingable from the FAR.

interface Wpan4/1

  no shutdown

  rpl prefix 2013:dead:beef:cafe::/64

  panid 60

  ssid itron-cisco-linda  <-- Make sure this is the same as programmed in node

  ieee154_beacon_async 30 60 1  <-- this is for testing only --- speeding up network forming

  ipv6 address 2013:dead:beef:cafe::/64

  ipv6 dhcp relay client-interface 


plc-3# show wpan config in-hardware all

serial_num: 2D-00-21-00-0E-47-31-30

eui64: 00-17-3B-0E-00-21-00-2D

ssid: itron-cisco-linda

panid: 60

txpower: 32

sec_mode: 0

phase: 1

ieee154_beacon_async: 30 60 1

  • Check wpan packet counts

plc-3# show wpan packet-count

TOTAL:

     incoming: 152424 (20990085 bytes)

     outgoing: 25806 (2675758 bytes)

-------------------------------------------------

lowpan:

     incoming: 152424 (20990085 bytes)

     outgoing: 25806 (2675758 bytes)

dot1x:

     incoming: 0 (0 bytes)

     outgoing: 0 (0 bytes)

outage:

     incoming: 0 (0 bytes)

-------------------------------------------------

lowpan.icmp:

     incoming: 48504 (5671166 bytes)

          rpl dao: 7541 (1286474 bytes)

          rpl dio: 13637 (1770980 bytes)

          rpl dis: 0 (0 bytes)

          nd ns : 8448 (650400 bytes)

     outgoing: 24040 (2554923 bytes)

          rpl ra : 1781 (240435 bytes)

          nd rs : 8 (384 bytes)

lowpan.dhcp:

     incoming: 342 (39747 bytes)

     outgoing: 185 (36981 bytes)

lowpan.csmp:

     incoming: 7420 (4508833 bytes)

          - mcast: 0 (0 bytes)

          - ucast: 7420 (4508833 bytes)

     outgoing: 1578 (83566 bytes)

          - mcast: 0 (0 bytes)

          - ucast: 1578 (83566 bytes)

lowpan.c1222:

     incoming: 0 (0 bytes)

          - mcast: 0 (0 bytes)

          - ucast: 0 (0 bytes)

     outgoing: 0 (0 bytes)

          - mcast: 0 (0 bytes)

          - ucast: 0 (0 bytes)

lowpan.unknown:

     incoming: 0 (0 bytes)

     outgoing: 3 (288 bytes)

-------------------------------------------------

ucast:

     incoming: 42630 (8449521 bytes)

     outgoing: 1768 (121067 bytes)

mcast:

     incoming: 96157 (10769584 bytes)

     outgoing: 22246 (2313584 bytes)

bcast:

     incoming: 13637 (1770980 bytes)

     outgoing: 1792 (241107 bytes)

-------------------------------------------------

bridge:

     incoming: 9065 (109670 bytes)

     outgoing: 9063 (90200 bytes)

-------------------------------------------------

(cgos):

     incoming: 33792 (3655889 bytes)

     outgoing: 152452 (23130279 bytes)

(hdlc):

     incoming: 240892 (28884680 bytes)

     outgoing: 79361 (12114401 bytes)

-------------------------------------------------

udp checksum error:

     incoming: 1 (755 bytes)

     icmp checksum error: incoming: 0 (0 bytes)


  • Start ethanalyzer on FAR

Router# term len 0

Router#ethanalyzer local interface wpan limit-captured-frames 0

total args=7

/usr/bin/sudo tshark -t ad -l -i wpan0

2013-01-15 16:40:15.935782 fe80::217:3b0b:2a:31 -> fe80::217:3b0e:21:2d ICMPv6 Neighbor solicitation

2013-01-15 16:40:15.937194 fe80::217:3b0e:21:2d -> fe80::217:3b0b:2a:31 ICMPv6 Neighbor advertisement

2013-01-15 16:40:16.944249 2013:dead:beef:cafe:abcd:3b0b:35:30 -> 2013:dead:beef:cafe:: ICMPv6 Unknown (0x9b) (Unknown (0x02))

2013-01-15 16:40:18.177917 fe80::217:3b0b:2a:31 -> ff02::1a ICMPv6 Unknown (0x9b) (Unknown (0x01))


  • Wait for the neighbor table (How to See the WPAN Neighbor Table) to form if node is communicating with FAR --- when seeing nodes in the neighbor table, this usually is a good sign.

PLC:

plc-3# show wpan linknbrs table

------------------------------------------------------------------------ WPAN LINK NEIGHBOR TABLE ------------------------------------------------------------------------

EUI64                   RSSIF   RSSIR   LQIF    LQIR    MODF    MODR    TXGAINF TXGAINR TXRESF  TXRESR  TONEMAPF    TONEMAPR    TXCOEFFF    TXCOEFFR    PHASE   LAST_HEARD

00173b0e00400037        98      98      14      14      DQPSK   D8PSK   1       1       6       6       00003f      00001f      01ff01ff    01ff01ff    0       18:45:56

00173b05002b003a        98      98      14      14      D8PSK   D8PSK   1       1       6       6       00003f      00003f      01ff01ff    01ff01ff    0       18:48:19

00173b060026003d        98      98      14      14      D8PSK   D8PSK   1       1       6       6       00003f      00001f      01ff01ff    01ff01ff    0       18:42:42

00173b060029003d        98      98      17      17      D8PSK   DQPSK   1       1       6       6       00003f      00003f      01ff01ff    01ff01ff    0       18:45:02

00173b060031003c        98      98      14      14      D8PSK   D8PSK   1       1       6       6       00003f      00003f      01ff01ff    01ff01ff    0       18:46:21

00173b0600380041        98      98      14      14      DQPSK   D8PSK   1       1       6       6       00000e      00003f      01ff01ff    01ff01ff    0       18:37:17

00173b0700180032        98      98      14      14      ROBO    D8PSK   1       1       6       6       00001f      00003f      01ff01ff    01ff01ff    0       18:47:06

00173b07001e0036        98      98      14      14      D8PSK   D8PSK   1       1       6       6       00003f      00003f      01ff01ff    01ff01ff    0       18:46:50

00173b07002f0040        98      98      14      14      D8PSK   D8PSK   1       1       6       6       00003f      00001f      01ff01ff    01ff01ff    0       18:47:04

00173b07002f0042        98      98      14      14      D8PSK   D8PSK   1       1       6       6       00003f      00001f      01ff01ff    01ff01ff    0       18:39:18

00173b0700330032        98      98      11      11      D8PSK   D8PSK   1       1       6       6       00003f      00003f      01ff01ff    01ff01ff    0       18:44:36

00173b0700360032        98      98      14      14      D8PSK   DQPSK   1       1       6       6       00003f      00003f      01ff01ff    01ff01ff    0       18:44:38

00173b070039003e        98      98      14      14      D8PSK   DQPSK   1       1       6       6       00003f      00003f      01ff01ff    01ff01ff    0       18:48:31

00173b0b0019002f        98      98      17      17      DQPSK   DQPSK   1       1       6       6       00000f      00003f      01ff01ff    01ff01ff    0       18:48:54

00173b0b0026001f        98      98      14      14      DQPSK   DQPSK   1       1       6       6       00003f      00003f      01ff01ff    01ff01ff    0       18:45:30

00173b0b002a0031        98      98      14      14      D8PSK   D8PSK   1       1       6       6       00003f      00003f      01ff01ff    01ff01ff    0       18:46:13

00173b0b002e001e        98      98      14      14      D8PSK   DQPSK   1       1       6       6       00003f      00003f      01ff01ff    01ff01ff    0       18:46:31

00173b0b0032001a        98      98      14      14      DQPSK   DQPSK   1       1       6       6       00000f      00003f      01ff01ff    01ff01ff    0       18:48:00

00173b0b00330030        98      98      14      14      D8PSK   D8PSK   1       1       6       6       00003f      00003f      01ff01ff    01ff01ff    0       18:48:11

00173b0b00350030        98      98      14      14      D8PSK   D8PSK   1       1       6       6       00003f      00003f      01ff01ff    01ff01ff    0       18:42:43

00173b0b003b0030        98      98      14      14      D8PSK   D8PSK   1       1       6       6       00003f      00003f      01ff01ff    01ff01ff    0       18:48:18

 

RF-mesh:

CDN-CGR1240-1# show wpan linkn tab

-------------------------- WPAN LINK NEIGHBOR TABLE ----------------------------

EUI64 RSSIF RSSIR LQIF LQIR FIRST_HEARD LAST_HEARD

00173bab00c183f2 -60 -66 36 9 16:13:59 19:29:29

00173bab00c183fe -51 -49 5 61 16:13:22 19:26:32

Number of Entries in WPAN LINK NEIGHBOR TABLE: 2

Check the Node

  • The primary means of getting diagnostic information from the node CM is via its PPP host interface.  The CSMP protocol can be used on this interface to get certain TLVs that will help you debug the connection.  The CSMP GUI tool can be downloaded from here: CG-MeshDocumentation is included in the download.

  • The GUI tool can operate over PPP as well as over the ethernet interface.  In this case will need to use it over the PPP host interface since the CG mesh communications may not be verified yet.  Assuming that you have the tool downloaded and configured to talk to the PPP port of the CM, the following steps will help you debug the CM.

Following GUI screenshots are all captured from the CSMP GUI tool.

  • Make sure the FW running on the Node is the same as FAR. From node, retrieve TLV 75 to get the FW version running which should match the bridge FW on the FAR.

plc-3# show wpan in-hardware version

version: 5.3.8, cg-mesh-bridge, cg-mesh-5.3.8, 3e26aaa, Jan  7 2013, (lmac-0.0.1.1)

4.jpg

  • Using the CSMP GUI tool retrieve the TLVs 35 and 52 from the CM.  In TLV 35, verify that the SSID matches what is configured on the FAR's WPAN interface.
  • Look for the radio signal strength indicators -- RSSI Forward and RSSI Reverse values in the TLV 52 results.  They should be higher than -90 dBm.  If they are in the -100 dBm range, check that you have an antenna connected to the CM and that it is not loose.
    • "RSSI Reverse" refers to the received signal strength as measured by the local node's Comm Module.
    • "RSSI Forward" refers to the signal strength of the packets transmitted by the local node as measured by a remote receiving node and then conveyed back to the local node in L2 mesh transmissions.  If the local node has not yet jpoined the mesh or not received any transmissions from remte nodes, this value may be very low.
  • For indoor debugging on the lab bench, make sure that the power levels on the FAR and node are set to defaults.  On the node and the FAR the default is -36 dBm.  As the setting is configurable on the FAR, please be sure to set it to "low" as follows:

config term

int wpan4/1

  txpower low

  exit

exit

copy running-config startup-config <----CGOS only

write mem <---- IOS only

  • Using the CSMP GUI tool to retrieve information from Node, such as TLV "2/DeviceID" --- this value should match entry in FAR's neighbor table.

5.jpg

plc-3# show wpan linknbrs table

------------------------- WPAN LINK NEIGHBOR TABLE ----------------------------------------------------------

EUI64            RSSIF RSSIR LQIF LQIR MODF  MODR TXGAINF TXGAINR TXRESF TXRESR TONEMAPF TONEMAPR TXCOEFFF TXCOEFFR PHASE LAST_HEARD

00173b0e00400037 98    98    14   14   DQPSK D8PSK 1      1       6      6      00003f   00001f   01ff01ff 01ff01ff 0     18:45:56

  • When Node and FAR are in sync, Node should see the "panid" configured on the FAR when pull TLV "20/WPANSetting". In our case with above configuration, it will take around 10 ~ 20 minutes when we see the value change from 65535 to the configured value "60".

6.jpg

   From the FAR, issue "show run interface wpan4/1"

interface Wpan4/1

  no shutdown

  rpl prefix 2013:dead:beef:cafe::/64
  panid 60


Attachments

    Outcomes