Date: Fri, 1 Dec 2006 00:06:03 +0200
Hello!
Thank you for good idea! I think it can fit into current DCI model
without huge changes in it. For now I see it as follows: you will have
additional DCI origin - SNMP table; if you create DCI of such type, you
will have access to table configuration like you described, and server
will create additional DCIs of appropriate origin and type as needed -
for storing and processing actual data. These DCIs will be realated to
table DCI, inherit threshold settings, and so on. Creating tables as
special DCI type will allow you to use them in templates as easy as
simple DCIs.
I will try to implement this in next or next after next release.
Best regards,
Victor
-----Original Message-----
From: netxms_at_christoffer.totalnett.no
[mailto:netxms_at_christoffer.totalnett.no]
Sent: Tuesday, 28 November, 2006 18:25
To: NetXMS Users
Subject: [netxms-users] Polling tables
Hi...
I've tried to put down some ideas around how to poll tables - both
static and dynamic.
See picture below how a GUI could look like. I guess the picture says
much, but I'll try to put down in words how I think.
1. First of all the user has to specify which table to monitor.
2. The user must tell how to index the data. Sometimes entries will
have different index in the table, and therefore the user should select
what is the best column for indexing. To avoid problems with unique, the
user could select more columns as primary key. More combos are created
when necessary ( max: #fields - 1)
3. The user could choose what values should be collected by
clicking a checkbox above the list. Fields used as primary keys are
disabled and cannot be collected.
4. The option "poll currently selected entries" is useful on tables
where only some entries are useful/wanted
The option "poll all table entries" is meant for dynamic tables (tables
where number of entires is not static), example; a wireless accesspoints
connected client table.
I don't know if it is possible to do this with the DCI feature with some
helper table for primary keys, or a new feature has to be added...
Anyway, the server should only ask for the table once for all entries,
not one poll per key.
I hope to see something like this in a future version of NetXMS.
Victor Kirhenshtein wrote:
Hello!
We receive wrong data when doing snmp-get on our equipment.
The problem
seems to apply to Integer OID with negative values. See example using
nxsnmpget and Net-SNMP's snmpget:
the OID 8 is STRING value and OID 21 is equivalent integer value:
NetXMS:
./nxsnmpget -c public -v 2c 10.0.0.1 1.3.6.1.4.1.161.19.3.2.2.8.0
.1.3.6.1.4.1.161.19.3.2.2.8.0 [04]: -57 dBm
./nxsnmpget -c public -v 2c 10.0.0.1 1.3.6.1.4.1.161.19.3.2.2.21.0
.1.3.6.1.4.1.161.19.3.2.2.21.0 [02]: 198
Net-SNMP
snmpget -c public -v2c 10.0.0.1 1.3.6.1.4.1.161.19.3.2.2.21.0
WHISP-SM-MIB::radioDbmInt.0 = INTEGER: -57
snmpget -c public -v2c 10.0.0.1 1.3.6.1.4.1.161.19.3.2.2.8.0
WHISP-SM-MIB::radioDbm.0 = STRING: -57 dBm
Yes, there are an error in BER decoding function. I'll fix that and send
you a patch.
I have a wireless accesspoint that we want statistics from.
The data is
availible in an SNMP table. The challenging thing is that the
number of
clients connected is dynamic. How do I configure a DCI collection to
collect data from a table?
The dump of a table could look like this:
Client Name / Mac-address / Signal Strength / Noise Ratio
client 1 / 00:00:00:00:00:a1 / -58 / 0
client 2 / 00:00:00:00:00:a2 / -64 / 0
client 3 / 00:00:00:00:00:a3 / -23 / 0
client 4 / 00:00:00:00:00:a4 / -50 / 0
The only way you can collect table data in DCI is to configure different
DCI for each (possible) table element. For example, if you have table
with base OID .1.2.3.4 and you have instances from 1 to 5, you can
configure five DCIs: from .1.2.3.4.1 to .1.2.3.4.5. If you don't need to
collect a history, but only need to look at a current values, you can
define a table tool which will show you content of an SNMP table.
Unfortunatelly, GUI for defining SNMP tables is not ready yet, so you
have to define such tools directly in SQL database, which may be a
little tricky. If you need object tool definition, send me an OIDs, and
I'll send you all required SQL statements to add it.
Also, do you have any ideas how NetXMS server should collect/handle
table data?
Is it possible to to make NetXMS to send a snmpset before
doing snmpget?
It's not possible at the moment. I will add it to the TODO list.
Best regards,
Victor
421 4.3.0 deliver: couldn't connect to lmtpd
