Search
- Filter results by:
- View attachments
- https://kb.netapp.com/on-prem/Switches/Broadcom-KBs/unk_performance_impact_on_ISL_port_due_to_high_deskew_value2020/09/22-15:29:31, [C4-1044], 349, CHASSIS, INFO, BrocadeG610, Trunk performance impact on port (20) due to high deskew value. [TRUNK_PERF:11 percent, Deskew:5684] You may also see the following err...2020/09/22-15:29:31, [C4-1044], 349, CHASSIS, INFO, BrocadeG610, Trunk performance impact on port (20) due to high deskew value. [TRUNK_PERF:11 percent, Deskew:5684] You may also see the following error messages being reported in EMS log to remote disks or ATTO bridges as a result of this issue You may also see the following reported in the Active IQ intermittently as a result of this issue
- https://kb.netapp.com/on-prem/ontap/mc/MC-KBs/How_to_troubleshoot_a_down_ISL_port_in_Fabric_MetroCluster_CiscoThis article is not intended as a comprehensive troubleshooting guide, but as a tool to assist in ISL link troubleshooting. Whenever troubleshooting ISL link a number of factors should be considered: ...This article is not intended as a comprehensive troubleshooting guide, but as a tool to assist in ISL link troubleshooting. Whenever troubleshooting ISL link a number of factors should be considered: What is the distance of the ISL links? Have the ISL ports been configured correctly as per the installation guide? What type of ISL is being used? What additional components are in the link? What is the health of the components on the link?
- https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/ISL_port_might_be_faulty_on_NX5596system health alert show output with the following errors: The cable used to connect switch "switch(sn#) /Ethernet1/41" to the ISL port might be faulty. The cable used to connect switch "switch(sn#)/E...system health alert show output with the following errors: The cable used to connect switch "switch(sn#) /Ethernet1/41" to the ISL port might be faulty. The cable used to connect switch "switch(sn#)/Ethernet1/42" to the ISL port might be faulty. The cable used to connect switch "switch(sn#) /Ethernet1/43" to the ISL port might be faulty. The cable used to connect switch "switch(sn#)/Ethernet1/44" to the ISL port might be faulty. For the port-channel, please check each individual link.
- https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/CLUSTER_NETWORK_DEGRADED_Autosupport_Messages_for_ISL_issues=-=-=-=-=-=Thu Feb 18 2021, 15:13:31 CET -- interface e0b (13 days, 4 hours, 22 minutes, 23 seconds) -- Error symbol: 83 | Illegal symbol: 53 | Bus overruns: 0 -- interface e0d (13 days, 4 hours, 22 m...=-=-=-=-=-=Thu Feb 18 2021, 15:13:31 CET -- interface e0b (13 days, 4 hours, 22 minutes, 23 seconds) -- Error symbol: 83 | Illegal symbol: 53 | Bus overruns: 0 -- interface e0d (13 days, 4 hours, 22 minutes, 15 seconds) -- Error symbol: 55 | Illegal symbol: 32 | Bus overruns:
- https://kb.netapp.com/on-prem/ontap/mc/MC-KBs/Brocade__How_to_perform_diagnostics_on_ISL_E_PortsThis article describes the procedure to perform diagnostics on ISL E Ports with ISL speeds of 8gb or higher. Note: The distance is based on the roundtrip time of a frame and can differ from the physic...This article describes the procedure to perform diagnostics on ISL E Ports with ISL speeds of 8gb or higher. Note: The distance is based on the roundtrip time of a frame and can differ from the physical distance due to WDM equipment or patch panels. D_Port diagnostics can be run on productive switches, though the ISLs on the fabric undergoing testing will not pass data traffic for the duration of the test.
- https://kb.netapp.com/on-prem/Switches/Brocade-KBs/Zone_conflict_reported_on_ISL_port_of_Brocade_switchSwitch show output provides a segmented and zone conflict at the ISL port after the power maintenance: Switch show output provides a segmented and zone conflict for the ISL port with out any activity ...Switch show output provides a segmented and zone conflict at the ISL port after the power maintenance: Switch show output provides a segmented and zone conflict for the ISL port with out any activity being performed: 21 21 011500 id N16 Online FC E-Port segmented,10:0x:dx:1x:cc:8b:50:6x (zone conflict) Duplicate entries in zone error reported in errdump, issue persisted even after clearing the duplicate zones:
- https://kb.netapp.com/on-prem/Switches/Brocade-KBs/IO_PERF_IMPACT_and_IO_LATENCY_CLEAR_events_reported_on_E-Ports_on_Brocade_Switch2022/01/27-10:59:24:421723, [MAPS-1003], 883769/797720, SLOT 2 | FID 128, WARNING, NETM_X6_101_FAB1, slot10 port47, E-Port 10/47, Condition=ALL_PORTS(DEV_LATENCY_IMPACT==IO_PERF_IMPACT), Current Value...2022/01/27-10:59:24:421723, [MAPS-1003], 883769/797720, SLOT 2 | FID 128, WARNING, NETM_X6_101_FAB1, slot10 port47, E-Port 10/47, Condition=ALL_PORTS(DEV_LATENCY_IMPACT==IO_PERF_IMPACT), Current Value:[DEV_LATENCY_IMPACT, IO_PERF_IMPACT, (10 ms Frame Delay) ], RuleName=defALL_PORTS_IO_PERF_IMPACT_UNQUAR, Dashboard Category=Fabric Performance Impact., raslogAction.c, line: 170, comp:md, ltime:2022/01/27-10:59:24:421570
- https://kb.netapp.com/on-prem/ontap/mc/MC-KBs/How_to_troubleshoot_an_ISL_down_in_Fabric_MetroCluster_BrocadeThis article is not intended as a comprehensive troubleshooting guide, but as a tool to assist in ISL link troubleshooting. Whenever troubleshooting ISL link a number of factors should be considered: ...This article is not intended as a comprehensive troubleshooting guide, but as a tool to assist in ISL link troubleshooting. Whenever troubleshooting ISL link a number of factors should be considered: - What is the distance of the ISL links? - Have the ISL ports been configured correctly as per the installation guide? - What type of ISL is being used? - What additional components are in the link? - What is the health of the components on the link?
- https://kb.netapp.com/on-prem/ontap/Perf/Perf-KBs/High_write_latency_on_MetroCluster-IP_during_heavy_peak_of_write_workloadApplies to Ontap 9 MCIP Write latency Issue High write latency based on Back-2-Back Consistency points during heavy write workload peaks (time in UTC).
- https://kb.netapp.com/on-prem/ontap/mc/MC-KBs/MetroCluster_ISL_trunk_requirements_and_common_issues_BrocadeApplies to MetroCluster Brocade switches A trunk on the ISLs of a Brocade switch in a MetroCluster backend does not form correctly Common Issue: The trunk does not form when attempting to create it on...Applies to MetroCluster Brocade switches A trunk on the ISLs of a Brocade switch in a MetroCluster backend does not form correctly Common Issue: The trunk does not form when attempting to create it on Brocade switches: The trunkshow output is similar to the following: 2: 11-> 11 10:00:50:eb:1a:20:83:96 5 deskew 16 MASTER On a correctly formed trunk, the output is similar to this: 1: 10-> 10 10:00:50:eb:1a:20:83:96 5 deskew 15 MASTER 11-> 11 10:00:50:eb:1a:20:83:96 5 deskew 16
- https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/Communication_to_remote_volume_downApplies to E-series Asynchronous Remote Volume Mirroring (ARVM) Issue Storage Manager reports the following error in the GUI : Data could not be loaded from the storage array. One possible cause is th...Applies to E-series Asynchronous Remote Volume Mirroring (ARVM) Issue Storage Manager reports the following error in the GUI : Data could not be loaded from the storage array. One possible cause is the object on which you you were performing the operation no longer exists. Other possible causes include network issues, inability to communicate with the controller, or loss of power to the storage array. Check these causes and then retry the operation.
