Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 5 results
    • The 2nd node upgrade failed on System Manager from 9.14 to 9.15
      https://kb.netapp.com/on-prem/ontap/Upgrade/Upgrade-KBs/The_2nd_node_upgrade_failed_on_System_Manager_from_9.14_to_9.15
      check the failover-group and failover-policy for each lif to make sure there is a network port it can fail over to on migrate the lif to a port that is operarional. The upgrade is implemented on Syste...check the failover-group and failover-policy for each lif to make sure there is a network port it can fail over to on migrate the lif to a port that is operarional. The upgrade is implemented on System Manager by ignoring the above warning and at the phase of the 2nd node upgrade, it failed with the below error message: Migrate all of the data LIFs using the "network interface migrate-all -node Node01" command. The port which data lif going to to migrate is in degraded status.
    • VLAN tagged ports are in different broadcast domains with auto port placement in ONTAP
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/VLAN_tagged_ports_are_in_different_broadcast_domains_with_auto_port_placement_in_ONTAP
      Applies to ONTAP 9.8 and later Issue VLAN tagged ports with the same VLAN ID are automatically added to different broadcast domains: cluster1::> network port broadcast-domain show IPspace Broadcast Up...Applies to ONTAP 9.8 and later Issue VLAN tagged ports with the same VLAN ID are automatically added to different broadcast domains: cluster1::> network port broadcast-domain show IPspace Broadcast Update Name Domain Name MTU Port List Status Details ------- ----------- ------ ----------------------------- -------------- Default-1 1500 cluster1-01:a0a-2304 complete Default-2 1500 cluster1-02:a0a-2304 complete
    • What is mechanism for checking L2 reachability
      https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/What_is_mechanism_for_checking_L2_reachability
      In order to identify OSI layer 2 reachability issues, an L2 algorithm is used to ping the MAC addresses of the other ports in the cluster that belong to the same broadcast domain. The L2 ping is perfo...In order to identify OSI layer 2 reachability issues, an L2 algorithm is used to ping the MAC addresses of the other ports in the cluster that belong to the same broadcast domain. The L2 ping is performed by sending Connectivity Fault Management (CFM) frames A port considers itself 'healthy' if it receives a CFM frame from any other port in its configured broadcast domain A port considers itself 'degraded' if it is receives no CFM frames from its configured broadcast domain
    • Cluster create fails due to cluster port L2 connectivity issues
      https://kb.netapp.com/on-prem/Switches/Cisco-KBs/Cluster_create_fails_due_to_cluster_port_L2_connectivity_issues
      System start up System start up . System start up .. System start up ... System start up .... System start up ..... Starting cluster support services Starting cluster support services . Trying to crea...System start up System start up . System start up .. System start up ... System start up .... System start up ..... Starting cluster support services Starting cluster support services . Trying to create cluster again as previous attempt failed. System start up System start up . System start up .. System start up ... System start up .... System start up ..... Starting cluster support services Starting cluster support services . Error: Not all local cluster ports have reachability to one another.
    • Temporary vifmgr.port.monitor.failed error. Failed "l2_reachability" health check
      https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/vifmgr_port_monitor_failed_error_due_to_failed_l2_reachability_health_check
      Thu Dec 03 15:57:44 +0100 [node_name: vifmgr: vifmgr.portDeg.lifMoved:notice]: LIF node_name-clus1 (on virtual server 4294967293), IP address 169.254.114.29, is being moved to node node_name, port e0b...Thu Dec 03 15:57:44 +0100 [node_name: vifmgr: vifmgr.portDeg.lifMoved:notice]: LIF node_name-clus1 (on virtual server 4294967293), IP address 169.254.114.29, is being moved to node node_name, port e0b from node node_name, port e0a because the port's health status is in a degraded state.