FLARION-TRAP-MIB: View SNMP OID List / Download MIB

VENDOR: FLARION TECHNOLOGIES


 Home MIB: FLARION-TRAP-MIB
Download as:   
SNMPv2-CONF, SNMPv2-SMI, SNMPv2-TC, FLARION-MIB

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
         rrTrapVars 1.3.6.1.4.1.8603.1.1.1
             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)).
             rrSeqNum 1.3.6.1.4.1.8603.1.1.1.2 integer read-only
The event sequence number.
             rrSeverity 1.3.6.1.4.1.8603.1.1.1.3 alarmseverity read-only
The event severity.
             rrMoType 1.3.6.1.4.1.8603.1.1.1.4 motype read-only
Type managed object associated with this trap.
             rrMoId 1.3.6.1.4.1.8603.1.1.1.5 integer read-only
The instance of the managed object logical identifier.
             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
                 alarmTrap 1.3.6.1.4.1.8603.1.1.2.0.1
Alarm notification.
                 bootStatusUp 1.3.6.1.4.1.8603.1.1.2.0.2
The system is up and running.
                 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.
                 mcuOperStatus 1.3.6.1.4.1.8603.1.1.2.0.120
MCU operational status changed.
                 mcuFaultLedStatus 1.3.6.1.4.1.8603.1.1.2.0.121
MCU fault LED status changed.
                 mcuTempStatus 1.3.6.1.4.1.8603.1.1.2.0.122
MCU temperature status changed.
                 mcuVoltageStatus 1.3.6.1.4.1.8603.1.1.2.0.123
MCU voltage status changed.
                 mlpppStatus 1.3.6.1.4.1.8603.1.1.2.0.160
Multilink PPP status changed.
                 bbuOperStatus 1.3.6.1.4.1.8603.1.1.2.0.200
BBU operational status changed.
                 bbuFaultLedStatus 1.3.6.1.4.1.8603.1.1.2.0.201
BBU fault LED status changed.
                 bbuTempStatus 1.3.6.1.4.1.8603.1.1.2.0.202
BBU temperature status changed.
                 bbuVoltageStatus 1.3.6.1.4.1.8603.1.1.2.0.203
BBU voltage status changed.
                 bbuDspStatus 1.3.6.1.4.1.8603.1.1.2.0.204
BBU DSP status changed.
                 alarmInputStatus 1.3.6.1.4.1.8603.1.1.2.0.280
Alarm input status changed.
                 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
           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)).
           flaSeqNum 1.3.6.1.4.1.8603.10.1.2 integer read-only
The event sequence number.
           flaSeverity 1.3.6.1.4.1.8603.10.1.3 alarmseverity read-only
The event severity.
           flaMoType 1.3.6.1.4.1.8603.10.1.4 motype read-only
Type managed object associated with this trap.
           flaMoId 1.3.6.1.4.1.8603.10.1.5 integer read-only
The instance of the managed object logical identifier.
           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
               mcuBootStatusUp 1.3.6.1.4.1.8603.10.2.0.1
The MCU software is up and running.
               mcuBootStatusDown 1.3.6.1.4.1.8603.10.2.0.2
The MCU software is shutting down.
               mcuOperStatusUp 1.3.6.1.4.1.8603.10.2.0.3
MCU operational status is up.
               mcuOperStatusDown 1.3.6.1.4.1.8603.10.2.0.4
MCU operational status is down.
               mlpppStatusUp 1.3.6.1.4.1.8603.10.2.0.5
Multilink PPP status is up.
               mlpppStatusDown 1.3.6.1.4.1.8603.10.2.0.6
Multilink PPP status is up.
               bbuOperStatusUp 1.3.6.1.4.1.8603.10.2.0.7
BBU card operational status is up.
               bbuOperStatusDown 1.3.6.1.4.1.8603.10.2.0.8
BBU card operational status is down.
               bbuOperStatusNotPresent 1.3.6.1.4.1.8603.10.2.0.9
BBU card operational status is not present.
               bbuTempNormal 1.3.6.1.4.1.8603.10.2.0.10
BBU temperature has transitioned inot normal operating range.
               bbuTempHigh 1.3.6.1.4.1.8603.10.2.0.11
BBU temperature has transitioned into a high operating range.
               bbuTempSevere 1.3.6.1.4.1.8603.10.2.0.12
BBU temperature has transitioned into a severe operating range.
               bbuTempCritical 1.3.6.1.4.1.8603.10.2.0.13
BBU temperature has transitioned into a critical operating range.
               bbuVoltageNormal 1.3.6.1.4.1.8603.10.2.0.14
BBU voltage has transitioned into normal operating range.
               bbuVoltageHigh 1.3.6.1.4.1.8603.10.2.0.15
BBU voltage has transitioned above normal operating limits.
               bbuVoltageLow 1.3.6.1.4.1.8603.10.2.0.16
BBU voltage has transitioned below normal operating limits.
               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.
               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.
               dspStatusOos 1.3.6.1.4.1.8603.10.2.0.19
DSP has transitioned into the Out of Service state.
               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.
               accountingRadiusUp 1.3.6.1.4.1.8603.10.2.0.21
Accounting/RADIUS server is up.
               accountingRadiusDown 1.3.6.1.4.1.8603.10.2.0.22
Accounting/RADIUS server is down.