Search
- Filter results by:
- View attachments
- https://kb.netapp.com/on-prem/E-Series/Management-Apps-KBs/NET_SETUP_ERROR_reported_in_the_Recovery_GuruApplies to All E-Series Controllers All E-Series Firmware Issue NET_SETUP_ERROR is reported in the Recovery Guru Indicates an Ethernet configuration conflict, where both controllers have the same subn...Applies to All E-Series Controllers All E-Series Firmware Issue NET_SETUP_ERROR is reported in the Recovery Guru Indicates an Ethernet configuration conflict, where both controllers have the same subnet
- https://kb.netapp.com/on-prem/ontap/Perf/Perf-KBs/High_network_LIF_bandwidth_utilization_or_S3_target_load_due_to_FabricPoolApplies to ONTAP 9.2 or newer ONTAP S3 Server FabricPool Issue High Intercluster LIF throughput 100% ethernet port utilization from LIFS used for FabricPool cloud tiering The WAN pipe may be saturated...Applies to ONTAP 9.2 or newer ONTAP S3 Server FabricPool Issue High Intercluster LIF throughput 100% ethernet port utilization from LIFS used for FabricPool cloud tiering The WAN pipe may be saturated to the cold tier due to the high tiering throughput coming from ONTAP Files may be unavailable under archive paths or jobs may fail which access those jobs. ONTAP nodes with disk aggregates and ONTAP S3 server hosting FabricPool may see high disk utilization and latency.
- https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Network_interfaces_not_reachable_for_several_minutes_after_storage_failoverApplies to ONTAP Issue After takeover/giveback or upgrade, clients lose network access to resources on the storage controller Some of the LIFs become unreachable via ping The issue resolves by itself ...Applies to ONTAP Issue After takeover/giveback or upgrade, clients lose network access to resources on the storage controller Some of the LIFs become unreachable via ping The issue resolves by itself after a few minutes
- https://kb.netapp.com/on-prem/ontap/da/SAN/SAN-KBs/ONTAP_error_inconsistency_between_TCP_metadata_and_socket_send_bufferEMS error tcp.conn.inconsistent Problem description Syslog Translator Event Details : tcp.conn.inconsistent see also EMS Event catalogue page 1926 node run -node <node> netstat -s -p tcp network tunin...EMS error tcp.conn.inconsistent Problem description Syslog Translator Event Details : tcp.conn.inconsistent see also EMS Event catalogue page 1926 node run -node <node> netstat -s -p tcp network tuning tcp show event log show -severity ERROR tcp.conn.inconsistent: Inconsistency between TCP metadata and the socket send buffer occurred for the connection with local address and remote address . The inconsistency occurred while processing "[cc_cong_signal:506]". The connection is "NOT Reset".
- https://kb.netapp.com/on-prem/ontap/Perf/Perf-KBs/Transfer_speeds_not_hitting_10_Gigabit_maximumApplies to FAS 2500 series FAS 2600 series FAS 2700 series Issue Transfer speeds between an application and ONTAP, such as Hyper-V cluster disks, appears to be much slower than it should be Server sho...Applies to FAS 2500 series FAS 2600 series FAS 2700 series Issue Transfer speeds between an application and ONTAP, such as Hyper-V cluster disks, appears to be much slower than it should be Server should be utilizing a 10Gigabit connection, but transfer speeds are around 100 MBps on average, and recorded throughput of between 150-350 MBps
- https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Both_ports_down_on_a_10Gb_Ethernet_cardBoth ports are physically connected to different switches and different networks ERROR net.ifgrp.lacp.link.inactive: ifgrp a1d, port e3a has transitioned to an inactive state. ERROR net.ifgrp.lacp.lin...Both ports are physically connected to different switches and different networks ERROR net.ifgrp.lacp.link.inactive: ifgrp a1d, port e3a has transitioned to an inactive state. ERROR net.ifgrp.lacp.link.inactive: ifgrp a1d, port e3b has transitioned to an inactive state. ::> net port ifgrp show -node <node_name> -ifgrp <ifgrp_name> -instance ::> net port show -node <node_name> -port <port_name> -instance Switch port SFP re-seating/replacing to no avail Using different switch port to no avail