Cisco Cisco Aironet 1310 Access Point Bridge Information Guide
Q. Are there any specific requirements or recommendations for a WAN
link that is implemented between REAP/HREAP AP at the remote site
and WLC at the main site?
link that is implemented between REAP/HREAP AP at the remote site
and WLC at the main site?
A. These are some of the main factors to be considered for the WAN link:
Ensure that the bandwidth of the WAN link is at least 128kbps.
♦
Ensure that the latency or round−trip delay between the two sites across the WAN
link is not more than 300ms because more than a 300ms delay can create
authentication problems to the client, especially when central authentication is
implemented.
link is not more than 300ms because more than a 300ms delay can create
authentication problems to the client, especially when central authentication is
implemented.
♦
Q. I had a network shut down for a few hours, due to which the LAPs lost
communication with WLCs. After the network came back up, the LAPs
took the IP address from the DHCP server, even though these APs are
configured with a static IP address. In the "
communication with WLCs. After the network came back up, the LAPs
took the IP address from the DHCP server, even though these APs are
configured with a static IP address. In the "
show ap config general
<ap−name>
" it shows as "
Fallback IP Address
." Why does this
happen?
A. The LAP tries to associate with the WLC up to 20 times with LWAPP discovery
messages. In case it is not able connect, it tries to obtain a new IP address through DHCP. If
the LAP is able to get one IP address from the DHCP server, this IP address is the active one,
and the statically assigned IP address is used for fallback. The idea behind this is that in case
the LAPs are moved to a different VLAN (for example, to a another building), they are able
to retrieve an IP address and join a WLC. This behavior is explained in bug CSCse66714.
You must upgrade the WLC to software Version 4.0.206.0.
messages. In case it is not able connect, it tries to obtain a new IP address through DHCP. If
the LAP is able to get one IP address from the DHCP server, this IP address is the active one,
and the statically assigned IP address is used for fallback. The idea behind this is that in case
the LAPs are moved to a different VLAN (for example, to a another building), they are able
to retrieve an IP address and join a WLC. This behavior is explained in bug CSCse66714.
You must upgrade the WLC to software Version 4.0.206.0.
Q. Is it mandatory to configure a bridge group name for a mesh network?
A. A bridge group name (BGN) can be used to logically group the APs in the mesh. Although
by default, the APs come with a null value BGN to allow association, we recommend that you
set a BGN. You can make this configuration change through the CLI or GUI with this
command:
by default, the APs come with a null value BGN to allow association, we recommend that you
set a BGN. You can make this configuration change through the CLI or GUI with this
command:
config ap bridgegroupname set Bridge Group Name Cisco AP
Note: BGNs can be a maximum of ten characters. If you enter more than 10 characters into
the BGN field on the controller GUI mesh access point configuration page, it generates an
error message. An error also appears when you configure this parameter through the config
ap bridgegroupname set groupname Cisco_MAP CLI command or WCS (CSCsk64812).
the BGN field on the controller GUI mesh access point configuration page, it generates an
error message. An error also appears when you configure this parameter through the config
ap bridgegroupname set groupname Cisco_MAP CLI command or WCS (CSCsk64812).
When you configure BGN on a live network, ensure that you configure from the farthest
MAP and work your way back to the RAP. This is very important because you can strand a
child MAP that cannot associate with a parent, which can have an updated BGN. Use
different BGNs to logically group different parts of your network. This is useful in situations
where you have RAPs within the same RF area and you want to keep segments of your mesh
separated.
MAP and work your way back to the RAP. This is very important because you can strand a
child MAP that cannot associate with a parent, which can have an updated BGN. Use
different BGNs to logically group different parts of your network. This is useful in situations
where you have RAPs within the same RF area and you want to keep segments of your mesh
separated.
If you want to add a new AP to a live network, you must pre−configure the BGN on the new
AP. If you bring up the mesh network from the scratch with new, out−of−the−box APs, the
BGN is preset in the APs to a NULL value. APs join in a new network with this default value
AP. If you bring up the mesh network from the scratch with new, out−of−the−box APs, the
BGN is preset in the APs to a NULL value. APs join in a new network with this default value