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. Stacked switches in rack view

Stacked switches in rack view

Scheduled Pinned Locked Moved Support
4 Posts 4 Posters 14.7k 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
    TSimmonsHJ
    wrote on last edited by
    #1

    Greetings all,
    I am evaluating NetXMS for use in our environment and I have a question about how to best represent stacked switches in the rack function. Since they only show up as one node, it's challenging for us. It's not uncommon for us to have switch stacks spread out across multiple racks as well - usually in the same room, but sometimes not. What is the best way to represent this? We use Juniper (EX), Aruba (2930f, 3810m), and Cisco (moving to Cat 9series) mostly - but we could inherit all sorts of things.

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

      Hi,

      one possible option is to create fake nodes without IP address to represent different units and use status DCIs to set unit status. I will also think about implementing some sort of built-in mechanism for representing units of distributed stack as that seems to be quite common task. If you wish you can follow on this ticket: https://track.radensolutions.com/issue/NX-1657

      Best regards,
      Victor

      1 Reply Last reply
      0
      • 2
        2
        2b2bff
        wrote on last edited by
        #3

        Hi,

        I'm facing the same issue. Is there any news on this, or is it still the best recommendation?

        Cheers,
        Frank

        1 Reply Last reply
        0
        • F
          F
          Filipp Sudanov
          wrote on last edited by
          #4

          Hi,

          We had a discussion with developers and formulated how this could be implemented somewhere in the future: https://track.radensolutions.com/issue/NX-2466

          For the time being, you can create dummy nodes (specifying ip address 0.0.0.0), create one script DCI on each of these nodes with "Use this DCI for node status calculation" and use script to determine status (script should be returning 0...4 for Normal...Critical)

          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