免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
12下一页
最近访问板块 发新帖
查看: 6179 | 回复: 17
打印 上一主题 下一主题

[Veritas NBU] 无法识别SUN L25带库?solaris9(E3000+emulex9002卡)+NBU5.1 [复制链接]

论坛徽章:
0
跳转到指定楼层
1 [收藏(0)] [报告]
发表于 2005-01-15 12:14 |只看该作者 |倒序浏览
sgsan时,可以看到Meta 400
                             HP tape(???)Ultra Scsi 2的信息
        ???是不是问题的所在?如何解决?

但是,用netbackup图形界面配置storage时,显示 Drive0 Dirve1(not use)不可用,机械手也可以识别的到,solaris打了113277-26补丁和最新的EIS补丁;光纤卡用的不是sun的,而是Emulex的,可以识别到设备,但是好像没有驱动好。是不是st.conf,sg.conf文件里没有L25带库的驱动信息,以前用别的厂家的带库好像没有这个问题,安装完NBU,直接就可以配置设备了。

另外/usr/openv/volmgr/bin/sg.build all -mt 15 -ml 1 是不是必须要做,我只有两个驱动器和一个机械手

谢谢!

论坛徽章:
0
2 [报告]
发表于 2005-01-15 12:19 |只看该作者

无法识别SUN L25带库?solaris9(E3000+emulex9002卡)+NBU5.1

参考下这个
http://sunsolve.sun.com/search/printfriendly.do?assetkey=1-9-72544-1

论坛徽章:
0
3 [报告]
发表于 2005-01-15 12:26 |只看该作者

无法识别SUN L25带库?solaris9(E3000+emulex9002卡)+NBU5.1

Solaris 7 OS - 107460-xx
Solaris 8 OS - 108725-xx
Solaris 9 OS - 113277-xx

打完PATCH后,重启机器吗?
mt status 和sgscan的信息贴出来看看

论坛徽章:
0
4 [报告]
发表于 2005-01-15 12:37 |只看该作者

无法识别SUN L25带库?solaris9(E3000+emulex9002卡)+NBU5.1

longe你好,我sunslove的帐号好像不能用,要什么Please enter your valid Sun Support Contract Number here
能不能把内容贴给我,谢谢

论坛徽章:
0
5 [报告]
发表于 2005-01-15 12:44 |只看该作者

无法识别SUN L25带库?solaris9(E3000+emulex9002卡)+NBU5.1

打完patch113277-26后,重启了。
L25带库是不是有些细节的注意事项?
NBU5.1在使用L25带库的时候有没有特殊的配置?

论坛徽章:
0
6 [报告]
发表于 2005-01-15 12:51 |只看该作者

无法识别SUN L25带库?solaris9(E3000+emulex9002卡)+NBU5.1

Description: Top

FC420 is a L25/100 add-on PCI card peripheral from ATTO that installs
inside the L25/100 tape libraries.  The FC420 SCSI to Fibre-
Channel bridge is used to allow SCSI tape devices in the L25/100
libraries to join a SAN.

Below procedures detail how to configure Netbackup and Enterprise Backup
Software environments to detect tape drives behind a FC420 bridge.

In this example, the L25/100 is configured with two tape drives.   
From the L25/100's front panel, target IDs are set as follows:
    Robot   = ID-0
    Drive-1 = ID-1
    Drive-2 = ID-2Document Body: Top

Ensure the L25/100 is connected, powered and has passed its internal
diagnostics from the panel.

Check that serialization is enabled from the front panel of the L25/L100
Library.  If it is disabled, then enable it by:

1) On the main screen, press Menu. The GUI displays the Menu screen.
2) Press Config. The GUI displays the Configuration screen.
3) Press the Up or Down buttons until Serialization is highlighted.
4) Press Select.
5) Use the Up or Down buttons to select Enabled.
6) Press Select.
7) Press Main to return to the main screen.


Prior to following steps you must insure that you can can see tape drives and
changer in Solaris first.
See InfoDoc 51380


                                VERITAS NetBackup
                                -----------------

If you are using VERITAS NetBackup 4.5 and later, you will need to follow
the procedure outlined below.  In a bridge environment, sg.build will not
detect all the devices attached through a FC420 bridge.  Some manual
configuration of sg driver will be needed.

1. Run sg.build to detect devices as needed.
- This will create st.conf, sg.conf and sg.links files as needed.
- The st.conf file can be appended to /kernel/drv/st.conf.
- The sg.conf and sg.links files will need to be edited.

2. Run "cfgadm -la -o show_FCP_dev" to determine which devices are seen
through the OS and their luns.

  Sample output:

Ap_Id                      Type         Receptacle   Occupant     Condition
c7                         fc-fabric    connected    configured   unknown
c7::2100001086107794,0     med-changer  connected    configured   unknown
c7::2100001086107794,1     tape         connected    configured   unknown
c7::2100001086107794,2     tape         connected    configured   unknown
c7::2100001086107794,3     ESI          connected    configured   unknown

  Note that in our example:
   * 2100001086107794 is the needed wwn.
   * The media-changer/robotics arm is located at lun 0.
   * The two drives are located at luns 1 and 2.

3. Edit the sg.conf file just created.
  Sample output:

     name="sg" parent="fp" target=0 lun=0 fc-port-wwn="2100001086107794";
     name="sg" parent="fp" target=0 lun=1 fc-port-wwn="2100001086107794";

  Note that the entry for lun 0, and possibly lun 1, device already
exists.

  There needs to be added entries for the other luns as well.  All media-
changer and tape devices will need their own entry.  In our example, the
final entries related to this device will be:

     name="sg" parent="fp" target=0 lun=0 fc-port-wwn="2100001086107794";
     name="sg" parent="fp" target=0 lun=1 fc-port-wwn="2100001086107794";
     name="sg" parent="fp" target=0 lun=2 fc-port-wwn="2100001086107794";
  
  Refer to the VERITAS NetBackup Admin Guide for more details on sg.conf
entries.

4. Edit the sg.links file just created.
  Sample output:

     type=ddi_pseudo;name=sg;addr=w2100001086107794,0;       sg/c\N0t\A1l0
     type=ddi_pseudo;name=sg;addr=w2100001086107794,1;       sg/c\N0t\A1l1

  Note that the entry for lun 0, and possibly lun 1, device already
exists.

  There needs to be added entries for the other luns as well.  All media-
changer and tape devices will need their own entry.  In our example, the
final entries related to this device will be:

     type=ddi_pseudo;name=sg;addr=w2100001086107794,0;       sg/c\N0t\A1l0
     type=ddi_pseudo;name=sg;addr=w2100001086107794,1;       sg/c\N0t\A1l1
     type=ddi_pseudo;name=sg;addr=w2100001086107794,2;       sg/c\N0t\A1l2

  Note that the lun is specified in the addr as well as the sg path.

  Refer to the VERITAS NetBackup Admin Guide for more details on sg.links
entries.

5. Continue the configuration by using the sg.install link as specified
in the VERITAS NetBackup Admin Guide.

6. Verify that sg driver is attached to the devices by running sgscan.
  The media changer and the drives should appear now.

  Sample output:

     /dev/sg/c0tw2100001086107794l0: Changer: "M4 DATA MagFile"
     /dev/sg/c0tw2100001086107794l1: Tape (/dev/rmt/3): "QUANTUM SDLT320"
     /dev/sg/c0tw2100001086107794l2: Tape (/dev/rmt/2): "QUANTUM SDLT320"

NOTE: These steps will need to be repeated if sg.build is run again and
the devices are no longer seen.

论坛徽章:
0
7 [报告]
发表于 2005-01-15 12:56 |只看该作者

无法识别SUN L25带库?solaris9(E3000+emulex9002卡)+NBU5.1

st.conf需要做什么修改吗?

论坛徽章:
0
8 [报告]
发表于 2005-01-15 12:59 |只看该作者

无法识别SUN L25带库?solaris9(E3000+emulex9002卡)+NBU5.1

文档中是老L25的QUANTUM DRIVER,设置方法应该是一样的,这个应该是以后的配置,你现在先要确认,系统能正常识别driver

你的ptach打上,用mt status看一下,应该是类似这样的输出
Example (Supported Device):
    # mt -f /dev/rmt/0 status
    HP Ultrium LTO 2 tape drive:
        sense key(0x0)= No Additional Sense   residual= 0   retries= 0
        file no= 0   block no=
    #

论坛徽章:
0
9 [报告]
发表于 2005-01-15 13:06 |只看该作者

无法识别SUN L25带库?solaris9(E3000+emulex9002卡)+NBU5.1

st.conf里面要有相应数量的条目,比如下面的例子
0: robot
1:   driver0   0cbn
2:   driver1   1cbn

name="st" class="scsi" target=4 lun=0;
name="st" class="scsi" target=4 lun=1;
name="st" class="scsi" target=4 lun=2;

论坛徽章:
0
10 [报告]
发表于 2005-01-15 13:11 |只看该作者

无法识别SUN L25带库?solaris9(E3000+emulex9002卡)+NBU5.1

你的HBA卡直连带库还是连SWITCH,如果连SWITCH,SWITCH下面还连盘阵的话,有可能会造成target id冲突(L25的光桥和盘阵),检查一下,可以考虑在HBA卡的配置文件里作WWN到target id的手工绑定。

先检查系统认带机和机械手是不是正确,然后再考虑NBU的配置
最好能吧
cfgadm -al 中带机和机械手的信息
mt -f /dev/rmt/0
mt -f /dev/rmt/1
sg.scan的输出贴出来看一下
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

北京盛拓优讯信息技术有限公司. 版权所有 京ICP备16024965号-6 北京市公安局海淀分局网监中心备案编号:11010802020122 niuxiaotong@pcpop.com 17352615567
未成年举报专区
中国互联网协会会员  联系我们:huangweiwei@itpub.net
感谢所有关心和支持过ChinaUnix的朋友们 转载本站内容请注明原作者名及出处

清除 Cookies - ChinaUnix - Archiver - WAP - TOP