netdiag error codes

Network error codes are generated by the netdiag command. They describe the network problems and suggest the actions that you can take.

The following table lists some network error codes, describes the problems that the error codes point to, and suggests actions that you can take to fix the problems.

Note: Only a small fraction of the possible network error messages are presented in the following table. If you receive any problem code not listed in this chapter, contact your technical support.

Error code	Description	Recommended actions
201	Link not detected.	Complete the following steps until you detect a link: Ensure that a cable is connected between the switch port and your storage system interface, and that both ends are securely attached. Ensure that the switch port and interface are both configured up, and one of the following is true: Autonegotiation is enabled on both sides Autonegotiation is disabled on both sides, and the duplex and speed settings match Because the switch port, cable, or NIC might be faulty, replace them, one-by-one, to locate the fault. If the problem persists, contact your technical support.
203	No link is detected because of a speed mismatch.	Change the interface configuration or peer switch port configuration to match the speed.
204	The interface is not configured up.	Configure the interface up.
205	Duplex mismatch.	Change the interface or peer switch port duplex setting so they match.
206	Link capacity problem.	Upgrade to a faster interface.
207	The interface is not transmitting or receiving.	Complete the following steps: Pull the network cable out from the network interface card. Reinsert the cable. Use ifstat to display statistics. Link errors, such as CRC, are caused by a faulty switch port, cable, or NIC; replace them one-by-one to locate the fault. Out-of-resource errors are caused by heavy loads. If the problem persists, contact your technical support.
208	Excessive I/O errors.	Complete the following steps: Reseat the interface card. Check the cables. If the problem persists, contact your technical support.
209	Excessive unsupported protocol packets are being sent to your storage system.	The problem is not with your storage system. Contact your network administrator to resolve the problem.
301	The IP address and the netmask are inconsistent with the assigned broadcast address.	Change the configuration using the ifconfig command.
302	The broadcast address reaches a larger set of hosts than the standard broadcast computed from the IP address and netmask.	If this behavior is erroneous, change the configuration.
303	There are excessive IP reassembly errors.	Switch from NFS over UDP to NFS over TCP.
401	The TCP window advertised by the client is too small.	The problem is not with your storage system. Reconfigure the client.
402	There is excessive packet loss on the sending side.	The problem is not with your storage system. Examine the network and the client for congestion.
403	There is excessive packet loss on the receiving side.	The problem is not with your storage system. Examine the network and the client for congestion.
404	The average TCP packet size is poor on the receiving side because the network, client, or both are not enabled to support jumbo frames.	The problem is not with your storage system. Enable support for jumbo frames in network devices and the client.
405	The average TCP packet size is poor on the receiving side because of a problem with the network, client, or both.	The problem is not with your storage system. Examine the network and client for configured MTUs.
406	The average TCP packet size is poor on the receiving side because of a client application problem.	The problem is not with your storage system. Examine the client application data transmission strategy.
407	Excessive TCP listen socket drops because the system is overloaded or under security attack.	Contact your network administrator to resolve the problem.
408	There are excessive filtered TCP port drops because the system is under security attack.	Check your network. Contact your network administrator to resolve the problem.
409	There are excessive embryonic TCP connection drops because the system is under security attack or because a client has a bug.	Contact your network administrator to resolve the problem. A packet trace might assist in locating the problem.
410	Excessive TCP checksum errors. These errors can be caused bad hardware on the client, in the network infrastructure (e.g., blade in switch or router), or on the NIC. These errors can also be caused by a bug in the client.	Check your client system for bugs. Replace hardware components until the problem goes away. Contact your network administrator to resolve the problem.
411	There are packets because of a client. Your system might be under a security attack.	The problem is not with your storage system. Check your client system for bugs. Check for a security attack.
451	There are excessive UDP checksum errors.	Switch from NFS over UDP to NFS over TCP.
601	The DNS server is not reachable.	Examine the DNS server and the path to the DNS server.
602	The NIS server is not reachable.	Examine the NIS server and the path to the NIS server.