How Can I Request Support For New Hardware/Application


How Can I Request Support For New Hardware/Application


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 If you are attempting to monitor any 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:

  1. 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.

  2. 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:

      LAST-UPDATED  "200703140000Z"
      "This is RMX MCU MIB"
        ::= { enterprises 13885 }

    In this case, the enterprise OID is . In order to collect the necessary information, you can execute the following commands from your Traverse server:

    Please replace ENTERPRISEOID with the actual enterprise OID as described above.

    The commands must be run from the DGE/DGEX that is monitoring the new hardware

    <TRAVERSE_HOME> is the Traverse installation directory, typically /usr/local/traverse (on Linux), C:\Program Files (x86)\Traverse (Windows)

    bin/snmpwalk -Oefqnt -v 2c -c XYZ n.n.n.n > snmpwalk_device_1.txt
    bin/snmpwalk -Oefqnt -v 2c -c XYZ n.n.n.n . > snmpwalk_device_2.txt

    bin\snmpwalk -Oefqnt -v 2c -c XYZ n.n.n.n > snmpwalkdevice_1.txt
    bin\snmpwalk -Oefqnt -v 2c -c XYZ n.n.n.n . > snmpwalk_device_2.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.


  3. 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. This will especially help expedite the device creation process.

  4. Run probesnmptests to determine the metrics currently being discovered against the device:

    utils/ --host n.n.n.n --comm XYZ --version 2 --debug > probe_device.txt

    utils\ --host n.n.n.n --comm XYZ --version 2 --debug > probe_device.txt

    where n.n.n.n is the IP address of the device in question and XYZ is the appropriate community string.


Please review the contents on the files  snmpwalk_device_1.txt, snmpwalk_device_2.txt, and probe_device.txt to ensure they are populated with data. If an error message is encountered, please correct the issue and gather the data.

Please open up a support ticket and send the MIB file(s), the generated files from this KB, and provide any relevant details into what metrics you are specifically interested in. During this process, your support tech may have additional questions and will work with you to test them before finalizing them.

Was this article helpful?
5 out of 6 found this helpful
Have more questions? Contact us