Fortress Bridge: Command-Line Interface
108
Bridges. Alternatively, you can specify only a subnet
and allow SAC to automatically generate all member IP
addresses within that subnet, including that of the root/
master Bridge.
The IP or subnet address you enter must fall within one
of these reserved ranges:
10.0.0.0–10.255.255.255
172.16.0.0–172.31.255.255
192.168.0.0–192.168.255.255
For example, the command below establishes the
network Access ID, leaves the rest of the security
settings at their defaults, configures an SSID and
channel setting for each radio, and specifies a subnet
for the deployment:
[GW]>
set sac start -a 0f0e0d0c0b0a0b0c -sa r2s1s2i3d4 -ca 161 -sg r1s0s9i8d7 -cg 11 -ipnw 172.24.0.0
[OK] Started SAC process successfully
When the SAC process starts, you can observe the
master/root Bridge’s front-panel Stat1 LED flash amber,
while its Stat2 LED lights solid amber. As each slave/
non-root Bridge receives the SAC parameters, its Stat1
and Stat2 LEDs flash amber in unison.
4Check the status of the SAC process with the show sac
command:
[GW]>
show sac
SwabSerialNum:24656196
SwabConfigID:19082
SwabSACRole:SAC_MASTER
SwabSACState:SAC_STOP_4SWAB
SwabSACVer:SAC_VER_PEGASUS_ARCH1
*********SACPeerInformation*********
SeriallNum|IpAddress|CfgID|PeerNum|PeerSACStatus|PeerSACState|PeerSACVer
24743196|172.24.0.3|0|1|SAC_PEER_CONFIRMED|SAC_FINISH_4PEER|SAC_VER_PEGASUS_ARCH1
24773196|172.24.0.4|0|2|SAC_PEER_CONFIRMED|SAC_FINISH_4PEER|SAC_VER_PEGASUS_ARCH1
The master Bridge confirms the SAC_PEER status of each
new slave Bridge and displays SAC_FINISH for each of
them that has successfully received SAC parameters.
5Confirm that all of the slave/non-root Bridges in the network
are recognized as SAC Peers with show sp:
[GW]>
show sp
Peer1=>Serial_Number:24743196
Peer2=>Serial_Number:24773196
6When the master Bridge shows SAC_FINISH for all slave
Bridges and you have confirmed that the SAC Peer list is
complete, save the network configuration with set sac
stop: