Search

Node failed to boot with 'Waiting for SP ...' and all sensors are good
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Node_failed_to_boot_with_Waiting_for_SP_and_all_sensors_are_good
Record 1866: Sun May 26 04:07:04.000000 2024 [SysFW.notice]: SP responded to sync command in 0 seconds. Record 1868: Sun May 26 04:07:06.000000 2024 [SysFW.notice]: Waiting for SP ... Record 1870: Sun...Record 1866: Sun May 26 04:07:04.000000 2024 [SysFW.notice]: SP responded to sync command in 0 seconds. Record 1868: Sun May 26 04:07:06.000000 2024 [SysFW.notice]: Waiting for SP ... Record 1870: Sun Jan 01 00:00:37.890000 2017 [BMC.notice]: Running primary version 11.8Record 1903: Sun May 26 04:12:29.490000 2024 [BMC.notice]: Switch is running on latest version 19
AIQUM: Status of the service processor with address is offline but SP is online
https://kb.netapp.com/data-mgmt/AIQUM/AIQUM_Kbs/AIQUM__Status_of_the_service_processor_with_address_is_offline_but_SP_is_online
AIQUM host received SNMP trap shows BMC is offline: .1.3.6.1.4.1.789.5.1.2.1.0 type=4 value=STRING: "Service Processor Offline" .1.3.6.1.4.1.789.5.1.2.5.0 type=4 value=STRING: "error event on NODE-01 ...AIQUM host received SNMP trap shows BMC is offline: .1.3.6.1.4.1.789.5.1.2.1.0 type=4 value=STRING: "Service Processor Offline" .1.3.6.1.4.1.789.5.1.2.5.0 type=4 value=STRING: "error event on NODE-01 (Service Processor Offline)" .1.3.6.1.4.1.789.5.1.2.6.0 type=4 value=STRING: "Status of the service processor with address xx.xx.xx.xx is offline." Service Processor Status: Online Mon Jul 15 22:55:24 +0900 [NODE-01: spmgrd: sp.dup.ip:error]: SP IP address xxx.xxx.xxx.xxx in use by another system.
Cannot disable SP access via SSH from ONTAP
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Cannot_disable_SP_access_via_SSH_from_ONTAP
Service Processor(SP) disable SSH with the "security login delete" command, but only one node(node-1) cannot disabled. security login create admin node-1 application service-processor -authentication-...Service Processor(SP) disable SSH with the "security login delete" command, but only one node(node-1) cannot disabled. security login create admin node-1 application service-processor -authentication-method password security login create admin node-1 application ssh -authentication-method password security login delete admin node-1 application service-processor -authentication-method password security login delete admin node-1 application ssh -authentication-method password
"Waiting for cluster applications to come online on the local node" displays after takeover and cannot give back
https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Waiting_for_cluster_applications_to_come_online_on_the_local_node_displays_after_takeover_and_cannot_give_back
After takeover occurs on the system, the message "Waiting for cluster applications to come online on the local node." [?] Fri Jul 10 18:34:40 JST [fas2650-a: kernel: bsdsocket.queueLimit.reached:error...After takeover occurs on the system, the message "Waiting for cluster applications to come online on the local node." [?] Fri Jul 10 18:34:40 JST [fas2650-a: kernel: bsdsocket.queueLimit.reached:error]: Number of connection requests for the socket bound to port 935 having the IP address * has reached the limit of 1536 connections.
How to calculate the overhead of storage pool based on the desired capacity when deploy a new ONTAP Select cluster or add capacity to an existed cluster
https://kb.netapp.com/on-prem/ontap/ontap-select/Select-KBs/How_to_calculate_the_overhead_of_storage_pool_based_on_the_desired_capacity_when_deploy_a_new_ONTAP_Select_cluster_or_add_capacity_to_an_existed_cluster
When deploy a new ONTAP Select cluster, you must to specify a proper storage pool capacity limit so that you can safely deploy and use the cluster. The way to calculate overhead of the storage pool is...When deploy a new ONTAP Select cluster, you must to specify a proper storage pool capacity limit so that you can safely deploy and use the cluster. The way to calculate overhead of the storage pool is different when creating a new select cluster or add capacity to an existed cluster. If ONTAP Select attempts to use storage that has been allocated to it and if enough storage is not available, a data-serving outage will occur.
Will internal switch version be downgraded or upgraded automatically when downgrading or upgrading SP Firmware
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/If_downgrade_the_SP_Firmware_is_the_internal_switch_version_downgraded_automatically
No, the internal switch version cannot be downgraded or upgraded automatically. Note: Firmware update will need to reboot the SP on completion. The SP Firmware has been downgraded to 5.6P1, but the in...No, the internal switch version cannot be downgraded or upgraded automatically. Note: Firmware update will need to reboot the SP on completion. The SP Firmware has been downgraded to 5.6P1, but the internal switch version remains 17. Downgrade the SP internal switch version. SP fas2650-1a*> sp switch-update SP fas2650-1a*> sp switch-version SP fas2650-1a*> sp switch-verify SP fas2650-1a*> sp switch reset SP fas2650-1a*> sp switch write 0x1c 0x9 0xc000 SP fas2650-1a*> sp switch read 0x1c 0xa 0xe
How to identify the key of -parameter-criteria when adding event filter rules
https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/How_to_identify_the_key_of_-parameter-criteria_when_adding_event_filter_rules
Applies to ONTAP 9.13.1 Description Start from ONTAP 9.13.1, there has a new option -parameter-criteria add in the CLI event filter rule add. When add rules to the event filter, you can configure even...Applies to ONTAP 9.13.1 Description Start from ONTAP 9.13.1, there has a new option -parameter-criteria add in the CLI event filter rule add. When add rules to the event filter, you can configure event notifications for specific resources by specifying the [key>=<value] of -parameter-criteria.
"sp-latest-ipmi" log shows PSU status "invalid"
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/sp_latest_ipmi_log_shows_PSU_status_invalid
Applies to FAS26x0 FAS27x0 ONTAP 9 Issue The sp-latest-ipmi log displays part of sensor is "invalid". Example: Sensor Name State Current Critical Warning Warning Critical Reading Low Low High High ---...Applies to FAS26x0 FAS27x0 ONTAP 9 Issue The sp-latest-ipmi log displays part of sensor is "invalid". Example: Sensor Name State Current Critical Warning Warning Critical Reading Low Low High High ------------------------------------------------------------------------------------------------- PSU2 Bad invalid -- PSU1 Bad invalid -- PSU2 invalid -- PSU1 invalid -- PSU2 ON ON PSU1 ON ON PSU1 INFO invalid --
What are LoginGraceTime and MaxStartups used for?
https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/What_are_LoginGraceTime_and_MaxStartups_used_for
MaxStartups determines the maximum number of concurrent unauthenticated connections that the SSH server will allow. It sets limits on the number of simultaneous connection attempts that can be made to...MaxStartups determines the maximum number of concurrent unauthenticated connections that the SSH server will allow. It sets limits on the number of simultaneous connection attempts that can be made to the SSH server before authentication is completed. When the number of unauthenticated connections reaches the specified limit, the server will start rejecting new connection attempts until existing connections are authenticated or closed.
Single data ethernet port repeats netif.linkDown to netif.linkUp
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Single_data_ethernet_port_repeats_netif.linkDown_to_netif.linkUp
Single data ethernet port repeats link down to up: Wed Aug 21 07:23:56 +0900 [Node-01: kernel: netif.linkDown:info]: Ethernet e3a: Link down, check cable. Wed Aug 21 07:23:59 +0900 [Node-01: kernel: n...Single data ethernet port repeats link down to up: Wed Aug 21 07:23:56 +0900 [Node-01: kernel: netif.linkDown:info]: Ethernet e3a: Link down, check cable. Wed Aug 21 07:23:59 +0900 [Node-01: kernel: netif.linkUp:info]: Ethernet e3a: Link up. Wed Aug 21 08:38:19 +0900 [Node-01: kernel: netif.linkDown:info]: Ethernet e3a: Link down, check cable. Wed Aug 21 09:19:40 +0900 [Node-01: kernel: netif.linkDown:info]: Ethernet e3a: Link down, check cable.
BDFU get stuck when the aggregate to which the disks belong is not on the home node
https://kb.netapp.com/on-prem/ontap/Upgrade/Upgrade-KBs/BDFU_get_stuck_when_the_aggregate_to_which_the_disks_belong_is_not_on_the_home_node
Sat Jan 13 22:39:22 +0900 [Node-01: bg_disk_fw_update_admin: bdfu.selected:info]: Disk 0a.01.14 [NETAPP X477_TTCRE04TA07 NA02] S/N [69J0A0JZF9XC] selected for background disk firmware update. Manually...Sat Jan 13 22:39:22 +0900 [Node-01: bg_disk_fw_update_admin: bdfu.selected:info]: Disk 0a.01.14 [NETAPP X477_TTCRE04TA07 NA02] S/N [69J0A0JZF9XC] selected for background disk firmware update. Manually update the disk firmware by specify the node, then ems raise the following event even if disks are not get update: