centos monitor network traffic

/mailtmp.txtecho "$ $" > $FILEDos2unix-k $FILEMail-s "$" $ #chmod 755 sendmail.sh#chown Zabbix.zabbix sendmail.sh#touch/tmp/mailtmp.txt#chmod 755/tmp/mailtmp.txt#chown Zabbix.zabbix/tmp/mailtmp.txtConfigure Web pagesCreate Media typeManage –> Alarm Media type –> Create media typeClick Update when you are done with the icon, and you will see the type of email you just created in the alarm media typeAdding an alarm medium to the userHere to Admin user for example Management –> user –> Click AdminC

confirmation, the RedHat OS has a compatibility bug in the support of the Broadcom 5709 Nic drive bnx2-in some special cases when the business data traffic is too large (that is, when the network port load is too large ), there is a small probability that the NIC will fail and the service will be interrupted. for details, refer to RedHat's description of this problem: The image description shows that this

Recently, a number of Cisco ucs c Series servers have been added. After two weeks of deployment and installation, the server can finally be tested. This document briefly introduces the network configuration of the Operating System (centos 6) in the Cisco UCS server. It can be simply considered that this article describes the network configuration of a physical se

remember that even if your machine is a light-load Web server, there is a large number of dead sockets and memory overflow risk, fin-wait-2 is less dangerous than fin-wait-1, Because it can only eat up to 1.5K of memory, but they have a longer lifetime.With such an optimized configuration, your server's TCP concurrency will increase significantly. The above configuration is for reference only, for the production environment please according to their actual situation.Turn fromLinux (

Problems with the compatibility between CentOS and Broadcom 5709 that cause service network interruptions I. symptom 1: a machine in the development team is down (neither ping nor ssh ), I can see from the remote management port that the machine B is not mounted. I log in and can't ping any IP address, and the system log does not report an error. Finally, I restarted the NIC AND THE machine went back to nor

, it stops there, stating that the boot was successful and then going to the client to perform the command testExecute the following command on the 192.168.0.129 (client)#qperf-T--use_bits_per_sec 192.168.0.91 TCP_BWBW = 93.7 Mb/sec--------->>> This is the network bandwidthExecute the following command on the 192.168.0.129 (client)#qperf-T--use_bits_per_sec 192.168.0.91 Tcp_latLatency = 187us--------->>> This is n