Avoiding Nacn Password Conflicts - Juniper NETWORK AND SECURITY MANAGER 2010.3 - ADMINISTRATION GUIDE REV1 Administration Manual

Avoiding NACN Password Conflicts

Copyright © 2010, Juniper Networks, Inc.
Add a Single Infranet Enforcer or Infranet Enforcer Cluster.
f.
Repeat steps e and f for every Infranet Enforcer or Infranet Enforcer Cluster you
g.
need to add to NSM. When you are finished, $infranet appears instead of
$infranet_# in each of the domains except the global domain.
In NSM, add the Infranet Enforcer objects to the new domain:
7.
Select Device Manager > Devices.
a.
Click the Add icon, and then select Device to start the Add Device wizard.
b.
In the New Device window, provide a name for the device, a color for its icon in
c.
NSM, and check Device is Reachable.
Follow the instructions in the wizard to add and import the device.
d.
Repeat steps b through d for each Infranet Enforcer device.
e.
When you need to manage the Infranet Enforcers, reimport the configuration each time.
Otherwise, a NACN password mismatch is possible because the Infranet Controller
Dynamically changes this password periodically. Additionally, it is also good practice to
issue a Summarize Delta Config directive and ensure that no $infra policies are present.
If there are, that means that the Infranet Controller has changed something on the Infranet
Enforcer since you last imported the device configuration.
If you do not reimport the configuration, be sure to update the Infranet Controller and
Infranet Enforcer at the same time.
Chapter 4: Adding Devices
183