NetXMS Support Forum

Fixed by now. We had lot of broken files in this release due to error during upload.

Best regards,
Victor

Hi!

Put attached ssleay.dll to NetXMS bin folder. It's new dependency, and I forgot to include it into installer. Repacked installer will also be available in few hours.

Best regards,
Victor

Hi!

Please send output of configuration poll.

Best regards,
Victor

Quote from: Taomyn on July 21, 2013, 10:50:12 PM
Have the files not fully been added to your site as https://www.netxms.org/download/netxms-1.2.8-x64.exe keeps coming down as corrupted?

Yes, looks like some files was corrupted. Now correct versions are uploaded.

Best regards,
Victor

Hi all!

NetXMS version 1.2.8 is out. Changes since previous release:

- Support for data collection using SM-CLP protocol
- Aggregated DCI values on cluster objects
- Transformation scripts for table DCIs
- Support for multi-column keys (instances) in table DCIs
- Implemented SNMP table DCIs
- Configurable DCI summary tables
- Default background color for new network maps made configurable
- Logged in users cannot be deleted
- Empty containters have "Normal" status instead of "Unknown"
- New NXSL functions: AgentReadTable, DeleteObject, GetDCIRawValue
- Map objects can have status calculated from contained objects' status
- SNMP trap listener port now configurable
- HP-UX agent improved
- Some D-Link MIBs added to distribution
- Debian binaries built in UNICODE mode
- Management console:
   - Simplified table DCI configuration
   - Charts can be created from table data
   - Severity filter in dashboard element "Alarm Viewer"
   - Zoom level can be configured for "Network Map" dashboard elements
   - Values of custom attributes can be used in object tools
   - Vertical orientation for dial chart elements
- Web UI:
   - Single sign-on support using CAS
   - Configuration file nxmc.properties can be placed outside of war file
   - Workbench layout and user preferences saved between sessions
- Fixed issues: #57, #58, #195, #198, #262, #277, #281, #284, #286, #291, #293

Best regards,
Victor

E.T.A. is today Most components already packed, I'll put everything on to web site during the day.

Best regards,
Victor

Having no encryption password means that encryption is not used. Try the following command:

nxsnmpwalk.exe -u private -a SHA1 -A private 192.168.my.ip .1.3.6.1.2.1.1

Best regards,
Victor

Encryption password (option -E) seems to be missing. Otherwise command is correct.

Best regards,
Victor

Hi!

Looks like broken build. I'll make sure that versions for 1.2.8 will match, so you'll be able to use it after upgrade.

Best regards,
Victor

Looks like server connects to loopback for some reason and so reads data from it's own agent. Can you please try to remove "wrong" duplicate nodes (with agent marked as presented) and see if they will reappear? Is it possible to determine if duplicates was created by 1.2.7 or previous server version?

Best regards,
Victor

Hi!

Looks like problem is with SNMP communications. Can you try to get something from the switch using nxsnmpwalk command line tool? Please send me the output of nxsnmpwalk of .1.3.6.1.2.1.1 MIB. Also, what SNMP version you are using? What authentication/encryption if SNMP v3?

Best regards,
Victor

Hi!

What is the configuration poll output for 2510? As you cannot get interface list, I suspect that it does not respond to SNMP requests from NetXMS server, and so topology cannot be built correctly.

Best regards,
Victor

Hi!

It makes perfect sense. I was thinking for some time about representing different entities as separate object classes. Main reason why this not implemented yet is lack of resources (time and/or staff).

System itself can be expanded this way quite easy, and creating new object classes is not a big issue. Also, we already have implemented APIs which allow creation of server modules and corresponding UI plugins to provide additional object classes, so it is even possible to have custom objects. Creating such extension, however, requires good understanding of server and GUI internals.

Another possible option is to allow user to configure custom objects. It can be some simple extension to container (or just allow containers to have DCIs) which allows data collection. Actual data for DCIs defined on such objects can be read from nodes using "proxy node" option in DCIs or transformation scripts.

Some workarounds also exists - for example, you can create additional "fake" nodes without IP address to represent components, and use same proxy node and/or transformation script technique to get data.

Best regards,
Victor

Hi!

This issue should be fixed in 1.2.8 release.

Best regards,
Victor

Hi!

Can you gather more information about these nodes? Also, could it be situation when node with agent has DHCP-assigned address which is reassigned to node without agent?

Best regards,
Victor