SNMP 陷阱中属性的顺序重要吗
我正在使用一些 SNMP 陷阱来监视应用程序。现在我被告知,如果陷阱中的属性顺序与 MIB 中定义的不同,某些监控系统可能会出现问题。由于 OID 的复杂性可以很容易地用于对属性进行重新排序,我对此感到惊讶,因此我试图找到 RFC 的相关部分,但我既找不到允许任何排序的内容,也找不到任何允许排序的内容。说这很重要。在有关 SNMP 的其他辅助文档中,我也找不到任何有用的内容。
所以这更多的是一个好奇的问题,但是也可以帮助使用 SNMP 的进一步项目。就这个问题而言,任何人都可以指出我正确的文档吗?或者这是一个软件可以处理的事情,而其他软件可能无法处理这个问题,我应该检查该软件的实际文档?
I am using some SNMP traps for monitoring of applications. Now I was told that some monitoring systems might have problems if the order of the attributes within the the traps was not the same as defined in the MIB. From the Complexity of the OIDs that could easily be used to re-order the attributes I was surprised by this, so I tried to find the relevant section of the RFC, but I could neither find something that said any ordering is allowed nor anything that said it is important. In other secondary documentation about SNMP I was not able to find anything usefull either.
So this is more a curiosity question, that could however also help in further projects using SNMP. Could anyone point me to the correct documentation as far as this problem is concerned. Or is this something that one software might handle while other software might not handle this and I should check the actual documentation for that software?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
我找到了相关文档。
第 3.1.2 节指定:
感谢向我指出这一点的人。
I found the relevant document.
Section 3.1.2 specifies:
Thanks to the person who pointed this out to me.