メインコンテンツへスキップ

CHW-1892:10.8から10.9へのfwアップグレード後のAFF A800 BMC APIの到達可能性エラー

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

問題

  • BMCファームウェアをバージョン 10.9 にアップデートすると、「system node autosupport manifest show -node * -body-file platform-sensors.xml」の出力は次のようになります。

The Service Processor on node "node_name" is not reachable. Verify that the SP or BMC is online, verify that api-service is enabled on the SP or BMC, verify that the partner node is running, check if pings from SP or BMC to partner node work, check if hw-assist keep-alives are normal, check that network ports are configured correctly and are functional (up). Then, try the command again.
  • 「system service-processor api-service check -node node_name」の出力にエラーが示されています:

Node: node_name
Port: 50000
Local Private IPv4: failed (192.0.2.81) (ping failed)
Local Public IPv4: ok (<BMC_IP>)

  • 「bmc status -d」のBMC出力は次のようになります。

[kern_servprocd:info:7973] bmc_set_privlanconfig_to_chip:return err(-1)
[kern_servprocd:info:7973] bmc_set_privlanconfig_to_chip: netmask set failed
[kern_servprocd:info:7973] 0x808cd4e00: 0: ERR: Servprocd::SPConfig: manage_ipmi_tasks : Failed to set BMC priv lan.
[kern_servprocd:info:7973] 0x808cd4e00: 0: ERR: Servprocd::SPConfig: manage_ipmi_tasks : GET priv LANCONFIG : Network config from BMC 0.0.0.0 0.0.0.0

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.