注册登录
提 问
English中文版
软件开发v5000自动恢复

IBM V5000 node1无人操作， 出现offline，过后自动恢复，这种情况怎么处理？（已过保)？

1.客户通过小机errpt 发现：
F31FFAC3 0906092417 I H hdisk7 PATH HAS RECOVERED
F31FFAC3 0906092417 I H hdisk7 PATH HAS RECOVERED
F31FFAC3 0906092417 I H hdisk3 PATH HAS RECOVERED
F31FFAC3 0906092417 I H hdisk3 PATH HAS RECOVERED
F31FFAC3 0906092317 I H hdisk5 PATH HAS RECOVERED
F31FFAC3 0906092317 I H hdisk5 PATH HAS RECOVERED
5A7598C3 0906092317 I O fscsi0 Additional FC SCSI Protocol Driver Infor
5A7598C3 0906092317 I O fscsi2 Additional FC SCSI Protocol Driver Infor
C62E1EB7 0906092217 P H hdisk3 DISK OPERATION ERROR
DE3B8540 0906092217 P H hdisk3 PATH HAS FAILED
DE3B8540 0906092217 P H hdisk3 PATH HAS FAILED
DCB47997 0906092217 T H hdisk5 DISK OPERATION ERROR
C62E1EB7 0906092217 P H hdisk5 DISK OPERATION ERROR
C62E1EB7 0906092217 P H hdisk7 DISK OPERATION ERROR
DE3B8540 0906092217 P H hdisk5 PATH HAS FAILED
DE3B8540 0906092217 P H hdisk7 PATH HAS FAILED
D5676F6F 0906092217 T H fscsi2 ATTACHED SCSI TARGET DEVICE ERROR
DE3B8540 0906092217 P H hdisk7 PATH HAS FAILED
DE3B8540 0906092217 P H hdisk5 PATH HAS FAILED
D5676F6F 0906092217 T H fscsi0 ATTACHED SCSI TARGET DEVICE ERROR
2.通过命令确认小机HBA卡没有问题，光交换机运行正常，
3.登录v5000存储,监控发现：
Error Log Entry 191
Node Identifier : node1
Object Type : iogroup
Object ID : 0
Copy ID :
Sequence Number : 292
Root Sequence Number : 292
First Error Timestamp : Wed Sep 6 08:43:55 2017

                    : Epoch + 1504658635

Last Error Timestamp : Wed Sep 6 08:43:55 2017

                    : Epoch + 1504658635

Error Count : 1
Error ID : 981102 : SAS discovery occurred, configuration changes pending
Error Code :
Status Flag : SNMP trap raised
Type Flag : INFORMATION

01 02 00 00 44 00 00 00 03 00 00 00 10 00 00 00
00 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00
01 01 01 00 0F 00 0F 00 0F 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Error Log Entry 192
Node Identifier :
Object Type : node
Object ID : 1
Copy ID :
Sequence Number : 293
Root Sequence Number : 293
First Error Timestamp : Wed Sep 6 08:43:55 2017

                    : Epoch + 1504658635

Last Error Timestamp : Wed Sep 6 08:43:55 2017

                    : Epoch + 1504658635

Error Count : 1
Error ID : 9052 : Node missing. The node is no longer a functional member of the cluster
Error Code : 1196 : Node is offline
Status Flag : FIXED : SNMP trap raised
Type Flag : ERROR CAT 2

18 76 00 03 68 07 05 50 02 00 00 00 6E 6F 64 65
31 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 30 31 2D 31
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Error Log Entry 193
Node Identifier : node2
Object Type : iogroup
Object ID : 0
Copy ID :
Sequence Number : 294
Root Sequence Number : 292
First Error Timestamp : Wed Sep 6 08:43:55 2017

                    : Epoch + 1504658635

Last Error Timestamp : Wed Sep 6 08:43:55 2017

                    : Epoch + 1504658635

Error Count : 1
Error ID : 981103 : SAS discovery occurred, configuration changes complete
Error Code :
Status Flag : SNMP trap raised
Type Flag : INFORMATION

01 02 00 00 4D 00 00 00 02 00 00 00 10 00 00 00
00 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00
01 01 01 00 0F 00 0F 00 00 00 0F 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Error Log Entry 194
Node Identifier : node2
Object Type : node
Object ID : 1
Copy ID :
Sequence Number : 295
Root Sequence Number : 295
First Error Timestamp : Wed Sep 6 08:46:19 2017

                    : Epoch + 1504658779

Last Error Timestamp : Wed Sep 6 08:46:19 2017

                    : Epoch + 1504658779

Error Count : 1
Error ID : 980349 : Node added
Error Code :
Status Flag : SNMP trap raised
Type Flag : INFORMATION

00 00 00 00 6E 6F 64 65 31 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 18 76 00 03 68 07 05 50
30 31 2D 31 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Error Log Entry 195
Node Identifier : node1
Object Type : node
Object ID : 1
Copy ID :
Sequence Number : 296
Root Sequence Number : 296
First Error Timestamp : Wed Sep 6 08:46:19 2017

                    : Epoch + 1504658779

Last Error Timestamp : Wed Sep 6 08:46:19 2017

                    : Epoch + 1504658779

Error Count : 1
Error ID : 73724 : Fewer ethernet ports operational
Error Code : 1401 : Ethernet port failure
Status Flag : UNFIXED : SNMP trap raised
Type Flag : ERROR CAT 2

01 00 24 07 31 20 31 20 30 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Error Log Entry 196
Node Identifier : node1
Object Type : iogroup
Object ID : 0
Copy ID :
Sequence Number : 297
Root Sequence Number : 297
First Error Timestamp : Wed Sep 6 08:46:19 2017

                    : Epoch + 1504658779

Last Error Timestamp : Wed Sep 6 08:46:19 2017

                    : Epoch + 1504658779

Error Count : 1
Error ID : 981102 : SAS discovery occurred, configuration changes pending
Error Code :
Status Flag : SNMP trap raised
Type Flag : INFORMATION

01 02 00 00 4D 00 00 00 02 00 00 00 10 00 00 00
00 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00
01 01 01 00 0F 00 0F 00 00 00 0F 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Error Log Entry 197
Node Identifier : node1
Object Type : node
Object ID : 1
Copy ID :
Sequence Number : 298
Root Sequence Number : 298
First Error Timestamp : Wed Sep 6 08:46:24 2017

                    : Epoch + 1504658784

Last Error Timestamp : Wed Sep 6 08:46:24 2017

                    : Epoch + 1504658784

Error Count : 1
Error ID : 74002 : Node warmstarted due to an internal error
Error Code : 2030 : Internal error
Status Flag : UNFIXED : SNMP trap raised
Type Flag : ERROR CAT 1

41 73 73 65 72 74 20 46 69 6C 65 20 2F 62 75 69
6C 64 2F 6C 6F 64 65 73 74 6F 6E 65 37 31 30 2F
31 33 30 37 31 31 61 2F 73 72 63 2F 75 73 65 72
2F 64 72 76 2F 73 61 2F 70 6C 73 61 5F 68 65 61
72 74 62 65 61 74 2E 63 20 4C 69 6E 65 20 32 30
32 0A 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Error Log Entry 198
Node Identifier : node1
Object Type : iogroup
Object ID : 0
Copy ID :
Sequence Number : 299
Root Sequence Number : 297
First Error Timestamp : Wed Sep 6 08:46:24 2017

                    : Epoch + 1504658784

Last Error Timestamp : Wed Sep 6 08:46:24 2017

                    : Epoch + 1504658784

Error Count : 1
Error ID : 981103 : SAS discovery occurred, configuration changes complete
Error Code :
Status Flag : SNMP trap raised
Type Flag : INFORMATION

01 02 00 00 56 00 00 00 03 00 00 00 20 00 00 00
10 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00
01 01 01 00 0F 00 0F 00 0F 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

关注2
评论
参与8

2同行回答
|
按赞同排序
按时间排序

danji0522danji0522软件开发工程师小兔
IBM估计会说是BUG,你可以升到最新微码，试试显示全部

IBM估计会说是BUG,你可以升到最新微码，试试

收起
互联网服务 · 2017-09-07
浏览7383
查看赞同的人
评论1
  • lengaoqun  lengaoqun
    都用了三年多了， 最近出现这个问题，有点理解不了。
    2017-09-07
    赞同
    评论
laopeng3laopeng3项目经理IT
按照你的时间往前推三年，那个是时候的微码版本都不高，这种情况常见，尽早升级微码可以有效避免这种问题，如果控制器有问题offline后就不会在自动启动起来了显示全部

按照你的时间往前推三年，那个是时候的微码版本都不高，这种情况常见，尽早升级微码可以有效避免这种问题，如果控制器有问题offline后就不会在自动启动起来了

收起
系统集成 · 2018-11-24
浏览6859
查看赞同的人
评论

提问者

lengaoqun
lengaoqun
其它中航工业
擅长领域： 存储，IBM storwize v7000，系统管理
关注2
回答3
评论15

相关问题

  • V5000和V7000换电池控制器等操作真的是个雷区吗？
  • IBM V5000存储用命令查看硬盘状态？
  • 如何从v5000把存储数据迁移过来？
  • v3700、v5000 一代控制器微码？

    • 问题状态

  • 发布时间：2017-09-07
  • 关注会员：2 人
  • 问题浏览：9094
  • 最近回答：2018-11-24

    • 关于TWT使用指南社区专家合作厂商入驻社区企业招聘投诉建议版权与免责声明联系我们
    © 2024talkwithtrend — talk with trend,talk with technologist京ICP备09031017号-30

    X社区推广