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

Network and Security Manager 2010.4 Release Notes
16
534638—For ISG-IDP Series clusters running 6.1.x versions, when a root device is
updated with a new detector, the detector version is updated only for the root device
and not for the vsys members of this device. This mismatch in detector version between
the vys members and the root device results in a device update failure.
534943—An SRX device update fails when you push a policy that contains a customer
service object with the SQL*Net Version 2 application protocol.
535137—During a device update, NSM does not push the maximum bandwidth setting
for a firewall policy that has traffic shaping configured. NSM creates an exception.
537273—When you import an SOS cluster device to NSM in root mode, the aggregate
subinterfaces are displayed as physical interfaces.
538643—With NSM, when you set the interface zone to null, the device update fails
as NSM tries to unset the
g-arp
538908—NSM Policy Manager does not display comments for a rule that has a single
service enabled.
541154—After an upgrade from 2010.2 to 2010.3, policy names are getting overwritten
with the corresponding policy IDs during a J Series or SRX Series device update.
541576—NSM does not support adding more than one physical interface to an aggregate
interface in the ns-5000-8G2-G4 card for an ns5000 series device.
541992—The custom phase 2 VPN proposal configuration from Junos OS devices is
incorrectly imported into NSM. In addition, NSM does not permit a user to edit this
configuration.
542616—If an SRX Series device upgrade fails from NSM, then you cannot upgrade it
again from NSM due to space limitation. You must manually clear all temporary files
created on the device by NSM before upgrading again.
542814—The custom phase 1 VPN proposal configuration from Junos OS devices is
incorrectly imported into NSM. In addition, NSM does not permit the user to edit this
configuration.
543140—NSMXpress Web UI allows users created from the Web UI to log on using an
incorrect password.
545126—For an SRX Series device, the traffic logs in the NSM Log Viewer do not contain
any information for the Rule ID and Policy ID fields.
545225—If the Junos OS-based devices (such as SRX Series devices) are configured
with policy- or route-based VPNs, even after a device update, the Delta Config summary
shows there are configuration differences for the preshared key.
547929—With the NSM 2010.2r1-13.1n59 release, adding or editing devices takes
relatively more time than in previous releases.
549986—The NSM installation script fails if there are multiple tmp partitions on the
Solaris server (such as, "/tmp" and "/var/tmp").
550796—If you add a cluster server to NSM after an upgrade from 2008.3 to 2010.2
LGB13z1n33 (with schema 143 and running on RH5 with service pack 5), then the
cluster's secondary server settings are grayed out in NSM.
parameter for that specific interface.
Copyright © 2010, Juniper Networks, Inc.