Switch Stack Poller "Not a match" For Certain Stacked Cisco Nodes?

Question

Hi, 
 I ran a SWQL to report on 3850/9300/9500 nodes that are showing the switch stack member count as NULL: 
 
 select i.nodename as [Hostname], i.ip as [Device IP], i.MachineType as [Model], i.StatusDescription as [Current Status], i.SwitchStack.MemberCount

from orion.nodes i

where i.UnManaged='False' 
and (i.MachineType like '%9300%' or i.MachineType like '%38xx%' or i.MachineType like '%9500%')
and i.SwitchStack.MemberCount is NULL

order by i.NodeName 
 
 I then went over to settings -> all settings -> manage pollers -> Switch Stack -> Assign, and searched for the above results. All of them are showing as "Not a match". 
 It's possible some of these nodes were initially imported into SolarWinds as non-stackable nodes, and then replaced with one of the above Cisco models with the same polling IP. 
 Does anyone have any feedback as far as how to allow SolarWinds to recognize these nodes as being a match so that I can appropriately enable the poller? 
 Thanks!

k_barton · Accepted Answer

For anyone who comes across this, note that the switch stack poller can only apply to nodes that have the "StackPort" or "StackSub-St" ports in "List Resources" of the node. Even if you have a single switch, you need to specifically manage StackPort1, and then the Switch Stack poller will show as an exact match. Unfortunately, this doesn't seem to apply to 9500's as they do not have the StackPorts.

Switch Stack Poller "Not a match" For Certain Stacked Cisco Nodes?

Top Replies