BelAir20E User Guide
Mesh Auto-connection Example
April 2, 2012
Confidential
Document Number BDTM02201-A01 Standard
mobile admin state: ...... Disabled
mobile link id: ..........
mobile link role: ........ ss
Protection Backhaul:
protection admin state: .. Disabled
Blacklist:
No blacklist entries
Link Failure Detection: ...... Disabled
Backhaul T1 Bandwidth limit:.. Disabled
Display the mesh topology.
/interface/wifi-1-1# show backhaul status
WiFi backhaul states:: stationary=[Enabled] mobile=[Disabled] protection=[Disabled]
Backhaul Links:
Link Radio Mac State(L,R) RSSI Radio Node IP Node Name
----- ----------------- ---------- ---- ----- -------- ----------
[S] 1 00:0d:67:10:e8:92 up fwd -58 wifi-1-1 180.7.4.122
[S] 2 00:0d:67:0c:22:29 fwd fwd -47 wifi-1-1 180.7.4.121
[S] 3 00:0d:67:0c:22:4b up fwd -67 wifi-1-1 180.7.4.120
Display the auto-connect topology.
/services/auto-conn# show status
Oper State Ether Link State Egress Reachable Use Alternate Mesh
----------- ---------- ---------------- ----------------
up down yes yes
Node121 (Egress Node of Mesh B)
Display the auto-connect topology. It shows that it is using the alternate mesh
as an egress point.
/services/auto-conn# show status
Oper State Ether Link State Egress Reachable Use Alternate Mesh
----------- ---------- ---------------- ----------------
up down yes yes
Recovery
Conditions
At this point, the Ethernet connection used by the Mesh B egress node
(Node121) is re-established. Because it is an egress node, Node121
automatically reverts back to its own mesh and begins to use the Ethernet
connection to egress its traffic. However, its child nodes (for example,
Node123) continue to use the Mesh A egress node until an explicit revert
command is issued on each child you want to return to using Node121 as an
egress.