piyushm
July 27 2009, 04:27 PM
When certain SNMP tests are not being created/discovered/provisioned for a device, one of the things that almost always is required by way of troubleshooting is additional debug data obtained by running the probeSnmpTests.pl command.
Please run the following command on the DGE that the device is provisioned at.
On Linux/Solaris,
================
From a shell terminal,
# cd <TRAVERSE_HOME>/utils
# ./probeSnmpTests.pl --host n.n.n.n --comm XYZ --debug > probe.txt
On Windows,
================
From a command line prompt
c:\> cd <TRAVERSE_HOME>\utils
c:\> probeSnmpTests.pl --host n.n.n.n --comm XYZ --debug > probe.txt
where:
n.n.n.n = the device ip
XYZ = the snmp community string
<TRAVERSE_HOME> is the installation directory for the Traverse software
Attach the probe.txt file to the Helpdesk ticket you open with Zyrion
You may choose to leave the probe.txt file on the disk. It does no harm.
Please run the following command on the DGE that the device is provisioned at.
On Linux/Solaris,
================
From a shell terminal,
# cd <TRAVERSE_HOME>/utils
# ./probeSnmpTests.pl --host n.n.n.n --comm XYZ --debug > probe.txt
On Windows,
================
From a command line prompt
c:\> cd <TRAVERSE_HOME>\utils
c:\> probeSnmpTests.pl --host n.n.n.n --comm XYZ --debug > probe.txt
where:
n.n.n.n = the device ip
XYZ = the snmp community string
<TRAVERSE_HOME> is the installation directory for the Traverse software
Attach the probe.txt file to the Helpdesk ticket you open with Zyrion
You may choose to leave the probe.txt file on the disk. It does no harm.