[22636 SYMCLI:8772-1] Jan-05 8:07:57 : [new_find_pooled_gk()] Skipping device '/dev/rdsk/c8t0d0' - it is invalid (see earlier messages)
[22636 SYMCLI:8772-1] Jan-05 8:07:57 : [new_find_pooled_gk()] Could not open a gatekeeper to array xxxxxxxxxxxx: A condition has been detected that requires running SymDiscover to update the gatekeeper information
[22636 SYMCLI:8772-1] Jan-05 8:07:57 : [get_array_info()] Could not obtain information on array 'xxxxxxxxxxxx': A condition has been detected that requires running SymDiscover to update the gatekeeper information
[22636 SYMCLI:8772-1] Jan-05 8:07:57 : [gkmgt_get_array_info()] Array 'xxxxxxxxxxxx' appears to be offline
[22636 SYMCLI:8772-1] Jan-05 8:07:57 : Failed to get info on array 'xxxxxxxxxxxx': There is no gatekeeper device that can be used to communicate with the symmetrix
Zhang_Jiawen
1.2K 消息
0
2013年1月4日 00:00
Gate keeper设备是用来在主机和阵列之间通信时用的。设想如果同一磁盘设备既用来读写I/O,同时又用来接收管理命令,那么当一个命令在执行时另一个命令会造成拥塞。Gakekeeper大小为2880KB,它不能用来处理I/O,只能用来处理监控和管理命令。
每一个主机最小配置5个Gatekeeper。创建Gakekeeper与创建一般的磁盘设备一样,map到Symmetrix前端口之后,再mask给主机HBA。
Fenglin1
2.1K 消息
1
2013年1月4日 00:00
symdev命令不成功?你到STORAPID daemon log里面看看有没有什么报错,然后贴出来大家看看吧。
/var/symapi/storapid.log
liulei_it
3.2K 消息
0
2013年1月4日 04:00
控制信息流不是在存储的cache中的呀。
liulei_it
3.2K 消息
0
2013年1月4日 06:00
不好意思 想问 如果 被选中的gatekeeper的盘 是不是同时在做存储数据和存储转发控制信息的双重职责呢?
Zhang_Jiawen
1.2K 消息
0
2013年1月4日 16:00
如Alex所说。Gatekeeper设备仅仅用来处理读写磁盘设备的SCSI指令。
Alex_Ye
109 消息
0
2013年1月4日 16:00
Solutions Enabler软件会自动选择最小的LUN作为Gatekeeper设备。
如果没有给一个安装了Solutions Enabler软件的服务器分配特定的Gatekeeper设备,那么存放数据的LUN也会被SE选中作为Gatekeeper设备来使用。这样的情况对某些应用对这些LUN的访问会造成影响。
因此,EMC要求对于每一个SE主机分配至少5个(有些文档里面会说6个)大小为2880 KB的设备,这样SE会选择它们作为GK,并且这些设备上也不会存放数据。
liulei_it
3.2K 消息
0
2013年1月4日 17:00
请教各位前辈偶查看了日志是这样的。把symmetrix ID给替代啦。
tail -30 storapid.log0
[22636 SYMCLI:8772-1] Jan-05 8:07:57 : [lock_and_open_device()] Closing device /dev/rdsk/c6t7d1 - SymmID mismatch: expected 'xxxxxxxxxxxx', received 'yyyyyyyyyyyy'
[22636 SYMCLI:8772-1] Jan-05 8:07:57 : [new_find_pooled_gk()] Skipping device '/dev/rdsk/c6t7d1' - it is invalid (see earlier messages)
[22636 SYMCLI:8772-1] Jan-05 8:07:57 : [lock_and_open_device()] Closing device /dev/rdsk/c6t7d2 - SymmID mismatch: expected 'xxxxxxxxxxxx', received 'yyyyyyyyyyyy'
[22636 SYMCLI:8772-1] Jan-05 8:07:57 : [new_find_pooled_gk()] Skipping device '/dev/rdsk/c6t7d2' - it is invalid (see earlier messages)
[22636 SYMCLI:8772-1] Jan-05 8:07:57 : [lock_and_open_device()] Closing device /dev/rdsk/c6t7d3 - SymmID mismatch: expected 'xxxxxxxxxxxx', received 'yyyyyyyyyyyy'
[22636 SYMCLI:8772-1] Jan-05 8:07:57 : [new_find_pooled_gk()] Skipping device '/dev/rdsk/c6t7d3' - it is invalid (see earlier messages)
[22636 SYMCLI:8772-1] Jan-05 8:07:57 : [lock_and_open_device()] Closing device /dev/rdsk/c6t7d4 - SymmID mismatch: expected 'xxxxxxxxxxxx', received 'yyyyyyyyyyyy'
[22636 SYMCLI:8772-1] Jan-05 8:07:57 : [new_find_pooled_gk()] Skipping device '/dev/rdsk/c6t7d4' - it is invalid (see earlier messages)
[22636 SYMCLI:8772-1] Jan-05 8:07:57 : [lock_and_open_device()] Closing device /dev/rdsk/c6t7d5 - SymmID mismatch: expected 'xxxxxxxxxxxx', received 'yyyyyyyyyyyy'
[22636 SYMCLI:8772-1] Jan-05 8:07:57 : [new_find_pooled_gk()] Skipping device '/dev/rdsk/c6t7d5' - it is invalid (see earlier messages)
[22636 SYMCLI:8772-1] Jan-05 8:07:57 : [lock_and_open_device()] Closing device /dev/rdsk/c6t7d6 - SymmID mismatch: expected 'xxxxxxxxxxxx', received 'yyyyyyyyyyyy'
[22636 SYMCLI:8772-1] Jan-05 8:07:57 : [new_find_pooled_gk()] Skipping device '/dev/rdsk/c6t7d6' - it is invalid (see earlier messages)
[22636 SYMCLI:8772-1] Jan-05 8:07:57 : [lock_and_open_device()] Closing device /dev/rdsk/c6t7d7 - SymmID mismatch: expected 'xxxxxxxxxxxx', received 'yyyyyyyyyyyy'
[22636 SYMCLI:8772-1] Jan-05 8:07:57 : [new_find_pooled_gk()] Skipping device '/dev/rdsk/c6t7d7' - it is invalid (see earlier messages)
[22636 SYMCLI:8772-1] Jan-05 8:07:57 : [lock_and_open_device()] Closing device /dev/rdsk/c6t8d0 - SymmID mismatch: expected 'xxxxxxxxxxxx', received 'yyyyyyyyyyyy'
[22636 SYMCLI:8772-1] Jan-05 8:07:57 : [new_find_pooled_gk()] Skipping device '/dev/rdsk/c6t8d0' - it is invalid (see earlier messages)
[22636 SYMCLI:8772-1] Jan-05 8:07:57 : [lock_and_open_device()] Closing device /dev/rdsk/c6t8d1 - SymmID mismatch: expected 'xxxxxxxxxxxx', received 'yyyyyyyyyyyy'
[22636 SYMCLI:8772-1] Jan-05 8:07:57 : [new_find_pooled_gk()] Skipping device '/dev/rdsk/c6t8d1' - it is invalid (see earlier messages)
[22636 SYMCLI:8772-1] Jan-05 8:07:57 : [lock_and_open_device()] Closing device /dev/rdsk/c6t8d2 - SymmID mismatch: expected 'xxxxxxxxxxxx', received 'yyyyyyyyyyyy'
[22636 SYMCLI:8772-1] Jan-05 8:07:57 : [new_find_pooled_gk()] Skipping device '/dev/rdsk/c6t8d2' - it is invalid (see earlier messages)
[22636 SYMCLI:8772-1] Jan-05 8:07:57 : [lock_and_open_device()] Closing device /dev/rdsk/c6t8d3 - SymmID mismatch: expected 'xxxxxxxxxxxx', received 'yyyyyyyyyyyy'
[22636 SYMCLI:8772-1] Jan-05 8:07:57 : [new_find_pooled_gk()] Skipping device '/dev/rdsk/c6t8d3' - it is invalid (see earlier messages)
[22636 SYMCLI:8772-1] Jan-05 8:07:57 : [lock_and_open_device()] Closing device /dev/rdsk/c6t0d0 - SymmID mismatch: expected 'xxxxxxxxxxxx', received 'yyyyyyyyyyyy'
[22636 SYMCLI:8772-1] Jan-05 8:07:57 : [new_find_pooled_gk()] Skipping device '/dev/rdsk/c6t0d0' - it is invalid (see earlier messages)
[22636 SYMCLI:8772-1] Jan-05 8:07:57 : [lock_and_open_device()] Closing device /dev/rdsk/c8t0d0 - SymmID mismatch: expected 'xxxxxxxxxxxx', received 'yyyyyyyyyyyy'
[22636 SYMCLI:8772-1] Jan-05 8:07:57 : [new_find_pooled_gk()] Skipping device '/dev/rdsk/c8t0d0' - it is invalid (see earlier messages)
[22636 SYMCLI:8772-1] Jan-05 8:07:57 : [new_find_pooled_gk()] Could not open a gatekeeper to array xxxxxxxxxxxx: A condition has been detected that requires running SymDiscover to update the gatekeeper information
[22636 SYMCLI:8772-1] Jan-05 8:07:57 : [get_array_info()] Could not obtain information on array 'xxxxxxxxxxxx': A condition has been detected that requires running SymDiscover to update the gatekeeper information
[22636 SYMCLI:8772-1] Jan-05 8:07:57 : [gkmgt_get_array_info()] Array 'xxxxxxxxxxxx' appears to be offline
[22636 SYMCLI:8772-1] Jan-05 8:07:57 : Failed to get info on array 'xxxxxxxxxxxx': There is no gatekeeper device that can be used to communicate with the symmetrix
是不是什么东西坏了?
liulei_it
3.2K 消息
0
2013年1月4日 18:00
就听楼上的,如果不是什么东西损坏了是否可以不管呢?
liulei_it
3.2K 消息
0
2013年1月4日 18:00
ioscan -fnCdisk 看过了标记为GK的LUN都是CLAIMED的。。
Alex_Ye
109 消息
0
2013年1月4日 18:00
从日志看上去,是这台服务器到某个Symm的连接有问题,体现在从这个阵列分过来的GK都无法访问了。
可以尝试运行一下symcfg discover,然后看看symcfg list还能不能列出这个阵列,并且查看一下这些报错的设备在ioscan -fnkC disk中是CLAIMED还是NO_HW状态。(看上去是HP-UX是吧?)
如果这些解决不了就开case吧,提供详细日志给支持工程师分析一下。
liulei_it
3.2K 消息
0
2013年1月4日 18:00
谢谢楼上的几位前辈应该是 偶用syminq -symmids查看到 Type 为Gk的的吧
偶看到https://community.emc.com/message/398273#398273 老外的帖子。不过说的操作课不敢做。哈
Zhang_Jiawen
1.2K 消息
1
2013年1月4日 18:00
猜测是否由于使用了multi pathed gatekeeper引起的?如果是,解决的方式应该是将gatekeeper 只map到1条路径,至少每条路径3个gatekeeper,然后运行symcfg discover刷新SYMAPI database。
建议客户打800而不要自己操作。