But the general problem is not directly overlooked> Carbon Miao appear when the server will be different in English remind, there are different questions have different English Carbon Miao know in order to remind Carbon Miao appear in English corresponds to what the server appear to remind the Carbon Miao, in fact, not difficult, according to our years of experience of some of the common reference for all server controls the general type Carbon Miao remind remind eth1: too much work at interrupt, intrstatus = 0x0001 implications of this reminder. a card interrupt cry too much. If once can be ignored only occasionally, but this article reminded often, or if the focus on the emergence related to the possibility that more may need to be dealt with. more possibilities, such as card function; server function; network invasion .. so ipvs: incoming icmp: failed checksum from 61.172.0.x! server receives a check and the icmp packet Carbon Miao such packets may be illegal garbage generated data, but From now, the server receives the data as it is many more. are generally ignored in the general work of the special circumstances a proxy server to forward thousands of packets per second. Carbon Miao received several packets will not affect the normal work, which I asked a class of up to remind the net: n messages suppressed. server ignores the n data packets. and a reminder on a similar server receives the data packet is considered useless junk data in the data and such data are mostly produced by the invasion of a program, if the reminder of this relatively small when n is negligible, but often, or if the data over a long time there three such reminders. it is likely that the server has been invaded garbage data bandwidth class the udp: bad checksum. from 221.200.xx: 50279 to 218.62.xx: 1155 ulen 24udp: short packet: 218.2.xx: 3072 3640/217 to 222.168.xx: 57596218.26.131.x sent an invalid icmp type 3, code 13 error to a broadcast: 0.1.0.4 on eth0 Carbon Miao server receives a packet, respectively for the udp checksum Carbon Miao; too short udp packets; a Carbon Barthelemy icmp type data such information generally also illegal under the resulting kernel: conntrack_ftp: partial 227 2205426703 +13 ftp_nat: partial packet 2635716056/20 in 2635716048/2635716075 server ftp protocol in maintaining a connection error, such as many reminders can generally ignore thereset"> Network Communications serious error to remind netdev watchdog: eth1: transmit timed outeth1: link downeth1 : link up, 10mbps, half-duplex, lpa 0x0000eth2: link up, 100mbps, full-duplex, lpa 0x41e1setting full-duplex based on mii # 24 link partner capability of 45e1 these reminders is a serious problem in network communication occurs only when Impeding a relationship base and network disconnection, which represent a few to remind the meaning of a piece of card to transfer data out; LAN connection down; network card to connect up, connection speed 10/100mbps, full / half duplex, which take the written reminder to the last three lines compare similar occurrence of such reminders should be noted that the network connection status for processing!!! nic link is up 100 mbps full duplex case and kernel: eth1: link up, ... the same refers to a block NIC response to the connection speed is generally considered did not say which card down, but consecutive response card communication speed is a problem if the cable is disconnected you can ignore the normal kind of information eth0: transmit timed out, status 0000, phy status 786d ,resetting ... eth0:resetnot complete yet. trying harder. the first to send data failed to remind the card off, reset the card. The second reminder card reset is not successful. ... these alerts are serious communication problems eth1: transmit error, tx status register 82. probably a duplex mismatch. see documentation / networking / vortex.txt flags; bus-master 1, dirty 9994190 (14) current9994190 (14) transmit list 00000000 vs. f7171580. 0: @ f7171200 length 800001e6 status 000101e6 1: @ f7171240 length 8000008c status 0001008c .... this is a 3com network card to remind unique. feel if the volume is not there, then it will not affect very serious now see one-dimensional solution is to replace the server's network card 3com network card is feeling some of the problems ... server alarm program to remind 0001 # # wmpcheckv001 # # 2005-04-13_10: 10:01 found. (arp spoofing sniffer)! ip: 183 mac: 5 0002 # # wmpcheckv001 # # 2005-04-07_01: 53:32 found. (mac_incomplete)! ip: 173mac_incomplete: 186 0003 # # wmpcheckv001 # # 2005-04-17_16: 25:11 found. ( high_synsent)! totl: 4271 synsent: 3490 0004 # # wmpcheckv001 # # 20 ...... This is caused by the alarm reminder program. detailed information needed for alarm program clients receive real-time. For details, please see "alarm module and log"