how to connect to mysql server netxms bineris

It worked Thanks for the support

Understood Best Regards, Lindeamon

understood Best Regards, Lindeamon

when you right click the node and choose "Tools" and then "Info" and then "Agent" and then "Supported parameters" what do you get ? when you select the node, does it show "isAgent" on the capabilities ?

hi victor, thank you very much. will it be fixed in the next release ? Best Regards, Lindeamon

Hi, after running NetXMS via web server, i am able to see an Overview, the alarms, the objects, and under the objects i am able to have an overview and alarms and DataView that shows the activated node. once i add a line chart to a node in my console, i am not able to check this chart from the web server although under the DataView their is a 'show the graph' icon. any idea how to activate this icon ?

so maybe it has to be taken care of in the code in a form of refresh or something like that

Also, I suppose that you have to use custom event log name, not a full path to actual .evt file. If I understand correctly, all available logs are listed in registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog. But I never works with custom Windows event logs, so I may be wrong. Best regards, Victor

It's ironic you would mention that.  I installed 1.1.7 on my workstation with MS SQL 2008 Express and started to monitor the Cisco WAP200's we have throughout our business.  I actually did this earlier this week and was going to mention it in my original post, but I didn't want to confuse the issue any further.  So, after running 1.1.7 for about 4 days now, I think I can safely say that 1.1.7 is NOT behaving the same way as 1.0.13.  When polling for Interfaces, the access points have the correct number of RA interfaces, and there are no wierd subnets. I'm wondering if I should just move to version 1.1.7.  I've considered it previously, but I've always been relunctant to introduce beta or development versions into my production environment.  I would like to keep both version running, but alot of my SNMP devices only allow for a single, trusted SNMP manager. Anyway, let me know if you would like any more information.

Hi! You can limit access to alarms only by objects - i.e. allow users to see alarms only for specific objects. This is controlled by "view alarms" access rights in object's ACL. Best regards, Victor

hi victor, the value is "2". i have done some reading and i found that i do not use port security so this is the reason for it not to work. Best Regards, Lindeamon

thank you victor

hi, basically if the a node has 1 net card and it is down the node is considered down since no ping can be accepted. lindeamon

Hi, i have to create a situation in which when an interfaces goes down, no alarm is sent for the relative node down. I have to do this for many interfaces and many nodes. I use the procedure exposed in NetXms Manual, but i have a doubt for the filtering script. Suppose we have node A with interface A and node B with interface B. I use a general script like this (in the template "show alarm when node is down") sub main() { s = FindSituation("ServiceStatus", %n); if (s != NULL) { if (s->status == "failed") return false; // Don't match rule } return true; // Match rule } and in "show alarm when interfaces is down" i set this value: Situations object:ServiceStatus Instance:%n and in Attributes:                       name=status                       value=failed. Can i use the previous general script or i Have to create specific script like the following? in "show alarm when node is down" set source=nodeA and insert the following script: sub main() { s = FindSituation("ServiceStatus", InterfaceA); if (s != NULL) { if (s->status == "failed") return false; // Don't match rule } return true; // Match rule } and in "show alarm when interface is down" set source= interface A and situations: Situations object:ServiceStatus Instance:InterfaceA and in Attributes:                       name=status                       value=failed. (obviously i repeat this procedure for interface B and node B). Thank you for help.

Great help, Thank you!:):)

Thank you very much

thank you victor.

Hi, In the Event Browser I Find SYS_AGENT_UNREACHEABLE for all servers that were shut downed. Once the servers were restarted another SYS_AGENT_UNREACHEABLE was received, followed by SYS_AGENT_OK for the servers without issues. I'm afraid the events on the Agent servers were overwritten since 22 November, as fas as I can remember there were no event to be seen. For some reason the agent starts but cannot be detected after reboot by the server. Restarting the agent service later on solves the problem. Strange. Regards, Dan PS. I had no rule, just added one

Hi! Could you please provide some additional information: actual numbers for load average reported by NetXMS and by OS tools; Output of ps fax command, exact parameter name (probably "Process.Count(apache2)"?), and result returned by parameter. Version of NetXMS agent; Result of uname -a Best regards, Victor