User Manual

Chapter 3 - Operation and Administration of the Macro BTS NPU Configuration
4Motion 228 System Manual
provisioned with a list of redundant ASN-GWs (pool). The BS applies round-robin
mechanism in order to pick an Authenticator for each MS that performs initial
network entry. This should eventually distribute the load between Anchor
ASN-GWs. Geographical site backup can be achieved by using different priority of
ASN-GW pools (Authenticator "metric").
At the unit (NPU) level, up to two pools (with different priorities), each with up to
10 ASN-GWs, can be defined. Each BS defined in the unit will “inherit” these
pools. It should be noted that the ASN-GW defined in the BS as the default
authenticator (see “Managing Authentication Relay Parameters” on page 592) will
be automatically included in Pool1 (although it will not be shown as one of the
ASN-GWs in the pool).
This section includes:
 “Adding an ASN-GW to a BTS Load Balancing Pool” (Section 3.4.11.1).
 “Removing an ASN-GW from a BTS Load Balancing Pool” (Section 3.4.11.2).
 “Displaying Configuration Information for BTS Load Balancing Pools”
(Section 3.4.11.3).
3.4.11.1 Adding an ASN-GW to a BTS Load Balancing Pool
Run the following command to add an ASN-GW to Pool 1 (highest priority pool):
npu(config)# loadbalancePool1IP <ip-address>
Run the following command to add an ASN-GW to Pool 2 (lowest priority pool):
npu(config)# loadbalancePool2IP <ip-address>
Each pool can contain up to 10 IP addresses. Each IP address must be unique in
both Pool1 and Pool2.
Note that Pool2 cannot be populated if Pool1 is empty.
Command
Syntax
npu(config)# loadbalancePool1IP <ip-address>
npu(config)# loadbalancePool2IP <ip-address>
Privilege
Level
10