各位高人还在线吗
我有2台450加1台a1000作ha,装好raid manager,单独开每一台机器都能够,假如先开1,后开2,2启动是提示:got scsi bus reset,然后1的raid manager中status 就变为dead.为什么

rabbit7505 回复于:2002-06-28 18:30:47
这是常见HA问题,由于A1000的两个SCSI接口同时连接2台服务器,所以2台服务器的HBA和A1000的SCSI控制器就在同一个SCSI通道上,缺省状态下,每个主机HBA的SCSI ID号都为7,1个链路上同时存在2个ID为7的SCSI控制器,就产生了冲突,所以当2台服务器同时开启的时候,就出现您所说的错误。
解决方法是将一台主机的SCSI ID改为6(其实只要不是7就能够),修改方法能够参照SUN公司网站docs.sun.com上有关Sun Cluster的文档修改。

daisyqi 回复于:2002-06-28 20:53:45
a1000有4个硬盘,装好raid manager后,自动生成了一个10M raid0的LUN.创建新lun时,不能选其他raid level,是否要先更改这个group的raid level.另外,创建lun时不能定义大小,只能选建几个lun.

rabbit7505 回复于:2002-06-28 21:06:03
对于A1000中初始的RAID配置,大能够删掉,即删除原始的Disk Group,因为1个硬盘只能属于1个DG,您的问题可能跟此有关。在创建新的DG,把您的4块硬盘全部加入进去,再创建LUN,配置RAID类型。
A1000的Raid Manager和Volume Manager的原理不同,不能在创建LUN时指定大小,而是依据磁盘的大小和RAID类型自动完成。

daisyqi 回复于:2002-06-28 22:23:45
假如我创建了几个raid 5 lun,能够将一个改为raid1吗?

rabbit7505 回复于:2002-06-29 10:43:53
没问题啊,只但是您在这个LUN上的数据就没有了。

daisyqi 回复于:2002-06-29 14:51:31
将一台主机的SCSI ID改为6,是否Setting scsi-initiator-id,
ok setenv scsi-initiator-id 6
但文档后面更有一段
ok nvedit
0: dev scsi
1: 7 encode-int " scsi-initiator-id" property
2: device-end [Control-c]
是什么意思,为什么要设


南非蜘蛛 回复于:2002-06-29 15:16:47
scsi ID6 好象是专门给磁带机,或其他一些特别设备用的,我忘了,不好意思,ID7是给scsi的控制器用.

daisyqi 回复于:2002-06-29 15:24:22
这是我在网上找的文档,不知是否适用于我的情况

Since the factory default scsi-initiator-id for all adapter cards on the system is 7, it is suggested that the scsi-initiator-id for all the SunSwift cards on one host be 7 and those on the other host be set to 6. Therefore, the procedure outlined below must be done on only one of the cluster hosts.
The easiest way to accomplish this configuration is to set the Initiator ID for one of the cluster hosts to 6 and then to change the scsi-initiator-id for the on-board SCSI controller to 7. This configuration is set from the OpenBoot(TM) PROM (OBP) Monitor.
Table 3-3 SCSI Initiator ID Settings Controller Instance Cluster Node A Initiator ID Cluster Node B Initiator ID

0 (internal) 7 7
1 7 6
2 7 6

Setting Up the nvramrc Script in the OBP Monitor The OpenBoot PROM Monitor builds its own device tree based on the devices attached to the system when the boot sequence is invoked. The OBP Monitor has a set of default aliases for the commonly occurring devices in the system.
A nvramrc script contains a series of OpenBoot PROM commands that are executed during the boot sequence. It is assumed that this file is nonexistent and will be created. The steps to create or edit a nvramrc script are similar. You need to be familiar with nvramrc Editor Keystroke Commands. Table 3-4 lists the most useful commands.
Enter the OBP Monitor by shutting down the system:
# shutdown -g0 -y -i0

Set the NVRAM parameters to the default values.

ok set-defaults
Setting NVRAM parameters to default values.
ok

Set the scsi-initiator-id to 6.

ok setenv scsi-initiator-id 6
scsi-initiator-id = 6
ok

Enter the nvedit command to create and store an nvramrc script.
The line numbers (0:, 1:, and so on) are printed by the OpenBoot PROM Monitor. See Table 3-4 for the nvramrc editor keystroke commands.

ok nvedit
0: dev scsi
1: 7 encode-int " scsi-initiator-id" property
2: device-end [Control-c]
ok
--------------------------------------------------------------------------------
Caution - Insert exactly one space after the double quote and before scsi-initiator-id.

--------------------------------------------------------------------------------
Store or discard the changes.
The changes you make using the nvedit command are done on a temporary copy of the nvramrc script. You can continue to edit this copy without risk. Once you are through editing, save the modifications. If you are not sure about the changes, discard them. If, for any reason, you do not want to save the contents of the nvedit buffer, type:

ok nvquit
ok

To store the changes, type:

文章整理:西部数码--专业提供域名注册虚拟主机服务
http://www.west263.com
以上信息与文章正文是不可分割的一部分,如果您要转载本文章,请保留以上信息,谢谢!