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

Addressed Issues
411983—NSM attempts to set OSPF retransmit intervals even when the interface is
not part of an OSPF area.
412776—If you create a custom view using an existing view, the custom view is not
saved in the LogViewer.
414615—The NSM GUI is very slow.
415598—Importing a firewall into NSM generates a validation error.
421675—NSM does not generate unset commands correctly on devices running
ScreenOS.
436368—NSM displays 'unset interface ethernet0/3 g-arp' in the delta config summary.
436779—Editing settings at the member level in NSM deletes settings in multiple
clusters.
438346—VRRP support for devices running ScreenOS 6.0.
438686—Upgrades from ScreenOS release 5.4 to 6.1 in NSM causes template overrides
at the cluster level.
438804—Deleting a virtual router from NSM also deletes the virtual router configuration
on multiple clusters.
441419—NSM 2007.3r5 as well as NSM 2008 (with ScreenOS 6.1 schema) does not
include the CLI: set flow vpn-tcp-mss and set flow tcp-mss.
442379—Tunnel interfaces belonging to shared virtual routers and zones are not
available in the Vsys.
444462—Updates to devices running JUNOS fail if there are spaces in the name of the
address object.
451634—NSM incorrectly displays differences immediately after creating a new policy
version with the policy versioning tool.
453177—When you create a full mesh route-based VPN from the VPN Manager with
a numbered tunnel interface and NHTB with next hop IP-enabled, and then you delete
a device in the VPN setup and add the same device again, NSM generates a validation
error on the tunnel interface. The previous NHTB entries are also lost.
454594—When a GRE over IPSec transport mode is selected for a VPN bound to a
tunnel interface, NSM generates an error.
459772—When you right-click on a device in Device Manager, the software install list
is blank.
460404—NSM 2008.2r2 does not support the ScreenOS 6.1 MGT zone for modeled
SSG5 devices.
463817—On a modeled device running JUNOS software, you need to promote a
template twice in order to update it. However, after you promote the template,
previously edited device settings are erased from the device template.
466215—When you install NSM with a custom data directory, NSM changes the
ownership and permissions of all files and folders present under the parent directory
instead of modifying the custom data directory alone.
Copyright © 2010, Juniper Networks, Inc. 17