NetXMS Forum

Hi! Still not fixed... Workaround should work however - run legacy console if possible and create connectors from there. Best regards, Victor

OK, maybe I should clarify a little bit.  The IP address that is bound to the X0 (LAN) port on my TZ210 does not change.  It is always 192.168.1.99.  It is only within NetXMS that shows the primary IP address as something from the Static IP pool for SSLVPN clients.  The actual IP address on the device never changes.  I can always pull up a web browser and administer the TZ210.  But, within NetXMS, after the node's Primary IP address is changed from 192.168.1.99 to an IP from the static pool, NetXMS shows the node as "DOWN" and none of the DCI's work, presumably because NetXMS is trying to communicate via an IP address from within the static pool, and not the IP that is bound to the X0 port. What is the mechanism used to determine a nodes Primary IP Address?  Also, what polling occurs at regular intervals?

Core agent already can be compiled and installed on OS X, however platform subagent in early stage of development. I just started it a week ago, and I think it will be included in 1.2.4 release. In a meantime, you can use SNMP, according to Apple it's included in Server version of OS. Instructions: http://support.apple.com/kb/TA20884

Hi! The correct syntax will be return $node->ipAddr == "10.0.0.18" || $node->ipAddr == "10.0.0.92" || $node->ipAddr == "10.0.0.93" || $node->ipAddr == "10.0.0.94" || $node->ipAddr == "10.0.0.96" || $node->ipAddr == "10.0.0.97"; Best regards, Victor

Support for clients with dynamic addresses is partially here - you an replace primary IP address with DNS name, and then server will do name resolution at each poll. Looks like we need additional option to use DNS name instead of IP address for discovered nodes, then this problem will be solved completely. I'll add this to my to-do list. Best regards, Victor

It's ironic you would mention that.  I installed 1.1.7 on my workstation with MS SQL 2008 Express and started to monitor the Cisco WAP200's we have throughout our business.  I actually did this earlier this week and was going to mention it in my original post, but I didn't want to confuse the issue any further.  So, after running 1.1.7 for about 4 days now, I think I can safely say that 1.1.7 is NOT behaving the same way as 1.0.13.  When polling for Interfaces, the access points have the correct number of RA interfaces, and there are no wierd subnets. I'm wondering if I should just move to version 1.1.7.  I've considered it previously, but I've always been relunctant to introduce beta or development versions into my production environment.  I would like to keep both version running, but alot of my SNMP devices only allow for a single, trusted SNMP manager. Anyway, let me know if you would like any more information.