WESM zl Management and Configuration Guide WT.01.28 and greater

10-23
Redundancy Groups
Configuring a Redundancy Group
■ Updates Received—the number of updates that the module has received from
this member
■ Radio Portals—the number of radios adopted by this member (some RPs have
two radios)
■ Associated Stations—the number of stations associated to RPs adopted by this
member
■ Rogue AP—the number of unapproved APs detected by RPs adopted by this
member
■ Self Healing Radios—the number of radios adopted by this member that are
configured for self healing
When you have finished reviewing this information, click the Close button.
Setting up Adoption Preference IDs to Control RP Adoption
Your redundancy group might include more than one active module. In this case, you
can use adoption preference IDs to control which Wireless Edge Services zl Module
(or Redundant Wireless Services zl Module) adopts particular RPs.
You set an adoption preference ID for both the module and the RPs. If you want a
module to adopt an RP, the module’s adoption preference ID should match the RP’s
adoption preference ID (which can be set in the radio adoption default configuration
or the configuration for a particular RP).
Before configuring adoption preference IDs, consider your goals. Which RPs do you
want a particular module to support and why? Sometimes you might want to group
RPs in the same general location on the same module in order to simplify roaming.
On the other hand, having different modules adopt RPs in the same general location
can help build redundancy into your network. In this case, though, remember to set
up roaming correctly as described in Chapter 9: “Fast Layer 2 Roaming and Layer 3
Mobility.”
Once you have planned your deployment, begin to configure adoption preference
IDs. The following procedure for setting preference IDs gives you the greatest control
over RP adoption: you set adoption preference IDs for each RP on each module before
you install the RPs.
Note These instructions also apply to Wireless Edge Services zl Modules that are not in a
redundancy group but are in the same network.
1. Assign a different adoption preference ID to each active module in the redun-
dancy group. Record the IDs in a table such as Table 10-3 on page 10-26.