All MIBs › EXTREME-SYSTEM-MIB
Organization: Extreme Networks, Inc.
Last Updated: 2000-07-24
Category: Device Management, Vendor: Extreme Networks
Description:
Contains common system-level objects for Extreme Networks switches, including system identification, configuration save/restore status, and basic platform information.
Imported Objects
From EXTREME-BASE-MIB
| PortList | |
| extremeAgent | OBJECT-IDENTITY |
From RFC1213-MIB
| DisplayString | |
| ifDescr | |
| sysDescr | |
| sysUpTime |
From SNMPv2-SMI
| Counter64 | |
| Integer32 | |
| IpAddress | |
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-TYPE | |
| Unsigned32 |
From SNMPv2-TC
| MacAddress | |
| RowStatus | |
| TEXTUAL-CONVENTION | |
| TruthValue |
What Is EXTREME-SYSTEM-MIB?
EXTREME-SYSTEM-MIB is an Extreme Networks proprietary MIB providing common system-level management objects shared across Extreme's switch product lines. It exposes platform-wide data such as system identification, image/firmware feature information, configuration save/restore status, and system-level trap definitions. It is directly useful for monitoring device software status: the extremeImageFeatureTable lets an operator confirm which firmware image and feature set is active, while system notification/trap objects report events like configuration changes or save failures that indicate operational health issues. This kind of EXTREME-SYSTEM-MIB SNMP monitoring is typically combined with the vendor's VLAN, chassis, and port-specific MIBs to build a complete operational picture of a given switch. It is a base/common MIB that other Extreme Networks product-specific MIBs (VLAN, chassis, port) build on top of. It is deployed across Extreme Networks Ethernet switch and routing platforms in enterprise and data-center networks.
IPNetwork Monitor allows you to monitor SNMP objects defined in EXTREME-SYSTEM-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.
What Can Be Monitored
- active firmware image/feature set
- configuration save/restore status
- system-level trap/notification events
Supported Devices
- Extreme Networks 5420 Series (current) — stackable edge switches, 24/48-port, up to 90W PoE
- Extreme Networks 4000 Series (current) — Layer 2 campus/branch switches
Monitoring Examples
An administrator polls extremeImageFeatureTable to verify which software image and feature license is currently running on the switch, useful for confirming a firmware upgrade took effect. Traps generated under extremeSystemTrapsPrefix (rooted through extremeSystemNotifications) alert on events such as configuration-save failures or system state changes, which an NMS would correlate with unexpected reboots or config drift. Because this is a common/base MIB, its objects are typically polled alongside chassis- and port-specific Extreme MIBs for a full system health picture.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| extremeSystem | 1.3.6.1.4.1.1916.1.1 | Extreme System objects: objects common to all platforms | ||
| extremeSystemCommon | 1.3.6.1.4.1.1916.1.1.1 | |||
| INT extremeSaveConfiguration | 1.3.6.1.4.1.1916.1.1.1.3 | INTEGER | read-write | When this object is set, the device will copy the contents of the configuration database to a buffer and save it to the persistant store specified by the value of the object. The save is performed asynchronously, and the snmp agent will continue to respond to both gets and sets while the save is taking place. A network management application may use the extremeSaveStatus object to determine when the asynchronous save operation has completed. |
| INT extremeSaveStatus | 1.3.6.1.4.1.1916.1.1.1.4 | INTEGER | read-only | This object will return the status of a save operation invoked by setting the extremeSaveConfiguration object. A network management application can read this object to determine that a save operation has completed. |
| INT extremeCurrentConfigInUse | 1.3.6.1.4.1.1916.1.1.1.5 | INTEGER | read-only | Shows which NVRAM configuration store was used at last boot. |
| INT extremeConfigToUseOnReboot | 1.3.6.1.4.1.1916.1.1.1.6 | INTEGER | read-write | Controls which NVRAM configuration store will be used on next reboot. |
| T/F extremeOverTemperatureAlarm | 1.3.6.1.4.1.1916.1.1.1.7 | TruthValue | read-only | Alarm status of overtemperature sensor in device enclosure. |
| INT extremeCurrentTemperature | 1.3.6.1.4.1.1916.1.1.1.8 | INTEGER | read-only | Current temperature in degrees celcius measured inside device enclosure. |
| extremeFanStatusTable | 1.3.6.1.4.1.1916.1.1.1.9 | not-accessible | Table of operational status of all internal cooling fans. | |
| extremeFanStatusEntry | 1.3.6.1.4.1.1916.1.1.1.9.1 | not-accessible | Entry in table of all internal cooling fans. | |
| INT extremeFanNumber | 1.3.6.1.4.1.1916.1.1.1.9.1.1 | INTEGER | read-only | Identifier of cooling fan, numbered from the front and/or left side of device. |
| T/F extremeFanOperational | 1.3.6.1.4.1.1916.1.1.1.9.1.2 | TruthValue | read-only | Operational status of a cooling fan. |
| INT extremeFanEntPhysicalIndex | 1.3.6.1.4.1.1916.1.1.1.9.1.3 | INTEGER | read-only | The entity index for this fan entity in the entityPhysicalTable table of the entity MIB. |
| T/F extremePrimaryPowerOperational | 1.3.6.1.4.1.1916.1.1.1.10 | TruthValue | read-only | Operational status of internal power supply of a device. |
| INT extremeRedundantPowerStatus | 1.3.6.1.4.1.1916.1.1.1.11 | INTEGER | read-only | Operational status of an external redundant power supply to a device. |
| T/F extremeRedundantPowerAlarm | 1.3.6.1.4.1.1916.1.1.1.12 | TruthValue | read-only | Alarm state of an external redundant power supply to a device. Alarm state indicates either fan failure or overtemperature condition. |
| STR extremePrimarySoftwareRev | 1.3.6.1.4.1.1916.1.1.1.13 | DisplayString | read-only | The software revision of the primary image stored in this device. This string will have a zero length if the revision is unknown, invalid or not present. This will also be reported in RMON2 probeSoftwareRev if this is the software image currently running in the device. |
| STR extremeSecondarySoftwareRev | 1.3.6.1.4.1.1916.1.1.1.14 | DisplayString | read-only | The software revision of the secondary image stored in this device. This string will have a zero length if the revision is unknown, invalid or not present. This will also be reported in RMON2 probeSoftwareRev if this is the software image currently running in the device. |
| INT extremeImageToUseOnReboot | 1.3.6.1.4.1.1916.1.1.1.15 | INTEGER | read-write | Controls which image will be used on next reboot. |
| STR extremeSystemID | 1.3.6.1.4.1.1916.1.1.1.16 | DisplayString | read-only | This represents the System ID of the Summit Switch. |
| STR extremeSystemBoardID | 1.3.6.1.4.1.1916.1.1.1.17 | DisplayString | read-only | This represents the Board ID of the Summit Switch. |
| STR extremeSystemLeftBoardID | 1.3.6.1.4.1.1916.1.1.1.18 | DisplayString | read-only | This represents the Left Board ID of the Summit Switch. |
| STR extremeSystemRightBoardID | 1.3.6.1.4.1.1916.1.1.1.19 | DisplayString | read-only | This represents the Right Board ID of the Summit Switch. |
| INT extremeInputPowerVoltage | 1.3.6.1.4.1.1916.1.1.1.20 | INTEGER | read-only | The input power voltage at which the system is currently operating. |
| INT extremePowerStatus | 1.3.6.1.4.1.1916.1.1.1.21 | INTEGER | read-only | Operational status of the power supply to a device. |
| T/F extremePowerAlarm | 1.3.6.1.4.1.1916.1.1.1.22 | TruthValue | read-only | Alarm state of the power supply to a device. Alarm state indicates either fan failure or overtemperature condition. |
| T/F extremeRmonEnable | 1.3.6.1.4.1.1916.1.1.1.23 | TruthValue | read-write | Setting this to true will cause the agent to start collecting RMON statistics. |
| STR extremeBootROMVersion | 1.3.6.1.4.1.1916.1.1.1.25 | DisplayString | read-only | The software revision of the bootrom on the device. This string will have a zero length if the revision is unknown or invalid. |
| T/F extremeDot1dTpFdbTableEnable | 1.3.6.1.4.1.1916.1.1.1.26 | TruthValue | read-write | Setting this to true will cause GetNext operations on the dot1dTpFdbTable to be allowed. Note that Get operations are always allowed. |
| extremePowerSupplyTable | 1.3.6.1.4.1.1916.1.1.1.27 | not-accessible | Table of status of all power supplies in the system. | |
| extremePowerSupplyEntry | 1.3.6.1.4.1.1916.1.1.1.27.1 | not-accessible | An entry indicating the status of a specific power supply. | |
| INT extremePowerSupplyNumber | 1.3.6.1.4.1.1916.1.1.1.27.1.1 | INTEGER | accessible-for-notify | Power supply number. |
| INT extremePowerSupplyStatus | 1.3.6.1.4.1.1916.1.1.1.27.1.2 | INTEGER | read-only | Status of the power supply. |
| INT extremePowerSupplyInputVoltage | 1.3.6.1.4.1.1916.1.1.1.27.1.3 | INTEGER | read-only | Input voltage of the power supply |
| STR extremePowerSupplySerialNumber | 1.3.6.1.4.1.1916.1.1.1.27.1.4 | DisplayString | read-only | The serial number of the power supply unit. |
| INT extremePowerSupplyEntPhysicalIndex | 1.3.6.1.4.1.1916.1.1.1.27.1.5 | INTEGER | read-only | The entity index for this psu entity in the entityPhysicalTable of the entity MIB. |
| INT extremeCpuAggregateUtilization | 1.3.6.1.4.1.1916.1.1.1.28 | INTEGER | read-only | The aggregate CPU utilization since the time the start started executing. |
| extremeCpuTask2Table | 1.3.6.1.4.1.1916.1.1.1.29 | not-accessible | Table of CPU tasks that are active. | |
| extremeCpuTask2Entry | 1.3.6.1.4.1.1916.1.1.1.29.1 | not-accessible | An entry in table of describes a single task. | |
| U32 extremeCpuTask2CpuId | 1.3.6.1.4.1.1916.1.1.1.29.1.1 | Unsigned32 | not-accessible | CPU on which this task last executed or is executing. The primary CPU has a value of 1. |
| STR extremeCpuTask2Name | 1.3.6.1.4.1.1916.1.1.1.29.1.2 | DisplayString | not-accessible | Name associated with the reported task id. |
| U32 extremeCpuTask2Id | 1.3.6.1.4.1.1916.1.1.1.29.1.3 | Unsigned32 | read-only | Task identifier assigned by the operating system when this task is spawned. |
| U32 extremeCpuTask2Pc | 1.3.6.1.4.1.1916.1.1.1.29.1.4 | Unsigned32 | read-only | The value of the program counter for this task. It indicates the address of the next instruction that would be executed once the operating system resumes this task. |
| STR extremeCpuTask2Status | 1.3.6.1.4.1.1916.1.1.1.29.1.5 | DisplayString | read-only | The current status of the task as reported by the operating system. |
| U32 extremeCpuTask2Utilization | 1.3.6.1.4.1.1916.1.1.1.29.1.6 | Unsigned32 | read-only | The current CPU utilization by this task. This is the utilization when the task last executed. |
| U32 extremeCpuTask2MaxUtilization | 1.3.6.1.4.1.1916.1.1.1.29.1.7 | Unsigned32 | read-write | The maximum CPU utilization by this task since the time the start started executing. This value may be cleared. |
| IP extremeAuthFailSrcAddr | 1.3.6.1.4.1.1916.1.1.1.30 | IpAddress | accessible-for-notify | The IP address of the originator of the bad SNMP request that caused the generation of an authentication failure trap. |
| INT extremeCpuTransmitPriority | 1.3.6.1.4.1.1916.1.1.1.31 | INTEGER | read-write | The CPU transmit priority. |
| INT extremeImageBooted | 1.3.6.1.4.1.1916.1.1.1.32 | INTEGER | read-only | The image with which the switch was last booted, using which it is currently running. |
| INT extremeMsmFailoverCause | 1.3.6.1.4.1.1916.1.1.1.33 | INTEGER | read-only | The cause of the last MSM failover. never(1) means an MSM Failover has not occurred since the last reboot. admin(2) means the failover was initiated by the user. exception(3) means the former master MSM encountered a software exception condition. removal(4) means the master MSM was physically removed from the chassis. hwFailure(5) means a diagnostic failure was detected in the master MSM. watchdog(6) means that the master MSM hardware watchdog timer expired. keepalive(7) means the master MSM failed to respond to slave keepalive requests. The MSM failover will have been hitless only in the admin(2) and exception(3) cases |
| extremeImageTable | 1.3.6.1.4.1.1916.1.1.1.34 | not-accessible | A table containing information about each software image. | |
| extremeImageEntry | 1.3.6.1.4.1.1916.1.1.1.34.1 | not-accessible | A table entry containing information about each software image. | |
| INT extremeImageNumber | 1.3.6.1.4.1.1916.1.1.1.34.1.1 | INTEGER | read-only | A unique integer identifying the particular software image. |
| INT extremeMajorVersion | 1.3.6.1.4.1.1916.1.1.1.34.1.2 | INTEGER | read-only | The ExtremeWare Release Major Version. |
| INT extremeSubMajorVersion | 1.3.6.1.4.1.1916.1.1.1.34.1.3 | INTEGER | read-only | The ExtremeWare Release Sub-major Version. |
| INT extremeMinorVersion | 1.3.6.1.4.1.1916.1.1.1.34.1.4 | INTEGER | read-only | The ExtremeWare Release Minor Version. |
| INT extremeBuildNumber | 1.3.6.1.4.1.1916.1.1.1.34.1.5 | INTEGER | read-only | The ExtremeWare Build Number. |
| INT extremeTechnologyReleaseNumber | 1.3.6.1.4.1.1916.1.1.1.34.1.6 | INTEGER | read-only | The Technology Release version. This value is zero for all but TR releases. |
| INT extremeSustainingReleaseNumber | 1.3.6.1.4.1.1916.1.1.1.34.1.7 | INTEGER | read-only | The Sustaining Release number for the ExtremeWare version. |
| INT extremeBranchRevisionNumber | 1.3.6.1.4.1.1916.1.1.1.34.1.8 | INTEGER | read-only | The incremental build on specified branch. |
| INT extremeImageType | 1.3.6.1.4.1.1916.1.1.1.34.1.9 | INTEGER | read-only | The branch type from which the image was built. |
| STR extremeImageDescription | 1.3.6.1.4.1.1916.1.1.1.34.1.10 | DisplayString | read-only | A unique string that can be used to identify the specific patch, technology, or development branch release. |
| INT extremeImageSecurity | 1.3.6.1.4.1.1916.1.1.1.34.1.11 | INTEGER | read-only | Indicates whether image was built with ssh. This object is deprecated, the ssh capability can be obtained from the extremeImageSshCapability of the ImageFeatureTable |
| INT extremePatchVersion | 1.3.6.1.4.1.1916.1.1.1.34.1.12 | INTEGER | read-only | The ExtremeWare Release Patch Version. |
| extremeImageFeatureTable | 1.3.6.1.4.1.1916.1.1.1.35 | not-accessible | A table containing information about the software features. | |
| extremeImageFeatureEntry | 1.3.6.1.4.1.1916.1.1.1.35.1 | not-accessible | A table entry containing information about software features. | |
| INT extremeImageFeatureNumber | 1.3.6.1.4.1.1916.1.1.1.35.1.1 | INTEGER | read-only | A unique integer identifying the particular software image. |
| INT extremeImageSshCapability | 1.3.6.1.4.1.1916.1.1.1.35.1.2 | INTEGER | read-only | Indicates whether image has ssh capability. |
| INT extremeImageUAACapability | 1.3.6.1.4.1.1916.1.1.1.35.1.3 | INTEGER | read-only | Indicates whether image has Wireless(UAA) components. |
| extremeChassisGroup | 1.3.6.1.4.1.1916.1.1.2 | |||
| INT extremeMasterMSMSlot | 1.3.6.1.4.1.1916.1.1.2.1 | INTEGER | read-only | The extremeSlotNumber of the master MSM module. |
| extremeSlotTable | 1.3.6.1.4.1.1916.1.1.2.2 | not-accessible | A table containing information about each slot in the chassis. | |
| extremeSlotEntry | 1.3.6.1.4.1.1916.1.1.2.2.1 | not-accessible | A table entry containing information about the module in each slot of the chassis. | |
| INT extremeSlotNumber | 1.3.6.1.4.1.1916.1.1.2.2.1.1 | INTEGER | read-only | A unique integer identifying the particular slot in the chassis. |
| STR extremeSlotName | 1.3.6.1.4.1.1916.1.1.2.2.1.2 | DisplayString | read-only | A name identifying the particular slot in the chassis. |
| INT extremeSlotModuleConfiguredType | 1.3.6.1.4.1.1916.1.1.2.2.1.3 | INTEGER | read-write | The configured module type for the given slot. At startup, the module-type is none(1). It is possible to configure the module-type even if there is no module in the slot. If the current module in the slot is different than the requested configured module-type, then the current configuration for the module is erased and the card will be restarted. The new configured module-type will be recorded. Since the configured module type is different than the actual module type, a moduleMismatch trap will be sent, and the extremeSlotModuleState for that module will show a mismatch(3). Setting this variable to none(1) will clear the previously assigned module-type of this slot, and all configuration information related to the slot will be erased. |
| INT extremeSlotModuleInsertedType | 1.3.6.1.4.1.1916.1.1.2.2.1.4 | INTEGER | read-only | The module type inserted into the slot. It is possible to have a slot inserted into the slot even though extremeSlotConfiguredType is none(1). |
| INT extremeSlotModuleState | 1.3.6.1.4.1.1916.1.1.2.2.1.5 | INTEGER | read-only | The state of the module inserted in this slot. |
| STR extremeSlotModuleSerialNumber | 1.3.6.1.4.1.1916.1.1.2.2.1.6 | DisplayString | read-only | The serial number of the module inserted in this slot. |
| INT extremeChassisPortsPerSlot | 1.3.6.1.4.1.1916.1.1.2.3 | INTEGER | read-only | The maximum number of ports that can be accomodated in a single slot. This number would change to accomodate blades with higher port density than current ones. |
| extremeSystemHealthCheck | 1.3.6.1.4.1.1916.1.1.3 | |||
| INT extremeHealthCheckErrorType | 1.3.6.1.4.1.1916.1.1.3.1 | INTEGER | accessible-for-notify | The error reported in the system health check trap |
| INT extremeHealthCheckAction | 1.3.6.1.4.1.1916.1.1.3.2 | INTEGER | read-only | The action/alarm level configured for health check. |
| INT extremeHealthCheckMaxRetries | 1.3.6.1.4.1.1916.1.1.3.3 | INTEGER | read-only | The maximum number of times a module restart will be attempted if it fails. If extremeHealthCheckAction is not autorecovery(5), then this value is zero. |
| extremeSystemThresholds | 1.3.6.1.4.1.1916.1.1.4 | |||
| INT extremeCpuUtilRisingThreshold | 1.3.6.1.4.1.1916.1.1.4.1 | INTEGER | read-write | Rising threshold for CPU Aggregation utilization trap |
| STR extremeCpuTaskUtilPair | 1.3.6.1.4.1.1916.1.1.4.2 | DisplayString | accessible-for-notify | TaskName/CPU_% Util pair reported in CPU Utilization trap |
FAQ
How can EXTREME-SYSTEM-MIB confirm which firmware is running on an Extreme switch?
Its extremeImageFeatureTable lets an operator check which firmware image and feature set is currently active on the device.
What does this MIB report when a configuration save fails on an Extreme switch?
It includes system-level trap and notification objects that report events such as configuration changes or save failures, which operators can use to flag operational health issues alongside the vendor's VLAN, chassis, and port-specific MIBs.
RFC description
Extreme Networks proprietary MIB (OID 1.3.6.1.4.1.1916.1.1) containing system objects and device parameters common to all Extreme platform devices.
Start monitoring Extreme Networks switch/routing platform (common system objects, base MIB) 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.