Juniper NETWORK AND SECURITY MANAGER 2010.4 - ADMININISTRATION GUIDE REV1, Administration Manual

Page: 206 / 1026

7.
Click Next , The device is detected and the device details are displayed.
8.
Enter a new name for the device in Device Name to change the host name of the
device. An error message is displayed if the device name is not unique.
9.
Click Finish to add the cluster member to the NSM GUI. The cluster member is added
as a child of the device cluster in the Devices workspace.
Adding Clusters of Routers Running Junos OS
You can use NSM to manage clusters made up of J Series or SRX Series devices. You
cannot create clusters of EX Series, M Series, or MX Series devices.
J Series and SRX Series clusters have two members; a primary member and a secondary
member. You import a configuration for the entire cluster from the primary member. You
need to import the configuration only once because both members share the same
configuration file. Similarly, to update the configuration on the cluster, you need to push
the configuration to only the primary member.
To configure local data for one cluster only, you must use a configuration group dedicated
to that purpose. See “Configuring Devices” on page 187 for details.
To add a cluster of J Series or SRX Series devices to NSM, you use the Add Cluster wizard
as for any other cluster type, and provide a cluster name, a color for the icon in NSM,
supply Junos as the name of the operating system, J Series as the Junos OS Type, a
platform name, and managed OS version.
You add cluster members one at a time, in a similar manner to adding standalone devices.
You can add and import devices with dynamic IP addresses, or you can model devices
that have not yet been configured. NSM does not support importing cluster members
with static IP addresses.
When adding a modeled device, you are asked to provide a member ID. One member of
the cluster should be member 0 and the other member 1. These member IDs allow
configuration groups to distinguish between the two cluster members, thereby providing
local configuration data in a configuration group dedicated to member 0, and local
configuration data in another configuration group dedicated to member 1.
When importing cluster members, the member ID is imported as part of the cluster, so
the Add Member workflow does not prompt for this information.
The Add Cluster Member wizard workflow differs depending on whether you are importing
a cluster member or modeling a cluster member. Outline procedures are given here. For
examples of adding clusters in NSM, see “Example: Adding and Importing a Cluster” on
page 159 and “Example: Creating, Activating, and Updating a Cluster with Modeled Cluster
Members” on page 161.
• Adding and Importing a Junos Cluster on page 157
•
Adding a Junos Cluster with Modeled Cluster Members on page 157
•
Activating and Updating a Modeled Junos Cluster on page 158
Copyright © 2010, Juniper Networks, Inc. 156
Network and Security Manager Administration Guide