UNIX for Dummies Questions & Answers

# netstat -in
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
net1 1500 192.168 192.168.0.11 24508 0 12212 112931 2795
lo0 8232 127 127.0.0.1 42 0 42 0 0
atl0* 8232 none none No Statistics Available


as shown above, Opkts & Oerrs of net1 are too big, there maybe some problems on the net card or the lan, so what's it? and how i can resolve them ?

Thanks!

It seems at first glance your problem lies with the configuration of the interface or the switch the system is connected to. Having a lot of output packets is common in a server, I don't believe you have a problem there.




First you must find out what your NIC card is configured for or what your machine is set for in the /etc/system file there could be an entry that states something like the following:

set hme:hme_adv_100autoneg_cap=0
set hme:hme_adv_100fdx_cap=1
set hme:hme_adv_100hdx_cap=0


These settings force the machine to be 100 fullduplex and does not allow the system to autonegotiate.

If these settings are not in the system file, then you can type the following commands to let you know what your system is configured for (you have to be root, and know what interface you are using hme0, le0, ge0)

[root@hostname]$ndd /dev/hme link_mode

[root@hostname]$ndd /dev/hme link_status

[root@hostname]$ndd /dev/hme link_speed

If your response is 1 to all, your machine is at 100fullduplex, if your response to any of these above commands is zero your machine is set to 100/halfduplex

Now that you have your NIC card settings, check with your IT department and find out what the switch is set for which this server is connected to. It looks like your machine is set to 100/full while the switch is set to 100/half. If this does not solve the problem take the machine down to the ok prompt. Run test-all. This runs a PROM level test which includes the NIC card.Or you can run post-results.