Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - zsing82

#16
General Support / Need help troubleshooting
October 12, 2012, 04:47:29 PM
I have NetXMS 1.2.3 setup on Windows 2008 R2 64-bit.  One of my nodes is a SonicWall TZ210.  Firmware is SonicOS Enhanced 5.8.1.8-57o.  This firewall is the default gateway for all my servers, with custom NATs for my hosted services.  It is also configured for SSLVPN Access.  SonicWall TZ210 IP address is 192.168.1.99.  When SSLVPN client connects to SSLVPN router, the client gets an IP address from a static pool configured within the TZ210.  (FYI, I have DHCP on my domain controller configured to issue 192.168.1.100-200.  SSLVPN static pool is 192.168.1.201-215)

At random times (I believe during configuration polling...?), an alarm is generated saying that SonicWall TZ210 node is down.  When I check the node in NetXMS console, I notice the Primary IP Address has changed.  The IP address is different sometimes, but it's always within the static pool for SSLVPN clients.  After the Primary IP address changes, none of the details or DCIs are available.  I can go into Node Properties and manually change the IP address back to 192.168.1.99, then run a Configuration Poll and everything is back to normal.  Then, at some point, the IP address will change back to an IP within the SSLVPN static pool.

So, my question is kind of loaded, but how can I troubleshoot this?  I'm not sure if it's something in the SonicWall or NetXMS.  Any help is appreciated.  Thanks in advance!!
#17
General Support / Re: Difference between parameters
October 11, 2012, 01:40:12 AM
Is there documentation anywhere that details the NetXMS agent and sub-agent parameters?  I'm currently trying to differentiate between System.CPU.Usage and System.CPU.LoadAvg from NetXMS Agent 1.2.3 on Windows 2008 R2 x64.

I'm sure there are many in the community who would like to have a table with specific descriptions of each NetXMS Agent parameter.  Maybe it's already documented and I'm just not paying close enough attention.  If anyone knows, please post a link.  Thanks!
#18
General Support / Agent on Mac OS
September 20, 2012, 05:25:05 PM
Hello.  I'm wondering if it's currently supported to install NetXMS agent on Mac OS.  I have a customer with an Apple environment, all clients and servers are using Mac OS.  This customer only calls me when he believes his switches, routers, or firewall are giving him problems.  I'm not very familiar with Mac OS, but my customer is.  Is there a way I can install NetXMS agent on my customer's Mac servers so I can monitor performance?  If NetXMS agent cannot be installed on Mac OS, does the server operating system have a SNMP agent that can be installed/enabled?  Any help would be greatly appreciated!!  Thank you.
#19
General Support / Auto bind script
February 29, 2012, 06:11:13 PM
Is this syntax correct?  I've manually ran configuration polls, but nodes aren't binding.  We have 5 IP cameras and Video server.  I created a Container in "Infrastructure Services" named "Camera" and configured Automatic Bind Rules with the following script:

sub main()
{
return $node->ipAddr == "10.0.0.18" ||
return $node->ipAddr == "10.0.0.92" ||
return $node->ipAddr == "10.0.0.93" ||
return $node->ipAddr == "10.0.0.94" ||
return $node->ipAddr == "10.0.0.96" ||
return $node->ipAddr == "10.0.0.97";
}
The cameras are configured with static IPs listed above, except for 10.0.0.18, that is our video server, also configured with static IPs.  I just want to container to autobind based on the IP address of the node, as opposed to manually right-clicking the node, selecting "Bind" and navigating the hierarchy tree.  Am I doing this correctly?
#20
General Support / Re: Lots of Wierd Subnets
December 16, 2011, 04:09:17 PM
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.
#21
General Support / Re: Lots of Wierd Subnets
December 15, 2011, 04:51:00 PM
1.  What is NetXMS server version?
1.0.13
2.  What driver is selected for those devices (you can see it on object overview page) - relevant only for version 1.1.x?
Not relevant, using version 1.0.x
3.  Result of nxsnmpwalk for the following OIDS:
SNMPWALK results attached in TXT file

Attached TXT file is for 2 access points.  I can provide SNMPWALK of other 3 access points if you'd like.
#22
Feature Requests / Clients with Dynamic IP address
December 14, 2011, 04:28:51 PM
I'm wondering if it would make more sense to create nodes and assign ID numbers based on MAC address as opposed to IP address/DNS name.  I have seen duplicate nodes of the same laptop in my NetXMS setup because the user will come in to the office, obtain an IP address and work, then not return to the office until next week.  By that time, his DHCP license has expired and receives a new IP address, so when AutoNetworkDiscovery runs, it adds a new node with new ID number.  Not sure if that makes sense or is feasible in any way.

Please let me know what you think.
Zac
#23
General Support / Lots of Wierd Subnets
December 14, 2011, 04:20:43 PM
Hello all.  Been using NetXMS for about a year now, but this is my first post.  I've been using NetXMS to monitor the throughput on the trunk ports of all my switches.  I'm also using it to monitor basic node status of various devices, such as routers, printers, IP Cameras, etc.

We recently upgraded our wireless network to provide full WiFi coverage over our entire property.  We installed 5 Cisco WAP200 access points across our internal/private network.  They're configured with Static IP, and only broadcasting 802.11g using WPA2-PSK with AES encryption.  We're not using any VLANs and the wireless SSID that clients connect to is the same subnet that our wired clients and servers connect to (192.168.1.0/24).  The management addresses for all access points are also on the same subnet (192.168.1.0/24).

So, here's my problem:  Whenever NetXMS polls the WAP200's, I get a bunch of wierd subnets under "Entire Network"  There are a bunch of 0.0.0.0/28, 0.0.0.0/32, 0.0.0.0/19 subnets.  Even more wierd ones are 0.0.0.48/28, 0.0.0.152/30, 37.0.112.0/24, 110.32.32.46/31, and lots of others.

I'm wondering if I've configured something wrong in NetXMS.  I downloaded and recompiled all of Cisco's Wireless MIBs into NetXMS, but that didn't change the behavior.  If anyone could please provide some insight as to what is going on, I would greatly appreciate it.  I'm hoping that this is a bug and can be fixed in a new release or that this behavior can be remedied by changing a setting somewhere. Thank you in advace.

Zac
P.S.  Great product and looking forward to upgrades in the future.

---[UPDATE]---
There are still wierd subnets being added to "Entire Network" but now, each Cisco WAP200 has multiple duplicate interfaces.  They all seem to have the same MAC address, but there are wierd IP addresses and subnet masks with each. (Never seen a 47.0.115.0 subnet mask.)

Initially, each WAP200 would have 7 interfaces, br0, eth0, and ra0 - ra4.  The bridge and ethernet have the same MAC and the RA interfaces have a different, but similar, MAC.  (For instance, BR0 and ETH0 have D0-C2-82-E7-DC-6C while RA0-RA4 have D0-C2-82-E7-DC-68).  Another wierd going-on is the "Slot/Port" number.  These seem to be randomly generated when browsing from interface to interface within the same node.

Again, any insight is much appreciated.