Hello, yes, yesterday I tried  perform the discovery with SNMPWalk-OID but didnt work. Today, after reading your answer, I tried again and this time it work (I dont remember what was the difference between the code that I was trying yesterday and the current to make them work): [image: Capture_NETXMS_Jun022016_P1.jpg] imag The only doubt that I have regarding this is how to convert the base DCI in template. I tried to add with the option "convert to template item" but dont allow me, it dont appear in the template group that I choose. Thanks for the advice. Regards.

Hi Tomas, Thanks for the reply (and the excellent videos that got me going with NetXMS).  I think you are spot on.  I added a bridge and it now responds but only with info from the bridge, not from the switch. Not to worry, just another CRS thing that would have been nice. Thanks.

If the name of custom attribute is "Farm", then you need to use "%{Farm}". I believe its case sensitive.

Hi, currently drivers can be written only in C++. If you know C++ you can built one. To be able to create new driver we need at least MIBs for device (ideally also indicate places where to find relevant information) and either dump of SNMP walk or (preferred) access to test device over SNMP. Best regards, Victor

Hi, yes, this patch will be included into 2.0.4 release. Best regards, Victor

Hi Victor That was it.  I left out the instance in thresholds.  I initially thought that it would use the instance name in the parameter description. But all is good now. Thanx again for your speedy replies Regards

thank you very much for your help!

No, origin need to be "NetXMS agent". Yes, this is the main reason why agent needs SQLite. Usually no additional configuration required, agent will create local database in reasonable location ($install_prefix/var/lib/netxms if built from sources, /var/lib/netxms if installed from deb package). There is a bug in 2.0.3 (fixed in 2.0.4) that cached mode actually works only for servers listed as MasterServers in agent configuration. Best regards, Victor

Hello: Follow this guide , it worked for me: https://wiki.netxms.org/wiki/Add_new_MIBs

Ok, perfect.  Thanks again for the help.

You dont need to create DCIs for this. Just go to the "Interfaces" tab, all port statuses can be seen there. (and port's admin status too)

Again, this breaks basic IP communication standards. Packets like this would not traverse through any SPI firewall, or any NAT. Even basic iptables firewall on your server would block such packets. Any network device along the path that does any SPI or NAT will drop these packets. These packets will be considered as unsolicited packets, since they are not responses to any established UDP stream (because of wrong IP header). What you quoted from Juniper is for SNMP traps, which behave entirelly differently from RESPONSES to SNMP requests. Imagine if NetXMS was to implement behaviour for every vendor's broken networking/snmp implementation... That would be a very fast way to hell... The correct way here is for the vendor of your device to fix the broken implementation, not for NetXMS to adjust to a broken implementation.

Forgiveness was a bad mia settings. Is solved, thank you very much.

Hello all, I wanted to share how I have been fixing my DCI collection errors.  First, I am using a CentOS based linux server as a NetXMS host, so your commands may be a little different for your OS. NETXMS DCI Database repair steps: If DCI errors are reported in Graph Elements perform the following steps from the command line of the NetXMS linux server: service netxmsd stop mysqlcheck --auto-repair netxms -u root –p nxdbmgr check service netxmsd start Graph Elements should now populate after a few polls.

I just had to stop the firewall service, Problem resolved!! thanks

thank you Sir.

Hi, so those devices really reports VRRP virtual MAC address as interface's MAC address. Currently I've changed server to ignore VRRP and HSRP MAC addresses, so it won't try to use them for building L2 topology. However, because those devices do not provide real MAC addresses for interfaces (at least not through standard MIB) they won't appear on L2 topology map. It is actually a bug in WatchGuard's SNMP agent - it should return interface's own MAC instead of VRRP MAC even if VRRP is configured on interface. Best regards, Victor

Hi, yes, that's a problem. I think that configuration for combining DCIs into single chart should be changed to use some sort of a key - then you just specify same free form key for all DCIs you want on one chart and system combines them. This will eliminate current complexity and bugs. The only issue is that current configurations may break down during migration. Best regards, Victor

Late night update: I got the configuration to work, for some reason the mysql module didnt install during the setup so i just re ran it and it copied it over this time. Me being dumb maybe idk.

Yes, several objects can have the same name (name is more like description really). IP address of 2 objects can NOT be the same however.