piyushm
November 2 2009, 02:40 PM
Traverse supports a wide range of IT infrastructure devices and applications out-of-the-box for automatic test discovery where it is able to recognize key availability and performance metrics. This is accomplished through our unique Device Signature technology and eliminates the painstaking process of compiling, loading and analyzing SNMP MIBs.
New Device Signatures are being added to Traverse on a regular basis and the most up-to-date list can be obtained from http://zyrion.com/products/datasheets/. If you are attempting to monitor an SNMP enabled device/application that is not currently supported, you may submit a new request for a suitable Device Signature. In order to create a new signature, we will need the following information from you:
The SNMP MIB files for the device/application in question. If you have already received the relevant files from the vendor, include them in the request. Otherwise you may point us to a website where the MIBs are located.
Output from "snmpwalk" for the enterprise OID tree executed against a suitable device/application. You can determine the enterprise OID by inspecting the header portion of the MIB. For example, here is an excerpt from POLYCOM-RMX-MIB as
an example:
polycom MODULE-IDENTITY
LAST-UPDATED "200703140000Z"
[...]
DESCRIPTION
"This is RMX MCU MIB"
::= { enterprises 13885 }
In this case the enterprise OID is .1.3.6.1.4.1.13885. In order to collect the necessary information, you can execute the following commands from your Traverse server:
Linux/Solaris:
cd /usr/local/traverse
bin/snmpwalk -Oefqn -v 2c -c XYZ n.n.n.n > snmpwalk-device.txt
bin/snmpwalk -Oefqn -v 2c -c XYZ n.n.n.n .1.3.6.1.4.1.13885 >> snmpwalk-device.txt
Windows:
C:
cd "\Program Files (x86)\Traverse"
bin\snmpwalk -Oefqn -v 2c -c XYZ n.n.n.n > snmpwalk-device.txt
bin\snmpwalk -Oefqn -v 2c -c XYZ n.n.n.n .1.3.6.1.4.1.13885 >> snmpwalk-device.txt
where n.n.n.n is the IP address of the device in question and XYZ is the appropriate community string. Note that the first parameter uses the uppercase letter "O", not number zero.
If there are specific metrics that you would like to be discovered, let us know. It is also helpful if you have suggestions regarding the default warning/critical thresholds and polling interval.
Send the MIB file(s) and snmpwalk-device.txt file to our support team (support@zyrion.com)who will start to analyze the MIB and building the Device Signature. During this process, they may have additional questions and will work with you to test it before finalizing it.
New Device Signatures are being added to Traverse on a regular basis and the most up-to-date list can be obtained from http://zyrion.com/products/datasheets/. If you are attempting to monitor an SNMP enabled device/application that is not currently supported, you may submit a new request for a suitable Device Signature. In order to create a new signature, we will need the following information from you:
The SNMP MIB files for the device/application in question. If you have already received the relevant files from the vendor, include them in the request. Otherwise you may point us to a website where the MIBs are located.
Output from "snmpwalk" for the enterprise OID tree executed against a suitable device/application. You can determine the enterprise OID by inspecting the header portion of the MIB. For example, here is an excerpt from POLYCOM-RMX-MIB as
an example:
polycom MODULE-IDENTITY
LAST-UPDATED "200703140000Z"
[...]
DESCRIPTION
"This is RMX MCU MIB"
::= { enterprises 13885 }
In this case the enterprise OID is .1.3.6.1.4.1.13885. In order to collect the necessary information, you can execute the following commands from your Traverse server:
Linux/Solaris:
cd /usr/local/traverse
bin/snmpwalk -Oefqn -v 2c -c XYZ n.n.n.n > snmpwalk-device.txt
bin/snmpwalk -Oefqn -v 2c -c XYZ n.n.n.n .1.3.6.1.4.1.13885 >> snmpwalk-device.txt
Windows:
C:
cd "\Program Files (x86)\Traverse"
bin\snmpwalk -Oefqn -v 2c -c XYZ n.n.n.n > snmpwalk-device.txt
bin\snmpwalk -Oefqn -v 2c -c XYZ n.n.n.n .1.3.6.1.4.1.13885 >> snmpwalk-device.txt
where n.n.n.n is the IP address of the device in question and XYZ is the appropriate community string. Note that the first parameter uses the uppercase letter "O", not number zero.
If there are specific metrics that you would like to be discovered, let us know. It is also helpful if you have suggestions regarding the default warning/critical thresholds and polling interval.
Send the MIB file(s) and snmpwalk-device.txt file to our support team (support@zyrion.com)who will start to analyze the MIB and building the Device Signature. During this process, they may have additional questions and will work with you to test it before finalizing it.