Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - blingblouw

#1
General Support / Re: node status
February 11, 2021, 08:27:54 AM
Thanks for your reply. I would say that it seems to be something there causing the issue (though i've not touched EPP AFAIK)  but as soon as I remove one of these alarms it does show as up
#2
General Support / Re: node status
February 10, 2021, 04:37:54 PM
says node down which is weird. on the overview field i can see the ICMP average response time so its getting pings
#3
General Support / node status
February 10, 2021, 09:02:02 AM
Hi.

NetXMS is monitoring nodes over a VPN.Every so often, the VPN will die. When this happens, NetXMS (rightfully) marks the nodes as down but when the VPN comes back, the nodes never get marked as up.

If I manually run the status it says the following

[10.02.2021 09:00:09] **** Poll request sent to server ****
[10.02.2021 09:00:09] Poll request accepted
[10.02.2021 09:00:14] Starting status poll for node Remote-RouterOS RB960PGS-6.40.9
[10.02.2021 09:00:14] Checking SNMP agent connectivity
[10.02.2021 09:00:14]    Starting status poll on interface ether1
[10.02.2021 09:00:14]       Current interface status is NORMAL
[10.02.2021 09:00:14]       Retrieving interface status from SNMP agent
[10.02.2021 09:00:14]       Interface status retrieved from SNMP agent
[10.02.2021 09:00:14]       Interface is NORMAL for 357 polls (1 poll required for status change)
[10.02.2021 09:00:14]       Interface status after poll is NORMAL
[10.02.2021 09:00:14]    Finished status poll on interface ether1
[10.02.2021 09:00:14]    Starting status poll on interface ether2
[10.02.2021 09:00:14]       Current interface status is NORMAL
[10.02.2021 09:00:14]       Retrieving interface status from SNMP agent
[10.02.2021 09:00:14]       Interface status retrieved from SNMP agent
[10.02.2021 09:00:14]       Interface is NORMAL for 357 polls (1 poll required for status change)
[10.02.2021 09:00:14]       Interface status after poll is NORMAL
[10.02.2021 09:00:14]    Finished status poll on interface ether2
[10.02.2021 09:00:14]    Starting status poll on interface ether3
[10.02.2021 09:00:14]       Current interface status is NORMAL
[10.02.2021 09:00:14]       Retrieving interface status from SNMP agent
[10.02.2021 09:00:14]       Interface status retrieved from SNMP agent
[10.02.2021 09:00:14]       Interface is NORMAL for 357 polls (1 poll required for status change)
[10.02.2021 09:00:14]       Interface status after poll is NORMAL
[10.02.2021 09:00:14]    Finished status poll on interface ether3
[10.02.2021 09:00:14]    Starting status poll on interface ether4
[10.02.2021 09:00:14]       Current interface status is NORMAL
[10.02.2021 09:00:14]       Retrieving interface status from SNMP agent
[10.02.2021 09:00:14]       Interface status retrieved from SNMP agent
[10.02.2021 09:00:14]       Interface is NORMAL for 357 polls (1 poll required for status change)
[10.02.2021 09:00:14]       Interface status after poll is NORMAL
[10.02.2021 09:00:14]    Finished status poll on interface ether4
[10.02.2021 09:00:14]    Starting status poll on interface ether5
[10.02.2021 09:00:14]       Current interface status is NORMAL
[10.02.2021 09:00:14]       Retrieving interface status from SNMP agent
[10.02.2021 09:00:14]       Interface status retrieved from SNMP agent
[10.02.2021 09:00:14]       Interface is NORMAL for 357 polls (1 poll required for status change)
[10.02.2021 09:00:14]       Interface status after poll is NORMAL
[10.02.2021 09:00:14]    Finished status poll on interface ether5
[10.02.2021 09:00:14]    Starting status poll on interface sfp1
[10.02.2021 09:00:14]       Current interface status is NORMAL
[10.02.2021 09:00:14]       Retrieving interface status from SNMP agent
[10.02.2021 09:00:14]       Interface status retrieved from SNMP agent
[10.02.2021 09:00:14]       Interface is NORMAL for 357 polls (1 poll required for status change)
[10.02.2021 09:00:14]       Interface status after poll is NORMAL
[10.02.2021 09:00:14]    Finished status poll on interface sfp1
[10.02.2021 09:00:14]    Starting status poll on interface bridge1
[10.02.2021 09:00:14]       Current interface status is NORMAL
[10.02.2021 09:00:14]       Retrieving interface status from SNMP agent
[10.02.2021 09:00:14]       Interface status retrieved from SNMP agent
[10.02.2021 09:00:14]       Interface is NORMAL for 357 polls (1 poll required for status change)
[10.02.2021 09:00:14]       Interface status after poll is NORMAL
[10.02.2021 09:00:14]    Finished status poll on interface bridge1
[10.02.2021 09:00:14] Node is connected
[10.02.2021 09:00:14] Finished status poll for node Remote-RouterOS RB960PGS-6.40.9
[10.02.2021 09:00:14] Node status after poll is CRITICAL
[10.02.2021 09:00:14] **** Poll completed successfully ****

Why would the poll status remain CRITICAL and what can I do to reset it?
#4
General Support / Container based map
November 26, 2020, 01:11:38 PM
Hi.

I've setup NetXMS in a way that each container represents a physical site and in each container is all the network equipment for that site.

Is it possible to build a layer3 map based upon containers instead of nodes so that it is easy to see how they are interlinked without having each and every device shown?
#5
- Correctly detect LLDP capability on Mikrotik devices


Very curious about this one. I see devices are still not showing as isLLDP on capabilities also don't get anything on the layer2 topology map

EDIT: sorry, upgrade went bad. it is showing now. great!
#6
General Support / Re: Mikrotik/RouterOS isCDP
April 30, 2020, 06:37:07 PM
Hi.

I just wanted to find out if there has been any progress on this yet?
#7
General Support / Icmp.Ping in Hook::EventProcessor
February 12, 2020, 10:31:43 AM
Hi.

I have 2 questions and would like to find out if it's possible.

1) Can I use Icmp.Ping inside of EvenProcessor Hook?

I have tried to use

AgentReadParameter(server, "Icmp.Ping(" . IP . ")");

and

Icmp.Ping(IP);

However both return null?

2) The other question I have is, NetXMS SYS_NODE_DOWN event can I alter that inside of the EventProcessor?

Basically the issue I have is that in the event of major power loss or link loss, all my end sites show "down" on NetXMS, this makes it pretty difficult to figure out what is the route cause of the downtime.

What I am hoping to do is, when a down event is happening on a node, check its default route (which I currently have stored as a custom attribute per node), try and ping that, if it is down, do not continue with the event OR even better, change the event type to something else so that I can have a view on what is "down" but in a more critical state, view what is the cause of the downtime?
#8
General Support / Re: SNMP OID not supported
February 11, 2020, 01:31:11 PM
nevermind.

I am not sure why but I needed an extra .1 at the end on NetXMS
#9
General Support / SNMP OID not supported
February 11, 2020, 01:25:56 PM
Hi.

So having a weird issue.

When I try adding a DCI for an OID, netxms reports that it is unsupported. However when I use snmpwalk to query that oid, it returns a result.

I'm not really sure what kind of troubleshooting to do to really understand why this is happening.

The OID i am interested in is .1.3.6.1.4.1.41112.1.4.1.1.2 on a Ubiquiti Radio.

SNMPWalk returns

SNMPv2-SMI::enterprises.41112.1.4.1.1.2.1 = INTEGER: 1
#10
General Support / Re: NetXMS 3 automatic apply rules
October 16, 2019, 06:33:18 PM
this seems to work

return $node->sysDescription like "*CSS*";
#11
General Support / NetXMS 3 automatic apply rules
October 16, 2019, 05:29:16 PM
Hi.

Since upgrading to NetXMS v3 my template automatic apply rules don't work. They are pretty simple, could this be due to the regex change?

This is my one below. Any ideas?

return $node->sysDescription ~= "CSS";
#12
General Support / Re: FDB from Script
October 04, 2019, 11:39:50 AM
Hi.

Thanks for the response. Does NetXMS offer some paid support where I can request and pay someone to do this for me?
#13
General Support / FDB from Script
September 26, 2019, 04:33:01 PM
Hi. I am trying to find a way to do the following.

I have the MAC addresses of most devices connected to my switches on an external server.

What I am hoping to achieve is something like this in a script

1) On configuration poll, loop through device FDB
2) If there is a single MAC address on an interface, do an external call to a REST API to get a "name" for that port
3) Rename the interface in NetXMS

The reason I want to do this is that the devices connected to the switches are not running SNMP and currently NetXMS will report a specific port went offline, which is great, however it will be super helpful if it would tell me *what* went down as I have that information on a seperate server.

So my question is, is it possible to loop through the FDB from a script?
#14
General Support / Re: Count Wireless Stations
September 09, 2019, 02:40:33 PM
Quote from: Tursiops on September 09, 2019, 02:34:55 PM


I'm assuming you placed the script into your script library, created a DCI with a "Script" Origin and provided your script name as Parameter and Data Type is Integer?

Hi. No I didn't do that. Thanks, you are correct its working now. Much appreciated
#15
General Support / Count Wireless Stations
September 09, 2019, 12:35:13 PM
Hi.

I'm hoping someone can maybe assist me.

I've downloaded a template for UBNT Airmax which works perfectly, however I would like to add a new DCI that "counts" the amount of wireless stations. I tried to modify some other script but I failed. Is there anyone that can help point me in the right direction?

currently I have this, but Netxms says its unsupported

walk_oid = ".1.3.6.1.4.1.41112.1.4.7.1.1";

tube = CreateSNMPTransport($node);
if (tube == null)
  return null;

varbinds = SNMPWalk(tube, walk_oid);
if (varbinds == null)
  return null;

return varbinds->size;