Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum

  1. Home
  2. Support
  3. How to monitor a host with TCP without agent?

How to monitor a host with TCP without agent?

Scheduled Pinned Locked Moved Support
15 Posts 3 Posters 101.4k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J
    J
    jonasc
    wrote on last edited by
    #3

    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.

    1 Reply Last reply
    0
    • J
      J
      jonasc
      wrote on last edited by
      #4

      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

      1 Reply Last reply
      0
      • J
        J
        jonasc
        wrote on last edited by
        #5

        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


        netxms_new_node.png

        netxms_polling.png

        netxms_new_dci.png

        netxms_parameters_empty.png

        1 Reply Last reply
        0
        • J
          J
          jonasc
          wrote on last edited by
          #6

          Anyone?

          1 Reply Last reply
          0
          • T
            T
            Tursiops
            wrote on last edited by
            #7

            Set the "Source Node" in your third screenshot to be your NetXMS server.
            This will tell NetXMS to run your check on the NetXMS server, but the results will display on the DCI on your netxms.org node.

            You will not see any available parameters on your netxms.org node, as it does not have an agent running on it.
            However, you can right-click on your NetXMS server node and go to Tools -> Info -> Agent -> Supported parameters.
            This will give you a list of what's available. You will have to manually enter/type the one you want to use into the DCI on your netxms.org node.

            1 Reply Last reply
            0
            • J
              J
              jonasc
              wrote on last edited by
              #8

              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.
              1 Reply Last reply
              0
              • T
                T
                tomaskir
                wrote on last edited by
                #9

                It a bit more complicated for "netxms.org", because it doesnt respond to ping.

                I created a step-by-step tutorial for you:
                https://wiki.netxms.org/wiki/Step_by_step_service_monitoring

                Please note, that for a website that responds to ping, it would be much simpler 🙂

                1 Reply Last reply
                0
                • J
                  J
                  jonasc
                  wrote on last edited by
                  #10

                  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.

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

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

                  1. "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:-)

                  1 Reply Last reply
                  0
                  • T
                    T
                    tomaskir
                    wrote on last edited by
                    #11
                    1. To make the tutorial shorter and more generic-oriented, I chose just custom port check.
                      Feel free to use actual HTTP service checking (and setup the DCI accordingly).

                    2. Its not redundant. We need this 2nd DCI for node status calculation.
                      The DCI used for node status calc must return values consistent with object status codes.
                      This is why it has the transform script, and has the "Use for status calculation" checked.

                    We cant use the ServiceResponseTime DCI, because we want to have actual historic values of the response time.
                    So this one we dont want to / cant use for status calc.

                    As mentioned, this would not be needed if the node responded to ICMP, and status poll would just use ICMP for status calculation.

                    1 Reply Last reply
                    0
                    • J
                      J
                      jonasc
                      wrote on last edited by
                      #12

                      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.


                      netxms_unsupported.png

                      1 Reply Last reply
                      0
                      • T
                        T
                        tomaskir
                        wrote on last edited by
                        #13

                        Are you sure you have the portcheck SubAgent enabled on your NetXMS server?

                        1 Reply Last reply
                        0
                        • J
                          J
                          jonasc
                          wrote on last edited by
                          #14

                          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.

                          1 Reply Last reply
                          0
                          • T
                            T
                            tomaskir
                            wrote on last edited by
                            #15

                            Ok, this will probably be much faster in person.

                            Feel free to add me on Skype at t.kirnak[at]atris[dot]sk.

                            1 Reply Last reply
                            0

                            Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                            Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                            With your input, this post could be even better 💗

                            Register Login
                            Reply
                            • Reply as topic
                            Log in to reply
                            • Oldest to Newest
                            • Newest to Oldest
                            • Most Votes


                            • Login

                            • Don't have an account? Register

                            • Login or register to search.
                            Powered by NodeBB Contributors
                            • First post
                              Last post
                            0
                            • Categories
                            • Recent
                            • Tags
                            • Popular
                            • Users
                            • Groups