CISCO-SYSTEM-EXT-MIB

All MIBs › CISCO-SYSTEM-EXT-MIB

Organization: Cisco Systems Inc.

Last Updated: 2016-06-14

Category: Cisco Devices, Device Management

Description: Extends system management with Cisco-specific hostname, NTP synchronization, reboot reason, and resource threshold objects.

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.

What Is CISCO-SYSTEM-EXT-MIB?

CISCO-SYSTEM-EXT-MIB is a Cisco vendor-specific MIB that extends standard system management with High Availability status, SNMP SET error diagnostics, software-core-file tracking, and system-level operational state for Cisco networking equipment. It exposes CPU and memory utilization gauges (cseSysCPUUtilization, cseSysMemoryUtilization), configuration change tracking (cseSysConfLastChange, cseSysAutoSync/cseSysAutoSyncState for active/standby supervisor image sync), a detailed SNMP-error table (cseSnmpErrorTable) that supplies platform-specific error codes/descriptions beyond standard SNMP error-status values, High Availability restart/shutdown reason objects (cseHaRestartReason, cseHaRestartService, cseHaShutDownReason) with an associated cseHaRestartNotify/cseShutDownNotify trap pair, and a software-core-file table (cseSwCoresTable) recording which process crashed, when, and where the core file was written. It also covers console/Telnet/FIPS activation status, system uptime (cseSysUpTime), switching-mode (Nexus 3000/9000) admin vs. operational state, and a maintenance-mode state machine (cseMaintModeState) with change notifications. Monitoring this MIB is central to Cisco platform health and HA diagnostics: rising CPU/memory utilization, unexpected supervisor restarts, generated core files, or a system stuck in maintenance mode are all leading indicators of instability, and it is deployed on Cisco switches and routers with supervisor redundancy, particularly Nexus/Catalyst platforms. Administrators can perform a CISCO-SYSTEM-EXT-MIB download to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-SYSTEM-EXT-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Cisco switches/routers with supervisor redundancy (Nexus/Catalyst platforms)

Monitoring Examples

An operator polls cseSysCPUUtilization and cseSysMemoryUtilization alongside cseSwCoresTable; a spike in CPU/memory utilization followed by a new entry appearing in cseSwCoresTable (and a corresponding cseFailSwCoreNotify trap) would indicate a process crash likely caused by resource exhaustion.

What Can Be Monitored

CPU and memory utilization gauges
SNMP SET error code/description table
high-availability restart and shutdown reason objects
software core-file generation table
switching-mode and maintenance-mode operational state
configuration last-change and auto-sync status

Imported Objects

From CISCO-SMI

ciscoMgmt

OBJECT-IDENTITY

From CISCO-TC

EntPhysicalIndexOrZero
TimeIntervalSec

From INET-ADDRESS-MIB

InetAddress
InetAddressType

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-MIB

sysName

OBJECT-TYPE

From SNMPv2-SMI

Gauge32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

DateAndTime
TEXTUAL-CONVENTION
TruthValue

How to Use in IPNetwork Monitor

Example using cseSysCPUUtilization OID:

Select a Cisco switch/router with supervisor redundancy (Nexus/Catalyst) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type cseSysCPUUtilization into the Find box to locate it in the OID tree, then select it and click OK. The average utilization of CPU on the active supervisor. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Gauge32-type OID, Value bounds is the most useful condition here — trigger an alert if utilization exceeds 85%, a common warning threshold before sustained high load affects performance. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
ciscoSystemExtMIB	1.3.6.1.4.1.9.9.305			MIB module for monitoring High Availability, SNMP SET errors and bandwidths. This mib module also provides the information on core files that are generated in the system. GLOSSARY FIPS Federal Information Processing Standards Publication.
ciscoSystemExtMIBNotifsPrefix	1.3.6.1.4.1.9.9.305.0
ciscoSystemExtMIBObjects	1.3.6.1.4.1.9.9.305.1
ciscoSysInfoGroup	1.3.6.1.4.1.9.9.305.1.1
G32 cseSysCPUUtilizationEx	1.3.6.1.4.1.9.9.305.1.1.1	Gauge32	read-only	The average utilization of CPU on the active supervisor.
G32 cseSysMemoryUtilization	1.3.6.1.4.1.9.9.305.1.1.2	Gauge32	read-only	The average utilization of memory on the active supervisor.
DAT cseSysConfLastChange	1.3.6.1.4.1.9.9.305.1.1.3	DateAndTime	read-only	The local date and time when the configuration was last changed. This object will be set to zero on power cycle or on reboot of the system. Also, if the clock is changed on local system it is set to zero.
INT cseSysAutoSync	1.3.6.1.4.1.9.9.305.1.1.4	INTEGER	read-write	The state of the auto synchronization of images between the active and standby supervisor. Setting the value to sync when the existing value is sync, has no effect on the operation.
INT cseSysAutoSyncState	1.3.6.1.4.1.9.9.305.1.1.5	INTEGER	read-only	The status of the current auto synchronization process, or if no such process is in progress, then the state of the most recent one. The value 'notStarted' indicates no auto synchronization process has occurred recently.
INT cseWriteErase	1.3.6.1.4.1.9.9.305.1.1.6	INTEGER	read-write	This object is used to initiate a write erase on the device's saved configuration file(s) from which the device loads its configuration when it restarts. If the value of this object is set to 'eraseAll', then all the saved configurations are removed. No action is taken when the this object is set to 'noOp'. When read, the value of this object is always 'noOp'.
INT cseSysConsolePortStatus	1.3.6.1.4.1.9.9.305.1.1.7	INTEGER	read-only	This object describes the status of the console port on this device. The status 'connected' means that there is a cable attached to the console port. The status 'notConnected' means that there is no connection out of the console port.
T/F cseSysTelnetServiceActivation	1.3.6.1.4.1.9.9.305.1.1.8	TruthValue	read-write	Enables or disables the Telnet service on the device. In other words, it enables or disables the telneting to the device.
T/F cseSysFIPSModeActivation	1.3.6.1.4.1.9.9.305.1.1.9	TruthValue	read-write	The object to enable/disable FIPS mode on the device. FIPS 140-2 is a set of security requirements for cryptographic modules and it details the U.S. Government requirements for cryptographic modules. A module will comprise both hardware and software, eg a datacenter switching or routing module. The module is said to be in FIPS enabled mode when a request is recieved to enable the FIPS mode and a set of self-tests are successfully run in response to the request. If the self-tests fail, then an appropriate error is returned.
NUM cseSysUpTime	1.3.6.1.4.1.9.9.305.1.1.10	TimeIntervalSec	read-only	The time (in seconds) since the entire system was last re-initialized as a result of reload. The initialization being system loaded and running with a system image software on the first active supervisor (SUP). In High Availibility (HA) capable system / System that provides Supervisor module redundancy, this uptime indicates time elapsed since the first active SUP was booted. This will not change even if the active SUP goes down and stand-by takes over as active.
ciscoSysErrorGroup	1.3.6.1.4.1.9.9.305.1.2
cseSnmpErrorTable	1.3.6.1.4.1.9.9.305.1.2.1		not-accessible	A table containing information about the errors which have recently caused the generation of a SNMP Response PDU with a non-zero value in its error-status field for SNMP Set Response PDU. This table serves as an extension to the SNMP's error status when a SNMP Set request fails. SNMP returns only a pre-defined set of standard error codes which does not convey the specific cause for an error. Typically, there is an incumbent and sizable burden on the configuration application to determine if the configuration request failure is the result of a resource issue, a security issue, or an application error (like an object depending on some other objects). So from a user perspective, it is important that a specific error be made known. Ideally, when a 'badValue' error occurs for a given set request, an application can query the command responder for more details on the error. This table provides a framework for the command responders to provide more information on the SET errors. It is up to the implementation to create entries in this table for either only certain SNMP errors or all of the SNMP errors. Note that only most recent incarnation of an entry is kept in this table.
cseSnmpErrorEntry	1.3.6.1.4.1.9.9.305.1.2.1.1		not-accessible	An entry (conceptual row) in the cseSnmpErrorTable, containing information about an error which has recently caused a SNMP SetRequest to fail. An entry is created by the agent on the occurrence of an error, and is deleted approximately 5 minutes later. The reasons for this are : - to prevent old entries clogging the table. - optimal utilization of the resources like memory.
IPt cseSnmpErrorAddressType	1.3.6.1.4.1.9.9.305.1.2.1.1.1	InetAddressType	not-accessible	The type of address from which the error-ed SetRequest originated.
IP cseSnmpErrorAddress	1.3.6.1.4.1.9.9.305.1.2.1.1.2	InetAddress	not-accessible	The address from which the error-ed SetRequest originated.
U32 cseSnmpErrorRequestId	1.3.6.1.4.1.9.9.305.1.2.1.1.3	Unsigned32	not-accessible	The request-id of the error-ed SetRequest.
U32 cseSnmpErrorCode	1.3.6.1.4.1.9.9.305.1.2.1.1.4	Unsigned32	read-only	The code for the Mib object specific error which caused a SetRequest to fail. This error code is platform-specific and for debugging purposes only. For information on this code, the corresponding instance of cseSnmpErrorDescription must be used. This code is not the same as the value contained in the error-status field of SNMP Response PDU.
STR cseSnmpErrorDescription	1.3.6.1.4.1.9.9.305.1.2.1.1.5	SnmpAdminString	read-only	The error description for the error happened for the SetRequest.
ciscoHaGroup	1.3.6.1.4.1.9.9.305.1.3
CSE cseHaRestartReason	1.3.6.1.4.1.9.9.305.1.3.2	CseHaRestartReason	accessible-for-notify	The reason for most recent restart of a service on the 'active' supervisor.
T/F cseHaRestartStateless	1.3.6.1.4.1.9.9.305.1.3.3	TruthValue	accessible-for-notify	Tells if the most recent restart of a service on the 'active' supervisor was 'stateless' or not. A 'stateless' restart of a service is where no runtime information is preserved while restarting the service.
STR cseHaRestartService	1.3.6.1.4.1.9.9.305.1.3.4	SnmpAdminString	accessible-for-notify	Name of the service (or process) that was restarted on the 'active' supervisor.
cseHaNotification	1.3.6.1.4.1.9.9.305.1.3.5
cseHaNotificationPrefix	1.3.6.1.4.1.9.9.305.1.3.5.0
NTF cseHaRestartNotify	1.3.6.1.4.1.9.9.305.1.3.5.0.1			A service restart notification is generated whenever a service (or a process) on the 'active' supervisor is restarted.
NTF cseShutDownNotify	1.3.6.1.4.1.9.9.305.1.3.5.0.2			A system shutdown notification is generated whenever a system is going to shut down. The cseHaShutDownReason, describes the reason as to why the system is going to go down.
STR cseHaShutDownReason	1.3.6.1.4.1.9.9.305.1.3.6	SnmpAdminString	accessible-for-notify	The description of the reason as to why the system is going to go down.
ciscoSwFailureGroup	1.3.6.1.4.1.9.9.305.1.4
STR cseSwCorePath	1.3.6.1.4.1.9.9.305.1.4.1	SnmpAdminString	read-only	Provides the path where the software cores are stored on the system. The management application can use this path to copy the cores from the system using CISCO-FLASH-MIB.
cseSwCoresTable	1.3.6.1.4.1.9.9.305.1.4.2		not-accessible	A table containing information about the system cores that have been generated as an effect of some system failures.
cseSwCoresEntry	1.3.6.1.4.1.9.9.305.1.4.2.1		not-accessible	An entry (conceptual row) in the cseSwCoresTable, containing information about cores that have been generated.
ENT cseSwCoresModule	1.3.6.1.4.1.9.9.305.1.4.2.1.1	EntPhysicalIndexOrZero	not-accessible	The physical module on which the process crashed.
STR cseSwCoresProcName	1.3.6.1.4.1.9.9.305.1.4.2.1.2	SnmpAdminString	not-accessible	The name of the process that crashed and generated core.
U32 cseSwCoresInstance	1.3.6.1.4.1.9.9.305.1.4.2.1.3	Unsigned32	not-accessible	The instance of the core for a process identified by cseSwCoresProcName and on the module identified by cseSwCoresModule. To uniquely identify a core, the module number and process name are not sufficient as there could be multiple cores for the same module number and process name.
U32 cseSwCoresPID	1.3.6.1.4.1.9.9.305.1.4.2.1.4	Unsigned32	read-only	The process identifier of the process that dumped the core.
DAT cseSwCoresTimeCreated	1.3.6.1.4.1.9.9.305.1.4.2.1.5	DateAndTime	read-only	The time at which the core was created.
U32 cseSwCoresSlotNum	1.3.6.1.4.1.9.9.305.1.4.2.1.6	Unsigned32	read-only	The slot number corresponding to the cseSwCoresModule in this chassis.
STR cseSwCoresFileName	1.3.6.1.4.1.9.9.305.1.4.2.1.7	SnmpAdminString	read-only	This object contains the core file-name(including the path, relative to the value in the cseSwCorePath object). If the cseSwCorePath contains zero length octet string, then this object will contain the filename with absolute path. If this object contains zero length octet string, then the core file is available in path identified in cseSwCorePath.
cseFailNotification	1.3.6.1.4.1.9.9.305.1.4.3
cseFailNotificationPrefix	1.3.6.1.4.1.9.9.305.1.4.3.0
NTF cseFailSwCoreNotify	1.3.6.1.4.1.9.9.305.1.4.3.0.1			A notification is generated whenever a software crash occurs and a core file is generated.
NTF cseFailSwCoreNotifyExtended	1.3.6.1.4.1.9.9.305.1.4.3.0.2			A notification is generated whenever a software crash occurs and a core file is generated.
ciscoSwFailureNotifControl	1.3.6.1.4.1.9.9.305.1.5
T/F ciscoSwFailureNotifEnable	1.3.6.1.4.1.9.9.305.1.5.1	TruthValue	read-write	This object is used for administratively enabling/disabling the cseFailSwCoreNotify or cseFailSwCoreNotifyExtended notifications.
ciscoSystemSwitchingModeGroup	1.3.6.1.4.1.9.9.305.1.6
INT ciscoSystemSwitchingModeAdmin	1.3.6.1.4.1.9.9.305.1.6.1	INTEGER	read-write	Object to specify system's switching mode. 'other' - any other state not covered by below enumerations 'notApplicable' - switching mode configuration is not applicable for this system 'nexus3000' - system switching mode is configured as Nexus 3000 'nexus9000' - system switching mode is configured as Nexus 9000.
INT ciscoSystemSwitchingModeOper	1.3.6.1.4.1.9.9.305.1.6.2	INTEGER	read-only	Object indicate system's operational switching mode. 'other' - any other state not covered by below enumerations 'notApplicable' - switching mode configuration is not applicable for this system 'nexus3000' - system is opeerating in Nexus 3000 mode 'nexus9000' - system is opeerating in Nexus 9000 mode.
ciscoSystemMaintModeGroup	1.3.6.1.4.1.9.9.305.1.7
NUM cseMaintModeState	1.3.6.1.4.1.9.9.305.1.7.1	CiscoMaintModeState	read-only	The maintenance mode operational state for the system.
cseMaintModeNotification	1.3.6.1.4.1.9.9.305.1.7.2
cseMaintModeNotificationPrefix	1.3.6.1.4.1.9.9.305.1.7.2.0
NTF cseNormalModeChangeNotify	1.3.6.1.4.1.9.9.305.1.7.2.0.1			A normal mode state change is generated when the system is changed from maintenance mode to normal mode.
NTF cseMaintModeChangeNotify	1.3.6.1.4.1.9.9.305.1.7.2.0.2			A maintenance mode state change is generated when the system is changed from normal mode to maintenance mode.
ciscoSystemMaintModeNotifControl	1.3.6.1.4.1.9.9.305.1.8
T/F ciscoSystemNormalModeNotifEnable	1.3.6.1.4.1.9.9.305.1.8.1	TruthValue	read-write	This object is used for administratively enabling/disabling the cseNormalModeChangeNotify.
T/F ciscoSystemMaintModeNotifEnable	1.3.6.1.4.1.9.9.305.1.8.2	TruthValue	read-write	This object is used for administratively enabling/disabling the cseMaintModeChangeNotify.
ciscoSystemReloadGroup	1.3.6.1.4.1.9.9.305.1.9
T/F cseSystemReloadPending	1.3.6.1.4.1.9.9.305.1.9.1	TruthValue	read-only	This object is used to indicate if a system reload is needed to make feature configuration change effective. The object returns 'true' if a system reload is required; it returns 'false' if no system reload is required.
ciscoSystemExtMIBConformance	1.3.6.1.4.1.9.9.305.2
ciscoSystemExtMIBCompliances	1.3.6.1.4.1.9.9.305.2.1
ciscoSystemExtMIBCompliance	1.3.6.1.4.1.9.9.305.2.1.1			The compliance statement for entities which implement the CISCO-SYTEM-EXT-MIB.
ciscoSystemExtMIBComplianceRev1	1.3.6.1.4.1.9.9.305.2.1.2			The compliance statement for entities which implement the CISCO-SYTEM-EXT-MIB.
ciscoSystemExtMIBComplianceRev2	1.3.6.1.4.1.9.9.305.2.1.3			The compliance statement for entities which implement the CISCO-SYTEM-EXT-MIB.
ciscoSystemExtMIBComplianceRev3	1.3.6.1.4.1.9.9.305.2.1.4			The compliance statement for entities which implement the CISCO-SYTEM-EXT-MIB.
ciscoSystemExtMIBComplianceRev4	1.3.6.1.4.1.9.9.305.2.1.5			The compliance statement for entities which implement the CISCO-SYTEM-EXT-MIB.
ciscoSystemExtMIBComplianceRev5	1.3.6.1.4.1.9.9.305.2.1.6			The compliance statement for entities which implement the CISCO-SYTEM-EXT-MIB.
ciscoSystemExtMIBComplianceRev6	1.3.6.1.4.1.9.9.305.2.1.7			The compliance statement for entities which implement the CISCO-SYTEM-EXT-MIB.
ciscoSystemExtMIBComplianceRev7	1.3.6.1.4.1.9.9.305.2.1.8			The compliance statement for entities which implement the CISCO-SYTEM-EXT-MIB.
ciscoSystemExtMIBComplianceRev8	1.3.6.1.4.1.9.9.305.2.1.9			The compliance statement for entities which implement the CISCO-SYTEM-EXT-MIB.
ciscoSystemExtMIBComplianceRev9	1.3.6.1.4.1.9.9.305.2.1.11			The compliance statement for entities which implement the CISCO-SYTEM-EXT-MIB.
ciscoSystemExtMIBComplianceRev10	1.3.6.1.4.1.9.9.305.2.1.12			The compliance statement for entities which implement the CISCO-SYTEM-EXT-MIB.
ciscoSystemExtMIBGroups	1.3.6.1.4.1.9.9.305.2.2
ciscoSystemExtInfoGroup	1.3.6.1.4.1.9.9.305.2.2.1			A collection of objects for system information. ciscoSystemExtInfoGroup object is superseded by ciscoSystemExtInfoGroupRev1.
ciscoSystemExtErrorGroup	1.3.6.1.4.1.9.9.305.2.2.2			A collection of objects for logging SNMP set error.
ciscoSystemExtHaGroup	1.3.6.1.4.1.9.9.305.2.2.3			A collection of objects for High Availability.
ciscoSystemExtNotificationGroup	1.3.6.1.4.1.9.9.305.2.2.4			A collection of notifications for the High Availability.
ciscoSystemExtInfoGroupRev1	1.3.6.1.4.1.9.9.305.2.2.5			A collection of objects for system information. ciscoSystemExtInfoGroupRev1 object is superseded by ciscoSystemExtInfoGroupRev3.
ciscoSystemExtInfoGroupOptional	1.3.6.1.4.1.9.9.305.2.2.6			A collection of objects for system information which are optional.
ciscoSystemExtSwFailureGroup	1.3.6.1.4.1.9.9.305.2.2.7			A collection of objects for system software failure information which are optional.
ciscoSystemExtInfoGroupRev2	1.3.6.1.4.1.9.9.305.2.2.8			A collection of objects for system information.
ciscoSystemExtSwFailureGroup2	1.3.6.1.4.1.9.9.305.2.2.9			A collection of objects for system software failure information which are optional.
ciscoSystemExtNotificationGroupSup1	1.3.6.1.4.1.9.9.305.2.2.10			A collection of notifications for the system MIB.
ciscoSystemExtHaGroupRev1	1.3.6.1.4.1.9.9.305.2.2.11			A collection of objects for High Availability.
ciscoSystemExtInfoTelnetGroup	1.3.6.1.4.1.9.9.305.2.2.12			A collection of objects related to telnet support to the device.
ciscoSystemExtNotificationGroupSup2	1.3.6.1.4.1.9.9.305.2.2.13			A collection of notification related to core file creation.
ciscoSystemExtSwFailureGroup3	1.3.6.1.4.1.9.9.305.2.2.14			A collection of objects related to the core file.
ciscoSystemExtSwFailureControlGroup	1.3.6.1.4.1.9.9.305.2.2.15			This group of objects controls the sending of notifications defined in this MIB module.
ciscoSystemExtInfoFIPSGroup	1.3.6.1.4.1.9.9.305.2.2.16			A collection of objects related to FIPS support to the device.
ciscoSystemExtInfoGroupRev3	1.3.6.1.4.1.9.9.305.2.2.17			A collection of objects for system information.
ciscoSystemSwitchingModeObjectsGroup	1.3.6.1.4.1.9.9.305.2.2.18			A collection of objects to support Switching Mode feature.
ciscoSystemMaintModeObjectsGroup	1.3.6.1.4.1.9.9.305.2.2.19			A collection of objects to support Maint mode state feature.
ciscoSystemMaintModeNotificationGroup	1.3.6.1.4.1.9.9.305.2.2.20			A collection of notification related to core file creation.
ciscoSystemReloadObjectsGroup	1.3.6.1.4.1.9.9.305.2.2.21			A collection of objects to support system reload.

RFC description

Monitors High Availability, SNMP SET errors, bandwidth utilization, and core file generation on Cisco systems.

Start monitoring Cisco switches/routers with supervisor redundancy (Nexus/Catalyst) 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.

Download CISCO-SYSTEM-EXT-MIB