Skip to main content
NetApp Knowledge Base

SP inaccessible with e0M up and functioning

Views:
231
Visibility:
Public
Votes:
0
Category:
fas-systems
Specialty:
hw
Last Updated:

Applies to

  • FAS 8020

Issue

  • The Service Processor IP address is inaccessible on one node of the HA pair, the network connectivity was verified but the SP IP does not respond to pings.
  • The Cluster management and node management LIFs on the affected node, hosted on the e0M port, are functioning normally as they are pingable and accessible.
  • The MAC address for the Service Processor is not seen on the connected switch port, although the MAC addresses for the e0M port is seen.
  • The Service Processor was rebooted, and the firmware was attempted to be upgraded, which failed:
::> system service-processor reboot-sp -node <node name>
  • Service Processor upgrade failure (SP-MGMT-MLOG-TXT.GZ in Autosupport):
Jan 13 22:44:34 +0000 [node01: servprocd: sp.servprocd.upd.unexpt.evts:debug]: params: {'reason': 'Unable to transfer SP firmware image using network interface'}
[?] Thu Jan 13 22:44:34 +0000 [node01: servprocd: sp.servprocd.upd.error:error]: SP update error: SP firmware update failure has been detected.
[?] Thu Jan 13 22:45:00 +0000 [node01: nphmd: hm.alert.raised:alert]: Alert Id = SPAutoUpgradeFailedMajorAlert , Alerting Resource = SP Upgrade raised by monitor controller
[?] Thu Jan 13 22:46:22 +0000 [node01: servprocd: sp.servprocd.upd.evts:debug]: params: {'reason': 'SP Firmware network update from 3.10 to 3.11 has been triggered.'}
[?] Thu Jan 13 22:46:34 +0000 [node01: notifyd: callhome.ondemand.invoke.all:notice]: params: {'aod_req_id': '61e0a0969f3f553997c0cd32', 'sequence': '472', 'URI': '', 'subject': 'ON DEMAND (ALL:AODS TRIGGERED)'}

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

New to NetApp?

Learn more about our award-winning Support

Scan to view the article on your device