NetXMS Support Forum

Quote from: DanG on July 27, 2012, 07:56:36 AM
What I find strange is that for all Windows PC's the interface object is unknown, NetXMS knows their IP but not their MAC. Windows machines with an agent installed do have correct interface objects, surly I don't have to install an agent on each machine to have it's MAC?

Currently NetXMS can obtain MAC address only directly from device, by SNMP or via agent. I plan to add setting MAC address for nodes without agent or SNMP based on ARP information. Hopefully it will be implemented in version 1.2.3.

Quote from: DanG on July 27, 2012, 07:56:36 AM
BTW, is there a way to obtain information about the progress of the auto-discovery?

No. There are feature request for that.

Best regards,
Victor

Quote from: djaksons on July 25, 2012, 10:01:17 AM
Хотел мониторить время работы от батарей но в программе нет переменной такого типа

Имеется ввиду TIMETICKS? Это обычный unsigned integer. Поставьте соответствующий тип в DCI, и все будет собираться корректно.

Quote from: SKYnv on July 26, 2012, 10:30:47 PM

Quote from: Victor Kirhenshtein on July 26, 2012, 10:07:21 PM
Хорошее описание по добавлению параметров получилось. Поставил как отдельный топик.

НУ тогда явно напрашивается раздел Best Practices или Tips and Tricks

Скорее wiki, но там русского раздела еще нет...

I'll try to fix it till next release.

Best regards,
Victor

Can it be that said printer was connected to port 20 before? Or it was always in port 2?

Best regards,
Victor

Either bug, or switch really does not provide state for these ports. Can you do nxsnmpwalk on .1.3.6.1.2.1.2.2 and send output to me?

Best regards,
Victor

Yes, alarm state should change to "Resolved".

Best regards,
Victor

Can you dump server objects by running command

nxadm -c "sh o" > file

and try to find records for problematic objects in that file, and send them to me?

Best regards,
Victor

Hi!

From the logs looks like a lot of IP addresses coming from node ormanage.orion.local (172.16.0.7). Log is wrapped, so I don't see beginning of the poll, but there are a lot of IPs from 172.16.47.xxx for example, almost each IP address. All these addresses coming from ARP cache. Check what this node really reports as it's ARP cache. To prevent this from happening you can disable discovery polling for that problematic node.

Best regards,
Victor

Yes, it could be useful. I'll add it as low priority feature request.

Best regards,
Victor

Hi!

Are you using 1.2.1 or 1.2.2 already? There was a major fixes and improvements regarding MAC address search in 1.2.2. If 1.2.2 is not working, can you please check MAC address table on your Cisco switch and ensure that it contains entry for your tape library?

Best regards,
Victor

Binary was built for version 1.2.2, but it will work with earlier client library versions too.

Best regards,
Victor

Server should have access to MAC address tables on your switches to be able to find exact switch port. Do you have all your switches visible to NetXMS? Also this functionality was greatly improved in version 1.2.2, so I strongly recommend to do an upgrade.

Best regards,
Victor

User must have "send events" access right on source object, i.e. if you are sending event from management server itself, user must have "send events" right on node object representing management server. This is the only requirement for that user. You can only use event codes in nxevent (it have to be fixed).

Best regards,
Victor

You can access trap-originated event's parameters in script, but only by index, like this:

$event->parameters[2]

Best regards,
Victor