Show Advanced fra
shows you the current FRA state (enable/disable), sensitivity, current run
interval, last run time, and status and state of all Flexible radios
(Cisco Controller) >show advanced fra
FRA State........................................ Enabled
FRA Sensitivity.................................. high (90)
FAR Interval..................................... 1 Hour(s)
Last Run....................................... 620 seconds ago
Last Run Time.................................. 0 seconds
AP Name MAC Address Slot Current Band COF % Suggested Mode
-------------------------------- ----------------- ---- -------------- -------------------- ---
3800_e_BC80 58:ac:78:df:7e:e0 0 2.4GHz 46 2.4GHz
2802_i.89D0 00:f2:8b:26:ed:d0 0 5GHz 84 5G/Monitor
3802_i.D9A0 58:ac:78:df:9c:20 0 5GHz 100 5G/Monitor
COF : Coverage Overlap Factor
Show Advanced
802.11a/b summary will show you all radios in a given band, Flexible radios
show up on slot 0 when assigned an 802.11a role. You can also show just the
flexible radios with show advanced 802.11-abgn summary
(Cisco Controller) >show advanced 802.11-abgn sum
Member RRM Information
AP Name MAC Address Slot Admin Oper Channel TxPower
-------------------------------- ----------------- ---- -------- ------- -------- -------------
3800_e_BC80 58:ac:78:df:7e:e0 0 ENABLED UP 1* *8/8 ( 2 dBm)
2802_i.89D0 00:f2:8b:26:ed:d0 0 ENABLED UP (56,52)* *7/7 ( 2 dBm)
3802_i.D9A0 58:ac:78:df:9c:20 0 ENABLED UP (36,40)* *7/7 ( 2 dBm)
Config advanced fra
revert Can be used to quick flip all or just the flexible radios in auto back
to default state of 2.4 GHz client serving and mark them Auto FRA or Manual
(very useful for recalculating COF's after adding or moving AP's)
(Cisco Controller) >config advanced fra revert all auto
Reverting XOR radios can cause disruption for associated clients. Are you sure you want to continue? (y/n)y
(Cisco Controller) >show advanced fra
<snip>
AP Name MAC Address Slot Current Band COF % Suggested Mode
-------------------------------- ----------------- ---- -------------- ------ ----------------
3800_e_BC80 58:ac:78:df:7e:e0 0 2.4GHz 46 2.4GHz
2802_i.89D0 00:f2:8b:26:ed:d0 0 2.4GHz 84 5G/Monitor
3802_i.D9A0 58:ac:78:df:9c:20 0 2.4GHz 100 5G/Monitor
Debug
airewave-director fra enable will invoke the FRA debug, we'll take this in
sections focusing on what's important. There is a lot in this command that's
only important to developers so for brevity we'll skip some of the redundant
lines.
![](https://www.cisco.com/content/dam/en/us/td/i/templates/warn.gif)
Warning
|
There is a lot of
output in a debug command- debug FRA should never be run on a fully loaded
production system against all AP's. You can use the
debug mac addr
<
mac1,mac2,mac3>
to isolate the debug to just the devices you are concerned with.
|
The first part of
the debug lists all the radios that will be included in the solution set as
well as if it is an RRF (Redundant Radio Flexible or a 2800/3800) candidate.
Note that the AP's displayed - should be the AP's with 2.4 GHz interfaces. The
last column - is extremely useful - NDM (Network Density Metric) this is the
number of AP's that each of the indexed AP's have as neighbors they can hear
above -67 dBm. The higher that number the denser (AP's closer together) the
network is.
(Cisco Controller) >debug airewave-director fra enable
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.014: Executing FRA on 802.11bg
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.014: ----------------------------------------------------
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.014:
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.014: RDCI List :
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.014: ------------
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.014: Index AP RRF Candidate NDM
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.014: ------ ------------------- -------- -----
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.014: 0 58:AC:78:DF:9C:20(0) YES 6
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.014: 1 00:F2:8B:26:ED:D0(0) YES 6
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.014: 2 F0:7F:06:5E:FD:C0(0) NO 6
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.014: 3 E4:C7:22:AA:38:20(0) NO 6
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.015: 4 E4:C7:22:AA:34:40(0) NO 6
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.015: 5 08:CC:68:B4:20:00(0) NO 6
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.015: 6 58:AC:78:DF:7E:E0(0) NO 5
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.015: 7 64:D9:89:46:7F:B0(0) NO 4
The next step starts
the calculation for each RRF Candidate AP in the above list, in this example we
will have 2 AP's that are marled Yes. I have 1 3800i, one 2800i, and a 3800 e
with NO Dart connector so not currently flexible, the remaining AP's on the
list are 3500/3600/3700.
For AP Index 0
(58:AC:78:DF:9C:20) the AP mac address is displayed- and immediately we get the
neighborhood list. This is the list of Neighbors to the target AP that will be
used in AP index 0's calculation. This is where you see the Neighbors that
matter. Only the loudest 4 neighbors will be used- all must be in the same AP
group. If an AP is not on this list that you think honestly should be - due to
proximity- it is not known as one of the 4 loudest neighbors to the target AP.
This could be because it is in a different AP group or that Neighbor
information is not yet available (newly powered on).
In the output, you
see the first AP on the list selected index 0, and its loudest 4 neighbors
displayed along with their neighbor RSSI and their TX power (because of a
cosmetic bug, current TX power is incorrect and always displays as max power in
release 8.2 MR1, but the algorithm is using current TX power). This establishes
the AP's that can be considered for coverage of AP 58:AC:78:DF:9C:20 coverage
area.
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.015: 58:ac:78:df:9c:20 ---------------------------------------------------------
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.015: 58:ac:78:df:9c:20 Redundancy Iteration 0 , RDCI 0
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.015: 58:ac:78:df:9c:20 ---------------------------------------
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.029: 58:ac:78:df:9c:20 Neighborhood list for AP 0
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.029: 58:ac:78:df:9c:20 ---------------------------------------
Jun 07 16:22:05.029: 58:ac:78:df:9c:20 RDCI Index AP RSSI Tx Power(dBm)
Jun 07 16:22:05.029: 58:ac:78:df:9c:20 ----------- ------- ------- -----------
Jun 07 16:22:05.029: 58:ac:78:df:9c:20 0 58:AC:78:DF:9C:20(0) 0 23
Jun 07 16:22:05.029: 58:ac:78:df:9c:20 2 F0:7F:06:5E:FD:C0(0) -14 22
Jun 07 16:22:05.029: 58:ac:78:df:9c:20 7 64:D9:89:46:7F:B0(0) -30 22
Jun 07 16:22:05.029: 58:ac:78:df:9c:20 5 08:CC:68:B4:20:00(0) -31 23
Jun 07 16:22:05.029: 58:ac:78:df:9c:20 4 E4:C7:22:AA:34:40(0) -43 20
Jun 07 16:22:05.029: 58:ac:78:df:9c:20 3 E4:C7:22:AA:38:20(0) -48 20
Jun 07 16:22:05.029: 58:ac:78:df:9c:20 6 58:AC:78:DF:7E:E0(0) -66 23
Jun 07 16:22:05.029: 58:ac:78:df:9c:20
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.029: 58:ac:78:df:9c:20 Neighborhood Path Loss Matrix
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.030: 58:ac:78:df:9c:20 -----------------------------
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.030: 58:ac:78:df:9c:20 0 37 52 53 54 66 71 89
<snip> Calculating every AP to every AP’s path loss
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.030: 58:ac:78:df:9c:20 Neighborhood Distance Matrix
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.030: 58:ac:78:df:9c:20 -----------------------------
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.030: 58:ac:78:df:9c:20 0 0 4 5 5 14 17
<snip>Calculating RF distances between AP’s
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.030: 58:ac:78:df:9c:20 Unable to triangulate neighborhood, assigning single axis coordinates <normal behavior– perfectly fine we are operating in 2D>
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.030: 58:ac:78:df:9c:20 Computed Coordinates
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.030: 58:ac:78:df:9c:20 ---------------------
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.030: 58:ac:78:df:9c:20 X Y R
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.031: 58:ac:78:df:9c:20 ---- ---- -----
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.031: 58:ac:78:df:9c:20 0 0 18
<snip> many lines of X, Y positions – and calculated radius of each cell
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.031: 58:ac:78:df:9c:20 Neighborhood Multi-Point Check
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.031: 58:ac:78:df:9c:20 Using 4 neighbors for overlap computation
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.031: 58:ac:78:df:9c:20 Point Coordinates Coverage Score
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.031: 58:ac:78:df:9c:20 ------------------ --------------
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.031: 58:ac:78:df:9c:20 0 , 0 2
<snip> Many more lines – deleted for brevity. This is the output and score from the multipoint overlap calculation.
<comment> followed by the RDCI Overlap Factor for this radio and it’s conclusion
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.031: 58:ac:78:df:9c:20 RDCI Overlap Factor : 92 %
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.031: 58:ac:78:df:9c:20 RDCI is redundant
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.032: 00:f2:8b:26:ed:d0 Redundancy Iteration 1 , RDCI 1(00:F2:8B:26:ED:D0(0))
<snip> Redundancy iterations continue for each radio marked as Yes for RRF candidate
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.034: 58:ac:78:df:7e:e0 Redundancy Iteration 2 , RDCI 6(58:AC:78:DF:7E:E0(0))
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.037: Redundancy Identification Complete
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.037: ----------------------------------------------------
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.037:
<snip> The last entry below – is the output you see in show advanced fra
*RRM-MGR-2_4-GRP: Jun 07 16:22:05.037: RDCI List :
*RRM-MGR-2_4-GRP: Index AP Overlap % Redundant overlap Contributor
*RRM-MGR-2_4-GRP: ------ ------- -------- ----------- -------------------
*RRM-MGR-2_4-GRP:0 58:AC:78:DF:9C:20(0) 92 YES NO
*RRM-MGR-2_4-GRP:1 00:F2:8B:26:ED:D0(0) 69 NO YES
*RRM-MGR-2_4-GRP:6 58:AC:78:DF:7E:E0(0) 53 N/A NO
The debug concludes
with the conclusions. Note that AP index 0 is marked as redundant, and is NOT a
overlap contributor. The current threshold for FRA is High (90%) and 92% is
above 90 %. Had sensitivity been set to medium (85%) it would not have been
marked redundant.
Also notice that AP
Index 1, is marked as a coverage contributor. This means regardless of the
percentage of COF, this AP's 2.4 GHz interface is being counted on to provide
coverage for another Radio that has been Marked as Redundant already (AP index
0).
Remember, FRA only
identifies a redundant interface and once identified DCA must run to assign a
new Role. Things that will prevent a radio from being assigned a new role:
-
Client-network-preference–by default for FRA only we use the
connectivity profile. This enforces that 3 or more clients associated to the
radio – it will not transition. This is evaluated at DCA run time.
-
DCA not
running–in which case you will not get a suggested role in the show output
since it can not be evaluated.