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. Issue with NetXMS misidentifying subnets

Issue with NetXMS misidentifying subnets

Scheduled Pinned Locked Moved Support
6 Posts 4 Posters 25.3k 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
    SignalTom
    wrote on last edited by
    #1

    Hello,

    I've got a very strange issue where when its mapped our network its not picked up some of the subnets correctly.

    In our datacentre we run a 10.10.10.0/24 subnet. However when NetXMS was setup last week its detected (what was) the only server (NetXMS) setup as a 10.10.10.56/29 network.
    Its later discovered the 10.10.10.0/24 network as well as the other genuine networks a /27 public range, a /30 on 10.1.1.0/30.

    Checking every interface on the servers I can only see the /24 so I'm at a loss to how it found this network, or how to change it.

    1 Reply Last reply
    0
    • Z
      Z
      Zebble
      wrote on last edited by
      #2

      The device(s) that are being detected with that 10.10.10.56/29 should be showing up under that subnet folder so you should be able to narrow down the culprit...

      1 Reply Last reply
      0
      • J
        J
        Kriptoker
        wrote on last edited by
        #3

        I have the exact same issue. And as the first poster stated, it is not a device out on the network being detected. It is the server NetXMS is installed on itself that is being detected incorrectly.

        Also, under the 'Infrastructure Services' section, where the NetXMS server is listed. The Ethernet Interface shows the incorrect /29 subnet as well.

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

          What OS it is? If possible, please provide output of ifconfig -a for Linux or ipconfig /all for Windows.
          Do you have NetXMS agent also running on the server? If yes, please provide output of command
          nxget -l 127.0.0.1 Net.InterfaceList

          Best regards,
          Victor

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

            Hi Victor,

            On the Windows Server hosting my NetXMS install, the ipconfig /all reports back just the expected information.

            Is the agent part of the server install package? I see a NetXMS Agent service running, but I did not install one of the separate agent packages available on the downloads page. All that is installed, is what came with the Server Install Package.

            ipconfig /all output -

            Ethernet adapter Ethernet0:

            • MAC Address: 00-50-56-B5-0D-B0
            • DHCP Enabled: No
            • Autoconfiguration Enabled: Yes
            • IPv4 Address: 100.100.110.100(Preferred)
            • Subnet Mask: 255.255.255.0
            • Default Gateway: 100.100.110.1
            • DNS Servers: 100.100.110.250
                                      10.80.1.250
            • NetBIOS over Tcpip: Enabled

            I did attempt to shut down the NetXMS application, and go in and change the Mask to /24 from /29 directly in the database. It appeared to fix it for a short time, and then it changed it back to /29. I also have this alert showing for the Server in question: Invalid network mask /29 on interface "Ethernet0", should be /24

            Edit:
            I tried running that agent command and it looks like maybe I somehow installed the agent with the server install package.

            Here is the output for the command:
            c:\NetXMS\bin>nxget -l 127.0.0.1 Net.InterfaceList
            12 100.100.110.100/24 6(1500) 005056B50DB0 Ethernet0
            1 ::1/128 24(2147483647) 000000000000 Loopback Pseudo-Interface 1
            1 127.0.0.1/8 24(2147483647) 000000000000 Loopback Pseudo-Interface 1

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

              Hi Victor,

              Just to provide a bit more info as far as my config goes. I did go in and actually manually change the IP Subnet directly in the database (while the system was powered down). This did seem to work for a short time, but then it auto changed back to /29.

              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