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

Network and Security Manager 2010.3 Release Notes

Release 2010.1

16
This section describes the issues in 2010.1:
236415—NSM erroneously autopopulates interface settings in templates.
250830—NSM does not allow you to add SSG500 and SSG500M devices to the same
cluster.
256770—A template operation directive may incorrectly remove passwords.
269588—gl29042 IDP clusters in third party HA configurations display a failed status
at all times while IDP clusters in standalone HA installations display correct status.
275084—NSM does not display address objects from the global domain under filtered
logs within a subdomain.
277921—NSM does not allow you to add both SSG550 and SSG550M devices to the
same cluster.
283064—DSCP values are not exported when a policy is exported to HTML format.
289807—When configured, NSM fails to unset the BGP Neighbor route map.
290186—NSM does not allow grouping of multicast address objects.
294623—In NSM, you can accidentally create a firewall policy with a Policy ID (PID)
that is already associated with another policy. If this happens, NSM displays a yellow
warning message but allows the action to continue. Then NSM renumbers the policy
and pushes it to the device. However, NSM does not change the PID in the policy list.
This can lead to inconsistencies such as a mismatch between policies and PIDs.
301001—NSM generates a validation error on subinterfaces based on aggregate
interfaces when bandwidth is greater than 100 Mbps.
308927—NSM does not import the negate operator for a DI Custom attack.
392276—NSM does not remove BGP commands when unsetting a tunnel interface.
392731—The Search feature is missing some special characters.
394395—The NSM GUI does not display traffic logs.
397197—During an attack update in NSM, the GuiSvr manager restarts and performs
a core dump.
398479—The devSvrLogWalker process crashes frequently.
402285—NSM fails to create an MIP on a device resulting in a device update failure
when the MIP is included in a policy rule. However, the MIP can be created locally on
the device and used.
405236,ScreenOS PR 408237—NSM does not provide an option for enabling an NTP
server on a firewall running ScreenOS 6.X.
405802—NSM does not allow the manual mode setting for interfaces.
406401—NSM Security Explorer does not display top attacks or top attackers when
an attack log is created.
Copyright © 2010, Juniper Networks, Inc.