snmpm
Common Data Types
The following data types are used in the functions below:
oid() = [byte()] - The oid() type is used to represent an ASN.1 OBJECT IDENTIFIER snmp_reply() = {error_status(), error_index(), varbinds()} error_status() = noError | atom() error_index() = integer() varbinds() = [varbind()] atl_type() = read | write | read_write target_name() = string() - Is a unique *non-empty* string vars_and_vals() = [var_and_val()] var_and_val() = {oid(), value_type(), value()} | {oid(), value()} value_type() = o ('OBJECT IDENTIFIER') | i ('INTEGER') | u ('Unsigned32') | g ('Unsigned32') | s ('OCTET SRING') | b ('BITS') | ip ('IpAddress') | op ('Opaque') | c32 ('Counter32') | c64 ('Counter64') | tt ('TimeTicks') value() = term() community() = string() sec_model() = any | v1 | v2c | usm sec_name() = string() sec_level() = noAuthNoPriv | authNoPriv | authPriv
See also the data types in snmpa_conf.
Types
Request a notification (message) when the SNMP manager has started.
The Timeout is the time the request is valid. The value has to be greater then zero.
The Pid is the process handling the supervision of the SNMP manager start. When the manager has started a completion message will be sent to the client from this process: {snmpm_started, Pid}. If the SNMP manager was not started in time, a timeout message will be sent to the client: {snmpm_start_timeout, Pid}.
A client application that is dependent on the SNMP manager will use this function in order to be notified of when the manager has started. There are two situations when this is useful:
-
During the start of a system, when a client application could start prior to the SNMP manager but is dependent upon it, and therefore has to wait for it to start.
-
When the SNMP manager has crashed, the dependent client application has to wait for the SNMP manager to be restarted before it can reconnect.
The function returns the pid() of a handler process, that does the supervision on behalf of the client application. Note that the client application is linked to this handler.
This function is used in conjunction with the monitor function.
Types
Register the manager entity (=user) responsible for specific agent(s).
Module is the callback module (snmpm_user behaviour) which will be called whenever something happens (detected agent, incoming reply or incoming trap/notification). Note that this could have already been done as a consequence of the node config. (see users.conf).
The argument DefaultAgentConfig is used as default values when this user register agents.
The type of Val depends on Item:
community = string() timeout = integer() | snmp_timer() max_message_size = integer() version = v1 | v2 | v3 sec_model = any | v1 | v2c | usm sec_name = string() sec_level = noAuthNoPriv | authNoPriv | authPriv
Types
Register the monitored manager entity (=user) responsible for specific agent(s).
The process performing the registration will be monitored. Which means that if that process should die, all agents registered by that user process will be unregistered. All outstanding requests will be canceled.
Module is the callback module (snmpm_user behaviour) which will be called whenever something happens (detected agent, incoming reply or incoming trap/notification). Note that this could have already been done as a consequence of the node config. (see users.conf).
The argument DefaultAgentConfig is used as default values when this user register agents.
The type of Val depends on Item:
community = string() timeout = integer() | snmp_timer() max_message_size = integer() version = v1 | v2 | v3 sec_model = any | v1 | v2c | usm sec_name = string() sec_level = noAuthNoPriv | authNoPriv | authPriv
Types
Explicitly instruct the manager to handle this agent, with UserId as the responsible user.
Called to instruct the manager that this agent shall be handled. This function is used when the user knows in advance which agents the manager shall handle. Note that there is an alternate way to do the same thing: Add the agent to the manager config files (see agents.conf).
TargetName is a non-empty string, uniquely identifying the agent.
The type of Val depends on Item:
[mandatory] engine_id = string() [mandatory] tadress = transportAddress() % Depends on tdomain [optional] port = inet:port_number() [optional] tdomain = transportDomain() [optional] community = string() [optional] timeout = integer() | snmp_timer() [optional] max_message_size = integer() [optional] version = v1 | v2 | v3 [optional] sec_model = any | v1 | v2c | usm [optional] sec_name = string() [optional] sec_level = noAuthNoPriv | authNoPriv | authPriv
Note that if no tdomain is given, the default value, transportDomainUdpIpv4, is used.
Note that if no port is given and if taddress does not contain a port number, the default value is used.
Types
Update agent config. The function update_agent_info/3 should be used when several values needs to be updated atomically.
See function register_agent for more info about what kind of items are allowed.
Types
Explicitly instruct the manager to handle this USM user. Note that there is an alternate way to do the same thing: Add the usm user to the manager config files (see usm.conf).
The type of Val depends on Item:
sec_name = string() auth = usmNoAuthProtocol | usmHMACMD5AuthProtocol | usmHMACSHAAuthProtocol | usmHMAC128SHA224AuthProtocol | usmHMAC192SH256AuthProtocol | usmHMAC256SHA384AuthProtocol | usmHMAC384SHA512AuthProtocol auth_key = [integer()] (length 16 if auth = usmHMACMD5AuthProtocol, length 20 if auth = usmHMACSHAAuthProtocol, length 28 if auth = usmHMAC128SHA224AuthProtocol, length 32 if auth = usmHMAC192SHA256AuthProtocol, length 48 if auth = usmHMAC256SHA384AuthProtocol, length 64 if auth = usmHMAC384SHA512AuthProtocol) priv = usmNoPrivProtocol | usmDESPrivProtocol | usmAesCfb128Protocol priv_key = [integer()] (length is 16 if priv = usmDESPrivProtocol | usmAesCfb128Protocol).
sync_get2(UserId, TargetName, Oids, SendOpts) -> {ok, SnmpReply, Remaining} | {error, Reason}
OTP R14B03
Types
Synchronous get-request.
Remaining is the remaining time of the given (or default) timeout time.
When Reason is {send_failed, ...} it means that the net_if process failed to send the message. This could happen because of any number of reasons, i.e. encoding error. ActualReason is the actual reason in this case.
The send option extra specifies an opaque data structure passed on to the net-if process. The net-if process included in this application makes, with one exception, no use of this info, so the only use for it in such a option (when using the built in net-if) would be tracing. The one usage exception is: Any tuple with snmpm_extra_info_tag as its first element is reserved for internal use.
Some of the send options (community, sec_model, sec_name, sec_level and max_message_size) are override options. That is, for this request, they override any configuration done when the agent was registered.
For SnmpInfo, see the user callback function handle_report.
Types
Asynchronous get-request.
The reply, if it arrives, will be delivered to the user through a call to the snmpm_user callback function handle_pdu.
The send option timeout specifies for how long the request is valid (after which the manager is free to delete it).
The send option extra specifies an opaque data structure passed on to the net-if process. The net-if process included in this application makes, with one exception, no use of this info, so the only use for it in such a option (when using the built in net-if) would be tracing. The one usage exception is: Any tuple with snmpm_extra_info_tag as its first element is reserved for internal use.
Some of the send options (community, sec_model, sec_name, sec_level and max_message_size) are override options. That is, for this request, they override any configuration done when the agent was registered.
sync_get_next2(UserId, TargetName, Oids, SendOpts) -> {ok, SnmpReply, Remaining} | {error, Reason}
OTP R14B03
Types
Synchronous get-next-request.
Remaining is the remaining time of the given (or default) timeout time.
When Reason is {send_failed, ...} it means that the net_if process failed to send the message. This could happen because of any number of reasons, i.e. encoding error. ActualReason is the actual reason in this case.
The send option extra specifies an opaque data structure passed on to the net-if process. The net-if process included in this application makes, with one exception, no use of this info, so the only use for it in such a option (when using the built in net-if) would be tracing. The one usage exception is: Any tuple with snmpm_extra_info_tag as its first element is reserved for internal use.
Some of the send options (community, sec_model, sec_name, sec_level and max_message_size) are override options. That is, for this request, they override any configuration done when the agent was registered.
For SnmpInfo, see the user callback function handle_report.
Types
Asynchronous get-next-request.
The reply will be delivered to the user through a call to the snmpm_user callback function handle_pdu.
The send option timeout specifies for how long the request is valid (after which the manager is free to delete it).
The send option extra specifies an opaque data structure passed on to the net-if process. The net-if process included in this application makes, with one exception, no use of this info, so the only use for it in such a option (when using the built in net-if) would be tracing. The one usage exception is: Any tuple with snmpm_extra_info_tag as its first element is reserved for internal use.
Some of the send options (community, sec_model, sec_name, sec_level and max_message_size) are override options. That is, for this request, they override any configuration done when the agent was registered.
sync_set2(UserId, TargetName, VarsAndVals) -> {ok, SnmpReply, Remaining} | {error, Reason}
OTP R14B03
sync_set2(UserId, TargetName, VarsAndVals, SendOpts) -> {ok, SnmpReply, Remaining} | {error, Reason}
OTP R14B03
Types
Synchronous set-request.
Remaining is the remaining time of the given (or default) timeout time.
When Reason is {send_failed, ...} it means that the net_if process failed to send the message. This could happen because of any number of reasons, i.e. encoding error. ActualReason is the actual reason in this case.
When var_and_val() is {oid(), value()}, the manager makes an educated guess based on the loaded mibs.
The send option extra specifies an opaque data structure passed on to the net-if process. The net-if process included in this application makes, with one exception, no use of this info, so the only use for it in such a option (when using the built in net-if) would be tracing. The one usage exception is: Any tuple with snmpm_extra_info_tag as its first element is reserved for internal use.
Some of the send options (community, sec_model, sec_name, sec_level and max_message_size) are override options. That is, for this request, they override any configuration done when the agent was registered.
For SnmpInfo, see the user callback function handle_report.
Types
Asynchronous set-request.
The reply will be delivered to the user through a call to the snmpm_user callback function handle_pdu.
The send option timeout specifies for how long the request is valid (after which the manager is free to delete it).
When var_and_val() is {oid(), value()}, the manager makes an educated guess based on the loaded mibs.
The send option extra specifies an opaque data structure passed on to the net-if process. The net-if process included in this application makes, with one exception, no use of this info, so the only use for it in such a option (when using the built in net-if) would be tracing. The one usage exception is: Any tuple with snmpm_extra_info_tag as its first element is reserved for internal use.
Some of the send options (community, sec_model, sec_name, sec_level and max_message_size) are override options. That is, for this request, they override any configuration done when the agent was registered.
sync_get_bulk2(UserId, TragetName, NonRep, MaxRep, Oids) -> {ok, SnmpReply, Remaining} | {error, Reason}
OTP R14B03
sync_get_bulk2(UserId, TragetName, NonRep, MaxRep, Oids, SendOpts) -> {ok, SnmpReply, Remaining} | {error, Reason}
OTP R14B03
Types
Synchronous get-bulk-request (See RFC1905).
Remaining is the remaining time of the given (or default) timeout time.
When Reason is {send_failed, ...} it means that the net_if process failed to send the message. This could happen because of any number of reasons, i.e. encoding error. ActualReason is the actual reason in this case.
The send option extra specifies an opaque data structure passed on to the net-if process. The net-if process included in this application makes, with one exception, no use of this info, so the only use for it in such a option (when using the built in net-if) would be tracing. The one usage exception is: Any tuple with snmpm_extra_info_tag as its first element is reserved for internal use.
Some of the send options (community, sec_model, sec_name, sec_level and max_message_size) are override options. That is, for this request, they override any configuration done when the agent was registered.
For SnmpInfo, see the user callback function handle_report.
async_get_bulk2(UserId, TargetName, NonRep, MaxRep, Oids) -> {ok, ReqId} | {error, Reason}
OTP R14B03
async_get_bulk2(UserId, TargetName, NonRep, MaxRep, Oids, SendOpts) -> {ok, ReqId} | {error, Reason}
OTP R14B03
Types
Asynchronous get-bulk-request (See RFC1905).
The reply will be delivered to the user through a call to the snmpm_user callback function handle_pdu.
The send option timeout specifies for how long the request is valid (after which the manager is free to delete it).
The send option extra specifies an opaque data structure passed on to the net-if process. The net-if process included in this application makes no use of this info, so the only use for it in such a configuration (when using the built in net-if) would be tracing.
Some of the send options (community, sec_model, sec_name, sec_level and max_message_size) are override options. That is, for this request, they override any configuration done when the agent was registered.
log_to_txt(LogDir, Mibs, OutFile, LogName, LogFile, Block | Start) -> ok | {ok, Cnt} | {error, Reason}
log_to_txt(LogDir, Mibs, OutFile, LogName, LogFile, Block, Start) -> ok | {ok, Cnt} | {error, Reason}
log_to_txt(LogDir, Mibs, OutFile, LogName, LogFile, Start, Stop) -> ok | {ok, Cnt} | {error, Reason}
log_to_txt(LogDir, Mibs, OutFile, LogName, LogFile, Block, Start, Stop) -> ok | {ok, Cnt} | {error, Reason}
OTP R16B03
Types
Converts an Audit Trail Log to a readable text file. OutFile defaults to "./snmpm_log.txt". LogName defaults to "snmpm_log". LogFile defaults to "snmpm.log".
The Block argument indicates if the log should be blocked during conversion. This could be useful when converting large logs (when otherwise the log could wrap during conversion). Defaults to true.
See snmp:log_to_txt for more info.
log_to_io(LogDir, Mibs, LogName, LogFile, Block | Start) -> ok | {ok, Cnt} | {error, Reason}
OTP R15B01
log_to_io(LogDir, Mibs, LogName, LogFile, Block, Start) -> ok | {ok, Cnt} | {error, Reason}
OTP R15B01
log_to_io(LogDir, Mibs, LogName, LogFile, Start, Stop) -> ok | {ok, Cnt} | {error, Reason}
OTP R15B01
log_to_io(LogDir, Mibs, LogName, LogFile, Block, Start, Stop) -> ok | {ok, Cnt} | {error, Reason}
OTP R16B03
Types
Converts an Audit Trail Log to a readable format and prints it on stdio. LogName defaults to "snmpm_log". LogFile defaults to "snmpm.log".
The Block argument indicates if the log should be blocked during conversion. This could be useful when converting large logs (when otherwise the log could wrap during conversion). Defaults to true.
See snmp:log_to_io for more info.
Types
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.
Types
Types
This utility function is used to create a formatted (pretty printable) string of the error reason received from either:
-
The Reason returned value if any of the sync/async get/get-next/set/get-bulk functions returns {error, Reason}
-
The Reason parameter in the handle_error user callback function.
Prefix should either be an indentation string (e.g. a list of spaces) or a positive integer (which will be used to create the indentation string of that length).