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. Multiple Node Status

Multiple Node Status

Scheduled Pinned Locked Moved Support
5 Posts 2 Posters 18.4k 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
    tamal_g
    wrote on last edited by
    #1

    Hi Victor,

    I have created a node (Ex: NODE-A) of my device having IP address (192.168.200.130). My device is connected with another device by means of optical fibre. That device does not have any physical IP interface. But still I have created another node (Ex: NODE-B) with the same IP address of NODE-A. Both the devices are having their own set of SNMP traps which NODE-A sends to the server. SNMP traps of both the node's are always being sent by NODE-A.

    My aim is to configure NetXMS server in such a fashion that when NODE-B specific trap comes I should be able to change the status of NODE-B only (although the trap source is NODE-A).

    I have configured the specific traps and events accordingly. I have also configured the Event policies for all the traps but unfortunately I could only be able to change the status of NODE-A not NODE-B. I am not able to distinguish the traps specific for NODE-A and NODE-B.

    Please help.

    Regards,
    tamal_g

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

      Hi!

      Currently there are no simple solution. What you possibly can do is to catch events from node A which are in fact related to node B, use NXSL script as action for them, and use PostEvent function (http://wiki.netxms.org/wiki/NXSL:PostEvent) to re-send same (or different) event on behalf of node B.

      Best regards,
      Victor

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

        Thanks Victor.

        I Have tried to implement as suggested by you. But the problem is all the event's source node is NODE-A and whenever I have passed the $node object, the $node->name is always having the name of NODE-A. I am not able to change the status of NODE-B with their specific traps.

        Can you please give me some more details on how to implement PostEvent() function on this particular configuration?

        Regards,
        tamal_g

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

          Hi!

          Global variable $node always points to source node of event being processed, node A in your case. You have to find node object for node B using FindNodeObject (http://wiki.netxms.org/wiki/NXSL:FindNodeObject) function, like this:

          nodeB = FindNodeObject($node, "NodeB");
          PostEvent(nodeB, "MY_EVENT", null, ...); // add parameters as required

          Best regards,
          Victor

          1 Reply Last reply
          0
          • T
            T
            tamal_g
            wrote on last edited by
            #5

            Once again thanks for your help.

            Exactly the same logic what I implemented and it worked.

            Thanks once again

            Chz!!!

            Regards,
            tamal_g

            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