The module
The
The record
A user defined identity representing this notification send operation.
A module implementing the
This is any extra info the user wants to have supplied when the functions in the callback module is called.
This function can be used to add an AGENT-CAPABILITY statement to the sysORTable in the agent. The table is defined in the SNMPv2-MIB.
This function can be used to delete an AGENT-CAPABILITY statement to the sysORTable in the agent. This table is defined in the SNMPv2-MIB.
Returns all AGENT-CAPABILITY statements in the sysORTable in the agent. This table is defined in the SNMPv2-MIB.
Performs a GET operation on the agent. All loaded MIB objects are visible in this operation. The agent calls the corresponding instrumentation functions just as if it was a GET request coming from a manager.
Note that the request specific parameters (such as
Performs a GET-NEXT operation on the agent. All loaded MIB objects are visible in this operation. The agent calls the corresponding instrumentation functions just as if it was a GET request coming from a manager.
Note that the request specific parameters (such as
Backup persistent/permanent data handled by the agent (such as local-db, mib-data and vacm).
Data stored by mnesia is not handled.
BackupDir cannot be identical to DbDir.
Returns a list (a dictionary) containing information about the agent. Information includes loaded MIBs, registered sub-agents, some information about the memory allocation.
As of version 4.4 the format of the info has been changed.
To convert the info to the old format, call the
As of version 4.4 the format of the info has been changed. This function is used to convert to the old (pre-4.4) info format.
Loads
Dir = code:priv_dir(my_app) ++ "/mibs/",
snmpa:load_mibs(snmp_master_agent, [Dir ++ "MY-MIB"]).
Unloads MIBs into an agent. If it cannot unload all MIBs, it will indicate where unloading was aborted.
Retrieve the list of all the mibs loaded into this agent. Default is the master agent.
Get the full path to the (compiled) mib-file.
Get the request-id, context, community and address of the request currently being processed by the agent.
Note that these functions is intended to be called by the instrumentation functions and only if they are executed in the context of the agent process (e.g. it does not work if called from a spawned process).
Converts the symbolic value
Converts the integer
Looks up the OBJECT IDENTIFIER of a MIB object, given the symbolic name. Note, the OBJECT IDENTIFIER is given for the object, not for an instance.
Looks up the symbolic name of a MIB object, given OBJECT IDENTIFIER.
Retrieve all alias-names known to the agent.
Retrieve all tables known to the agent.
Retrieve all variables known to the agent.
Retrieve all notifications (and traps) known to the agent.
Converts an Audit Trail Log to a readable text file.
Changes the log size of the Audit Trail Log. The application must be configured to use the audit trail log function. Please refer to disk_log(3) in Kernel Reference Manual for a description of how to change the log size.
The change is permanent, as long as the log is not deleted. That means, the log size is remembered across reboots.
Changes the run-time Audit Trail log type.
Note that this has no effect on the application configuration as defined by configuration files, so a node restart will revert the config to whatever is in those files.
This function is primarily useful in testing/debugging scenarios.
Finds the mib corresponding to the
Finds the mib entry corresponding to the
Invalidate the mib server cache.
The entire contents of the cache will be deleted.
Enable the mib server cache.
Disable the mib server cache.
Retreive the size of the mib server cache.
Perform mib server cache gc.
Manually performs a mib server cache gc.
This can be done regardless of the value of the
Enable automatic gc of the mib server cache.
Disable automatic gc of the mib server cache.
Change the mib server cache
Change the mib server cache
Registers a notification filter.
Unregister a notification filter.
List all notification filters in an agent.
Changes the request limit.
Note that this has no effect on the application configuration as defined by configuration files, so a node restart will revert the config to whatever is in those files.
This function is primarily useful in load regulation scenarios.
Registers a sub-agent under a sub-tree of another agent.
It is easy to make mistakes when registering sub-agents and this activity should be done carefully. For example, a strange behaviour would result from the following configuration:
snmp_agent:register_subagent(MAPid,[1,2,3,4],SA1), snmp_agent:register_subagent(SA1,[1,2,3], SA2).
Unregister a sub-agent. If the second argument is a pid,
then that sub-agent will be unregistered from all trees in
Sends the notification
The parameter
If
This inform the user which target addresses the notification was sent to.
This informs the user that this target address acknowledged the notification.
This informs the user that this target address did not acknowledge notification.
The notification is sent as an Inform-Request to each
target address in
The
where
Addresses = [address()] Address = address() address() = v1_address() | v3_address() v1_address() = {TDomain, TAddress} v3_address() = {{TDomain, TAddress}, V3MsgData} TDomain = tdoamin() TAddress = taddress() tdomain() = The oid of snmpUDPDomain This is the only supported transport domain. taddress() = [A1, A2, A3, A4, P1, P3] The 4 first bytes makes up the IP-address and the last 2, the UDP-port number. V3MsgData = v3_msg_data() v3_msg_data() = term()
If
The optional argument
For example, to specify that
If a variable in the notification is a table element, the
This function is asynchronous, and does not return any
information. If an error occurs,
Note that the use of the LocalEngineID argument is only intended
for special cases, if the agent is to "emulate" multiple EngineIDs!
By default, the agent uses the value of
Initiate the discovery process with the manager identified by
This function is synchronous, which means that it will return when the discovery process has been completed or failed.
The
The
If we are not at security-level
The default discovery handler will require
additional actions by the caller and the discovery will not work
if the security-level is higher then
This off-line utility function can be used to convert the old snmp application config (pre snmp-4.0) to the new snmp agent config (as of snmp-4.0).
For information about the old config (
For information about the current agent config
(
Restart the worker process of a multi-threaded agent.
This is a utility function, that can be useful when e.g. debugging instrumentation functions.
Restart the set worker process of a multi-threaded agent.
This is a utility function, that can be useful when e.g. debugging instrumentation functions.
Sets verbosity for the designated process. For the lowest
verbosity
calendar(3), erlc(1)