<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: hpmodify -ERROR in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/hpmodify-error/m-p/4735325#M524072</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;You need to stop and start guest after adding any new device. Execute following commands:&lt;BR /&gt;# hpvmstop -p 1&lt;BR /&gt;# hpvmstart -p 1&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Bhadresh</description>
    <pubDate>Fri, 07 Jan 2011 12:42:52 GMT</pubDate>
    <dc:creator>Bhadresh</dc:creator>
    <dc:date>2011-01-07T12:42:52Z</dc:date>
    <item>
      <title>hpmodify -ERROR</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hpmodify-error/m-p/4735324#M524071</link>
      <description>Friends,&lt;BR /&gt;&lt;BR /&gt; Am allocating 100g lun to my guest but am facing below error.&lt;BR /&gt;Kindly advice how to solve the issue..&lt;BR /&gt;&lt;BR /&gt;# hpvmstatus&lt;BR /&gt;[Virtual Machines]&lt;BR /&gt;Virtual Machine Name VM #  OS Type State     #VCPUs #Devs #Nets Memory  Runsysid&lt;BR /&gt;==================== ===== ======= ========= ====== ===== ===== ======= ========&lt;BR /&gt;vm01                     1 HPUX    On (OS)        4    12     1   11 GB        0&lt;BR /&gt;vm02                     2 HPUX    Off            2    12     1    6 GB        0&lt;BR /&gt;#&lt;BR /&gt;# hpvmmodify -p1 -a disk:avio_stor::disk:/dev/rdisk/disk113&lt;BR /&gt;hpvmmodify: Unable to dynamically create device disk:avio_stor:0,4,0:disk:/dev/rdisk/disk113 - Protocol error.&lt;BR /&gt;hpvmmodify: Guest needs to be restarted (using hpvmstop followed by hpvmstart) for all changes to take effect.&lt;BR /&gt;hpvmmodify: WARNING (host): Device /dev/rdsk/c3t0d0 took 14 seconds to open.&lt;BR /&gt;&lt;BR /&gt;1)Its required reboot for alocating LUN.&lt;BR /&gt;2)Purpose of creating new file system &lt;BR /&gt;3)How to add the storage to excisting F/S.&lt;BR /&gt;&lt;BR /&gt;Thanks in Advance.....</description>
      <pubDate>Fri, 07 Jan 2011 10:45:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hpmodify-error/m-p/4735324#M524071</guid>
      <dc:creator>Musa123</dc:creator>
      <dc:date>2011-01-07T10:45:52Z</dc:date>
    </item>
    <item>
      <title>Re: hpmodify -ERROR</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hpmodify-error/m-p/4735325#M524072</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;You need to stop and start guest after adding any new device. Execute following commands:&lt;BR /&gt;# hpvmstop -p 1&lt;BR /&gt;# hpvmstart -p 1&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Bhadresh</description>
      <pubDate>Fri, 07 Jan 2011 12:42:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hpmodify-error/m-p/4735325#M524072</guid>
      <dc:creator>Bhadresh</dc:creator>
      <dc:date>2011-01-07T12:42:52Z</dc:date>
    </item>
    <item>
      <title>Re: hpmodify -ERROR</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hpmodify-error/m-p/4735326#M524073</link>
      <description>&lt;P&gt;Hello,&lt;BR /&gt;You may refer this forum&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h30499.www3.hp.com/t5/Virtualization/Integrity-Virtual-Machines-v4-0-unable-to-dynamically-add-disk/m-p/5132322#M3575" target="_blank"&gt;http://h30499.www3.hp.com/t5/Virtualization/Integrity-Virtual-Machines-v4-0-unable-to-dynamically-add-disk/m-p/5132322#M3575&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;2)Purpose of creating new file system &lt;BR /&gt;&lt;BR /&gt;As per your requirement in your environment&lt;BR /&gt;&lt;BR /&gt;3)How to add the storage to excisting F/S&lt;BR /&gt;&lt;BR /&gt;1) Present a LUN ( or use existing free LUN ) and find out it's details on your HPVM guest server&lt;BR /&gt;# ioscan -fnkCdisk&lt;BR /&gt;# ioscan em dsf&lt;BR /&gt;&lt;BR /&gt;o/p looks some thing like below format&lt;BR /&gt;&lt;BR /&gt;/dev/rdisk/disk533 /dev/rdsk/c17t0d7&lt;BR /&gt;/dev/rdsk/c21t0d7&lt;BR /&gt;/dev/rdsk/c19t0d7&lt;BR /&gt;/dev/rdsk/c23t0d7&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;disk 533 64000/0xfa00/0xd4 esdisk CLAIMED DEVICE online HITACHI DF600F&lt;BR /&gt;0/0/4/0/0/0/0.0x50060e8000c3f1b2.0x4007000000000000&lt;BR /&gt;0/0/4/0/0/0/1.0x50060e8000c3f1b4.0x4007000000000000&lt;BR /&gt;0/0/14/0/0/0/0.0x50060e8000c3f1b2.0x4007000000000000&lt;BR /&gt;0/0/14/0/0/0/1.0x50060e8000c3f1b4.0x4007000000000000&lt;BR /&gt;/dev/disk/disk533 /dev/rdisk/disk533 /dev/rdisk/disk_name &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Lun H/W Path Lunpath H/W Path Legacy H/W Path&lt;BR /&gt;====================================================================&lt;BR /&gt;64000/0xfa00/0xd4&lt;BR /&gt;0/0/4/0/0/0/0.0x50060e8000c3f1b2.0x4007000000000000 0/0/4/0/0/0/0.6.25.0.0.0.7&lt;BR /&gt;0/0/4/0/0/0/1.0x50060e8000c3f1b4.0x4007000000000000 0/0/4/0/0/0/1.1.28.0.0.0.7&lt;BR /&gt;0/0/14/0/0/0/0.0x50060e8000c3f1b2.0x4007000000000000 0/0/14/0/0/0/0.6.25.0.0.0.7&lt;BR /&gt;0/0/14/0/0/0/1.0x50060e8000c3f1b4.0x4007000000000000 0/0/14/0/0/0/1.1.28.0.0.0.7&lt;BR /&gt;&lt;BR /&gt;2) execute follwoing commands on your sysstem using new lun details&lt;BR /&gt;&lt;BR /&gt;# scsimgr get_info -H 64000/0xfa00/0xd4&lt;BR /&gt;&lt;BR /&gt;# scsimgr save_attr -a load_bal_policy=preferred_path -H 64000/0xfa00/0xd4&lt;BR /&gt;&lt;BR /&gt;# scsimgr save_attr -a preferred_path=0/0/14/0/0/0/0.0x50060e8000c3f1b2.0x4007000000000000 -H 64000/0xfa00/0xd4&lt;BR /&gt;&lt;BR /&gt;Check&lt;BR /&gt;# scsimgr get_info -H 64000/0xfa00/0xd4&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;3. Check the size of disk&lt;BR /&gt;&lt;BR /&gt;for e.g&lt;BR /&gt;&lt;BR /&gt;# diskinfo /dev/rdisk/disk533&lt;BR /&gt;SCSI describe of /dev/rdisk/disk533:&lt;BR /&gt;vendor: HITACHI&lt;BR /&gt;product id: DF600F&lt;BR /&gt;type: direct access&lt;BR /&gt;size: 10486784 Kbytes&lt;BR /&gt;bytes per sector: 512&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;4. Map the device file for easy identification of data LUN of your HPVM host, it is better and easy to identyfy respective HPVMs data luns&lt;BR /&gt;&lt;BR /&gt;# ll /dev/rdisk/disk533&lt;BR /&gt;crw-r----- 1 bin sys 23 0x0000d4 Nov 25 16:40 /dev/rdisk/disk533&lt;BR /&gt;&lt;BR /&gt;# mknod /dev/rdisk/HPVM_shortname_dataNN c 23 0x0000d4 ( NN- data lun number, for e.g host=marvin &amp;amp; datalun 2 =&amp;gt; marvin_data2)&lt;BR /&gt;# ioscan -m lun |grep disk533&lt;BR /&gt;/dev/disk/disk533 /dev/rdisk/disk533 /dev/rdisk/HPVM_shortname_dataNN &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;5. Add the disk to HPVM&lt;BR /&gt;&lt;BR /&gt;HPVMguest # hpvmmodify -P HPVM_name -a disk:avio_stor::disk:/dev/rdisk/disk533 ( HPVMgues=your guest server, HPVM= your HPVM host)&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;====================&lt;BR /&gt;Logon to your HPVM &lt;BR /&gt;====================&lt;BR /&gt;&lt;BR /&gt;6. Login to HPVM_name and run ioscan again and identify the new disk&lt;BR /&gt;&lt;BR /&gt;# ioscan -fnC disk&lt;BR /&gt;Class I H/W Path Driver S/W State H/W Type Description&lt;BR /&gt;=====================================================================&lt;BR /&gt;disk 1 0/0/0/0.0.0 sdisk CLAIMED DEVICE HP Virtual Disk&lt;BR /&gt;/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0&lt;BR /&gt;disk 4 0/0/0/0.1.0 sdisk CLAIMED DEVICE HP Virtual Disk&lt;BR /&gt;/dev/dsk/c0t1d0 /dev/rdsk/c0t1d0&lt;BR /&gt;.............&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;6. Take a backup of existing LVM config:&lt;BR /&gt;&lt;BR /&gt;# bdf &lt;BR /&gt;Filesystem kbytes used avail %used Mounted on&lt;BR /&gt;............&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;7) backup configuration files&lt;BR /&gt;&lt;BR /&gt;#cp -p /etc/lvmtab /etc/lvmtab.old_date&lt;BR /&gt;&lt;BR /&gt;# vgexport -pvs -m /etc/lvmconf/vg_name.map.old_date /dev/vg_name&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;8. Create the LVM sturcture on the new disk and add it to the vg on HPVM &lt;BR /&gt;&lt;BR /&gt;# pvcreate /dev/rdisk/disk17&lt;BR /&gt;&lt;BR /&gt;# vgextend /dev/vg_name /dev/disk/disk17&lt;BR /&gt;&lt;BR /&gt;9 ) Extend the filesystem size as required. I assume you have online jfs&lt;BR /&gt;&lt;BR /&gt;# lvextend -l 478 /dev/vg_name/lvol_number&lt;BR /&gt;&lt;BR /&gt;# fsadm -F vxfs -b size M mount point&lt;BR /&gt;&lt;BR /&gt;# bdf mount point&lt;BR /&gt;Filesystem kbytes used avail %used Mounted on&lt;BR /&gt;..........&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Note: I assume that you are extending existing VG on HPVM or else you may need to follow steps to create new VG as well.&lt;BR /&gt;&lt;BR /&gt;I have atatched these steps for your reference&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;&lt;BR /&gt;good luck&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;INH&lt;/P&gt;</description>
      <pubDate>Thu, 10 Nov 2011 21:49:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hpmodify-error/m-p/4735326#M524073</guid>
      <dc:creator>INH</dc:creator>
      <dc:date>2011-11-10T21:49:13Z</dc:date>
    </item>
  </channel>
</rss>

