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

Known Issues

NSM

Copyright © 2010, Juniper Networks, Inc.
552226—Under the
Policies > Source NAT
displayed, and the source and destination addresses are not selectable. In addition,
you cannot select a target for this policy.
553746—NSM does not manage address objects with dns-name for SRX Series devices
running on Junos OS Release 10.2R2 and 10.0R2 images.
557767—As SRX OS platforms have been renamed from 10.2 and later, if you model
any SRX Series low-end devices with the 10.2 or later OS using the old platform-name,
NSM GUI displays the old platform-name instead of the new platform-name.
559528—Within an SOS template, if you assign the same host IP address for IPv4 and
IPv4/IPv6 options under the SNMP Reporting settings, NSM displays a validation error.
560765—NSM Log Viewer stops responding and does not display the logs when there
is a huge amount of logs to be processed by the log-walker.
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.
tab in NSM, the zone information is not
View Security Policies role can still see the
Known Issues
17