![Juniper STRM 2008-2 - TECHNICAL NOTE CHANGING NETWORK SETTING 6-2008 Скачать руководство пользователя страница 8](http://html.mh-extra.com/html/juniper/strm-2008-2-technical-note-changing-network-setting-6-2008/strm-2008-2-technical-note-changing-network-setting-6-2008_release-note_2032909008.webp)
530-025618-01
8
STRM Release Notes
Known Issues and
Limitations
This section describes the known issues and limitations for the following areas:
•
General
•
System Configuration
•
Deployment Editor
•
Network Surveillance
•
Offense Manager
•
Event Viewer
•
Flow Viewer
•
Reports
General
Objects Menu Tree May Not Appear in Equation Editor After Adding a New
Custom View
If you create a new Custom View and then open the Equation Editor, the menu tree
displaying network objects may not appear the first time you attempt to access the
menu tree. However, if you choose a new object using the drop-down list box, the
menu tree appears.
Workaround
: Close the Equation Editor window and re-open.
Configuring an Asset Profile View of 0 Causes Errors
In the STRM System Settings, you can configure the Asset Profile View parameter
to specify the views you wish the system to use when accumulating asset profile
data. By default, the list includes the following views: 1, 2, 15, and 16. If you set a
view to 0, an error appears in the log files. Also, if you upgrade to STRM 2008.2,
any Asset Profile View set to 0 is automatically changed to a value of 16.
Workaround
: None.
During a Restart, an Error May Appear Regarding the Tomcat Server
Any changes to STRM using the web-based system administration interface
requires the Tomcat server to restart. This server may take 1 to 2 minutes to
restart. If, during this time, you access the STRM interface, a fatal error message
appears. Do not attempt to restart the Tomcat server manually. Once the server
restarts, STRM will continue to function as expected.
Workaround
: Wait several minutes for the server to restart, then access the STRM
interface.
Upgrade May Fail with Custom SSL Certificate
The upgrade of STRM may fail if your deployment meets both of the following
conditions:
•
You use a custom SSL (trusted) certificate, rather than the default certificate
shipped with STRM, somewhere in your deployment.
•
The custom certificate has an Intermediate key.