Known Issues; Nsm - Juniper NETWORK AND SECURITY MANAGER - RELEASE NOTES REV 3 Release Note

Network and Security Manager 2010.3 Release Notes

Known Issues

NSM

20
This section describes known issues with the current release of NSM. Whenever possible,
a workaround is suggested. These release notes contain issues related to NSM only. For
a complete list of addressed issues for each device, see the release notes associated
with the device.
266865—When you use NSM to edit the startup information of a device and change
the Use Device Server Through MIP setting to Use Default Device Server IP Address
and Port or make the opposite change, NSM does not push the change to the device.
277604—Interface configuration screens show more settings than are supported by
the actual interface.
277718—When you use NSM to set Antivirus (AV) parameters for a policy on a Juniper
Secure Services Gateway (SSG) 300 Series device running ScreenOS 6.0r4, the new
setting is not pushed to the device. However, NSM can be used successfully to send
AV parameters settings to SSG 140 Series devices running ScreenOS 6.0r4.
277997—Device updates fail when a policy that references address objects for ScreenOS
devices is assigned to a J Series device because the address object naming conventions
for J Series devices are more restrictive than the naming conventions for ScreenOS
devices. For J Series devices, the address object name must be a string that begins
with a letter and consists of letters, numbers, dashes, and underscores. For ScreenOS
devices, the address object name can include a combination of numbers, characters,
and symbols. To ensure that a J Series device can use the Address Objects referenced
by the security policy that is assigned to the J Series device, all address objects in that
policy must follow the address object naming conventions for J Series devices. If the
policy that is assigned to a J Series device contains preexisting address objects for
ScreenOS devices, these address objects must be renamed to follow the same address
object naming conventions for J Series devices.
284698—NSM users that do not have the
policy node within devices that have their Policy Management Mode set to In-Device.
286643—When you create a virtual system device with a '.' in the name, the firmware
upgrade fails. The root device will reflect the change, but the virtual system will not.
287814—NSM users with IDP administrator credentials logged into a subdomain can
edit shared address objects that are also visible in the global domain.
288309—For J Series routers in an NSM cluster, when the cluster member device
reboots and reconnects to NSM, the hardware inventory displays out-of-sync in the
Device list table. To work around this issue, execute the Reconcile Inventory directive
to synchronize the inventory state of the device.
288993—When you customize a predefined report,
correctly and causes subsequent reports to fail.
View Security Policies role can still see the
does not generate it
guiSvrCli.sh
Copyright © 2010, Juniper Networks, Inc.