MIB的订购
我有一个 MIB SAF-CKPT-MIB 当我尝试该命令时
snmpget -v2c -c public -mALL (IP_address) SAF-CKPT-MIB::saCkptCheckpointMaxSectionSize.14.118.100.115.95.118.100.101.115.116.95.100.98.95.49 SAF-CKPT-MIB::saCkptNodeReplicaType.14.118.100.115.95.118.100.101.115.116.95.100.98.95.49.14.115.97.102.78.111.100.101.61.83.67.95.50.95.50
，我收到消息“超时：IP_address 无响应”
当我更改顺序时，
snmpget -v2c -c public -mALL (IP_address) SAF-CKPT-MIB::saCkptNodeReplicaType.14.118.100.115.95.118.100.101.115.116.95.100.98.95.49.14.115.97.102.78.111.100.101.61.83.67.95.50.95.50 SAF-CKPT-MIB::saCkptCheckpointMaxSectionSize.14.118.100.115.95.118.100.101.115.116.95.100.98.95.49
它工作正常......
我的问题是，更改顺序在这里有何影响？ 我希望我的问题很清楚......
I am having one MIB SAF-CKPT-MIB
When I am trying the command
snmpget -v2c -c public -mALL (IP_address) SAF-CKPT-MIB::saCkptCheckpointMaxSectionSize.14.118.100.115.95.118.100.101.115.116.95.100.98.95.49 SAF-CKPT-MIB::saCkptNodeReplicaType.14.118.100.115.95.118.100.101.115.116.95.100.98.95.49.14.115.97.102.78.111.100.101.61.83.67.95.50.95.50
I am getting the message "Timeout: No Response from IP_address"
When I am changing the order like
snmpget -v2c -c public -mALL (IP_address) SAF-CKPT-MIB::saCkptNodeReplicaType.14.118.100.115.95.118.100.101.115.116.95.100.98.95.49.14.115.97.102.78.111.100.101.61.83.67.95.50.95.50 SAF-CKPT-MIB::saCkptCheckpointMaxSectionSize.14.118.100.115.95.118.100.101.115.116.95.100.98.95.49
It is working fine .....
My question is how this changing the order is making difference here ??
I hope my question is clear ...
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
消息“Timeout: No Response from IP_address”表示 IP_address 处的 snmp 服务器在
snmpget使用的超时期限内（默认情况下为 5 秒）没有响应。IP_address 处的 snmp 服务器在第一个实例中根本没有响应或者响应太慢。这可以通过增加超时来测试。例如：
<代码>
snmpget -v2c -c public -mALL -t 60（IP 地址）
当然也可以按照Lex Li的建议使用Wireshark抓包来测试。
由于请求中 MIB 变量的顺序而导致的任何行为变化听起来像是在 snmp 服务器上实现此 MIB 时出现的问题。
The message "Timeout: No Response from IP_address" is indicating that the snmp server at IP_address is not responding within the timeout period that
snmpgetis using (iirc it's 5 seconds by default).Either the snmp server at IP_address is not responding at all in the first instance or is responding too slowly. This can be tested by increasing the timeout. eg:
snmpget -v2c -c public -mALL -t 60 (IP_address)
Of course it could also be tested by capturing the packets using Wireshark as suggested by Lex Li.
Any change in behaviour due to the order of the MIB variables in the request sounds like a problem in the implementation of this MIB at the snmp server.
很少看到与顺序相关的问题，因为一般来说顺序不会对生成的 SNMP 数据包产生影响。当然，使用 Wireshark 或 Microsoft Network Monitor 捕获网络流量可以在幕后显示一些提示。
莱克斯·李
http://sharpsnmplib.codeplex.com
Rarely saw such order related issue, as generally speaking the order does not have an impact on the resulting SNMP packets. But of course, capturing network traffic with either Wireshark or Microsoft Network Monitor can show some hints under the hood.
Lex Li
http://sharpsnmplib.codeplex.com