We have many switch stacks in our environment. Most of them are built with Catalyst 9300 switches. The product OID that comes back for these is 22.214.171.124.126.96.36.199.2494 which the Cisco OID tool reports back as cisco9300FixedSwitchStack. Lansweeper reports this OID as Catalyst 9300-24P instead of a stack. Lansweeper does correctly read all of the ports in the stack and shows links to the assets that are found on those ports. The problem with the reporting is that Lifecycle reports these stacks as nearing end of life. The system also is unable to scan IOS version at this level (OID 188.8.131.52.184.108.40.206.220.127.116.11.1001). This may also mean that Security Insights cannot properly analyze these assets.
We also have a stack of 9400 switches that does not return an iOS version either. That OID is 18.104.22.168.22.214.171.124.2500 and it reports as a Catalyst 9407R.
I searched the community for previous threads on switch stacks and found very little. The only relevant one I found was from several years ago saying that deeper scanning could not be done. https://community.lansweeper.com/t5/forum/stacked-switches/m-p/50264
My network admin did find that there is another MIB that could possibly give a solution on this. The thread he gave me as reference deals with PRTG but the methodology could probably be adapted. The MIB referenced is CISCO-STACKWISE-MIB. The thread is https://kb.paessler.com/en/topic/41133-how-can-i-get-prtg-to-recognize-cisco-switches-in-stack-that-...
If you are able to update the scanning engine to use this, I am not sure how I would expect the result to be treated. Logically it is 1 asset but there could be multiple serial numbers found so should that trigger Lansweeper to create multiple assets with same IP address and asset name?
Please give me some indication if this will be added to a roadmap, or if it is feasible to work into the system.
Scanning stacked switches is still very limited, as explained in that forum post you found. It's on our customer wish list to improve on this, but we can't guarantee that this feature will be implemented or provide you with an estimated release date at this time.
However, we have some KB articles that you might find useful: