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. Passive Network Discovery on only specified device

Passive Network Discovery on only specified device

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

    Hi,

    I'd like to execute passive network discovery on only one device, it's possible?
    i have to add to Netxms throught Network Discover all the laptops present in all my network...The laptops run Window 7, so they have ICMP ping disabled and then they cannot be discovered throught active mode of network discovered...
    If i use "normal" passive network discovery, netxms try to catch info about user by catching the ARP cache and the IP routing table of all device known...The problem is  in my network there are several device(UPS) not managed by me, that use different snmp community each other...this device detect snmp wrong access and send email alarm to they owner...So if i use passive network discovery and i specify a default community, all the device that have a community different than the default will sent alarm, and panic happens 😢
    All mac address and IP info of the laptop are stored in the core switch of the network, can i limit the passive network discovery on only this device?
    If i set the UPS unmanaged, when i exec the network discovery,will netxms try to access howewer the device?

    Thank you,

    Giovanni

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

      Hi!

      I see few options here. The best one is to use address filters in network discovery, if your network scheme allows this. Device address validated before trying to access device using SNMP, so this should help. Another possible option is to manually add these devices to NetXMS (or let them being discovered) and then disable SNMP access (in node properties, check "Disable SNMP for all polls" on "Polling" page), or just set them to "unmanaged" state.

      Best regards,
      Victor

      1 Reply Last reply
      0
      • T
        T
        tivanni
        wrote on last edited by
        #3

        OK,

        i choose to Disable SNMP for all polls for the "problematic" nodes, that are already on Netxms.
        The problem is resolved, thank you so much!

        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