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. Discovery subnets mistake

Discovery subnets mistake

Scheduled Pinned Locked Moved Support
4 Posts 3 Posters 16.9k 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.
  • S
    S
    samueleorso
    wrote on last edited by
    #1

    Hi all,
    I'm using NetXMS 0.2.20 for discovering my local network.
    I launched active&passive discovery with an ip subnet filter: 10.6.0.0/21.
    The discovery process start correctly but when it find a host with incorrect netmask (255.0.0.0 instead of 255.255.248.0), it creates the subnet "10.0.0.0/8" and put all nodes inside this one (it never creates the subnet "10.6.0.0/21).
    I think this behavior is not correct, and I don't know how to correct it. Any hints???

    Another question: is it possible to create manually a subnet or moving a node to another subnet???

    Thanks a lot in advance...

    Samuele

    1 Reply Last reply
    0
    • A
      A
      Alex Kirhenshtein
      wrote on last edited by
      #2

      Hello.

      Manually add node with correct netmask (F11), server should create correct subnet, then you can run autodiscovery.

      Currently you can create subnets by hand only by changing database directly (table "subnets") - but don't change it when server is running.

      Manual moving is currently unavailable, but server should do it automatically when correct subnet is detected.

      1 Reply Last reply
      0
      • S
        S
        samueleorso
        wrote on last edited by
        #3

        Hi Alex,
        thanks a lot for your response...
        We tried to do this:
        1_Discovery of only 1 node with correct netmask (10.6.0.0/21)
        2_NetXms create the correct subnet and put the node inside it
        3_New discovery of entire subnet (10.6.0.0/21)
        4_Nextms create the 10.0.0.0/8 subnet and put all new nodes inside it
        5_The nodes with correct netmask (10.6.0.0/21) remain into the 10.0.0.0/8 subnet (NetXMS doesn't move them)

        What do you think about this behavior?

        Thanks in advance..

        Samuele

        1 Reply Last reply
        0
        • V
          V
          Victor Kirhenshtein
          wrote on last edited by
          #4

          Hello!

          It's looks like a bug... 😞 I'll check it.

          Best regards,
          Victor

          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