NetXMS Support Forum

Hi,

you can install agent and then use Process.Count(exe_name) parameter to monitor how many instances of given process are running, and setup threshold to raise an alarm when it is 0 (or below any other required number). There are video tutorials available on setting up basic stuff like installing agent, configuring thresholds, event processing rules, etc.

Best regards,
Victor

Do you see correct MAC address on workstation's interface? If yes, is this MAC address present in FDB table you see in console and is it the only MAC address on a port?

So the problem is not with reading FDB, but with internal logic. Can you run manual topology poll (from Poll->Topology context menu) on Cisco switch and your workstation and show results?

Hi,

do you remember what exact version you were using before? From the log it seems that driver cannot receive anything from serial port, and there were no changes in driver code since 1.2.12.

Best regards,
Victor

I just noticed that you check FDB on switch using object tools. What is shown if you use Topology -> Switch forwarding database context menu on switch?

Is it all MAC addresses that should be? If not, try to use community@vlan for different vlans (for example, public@100 as community string for vlan 100) - will it report all MAC addresses? Also please do walk on .1.3.6.1.2.1.17.4.3.1.2 and .1.3.6.1.2.1.17.4.3.1.3 (or just one walk on .1.3.6.1.2.1.17.4.3.1).

Best regards,
Victor

Hi,

check if you have -D0 in service command line. If yes, remove it.

Best regards,
Victor

Could you please send result of SNMP walk on .1.3.6.1.2.1.17.4.3.1.1 for that switch?

Best regards,
Victor

Hi,

logic behind node down/node up is following:

if status poll detects that all interfaces and agents are not responding, it marks node as unreachable. Then it checks network path - for nodes behind proxy it involves proxy checking. If server considers proxy node down, it marks current node as having network path problems and generates SYS_NODE_UNREACHABLE event, otherwise SYS_NODE_DOWN is generated. When contact with node restored, SYS_NODE_UP generated. To distinguish between SYS_NODE_UP generated from down nodes or nodes with network path problems, SYS_NODE_UP comes with parameter number 1 set to 0 if node recovered from "down" state or 1 if node recovered from "network path problem" state.

Is it possible that you had proxy node down?

Best regards,
Victor

You should set full path to log file in LogFile parameter in nxagentd.conf.

Best regards,
Victor

Hi,

what driver is selected for this Cisco switch (you can see it on object overview page)?

Best regards,
Victor

Hi,

I've fixed startup scripts, thank you!

Best regards,
Victor

Hi,

I suppose you mean NetXMS client (GUI application), not agent?

Best regards,
Victor

Hi!

Do you have zones and agent set as proxy for zone, or it is set as proxy for individual nodes?

Best regards,
Victor

Hi,

try to switch agent logging to file if it's not done already (by changing LogFile parameter in nxagentd.conf), set debug level to 6 (by adding DebugLevel = 6 to nxagentd.conf) and run agent for some time. After you got some agent unreachable errors, post your log file (or send it to [email protected]).

Best regards,
Victor