WESM zl Management and Configuration Guide WT.01.28 and greater
10-9
Redundancy Groups
High Availability for Wireless Services
[VLANs] and redundancy group settings) and save the configuration to the each
module’s startup-config. If you later change the configuration of one module, you
must remember to make the same change to other modules.
Redundancy Group Configuration Mode Context
Alternatively, you can use the redundancy group configuration mode in the CLI to
configure settings that are pushed to all members of the group.
The redundancy group configuration mode is a special configuration mode available
from the enable mode context of the Wireless Edge Services zl Module CLI. You can
only access the redundancy group configuration mode, however, in these circum-
stances:
■ The module is a member of a redundancy group.
■ All members of the group are in the Online state.
The redundancy group configuration mode is shared among all members, so that
must the local module must be able to communicate with them.
To enter the redundancy group configuration mode context, enter this command from
the module enable mode context:
ProCurve(wireless-services-C)# redundancy-group-cli-config enable
ProCurve(wireless-services-C)redundancy-cli*#
After accessing the redundancy group configuration mode context, you can enter
almost any command that you can enter from the configuration mode contexts of an
individual module. For example, you can configure a WLAN. However, when you
enter commands, not only the local module, but all modules in the group, receive the
commands. In this way, all members of the redundancy group enforce consistent
settings.
You cannot enter some commands from the redundancy group configuration mode
context. For example, you cannot configure IP settings and redundancy group
settings. These you must set on members on an individual basis.
If you paste a configuration file into the redundancy group configuration mode
context, the invalid commands simply do not take effect. For example, you could
configure one Wireless Edge Services zl Module with all the settings for your
network. Then you could set up the redundancy group, access the redundancy group
configuration mode context, move to the global configuration mode context, and
paste the startup-config of the base module into the CLI. The other modules in the
redundancy group would receive WLAN, radio, DHCP, and RADIUS settings (as
well as others), but each module would keep its own IP address.