CISCO-ENTITY-VENDORTYPE-OID-MIB (page 1 of 3)

Description: Defines Cisco-specific vendor type OIDs used to identify physical entities in the ENTITY-MIB entPhysicalVendorType field.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

CISCO-ENTITY-VENDORTYPE-OID-MIB is a definitional module that assigns object identifiers to the various hardware components found across Cisco products, for use as values in the entPhysicalVendorType field of the standard IETF ENTITY-MIB's entPhysicalTable. It does not define managed objects with runtime values of its own; rather it is a registry/enumeration of OIDs identifying card types, modules, and other physical components (such as cevOtherUnknownCard or cevOtherMoH). Consequently it has no direct role in monitoring hardware or software status, uptime, or performance — it exists solely so that when ENTITY-MIB or ENTITY-PERFORMANCE-MIB report a component, its vendor-specific type can be looked up and translated into a human-meaningful category. It is entirely dependent on, and exists only to support, the IETF ENTITY-MIB's entPhysicalVendorType object. It is referenced across the whole range of Cisco hardware platforms wherever physical inventory reporting is used. Engineers can download the CISCO-ENTITY-VENDORTYPE-OID-MIB file directly to load it into their MIB browser.

This module defines no runtime data objects itself, only OID assignments such as cevOtherUnknownCard or cevNmeApaLink used as values elsewhere; there is no polling scenario against this MIB directly. An NMS would instead read entPhysicalVendorType from ENTITY-MIB and use this MIB's OID tree to translate that value into a recognizable Cisco component type (e.g., identifying a returned OID as a specific network module).