Addressed Issues - Juniper NETWORK AND SECURITY MANAGER - RELEASE NOTES REV 1 Release Note

Table of Contents

Advertisement

Network and Security Manager 2010.4 Release Notes

Addressed Issues

10
stateOrProvinceName :PRINTABLE:'State'
localityName :PRINTABLE:'City'
organizationName :PRINTABLE:'Name of the Organization'
commonName :PRINTABLE:'NSM'
emailAddress :IA5STRING:'user@example.com'
Certificate is to be certified until Aug 3 22:41:04 2019 GMT (3650 days)
Write out database with 1 new entries
Data Base Updated
Certificate was added to keystore
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.
228510—If you configure a multi-line banner for a device, verification fails on update.
271590—Deleting the system services outbound-ssh stanza does not cause existing
connections to be dropped.
407541—When you add Junos OS devices in cluster mode through the reachable device
workflow, device status is Import Needed if you first add the primary and then the
secondary device. To change the cluster status to Managed and In Sync, you must
import the cluster. To work around this issue, first add the secondary device and then
the primary device.
403809—Policies cannot be edited as NSM displays a
even though another user is not logged in to NSM.
,
,
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
Copyright © 2010, Juniper Networks, Inc.
, and
.
keystore.ts
to
to
C:\Program
locked by another user
message

Advertisement

Table of Contents
loading

This manual is also suitable for:

Network and security manager

Table of Contents