Why are devices being set to model class Switch-Router when we feel these should be set as model class Router
If the device responds to Bridge-MIB, Spectrum considers it has switching capability and will be set as model class Switch-Router.
So for example you may have a device that you are only using as a Router and you feel should be set as model class Router but the device may have switching capability its just that it is not enabled.
If a device has switching ability even if not enabled and responds to Bridge MIB then It will be set as model class Switch-Router.
We are reading below OID’s in code. If any of these attributes are filled we say it’s a switch:
dot1dTpLearnedEntryDiscards - 220.127.116.11.18.104.22.168.1
dot1dTpAgingTime - 22.214.171.124.126.96.36.199.2
dot1dBaseBridgeAddress - 188.8.131.52.184.108.40.206.1
Additionally you can cross check with the vendor if a device supports switching functionality.
For example the following link allows us to see from the device vendor Cisco that the model class set as Switch-Router is correct not only from seeing that the above OIDs were populated but also the vendor web page confirms it:
IT consolidation, space savings, and improved total cost of ownership (TCO) ● Single converged branch platform integrates routing, switching, virtual server, storage, security, unified communications, WAN optimization, and performance management tools.
If you would like to see the Model Class as Router for this device they can do the following workaround:
- Change the Model Class of the Device to Router
- Change the Lock Model Class (0x12b4a) attribute value to "Yes"