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. Lost Node

Lost Node

Scheduled Pinned Locked Moved Support
3 Posts 2 Posters 23.1k 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.
  • K
    K
    kummerr
    wrote on last edited by
    #1

    Greetings...

    I recently replaced a Cisco switch and used the same IP address when configuring the new switch.  The new switch is working as expected, but NetXMS will not recognize the new device.  Before adding the new switch I deleted the old node and then I tried to create a new node with the same IP, but I get an IP conflict error (see attached screenshot). 

    The log file indicates an object as a "lost_node" which I'm sure is the new switch.

    2018.02.02 06:19:36.024 *D* [obj.sync          ] Object lost_node_6931 [6931] modified
    2018.02.02 06:19:36.024 *D* [obj.sync          ] Object lost_node_6931 [6931] modified
    2018.02.02 06:19:36.509 *D* Subnet[193.193.0.0/20]::findMacAddress: reading ARP cache for node lost_node_6931 [6931]
    2018.02.02 06:19:36.509 *D* Subnet[193.193.0.0/20]::findMacAddress: reading ARP cache for node lost_node_6931 [6931]
    2018.02.02 06:20:01.421 *D* Node 6931 "lost_node_6931" queued for status poll
    2018.02.02 06:20:01.421 *D* Node 6931 "lost_node_6931" queued for status poll
    2018.02.02 06:20:01.422 *D* Starting status poll for node lost_node_6931 (ID: 6931)
    2018.02.02 06:20:01.422 *D* Starting status poll for node lost_node_6931 (ID: 6931)
    2018.02.02 06:20:01.422 *D* StatusPoll(lost_node_6931): check SNMP
    2018.02.02 06:20:01.430 *D* StatusPoll(lost_node_6931): SNMP check finished

    Any thoughts on how to resolve this would be greatly appreciated!

    Thanks in advance!


    Problem.PNG

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

      Hi,

      likely old node was not deleted completely. Try to login with user "system", find that node, and delete it.

      Best regards,
      Victor

      1 Reply Last reply
      0
      • K
        K
        kummerr
        wrote on last edited by
        #3

        That fixed it, thanks 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