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. Configuration of NetXMS

Configuration of NetXMS

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

    Hello Everyone,

              This is my really first in depth try at using NetXMS, I have a db server in stalled on Windows Server 2008 R2 and I have the NetXMS Server installed on another node/host with Windows Server 2008 R2 and after a few hiccups with the install I finally got to configure it but now I am seeing some odd stuff in my Alarms, NetXMS is a VM and The Database is a Physical Server. Please see the attachment for the anomoly I am seeing.
    These appear to be some type of tunnel but I can't figure out what purpose they are for.

    [Minor] CFMON (NetXMS) Interface "Local Area Connection* 8" changed state to DOWN (IP Addr: UNSPEC/0, IfIndex: 11)
    [Minor] CFMON (NetXMS) Interface "Local Area Connection* 8" changed state to DOWN (IP Addr: UNSPEC/0, IfIndex: 11)

    [Minor] cfdatabase (Database) Interface "Local Area Connection* 8" changed state to DOWN (IP Addr: UNSPEC/0, IfIndex: 11)

    I am not sure what this is telling me. There is only 1 NIC in each system, So I can't figure out why this is going on.

    Thanks in advance for your help,
    Michael

    1 Reply Last reply
    0
    • T
      T
      Tursiops
      wrote on last edited by
      #2

      Hi Michael,

      Quite a few Windows servers I am monitoring show such "Local Area Connection* <N>" interfaces, which are not active interfaces on the system itself.
      I didn't dig too deep into it, but made a guess that these are probably inactive networks that Windows has saved somewhere (e.g. a different network connected during server setup or similar). The only thing in common was the "*" in the name, so I filtered those out using a script in Hook::CreateInterface in the Script Library.
      In our case, I did the same for isatap and Teredo (and a few other) interfaces, as we don't need to see those either.

      See below for an example using the three interfaces mentioned above:

      if ( $1->name ~= "^isatap" ) return false;
      if ( $1->name ~= "^Teredo" ) return false;
      if ( $1->name ~= "\*" ) return false;
      return true;
      

      Cheers

      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