PEA-EQUIPMENT-FELX
File:
PEA-EQUIPMENT-FELX.mib (23902 bytes)
Imported modules
Imported symbols
Defined Types
| DateType |
|
|
Represents a date:
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.
|
| TEXTUAL-CONVENTION |
|
|
|
| |
OCTET STRING |
Size(4) |
|
| IfTrafficForwardingEntry |
|
| SEQUENCE |
|
|
|
| |
ifIndexIngress |
InterfaceIndex |
|
| |
ifIndexEgress |
InterfaceIndex |
|
| |
ifTrafficForwardingEnable |
TruthValue |
|
| IfFlowControlEntry |
|
| SEQUENCE |
|
|
|
| |
ifFlowControlIndex |
InterfaceIndex |
|
| |
ifFlowControlEnable |
TruthValue |
|
| Dot3PhyModeEntry |
|
| SEQUENCE |
|
|
|
| |
dot3PhyModeIndex |
InterfaceIndex |
|
| |
dot3PhyMode |
INTEGER |
|
Defined Values
| 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.
|
| MODULE-IDENTITY |
|
|
|
| felxObjects |
1.3.6.1.4.1.193.72.800.10.1 |
| OBJECT IDENTIFIER |
|
|
|
| idData |
1.3.6.1.4.1.193.72.800.10.1.1 |
| OBJECT IDENTIFIER |
|
|
|
| ifObjects |
1.3.6.1.4.1.193.72.800.10.3 |
| OBJECT IDENTIFIER |
|
|
|
| dot3Objects |
1.3.6.1.4.1.193.72.800.10.11 |
| OBJECT IDENTIFIER |
|
|
|
| productNumberSup |
1.3.6.1.4.1.193.72.800.10.1.1.2.1 |
|
Index number that identifies the device.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(0..24) |
|
| revisionStateSup |
1.3.6.1.4.1.193.72.800.10.1.1.2.2 |
|
Revision State or 'R-state' declaring minor versions.
E.g. different types of components or new boot SW.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(0..7) |
|
| functionDesignationSup |
1.3.6.1.4.1.193.72.800.10.1.1.2.3 |
|
Number with reference to the handling and use of the product.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(0..12) |
|
| dateOfProductionSup |
1.3.6.1.4.1.193.72.800.10.1.1.2.4 |
|
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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DateType |
|
|
| dateOfRepairSup |
1.3.6.1.4.1.193.72.800.10.1.1.2.5 |
|
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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DateType |
|
|
| productionSerialNumberSup |
1.3.6.1.4.1.193.72.800.10.1.1.2.6 |
|
Unique serial number, describing the product in terms of a manufacturing
site code and a sequence number.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(13) |
|
| layoutVersionCodeSup |
1.3.6.1.4.1.193.72.800.10.1.1.2.7 |
|
The data layout version that allows the possibility
to interpret stored data differently.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
OCTET STRING |
Size(4) |
|
| idCheckSumSup |
1.3.6.1.4.1.193.72.800.10.1.1.2.8 |
|
CRC32 Checksum of identification data structure
of the device.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
OCTET STRING |
Size(4) |
|
| productNumberDdc |
1.3.6.1.4.1.193.72.800.10.1.1.3.1 |
|
Index number that identifies the device.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(0..24) |
|
| revisionStateDdc |
1.3.6.1.4.1.193.72.800.10.1.1.3.2 |
|
Revision State or 'R-state' declaring minor versions.
E.g. different types of components or new boot SW.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(0..7) |
|
| functionDesignationDdc |
1.3.6.1.4.1.193.72.800.10.1.1.3.3 |
|
Number with reference to the handling and use of the product.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(0..12) |
|
| dateOfProductionDdc |
1.3.6.1.4.1.193.72.800.10.1.1.3.4 |
|
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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DateType |
|
|
| dateOfRepairDdc |
1.3.6.1.4.1.193.72.800.10.1.1.3.5 |
|
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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DateType |
|
|
| productionSerialNumberDdc |
1.3.6.1.4.1.193.72.800.10.1.1.3.6 |
|
Unique serial number, describing the product in terms of a manufacturing
site code and a sequence number
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(13) |
|
| layoutVersionCodeDdc |
1.3.6.1.4.1.193.72.800.10.1.1.3.7 |
|
The data layout version that allows the possibility
to interpret stored data differently.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
OCTET STRING |
Size(4) |
|
| idCheckSumDdc |
1.3.6.1.4.1.193.72.800.10.1.1.3.8 |
|
CRC32 Checksum of identification data structure
of the device.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
OCTET STRING |
Size(4) |
|
| ifTrafficForwardingTable |
1.3.6.1.4.1.193.72.800.10.3.1 |
|
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).
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
SEQUENCE OF |
|
|
| |
|
IfTrafficForwardingEntry |
|
| ifTrafficForwardingEntry |
1.3.6.1.4.1.193.72.800.10.3.1.1 |
|
This is an entry of the ifTrafficForwardingTable.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
IfTrafficForwardingEntry |
|
|
| ifIndexIngress |
1.3.6.1.4.1.193.72.800.10.3.1.1.1 |
|
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.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
InterfaceIndex |
|
|
| ifIndexEgress |
1.3.6.1.4.1.193.72.800.10.3.1.1.2 |
|
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.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
InterfaceIndex |
|
|
| ifTrafficForwardingEnable |
1.3.6.1.4.1.193.72.800.10.3.1.1.3 |
|
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.
|
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
TruthValue |
|
|
| ifBandwidthMeasurementPeriod |
1.3.6.1.4.1.193.72.800.10.3.2 |
|
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.
|
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
Integer32 |
0..2147483647 |
|
| ifBandwidthUsageThreshold |
1.3.6.1.4.1.193.72.800.10.3.3 |
|
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.
|
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
Gauge32 |
1..99 |
|
| ifFlowControlTable |
1.3.6.1.4.1.193.72.800.10.3.5 |
|
This is to enable/disable the flow control function. The parameter
can be changed per interface (hence the table).
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
SEQUENCE OF |
|
|
| |
|
IfFlowControlEntry |
|
| ifFlowControlEntry |
1.3.6.1.4.1.193.72.800.10.3.5.1 |
|
This is an entry of the ifFlowContorlTable.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
IfFlowControlEntry |
|
|
| ifFlowControlIndex |
1.3.6.1.4.1.193.72.800.10.3.5.1.1 |
|
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.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
InterfaceIndex |
|
|
| ifFlowControlEnable |
1.3.6.1.4.1.193.72.800.10.3.5.1.2 |
|
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.
|
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
TruthValue |
|
|
| ifManagementInterfaceIndex |
1.3.6.1.4.1.193.72.800.10.3.6 |
|
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.
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
InterfaceIndex |
|
|
| dot1pQueuePriorityBarrier |
1.3.6.1.4.1.193.72.800.10.5.1 |
|
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.
|
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
0..7 |
|
| dot1pQoSEnable |
1.3.6.1.4.1.193.72.800.10.5.2 |
|
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.
|
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
TruthValue |
|
|
| tmsCommonIgmpSnoopEnabled |
1.3.6.1.4.1.193.72.800.10.9.8.1 |
|
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.
|
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
TruthValue |
|
|
| tmsCommonMiscSpanOnOff |
1.3.6.1.4.1.193.72.800.10.9.6.3 |
|
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.
|
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
enable(1), disable(2) |
|
| directionMask |
1.3.6.1.4.1.193.72.800.10.4.1.1 |
|
A general variable for direction: IN, OUT or BOTH.
|
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
none(0), in(1), out(2), both(3) |
|
| 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
|
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| 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
|
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| dot3PhyModeTable |
1.3.6.1.4.1.193.72.800.10.11.1 |
|
This is to modify the duplex mode and speed for each port.
This is an extension to RFC2665.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
SEQUENCE OF |
|
|
| |
|
Dot3PhyModeEntry |
|
| dot3PhyModeEntry |
1.3.6.1.4.1.193.72.800.10.11.1.1 |
|
This is an entry in the dot3PhyModeTable
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
Dot3PhyModeEntry |
|
|
| dot3PhyModeIndex |
1.3.6.1.4.1.193.72.800.10.11.1.1.1 |
|
This is an index to the dot3PhyModeTable. The indices are 1-based.
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
InterfaceIndex |
|
|
| dot3PhyMode |
1.3.6.1.4.1.193.72.800.10.11.1.1.2 |
|
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.
|
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
invalid(0), autoNeg(1), halfDuplex10(2), halfDuplex100(3), fullDuplex10(4), fullDuplex100(5), fullDuplex1000(6) |
|