在SANtricity统一管理器中、E系列阵列脱机

最后更新
另存为PDF

Views:: 3

Visibility:: Public

Votes:: 0

Category:: e-series-santricity-unified-manager<a>2009年679544</a>

Specialty:: esg

Last Updated:

适用场景

NetApp E 系列
SANtricity统一管理器

问题描述

如果同时使用IPv4和IPv6地址添加阵列、而其中一个地址无法访问、则系统仍会尝试访问分配的IP。

在 trace.log 适用于Unified Manager的中、您会看到以下错误：

HTTP Insecure Client Thread-1] c.n.e.a.d.StorageDevice [StorageDevice.java:529] [requestId=0, deviceId=N/A] b4beb545-a0ae-4dd0-822c-0bd8861f3176: Error encountered checking for HTTPS client support on /10.108.19.2: Timeout connecting to [/10.108.19.2:8443]
 2023-08-17 00:04:19,595 INFO [NonBlockingPool-1] c.n.e.a.d.c.FTClient [FTClient.java:352] [requestId=0, deviceId=N/A] Device b4beb545-a0ae-4dd0-822c-0bd8861f3176: 9 connection failures exceeded max of 8. Proc getObjectGraph. Retry count: 9/20. Last Error: The connection to the device has failed.