Router Density and Mesh Failover Evidence

Router Density and Mesh Failover Evidence

Router Density and Failover Evidence

The strongest mesh-simulation exercise is usually a bounded self-healing test. Remove a router, weaken a backbone link, or force an end device to lose its parent, then record what the model says changed. Zigbee route repair can find another path only when the router backbone has an alternate path. An end device can rejoin only when another suitable parent is in range.

Injected fault Zigbee response What density decides
Router lost AODV-style route repair searches for another path through routers. Whether an alternate relay path exists at all.
End device parent lost The end device searches for a new parent and rejoins. Whether another router or the coordinator can parent that endpoint.
Backbone thinned Routes may become longer, slower, or unavailable. Whether the topology has enough redundancy to avoid partition.

When a simulated route heals, record the original path, the failed or removed element, the alternate path, the endpoints affected, and the evidence the simulator cannot provide. When it partitions, record whether the failed router was a hidden single dependency and whether the design needs another router, different placement, or a field retest.

Back to the chapter