Addressed Issues; Release 2010.3 - Juniper NETWORK AND SECURITY MANAGER - RELEASE NOTES REV 3 Release Note

Table of Contents

Advertisement

Addressed Issues

Release 2010.3

Copyright © 2010, Juniper Networks, Inc.
Certificate was added to keystore
[root@nsm/]#
This step creates four files:
NOTE: The files truststore.ts and keystore.ts consist of private keys and
must be protected.
On the NSM GUI server, copy the files
5.
/usr/netscreen/GuiSvr/var/certDB/TrustedCA/
On the NSM client, copy the file
6.
NSM_GUI_INSTALLATION/security
Files\Network & Security manager\security
systems where the client is installed.
Restart NSM GUI server services for a new certificate to be used:
7.
#/etc/init.d/guiSvr restart
If using a high availability environment, execute: #/etc/init.d/haSvr restart.
This section includes issues addressed for NSM, ScreenOS, Secure Access SSL VPN SA
Series, Unified Access Control (UAC) Infranet Controllers, and SRX Series Services
Gateways. These release notes contain only NSM-related issues. For a complete list of
addressed issues for each device, see the release notes associated with the device.
This section describes the addressed issues in 2010.3:
403809—Policies cannot be edited as NSM displays a
even though another user is not logged into NSM.
407764—With NSM, the logs of a subdomain cannot be saved on the first try. The
workaround is to quit NSM and then try saving the logs again.
413166—NSM displays an error when a MIP with an IP from a different subnet as the
interface IP is added on a firewall device.
459994—In NSM 2007.3r5, DevServer Manager crashes when a PCAP retrieval operation
is performed on logs.
465850—Uploading of the IDP 5.0 image fails in NSM after an upgrade from the
2008.2r1 to the 2008.2r2 release.
477726—Using templates to activate an SSG5 device results in the creation of tunnel
interfaces with blank names. Because of this, the device cannot be updated.
481066—SRX Series IDP severity level log information is displayed incorrectly in the
NSM Log Viewer.
root.pem
,
server.pem
,
truststore.ts
and
root.pem
server.pem
and
trustedtore.ts
keystore.ts
directory. (The default directory is
.) Note that this must be executed on all
Addressed Issues
, and
keystore.ts
.
to
to
C:\Program
message
locked by another user
11

Advertisement

Table of Contents
loading

This manual is also suitable for:

Network and security manager

Table of Contents