这是一件很奇怪的事情。我注意到我的一个名称服务器抱怨一些出站拥塞,而且它似乎与出站路径上接口丢弃的增加有关。一目了然,对吧?当我仔细观察时,我注意到系统范围的计数器在增加,但每个接口的计数器没有增加:
# snmpbulkwalk -v2c -cexample localhost 1.3.6.1.2.1.4.31 | grep Discards
IP-MIB::ipSystemStatsInDiscards.ipv4 = Counter32: 0
IP-MIB::ipSystemStatsInDiscards.ipv6 = Counter32: 0
IP-MIB::ipSystemStatsOutDiscards.ipv4 = Counter32: 14856
IP-MIB::ipSystemStatsOutDiscards.ipv6 = Counter32: 0
IP-MIB::ipIfStatsInDiscards.ipv6.1 = Counter32: 0
IP-MIB::ipIfStatsInDiscards.ipv6.2 = Counter32: 0
IP-MIB::ipIfStatsInDiscards.ipv6.3 = Counter32: 0
IP-MIB::ipIfStatsInDiscards.ipv6.4 = Counter32: 0
IP-MIB::ipIfStatsInDiscards.ipv6.5 = Counter32: 0
IP-MIB::ipIfStatsInDiscards.ipv6.6 = Counter32: 0
IP-MIB::ipIfStatsOutDiscards.ipv6.1 = Counter32: 0
IP-MIB::ipIfStatsOutDiscards.ipv6.2 = Counter32: 0
IP-MIB::ipIfStatsOutDiscards.ipv6.3 = Counter32: 0
IP-MIB::ipIfStatsOutDiscards.ipv6.4 = Counter32: 0
IP-MIB::ipIfStatsOutDiscards.ipv6.5 = Counter32: 0
IP-MIB::ipIfStatsOutDiscards.ipv6.6 = Counter32: 0
我对这些计数器的理解是,这些SystemStats
计数器反映了整个系统的统计数据(总计),但这似乎并非如此。看一下 MIB 似乎证实了我对这个问题的记忆:
ipSystemStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF IpSystemStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The table containing system wide, IP version specific
traffic statistics. This table and the ipIfStatsTable
contain similar objects whose difference is in their
granularity. Where this table contains system wide traffic
statistics, the ipIfStatsTable contains the same statistics
but counted on a per-interface basis."
::= { ipTrafficStats 1 }
有人遇到过这种情况吗?试图确定这是否应该归咎于 Broadcom NIC,或者我是否可以在这里学到一些新东西。作为参考,eth2 和 eth3 是绑定的,但所有三个接口在上表中都有自己的计数器。
- 机壳:戴尔r620
- 操作系统:RHEL6
- 核心:更新日志
网卡信息:
# dmesg | grep Ethernet
tg3 0000:01:00.0: eth0: attached PHY is 5720C (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
tg3 0000:01:00.1: eth1: attached PHY is 5720C (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
tg3 0000:02:00.0: eth2: attached PHY is 5720C (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
tg3 0000:02:00.1: eth3: attached PHY is 5720C (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
# ethtool -i eth3
driver: tg3
version: 3.137
firmware-version: FFV7.8.53 bc 5720-v1.32
bus-info: 0000:02:00.1
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no