HPUX 11.31下更改设备名【转载】

       在HPUX(特别是HPUX 11.31,不能安装其它多路径软件)下安装ORACLE RAC时,建ASM磁盘组时有时会碰到两个节点上存储映射过来的磁盘盘符不一致,有时是物理路径一致,但聚合后路径不一致,有时甚至物理路径也不一致,此时就需将两个节点上的磁盘盘符修改为一致,上网找了很久,找到一篇HPUX网站上的一篇文档,将实施过程记录下来,以备后查:

1.确认LUN ID与磁盘的对应关系,确认两个节点磁盘的对应关系

首先找到存储映射到主机的磁盘的LUN ID,并将两台主机之间相同LUN ID的磁盘对应关系找到,因为HP 11.31使用的是HP自己的多路径软件,如果存储是HDS的话可以通过HDS提供的工具脚本来找到磁盘和LUN ID的对应关系:

HPUX下Lun对应关系查看方式如下:

请将附件的工具inqraid.hpux以二进制模式ftp上传到主机/tmp目录,执行以下命令

a>cd /tmp

b>chmod +x /tmp/inqraid.hpux

c>ioscan -fun | grep -e rdisk -e rdsk | ./inqraid.hpux -CLI -fx

d>ioscan -fun | grep -e rdisk -e rdsk | ./inqraid.hpux -CLI -fx -fg

 

 

-h可以看到更多选项。。。。。。

 

根据命令的输出结果可以核对出主机设备名与存储设备Lun的对应关系。

 

如果是EMC或者其它的需要找存储厂商了解,如果找不到办法就只有用最笨的办法,一块盘一块盘的映射来找磁盘和LUN ID的对应关系 

以下映射了5块磁盘,存储是EMC CX4-240,在两个节点上磁盘与LUN ID的对应关系如下:

LUNID                                            节点1磁盘名                                                        节点2磁盘名         

lun 36                                             /dev/rdisk/disk216                                              /dev/rdisk/disk191

lun 37                                             /dev/rdisk/disk217                                              /dev/rdisk/disk192

lun 38                                             /dev/rdisk/disk218                                              /dev/rdisk/disk193

lun 39                                             /dev/rdisk/disk219                                              /dev/rdisk/disk194

lun 40                                             /dev/rdisk/disk220                                              /dev/rdisk/disk195

 

查看两个节点上聚合后和聚合前磁盘对应关系

                   节点1                                                                                                   节点2

nodeA#ioscan -m dsf                                nodeB#ioscan -m dsf    

Persistent DSF           Legacy DSF(s)        Persistent DSF      Legacy DSF(s)

===================================      ===================================  

/dev/rdisk/disk216  /dev/rdsk/c36t0d0              /dev/rdisk/disk191  /dev/rdsk/c37t0d0

                    /dev/rdsk/c35t0d0                        /dev/rdsk/c36t0d0

                    /dev/rdsk/c38t0d0                        /dev/rdsk/c38t0d0

                    /dev/rdsk/c37t0d0                        /dev/rdsk/c39t0d0

/dev/rdisk/disk217  /dev/rdsk/c36t0d1              /dev/rdisk/disk192  /dev/rdsk/c37t0d1

                    /dev/rdsk/c35t0d1                        /dev/rdsk/c36t0d1

                    /dev/rdsk/c38t0d1                        /dev/rdsk/c38t0d1

                    /dev/rdsk/c37t0d1                        /dev/rdsk/c39t0d1

/dev/rdisk/disk218  /dev/rdsk/c36t0d2          /dev/rdisk/disk193  /dev/rdsk/c37t0d2

                    /dev/rdsk/c35t0d2                        /dev/rdsk/c36t0d2

                    /dev/rdsk/c38t0d2                        /dev/rdsk/c38t0d2

                    /dev/rdsk/c37t0d2                        /dev/rdsk/c39t0d2

/dev/rdisk/disk219  /dev/rdsk/c36t0d3               /dev/rdisk/disk194  /dev/rdsk/c37t0d3

                    /dev/rdsk/c35t0d3                        /dev/rdsk/c36t0d3

                    /dev/rdsk/c38t0d3                        /dev/rdsk/c38t0d3

                    /dev/rdsk/c37t0d3                        /dev/rdsk/c39t0d3

/dev/rdisk/disk220  /dev/rdsk/c35t0d4               /dev/rdisk/disk195  /dev/rdsk/c37t0d4

                    /dev/rdsk/c36t0d4                        /dev/rdsk/c36t0d4

                    /dev/rdsk/c38t0d4                        /dev/rdsk/c38t0d4

                    /dev/rdsk/c37t0d4                        /dev/rdsk/c39t0d4

节点1                                                     节点2

 /dev/rdisk/disk216                       /dev/rdisk/disk191

 /dev/rdisk/disk217                       /dev/rdisk/disk192

 /dev/rdisk/disk218                       /dev/rdisk/disk193

 /dev/rdisk/disk219                       /dev/rdisk/disk194

 /dev/rdisk/disk220                       /dev/rdisk/disk195

 

根据以上情况决定以第一个节点上的盘符为准,将第二个节点上的盘符进行更改:

2.根据磁盘路径信息生成IO初始化的infile文件

查找磁盘聚合后路径:

nodeB#ioscan -fnNkCdisk                                                    

Class     I  H/W Path  Driver         S/W State   H/W Type     Description     

===========================================================================    

disk  191  64000/0xfa00/0x1e  esdisk         CLAIMED     DEVICE  DGC CX4-240WDR5

                    /dev/disk/disk191             /dev/rdisk/disk191                       

disk  192  64000/0xfa00/0x1f  esdisk         CLAIMED     DEVICE  DGC CX4-240WDR5

                    /dev/disk/disk192            /dev/rdisk/disk192                       

disk  193  64000/0xfa00/0x20  esdisk         CLAIMED     DEVICE  DGC CX4-240WDR5

                    /dev/disk/disk193            /dev/rdisk/disk193                        

disk  194  64000/0xfa00/0x21  esdisk         CLAIMED     DEVICE  DGC CX4-240WDR5

                    /dev/disk/disk194            /dev/rdisk/disk194                       

disk  195  64000/0xfa00/0x22  esdisk         CLAIMED     DEVICE  DGC CX4-240WDR5

                      /dev/disk/disk195         /dev/rdisk/disk195                                            

.....                                                                                                 

查找磁盘聚合前路径:                                                                                                 

nodeB#ioscan -fnkCdisk                                                        

Class     I  H/W Path      Driver         S/W State   H/W Type     Description    

============================================================================      

                                                                                  

disk  28  0/3/1/0.1.21.0.0.0.0  sdisk           CLAIMED     DEVICE  DGC CX4-240WDR5

                       /dev/dsk/c37t0d0    /dev/rdsk/c37t0d0                        

disk 149  0/3/1/0.1.21.0.0.0.1  sdisk           CLAIMED     DEVICE  DGC CX4-240WDR5

                       /dev/dsk/c37t0d1  /dev/rdsk/c37t0d1                        

disk 150  0/3/1/0.1.21.0.0.0.2  sdisk           CLAIMED     DEVICE  DGC CX4-240WDR5

                       /dev/dsk/c37t0d2  /dev/rdsk/c37t0d2                        

disk 151  0/3/1/0.1.21.0.0.0.3  sdisk           CLAIMED     DEVICE  DGC CX4-240WDR5

                       /dev/dsk/c37t0d3  /dev/rdsk/c37t0d3                        

disk 152  0/3/1/0.1.21.0.0.0.4  sdisk           CLAIMED     DEVICE  DGC CX4-240WDR5

                       /dev/dsk/c37t0d4  /dev/rdsk/c37t0d4                        

disk 153  0/3/1/0.1.21.0.0.0.5  sdisk           CLAIMED     DEVICE  DGC CX4-240WDR5

                       /dev/dsk/c37t0d5  /dev/rdsk/c37t0d5                        

disk 154  0/3/1/0.1.21.0.0.0.6  sdisk           CLAIMED     DEVICE  DGC CX4-240WDR5

                       /dev/dsk/c37t0d6  /dev/rdsk/c37t0d6                        

disk 155  0/3/1/0.1.21.0.0.0.7  sdisk           CLAIMED     DEVICE  DGC CX4-240WDR5

                       /dev/dsk/c37t0d7  /dev/rdsk/c37t0d7                        

disk 156  0/3/1/0.1.21.0.0.1.0  sdisk           CLAIMED     DEVICE  DGC CX4-240WDR5

                       /dev/dsk/c37t1d0  /dev/rdsk/c37t1d0                        

disk 157  0/3/1/0.1.21.0.0.1.1  sdisk           CLAIMED     DEVICE  DGC CX4-240WDR5

                       /dev/dsk/c37t1d1  /dev/rdsk/c37t1d1                        

disk 158  0/3/1/0.1.21.0.0.1.2  sdisk           CLAIMED     DEVICE  DGC CX4-240WDR5

                       /dev/dsk/c37t1d2  /dev/rdsk/c37t1d2                        

....                                                                               

disk 174  0/7/1/0.1.23.0.0.1.4  sdisk           CLAIMED     DEVICE  DGC CX4-240WDR5

                       /dev/dsk/c38t1d4  /dev/rdsk/c38t1d4                        

disk 175  0/7/1/0.1.23.0.0.1.5  sdisk           CLAIMED     DEVICE  DGC CX4-240WDR5

                       /dev/dsk/c38t1d5  /dev/rdsk/c38t1d5                        

disk 176  0/7/1/0.1.23.0.0.1.6  sdisk           CLAIMED     DEVICE  DGC CX4-240WDR5

                       /dev/dsk/c38t1d6  /dev/rdsk/c38t1d6

生成infile文件

# cd /tmp

 # ioscan -kNf | grep ^disk | awk '{printf "%s %s %s\n",$3,$1,$2}' > infile

 # ioscan -kf | grep ^disk | awk '{printf "%s %s %s\n",$3,$1,$2}'  >> infile

 

修改生成的infile文件,以64000/0xfa00/0x1e开始的行,除了需要修改设备名的,其它的都删除掉:

 # vi infile                                         

 nodeBtmp/hpdisk#vi infile                       

"infile" 109 lines, 3144 characters                  

64000/0xfa00/0x1e disk 191

64000/0xfa00/0x1f disk 192

64000/0xfa00/0x20 disk 193

64000/0xfa00/0x21 disk 194

64000/0xfa00/0x22 disk 195                           

0/0/2/1.0.16 disk 3                           

0/3/1/0.1.21.0.0.0.0 disk 28                         

……                       

0/3/1/0.1.22.0.0.0.1 disk 118

0/3/1/0.1.22.0.0.0.2 disk 119

0/3/1/0.1.22.0.0.0.3 disk 120

0/3/1/0.1.22.0.0.0.4 disk 121

                        

将阴影部分修改成以下内容:

64000/0xfa00/0x1e disk 216

64000/0xfa00/0x1f disk 217

64000/0xfa00/0x20 disk 218

64000/0xfa00/0x21 disk 219

64000/0xfa00/0x22 disk 220

0/0/2/1.0.16 disk 3

0/3/1/0.1.21.0.0.0.0 disk 28

……

0/3/1/0.1.22.0.0.0.1 disk 118

0/3/1/0.1.22.0.0.0.2 disk 119

0/3/1/0.1.22.0.0.0.3 disk 120

0/3/1/0.1.22.0.0.0.4 disk 121

3.初始化修改后设备文件

执行生成的文件:

nodeB #ioinit -f ./infile

ioinit: Input is identical to kernel, line ignored

Input line 2:  0/0/2/1.0.16 disk 3

……

ioinit: Input is identical to kernel, line ignored   

Input line 83:  0/7/1/0.1.23.0.0.1.6 disk 176

  4.删除之前旧的设备

nodeB#rmsf /dev/disk/disk191        /dev/rdisk/disk191

nodeB#rmsf /dev/disk/disk192        /dev/rdisk/disk192

nodeB#rmsf /dev/disk/disk193        /dev/rdisk/disk193

nodeB#rmsf /dev/disk/disk194        /dev/rdisk/disk194

nodeB#rmsf /dev/disk/disk195        /dev/rdisk/disk195

 

5.验证查询                  

 

nodeBtmp#ioscan -m dsf

Persistent DSF           Legacy DSF(s)

========================================

/dev/rdisk/disk1            /dev/rdsk/c34t0d0

                         /dev/rdsk/c35t0d0

/dev/rdisk/disk41           /dev/rdsk/c34t0d2

                         /dev/rdsk/c35t0d2

.....

/dev/rdisk/disk216          /dev/rdsk/c37t0d0

                         /dev/rdsk/c36t0d0

                         /dev/rdsk/c38t0d0

                         /dev/rdsk/c39t0d0

/dev/rdisk/disk217          /dev/rdsk/c37t0d2

                         /dev/rdsk/c36t0d2

                         /dev/rdsk/c38t0d2

                         /dev/rdsk/c39t0d2

/dev/rdisk/disk218          /dev/rdsk/c37t0d4

                         /dev/rdsk/c36t0d4

                         /dev/rdsk/c38t0d4

                         /dev/rdsk/c39t0d4

/dev/rdisk/disk219          /dev/rdsk/c37t0d6

                         /dev/rdsk/c36t0d6

                         /dev/rdsk/c38t0d6

                         /dev/rdsk/c39t0d6

/dev/rdisk/disk220          /dev/rdsk/c37t1d0

                         /dev/rdsk/c36t1d0

                         /dev/rdsk/c38t1d0

                         /dev/rdsk/c39t1d0


又遇到问题可看我另外一篇转载文章

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
QEMU(Quick Emulator)是一个开源的系统模拟器和虚拟机监控程序,支持多种操作系统,包括HP-UX。要在Linux或Unix-like系统上安装QEMU并配置它来运行HP-UX,你可以按照以下步骤操作: 1. **下载和安装QEMU**: - 首先,你需要从QEMU的官方网站 <https://www.qemu.org/download/> 下载适用于你系统的QEMU源代码包。选择适用于你的Linux发行版的版本,通常会有一个预编译的二进制包,如果需要从源码编译,请下载源代码。 2. **构建和安装**: - 解压下载的源代码包,然后进入目录,执行 `./configure`,之后用 `make` 命令构建QEMU。 - 安装QEMU,使用 `sudo make install` 或者根据构建选项中的提示。 3. **获取HP-UX镜像**: - 找到合法的HP-UX ISO镜像文件,可以从HP的官方网站或旧版本软件仓库获取。如果你没有权限访问这些资源,可能需要寻找公共可用的镜像。 4. **创建HP-UX模板**: - 使用QEMU的`qemu-img create`命令创建一个新的硬盘映射文件,如 `qemu-img create -f raw hpux_disk.raw size`,其中`size`是磁盘大小。 5. **加载ISO并启动虚拟机**: - 在QEMU的命令行中,使用`qemu-system-hppa -hda hpux_disk.raw -cdrom path/to/hpux_iso.iso`命令启动虚拟机,替换`path/to/hpux_iso.iso`为你的HP-UX镜像路径。 6. **配置网络、内存和其他设置**: - 可能需要额外配置网络接口和分配适当的内存给虚拟机,这可以通过修QEMU的启动参数完成。 7. **启动和管理**: - 启动后,你将看到一个控制台,可以尝试登录并开始使用HP-UX系统。对于更复杂的操作,可能还需要安装必要的驱动和工具,并适应QEMU提供的模拟环境。

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值