ZABBIX优化、如配置文件优化、后台数据库优化……
3 篇帖子 分页: 1 / 1
帖子lynnpierre » 2018年 8月 24日 17:00 星期五
场景:监控专线工作状态
问题:端口监控无法感知到对端的链接是否正常,手工做法是ping对端的接口IP地址
方法:因在设备上开启了NQA单向检测,试图抓紧NQA状态来监控专线状态
华为官方支持信息:
OID:1.3.6.1.4.1.2011.5.25.111.4.1.1.3
节点名称:nqaResultsCompletions
数据类型:INTEGER
noResult(0)
success(1)
failure(2)
最大访问权限:Read-only
含义:测试例成功执行的状态。
实现规格:实现与MIB文件定义一致。
帖子lynnpierre » 2018年 8月 27日 09:17 星期一
不知道怎么上传图片,不知道是否没有权限。而帖子好像又无法再重新编辑了,见谅!
提示:“对不起,您的附件限额已经用完了。”
帖子lynnpierre » 2018年 8月 28日 16:06 星期二
根据资料《net-snmp中载入第三方mib库》所述https://blog.csdn.net/qq_27204267/article/details/51679191

在CSDN上找到一份老的华为MIB文件后,将需要的NQA-MIB.mib导入到/usr/share/snmp/mibs目录下。
使用第一种方法,将mibs +NQA-MIB添加到snmp.conf中,重启snmp服务后不生效,查询snmp.conf发现添加的配置丢失,引向另一问题;
因此试用第二种方法,使用环境变量
MIBS=+CISCO-RHINO-MIB:SOME-OTHER-SPIFFY-MIB
export MIBS
然后执行# snmpget -v2c -c public host 1.3.6.1.4.1.2011.5.25.111.4.1.1.3
结果如下:
代码: 全选
……
Cannot adopt OID in NQA-MIB: nqaPppoeStatsTable ::= { nqaStats 9 }
Cannot adopt OID in NQA-MIB: nqaPathJitterStatsTable ::= { nqaStats 8 }
Cannot adopt OID in NQA-MIB: nqaPathMtuStatsTable ::= { nqaStats 7 }
Cannot adopt OID in NQA-MIB: nqaMtracertStatsTable ::= { nqaStats 6 }
Cannot adopt OID in NQA-MIB: nqaMpingStatsTable ::= { nqaStats 5 }
Cannot adopt OID in NQA-MIB: nqaFTPStatsTable ::= { nqaStats 4 }
Cannot adopt OID in NQA-MIB: nqaJitterStatsTable ::= { nqaStats 3 }
Cannot adopt OID in NQA-MIB: nqaHTTPStatsTable ::= { nqaStats 2 }
Cannot adopt OID in NQA-MIB: nqaResultsTable ::= { nqaStats 1 }
Cannot adopt OID in NQA-MIB: nqaAdminExtPara50 ::= { nqaAdminParaExtEntry 50 }
Cannot adopt OID in NQA-MIB: nqaAdminExtPara49 ::= { nqaAdminParaExtEntry 49 }
Cannot adopt OID in NQA-MIB: nqaAdminExtPara48 ::= { nqaAdminParaExtEntry 48 }
Cannot adopt OID in NQA-MIB: nqaAdminExtPara47 ::= { nqaAdminParaExtEntry 47 }
Cannot adopt OID in NQA-MIB: nqaAdminExtPara46 ::= { nqaAdminParaExtEntry 46 }
……
Cannot adopt OID in NQA-MIB: nqaAdminExtPara5 ::= { nqaAdminParaExtEntry 5 }
Cannot adopt OID in NQA-MIB: nqaAdminExtPara4 ::= { nqaAdminParaExtEntry 4 }
Cannot adopt OID in NQA-MIB: nqaAdminExtPara3 ::= { nqaAdminParaExtEntry 3 }
Cannot adopt OID in NQA-MIB: nqaAdminExtPara2 ::= { nqaAdminParaExtEntry 2 }
Cannot adopt OID in NQA-MIB: nqaAdminExtPara1 ::= { nqaAdminParaExtEntry 1 }
Cannot adopt OID in NQA-MIB: nqaMpingHistoryEntry ::= { nqaMpingHistoryTable 1 }
Cannot adopt OID in NQA-MIB: nqaGroupEntry ::= { nqaGroupTable 1 }
Cannot adopt OID in NQA-MIB: nqaAdminParaEntry ::= { nqaAdminParaTable 1 }
Cannot adopt OID in NQA-MIB: nqaGroupTable ::= { nqaCtrl 4 }
Cannot adopt OID in NQA-MIB: nqaScheduleTable ::= { nqaCtrl 3 }
Cannot adopt OID in NQA-MIB: nqaAdminParaExtTable ::= { nqaCtrl 5 }
Cannot adopt OID in NQA-MIB: nqaAdminParaTable ::= { nqaCtrl 2 }
Cannot adopt OID in NQA-MIB: nqaAdminCtrlTable ::= { nqaCtrl 1 }
Cannot adopt OID in NQA-MIB: nqaPathMtuStatsEntry ::= { nqaPathMtuStatsTable 1 }
Cannot adopt OID in NQA-MIB: nqaAlarmStatus ::= { nqaAlarmEntry 51 }
Cannot adopt OID in NQA-MIB: nqaAlarmDescription ::= { nqaAlarmEntry 19 }
Cannot adopt OID in NQA-MIB: nqaAlarmFallingEventIndex ::= { nqaAlarmEntry 18 }
Cannot adopt OID in NQA-MIB: nqaAlarmRisingEventIndex ::= { nqaAlarmEntry 17 }
Cannot adopt OID in NQA-MIB: nqaAlarmFallingThreshold ::= { nqaAlarmEntry 16 }
Cannot adopt OID in NQA-MIB: nqaAlarmRisingThreshold ::= { nqaAlarmEntry 15 }
Cannot adopt OID in NQA-MIB: nqaAlarmStartUpNqaAlarm ::= { nqaAlarmEntry 14 }
Cannot adopt OID in NQA-MIB: nqaAlarmValue ::= { nqaAlarmEntry 13 }
Cannot adopt OID in NQA-MIB: nqaAlarmSampleType ::= { nqaAlarmEntry 12 }
Cannot adopt OID in NQA-MIB: nqaAlarmVariable ::= { nqaAlarmEntry 11 }
Cannot adopt OID in NQA-MIB: nqaAlarmIndex ::= { nqaAlarmEntry 1 }
SNMPv2-SMI::enterprises.2011.5.25.111.4.1.1.3 = No Such Instance currently exists at this OID

有所进展,但问题仍未解决,继续研究……
3 篇帖子 分页: 1 / 1

登录

在线用户

正在浏览此版面的用户:没有注册用户 和 4 位游客