Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 6 results
    • Is the Network Port DCB configurable on NetApp to match the Cisco Switch settings?
      https://kb.netapp.com/on-prem/Switches/Cisco-KBs/Is_the_Network_Port_DCB_configurable_on_NetApp_to_match_the_Cisco_Switch_settings
      Any changes made with regards to QoS/CoS/ DCB on Cisco Switch should reflect immediately on NetApp Storage. There is no specific configuration change required from ONTAP. Use dcb show command on ONTAP...Any changes made with regards to QoS/CoS/ DCB on Cisco Switch should reflect immediately on NetApp Storage. There is no specific configuration change required from ONTAP. Use dcb show command on ONTAP to verify the settings. Interface PGID Priority Application Bandwidth --------- ---- ---------- ------------ ------------ e3a 0 0 1 2 4 5 6 7 unassigned 50% 1 3 FCoE 50% e3b 0 0 1 2 3 4 5 6 7 unassigned 0% e4a 0 0 1 2 4 5 6 7 unassigned 50% 1 3 FCoE 50% e4b 0 0 1 2 3 4 5 6 7 unassigned 0%
    • ESXi FCoE hosts cannot access volumes however paths are visible
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/ESXi_FCoE_hosts_cannot_access_volumes_however_paths_are_visible
      FCoE VMware ESXi LUN paths visible but vCenter ESXi in different location cannot access the datastore using Fibre Channel over Ethernet (FCoE) Output of command esxcli storage core device list Status ...FCoE VMware ESXi LUN paths visible but vCenter ESXi in different location cannot access the datastore using Fibre Channel over Ethernet (FCoE) Output of command esxcli storage core device list Status : degraded ( means single path ) Note: "unknown" means ESXi does not recognize the state of the device or "off" may indicate Permanent Device Loss (PDL) Output of vmkwarning.log while trying to access LUN cpu12:123)WARNING: Partition: 123: Partition table read from device naa.xyz failed: I/O error
    • FC host connectivity lost after ONTAP upgarde
      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.
    • FCoE ports no longer show as up on any ports in the environment in ONTAP
      https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/FCoE_ports_no_longer_show_as_up_on_any_ports_in_the_environment_in_ONTAP
      Applies to ONTAP 9.X FCoE Issue Host were no longer able to see their boot LUN due to all FCoE connections were down
    • Brocade Defect 'DEFECT000568423' : I/O abort issue on the host
      https://kb.netapp.com/on-prem/Switches/Brocade-KBs/Brocade_Defect_DEFECT000568423___I_O_abort_issue_on_the_host
      Applies to FCoE FCIP Fabric Operating System (FOS) v7.2.1 Switch 7800/FX8024 Brocade Issue Frequent I/O abort issues on the ESX host.
    • ONTAP SAN FCoE with Cisco Nexus FDISC error ID could not be acquired for this virtual port
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/ONTAP_SAN_FCoE_with_Cisco_Nexus_FDISC_error_ID_could_not_be_acquired_for_this_virtual_port
      fcp-svm fcp-lif-01-0e down FDISC error - ID could not be acquired for this virtual port. fcp-svm fcp-lif-02-0e down FDISC error - ID could not be acquired for this virtual port. FDISC RJT - FDISC fail...fcp-svm fcp-lif-01-0e down FDISC error - ID could not be acquired for this virtual port. fcp-svm fcp-lif-02-0e down FDISC error - ID could not be acquired for this virtual port. FDISC RJT - FDISC failed because a LS_RJT was received for virtual port 1. 3700) Event:E_DEBUG, length:112, at 722146 usecs after Thu Jan 01 10:01:10 2020 [102] fcoe_mgr_handle_fka(4440): sending cvl to unknown vnport for 1002, 00:a0:98:bc:c7:XX mac:00:a0:98:bc:c7:XX