NetXMS Support Forum

What is the plan for IPV6 support in NetXMS?

We changed the connection between two LLDP-capable switches:

First Switch1-Port7 connected to Switch2-Port1,
Then we changed to Switch1-Port2 connected to Switch2-Port8.

Now in [Object Details] - [Interfaces] of node Switch1 I can see Switch2 connected to Port 2 AND 7. the same MAC and the same IP-Addresse and Peer Discovery on both interfaces = LLDP. The same on Switch2.
When I look at [Tools] - [Info] - [Topology Table (LLDP)] there is only the new connection.

Is there something like a Lease Time for LLDP information?

It would be helpfull to change the image file (png) of an existing Image in the image library. So no nodes must be reconfigured. If you choose 'edit' of an image in image library you can choose another image file but on 'Ok' you get the error message "Image xy in Network Objects category already exists."

In Node Properties on register 'Communications' is an option 'This is address of remote management node'.
What is this for. I didn't found it in the documentation. And I can't remember it was there before.

Thanks

We have a few VPN connections between our sites. So I set up the VPN connectors between the internet gateways using the old legacy console. These connectors are shown in the java console under the gateway nodes (as object class VPNConnector).
Since NetXMS 1.2.14 they have also an icon (but I don't know why with a questionmark on the icon) and they appears on Layer3-maps (that's fixed, thanks)

So I see still 2 issues with VPN connectors:

1. Configuration:
The VPN connectors are still not configurable in Java console (1.2.14), whether changes nor creation.

2. Event Correlation:
When a VPN tunnel goes down, we recieve from NetXMS one 'Node down' for the remote VPN gateway (=ok). But when the VPN tunnel goes up again, we allways get 'Node up' for every node on this remote site (=not ok). It seems the event correlation on 'down' is ok but not on 'up'.

Are the Windows Agent DCIs System.AntiVirus* still broken. If yes, is it possible to fix for next release?

thanks
Dani

Is there a possibility to use windows environment variables in nxagentd.conf on windows nodes? So we could use one config-file for all windows nodes (32bit oder 64bit, English or different language). Especially %ProgramFiles% would be usefull.

We use NetXMS V1.2.13:

If you use 'Tools' - 'Shutdown System' for a linux node you get the following error (but the node is shutdown after that)
   'Execute action on node xy' has encountered a problem.
   Cannot execute action on node xy:
   Communication failure

On Windows nodes everything is fine: "Action System.Shutdown executed successfully on node xy"

I have collected a few smaller feature requests. Most of theme should be easy to implement:

1.
In Actions: a test possibility (like in Transformation scripts)

2.
In 'Actions Configuration' edit action: field 'Message text' bigger (more than 1 line) for better overview

3.
Possibility to display node custom attributes in 'Object Details' 'Overview' page. We use it for some inventory information.

4.
In Custom map: no possibility to unlink 2 objects (you have to delete one!)

5.
In Data Collection Configuration:, 'New parameter...': if you leave this dialog with 'cancel' a DCI is created anyway (an empty one).

6.
EventLog (View - Event Log): is unsorted if no sorting is selected. So most of time you have to set Ordering = Time descending. It would be convenient if 'Time descending' would be the default (but changable)

thanks
Dani

I just started to use the windows EventLog parsing and have some questions:

1.
I would like to have a quite generic parser which parses for all errors in system eventlog (all sources and all IDs). I managed that.  Than I would like to give the event-source and the event-id as parameters to NetXMS. But I only see the possibility to extract parameters out of the eventlog-description field (with regexp). In this field there are source and ID not available. I tried [<id>(.*)</id>], but that's not supported. Is there another possibility for such parsing? I can't make a rule for each possible source and each ID.

2.
I would like to parse for 'the previous shutdown was unexpected' events (source=EventLog, id=6008). But it's not possible. I suppose the agent starts parsing the eventlog when he starts up. But this EventLog-event is earlier (between system boot and start of NetXMS agent). Is there a possibility that the agent can also parse the events between system start and agent start?

3.
Is there a good website with ideas for EventLog-events which should be monitored? In some commercial network monitoring products are a lot of predefined EventLog events. Maybe someone knows a good source.

4.
What's the best solution to deliver the parser xml files to a lot of nodes?
thanks
Dani

Is it possible to use macros and/or scripts in the 'Parameter' field of DCIs? I could use it with subagents. Otherwise everything must be implemented in transformation scripts. That would be a litlle bit confusing if you only need things like node-name oder node-IP.

I have a conceptual question:
What exactly are the advatages of network services? Is using DCIs (Origin=NetXMS Agent) with the NetXMS server as the proxy node not more flexible? So you can use the huge flexibility of ExternalCommands. In network services you can't use custom schedule (yes, on the corresponding service status DCI you can). And a very important disadvantage in my opinion: In templates you can't define network services for nodes (and so you can't use instance discovery either).

Maybe I overlook a few advantages of network services.
Thanks for any help.

I miss the 'comments' tab on DCI objects for internal documentation purposes. I like to document things directly in the application and not in out-dated Word-documents. In nodes and maps objects there is already a 'comments' tab.

We have a few VPN connections between our sites. So I set up the VPN connections between the internet gateways using the old legacy console (the VPN connectors are still not available in the java console). These connectors are now shown in the java console under the gateway nodes (as object class 12 but without icon in the object tree).
But I think these connectors are not used in IP topology maps (I also set the discovery radius of the map to 10). But the map shows no VPN-connection. When I use 'IP neighbours' on one of the internet gateways I never get another gateway as IP neighbour (inspite of the VPN connectors set up in the legacy console). Do I have a misconfiguration or is there some code broken?
Current Version of NetXMS: V1.2.13.

Is there an 'official' naming convention in NetXMS or maybe a good suggestion for naming objects like:
- DCI
- Event (I see 'DC_', 'SNMP_', 'SYS_', what is the definition behind this 3?)
- EventProcessingPolicies
- Actions

A good system/convention in DCIs and Events would be the most important part.
How do others handle this?

I have the following situation:
some firewalls (call it GATEWAY1) with dynamic WAN-IP addresses. There I have to ping the default gateway of the WAN interface from the NetXMS server and the result should be shown on the node GATEWAY1.

I see two possibilities but can't find a working solution:
1.
On GATEWAY1 a DCI: Origin = Internal, Parameter = Dummy, Proxy-node = NetXMS-server. Than in transformation script SNMPGetValue (is functional) and a call of a subagnet icmp.ping. But I could't find a possibility to call a subagent from the script.
2.
put the SNMPGetValue in a script in the script library
On GATEWAY1 a DCI: Origin = NetXMS Agent, Parameter = something like 'icmp.ping(script:getip)', no proxy node

Does anybody have a hint or better a solution? I hope I described the situation accurate

I have defined on a node a Network Service type=HTTPS, Port=5001 (custom port). With the first poll the nxagentd crashes.

Request is: $node:\index.html
Response is: ^HTTP/1\.[01] 200.*

server is V1.2.11 on Linux. Debug log (D= 9) of agent on the NetXMS server shows:

---
[07-Feb-2014 12:39:49.436] [DEBUG] [session:1] Received message CMD_CHECK_NETWORK_SERVICE
Segmentation fault
---

If port is 443 there is no crash. Case is not very urgent

I just started with syslog parser for the first time. At the moment I only have 3 rules to start:

<parser>
   <rules>
      <rule>
         <match>.*Due to active connection allowed exceeded.*</match>
         <event params="0">100832</event>
      </rule>
      <rule>
         <match>.*msg=(Administrator|User) (.*) from l2tp has logged in ZyWALL.*</match>
         <event params="2">100833</event>
      </rule>
      <rule>
         <match>.*msg=(Administrator|User) (.*) from l2tp has logged out ZyWALL.*</match>
         <event params="2">100834</event>
      </rule>
   </rules>
   <macros/>
</parser>

The first is ok.
But the 2. and the 3. are always generated twice. But in internal syslog there is only one entry. (see attachments)
My install is V1.2.11 (from sources) on linux.
Thanks for any help.

would it be possible to develop a driver for cisco SMB (Small Business series 200, 300. 500) switches. I have customers using cisco smb switches. They are managable support LLDP, CDP, SNMP, STP.
Which information you would need for that?

We would like to monitor physical Windows servers with management boards (we use HP servers, there it's called iLO, they have a dedicated network port). The ilo network interface should be a second interface to the server node in netxms (we don't want 2 nodes, 1 for the server and a second for the iLO). That's manually possible. But then I have the problem that the server has a native windows netxms agent and snmp agent installed. The iLo has SNMP for themself (there it would be possible to passthrue the SNMP to the server OS. But now I can't configure the netxms server to poll the netxms-agent on the server network interface and SNMP on the iLO interface (for some hardware monitoring for example).

What would be the best configuration solution for such situations in netxms? The same situation exists in 'network services', where you also can't configure a specific node interface for a network interface.

Every input and suggestions are very appreciated