4. Can I prevent particular management
station(s) from accessing my agent?
This can be achieved by using the Access Control Table associated
with the agent, where authentication information are given.
To restrict access to particular management stations refer
Managers to Community" page of the help documentation.
6. Is it possible to send different versions
of trap to different management stations or NMS, from the
SNMP agents can send different version traps to different
destinations using Trap Forwarding Table. The table provides
a column named ManagerVersion wherein the Trap version can
be specified. The trap thus gets forwarded to the management
stations according to the entries in the Trap Forwarding Table.
9. Does the SNMP agent toolkit provide database
management through SNMP?
Yes. SNMP agent can access the database table and retrieve
the stored information from it. This helps the user to save
considerable memory space as database serves as a resource
to persist data. For more details on database supported by
the SNMP Agent Toolkit, refer to "Supported
Storage Types for Scalars and Tables" of the help
A node in the MIB Tree refers to an object to be managed
by the agent. Each object whether it is a device or a characteristics
of a device, must have a name by which it can uniquely be
identified. The name is called the Object Identifier (OID).
The OID is written as a sequence of integers, separated by
periods. For example, the sequence .184.108.40.206.220.127.116.11 specifies
the system description within the system group of the management
11. Is it possible to port the agent developed
by SNMP Agent Toolkit to devices with very limited resources?
Using WebNMS SNMP Agent Toolkit, it is possible to develop
J2ME SNMP v1/v2c agents. They are compatible with Sun J2ME
CDC/ IBM J2ME CDC specifications. The J2ME agents can be ported
to devices with limited resources(like embedded devices having
low memory footprint, etc). For more details, refer the "Developing
and Porting SNMP Agent in J2ME CDC Environment" page
in our help documentation.
WebNMS SNMP Agent Toolkit introduces the concept of Rule Engine
using which users' business logic can be defined as a set
of rules in configuration files and some tasks (like sending
e-mails, traps, etc) can be performed based on this without
modifying the code. Thus, the business logic need not be hard-coded
in the stub files. For more details, refer the "Implementing
Business Logic using Rule Engine" page in our help
The agents which are not directly exposed to the manager
are called sub-agents.
The agent which acts as a proxy/interface for sub agent(s)
is called master agent. It contains the details about sub
agents and acts as a interface between the manager and sub
agent. When SNMP requests intended for sub agents reaches
the master agent, the master agent will forward those requests
to the sub-agent and the responses from the sub agents will
be sent back to the manager.
6. Does WebNMS support AgentX for master
No, but WebNMS provides a better solution for master subagent
architecture via SNMP i.e, the communication between master
and sub-agent through SNMP enhances more flexibility as any
legacy SNMP agent can be registered as sub-agent to WebNMS
master agent and also WebNMS's SNMP agent can be registered
as sub-agent to the existing master agent.
10. Can I add sub-agent to master agent
at runtime without bringing other
Yes. To achieve this, add sub-agent entries to the proxy
table of the master agent by loading AGENT-SNMP-CONFIG-MIB
packaged with the product. Please refer to the SNMPv1/v2
demo that illustrates the steps involved, while adding
an WebNMS SNMP agent to a master agent.
11. Does the toolkit support MIB II implementation?
Yes. SNMP Agent Toolkit supports MIB II implementation through
master-subagent architecture. WebNMS's SNMP agent can proxy
other third-party SNMP agent supporting MIB II, by configuring
it as sub-agent to WebNMS's SNMP agent.