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. Remote network monitoring & Create parent nodes

Remote network monitoring & Create parent nodes

Scheduled Pinned Locked Moved Support
3 Posts 2 Posters 22.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.
  • F
    F
    fdavidcn
    wrote on last edited by
    #1

    Hi guys, i have two little cuestions about NetXMS

    We have running 2 NetXMS servers in two different locations and everything works fine. My question is... is possible to use only one server to monitor the two entire networks?

    In case the answer is yes, how can i do it?

    The other question is how can i create parent nodes? For example, if we have the following diagram

    AP-------(wireless)------ST---[switch]--Node 1
                                                    |---- Node 2
                                                    |---- Node n

    If node called "ST" goes down, i dont want to receive one email for every node behind the node "ST". I want only receive one email that says "Node ST is down" and i know that the child nodes are down also. Its posible make this with NetXMS?

    Thank for support!

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

      Both of these are possible.

      1. You have to enable zoning in NetXMS.
        Then create a separate zone for each network.

      For the remote zone, you can proxy all communication to the zone through a proxying Agent (just normal NetXMS Agent with proxying enabled).

      1. This actually happens completly automatically when NetXMS has enough information about the network.
        NetXMS internally builds topology, and uses that for outage correlation.

      So if all devices properly expose topology information to NetXMS, it will just work.
      You can check by creating an L2 map with the AP as the root node.

      If the map properly shows the entire topology, then network correlation will work.

      1 Reply Last reply
      0
      • F
        F
        fdavidcn
        wrote on last edited by
        #3

        Thanks tomaskir, i will read documentation about zoning and proxy to try this.

        Thanks again!

        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