IBM 8237 Installation And User Manual page 134

SYNTAX INTEGER (1..10)
ACCESS read-only
STATUS mandatory
DESCRIPTION "ID number of a hub unit, used to select it."
::= { basicFemEntry 1 }
basicFemType OBJECT-TYPE
SYNTAX INTEGER {
ACCESS read-only
STATUS mandatory
DESCRIPTION "Port type of the FEM port."
::= { basicFemEntry 2 }
basicFemLinkStatus OBJECT-TYPE
SYNTAX INTEGER {
ACCESS read-only
STATUS mandatory
DESCRIPTION "Link status of the FEM port."
::= { basicFemEntry 3 }
basicFemDuplexStatus OBJECT-TYPE
SYNTAX INTEGER {
ACCESS read-write
STATUS mandatory
DESCRIPTION "Setting this object to full-duplex(2) enables
the FEM port for full-duplex mode, so that the
port can send and receive frames at the same
time. Setting this object to auto-
negotiation(3) lets the transceiver decide the
duplex status of the port. The result of the
auto-negotiation is reflected as negotiated-
half-duplex(4) or negotiated-full-duplex(5).
Setting to these two values is not valid;
'snmpBadValue' will be returned."
::= { basicFemEntry 4 }
basicFemBackPressureStatus OBJECT-TYPE
SYNTAX INTEGER {
ACCESS read-write
STATUS mandatory
DESCRIPTION "Setting this object to enabled(1) enables the FEM
backpressure feature.
full, the FEM port will generate collisions
back to the source network everytime a frame is
received.
Setting this object to disabled(1) lets the FEM
port discard the input frames of the source
network when the output queue is full."
::= { basicFemEntry 5 }
basicFemForwardingMode OBJECT-TYPE
Appendix B. The IBM 8237 Management Information Base
not-present(1),
100base-tx(2),
100base-fx(3)
}
goodlink(1),
badlink(2)
}
half-duplex(1),
full-duplex(2),
auto-negotiation(3),
negotiated-half-duplex(4),
negotiated-full-duplex(5)
}
enabled(1),
disabled(2)
}
When the output queue is
B-17