跳转到主内容

在 LIF 在恢复后迁移了主目录后、 LIF 无法在子网之外进行通信

Views:
20
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

适用于

  • 任何存储控制器
  • 任何 ONTAP 版本

问题

LIF 在进行恢复后迁移回家后无法在指定子网之外进行通信,似乎有些 LIF 无法再从其子网外部访问。

After a giveback, it seems that some of the lifs cannot be reached anymore from outside their subnet.
检查 LIF 是否返回主目录:
Ping 同一子网中的某些 IP 或默认网关—它可以
ping 子网外的某些 IP —它会失败

命令以供参考:
     cluster::> network interface show -vserver <vserver_name>
  cluster::> network route show -vserver <vserver_name>
    (The route, or routes, with 0.0.0.0/0 indicate a default route.  The one with the lowest metric takes priority over any others.)
  cluster::> network ping -lif <lif_name> -vserver <vserver_name> -destination <IP>
   (Try some different IPs in and outside the subnet to be sure that issue is not with the destination IP)

 

ONTAP 提供的免费 ARP ( GARP )数据包可以使用当前托管 LIF 的端口的 MAC 地址更新交换机。
           有关 GARP 的详细信息,请参见此处[1]

如何检查我们是否确实发送了 GARP 数据包?
收集数据包跟踪。

  1. 在恢复过程中以及 MGWD 可用后立即在受影响的 LIF 接口上启动数据包跟踪

    有关如何在存储控制器上收集 P[ 封包跟踪 ] 的以下文章:
- How to Capture Packet Traces (TCPDump) on ONTAP 9.2+ Systems
- How to Capture Packet Traces (pktT) on Data ONTAP 8 集群模式系统

2. 等待 LIF 迁移到主目录并尝试在子网外部执行 ping 操作

3. 检查交换机上的 ARP 表
—它仍应显示映射到合作伙伴上 MAC 地址的 LIF IP

 

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.