Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 42 results
    • https://kb.netapp.com/on-prem/ontap/da/SAN/SAN-KBs/Link_break_on_FCoE__Firmware_status_code_status1_0x10_status2_0x7_and_status4_0x31
      Applies to ONTAP 9.X Issue FCoE LIF shows Extended Status: waiting for Link. Link break detected with the following EMS message: [NETAPP01: fct_tpd_work_thread_0: scsitarget.ispfct.linkBreak:error]: L...Applies to ONTAP 9.X Issue FCoE LIF shows Extended Status: waiting for Link. Link break detected with the following EMS message: [NETAPP01: fct_tpd_work_thread_0: scsitarget.ispfct.linkBreak:error]: Link break detected on Fibre Channel target adapter 2a. Firmware status code status1 0x10, status2 0x7, and status4 0x31.
    • https://kb.netapp.com/on-prem/Switches/Cisco-KBs/Questions_for_qualified_Cisco_cluster_and_storage_network_switches
      It is the customer responsibility to register all the switches purchased from NetApp directly with Cisco or a Cisco reseller as well change entitlements or to renew their systems to get support for th...It is the customer responsibility to register all the switches purchased from NetApp directly with Cisco or a Cisco reseller as well change entitlements or to renew their systems to get support for the switches. If the switch was purchased with Cisco's onsite replacement entitlement, a Cisco onsite field engineer can reconfigure the switch for management access, load the desired NX-OS version, and reload the RCF file if instructed to do so prior to going onsite.
    • https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/LACP_ports_listed_under_the_show_lacp_issu_impact_as_not_ISSU_ready
      LACP ports listed under the command show lacp issu-impact report as not ISSU ready The Nexus upgrade process will therefore force the chassis itself to upgrade disruptively if LACP fast is used. A “di...LACP ports listed under the command show lacp issu-impact report as not ISSU ready The Nexus upgrade process will therefore force the chassis itself to upgrade disruptively if LACP fast is used. A “disruptive” upgrade means the chassis itself will fully reload which in essence would impact all ports on the switch and not just the “LACP fast” ones. Recommendation from Cisco is not to change to LACP fast on Nexus modular switches
    • https://kb.netapp.com/on-prem/ontap/da/SAN/SAN-KBs/Initiator_showing_as_logged_in__post_decommission_of_the_host
      Host WWPNs showing as logged in under igroup show and fcp ping-initiator show even after zone removal on switch and host shutdown/decommission. igroup show -vserver vserver-nprod -igroup ig_fcp_xx Ini...Host WWPNs showing as logged in under igroup show and fcp ping-initiator show even after zone removal on switch and host shutdown/decommission. igroup show -vserver vserver-nprod -igroup ig_fcp_xx Initiators: 20:00:00:xx:xx:xx:xx:0x (logged in) 20:00:00:xx:xx:xx:xx:0x (logged in) node-c01::> fcp ping-initiator show -vserver vserver-nprod -wwpn 20:00:00:xx:xx:xx:xx:0x (vserver fcp ping-initiator show) 20:00:00:xx:xx:xx:xx:0x node-n01 lif-0e zone-info-not-available -
    • https://kb.netapp.com/on-prem/ontap/mc/MC-KBs/Command_mapping_between_Cisco_and_NVIDIA_switches
      nv show --paginate on|off nv show --paginate on system nv show system nv show platform nv show platform environment nv show platform hardware show ip interface mgmt 0 nv show interface mgmt show runni...nv show --paginate on|off nv show --paginate on system nv show system nv show platform nv show platform environment nv show platform hardware show ip interface mgmt 0 nv show interface mgmt show running-config interface ethernet 1/9 nv show interface <if_name> nv show interface swp3 nv show interface neighbor nv show interface nv show interface --view=pluggables nv config show nv config show -o commands nv config show --startup -o commands nv config show --rev=startup
    • https://kb.netapp.com/on-prem/Switches/Cisco-KBs/What_is_the_minimum_support_offering_required_to_have_with_Cisco_and_NetApp
      Applies to Cisco MDS and Nexus switches purchased from NetApp Answer NetApp recommends: Purchasing a Cisco Smart Net Total Care support contract at the same level of service as NetApp Support Edge Adv...Applies to Cisco MDS and Nexus switches purchased from NetApp Answer NetApp recommends: Purchasing a Cisco Smart Net Total Care support contract at the same level of service as NetApp Support Edge Advisor or Premium Purchasing Cisco Solution Support for the highest level of Cisco support Additional Information additionalInformation_text
    • https://kb.netapp.com/on-prem/Switches/NetApp-KBs/IP_interfaces_not_connecting_after_cluster_switch_upgrade_from_CN1610_to_3132Q
      Eth1/1 1 eth access down XCVR not inserted auto(D) -- Eth1/25/2 20 eth access down Administratively down auto(D) -- Eth1/25/3 20 eth access down Administratively down auto(D) -- Eth1/25/4 20 eth acces...Eth1/1 1 eth access down XCVR not inserted auto(D) -- Eth1/25/2 20 eth access down Administratively down auto(D) -- Eth1/25/3 20 eth access down Administratively down auto(D) -- Eth1/25/4 20 eth access down Administratively down auto(D) -- Eth1/26/2 20 eth access down Administratively down auto(D) -- Eth1/26/3 20 eth access down Administratively down auto(D) -- Eth1/26/4 20 eth access down Administratively down auto(D) -- Eth1/27/1 20 eth access down XCVR not inserted auto(D) --
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/FC_host_connectivity_lost_after_ONTAP_upgarde
      Applies to ONTAP FCP/FCoE Cisco Issue During ONTAP upgrade FCoE host connectivity got lost.
    • https://kb.netapp.com/on-prem/Switches/Cisco-KBs/How_to_return_a_Cisco_product_that_is_dead_on_arrival
      Dead on arrival (DOA) is defined as a product that fails at initial power-up Once TAC has determined the product to be DOA and eligible for new product, a request for a replacement and Returns Materia...Dead on arrival (DOA) is defined as a product that fails at initial power-up Once TAC has determined the product to be DOA and eligible for new product, a request for a replacement and Returns Material Authorization (RMA) will be submitted. A replacement sales order will be created as well as a RMA to return the defective gear. Return the defective gear to the designated Cisco return depot within 30 days to avoid being invoiced for the replacement product.
    • https://kb.netapp.com/on-prem/Switches/Cisco-KBs/How_to_upgrade_CISCO_MDS_9000_Series_Switch_firmware
      Applies to Cisco MDS 9000 Series Switches Front End SAN Switch Description This article describes the Cisco MDS 9148 Multilayer Director Switch firmware upgrade procedure from version 8.2 to 8.4
    • https://kb.netapp.com/on-prem/Switches/Cisco-KBs/Who_calls_Cisco_and_opens_the_TAC_case_when_there_is_a_Cisco_issue
      Contact NetApp to provide initial triage and fault isolation if the issue is uncertain Contact Cisco directly if the problem is believed to be a switch issue such as powersupply failure or password re...Contact NetApp to provide initial triage and fault isolation if the issue is uncertain Contact Cisco directly if the problem is believed to be a switch issue such as powersupply failure or password reset Every Cisco technical case recommending configuration or firmware changes requires a case to be opened with NetApp If subsequent determination points to Cisco, NetApp will assist the customer to raise a case with Cisco (customer Cisco.com CCOID and serial number required)