Script will be $1 / 48 Best regards, Victor

You should compile them first. Standing in the directory where all mibs reside, run the following command: nxmibc -d . nxmibc is located in NetXMS bin directory, so on Windows you probably will need to run it as ..\..\bin\nxmibc -d . If everything goes OK, MIB compiler should produce updated file netxms.mib in mibs directory. You don't need to restart NetXMS server, just console. Console will detect that mib file is updated and download it. After that, you will see new oids in mib browser. Best regards, Victor P.S. You may also wish to add -z option to produce compressed netxms.mib, which will be significantly smaller than uncompressed.

Thanks for the speedy reply! Yes, this helps

I've send you an email with further tests

Again, thank you very much...

Hello! Looks like server you trying to get DCI from is not responding to SNMP queries from NetXMS server. Check the following: In the properties of a taget server object, go to "Cappabilities" tab and check that isSNMP attribute is "TRUE"; Check that community string and SNMP version set correctly; Check that there are no firewall between NetXMS server and target server that blocks SNMP traffic; Run configuration poll (right-click on object, then select Poll -> Configuration) and see for any SNMP-related messages. Best regards, Victor

I think it works now... !!! Thank you very much for your support.

Hello! Sorry for late reply, I'm overlooked your post. If you try to configure SNMP parameter, then you should select "SNMP agent" as origin first. After that, if you press "Select" button you'll get MIB browser and will be able to select SNMP parameter from MIB tree. Best regards, Victor

Hello! Short instruction how to get an alarm from SNMP trap: Create new event that will be generated on trap receive: go to Control Panel -> Events and select New. Create trap matching record: 2.1. Go to Control Panel -> SNMP Traps 2.2. Select New and enter EMC trap OID - for example, 1.3.6.1.4.1.1139.1.1 for emcDeviceStatusTrap 2.3. Select your newly created event as event to be generated 2.4. Add variable bindings if needed: I don't now what variables EMC devices send, but if, for example, trap contains emcSymDevStats variable, enter 1.3.6.1.4.1.1139.1.1.1.12 as variables OID. You can use values of variables in your event text by using macros %2, %3, and so on. Add alarm generation: go to Control Panel -> Event Processing Policy, add new rule, select your new event, select "generate alarm" and enter %m as alarm text. As soon as you save your policy, system will generate alarms for each SNMP trap with given OID. Of course, you can use all event processing mechanisms for events generated from SNMP traps - run scripts, send e-mails, etc. Some useful hints: You can set server's parameter LogAllSNMPTraps to 1, and then use View -> SNMP Trap Log to observe all received traps with all variables. This can be useful if you are not sure what variables are attached to the traps or exact trap OIDs used. System will not process traps from unknown devices, so you have to register your EMC device as a node. Hope this helps! Best regards, Victor

Sorry, actually solved this myself by first creating the user netxms, then giving it permissions on the database.  I've run into this issue before when installing proggies which use mysql.