SNMP Device Scan Settings Priority Scanning with Netbotz 200

DCIM_Support · ‎2020-07-04

The Priority scanning doesn't appear to work with the netbotz 200.

I have configured snmp traps to the dce server (7.5.0), but alerts only appear at the next poll interval (set to 5 minutes).

Other devices configured for Priority Scanning alert from DCE withing seconds rather than at the next poll.

Is this a limitation of the netbotz 200's?

There is a trap test function on the netbotz, but no way to see if it was received by DCE.

DCIM_Support · ‎2020-07-04

Dear Mark,

For me this is a long-known problem, the solution of which I know, but I do not know the reasons for its occurrence 😀. The solution to this problem can be found in my post .

To begin with, I highly recommend that you download the config.ini file from your problematic device and examine its section [SecureInterface]. Is there an IP-address for your target DCE-server in this section?

I will be interested in your answer.

With respect.

DCIM_Support · ‎2020-07-04

Thanks for the response.

I didn't do the initial DCE server setup and devices have only been manually added since.

So does access disabled in this mean it is turned off ?

The CurrentAISubscriber is correct.

is the TrapPort the source or destination port? there are firewalls in the network between these.

My other Netbotz 200 appears to do the traps as notifications are fast.

There are two more Netbotz 250's that are also not working as expected.

Mark.

[SecureInterface]
; APC Secure Interface (ASI):
; To add an ASI trap recipient, list the IP address in the following form:
; :,
; CurrentASISubscriber=192.168.0.1
; To remove an ASI trap recipient, list the IP or DNS name using the keyword:
; RemoveASISubscriber=192.168.0.2
; To remove all ASI trap recipients, use the keyword, value pair:
; RemoveALLASISubscribers=yes
Access=disabled
AuthenticationPhrase=APC ASI auth phrase
EncryptionPhrase=APC ASI crypt phrase
TrapPort=9952
CurrentASISubscriber=192.168.1.53:162, ISX Manager

DCIM_Support · ‎2020-07-04

Dear Mark,

Judging by your config.ini, you are all set up correctly, because only one line is important for this:

CurrentASISubscriber=192.168.1.53:162, ISX Manager

All other lines in your case do not matter.

My other Netbotz 200 appears to do the traps as notifications are fast.

I.e., all your NetBotz-200 devices already work correctly with priority scanning? I.e., do all of your NetBotz-200 devices have the above line in the config.ini file? Did I understand you correctly?

There are two more Netbotz 250's that are also not working as expected.

I want to note, that NetBotz-200 and NetBotz-250 are very different devices from different generations. And yet, did you check the config.ini files for the presence of the above line for all your NetBotz-250 devices of the new generation?

With respect.

DCIM_Support · ‎2020-07-04

Hi Spezialist,

Many thanks for your expert help.

With guidance from you posts on sorting this with an ATS, and inspecting the config.ini, I seem to have it working better on at least one. They all monitor generators via dry contacts, so I have to wait until a scheduled test to see if it has changed. An snmp set is an easy way to get the entry in.

One thing that isn't configured on most of my devices is snmp writes. Enabling this and adding snmp trap entries enabled priority scanning for APC UPS's, but not the netbotz.

Thanks again,

Mark.

DCIM_Support · ‎2020-07-04

Dear Mark,

It's nice to hear that it helped you 😀.

One thing that isn't configured on most of my devices is snmp writes. Enabling this and adding snmp trap entries enabled priority scanning for APC UPS's, but not the netbotz.

I do not understand why you can not do with NetBotz devices. I, for example, have no problems with NetBotz-200 devices.

Concerning the NetBotz-250 devices I can not say anything: these are devices of another generation. Therefore, you need to first clarify with which NetBotz devices you have problems?

With respect.

DCIM_Support · ‎2020-07-04

Both Netbotz 200 and 250. Chnages have been made and I'll have them all tested again in the next few weeks.

DCIM_Support · ‎2020-07-04

Dear Mark,

Tell us, please, could you solve your problem or not?

With respect.

DCIM_Support · ‎2020-07-04

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.