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

Release 2010.2

Copyright © 2010, Juniper Networks, Inc.
517864—During an SRX Series device update, VPN Manager-configured VPN settings
are being removed from the secondary node of the cluster.
518196—If you have an NSM HA set up with MIP IP addresses and perform a delta
config, NSM unsets the secondary NSM server IP address from the cluster members.
519004—You cannot select an interface for an imported SRX Series device from the
VLAN interface in NSM. NSM displays the following error: "Reference to undefined
collection-of-interface-range".
519395—For ScreenOS 6.3 devices, the NSM VPN Manager does not generate proxy-id
configurations for VPNs.
521126—When a Source NAT update is pushed to an imported SRX Series device from
NSM, a reference to the NSM's local database is pushed instead of the IP address or
address object.
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. From 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.
533763—NSM stops responding at 76 percent when policies are updated on
ScreenOS-based ISG-IDP devices.
538643—With NSM, when you set the interface zone to null, the device update fails
as NSM tries to unset the
This section describes the addressed issues in 2010.2:
228510—If you configure a multi-line banner for a device, verification fails on update.
271590—Deleting the system services outbound-ssh stanza does not cause existing
connections to be dropped.
407541—When you add Junos OS devices in cluster mode through the reachable device
workflow, device status is Import Needed if you first add the primary and then the
secondary device. To change the cluster status to Managed and In Sync, you must
import the cluster. To work around this issue, first add the secondary device and then
the primary device.
parameter for that specific interface..
g-arp
Addressed Issues
13