Software Update Name: BCM.R400.160-SoftwareManagement

Applicable H/W Platforms: BCM1000, BCM200, BCM400, SRG200 1.5, SRG400 1.5

Applicable S/W Platforms: BCM 4.0, SRG 1.5 based on BCM 4.0

Category: GEN

Installation Recommendations: This patch should be applied to 
   all new installs of BCM4.0 and SRG 1.5 based on BCM 4.0. 
   Existing installations should have this patch applied if they 
   are experiencing any of the issues that are corrected. There 
   is no need to schedule specific maintenance to apply this upgrade 
   if there are no reported issues. In those cases, systems should 
   be updated at the next regular service opportunity. 

Component & Version:
   dialogger            41.20.04.15
   software-management  41.20.003.158

Dependencies:
   Required patches     
      - BCM.R400.SU.System.005 or later version
The dependency patch should be applied first.

   Product Dependencies - None

Size: 505KB

System Impact:
   Time to apply patch ~ 1 min
   Does update application force reboot: Yes
   Other impacts: None

Limitations: None

Update Removable: No


Description:
-----------
The following issues are addressed:

1. The transfer of software is optimized when "My Computer" retrieval 
   option is used from Element Manager. Only the necessary software 
   packages in the patch will be downloaded to the BCM instead of all 
   the software packages.
   Q01791291-01


This patch includes the content of the following superseded updates:

BCM.R400.156-SoftwareManagement:
-------------------------------
    
1. Automatic backup and restore of RPM Database
   The RPM database on BCM 4.0 can become corrupted, preventing users from
   logging in with Element Manager or applying patches. This update delivers
   enhancements to the RPM Database robustness.
   Q01592770-01


BCM.R400.046-SoftwareManagement:
-------------------------------

1. "Scheduled" Patch fails to perform required reboot
   A "scheduled" patch that requests a reboot would fail to perform that reboot.
   Q01503795-02, Q01411128

2. Patches report "Success" before patch application is complete
   The patching process previously would report "Success" as soon as their 
   constituent RPMs were installed. Some patches can perform significant 
   operations after installing their RPMs which, if interrupted by a power cycle, 
   could cause the patch to fail and in the worst case disable the BCM 
   completely. This patch causes future patch processes to wait until all 
   post-processing is complete before reporting patch completion status.
   Q01511412-01

