Device Type Name for Cisco Chassis devices
Article ID: 207306
Updated On:
Products
Issue/Introduction
The 'Device Type' Name for Cisco Chassis devices is not descriptive enough and is too generic. It is often necessary to pull the chassis module type from
the ENTITY-MIB via entPhysicalModelName
A couple of examples
Cisco IOS Software [Gibraltar], Catalyst L3 Switch Software (CAT3K_CAA-UNIVERSALK9-M), Version 16.12.4, RELEASE SOFTWARE (fc5)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2020 by Cisco Systems, Inc.
Compiled Thu 09-Jul-20 18:
System Object ID 1.3.6.1.4.1.9.1.1745
The Device Type shows as a Cat38xxStack
While the entPhysicalModelName attribute in the ENTITY-MIB shows WS-C3850-48F-S
Cisco IOS Software [Gibraltar], Catalyst L3 Switch Software (CAT9K_IOSXE), Version 16.12.4, RELEASE SOFTWARE (fc5)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2020 by Cisco Systems, Inc.
Compiled Thu 09-Jul-20 21:49 by mcpre
System Object ID 1.3.6.1.4.1.9.1.2494
The Device Type shows as a 'Cisco Catalyst 9300 Switch'
While the entPhysicalModelName attribute in the ENTITY-MIB shows
Environment
Release : Any
Resolution
At this time the 'Device Type' name is statically mapped within the Device Certification GUI and would require an enhancement for Spectrum to pull the Device Type Name from the ENTITY-MIB (entPhysicalModelName) for Chassis Devices
Feedback
