NetXMS Support Forum

Hi,

that seems to be a limitation of libvirt. We are currently considering implementation of Hyper-V monitoring directly without libvirt as it is done already for XEN.

Best regards,
Victor

Hi all!

NetXMS patch release 2.1.2 is out. Changes since previous release:

- Summary tables for table DCIs
- Multi-valued columns in summary tables
- Threshold violation events have current DCI value as parameter 8 (named as "dciValue")
- New agent configuration parameter TunnelKeepaliveInterval
- Optimizations in database access layer
- Improved database check procedure
- Management console:
        - Option to set root object for "Geo Map" dashboard element
        - Filter in geo map view
        - "Duplicate" button in DCI threshold editor
        - Option to show legend for performance tab graphs with single DCI
        - Fixed file upload errors in web UI
        - Option to show "Top N items" in dashboad summary table using given sorting columns
- Fixed issues: NX-1147, NX-1265, NX-1270, NX-1276, NX-1282, NX-1290, NX-1296, NX-1300, NX-1309, NX-1313, NX-1314, NX-1315, NX-1320, NX-1324, NX-1325, NX-1331, NX-1333, NX-1335

Best regards,
Victor

Попробуем сделать. Зарегистрировал в трекере: https://track.radensolutions.com/issue/NX-1337

Hi,

if topology correlation is working, device D should become red, and rest of devices and links blue. Blue in that case means "unknown" - because links and devices could be up actually, but because of failed link NMS cannot determine their status. We probably could add map option to color all unreachable devices and links in red - will discuss that internally.

Best regards,
Victor

Hi,

are you sure "NetXMS Core" service is running? If yes, check that port 4701 is listening and that firewall exception for port 4701 or process netxmsd.exe is set.

Best regards,
Victor

Hi,

server should not remove device from the map just because it's down. But if topology information was removed, then it will disappear. What is discovery protocol used for those devices with wrong locations?

Best regards,
Victor

Hi,

It looks like older agents sometimes send corrupted message which cause server to crash. We fixed server side in 2.1.2 (ignore malformed messages). Upgrading agent to 2.1.1 should also help.

Best regards,
Victor

Hi,

yes, it's possible. You can create two push DCIs and a script. Set this script as an action for your event, extract numbers from message text, and use PushDCIData function to push data into appropriate DCIs.

Best regards,
Victor

 It is internal diagnostic messages meaning that data collection scheduler was not able to work with DCI because it was locked by other part of the system. Most often it happens when DCI is locked because of database update. Other possible reason could be long running transformation scripts.
If you don't experience issues with data collection and don't get "thread not responding" alarms then you can ignore those messages.

Best regards,
Victor

Hi,

do you have wrong data collected or data is correct but not shown on the map?

For link status - could you please share screenshot of link properties?

Best regards,
Victor

P.S. You can also try to use "nxdbmgr migrate" to move data directly to target database without creating intermediate dump.

Hi,

it's a bug in DB manager, fixed in upcoming 2.1.2.

Best regards,
Victor

Hi,

could it be that objects are being deleted from the map and then re-added? Positions looks like default positions for newly added objects.

Best regards,
Victor

Hi,

you can use filtering script. If you are handling SYS_IF_DOWN event then parameters of the event will be following:

1) Interface object ID
2) Interface name
3) Interface IP address
4) Interface netmask
5) Interface index

They are accessible within script via $event->parameters[n]. For example, to process only events for interfaces Ge0/0 and Ge0/2:


ifName = $event->parameters[2];
return (ifName == "Ge0/0") || (ifName == "Ge0/2");


Best regards,
Victor

Hi,

you have to set two server configuration parameters:

SMSDriver to smseagle.sms
SMSDrvConfig to configuration string in key1=value1;key2=value2;... format. SMSEagle driver accepts the following parameters: host,port,login,password. For example:

host=10.10.10.2;port=1234;login=user;password=UserPass

You'll have to restart server after setting SMS driver parameters.

Then you can create SMS sending action as usual and use this action in event processing policy.

Best regards,
Victor