Adding Infranet Controller Clusters; Chapter 4 Adding Infranet Controller Clusters; Infranet Controllers Clusters In Nsm Overview - Juniper NETWORK AND SECURITY MANAGER 2010.4 - CONFIGURING INFRANET CONTROLLER GUIDE REV 01 Manual

CHAPTER 4

Adding Infranet Controller Clusters

Infranet Controllers Clusters in NSM Overview

Copyright © 2010, Juniper Networks, Inc.
Infranet Controllers Clusters in NSM Overview on page 23
Adding an Infranet Controller Cluster with Imported Cluster Members on page 24
When you add an Infranet Controller cluster in NSM, you first add the cluster object and
then add each member. Adding a member is similar to adding a standalone device.
Infranet Controller clusters can be configured by the device administrator to operate in
active/passive mode or in active/active mode. Clusters in active/passive mode are made
up of a primary member and a secondary member. All authentication requests are handled
by the primary member. If a primary member fails, then the secondary member takes
over.
In active/active mode, authentication requests are load-balanced across all cluster
members. If one member fails, then load balancing takes place among the surviving
members.
The number of members permitted in a cluster depends on the Infranet Controller platform
and whether the cluster is configured in active/active mode or in active/passive mode.
You can have no more than two cluster members in active/passive mode. In active/active
mode you can have up to four members.
Before you can add a cluster member in NSM, the device administrator must have already
created the cluster and added, configured, and enabled the physical cluster member.
See the Juniper Networks Unified Access Control Administration Guide for details on creating
and configuring clusters.
Infranet Controller devices configured in a cluster must have a cluster object and member
objects defined in the NSM before the Infranet Controller Cluster nodes can be recognized
by NSM. Nodes from this cluster that subsequently contact NSM will be represented by
fully functional member icons in the Cluster Manager. Cluster members whose DMI agents
do not contact NSM will be displayed in the NSM Device Monitor as unconnected devices.
Infranet Controller devices use member IDs to identify each cluster member object. When
importing cluster members, the member ID is imported as part of the cluster, so the Add
Cluster Member wizard does not prompt for the member ID.
23