Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 13 results
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Error_The_specified_port_is_not_assigned_to_Default_IPspace_when_adding_a_port_to_an_Interface_Group
      Applies to ONTAP 9.5 IPspace Interface Group (ifgrp) Issue Adding a port to an Interface Group, error appears: ::*> network port ifgrp add-port -node <node_name> -ifgrp a0a -port e0g Error: command fa...Applies to ONTAP 9.5 IPspace Interface Group (ifgrp) Issue Adding a port to an Interface Group, error appears: ::*> network port ifgrp add-port -node <node_name> -ifgrp a0a -port e0g Error: command failed: Specified port is not assigned to Default IPspace.
    • https://kb.netapp.com/on-prem/Switches/NetApp-KBs/How_to_disable_and_enable_a_port_on_a_CN1610_switch
      Applies to Cluster Network Switch (CNS) CN1610 Description For troubleshooting purposes there might be a need to disable and enable a CN1610 switch port
    • https://kb.netapp.com/on-prem/solidfire/hardware_Kbs/AutoSupport_Message__Fibre_channel_port_at_PCI_Slot_x_HBA_Port_x_has_non_online_state_Linkdown
      Applies to NetApp Element software NetApp FC0025 NetApp SF-FCN-01 Issue On NetApp SolidFire Active IQ: (Fibre Channel Warning) Fibre channel port at PCI Slot <x> HBA Port <x> has non-online state Link...Applies to NetApp Element software NetApp FC0025 NetApp SF-FCN-01 Issue On NetApp SolidFire Active IQ: (Fibre Channel Warning) Fibre channel port at PCI Slot <x> HBA Port <x> has non-online state Linkdown
    • https://kb.netapp.com/on-prem/E-Series/Hardware-KBs/Only_one_port_is_responding_on_the_E-Series
      Applies to NetApp E-Series Issue After some switch maintenance only one iSCSI target port is responding to pings Other ports up however are not responding
    • https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/SnapCenter_unable_to_add_SVM_No_connection_could_be_made_because_the_target_machine_actively_refused_it__8145
      Applies to SnapCenter Server (SC) 4.1 Windows Active Directory with GPO Filtering Issue Adding SVM fails with: host No connection could be made because the target machine actively refused it [::1]:814...Applies to SnapCenter Server (SC) 4.1 Windows Active Directory with GPO Filtering Issue Adding SVM fails with: host No connection could be made because the target machine actively refused it [::1]:8145
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Network_port_becomes_unusable_due_to_netif.sfpNotSupported
      Network port becomes unusable due to an unsupported SFP+ or QSFP+ module being installed. Dec 10 17:13:49 [cluster-01:netif.sfpNotSupported:error]: The SFP+ or QSFP+ module (AVAGO AFBR-57F5MZ-NA1 ) in...Network port becomes unusable due to an unsupported SFP+ or QSFP+ module being installed. Dec 10 17:13:49 [cluster-01:netif.sfpNotSupported:error]: The SFP+ or QSFP+ module (AVAGO AFBR-57F5MZ-NA1 ) installed in e0c is not supported with this network interface. The SFP parts number and serial number might not seen in SYSCONFIG -A: 5/23/2024 04:52:07 Node01 ERROR netif.sfpNotSupported: The SFP+ or QSFP+ module (not supported ) installed in e3a is not supported with this network interface.
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Network_interfaces_not_reachable_for_several_minutes_after_storage_failover
      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 ...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/hybrid/StorageGRID/Protocols/The_request_signature_we_calculated_does_not_match_the_signature_you_provided_on_Velero_when_configured_with_StorageGRID
      Velero application reports the following error when attempting to execute the velero backup logs <backup_name> command on client-side The request signature we calculated does not match the signature y...Velero application reports the following error when attempting to execute the velero backup logs <backup_name> command on client-side The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key REST Authentication and SOAP Authentication for details. Additionally, the following error can be seen on the StorageGRID-side on the storage node that receives the request in the bycast.log: to verify signature}
    • https://kb.netapp.com/on-prem/Switches/Broadcom-KBs/faulty_port_in_Brocade_Broadcom_switch
      VMware corruption may occur with flapping switch port causing FC frame drops on target ports. FC switch port is in an 'Offline' state: portshow 01 portDisableReason: None portCFlags: XXX portFlags: XX...VMware corruption may occur with flapping switch port causing FC frame drops on target ports. FC switch port is in an 'Offline' state: portshow 01 portDisableReason: None portCFlags: XXX portFlags: XXXXXX PRESENT U_PORT DISABLED LED LocalSwcFlags: XXX portType: 26.0 POD Port: Port is licensed portState: 2 Offline Protocol: FC portPhys: 5 No_Sync portScn: 2 Offline port generation number: XXXXXX state transition count: XXXX When plugging the SFP into a different port, it works as normal
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Frequent_nfsConnResetAndClose_error_due_to_packet_sent_using_the_wrong_port
      Applies to ONTAP 9 NFS v3 Issue Event log shows frequent nfsConnResetAndClose error messages The reason listed in the error message is Packet is sent using the wrong port: Example: Wed Sep 30 14:31:19...Applies to ONTAP 9 NFS v3 Issue Event log shows frequent nfsConnResetAndClose error messages The reason listed in the error message is Packet is sent using the wrong port: Example: Wed Sep 30 14:31:19 CEST [Node-01: kernel: Nblade.nfsConnResetAndClose:error]: Shutting down connection with the client. Vserver ID is 3; network data protocol is NFS, Rpc Xid 0x-750XXXXX; client IP address:port is 10.10.10.11:300. local IP address is 10.10.10.20; reason is Packet is sent using the wrong port.
    • https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/Cannot_establish_cluster_peering_Data_connection_but_ICMP_is_working
      [?] Mon Mar 28 00:36:28 +0300 [<cluster_name-02>: mgwd: cpeer.xcm.addr.disc.warn:error]: Address discovery failed for peer cluster <UUID>. Reason: Failed to discover remote addresses: Failed to contac...[?] Mon Mar 28 00:36:28 +0300 [<cluster_name-02>: mgwd: cpeer.xcm.addr.disc.warn:error]: Address discovery failed for peer cluster <UUID>. Reason: Failed to discover remote addresses: Failed to contact peer cluster "<cluster_name>" at addresses: <IP>. RPC: Remote system error [from mgwd on node "<cluster_name-02>" (VSID: -3) to mgwd at <IP>].