Solarwinds service graph connector - stacked switches

Stacey Pevec
Tera Expert

‎08-07-2024 02:04 PM - edited ‎08-07-2024 02:08 PM

Hi community - I recently implemented the SolarWinds Service graph connector but am seeing an issue with Stacked switches. It seems that only one of the nodes in the stack is in the import set. It is usually the master or one slave but there is always only a single node from the stack. When I look in SolarWinds, it seems that there is one node listed and then a section from that node where it shows the switches in the stack with the model, serial, MAC address, CPU and RAM. My question is around how to get all members of the stack to be included in the import set? 
Thanks in advance!

0 Helpfuls
  • 1,246 Views
4 REPLIES 4

singhr17
Tera Contributor

‎03-26-2025 04:08 AM

Hi,

Did you get any solution for this? I am also facing the same issue.

 

Thanks

0 Helpfuls

Stacey Pevec
Tera Expert
In response to singhr17

‎03-26-2025 07:39 AM

I did not find a solution unfortunately. 

0 Helpfuls

ROBC-BTS
Tera Contributor

‎12-01-2025 02:37 AM

Hi there... a few months have past now, just wondering if you found any Solution yet to this, or how you may of worked around this issue?

0 Helpfuls

Alan Akins
Tera Expert

2 weeks ago

I have come upon this issue myself recently. I asked the google AI and it came up with the below. I need to look up "Hardware Graph." I don't know what the "related list" is for the stacked components. I do not see this in my instances.

 

How to address and track the serials
 
While you cannot split the stack in the SGC, you can manage the visibility of the internal serialized members using these approaches:
  1. Leverage the Hardware Graph: The SGC pulls stacked component data as a related list. Review the Hardware and Asset tables associated with the Master switch CI in your instance to locate the serialized component information.
  2. Review ServiceNow Support Guidance: Track official updates or documented workarounds for this specific behavior via the ServiceNow KB3008085 support article.
  3. Customize your Payload (Advanced): If your business requires strict CI separation for every stack member, you must build a custom transform script or modify the IRE payload processing within ServiceNow to split the SolarWinds API payload manually. Keep in mind that heavy customization may increase technical debt during upgrades.
 
 
 
 
 
0 Helpfuls