The following table lists some network error codes, descriptions of problems that the error codes point to, and actions that you can take to fix the problems. For additional information, see the Network Management Guide.
Error code
|
Description
|
Recommended actions
|
|---|
200
|
Unspecified hardware problem.
|
Reseat the network interface card.
If the problem persists, contact Network Appliance Technical Support.
|
201
|
Link not detected.
|
Complete the following steps until you detect a link:
- Ensure that a cable is
connecting the network
interface card to the network.
- Check the cable.
- Check the interface card and
corresponding switch port
setting for a speed mismatch.
- Check for a switch or hub port
problem.
- Reseat the network interface
card.
- If the problem persists, contact
Network Appliance Technical
Support.
|
202
|
A link on an Alteon Gigabit adapter is not detected because of an autonegotiation mismatch.
|
Change the interface configuration or peer switch port configuration so that the settings match.
|
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.
- Change the media type using
the ifconfig command, wait
five seconds, and then restore
the media type to the previous
setting.
- If the problem persists, contact
Network Appliance Technical
Support.
|
208
|
Excessive I/O errors.
|
Complete the following steps:
- Reseat the interface card.
- Check the cables.
- If the problem persists, contact
Network Appliance Technical
Support.
|
209
|
Excessive unsupported protocol packets are being sent to the filer.
|
The problem is not with your filer.
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 filer.
Reconfigure the client.
|
402
|
There is excessive packet loss on the sending side.
|
The problem is not with your filer.
Examine the network and the client for congestion.
|
403
|
There is excessive packet loss on the receiving side.
|
The problem is not with your filer.
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 filer.
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 filer.
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 filer.
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 because of a client or a network that loses packets when loaded.
|
The problem is not with your filer.
- Check your client system for bugs.
- Your network might be overloaded.
- 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 filer.
- Check your client system for bugs.
- Check for a security attack.
|
451
|
There are xcessive 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.
|
