Found it in the device's --> properties --> snmp --> basic configuration
Thank you.
On 4/10/24 10:33, Eric W. Bates (he) wrote:
> Thanks for your reply about poller.php.
>
> The problem appears to be the -t (timeout) option given to snmpget in
> the poller is set to 1 second.
> 4 of our 6 Palos n
Thanks for your reply about poller.php.
The problem appears to be the -t (timeout) option given to snmpget in
the poller is set to 1 second.
4 of our 6 Palos need more than one second to come up with an answer.
How do I increase that timeout value?
It's set explicitly in the [CMD] so I don't thi
Apologies. My mistake. I found your reply.
On 4/10/24 10:02, Eric W. Bates (he) wrote:
> Anything? We are paying for a professional license.
>
> What is devices.status?
> How do I toggle it on?
> If I just toggle it in the SQL, what will break?
>
> On 3/19/24 08:56, Eric W. Bates wrote:
>> I have
Anything? We are paying for a professional license.
What is devices.status?
How do I toggle it on?
If I just toggle it in the SQL, what will break?
On 3/19/24 08:56, Eric W. Bates wrote:
> I have 2 Palo Alto firewalls which dropped off the map at the same time
> about 25 days ago. I think it may
Device status is set right at the start of the poller when it decides if
the device is up or down based on whether it responds to initial ping &
snmp attempts or not.
We don't run discovery on devices which are marked as down, because it
wouldn't work :D
Don't confuse the massively overlappi