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. L2 Topology not updating

L2 Topology not updating

Scheduled Pinned Locked Moved Support
2 Posts 2 Posters 20.0k 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.
  • G
    G
    gmonk63
    wrote on last edited by
    #1

    current version is 4.1.377  We have a layer2 redundant loop in our network and needed to break the loop by shutting down one of the switch interfaces temporarily. However netxms never updates the topology to reflect the broken loop even after two days its still shows the link connected between the two switches when interface details on both switches shows the interface as down.  I would expect the link to be removed after a topology poll was completed showing the loop broken in the middle where the interfaces are down. Is this normal or do I have to do something to force an update.

    Thanks

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

      When interface is down, we have two contradicting requirements: one is to show what was connected to that interface before it went down, and other is to show actual connectivity. First requires to keep showing link between disconnected interfaces, second requires to delete that link immediately after interface goes down. As NetXMS server has no way of knowing if disconnect is permanent or temporary, and there are seems to be more requests to provide access to last known connection information, NetXMS server keeps that connection until it will know that topology was changed (for example, one of previously connected interfaces will go up and LLDP will report different peer).
      One possible solution could be configurable topology expiration time - i.e. if interface is down for N days, remove any known topology information from it.
      Currently as a workaround you can delete interface that is disconnected - configuration poll will find it and re-create, but peer information will be erased.

      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