Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 4 results
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Found_duplicate_filer_table_entries_with_same_name_nodename_but_different_system_ids
      AFF8040 two node cluster controller upgrade to AFF-A300 controllers failed on step 15, page 61 of the Using Aggregate Relocation to Upgrade Controller Hardware guide. When executing the, 'boot_after_c...AFF8040 two node cluster controller upgrade to AFF-A300 controllers failed on step 15, page 61 of the Using Aggregate Relocation to Upgrade Controller Hardware guide. When executing the, 'boot_after_controller_replacement' command the new node 2(node 4 in the guide) would fail to boot with the error below: [localhost:diskown.duplicateSoftEntries:notice]: Found duplicate filer_table entries with same name nodename but different system ids ( old_sys_id, new_sys_id)
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Cluster_applications_fail_to_come_online_after_controller_upgrade_procedure
      Controller upgrade (head swap) with platforms using different cluster interconnect ports (Example: FAS8200 [e0a/e0b] to FAS8300 e0c/e0d]) Controller upgrade on ONTAP 9.5+ not using the "system control...Controller upgrade (head swap) with platforms using different cluster interconnect ports (Example: FAS8200 [e0a/e0b] to FAS8300 e0c/e0d]) Controller upgrade on ONTAP 9.5+ not using the "system controller replace" procedure After replacing both controllers with newer platform controllers, cluster applications fail to come online Attempting to migrate cluster LIFs to new platform ports while in this state using network interface migrate results in error:
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Unable_to_bring_cluster_into_quorum_during_switchless_A300_FAS8200_to_A400_FAS8300_head_upgrade
      Head upgrade for 2-node switchless cluster from FAS8200 to FAS8300 or AFF A300 to AFF A400 using nondisruptive aggregate relocation (ARL) procedure or moving storage disruptive procedure Unable to bri...Head upgrade for 2-node switchless cluster from FAS8200 to FAS8300 or AFF A300 to AFF A400 using nondisruptive aggregate relocation (ARL) procedure or moving storage disruptive procedure Unable to bring cluster into quorum after first AFF A400/FAS8300 is installed and connected to old AFF A300/FAS8200 node (using ARL procedure) or after both new nodes are in place (using disruptive procedure when moving storage) Attempting to update Cluster broadcast domain to the new ports results in error:
    • https://kb.netapp.com/on-prem/ontap/Upgrade/Upgrade-KBs/ONTAP_upgrade_after_controller_upgrade_fails_with_SAN_or_NVMe_LIFs_down_and_delete_fails
      ONTAP upgrade after controller hardware upgrade pauses. Error: SAN or NVMe LIFs are currently down, potentially causing an outage when the cluster is upgraded. Action: Before upgrading, bring all SAN ...ONTAP upgrade after controller hardware upgrade pauses. Error: SAN or NVMe LIFs are currently down, potentially causing an outage when the cluster is upgraded. Action: Before upgrading, bring all SAN and NVMe LIFs up using the 'network interface modify { -data-protocol fcp|iscsi|fc-nvme|nvme-tcp } -status-admin up' command. Attempts to delete the FC LIFs fails. To disable the LIF, use the "network interface modify" command to change the LIF's "status-admin" setting to "down".