Juniper NETWORK AND SECURITY MANAGER - RELEASE NOTES REV 1 Release Note page 15

Addressed Issues
519395—For ScreenOS 6.3 devices, the NSM VPN Manager does not generate proxy-id
configurations for VPNs.
519888—NSM cannot create a single tunnel interface VPN using VPN manager. NSM
builds NHTB entries using the egress interface of the end device, instead of the tunnel
interface.
521126—When a Source NAT update is pushed to an imported SRX Series device from
NSM, a reference to the local NSM database is pushed instead of the IP address or
address object.
521182—As NSM does not validate the number of entries in an address group, an SRX
Series device update fails if the entries exceed 256.
523762—Prior to the NSM 2010.2 release, NSM did not manage SRX Series policy
names. When the device is imported and updated, NSM overwrites these policy names
with the corresponding NSM policy IDs. With NSM 2010.2 release and later, these policy
names are managed and displayed in the newly introduced Policy Name column.
523931—Even though NSM pushes the RADIUS server information to an SRX Series
device on every device update, the Delta Config summary shows that this information
still needs to be pushed.
525134—NSM does not save some of the changes to the user preferences for users
who are authenticated through the RADIUS server.
525264—After an upgrade from 2010.1, the detector version information is not imported
into the cluster record when you import an ISG-IDP series root device cluster with its
associated vsys members in NSM.
525588—In spite of filtering the report based on specific event categories, the
NSM-generated report also has information about other event categories.
525729—When OSPF parameters are configured using a template and then updated
on a device, the OSPF ID is not imported when you import the device configuration
back to NSM.
528500—If you make more than 100 configuration changes in NSM from the actual
device configuration, the Job Manager displays only the first 100 lines.
528681—When a polymorphic object is updated to a device, NSM sends the polymorphic
object name instead of the address object information.
529124—As several of the NSM windows (such as Policy windows, Device edit windows,
and Download schema windows) were too tall, some of the buttons/functionalities
within these windows were inaccessible on normal displays. With the 2010.3 release
and later, the windows are resized automatically to fit within the display.
532571—If RMA/Activate is performed on a managed Junos OS device, it cannot connect
to NSM after the device is rebooted or the Device server is restarted.
533009—After an upgrade to the NSM 2010.2 release, an SRX device policy update
fails if this policy had comments with spaces in the previous release (that is, in the
release from which you had upgraded).
533763—NSM stops responding at 76 percent when policies are updated on
ScreenOS-based ISG-IDP devices.
Copyright © 2010, Juniper Networks, Inc. 15