跳转到主内容

执行“ network FCP zone show ”命令后、 Brocade 交换机降级并定义的配置变为空

Views:
52
Visibility:
Public
Votes:
0
Category:
fabric-interconnect-and-management-switches
Specialty:
brocade
Last Updated:

适用场景

  • Brocade FC交换机
  • FOS v8.2-1至v8.2.1D
  • FOS 8.2.2至8.2.2版
  • Emulex 目标端口(ONTAP 9.7P4之前的版本)
  • QLogic目标端口(ONTAP 9.8之前的版本)

问题描述

  • network fcp zone show对逻辑端口(ONTAP 9.8之前的版本)或Emulex端口(ONTAP 9.7P4之前的版本)发出""命令将发生原因传输一个GAZS请求帧、该请求帧要求交换机使用有限的响应有效负载大小(4096字节)。  
  • 如果请求的偏移量恰好位于活动分区数据库中的特定位置、则可能会发生以下情况:
    • Brocade GAZS ACC可能包含不正确的字段。
    • 在这种情况下、区域数据库在处理命令后也会损坏、并且在区域成员列表的末尾会保留一个额外的分号(之后可以包含或不包含额外的字符、如上所示)。  
    • 启用此损坏的分区配置还会影响网络结构中设备的流量。
    • 损坏的GAZS ACC可能会将network fcp zone show发出“”命令的NetApp控制器发生原因为崩溃状态。

此问题描述的症状包括: 

  • 已定义的分区配置数据库已删除、HA同步丢失、并验证备用CP上显示的错误
  • 网络结构已分段、原因为"分段区域冲突"
  • 日志中的错误:

2020/03/27-10:46:03, [ZONE-1062], 2850, FID 128, WARNING, switch, Defined and Effective zone configurations are inconsistent.
2020/03/27-10:46:17, [RCS-1006], 2851, FID 128, INFO, switch, State 2, Application Zoning AD0, RCS CM. Domain 7 returned 0x8. App Response Code 3.
2020/03/27-10:46:17, [ZONE-1019], 2852, FID 128, ERROR, switch, Transaction Commit failed.  Reason code 3 (3) - "Sfc Was Rejected: Remote Switch Unable To Process".

  •  区域成员列表的末尾会保留一个额外的分号

执行后、Brocade交换机降级且定义的配置为空

  • 区域成员列表末尾会保留一个额外的分号、后跟一些额外的字符(即、不是有效的别名条目):

执行后、Brocade交换机降级且定义的配置为空

 

 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.