martes, 20 de septiembre de 2011

Versiones de HP-UX y fechas de fin de soporte

Versiones de HP-UX

Como todo Sistema Operativo, HP-UX ha tenido varias  modificaciones y fue evolucionando con distintas versiones a lo largo del tiempo

Versión Plataforma Fecha de release Fecha de fin de soporte
HP-UX 10.20  HP 9000 Agosto 1996 Junio 2003
HP-UX 11.00 HP 9000 Noviembre 1997  Diciembre 2006
HP-UX 11iv1 HP 9000 Diciembre 2000 Diciembre 2013
HP-UX 11iv2 HP 9000 & Integrity  Octubre 2003 Diciembre 2013
HP-UX 11iv3 HP 9000 & Integrity Febrero 2007 Diciembre 2020
Esta información puede cambiar por lo tanto se recomienda visitar www.hp.com/go/hpuxsupportmatrix para mayor seguridad

A partir del lanzamiento de la versión 11.31 HP implemento la política de liberar nuevos updates del sistema operativo 2 veces por año. A la fecha de hoy de han liberado los siguientes updates de 11v3
  • HP-UX 11i v3 Sep 2011 (Update 9)
  • HP-UX 11i v3 Mar 2011 (Update 8)
  • HP-UX 11i v3 Sep 2010 (Update 7)
  • HP-UX 11i v3 Mar 2010 (Update 6)
  • HP-UX 11i v3 Sep 2009 (Update 5)
  • HP-UX 11i v3 Mar 2009 (Update 4)
  • HP-UX 11i v3 Sep 2008 (Update 3)
  • HP-UX 11i v3 Mar 2008 (Update 2)
  • HP-UX 11i v3 Sep 2007 (Update 1)
HP-UX 11v3 viene en 3 Operating Enviroments adicionales ademas del BaseOE. Los Operating Enviroments (OE) son paquetes de software extra que nos permiten, Virtualizar, Espejar discos por soft, armar clusters de alta disponibilidad, entre otras.

HP-UX 11iv3 (BOE)
* Base OE, es el sistema operativo base

HP-UX 11iv3 (HA-OE)
* Base OE,
* Mirror/UX,
* MCServiceGuard + Toolkits,
* OnlineJFS (VxFS full),
* GlancePlus Pak

HP-UX 11iv3 (VSE-OE)
* Base OE,
* HP-UX 11i vPars,
* HP Integrity Virtual Machines,
* HP Online VM Migration,
* OnlineJFS (VxFS full),
* Mirror/UX,
* GlancePlus Pak

HP-UX 11iv3 (DC-OE)
* Base OE,
* HP-UX 11i vPars,
* HP Integrity Virtual Machines,
* HP Online VM Migration,
* Mirror/UX,
* MCServiceGuard + Toolkits,
* OnlineJFS (VxFS full),
* GlancePlus Pak


Para mas información acerca de los Operating Enviroments hacer click aqui

viernes, 9 de septiembre de 2011

Uso de Dynamic root disk (DRD)

Descripción de la herramienta

Dynamic Root Disk (DRD) es una utilidad gratuita para las versiones 11v2 y 11v3 de HP-UX que nos permite clonar el root disk a otro disco para poder realizar tareas de mantenimiento con un mínimo downtime.

Instalación

Podemos verificar si el producto DRD esta instalado en nuestro equipo, para ello corremos lo siguiente

<root@corona/root>swlist -l product |grep DRD
  DRD                   B.1131.A.3.8.454 Dynamic Root Disk 

Caso contrario bajaremos el software de la url http://software.hp.com a la fecha la ultima versión disponible y con la que trabajaremos es la A.3.9.432


Una vez que descargamos el soft lo copiamos al servidor en el cual haremos las pruebas y verificamos el contenido del depot con un swlist


# swlist -s /var/tmp/DRD_1131_WEB1107.depot 
# Initializing...
# Contacting target "corona"...
#
# Target:  corona:/var/tmp/DRD_1131_WEB1107.depot
#

#
# Bundle(s):
#

  DynRootDisk                   B.1131.A.3.9.432 Dynamic Root Disk 
  Judy                          B.11.31.04.18  Judy Libraries 
  SD                            B.11.31.1109.366 HP Software Distributor 
#
# Product(s) not contained in a Bundle:
#

  PHCO_38608                    1.0            auto_parms/set_parms/dhcpdb2conf cumulative patch 
  PHCO_39064                    1.0            FirstBoot sysinfo.4 manpage patch 
  PHCO_39359                    1.0            FirstBoot Japanese sysinfo.4 manpage patch 
  SWM                           A.3.9.1.432    HP-UX Software Manager 

En el listado de arriba figuran los paquetes que se instalaran en el equipo junto con el DRD. 
Ahora procederemos a instalar el soft. 
NOTA: Recordemos siempre mirar en las instrucciones de instalación, requerimientos y parches necesarios para la herramienta.

Podemos optar de una instalacion no interactiva mediante el comando

<corona:/root>swinstall -s /var/tmp/DRD_1131_WEB1107.depot \*

O podemos hacer una instalacion interactiva de esta  otra forma

<corona:/root>swinstall -s /var/tmp/DRD_1131_WEB1107.depot

Nosotros vamos a a elegir el modo no interactivo.

<corona:/root>swinstall -s /var/tmp/DRD_1131_WEB1107.depot \*

=======  09/08/11 12:09:41 SAT  BEGIN swinstall SESSION
         (non-interactive) (jobid=corona-0001)

       * Session started for user "root@corona".
         
       * Beginning Selection
       * Target connection succeeded for "corona:/".
       * Source:                 /var/tmp/DRD_1131_WEB1107.depot
       * Targets:                corona:/
       * Software selections:
             DynRootDisk,r=B.1131.A.3.9.432,a=HP-UX_B.11.31_IA/PA,v=HP
             Judy,r=B.11.31.04.18,a=HP-UX_B.11.31_IA/PA,v=HP
             SD,r=B.11.31.1109.366,a=HP-UX_B.11.31_IA/PA,v=HP
             DRD.DRD-ENG-A-MAN,r=B.1131.A.3.9.432,a=HP-UX_B.11.31_IA/PA,v=HP,fr=B.1131.A.3.9.432,fa=HP-UX_B.11.31_IA/PA
             DRD.DRD-RUN,r=B.1131.A.3.9.432,a=HP-UX_B.11.31_IA/PA,v=HP,fr=B.1131.A.3.9.432,fa=HP-UX_B.11.31_PA
....
       * Selection succeeded.
         
       * Beginning Analysis and Execution
       * Session selections have been saved in the file
         "/root/.sw/sessions/swinstall.last".
       * "corona:/":  4 filesets have the selected revision already
         installed.
       * "corona:/":  The software dependencies for 2 products or
         filesets cannot be resolved.
       * "corona:/":  6 software objects were determined to be skipped
         in the analysis phase.
       * Analysis and Execution succeeded.
        
NOTE:    More information may be found in the agent logfile using the
         command "swjob -a log corona-0001 @ corona:/".

=======  09/08/11 12:10:17 SAT  END swinstall SESSION (non-interactive)
         (jobid=corona-0001)



Como chequeo adicional vamos a verificar que todos los filesets hayan quedado en configured y que todos los parches estén bien configurados

<corona:/root>swlist -l fileset -a state |grep -v configured |grep -v "#"

Si la salida de este comando es vacía todos los filesets del equipo están configurados

<corona:/root>check_patches
Obtaining information on installed patches
Checking for invalid patches
Checking object module checksums for active patch fileset   506 of   506
Checking patch filesets for active patch   287 of   287
Checking state for patch fileset   506 of   506
Checking patch_state for patch fileset   506 of   506
Checking load order of patch fileset   506 of   506
Running swverify on all patch filesets, this may take several minutes
RESULT: No problems found, review /tmp/check_patches.report for details.

Como vemos la salida comando anterior no dio problemas con ningún parche. Con lo cual el estado del equipo luego de la instalación de DRD es saludable.

Descripción de las opciones de uso y ejemplos

Ahora que tenemos la herramienta instalada en nuestro equipo analizaremos las operaciones que se pueden hacer con DRD son,
  • drd activate
    Activa el disco clon para el próximo booteo.
  • drd clone
    Genera la copia del disco de booteo.
  • drd deactivate
    Es la operación inversa al drd activate. Vuelve a setear como booteable al disco original.
  • drd mount
    Monta los filesystems de la imagen inactiva en /var/opt/drd/mnts/sysimage_001
  • drd rehost
    Permite provisionar nuevos servidores. Esta opción solo funciona para servidores Itanium.
  • drd runcmd
    Permite ejecutar comandos en la imagen inactiva. Estos comandos pueden ser de SD-UX y tuneables de kernel.
  • drd status
    Muestra información de estado de la copia
  • drd sync
    Permite sincronizar las diferencias entre la imagen activa y la inactiva
  • drd umount
    Desmonta la imagen que fue montada previamente con un drd mount
  • drd unrehost
    Quita la informacion que sirve para rehosting del disco clon.
DRD clone

Antes de proceder con el clonado del disco de booteo  debemos identificar el disco destino.  


NOTA: Aquí nos podemos encontrar con varios escenarios, podemos tener discos en LVM 1.0 en LVM 2.X, o gestionados por VxVM o por ultimo que estos sean raw devices. Aquí vamos a simplificar el tutorial suponiendo que podemos encontrarnos solo con discos bajo LVM (1.0 o 2.X) 

<corona:/root>ioscan -fnC disk
Class     I  H/W Path       Driver S/W State   H/W Type     Description
=======================================================================
disk      2  0/0/3/0.0.0.0  sdisk   CLAIMED     DEVICE       TEAC    DV-28E-N
                           /dev/dsk/c0t0d0   /dev/rdsk/c0t0d0
disk      0  0/1/1/0.0.0    sdisk   CLAIMED     DEVICE       HP 73.4GHUS153073VL3800
                           /dev/dsk/c2t0d0   /dev/rdsk/c2t0d0
disk      1  0/1/1/0.1.0    sdisk   CLAIMED     DEVICE       HP 73.4GHUS153073VL3800
                           /dev/dsk/c2t1d0   /dev/rdsk/c2t1d0

Vemos que en este caso poseemos 2 discos y una unidad de DVD. Ahora para ver que disco tenemos asignado a LVM podemos hacer un

<corona:/root>strings /etc/lvmtab
/dev/vg00
~`Ng
/dev/disk/disk4

Chequeamos también si tenemos discos bajo LVM 2.X

<corona:/root>strings /etc/lvmtab_p

Se podría haber revisado esto ultimo con un solo comando lvmadm -l 


<corona:/root>lvmadm -l

--- Version 1.0 volume groups ---

VG Name /dev/vg00

PV Name /dev/disk/disk4


Del ultimo comando sabemos que el disk4 forma parte del vg00, ahora para establecer la correspondencia de Legacy DSF a Agile DSF podemos correr el siguiente ioscan

<corona:/root>ioscan -m dsf
Persistent DSF           Legacy DSF(s)
========================================
/dev/rdisk/disk3         /dev/rdsk/c2t0d0
/dev/rdisk/disk4         /dev/rdsk/c2t1d0
/dev/rdisk/disk5         /dev/rdsk/c0t0d0

El disco libre que tenemos en el equipo es el disk3 (c2t0d0). En una nota futura vamos a analizar las ventajas de los DSF Agile(Persistent) respecto los Legacy.

Ya instalado el software de DRD e identificado el disco, podemos lanzar un el comando para realizar el clonado del disco, las opciones -p es para que efectúe un preview -v para que que lo haga verbose -t es el target device, es decir el disco libre.



<corona:/root>drd clone -p -v -t /dev/disk/disk3


=======  09/08/11 12:22:08 SAT  BEGIN Clone System Image Preview (user=root)
         (jobid=corona)


       * Reading Current System Information
       * Selecting System Image To Clone
       * Selecting Target Disk
ERROR:   Selection of the target disk fails.
         - Selecting the target disk fails.
         - Validation of the disk "/dev/disk/disk3" fails with the following
           error(s): 
         - The disk "/dev/disk/disk3" contains data. To overwrite this disk use
           the option "-x overwrite=true".
       * Selecting Target Disk failed with 1 error.
       * DRD operation failed, contents of /var/opt/drd/tmp copied to
         /var/opt/drd/save.


=======  09/08/11 12:22:17 SAT  END Clone System Image Preview failed with 1
         error. (user=root)  (jobid=corona)


En el caso anterior, la creación del clon fallo debido a que el disco destino tenia una estructura de LVM, esto puede ser a que el disco estuvo en algún momento y no se elimino la cabecera de LVM con un pvremove o a que el disco esta dentro de un vg.
Podemos forzar la creación del clon mediante el flag -x overwrite=true 



<corona:/root>drd clone -p -v -x overwrite=true -t /dev/disk/disk3


=======  09/08/11 12:59:13 SAT  BEGIN Clone System Image Preview (user=root)
         (jobid=corona)


       * Reading Current System Information
       * Selecting System Image To Clone
       * Selecting Target Disk
       * The disk "/dev/disk/disk3" contains data which will be overwritten.
       * Selecting Volume Manager For New System Image
       * Analyzing For System Image Cloning


=======  09/08/11 12:59:21 SAT  END Clone System Image Preview succeeded.
         (user=root)  (jobid=corona)

Vemos que el preview no produjo ningún error, por que vamos a correr el comando sin el flag -p. Este comando puede demorar varios minutos



<corona:/root>drd clone -v -x overwrite=true -t /dev/disk/disk3   


=======  09/08/11 12:59:42 SAT  BEGIN Clone System Image (user=root)
         (jobid=corona)


       * Reading Current System Information
       * Selecting System Image To Clone
       * Selecting Target Disk
       * The disk "/dev/disk/disk3" contains data which will be overwritten.
       * Selecting Volume Manager For New System Image
       * Analyzing For System Image Cloning
       * Creating New File Systems
       * Copying File Systems To New System Image
       * Making New System Image Bootable
       * Unmounting New System Image Clone
       * System image: "sysimage_001" on disk "/dev/disk/disk3"


=======  09/08/11 13:15:46 SAT  END Clone System Image succeeded. (user=root)
         (jobid=corona)

Si abrimos otra treminal mientras corre el drd clone podemos observar que se creo un nuevo VG llamado drd00 y que replica la estructura del vg00 en /var/opt/drd/mnts/sysimage_001



<root@corona/root>bdf
Filesystem          kbytes    used   avail %used Mounted on
/dev/vg00/lvol3    1048576  144352  897272   14% /
/dev/vg00/lvol7    4210688 2066304 2127744   49% /usr
/dev/vg00/lvol6    5341184 3042304 2282600   57% /opt
/dev/vg00/lvol8    10485760 2353336 8071128   23% /var
/dev/vg00/lvol4     524288  124160  397104   24% /tmp
/dev/vg00/lvol1    1776056   93080 1505368    6% /stand
/dev/vg00/lvol5    10485760 7188200 3271912   69% /home
10.1.10.13:/SD-UX  10321208 8977060  819860   92% /SD
/dev/drd00/lvol3   1048576  143824  897792   14% /var/opt/drd/mnts/sysimage_001/
/dev/drd00/lvol1   1776056   90392 1508056    6% /var/opt/drd/mnts/sysimage_001/stand
/dev/drd00/lvol4    524288  119592  401632   23% /var/opt/drd/mnts/sysimage_001/tmp
/dev/drd00/lvol5   10485760 7187520 3272584   69% /var/opt/drd/mnts/sysimage_001/home
/dev/drd00/lvol6   5341184 3040360 2282864   57% /var/opt/drd/mnts/sysimage_001/opt
/dev/drd00/lvol7   4210688 2058056 2135888   49% /var/opt/drd/mnts/sysimage_001/usr
/dev/drd00/lvol8   10485760   21032 10382984    0% /var/opt/drd/mnts/sysimage_001/var


Si ejecutamos un top para ver el estado de la maquina mientras corre el proceso de clonado por drd podemos observar que este realiza la copia mediante las herramientas de HP-UX fbackup y frecover



System: corona                                        Wed Sep  7 12:54:09 2011
Load averages: 0.16, 0.08, 0.03
167 processes: 112 sleeping, 55 running
Cpu states:
CPU   LOAD   USER   NICE    SYS   IDLE  BLOCK  SWAIT   INTR   SSYS
 0    0.16   0.8%   0.0%  10.6%  88.6%   0.0%   0.0%   0.0%   0.0%
 1    0.13   0.6%   0.0%  10.4%  89.0%   0.0%   0.0%   0.0%   0.0%
 2    0.15   1.2%   0.0%  13.1%  85.7%   0.0%   0.0%   0.0%   0.0%
 3    0.18   1.2%   0.0%   8.2%  90.6%   0.0%   0.0%   0.0%   0.0%
---   ----  -----  -----  -----  -----  -----  -----  -----  -----
avg   0.16   1.0%   0.0%  10.6%  88.4%   0.0%   0.0%   0.0%   0.0%


System Page Size: 4Kbytes
Memory: 297828K (165376K) real, 544076K (286956K) virtual, 1327952K free  Page#
1/19


CPU TTY  PID USERNAME PRI NI   SIZE    RES STATE    TIME %WCPU  %CPU COMMAND
 0   ?  4668 root     134 20  3036K  1196K run      0:40 26.01 25.97 frecover
 2   ?  4670 root     168 20  2244K   260K sleep    0:06  4.63  4.62 fbackuprdr
 2   ?  4669 root     168 20  2244K   260K sleep    0:06  4.50  4.49 fbackuprdr
 0   ?     2 root     128 20    36K    36K run      9:51  4.04  4.04 vhand
 1   ?  4667 root     168 20 14560K 12348K sleep    0:07  3.07  3.07 fbackup
 3   ?  4671 root     154 20  2396K   312K sleep    0:03  2.89  2.88 fbackupwrtr
 3   ?    63 root     128 20    36K    36K sleep    8:04  0.48  0.47 fcachedaem

Finalizado el proceso de clonado podemos lanzar un drd status




<corona:/root>drd status


=======  09/08/11 13:54:23 SAT  BEGIN Displaying DRD Clone Image Information
         (user=root)  (jobid=corona)


       * Clone Disk:               /dev/disk/disk3
       * Clone LIF Area:           AUTO file present, Boot loader present 
       * Clone Creation Date:      09/08/11 12:59:52 SAT
       * Last Sync Date:           None
       * Clone Mirror Disk:        None
       * Mirror LIF Area:          None
       * Original Disk:            /dev/disk/disk4
       * Original LIF Area:        AUTO file present, Boot loader present 
       * Booted Disk:              Original Disk (/dev/disk/disk4)
       * Activated Disk:           Original Disk (/dev/disk/disk4)


=======  09/08/11 13:54:34 SAT  END Displaying DRD Clone Image Information
         succeeded. (user=root)  (jobid=corona)


Ahora podemos hacer tareas de mantenimiento con el drd tales como, instalar parches, tunear el kernel y llevar el SO a un release mayor, entre otras.


DRD cmd


Con drd cmd podemos lanzar ciertos comandos que son drd safe dentro de estos comandos se encuentran los de modificación de parámetros de kernel, los comandos de SD-UX y el update-ux.


Modificación de parámetros de kernel usando drd cmd


<corona:/root>drd runcmd kctune maxfiles=4096

=======  09/09/11 16:11:48 SAT  BEGIN Executing Command On Inactive System
         Image (user=root)  (jobid=corona)

       * Checking for Valid Inactive System Image
       * Analyzing Command To Be Run On Inactive System Image
       * Locating Inactive System Image
       * Preparing Inactive System Image For Command Execution
       * Selected inactive system image "sysimage_001" on disk
         "/dev/disk/disk3".
       * Accessing Inactive System Image for Command Execution
       * Setting Up Environment For Command Execution
       * Executing Command On Inactive System Image
       * Executing command: "/usr/sbin/kctune maxfiles=4096"
     ==> Update the automatic 'backup' configuration first? y
WARNING: The backup behavior 'yes' is not supported in alternate root
         environments.  The behavior 'once' will be used instead.
       * The automatic 'backup' configuration has been updated.
       * Future operations will ask whether to update the backup.
       * The requested changes have been applied to the currently
         running configuration.
Tunable              Value  Expression  Changes
maxfiles  (before)  (auto)  Default     Immed
          (now)       4096  4096        
       * The command "/usr/sbin/kctune maxfiles=4096" succeeded.
       * Cleaning Up After Command Execution On Inactive System Image

=======  09/09/11 16:12:32 SAT  END Executing Command On Inactive System Image
         succeeded. (user=root)  (jobid=corona)

Corremos un kctune maxfiles para verificar que el parámetro no cambio en el disco original.

<corona:/root>kctune maxfiles
Tunable   Value  Expression  
maxfiles   2048  Default   

DRD activate

 Ahora vamos a activar el disco clon para bootear la imagen de kernel modificada

<corona:/root>drd activate -x reboot=true


=======  09/09/11 16:29:12 SAT  BEGIN Activate Inactive System Image
         (user=root)  (jobid=corona)


       * Checking for Valid Inactive System Image
       * Reading Current System Information
       * Locating Inactive System Image
       * Determining Bootpath Status
       * Primary bootpath : /dev/disk/disk4 before activate.
       * Primary bootpath : /dev/disk/disk3 after activate.
       * Alternate bootpath : /dev/disk/disk3 before activate.
       * Alternate bootpath : /dev/disk/disk3 after activate.
       * Activating Inactive System Image
       * Rebooting System


SHUTDOWN PROGRAM
09/09/11 16:29:36 SAT


Broadcast Message from root (pts/0) Fri Sep  9 16:29:36...
PLEASE LOG OFF NOW ! ! !
        System maintenance about to begin.
All processes will be terminated in 0 seconds.


Vamos a chequear si el parámetro efectivamente fue modificado


<corona:/root>kctune maxfiles
Tunable   Value  Expression  
maxfiles   4096  4096 


Podemos verificar que booteamos de la imagen clonada corriendo un drd status


<corona:/root>drd status


=======  09/09/11 16:48:46 SAT  BEGIN Displaying DRD Clone Image Information
         (user=root)  (jobid=corona)


       * Clone Disk:               /dev/disk/disk3
       * Clone LIF Area:           AUTO file present, Boot loader present 
       * Clone Creation Date:      09/08/11 12:59:52 SAT
       * Last Sync Date:           None
       * Clone Mirror Disk:        None
       * Mirror LIF Area:          None
       * Original Disk:            /dev/disk/disk4
       * Original LIF Area:        AUTO file present, Boot loader present 
       * Booted Disk:              Clone Disk (/dev/disk/disk3)
       * Activated Disk:           Clone Disk (/dev/disk/disk3)


=======  09/09/11 16:48:57 SAT  END Displaying DRD Clone Image Information
         succeeded. (user=root)  (jobid=corona)


Procedimiento para hacer un update-ux usando DRD

Vamos a chequear la versión actual del OS, 

<corona:/root>swlist -l bundle |grep HPUX11i
  HPUX11i-BOE           B.11.31.1009   HP-UX Base Operating Environment 

Montamos el cdrom con una version superior de HP-UX
<corona:/root>mount /dev/disk/disk5 /cdrom

Chequeo si la versión de 11.31 del cdrom es superior a la que tengo instalada

<corona:/root>swlist -s /cdrom
# Initializing...
# Contacting target "corona"...
#
# Target:  corona:/cdrom
#


#
# Bundle(s):
#


  10GigEthr-00          B.11.31.1012   PCI-X 10 Gigabit Ethernet;Supptd HW=AB287, HW=AD385
  10GigEthr-01          B.11.31.1012   PCIe 10 Gigabit Ethernet;Supptd HW=AD386A
  10GigEthr-02          B.11.31.1103   PCIe 10 Gigabit Ethernet;Supptd HW=467799-B21
  10GigEthr-03          B.11.31.1103   PCIe 10 Gigabit Ethernet;Supptd HW=580151-B21
  ...
  HPUX11i-BOE           B.11.31.1103   HP-UX Base Operating Environment
  ...
  hpuxwsXml             A.2.03         HPUX XML      
  perl                  E.5.8.8.F      Perl Programming Language
  scsiU320-00           B.11.31.0909   PCI-X SCSI U320;Supptd HW=A7173A/AB290A
  swapoff               B.11.31.0809.02 HP-UX Swapoff Enhancement

Como recomendación HP sugiere primero actualizar el paquete Update-UX, para ello vamos a instalar la versión que viene en el DVD del nuevo release.

<corona:/cdrom>swinstall -s /cdrom Update-UX


=======  09/19/11 16:14:48 SAT  BEGIN swinstall SESSION
         (non-interactive) (jobid=corona-0027)


       * Session started for user "root@corona".
         
       * Beginning Selection
       * Target connection succeeded for "corona:/".
       * "corona:/cdrom":  Cannot open the logfile on this target or
         source.  Possibly the media is read-only or there is a
         permission problem.  Check the daemon logfile and
         "/var/tmp/swagent.log" on this host for more information.
       * Source:                 /cdrom
       * Targets:                corona:/
       * Software selections:
             Update-UX.SD-AGENT,r=B.11.31.1103.360,a=HP-UX_B.11.31_IA/PA,v=HP,fr=B.11.31,fa=HP-UX_B.11.31_PA
             Update-UX.SD-CMDS,r=B.11.31.1103.360,a=HP-UX_B.11.31_IA/PA,v=HP,fr=B.11.31,fa=HP-UX_B.11.31_PA
             Update-UX.SD-FRE-I-MSG,r=B.11.31.1103.360,a=HP-UX_B.11.31_IA/PA,v=HP,fr=B.11.31.1103.360,fa=HP-UX_B.11.31_IA/PA
             Update-UX.SD-GER-I-MSG,r=B.11.31.1103.360,a=HP-UX_B.11.31_IA/PA,v=HP,fr=B.11.31.1103.360,fa=HP-UX_B.11.31_IA/PA
             Update-UX.SD-JPN-E-MSG,r=B.11.31.1103.360,a=HP-UX_B.11.31_IA/PA,v=HP,fr=B.11.31.1103.360,fa=HP-UX_B.11.31_IA/PA
             Update-UX.SD-JPN-S-MSG,r=B.11.31.1103.360,a=HP-UX_B.11.31_IA/PA,v=HP,fr=B.11.31.1103.360,fa=HP-UX_B.11.31_IA/PA
             Update-UX.SD-KOR-E-MSG,r=B.11.31.1103.360,a=HP-UX_B.11.31_IA/PA,v=HP,fr=B.11.31.1103.360,fa=HP-UX_B.11.31_IA/PA
             Update-UX.SD-TCH-B-MSG,r=B.11.31.1103.360,a=HP-UX_B.11.31_IA/PA,v=HP,fr=B.11.31.1103.360,fa=HP-UX_B.11.31_IA/PA
             Update-UX.SD-TCH-H-MSG,r=B.11.31.1103.360,a=HP-UX_B.11.31_IA/PA,v=HP,fr=B.11.31.1103.360,fa=HP-UX_B.11.31_IA/PA
             Update-UX.UUX,r=B.11.31.1103.360,a=HP-UX_B.11.31_IA/PA,v=HP,fr=B.11.31.1103.360,fa=HP-UX_B.11.31_IA/PA
             Update-UX.UUX-ENG-A-MAN,r=B.11.31.1103.360,a=HP-UX_B.11.31_IA/PA,v=HP,fr=B.11.31.1103.360,fa=HP-UX_B.11.31_IA/PA
             Update-UX.UUX-JPN-E-MAN,r=B.11.31.1103.360,a=HP-UX_B.11.31_IA/PA,v=HP,fr=B.11.31.1103.360,fa=HP-UX_B.11.31_IA/PA
             Update-UX.UUX-JPN-S-MAN,r=B.11.31.1103.360,a=HP-UX_B.11.31_IA/PA,v=HP,fr=B.11.31.1103.360,fa=HP-UX_B.11.31_IA/PA
             Update-UX.UUX2-OS-LIBS,r=B.11.31.1103.360,a=HP-UX_B.11.31_IA/PA,v=HP,fr=B.11.31,fa=HP-UX_B.11.31_PA
       * Selection succeeded.
      
         
       * Beginning Analysis and Execution
       * Session selections have been saved in the file
         "/root/.sw/sessions/swinstall.last".
       * "corona:/":  1 filesets have the selected revision already
         installed.
       * "corona:/":  10 software objects had their check script return
         the code indicating that the software will be excluded from
         further processing.
       * "corona:/":  11 software objects were determined to be skipped
         in the analysis phase.
       * Analysis and Execution succeeded.
         
         
NOTE:    More information may be found in the agent logfile using the
         command "swjob -a log corona-0027 @ corona:/".


=======  09/19/11 16:15:10 SAT  END swinstall SESSION (non-interactive)
         (jobid=corona-0027)


Ahora podemos lanzar el proceso de actualización


<corona:/cdrom>drd runcmd update-ux -s /cdrom


=======  09/19/11 16:30:27 SAT  BEGIN Executing Command On Inactive System Image (user=root)  (jobid=corona)


       * Checking for Valid Inactive System Image
       * Analyzing Command To Be Run On Inactive System Image
       * Locating Inactive System Image
       * Preparing Inactive System Image For Command Execution
       * Selected inactive system image "sysimage_001" on disk "/dev/disk/disk4".
       * Accessing Inactive System Image for Command Execution
       * Setting Up Environment For Command Execution
       * Executing Command On Inactive System Image
       * Starting fsdaemon for drd runcmd
       * Using unsafe patch list version 20080324
       * Starting swagentd for drd runcmd
       * User supplied command: "/usr/sbin/update-ux -s /cdrom"
       * Executing command: "/opt/swm/bin/swm oeupdate -s /cdrom"


=======  09/19/11 16:30:54 SAT  BEGIN Operating Environment Update (user=root)  (jobid=000004)


       * Reading Target System's Installed Product Database (IPD)
       * Target IPD:   corona
       * Reading Source Depot(s)
       * Source depot: corona:/cdrom
       * Choosing Operating Environment
       * The chosen operating environment (OE) is: "HPUX11i-BOE".
NOTE:    Loading *temporary* update tools that do not affect the running system and will be removed when the OE update is finished
         
       * Analyzing OE Update Tools To Be Installed
       * Analysis Summary
         - Reboot needed: No
         - Kernel build needed: No
         - Number of check scripts run: 12 (0 excluded, 0 failed)
         - Install:  20 filesets
       * Loading OE Update Tools
       * Installing fileset "SW-GETTOOLS.PRE-UPDATE,r=B.11.31.1103" (1 of 20).
       * Installing fileset "SW-GETTOOLS.SD-SUPPORT,r=B.11.31.1103" (2 of 20).
       * Installing fileset "SW-GETTOOLS.SD2-SUPPORT,r=B.11.31.1103" (3 of 20).
       * Installing fileset "SWMTRANS.SWMT-ENG-A-HELP,r=A.3.8.1.318" (4 of 20).
       * Installing fileset "SWMTRANS.SWMT-ENG-A-MAN,r=A.3.8.1.318" (5 of 20).
       * Installing fileset "SWMTRANS.SWMT-JPN-E-HELP,r=A.3.8.1.318" (6 of 20).
       * Installing fileset "SWMTRANS.SWMT-JPN-E-MAN,r=A.3.8.1.318" (7 of 20).
       * Installing fileset "SWMTRANS.SWMT-JPN-S-HELP,r=A.3.8.1.318" (8 of 20).
       * Installing fileset "SWMTRANS.SWMT-JPN-S-MAN,r=A.3.8.1.318" (9 of 20).
       * Installing fileset "SWMTRANS.SWMT-RUN,r=A.3.8.1.318" (10 of 20).
       * Installing fileset "Update-UX.SD-AGENT,r=B.11.31.1103.360" (11 of 20).
       * Installing fileset "Update-UX.SD-CMDS,r=B.11.31.1103.360" (12 of 20).
       * Installing fileset "Update-UX.SD-FRE-I-MSG,r=B.11.31.1103.360" (13 of 20).
       * Installing fileset "Update-UX.SD-GER-I-MSG,r=B.11.31.1103.360" (14 of 20).
       * Installing fileset "Update-UX.SD-JPN-E-MSG,r=B.11.31.1103.360" (15 of 20).
       * Installing fileset "Update-UX.SD-JPN-S-MSG,r=B.11.31.1103.360" (16 of 20).
       * Installing fileset "Update-UX.SD-KOR-E-MSG,r=B.11.31.1103.360" (17 of 20).
       * Installing fileset "Update-UX.SD-TCH-B-MSG,r=B.11.31.1103.360" (18 of 20).
       * Installing fileset "Update-UX.SD-TCH-H-MSG,r=B.11.31.1103.360" (19 of 20).
       * Installing fileset "Update-UX.UUX2-OS-LIBS,r=B.11.31.1103.360" (20 of 20).
       * Re-starting Using the Latest OE Update Tools
       * Reading Target System's Installed Product Database (IPD)
       * Target IPD:   corona
       * Reading Source Depot(s)
       * Source depot: corona:/cdrom
       * Selecting Software Dependencies, etc.
WARNING: The following was found while selecting software: 
         - The same version of the following software is already installed (to select this software, set '-x reinstall=true' and try
           again):
           - ACC-LINK.ACC-LINK,r=C.03.80
           - AVXFS.AVXFSPKG,r=B.05.00.02
           - Accounting.ACCOUNTNG,r=B.11.31
           - Accounting.ACCOUNTNG2,r=B.11.31
           - Accounting.ACCT-ENG-A-MAN,r=B.11.31
           - BLKONLY-MS.BLKONLY-MS-KRN,r=D.11.31.0909
           - BLKONLY-MS.BLKONLY-MS-RUN,r=D.11.31.0909
           - BOOT-KBD.BOOT-KBD-KRN,r=D.11.31.0909
           - BOOT-MOUSE.BOOT-MOUSE-KRN,r=D.11.31.0909
           - Bastille.BASTILLE,r=B.3.3
           - Bastille.BASTILLE-AUX,r=B.3.3
           - CDE.CDE-SHLIBS,r=B.11.31
           - CIFS-Client.CIFSCLIENT-KRN,r=A.02.02.02
           - CIFS-Client.CIFSCLIENT-MAN,r=A.02.02.02
           - CIFS-Client.CIFSCLIENT-MIS,r=A.02.02.02
           - CIFS-Client.CIFSCLIENT-RUN,r=A.02.02.02
           - COMPLIBS.LIBBLAS-PA32,r=B.11.31
           - COMPLIBS.LIBCPS-INC,r=B.11.31
           - COMPLIBS.LIBCPS-PA32,r=B.11.31
           - COMPLIBS.LIBCPS-PA64,r=B.11.31
           ....
           - SwAssistant,r=C.02.80
           - SwaMin.SWA-ENG-A-MAN,r=C.02.80
           - SwaMin.SWA-RUN,r=C.02.80
           - SwaMin,r=C.02.80
           - Java60JDK.Jdk60,r=1.6.0.09.00
           - Java60JDK.Jre60,r=1.6.0.09.00
           - Java60JDKadd.Jdk60,r=1.6.0.09.00
           - Java60JDKadd.Jre60,r=1.6.0.09.00
           - Java60JRE.Jre60,r=1.6.0.09.00
           - Java60JREadd.Jre60,r=1.6.0.09.00
       * Analyzing Software To Be Installed
       * Running checkinstall Scripts
       * Running "checkinstall" for "ObsIPQoS,r=B.11.31".
NOTE:    The ObsIPQoS product is relevant during an update where there
         is incompatible IPQoS (HPUXIPQOS) software on the system to be
         obsoleted (removed).
NOTE:    The "checkinstall" for "ObsIPQoS,r=B.11.31" gave an Exclude return (exit code "3"). The script location was
         "/var/opt/swm/tmp/swmt2pBkS54b/SDcat0X4DbOq/catalog/ObsIPQoS/pfiles/checkinstall".
       * Running "checkinstall" for "ObsISCSI-SWD,r=B.11.31.01".
NOTE:    The "checkinstall" for "ObsISCSI-SWD,r=B.11.31.01" gave an Exclude return (exit code "3"). The script location was
         "/var/opt/swm/tmp/swmt2pBkS54b/SDcat0X4DbOq/catalog/ObsISCSI-SWD/pfiles/checkinstall".
       * Running "checkinstall" for "ObsDMI.DMI-PRG,r=B.11.31.03".
NOTE:    The "checkinstall" for "ObsDMI.DMI-PRG,r=B.11.31.03" gave an Exclude return (exit code "3"). The script location was
         "/var/opt/swm/tmp/swmt2pBkS54b/SDcat0X4DbOq/catalog/ObsDMI/DMI-PRG/checkinstall".
       * Running "checkinstall" for "ObsSCR.SCR-RUN,r=B.11.31.03".
NOTE:    The "checkinstall" for "ObsSCR.SCR-RUN,r=B.11.31.03" gave an Exclude return (exit code "3"). The script location was
         "/var/opt/swm/tmp/swmt2pBkS54b/SDcat0X4DbOq/catalog/ObsSCR/SCR-RUN/checkinstall".
       * Analysis Summary
         - Reboot needed: No
         - Kernel build needed: Yes
         - Number of check scripts run: 84 (4 excluded, 0 failed)
         - Install:  22 bundles  725 filesets
         - Update:   39 bundles  417 filesets
       * Running update_prep Scripts
       * Running any scripts found in directory "/var/adm/sw/update_prep".
       * Running "/var/adm/sw/update_prep/FSCmdsEnh.099".
NOTE:    FSCmdsEnh already cleaned from system.
NOTE:    FSLibEnh already cleaned from system.
NOTE:    DiskQuota-Enh already cleaned from system.
       * Running "/var/adm/sw/update_prep/ENHKEY.100".
NOTE:    EnhancedKey already cleaned from system.
       * Running "/var/adm/sw/update_prep/NodeHostXpndEnbl.100".
NOTE:    NodeHostXpndEnbl already cleaned from system.
       * Loading Kernel Software
       * Executing "/usr/lbin/sysadm/system_prep"
NOTE:    Saving the current system file at "/stand/system" to
         "/stand/system.prev"
NOTE:    The template file has been extracted from "/stand/vmunix"
         It has been placed in "/stand/system" where it will be used
         to build a new kernel.
       * Installing fileset "NFS.NFS-KRN,r=B.11.31.10" (1 of 1142).
       * Installing fileset "LdapUxClient.LDAP-C-SDK,r=B.05.01" (2 of 1142).
       * Running "preinstall" script for fileset "CIFS-Server.CIFS-RUN".
NOTE:    Preserve /etc/opt/samba/smb.conf.
NOTE:    Preserve /etc/rc.config.d/samba.
       * Installing fileset "CIFS-Server.CIFS-RUN,r=A.02.04.03" (3 of 1142).
       * Running "postinstall" script for fileset "CIFS-Server.CIFS-RUN".
NOTE:    A new version of "/etc/opt/samba/smb.conf" has been installed
         on the system.
NOTE:    A new version of "/etc/rc.config.d/samba" has been installed
         on the system.
       * Installing fileset "CIFS-CFSM.CFSM-KRN,r=A.02.04.03" (4 of 1142).
       * Installing fileset "DNPars.DNPARS-KRN,r=B.11.31.0709" (5 of 1142).
       * Installing fileset "FC-FCD.FC-FCD-KRN,r=B.11.31.1103" (6 of 1142).
       * Installing fileset "PHKL_41088.CORE2-KRN,r=1.0" (7 of 1142).
       * Installing fileset "PHKL_41304.CORE2-KRN,r=1.0" (8 of 1142).
       * Installing fileset "PHKL_41525.CORE2-KRN,r=1.0" (9 of 1142).
       * Installing fileset "HP-APA-KRN.APA-KRN,r=B.11.31.50" (10 of 1142).
       * Installing fileset "IETHER-DRV.IETHER-RUN,r=B.11.31.1103" (11 of 1142).
       ...
       * Installing fileset "iCOD.ICOD-TCH-E-MSG,r=B.11.31.10.03.00.06" (1141 of 1142).
       * Installing fileset "iCOD.ICOD-TCH-U-MSG,r=B.11.31.10.03.00.06" (1142 of 1142).
NOTE:    More information may be found in the Software Manager logfile using the command "drd runcmd swm job log -v 000004".


=======  09/19/11 17:34:04 SAT  Operating Environment Update - Saving State (user=root)  (jobid=000004)


       * The command "/opt/swm/bin/swm oeupdate -s /cdrom" succeeded.
       * Stopping swagentd for drd runcmd
       * Stopping fsdaemon for drd runcmd
       * Cleaning Up After Command Execution On Inactive System Image


=======  09/19/11 17:34:32 SAT  END Executing Command On Inactive System Image succeeded. (user=root)  (jobid=corona)

Ya tenemos hecho el update en el disco clon, para terminar nos queda actualizar diferencias que hayan podido surgir en el disco original mientras se producía el update y activar y rebootear el equipo con el disco clon

<corona:/cdrom>drd sync

=======  09/19/11 17:57:36 SAT  BEGIN Synchronizing Images (user=root)  (jobid=corona)

       * Locating System Images
       * Identifying Inactive System Image for synchronization
       * Selected inactive system image "sysimage_001" on disk "/dev/disk/disk4".
       * Accessing Inactive System Image for synchronization
       * Identifying Files to Be Synchronized
       * The list of files that will be copied to the inactive image has been written to the file
         "/var/opt/drd/sync/files_to_be_copied_by_drd_sync"
       * Running command to synchronize files
       * Identifying system image to be unmounted
       * Unmounting Inactive System Image

=======  09/19/11 17:59:22 SAT  END Synchronizing Images succeeded. (user=root)  (jobid=corona)

<corona:/root>drd activate -x reboot=true

=======  09/19/11 18:03:35 SAT  BEGIN Activate Inactive System Image (user=root)  (jobid=corona)

       * Checking for Valid Inactive System Image
       * Reading Current System Information
       * Locating Inactive System Image
       * Determining Bootpath Status
       * Primary bootpath : /dev/disk/disk3 before activate.
       * Primary bootpath : /dev/disk/disk4 after activate.
       * Alternate bootpath : /dev/disk/disk3 before activate.
       * Alternate bootpath : /dev/disk/disk3 after activate.
       * Activating Inactive System Image
       * Rebooting System

SHUTDOWN PROGRAM
09/19/11 18:03:57 SAT

Broadcast Message from root (console) Mon Sep 19 18:03:57...
PLEASE LOG OFF NOW ! ! !
        System maintenance about to begin.
All processes will be terminated in 0 seconds.


Broadcast Message from root (console) Mon Sep 19 18:03:57...
SYSTEM BEING BROUGHT DOWN NOW ! ! !

...

Firmware Version  46.34

Duplex Console IO Dependent Code (IODC) revision 1
------------------------------------------------------------------------------
   (c) Copyright 1995-2004, Hewlett-Packard Company, All rights reserved
------------------------------------------------------------------------------

  Processor   Speed            State           CoProcessor State  Cache Size
  Number                                       State              Inst    Data
  ---------  --------   ---------------------  -----------------  ------------
      0     1000  MHz   Active                 Functional         67108864 67108864
      1     1000  MHz   Idle                   Functional         67108864 67108864
      2     1000  MHz   Idle                   Functional         67108864 67108864
      3     1000  MHz   Idle                   Functional         67108864 67108864

  Central Bus Speed (in MHz)  :        200  
  Available Memory            :   10485760  KB
  Good Memory Required        : Not initialized. Defaults to 32 MB. 

   Primary boot path:    0/1/1/0.1           
   Alternate boot path:  0/1/1/0.0           
   Console path:         0/0/1/1.0           
   Keyboard path:        0/0/4/0.0           


Processor is booting from the first available device.

To discontinue, press any key within 10 seconds.

Boot terminated.


---- Main Menu ---------------------------------------------------------------

     Command                           Description
     -------                           -----------
     BOot [PRI|ALT|<path>]             Boot from specified path
     PAth [PRI|ALT] [<path>]           Display or modify a path
     SEArch [DIsplay|IPL] [<path>]     Search for boot devices

     COnfiguration menu                Displays or sets boot values
     INformation menu                  Displays hardware information
     SERvice menu                      Displays service commands

     DIsplay                           Redisplay the current menu
     HElp [<menu>|<command>]           Display help for menu or command
     RESET                             Restart the system
----
Main Menu: Enter command or menu > [A[A[A[A[A[B[B[B[B[B

ERROR: Unknown command

Main Menu: Enter command or menu >
nteract with IPL (Y, N, or Cancel)?> n

Booting... 
Boot IO Dependent Code (IODC) revision 3


HARD Booted.

ISL Revision A.00.44  Mar 12, 2003 

ISL booting  hpux

Boot
: disk(0/1/1/0.1.0.0.0.0.0;0)/stand/vmunix
14348288 + 3534848 + 4914208 start 0x14d768

alloc_pdc_pages: Relocating PDC from 0xfffffff0f0c00000 to 0x3e900000.
DoCalllist done
Module ciss is put into ramfs:load time: driver_install, state: loaded
Module lvmp is put into ramfs:load time: driver_install, state: loaded
Module igelan is put into ramfs:load time: driver_install, state: loaded
Module iether is put into ramfs:load time: driver_install, state: loaded
Module fcd is put into ramfs:load time: driver_install, state: loaded
Module cfsm is put into ramfs:load time: driver_install, state: auto
Module cfsmdr is put into ramfs:load time: driver_install, state: auto
Module btlan is put into ramfs:load time: driver_install, state: loaded
Module procsm is put into ramfs:load time: driver_install, state: loaded
Module c8xx is put into ramfs:load time: driver_install, state: loaded
Module iomem is put into ramfs:load time: driver_install, state: auto
Module cdfs is put into ramfs:load time: driver_install, state: auto
Module cifs is put into ramfs:load time: driver_install, state: auto
Module td is put into ramfs:load time: driver_install, state: loaded
Module gelan is put into ramfs:load time: driver_install, state: loaded
Module fspd is put into ramfs:load time: driver_install, state: auto
Module fdd is put into ramfs:load time: driver_install, state: loaded
Module mpt is put into ramfs:load time: driver_install, state: loaded
Using /stand/ext_ioconfig 
gate64: sysvec_vaddr = 0xc0002000 for 2 pages

Memory Class Setup
-------------------------------------------------------------------------
Class     Physmem              Lockmem              Swapmem
-------------------------------------------------------------------------
System :  9788 MB              9788 MB              9788 MB             
Kernel :  9787 MB              9787 MB              9787 MB             
User   :  9345 MB              8285 MB              8317 MB             
-------------------------------------------------------------------------

ktracer is off until requested.
Installing Socket Protocol families AF_INET and AF_INET6
Kernel EVM initialized
Installed MemFS
sec_init(): kernel RPC authentication/security initialization.
secgss_init():  kernel RPCSEC_GSS security initialization.
rpc_init(): kernel RPC initialization.
rpcmod_install(): kernel RPC STREAMS module "rpcmod" installation. ...(driver_install)
NOTICE: nfs_client_pv3_install(): nfs3 File system was registered at index 11.
NOTICE: nfs_client_pv4_install(): nfs4 File system was registered at index 12.
NOTICE: cachefsc_install: cachefs File system was registered at index 14.
0/2/1/0: Fabric Name Server rejected GPN_FT query.
Reason code: unable to perform request;
Explanation: FC-4 Type not registered. 
This may indicate that the HBA port is not part of a zone. 
Please check zone configuration on your switch. 

0/6/1/0: Fabric Name Server rejected GPN_FT query.
Reason code: unable to perform request;
Explanation: FC-4 Type not registered. 
This may indicate that the HBA port is not part of a zone. 
Please check zone configuration on your switch. 

0/2/1/0: Fabric Name Server rejected GPN_FT query.
Reason code: unable to perform request;
Explanation: FC-4 Type not registered. 
This may indicate that the HBA port is not part of a zone. 
Please check zone configuration on your switch. 

0/6/1/0: Fabric Name Server rejected GPN_FT query.
Reason code: unable to perform request;
Explanation: FC-4 Type not registered. 
This may indicate that the HBA port is not part of a zone. 
Please check zone configuration on your switch. 


    System Console is on the Built-In Serial Interface
iether0: INITIALIZING HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core at hardware path 0/1/2/0
iether1: INITIALIZING HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core at hardware path 0/1/2/1
iether4: INITIALIZING HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter at hardware path 0/5/2/0
iether5: INITIALIZING HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter at hardware path 0/5/2/1
iether2: INITIALIZING HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter at hardware path 0/5/1/0
iether3: INITIALIZING HP A7012-60601 PCI/PCI-X 1000Base-T Dual-port Adapter at hardware path 0/5/1/1
AF_INET socket/streams output daemon running, pid 49
afinet_prelink: module installed
Starting the STREAMS daemons-phase 1 
LVM: Root VG activated
    Swap device table:  (start & size given in 512-byte blocks)
        entry 0 - major is 64, minor is 0x2; start = 0, size = 16777216
Checking root file system.
file system is clean - log replay is not required
Root check done.
NOTICE: return ramfs memory for BTL: [FREE] top 0x00000002c4300000, pages 3742

Create STCP device files
Starting the STREAMS daemons-phase 2 
     $Revision: vmunix:    B.11.31_LR FLAVOR=perf 
Memory Information:
    physical page size = 4096 bytes, logical page size = 4096 bytes
    Physical: 10483712 Kbytes, lockable: 7614312 Kbytes, available: 8685532 Kbytes

/sbin/ioinitrc:
/sbin/krs_sysinit:
       * The module 'rng' has been loaded.

insf: Installing special files for ipmi instance 0 address 16
insf: Installing special files for pseudo driver framebuf

/sbin/bcheckrc:
Checking for LVM volume groups and Activating (if any exist)
Volume group "/dev/vg00" is already active on this system.
Resynchronized volume group /dev/vg00
Checking hfs file systems
/sbin/fsclean: /dev/vg00/lvol1 (mounted) ok
HFS file systems are OK, not running fsck
Checking vxfs file systems
UX:vxfs fsck: INFO: V-3-20913: /dev/vg00/lvol3:sanity check: root file system OK (mounted read/write)
UX:vxfs fsck: INFO: V-3-20915: /dev/vg00/lvol4:sanity check: /dev/vg00/lvol4 OK
UX:vxfs fsck: INFO: V-3-20915: /dev/vg00/lvol5:sanity check: /dev/vg00/lvol5 OK
UX:vxfs fsck: INFO: V-3-20915: /dev/vg00/lvol6:sanity check: /dev/vg00/lvol6 OK
UX:vxfs fsck: INFO: V-3-20915: /dev/vg00/lvol7:sanity check: /dev/vg00/lvol7 OK
UX:vxfs fsck: INFO: V-3-20915: /dev/vg00/lvol8:sanity check: /dev/vg00/lvol8 OK

Cleaning /etc/ptmp...
(c)Copyright 1983-2006 Hewlett-Packard Development Company, L.P.
(c)Copyright 1979, 1980, 1983, 1985-1993 The Regents of the Univ. of California
(c)Copyright 1980, 1984, 1986 Novell, Inc.
(c)Copyright 1986-2000 Sun Microsystems, Inc.
(c)Copyright 1985, 1986, 1988 Massachusetts Institute of Technology
(c)Copyright 1989-1993  The Open Software Foundation, Inc.
(c)Copyright 1990 Motorola, Inc.
(c)Copyright 1990, 1991, 1992 Cornell University
(c)Copyright 1989-1991 The University of Maryland
(c)Copyright 1988 Carnegie Mellon University
(c)Copyright 1991-2006 Mentat Inc.
(c)Copyright 1996 Morning Star Technologies, Inc.
(c)Copyright 1996 Progressive Systems, Inc.

Confidential computer software. Valid license from HP required for
possession, use or copying.  Consistent with FAR 12.211 and 12.212,
Commercial Computer Software, Computer Software Documentation, and
Technical Data for Commercial Items are licensed to the U.S. Government
under vendor's standard commercial license.


/sbin/auto_parms: DHCP access is disabled (see /etc/auto_parms.log)

ovc instance NOT running

     HP-UX Start-up in progress
     __________________________

     Configure system crash dumps ................................ OK
     Removing old vxvm files ..................................... OK
     Mount file systems .......................................... OK
     Remounting Root File System ................................. OK
     Setting hostname ............................................ OK
     Start containment subsystem configuration ................... OK
     Set privilege group ......................................... N/A 
     Display date ................................................ N/A 
     Copy processor logs to /var/tombstones ...................... OK
     Save system crash dump if needed ............................ N/A 
     Start evp ................................................... OK
     Enable auxiliary swap space ................................. OK
     Start syncer daemon ......................................... OK
     Initializing livedump ....................................... N/A 
     Start Utmp Daemon : manages User Accounting Database ........ OK
     Configure Loopback interfaces (lo0) ......................... OK
     Reconfiguring setboot event subscription .................... OK
     Starting Event Management (EVM) (phase 1) ................... OK
     Start Essential Services monitoring daemon .................. OK
     Continuing install jobs, configuring filesets ............... OK <-- En este punto el sistema puede demorar varios minutos
     Configuring all unconfigured software filesets .............. OK

The system is ready.

GenericSysName [HP Release B.11.31] (see /etc/issue)
Console Login: 

En este momento podemos chequear la versión del release del OS

<corona:/root>swlist -l bundle |grep  HPUX11i
  HPUX11i-BOE           B.11.31.1103   HP-UX Base Operating Environment 

Llegado a este paso debemos testear el nuevo entorno y luego de esto deberemos decidir si lo conservamos o no. Esto se reduce a hacer un drd activate para bootear del disco original o bien hacer un drd clone nuevo contra el otro disco.