Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 5 results
    • Cluster port link down/up repeats from FAS8300 platform
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Cluster_port_link_down_up_repeats_from_FAS8300_platform
      [?] Sun Aug 06 05:22:53 [node01: vifmgr: vifmgr.portdown:notice]: A link down event was received on node node01, port e0c. [?] Sun Aug 06 05:22:53 [node01: vifmgr: vifmgr.portdown:notice]: A link down...[?] Sun Aug 06 05:22:53 [node01: vifmgr: vifmgr.portdown:notice]: A link down event was received on node node01, port e0c. [?] Sun Aug 06 05:22:53 [node01: vifmgr: vifmgr.portdown:notice]: A link down event was received on node node01, port e0d. Sun Aug 06 05:22:53 [node01: vifmgr: vifmgr.portdown:notice]: A link down event was received on node node01, port e0c. Sun Aug 06 05:22:53 [node01: vifmgr: vifmgr.portdown:notice]: A link down event was received on node node01, port e0d.
    • Cluster port down in a Switchless configuration
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Cluster_port_down_in_a_Switchless_configuration
      Wed Nov 15 18:20:39 +0900 [Node01: vifmgr: vifmgr.portdown:debug]: A link down event was received on node Node01, port e0b. Wed Nov 15 18:20:39 +0900 [Node01: vifmgr: vifmgr.clus.linkdown:debug]: The ...Wed Nov 15 18:20:39 +0900 [Node01: vifmgr: vifmgr.portdown:debug]: A link down event was received on node Node01, port e0b. Wed Nov 15 18:20:39 +0900 [Node01: vifmgr: vifmgr.clus.linkdown:debug]: The cluster port e0b on node Node01 has gone down unexpectedly. Wed Nov 15 18:25:34 +0900 [Node01: vifmgr: vifmgr.portdown:debug]: A link down event was received on node Node01, port e0b.
    • e0a/e0b link flaps on A300/FAS8200, A200/FAS2600, A220/FAS2700,C190 may cause a Takeover
      https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/e0a_e0b_link_flaps_on_A300_FAS8200_A200_FAS2600_A220_FAS2700_C190_may_cause_a_Takeover
      Cluster ports e0a/e0b links flap or go down at the same time, with or without a node takeover. This could be caused by hardware failure on one of the nodes. KB article provides steps to identify the a...Cluster ports e0a/e0b links flap or go down at the same time, with or without a node takeover. This could be caused by hardware failure on one of the nodes. KB article provides steps to identify the affected node and resolve the issue.
    • Cluster port e0b repeatedly goes down and up
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Cluster_port_e0b_repeatedly_goes_down_and_up
      Wed Jul 10 13:41:58 [node01: vifmgr: vifmgr.portdown:notice]: A link down event was received on node node01, port e0d. Wed Jul 10 13:42:12 [node01: vifmgr: vifmgr.portup:notice]: A link up event was r...Wed Jul 10 13:41:58 [node01: vifmgr: vifmgr.portdown:notice]: A link down event was received on node node01, port e0d. Wed Jul 10 13:42:12 [node01: vifmgr: vifmgr.portup:notice]: A link up event was received on node node01, port e0d. Wed Jul 24 16:50:40 [node01: vifmgr: vifmgr.portdown:notice]: A link down event was received on node node01, port e0d. Wed Jul 24 16:50:57 [node01: vifmgr: vifmgr.portup:notice]: A link up event was received on node node01, port e0d.
    • Link down on cluster port
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Link_down_on_cluster_port
      Article covers solution when in EMS port goes down and LIF migrates to surviving port