PEA-EQUIPMENT-FELX: View SNMP OID List / Download MIB

VENDOR: ERICSSON AB


 Home MIB: PEA-EQUIPMENT-FELX
Download as:   
PEM-STANDARD, SNMPv2-CONF, IF-MIB, PEA-POWER-ETHERNET-MIB, SNMPv2-SMI, PEA-FELX-SMI, SNMPv2-TC

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
 peaEquipmentFelx 1.3.6.1.4.1.193.72.800.10
The public ethernet access software supports a number of standard and proprietary MIBs. This MIB module defines objects specific to FELX switch.
       felxObjects 1.3.6.1.4.1.193.72.800.10.1
           idData 1.3.6.1.4.1.193.72.800.10.1.1
               supBoardIdData 1.3.6.1.4.1.193.72.800.10.1.1.2
                   productNumberSup 1.3.6.1.4.1.193.72.800.10.1.1.2.1 displaystring read-only
Index number that identifies the device.
                   revisionStateSup 1.3.6.1.4.1.193.72.800.10.1.1.2.2 displaystring read-only
Revision State or 'R-state' declaring minor versions. E.g. different types of components or new boot SW.
                   functionDesignationSup 1.3.6.1.4.1.193.72.800.10.1.1.2.3 displaystring read-only
Number with reference to the handling and use of the product.
                   dateOfProductionSup 1.3.6.1.4.1.193.72.800.10.1.1.2.4 datetype read-only
Manufacturing date, describing when the unit has been manufactured, in terms of a year, month and a day, as described below: Year code(0000 ..9999) - 2 bytes (LSB,MSB) Month (1..12)- 1 byte Day (1 ..31)- 1 byte. For example, Wednesday June 12, 2002 would be displayed as: h'02, h'14, h'06, h'0C.
                   dateOfRepairSup 1.3.6.1.4.1.193.72.800.10.1.1.2.5 datetype read-only
Repair date, declaring the year, month and day of the latest repair. The format is described below: Year code(0000 ..9999) - 2 bytes (LSB,MSB) Month (1..12)- 1 byte Day (1 ..31)- 1 byte. For example, Wednesday June 12, 2002 would be displayed as: h'02, h'14, h'06, h'0C.
                   productionSerialNumberSup 1.3.6.1.4.1.193.72.800.10.1.1.2.6 displaystring read-only
Unique serial number, describing the product in terms of a manufacturing site code and a sequence number.
                   layoutVersionCodeSup 1.3.6.1.4.1.193.72.800.10.1.1.2.7 octet string read-only
The data layout version that allows the possibility to interpret stored data differently.
                   idCheckSumSup 1.3.6.1.4.1.193.72.800.10.1.1.2.8 octet string read-only
CRC32 Checksum of identification data structure of the device.
               ddcBoardIdData 1.3.6.1.4.1.193.72.800.10.1.1.3
                   productNumberDdc 1.3.6.1.4.1.193.72.800.10.1.1.3.1 displaystring read-only
Index number that identifies the device.
                   revisionStateDdc 1.3.6.1.4.1.193.72.800.10.1.1.3.2 displaystring read-only
Revision State or 'R-state' declaring minor versions. E.g. different types of components or new boot SW.
                   functionDesignationDdc 1.3.6.1.4.1.193.72.800.10.1.1.3.3 displaystring read-only
Number with reference to the handling and use of the product.
                   dateOfProductionDdc 1.3.6.1.4.1.193.72.800.10.1.1.3.4 datetype read-only
Manufacturing date, describing when the unit has been manufactured, in terms of a year, month and a day, as described below: Year code(0000 ..9999) - 2 bytes (LSB,MSB) Month (1..12)- 1 byte Day (1 ..31)- 1 byte. For example, Wednesday June 12, 2002 would be displayed as: h'02, h'14, h'06, h'0C.
                   dateOfRepairDdc 1.3.6.1.4.1.193.72.800.10.1.1.3.5 datetype read-only
Repair date, declaring the year, month and day of the latest repair. The format is described below: Year code(0000 ..9999) - 2 bytes (LSB,MSB) Month (1..12)- 1 byte Day (1 ..31)- 1 byte. For example, Wednesday June 12, 2002 would be displayed as: h'02, h'14, h'06, h'0C.
                   productionSerialNumberDdc 1.3.6.1.4.1.193.72.800.10.1.1.3.6 displaystring read-only
Unique serial number, describing the product in terms of a manufacturing site code and a sequence number
                   layoutVersionCodeDdc 1.3.6.1.4.1.193.72.800.10.1.1.3.7 octet string read-only
The data layout version that allows the possibility to interpret stored data differently.
                   idCheckSumDdc 1.3.6.1.4.1.193.72.800.10.1.1.3.8 octet string read-only
CRC32 Checksum of identification data structure of the device.
       ifObjects 1.3.6.1.4.1.193.72.800.10.3
           ifTrafficForwardingTable 1.3.6.1.4.1.193.72.800.10.3.1 no-access
This is a symmetrical two-dimentional matrix indexed by the same interface numbers in both directions (ifIndex from IF-MIB). Every element of the matrix is a boolean value (TruthValue) indicating if the traffic from the corresponding ingress interface (the first index, e.g. vertical) can be switched to the corresponding egress interface (the second index, horizontal).
               ifTrafficForwardingEntry 1.3.6.1.4.1.193.72.800.10.3.1.1 no-access
This is an entry of the ifTrafficForwardingTable.
                   ifIndexIngress 1.3.6.1.4.1.193.72.800.10.3.1.1.1 interfaceindex no-access
This represents an ingress interface used in ifTrafficForwardingTable as the first index. All values of this index should coincide with the values of the ifIndex in the ifTable of the IF-MIB.
                   ifIndexEgress 1.3.6.1.4.1.193.72.800.10.3.1.1.2 interfaceindex no-access
This represents an egress interface used in ifTrafficForwardingTable as the second index. All values of this index should coincide with the values of the ifIndex in the ifTable of the IF-MIB.
                   ifTrafficForwardingEnable 1.3.6.1.4.1.193.72.800.10.3.1.1.3 truthvalue read-write
This defines if traffic forwarding from the corresponding ingress interface to the corresponding egress interface is enabled. The value of true(1) enables traffic forwarding. The value of false(2) disables traffic forwarding.
           ifBandwidthMeasurementPeriod 1.3.6.1.4.1.193.72.800.10.3.2 integer32 read-write
The bandwidth threshold function is used to monitor the average bandwidth over the ifBandwidthMeasurementPeriod on each of the device's external interfaces. If the measured average bandwidth (in percents to the maximum possible bandwidth on this particular interface) reaches the ifBandwidthUsageThreshold (given also in percents), the ifBandwidthUsageThresholdNotification is sent. Likewise, when the next measurement period with the average bandwidth lower than the ifBandwidthUsageThreshold is encountered, the ifBandwidthUsageThresholdCeasingNotification is sent. This defines the measurement period for the bandwidth threshold function. The period is expressed in minutes. The minimum possible value is 1 minute. The maximum possible value is limited by the size of a 32-bit integer (i.e. virtually unlimited). The value of 0 turns the function off. Setting this to a value different from the current value results in all the measurement counters being cleared and all active threshold notifications being ceased.
           ifBandwidthUsageThreshold 1.3.6.1.4.1.193.72.800.10.3.3 gauge32 read-write
The bandwidth threshold function is used to monitor the average bandwidth over the ifBandwidthMeasurementPeriod on each of the device's external interfaces. If the measured average bandwidth (in percents to the maximum possible bandwidth on this particular interface) reaches the ifBandwidthUsageThreshold (given also in percents), the ifBandwidthUsageThresholdNotification is sent. Likewise, when the next measurement period with the average bandwidth lower than the ifBandwidthUsageThreshold is encountered, the ifBandwidthUsageThresholdCeasingNotification is sent. This defines the threshold value for the bandwidth threshold function. The value is given in percents and can lie between 1 and 99 (inclusive). Setting this to a value different from the current value results in all the active threshold notifications being revised. The measurement counters are not cleared.
           ifFlowControlTable 1.3.6.1.4.1.193.72.800.10.3.5 no-access
This is to enable/disable the flow control function. The parameter can be changed per interface (hence the table).
               ifFlowControlEntry 1.3.6.1.4.1.193.72.800.10.3.5.1 no-access
This is an entry of the ifFlowContorlTable.
                   ifFlowControlIndex 1.3.6.1.4.1.193.72.800.10.3.5.1.1 interfaceindex no-access
This is an index to the ifFlowControlTable. All values of this index should coincide with the values of the ifIndex in the ifTable of the IF-MIB.
                   ifFlowControlEnable 1.3.6.1.4.1.193.72.800.10.3.5.1.2 truthvalue read-write
This defines if the flow control function is enabled on the particular interface.The value of true(1) enables flow control. The value of false(2) disables flow control.
           ifManagementInterfaceIndex 1.3.6.1.4.1.193.72.800.10.3.6 interfaceindex read-only
This is an index of the interface the management traffic is forwarded through. The value is for information only (there are cases, such as when the traffic is split among several interfaces, when the value cannot be relied upon). This parameter can take one of the values of the ifIndex in the ifTable of the IF-MIB.
       ifNotifications 1.3.6.1.4.1.193.72.800.10.4
           ifNotificationTypes 1.3.6.1.4.1.193.72.800.10.4.0
               ifBandwidthUsageThresholdNotification 1.3.6.1.4.1.193.72.800.10.4.0.1
The bandwidth threshold function is used to monitor the average bandwidth over the ifBandwidthMeasurementPeriod on each of the device's external interfaces. If the measured average bandwidth (in percents to the maximum possible bandwidth on this particular interface) reaches the ifBandwidthUsageThreshold (given also in percents), the ifBandwidthUsageThresholdNotification is sent. Likewise, when the next measurement period with the average bandwidth lower than the ifBandwidthUsageThreshold is encountered, the ifBandwidthUsageThresholdCeasingNotification is sent. This notification is sent when the measured average bandwidth on a particular interface has reached the ifBandwidthUsageThreshold. The 'direction' variable shows which counter has triggered the notification: 'in' - incoming traffic counter, 'out' - outgoing traffic counter. Corrective Actions: - None. Valid from: EDA 1.3 R2A Parameters 1: Managed object class ESN108 2: Managed object ID [MAC + PortNo] 3: Sequence number [Alarm sequence number] 4: Perceived severity Warning 5: Event time [Timestamp is retrieved from an SNTP server] 6: Event type QOS 7: Probable cause Other 8: Direction Mask [Direction of traffic (incoming or outgoing) which triggered the alarm] Ceasing OID: 1.3.6.1.4.1.193.72.600.1.2.0.7 # restartAlarm Ceasing OID: 1.3.6.1.4.1.193.72.800.10.4.0.2 # ifBandwidthUsageThresholdCeasingNotification
               ifBandwidthUsageThresholdCeasingNotification 1.3.6.1.4.1.193.72.800.10.4.0.2
The CEASING counterpart of ifBandwidthUsageThresholdNotification. Valid from: EDA 1.3 R2A Parameters 1: Managed object class ESN108 2: Managed object ID [MAC + PortNo] 3: Sequence number [Alarm sequence number] 4: Perceived severity Ceasing 5: Event time [Timestamp is retrieved from an SNTP server] 6: Event type QOS 7: Probable cause Other
           ifNotificationParameters 1.3.6.1.4.1.193.72.800.10.4.1
               directionMask 1.3.6.1.4.1.193.72.800.10.4.1.1 integer no-access
A general variable for direction: IN, OUT or BOTH. Enumeration: 'both': 3, 'none': 0, 'in': 1, 'out': 2.
       dot1pObjects 1.3.6.1.4.1.193.72.800.10.5
           dot1pQueuePriorityBarrier 1.3.6.1.4.1.193.72.800.10.5.1 integer read-write
This defines the lowest possible priority (802.1p) a packet should have to be placed in the HIGH PRIORITY queue. If the packet's priority is yet lower than this value, the packet is put in the LOW PRIORITY queue. A recommended default value of this parameter is 4, meaning that packets with priorities 0 through 3 are placed in the LOW PRIORITY queue and packets with priorities 4 through 7 are placed in the HIGH PRIORITY queue.
           dot1pQoSEnable 1.3.6.1.4.1.193.72.800.10.5.2 truthvalue read-write
This enables a separate handling of priority packets (802.1p). When enabled, the packets with priority equal or higher than the value of dot1pQueuePriorityBarrier are placed in the HIGH PRIORITY queue. The value of true(1) enables the function. The value of false(2) disables it.
       tmsCommonObjects 1.3.6.1.4.1.193.72.800.10.9
           tmsCommonMisc 1.3.6.1.4.1.193.72.800.10.9.6
               tmsCommonMiscSpanOnOff 1.3.6.1.4.1.193.72.800.10.9.6.3 integer read-write
THIS IS AN ALIAS FOR THE CORRESPONDING OBJECT FROM THE TMSCOMMON.MIB Enable/Disable Spanning Tree for the bridge. When 'disable(2)', all ports of the device are placed in the forwarding mode, regardless of current Spanning Tree state. When 'enable(1)', the normal STP state transitions take place. Enumeration: 'enable': 1, 'disable': 2.
           tmsCommonIgmpSnoop 1.3.6.1.4.1.193.72.800.10.9.8
               tmsCommonIgmpSnoopEnabled 1.3.6.1.4.1.193.72.800.10.9.8.1 truthvalue read-write
THIS IS AN ALIAS FOR THE CORRESPONDING OBJECT FROM THE TMSCOMMON.MIB Setting this object to true(1) enables IGMP Snooping. Setting it to false(2) disables IGMP Snooping. Note that IGMP Snooping can function with or without GVRP and GMRP enabled.
       dot3Objects 1.3.6.1.4.1.193.72.800.10.11
             dot3PhyModeTable 1.3.6.1.4.1.193.72.800.10.11.1 no-access
This is to modify the duplex mode and speed for each port. This is an extension to RFC2665.
                 dot3PhyModeEntry 1.3.6.1.4.1.193.72.800.10.11.1.1 no-access
This is an entry in the dot3PhyModeTable
                     dot3PhyModeIndex 1.3.6.1.4.1.193.72.800.10.11.1.1.1 interfaceindex no-access
This is an index to the dot3PhyModeTable. The indices are 1-based.
                     dot3PhyMode 1.3.6.1.4.1.193.72.800.10.11.1.1.2 integer read-write
This describes the duplex mode and speed for each port. This is an extension to RFC2665 where the duplex status and interface speed can be modifed for each port. For ports 1-8, allowed values are autoNeg, halfDuplex10, halfDuplex100, fullDuplex10, fullDuplex100. Setting is not allowed for port 9. It can be only read. For port 9, the value retuned indicates the type of SFP module inserted. If no SFP module is inserted, invalid(0) is returned. If 100Mbps SFP module is inserted, fullDuplex100(5) is returned. If 1000Mbs SFP module is inserted, fullDuplex1000(6) is returned. Enumeration: 'fullDuplex10': 4, 'invalid': 0, 'fullDuplex1000': 6, 'halfDuplex100': 3, 'halfDuplex10': 2, 'fullDuplex100': 5, 'autoNeg': 1.