免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
最近访问板块 发新帖
查看: 6319 | 回复: 9

请教eva4000的故障问题,请高手进来看下 [复制链接]

论坛徽章:
0
发表于 2011-09-27 19:17 |显示全部楼层
本帖最后由 幽冥公子 于 2011-10-14 12:09 编辑

小弟愚钝,看不明白具体报错在那里,请高手帮忙看下,谢谢。

Severity: Warning -- not failed but attention recommended or required. A Fibre Channel port on the HSV200 controller has failed to respond.

Error reading extended event description from c:\hsvmafiles\napp\eventout.txt

EIP08 - Fibre Channel Services Fibre Channel Port Link Failure
A Fibre Channel port link has failed or a Drive Enclosure Environmental Monitoring Unit task has failed.

Event Log Packet Event Specific Information

   flags (Flags)
      Flag field bits: 00000011

      Time has been set on this HSV200 controller: TRUE
      Time has been synchronized with all HSV200 controllers in the Storage System: TRUE
      Event sequence number reset occurred: FALSE
      Event reported out of sequence due to Final Event Block reconciliation or lost host event: FALSE
      Event requeued following restart or resynchronization: FALSE
      Event reported using LAB code: FALSE
      Event reported by primary HSV200 controller (Note: Not valid until Storage System primary HSV200 controller is elected): FALSE
      Single power supply HSV200 controller: FALSE

   revision - Structure revision number: 2  [0x02]
   count - Event specific information size in bytes: 180  [0xb4]
   sequence_number - Sequence number assigned to the event: 125609  [0x01eaa9]
   sw_version - HSV200 controller software version number string: 6000
   baselevel_id - HSV200 controller baselevel build string: CR0D63
   ctrlr_model_id - HSV200 controller model string: HSV200
   reporting_ctrlr - Storage System Management Interface Handle of HSV200 controller that reported the event: Noid: 0   IdType: 7   IdLength: 8   UUID: 5005-08b4-0010-8a4d-0000-0000-0000-0000
   report_time - Time event was reported: Date: 27-Sep-2011  Time: 09:24:29:877
   report_location - Location of event report call: 1413556  [0x1591b4]

   header (Header Information)

      ** NOTE: The following is part of a UNION with more than one interpretation.
         You will need to determine which union value is relevant.

      ** START UNION: ( u - Event Code Union ) **

      ec (Event Code)
         eiptype - Event Information Packet Type Code: 8  [0x08]
         cac - Corrective Action Code: 74  [0x4a]
            Corrective Action: Unable to communicate through a Fibre Channel link to a Fibre Channel port. This may be caused by a missing Fibre connection to an HSV200 controller Host Port or Drive Enclosure, faulty GBIC, faulty Drive Enclosure, faulty Fibre Channel Cable, faulty Drive Enclosure I/O module, or faulty Fibre Channel Switch. This is a preemptive action warning, no immediate action is necessary.
         evnum - Event Number: 1  [0x01]
         scid - HSV200 Controller Software Component Identification: 6  [0x06]

      ** UNION OR: ( u - Event Code Union ) **
      value - Event Code Value: 100747784  [0x06014a08]
      ** END UNION: ( u - Event Code Union ) **
      revision - Packet revision number: 3  [0x03]
      type - Packet type: 8  [0x08]
      count - Number of bytes in packet: 116  [0x74]

   cerp_id - HSV200 controller enclosure rear panel Fibre Channel port: DP-1B
   other_cerp_id - HSV200 controller enclosure rear panel Fibre Channel port attached to the physical disk drive or mirror port:

   peb[0] (Fibre Channel port Event Blocks)
      type - Error type code: 3  [0x03]
      context - Error context: 3735879684  [0xdead0004]


   peb[1] (Fibre Channel port Event Blocks)
      type - Error type code: 3  [0x03]
      context - Error context: 3735879684  [0xdead0004]


   peb[2] (Fibre Channel port Event Blocks)
      type - Error type code: 3  [0x03]
      context - Error context: 3735879684  [0xdead0004]


   peb[3] (Fibre Channel port Event Blocks)
      type - Error type code: 3  [0x03]
      context - Error context: 3735879684  [0xdead0004]


   peb[4] (Fibre Channel port Event Blocks)
      type - Error type code: 3  [0x03]
      context - Error context: 3735879684  [0xdead0004]


   peb[5] (Fibre Channel port Event Blocks)
      type - Error type code: 3  [0x03]
      context - Error context: 3735879684  [0xdead0004]


   peb[6] (Fibre Channel port Event Blocks)
      type - Error type code: 3  [0x03]
      context - Error context: 3735879684  [0xdead0004]


   peb[7] (Fibre Channel port Event Blocks)
      type - Error type code: 3  [0x03]
      context - Error context: 3735879684  [0xdead0004]

   peq_prod_index - Producer index: 6  [0x06]
   peq_frz_prod_index - Error idle or freeze producer index: 6  [0x06]
   failure_cause - Code indicating path to link failure: 3  [0x03]
   peq_cons_index - Consumer index: 5  [0x05]
   reserved1 - Reserved: 0  [0x00]
   time - Used to represent a retry time or other time based element in the event.: 16  [0x10]
   other_port - HSV200 controller internal Fibre Channel port number: 0  [0x00]
   port - HSV200 controller internal Fibre Channel port number: 1  [0x01]

   recovery (Loop Recovery Operations)
      progress - EWE Step for recovery process: 0  [0x00]
      shelf - Physical Shelf being evaluated.: 0  [0x00]
      slot - Physical Slot being evaluated.: 0  [0x00]
      cab - Cabinet rack being evaluated.: 0  [0x00]


*** End of Data ***

说是光纤通道不通,但是具体在哪个位置不通,小弟看不明白,谢谢。

论坛徽章:
3
CU十二周年纪念徽章
日期:2013-10-24 15:41:34狮子座
日期:2014-03-27 15:44:382015年辞旧岁徽章
日期:2015-03-03 16:54:15
发表于 2011-09-27 20:25 |显示全部楼层
查看一下port是否正常嘛,你用的哪个多路径软件?
EMC PowerPath的话用 powermt display dev=all 查看一下路径
如果是symantec的VxVM的话 vxdmpadm getsubpaths  确认一下

论坛徽章:
48
15-16赛季CBA联赛之青岛
日期:2021-01-07 13:41:2315-16赛季CBA联赛之上海
日期:2020-12-01 18:02:0720周年集字徽章-20	
日期:2020-10-28 14:14:2620周年集字徽章-20	
日期:2020-10-28 14:04:3015-16赛季CBA联赛之天津
日期:2020-10-18 22:51:412016猴年福章徽章
日期:2016-02-18 15:30:3415-16赛季CBA联赛之北控
日期:2015-12-22 13:30:48操作系统版块每日发帖之星
日期:2015-12-07 06:20:00操作系统版块每日发帖之星
日期:2015-09-04 06:20:002015亚冠之德黑兰石油
日期:2015-08-05 18:46:082015年亚洲杯之巴勒斯坦
日期:2015-04-19 10:42:502015年亚洲杯之巴林
日期:2015-04-09 08:03:23
发表于 2011-09-27 21:09 |显示全部楼层
检查控制器5005-08b4-0010-8a4d的DP-1B

论坛徽章:
0
发表于 2011-09-28 00:05 |显示全部楼层
你确定你的故障设备是EVA4400?我怎么看到了HSV200?难道是年纪大了,眼花????

论坛徽章:
0
发表于 2011-09-28 00:59 |显示全部楼层
HSV200是控制器的型号啊

论坛徽章:
0
发表于 2011-09-28 02:09
本帖最后由 joeandjane 于 2011-09-28 02:23 编辑

那是我孤陋寡闻,原来EVA4400还可以用HSV200的控制器呀? 不过有个疑问;
EVA4400是单机框双控制板设计
eva4400.JPG

HSV200是双独立机框设计。
捕获1.JPG
这个HSV200的控制器可该如何接到EVA4400的机框里面去呢?如果真要这么个配法,估计EVA4400非得要爆菊花不可了。

论坛徽章:
0
发表于 2011-09-28 02:51 |显示全部楼层
先查一下你的EMU是否正常,包括EAB线路,是否松动。然后从SMA上登录CV进去看看硬件设备的状态。是否有扩展柜报错,离线或者有黄色的感叹号。同时看,是否主备控制器发生了倒换。UUID低的是主控,高的是从控。然后再做进一步分析。

论坛徽章:
0
发表于 2011-09-28 12:16 |显示全部楼层
谢谢楼上各位,各个状态灯都正常,现在就是怀疑是loop B上的DP1B出了问题,单是不知道是线缆问题还是端口问题。

论坛徽章:
48
15-16赛季CBA联赛之青岛
日期:2021-01-07 13:41:2315-16赛季CBA联赛之上海
日期:2020-12-01 18:02:0720周年集字徽章-20	
日期:2020-10-28 14:14:2620周年集字徽章-20	
日期:2020-10-28 14:04:3015-16赛季CBA联赛之天津
日期:2020-10-18 22:51:412016猴年福章徽章
日期:2016-02-18 15:30:3415-16赛季CBA联赛之北控
日期:2015-12-22 13:30:48操作系统版块每日发帖之星
日期:2015-12-07 06:20:00操作系统版块每日发帖之星
日期:2015-09-04 06:20:002015亚冠之德黑兰石油
日期:2015-08-05 18:46:082015年亚洲杯之巴勒斯坦
日期:2015-04-19 10:42:502015年亚洲杯之巴林
日期:2015-04-09 08:03:23
发表于 2011-09-28 14:04 |显示全部楼层
这肯定不是EVA4400了,EVA4400的控制器是HSV300。LZ还是先在CommandView EVA里面检查一下目前该控制器的DP-1B是否正常吧,如果正常的话就不用管了。因有可能是之前的报错~

论坛徽章:
0
发表于 2011-10-07 14:01 |显示全部楼层
你在command view 里能看到报错么。
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

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

清除 Cookies - ChinaUnix - Archiver - WAP - TOP