NetXMS Support Forum

Hello!

Looks like server you trying to get DCI from is not responding to SNMP queries from NetXMS server. Check the following:
1. In the properties of a taget server object, go to "Cappabilities" tab and check that isSNMP attribute is "TRUE";
2. Check that community string and SNMP version set correctly;
3. Check that there are no firewall between NetXMS server and target server that blocks SNMP traffic;
4. Run configuration poll (right-click on object, then select Poll -> Configuration) and see for any SNMP-related messages.

Best regards,
Victor

Hello!

Looks like you have libstdc++ installed in unusual place or not installed at all. First, try to find if there are libstdc++.so anywhere on your system. If you will found it, try to put a symbolic link to it to from some usual lib directory, like /usr/lib or /usr/lib64 (32-bit and 64-bit respectively, depending on where you will find the file). After that, try to remove all the .la files so the libtool not get them.
If you will not find libstdc++.so anywhere, then you need to (re)install gcc package from somewhere (I'm not very familar with Solaris, so I cannot provide you with exact location for correct package).

Best regards,
Victor

Hello!

Sorry for late reply, I'm overlooked your post. If you try to configure SNMP parameter, then you should select "SNMP agent" as origin first. After that, if you press "Select" button you'll get MIB browser and will be able to select SNMP parameter from MIB tree.

Best regards,
Victor

Hello!

It's a libtool on Solaris problem. There are a solution: http://forum.sun.com/jive/thread.jspa?threadID=73150&tstart=45

Hope this helps!

Best regards,
Victor

Also, I suggest you to upgrade to 0.2.13, where shutdown/startup procedures was improved.

Best regards,
Victor

Hello all!

Version 0.2.13 is out!
(Actually, we already found and fixed small bug in console, so it's now 0.2.13-hf1).

Changes from previous version:

- Implemented central (stored on server) agent configs
- Agent ported to IPSO
- Added installer command line options for unattended installation of
  Windows agent
- New MIBs added: S5-ETH-MULTISEG-TOPOLOGY-MIB, BN-IF-EXTENSIONS-MIB
- Server startup and shutdown procedures improved
- Added detection of lost database connections and automatic reconnect
- Native operating system read/write locks used whenever possible
- Added possibility to use alarm message text in actions (if action executed by
  the same event processing rule as alarm)
- Better handling of interface names of Nortel ethernet switches
- SNMP trap varbinds now can be mapped to event parameters not only by OID,
  but also by position in trap PDU
- Windows binaries built against OpenSSL 0.9.8b
- Windows console:
  - DCI history data viewer improved
  - Graphs improved
- nxsnmpset utility improved
- nxevent: added -e command line option to turn on session encryption
- Implemented parameter UPS.Load for BCM/XCP compatible devices
- Fixed issues: #4, #20, #47, #67, #79, #80, #91, #92, #93, #94, #95, #96, #97,
                #98, #99, #100, #101, #102, #103

Best regards,
Victor

Is there any messages in log file or system event log? Also, try to run

nxdbmgr check

to check database consistency.

Best regards,
Victor

Hello!

Short instruction how to get an alarm from SNMP trap:

1. Create new event that will be generated on trap receive: go to Control Panel -> Events and select New.
2. Create trap matching record:
2.1. Go to Control Panel -> SNMP Traps
2.2. Select New and enter EMC trap OID - for example, 1.3.6.1.4.1.1139.1.1 for emcDeviceStatusTrap
2.3. Select your newly created event as event to be generated
2.4. Add variable bindings if needed: I don't now what variables EMC devices send, but if, for example, trap contains emcSymDevStats variable, enter 1.3.6.1.4.1.1139.1.1.1.12 as variables OID. You can use values of variables in your event text by using macros %2, %3, and so on.
3. Add alarm generation: go to Control Panel -> Event Processing Policy, add new rule, select your new event, select "generate alarm" and enter %m as alarm text. As soon as you save your policy, system will generate alarms for each SNMP trap with given OID. Of course, you can use all event processing mechanisms for events generated from SNMP traps - run scripts, send e-mails, etc.

Some useful hints:

1. You can set server's parameter LogAllSNMPTraps to 1, and then use View -> SNMP Trap Log to observe all received traps with all variables. This can be useful if you are not sure what variables are attached to the traps or exact trap OIDs used.
2. System will not process traps from unknown devices, so you have to register your EMC device as a node.

Hope this helps!

Best regards,
Victor

Hi all!

NetXMS version 0.2.12 is out!

Changes from previous version:

- Added possibility to define complicated conditions using "condition" objects
- Implemented RADIUS authentication for NetXMS users
- Added support for compressed MIB files
- New MIBs added: ENTITY-MIB
- Added support for DRBD device monitoring
- Windows console: Event editor improved
- UPS subagent:
  - Redesigned to improve stability and performance
  - Added parameter UPS.OnlineStatus
  - Fixed problem with occasional APC UPS disconnections
- Fixed issues: #89

Best regards,
Victor

Hello!

See reply in Installation board.

Best regards,
Victor

Hello!

To compile NetXMS on Windows, you have to have the following packages and libraries:

1. Latest Microsoft Platform SDK
2. OpenSSL library. Currently we use 0.9.8a, but any other recent version should be ok.
3. Scintilla library (used only by GUI components)
4. ZLib
5. Microsoft Speech SDK (used only by GUI components)
6. Windows DDK (XP or 2003 version)
7. GD library (used only by nxhttpd)

Everything should be built with VC++ 6.0.

Hope this helps!

Also, we are starting to provide commercial NetXMS support. Detailed information will be published on our web site very soon, so you can contact us if you ar interested.

Best regards,
Victor

NetXMS Forum is open! I hope it will be useful.

Victor