NetXMS Support Forum

Hello!

ConditionStatus() DCI is available in 0.2.20-RC3. Please note that to use it you should add node on which you configure this DCI to condition's trusted nodes list, or disable trusted nodes checking by setting global server configuration parameter CheckTrustedNodes to 0.

Best regards,
Victor

Version 0.2.20-RC3 (Release Candidate 3) is available for download from https://www.netxms.org/download/rc. Changes from 0.2.19 are following:

- Implemented advanced event processing using situations
- Added checking of NetXMS server own network connectivity via beacon hosts
- Implemented "proxy node" functionality for DCIs
- Added possibility to use values of other DCIs in transformation scripts
- Added possibility to specify multiple recipients in e-mail or SMS action
- Implemented System.CPU.Usage for individual processors on Linux
- PING subagent: added parameter ICMP.PacketLoss(*)
- Command line options for the server changed to use common style
- Added UNICODE support in client part on Linux/UNIX
- Implemented macros in template DCIs (expanded when template applies to node)
- Added event storm detection
- Added possibility to specify multiple SNMP community strings for discovery
  and configuration polls
- NetXMS server now can understand interface aliases (description in Cisco terms)
- Added optional synchronization of node names with DNS
- New command line tool for managing alarms - nxalarm
- Implemented "stop processing" option for event processing policy rule
- Implemented "move" operation for templates (move between template groups)
- New internal parameter: ConditionStatus(*)
- Fixed issues: #188, #189, #190, #191, #195, #199, #203

If nobody finds serious bugs in this RC, it will become 0.2.20 on Monday or Tuesday.

Best regards,
Victor

Hi!

Problema s kounterom v propushenom dvoetochii. Pravil'no budet

*WinPerf
Counter = NetUtilization:"\Network Interface(Broadcom NetXtreme Gigabit Ethernet)\Current bandwidth":60:A:INT:Average bandwidth utilization for last minute


A postavlennuju zadachu mozno reshit' cherez transformation script - delaetsja DCI na bytes/sec cherez interface, i v transformation script delaetsja pereschet v procenti. V tekuschej versii maximal'nuju skorost' interfeisa pridetsja v scripte zadavat' konstantoj, no nachinaja s 0.2.20-RC3 mozno budet ispol'zovat' znachenie DCI.

Primer transformation sripta (dlja 100Mbps interfeisa):


$1 / 1000000


Best regards,
Victor

I will roll out 0.2.20-RC3 today, and if nobody found any bugs, final 0.2.20 release will come out Monday or Tuesday.

Best regards,
Victor

Hello!

It's not possible to access database from NXSL. Although it's not hard to implement this functionality, it potentially can be a big security hole. But you can expect ConditionStatus DCI in 0.2.20

Best regards,
Victor

Ispravil vse krome MAC adresa. Pro MAC - mozno popodrobnee (ja vozmozno eto uze sprashival, ne pomnju tochno)?

Ja proveril, eto bag v nxmibc, v versii 0.2.20 on ispravlen.

Best regards,
Victor

Добрый день!

А какая версия NetXMS? Я вроде похожую проблему исправлял уже...
Лучше вего просто прислать мне MIB, я посмотрю где проблема, заодно и компилятор поправлю. Debug режима к сожалению нет.

Виктор

Hello!

It's not possible now, but idea is good, so I will implement a special DCI for obtaining condition status.

Best regards,
Victor

Net, ne pravil'no. Na padenie kazdogo interfeisa generiruetsja otdel'noe sobitie, i kazdoe iz nih prohodit cherez event policy. Prohozdenie sobitija zakanchivaetsja kogda zakanchivaetsja policy (vse pravila projdeni) ili vstrechaetsja pravilo "stop processing". No nezavisimo ot togo kak prekratilas' obrabotka tekuschego sobitija, budet vzjato sledujuschee sobitie iz ocheredi i process povtoritsja.

Mozno poprobovat' etot patch - nado zamenit' ber.cpp v src/libnxsnmp na prilozennij.

Net raznici, 1, 20, ili 100 - kazdoe sobitie obrabativaetsja nezavisimo. Tak chto dlja kazdogo sobitija esli uslovie sootvetstvuet i stoit stop processing - mi obrabotku etogo konkretnogo sobitija prekraschaem. No na drugie sobitija eto nikakogo vlijanija ne okazivaet.

Ja kazetsja ponjal v chem problema - NetXMS nekorrektno obrabativaet encoding OID'ov sostojashih tol'ko iz odnoj cifri. T.e. hotja


nxsnmpget -c public host .1


ne rabotaet, variant


nxsnmpget -c public host .1.3


budet raqbotat'. Mozno eto proverit'? A ja poka-chto pitajus' razobratsja kak pravil'no encodit' OID'i dlinnoj 1.

I didn't play much with new NNM 8i, but NNM 6.x and 7.x uses a slightly different approach - status of a node is depending on number of interfaces being down - for example if less than half of interfaces is down node status will be Minor, and if more than half is down - Major. If talking anout HP management products, we use approach similar to OpenView Operations - by default parent object's status equal to most critical child status, but you can change this by changing status propagation and/or calculation properties for either parent or child object.
For example, setting status calculation mode for switch node object to "multiple thresholds" and setting thresholds to Warning 0.1, Minor 0.2, Major 0.5, Critical 0.9 will give you kind of NNM-like status calcualtion for switch node.

Best regards,
Victor

A mozno tcpdump zapustit' s kljuchami -X -s 1000? Togda ja smogu sravnit' strukturi paketov.