Why are Cisco ISR Routers discovered as Switches<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Firstly, this is the expected behaviour of Discovery for these devices. Cisco has several families of Integrated Services Routers (ISR), but these don't only do routing functions. They are not just Routers in the traditional sense. e.g. "The ISR 1000 Series combines routing, switching, Wi-Fi, integrated security, and DSL and LTE uplink connectivity options in a single, lightweight, high-performance device." When automatically classifying a device, using data returned by the SNMP Classify probe, the Discovery sensor script will work out if the device can switch, can print, can route etc. Using those flags, the Classifications, in order, decide which Class the device is, and based on the class defines which Pattern will run. Switch comes first in the order, followed by Router. Only the Switch pattern gathers Switching information, so using that system of classifications, devices that can switch will be deliberately classified as Switches even if the device also has Routing functions. You could in theory add an OID record (1.3.6.1.4.1.9.1.2666 / 1.3.6.1.4.1.9.1.2668), to override the classification scripts, and force Discovery to use a certain Classifier, Table Class, and Pattern, to get the CI created in your favoured table, but then you won't get all the Switch information recorded in the CMDB. And that would break features that depend on Switch data, L2/L3 Discovery, including Service Mapping, that need this data in order to tie devices and software together that connect via the switch.