Juniper NETWORK AND SECURITY MANAGER - RELEASE NOTES REV 3 Release Note page 21

Copyright © 2010, Juniper Networks, Inc.
291820—When you find shared objects within the Policy Manager, the window for
groups may freeze. This occurs if you do the following in NSM:
Select Policy Manager > Security Policies.
1.
Select a firewall policy.
2.
Find usages on a grouped address object in Shared Objects for the policy.
3.
Click on a link to a policy in the Rule Reference window.
4.
Close the Security Policy window, and click Finish. The NSM main window may
5.
change to gray with no information displayed.
You can recover from this condition by returning to the NSM security policy list and
deselecting the previously selected policy.
292369—When you create a policy-based VPN and then update the device and import
it back into NSM, the VPN rules previously created with VPN Manager and updated to
the device are now imported in the new policy created under Policy Manager > Security
Policies, and the new policy is assigned to the device. However, if the VPN is
subsequently deleted by the user, the VPN and all rules associated with it are removed
from the VPN Manager, but not the Policy Manager policy. Before you can successfully
update the devices, you must manually delete these VPN rules in the policy under
Policy Manager.
292522—On a Secure Access SSL VPN SA Series device, when a user creates a resource
profile, updates the device, and tries to add another bookmark, the new bookmark
page does not show the Host and Server port values.
295156—On a Secure Access SSL VPN SA Series device, the order of the policies within
a SAM policy is not maintained when the SAM policy is edited with the NSM GUI.
295314—After the initial import of a device, the database version feature shows the
user who performed the import as 'unknown.'
299504—When you promote a device with a medium-sized configuration to a template
from the root configuration level, you must wait at least 1 minute for the change to
take effect before opening the template.
299014—During an upgrade installation, license information is required to complete
the installation.
302289—The virtual management Ethernet interface must be set as the management
interface on the Virtual Chassis for it to be managed through NSM.
302500—If you perform a firmware upgrade from Junos OS Release 9.0 to 9.1 through
the device UI (or CLI) and not through NSM, you must reimport the device in NSM and
adjust the operating system (OS) version of the device. To adjust the OS version in
NSM, open Device Manager and right-click the device. Select either View/Reconcile
Inventory or Adjust-OS Version. Ensure that the OS version running on the device
matches the one recorded in the NSM database.
In NSM 2008.2, the NSM UI connects with the GUI server through port 7808, which is
FIPS compliant. When installation is complete, you see the following message: "Please
Known Issues
21