Differences

This shows you the differences between two versions of the page.

--- mtrp:diagnostics [2026/06/10 12:52] – created mosh
+++ mtrp:diagnostics [2026/06/10 13:11] (current) – mosh
@@ Line 1: / Line 1: @@
 ====== Diagnostics ======
-MTRP exposes table and router summaries for bench testing and protocol verification.
+===== 1. Purpose =====
-===== Summary Output =====
+This document describes the intended interpretation of MTRP diagnostic output.
-The main summary typically includes:
+===== 2. Summary Output =====
-  * device ID
+The summary output SHOULD provide a concise view of current router state, including:
-  * local node ID
-  * network ID
+  * device identifier
+  * local node identifier
+  * network identifier
   * address state
   * router state
@@ Line 18: / Line 20: @@
   * security capabilities
-===== Route Summary =====
+===== 3. Neighbor Summary =====
+The neighbor summary describes directly reachable peers.
+This output SHOULD be used to confirm:
+  * direct neighbor discovery
+  * direct-link metric values
+  * aging and expiry behavior
+  * capability and security visibility
+===== 4. Route Summary =====
-The route summary shows learned forwarding candidates.
+The route summary describes learned forwarding candidates.
-Important note:
+The route summary MUST NOT be interpreted as a one-route-per-destination table.
-  * this is not limited to one route per destination
-  * multiple next-hop candidates for the same destination are normal
-===== Preferred Route Summary =====
+Multiple entries for the same destination MAY be present and are normal when multiple next-hop candidates exist.
-The preferred route summary shows only forwarding routes that were actually selected during send-time resolution.
+===== 5. Preferred Route Summary =====
-If the node has only needed direct-neighbor routing so far, this table may remain empty.
+The preferred route summary describes forwarding choices actually selected during send-time route resolution.
-===== Neighbor Summary =====
+This table MAY remain empty if forwarding-table resolution has not yet been required.
-The neighbor summary is the best place to verify:
+===== 6. Interpretation Guidance =====
-  * direct peers
-  * last-seen timing
-  * expiry timing
-  * direct-link metric
-  * transport/security capability state
-===== Recommended Tests =====
+If active routes are present while preferred routes remain absent, that usually indicates:
-  * verify direct neighbors appear with expected metrics
+  * route learning is functioning
-  * verify indirect learned routes appear with additive metrics
+  * forwarding candidates exist
-  * move nodes to force loss of a direct path
+  * direct-neighbor resolution has been sufficient so far
-  * confirm traffic falls back to a forwarded candidate
-  * confirm preferred-route entries appear when forwarding is actually used