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 - jonasc

#1
Atleast I've got:

SubAgent = portcheck.nsm

in the nxagentd.conf

I have no other way of checking if it's ok.
It had the value from start so I haven't added anything in the conf-file, just verified that the entry was there.
#2
Hi again!

After creating the template DCI and assigning it to the netxms.org-node I get this "UNSUPPORTED" message.
See enclosed image

Also, the "last values" page on the node is empty.
#3
Thank you very much for your wiki!!
Very serious!

I have a few comments:

1. "Special note: in NetXMS 2.0.4 and older, there was a bug that would create a node down alarm.
Please terminate this alarm on this node before proceeding further in the tutorial if running a version older than 2.0.5 (or 2.1)."

That really confused at first but now when I got it confirmed that it's a bug I'm satisfied:-) Thanks for the confirmation.


2. "We create a new DCI. Make sure Origin is set to NetXMS Agent, press Select, and find ServiceResponseTime.Custom(*)."

Why not use "ServiceResponseTime.HTTP(*)"?


3. "We will create another DCI, this one will be used to check just if the website is up or down."

Is this a redundant post?
I mean, we don't need to create two DCIs, do we?


Thanks again for your serious respons!
I didn't expect that:-)
#4
I'm a newbie too. I agree with the thread owner.

Also, "apply" maybe should be changed to "assign node" or similar.

While talking about templates...
When I have a node under a template and (while looking for how to remove the node from it) I was a second from clicking "delete" on the node under the template.
My initial thought would be that it's just a reference to the object and that the reference is being removed.
But it seems that you remove the whole node.

Thanks for your time
#5
I'm really sorry. I must be slow...

I have tried everything you describe and what was described above too.
Unsupported DCI, error with timestamp 1970-01-01 etc etc comes up.

So, I shouldn't use poller node?
Is it source node on the DCI that should be used for this purpose?

I created a template, netxms agent origin, selected "ServiceCheck.HTTP(*)".
Set source node as netxms1 (my netxms server).
Applied it to the netxms.org-node.

The status of the DCI under netxms.org is "Not supported".

- All I want to do is monitor www.netxms.org port 80 and get an alert if it doesn't respond to TCP on port 80.
This must be the worlds simplest task and I am unable to understand how I should do it.
I'm really sorry for my newbie questions. I thought 22 years of experience would be enough, obviously it's not.
#6
Anyone?
#7
Hello dear friends!

I still don't get it right...

Attached are some screenshots of what I see.
I created a new netxms.org-node

_new_node shows just what I see when I create the new node.
_polling shows the polling settings <server> is there as default, I also tried changing that to the server "netxms"
_new_dci shows the new DCI-form you all know
_parameters_empty shows what I see when I click [select]. On a node with netxmsagent installed this list is full of goodies, but not now.
For appearent reasons I can't install the agent on all websites and gear I want to monitor with TCP.

Thanks for your patience
#8
Sorry, I found poller node on the netxms.org-node.
thanks I'll give it a shot.

Update:
After changing to netxms-server as poller node on "netxms.org"-node I created a DCI and selected "Netxms agent".
This still gives me an empty parameters list when I hit [Select].

Any ideas?
thanks
#9
Thanks for your reply!
If you mean "source node" as poller node on the DCI i created on the netxms.org-node i tried that.
The problem I get is that the parameter list I expected to see when I clicked [Select] is empty.
#10
Hi!

I know that this is such a newbie question but I've tried to accomplish this for many days.
My colleagues have looked into it as well without result.

Let's say I want to monitor www.netxms.org and make sure it responds to TCP on port 80
As I understand there are some options:

1. Create a node and a network service
This is a straight forward thing but:
- According to a post in the forum this is the deprecated way and DCIs should be used instead.
- Templates cannot be used, as with DCIs
- The status calculation doesn't seem to work properly; When the service is down and comes back again the node still shows down.
   After terminating the error it goes away but after that never goes into alarm mode again even though the network service is down.

2. DCIs
This is perfect when you can use templates but since the new 'www.netxms.org'-node get SYS_DCI_UNSUPPORTED I guess it can't handle netxmsagent-DCIs.
I mean, www.netxms.org does not have the Netxms agent installed.

3. According to a forum post this should maybe be handled by adding DCIs under the netxms-server.
It feels wrong but maybe this is the way to do it?


I like number 1 best because you can see in the tree what's being monitored, the network services are added below the node and the whole supportteam can see it all clear.


So... what do you pros think the best way is?

Thanks in advance
#11
Quote from: zshnet on June 20, 2016, 09:13:46 PM
Hi there,

Not sure if this is helpful to your issue, but alt-shift-a opens the alarm page for whatever node you've selected while F8 opens the alarm browser for all alarms. My suspicion is you were opening Alt-Shift-A while selecting a container for all items in your network, which would of course not contain the deleted node. Thus, when you click F8, an extra alarm appeared because it shows all alarms, regardless of the node. Also, in my experience, deleting or unmanaging a node does not remove all alarms relating to that node, so before/after deleting it you need to delete all alarms relating to that node.

Hope that helps!
Thanks,
Zach

I wish it was that simple...
No, I was on the top level Entire Network, right click, Alarms.
By accident I went into F8 (Alarm browser) and found ID 1526 (which I recognized from the alarm_events table).
We have a dashboard where I publish active alerts from alarm_events and we wondered why a deleted node still was active.
#12
General Support / Re: Controlling PDU
June 16, 2016, 06:12:30 PM
You need to create your own.
What I have is a template called APC-PDU and to that I assign (called apply in the meny) all new PDUs so that DCIs are created for each new PDU.
Talking about "apply" I would consider changing that to "assign"...
#13
New information:

In Alarms [F8] I have one entry more than in [ALT]-[Shift]-[A].

That entry is referring to the source/node that previously was removed.
The extra entry in Alarms [F8] looks like this:

[Critical]   [1526]   Node down

It only references to 1526 instead the source name.
When I click on terminate it goes away.

A thought F8 and Alt-Shift-A would show the same things.
#14
General Support / Re: Controlling PDU
June 16, 2016, 11:10:51 AM
Quote from: biker9009 on June 15, 2016, 06:14:37 PM
Hello,

Is it possible to control a PDU using NetXMS?

I'm working with that right now. We're using APC PDUs but the MIBs from APC seem to contain some error or something because when browsing the MIB using the built in MIB Browser I can't drill down to certain OIDs other than using walks and picking the OID manually.

But yes, it works fine to monitor the PDUs.
I recommend you to use a template.
#15
Hi!

We had a node with an active critical alert and the alert was listed in the table alarm_events and also shown in the "alarms entire network" tab in the Console.
When I removed the node from the inventory the alert in "alarms entire network" was removed and all was fine.

However, the entry in the alarm_events table still holds the record as if it would be active.
My impression was that alarm_events used to contain only active alerts.

Can anyone shed some light on this?
Thanks in advance