Wireless/Redundant Edge Services xl Module Management and Configuration Guide WS.01.03 or greater

1-28
Introduction
ProCurve Wireless Edge Services xl Module
The ProCurve Wireless Edge Services xl Module comes in two models:
■ the J9001A, the primary module
■ the J9003A, the redundant module
The cost-effective Redundant Wireless Services xl Module provides all the
same capabilities as the primary module; however, it does not include any
licenses, and you cannot add licenses to it. Instead the redundant module is
authorized to use the primary module’s licenses in certain situations, which
will be discussed below. In this way, the redundant module scales with the
primary module, and at no further cost.
To enable a redundant module to back up a primary module, you must place
the two in a redundancy group. A redundancy group always consists of exactly
one primary module and exactly one redundant module, which can be
installed in the same or in different ProCurve Switches 5300xl.
Group members can operate in either active mode or standby mode. In normal
operation, the redundant module is in standby mode, and the primary module
in active mode. An active member can adopt RPs at any time. A standby
member can only adopt ports when:
■ for a certain time, it misses heartbeats from the active member
■ the active member fails to adopt an RP
Thus, when necessary, the redundant module assumes the primary module’s
services, and wireless sessions continue after a minimum of delay. Table 1-6
describes some of the situations in which a standby, redundant module adopts
RPs.
Table 1-6. Situations in Which the Standby Module Adopts RPs
Figure 1-10 illustrates a situation in which a standby, redundant module
adopts RPs.
Situation Possible Causes
The standby module misses
heartbeats from the active
module.
• The active module has failed.
• The switch in which the active module is installed has
failed.
• A failed network connection has cut the wireless-
enabled switch off from the network.
The active module fails to adopt
an RP.
• The active module’s internal downlink port has not
been tagged for the Radio Port VLAN.
• The active module is explicitly prohibited from
adopting the RP.