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.
Applies to Cluster Network Switch (CNS) CN1610 Description For troubleshooting purposes there might be a need to disable and enable a CN1610 switch port
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
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
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
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.
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
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}
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
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.