在数据端口中使用CRC进行MetroCluster切换期间、数据服务中断
适用场景
- MetroCluster IP
- 数据交换机
问题描述
- 在MetroCluster切换和切回期间、数据服务中断:
- 数据存储库脱机
- 聚合联机
- 网络接口已启动
- LUN已映射并联机
- 在两个节点的MCC阵列的一侧发现CRC错误
- 在问题描述之前、ifstat中已存在CRC错误
- 示例:
Node: Cluster01-n01
-- interface e4a (136 days, 19 hours, 38 minutes, 22 seconds) --
RECEIVE
Total frames: 61123k | Frames/second: 5 | Total bytes: 9351m
Bytes/second: 791 | Total errors: 19203 | Errors/minute: 0
...
CRC errors: 19036 | Runt frames: 0 | Fragment: 0
...
Jumbo: 7 | Error symbol: 0 | Bus overruns: 0
...
Node: Cluster01-n02
-- interface e4a (136 days, 19 hours, 38 minutes, 14 seconds) --
RECEIVE
Total frames: 74898k | Frames/second: 6 | Total bytes: 14696m
Bytes/second: 1243 | Total errors: 11610 | Errors/minute: 0
...
CRC errors: 11532 | Runt frames: 0 | Fragment: 0
...
Jumbo: 11 | Error symbol: 0 | Bus overruns: 0
...
- 网络错误的ONTAP事件消息。示例:
ALERT: vifmgr.cluscheck.hwerrors: Port e5a-603 on node node_name is reporting a high number (at least 1 per 1000 packets) of observed hardware errors (CRC, length, alignment, dropped).
- 从vSphere断开与LUN的连接、直到切回完成。