Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 10 results
    • VIFMGR offline migrating cluster switch CN1610 to BES-53248
      https://kb.netapp.com/on-prem/Switches/Broadcom-KBs/VIFMGR_offline_migrating_cluster_switch_CN1610_to_BES-53248
      Wed Jun 23 2021 09:28:08 +02:00 [kern_vifmgr:info:7192] [0x80bae2900] [FailoverMgr::cluster_check] l2ping failed e0a on node1 -> e0c on node2 result='remote interface is down or unreachable. Wed Jun 2...Wed Jun 23 2021 09:28:08 +02:00 [kern_vifmgr:info:7192] [0x80bae2900] [FailoverMgr::cluster_check] l2ping failed e0a on node1 -> e0c on node2 result='remote interface is down or unreachable. Wed Jun 23 2021 09:28:33 +02:00 [kern_vifmgr:info:7192] [0x80bae2900] [FailoverMgr::cluster_check] l2ping failed e0a on node1 -> e0c on node2 result='remote interface is down or unreachable.
    • Vifmgr: Packet loss when pinging from one cluster lif to another cluster lif
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Vifmgr__Packet_loss_when_pinging_from_one_cluster_lif_to_another_cluster_lif
      8/23/2022 12:41:38 node_name-11 ALERT vifmgr.cluscheck.droppedall: Total packet loss when pinging from cluster lif node_name-11_clus1 (node node_name-11) to cluster lif node_name-01_clus2 (node node_n...8/23/2022 12:41:38 node_name-11 ALERT vifmgr.cluscheck.droppedall: Total packet loss when pinging from cluster lif node_name-11_clus1 (node node_name-11) to cluster lif node_name-01_clus2 (node node_name-01). 8/23/2022 08:28:35 node_name-11 ALERT vifmgr.cluscheck.droppedall: Total packet loss when pinging from cluster lif node_name-11_clus1 (node node_name-11) to cluster lif node_name-12_clus2 (node node_name-12).
    • Logical Interface Manager(VifMgr) aborted as a result of signal 6
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Logical_Interface_Manager_VifMgr_aborted_as_a_result_of_signal_6
      Applies to ONTAP 9.3P18 Issue LIF manager is restarted for unknown reason [netapp-b: spmd: spm.vifmgr.process.exit:EMERGENCY]: Logical Interface Manager(VifMgr) with ID 7616 aborted as a result of sig...Applies to ONTAP 9.3P18 Issue LIF manager is restarted for unknown reason [netapp-b: spmd: spm.vifmgr.process.exit:EMERGENCY]: Logical Interface Manager(VifMgr) with ID 7616 aborted as a result of signal signal 6. The subsystem will attempt to restart. [netapp-b: vifmgr: vifmgr.started:notice]: The Logical Interface Manager (VIFMgr) has started.
    • Alert Id = NodeSwitchPortMTU_Alert,  Level raised by monitor cluster-switch
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Alert_Id_NodeSwitchPortMTU_Alert_Level_raised_by_monitor_cluster_switch
      Sat Apr 24 10:19:55 +0200 [node_name: cshmd: hm.alert.raised:alert]: Alert Id = NodeSwitchPortMTU_Alert , Alerting Resource = Clusterswitch/Slot: 0 Port: 3 10G - Level raised by monitor cluster-switch...Sat Apr 24 10:19:55 +0200 [node_name: cshmd: hm.alert.raised:alert]: Alert Id = NodeSwitchPortMTU_Alert , Alerting Resource = Clusterswitch/Slot: 0 Port: 3 10G - Level raised by monitor cluster-switch Sat Apr 24 10:25:17 +0200 [node_name: cshmd: hm.alert.cleared:notice]: Alert Id = NodeSwitchPortMTU_Alert , Alerting Resource = Clusterswitch/Slot: 0 Port: 3 10G - Level cleared by monitor cluster-switch
    • LIFs go down during a Failover
      https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/LIFs_go_down_during_a_Failover
      Applies to ONTAP 9.x Logical Interface (LIF) Flash Cache Issue Vifmgr is going "Out-Of-Quorum" during a Failover, which results in LIFs being down. [kern_vifmgr:info:5605] Notice: online_status_callba...Applies to ONTAP 9.x Logical Interface (LIF) Flash Cache Issue Vifmgr is going "Out-Of-Quorum" during a Failover, which results in LIFs being down. [kern_vifmgr:info:5605] Notice: online_status_callback: RDB unit is offline
    • vifmgr reporting CRC errors on multiple interfaces
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/vifmgr_reporting_CRC_errors_on_multiple_interfaces
      ONTAP 9 / FAS / AFF Systems: Multiple interfaces report CRC errors.
    • Node panics due to mhost application becoming unresponsive
      https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/AFF_A200_A220_experince_a_nodewatchdog_panic_due_to_vifmgr_becoming_unresponsive
      Panic String: Process vifmgr unresponsive for 210 seconds in process nodewatchdog on release 9.8P3 (C) Panic string: Process vldb unresponsive for 209 seconds in process nodewatchdog on release 9.8P1 ...Panic String: Process vifmgr unresponsive for 210 seconds in process nodewatchdog on release 9.8P3 (C) Panic string: Process vldb unresponsive for 209 seconds in process nodewatchdog on release 9.8P1 (C) Panic string: Process bcomd unresponsive for 210 seconds in process nodewatchdog on release 9.9.1P6 (C) PANIC: thread (swi4: clock (0)) on cpu 0 hung for 4001 milliseconds in process swi4: clock (0) on release 9.9.1P3 (C)
    • Cluster join fails due to vifmgr process failure
      https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Cluster_join_fails_due_to_vifmgr_process_failure
      pre-setup check-unused-cluster-ports success 20 0 node-check check-for-mroot success 20 0 node-check ha-mode-check success 20 0 node-check sfo-partner-check success 20 0 node-check platform-check succ...pre-setup check-unused-cluster-ports success 20 0 node-check check-for-mroot success 20 0 node-check ha-mode-check success 20 0 node-check sfo-partner-check success 20 0 node-check platform-check success 20 0 node-check license-check success 20 0 node-check join-switchless success 20 0 node-check get-node-time success 20 0 node-check get-node-name success 20 0 node-check check-node-name success 20 0 node-check resolve-aggr-names success 20 0 node-check cluster-ha-check success 20 0
    • "vifmgr.lifdown.noports" alert occurs without clear reason
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/vifmgr_lifdown_noports_alert_occurs_without_clear_reason
      Below vifmgr.lifdown.noports alert occurs and hosted port(SOURCE port) is being removed from cluster LIF without any hardware issue on the port. [?] Tue Jun 23 03:32:12 KST [nas-01: vifmgr: vifmgr.lif...Below vifmgr.lifdown.noports alert occurs and hosted port(SOURCE port) is being removed from cluster LIF without any hardware issue on the port. [?] Tue Jun 23 03:32:12 KST [nas-01: vifmgr: vifmgr.lifdown.noports:alert]: LIF nas-01_clus1 (on virtual server xxxxxxxxxx), IP address xxx.xxx.xxx.xxx, currently cannot be hosted on node nas-01, port e0a, or any of its failover targets, and is being marked as down.
    • PANIC: Process vifmgr unresponsive for X seconds in process nodewatchdog
      https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/PANIC__Process_vifmgr_unresponsive_for_X_seconds_in_process_nodewatchdog
      Applies to ONTAP 9 FAS/AFF Issue Node goes down with the following panic string: PANIC: Process vifmgr unresponsive for 194 seconds in process nodewatchdog on release 9.8P3 (C) on Wed Mar 9 12:10:43 C...Applies to ONTAP 9 FAS/AFF Issue Node goes down with the following panic string: PANIC: Process vifmgr unresponsive for 194 seconds in process nodewatchdog on release 9.8P3 (C) on Wed Mar 9 12:10:43 CST 2022