Re: data query XML file

Unfortunately, the tests differ to a specific extend:

When accessing a device from the web-interface, the web server is using specific
code to test SNMP accessability.
Wheras spine has it's own code to perform the test.
There are certain conditions, where specific devices react differently to those
tests. Mainly, following reasons are known

- some devices don't like snmpwalks, they work when using snmpget. This can be
handled to a specific extend by changing the XML file accordingly
- some devices don't like snmpbulkwalk either, but e.g. php performs this in the
background, even when not asking for that. Setting the MAX OID parameter for the
device unfortunately affects spine behavior only. For the rest, using SNMPV1
_forces_ php not to use snmpbulkwalks
- some devices act "specifically", when switching between SNMP V1 and SNMP V2c.
Usually, the higher version is performing better - but under some circumstances
you will only get data for SNMP V1

You will get moreinformation when running spine in verbose mode for the device
in question, e.g.
spine --verbosity=5 <id> <id>
where <id> is the device id of the device in Cacti
Reinhard

On 09.08.2013 06:29, Steven Lo wrote:
> 
> Hi,
> 
> I manage to modify one of the XML file (WxGoose-ext-temperature.xml) by 
> editing the
> OID fields, copy it to /usr/local/cacti/resource/snmp_queries and name it
> weather_goose_temperature_sensor.xml.  After that, Data Queries does not 
> complain
> since it's able to locate the XML file.
> 
> I then run "Verbose Query" and seems like it's able to find the value 
> with snmpwalk.
> 
> Next, I create new graph for this host and seems like that is working as 
> well:
> 
> -sh-3.2$ php -q add_perms.php --list-graphs --host-id=2
> Known Host Graphs: (id, name, template)
> 10    MiniGoose II - A - |query_temperatureSensorName|     ITWatchdogs - 
> Temperature Sensor
> 11    MiniGoose II - A - |query_temperatureSensorName|     ITWatchdogs - 
> Temperature Sensor
> 12    MiniGoose II - A - |query_temperatureSensorName|     ITWatchdogs - 
> Temperature Sensor
> 13    MiniGoose II - A - |query_temperatureSensorName|     ITWatchdogs - 
> Temperature Sensor
> 14    MiniGoose II - A - |query_temperatureSensorName|     ITWatchdogs - 
> Temperature Sensor
> 15    MiniGoose II - A - |query_temperatureSensorName|     ITWatchdogs - 
> Temperature Sensor
> 16    MiniGoose II - A - |query_temperatureSensorName|     ITWatchdogs - 
> Temperature Sensor
> 17    MiniGoose II - A - |query_temperatureSensorName|     ITWatchdogs - 
> Temperature Sensor
> 18    MiniGoose II - A - |query_AirFlowSensorName|      ITWatchdogs - 
> AirFlow Sensor
> 
> 
> Now, the problem I'm running into is that the device status is "unknown" 
> and the device never
> make it to the poller cache.  I did rebuild_poller_cache.php and 
> poller_reindex_hosts.php but
> problem persist.
> 
> What cause the device in "unknown" stage and how do we make it poll the 
> device??
> 
> 
> When I do Console -> Device -> MiniGoose II - A, it's able to get the 
> system information (System Name,
> Uptime, Hostname, etc) without any problem.  I did see the SNMP traffic 
> when I probe the network
> interface.  So I guess it's not SNMP problem.
> 
> 
> Thanks in advance for your help.
> 
> 
> Steven.
> 
> 
> On 08/07/2013 11:46 PM, David RIBEIRO wrote:
>> Hello Steven,
>>
>> The contributor forget to put in the tar.gz the 3 XML.
>> The file in your zip file only import into cacti information about the
>> graph, where and how get values.
>>
>> Sorry for you but your only solution is to build the 3 XML or found the
>> coder ;)
>>
>> David
>>
>>
>> 2013/8/8 Steven Lo<[email protected]>
>>
>>> Hi Paul,
>>>
>>> On 08/07/2013 10:21 PM, Paul Gevers wrote:
>>>> Hi Steven,
>>>>
>>>> I have no experience with templates such as the one you are describing,
>>>> but...
>>>>
>>>>> /usr/local/cacti/resource/snmp_queries/ :
>>>> Are you running Debian? This location does not seem like a regular cacti
>>>> location, but indeed in Debian that would be the location that
>>>> could/would be proposed.
>>> We're running RHEL 5.  The RPM install Cacti in /var/www/cacti but we move
>>> it to /usr/local/cacti since the partition has more disk space.
>>>
>>>>> Data Template
>>>>> [success] ITWatchdogs - Builtin [new]
>>>>> [success] ITWatchdogs - airFlowSensor [new]
>>>>> [success] ITWatchdogs - TemperatureSensor [new]
>>>> It looks like they were successfully created, but the question is,
>>>> where? Or maybe it reported success when it failed...
>>> Cacti does show all the templates except the XML files.  I did not
>>> notice any
>>> error message in the log file.
>>>
>>>> Can you please post the URL of where you found this contributed
>>>> template, and I will try this at home.
>>> I use wget to download the template:
>>>
>>> wget
>>>
>>> http://docs.cacti.net/_media/usertemplate:host:itwatchdogs:cacti_host_template_itwatchdogs_-_goose_series.xml.gz
>>>
>>>
>>> Thanks for testing the template.
>>>
>>>
>>> Steven.
>>>
>>>> Paul

------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead. 
Download for free and get started troubleshooting in minutes. 
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk