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

Network and Security Manager 2010.3 Release Notes
12
482421—The BGP neighbor configuration in a ScreenOS cluster without VSD is not
accurately synced in NSM.
482988—The NSM calculation of the estimated disk space required for DevSvr logs
is inaccurate (
Administer > Server Manager > Servers > Disk and Log Management
482995—DevSvr logs are not getting purged after the specified time interval if you set
this interval using the NSM GUI (
Log Management > Number of days to retain logs
483416—Accessing the policy options of an existing policy causes the NSM GUI client
to lock up, which prevents you from making any further changes.
486787—You cannot import or manage SRX Series devices after an upgrade. Also, the
GuiSvr core dumps if any changes were done using the NSM GUI.
489258—The DevSvr crashes while viewing the IDP logs in Log Viewer.
491015—An inconsistent export of DevSvr log data to csv format occurs when using
the devSvrCli.sh log2action
495737—When updating the device software for an imported ScreenOS cluster device,
a warning message appears stating that the configuration in NSM and the actual device
configuration are not in sync, even when they are.
503179—Logs are not getting parsed because of file header corruption, resulting in a
devSvrManager crash with core.
503231—A sub-interface cannot be created on a serial interface on the SSG-20 platform
as the interface is not displayed in the NSM GUI.
505169—In NSM, the log filter is getting created only for the group and host address
objects and not for the network address object when you create the filter by
right-clicking the source or destination address column within a log.
507098—A GuiServer Manager core dump occurs when compiling IDP policies.
512215—When editing an imported firewall cluster configuration, even if the VR is shared
NSM displays the following error message on the zone: "Shared zone must be in shared
VR" .
513335—During an IDP firmware upgrade, if an error occurs, the upgrade process
continues indefinitely and cannot be stopped. With the 2010.3 release and later, a
timeout option is provided to stop this process.
513985—During an import for a ScreenOS cluster, the BGP neighbor configuration is
imported to cluster level instead of member level.
514579—PIM-SM settings or any dynamic routing protocol cannot be configured on
an imported firewall because the NSM GUI does not display the Protocol section under
interfaces when SOS devices are added in Cluster mode.
516433—NSM displays an out-of-sync message when the primary device in an SRX
Series virtual cluster goes down and the secondary devices takes the primary role. The
workaround is to reconcile inventory.
517009—A Global MIP object cannot be created on the subinterface of a cluster as
the subinterface ( redundant1
Server Manager > Servers > Device Server > Disk and
).
utility.
) is not being listed in Object Manager
Copyright © 2010, Juniper Networks, Inc.
).
.