To specify the SAE community that connects to a policy server group, you need to add an application manager group object to the directory.
Use the following configuration statements to specify the application manager for the policy server:
- shared network application-manager-group name {
- description description;
- application-manager-id application-manager-id;
- connected-sae [connected-sae...];
- pdp-group pdp-group;
- local-address-pools [local-address-pools...];
- managing-sae-ior managing-sae-ior;
- }
To add an application manager group:
- [edit shared network application-manager-group name]
- user@host# set connected-sae [connected-sae...]
When you modify a community, wait for passive session stores of the new community members to be updated before you shut down the current active SAE. Otherwise, a failover from the current active SAE to the new member is triggered immediately, and the new member’s session store may not have received all data from the active SAE’s session store.
- [edit shared network application-manager-group name]
- user@host# set local-address-pools local-address-pools
You must configure a local address pool if you are using the NIC so that the NIC can resolve the IP-to-SAE mapping. See Using the NIC Resolver.
- [edit shared network application-manager-group name]
- user@host# set managing-sae-ior managing-sae-ior
The amIorPublisher script provides this information when the SAE connects to the policy server. If you do not select this script when configuring initialization scripts, enter a value. For information about configuring initialization scripts, see Configuring Initialization Scripts.