Nsm Documentation And Release Notes; Documentation Feedback - Juniper NETWORK AND SECURITY MANAGER - RELEASE NOTES REV 1 Release Note

NSM Documentation and Release Notes

Documentation Feedback

Copyright © 2010, Juniper Networks, Inc.
461264—At times, an update on an SRX Series device fails with the error message
"Previous commit in progress." This may happen when a previous commit is still being
executed on the device in the background; for example, during an IDP policy compilation.
For a workaround, see
http://kb.juniper.net/KB16548
policy compilation, the workaround is to add the device again.
477359—The private edit mode used in SRX Series clusters does not block NSM.
480097—You cannot add an SRX Series cluster member in the auto-import
configuration list.
514021—The model number of SRX devices is incorrectly displayed under Hardware
Inventory.
516144—NSM allows adding an SRX Series virtual chassis as a cluster member.
517276— NSM does not display logs for the backup device in an SRX Series virtual
chassis in the Log viewer.
517284—IDP Detector Engine update does not work for both devices in an SRX Series
virtual cluster.
519796—NSM does not display SRX Series virtual chassis details in Device Monitor.
For a list of related NSM documentation, see
http://www.juniper.net/techpubs/software/management/security-manager/
If the information in the latest release notes differs from the information in the
documentation, follow the NSM Release Notes.
To obtain the most current version of all Juniper Networks technical documentation, see
the product documentation page on the Juniper Networks website at
http://www.juniper.net/techpubs/
We encourage you to provide feedback, comments, and suggestions so that we can
improve the documentation. You can send your comments to
techpubs-comments@juniper.net
https://www.juniper.net/cgi-bin/docbugreport/
the following information with your comments:
Document name
Document part number
Page number
Software release version
NSM Documentation and Release Notes
. If the error is not due to an IDP
.
, or fill out the documentation feedback form at
. If you are using e-mail, be sure to include
.
31