Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 7 results
    • e0M port showing connected to partner e0M
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/e0M_port_showing_connected_to_partner_e0M
      Applies to AFF systems FAS systems ONTAP 9 Cisco Discovery Protocol (CDP) Issue Network port show and device discovery report that the e0M port of a node is directly connected to the e0M port of the p...Applies to AFF systems FAS systems ONTAP 9 Cisco Discovery Protocol (CDP) Issue Network port show and device discovery report that the e0M port of a node is directly connected to the e0M port of the partner node
    • Management port - e0M down
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Management_port_-_e0M_down
      Management port e0M count be down for two reasons: a) faulty port, or b) faulty cable/switch
    • HW-assisted takeover missing keep-alive messages from HA partner since Ontap Upgrade
      https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/HW-assisted_takeover_missing_keep-alive_messages_from_HA_partner_since_Ontap_Upgrade
      Applies to FAS8040 ONTAP 9.7 Cisco Catalyst 3750 Issue Error after ONTAP update from ONTAP 9.7P5 to 9.7P11: 2/23/2021 15:31:09 Node1 ERROR cf.hwassist.missedKeepAlive: HW-assisted takeover missing kee...Applies to FAS8040 ONTAP 9.7 Cisco Catalyst 3750 Issue Error after ONTAP update from ONTAP 9.7P5 to 9.7P11: 2/23/2021 15:31:09 Node1 ERROR cf.hwassist.missedKeepAlive: HW-assisted takeover missing keep-alive messages from HA partner (Node2) 2/23/2021 15:30:11 Node2 ERROR cf.hwassist.missedKeepAlive: HW-assisted takeover missing keep-alive messages from HA partner (Node1) No errors in hwassist-stats No entries in the "ID_mismatch" section for "storage failover hwassist stats show"
    • 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"
    • e0M and e0P port repeat Link Down/Up
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/e0M_and_e0P_port_repeat_Link_Down_Up
      [?] Tue Mar 10 11:40:51 JST [hostname: vifmgr: vifmgr.portdown:info]: A link down event was received on node hostname, port e0M. [?] Tue Mar 10 11:40:51 JST [hostname: vifmgr: vifmgr.lifdown.noports:e...[?] Tue Mar 10 11:40:51 JST [hostname: vifmgr: vifmgr.portdown:info]: A link down event was received on node hostname, port e0M. [?] Tue Mar 10 11:40:51 JST [hostname: vifmgr: vifmgr.lifdown.noports:error]: LIF hostname_mgmt1 (on virtual server 4294967295), IP address 172.30.254.171, currently cannot be hosted on node hostname, port e0M, or anywhere else, and is being marked as down.
    • e0M port is degraded due to link_flapping
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/e0M_port_is_degraded_due_to_link_flapping
      Applies to E0M port is degraded due to link_flapping Port Health Status: degraded Port health Degraded Reasons: link_flapping vifmgr.lifmoved.linkdown message repeats from the home node. [cluster-01: ...Applies to E0M port is degraded due to link_flapping Port Health Status: degraded Port health Degraded Reasons: link_flapping vifmgr.lifmoved.linkdown message repeats from the home node. [cluster-01: vifmgr: vifmgr.lifmoved.linkdown:notice]: LIF N1_mgmt1 (on virtual server ##########), IP address xxx.xxx.xxx.101, is being moved to node cluster-01, port e0M. Cluster mgmt and node mgmt LIFs are shown below Is home: false Home: cluster-01 Is home: true IP address xxx.xxx.xxx.101
    • Port e0M on node is not capable of hosting LIF
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Port_e0M_on_node_is_not_capable_of_hosting_LIF
      Applies to ONTAP 9 Issue Trying to create a data lif on a management network port fails. ::> network interface create -vserver <vserver> -lif <lif> -service-policy default-data-files -role data -data-...Applies to ONTAP 9 Issue Trying to create a data lif on a management network port fails. ::> network interface create -vserver <vserver> -lif <lif> -service-policy default-data-files -role data -data-protocol <data protocol> -address <IP address> -netmask 255.255.252.0 -home-node <node> -status-admin up -home-port e0M Info: Failed to create logical interface. Error: command failed: Port e0M on node <node> is not capable of hosting LIF <data protocol>