Cisco Cisco 5520 Wireless Controller Referencia técnica
16
Radio Resource Management–Radio Frequency Grouping Algorithm
Troubleshooting
\\Join is Denied because the group ID does not match.
*RRM-MGR-2_4: Jan 16 18:51:07.651: Airewave Director: Group received Join Request from
802.11bg group C0.A8.0A.14.00.4B(63131), IP addr 192.168.10.20
\\Second Join Request received.
*RRM-MGR-2_4: Jan 16 18:51:07.651: Airewave Director: Member in join request from source
IP addr 192.168.10.20 to 802.11bg group, member IP 192.168.10.20 our Id 500 srcType 75
*RRM-MGR-2_4: Jan 16 18:51:07.651: Airewave Director: adding entry C0.A8.0A.14.00.4B (75)
to 802.11bg group
\\The request is honored and the WLC is added to the group.
*RRM-MGR-2_4: Jan 16 18:56:59.958: Airewave Director: Group received Join Request from
802.11bg group C0.A8.0A.1E.00.32(63131), IP addr 192.168.10.30
\\A second WLC sends its join request.
*RRM-MGR-2_4: Jan 16 18:56:59.958: Airewave Director: Member in join request from source
IP addr 192.168.10.30 to 802.11bg group, member IP 192.168.10.30 our Id 500 srcType 50
*RRM-MGR-2_4: Jan 16 18:56:59.958: Airewave Director: adding entry C0.A8.0A.1E.00.32 (50)
to 802.11bg group
\\And the second WLC is added to the group (Complete).
*RRM-MGR-2_4-GRP: Jan 16 18:57:20.909: Airewave Director: prep to join 802.11bg group
C0.A8.0A.65.03.E8(63126) due to rssi -8
*RRM-MGR-2_4: Jan 16 18:57:36.839: Airewave Director: Group 802.11bg attempting to join
group IP Address 192.168.10.101, ctrl count 3
\\Now the GL attempts to join another WLC whose Group ID is higher–with a controller count of 3 (The
GL plus the two new WLC additions).
GL plus the two new WLC additions).
*RRM-MGR-2_4: Jan 16 18:57:36.857: Airewave Director: Group received join failure from
802.11bg C0.A8.0A.65.03.E8(63126) (192.168.10.101) for reason Not a configured static
member
*RRM-MGR-2_4: Jan 16 18:57:36.857: Airewave Director: Group validated join failure from
802.11bg C0.A8.0A.65.03.E8(63126) for reason Not a configured static member
\\But access is denied–192.168.10.101 is configured as a static GL, and the GL attempting to join is not
configured as members under that static GL.
configured as members under that static GL.
Summary of the Reason Codes
1.
Invalid IP: This suggests that the controller IP is invalid or does not match the controller system
name.
name.
2.
Group Size exceeded: When the operational limits of a Leader controller is reached either because
of AP numbers or number of member controllers addition, the Leader rejects addition of more
controllers and display this reason for rejection.
of AP numbers or number of member controllers addition, the Leader rejects addition of more
controllers and display this reason for rejection.
3.
Invalid Group order: This error message is displayed for the following reasons:
–
If the grouping order is not in the way it has been formulated for reasons such as memory
corruption.
corruption.
–
If the data-structures have been corrupted during transmission.
–
If an unknown controller type is attempting to join.
4.
Source Not Included: No valid source identification.
5.
Weak Signal Strength: Nearest neighbor is not close enough. (Not applicable to static RF grouping)