June 30, 2006
Confidential
Document Number BDTM10001-A05 Standard
BelAir100 User Guide
Backhaul Link Configuration
00:12:88:de:14:d1 6 undef-61 mesh -- -------- N
00:12:88:de:07:01 6 undef-62 p2p -- -------- N
Mesh Portal Attribute
set {arm<n>|brm<n>} mesh-portal {yes|no}
This command establishes whether the member of the mesh cluster is a mesh
portal or not. The default value is
no
, meaning that the member of the mesh
cluster is not a mesh portal.
CAUTION!
BelAir Networks strongly recommends that each mesh cluster has only one
mesh portal.
Managing RSTP BPDUs
rstp isolate {arm<n>|brm<n>}
no rstp isolate {arm<n>|brm<n>}
These commands control whether or not RSTP BPDUs are sent and received
through the LPM Ethernet port of the BelAir100 node. The default setting is to
isolate the node; that is, it does not send or receive RSTP BPDUs.
BelAir Networks recommends that you do not change this setting unless
advised to do so by BelAir Networks technical support staff. An improper
settings of this parameter may result in subsequent RSTP topology issues.
Managing the Mesh
Accept List
show {arm<n>|brm<n>} mesh-accept
accept {arm<n>|brm<n>} mesh
For a 2.4 GHz mesh cluster, you can use these commands only with the mesh
portal. For a 5 GHz mesh cluster, you can used these commands with any
member of a multipoint-to-multipoint mesh.
The
accept
command puts into persistent storage a snapshot of the cluster
topology. The node then issues an alarm if it detects any deviation in the
topology from that snapshot. For example, the mesh portal would issue an
alarm if a member of the cluster becomes unreachable, or if an unexpected new
member is added to the topology.
The
show
command lists the MAC addresses of the nodes that are in the mesh
Accept list.
Example 1
/radio# accept arm1 mesh
These remote mesh points have been accepted:
00:0d:67:00:2d:7d
00:0d:67:00:2d:c0
00:0d:67:00:1f:4a
00:0d:67:00:01:05
