RingMaster Management Guide - Juniper Networks

On the Access Control Web page you can enable or disable Access Control functionality. You can
perform user operations on this page. On the RADIUS Servers page you can set up the parameters
for RADIUS Servers.
Grouping
As networks continue to scale, the need for a network partitioning feature grows. With larger
installations, responsibility for managing a network is distributed among individuals, where each one is
concerned only with a particular subset of the overall network. The way networks are partitioned is
dependent on the structure of the associated business. It may be physical location-oriented (e.g. a
group of Sites), or it may be more logical (e.g. department-oriented).
This feature provides a user flexibility to partition a network in a way that matches their organization
and their IT support group. The access control feature provides an ability for an administrator to assign
privileges to various entities throughout a network. Network partitioning provides a way of identifying
entities at a high level, rather than individually.
Refer to the publication RingMaster Configuration Guide for details on
setting up Groups for your network.
Object Groups
Two types of object grouping schemes are supported:
❑ Equipment groups, and
❑ Location groups.
There is no direct relation between these two and users may choose to use both, just one, or no
grouping scheme at all.
Equipment Group
An equipment group can contain the following types of objects:
❑ MobilityDomain – All member devices are implicitly included as equipment group members.
❑ Standalone MX – A device not associated with a MobilityDomain
❑ MobilityDomain member MX – A device associated with a MobilityDomain where the
MobilityDomain as a whole is not a member of the equipment group.
Equipment groups can be created under a top-level plan object, or under a MobilityDomain.
Organizer
The equipment organizer tree is enhanced to support the concept of equipment groups. Equipment
group nodes appear in the tree to contain associated device and/or MobilityDomain members. Device
nodes hang directly under an equipment group node, unless a device’s Mobility Domain is a member
of the group. Selecting a device node, reveals any MobilityDomain membership information in the
configuration view’s detail panel.
Cluster Configuration
Whenever a Mobility Domain is cluster-enabled, an associated Cluster node will appear in the
organizer. This node will contain the cluster’s seeds, members, and the DomainConfiguration node.
The following example illustrates a simple case involving no equipment groups. A MobilityDomain’s
cluster node may appear multiple times in the tree. There is no method for assigning a cluster as a
whole to an equipment group. Only devices and MobilityDomains can be assigned to a group. One
restriction is enforced regarding assignment of devices to equipment groups, which is that, if a device
is a cluster seed, the other cluster seed must also be assigned to the same equipment group. This is
required to ensure that a deploy target switchover will not to be rejected due to access control
restrictions.
Flat View
The organizer is enhanced to provide a context-sensitive “flatten” operation that can be invoked on
group nodes. This transforms a selected subtree into a flat list of immediate child nodes. Child node
54 Managing with RingMaster Copyright © 2011, Juniper Networks, Inc.