SNMP4J-Agent与SMI：代码生成与领域建模指南

需积分: 10 82 浏览量更新于2024-07-23 收藏 460KB PDF 举报

"SNMP4J-Agent-Guide" SNMP（简单网络管理协议）是一种广泛使用的网络管理协议，用于在管理站和代理之间交换管理信息。SNMP4J-Agent是针对该协议的一个应用编程接口（API），它允许开发人员创建能够响应SNMP命令的代理程序。SNMP4J-Agent-Guide提供了关于如何使用这个API来构建SNMP代理的详细指导。在SNMP领域，其建模语言是SMI（Structure of Management Information）。SMI是一种用于定义管理信息结构的语言，它与ASN.1（抽象语法记号#1）经常被混淆，但两者并不相同。ASN.1是一种通用的编码标准，而SMI则是专门针对网络管理领域的模型化语言。SMI用于描述管理对象的静态结构，包括它们的依赖性和语义。代码生成在模型驱动工程（MDE）中扮演重要角色。对于SNMP，代码生成工具如AgenPro可以自动生成符合SMI定义的代码。AgenPro支持扩展和定制，通过代码生成模板，可以适应不同需求。当使用SNMP4J-Agent的代码生成模板时，AgenPro将生成适配SNMP4J-Agent API的代码。这些模板包含了SNMP4J-Agent API领域所需的知识，因此，开发者可以通过AgenPro快速构建SNMP代理程序，而无需从头编写所有底层逻辑。 SMI的版本，如SMIv1和SMIv2，虽然在提供机器可读的对象依赖性和语义信息方面可能有所不足，但它们仍然足够详细地定义了管理对象的静态结构。通过理解SMI，开发者可以更好地设计和实现SNMP代理，确保其与SNMP协议的兼容性。 SNMP4J-Agent-Guide不仅涵盖了SNMP的基础概念，还深入到SMI的细节，以及如何利用AgenPro这样的工具进行代码自动化生成。这使得开发者能够更高效地开发出符合标准的SNMP代理，从而更有效地管理和监控网络设备。此外，指南可能还会包含错误处理、性能优化、安全考虑等实际开发中的重要议题，帮助开发者实现稳定可靠的SNMP解决方案。通过学习这份指南，开发人员可以迅速掌握SNMP4J-Agent API的使用方法，提升开发效率，并为网络管理提供强大支持。

SNMP4J-AGENT INSTRUMENTATION GUIDE

Table Instrumentation

3 Table Instrumentation

In contrast to a scalar value, a table may have a varying number of instanc-

es. This circumstance is taken into account by SNMP4J-Agent by dividing

the responsibility for the table object instrumentation into the table and its

model.

The table model implements the MOTableModel interface and it is

responsible for providing the managed object instance values that the table

manages. Basically, there are four types of table models in the SNMP con-

text:

 Static table models where the number of rows do not vary or vary only

within intervals of several minutes. These table models implement the

MOTableModel interface.

For most use cases, the concrete DefaultMOTableModel class

can be used without modification. Although the number of rows can-

not be changed directly through a SNMP SET command, static table

models may support write access to their object instances. Create

access, however, cannot be supported by such table models.

 Dynamic table models where the number of rows may vary dynami-

cally within seconds, but as above, create access is not supported.

These table models also implement the MOTableModel interface,

but there is not a default implementation that is ready-to-use.

 Static mutable table models which support managed object instance

(row) creation through SNMP SET in addition to static table models.

Static mutable table models have to implement at least the MOMu-

tableTableModel interface.

For most use cases, the concrete DefaultMOMutableTable-

Model class can be used without modification.

 Dynamic mutable table models which support managed object

instance (row) creation through SNMP SET while the number of rows

in the model may change frequently. Like static mutable table models,

the dynamic counterpart implements the MOMutableTable-

Model, however, the default implementation of that interface, the

DefaultMOMutableTableModel class, is often not the best

choice to implement a dynamic mutable table model. In many cases, a

problem specific implementation of the MOMutableTableModel

is necessary.

SNMP4J-AGENT INSTRUMENTATION GUIDE

Static Tables

There are many aspects that influence the way of instrumenting SNMP ta-

bles, but the primary aspect is the combination of management informa-

tion access complexity and update frequency. Whether the management

information can be modified or new instances can be created through

SNMP is a secondary aspect, because the added complexity (for the instru-

mentation) is small.

AgenPro uses instances of the MOMutableTableModel for all ta-

bles by default, regardless whether a table supports read-create access or

not. When a table model implements that interface, it supports the usage

of a MOTableRowFactory instance which is the preferred way of using

custom MOTableRow instances as table rows. Since AgenPro generates

such custom row factories for you, it uses the MOMutableTableMod-

el to assign them to the used table model. If you do not want row factories

or do not want to implement the mutable table model interface, then set

the property noRowFactory to yes for that table object in the Agen-

Pro configuration.

Even if using instances of the MOMutableTableModel interface,

SNMP based row creation can be disabled by simply using only MOCol-

umn instances with access read-write or less.

The following sections describe approaches for implementing four as-

pects of table instrumentation: static and dynamic tables, managed object

modification and instance creation. The first two are exclusive whereas the

other aspects can be combined almost arbitrarily. For an overview about

the table model instrumentation approaches and how they are applied to

concrete requirements see Table 2 on page 13.

3.1 Static Tables

The instrumentation approaches

provided here are recommended

for most use cases. Nevertheless,

special requirements may reason

different approaches not dis-

cussed here. So please do not treat

them as law.

Static table instrumentation uses the DefaultMOTableModel or the

DefaultMOMutableTableModel in conjunction with the De-

faultMOTable class. The table model is populated with data at any of

the following events:

 Initialization of the agent.

 Access to the table managed object.

 An update event from the table object instrumentation indicating that

the table data has changed and thus the table model needs to be

updated.

Characteristical for static table instrumentation is the passivity of the table

model. Updates of the model’s data are performed outside of the model

剩余61页未读，继续阅读

three_man

粉丝: 84
资源: 23

SNMP4J-Agent与SMI：代码生成与领域建模指南

用java开发snmp包的发送和接收以及抓包

SNMP4J-Agent中文版API.chm

SNMP4J-agent.jar

如何利用SNMP4J-Agent和AgenPro工具进行SNMP代理的代码自动生成，并确保生成的代码完全符合SMI定义？

Java SNMP Agent Guide

snmp-guide.pdf

snmp agent user guide

NetBackup Appliance SNMP Traps Reference Guide

snmp_subagent_user_guide

SNMP 教师参考

最新资源