Patch Name: PHSS_27139 Patch Description: s700_800 11.11 Database update on remote vPar Creation Date: 02/06/02 Post Date: 02/06/17 Hardware Platforms - OS Releases: s700: 11.11 s800: 11.11 Products: VirtualPartition A.01.01.00; Filesets: VirtualPartition.VPAR-MON,fr=A.01.01.00,fa=HP-UX_B.11.11_64,v=HP VirtualPartition.VPAR-MON2,fr=A.01.01.00,fa=HP-UX_B.11.11_64,v=HP Automatic Reboot?: No Status: General Release Critical: No Category Tags: defect_repair general_release Path Name: /hp-ux_patches/s700_800/11.X/PHSS_27139 Symptoms: PHSS_27139: ( SR:8606244661 CR:JAGae11146 ) On a running vPars system, if a change is made to the live vPars database from one vPar, the change is not reflected to the local copies of the database on the other vPars. To reproduce the problem, use the vparmodify command to make a change to the live database from a vPar on a system with multiple vPars. Then check the time stamp of the database file (/stand/vpdb) on one of the other vPars. The database file should get sync'ed up within a short time (~5 seconds). This is not happening currently. Note that if you use the vparstatus command to view the database, the command itself will sync up the database. Defect Description: PHSS_27139: ( SR:8606244661 CR:JAGae11146 ) The vPars monitor is not correctly setting a flag which indicates that the vPars database has been changed and needs to be sync'ed up with the local copy (/stand/vpdb). Resolution: The vPars monitor internally maintains an operations bitmask for each configured vPar. One of the bits in this bitmask is for the database sync operation. The vPars daemon which runs on every running vPar periodically (~ every 5 seconds) polls this bit to determine if the database file needs to be sync'ed up. When a change is made to the live database from one vPar, this bit gets set for every other vPar. The defect happened because the bit was not getting set correctly. This has been rectified. SR: 8606244661 Patch Files: VirtualPartition.VPAR-MON,fr=A.01.01.00,fa=HP-UX_B.11.11_64, v=HP: /stand/vpmon VirtualPartition.VPAR-MON2,fr=A.01.01.00, fa=HP-UX_B.11.11_64,v=HP: /stand/vpmon what(1) Output: VirtualPartition.VPAR-MON,fr=A.01.01.00,fa=HP-UX_B.11.11_64, v=HP: /stand/vpmon: $Revision: vpmon: vw: -f selectors: CUP11.11_B L2002_0602_1 PHSS_27139 'CUP11.11_BL2002_060 2_1' Sun Jun 2 09:57:05 PDT 2002 $ $Revision: vpmon: vw: -f selectors: CUP11.11_B L2002_0602_1 PHSS_27139 'CUP11.11_BL2002_060 2_1' Sun Jun 2 09:57:05 PDT 2002 $ $Revision: libfs.a: vw: -f selectors: CUP11.11 _BL2002_0602_1 PHSS_27139 'CUP11.11_BL2002_0 602_1' Sun Jun 2 09:56:14 PDT 2002 $ $Revision: libinit.a: vw: -f selectors: CUP11. 11_BL2002_0602_1 PHSS_27139 'CUP11.11_BL2002 _0602_1' Sun Jun 2 09:56:04 PDT 2002 $ $Revision: libinit-pdk.a: vw: -f selectors: CU P11.11_BL2002_0602_1 PHSS_27139 'CUP11.11_BL 2002_0602_1' Sun Jun 2 09:57:02 PDT 2002 $ $Revision: libio.a: vw: -f selectors: CUP11.11 _BL2002_0602_1 PHSS_27139 'CUP11.11_BL2002_0 602_1' Sun Jun 2 09:55:52 PDT 2002 $ $Revision: libio-pdk.a: vw: -f selectors: CUP1 1.11_BL2002_0602_1 PHSS_27139 'CUP11.11_BL20 02_0602_1' Sun Jun 2 09:55:37 PDT 2002 $ $Revision: libldr-pdk.a: vw: -f selectors: CUP 11.11_BL2002_0602_1 PHSS_27139 'CUP11.11_BL2 002_0602_1' Sun Jun 2 09:56:52 PDT 2002 $ $Revision: libmem.a: vw: -f selectors: CUP11.1 1_BL2002_0602_1 PHSS_27139 'CUP11.11_BL2002_ 0602_1' Sun Jun 2 09:55:22 PDT 2002 $ $Revision: libmem-pdk.a: vw: -f selectors: CUP 11.11_BL2002_0602_1 PHSS_27139 'CUP11.11_BL2 002_0602_1' Sun Jun 2 09:55:14 PDT 2002 $ $Revision: libpdc-pdk.a: vw: -f selectors: CUP 11.11_BL2002_0602_1 PHSS_27139 'CUP11.11_BL2 002_0602_1' Sun Jun 2 09:56:39 PDT 2002 $ $Revision: libpdcem.a: vw: -f selectors: CUP11 .11_BL2002_0602_1 PHSS_27139 'CUP11.11_BL200 2_0602_1' Sun Jun 2 09:56:32 PDT 2002 $ $Revision: libsvc.a: vw: -f selectors: CUP11.1 1_BL2002_0602_1 PHSS_27139 'CUP11.11_BL2002_ 0602_1' Sun Jun 2 09:55:09 PDT 2002 $ $Revision: libsvc-pdk.a: vw: -f selectors: CUP 11.11_BL2002_0602_1 PHSS_27139 'CUP11.11_BL2 002_0602_1' Sun Jun 2 09:56:26 PDT 2002 $ $Revision: libutil-pdk.a: vw: -f selectors: CU P11.11_BL2002_0602_1 PHSS_27139 'CUP11.11_BL 2002_0602_1' Sun Jun 2 09:56:23 PDT 2002 $ vp_config.c $Date: 2002/05/22 10:38:44 $Revision: r1 1.11/5 PATCH_11.11 (PHSS_27139) VirtualPartition.VPAR-MON2,fr=A.01.01.00, fa=HP-UX_B.11.11_64,v=HP: /stand/vpmon: $Revision: vpmon: vw: -f selectors: CUP11.11_B L2002_0602_1 PHSS_27139 'CUP11.11_BL2002_060 2_1' Sun Jun 2 09:58:09 PDT 2002 $ $Revision: vpmon: vw: -f selectors: CUP11.11_B L2002_0602_1 PHSS_27139 'CUP11.11_BL2002_060 2_1' Sun Jun 2 09:58:09 PDT 2002 $ $Revision: libfs.a: vw: vpar_pib3_pub1 selecto rs: CUP11.11_BL2001_1101 Sat Nov 3 08:40:3 7 PST 2001 $ $Revision: libinit.a: vw: vpar_pib3_pub1 selec tors: CUP11.11_BL2001_1101 Sat Nov 3 08:40 :26 PST 2001 $ $Revision: libinit-pdk.a: vw: -f selectors: CU P11.11_BL2002_0602_1 PHSS_27139 'CUP11.11_BL 2002_0602_1' Sun Jun 2 09:58:04 PDT 2002 $ $Revision: libio.a: vw: vpar_pib3_pub1 selecto rs: CUP11.11_BL2001_1101 Sat Nov 3 08:40:1 3 PST 2001 $ $Revision: libio-pdk.a: vw: vpar_pib3_pub1 sel ectors: CUP11.11_BL2001_1101 Sat Nov 3 08: 39:56 PST 2001 $ $Revision: libldr-pdk.a: vw: -f selectors: CUP 11.11_BL2002_0602_1 PHSS_27139 'CUP11.11_BL2 002_0602_1' Sun Jun 2 09:57:57 PDT 2002 $ $Revision: libmem.a: vw: vpar_pib3_pub1 select ors: CUP11.11_BL2001_1101 Sat Nov 3 08:39: 39 PST 2001 $ $Revision: libmem-pdk.a: vw: vpar_pib3_pub1 se lectors: CUP11.11_BL2001_1101 Sat Nov 3 08 :39:31 PST 2001 $ $Revision: libpdc-pdk.a: vw: -f selectors: CUP 11.11_BL2002_0602_1 PHSS_27139 'CUP11.11_BL2 002_0602_1' Sun Jun 2 09:57:52 PDT 2002 $ $Revision: libpdcem.a: vw: -f selectors: CUP11 .11_BL2002_0602_1 PHSS_27139 'CUP11.11_BL200 2_0602_1' Sun Jun 2 09:57:49 PDT 2002 $ $Revision: libsvc.a: vw: vpar_pib3_pub1 select ors: CUP11.11_BL2001_1101 Sat Nov 3 08:39: 24 PST 2001 $ $Revision: libsvc-pdk.a: vw: -f selectors: CUP 11.11_BL2002_0602_1 PHSS_27139 'CUP11.11_BL2 002_0602_1' Sun Jun 2 09:57:47 PDT 2002 $ $Revision: libutil-pdk.a: vw: vpar_pib3_pub1 s electors: CUP11.11_BL2001_1101 Sat Nov 3 0 8:40:46 PST 2001 $ vp_config.c $Date: 2002/05/22 10:38:44 $Revision: r1 1.11/5 PATCH_11.11 (PHSS_27139) cksum(1) Output: VirtualPartition.VPAR-MON,fr=A.01.01.00,fa=HP-UX_B.11.11_64, v=HP: 2457993523 854792 /stand/vpmon VirtualPartition.VPAR-MON2,fr=A.01.01.00, fa=HP-UX_B.11.11_64,v=HP: 2070733358 854792 /stand/vpmon Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: 9000/800/L3000 9000/800/N4000, Other Dependencies: None Supersedes: None Equivalent Patches: None Patch Package Size: 1700 KBytes Installation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. ------------------------------------------------------------ 1. Back up your system before installing a patch. 2. Login as root. 3. Copy the patch to the /tmp directory. 4. Move to the /tmp directory and unshar the patch: cd /tmp sh PHSS_27139 5. Run swinstall to install the patch: swinstall -x autoreboot=true -x patch_match_target=true \ -s /tmp/PHSS_27139.depot By default swinstall will archive the original software in /var/adm/sw/save/PHSS_27139. If you do not wish to retain a copy of the original software, include the patch_save_files option in the swinstall command above: -x patch_save_files=false WARNING: If patch_save_files is false when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. For future reference, the contents of the PHSS_27139.text file is available in the product readme: swlist -l product -a readme -d @ /tmp/PHSS_27139.depot To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHSS_27139.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: Process for patching the vPars monitor ====================================== 1. Boot the system in standalone (ie, non-vpars) mode. 2. Install the new vPars patch using the swinstall command. This will install the new vPars monitor (/stand/vpmon), commands and daemons on your system. The system will not be automatically rebooted. 3. Reboot the system and launch the vPars monitor from the disk where the vPars patch was installed. For details on launching the vPars monitor, please refer to the vPars sysadmin guide. 4. Launch the vPars from the monitor. Note: if your vPars monitor is set to automatically boot the vPars, then the vPar OSes will be launched automatically. For details on configuring and running vPars, please refer to the vPars sysadmin guide. 5. Once a vPar is up and running, repeat step 2 to install the vPars patch on each individual vPar (Note: The vPar which owns the boot disk which was used to boot in standalone mode in step 1 has already been patched and hence may be excluded from this step.) No reboot is required. All vPars must be patched before the system is put back into production.