All MIBs › FLARION-TRAP-MIB
Category: Alarm and Event Management, Domain: Fault Management, Domain: Wireless
Description:
Flarion Technologies top-level trap MIB defining general SNMP notifications for Flash-OFDM network element fault conditions.
Imported Objects
From FLARION-MIB
| AddtlInfo | |
| AlarmSeverity | |
| MoType | |
| flarion | MODULE-IDENTITY |
| rrCommonMib | OBJECT-IDENTITY |
From SNMPv2-SMI
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-TYPE |
What Is FLARION-TRAP-MIB?
FLARION-TRAP-MIB is a vendor MIB from Flarion Technologies (a Flash-OFDM mobile broadband technology provider) defining the general SNMP notification/trap framework used across Flarion network element MIBs. It exposes common trap variable bindings rather than a data table, standardizing how fault and event notifications are structured. Its monitoring value is in fault/event detection: each trap carries a timestamp, sequence number, severity, managed-object type and ID, and additional diagnostic info, letting operators detect and correlate fault conditions across Flash-OFDM network elements as they occur, rather than polling ongoing status. Other Flarion-specific MIBs depend on this trap-variable framework to emit consistent, correlated notifications. It was deployed in Flash-OFDM (mobile WiMAX-competitor) wireless network infrastructure operated by carriers using Flarion equipment. FLARION-TRAP-MIB SNMP monitoring is therefore event-driven rather than poll-based, with operators configuring trap receivers to capture fault notifications as they occur.
IPNetwork Monitor allows you to monitor SNMP objects defined in FLARION-TRAP-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
- trap severity level
- managed object type and ID raising the event
- event timestamp and sequence number
- additional fault diagnostic information
Supported Devices
- Flarion Flash-OFDM mobile broadband network element (base station/radio equipment)
Monitoring Examples
A network management system would subscribe to traps under flarionTraps/flaTraps and parse flaTimeStamp, flaSeqNum, flaSeverity, flaMoType, and flaMoId to identify which managed object (e.g., a base station or radio module) raised a fault and its severity, using flaAddtlInfo for further diagnostic detail. The parallel rrTimeStamp/rrSeqNum/rrSeverity/rrMoType/rrMoId set of variables suggests a second notification category (possibly radio-resource related) carrying the same structured fault information.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| rrTrapVars | 1.3.6.1.4.1.8603.1.1.1 | |||
| INT rrTimeStamp | 1.3.6.1.4.1.8603.1.1.1.1 | INTEGER | read-only | The time at which the event was generated. This value is expressed in seconds since 00:00:00 UTC, January 1, 1970 (see time(2)). |
| INT rrSeqNum | 1.3.6.1.4.1.8603.1.1.1.2 | INTEGER | read-only | The event sequence number. |
| ALA rrSeverity | 1.3.6.1.4.1.8603.1.1.1.3 | AlarmSeverity | read-only | The event severity. |
| MOT rrMoType | 1.3.6.1.4.1.8603.1.1.1.4 | MoType | read-only | Type managed object associated with this trap. |
| INT rrMoId | 1.3.6.1.4.1.8603.1.1.1.5 | INTEGER | read-only | The instance of the managed object logical identifier. |
| ADD rrAddtlInfo | 1.3.6.1.4.1.8603.1.1.1.6 | AddtlInfo | read-only | Event description. |
| rrTraps | 1.3.6.1.4.1.8603.1.1.2 | |||
| rrTrapSpecific | 1.3.6.1.4.1.8603.1.1.2.0 | |||
| NTF alarmTrap | 1.3.6.1.4.1.8603.1.1.2.0.1 | Alarm notification. | ||
| NTF bootStatusUp | 1.3.6.1.4.1.8603.1.1.2.0.2 | The system is up and running. | ||
| NTF bootStatusDown | 1.3.6.1.4.1.8603.1.1.2.0.3 | The system has failed to boot or the system is shutting down. | ||
| NTF mcuOperStatus | 1.3.6.1.4.1.8603.1.1.2.0.120 | MCU operational status changed. | ||
| NTF mcuFaultLedStatus | 1.3.6.1.4.1.8603.1.1.2.0.121 | MCU fault LED status changed. | ||
| NTF mcuTempStatus | 1.3.6.1.4.1.8603.1.1.2.0.122 | MCU temperature status changed. | ||
| NTF mcuVoltageStatus | 1.3.6.1.4.1.8603.1.1.2.0.123 | MCU voltage status changed. | ||
| NTF mlpppStatus | 1.3.6.1.4.1.8603.1.1.2.0.160 | Multilink PPP status changed. | ||
| NTF bbuOperStatus | 1.3.6.1.4.1.8603.1.1.2.0.200 | BBU operational status changed. | ||
| NTF bbuFaultLedStatus | 1.3.6.1.4.1.8603.1.1.2.0.201 | BBU fault LED status changed. | ||
| NTF bbuTempStatus | 1.3.6.1.4.1.8603.1.1.2.0.202 | BBU temperature status changed. | ||
| NTF bbuVoltageStatus | 1.3.6.1.4.1.8603.1.1.2.0.203 | BBU voltage status changed. | ||
| NTF bbuDspStatus | 1.3.6.1.4.1.8603.1.1.2.0.204 | BBU DSP status changed. | ||
| NTF alarmInputStatus | 1.3.6.1.4.1.8603.1.1.2.0.280 | Alarm input status changed. | ||
| NTF accountingRadiusStatus | 1.3.6.1.4.1.8603.1.1.2.0.350 | Accounting/RADIUS server status changed. | ||
| flarionTraps | 1.3.6.1.4.1.8603.10 | |||
| flaTrapVars | 1.3.6.1.4.1.8603.10.1 | |||
| INT flaTimeStamp | 1.3.6.1.4.1.8603.10.1.1 | INTEGER | read-only | The time at which the event was generated. This value is expressed in seconds since 00:00:00 UTC, January 1, 1970 (see time(2)). |
| INT flaSeqNum | 1.3.6.1.4.1.8603.10.1.2 | INTEGER | read-only | The event sequence number. |
| ALA flaSeverity | 1.3.6.1.4.1.8603.10.1.3 | AlarmSeverity | read-only | The event severity. |
| MOT flaMoType | 1.3.6.1.4.1.8603.10.1.4 | MoType | read-only | Type managed object associated with this trap. |
| INT flaMoId | 1.3.6.1.4.1.8603.10.1.5 | INTEGER | read-only | The instance of the managed object logical identifier. |
| ADD flaAddtlInfo | 1.3.6.1.4.1.8603.10.1.6 | AddtlInfo | read-only | Event description. |
| flaTraps | 1.3.6.1.4.1.8603.10.2 | |||
| flaTrapPrefix | 1.3.6.1.4.1.8603.10.2.0 | |||
| NTF mcuBootStatusUp | 1.3.6.1.4.1.8603.10.2.0.1 | The MCU software is up and running. | ||
| NTF mcuBootStatusDown | 1.3.6.1.4.1.8603.10.2.0.2 | The MCU software is shutting down. | ||
| NTF mcuOperStatusUp | 1.3.6.1.4.1.8603.10.2.0.3 | MCU operational status is up. | ||
| NTF mcuOperStatusDown | 1.3.6.1.4.1.8603.10.2.0.4 | MCU operational status is down. | ||
| NTF mlpppStatusUp | 1.3.6.1.4.1.8603.10.2.0.5 | Multilink PPP status is up. | ||
| NTF mlpppStatusDown | 1.3.6.1.4.1.8603.10.2.0.6 | Multilink PPP status is up. | ||
| NTF bbuOperStatusUp | 1.3.6.1.4.1.8603.10.2.0.7 | BBU card operational status is up. | ||
| NTF bbuOperStatusDown | 1.3.6.1.4.1.8603.10.2.0.8 | BBU card operational status is down. | ||
| NTF bbuOperStatusNotPresent | 1.3.6.1.4.1.8603.10.2.0.9 | BBU card operational status is not present. | ||
| NTF bbuTempNormal | 1.3.6.1.4.1.8603.10.2.0.10 | BBU temperature has transitioned inot normal operating range. | ||
| NTF bbuTempHigh | 1.3.6.1.4.1.8603.10.2.0.11 | BBU temperature has transitioned into a high operating range. | ||
| NTF bbuTempSevere | 1.3.6.1.4.1.8603.10.2.0.12 | BBU temperature has transitioned into a severe operating range. | ||
| NTF bbuTempCritical | 1.3.6.1.4.1.8603.10.2.0.13 | BBU temperature has transitioned into a critical operating range. | ||
| NTF bbuVoltageNormal | 1.3.6.1.4.1.8603.10.2.0.14 | BBU voltage has transitioned into normal operating range. | ||
| NTF bbuVoltageHigh | 1.3.6.1.4.1.8603.10.2.0.15 | BBU voltage has transitioned above normal operating limits. | ||
| NTF bbuVoltageLow | 1.3.6.1.4.1.8603.10.2.0.16 | BBU voltage has transitioned below normal operating limits. | ||
| NTF dspStatusActive | 1.3.6.1.4.1.8603.10.2.0.17 | DSP has transitioned into the Active state. In this state, mobiles are allowed to establish connections and data traffic can be received/transmitted. | ||
| NTF dspStatusStandby | 1.3.6.1.4.1.8603.10.2.0.18 | DSP has transitioned into the Disabled/Standby state. In this state, mobiles can not establish connections and data traffic can not be received/transmitted. This is typically caused by administrative intervention or the DSP has initiated this state change due to an alarm condition elsewhere in the system. | ||
| NTF dspStatusOos | 1.3.6.1.4.1.8603.10.2.0.19 | DSP has transitioned into the Out of Service state. | ||
| NTF dspStatusNonOperational | 1.3.6.1.4.1.8603.10.2.0.20 | DSP has transitioned into the Non Operational state. This state is entered when the system is unable to determine the condition of the DSP. | ||
| NTF accountingRadiusUp | 1.3.6.1.4.1.8603.10.2.0.21 | Accounting/RADIUS server is up. | ||
| NTF accountingRadiusDown | 1.3.6.1.4.1.8603.10.2.0.22 | Accounting/RADIUS server is down. |
FAQ
What information does a FLARION-TRAP-MIB notification carry when a Flarion Flash-OFDM network element hits a fault condition?
Each trap carries a timestamp of when the event was generated, a sequence number, a severity level, the type and ID of the managed object raising the event, and additional diagnostic information -- giving operators a structured way to identify and correlate fault events.
Why would an operator monitoring a Flash-OFDM network rely on FLARION-TRAP-MIB notifications rather than only polling device status?
Because the trap framework standardizes how fault and event conditions are reported across all Flarion network element MIBs, operators can detect and correlate issues as they happen using the timestamp and sequence number in each notification, rather than waiting for the next polling cycle to catch a transient fault.
RFC description
Flarion trap MIB defining SNMP notification definitions for Flarion wireless broadband systems.
Start monitoring Flarion (Qualcomm) Flash-OFDM network element (common trap framework) 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.