Patch ID: OpForce5.0MP1+p1944256
Release Date: 18th March 2010
Synopsis: Support for HP smart array P410i, Broadcom Corporation NetXtreme II BCM57711E 10Gigabit PCI
Apply to Release: 5.0 MP1 
Affected Architecture(s): x86, x86_64
Etract ID(s): 1944256
Also Includes: N/A
Conflicting Patches: None
Other Required Patches: None

Keywords: cciss drivers, bnx2x drivers, 2.6.18 Kernel


Rollback possible: Yes

Description: 

  This patch addresses the following issues:
	Support for HP smart array P410i
	Support for Broadcom Corporation NetXtreme II BCM57711E 10Gigabit PCI   

  This patch 
	Adds new files 
		default-2.6.18.krn  
		default-autoeth-65536-2.6.18.gz  
		default-autoeth-131072-2.6.18.gz  
		upgrade-i686-Linux-2.6.18.tgz
        Modifies files
		/opt/veritas/opforce/tomcat/shared/lib/elemental.jar

		/opt/veritas/opforce/lib/elemental.jar   (on Remote boot daemon)


Patch Installation Instructions:  

To apply this patch on a Linux or Solaris OpForce server:

  1. Create a patch directory, and extract:
     OpForce5.0MP1+p1944256.tar
  2. Change directory to the patch directory.
  3. Run ./setup.sh
  4. Select new ActiveOS (OpBoot(TM) Standard X86 (2.6.18 kernel) 256MB or 512MB) for Target
  5. Reboot targets in Admin State with new ActiveOS (OpBoot(TM) Standard X86 (2.6.18 kernel) 256MB or 512MB)

If you have already applied this patch once already, use the backed up
default-2.6.18.krn,
upgrade-i686-Linux-2.6.18.tgz,
default-autoeth-65536-2.6.18.gz,
elemental.jar-Pre-Opforce5.0MP1+p1944256

 present on your system and use them to rollback the patch, if needed.

Remote Boot Daemon:

To install this patch on a Remote Boot Daemon follow the steps mentioned above.
Boot the targets using the Remote boot Daemon listed on the VPM server.


Rollback Procedure: 
./setup.sh uninstall
  

Importatnt: 
Targets machines using AOS 揙pBoot(TM) Standard X86 (2.6.18 kernel) 256MB or 512MB� should be removed or AOS should be changed before uninstalling this patch. 
If not then the target machine has to be removed from list of computing devices and rediscovered again.

Also in case you need to customize the name of the new AOSs, use the following properties in elemental.properties

driver.bootd.dhcp.aos.x86opboot.rh5-256MB.desc=2.6.18 Kernel 256M Autonegotiate 
driver.bootd.dhcp.aos.x86opboot.rh5-512MB.desc=2.6.18 Kernel 512M 100Full