zabbix Server 4.0 监控TCP的12种状态
作者：尹正杰
版权声明：原创作品，谢绝转载！否则将追究法律责任。
大家对TCP三次握手比较熟悉了，都知道当发生DOSS攻击时，客户端发送SYN给服务端后，服务端响应SYN+ACK，此时客户端就不回应服务端ACK啦（如果正常建立三次握手客户端会回应ACK，表示三次握手建立成功，服务端状态变为ESTABLISED状态，不了解的小伙伴可以自行百度。），这会导致服务端的SYN-RCVD状态偏多。因此监控TCP的连接数还是很有必要的，当某个SYN-RCVD偏多时，我们就可能猜测服务有异常了，需要人工介入处理。接下来我们就看看zabbix是如何监控TCP的11中状态的。
一.TCP状态扫盲
1>.三次握手
参考链接：https://baike.baidu.com/item/%E4%B8%89%E6%AC%A1%E6%8F%A1%E6%89%8B/5111559?fr=aladdin。
2>.使用netstat命令工具查看TCP的状态
ESTABLISHED
SYN_SENT
SYN_RECV
FIN_WAIT1
FIN_WAIT2
TIME_WAIT
CLOSE
CLOSE_WAIT
LAST_ACK
LISTEN
CLOSING
UNKNOWN
TCP的12种状态
3>.命令行中查看服务器TCP的某种状态
[root@node102.yinzhengjie.org.cn ~]# netstat -ant | grep -c LISTEN[root@node102.yinzhengjie.org.cn ~]#
二.zabbix监控TCP状态案例并自定义模板
1>.在zabbix agent端自定义key并重启服务
[root@node102.yinzhengjie.org.cn ~]# cat /etc/zabbix/zabbix_agentd.d/TCP_STATUS.conf
UserParameter=TCP_STATUS[*],netstat -ant | grep -c $
[root@node102.yinzhengjie.org.cn ~]#
[root@node102.yinzhengjie.org.cn ~]# systemctl restart zabbix-agent
[root@node102.yinzhengjie.org.cn ~]#
[root@node102.yinzhengjie.org.cn ~]# systemctl status zabbix-agent
● zabbix-agent.service - Zabbix Agent
Loaded: loaded (/usr/lib/systemd/system/zabbix-agent.service; enabled; vendor preset: disabled)
Active: active (running) since Tue -- :: PDT; 4s ago
Process: ExecStop=/bin/kill -SIGTERM $MAINPID (code=exited, status=/SUCCESS)
Process: ExecStart=/usr/sbin/zabbix_agentd -c $CONFFILE (code=exited, status=/SUCCESS)
Main PID: (zabbix_agentd)
CGroup: /system.slice/zabbix-agent.service
├─ /usr/sbin/zabbix_agentd -c /etc/zabbix/zabbix_agentd.conf
├─ /usr/sbin/zabbix_agentd: collector [idle sec]
├─ /usr/sbin/zabbix_agentd: listener # [waiting for connection]
├─ /usr/sbin/zabbix_agentd: listener # [waiting for connection]
├─ /usr/sbin/zabbix_agentd: listener # [waiting for connection]
└─ /usr/sbin/zabbix_agentd: active checks # [idle sec]May :: node102.yinzhengjie.org.cn systemd[]: Starting Zabbix Agent...
May :: node102.yinzhengjie.org.cn systemd[]: PID file /run/zabbix/zabbix_agentd.pid not readable (yet?) after start.
May :: node102.yinzhengjie.org.cn systemd[]: Started Zabbix Agent.
[root@node102.yinzhengjie.org.cn ~]#
[root@node102.yinzhengjie.org.cn ~]# systemctl restart zabbix-agent
2>.服务端验证zabbix agent自定义的key是否生效
[root@node101.yinzhengjie.org.cn ~]# yum -y install zabbix-get
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
epel/x86_64/metalink | 6.0 kB ::
* base: mirrors.aliyun.com
* epel: mirrors.tuna.tsinghua.edu.cn
* extras: mirrors.aliyun.com
* updates: mirrors.aliyun.com
base | 3.6 kB ::
epel | 4.7 kB ::
extras | 3.4 kB ::
mysql-connectors-community | 2.5 kB ::
mysql-tools-community | 2.5 kB ::
mysql56-community | 2.5 kB ::
updates | 3.4 kB ::
zabbix | 2.9 kB ::
zabbix-non-supported | B ::
(/): extras//x86_64/primary_db | kB ::
epel/x86_64/primary_db FAILED
https://mirrors.tuna.tsinghua.edu.cn/epel/7/x86_64/repodata/b46e7947260ac0114fc1b48c782d12377659fe2b8f565a55bcab0cf98b124aa1-primary.sqlite.bz2: [Errno 14] HTTPS Error 404 - Not Found ] 0.0 B/s | 0 B --:--:-- ETA
Trying other mirror.
To address this issue please refer to the below wiki article https://wiki.centos.org/yum-errorsIf above article doesn't help to resolve this issue please use https://bugs.centos.org/.(/): mysql-tools-community/x86_64/primary_db | kB ::
(/): epel/x86_64/updateinfo | kB ::
(/): updates//x86_64/primary_db | 4.2 MB ::
(/): epel/x86_64/primary_db | 6.7 MB ::
Resolving Dependencies
--> Running transaction check
---> Package zabbix-get.x86_64 :4.0.-.el7 will be installed
--> Finished Dependency ResolutionDependencies Resolved==================================================================================================================================================================================================================================
Package Arch Version Repository Size
==================================================================================================================================================================================================================================
Installing:
zabbix-get x86_64 4.0.-.el7 zabbix kTransaction Summary
==================================================================================================================================================================================================================================
Install PackageTotal download size: k
Installed size: 1.1 M
Downloading packages:
zabbix-get-4.0.-.el7.x86_64.rpm | kB ::
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
Installing : zabbix-get-4.0.-.el7.x86_64 /
Verifying : zabbix-get-4.0.-.el7.x86_64 / Installed:
zabbix-get.x86_64 :4.0.-.el7 Complete!
[root@node101.yinzhengjie.org.cn ~]#
[root@node101.yinzhengjie.org.cn ~]# yum -y install zabbix-get
[root@node101.yinzhengjie.org.cn ~]# zabbix_get -s node102.yinzhengjie.org.cn -k TCP_STATUS[LISTEN] #需要注意的是:这样取值其实在客户端是以zabbix用户进行取值操作，有些命令需要root用户权限才能执行，因此我们要考虑命令权限的问题哟！[root@node101.yinzhengjie.org.cn ~]#
3>.在zabbix web页面中创建模板
4>.填写相应参数并添加模板
5>.模板添加成功
6>.为模板添加监控项（item）
7>.监控ESTABLISHED状态
8>.克隆上述操作，将其他11中状态监控起来
9>.TCP的12中状态照单全收
三.使用自定义模板
1>.配置主机的监控信息
2>.链接我们自定义的模板
3>.自定义zabbix监控项
4>.刷新配置并查看最新数据
[root@node101.yinzhengjie.org.cn ~]# zabbix_server -R config_cache_reload #在zabbix server端刷新一下配置
zabbix_server []: command sent successfully
[root@node101.yinzhengjie.org.cn ~]#
、
