NetXMS Support Forum

As requested, I have attached the log file.  I wasn't able to attach the screen shot of the discovery settings (my attachment was over 1MB in size, your message board declined to accept it).  I will see if I can create a smaller image file, and then post it if possible.

In looking at the log entries, I do seem to have some database corruption...


Thanks for your help!

-Kevin C.

I have upgraded to 1.2.5, and this issue persists.

I even removed the subnets and let it re-discover, which it did, but again the routers themselves for those last 10 subnets are not being discovered.  However, some printers and managed switch devices on each of those subnets are being discovered.

I could manually add the routers, but - any ideas on what to check, or what would cause this?


-Kevin C.

Great to hear!

Is it OK to upgrade directly from 1.2.3 to the latest 1.2.5 version?  We are running NetXMS on CentOS.


Thanks,

-Kevin C.

Greetings,

I have a situation where discovery has been working fine, on my first 40 subnets. I have been adding subnets 10 at a time to the discovery configuration.

On the last 10 subnets I added, discovery actually discovered some devices within the remote subnets, however, the routers themselves for those subnets, and also some other devices within the remote subnets were NOT discovered (or at least, not displayed).

I am using version 1.2.3.  Any help is appreciated!


-Kevin C.

OK great, thanks Victor!

I am now monitoring 50 remote networks, and so far I am happy with NetXMS (and I have yet to upgrade to the latest 1.2.4 version)!


-Kevin

Hi Victor,

Has this issue been fixed with v1.2.4?  If not, could you provide me with the bug #, so I can track it.


Thanks!

-Kevin

Hi Victor,

I spoke with our network provider; they do not believe that the remote router being "hidden" from a traceroute would have any impact on the NetXMS server knowing the route to the remote devices.

You mentioned that it it often does not work as expected - is this a known bug?


-Kevin

Ah, of course.  I did not take into account the 59 minutes, and 59 seconds!  I will also look at the Saturday and Sunday code example you provided.


Thank you!

-Kevin

Greetings,

I believe I see the problem: Our NetXMS server does not see the remote router on our MPLS network when doing a traceroute to a node behind that remote router.  I will inquire with our network provider about this, as I would much rather have the server do this, rather than having to configure a situation for each remote subnet.


-Kevin

I am happy to report that Active Discovery is working fine now.


-Kevin

Hi bjet,

Actually, I am quite new myself to NetXMS, and still in the learning curve.  I still do not have it deployed to all of our subnets.

When I started out, I had the same issue that you have, and I was getting alerts like crazy (NetXMS discovered our entire network).  So, I ended up dropping the database completely, and starting over. Now what I do is I define address filters first (in the Network Discovery Configuration) by checking "Accept node if it is within given range or subnet". I happen to use IP address ranges, because we have a lot of DHCP devices in the upper end of each range, and I don't need to monitor them. After that, I proceed and add subnets to the Active Discovery Targets. The other thing I did was modified some of the "fine tuning" parameters in Server Configuration because of the size of our network.

I'm not sure if this is the best way, but it worked for me.  I hope this helps!


-Kevin

Hi bjet,

I do believe that what you experienced is expected behavior with Active Discovery - I experienced the same.


-Kevin

Hi Victor,

My goal is to not get any node down alerts between 6pm and 10pm.  I have this filtering script in my event policy - this is my first script, so please bear with me :-)

sub main()
{
   now = localtime();
   return (now->hour <= 18 || now->hour >= 22);
}

It is not working (I receive alerts during the time window).  Also, after I get this working, I will need to specify another time window for the weekends (Saturday and Sunday).


Any advice is appreciated!

-Kevin

Greetings,

Passive discovery seems to be working fine, but active discovery stopped working after I made some changes to the discovery filters (and restarted the XMS server); see the attached screen shot.


-Kevin

Greetings,

I have set:

UseFQDNForNodeNames

To "0". However, newly discovered nodes (Windows servers) are still showing up in the console with FQDN's, instead of just the host name.  Is my understanding of this setting correct, or perhaps I need to make another setting change somewhere else?



-Kevin