Xmptomrtg: Difference between revisions
From Krupczak.org
No edit summary |
|||
| Line 6: | Line 6: | ||
xmptomrtg host[:port] authenUser mib1[-table1]:var1[,instance1] mib2[-table2]:var2[,instance2] | xmptomrtg host[:port] authenUser mib1[-table1]:var1[,instance1] mib2[-table2]:var2[,instance2] | ||
</pre> | </pre> | ||
* host[:port] - the host and optional port to query. The default XMP port is TCP/5270. | |||
* authenUser - the authenticated user parameter to use when querying the XMP entity. It is similar to a community string and is used to identify an access control regime when querying the XMP entity. Since XMP is not sent in clear-text, it is not susceptible to snooping while in transit. The XMP entity must also be configured with this parameter. The MIB objects being queried need to be included in that authenUser's parameters. | |||
* Two MIB variable specifications. MIB variable specifications require a MIB-name, and object-name, and an optional instance. If the MIB object is contained within a table, the table name needs to be included separated by a dash character. Instances, if specified, need to be delineated by a comma character. | |||
Below is an example invocation querying two scalar MIB objects (''numThreads'' and ''numProcesses'') contained within the ''cartographer'' MIB. | |||
<pre> | |||
xmptomrtg mailserver xmpUser cartographer:numThreads cartographer:numProcesses | |||
</pre> | |||
Below is an example invocation querying two tabular MIB objects contained in the MIB-2 interface table. The instance being queried is ''if0''. | |||
<pre> | |||
xmptomrtg abigserver xmpUser mib2-ifTable:ifInOctets,if0 mib2-ifTable:ifOutOctets,if0 | |||
</pre> | |||
= Platform-specific Binaries = | = Platform-specific Binaries = | ||
Revision as of 19:35, 9 November 2008
xmptomrtg is a tool for querying XMP entities using the XMP protocol and outputing the result in a format for usage with MRTG.
Usage
xmptomrtg host[:port] authenUser mib1[-table1]:var1[,instance1] mib2[-table2]:var2[,instance2]
- host[:port] - the host and optional port to query. The default XMP port is TCP/5270.
- authenUser - the authenticated user parameter to use when querying the XMP entity. It is similar to a community string and is used to identify an access control regime when querying the XMP entity. Since XMP is not sent in clear-text, it is not susceptible to snooping while in transit. The XMP entity must also be configured with this parameter. The MIB objects being queried need to be included in that authenUser's parameters.
- Two MIB variable specifications. MIB variable specifications require a MIB-name, and object-name, and an optional instance. If the MIB object is contained within a table, the table name needs to be included separated by a dash character. Instances, if specified, need to be delineated by a comma character.
Below is an example invocation querying two scalar MIB objects (numThreads and numProcesses) contained within the cartographer MIB.
xmptomrtg mailserver xmpUser cartographer:numThreads cartographer:numProcesses
Below is an example invocation querying two tabular MIB objects contained in the MIB-2 interface table. The instance being queried is if0.
xmptomrtg abigserver xmpUser mib2-ifTable:ifInOctets,if0 mib2-ifTable:ifOutOctets,if0
