Juniper STRM 2008.2 - RELEASE NOTES Release Note page 10

10 STRM Release Notes
System
Configuration
Step 1
Step 2
Step 3
Step 4
Step 5
Deployment Editor
530-025618-01
Restoring Configuration Information for Deployment with Encrypted
Systems Fails
If you attempt to restore configuration information in a deployment that includes
encrypted systems and then deploy all changes, the restore process fails for the
encrypted systems.
Workaround: Follow the Restoring Your Configuration procedure outlined in the
STRM Administration Guide, however, before you deploy all changes, wait for the
STRM interface to become active. Once the interface is active, follow this
procedure:
Log in to STRM, as root.
Enter the following command and any non-Console passwords, as prompted:
/opt/STRM/bin/push_ssh_auth_keys.sh
On the Console, enter the following command:
ssh <IP address/hostname of the non-Console>
On the non-Console, enter the following command:
ssh <IP address/hostname of the Console>
For all systems in your deployment, use SSH to connect from the Console to
non-Console systems and enter the following command:
service hostcontext restart
Performing an Automatic Update Does Not Deploy All Changes
When you update your system using the Auto-Update Configuration window in the
STRM Administration Console, the changes are not enforced throughout your
deployment. This results in updated contents do not appearing in the deployment.
Workaround: From the Administration Console Menu, select Configurations >
Deploy All to enforce the changes.
Unable to Disable an Endace DAG Interface Card Using the Web-Based
System Administration Interface
If you use the Network Interfaces window of the Web-based System Administration
interface to disable an Endace DAG Interface card, a message appears indicating
that the card was successfully disabled. However, the QFlow Collector continues
to receive flows from the disabled Endace DAG Interface card and if you return to
the Network Interface window, the card is set to Monitor.
Workaround: None
Able to Configure Scanner Assignments for Last Entered IP Address
When configuring scanner assignments, you are able to enter multiple IP
addresses; however, scanner assignment configurations are applied only to the IP
address that was entered last.
Workaround: Create scanner assignments for one CIDR address at a time.