IMC纳管S7610
问题背景:
IMC 纳管S7610 出现问题,但是却可以收到设备的trap信息。Debug 看snmp已经响应了,但是出方向抓包没有报文。
结论说明:
Snmp 队列拥塞导致debug可以看到cpu响应但是发包的时候丢弃,导致出方向丢弃。可以配置mib-view进行过滤。
定位过程:
1.
在debug中看 收到request之后做出了相应
*Aug 9 09:36:40:278 2019 qiaosi-7606 SNMP/7/PACKET_SRC: -MDC=1;
Packet received from 10.8.4.178 via UDP
*Aug 9 09:36:40:278 2019 qiaosi-7606 SNMP/7/PACKET: -MDC=1;
Get request
Request ID: 1893867743
Error status: 0
Error index: 0
*Aug 9 09:36:40:278 2019 qiaosi-7606 SNMP/7/VBLIST: -MDC=1;
hh3cOnuEncryptMan.21798:
*Aug 9 09:36:40:279 2019 qiaosi-7606 SNMP/7/PACKET: -MDC=1;
Response
Request ID: 1893867743
Error status: 0
Error index: 0
2.
3. 设备在处理ONU节点时(耗时很长),网管也还在请求其它节点,导致snmp队列积压。
<qiaosi-7606>dis udp verbose
Connection info: Src = 0.0.0.0:161, Dst = 0.0.0.0:0
Location: slot 1 cpu 0
Creator: snmpd[472]
State: N/A
Options: SO_REUSEPORT
Error: 0
Receiving buffer(cc/hiwat/lowat/drop/state): 42223 / 42240 / 1 / 16328076 / N/A
Sending buffer(cc/hiwat/lowat/state): 0 / 159 / 52 / N/A
Type: 2
Protocol: 17
Inpcb flags: INP_RECVDSTADDR INP_REUSEPORT INP_SYNCPCB
Inpcb extflag: N/A
Inpcb vflag: INP_IPV4
TTL: 255(minimum TTL: 0)
Send VRF: 0xffff
Receive VRF: 0xffff
3.
IMC读取节点用的get-next,现场读取的节点是读取RS485接口,但是现场用的ONU没有这种接口,所以IMC会已知读,直到读取到下一个值,现场有3K+的onu,都遍历一遍导致snmp队列拥塞。这里有一点,display packet-drop是看不到拥塞丢包的,在debug里看到是通过udp发送的,所以display udp verbose看到的丢包。
读取记录如下:
*Aug 28 16:18:23:483 2019 qiaosi-7606 SNMP/7/VBLIST: -MDC=1;
hh3cOnuRS485SessionNextIndex.18654.1: 0
*Aug 28 16:18:23:483 2019 qiaosi-7606 SNMP/7/VBLIST: -MDC=1;
hh3cOnuRS485SessionNextIndex.18654.1: 0
*Aug 28 16:18:23:484 2019 qiaosi-7606 SNMP/7/VBLIST: -MDC=1;
hh3cOnuRS485SessionNextIndex.18654.1: 0
*Aug 28 16:18:23:484 2019 qiaosi-7606 SNMP/7/VBLIST: -MDC=1;
hh3cOnuRS485SessionNextIndex.18654.1: 0
*Aug 28 16:18:23:484 2019 qiaosi-7606 SNMP/7/PACKET_DES: -MDC=1;
Packet sent to 10.8.4.178 via UDP
现场实际读取的节点是如下四个
Name: hh3cOnuRS485PropertiesTable
OID: 1.3.6.1.4.1.25506.2.42.1.5.31
Full path: iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).hh3c(25506).hh3cCommon(2).hh3cEpon(42).hh3cEponMibObjects(1).hh3cEponOnuMan(5).hh3cOnuRS485PropertiesTable(31)
Module: HH3C-EPON-MIB
Name: hh3cOnuRS485SessionSummaryTable
OID: 1.3.6.1.4.1.25506.2.42.1.5.32
Full path: iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).hh3c(25506).hh3cCommon(2).hh3cEpon(42).hh3cEponMibObjects(1).hh3cEponOnuMan(5).hh3cOnuRS485SessionSummaryTable(32)
Module: HH3C-EPON-MIB
Name: hh3cOnuRS485SessionTable
OID: 1.3.6.1.4.1.25506.2.42.1.5.33
Full path: iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).hh3c(25506).hh3cCommon(2).hh3cEpon(42).hh3cEponMibObjects(1).hh3cEponOnuMan(5).hh3cOnuRS485SessionTable(33)
Module: HH3C-EPON-MIB
Name: hh3cOnuRS485SessionErrInfoTable
OID: 1.3.6.1.4.1.25506.2.42.1.5.34
Full path: iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).hh3c(25506).hh3cCommon(2).hh3cEpon(42).hh3cEponMibObjects(1).hh3cEponOnuMan(5).hh3cOnuRS485SessionErrInfoTable(34)
Module: HH3C-EPON-MIB
可以通过mib-view过滤掉这四个节点来解决问题:
snmp-agent mib-view included eponEx iso
snmp-agent mib-view excluded eponEx hh3cOnuRS485PropertiesTable
snmp-agent mib-view excluded eponEx hh3cOnuRS485SessionSummaryTable
snmp-agent mib-view excluded eponEx hh3cOnuRS485SessionTable
snmp-agent mib-view excluded eponEx hh3cOnuRS485SessionErrInfoTable
snmp-agent community read public mib-view eponEx
该案例暂时没有网友评论
✖
案例意见反馈
亲~登录后才可以操作哦!
确定你的邮箱还未认证,请认证邮箱或绑定手机后进行当前操作