[mrtg] source interface for cfg file
McDonald, Dan
Dan.McDonald at austinenergy.com
Wed Nov 4 13:27:14 CET 2009
On Wed, 2009-11-04 at 10:40 +0600, Kushner Anatoliy wrote:
> is it possible to set source interface for each target ?
>
> something like
> Source[target]: 10.0.0.1
>
> Source[target2]: 10.0.0.2
>
Yes, it's part of the extended host name syntax:
Extended Host Name Syntax
In all places where ``community at router'' is accepted, you can
add additional parameters for the SNMP communication using
colon-separated suffixes. You can also append a pipe symbol
( | ) and the name of a numeric conversion subroutine as
described under the global keyword "ConversionCode" above. The
full syntax is as follows:
community at router[:[port][:[timeout][:[retries][:[backoff][:[version]][|name]]]]]
where the meaning of each parameter is as follows:
port
the UDP port under which to contact the SNMP agent (default:
161)
The complete syntax of the port parameter is
remote_port[!local_address[!local_port]]
Some machines have additional security features that only allow
SNMP queries to come from certain IP addresses. If the host
doing the query has multiple interface, it may be necessary to
specify the interface the query should come from.
The port parameter allows the specification of the port of the
machine being queried. In addition, the IP address (or hostname)
and port of the machine doing the query may be specified.
Examples:
somehost
somehost:161
somehost:161!192.168.2.4!4000 use 192.168.2.4 and port 4000 as source
somehost:!192.168.2.4 use 192.168.2.4 as source
somehost:!!4000 use port 4000 as source
--
Daniel J McDonald, CCIE # 2495, CISSP # 78281, CNX
www.austinenergy.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://lists.oetiker.ch/pipermail/mrtg/attachments/20091104/87777358/attachment.pgp
More information about the mrtg
mailing list