Search
- Filter results by:
- View attachments
- https://kb.netapp.com/on-prem/ontap/da/SAN/SAN-KBs/FCP_initiator_not_logged_in_on_VTICApplies to Data ONTAP operating in 7-mode Issue Initiators not logged in on unoptimized (or partner) paths.
- https://kb.netapp.com/on-prem/ontap/da/SAN/SAN-KBs/How_to_identify_controller_iSCSI_IQN_in_clustered_Data_ONTAPApplies to ONTAP 9.x SAN Protocol Description This article describes the procedure that should be followed to identify the controller's iSCSI IQN in clustered Data ONTAP.
- https://kb.netapp.com/on-prem/Switches/Brocade-KBs/CRC_errors_and_how_to_resolve_them_with_FC_and_Brocade_switch_running_any_version_of_Fabric_OSApplies to Brocade Switch Fibre Channel Cyclic Redundancy Check (CRC) porterrshow displays increased crc err frames enc crc crc too too bad enc disc link loss loss frjt fbsy c3timeout tx rx in err g_e...Applies to Brocade Switch Fibre Channel Cyclic Redundancy Check (CRC) porterrshow displays increased crc err frames enc crc crc too too bad enc disc link loss loss frjt fbsy c3timeout tx rx in err g_eof shrt long eof out c3 fail sync sig tx rx 0: 7.5m 8.7m 0 0 0 0 0 0 316 30 4 506 612 0 0 0 0 1: 3.2g 716.8m 0 11 11 0 0 0 19 14 8 11 14 0 0 0 0 2: 415.9m 3.4g 1.7m 121.8k 84.2k 85 0 37.5k 59.8k 1.5k 6 9 12 0 0 1.5k 0 Note: The connected device may experience disconnects and/or increased latency
- https://kb.netapp.com/data-mgmt/OTV/VSC_Kbs/VMware_Atomic_Test_and_Set_heartbeats_impact_connectivity_to_storage2022-04-04T12:33:16.355Z cpu1:2097617)NMP: nmp_ThrottleLogForDevice:3872: Cmd 0x89 (0x45bac31031c0, 2097193) to dev "naa.600a09803831364468244e4c5a47494e" on path "vmhba64:C1:T0:L0" Failed: H:0x5 D:0x...2022-04-04T12:33:16.355Z cpu1:2097617)NMP: nmp_ThrottleLogForDevice:3872: Cmd 0x89 (0x45bac31031c0, 2097193) to dev "naa.600a09803831364468244e4c5a47494e" on path "vmhba64:C1:T0:L0" Failed: H:0x5 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0. 2022-04-04T12:43:13.402Z cpu2:2097617)NMP: nmp_ThrottleLogForDevice:3872: Cmd 0x89 (0x45baf1751140, 2097193) to dev "naa.600a09803831364468244e4c5a47494e" on path "vmhba64:C0:T0:L0" Failed: H:0x5 D:0x0 P:0x0 Invalid sense data: 0x0 0x0 0x0.
- https://kb.netapp.com/on-prem/ontap/da/SAN/SAN-KBs/Multiple_new_iSCSI_sessions_are_seen_with_the_same_IQN_but_different_initiator_IPsTue Sep 04 16:18:26 CDT [PRD-NTAP-01: iswti_iscsip_thread: iscsi.warning:warning]: ISCSI: New session request from initiator iqn.1991-05.com.microsoft:prd-app-01.netapp.com, a session from this initia...Tue Sep 04 16:18:26 CDT [PRD-NTAP-01: iswti_iscsip_thread: iscsi.warning:warning]: ISCSI: New session request from initiator iqn.1991-05.com.microsoft:prd-app-01.netapp.com, a session from this initiator already exists. Tue Sep 04 16:20:09 CDT [PRD-NTAP-01: iswti_iscsip_thread: iscsi.warning:warning]: ISCSI: New session request from initiator iqn.1991-05.com.microsoft:prd-app-01.netapp.com, a session from this initiator already exists.
- https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/What_do_invalid_words_errors_mean_and_how_are_they_resolvedAny version of Data OnTap "Invalid words" errors is seen in fibre channel stats for NetApp controller. This article discusses what these errors mean. From the filer side "invalid words" errors are see...Any version of Data OnTap "Invalid words" errors is seen in fibre channel stats for NetApp controller. This article discusses what these errors mean. From the filer side "invalid words" errors are seen when running commands to view FCP adapter stats. Statistics for adapter 0c: Invalid Transmit Words: 1977 Cluster::*> network fcp adapter stats -node <node> -adapter <adapter> Number of adapter resets: 0 Number of frames overrun: - Number of frames underrun: - Invalid words transmitted: 1983
- https://kb.netapp.com/hybrid/FlexPod/UCS_SAN_Boot_Reference_DocumentationWhile most of the documentation is targeted at the Cisco/NetApp partnership program called Flexpod, it is important to note that these documents follow best practices put in place by both NetApp and C...While most of the documentation is targeted at the Cisco/NetApp partnership program called Flexpod, it is important to note that these documents follow best practices put in place by both NetApp and Cisco. If you are unable to find a guide that matches the your current configuration, there are additional guides available at Cisco Flexpod Validated Designs as well as NetApp Validated Designs.
- https://kb.netapp.com/on-prem/Switches/Cisco-KBs/Bad_SFPs_in_Cisco_switchesErrors for a particular port, constant or intermittent latency in a host attached to that port is seen. This could be caused due to hardware issues. Steps to troubleshoot and identify if the issue is ...Errors for a particular port, constant or intermittent latency in a host attached to that port is seen. This could be caused due to hardware issues. Steps to troubleshoot and identify if the issue is due to SFP or cable, is described in this KB article.
- https://kb.netapp.com/on-prem/ontap/da/SAN/SAN-KBs/SAN_host_does_not_failover_I_O_to_alternate_paths_when_one_or_more_paths_are_removed_and_an_RSCN_is_not_receivedIn Windows, if one or more paths to the storage target are removed, I/O hangs indefinitely until the path(s) are restored. The issue can be triggered by the removal of an Active/Optimized or Active/Un...In Windows, if one or more paths to the storage target are removed, I/O hangs indefinitely until the path(s) are restored. The issue can be triggered by the removal of an Active/Optimized or Active/Unoptimized path, and is observed regardless if there are Active/Optimized or Active/Unoptimized paths remaining. Generally, resetting the host port or rebooting the host will allow the host to detect any added paths.
- https://kb.netapp.com/on-prem/ontap/da/SAN/SAN-KBs/What_are_the_parameters_that_control_how_MS_iSCSI_survives_lost_TCP_connections_without_causing_applications_harmDuring transient loss of connection, instead of reporting "Device not available" immediately, the Microsoft iSCSI initiator will try to reconnect to the target and resubmit outstanding SCSI commands. ...During transient loss of connection, instead of reporting "Device not available" immediately, the Microsoft iSCSI initiator will try to reconnect to the target and resubmit outstanding SCSI commands. Note: Even after a Device Removal event is reported the Microsoft iSCSI initiator will still keep trying to reconnect to the target, as defined by the first two registry values, DelayBetweenReconnect and MaxConnectionRetries.
- https://kb.netapp.com/on-prem/Switches/Brocade-KBs/How_to_diagnose_and_resolve_laser_flt_errorsKB provides the solution when switchshow port status is Laser_Flt and the reasons why this happens.