STRM 2008.1 Patch #3
Updated 11 June, 2008

WARNING: When you apply this path, all undeployed changes will be applied.
         This will result in a gap in your data collection. Once complete, data collection will resume. 
 
Patch #3 includes prior patches 1 and 2, so if you have not applied the previous 2 patches for 2008.1, you do not need to download all 3 patches. This patch will detect your patch level during its preflight checks, and apply any prior patches depending upon its discovery. 

The patch #3 address the following STRM2008.1 issues. 
- Corrects inability to restore configuration backups on upgraded systems. 
- Changes postgresql startup to re-index and vacuum on reboot. 
- Fixes running lock management issue. 
- Corrects problem receiving checkpoint messages sent by leapipe. 
- Fixes communication failure with SDEE dsm and source. 
- Fixes out of memory problems with hostcontext process. 

This patch must be applied to all STRM systems running STRM release 2008.1. After this patch is applied, STRM is restarted.

Instructions to apply the patch:

1- Download the patch file (STRM2008.1_patchupdate-3.8.sh.bz2) from

    http://www.juniper.net/support

2- Copy the file to the /tmp directory on your system.

3- Go to the temporary directory:
       cd /tmp

4- Extract the file:
      bunzip2 /tmp/STRM2008.1_patchupdate-3.8.sh.bz2

5- Change the permissions of the file
      chmod 750 611_patchupdate-3.8.sh

6- Install the patch:
      As root, invoke the patch by typing ./STRM2008.1_patchupdate-3.8.sh

Note: Repeat the above instructions on all the servers in your deployment


Copyright 2008,Juniper Networks, Inc. All rights reserved. Juniper Networks, the Juniper Networks logo, NetScreen,
and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United States and other countries. JUNOS and JUNOSe are trademarks of Juniper Networks, Inc. All other trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners. Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer, or otherwise
revise this publication without notice.