Diagnosing a CGE not joining the CG mesh

Document created by mathaker on Sep 18, 2014
Version 1Show Document
  • View in full screen mode

If a node fails to join the mesh, do the following:

  1. Check the node's WPAN neighbor table and verify the RF signal strengths:
    • Connect a PC to the host uart/port of the node.
      • If you are using the IE kernel and have built your own app, you may want to temporarily load the standard PPP CM app from the CDN portal
    • start the CSMP CLI or GUI
    • Get the CSMP TLV 2, 11 and 52
      • TLV 2 will identify your node's EUI64 identifier
      • TLV 11 will confirm the node app version.  Verfy that it is what you expect
      • TLV 52 will tell you the neighbors heard by this node.
    • If TLV 52 does not return any neighbors in the list, wait another 10 minutes and try again.
    • If still no neighbors, check your CGR's configuration to make sure that the WPAN interface is in the "no shutdown" state and that the 'txpower' is set to 'high'.
    • Next check to see if a notch list has been defined (How is RF channel notching accomplished in the Cisco CG-Mesh products?) and if so, make sure the definition on the node matches that on ghe CGR.
    • If a ReverseRSSI value in the neighbor table is higher than -50 (dBm), it is possible that your node is saturating the CGR's receiver.
      • Add RF attenuators to the connection between your node and the antenna or, move the node farther away from the CG
      • Try to get the Reverese RSSI value to be between -50 and -70.
    • When you see both ForwardRSSI and RevereseRSSI values not "n/a" and higher than -90 and lower than -40, the node will likely join the mesh
    • check to if the node has joined the mesh.  How to See the WPAN Neighbor Table
  2. Verify that the node has been configured with the correct SSID of the CGR.
  • Use the JTAG tool to read config memory at 0x80E0000
  • Use the CSMP GUI or CLI tool to get TLV 20