Search

FAS8060: Environmental Reason Shutdown (Battery PCT capacity critical)
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/FAS8060__Environmental_Reason_Shutdown_Battery_PCT_capacity_critical
FAS8060 The node just replaced motherboard suddenly shutdown and console log indicates below message. Tue Dec 15 19:08:48 KST [Nodename:monitor.shutdown.emergency:EMERGENCY]: Emergency shutdown: Envir...FAS8060 The node just replaced motherboard suddenly shutdown and console log indicates below message. Tue Dec 15 19:08:48 KST [Nodename:monitor.shutdown.emergency:EMERGENCY]: Emergency shutdown: Environmental Reason Shutdown (Battery PCT capacity critical) The "system sensors" command displays "na": SP> system sensors filter Bat_Initial_Fcc Sensor Name | Current | Unit | Status | LCR | LNC | UNC | UCR Bat_Initial_Fcc | na | Amps * hour | ok | na | na | na | na
After deleting SnapVault relations between a source and destination, on the destination, some relationships are still showing
https://kb.netapp.com/Legacy/ONTAP/7Mode/After_deleting_SnapVault_relations_between_a_source_and_destination_on_the_destination_some_relationships_are_still_showing
Applies to SnapVault 7-Mode Issue After deleting SnapVault relationships, on the destination still, some relationships are showing
Emergency shutdown: Environmental Reason Shutdown (Battery charging current failed) due to an overloaded Service Processor
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Emergency_shutdown__Environmental_Reason_Shutdown_Battery_charging_current_failed_due_to_an_overloaded_Service_Processor
Sat Jun 20 10:01:01 CEST [node_name: env_mgr: monitor.fru.info.unreadable:error]: The inventory information of FRU FAN1 is not readable. Sat Jun 20 10:08:04 CEST [node_name: env_mgr: monitor.fru.info....Sat Jun 20 10:01:01 CEST [node_name: env_mgr: monitor.fru.info.unreadable:error]: The inventory information of FRU FAN1 is not readable. Sat Jun 20 10:08:04 CEST [node_name: env_mgr: monitor.fru.info.unreadable:error]: The inventory information of FRU FAN2 is not readable. Sat Jun 20 10:11:15 CEST [node_name: env_mgr: monitor.fru.info.unreadable:error]: The inventory information of FRU PSU2 is not readable.
Health monitor alert SPNotConfiguredAlert
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Health_monitor_alert_SPNotConfiguredAlert
The system health alert show command shows the below details: Use the "system service-processor network modify" command to configure the network interface of the Service Processor. Use the "system ser...The system health alert show command shows the below details: Use the "system service-processor network modify" command to configure the network interface of the Service Processor. Use the "system service-processor image modify -node cluster-01 -autoupdate true" to configure AutoUpdate feature of the Service Processor. Possible Effect: You might not be able to use the Service Processor to remotely access, monitor, and troubleshoot your storage system.
Deprecated SSH Cryptographic Settings in Service Processor: key exchange diffie-hellman-group1-sha1
https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Deprecated_SSH_Cryptographic_Settings_in_Service_Processor__key_exchange_diffie_hellman_group1_sha1
Applies to ONTAP 9 SP/BMC Issue Penetration testing tool or security software audit could report a vulnerability on the Service Processor IP address as supporting deprecated SSH Cryptographic Settings...Applies to ONTAP 9 SP/BMC Issue Penetration testing tool or security software audit could report a vulnerability on the Service Processor IP address as supporting deprecated SSH Cryptographic Settings, such as diffie-hellman-group1-sha1 or chacha20-poly1305@openssh.com A more generic alert such as ssh-weak-kex-algorithms or SSH Weak key Exchange Algorithms Enable could also be reported
SP in rebooting status after ONTAP upgrade or maintenance activity
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/SP_in_rebooting_status_after_ONTAP_upgrade_or_maintenance_activity
ONTAP 9 Service processor (SP) Baseboard Management Controller (BMC) The status of SP/BMC shows as rebooting after a maintenance activity: Cluster::> system service-processor show Node Type Status IP ...ONTAP 9 Service processor (SP) Baseboard Management Controller (BMC) The status of SP/BMC shows as rebooting after a maintenance activity: Cluster::> system service-processor show Node Type Status IP Configured FirmwareVersion IP Address FAS8200-01 BMC rebooting true 13.4P2 1.2.3.4 FAS8200-02 BMC online true 13.4P2 1.2.3.5 The same status is observed from sysconfig -a output as well: ::> system node run -node <node> -command sysconfig -a Service Processor Status: Rebooting
System Console session via the Service Processor corrupted by serial console port
https://kb.netapp.com/Legacy/ONTAP/7Mode/System_Console_session_via_the_Service_Processor_corrupted_by_serial_console_port
â–’Files /cfcard/x86_64/freebsd/image2/VERSION and /var/VERSION differ Waiting for PIDS: /usr/sbin/rpcbind 908wâ–’â–’wâ–’â–’â–’â–’w{â–’â–’â–’wâ–’â–’â–’{â–’â–’â–’â–’â–’{â–’â–’â–’â...â–’Files /cfcard/x86_64/freebsd/image2/VERSION and /var/VERSION differ Waiting for PIDS: /usr/sbin/rpcbind 908wâ–’â–’wâ–’â–’â–’â–’w{â–’â–’â–’wâ–’â–’â–’{â–’â–’â–’â–’â–’{â–’â–’â–’â–’â–’â–’â–’â–’â–’â–’wâ–’wâ–’â–’â–’â–’â–’â–’â–’â–’â–’â–’{â–’â–’â–’{â–’â–’â–’â–’â–’â–’{â–’â–’â–’â–’â–’â–’â–’â–’â–’â–’â–’â–’â–’â–’â–’â–’â–’â–’â–’â–’â–’â–’â–’â–’â–’â–’â–’{â–’â–’â–’â–’â–’â–’â–’â–’â–’â–’â–’â–’â–’â–’â–’â–’â–’â–’â–’â–…
How to update the network configuration information for a SP or BMC
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/How_to_reset_the_configuration_information_for_the_SP_BMC
Applies to AFF Systems ASA Systems FAS Systems Description This article describes how to reset the configuration information for the Service Processor (SP) or Baseboard Management Controller (BMC).
SP HBT MISSED in EMS log
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/SP_HBT_MISSED_in_EMS_log
Applies to Data ONTAP 8 ONTAP 9 Service Processor (SP) Issue System has similar "SP HBT MISSED" error in EMS: Mon Oct 25 13:10:39 +0900 [Nodename: spsm_listener: callhome.sp.hbt.missed:notice]: Call h...Applies to Data ONTAP 8 ONTAP 9 Service Processor (SP) Issue System has similar "SP HBT MISSED" error in EMS: Mon Oct 25 13:10:39 +0900 [Nodename: spsm_listener: callhome.sp.hbt.missed:notice]: Call home for SP HBT MISSED Tue Jun 21 10:32:10 +0900 [Nodename: spsm_listener: sp.heartbeat.stopped:error]: Have not received a IPMI heartbeat from the Service Processor (SP) in last 20 seconds.
e0M Port on controller is permanently down
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/e0M_Port_on_controller_is_permanently_down
Applies to e0M port FAS platforms AFF platforms Issue e0M port down Service Processor is accessible EMS: "vifmgr.port.monitor.failed: The "l2_reachability" health check for port e0M (node XXXX) has fa...Applies to e0M port FAS platforms AFF platforms Issue e0M port down Service Processor is accessible EMS: "vifmgr.port.monitor.failed: The "l2_reachability" health check for port e0M (node XXXX) has failed. The port is operating in a degraded state"
SP/e0m traffic fails while Service Processor firmware update stuck at 93 percent
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/SP_e0m_traffic_fails_while_Service_Processor_firmware_update_stuck_at_93_percent
Applies to FAS systems SP firmware 2.9P1 Issue The Service Processor firmware is updated The cluster still reports: ::*> system service-processor image update-progress show In Percent Node Progress St...Applies to FAS systems SP firmware 2.9P1 Issue The Service Processor firmware is updated The cluster still reports: ::*> system service-processor image update-progress show In Percent Node Progress Start Time Done End Time ---------------- -------- ------------------- ------- ------------------- node_name_01 yes - 93 - node_name_02 yes - 93 - 2 entries were displayed.