MFRAP-MIB
AI MIB Summary
Standard SNMP MIB module defining data structures for MFRAP-MIB.
1031
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
1031 total| Object Name |
|---|
private OBJECT IDENTIFIER .1.3.6.1.4 |
RFC-1215 Unknown .1.3.6.1.4 |
enterprises OBJECT IDENTIFIER .1.3.6.1.4.1 |
sync OBJECT IDENTIFIER .1.3.6.1.4.1.485 |
mfrap OBJECT IDENTIFIER .1.3.6.1.4.1.485.8 |
mfrapTrapAn mfrapTrap trap signifies that the
sending node had its `mfrapAlarmType`
variable modified. TRAP-TYPE .1.3.6.1.4.1.485.8.0.0 |
mfrapBadConfigTrapUnit has received a configuration
update request through SNMP but the
request was rejected to due an incorrect
or inappropriate parameter. TRAP-TYPE .1.3.6.1.4.1.485.8.0.1 |
mfrapLocalConfigTrapUnit configuration has been updated locally
(console port or front panel keypad) or
remotely (telnet). TRAP-TYPE .1.3.6.1.4.1.485.8.0.2 |
mfrapt1netwcarrierlossUnit is not detecting a signal from the
wide area network. TRAP-TYPE .1.3.6.1.4.1.485.8.0.3 |
mfrapt1netwcarrierdetectUnit is detecting a signal from the wide
area network. TRAP-TYPE .1.3.6.1.4.1.485.8.0.4 |
mfrapt1netwsynclossdeclareUnit is not properly synchronized to the
signal received from the wide area network.
Frame synchronization is required for normal
operation. TRAP-TYPE .1.3.6.1.4.1.485.8.0.5 |
mfrapt1netwsyncacquireUnit is now synchronized with the signal
received from the wide area network. TRAP-TYPE .1.3.6.1.4.1.485.8.0.6 |
mfrapt1netwredalarmdeclareUnit has experienced loss of frame
synchronization for an extended time
and is reporting an alarm condition that
severely impairs normal operation. During
this Red Alarm condition the unit will
transmit Yellow alarm back to the network.
If this condition persists consult your
service provider. TRAP-TYPE .1.3.6.1.4.1.485.8.0.7 |
mfrapt1netwredalarmclearUnit has achieved frame synchronization for
a length of time necessary to declare the
interface stable and operational. TRAP-TYPE .1.3.6.1.4.1.485.8.0.8 |
mfrapt1netwyellowalarmdetectUnit is receiving a yellow alarm indication
from the wide area network. Detection of
yellow alarm implies that the attached device
is in a red alarm conditon. Red alarm is declared
due to the extended absence of a properly framed
signal. If this condition persists consult your
service provider. TRAP-TYPE .1.3.6.1.4.1.485.8.0.9 |
mfrapt1netwyellowalarmclearUnit is no longer receiving a yellow alarm
indication from the wide area network. Yellow
alarm implies that the attached device is in a
red alarm conditon. Red alarm is declared due
to the extended absence of a properly framed signal. TRAP-TYPE .1.3.6.1.4.1.485.8.0.10 |
mfrapt1netwaisdetectUnit is receiving unframed all ones from the
wide area network (AIS, blue alarm). Detection
of AIS implies that the attached device is reporting
an alarm condition from an upstream device. If
this condition persists consult your service provider. TRAP-TYPE .1.3.6.1.4.1.485.8.0.11 |
mfrapt1netwaisclearUnit is no longer receiving unframed all ones
from the wide area network (AIS, blue alarm).
Detection of AIS implies that the attached device
is reporting an alarm condition from an upstream
device. TRAP-TYPE .1.3.6.1.4.1.485.8.0.12 |
mfrapt1controlledslipUnit is reporting an occurrence of a timing slip
causing either the deletion or repetition of a
block of data. This is indicative of a timing
problem within the application. Check for multiple
clock sources or the absence of a stable clock source. TRAP-TYPE .1.3.6.1.4.1.485.8.0.13 |
mfrapLocalUnitLoopbackEnabledTrapUnit is in a bidirectional unit loopback. Data
is received from either interface, processed,
and transmitted back towards the same interface.
When configured for Frame Relay operation the unit
will preserve the LMI path during this loopback.
In Frame Relay mode, only valid frames are looped
back (pseudorandom test patterns will be dropped). TRAP-TYPE .1.3.6.1.4.1.485.8.0.14 |
mfrapLocalUnitLoopbackDisabledTrapBidirectional unit loopback path is removed. TRAP-TYPE .1.3.6.1.4.1.485.8.0.15 |
mfrapLocalUnitLoopbackFailedTrapBidirectional unit loopback request has been
rejected by the unit. Typically, this is due
to the presence of another loopback condition. TRAP-TYPE .1.3.6.1.4.1.485.8.0.16 |
mfrapLocalDteLoopbackEnabledTrapUnit is in a bidirectional DTE loopback. All
data received at the DTE interface is looped
back regardless of format or content (line
loopback). When configured for Frame Relay
operation the unit will not preserve the LMI
path during this loopback. Data received from
the WAN is processed and transmitted back out
the WAN. In Frame Relay mode, on the WAN
interface, only valid frames are looped back
(pseudorandom test patterns will be dropped). TRAP-TYPE .1.3.6.1.4.1.485.8.0.17 |
mfrapLocalDteLoopbackDisabledTrapBidirectional DTE loopback path is removed. TRAP-TYPE .1.3.6.1.4.1.485.8.0.18 |
mfrapLocalDteLoopbackFailedTrapBidirectional DTE loopback request has been
rejected by the unit. Typically, this is due
to the presence of another loopback condition. TRAP-TYPE .1.3.6.1.4.1.485.8.0.19 |
mfrapLocalAggregateLoopbackEnabledTrapUnit is in local aggregate loopback. All data
received from the DTE is transmit to the WAN and
also looped back towards the DTE at a point just
prior to WAN transmission (digital loopback). When
configured for Frame Relay operation the unit will
not preserve the LMI path during this loopback. In
Frame Relay mode only valid frames are looped back
(pseudorandom test patterns will be dropped). TRAP-TYPE .1.3.6.1.4.1.485.8.0.20 |
mfrapLocalAggregateLoopbackDisabledTrapLocal aggregate loopback path is removed. TRAP-TYPE .1.3.6.1.4.1.485.8.0.21 |
mfrapLocalAggregateLoopbackFailedTrapLocal aggregate loopback request has been rejected
by the unit. Typically, this is due to the presence
of another loopback condition. TRAP-TYPE .1.3.6.1.4.1.485.8.0.22 |
mfrapLocalPayloadLoopbackEnabledTrapUnit is in payload loopback. All data received from
the WAN, regardless of format or content, is processed
at the physical layer before being reframed and
transmit back out the WAN. All ones are sent to the
DTE during this diagnostic state. When configured for
Frame Relay operation the unit will not preserve the
LMI path during this loopback. TRAP-TYPE .1.3.6.1.4.1.485.8.0.23 |
mfrapLocalPayloadLoopbackDisabledTrapLocal payload loopback path is removed. TRAP-TYPE .1.3.6.1.4.1.485.8.0.24 |
mfrapLocalPayloadLoopbackFailedTrapLocal payload loopback request has been rejected.
Typically, this is due to the presence of another
loopback condition. TRAP-TYPE .1.3.6.1.4.1.485.8.0.25 |
mfrapLocalNetLoopbackEnabledTrapUnit is in local network loopback. All data
received from the WAN, regardless of format or
content, is transmitted back out (line interface
loopback) while still being sent to the DTE. When
configured for Frame Relay operation the unit
will not preserve the LMI path during this loopback. TRAP-TYPE .1.3.6.1.4.1.485.8.0.26 |
mfrapLocalNetLoopbackDisabledTrapLocal network loopback path is removed. TRAP-TYPE .1.3.6.1.4.1.485.8.0.27 |
mfrapLocalNetLoopbackFailedTrapLocal network loopback request is rejected.
Typically, this is due to the presence of another
loopback condition. TRAP-TYPE .1.3.6.1.4.1.485.8.0.28 |
mfrapV54LoopUpInitiatedTrapUnit has sent the standard V54 loop up pattern
out the WAN at the DTE rate. A compatible piece
of equipment can sense this pattern and enter a
loopback state - typically putting up a bidirectional
DTE loopback path. After sending the V54 loop up
pattern, the (local) unit returns to normal operation,
expecting a loopback condition at the remote device. TRAP-TYPE .1.3.6.1.4.1.485.8.0.29 |
mfrapV54LoopDownCompletedTrapUnit has sent the standard V54 loop down pattern
out the WAN at the DTE rate. A compatible piece of
equipment can sense this pattern remove the loopback
state that is entered after receiving a loop up pattern -
typically a bidirectional DTE loopback path. After
sending the V54 loop down pattern, the unit returns
to normal operation. TRAP-TYPE .1.3.6.1.4.1.485.8.0.30 |
mfrapV54LoopbackEnabledTrapUnit has received a V54 loop up pattern from a
compatible piece of equipment. A bidirectional DTE
loopback is activated. All data received at the
DTE interface is looped back regardless of format
or content. When configured for Frame Relay
operation the unit will not preserve the LMI path
during this loopback. Data received from the WAN is
processed and transmitted back out the WAN. In
Frame Relay mode, on the WAN interface, only valid
frames are looped back (pseudorandom test patterns
will be dropped). TRAP-TYPE .1.3.6.1.4.1.485.8.0.31 |
mfrapV54LoopbackDisabledTrapUnit has received a V54 loop down pattern from
a compatible piece of equipment. The bidirectional
local DTE loopback is removed. TRAP-TYPE .1.3.6.1.4.1.485.8.0.32 |
mfrapV54LoopbackFailedTrapUnit has rejected the request to send a V54 loop
up. Typically, this is due to the presence of
another loopback condition. TRAP-TYPE .1.3.6.1.4.1.485.8.0.33 |
mfrapCsuLoopUpInitiatedTrapUnit has sent a standard CSU loop up pattern at
the full WAN rate. A compatible piece of equipment
can sense this pattern and enter a loopback state -
typically putting up a network line loopback.
After sending the CSU loop up pattern, the (local)
unit returns to normal operation, expecting a
loopback condition at the attached device. TRAP-TYPE .1.3.6.1.4.1.485.8.0.34 |
mfrapCsuLoopDownCompletedTrapUnit has sent the standard CSU loop down pattern
out the WAN at the full WAN rate. A compatible piece
of equipment can sense this pattern and remove the
loopback state that is entered after receiving a
loop up pattern - typically a network line loopback.
After sending the CSU loop down pattern, the unit
returns to normal operation. TRAP-TYPE .1.3.6.1.4.1.485.8.0.35 |
mfrapCsuLoopbackEnabledTrapUnit has received a standard CSU loop up pattern
and will enter a local network loopback state. All
data received from the WAN, regardless of format
or content, is transmitted back out (line interface
loopback) while still being sent to the DTE. When
configured for Frame Relay operation the unit will
not preserve the LMI path during this loopback. TRAP-TYPE .1.3.6.1.4.1.485.8.0.36 |
mfrapCsuLoopbackDisabledTrapUnit has received a standard CSU loop down pattern
and will remove the local network loopback path. TRAP-TYPE .1.3.6.1.4.1.485.8.0.37 |
mfrapCsuLoopbackFailedTrapUnit has rejected the request to send a CSU loop up.
Typically, this is due to the presence of another
loopback condition. TRAP-TYPE .1.3.6.1.4.1.485.8.0.38 |
mfrapDsuLoopUpInitiatedTrapUnit has sent a proprietary DSU loop up pattern at
the full WAN rate. A compatible piece of equipment
can sense this pattern and enter a network line
loopback state. After sending the DSU loop up
pattern, the (local) unit returns to normal
operation, expecting a loopback condition at the
remote device. TRAP-TYPE .1.3.6.1.4.1.485.8.0.39 |
mfrapDsuLoopDownCompletedTrapUnit has sent the proprietary DSU loop down pattern
out the WAN at the full WAN rate. A compatible
piece of equipment can sense this pattern and remove
a network line loopback condition. After sending the
DSU loop down pattern, the unit returns to normal
operation. TRAP-TYPE .1.3.6.1.4.1.485.8.0.40 |
mfrapDsuLoopbackEnabledTrapUnit has received a proprietary DSU loop up pattern
and will enter a local network loopback state. All
data received from the WAN, regardless of format or
content, is transmitted back out (line interface
loopback) while still being sent to the DTE. When
configured for Frame Relay operation the unit will
not preserve the LMI path during this loopback. TRAP-TYPE .1.3.6.1.4.1.485.8.0.41 |
mfrapDsuLoopbackDisabledTrapUnit has received a proprietary DSU loop down
pattern and will remove the local network
loopback path. TRAP-TYPE .1.3.6.1.4.1.485.8.0.42 |
mfrapDsuLoopbackFailedTrapUnit has rejected the request to send a DSU loop up.
Typically, this is due to the presence of another
loopback condition. TRAP-TYPE .1.3.6.1.4.1.485.8.0.43 |
mfrapBertInitiatedTrapUnit is sending a pseudorandom test pattern
(511 or QRSS) out the WAN and monitoring the
WAN received data for the same pattern. This
test may be ineffective in certain frame relay
applications as pseudorandom data lacks appropriate
framing. TRAP-TYPE .1.3.6.1.4.1.485.8.0.44 |
mfrapBertCompletedTrapUnit has stopped sending a pseudorandom test
pattern out the WAN. TRAP-TYPE .1.3.6.1.4.1.485.8.0.45 |
mfrapBertFailedTrapUnit has rejected the request to enter a BERT
test state. Typically, this is due to the presence
of another diagnostic condition. TRAP-TYPE .1.3.6.1.4.1.485.8.0.46 |
mfrapDLCIActiveTrapUnit is reporting this DLCI as active and
provisioned. An active DLCI is one that is
explictly declared ACTIVE in an LMI Full
Status Response (typically coming from a
frame relay switch). TRAP-TYPE .1.3.6.1.4.1.485.8.0.47 |
mfrapDLCIInactiveTrapUnit is reporting this DLCI as inactive. An
inactive DLCI is determined inactive one of two
ways: it is either explictly declared inactive
in an LMI Full Status Response (typically coming
from a frame relay switch) or a Full Status
Response is not seen causing a Full Status Timer
expiry. Having the unit's full status timer too
low could result in the unit falsely declaring DLCIs
inactive (then active again). This does not interfere
with any data activity on the DLCI but could result
in excessive traps. TRAP-TYPE .1.3.6.1.4.1.485.8.0.48 |
mfrapDLCITDThresholdTrapVNIP has measured a round-trip transit delay on this
PVC to this peer which exceeds the user-defined threshold. TRAP-TYPE .1.3.6.1.4.1.485.8.0.49 |
mfrapLmiSourcingChangePassthruTrapUnit is not sourcing any LMI messages. If this
state persists then LMI is up and the proper
handshaking is occurring independent of the unit.
This may also be a transient state if the unit
is in an LMI hunt mode. If this trap occurs
repeatedly, separated by other LMI sourcing states,
the unit is not seeing any of the expected LMI
messages from either interface. Check LMI type,
connectivity, and configuration of associated equipment. TRAP-TYPE .1.3.6.1.4.1.485.8.0.50 |
mfrapLmiSourcingChangeUserDteTrapUnit is acting as a source of LMI Status Requests
(Link Integrity Verification, Keep Alive). If this
state persists then the equipment attached to the
DTE interface is configured as a Frame Relay DCE
but a companion Frame Relay DTE device is not seen
out the WAN. This could also be a transient state
if the unit is in an LMI hunt mode. If this trap
occurs repeatedly, separated by other LMI sourcing
states, the unit is not seeing any of the expected
LMI messages from either interface. Check LMI type,
connectivity, and configuration of associated equipment. TRAP-TYPE .1.3.6.1.4.1.485.8.0.51 |
mfrapLmiSourcingChangeNetDteTrapUnit is acting as a source of LMI Status Responses
(Link Intergrity Verification, Keep Alive). If this
state persists then the equpiment attached to the
DTE interface is configured as a Frame Relay DTE
but a companion Frame Relay DCE device is not seen
out the WAN. This could also be a transient state
if the unit is in an LMI hunt mode. If this trap
occurs repeatedly, separated by other LMI sourcing
states, the unit is not seeing any of the expected
LMI messages from either interface. Check LMI type,
connectivity, and configuration of external equipment. TRAP-TYPE .1.3.6.1.4.1.485.8.0.52 |
mfrapLmiSourcingChangeUserT1TrapUnit is acting as a source of LMI Status Requests
(Link Integrity Verification, Keep Alive). If this
state persists then the equipment attached to the
WAN interface is configured as a Frame Relay DCE
but a companion Frame Relay DTE device is not seen
out the DTE interface. This could also be a transient
state if the unit is in an LMI hunt mode. If this
trap occurs repeatedly, separated by other LMI
sourcing states, the unit is not seeing any of the
expected LMI messages from either interface. Check
LMI type, connectivity, and configuration of
associated equipment. TRAP-TYPE .1.3.6.1.4.1.485.8.0.53 |
mfrapLmiSourcingChangeNetT1TrapUnit is acting as a source of LMI Status Responses
(Link Integrity Verification, Keep Alive). If this
state persists then the equipment attached to the
WAN interface is configured as a Frame Relay DTE
but a companion Frame Relay DCE device is not seen
out the DTE interface. This could also be a transient
state if the unit is in an LMI hunt mode. If this
trap occurs repeatedly, separated by other LMI sourcing
states, the unit is not seeing any of the expected
LMI messages from either interface. Check LMI type,
connectivity, and configuration of associated equipment. TRAP-TYPE .1.3.6.1.4.1.485.8.0.54 |
mfrapDteSignalRtsOnTrapUnit's DTE Request to Send (RTS) interface control
signal is now active (on). This signal is presented
by the external DTE device. Unit may be configured
to ignore the state of this signal or to require
it for data transmission. TRAP-TYPE .1.3.6.1.4.1.485.8.0.55 |
mfrapDteSignalRtsOffTrapUnit's DTE Request to Send (RTS) interface control
signal is now inactive (off). This signal is presented
by the external DTE device. Unit may be configured
to ignore the state of this signal or to require it
for data transmission. TRAP-TYPE .1.3.6.1.4.1.485.8.0.56 |
mfrapDteSignalDtrOnTrapUnit's DTE Data Terminal Ready (DTR) interface control
signal is now active (on). This signal is presented by the
external DTE device. The unit may be configured to ignore
the state of this signal or to require it for data transmission. TRAP-TYPE .1.3.6.1.4.1.485.8.0.57 |
mfrapDteSignalDtrOffTrapUnit's DTE Data Terminal Ready (DTR) interface control
signal is now inactive (off). This signal is presented by
the external DTE device. Unit may be configured to ignore
the state of this signal or to require it for data
transmission. TRAP-TYPE .1.3.6.1.4.1.485.8.0.58 |
mfrapNonIncrLmiSeqNumDteTrapUnit has detected a non-incrementing LMI sequence number
from the DTE. A Status Enquiry or Status Response message
has been seen at the DTE interface. The Link Integrity
information element's Send Sequence Number was not
incremented or was incremented more than once since the
last Send Sequence Number seen from the DTE interface. TRAP-TYPE .1.3.6.1.4.1.485.8.0.59 |
mfrapNonIncrLmiSeqNumT1TrapUnit has detected a non-incrementing LMI sequence number
from the WAN. A Status Enquiry or Status Response message
has been seen at the WAN interface. The Link Integrity
information element's Send Sequence Number was not
incremented or was incremented more than once since the
last Send Sequence Number seen from the WAN interface. TRAP-TYPE .1.3.6.1.4.1.485.8.0.60 |
mfrapLmiSeqNumMismatchDteTrapUnit has detetcted an LMI sequence number mismatch from
the DTE. A Status Enquiry or Status Response message has
been seen at the DTE interface. The Link Inetgrity information
element's Receive Sequence Number was not the most recent
Send Sequence number sent from the WAN interface. TRAP-TYPE .1.3.6.1.4.1.485.8.0.61 |
mfrapLmiSeqNumMismatchT1TrapUnit has detetcted an LMI sequence number mismatch from
the WAN. A Status Enquiry or Status Response message has
been seen at the WAN interface. The Link Inetgrity information
element's Receive Sequence Number was not the most recent
Send Sequence number sent from the DTE interface. TRAP-TYPE .1.3.6.1.4.1.485.8.0.62 |
mfrapTrapMutingActiveTrap generation is muted. TRAP-TYPE .1.3.6.1.4.1.485.8.0.75 |
mfrapTrapMutingInactiveTrap generation is re-enabled (muting disabled). TRAP-TYPE .1.3.6.1.4.1.485.8.0.76 |
mfrapVloopUpA Vnip PVC loopback (VLOOP) request has been sent to
a remote device on this DLCI out this interface. The
remote unit should respond by looping all data received
on this PVC back towards the unit that initiated this
request. A PVC running VLOOP will not be running any
user data. TRAP-TYPE .1.3.6.1.4.1.485.8.0.90 |
mfrapVloopDownA Vnip PVC loopback (VLOOP) disable request has been
sent to a remote device on this DLCI out this interface.
The remote unit should respond by tearing down the
logical loop on this DLCI. TRAP-TYPE .1.3.6.1.4.1.485.8.0.91 |
mfrapVloopUpViaRemoteA Vnip PVC loopback (VLOOP) request has been received
from a remote device on this DLCI on this interface.
The unit will respond by looping all data received on
this PVC back out the interface towards the unit that
initiated the request. TRAP-TYPE .1.3.6.1.4.1.485.8.0.92 |
mfrapVloopDownViaRemoteA request to disable a Vnip PVC loopback (VLOOP) on
this unit with the indicated DLCI and Interface has
been received. Usually this disable request is from
the remote device that requested the VLOOP, however
the request may also be due to a local event such as
expiration of a locally configured loopback timeout.
The unit will respond by tearing down the logical loop
on this DLCI. TRAP-TYPE .1.3.6.1.4.1.485.8.0.93 |
mfrapVloopRequestFailedThe request for a PVC loopback (VLOOP) has been rejected
or did not complete. TRAP-TYPE .1.3.6.1.4.1.485.8.0.94 |
mfrapVbertStartedA Vnip PVC error rate test (VBERT) has been started on
this DLCI out this interface to a remote device. The
VBERT test data will be statistically multiplexed in
with user data, management data, and networking data.
The destination peer will echo this test data back to
the source producing a full-duplex volume-based timed
test. TRAP-TYPE .1.3.6.1.4.1.485.8.0.95 |
mfrapVbertStoppedA Vnip PVC BERT (VBERT) has been stopped on this DLCI
on this interface to a remote device. TRAP-TYPE .1.3.6.1.4.1.485.8.0.96 |
mfrapVbertRequestFailedThe request for a PVC BERT (VBERT) on this DLCI
on this interface has been rejected. TRAP-TYPE .1.3.6.1.4.1.485.8.0.97 |
mfrapDandiCarrierLossUnit is not detecting a signal from the
Drop & Insert port. TRAP-TYPE .1.3.6.1.4.1.485.8.0.110 |
mfrapDandiCarrierDetectUnit is not detecting a signal from the
Drop & Insert port. TRAP-TYPE .1.3.6.1.4.1.485.8.0.111 |
mfrapDandiSyncLossDeclareUnit is not properly synchronized to the
signal received from the Drop & Insert port.
Frame synchronization is required for normal
operation. TRAP-TYPE .1.3.6.1.4.1.485.8.0.112 |
mfrapDandiSyncAcquireUnit is now synchronized with the signal
received from the Drop & Insert port. TRAP-TYPE .1.3.6.1.4.1.485.8.0.113 |
mfrapDandiRedAlarmDeclareUnit has experienced loss of frame
synchronization for an extended time
and is reporting an alarm condition that
severely impairs normal operation. During
this Red Alarm condition the unit will
transmit Yellow alarm back to the network.
If this condition persists consult your
service provider. TRAP-TYPE .1.3.6.1.4.1.485.8.0.114 |
mfrapDandiRedalArmclearUnit has achieved frame synchronization for
a length of time necessary to declare the
interface stable and operational. TRAP-TYPE .1.3.6.1.4.1.485.8.0.115 |
mfrapDandiYellowAlarmDetectUnit is receiving a yellow alarm indication
from the Drop & Insert port. Detection of
yellow alarm implies that the attached device
is in a red alarm conditon. Red alarm is declared
due to the extended absence of a properly framed
signal. If this condition persists consult your
service provider. TRAP-TYPE .1.3.6.1.4.1.485.8.0.116 |
mfrapDandiYellowAlarmClearUnit is no longer receiving a yellow alarm
indication from the Drop & Insert port. Yellow
alarm implies that the attached device is in a
red alarm conditon. Red alarm is declared due
to the extended absence of a properly framed signal. TRAP-TYPE .1.3.6.1.4.1.485.8.0.117 |
mfrapDandIaisDetectUnit is receiving unframed all ones from the
Drop & Insert port (AIS, blue alarm). Detection
of AIS implies that the attached device is reporting
an alarm condition from an upstream device. If
this condition persists consult your service provider. TRAP-TYPE .1.3.6.1.4.1.485.8.0.118 |
mfrapDandiAisClearUnit is no longer receiving unframed all ones
from the Drop & Insert port (AIS, blue alarm).
Detection of AIS implies that the attached device
is reporting an alarm condition from an upstream
device. TRAP-TYPE .1.3.6.1.4.1.485.8.0.119 |
mfrapDandiControlledSlipUnit is reporting an occurrence of a timing slip
causing either the deletion or repetition of a
block of data. This is indicative of a timing
problem within the application. Check for multiple
clock sources or the absence of a stable clock source. TRAP-TYPE .1.3.6.1.4.1.485.8.0.120 |
mfrapLocalDandiPayloadLoopbackEnabledTrapUnit is in local Drop & Insert payload loopback. All
Drop & Insert data received from the WAN, regardless
of format or content, is processed at the Drop & Insert
line interface before being reframed and transmited
back out the WAN. DTE data are unaffected. TRAP-TYPE .1.3.6.1.4.1.485.8.0.121 |
mfrapLocalDandiPayloadLoopbackDisabledTrapLocal Drop & Insert payload loopback path is removed. TRAP-TYPE .1.3.6.1.4.1.485.8.0.122 |
mfrapLocalDandiPayloadLoopbackFailureTrapLocal Drop & Insert payload loopback request has
been rejected. Typically, this is due to the
presence of another loopback condition. TRAP-TYPE .1.3.6.1.4.1.485.8.0.123 |
mfrapLocalDandiLineLoopbackEnabledTrapUnit is in local Drop & Insert line loopback. All
data received from the Drop & Insert port, regardless
of format or content, is transmitted back out (line
interface loopback) while still being sent to the WAN.
DTE data are unaffected. TRAP-TYPE .1.3.6.1.4.1.485.8.0.124 |
mfrapLocalDandiLineLoopbackDisabledTrapLocal Drop & Insert line loopback path is removed. TRAP-TYPE .1.3.6.1.4.1.485.8.0.125 |
mfrapLocalDandiLineLoopbackFailureTrapLocal Drop & Insert line loopback request is rejected.
Typically, this is due to the presence of another
loopback condition. TRAP-TYPE .1.3.6.1.4.1.485.8.0.126 |
mfrapNestFanOneAlarmUnit has received an alarm signal from
the nest that Fan 1 has malfunctioned. TRAP-TYPE .1.3.6.1.4.1.485.8.0.130 |
mfrapNestFanOneAlarmClearThe Fan 1 alarm signal from the nest
has been cleared. TRAP-TYPE .1.3.6.1.4.1.485.8.0.131 |
mfrapNestFanTwoAlarmUnit has received an alarm signal from
the nest that Fan 2 has malfunctioned. TRAP-TYPE .1.3.6.1.4.1.485.8.0.132 |
mfrapNestFanTwoAlarmClearThe Fan 2 alarm signal from the nest
has been cleared. TRAP-TYPE .1.3.6.1.4.1.485.8.0.133 |
mfrapNestPowerSupplyAlarmUnit has received an alarm signal from
the nest that the power supply has
malfunctioned. TRAP-TYPE .1.3.6.1.4.1.485.8.0.134 |
mfrapNestPowerSupplyAlarmClearThe power supply alarm signal from the nest
has been cleared. TRAP-TYPE .1.3.6.1.4.1.485.8.0.135 |
mfrapLocalPayloadLoopbackEnabledViaRemoteTrapLocal Payload loopback enabled Via Remote unit. TRAP-TYPE .1.3.6.1.4.1.485.8.0.136 |
mfrapLocalPayloadLoopbackDisabledViaRemoteTrapLocal Payload loopback disabled Via Remote unit. TRAP-TYPE .1.3.6.1.4.1.485.8.0.137 |
mfrapPvcRxUtilizationExceededTrapPercent utilization threshold was exceeded for the
defined number of Short Term Intervals in the
reception direction on this DLCI. TRAP-TYPE .1.3.6.1.4.1.485.8.0.138 |
mfrapPvcTxUtilizationExceededTrapPercent utilization threshold was exceeded for the
defined number of Short Term Intervals in the
transmission direction on this DLCI. TRAP-TYPE .1.3.6.1.4.1.485.8.0.139 |
mfrapPvcRxUtilizationClearedTrapPercent utilization was below the threshold for the
defined number of Short Term Intervals in the
reception direction on this DLCI. TRAP-TYPE .1.3.6.1.4.1.485.8.0.140 |
mfrapPvcTxUtilizationClearedTrapPercent utilization was below the threshold for the
defined number of Short Term Intervals in the
transmission direction on this DLCI. TRAP-TYPE .1.3.6.1.4.1.485.8.0.141 |
mfrapConfigInstallSuccessThe configuration install process has successfully
completed. TRAP-TYPE .1.3.6.1.4.1.485.8.0.142 |
mfrapTftpRequestedTrapUnit has received a TFTP download request. TFTP is
the preferred method for upgrading a unit's software
image. TRAP-TYPE .1.3.6.1.4.1.485.8.0.257 |
mfrapTftpTransferringTrapUnit has established a TFTP session, found the file,
and begun the transfer. The file must still be qualified
as appropriate for this unit. TRAP-TYPE .1.3.6.1.4.1.485.8.0.258 |
mfrapTftpProgrammingTrapUnit has completed the TFTP transfer of a new software
image which will next be programmed into non-volatile
flash memory. TRAP-TYPE .1.3.6.1.4.1.485.8.0.259 |
mfrapTftpAbortedTrapUnit's TFTP session was established but the transfer was
aborted by user intervention or an unrecoverable TFTP
protocol error. TRAP-TYPE .1.3.6.1.4.1.485.8.0.260 |
mfrapTftpSuccessTrapUnit's TFTP download completed successfully. Flash
devices will be programmed with a new image. Unit will stop
passing data during the programming phase (less than a minute)
and, upon completion, will reset and return to full operation
using the new image. TRAP-TYPE .1.3.6.1.4.1.485.8.0.261 |
mfrapTftpHostUnreachableTrapUnit could not establish a TFTP session with the
designated server. Verify that the correct TFTP
ip address, TFTP DLCI and TFTP interface are
configured on the unit and also verify the TFTP
server confguration. TRAP-TYPE .1.3.6.1.4.1.485.8.0.262 |
mfrapTftpNoFileTrapUnit could not locate the designated file on the TFTP
server. Verify the correct TFTP filename is configured
on the unit and verify the location of this file on
the server (file name may be case sensitive). TRAP-TYPE .1.3.6.1.4.1.485.8.0.263 |
mfrapTftpInvalidFileTrapUnit had established a TFTP session and began transfer
of the designated file. The unit aborted the transfer
after determining that the specified file is not
appropriate for this product (failed header verification). TRAP-TYPE .1.3.6.1.4.1.485.8.0.264 |
mfrapTftpCorruptFileTrapUnit transferred the designated file but aborted the
operation due to a checksum error within the downloaded
s-record file. TRAP-TYPE .1.3.6.1.4.1.485.8.0.265 |
mfrapSystem OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.1 |
mfrapSysTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.1.1 |
mfrapSysTypeA textual description of the system model identifier.
for example: SYNC-MFRAPro DisplayString .1.3.6.1.4.1.485.8.1.1.1 |
mfrapSysSoftRevDisplays the Software Revision of the application code
installed in this node.ro DisplayString .1.3.6.1.4.1.485.8.1.1.2 |
mfrapSysHardRevDisplays the Hardware Revision of the node.ro DisplayString .1.3.6.1.4.1.485.8.1.1.3 |
mfrapSysNumT1InstalledThe number of Wide Area Network (T1) ports that are
installed. There is 1 on the MFRAP.ro INTEGER .1.3.6.1.4.1.485.8.1.1.4 |
mfrapSysNumDteInstalledThe number of user serial data channels (DTE) that are
installed. There is 1 on the MFRAP.ro INTEGER .1.3.6.1.4.1.485.8.1.1.5 |
mfrapSysNumMaintInstalledThe number of Async Maintenance/Comm (console ports
that are installed. There are 2 on the MFRAP: one
for the console interface and one for SLIP management.ro INTEGER .1.3.6.1.4.1.485.8.1.1.6 |
mfrapSysNameThe user supplied name of the node. This object
does not affect operation, but may be useful
for network management.rw DisplayString .1.3.6.1.4.1.485.8.1.1.7 |
mfrapSysSerialNoThe serial number of the board.ro DisplayString .1.3.6.1.4.1.485.8.1.1.8 |
mfrapSysResetNodeCommand to reset the node. NODE WILL BE OFF-LINE AND
USER DATA WILL BE INTERRUPTED FOR APPROXIMATELY 15
SECONDS. Full network recovery may take longer.rw Enumeration .1.3.6.1.4.1.485.8.1.1.9 |
mfrapSysAmtMemoryInstalledThe amount of memory (RAM) installed (in megabytes).ro INTEGER .1.3.6.1.4.1.485.8.1.1.10 |
mfrapSysLocationThe user supplied location of the node. This
object does not affect operation, but may be
useful for network management.rw DisplayString .1.3.6.1.4.1.485.8.1.1.12 |
mfrapSysContactThe user supplied contact information for the
node. This object does not affect operation,
but may be useful for network management.rw DisplayString .1.3.6.1.4.1.485.8.1.1.13 |
mfrapSysPromptConfigurable Command Line Interface (CLI) prompt. CLI
is the User Interface protocol used for directly
attached VT100 terminal access and for remote
access via Telnet.rw DisplayString .1.3.6.1.4.1.485.8.1.1.15 |
mfrapSysBootRevDisplays the Software Revision of the Bootstrapping
code installed in this node.ro DisplayString .1.3.6.1.4.1.485.8.1.1.16 |
mfrapSysNestIdThe user supplied name of the nest where this card
resides. This can be used to group all cards from
the same nest together for network management. Note
an MFRAP standalone unit will not allow this to be
'set' and will return the string 'standalone'.rw DisplayString .1.3.6.1.4.1.485.8.1.1.17 |
mfrapSysFeatureTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.1.2 |
mfrapSysSLIPSupportedShows whether the unit has SLIP (Serial Line IP) capability.
SLIP is a method for out-of-band management that connects
through the asynchronous terminal port.ro DisplayString .1.3.6.1.4.1.485.8.1.2.1 |
mfrapSysPPPSupportedShows whether the unit has PPP (Point to Point protocol)
capability. PPP is a method for out-of-band management
that connects through the asynchronous terminal port.ro DisplayString .1.3.6.1.4.1.485.8.1.2.2 |
mfrapSysRDOSupportedShows whether the unit has Remote Dial Out capability.ro DisplayString .1.3.6.1.4.1.485.8.1.2.3 |
mfrapSysETHSupportedShows whether the unit has Ethernet capability.ro DisplayString .1.3.6.1.4.1.485.8.1.2.4 |
mfrapSysTKRSupportedShows whether the unit has Token Ring capability.ro DisplayString .1.3.6.1.4.1.485.8.1.2.5 |
mfrapSysExtTimSupportedShows whether the unit has External Timing capability.ro DisplayString .1.3.6.1.4.1.485.8.1.2.6 |
mfrapSysBRISupportedShows whether the unit has BRI (ISDN Basic Rate) capability.ro DisplayString .1.3.6.1.4.1.485.8.1.2.7 |
mfrapSysSelDTESupportedShows whether the unit has a Selectable DTE interface.ro DisplayString .1.3.6.1.4.1.485.8.1.2.8 |
mfrapSysMLSupportedShows whether the unit supports MLs
(out-of-band management links).ro DisplayString .1.3.6.1.4.1.485.8.1.2.9 |
mfrapSysNumDlcisSupportedShows how many DLCIs can be monitored
for Short Term Statistics.ro INTEGER .1.3.6.1.4.1.485.8.1.2.10 |
mfrapSysLTFNumDlcisShows how many DLCIs can be specified
in the Long Term Statistics Filter.ro INTEGER .1.3.6.1.4.1.485.8.1.2.11 |
mfrapSysLTFNumProtocolsShows how many protocols can be specified
in the Long Term Statistics Filter.ro INTEGER .1.3.6.1.4.1.485.8.1.2.12 |
mfrapSysNumUserProtocolsShows how many protocols can be defined by the user.
The user configures TCP/UDP ports which can be monitored
as protocols. They are available for short term or
long term statistics monitoring.ro INTEGER .1.3.6.1.4.1.485.8.1.2.13 |
mfrapSysNumSnmpMgrsShows how many SNMP managers can be programmed in the
table mfrapCfgSnmpMngrTable. These managers are sent
TRAPs if configured to do so.ro INTEGER .1.3.6.1.4.1.485.8.1.2.14 |
mfrapSysNumDlciNamesShows how many DLCI names can be defined by the user
in the table mfrapCfgFrPerfDlciNamesTable.ro INTEGER .1.3.6.1.4.1.485.8.1.2.15 |
mfrapConfiguration OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.2 |
mfrapCfgMgmtTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.2.1 |
mfrapCfgIpTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.2.1.1 |
mfrapCfgIpMyIPThe IP address for this node. This address will be unique to
the IP network and is required for in-band or out-of-band
ip and SNMP management.rw IpAddress .1.3.6.1.4.1.485.8.2.1.1.1 |
mfrapCfgIpPeerIPThis parameter is not used internally by
the unit. It is intended to identify either
the device directly connected to the SLIP
port or, in Frame Relay applications, the
address of the primary network management
station. This should always be non-zero.rw IpAddress .1.3.6.1.4.1.485.8.2.1.1.2 |
mfrapCfgIpMaskThe IP Network Mask (eg 255.255.255.0).rw IpAddress .1.3.6.1.4.1.485.8.2.1.1.3 |
mfrapCfgIpMaxMTUThe Maximum Transmission Unit is the size of the
largest IP packet supported. This value should
be set to the lowest value supported by any
equipment in the transmission path. A size of
1006 (including header) is suggested.rw INTEGER .1.3.6.1.4.1.485.8.2.1.1.4 |
mfrapCfgIpChannelThis is the method by which IP traffic is being carried.
Either via the SLIP port or a DLCI. This is how
your InBand Managenent scheme is set up.ro Enumeration .1.3.6.1.4.1.485.8.2.1.1.5 |
mfrapCfgIpTelnetEnableEnables/Disables the telnet feature.
Valid values are enable-telnet (1)
and disable-telnet (2).rw Enumeration .1.3.6.1.4.1.485.8.2.1.1.6 |
mfrapCfgIpTelnetAutoLogOutEnables/Disables the telnet auto-logout, logging out
the user after a certain length of idle time.
Valid values are disable-autologout (2), and a
number of timeout intervals including
autologout-at-15-minutes (1), autologout-at-3-minutes (3),
and the default autologout-at-5-minutes (5).rw Enumeration .1.3.6.1.4.1.485.8.2.1.1.7 |
mfrapCfgTftpTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.2.1.2 |
mfrapCfgTftpInitiateAfter setting the other TFTP parameters,
start the TFTP Flash ROM upgrade
by entering the TFTP password.rw DisplayString .1.3.6.1.4.1.485.8.2.1.2.1 |
mfrapCfgTftpIpAddressThe IP address of the TFTP host from which
to retrieve the Flash ROM image.rw IpAddress .1.3.6.1.4.1.485.8.2.1.2.2 |
mfrapCfgTftpFilenameThe filename of the new ROM Image on the TFTP host.rw DisplayString .1.3.6.1.4.1.485.8.2.1.2.3 |
mfrapCfgTftpInterfaceThe interface on which TFTP data passes. This is
only used for in-band management modes. When a unit is
in SLIP mode, this object is not applicable. A 'get'will
return a value of '3' and set is ignored.
(1) dte-interface
(2) t1-interface
(3) Not applicablerw Enumeration .1.3.6.1.4.1.485.8.2.1.2.4 |
mfrapCfgTftpDlciThe DLCI on which the TFTP host can be found.
A value of -1 signifies not-applicable.rw INTEGER (-1..63487) .1.3.6.1.4.1.485.8.2.1.2.5 |
mfrapCfgTftpStatusThe status of current or most recent TFTP operation.
Download can be canceled by a Set to inactive.rw Enumeration .1.3.6.1.4.1.485.8.2.1.2.6 |
mfrapCfgTftpNumBytesThe number of Bytes from the ROM image that have been
TFTP'd to the unitro Counter .1.3.6.1.4.1.485.8.2.1.2.7 |
mfrapCfgSnmpTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.2.1.3 |
mfrapCfgSnmpFrTrapControls whether or not the Frame Relay DLCI
status change traps are issued. These traps are
dfrapDLCIActiveTrap and dfrapDLCIInactiveTrap.
(1) FR Trap enabled - a trap will be sent each time
an individual DLCI changes status between active
and inactive.
(2) FR Trap disabled - DLCI state change traps are not sent.rw Enumeration .1.3.6.1.4.1.485.8.2.1.3.1 |
mfrapCfgSnmpMgrTableThe table of IP addresses of SNMP managers to receive
this node's TRAPs. SEQUENCE OF MfrapCfgSnmpMgrEntry .1.3.6.1.4.1.485.8.2.1.3.2 |
mfrapCfgSnmpMgrEntryThe IP address of a SNMP manager to receive this node's TRAPs. MfrapCfgSnmpMgrEntry .1.3.6.1.4.1.485.8.2.1.3.2.1 |
mfrapCfgSnmpMgrIndexThe index to the list of SNMP managers receiving TRAPs.ro INTEGER .1.3.6.1.4.1.485.8.2.1.3.2.1.1 |
mfrapCfgSnmpMgrIPThe IP address of a SNMP manager to receive this node's TRAPs.
Setting this value to 0.0.0.0 will disable the issuance of
traps to the indexed manager.rw IpAddress .1.3.6.1.4.1.485.8.2.1.3.2.1.2 |
mfrapCfgSnmpMgrInterfaceThe interface out which the indexed trap manager can be
reached. This entry is required in Piggyback and Bi-directional
in-band managed applications. In Local, Remote and SLIP-based
applications, the interface is known and this parameter is
ignored.
(1) Traps sent out DTE interface for this manager
(2) Traps sent out T1 interface for this manager
(3) Traps sent out SLIP interface (async maint port)
When the node is configured for SLIP, a GET on this MIB
object will return slip-interface(3) and a SET of this MIB
object to slip-interface(3) is allowed but unnecessary.
When the node is not configured for SLIP, this MIB
object can be SET to dte-interface(1) or t1-interface(2);
slip-interface(3) would be rejected.rw Enumeration .1.3.6.1.4.1.485.8.2.1.3.2.1.3 |
mfrapCfgSnmpMgrDlciThe DLCI to use to send TRAPs to this SNMP manager.rw INTEGER .1.3.6.1.4.1.485.8.2.1.3.2.1.4 |
mfrapCfgSnmpTrapMutingControls whether TRAPs are sent or muted. A value of
0 allows TRAPs to be sent. If not 0, the value represents
the interval (minutes) at which to send the MutingActive
trap. It is the only trap sent during muting. The valid
range for the interval is 30 to 10080 (a week).rw INTEGER .1.3.6.1.4.1.485.8.2.1.3.3 |
mfrapCfgSnmpNestAlarmTrapEnableEnables or disables the sending of traps for fan
and/or power supply alarms. Note an MFRAP standalone unit
will not allow this to be 'set' and will return the 'disable'.rw Enumeration .1.3.6.1.4.1.485.8.2.1.3.4 |
mfrapCfgSnmpDandIPortTrapEnableEnables or disables the sending of traps for the
Drop and Insert port.
(1) enable the sending of traps
(2) disable the sending of trapsrw Enumeration .1.3.6.1.4.1.485.8.2.1.3.5 |
mfrapCfgSnmpUtilTrapEnableEnables or disables the sending of per-DLCI
utilization traps.
(1) enable utilization traps
(2) disable utilization trapsrw Enumeration .1.3.6.1.4.1.485.8.2.1.3.6 |
mfrapCfgSnmpMgrClearNDeletes the number of entries in the mfrapCfgSnmpMgrTable
indicated by the value. If the value is a positive number
the entries will be deleted starting from the first entry.
If the value is negative the entries will be deleted
starting from the last entry.rw INTEGER .1.3.6.1.4.1.485.8.2.1.3.7 |
mfrapCfgCommTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.2.1.4 |
mfrapCfgCommModeThe protocol running on the Maintenance port. VT100 (1), for
the User Interface, SLIP (2) for the SNMP support,
MODEM(3) for remote VT100 support.rw Enumeration .1.3.6.1.4.1.485.8.2.1.4.1 |
mfrapCfgCommBaudAsynchronous baud rate for the Maintenance/Comm port
(Console). This must be configured to match either the
VT100 compatible terminal, MODEM support or the SLIP Terminal
Server depending upon the Comm port mode.
(2) baud-2400
(4) baud-9600
(5) baud-19200
(6) baud-38400rw Enumeration .1.3.6.1.4.1.485.8.2.1.4.2 |
mfrapCfgCommDataBitsDatabits for this Communication port. Values
are databits-7 (1) and databits-8 (2).rw Enumeration .1.3.6.1.4.1.485.8.2.1.4.3 |
mfrapCfgCommStopBitsNumber of Stopbits for this Communication port.
Values are stopbits-1 (1), stopbits-1-5 (2),
and stopbits-2 (3).rw Enumeration .1.3.6.1.4.1.485.8.2.1.4.4 |
mfrapCfgCommParityParity for this Communication port. Values are
no-parity (1), odd-parity (2), even-parity (3).rw Enumeration .1.3.6.1.4.1.485.8.2.1.4.5 |
mfrapCfgCommFlowCtrlFlow Control for this Communication port. Values
are no-flow-control (1).rw Enumeration .1.3.6.1.4.1.485.8.2.1.4.6 |
mfrapCfgCommModeAutoDetectEnables or disables the auto detection of RS-232
data on the front MAINT port. When enabled, and data
detected, the unit will temporarily convert to VT100 mode
to allow a local user access when the unit is in SLIP
or MODEM mode.
(1) enable COMM-MAINT port auto detect
(2) disable COMM-MAINT port auto detectrw Enumeration .1.3.6.1.4.1.485.8.2.1.4.7 |
mfrapCfgFrDLCITable OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.2.1.5 |
mfrapCfgFrDLCIModeShows the mode that DLCI In-band Management is set up for -
inactive (1) - Inband management is not enabled;
local (2) - Inband managed using a dedicated private
PVC with access exclusively through the
DTE interface;
remote (3) - Inband managed using a dedicated private
PVC with access exclusively through the
WAN interface;
bidirectional (4) - Inband managed using a dedicated private
PVC with access supported through either
interface;
piggyback (5) - Inband managed using any provisioned PVC,
statistically multiplexed with user data;
fixedDCE (6) - Inband managed mode similar to piggyback
mode except for LMI behavior; The unit
will always source LMI Responses separately
on each interface (emulating a Frame Relay
DCE device). A single PVC will be provisioned
and is used for both user data and management
traffic. This mode of operation is useful in
an environment that does not include a Frame
Relay switch but does include a pair of
interconnected Frame Relay FRADs or Routers
which can only be configured as a Frame Relay
DTE device.rw Enumeration .1.3.6.1.4.1.485.8.2.1.5.1 |
mfrapCfgFrDLCIValueThe DLCI identifier, the value of the DLCI field in the frame.rw INTEGER .1.3.6.1.4.1.485.8.2.1.5.2 |
mfrapCfgFrDLCIEncapThis is the protocol used for enacapsulating and formatting
ip data for Frame Relay transmission. This setting is specific
to management data to and from the unit.
(1) RFC1490 - per IETF standard with Network Level
Protocol ID (NLPID) set for IP encapsulation.
(2) RFC1490 SNAP/IP - per IETF standard with NLPID set
for Sub-Network Access Protocol (SNAP).
(3) auto - adjusts to either of these encapsulation techniques
as required.
(4) Cisco - proprietary encapsulation (4-byte header).rw Enumeration .1.3.6.1.4.1.485.8.2.1.5.3 |
mfrapCfgFrDLCIMgmtDEProvides user control over the state of the Frame Relay Discard
Eligibility bit of all management frames generated by
the unit. Frames marked DE=1 are more likely to be dropped in a
congested Frame Relay network than those that are DE=0. Heavily
congested circumstances can cause both to be dropped. Additionally,
frames marked DE=0 may get re-marked to DE=1 by intervening
equipment.
(1) DE bit cleared to 0: frame is not discard eligible
(2) DE bit set to 1: frame is discard eligiblerw Enumeration .1.3.6.1.4.1.485.8.2.1.5.4 |
mfrapCfgAppTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.2.2 |
mfrapCfgAppClockSourceDefault timing, or clock, source. There must be only one
source on a T1 line. Node should always be network (2)
timed on a point-to-network application. Line
Driver applications need one node as internal (1),
one as network (2). Options are given to source
the clock from the DTE port or the D&I port.rw Enumeration .1.3.6.1.4.1.485.8.2.2.1 |
mfrapCfgAppCircuitIdCircuit identifier provided by the service provider.rw DisplayString .1.3.6.1.4.1.485.8.2.2.2 |
mfrapCfgAppTypeIndicates type of service purchased on the attached
network line T1. Valid selections are
dedicated (1) and Frame Relay (2).rw Enumeration .1.3.6.1.4.1.485.8.2.2.3 |
mfrapCfgAppFormatRefer to Application Type. Frame Relay is based upon
HDLC framing. To operate in a Frame Relay application
the Format must be set for HDLC. To operate in a
protocol-independent application the Format must be
set for Constant Bit Operation (CBO). Note - changing
this value will automatically change the Application
Type setting and vice versa
(1) CBO: protocol-independent transparent DSU/CSU
(2) HDLC: Frame and protocol aware DSU/CSUrw Enumeration .1.3.6.1.4.1.485.8.2.2.4 |
mfrapCfgAppLpbkTimeoutThe amount of time a loopback may run before
timing out and automatically terminating.
The timeout is in minutes and a value of 0
means no timeout.rw INTEGER .1.3.6.1.4.1.485.8.2.2.5 |
mfrapCfgAppPerfBuffLimitThis value represents the throttling mechanism
used to determine the optimum level of statistical
processing versus managability of the unit. The
lower the value (1 - 128), the unit becomes more
responsive to management commands during very heavy
utilization at the possible expense of statistical
accuracy. The larger the value (129 - 512), the
more accurate the MFRAP performs statistical analysis
of the frames but management may seem slow or
unresponsive during periods of very heavy link
utilization.
NOTE: A value of 0 disables statistical
processing entirely.rw INTEGER .1.3.6.1.4.1.485.8.2.2.10 |
mfrapCfgT1Table OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.2.3 |
mfrapCfgT1FramingType of Framing on this T1 Line. Check with your service
provider to determine value.
(1) D4 - also known as Superframe or SF.
(2) ESF 54016 - Extended Superframe supporting the Facility Data
Link per AT&T pub 54016. ESF provides enhanced performance
monitoring capabilities over the FDL.
(3) ESF ANSI - Extended SuperFrame supporting the Facility Data
Link per ANSI T1.403 standard. ESF provides enhanced performance
monitoring capabilities over the FDL.rw Enumeration .1.3.6.1.4.1.485.8.2.3.1 |
mfrapCfgT1LineEncodingT1 interface bipolar encoding scheme. Check with your
service provider to determine value. B8ZS, which inherently
provides ample 'ones-density', is recommended. AMI users
must pay special attention to the 'ones-density' requirements
of the service provider.
(1) B8ZS - intercepts and encodes streams of 8 consecutive zeros
and transmits them as a special pattern including Bipolar or
Line Code Violations. Function not supported on certain networks.
(2) AMI - Alternate Mark Inversion - sends the user data without
introducing controlled BPVs.rw Enumeration .1.3.6.1.4.1.485.8.2.3.2 |
mfrapCfgT1DensityCSU 'ones density' monitor. Defines the maximum number of
consecutive zeros that can be transmitted to the WAN.
If density monitoring is enabled, the composite signal
is guaranteed to meet the selected density threshhold at
the expense of user data.
(1) No Density Monitoring - unit will transparently transmit
user data without regard for ones density. Recommended for
use in B8ZS applications, in nx56K applications where
bit-7 stuffing is configured for DTE Channel Density, and
when an external CSU is used.
(2) 12.5% - unit will maintain a sliding window and will assure
a minumum of 12.5% or an average of 1 in 8 ones.
(3) 1 in 16 - unit will guarantee that no more than 15 consecutive
zeros will be transmit to the WAN.
(4) 1 in 64 - unit will guarantee that no more than 63 consecutive
zeros will be transmit to the WAN.rw Enumeration .1.3.6.1.4.1.485.8.2.3.3 |
mfrapCfgT1InterfaceEnables the unit's internal CSU functionality. Typical
network access requires a CSU to condition the WAN signal,
guard against network hazards, and provide access to
service personnel for network maintenance.
(1) Disables internal CSU and unit operates as a DSX-1 cross
connect device. This should be the setting if the unit is
cabled to an external CSU device providing network access.
CSU.
(2) Enables internal CSU and corresponding feature set which
includes density monitoring, line build-out pulse shaping,
ESF facility data link, and certain diagnostic functions.
This should be the seting if the unit is directly cabled
to the service provider's equipment (such as a smart jack).rw Enumeration .1.3.6.1.4.1.485.8.2.3.4 |
mfrapCfgT1LboSettingCSU Line Build Out (LBO). This feature provides selectable output
signal strength. Consult service provider for proper setting. Signal
may require attenuation to equalize it with neighboring equipment
or under certain cabled access conditions. Not applicable if CSU
functions are diabled (interface type = dsx-1)
(1) 0dB - standard output signal
(2) -7.5dB - standard output signal attenuated by 7.5dB
(3) -15dB - standard output signal attenuated by 15 dB.rw Enumeration .1.3.6.1.4.1.485.8.2.3.5 |
mfrapCfgDteTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.2.4 |
mfrapCfgDteIntfTypeSets the electrical interface for the DTE port.
(3) V.35 interface
(4) RS-449 interface (not supported)ro Enumeration .1.3.6.1.4.1.485.8.2.4.1 |
mfrapCfgDteDataModeInverts the DTE data for transfer across the WAN. Can make
some applications, particularly HDLC-based protocols, meet
density requirements even across clear channel DS0s in AMI
mode.rw Enumeration .1.3.6.1.4.1.485.8.2.4.2 |
mfrapCfgDteClockModeThis selection controls how the unit internally latches
the transmit data from the DTE. Normal will sample
data with the rising edge of the selected TX Clock,
Invert will sample data with the falling edge of the
selected TX Clock. The TX Clock is selected using
CfgDteTiming. This clock invertion is most useful when
loop-2 timing is used - particularly at higher rates
and with long cable runs. Only in rare circumstances
will clock-invert be used with loop-1 timing. If the
DTE Interface TX statistics are indicating excessive
crc errors or aborts then changing this setting may have
some benefit.
(1) normal
(2) invertrw Enumeration .1.3.6.1.4.1.485.8.2.4.3 |
mfrapCfgDteTimingSerial DTE Transmit Timing mode. Loop-1 (1) uses the clock
returned from the DTE (TT/TCE) to sample tx data, Loop-2 (2)
uses the clock (ST/TC) generated by the node to sample tx
data.rw Enumeration .1.3.6.1.4.1.485.8.2.4.4 |
mfrapCfgDteLineRateSerial DTE Data Rate in bits per second. Valid
rates depend upon channel density selection: nX56K for
bit-7-stuffing, and nX64K for clear-channel (n is an
integer 1-24 inclusive). This read-only value is the
value which was most recently set through CfgDteConnRate;
in the event of a connection failure, this field should be
examined along with CfgDteChannelDensity and CfgDteStartDso
to determine the parameter mismatch that caused the connection
failure.ro INTEGER .1.3.6.1.4.1.485.8.2.4.5 |
mfrapCfgDteChannelDensityPacking of serial data into T1 DS0's. Bit-7-stuff
supports DTE rates of nX56Kb/s (from 56K to 1344K) and
provides sufficient ones-density on any circuit.
Clear-channel allows DTE rates of nX64Kb/s (from 64K
to 1.536M) and may require an additional means
of density enforcement (eg, B8ZS). This read-only value
is the value which was most recently set through CfgDteConnDensity;
in the event of a connection failure, this field should be
examined along with CfgDteLineRate and CfgDteStartDso to
determine the parameter mismatch that caused the connection
failure.ro Enumeration .1.3.6.1.4.1.485.8.2.4.6 |
mfrapCfgDteStartDs0T1 WAN includes 24 DS0's available for user data. Each DS0
carries either 56Kbit/sec (bit-7-stuffing) or 64KBit/sec
(clear-channel). This value is the starting DS0 used by the
node to allocate DS0s to match the DTE's data rate. Sequential,
contiguous DS0s are assigned as required. The number of DS0s
required is based upon the DTE Data Rate and DTE Channel Mapping.
This read-only value is the value which was most recently set
through DteCfgConnStartDs0; in the event of a connection failure,
this field should be examined along with CfgDteLineRate and
CfgDteChanelDensity to determine the parameter mismatch that
caused the connection failure.ro Enumeration .1.3.6.1.4.1.485.8.2.4.7 |
mfrapCfgDteConnStatusThe current status of the WAN to DTE mappings.
(1) connections valid and DS0s allocated to DTE data.
(4) no connections configured between WAN and DTE.ro Enumeration .1.3.6.1.4.1.485.8.2.4.8 |
mfrapCfgDteConnStartDs0T1 WAN includes 24 DS0's available for user data. Each DS0
carries either 56Kbit/sec (bit-7-stuffing) or 64KBit/sec
(clear-channel). This value is the starting DS0 used by the
node to allocate DS0s to match the DTE's data rate. Sequential,
contiguous DS0s are assigned as required. The number of DS0s
required is based upon the DTE Data Rate and DTE Channel Mapping.
Consult WAN service provider for the appropriate setting here in
a fractional T1 application.rw Enumeration .1.3.6.1.4.1.485.8.2.4.9 |
mfrapCfgDteConnRateSerial DTE Data Rate in bits per second. Valid
rates depend upon channel density selection: nX56K for
bit-7-stuffing, and nX64K for clear-channel (n is an
integer 1-24 inclusive). Rates are entered in bits/sec,
for example, 128000 for a 128Kbit/sec DTE data rate.rw INTEGER .1.3.6.1.4.1.485.8.2.4.10 |
mfrapCfgDteConnDensityPacking of serial data into T1 DS0's. Bit-7-stuff
supports DTE rates of nX56Kb/s (from 56K to 1344K) and
provides sufficient ones-density on any circuit.
Clear-channel supports DTE rates of nX64Kb/s (from 64K
to 1.536M) and may require an additional means
of density enforcement (eg, B8ZS).
(56) Bit 7 Stuffing (nx56K data rate, n=1-24)
(64) Clear Channel (nx64K data rate, n=1-24)rw Enumeration .1.3.6.1.4.1.485.8.2.4.11 |
mfrapCfgDteConnDs0RequiredThe number of DS0s required by the node's DTE port.
This is based upon the DTE data rate and channel density
selections.ro INTEGER .1.3.6.1.4.1.485.8.2.4.12 |
mfrapCfgDteConnAutoStatusThere's a tight correlation among DTE data rate, starting
DS0, and channel density. This read-only parameter reports
the status of the most recent change to any of these connection
parameters. If the connection request is not valid a mismatch
among DteLineRate, DteStartDs0, and DteChannelDensity must be
resolved
(1) and (3) configuration valid - the previous connections profile is
accepted and activated
(2) and (4) connections profile invalid, previous configuration
remains.ro Enumeration .1.3.6.1.4.1.485.8.2.4.13 |
mfrapCfgDteConnAutoUpdateUpdates the connection-critical parameters: line rate,
channel density and starting ds0; drops the currect
connection; and initiate the new connection. Following
the issuance of this command, DteAutoStatus should be
queried to verify the update was successful. The setting
of this object updates the mfrapCfgEditTable. In order
for the changes to take effect in the system, the
mfrapCfgConnUpdateCmd must subsequently be set.rw Enumeration .1.3.6.1.4.1.485.8.2.4.14 |
mfrapCfgDteRtsSelects whether the RTS signal is external-from-dte (2)
or internal-held-active (1).rw Enumeration .1.3.6.1.4.1.485.8.2.4.15 |
mfrapCfgDteDtrSelects whether the DTR signal is external-from-dte (2)
or internal-held-active (1).rw Enumeration .1.3.6.1.4.1.485.8.2.4.16 |
mfrapCfgDteDcdOutputSpecifies the behavior of this control signal generated by
the M-FRAP towards the DTE.
inactive-always (1) - signal is permanently INACTIVE.
active-always (2) - signal is permanently ACTIVE.
reflect-carrier (3) - signal echoes the carrier signal status
from the WAN.
inactive-with-test-mode (4) - signal is ACTIVE during normal
data transfer and INACTIVE during diagnostic conditions
that interfere with data transfer from the DTE to the WAN.
follow-RTS (5) - signal echoes the status of RTS as processed
from the DTE.
reflect-carrier-and-RTS (6) - signal is a logical AND between
RTS processed from the DTE and the carrier signal status
from the WAN. No signal from the WAN or RTS INACTIVE
will cause this control signal to be asserted INACTIVE.
reflect-sync-and-RTS (7) - signal is a logical AND between RTS
processed from the DTE and the frame synchronization with the WAN.
Red Alarm defines the threshold for declaring synchronization.
reflect-LMI-and-carrier-and-RTS (8) - signal is a logical AND
between RTS processed from the DTE and the carrier signal
status from the WAN and LMI. If the unit is in an LMI
passthrough state then LMI is considered Active.
LMI Inactivity timer must be non-zero for LMI to be declared
Inactive.
Note that there is a separate parameter for how the unit processes
RTS that is related to this function if options (4), (5), (6), or (7)
is selected, see CfgDteRts.rw Enumeration .1.3.6.1.4.1.485.8.2.4.18 |
mfrapCfgDteDsrOutputSpecifies the behavior of this control signal generated by
the M-FRAP towards the DTE.
inactive-always (1) - signal is permanently INACTIVE.
active-always (2) - signal is permanently ACTIVE.
reflect-carrier (3) - signal echoes the carrier signal status
from the WAN.
inactive-with-test-mode (4) - signal is ACTIVE during normal
data transfer and INACTIVE during diagnostic conditions
that interfere with data transfer from the DTE to the WAN.
follow-RTS (5) - signal echoes the status of RTS as processed
from the DTE.
reflect-carrier-and-RTS (6) - signal is a logical AND between
RTS processed from the DTE and the carrier signal status
from the WAN. No signal from the WAN or RTS INACTIVE
will cause this control signal to be asserted INACTIVE.
reflect-sync-and-RTS (7) - signal is a logical AND between RTS
processed from the DTE and the frame synchronization with the WAN.
Red Alarm defines the threshold for declaring synchronization.
reflect-LMI-and-carrier-and-RTS (8) - signal is a logical AND
between RTS processed from the DTE and the carrier signal
status from the WAN and LMI. If the unit is in an LMI
passthrough state then LMI is considered Active.
LMI Inactivity timer must be non-zero for LMI to be declared
Inactive.
Note that there is a separate parameter for how the unit processes
RTS that is related to this function if options (4), (5), (6), or (7)
is selected, see CfgDteRts.rw Enumeration .1.3.6.1.4.1.485.8.2.4.19 |
mfrapCfgDteCtsOutputSpecifies the behavior of this control signal generated by
the M-FRAP towards the DTE.
inactive-always (1) - signal is permanently INACTIVE.
active-always (2) - signal is permanently ACTIVE.
reflect-carrier (3) - signal echoes the carrier signal status
from the WAN.
inactive-with-test-mode (4) - signal is ACTIVE during normal
data transfer and INACTIVE during diagnostic conditions
that interfere with data transfer from the DTE to the WAN.
follow-RTS (5) - signal echoes the status of RTS as processed
from the DTE.
reflect-carrier-and-RTS (6) - signal is a logical AND between
RTS processed from the DTE and the carrier signal status
from the WAN. No signal from the WAN or RTS INACTIVE
will cause this control signal to be asserted INACTIVE.
reflect-sync-and-RTS (7) - signal is a logical AND between RTS
processed from the DTE and the frame synchronization with the WAN.
Red Alarm defines the threshold for declaring synchronization.
reflect-LMI-and-carrier-and-RTS (8) - signal is a logical AND
between RTS processed from the DTE and the carrier signal
status from the WAN and LMI. If the unit is in an LMI
passthrough state then LMI is considered Active.
LMI Inactivity timer must be non-zero for LMI to be declared
Inactive.
Note that there is a separate parameter for how the unit processes
RTS that is related to this function if options (4), (5), (6), or (7)
is selected, see CfgDteRts.rw Enumeration .1.3.6.1.4.1.485.8.2.4.20 |
mfrapCfgFrTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.2.5 |
mfrapCfgFrAddrLenDefines the size of the DLCI address field of the Frame Relay
header. This setting must correspond to the Frame Relay
transmission format; typically Two bytes.
(1) two byte DLCI address field
(2) three byte DLCI address field
(3) four byte DLCI address fieldrw Enumeration .1.3.6.1.4.1.485.8.2.5.1 |
mfrapCfgFrCrcModeThis defines the manner in which the unit handles HDLC
protocol errors (crc errors) in a Frame Relay application.
If Discard is selected the unit will respond to an errored
frame by aborting the frame if transmission has begun; or
simply discarding it if transmission has not begun. If
Passthru is selected the unit will transmit the entire frame
but will place an incorrect crc in it to preserve the error
indication.
(1) discard
(2) passthrurw Enumeration .1.3.6.1.4.1.485.8.2.5.2 |
mfrapCfgFrLmiTypeThe LMI type used in a Frame Relay application. This setting
must match the attached Frame Relay device configuration.
Annex-A and Annex-D use DLCI 0, and Type 1 uses DLCI 1023.
Type 1 is alternatively referred to as Cisco, Group of four,
or simply LMI. Annex-D may be referred to as ANSI T1.617.
Annex-A may be referred to as ITU or CCITT Q.933. Auto-sense
will either use the most recently detected LMI type or, in
the absence of any LMI, will attempt to instigate LMI
communications using each protocol.
(1) Annnex-A: conforms to ITU (CCITT) Q.933 annex A
(2) Annnex-D: conforms to ANSI T1.617 annex D
(3) Type 1: conforms to the original LMI as developed by
the Group of Four
(4) Auto-sense: unit will attempt to detect and synchronize
to the LMI type of the attached equipment.rw Enumeration .1.3.6.1.4.1.485.8.2.5.3 |
mfrapCfgFrLmiInactivityTimeoutTimer used by the unit to determine that an attached device is
not participating in the LMI protocol and that the unit should
attempt to source LMI. This timer also controls the length of
time that the LMI sourcing state machine remains in a particular
state as it attempts to locate an LMI peer.
(0) LMI Sourcing disabled
(2-255) LMI Inactivity timeoutrw INTEGER .1.3.6.1.4.1.485.8.2.5.4 |
mfrapCfgFrLmiKeepaliveTimeoutTimer used by the unit to determine the frequency at which Status
Enquiries are issued during LMI sourcing states where the unit is
emulating a Frame Relay DTE device.
(2-255) length of time between sending enquiries (in seconds)rw INTEGER .1.3.6.1.4.1.485.8.2.5.5 |
mfrapCfgFrAddrResModeEnable ARP (2), INARP (3), both (4), or neither (1).rw Enumeration .1.3.6.1.4.1.485.8.2.5.6 |
mfrapCfgFrAddrResInarpTimerThe frequency at which the unit issues INARP
requests (in seconds) from 5 to 86400 (24 hours).rw INTEGER .1.3.6.1.4.1.485.8.2.5.7 |
mfrapCfgFrLmiFullStatusTimer used by the unit to determine if an LMI Full Status
Report is missing. In the absence of a Full Status report
for the duration defined by this timer, the unit will
declare all DLCI's status INACTIVE and begin logging
down time. Data passage is not interfered with.
(0) Full Status Timer is disabled
(20-3600) Full Status Report Timeout in seconds.rw INTEGER .1.3.6.1.4.1.485.8.2.5.8 |
mfrapCfgFrAddrResDlcisAddress Resolution Dlcis determines which dlcis are
used for address resolution. Multiple DLCI support
only applies to piggyback mode; in other management
modes, only the configured default dlci is used
(1) Support the configured Address Resolution protocol(s)
out both ports on the single configured default DLCI
only (CfgFrDLCIValue).
(2) Support the configured Address Resolution protocol(s)
out both ports on all active DLCIs (per LMI).
(3) Support the configured Address Resolution protocol(s)
out the WAN on all active DLCIs (per LMI) and out the
DTE on only the single default DLCI (CfgFrDLCIValue).
(4) Support the configured Address Resolution protocol(s)
out the DTE on all active DLCIs (per LMI) and out the
WAN on only the single default DLCI (CfgFrDLCIValue).rw Enumeration .1.3.6.1.4.1.485.8.2.5.9 |
mfrapCfgVnipTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.2.6 |
mfrapCfgVnipModeThis setting configures the unit for VNIP topology support on
a per-interface basis. Establishing a VNIP topology is a
fundamental prerequisite to applying the VNIP feature set which
includes PVC-based delay measurement, diagnostics, and congestion
monitoring. With VNIP enabled on an interface the unit
will attempt to locate VNIP peers out that port. As peers are
discovered and logged the unit will report the topology it has
learned on its opposite interface. If VNIP is inactive on one
interface it will not engage in any VNIP dialog; however it will
continue to listen for topology messages on the inactive interface
and will reflect these messages out the opposite interface if VNIP
is enabled. With VNIP inactive on both interfaces the unit will
transparently pass all VNIP messages. The topology database includes
ip addresses, DLCI values, and the number of VNIP hops in between.
(1) Topology Inactive: VNIP messages pass through unit
(2) Topology Enabled on DTE only: unit logs VNIP peers seen
out the DTE interface. Unit listens for topology reports
from the WAN but doesn't generate any towards the WAN. Will
report learned WAN topology towards the DTE.
(3) Topology Enabled on WAN only: unit logs VNIP peers seen
out the WAN interface. Unit listens for topology reports
from the DTE but doesn't generate any towards the DTE. Will
report learned DTE topology towards the WAN.
(4) Topolgy Enabled on Both DTE and WAN: Unit logs VNIP peers
seen out both interfaces and generates DTE topolgy reports
towards the WAN and vice versa.rw Enumeration .1.3.6.1.4.1.485.8.2.6.1 |
mfrapCfgVnipInitTimerThe frequency of hello messages sent
during initialization in seconds from
5 seconds to 86400 seconds (24 hours).rw INTEGER .1.3.6.1.4.1.485.8.2.6.2 |
mfrapCfgVnipKeepAliveTimerThis is the frequency that topology reports are issued out
any interface that has VNIP enabled. Once a Hello exchange
occurs, the unit will periodically issue a VNIP message which
reflects the topology it has learned on the opposite interface.
This Keep Alive timer must be less than any peer unit's Inactivity
timer.
(5-86400) VNIP Topology Update frequency (in seconds)rw INTEGER .1.3.6.1.4.1.485.8.2.6.3 |
mfrapCfgVnipInactivityTimerThe length of time to wait before dropping a VNIP
peer from the database and attempting tp reestablish
communications by issuing the VNIP Hello message. If
this timer expires then the entire topology database
is reset. The Inactivity timers of any unit participating
in a VNIP topology must be greater than the highest Keep
Alive timer in the topology.
(5- 86400) VNIP Hello frequency (in seconds)rw INTEGER .1.3.6.1.4.1.485.8.2.6.4 |
mfrapCfgVnipTransitDelayFrequencyTransit Delay measurements may be enabled between any DLCI
peers that have been logged through the topology protocol.
Delay messages are issued at this frequency and results are
recorded. Transit delay measures the round-trip network
delay between two VNIP peers (internal unit latencies are
not part of the measurement). Traps may be optionally generated
if a delay threshold is exceeded.
(15-86400): Transit Delay message frequency (in seconds)rw INTEGER .1.3.6.1.4.1.485.8.2.6.5 |
mfrapCfgTransitDelayTableThe table defining the transit delay measurement profile for
each of the learned VNIP peers. As peers are located and
logged into the topology database, a default transit delay
profile is assumed. The default is to enable transit delay
to all hops located out the interface. A DLCI's transit
delay profile cannot be modified unless the DLCI has been
discovered through the VNIP topology protocol. SEQUENCE OF MfrapCfgTransitDelayEntry .1.3.6.1.4.1.485.8.2.6.20 |
mfrapCfgTransitDelayEntryA VNIP Transit Delay configuration entry for a particular
DLCI on a particular interface. A DLCI's transit delay
profile cannot be modified unless the DLCI has been
discovered through the VNIP topology protocol MfrapCfgTransitDelayEntry .1.3.6.1.4.1.485.8.2.6.20.1 |
mfrapCfgTransitDelayInterfaceThis is the interface being configured for VNIP Transit
Delay. If topology is enabled, each interface will contain
a database of VNIP peers organized by DLCI value and
Number of Hops.
(1) DTE Interface
(2) DDS Interfacerw Enumeration .1.3.6.1.4.1.485.8.2.6.20.1.1 |
mfrapCfgTransitDelayDlciValueThis is the DLCI being configured for VNIP Transit
Delay. If topology is enabled, each interface will contain
a database of VNIP peers organized by DLCI value and
Number of Hops.rw INTEGER .1.3.6.1.4.1.485.8.2.6.20.1.2 |
mfrapCfgTransitDelayNumHopsVNIP topolgy may include multiple units on a given
DLCI/interface. The topology logs the number of
intermediate VNIP peers between units (Hops). This
setting determines which peers on a DLCI are participating
in delay measurements.
(0) All hops
(1-254) individually addressable delay measurement
between any two peers.
(255) Furthest hop onlyrw INTEGER .1.3.6.1.4.1.485.8.2.6.20.1.4 |
mfrapCfgTransitDelayRcvSummaryCancelControls the Receive Summary Cancellation feature of VNIP
Transit Delay on this interface/DLCI. Every Transit Delay
measurement exchange includes a follow-up message from the
initiator with the delay results. If RSC is enabled, a unit
will log results based upon this summary message and will
not issue its next scheduled delay measurement. With RSC
disabled, the unit will not use the summary message and
will always issue its regularly scheduled message based on
the delay frequency timer. The purpose of this feature is to
reduce traffic introduced by VNIP. In a typical peer-to-peer
transit delay measurement where both ends are concurrently
conducting transit delay measurements it's recommended that
one end have RSC enabled and one end disabled.rw Enumeration .1.3.6.1.4.1.485.8.2.6.20.1.5 |
mfrapCfgTransitDelayThresholdSpecifies a transit delay threshold for this DLCI/interface.
When the transit delay exceeds the threshold, a TRAP is sent.
The threshold may be set from one millisecond to 24 hours.
A value of 0 will prevent a TRAP from being sent.
(0): Transit delay threshold trap disabled for this DLCI/interface
(1-86400000): delay threshhold. Any delay measurements exceeding
this result will generate a trap.rw INTEGER .1.3.6.1.4.1.485.8.2.6.20.1.6 |
mfrapCfgTDDeleteTableThe table allows the user to disable transit delay
measurements for a specific DLCI on a particular
interface. SEQUENCE OF MfrapCfgTDDeleteEntry .1.3.6.1.4.1.485.8.2.6.21 |
mfrapCfgTDDeleteEntryDisables VNIP Transit Delay for a particular
interface and DLCI. MfrapCfgTDDeleteEntry .1.3.6.1.4.1.485.8.2.6.21.1 |
mfrapCfgTDDeleteInterfaceTransit delay can be disabled for a given DLCI on
either interface. This indexes the interface.
Setting this index and the associated DLCI index
will disable transit delay on that combination. Enumeration .1.3.6.1.4.1.485.8.2.6.21.1.1 |
mfrapCfgTDDeleteDlciValueTransit delay can be disabled for a given DLCI on
either interface. This indexes the DLCI. Setting
this index and the associated interface index will
disable transit delay on that combination.rw INTEGER .1.3.6.1.4.1.485.8.2.6.21.1.2 |
mfrapCfgTransitDelayTableClearThe mfrapCfgTransitDelayTable is cleared.
(1) clear the tablerw Enumeration .1.3.6.1.4.1.485.8.2.6.22 |
mfrapCfgFrPerf OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.2.7 |
mfrapCfgFrPerfDlciNamesTableThis table allows the user to configure DLCI
specific parameters such as Names, CIR, and EIR.
Additionally, any DLCIs configured with these
parameters will be added into the Short Term
statistics database next time its cleared. SEQUENCE OF MfrapCfgFrPerfDlciNamesEntry .1.3.6.1.4.1.485.8.2.7.1 |
mfrapCfgFrPerfDlciNamesEntryA table entry indexed by DLCI, containing
a DLCI, a DLCI name, a CIR, and how the
CIR value was obtained. MfrapCfgFrPerfDlciNamesEntry .1.3.6.1.4.1.485.8.2.7.1.1 |
mfrapCfgFrPerfDlciNamesDlciValueA DLCI selected for customized configuration and to
be added to short term statistics collection (if it
wasn't already there).rw INTEGER .1.3.6.1.4.1.485.8.2.7.1.1.1 |
mfrapCfgFrPerfDlciNamesDlciNameA user-specifiable name for an individual DLCI.rw DisplayString .1.3.6.1.4.1.485.8.2.7.1.1.2 |
mfrapCfgFrPerfDlciNamesCirValueThe CIR value for an individual DLCI. This
value is used in the calculation utilization
as a percentage of CIR. If the CIR is reported
in the LMI message then the reported value will
override this configured entry. In the absence
of LMI CIR and a configured CIR, the unit will
assume that the CIR is the DTE Line Rate.rw INTEGER .1.3.6.1.4.1.485.8.2.7.1.1.3 |
mfrapCfgFrPerfDlciNamesCirTypeThe source of the CIR value for this DLCI.
If CIR for a DLCI is part of the LMI message
then this LMI supplied CIR will override any
defined CIR. If CIR is not part of LMI and
has not been explicitly defined by the user
it will default to the DTE Line Rate.
(1) CIR reported in LMI Full Status message
(2) CIR configured by user
(3) CIR defaulted to DTE Line Ratero Enumeration .1.3.6.1.4.1.485.8.2.7.1.1.4 |
mfrapCfgFrPerfDlciNamesUtilThresholdThe threshold for generating a utilization
threshold trap as a percentage of the CIR.
If the utilization percentage is above this
threshold for more than
mfrapCfgFrPerfDlciUtilThreshold number of
mfrapCfgFrPerfTimersSTInterval's a
mfrapPvc(Rx/Tx)UtilizationExceeded trap
will be issued. If the If the utilization
percentage falls below this threshold for
more than mfrapCfgFrPerfDlciUtilThreshold
number of mfrapCfgFrPerfTimersSTInterval's a
mfrapPvc(Rx/Tx)UtilizationExceeded trap
will be issued.rw INTEGER .1.3.6.1.4.1.485.8.2.7.1.1.5 |
mfrapCfgFrPerfDlciNamesEirValueThe EIR value for an individual DLCI. In the
absence of a configured EIR, the unit will
assume that the EIR is the DTE Line Rate.rw INTEGER .1.3.6.1.4.1.485.8.2.7.1.1.6 |
mfrapCfgFrPerfDlciNamesDeleteSetting this object with a specific DLCI value
will remove the DLCI from the DLCI-specific
parameters database.rw INTEGER .1.3.6.1.4.1.485.8.2.7.2 |
mfrapCfgFrPerfTimers OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.2.7.3 |
mfrapCfgFrPerfTimersSTIntervalShort term statistics maintain cumulative counts, and
counts for the current and previous short term windows.
This value is the window size for the short term statistics
intervals.
(3-60): short term statistics collection intervalrw INTEGER .1.3.6.1.4.1.485.8.2.7.3.1 |
mfrapCfgFrPerfTimersLTIntervalLong term statistics maintain 96 contiguous intervals
of configurable protocol per DLCI statistics. This value
is the window size of each interval. Adjusting this value
will change the overall length of time that the 96 intervals
will span.
(4-3600): long term statsistics collection intervalrw INTEGER .1.3.6.1.4.1.485.8.2.7.3.2 |
mfrapCfgFrPerfUserProtocolsTableThis table allows the user to select TCP/UDP ports
for statistics collection. Tx and Rx byte counts
will collected on the specified ports. These ports
are selectable as protocols in the long term
statistics filter and are displayed with the other
protocols in the short term statistics. SEQUENCE OF MfrapCfgFrPerfUserProtocolsEntry .1.3.6.1.4.1.485.8.2.7.4 |
mfrapCfgFrPerfUserProtocolsEntryAn index and TCP/UDP port number pair. MfrapCfgFrPerfUserProtocolsEntry .1.3.6.1.4.1.485.8.2.7.4.1 |
mfrapCfgFrPerfUserProtocolsIndexAn index. Beginning with index 1, the range is defined
in SysNumUserProtocolsro INTEGER .1.3.6.1.4.1.485.8.2.7.4.1.1 |
mfrapCfgFrPerfUserProtocolsPortNumTx and Rx byte counts will be collected on
the user-specifiable TCP/UDP port number.
(0) port not defined
(1-65535): IP TCP/UDP protocol port number.rw INTEGER .1.3.6.1.4.1.485.8.2.7.4.1.2 |
mfrapCfgFrPerfLTDlciFilterTableLong term statistics can only be collected
on a limited number of DLCIs. The value of
SysLTFNumDlcis defines the maximum number of
DLCIs that can be included in the Long Term
Statistics. Once one or more DLCIs are added
to Long Term Stats, the user may assign a
set of protocols that will be monitored across
all of the Long Term DLCIs. SEQUENCE OF MfrapCfgFrPerfLTDlciFilterEntry .1.3.6.1.4.1.485.8.2.7.5 |
mfrapCfgFrPerfLTDlciFilterEntryAn index and DLCI number pair. MfrapCfgFrPerfLTDlciFilterEntry .1.3.6.1.4.1.485.8.2.7.5.1 |
mfrapCfgFrPerfLTDlciFilterIndexAn index. Beginning with index 1, the maximum is
defined by the value of SysLTFNumDlcis.ro INTEGER .1.3.6.1.4.1.485.8.2.7.5.1.1 |
mfrapCfgFrPerfLTDlciFilterDlciNumSetting a DLCI value here will add that DLCI into
the Long term statistics database (associated with
its index) and it will be monitored for the protocol
activity defined in the Long Term Protocol filter.rw INTEGER .1.3.6.1.4.1.485.8.2.7.5.1.2 |
mfrapCfgFrPerfLTProtocolFilterTableLong term statistics can only be collected
on a limited number of protocols. The maximum
number of Long Term Protoocls are defined by
SysLTFNumProtocols. This table allows the user to
configure those protocols. SEQUENCE OF MfrapCfgFrPerfLTProtocolFilterEntry .1.3.6.1.4.1.485.8.2.7.6 |
mfrapCfgFrPerfLTProtocolFilterEntryAn index and protocol pair. MfrapCfgFrPerfLTProtocolFilterEntry .1.3.6.1.4.1.485.8.2.7.6.1 |
mfrapCfgFrPerfLTProtocolFilterIndexAn index. Beginning with index 1, the maximum is
defined by the value of SysLTFNumProtocols.ro INTEGER .1.3.6.1.4.1.485.8.2.7.6.1.1 |
mfrapCfgFrPerfLTProtocolFilterProtocolLong term statistics will be collected on
the user-specifiable protocol. Setting a -1
remove the indexed protocol from the filter.rw Enumeration .1.3.6.1.4.1.485.8.2.7.6.1.2 |
mfrapCfgFrPerfDlciDefaultUtilThresholdThe default threshold for generating a
utilization threshold trap as a percentage
of the CIR. This value is used for
mfrapCfgFrPerfDlciNamesUtilThreshold when
a DLCI is first discovered.rw INTEGER .1.3.6.1.4.1.485.8.2.7.7 |
mfrapCfgFrPerfDlciUtilDurationThe number of Short Term Intervals that a
DLCI's utilization as a percentage of CIR
must be above or below the value of
mfrapCfgFrPerfDlciUtilThreshold before a
mfrapPvc(Rx/Tx)UtilizationExceededTrap or
mfrapPvc(Rx/Tx)UtilizationClearedTrap is
issued.rw INTEGER .1.3.6.1.4.1.485.8.2.7.8 |
mfrapCfgFrPerfDlciNamesTableClearClears the smperCfgFrPerfDlciNamesTable
(1) clear the table or (2) clear the table
but don't remove the dlcis from the short
term statistics.rw Enumeration .1.3.6.1.4.1.485.8.2.7.9 |
mfrapCfgFrPerfUserProtocolsTableClearClears the mfrapCfgFrPerfUserProtocolsTable
(1) clear the tablerw Enumeration .1.3.6.1.4.1.485.8.2.7.10 |
mfrapCfgFrPerfLTDlciFilterTableClearClears the mfrapCfgFrPerfLTDlciFilterTable
(1) clear the tablerw Enumeration .1.3.6.1.4.1.485.8.2.7.11 |
mfrapCfgFrPerfLTProtocolFilterTableClearClears the mfrapCfgFrPerfLTProtocolFilterTable
(1) clear the tablerw Enumeration .1.3.6.1.4.1.485.8.2.7.12 |
mfrapCfgFrPerfUnprovDlcisDeleteDelete all unprovisioned and Not-In-LMI dlcis
(1) delete all unprovisionedrw Enumeration .1.3.6.1.4.1.485.8.2.7.13 |
mfrapCfgSecurityTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.2.8 |
mfrapCfgTelnetCliLcdPasswordThe password needed to start a
CLI (Command Line Interface),
Telnet or LCD session.rw DisplayString .1.3.6.1.4.1.485.8.2.8.1 |
mfrapCfgTftpPasswordThe password needed to initiate a TFTP download.rw DisplayString .1.3.6.1.4.1.485.8.2.8.2 |
mfrapCfgCliPasswordOBSOLETE: The Telnet, CLI and LCD passwords
are one and the same. Use the above
mfrapCfgTelnetCliLcdPassword to log into
the CLI (Command Line Interface).rw DisplayString .1.3.6.1.4.1.485.8.2.8.3 |
mfrapCfgLcdPasswordOBSOLETE: The Telnet, CLI and LCD passwords
are one and the same. Use the above
mfrapCfgTelnetCliLcdPassword to log into
the LCD Interface.rw DisplayString .1.3.6.1.4.1.485.8.2.8.4 |
mfrapCfgGetCommunityStringThe community string for doing SNMP GETs. The unit
will respond to GETs that use either this string or
the SET community string. All others will be rejected
and a trap will be generated. String is case sensitive.rw DisplayString .1.3.6.1.4.1.485.8.2.8.5 |
mfrapCfgSetCommunityStringThe community string for doing SNMP SETs. The unit
will reject SETs with any other coimmunity string
and will generate a trap. String is case sensitive.rw DisplayString .1.3.6.1.4.1.485.8.2.8.6 |
mfrapCfgLcdPswdEnableThis selection controls whether a password is
necessary to use the LCD interface.rw Enumeration .1.3.6.1.4.1.485.8.2.8.7 |
mfrapCfgLcdPswdTimeoutOBSOLETE.rw INTEGER .1.3.6.1.4.1.485.8.2.8.8 |
mfrapCfgConnectionTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.2.10 |
mfrapCfgCurrentConnTableRetrieves node's active connections assignments for
display only. To edit connections, use the mfrapCfgDteTable
and/or mfrapCfgEditConnTable. SEQUENCE OF MfrapCfgCurrentConnEntry .1.3.6.1.4.1.485.8.2.10.1 |
mfrapCfgCurrentConnEntryAn entry in the Current Connections Table. MfrapCfgCurrentConnEntry .1.3.6.1.4.1.485.8.2.10.1.1 |
mfrapCfgCurrentConnDestPortIndex to Destination port of interest. M-FRAP
currently only supports the Network port (1) as the
destinationro Enumeration .1.3.6.1.4.1.485.8.2.10.1.1.1 |
mfrapCfgCurrentConnDestDs0DS0 number 1 through 24 corresponding to the destination
port indexro INTEGER .1.3.6.1.4.1.485.8.2.10.1.1.2 |
mfrapCfgCurrentConnSrcPortDS0 assignment for Destination port. After
making any adjustments to the connections, the
mfrapCfgConnUpdateCmd must be sent. Node software
does not permit a port connection to itself.ro Enumeration .1.3.6.1.4.1.485.8.2.10.1.1.3 |
mfrapCfgCurrentConnSrcDs0DS0 number 1 through 24 corresponding to the sourced portro Enumeration .1.3.6.1.4.1.485.8.2.10.1.1.4 |
mfrapCfgCurrentConnTypeDefines the type of traffic being transported.ro Enumeration .1.3.6.1.4.1.485.8.2.10.1.1.5 |
mfrapCfgEditConnections OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.2.10.2 |
mfrapCfgEditConnCopyCurrtoEditFill the edit buffer with the node's current active
connections.rw Enumeration .1.3.6.1.4.1.485.8.2.10.2.1 |
mfrapCfgEditClearEditClear all connections from the edit buffer.rw Enumeration .1.3.6.1.4.1.485.8.2.10.2.2 |
mfrapCfgEditConnTableEdits current DS0 assignment. This table is also updated
by the mfrapCfgDteTable. After making any adjustments
to the connections, the mfrapCfgConnUpdateCmd must be sent. SEQUENCE OF MfrapCfgEditConnEntry .1.3.6.1.4.1.485.8.2.10.2.3 |
mfrapCfgEditConnEntryAn entry in the Edit Connections table. MfrapCfgEditConnEntry .1.3.6.1.4.1.485.8.2.10.2.3.1 |
mfrapCfgEditConnDestPortIndex to destination port of interest. M-FRAP currently
only supports the Network port (1) as the destination.ro Enumeration .1.3.6.1.4.1.485.8.2.10.2.3.1.1 |
mfrapCfgEditConnDestDs0DS0 number 1 through 24 corresponding to the Destination
port indexro INTEGER .1.3.6.1.4.1.485.8.2.10.2.3.1.2 |
mfrapCfgEditConnSrcPortDS0 assignment for indexed destination port. The value
not-connected may not be written; to clear a connection,
use the mfrapCfgEditDisconnect table element. Setting
mfrapCfgEditDisconnect to disconnect will cause this
element to return not-connected for a get.
Currently, M-FRAP will not allow setting this value to 3.
Connections defined by the mfrapCfgDteTable will be reflected in
reads of this object. After making any adjustments to the
connections, the mfrapCfgConnUpdateCmd must be sent. Node
software does not permit connections between a port and itself.rw Enumeration .1.3.6.1.4.1.485.8.2.10.2.3.1.3 |
mfrapCfgEditConnSrcDs0DS0 number 1 through 24 corresponding to the sourced port index.
The value no-connection may not be written. To clear a
connection use the mfrapCfgEditDisconnect table element.
Setting mfrapCfgEditDisconnect to disconnect will cause this
element to return no-connection for a get.rw Enumeration .1.3.6.1.4.1.485.8.2.10.2.3.1.4 |
mfrapCfgEditConnTypeDefines the type of traffic being transported. The value
not-connected may not be written. To clear a connection
use the mfrapCfgEditDisconnect table element. Setting
mfrapCfgEditDisconnect to disconnect will cause this
element to return not-connected for a get.rw Enumeration .1.3.6.1.4.1.485.8.2.10.2.3.1.5 |
mfrapCfgEditDisconnectSetting this object to disconnect will cause the state of
the Src and Type objects for this destination port and ds0
to be set to not-connected. When connections are updated,
the connection between the source and destination will be
terminated.rw Enumeration .1.3.6.1.4.1.485.8.2.10.2.3.1.6 |
mfrapCfgEditLastSetStatusThe status of the last set of an mfrapCfgEditConnTable
object. Invalid-dte-bandwidth is returned if the set
reduces the number of ds0's assigned to a DTE port
to less than the number required for the port's
bandwidth and density. Bandwidth-conflict is returned
if an attempt is made to change the source port without
first disconnecting the existing connection.
Ds0s-not-ascending is returned if the source ds0 being
set is not in ascending order with the other ds0's for
that source port.ro Enumeration .1.3.6.1.4.1.485.8.2.10.2.4 |
mfrapCfgEditConnStatusDisplays the status of the connections in the edit buffer.
This object should be read before setting the
mfrapCfgConnUpdateCmd. Incorrect-dte-bandwidth is returned if
there are not enough DS0's starting with the
mfrapCfgDteConnStartDs0 to accommodate the
mfrapCfgDteConnDs0Required. Incomplete-entry is returned
if the source port, source ds0 and/or connection type has
not been set for a connection (and at least one of them
has been set for that connection). Inconsistent-edit-buffer
is returned if there is an internal inconsistency in the
edit buffer; in this case, an mfrapCfgEditConnCopyCurrtoEdit
or mfrapCfgEditClearEdit set should be performed before
proceeding. Bad-connection-type is returned if the connection
type is not consistent with the source and destination ports.ro Enumeration .1.3.6.1.4.1.485.8.2.10.2.5 |
mfrapCfgConnUpdateCmdUpdates the connections with the edit buffer if the connections
are all valid. The edit buffer is comprised of any changes sent
(set) from the mfrapCfgEditConnTable or the mfrapCfgDteTable.
Note that if changes are made to the mfrapCfgDteTable, the
mfrapCfgConnAutoUpdate object must be set before the
mfrapCfgConnUpdateCmd in order for the changes to take effect.rw Enumeration .1.3.6.1.4.1.485.8.2.10.2.6 |
mfrapCfgDandiTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.2.11 |
mfrapCfgDandiFramingType of Framing on this D&I Line. Check with your service
provider to determine value. D4 is also known as
'SuperFrame', ESF is 'Extended SuperFrame'. ESF provides
enhanced performance monitoring capabilities.rw Enumeration .1.3.6.1.4.1.485.8.2.11.1 |
mfrapCfgDandiLineEncodingD&I interface bipolar encoding scheme. Check with your
service provider to determine value. B8ZS, which inherently
provides ample 'ones-density', is recommended. AMI users
must pay special attention to the 'ones-density' requirements
of the service provider.rw Enumeration .1.3.6.1.4.1.485.8.2.11.2 |
mfrapCfgLockRequest to start configuration download and lock out any
other means of configuring the unit. The integer passed in
represents the time out period in seconds between sets.
A set to this object will fail if the unit is already in a
configuration locked state.rw INTEGER .1.3.6.1.4.1.485.8.2.12 |
mfrapCfgLockIDReturns the IP Address of the management station currently
in control of configuration. A unit that is not in a
configuration locked state will return 0.0.0.0ro IpAddress .1.3.6.1.4.1.485.8.2.13 |
mfrapCfgIDA read of this object returns the Current Configuration ID
string. A write sets the Configuration ID string. The
string contains a starting character to indicate the last
configuration source C = Envisage N = CLI/TELNET L = LCD
S= other SNMP management station and a unique 7 integer
value to differentiate configurations between common sources.
A value of *STARTUP indicates the configuration has been
defaulted. A write will only be accepted from the management
station that has successfully obtained the configuration lockrw DisplayString .1.3.6.1.4.1.485.8.2.14 |
mfrapCfgStatusThe status of a configuration install is reported here.
On startup, a status of success will be reported.
(1) The configuration has been locked and an update or
unlock command has not been received.
(2) An update command has been received and the configuration
has been validated as consistent; .
(3) An update command has been received but the DTE port
datarate is not compatible with the density.
(4) An update command has been received but the number of
channels to be allocated will not fit in the available
channels.
(5) An update command has been received but there is an
error in the configuration that is not a
datarate-density-conflict or bandwidth-allocation-error.
(6) The time between consecutive set requests exceeded the
timeout sent with the tfrapCfgLock command.
(7) The user sent a tfrapCfgUnlock command before a
tfrapCfgUpdate command. This usually means that one
of the sets in the configuration failed.ro Enumeration .1.3.6.1.4.1.485.8.2.15 |
mfrapCfgUnlockThe management station sets this variable to complete
the configuration install process. Un-lock (1) notifies
the agent to remove the lock on configuring the unit
without updating the configuration.rw Enumeration .1.3.6.1.4.1.485.8.2.16 |
mfrapCfgUpdateThe management station sets this variable to complete
the configuration install process. Update (1) notifies
the agent to start the update process within the unit.rw Enumeration .1.3.6.1.4.1.485.8.2.17 |
mfrapDiagnostics OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.3 |
mfrapDiagUnitTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.3.1 |
mfrapDiagUnitLocLoopControls a bi-directional unit loopback. Data
is received from either the DTE or Network interface,
processed, and transmitted back towards the same interface.
When configured for Frame Relay operation the unit
will preserve the LMI path and maintain managed access
during this loopback. In Frame Relay mode, only valid
HDLC frames are looped back (pseudorandom test patterns
will be dropped). Data received on the Drop & Insert
is not affected by this loopback mode.
(1) enable unit loopback
(2) disable unit loopbackrw Enumeration .1.3.6.1.4.1.485.8.3.1.1 |
mfrapDiagUnitResetEnables the operator to remotely cause a software
reset on the unit. Using this command will cause
the unit to terminate all its connections and drop data.
(1) Reset Unit.rw Enumeration .1.3.6.1.4.1.485.8.3.1.2 |
mfrapDiagUnitTimeRemainingThe remaining time on the active loopback
before the loopback times out and disables
itself. The time is in hundredths of seconds
(TimeTicks).ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.485.8.3.1.3 |
mfrapDiagT1Table OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.3.2 |
mfrapDiagT1LocLineLpbkControls local network loopback. All data (including
framing and line errors) received from the WAN,
regardless of format or content, is transmitted back
out to the WAN (line interface loopback) while still
being passed through to the DTE. In Frame Relay
applications the unit will not preserve the LMI path during
this diagnostic and in-band management may not operate.
(1) disable line loopback
(2) enable line loopbackrw Enumeration .1.3.6.1.4.1.485.8.3.2.1 |
mfrapDiagT1LocPylLpbkControls network payload loopback. All data
received from the WAN is terminated, reframed
and sent back towards the WAN. Framing errors
and Line Code Violations are corrected.
Network contact via ESF Facility Data Link is
preserved during this loopback state. All user
data regardless of format or content, is transmitted
back out while all Ones are sent to the DTE. In Frame
Relay applications the unit will not preserve the LMI
path during this diagnostic and in-band management may
not operate.
(1) disable payload loopback
(2) enable payload loopbackrw Enumeration .1.3.6.1.4.1.485.8.3.2.2 |
mfrapDiagT1LocAggrLpbkControls Local Aggregate Loopback. All data
received from the DTE and Drop & Insert ports
is framed, formatted and transmitted towards
the WAN while being looped back towards the
respective port (DTE or Drop & Insert). The
loopback path covers the entire digital data
path within the device. In Frame Relay mode,
only error-free HDLC frames will pass through
the loopback path. Additionally, in Frame Relay
applications the unit will not preserve the LMI
path during this loopback and in-band management
may not operate.
(1) disable local aggregate (digital) loopback
(2) enable local aggregate (digital) loopbackrw Enumeration .1.3.6.1.4.1.485.8.3.2.3 |
mfrapDiagT1RmtLpbkStatusStatus of Remote Loopback commands sent or received on the WAN.
(1) no remote loopbacks are active.
(2) csu loopback from remote - indicates the node is in a Network
Line Loopback state due to the reception of the standard CSU
Loop-up pattern from the WAN.
(3) dsu loopback from remote - indicates the node is in a Network
Line Loopback state due to the reception of the Sync Research
proprietary Loop-up pattern from a remote node.
(4) payload loopback from remote - indicates the node is in a
Payload Loopback state due to the reception of the ESF Facility
Data Link's Loop-up pattern from the network.
(5) csu loopback sent to remote - indicates the node has sent a csu
loop up pattern towards the WAN. A device terminating the WAN's
physical link is expected to enter a Line Loopback. The initating
unit doesn't know if the loopback was accepted by the remote unit.
(6) dsu loopback sent to remote - indicates the node has sent a dsu
loop up pattern to a remote Sync unit out the WAN. A compatible
device detecting this pattern is expected to enter a Line Loopback.
The initating unit doesn't know if the loopback was accepted by
the remote unit.ro Enumeration .1.3.6.1.4.1.485.8.3.2.4 |
mfrapDiagT1RmtLpbkCmdRemote loopback commands are intended to place compatible external
equipment into a loopback state. The initiating unit will maintain
normal data flows during these tests.
(1) csu loop up - commands the node to send a standard in-band
csu loop up pattern towards the WAN. This is a repetetive
framed T1 signal consisting of four 'zeros' followed by one 'one'
persisting for a few seconds in place of all T1 data. A
device terminating the WAN's physical link is expected to enter
a Line Loopback condition upon recognition of this pattern.
The initating unit doesn't know if the command was accepted by
the remote unit.
(2) csu loop down - commands the node to send a standard in-band
csu loop down pattern towards the WAN. This is a repetetive
framed T1 signal consisting of two 'zeros' followed by one 'one'
persisting for a few seconds in place of all T1 data. A
device terminating the WAN's physical link is expected to clear
any Line Loopback condition upon recognition of this pattern.
The initating unit doesn't know if the commad was accepted by
the remote unit.
(3) dsu loop up - commands the node to send a proprietary in-band
dsu loop up pattern towards the WAN. This is a repetetive
framed T1 signal consisting of a pseudorandom pattern persisting
for a few seconds in place of all T1 data. A compatible
device terminating the WAN's physical link is expected to enter
a Line Loopback condition upon recognition of this pattern.
The initating unit doesn't know if the command was accepted by
the remote unit.
(4) dsu loop down - commands the node to send a proprietary in-band
dsu loop down pattern towards the WAN. This is a repetetive
framed T1 signal consisting of a pseudorandom pattern persisting
for a few seconds in place of all T1 data. A compatible
device terminating the WAN's physical link is expected to clear
any Line Loopback condition upon recognition of this pattern.
The initating unit doesn't know if the command was accepted by
the remote unit.rw Enumeration .1.3.6.1.4.1.485.8.3.2.5 |
mfrapDiagT1TimeRemainingThe remaining time on the active loopback before the loopback
times out and automatically clears itself to restore the unit
to normal operation. The time is in hundredths of seconds
(TimeTicks).ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.485.8.3.2.6 |
mfrapDiagDteTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.3.3 |
mfrapDiagDteSigRTSStatus of the Request to Send (RTS) signal from the DTE port.
(1) RTS Active
(2) RTS Inactivero Enumeration .1.3.6.1.4.1.485.8.3.3.1 |
mfrapDiagDteSigDTRStatus of the Data Terminal Ready (DTR) signal from the DTE port.
(1) DTR Active
(2) DTR Inactivero Enumeration .1.3.6.1.4.1.485.8.3.3.2 |
mfrapDiagDteLclLpbkControls the DTE loopback state. This is a
bi-directional loopback state where both the
DTE and WAN ports are placed in line loopback.
All data received on each interface is sent back
out the respective interface regardless of format
or content. In Frame Relay applications the unit
will not preserve the LMI path during this diagnostic
and in-band management will not operate.
(1) enable payload loopback
(2) disable payload loopbackrw Enumeration .1.3.6.1.4.1.485.8.3.3.3 |
mfrapDiagDteV54LpbkThis reports the status of any local V54 testing initiated by
a remote unit. Remote V54 loopback commands are intended to place
this unit into a loopback state. The initiating unit will maintain
normal data flows during these tests.
(1) V54 loop up received - indicates the node has received a standard
in-band loop up pattern from the WAN per ITU V.54. This is a
framed T1 signal consisting of a pseudorandom signal in place of
all user data (that is only in the DS0s assigned to the DTE). This
unit has entered a bi-directional DTE Loopback condition.
(2) V54 loop down received - indicates the node has received a standard
in-band loop down pattern from the WAN per ITU V.54. This is a
framed T1 signal consisting of a pseudorandom signal in place of
all user data (that is only in the DS0s assigned to the DTE). This
unit has cleared the bi-directional DTE Loopback condition.ro Enumeration .1.3.6.1.4.1.485.8.3.3.4 |
mfrapDiagDteRmtV54LpbkRemote V54 loopback commands are intended to place compatible
external equipment into a loopback state. The initiating unit
will maintain normal data flows during these tests.
(3) Transmit V54 loop up - commands the node to send a standard
in-band loop up pattern towards the WAN per ITU V.54. This is a
framed T1 signal consisting of a pseudorandom signal in place of
all user data (that is only in the DS0s assigned to the DTE). A
device terminating the fractional T1 data is expected to enter
a bi-directional DTE Loopback condition upon recognition of this
pattern. The initating unit doesn't know if the command was accepted
by the remote unit. This pattern will not traverse a typical frame
relay network and is designed for circuit-switched diagnostics.
(4) Transmit V54 loop down - commands the node to send a standard
in-band loop down pattern towards the WAN per ITU V.54. This is a
framed T1 signal consisting of a pseudorandom signal in place of
all user data (that is only in the DS0s assigned to the DTE). A
device terminating the fractional T1 data is expected to clear
a bi-directional DTE Loopback condition upon recognition of this
pattern. The initating unit doesn't know if the command was accepted
by the remote unit.rw Enumeration .1.3.6.1.4.1.485.8.3.3.5 |
mfrapDiagDteTimeRemainingThe remaining time on the active loopback
before the loopback times out. The time is
in hundredths of seconds (TimeTicks).ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.485.8.3.3.13 |
mfrapDiagBertTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.3.5 |
mfrapDiagBertStateThe unit is capable of sending a pseudorandom test pattern
(511 or QRSS) out the WAN and monitoring the WAN received
data for the same pattern. The BERT pattern may be selected
to occupy the full T1 payload, only the bandwidth
allocated to the DTE, only the bandwidth allocated to the
Drop & Insert or only the bandwidth allocated to the DTE
and the Drop & Insert (fractional T1). When a unit is sending
this BERT, the receiver will monitor and characterize the
incoming signal for the same BERT pattern. In Frame Relay
applications the unit will not preserve the LMI path during
this diagnostic and in-band management may not operate.
This test may be ineffective in certain frame relay environments
as pseudorandom data lacks appropriate framing. Refer to
VLOOP and VBERT for PVC-based error-rate testing in a live frame
relay network.
(1) Start a BERT test on full T1 - replaces entire T1 payload with
the configured BERT pattern while monitoring the full T1 bandwidth
(1.536M) for the presence of the BERT pattern.
(2) Start a BERT test on the DTE bandwidth - replaces only the portion
of the T1 payload that has been allocated to the DTE with the
configured BERT pattern while monitoring the same T1 bandwidth
(DTE Data Rate) for the presence of the BERT pattern.
(3) Stop a BERT test.
(4) Inject a single bit error into the outgoing pattern.
(5) Clear current BERT results.
(6) Starts a BERT test on the Drop & Insert bandwidth - replaces
only the portion of the T1 payload that has been allocated to
the Drop & Insert with the configured BERT pattern while
monitoring the same T1 bandwidth (D&I DS0's) for the presence
of the BERT pattern.
(7) Starts a BERT test on the DTE & D&I bandwidth (fractional T1) -
replaces only the portion of the T1 payload that has been
allocated to the DTE or the Drop & Insert with the configured
BERT pattern while monitoring the same T1 bandwidth for the
presence of the BERT pattern.rw Enumeration .1.3.6.1.4.1.485.8.3.5.1 |
mfrapDiagBertStatusDisplays the current BERT test sync status.
(1) BERT is not running
(2) BERT is running but is not in sync
(3) BERT is running and has detected a received BERTro Enumeration .1.3.6.1.4.1.485.8.3.5.2 |
mfrapDiagBertErrorsDisplays the number of errors detected in Bert Test.ro Counter .1.3.6.1.4.1.485.8.3.5.3 |
mfrapDiagBertErrSecDisplays the number of seconds containing 1 or more errors
in BERT Test.ro Counter .1.3.6.1.4.1.485.8.3.5.4 |
mfrapDiagBertTimeElapsElapsed time since BERT test was started or cleared.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.485.8.3.5.5 |
mfrapDiagBertResyncsDisplays the number of times BERT test has synched up
on the pattern. The BERT will attempt to resynchronize
in response to excessive errors. A running count here
indicates that a clean BERT is not being received.ro Counter .1.3.6.1.4.1.485.8.3.5.6 |
mfrapDiagBertPatternThe type of pseudorandom BERT pattern used.
(1) 511: 9-bit pseudorandom pattern
(2) QRSS: 20-bit pseudorandom pattern with
no more than 14 consecutive zerosrw Enumeration .1.3.6.1.4.1.485.8.3.5.7 |
mfrapDiagVnipTableTable of Diagnostics performed with the VNIP protocol SEQUENCE OF MfrapDiagVnipEntry .1.3.6.1.4.1.485.8.3.6 |
mfrapDiagVnipEntryVNIP VLOOP and VBERT diagnostic profile. Initiating
these tests require an established and stable VNIP topology
on an interface. Once the topology is in place, the user
can execute a PVC-based diagnostic between this unit and
any indexed entry in the topology table. The index into the
topology table for a particular interface is required. MfrapDiagVnipEntry .1.3.6.1.4.1.485.8.3.6.1 |
mfrapDiagVnipInterfaceThe interface out which a PVC-based VNIP diagnostic
will be run. This must be an interface with a valid
and stable VNIP topology for a VNIP Diagnostic.rw Enumeration .1.3.6.1.4.1.485.8.3.6.1.1 |
mfrapDiagVnipIndexThe index to the external VNIP peer as presented by the VNIP
topology database for the given interface. Refer to
VnipTopologyTable to determine the index of the remote peer.rw INTEGER .1.3.6.1.4.1.485.8.3.6.1.2 |
mfrapDiagVnipDlciThis is the DLCI value for the given interface/index
combination. This comes from the VniptTopologyTable.ro INTEGER .1.3.6.1.4.1.485.8.3.6.1.3 |
mfrapDiagVnipIpAddrThis is the ip address for the given interface/index
combination. This comes from the VniptTopologyTable.ro IpAddress .1.3.6.1.4.1.485.8.3.6.1.4 |
mfrapDiagVLOOPControls execution of the Vnip Logical Loopback (VLOOP) test.
VLOOP is designed as an intrusive test and customer data
on the DLCI-under-test will be discarded. The VLOOP test includes
a timed VBERT test and is run using the profile configured within
this table.
(1) start VLOOP test
(2) stop VLOOP test (override VBERT test duration)rw Enumeration .1.3.6.1.4.1.485.8.3.6.1.5 |
mfrapDiagVBERTControls execution of the Vnip Virtual Bit Eror Rate (VBERT) test.
VBERT is designed to be a non-intrusive test and will attempt to
statistically multiplex VBERT test data and customer data on the
DLCI-under-test. However, VBERT data is given priority over customer
data when the selected VBERT volume causes internal congestion.
The test is run using the profile configured within this table.
(1) start test
(2) stop test (override VBERT test duration)rw Enumeration .1.3.6.1.4.1.485.8.3.6.1.6 |
mfrapDiagVBERTRateSpecifies the throughput bit rate applied by VBERT or
VLOOP to the DLCI-under-test. For DTE Rates or configured
CIR up to 64K the maximum VBERT rate is either the DTE data
rate or 110% of CIR (which ever is less). For DTE Rates or
configured CIR greater than 64K, the maximum VBERT rate is
75% of the DTE data rate or 110% of CIR (which ever is less).
Note that selecting rates that approach line rate will impact
neighboring PVCs.
(8000-1152000): VBERT/VLOOP data rate (in bits per second).rw INTEGER .1.3.6.1.4.1.485.8.3.6.1.7 |
mfrapDiagVBERTSizeSpecifies the size of framed data that will be used
during the VBERT test, measured in Bytes.
(64) 64-byte frames
(128) 128-byte frames
(256) 256-byte frames
(512) 512-byte frames
(1024) 1024-byte frames
(2048) 2048-byte framesrw INTEGER .1.3.6.1.4.1.485.8.3.6.1.8 |
mfrapDiagVBERTPktPercentSpecifies percentage of VBERT packets that will have the
Frame Relay Discard Eligibility bit set. Frames with this
bit set may be more likley to get dropped in a congested
network.
(0) 0% of the test frames are marked discard eligible
(25) 25% of the test frames are marked discard eligible
(50) 50% of the test frames are marked discard eligible
(75) 75% of the test frames are marked discard eligible
(100) 100% of the test frames are marked discard eligiblerw Enumeration .1.3.6.1.4.1.485.8.3.6.1.9 |
mfrapDiagVBERTTestPeriodSpecifies the duration of a VBERT test. Note that VBERT is
subjected to the unit's Loopback Timer and will be terminated
by whichever timer expires first.
(10-1440): VBERT time duration in secondsrw INTEGER .1.3.6.1.4.1.485.8.3.6.1.10 |
mfrapDiagDandiTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.3.8 |
mfrapDiagDandiLocLineLpbkLocal Line Loopback on the Drop & Insert port. Data and
framing received at the D & I port is transmitted back
out the D & I port
(1) disable line loopback
(2) enable line loopbackrw Enumeration .1.3.6.1.4.1.485.8.3.8.1 |
mfrapDiagDandiLocPylLpbkLocal Payload Loopback on the Drop & Insert port. Data
(NOT framing) received at the T1 port is looped back
at the D&I port and reframed and transmitted back out
the T1 port.
(1) disable line loopback
(2) enable line loopbackrw Enumeration .1.3.6.1.4.1.485.8.3.8.2 |
mfrapDiagDandiTimeRemainingThe remaining time on the active loopback
before the loopback times out. The time is
in hundredths of seconds (TimeTicks).ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.485.8.3.8.6 |
mfrapStatus OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.4 |
mfrapStatusT1Table OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.4.1 |
mfrapStatusT1ModeStatus of allocation of T1 bandwidth to the DTE port data.
(1) no connections - indicates the DTE port has no connections
to the WAN.
(2) Active - indicates DTE data rate has been assigned T1 DS0s
and is in a normal data mode.
(3) Test - indicates DTE data rate has been assigned T1 DS0s
but is in a diagnostic condition.ro Enumeration .1.3.6.1.4.1.485.8.4.1.4 |
mfrapStatusT1StatusStatus of the signal received from the WAN
(1) In Sync - unit has detected a properly framed T1 signal
and is not experiencing any error conditions.
(2) In Sync with Errors - unit has detected a properly framed
T1 signal but is experiencing some error conditions. Refer to
T1 current performance results for details.
(3) Signal Detected without Frame Sync - while a signal is present
from the WAN it does not contain the framing pattern defined for
this unit. This could be either incorrectly configured T1 Frame
type or the presence of an alarm condition on the WAN.
(4) No Carrier - there is no signal detected from the WAN.
(5) Not Applicable.ro Enumeration .1.3.6.1.4.1.485.8.4.1.5 |
mfrapStatusT1AlarmsAlarms present at the T1 port.
(1) No alarm conditions present.
(2) Red Alarm Declared - Unit has experienced loss of frame
synchronization with the signal received from the WAN
for an extended time and is reporting an alarm condition
that severely impairs normal operation. During this Red
Alarm condition the unit will transmit Yellow alarm back
to the WAN. If this condition persists consult your
service provider.
(3) Yellow ALarm Detected - Unit is receiving a yellow alarm
indication from the wide area network. Detection of yellow
alarm implies that the attached device is in a red alarm
conditon. Red alarm is declared due to the extended absence
of a properly framed signal. If this condition persists
consult your service provider.
(4) Unframe All Ones Detected - Unit is receiving unframed all
ones from the wide area network (AIS, blue alarm). Detection
of AIS implies that the attached device is reporting
an alarm condition from an upstream device. If
this condition persists consult your service provider.ro Enumeration .1.3.6.1.4.1.485.8.4.1.6 |
mfrapVnipTopologyTableVNIP topology is a feature that, for each interface, maps all
compatible VNIP peers, their DLCI value, ip address and relative
location. The topology is a fundamental prerequisite to applying
the VNIP feature set which includes PVC-based delay measurement,
diagnostics, and congestion monitoring. With VNIP enabled on an
interface the unit will attempt to locate VNIP peers out that port.
As peers are discovered and logged the unit will report the topology
it has learned on its opposite interface. If VNIP is inactive on
one interface it will not engage in any VNIP dialog; however it
will continue to listen for topology messages on the inactive
interface and will reflect these messages out the opposite interface
if VNIP is enabled. With VNIP inactive on both interfaces the unit
will transparently pass all VNIP messages. The topology database
includes the interface, local DLCI value, remote peer DLCI value,
remote peer ip address, and the number of VNIP hops in between.
This table also reports the status of other VNIP features as well. SEQUENCE OF MfrapVnipTopologyEntry .1.3.6.1.4.1.485.8.4.2 |
mfrapVnipTopologyEntryThe DLCI, IP address, and number of hops
for a particular peer, discovered off of
an interface (DTE or T1). MfrapVnipTopologyEntry .1.3.6.1.4.1.485.8.4.2.1 |
mfrapVnipTopologyInterfaceThe interface off of which the peer was
discovered. Topology is discovered by
sending VNIP messages out each interface.
Units discovered via a particular interface
are kept in a list associated with that
interface.
(1) VNIP peers and status out DTE interface
(2) VNIP peers and status out WAN interfacero Enumeration .1.3.6.1.4.1.485.8.4.2.1.1 |
mfrapVnipTopologyIndexThe number of this discovered peer in the list
of nodes for this interface. For each interface,
the nodes are numbered 1 through n. This index
is required when disabling or enabling VBERT/VLOOP
to a particular peer.ro INTEGER .1.3.6.1.4.1.485.8.4.2.1.2 |
mfrapVnipTopologyDlciThe DLCI of the discovered neighboring peer.
This may be different from the local DLCI.ro INTEGER .1.3.6.1.4.1.485.8.4.2.1.3 |
mfrapVnipTopologyIpAddrThe IP address for the discovered peer.ro IpAddress .1.3.6.1.4.1.485.8.4.2.1.4 |
mfrapVnipTopologyNumHopsThe discovered peer is this number of hops away.
Each hop is a VNIP peer.ro INTEGER .1.3.6.1.4.1.485.8.4.2.1.5 |
mfrapVnipTopologyLocalDlciThe DLCI of this node over which the neighboring peer
was discovered.ro INTEGER .1.3.6.1.4.1.485.8.4.2.1.6 |
mfrapVnipTopoTDNumSamplesThe number of transit delay samples collected.ro Counter .1.3.6.1.4.1.485.8.4.2.1.10 |
mfrapVnipTopoTDAvgDelayThe average transit delay between this
unit and the remote peer (in milliseconds).ro Counter .1.3.6.1.4.1.485.8.4.2.1.11 |
mfrapVnipTopoTDMaxDelayThe maximum transit delay between this
node and the remote peer (in milliseconds).ro Counter .1.3.6.1.4.1.485.8.4.2.1.12 |
mfrapVnipTopoTDMinDelayThe minimum transit delay between this
node and the remote peer (in milliseconds).ro Counter .1.3.6.1.4.1.485.8.4.2.1.13 |
mfrapVnipTopoTDLastDelayThe most recent transit delay measured between
this node and the remote peer (in milliseconds).ro Counter .1.3.6.1.4.1.485.8.4.2.1.14 |
mfrapVnipTopoVLOOPStatusThis selection displays the status of the VNIP PVC
Loopback for this entry. This loopback is initiated
by the remote node through the VLOOP utility, causing
this node to loop data back to the remote node.
(1) Virtual Loopback path present on this PVC due to
command received from remote unit. All data received
on this DLCI will be looped back out the same interface.
(2) No active VLOOP test on thisro Enumeration .1.3.6.1.4.1.485.8.4.2.1.15 |
mfrapVnipTopoVBERTStatusDisplays the current status of the VBERT/VLOOP test.
(1) Off: no test has run or the entry has been cleared
(2) Testing: the entry is generating VBERT test frames
(3) Test Failed: the request for a test on this entry failed
(4) Test Completed: a test has run and is finished results
are complete
(5) In Test: the entry is on the receiving end of VBERT packetsro Enumeration .1.3.6.1.4.1.485.8.4.2.1.16 |
mfrapVnipTopoVBertTxDESetFramesDisplays the number of Frames transmitted during VBERT Test that
had the Discard Eligibility indicator bit set.ro Counter .1.3.6.1.4.1.485.8.4.2.1.17 |
mfrapVnipTopoVBertRxDESetFramesDisplays the number of Frames received during VBERT Test that
had the Discard Eligibility indicator bit set.ro Counter .1.3.6.1.4.1.485.8.4.2.1.18 |
mfrapVnipTopoVBertTxDEClrFramesDisplays the number of Frames transmitted during VBERT Test that
had the Discard Eligibility indicator bit cleared.ro Counter .1.3.6.1.4.1.485.8.4.2.1.19 |
mfrapVnipTopoVBertRxDEClrFramesDisplays the number of Frames received during VBERT Test that
had the Discard Eligibility indicator bit cleared.ro Counter .1.3.6.1.4.1.485.8.4.2.1.20 |
mfrapVnipTopoVBertTransitDelayMaxThe maximum transit delay between this node and the
remote peer during the VBERT test. This delay measurement
will include internal device latencies. This result may
differ from the VNIP transit delay measurement which accounts
for internal latencies.ro Counter .1.3.6.1.4.1.485.8.4.2.1.21 |
mfrapVnipTopoVBertTransitDelayAvgThe average transit delay between this node and the remote
peer during the VBERT test. This delay measurement
will include internal device latencies. This result may
differ from the VNIP transit delay measurement which accounts
for internal latenciesro Counter .1.3.6.1.4.1.485.8.4.2.1.22 |
mfrapVnipTopoVBertTimeElapseElapsed time since VBERT/VLOOP test was started or cleared
(in seconds).ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.485.8.4.2.1.23 |
mfrapVnipTopoVBertPerUtilCIRThe calculated percent of CIR utilization during a VBERT test,
this value is only valid after a test is complete not during.ro INTEGER .1.3.6.1.4.1.485.8.4.2.1.24 |
mfrapVnipTopoVBertPerUtilEIRThe calculated percent of EIR utilization during a VBERT test,
this value is only valid after a test is complete not during.ro INTEGER .1.3.6.1.4.1.485.8.4.2.1.25 |
mfrapStatusMgmtTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.4.3 |
mfrapStatusMgmtChannelThis is the method in which the unit is configured for
SNMP management access.
(1) None: SNMP management disabled
(2) SLIP: out-of-band management via asynchronous Serial Line IP
(3) Private DLCI: in-band management using a private DLCI that
is dedicated solely to this unit's management.
(4) Piggyback DLCI: in-band management using any DLCI optionally
multiplexing both management and user data.ro Enumeration .1.3.6.1.4.1.485.8.4.3.1 |
mfrapStatusMgmtInterfaceThis is the port(s) on which the management traffic will appear.
(1) Async Maintenance(Comm)/Console port - SLIP mode
(2) Local DTE interface: unit is configured for Private Local
DLCI mode
(3) Remote WAN Interface: unit is confiogured for Private Remote
DLCI mode
(4) DTE and WAN Interfaces: unit is configured for either Piggyback
Bidirectional mode.ro Enumeration .1.3.6.1.4.1.485.8.4.3.2 |
mfrapStatusMgmtInterfaceStatusThis is the status of the port(s) on which
the management traffic will appear.
(1) Active: port or DLCI is configured and status is okay
(2) Inactive: port or DLCI is declared out of service
(3) Alarm: port or DLCI is experiencing an alarm condition that may
interefere with management accessro Enumeration .1.3.6.1.4.1.485.8.4.3.3 |
mfrapStatusMgmtDefaultDLCINoThis is the DLCI for the PVC that is defined for the
Management port. All traffic using this DLCI in the Frame
Replay packet will be destined for the InBand Management task.ro INTEGER .1.3.6.1.4.1.485.8.4.3.4 |
mfrapStatusMgmtDefaultDLCIStatusThis is the status of the default management DLCI.
(1) not applicable: SLIP mode or management is disabled
(2) DLCI Active: default DLCI is active in the LMI full
status response.
(3) DLCI Inactive: default DLCI is not active in the LMI full
status response.ro Enumeration .1.3.6.1.4.1.485.8.4.3.5 |
mfrapStatusLedTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.4.4 |
mfrapStatusDteModeLEDStatus of the DTE Mode LED.
(1) DTE Mode LED off: Missing control signals
(2) DTE Mode LED green: Normal
(3) DTE Mode LED yellow: Test Modero Enumeration .1.3.6.1.4.1.485.8.4.4.1 |
mfrapStatusDteStatusLEDStatus of the DTE Status LED.
(1) DTE Status LED off: no connections to WAN
(2) DTE Status LED green: normalro Enumeration .1.3.6.1.4.1.485.8.4.4.2 |
mfrapStatusDteTxLEDStatus of the DTE Tx Data LED. In Frame Relay mode, this LED is ON
(green) when the DTE is not sending HDLC Flags and is OFF when
HDLC flags are being transmit. In CBO mode, the LED is ON (green)
for a SPACE and OFF for a MARK.
(1) DTE Transmit LED OFF: inactive (HDLC flags or CBO marks)
(2) DTE Transmit LED ON: active (HDLC frames or CBO spaces)ro Enumeration .1.3.6.1.4.1.485.8.4.4.3 |
mfrapStatusDteRxLEDStatus of the DTE Rx Data LED. In Frame Relay mode, this LED is ON
(green) when the WAN is receiving HDLC Flags and is OFF when
HDLC flags are being received. In CBO mode, the LED is ON (green)
for a SPACE and OFF for a MARK.
(1) DTE Receive LED OFF: inactive (HDLC flags or CBO marks)
(2) DTE Receive LED ON: active (HDLC frames or CBO spaces)ro Enumeration .1.3.6.1.4.1.485.8.4.4.4 |
mfrapStatusT1ModeLEDStatus of the WAN Mode LED.
(1) WAN Mode LED is green: normal data mode
(2) WAN Mode LED is yellow: test modero Enumeration .1.3.6.1.4.1.485.8.4.4.5 |
mfrapStatusT1StatusLEDStatus of the WAN Status LED.
(1) Off - no signal detected from WAN.
(2) Green - framed signal detected with no errors (normal operation)
(3) Yellow - remote alarm condition detected (yellow or AIS alarms)
(4) Red - unit has declared Red Alarm due to the presence of an
improperly framed signal from the WAN.
(5) Blinking Red and Off - unit has declared Red Alarm due to the
absence of a signal from the WAN.
(6) Blinking Green and Red - unit is receiving a properly framed signal
from the WAN but has detected a transient error condition. Possible
Line Code Violations or ESF CRC errors indicating errored data bits.
(7) Blinking Red and Yellow - unit is receiving an unframed all ones (AIS)
from the WAN. This is indicative of an upstream alarm condition on the
WAN.ro Enumeration .1.3.6.1.4.1.485.8.4.4.6 |
mfrapStatusAllLEDsStatus of all six MFRAP LEDs, encoded in a string.
'F' off
'5' green
'0' yellow
'A' red
'7' blinking green and off
'3' blinking yellow and off
'B' blinking red and off
'4' blinking green and yellow
'6' blinking green and red
'8' blinking yellow and red
Positionally, the 8 letters are DTE Mode, DTE status,
Dte Tx, Dte Rx, PBX Mode, PBX Status, T1 Mode, and T1 Status.
For example, '55555556' would mean: DTE in normal mode, active status,
transmitting and receiving PBX in normal mode with normal status and
T1 normal with transient errors.ro DisplayString .1.3.6.1.4.1.485.8.4.4.7 |
mfrapStatusDandiModeLEDStatus of the Drop & Insert Mode LED.
(1) Drop & Insert Mode LED is green: normal data mode
(2) Drop & Insert Mode LED is yellow: test modero Enumeration .1.3.6.1.4.1.485.8.4.4.8 |
mfrapStatusDandiStatusLEDStatus of the Drop & Insert Status LED.
(1) Off - no signal detected from Drop & Insert port.
(2) Green - framed signal detected with no errors
(normal operation)
(3) Yellow - remote alarm condition detected (yellow or
AIS alarms)
(4) Red - unit has declared Red Alarm due to the presence
of an improperly framed signal from the Drop & Insert
port.
(5) Blinking Red and Off - unit has declared Red Alarm due
to the absence of a signal from the Drop & Insert port.
(6) Blinking Green and Red - unit is receiving a properly
framed signal from the Drop & Insert port but has detected
a transient error condition. Possible Line Code Violations
or ESF CRC errors indicating errored data bits.
(7) Blinking Red and Yellow - unit is receiving an unframed
all ones (AIS) from the Drop & Insert port. This is
indicative of an upstream alarm condition on the
Drop & Insert port.ro Enumeration .1.3.6.1.4.1.485.8.4.4.9 |
mfrapVnipTransitDelayClearAllows the user to clear all the VNIP Transit Delay
data collected in the VNIP topology database.
(1) Clear entire Transit Delay results databaserw Enumeration .1.3.6.1.4.1.485.8.4.5 |
mfrapLmiSourcingIf configured for Frame Relay with a non-zero LMI inactivity timer
the unit will monitor the status of LMI and, if proper messaging
is not detected, will attempt to emulate either Frame Relay DTE or
DCE devices in attempt to restore LMI to any attached equipment and
provide managed access for diagnostic purposes. Typically frads/routers
are Frame Relay DTE while switches are Frame Relay DCE but this model
may vary. In the absence of full-duplex LMI, the unit will cycle
through various states in attempt to adapt to an LMI partner. The
unit will try each state for the duration of the LMI Inactivity timer
and then advance to the next one if satisfactory handshaking is not
established. While in any of these states if full-duplex LMI handshaking
does appear, the unit will immediately revert to the passthrough state.
(1) initializing
(2) Passthrough: not sourcing any LMI messages.
(3) Status Enquiries out DTE interface: unit is emulating a Frame
Relay DTE device out the its (physical) DTE interface.
(4) Status Enquiries out WAN interface: unit is emulating a Frame
Relay DTE device out the its WAN interface.
(5) Status Responses out the DTE interface: unit is emulating a
Frame Relay DCE device out the its (physical) DTE interface
(provisioning the single default management DLCI).
(6) Status Responses out the WAN interface: unit is emulating a
Frame Relay DCE device out the its WAN interface (provisioning
the single default management DLCI).
(7) Disabled - LMI Inactivity timer is zero or unit not configured
for a Frame Relay application.
(8) Status Responses out both DTE and WAN interfaces: unit is
configured for Fixed DCE mode of management and emulates a Frame
Relay DCE independently on both ports (provisioning
the single default management DLCI).ro Enumeration .1.3.6.1.4.1.485.8.4.6 |
mfrapStatusDteTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.4.7 |
mfrapStatusDteModeStatus of allocation of T1 bandwidth to the DTE port data.
(1) no connections - indicates the DTE port has no connections
to the WAN.
(2) Active - indicates DTE data rate has been assigned T1 DS0s
and is in a normal data mode.
(3) Test - indicates DTE data rate has been assigned T1 DS0s
but is in a diagnostic condition.ro Enumeration .1.3.6.1.4.1.485.8.4.7.1 |
mfrapStatusDteRtsStatus of the Request to Send (RTS) signal from the DTE port.
(1) RTS Active
(2) RTS Inactivero Enumeration .1.3.6.1.4.1.485.8.4.7.2 |
mfrapStatusDteDtrStatus of the Data Terminal Ready (DTR) signal from the DTE port.
(1) DTR Active
(2) DTR Inactivero Enumeration .1.3.6.1.4.1.485.8.4.7.3 |
mfrapStatusDteDcdStatus of the Data Carrier Detect (DCD) signal driven by this
unit towards the DTE port
(1) DCD Active
(2) DCD Inactivero Enumeration .1.3.6.1.4.1.485.8.4.7.4 |
mfrapStatusDteDsrStatus of the Data Set Ready (DSR) signal driven by this
unit towards the DTE port.
(1) DSR Active
(2) DSR Inactivero Enumeration .1.3.6.1.4.1.485.8.4.7.5 |
mfrapStatusDteCtsStatus of the Clear to Send (CTS) signal driven by this
unit towards the DTE port
(1) CTS Active
(2) CTS Inactivero Enumeration .1.3.6.1.4.1.485.8.4.7.6 |
mfrapStatusLmiAutosenseThis indicates the current status of LMI Auto Sensing if
it's enabled.
(1) Disabled: LMI is configured as Type 1, Annex-D, or Annex-A
(2) Searching: unit is attempting to determine the LMI type of
the attached equipment by issuing LMI messages of each LMI
type and searching for responses.
(3) Learned Annex-D: unit has successfully detected Annex-D LMI
(ANSI T1.617 Annex D)
(4) Learned Annex-A: unit has successfully detected Annex-A LMI
(ITU/CCITT Q.933 Annex A)
(5) Learned Type 1: unit has successfully detected Type 1 LMI
(Cisco, Group of four, LMI)ro Enumeration .1.3.6.1.4.1.485.8.4.12 |
mfrapStatusNestTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.4.14 |
mfrapStatusNestFanOneThe status of the chasis fan 1.
(1) Fan is operating normally
(2) Fan is in alarm state
(3) Fan alarm is not applicablero Enumeration .1.3.6.1.4.1.485.8.4.14.1 |
mfrapStatusNestFanTwoThe status of the chasis fan 2.
(1) Fan is operating normally
(2) Fan is in alarm state
(3) Fan alarm is not applicablero Enumeration .1.3.6.1.4.1.485.8.4.14.2 |
mfrapStatusNestPowerSupplyThe status of the chasis power supply.
(1) The nest power supply is operating
normally
(2) The nest power supply is in alarm
state
(3) A standalone unit will return 'na'ro Enumeration .1.3.6.1.4.1.485.8.4.14.3 |
mfrapStatusNestSlotIdThe chassis slot number (1-16) occupied by the MFRAP
nest card. A standalone unit will return a '0'.ro INTEGER .1.3.6.1.4.1.485.8.4.14.4 |
mfrapStatusDandiTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.4.15 |
mfrapStatusDandiModeStatus of allocation of T1 DS0s to the Drop & Insert port DS0s.
(1) no connections - indicates the Drop & Insert port has no
connections to the WAN.
(2) Active - indicates that at least one Drop & Insert DS0
has been assigned to a T1 DS0.
(3) Test - indicates that at least one Drop & Insert DS0
has been assigned to a T1 DS0 but is in a diagnostic condition.ro Enumeration .1.3.6.1.4.1.485.8.4.15.4 |
mfrapStatusDandiStatusStatus of the signal received from the Drop & Insert port.
(1) In Sync - unit has detected a properly framed T1 signal
and is not experiencing any error conditions.
(2) In Sync with Errors - unit has detected a properly framed
T1 signal but is experiencing some error conditions. Refer to
T1 current performance results for details.
(3) Signal Detected without Frame Sync - while a signal is present
from the Drop & Insert port, it does not contain the framing
pattern defined for this unit. This could be either incorrectly
configured T1 Frame type or the presence of an alarm condition
on the network.
(4) No Carrier - there is no signal detected from the WAN.
(5) Not Applicable.ro Enumeration .1.3.6.1.4.1.485.8.4.15.5 |
mfrapStatusDandiAlarmsAlarms present at the T1 port.
(1) No alarm conditions present.
(2) Red Alarm Declared - Unit has experienced loss of frame
synchronization with the signal received from the Drop
& Insert port for an extended time and is reporting an
alarm condition that severely impairs normal operation.
During this Red Alarm condition the unit will transmit
Yellow alarm back to the Drop & Insert port. If this
condition persists consult your service provider.
(3) Yellow ALarm Detected - Unit is receiving a yellow alarm
indication from the Drop & Insert port. Detection of yellow
alarm implies that the attached device is in a red alarm
conditon. Red alarm is declared due to the extended absence
of a properly framed signal. If this condition persists
consult your service provider.
(4) Unframe All Ones Detected - Unit is receiving unframed all
ones from the Drop & Insert port (AIS, blue alarm). Detection
of AIS implies that the attached device is reporting
an alarm condition from an upstream device. If
this condition persists consult your service provider.ro Enumeration .1.3.6.1.4.1.485.8.4.15.6 |
mfrapPerformance OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.5 |
mfrapPerfPhysicalIntf OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.5.1 |
mfrapPerfT1CurrentTableThe T1 physical layer performance numbers for the current
15 minute interval. These are defined and accumulated per
ANSI specification T1.403 and AT&T publication 54016. Depending
upon the configured T1 Framing mode, these results may be
retrieved via ESF facility data link by service personnel. SEQUENCE OF MfrapT1CurrentEntry .1.3.6.1.4.1.485.8.5.1.1 |
mfrapT1CurrentEntryAn entry in the T1 Current Perf table. MfrapT1CurrentEntry .1.3.6.1.4.1.485.8.5.1.1.1 |
mfrapT1CurrentIndexThe index value which uniquely identifies the
T1 interface to which this entry is applicable.
The Drop & Index port has its own Current
Performance Table, so the index will always be 1.ro INTEGER .1.3.6.1.4.1.485.8.5.1.1.1.1 |
mfrapT1CurrentCrc6EventsCount of CRC errors detected on an ESF framed circuit.
In ESF framing a CRC is generated at the source, based upon
the composite data. A CRC error indicates the presence of
at least one bit error in an ESF superframe. This field is
a free-running accumulation of CRC errors and IS NOT reset
when the current 15 minute interval expires. It can be reset
with the performance command mfrapT1PerfClearEvents.
Not applicable if D4/SF framing is selcted.ro Gauge .1.3.6.1.4.1.485.8.5.1.1.1.2 |
mfrapT1CurrentOofEventsCount of Out-of-Frame events on a T1 circuit. An out-of-
frame event occurs when the frame synchronization criteria
is lost and a resynchronization must occur. Data is interrupted
during frame resynchronization. This field is a free-running
accumulation of OOF transitions and IS NOT reset when the
current 15 minute interval expires. It can be reset with the
performance command mfrapT1PerfClearEvents.ro Gauge .1.3.6.1.4.1.485.8.5.1.1.1.3 |
mfrapT1CurrentESsThe number of Errored Seconds, encountered by
a T1 interface in the current 15 minute inter-
val. An errored second is a one-second interval with
CRC errors or a loss of frame sync occurred.ro Gauge .1.3.6.1.4.1.485.8.5.1.1.1.4 |
mfrapT1CurrentSESsThe number of Severely Errored Seconds encountered by
a t1 interface in the current 15 minute interval. A
severely errored second is a one second interval with
more than 320 CRC errors or one or more frame sync losses.ro Gauge .1.3.6.1.4.1.485.8.5.1.1.1.5 |
mfrapT1CurrentSEFSsThe number of Severely Errored Framing Seconds
encountered by a t1 interface in the current
15 minute interval. A SEFS is a one second interval
with one or more frame sync losses.ro Gauge .1.3.6.1.4.1.485.8.5.1.1.1.6 |
mfrapT1CurrentUASsThe number of Unavailable Seconds encountered
by a t1 interface in the current 15 minute in-
terval. A UAS is a one second interval during which
the received signal is classified as 'unavailable due
to excessive errors'. A signal is unavailable after
receiving ten consective severely errored seconds and
stays unavailable until ten seconds without a severely
errored second occur.ro Gauge .1.3.6.1.4.1.485.8.5.1.1.1.7 |
mfrapT1CurrentCSSsThe number of Controlled Slip Seconds encoun-
tered by a t1 interface in the current 15
minute interval. A controlled slip is the
replication or deletion of a T1 frame at the receiver.
These events often indicate a T1 network timing
problem.ro Gauge .1.3.6.1.4.1.485.8.5.1.1.1.8 |
mfrapT1CurrentBESsThe number of Bursty Errored Seconds (BESs)
encountered by a DS1 interface in the current
15 minute interval. A BES is a one second interval
with more than one and less than 320 CRC errors.ro Gauge .1.3.6.1.4.1.485.8.5.1.1.1.9 |
mfrapT1CurrentLCVsThe number of Line Code Violations (LCVs) en-
countered by a DS1 interface in the current 15
minute interval. LCVs are non-B8ZS related
violations of the alternate mark inversion protocol.
An excessive count usually indicates a B8ZS/AMI
configuration mismatch in the T1 network.ro Gauge .1.3.6.1.4.1.485.8.5.1.1.1.10 |
mfrapPerfT1IntervalTableThe DS1 Interval table. A history of physical layer performance
results are maintained and represented as 96 15-minute intervals.
These are defined and accumulated per ANSI specification T1.403
and AT&T publication 54016. Depending upon the configured T1
Framing mode, these results may be retrieved via ESF facility data
link by service personnel SEQUENCE OF MfrapT1IntervalEntry .1.3.6.1.4.1.485.8.5.1.2 |
mfrapT1IntervalEntryAn entry in the DS1 Interval table. MfrapT1IntervalEntry .1.3.6.1.4.1.485.8.5.1.2.1 |
mfrapT1IntervalIndexThe index value which uniquely identifies the
t1 interface to which this entry is applicable.
Since there is a separate Drop & Insert Performance
Intervals Table, the value of this index will
always be 1, referring to the WAN port.ro INTEGER .1.3.6.1.4.1.485.8.5.1.2.1.1 |
mfrapT1IntervalNumberA number between 1 and 96, where 96 is the most
recently completed 15 minute interval and 1 is
the least recently completed 15 minutes inter-
val which occured 24 hours ago (assuming that all
96 intervals are valid).ro INTEGER .1.3.6.1.4.1.485.8.5.1.2.1.2 |
mfrapT1IntervalESsThe number of Errored Seconds encountered by a
t1 interface in one of the previous 96, indi-
vidual 15 minute, intervals. An errored second is
a one-second interval with CRC errors or a loss
of frame sync occurred.ro Gauge .1.3.6.1.4.1.485.8.5.1.2.1.3 |
mfrapT1IntervalSESsThe number of Severely Errored Seconds encoun-
tered by a t1 interface in one of the previous
96, individual 15 minute, intervals. A severely
errored second is a one second interval with more
than 320 CRC errors or one or more frame sync losses.ro Gauge .1.3.6.1.4.1.485.8.5.1.2.1.4 |
mfrapT1IntervalSEFSsThe number of Severely Errored Framing Seconds
encountered by a t1 interface in one of the
previous 96, individual 15 minute, intervals.
A SEFS is a one second interval with one or more
frame sync losses.ro Gauge .1.3.6.1.4.1.485.8.5.1.2.1.5 |
mfrapT1IntervalUASsThe number of Unavailable Seconds encountered
by a t1 interface in one of the previous 96,
individual 15 minute, intervals. A UAS is a one second
interval during which the received signal is classified
as 'unavailable due to excessive errors'. A signal is
unavailable after receiving ten consective severely
errored seconds and stays unavailable until ten seconds
without a severely errored second occur.ro Gauge .1.3.6.1.4.1.485.8.5.1.2.1.6 |
mfrapT1IntervalCSSsThe number of Controlled Slip Seconds encoun-
tered by a t1 interface in one of the previous
96, individual 15 minute, intervals. A controlled
slip is the replication or deletion of a T1 frame
at the receiver. These events often indicate a T1
network timing problem.ro Gauge .1.3.6.1.4.1.485.8.5.1.2.1.7 |
mfrapT1IntervalBESsThe number of Bursty Errored Seconds (BESs)
encountered by a t1 interface in one of the
previous 96, individual 15 minute, intervals.
A BES is a one second interval with more than one
and less than 320 CRC errors.ro Gauge .1.3.6.1.4.1.485.8.5.1.2.1.8 |
mfrapT1IntervalLCVsThe number of Line Code Violations (LCVs) en-
countered by a DS1 interface in the current 15
minute interval. LCVs are non-B8ZS related
violations of the alternate mark inversion protocol.
An excessive count usually indicates a B8ZS/AMI
configuration mismatch in the T1 network.ro Gauge .1.3.6.1.4.1.485.8.5.1.2.1.9 |
mfrapPerfT1TotalTableThe T1 Total table cumulative physical layer performance
results from the past 24 hours. These are defined and
accumulated per ANSI specification T1.403 and AT&T publication
54016. Depending upon the configured T1 Framing mode, these
results may be retrieved via ESF facility data link by service
personnel. SEQUENCE OF MfrapT1TotalEntry .1.3.6.1.4.1.485.8.5.1.3 |
mfrapT1TotalEntryAn entry in the T1 Physical Layer Measurement Totals table. MfrapT1TotalEntry .1.3.6.1.4.1.485.8.5.1.3.1 |
mfrapT1TotalIndexThe index value which uniquely identifies the
t1 interface to which this entry is applica-
ble. Since there is a separate Drop & Insert Performance
24 Hour Table, the value of this index will
always be 1, referring to the WAN port.ro INTEGER .1.3.6.1.4.1.485.8.5.1.3.1.1 |
mfrapT1TotalESsThe number of Errored Seconds encountered by a
t1 interface in the previous 24 hour interval.
An errored second is a one-second interval with
CRC errors or a loss of frame sync occurred.ro Gauge .1.3.6.1.4.1.485.8.5.1.3.1.2 |
mfrapT1TotalSESsThe number of Severely Errored Seconds encoun-
tered by a t1 interface in the previous 24
hour interval. A severely errored second is a one
second interval with more than 320 CRC errors or
one or more frame sync losses.ro Gauge .1.3.6.1.4.1.485.8.5.1.3.1.3 |
mfrapT1TotalSEFSsThe number of Severely Errored Framing Seconds
24 hour interval. A SEFS is a one second interval
with one or more frame sync losses.ro Gauge .1.3.6.1.4.1.485.8.5.1.3.1.4 |
mfrapT1TotalUASsThe number of Unavailable Seconds encountered
by a t1 interface in the previous 24 hour in-
terval. A UAS is a one second interval during which
the received signal is classified as 'unavailable
due to excessive errors'. A signal is unavailable
after receiving ten consective severely errored
seconds and stays unavailable until ten seconds
without a severely errored second occur.ro Gauge .1.3.6.1.4.1.485.8.5.1.3.1.5 |
mfrapT1TotalCSSsThe number of Controlled Slip Seconds encoun-
tered by a t1 interface in the previous 24
hour interval. A controlled slip is the replication
or deletion of a T1 frame at the receiver. These
events often indicate a T1 network timing problem.ro Gauge .1.3.6.1.4.1.485.8.5.1.3.1.6 |
mfrapT1TotalBESsThe number of Bursty Errored Seconds (BESs)
encountered by a t1 interface in the previous
24 hour interval. A BES is a one second interval
with more than one and less than 320 CRC errors.ro Gauge .1.3.6.1.4.1.485.8.5.1.3.1.7 |
mfrapT1TotalLCVsThe number of Line Code Violations (LCVs) en-
countered by a t1 interface in the current 15
minute interval. LCVs are non-B8ZS related
violations of the alternate mark inversion protocol.
An excessive count usually indicates a B8ZS/AMI
configuration mismatch in the T1 network.ro Gauge .1.3.6.1.4.1.485.8.5.1.3.1.8 |
mfrapT1PerfCmdTypeTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.5.1.4 |
mfrapT1PerfFreezeStateThis command halts the node's performance monitoring
and freezes the current, interval, and total performance
register values.rw Enumeration .1.3.6.1.4.1.485.8.5.1.4.1 |
mfrapT1PerfClearEventsThis command resets all of the (user's) error event
registers. This includes the CRC6 and Out-of-Frame
counts. It does not affect the interval or 24 hour
performance totals.rw Enumeration .1.3.6.1.4.1.485.8.5.1.4.2 |
mfrapT1PerfClearAllThis command resets all of the (user's) performance
registers.rw Enumeration .1.3.6.1.4.1.485.8.5.1.4.3 |
mfrapPerfDandiCurrentTableThe T1 physical layer performance numbers for the current
15 minute interval. These are defined and accumulated per
ANSI specification T1.403 and AT&T publication 54016. Depending
upon the configured T1 Framing mode, these results may be
retrieved via ESF facility data link by service personnel. SEQUENCE OF MfrapDandiCurrentEntry .1.3.6.1.4.1.485.8.5.1.5 |
mfrapDandiCurrentEntryAn entry in the D&I Current Perf table. MfrapDandiCurrentEntry .1.3.6.1.4.1.485.8.5.1.5.1 |
mfrapDandiCurrentIndexThe index value which uniquely identifies the
D&I interface to which this entry is applica-
ble.ro Enumeration .1.3.6.1.4.1.485.8.5.1.5.1.1 |
mfrapDandiCurrentCrc6EventsCount of CRC errors detected on an ESF framed circuit.
In ESF framing a CRC is generated at the source, based upon
the composite data. A CRC error indicates the presence of
at least one bit error in an ESF superframe. This field is
a free-running accumulation of CRC errors and IS NOT reset
when the current 15 minute interval expires. It can be reset
with the performance command mfrapDandiPerfClearEvents.
Not applicable if D4/SF framing is selcted.ro Gauge .1.3.6.1.4.1.485.8.5.1.5.1.2 |
mfrapDandiCurrentOofEventsCount of Out-of-Frame events on a D&I circuit. An out-of-
frame event occurs when the frame synchronization criteria
is lost and a resynchronization must occur. Data is interrupted
during frame resynchronization. This field is a free-running
accumulation of OOF transitions and IS NOT reset when the
current 15 minute interval expires. It can be reset with the
performance command mfrapDandiPerfClearEvents.ro Gauge .1.3.6.1.4.1.485.8.5.1.5.1.3 |
mfrapDandiCurrentESsThe number of Errored Seconds, encountered by
a D&I interface in the current 15 minute inter-
val. An errored second is a one-second interval with
CRC errors or a loss of frame sync occurred.ro Gauge .1.3.6.1.4.1.485.8.5.1.5.1.4 |
mfrapDandiCurrentSESsThe number of Severely Errored Seconds encountered by
a D&I interface in the current 15 minute interval. A
severely errored second is a one second interval with
more than 320 CRC errors or one or more frame sync losses.ro Gauge .1.3.6.1.4.1.485.8.5.1.5.1.5 |
mfrapDandiCurrentSEFSsThe number of Severely Errored Framing Seconds
encountered by a D&I interface in the current
15 minute interval. A SEFS is a one second interval
with one or more frame sync losses.ro Gauge .1.3.6.1.4.1.485.8.5.1.5.1.6 |
mfrapDandiCurrentUASsThe number of Unavailable Seconds encountered
by a D&I interface in the current 15 minute in-
terval. A UAS is a one second interval during which
the received signal is classified as 'unavailable due
to excessive errors'. A signal is unavailable after
receiving ten consective severely errored seconds and
stays unavailable until ten seconds without a severely
errored second occur.ro Gauge .1.3.6.1.4.1.485.8.5.1.5.1.7 |
mfrapDandiCurrentCSSsThe number of Controlled Slip Seconds encoun-
tered by a D&I interface in the current 15
minute interval. A controlled slip is the
replication or deletion of a D&I frame at the receiver.
These events often indicate a D&I network timing
problem.ro Gauge .1.3.6.1.4.1.485.8.5.1.5.1.8 |
mfrapDandiCurrentBESsThe number of Bursty Errored Seconds (BESs)
encountered by a DS1 interface in the current
15 minute interval. A BES is a one second interval
with more than one and less than 320 CRC errors.ro Gauge .1.3.6.1.4.1.485.8.5.1.5.1.9 |
mfrapDandiCurrentLCVsThe number of Line Code Violations (LCVs) en-
countered by a DS1 interface in the current 15
minute interval. LCVs are non-B8ZS related
violations of the alternate mark inversion protocol.
An excessive count usually indicates a B8ZS/AMI
configuration mismatch in the D&I network.ro Gauge .1.3.6.1.4.1.485.8.5.1.5.1.10 |
mfrapPerfDandiIntervalTableThe DS1 Interval table. A history of physical layer performance
results are maintained and represented as 96 15-minute intervals.
These are defined and accumulated per ANSI specification T1.403
and AT&T publication 54016. Depending upon the configured T1
Framing mode, these results may be retrieved via ESF facility data
link by service personnel SEQUENCE OF MfrapDandiIntervalEntry .1.3.6.1.4.1.485.8.5.1.6 |
mfrapDandiIntervalEntryAn entry in the DS1 Interval table. MfrapDandiIntervalEntry .1.3.6.1.4.1.485.8.5.1.6.1 |
mfrapDandiIntervalIndexThe index value which uniquely identifies the
D&I interface to which this entry is applicable.
The interface identified by a particular value
of this index is the same interface as identified
by the same value as a NetwLineIndex object instance.ro Enumeration .1.3.6.1.4.1.485.8.5.1.6.1.1 |
mfrapDandiIntervalNumberA number between 1 and 96, where 1 is the most
recently completed 15 minute interval and 96 is
the least recently completed 15 minutes inter-
val (assuming that all 96 intervals are
valid).ro INTEGER .1.3.6.1.4.1.485.8.5.1.6.1.2 |
mfrapDandiIntervalESsThe number of Errored Seconds encountered by a
D&I interface in one of the previous 96, indi-
vidual 15 minute, intervals. An errored second is
a one-second interval with CRC errors or a loss
of frame sync occurred.ro Gauge .1.3.6.1.4.1.485.8.5.1.6.1.3 |
mfrapDandiIntervalSESsThe number of Severely Errored Seconds encoun-
tered by a D&I interface in one of the previous
96, individual 15 minute, intervals. A severely
errored second is a one second interval with more
than 320 CRC errors or one or more frame sync losses.ro Gauge .1.3.6.1.4.1.485.8.5.1.6.1.4 |
mfrapDandiIntervalSEFSsThe number of Severely Errored Framing Seconds
encountered by a D&I interface in one of the
previous 96, individual 15 minute, intervals.
A SEFS is a one second interval with one or more
frame sync losses.ro Gauge .1.3.6.1.4.1.485.8.5.1.6.1.5 |
mfrapDandiIntervalUASsThe number of Unavailable Seconds encountered
by a D&I interface in one of the previous 96,
individual 15 minute, intervals. A UAS is a one second
interval during which the received signal is classified
as 'unavailable due to excessive errors'. A signal is
unavailable after receiving ten consective severely
errored seconds and stays unavailable until ten seconds
without a severely errored second occur.ro Gauge .1.3.6.1.4.1.485.8.5.1.6.1.6 |
mfrapDandiIntervalCSSsThe number of Controlled Slip Seconds encoun-
tered by a D&I interface in one of the previous
96, individual 15 minute, intervals. A controlled
slip is the replication or deletion of a D&I frame
at the receiver. These events often indicate a D&I
network timing problem.ro Gauge .1.3.6.1.4.1.485.8.5.1.6.1.7 |
mfrapDandiIntervalBESsThe number of Bursty Errored Seconds (BESs)
encountered by a D&I interface in one of the
previous 96, individual 15 minute, intervals.
A BES is a one second interval with more than one
and less than 320 CRC errors.ro Gauge .1.3.6.1.4.1.485.8.5.1.6.1.8 |
mfrapDandiIntervalLCVsThe number of Line Code Violations (LCVs) en-
countered by a DS1 interface in the current 15
minute interval. LCVs are non-B8ZS related
violations of the alternate mark inversion protocol.
An excessive count usually indicates a B8ZS/AMI
configuration mismatch in the D&I network.ro Gauge .1.3.6.1.4.1.485.8.5.1.6.1.9 |
mfrapPerfDandiTotalTableThe T1 Total table cumulative physical layer performance
results from the past 24 hours. These are defined and
accumulated per ANSI specification T1.403 and AT&T publication
54016. Depending upon the configured T1 Framing mode, these
results may be retrieved via ESF facility data link by service
personnel. SEQUENCE OF MfrapDandiTotalEntry .1.3.6.1.4.1.485.8.5.1.7 |
mfrapDandiTotalEntryAn entry in the D&I Total table. MfrapDandiTotalEntry .1.3.6.1.4.1.485.8.5.1.7.1 |
mfrapDandiTotalIndexThe index value which uniquely identifies the
D&I interface to which this entry is applica-
ble. The interface identified by a particular
value of this index is the same interface as
identified by the same value as a NetwLineIndex
object instance.ro Enumeration .1.3.6.1.4.1.485.8.5.1.7.1.1 |
mfrapDandiTotalESsThe number of Errored Seconds encountered by a
D&I interface in the previous 24 hour interval.
An errored second is a one-second interval with
CRC errors or a loss of frame sync occurred.ro Gauge .1.3.6.1.4.1.485.8.5.1.7.1.2 |
mfrapDandiTotalSESsThe number of Severely Errored Seconds encoun-
tered by a D&I interface in the previous 24
hour interval. A severely errored second is a one
second interval with more than 320 CRC errors or
one or more frame sync losses.ro Gauge .1.3.6.1.4.1.485.8.5.1.7.1.3 |
mfrapDandiTotalSEFSsThe number of Severely Errored Framing Seconds
24 hour interval. A SEFS is a one second interval
with one or more frame sync losses.ro Gauge .1.3.6.1.4.1.485.8.5.1.7.1.4 |
mfrapDandiTotalUASsThe number of Unavailable Seconds encountered
by a D&I interface in the previous 24 hour in-
terval. A UAS is a one second interval during which
the received signal is classified as 'unavailable
due to excessive errors'. A signal is unavailable
after receiving ten consective severely errored
seconds and stays unavailable until ten seconds
without a severely errored second occur.ro Gauge .1.3.6.1.4.1.485.8.5.1.7.1.5 |
mfrapDandiTotalCSSsThe number of Controlled Slip Seconds encoun-
tered by a D&I interface in the previous 24
hour interval. A controlled slip is the replication
or deletion of a D&I frame at the receiver. These
events often indicate a D&I network timing problem.ro Gauge .1.3.6.1.4.1.485.8.5.1.7.1.6 |
mfrapDandiTotalBESsThe number of Bursty Errored Seconds (BESs)
encountered by a D&I interface in the previous
24 hour interval. A BES is a one second interval
with more than one and less than 320 CRC errors.ro Gauge .1.3.6.1.4.1.485.8.5.1.7.1.7 |
mfrapDandiTotalLCVsThe number of Line Code Violations (LCVs) en-
countered by a D&I interface in the current 15
minute interval. LCVs are non-B8ZS related
violations of the alternate mark inversion protocol.
An excessive count usually indicates a B8ZS/AMI
configuration mismatch in the D&I network.ro Gauge .1.3.6.1.4.1.485.8.5.1.7.1.8 |
mfrapDandiPerfCmdTypeTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.5.1.8 |
mfrapDandiPerfFreezeStateThis command halts the node's performance monitoring
and freezes the current, interval, and total performance
register values.rw Enumeration .1.3.6.1.4.1.485.8.5.1.8.1 |
mfrapDandiPerfClearEventsThis command resets all of the (user's) error event
registers. This includes the CRC6 and Out-of-Frame
counts. It does not affect the interval or 24 hour
performance totals.rw Enumeration .1.3.6.1.4.1.485.8.5.1.8.2 |
mfrapDandiPerfClearAllThis command resets all of the (user's) performance
registers.rw Enumeration .1.3.6.1.4.1.485.8.5.1.8.3 |
mfrapPerfMgmtIp OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.5.2 |
mfrapPerfMgmtIpIFStatsTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.5.2.1 |
mfrapPerfMgmtIpIFInOctetsThe count of all octets associated with received frames
that are specifically addressed as management packets
for this unit. Same as ifInOctets in mib-2.ro Counter .1.3.6.1.4.1.485.8.5.2.1.1 |
mfrapPerfMgmtIpIFInErrorsThe count of packets associated with received frames
that are specifically addressed as management packets
for this unit which could not be handled because of
errors. Same as ifInErrors in mib-2.ro Counter .1.3.6.1.4.1.485.8.5.2.1.2 |
mfrapPerfMgmtIpIFOutOctetsThe count of all octets associated with generated frames
that are specifically addressed as management packets
from this unit. Same as ifOutOctets in mib-2. Same as ifOutOctets in mib-2.ro Counter .1.3.6.1.4.1.485.8.5.2.1.3 |
mfrapPerfMgmtIpIFOperStatusThe current operational state of the management interface.
Same as ifOperStatus in mib-2.
(1) Interface Up
(2) Interface Down
(3) Interface in Testro Enumeration .1.3.6.1.4.1.485.8.5.2.1.4 |
mfrapPerfMgmtIpIPStatsTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.5.2.2 |
mfrapPerfMgmtIpIPInRcvThe count of all ip datagrams received which
are specifically addressed as management frames
for this unit. Same as ipInReceives in mib-2.ro Counter .1.3.6.1.4.1.485.8.5.2.2.1 |
mfrapPerfMgmtIpIPInHdrErrThe count of ip datagrams received which
are specifically addressed as management frames
for this unit that were discarded because of
errors in their IP headers. Same as ipInHdrErrors
in mib-2.ro Counter .1.3.6.1.4.1.485.8.5.2.2.2 |
mfrapPerfMgmtIpIPInAddrErrThe count of ip datagrams received which
are specifically addressed as management frames
for this unit that were discarded because unexpected
or invalid IP addresses in their IP headers.
Same as ipInAddrErrors in mib-2.ro Counter .1.3.6.1.4.1.485.8.5.2.2.3 |
mfrapPerfMgmtIpIPInProtUnkThe count of ip datagrams received which
are specifically addressed as management frames
for this unit that were discarded because of
unsupported protocols. Same as ipInUnknownProtos
in mib-2.ro Counter .1.3.6.1.4.1.485.8.5.2.2.4 |
mfrapPerfMgmtIpIPInDscrdThe count of datagrams received which
are specifically addressed as management frames
for this unit that were discarded for reasons
other than a problem with the datagram. Same as
ipInDiscards in mib-2.ro Counter .1.3.6.1.4.1.485.8.5.2.2.5 |
mfrapPerfMgmtIpIPInDlvrsThe count ofip datagrams received which
are specifically addressed as management frames
for this unit that were delivered to IP client
protocols. Same as ipInDelivers in mib-2.ro Counter .1.3.6.1.4.1.485.8.5.2.2.6 |
mfrapPerfMgmtIpIPOutRqstThe count of all outgoing datagrams generated by this
unit which are specifically addressed as management frames.
Same as ipOutRequests in mib-2.ro Counter .1.3.6.1.4.1.485.8.5.2.2.7 |
mfrapPerfMgmtIpIPOutDscrdThe count of outgoing datagrams generated by this
unit which are specifically addressed as management
frames that were discarded for reasons other than a
problem with the datagram. Same as ipOutDiscards in mib-2.ro Counter .1.3.6.1.4.1.485.8.5.2.2.8 |
mfrapPerfMgmtIpIPOutNoRtThe count of outgoing datagrams generated by this
unit which are specifically addressed as management
frames that were discarded because no route could be
found for transmission. Same as ipOutNoRoutes in mib-2.ro Counter .1.3.6.1.4.1.485.8.5.2.2.9 |
mfrapPerfMgmtIpICMPStatsTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.5.2.3 |
mfrapPerfMgmtIpICMPInMsgsThe count of all ICMP messages received which are
addressed to this unit. Same as icmpInMsgs in mib-2.ro Counter .1.3.6.1.4.1.485.8.5.2.3.1 |
mfrapPerfMgmtIpICMPInErrorsThe count of ICMP messages received which are
addressed to this unit but contain errors. Same
as icmpInErrors in mib-2.ro Counter .1.3.6.1.4.1.485.8.5.2.3.2 |
mfrapPerfMgmtIpICMPInDestUnreachsThe count of ICMP Destination Unreachable messages
received which are addressed to this unit. Same as
icmpInDestUnreachs in mib-2.ro Counter .1.3.6.1.4.1.485.8.5.2.3.3 |
mfrapPerfMgmtIpICMPInTimeExcdsThe count of ICMP Time Exceeded messages received which
are addressed to this unit. Same as icmpInTimeExcds in
mib-2.ro Counter .1.3.6.1.4.1.485.8.5.2.3.4 |
mfrapPerfMgmtIpICMPInParmProbsThe count of ICMP Parameter Problem messages received
which are addressed to this unit. Same as icmpInParmProbs
in mib-2.ro Counter .1.3.6.1.4.1.485.8.5.2.3.5 |
mfrapPerfMgmtIpICMPInRedirectsThe count of ICMP Redirect messages received which are
addressed to this unit. Same as icmpInRedirects in mib-2.ro Counter .1.3.6.1.4.1.485.8.5.2.3.6 |
mfrapPerfMgmtIpICMPInEchosThe count of ICMP Echo messages received which are
addressed to this unit. Same as icmpInEchos in mib-2.ro Counter .1.3.6.1.4.1.485.8.5.2.3.7 |
mfrapPerfMgmtIpICMPInEchoRepsThe count of ICMP Echo Reply messages received which are
addressed to this unit. Same as icmpInEchoReps in mib-2.ro Counter .1.3.6.1.4.1.485.8.5.2.3.8 |
mfrapPerfMgmtIpICMPOutMsgsThe count of all outgoing ICMP messages originating
from this node. Same as icmpOutMsgs in mib-2.ro Counter .1.3.6.1.4.1.485.8.5.2.3.9 |
mfrapPerfMgmtIpICMPOutErrorsThe count of outgoing ICMP messages generated by this
unit which are not transmitted due problems found by
the ICMP layer. Same as icmpOutErrors in mib-2.ro Counter .1.3.6.1.4.1.485.8.5.2.3.10 |
mfrapPerfMgmtIpICMPOutDestUnreachsThe count of outgoing ICMP Destination Unreachable
messages generated by this unit. Same as
icmpOutDestUnreachs in mib-2.ro Counter .1.3.6.1.4.1.485.8.5.2.3.11 |
mfrapPerfMgmtIpICMPOutParmProbsThe count of outgoing ICMP Parameter Problem messages
generated by this unit. Same as icmpOutParmProbs in mib-2.ro Counter .1.3.6.1.4.1.485.8.5.2.3.12 |
mfrapPerfMgmtIpICMPOutRedirectsThe count of outgoing ICMP Redirect messages generated
by this unit. Same as icmpOutRedirects in mib-2.ro Counter .1.3.6.1.4.1.485.8.5.2.3.13 |
mfrapPerfMgmtIpICMPOutEchosThe count of outgoing ICMP Echo messages generated by this
unit. Same as icmpOutEchos in mib-2.ro Counter .1.3.6.1.4.1.485.8.5.2.3.14 |
mfrapPerfMgmtIpICMPOutEchoRepsThe count of outgoing ICMP Echo Reply messages generated
by this unit. Same as icmpOutEchoReps in mib-2.ro Counter .1.3.6.1.4.1.485.8.5.2.3.15 |
mfrapPerfMgmtIpUDPStatsTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.5.2.4 |
mfrapPerfMgmtIpUDPInDatagramsThe count of all UDP datagrams received that are
addressed as management frames for this unit. Same
as udpInDatagrams in mib-2.ro Counter .1.3.6.1.4.1.485.8.5.2.4.1 |
mfrapPerfMgmtIpUDPOutDatagramsThe count of all UDP datagrams generated by
this unit. Same as udpOutDatagrams in mib-2.ro Counter .1.3.6.1.4.1.485.8.5.2.4.2 |
mfrapPerfMgmtIpUDPNoPortsThe count of all UDP datagrams received that are
addressed as management frames for this unit with
no application at the destination port. Same as
udpNoPorts in mib-2.ro Counter .1.3.6.1.4.1.485.8.5.2.4.3 |
mfrapPerfMgmtIpTCPStatsTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.5.2.5 |
mfrapPerfMgmtIpTCPActiveOpensThe count of the times TCP connections specific to this
unit have made a direct state transition from CLOSED to
SYN-SENT. Same as tcpActiveOpens in mib-2.ro Counter .1.3.6.1.4.1.485.8.5.2.5.1 |
mfrapPerfMgmtIpTCPPassiveOpensThe count of the times TCP connections specific to
this unit have made a direct state transition from
CLOSED to SYN-RCVD. Same as tcpPassiveOpens in mib-2.ro Counter .1.3.6.1.4.1.485.8.5.2.5.2 |
mfrapPerfMgmtIpTCPAttemptFailsThe count of the times TCP connections specific to this unit
have made a direct state transition from SYN-SENT or SYN-RCVD
to CLOSED state, plus the count of the times TCP connections
have made a direct state transition from SYN-RCVD to LISTEN.
Same as tcpAttemptFails in mib-2.ro Counter .1.3.6.1.4.1.485.8.5.2.5.3 |
mfrapPerfMgmtIpTCPCurrEstabThe count of the TCP connections specific to this unit
in state ESTABLISHED or CLOSE-WAIT. Same as tcpCurrEstab
in mib-2.ro Gauge .1.3.6.1.4.1.485.8.5.2.5.4 |
mfrapPerfMgmtIpTCPInSegsThe count of all the segments received that are
addressed as management frames for this unit.
Same as tcpInSegs in mib-2.ro Counter .1.3.6.1.4.1.485.8.5.2.5.5 |
mfrapPerfMgmtIpTCPOutSegsThe count of all the segments generated from this unit.
Same as tcpOutSegs in mib-2.ro Counter .1.3.6.1.4.1.485.8.5.2.5.6 |
mfrapPerfThruput OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.5.3 |
mfrapPerfThruputPerIntfTableThe throughput per interface table. These values are accumulated
across all DLCIs. SEQUENCE OF MfrapPerfThruputPerIntfEntry .1.3.6.1.4.1.485.8.5.3.1 |
mfrapPerfThruputPerIntfEntryAn entry in the throughput per interface table. MfrapPerfThruputPerIntfEntry .1.3.6.1.4.1.485.8.5.3.1.1 |
mfrapPerfThruputPerIntfIndexInterface for which the statistics apply.
(1) DTE interface
(2) T1 interfacero Enumeration .1.3.6.1.4.1.485.8.5.3.1.1.1 |
mfrapPerfThruputPerIntfRxByteCntThe number of bytes that have been counted
on this interface.ro Counter .1.3.6.1.4.1.485.8.5.3.1.1.2 |
mfrapPerfThruputPerIntfTxByteCntThe number of bytes that have been counted
on this interface.ro Counter .1.3.6.1.4.1.485.8.5.3.1.1.3 |
mfrapPerfThruputPerIntfRxFrameCntThe number of frames that have been counted
on this interface.ro Counter .1.3.6.1.4.1.485.8.5.3.1.1.4 |
mfrapPerfThruputPerIntfTxFrameCntThe number of frames that have been counted
on this interface.ro Counter .1.3.6.1.4.1.485.8.5.3.1.1.5 |
mfrapPerfThruputPerIntfRxCrcErrCntThe number of frames with CRC errors received
on this interface.ro Counter .1.3.6.1.4.1.485.8.5.3.1.1.6 |
mfrapPerfThruputPerIntfRxAbortCntThe number of aborted frames received
on this interface.ro Counter .1.3.6.1.4.1.485.8.5.3.1.1.7 |
mfrapPerfThruputPerDlciTableLayer 2 statistics on a per-DLCI basis. Transmit direction
is from DTE to WAN and receive direction is from the WAN
towards the DTE. SEQUENCE OF MfrapPerfThruputPerDlciEntry .1.3.6.1.4.1.485.8.5.3.2 |
mfrapPerfThruputPerDlciEntryThe Statistics for a particular Data Link
Connection Management Interface (DLCI). MfrapPerfThruputPerDlciEntry .1.3.6.1.4.1.485.8.5.3.2.1 |
mfrapPerfThruputPerDlciIndexThis value must be in the range 1-3.
Other than that, this value is ignored as
all three will return the same result.ro Index .1.3.6.1.4.1.485.8.5.3.2.1.1 |
mfrapPerfThruputPerDlciValueThe DLCI value in which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.8.5.3.2.1.2 |
mfrapPerfThruputPerDlciCreateTimeThe amount of time elapsed since this DLCI was first
detected through traffic sensing or in an LMI message
(in seconds).ro INTEGER .1.3.6.1.4.1.485.8.5.3.2.1.3 |
mfrapPerfThruputPerDlciChangeTimeThe amount of elapsed time since this DLCI last
changed state from active to inactive or vice versa
(in seconds).ro INTEGER .1.3.6.1.4.1.485.8.5.3.2.1.4 |
mfrapPerfThruputPerDlciRxByteThe number of bytes that have been received from
the WAN towards the DTE on this DLCI. This count
will include any frames that are terminated by the
unit and do not pass through to the opposite interface
(management and networking data).ro Counter .1.3.6.1.4.1.485.8.5.3.2.1.5 |
mfrapPerfThruputPerDlciTxByteThe number of bytes that have been transmit from the
DTE towards the WAN on this DLCI. This count
will include any frames that are terminated by the
unit and do not pass through to the opposite interface
(management and networking data).ro Counter .1.3.6.1.4.1.485.8.5.3.2.1.6 |
mfrapPerfThruputPerDlciRxFrameThe number of frames that have been received from
the WAN towards to the DTE on this DLCI. This count
will include any frames that are terminated by the
unit and do not pass through to the opposite interface
(management and networking data).ro Counter .1.3.6.1.4.1.485.8.5.3.2.1.7 |
mfrapPerfThruputPerDlciTxFrameThe number of frames that have been transmit from the
DTE towards the WAN on this DLCI. This count
will include any frames that are terminated by the
unit and do not pass through to the opposite interface
(management and networking data).ro Counter .1.3.6.1.4.1.485.8.5.3.2.1.8 |
mfrapPerfThruputPerDlciRxFecnThe number frames received from the WAN towards the DTE
that have had the Forward Explict Congestion Notification
(FECN) bit set on this DLCI. This count will include any
frames that are terminated by the unit and do not pass
through to the opposite interface (management and networking
data).ro Counter .1.3.6.1.4.1.485.8.5.3.2.1.9 |
mfrapPerfThruputPerDlciRxBecnThe number frames received from the WAN towards the DTE
that have had the Backward Explict Congestion Notification
(BECN) bit set on this DLCI. This count will include any
frames that are terminated by the unit and do not pass
through to the opposite interface (management and networking
data).ro Counter .1.3.6.1.4.1.485.8.5.3.2.1.10 |
mfrapPerfThruputPerDlciRxDeThe number frames received from the WAN towards the DTE
that have had the Discard Eligibility (DE) bit set on
this DLCI. This count will include any frames that are
terminated by the unit and do not pass through to the
opposite interface (management and networking data).ro Counter .1.3.6.1.4.1.485.8.5.3.2.1.11 |
mfrapPerfThruputPerDlciTxDeThe number frames transmit towards the WAN from the DTE
that have had the Discard Eligibility (DE) bit set on
this DLCI. This count will include any frames that are
terminated by the unit and do not pass through to the
opposite interface (management and networking data).ro Counter .1.3.6.1.4.1.485.8.5.3.2.1.12 |
mfrapPerfThruputPerDlciRxThruputThe number of bits/sec received from the WAN on this
DLCI. This count will include any frames that are
terminated by the unit and do not pass through to the
opposite interface (management and networking data).ro INTEGER .1.3.6.1.4.1.485.8.5.3.2.1.13 |
mfrapPerfThruputPerDlciTxThruputThe number of bits/sec transmit to the WAN on this
DLCI. This count will include any frames that are
terminated by the unit and do not pass through to
the opposite interface (management and networking data).ro INTEGER .1.3.6.1.4.1.485.8.5.3.2.1.14 |
mfrapPerfThruputPerDlciCIRThe Committed Information Rate (CIR) for this DLCI.
This can come form one of three sources: From the LMI
Full Status Response, configured by the user, or
the DTE line rate (default).ro INTEGER .1.3.6.1.4.1.485.8.5.3.2.1.15 |
mfrapPerfThruputPerDlciUptimeThe total amount of time that the DLCI has been up as
reproted by the LMI Full Status Response (in seconds).ro INTEGER .1.3.6.1.4.1.485.8.5.3.2.1.16 |
mfrapPerfThruputPerDlciDowntimeThe total amount of time that the DLCI has been declared
down (in seconds). A DLCI is Down if it's explicitly
declared Inactive through LMI or if it's missing from the
LMI Full Status message or if there is no Full Status
message at all.ro INTEGER .1.3.6.1.4.1.485.8.5.3.2.1.17 |
mfrapPerfThruputPerDlciCirTypeThe source of the CIR value for this DLCI.
(1) CIR acquired from LMI message. Will override user
configured CIR. This feature is not supported by all
Frame Relay DCE (switches).
(2) CIR configured by user.
(3) CIR is DTE Line Rate. Default if CIR is not set
by one of the other methods.ro Enumeration .1.3.6.1.4.1.485.8.5.3.2.1.18 |
mfrapPerfThruputPerDlciPvcStateThe current state of the DLCI:
(1) DLCI marked active in last full status LMI
(2) DLCI in last full status LMI but not marked active
(3) DLCI has never been seen in a full status LMI
(4) DLCI was seen at least once in a full status LMI
but was not in the last full status LMI
(5) the full status LMI has timed out; all previously
active or inactive DLCIs are changed to this state
(6) DLCI was detected in the traffic stream and a full
status LMI has not been received so the state cannot
be determined yet.ro Enumeration .1.3.6.1.4.1.485.8.5.3.2.1.19 |
mfrapPerfThruputPerDlciOutageCountThe number of times the smperPerfThruputPerDlciPvcState
transitions from pvc-active or pvc-undetermined to one
of the other (inactive) states.ro Counter .1.3.6.1.4.1.485.8.5.3.2.1.20 |
mfrapPerfThruputPerDlciAvailabilityThe measure of the percentage time the DLCI is
available: UpTime/CreateTime or zero if CreateTime
= 0. (in 1/1000 per cent; i.e. availability = 1000
converts to 1%).ro INTEGER .1.3.6.1.4.1.485.8.5.3.2.1.21 |
mfrapPerfThruputPerDlciMTBSOMean Time Between Service Outages: UpTime/OutageCount
or zero if OutageCount = 0 (in seconds).ro INTEGER .1.3.6.1.4.1.485.8.5.3.2.1.22 |
mfrapPerfThruputPerDlciMTTSRMean Time to ServiceRestoral: DownTime/OutageCount
or zero if OutageCount = 0 (in seconds).ro INTEGER .1.3.6.1.4.1.485.8.5.3.2.1.23 |
mfrapPerfThruputPerDlciEncapTypeThe encapsulation protocol seen in the last frame
analyzed on this DLCI:
(1) DLCI is the LMI DLCI or no frames have been
analyzed
(2) The encapsulation is per rfc1490
(3) The encapsulation is per Cisco proprietary
(4) The encapsulation is per Annex-G (X.25 over
frame relay)
(5) The encapsulation is not one of the above.ro Enumeration .1.3.6.1.4.1.485.8.5.3.2.1.24 |
mfrapPerfThruputPerDlciRxUtilizationStatusThe status of the per-DLCI utilization
alarm in the receive direction.
(1) there is no alarm condition; utilization
is under the configured CIR percentage
threshold; if traps are enabled and the
alarm had been previously triggered, a
utilization alarm clear trap will be sent.
(2) the utilization has been over the configured
CIR percentage threshold for less than the
configured duration.
(3) the utilization has been over the configured
CIR percentage threshold for more than the
configured duration; if traps are enabled
a utilization exceeded trap will be sent.
(4) the utilization has been under the configured
CIR percentage threshold for less than the
configured duration.ro Enumeration .1.3.6.1.4.1.485.8.5.3.2.1.25 |
mfrapPerfThruputPerDlciTxUtilizationStatusThe status of the per-DLCI utilization
alarm in the transmit direction.
(1) there is no alarm condition; utilization
is under the configured CIR percentage
threshold; if traps are enabled and the
alarm had been previously triggered, a
utilization alarm clear trap will be sent.
(2) the utilization has been over the configured
CIR percentage threshold for less than the
configured duration.
(3) the utilization has been over the configured
CIR percentage threshold for more than the
configured duration; if traps are enabled
a utilization exceeded trap will be sent.
(4) the utilization has been under the configured
CIR percentage threshold for less than the
configured duration.ro Enumeration .1.3.6.1.4.1.485.8.5.3.2.1.26 |
mfrapPerfThruputPerDlciEIRThe Excess Information Rate. This is defined to
be the maximum rate traffic is (supposed to be)
allowed to burst to.ro INTEGER .1.3.6.1.4.1.485.8.5.3.2.1.27 |
mfrapPerfThruputCommands OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.5.3.3 |
mfrapPerfThruputCmdClearDteStatsAllows the user to zero out all the interface statistics in
the DTE portion of the ThruputPerIntf statistics table.
(1) Clear DTE interface statistics command.rw Enumeration .1.3.6.1.4.1.485.8.5.3.3.1 |
mfrapPerfThruputCmdClearT1StatsAllows the user to zero out all the interface statistics in
the WAN portion of the ThruputPerIntf statistics table.
(1) Clear WAN interface statistics command.rw Enumeration .1.3.6.1.4.1.485.8.5.3.3.2 |
mfrapPerfThruputCmdClearAllIntfStatsAllows the user to zero out all the statistics in
the ThruputPerIntf statistics table.
(1) Clear all interface statistics command.rw Enumeration .1.3.6.1.4.1.485.8.5.3.3.3 |
mfrapPerfThruputCmdClearDlciStatsAllows the user to zero out all the per-DLCI statistics
in the ThruputPerDlci statistics table and the the short
term statistics tables.
(1) Clear layer 2 per-DLCI statistics command.rw Enumeration .1.3.6.1.4.1.485.8.5.3.3.4 |
mfrapPerfThruputCmdClearAllStatsAllows the user to zero out all the statistics
in the ThruputPerIntf and ThruputPerDlci statistics
tables and in the short term statistics tables.
(1) Clear all interface and layer 2 per-DLCI statistics.rw Enumeration .1.3.6.1.4.1.485.8.5.3.3.5 |
mfrapPerfThruputCmdRemoveStsDlciAllows the user to remove a Dlci from the short term
statistics tables.rw INTEGER .1.3.6.1.4.1.485.8.5.3.3.6 |
mfrapPerfThruputCmdReplaceDlciTableAllows the user to replace one DLCI in the short-term
statistics table with another one. SEQUENCE OF MfrapPerfThruputCmdReplaceDlciEntry .1.3.6.1.4.1.485.8.5.3.3.7 |
mfrapPerfThruputCmdReplaceDlciEntryAllows the user to replace one DLCI in the short-term
statistics table with another one. MfrapPerfThruputCmdReplaceDlciEntry .1.3.6.1.4.1.485.8.5.3.3.7.1 |
mfrapPerfThruputCmdReplaceDlciValueA Dlci that is in the short-term stats table. Index by
this Dlci value to identify the statistics entry to be
replaced.ro INTEGER .1.3.6.1.4.1.485.8.5.3.3.7.1.1 |
mfrapPerfThruputCmdReplaceDlciNewValueA Dlci that is to replace another in the short-term stats
table. Index by this Dlci value to identify the statistics
entry to do the replacing.rw INTEGER .1.3.6.1.4.1.485.8.5.3.3.7.1.2 |
mfrapPerfThruputCmdAvailabilityStsDlciResetAllows the user to reset the availability
statistics of an individual Dlci within
the short-term stats table.rw INTEGER .1.3.6.1.4.1.485.8.5.3.3.8 |
mfrapPerfThruputCmdAvailabilityStsDlciResetAllAllows the user to reset the availability
statistics of all Dlci's within the short-term
stats table.rw INTEGER .1.3.6.1.4.1.485.8.5.3.3.9 |
mfrapPerfThruputCmdCountsStsDlciResetAllows the user to reset the count
statistics of an individual Dlci within
the short-term stats table.rw INTEGER .1.3.6.1.4.1.485.8.5.3.3.10 |
mfrapPerfThruputCmdCountsStsDlciResetAllAllows the user to reset the count
statistics of all Dlci's within the short-term
stats table.rw INTEGER .1.3.6.1.4.1.485.8.5.3.3.11 |
mfrapPerfThruputCmdAllStsDlciResetAllows the user to reset both the count
and availability statistics of an individual Dlci within
the short-term stats table.rw INTEGER .1.3.6.1.4.1.485.8.5.3.3.12 |
mfrapPerfThruputCmdAllStsDlciResetAllAllows the user to reset both the count and the
availability statistics of all Dlci's within the short-term
stats table.rw INTEGER .1.3.6.1.4.1.485.8.5.3.3.13 |
mfrapPerfNetworkShortTerm OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.5.4 |
mfrapPerfNetwProtoPerDlciTableThe Short Term Statistics on the Network Layer
protocol for each DLCI. These are protocol-based
per-DLCI statistics. The Short Term model maintains
three intervals: current, previous, and cumulative
totals. Interval duration is defined by the Short Term
Timer (CfgFrPerfTimersSTInterval). SEQUENCE OF MfrapPerfNetwProtoPerDlciEntry .1.3.6.1.4.1.485.8.5.4.1 |
mfrapPerfNetwProtoPerDlciEntryThe Network Layer Short Term Statistics
for a particular DLCI. This table organizes
statistics by high-layer network protocol. MfrapPerfNetwProtoPerDlciEntry .1.3.6.1.4.1.485.8.5.4.1.1 |
mfrapPerfNetwProtoPerDlciIntervalThe Short Term statistics model maintains three
intervals: current, previous, and cumulative totals.
Interval duration is defined by the Short Term Timer
(CfgFrPerfTimersSTInterval).
(1) Currently active short term interval
(2) Previously completed short term interval
(3) Cumulative total since last cleared.ro Enumeration .1.3.6.1.4.1.485.8.5.4.1.1.1 |
mfrapPerfNetwProtoPerDlciValueThe DLCI value with which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.8.5.4.1.1.2 |
mfrapPerfNetwProtoPerDlciRxTotalThe total number of received Network Layer bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.1.1.3 |
mfrapPerfNetwProtoPerDlciTxTotalThe total number of transmitted Network Layer bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.1.1.4 |
mfrapPerfNetwProtoPerDlciRxIpThe number of received IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.1.1.5 |
mfrapPerfNetwProtoPerDlciTxIpThe number of transmitted IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.1.1.6 |
mfrapPerfNetwProtoPerDlciRxIpxThe number of received IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.1.1.7 |
mfrapPerfNetwProtoPerDlciTxIpxThe number of transmitted IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.1.1.8 |
mfrapPerfNetwProtoPerDlciRxSnaThe number of received SNA bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.1.1.9 |
mfrapPerfNetwProtoPerDlciTxSnaThe number of transmitted SNA bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.1.1.10 |
mfrapPerfNetwProtoPerDlciRxArpThe number of received ARP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.1.1.11 |
mfrapPerfNetwProtoPerDlciTxArpThe number of transmitted ARP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.1.1.12 |
mfrapPerfNetwProtoPerDlciRxCiscoThe number of received Cisco protocol bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.1.1.13 |
mfrapPerfNetwProtoPerDlciTxCiscoThe number of transmitted Cisco protocol bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.1.1.14 |
mfrapPerfNetwProtoPerDlciRxOtherThe number of received bytes on this DLCI
from protocols that are not counted elsewhere
in this table.ro Counter .1.3.6.1.4.1.485.8.5.4.1.1.15 |
mfrapPerfNetwProtoPerDlciTxOtherThe number of transmitted bytes on this DLCI
from protocols that are not counted elsewhere
in this table.ro Counter .1.3.6.1.4.1.485.8.5.4.1.1.16 |
mfrapPerfNetwProtoPerDlciRxVnipThe number of received VNIP protocol bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.1.1.17 |
mfrapPerfNetwProtoPerDlciTxVnipThe number of transmitted VNIP protocol bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.1.1.18 |
mfrapPerfNetwProtoPerDlciRxAnnexGThe number of received Annex G protocol
bytes that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.1.1.19 |
mfrapPerfNetwProtoPerDlciTxAnnexGThe number of transmitted Annex G protocol
bytes that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.1.1.20 |
mfrapPerfNetwProtoTotalTableThe Short Term Statistics on Network Layer
protocols summed across all DLCIs. SEQUENCE OF MfrapPerfNetwProtoTotalEntry .1.3.6.1.4.1.485.8.5.4.2 |
mfrapPerfNetwProtoTotalEntryThe Network Layer Short Term Statistics
for a particular DLCI. MfrapPerfNetwProtoTotalEntry .1.3.6.1.4.1.485.8.5.4.2.1 |
mfrapPerfNetwProtoTotalIntervalThe Short Term statistics model maintains three
intervals: current, previous, and cumulative totals.
Interval duration is defined by the Short Term Timer
(CfgFrPerfTimersSTInterval).
(1) Currently active short term interval
(2) Previously completed short term interval
(3) Cumulative total since last cleared.ro Enumeration .1.3.6.1.4.1.485.8.5.4.2.1.1 |
mfrapPerfNetwProtoTotalRxTotalThe total number of received Network Layer bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.2.1.3 |
mfrapPerfNetwProtoTotalTxTotalThe total number of transmitted Network Layer bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.2.1.4 |
mfrapPerfNetwProtoTotalRxIpThe number of received IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.2.1.5 |
mfrapPerfNetwProtoTotalTxIpThe number of transmitted IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.2.1.6 |
mfrapPerfNetwProtoTotalRxIpxThe number of received IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.2.1.7 |
mfrapPerfNetwProtoTotalTxIpxThe number of transmitted IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.2.1.8 |
mfrapPerfNetwProtoTotalRxSnaThe number of received SNA bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.2.1.9 |
mfrapPerfNetwProtoTotalTxSnaThe number of transmitted SNA bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.2.1.10 |
mfrapPerfNetwProtoTotalRxArpThe number of received ARP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.2.1.11 |
mfrapPerfNetwProtoTotalTxArpThe number of transmitted ARP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.2.1.12 |
mfrapPerfNetwProtoTotalRxCiscoThe number of received Cisco protocol bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.2.1.13 |
mfrapPerfNetwProtoTotalTxCiscoThe number of transmitted Cisco protocol bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.2.1.14 |
mfrapPerfNetwProtoTotalRxOtherThe number of received bytes on this DLCI
from protocols that are not counted elsewhere
in this table.ro Counter .1.3.6.1.4.1.485.8.5.4.2.1.15 |
mfrapPerfNetwProtoTotalTxOtherThe number of transmitted bytes on this DLCI
from protocols that are not counted elsewhere
in this table.ro Counter .1.3.6.1.4.1.485.8.5.4.2.1.16 |
mfrapPerfNetwProtoTotalRxVnipThe number of received VNIP protocol bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.2.1.17 |
mfrapPerfNetwProtoTotalTxVnipThe number of transmitted VNIP protocol bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.2.1.18 |
mfrapPerfNetwProtoTotalRxAnnexGThe number of received Annex G protocol bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.2.1.19 |
mfrapPerfNetwProtoTotalTxAnnexGThe number of transmitted Annex G protocol bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.2.1.20 |
mfrapPerfIpPerDlciTableThe Short Term Statistics on the IP
protocol for each DLCI. SEQUENCE OF MfrapPerfIpPerDlciEntry .1.3.6.1.4.1.485.8.5.4.3 |
mfrapPerfIpPerDlciEntryThe IP Short Term Statistics for a particular DLCI. MfrapPerfIpPerDlciEntry .1.3.6.1.4.1.485.8.5.4.3.1 |
mfrapPerfIpPerDlciIntervalThe Short Term statistics model maintains three
intervals: current, previous, and cumulative totals.
Interval duration is defined by the Short Term Timer
(CfgFrPerfTimersSTInterval).
(1) Currently active short term interval
(2) Previously completed short term interval
(3) Cumulative total since last cleared.ro Enumeration .1.3.6.1.4.1.485.8.5.4.3.1.1 |
mfrapPerfIpPerDlciValueThe DLCI value with which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.8.5.4.3.1.2 |
mfrapPerfIpPerDlciRxTotalThe total number of received IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.3.1.3 |
mfrapPerfIpPerDlciTxTotalThe total number of transmitted IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.3.1.4 |
mfrapPerfIpPerDlciRxTcpThe number of received TCP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.3.1.5 |
mfrapPerfIpPerDlciTxTcpThe number of transmitted TCP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.3.1.6 |
mfrapPerfIpPerDlciRxUdpThe number of received UDP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.3.1.7 |
mfrapPerfIpPerDlciTxUdpThe number of transmitted UDP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.3.1.8 |
mfrapPerfIpPerDlciRxIcmpThe number of received ICMP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.3.1.9 |
mfrapPerfIpPerDlciTxIcmpThe number of transmitted ICMP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.3.1.10 |
mfrapPerfIpPerDlciRxOtherThe number of received bytes on this DLCI
from protocols over IP that are not counted
elsewhere in this table.ro Counter .1.3.6.1.4.1.485.8.5.4.3.1.11 |
mfrapPerfIpPerDlciTxOtherThe number of transmitted bytes on this DLCI
from protocols over IP that are not counted
elsewhere in this table.ro Counter .1.3.6.1.4.1.485.8.5.4.3.1.12 |
mfrapPerfIpPerDlciRxIgrpThe number of received IGRP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.3.1.13 |
mfrapPerfIpPerDlciTxIgrpThe number of transmitted IGRP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.3.1.14 |
mfrapPerfIpTotalTableThe Short Term Statistics on the IP
protocol for each DLCI. SEQUENCE OF MfrapPerfIpTotalEntry .1.3.6.1.4.1.485.8.5.4.4 |
mfrapPerfIpTotalEntryThe IP Short Term Statistics for a particular DLCI. MfrapPerfIpTotalEntry .1.3.6.1.4.1.485.8.5.4.4.1 |
mfrapPerfIpTotalIntervalThe Short Term statistics model maintains three
intervals: current, previous, and cumulative totals.
Interval duration is defined by the Short Term Timer
(CfgFrPerfTimersSTInterval).
(1) Currently active short term interval
(2) Previously completed short term interval
(3) Cumulative total since last cleared.ro Enumeration .1.3.6.1.4.1.485.8.5.4.4.1.1 |
mfrapPerfIpTotalRxTotalThe total number of received IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.4.1.3 |
mfrapPerfIpTotalTxTotalThe total number of transmitted IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.4.1.4 |
mfrapPerfIpTotalRxTcpThe number of received TCP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.4.1.5 |
mfrapPerfIpTotalTxTcpThe number of transmitted TCP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.4.1.6 |
mfrapPerfIpTotalRxUdpThe number of received UDP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.4.1.7 |
mfrapPerfIpTotalTxUdpThe number of transmitted UDP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.4.1.8 |
mfrapPerfIpTotalRxIcmpThe number of received ICMP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.4.1.9 |
mfrapPerfIpTotalTxIcmpThe number of transmitted ICMP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.4.1.10 |
mfrapPerfIpTotalRxOtherThe number of received bytes on this DLCI
from protocols over IP that are not counted
elsewhere in this table.ro Counter .1.3.6.1.4.1.485.8.5.4.4.1.11 |
mfrapPerfIpTotalTxOtherThe number of transmitted bytes on this DLCI
from protocols over IP that are not counted
elsewhere in this table.ro Counter .1.3.6.1.4.1.485.8.5.4.4.1.12 |
mfrapPerfIpTotalRxIgrpThe number of received IGRP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.4.1.13 |
mfrapPerfIpTotalTxIgrpThe number of transmitted IGRP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.4.1.14 |
mfrapPerfIcmpPerDlciTableShort Term Statistics on the ICMP
protocol for each DLCI. SEQUENCE OF MfrapPerfIcmpPerDlciEntry .1.3.6.1.4.1.485.8.5.4.5 |
mfrapPerfIcmpPerDlciEntryThe ICMP Short Term Statistics for a particular DLCI. MfrapPerfIcmpPerDlciEntry .1.3.6.1.4.1.485.8.5.4.5.1 |
mfrapPerfIcmpPerDlciIntervalThe Short Term statistics model maintains three
intervals: current, previous, and cumulative totals.
Interval duration is defined by the Short Term Timer
(CfgFrPerfTimersSTInterval).
(1) Currently active short term interval
(2) Previously completed short term interval
(3) Cumulative total since last cleared.ro Enumeration .1.3.6.1.4.1.485.8.5.4.5.1.1 |
mfrapPerfIcmpPerDlciValueThe DLCI value in which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.8.5.4.5.1.2 |
mfrapPerfIcmpPerDlciRxTotalThe total number of ICMP bytes that have been
counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.5.1.3 |
mfrapPerfIcmpPerDlciTxTotalThe total number of ICMP bytes that have been
counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.5.1.4 |
mfrapPerfIcmpPerDlciRxEchoRepThe number of bytes in ICMP ECHO repies
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.5.1.5 |
mfrapPerfIcmpPerDlciTxEchoRepThe number of bytes in ICMP ECHO repies
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.5.1.6 |
mfrapPerfIcmpPerDlciRxDestUnrThe number of bytes in ICMP destination unreachables
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.5.1.7 |
mfrapPerfIcmpPerDlciTxDestUnrThe number of bytes in ICMP destination unreachables
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.5.1.8 |
mfrapPerfIcmpPerDlciRxSrcQuenchThe number of bytes in ICMP source quenches
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.5.1.9 |
mfrapPerfIcmpPerDlciTxSrcQuenchThe number of bytes in ICMP source quenches
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.5.1.10 |
mfrapPerfIcmpPerDlciRxRedirectThe number of bytes in ICMP redirects
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.5.1.11 |
mfrapPerfIcmpPerDlciTxRedirectThe number of bytes in ICMP redirects
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.5.1.12 |
mfrapPerfIcmpPerDlciRxEchoReqThe number of bytes in ICMP ECHO requests
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.5.1.13 |
mfrapPerfIcmpPerDlciTxEchoReqThe number of bytes in ICMP ECHO requests
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.5.1.14 |
mfrapPerfIcmpPerDlciRxTimeExcdThe number of bytes in ICMP time exceededs
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.5.1.15 |
mfrapPerfIcmpPerDlciTxTimeExcdThe number of bytes in ICMP time exceededs
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.5.1.16 |
mfrapPerfIcmpPerDlciRxParamProbThe number of bytes in ICMP parameter problems
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.5.1.17 |
mfrapPerfIcmpPerDlciTxParamProbThe number of bytes in ICMP parameter problems
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.5.1.18 |
mfrapPerfIcmpPerDlciRxTimestpReqThe number of bytes in ICMP timestamp requests
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.5.1.19 |
mfrapPerfIcmpPerDlciTxTimestpReqThe number of bytes in ICMP timestamp requests
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.5.1.20 |
mfrapPerfIcmpPerDlciRxTimestpRepThe number of bytes in ICMP timestamp replies
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.5.1.21 |
mfrapPerfIcmpPerDlciTxTimestpRepThe number of bytes in ICMP timestamp replies
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.5.1.22 |
mfrapPerfIcmpPerDlciRxAddrMaskReqThe number of bytes in ICMP address mask requests
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.5.1.23 |
mfrapPerfIcmpPerDlciTxAddrMaskReqThe number of bytes in ICMP address mask requests
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.5.1.24 |
mfrapPerfIcmpPerDlciRxAddrMaskRepThe number of bytes in ICMP address mask replies
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.5.1.25 |
mfrapPerfIcmpPerDlciTxAddrMaskRepThe number of bytes in ICMP address mask replies
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.5.1.26 |
mfrapPerfIcmpPerDlciRxPktTooBigThe number of bytes in ICMP packet too bigs
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.5.1.27 |
mfrapPerfIcmpPerDlciTxPktTooBigThe number of bytes in ICMP packet too bigs
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.5.1.28 |
mfrapPerfIcmpPerDlciRxGmQueryThe number of bytes in ICMP group membership
queries that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.5.1.29 |
mfrapPerfIcmpPerDlciTxGmQueryThe number of bytes in ICMP group membership
queries that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.5.1.30 |
mfrapPerfIcmpPerDlciRxGmReportThe number of bytes in ICMP group membership
reports that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.5.1.31 |
mfrapPerfIcmpPerDlciTxGmReportThe number of bytes in ICMP group membership
reports that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.5.1.32 |
mfrapPerfIcmpPerDlciRxGmReductThe number of bytes in ICMP group membership
reductions that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.5.1.33 |
mfrapPerfIcmpPerDlciTxGmReductThe number of bytes in ICMP group membership
reductions that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.5.1.34 |
mfrapPerfIcmpTotalTableShort Term Statistics on the ICMP
protocol for each DLCI. SEQUENCE OF MfrapPerfIcmpTotalEntry .1.3.6.1.4.1.485.8.5.4.6 |
mfrapPerfIcmpTotalEntryThe ICMP Short Term Statistics for a particular DLCI. MfrapPerfIcmpTotalEntry .1.3.6.1.4.1.485.8.5.4.6.1 |
mfrapPerfIcmpTotalIntervalThe Short Term statistics model maintains three
intervals: current, previous, and cumulative totals.
Interval duration is defined by the Short Term Timer
(CfgFrPerfTimersSTInterval).
(1) Currently active short term interval
(2) Previously completed short term interval
(3) Cumulative total since last cleared.ro Enumeration .1.3.6.1.4.1.485.8.5.4.6.1.1 |
mfrapPerfIcmpTotalRxTotalThe total number of ICMP bytes that have been
counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.6.1.3 |
mfrapPerfIcmpTotalTxTotalThe total number of ICMP bytes that have been
counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.6.1.4 |
mfrapPerfIcmpTotalRxEchoRepThe number of bytes in ICMP ECHO repies
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.6.1.5 |
mfrapPerfIcmpTotalTxEchoRepThe number of bytes in ICMP ECHO repies
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.6.1.6 |
mfrapPerfIcmpTotalRxDestUnrThe number of bytes in ICMP destination unreachables
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.6.1.7 |
mfrapPerfIcmpTotalTxDestUnrThe number of bytes in ICMP destination unreachables
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.6.1.8 |
mfrapPerfIcmpTotalRxSrcQuenchThe number of bytes in ICMP source quenches
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.6.1.9 |
mfrapPerfIcmpTotalTxSrcQuenchThe number of bytes in ICMP source quenches
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.6.1.10 |
mfrapPerfIcmpTotalRxRedirectThe number of bytes in ICMP redirects
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.6.1.11 |
mfrapPerfIcmpTotalTxRedirectThe number of bytes in ICMP redirects
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.6.1.12 |
mfrapPerfIcmpTotalRxEchoReqThe number of bytes in ICMP ECHO requests
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.6.1.13 |
mfrapPerfIcmpTotalTxEchoReqThe number of bytes in ICMP ECHO requests
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.6.1.14 |
mfrapPerfIcmpTotalRxTimeExcdThe number of bytes in ICMP time exceededs
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.6.1.15 |
mfrapPerfIcmpTotalTxTimeExcdThe number of bytes in ICMP time exceededs
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.6.1.16 |
mfrapPerfIcmpTotalRxParamProbThe number of bytes in ICMP parameter problems
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.6.1.17 |
mfrapPerfIcmpTotalTxParamProbThe number of bytes in ICMP parameter problems
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.6.1.18 |
mfrapPerfIcmpTotalRxTimestpReqThe number of bytes in ICMP timestamp requests
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.6.1.19 |
mfrapPerfIcmpTotalTxTimestpReqThe number of bytes in ICMP timestamp requests
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.6.1.20 |
mfrapPerfIcmpTotalRxTimestpRepThe number of bytes in ICMP timestamp replies
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.6.1.21 |
mfrapPerfIcmpTotalTxTimestpRepThe number of bytes in ICMP timestamp replies
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.6.1.22 |
mfrapPerfIcmpTotalRxAddrMaskReqThe number of bytes in ICMP address mask requests
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.6.1.23 |
mfrapPerfIcmpTotalTxAddrMaskReqThe number of bytes in ICMP address mask requests
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.6.1.24 |
mfrapPerfIcmpTotalRxAddrMaskRepThe number of bytes in ICMP address mask replies
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.6.1.25 |
mfrapPerfIcmpTotalTxAddrMaskRepThe number of bytes in ICMP address mask replies
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.6.1.26 |
mfrapPerfIcmpTotalRxPktTooBigThe number of bytes in ICMP packet too bigs
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.6.1.27 |
mfrapPerfIcmpTotalTxPktTooBigThe number of bytes in ICMP packet too bigs
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.6.1.28 |
mfrapPerfIcmpTotalRxGmQueryThe number of bytes in ICMP group membership
queries that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.6.1.29 |
mfrapPerfIcmpTotalTxGmQueryThe number of bytes in ICMP group membership
queries that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.6.1.30 |
mfrapPerfIcmpTotalRxGmReportThe number of bytes in ICMP group membership
reports that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.6.1.31 |
mfrapPerfIcmpTotalTxGmReportThe number of bytes in ICMP group membership
reports that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.6.1.32 |
mfrapPerfIcmpTotalRxGmReductThe number of bytes in ICMP group membership
reductions that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.6.1.33 |
mfrapPerfIcmpTotalTxGmReductThe number of bytes in ICMP group membership
reductions that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.6.1.34 |
mfrapPerfApplicationPerDlciTableThe Short Term Statistics on the Application
protocol for each DLCI. SEQUENCE OF MfrapPerfApplicationPerDlciEntry .1.3.6.1.4.1.485.8.5.4.7 |
mfrapPerfApplicationPerDlciEntryThe Application Short Term Statistics for a particular DLCI. MfrapPerfApplicationPerDlciEntry .1.3.6.1.4.1.485.8.5.4.7.1 |
mfrapPerfApplicationPerDlciIntervalThe Short Term statistics model maintains three
intervals: current, previous, and cumulative totals.
Interval duration is defined by the Short Term Timer
(CfgFrPerfTimersSTInterval).
(1) Currently active short term interval
(2) Previously completed short term interval
(3) Cumulative total since last cleared.ro Enumeration .1.3.6.1.4.1.485.8.5.4.7.1.1 |
mfrapPerfApplicationPerDlciValueThe DLCI value with which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.8.5.4.7.1.2 |
mfrapPerfApplicationPerDlciRxSnmpThe number of received SNMP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.7.1.3 |
mfrapPerfApplicationPerDlciTxSnmpThe number of transmitted SNMP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.7.1.4 |
mfrapPerfApplicationPerDlciRxSnmpTrapThe number of received SNMP TRAP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.7.1.5 |
mfrapPerfApplicationPerDlciTxSnmpTrapThe number of transmitted SNMP TRAP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.7.1.6 |
mfrapPerfApplicationPerDlciRxHttpThe number of received HTTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.7.1.7 |
mfrapPerfApplicationPerDlciTxHttpThe number of transmitted HTTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.7.1.8 |
mfrapPerfApplicationPerDlciRxTelnetThe number of received Telnet bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.7.1.9 |
mfrapPerfApplicationPerDlciTxTelnetThe number of transmitted Telnet bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.7.1.10 |
mfrapPerfApplicationPerDlciRxSmtpThe number of received SMTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.7.1.11 |
mfrapPerfApplicationPerDlciTxSmtpThe number of transmitted SMTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.7.1.12 |
mfrapPerfApplicationPerDlciRxFtpThe number of received FTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.7.1.13 |
mfrapPerfApplicationPerDlciTxFtpThe number of transmitted FTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.7.1.14 |
mfrapPerfApplicationPerDlciRxTftpThe number of received TFTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.7.1.15 |
mfrapPerfApplicationPerDlciTxTftpThe number of transmitted TFTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.7.1.16 |
mfrapPerfApplicationPerDlciRxCustom1The number of received bytes of
User Defined Protocol #1 that have
been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.7.1.17 |
mfrapPerfApplicationPerDlciTxCustom1The number of transmitted bytes of
User Defined Protocol #1 that have
been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.7.1.18 |
mfrapPerfApplicationPerDlciRxCustom2The number of received bytes of
User Defined Protocol #2 that have
been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.7.1.19 |
mfrapPerfApplicationPerDlciTxCustom2The number of transmitted bytes of
User Defined Protocol #2 that have
been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.7.1.20 |
mfrapPerfApplicationPerDlciRxCustom3The number of received bytes of
User Defined Protocol #3 that have
been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.7.1.21 |
mfrapPerfApplicationPerDlciTxCustom3The number of transmitted bytes of
User Defined Protocol #3 that have
been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.7.1.22 |
mfrapPerfApplicationPerDlciRxCustom4The number of received bytes of
User Defined Protocol #4 that have
been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.7.1.23 |
mfrapPerfApplicationPerDlciTxCustom4The number of transmitted bytes of
User Defined Protocol #4 that have
been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.7.1.24 |
mfrapPerfApplicationTotalTableThe Short Term Statistics on the Application
protocol for each DLCI. SEQUENCE OF MfrapPerfApplicationTotalEntry .1.3.6.1.4.1.485.8.5.4.8 |
mfrapPerfApplicationTotalEntryThe Application Short Term Statistics for a particular DLCI. MfrapPerfApplicationTotalEntry .1.3.6.1.4.1.485.8.5.4.8.1 |
mfrapPerfApplicationTotalIntervalThe Short Term statistics model maintains three
intervals: current, previous, and cumulative totals.
Interval duration is defined by the Short Term Timer
(CfgFrPerfTimersSTInterval).
(1) Currently active short term interval
(2) Previously completed short term interval
(3) Cumulative total since last cleared.ro Enumeration .1.3.6.1.4.1.485.8.5.4.8.1.1 |
mfrapPerfApplicationTotalRxSnmpThe number of received SNMP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.8.1.3 |
mfrapPerfApplicationTotalTxSnmpThe number of transmitted SNMP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.8.1.4 |
mfrapPerfApplicationTotalRxSnmpTrapThe number of received SNMP TRAP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.8.1.5 |
mfrapPerfApplicationTotalTxSnmpTrapThe number of transmitted SNMP TRAP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.8.1.6 |
mfrapPerfApplicationTotalRxHttpThe number of received HTTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.8.1.7 |
mfrapPerfApplicationTotalTxHttpThe number of transmitted HTTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.8.1.8 |
mfrapPerfApplicationTotalRxTelnetThe number of received Telnet bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.8.1.9 |
mfrapPerfApplicationTotalTxTelnetThe number of transmitted Telnet bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.8.1.10 |
mfrapPerfApplicationTotalRxSmtpThe number of received SMTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.8.1.11 |
mfrapPerfApplicationTotalTxSmtpThe number of transmitted SMTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.8.1.12 |
mfrapPerfApplicationTotalRxFtpThe number of received FTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.8.1.13 |
mfrapPerfApplicationTotalTxFtpThe number of transmitted FTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.8.1.14 |
mfrapPerfApplicationTotalRxTftpThe number of received TFTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.8.1.15 |
mfrapPerfApplicationTotalTxTftpThe number of transmitted TFTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.8.1.16 |
mfrapPerfApplicationTotalRxCustom1The number of received bytes of
User Defined Protocol #1 that have
been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.8.1.17 |
mfrapPerfApplicationTotalTxCustom1The number of transmitted bytes of
User Defined Protocol #1 that have
been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.8.1.18 |
mfrapPerfApplicationTotalRxCustom2The number of received bytes of
User Defined Protocol #2 that have
been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.8.1.19 |
mfrapPerfApplicationTotalTxCustom2The number of transmitted bytes of
User Defined Protocol #2 that have
been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.8.1.20 |
mfrapPerfApplicationTotalRxCustom3The number of received bytes of
User Defined Protocol #3 that have
been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.8.1.21 |
mfrapPerfApplicationTotalTxCustom3The number of transmitted bytes of
User Defined Protocol #3 that have
been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.8.1.22 |
mfrapPerfApplicationTotalRxCustom4The number of received bytes of
User Defined Protocol #4 that have
been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.8.1.23 |
mfrapPerfApplicationTotalTxCustom4The number of transmitted bytes of
User Defined Protocol #4 that have
been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.8.1.24 |
mfrapPerfRoutingPerDlciTableThe Short Term Statistics on the Routing
protocol for each DLCI. SEQUENCE OF MfrapPerfRoutingPerDlciEntry .1.3.6.1.4.1.485.8.5.4.9 |
mfrapPerfRoutingPerDlciEntryThe Routing Short Term Statistics for a particular DLCI. MfrapPerfRoutingPerDlciEntry .1.3.6.1.4.1.485.8.5.4.9.1 |
mfrapPerfRoutingPerDlciIntervalThe Short Term statistics model maintains three
intervals: current, previous, and cumulative totals.
Interval duration is defined by the Short Term Timer
(CfgFrPerfTimersSTInterval).
(1) Currently active short term interval
(2) Previously completed short term interval
(3) Cumulative total since last cleared.ro Enumeration .1.3.6.1.4.1.485.8.5.4.9.1.1 |
mfrapPerfRoutingPerDlciValueThe DLCI value with which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.8.5.4.9.1.2 |
mfrapPerfRoutingPerDlciRxOspfThe number of received OSPF bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.9.1.3 |
mfrapPerfRoutingPerDlciTxOspfThe number of transmitted OSPF bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.9.1.4 |
mfrapPerfRoutingPerDlciRxRipThe number of received RIP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.9.1.5 |
mfrapPerfRoutingPerDlciTxRipThe number of transmitted RIP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.9.1.6 |
mfrapPerfRoutingPerDlciRxNetbiosThe number of received Netbios bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.9.1.7 |
mfrapPerfRoutingPerDlciTxNetbiosThe number of transmitted Netbios bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.9.1.8 |
mfrapPerfRoutingTotalTableThe Short Term Statistics on the Routing
protocol for each DLCI. SEQUENCE OF MfrapPerfRoutingTotalEntry .1.3.6.1.4.1.485.8.5.4.10 |
mfrapPerfRoutingTotalEntryThe Routing Short Term Statistics for a particular DLCI. MfrapPerfRoutingTotalEntry .1.3.6.1.4.1.485.8.5.4.10.1 |
mfrapPerfRoutingTotalIntervalThe Short Term statistics model maintains three
intervals: current, previous, and cumulative totals.
Interval duration is defined by the Short Term Timer
(CfgFrPerfTimersSTInterval).
(1) Currently active short term interval
(2) Previously completed short term interval
(3) Cumulative total since last cleared.ro Enumeration .1.3.6.1.4.1.485.8.5.4.10.1.1 |
mfrapPerfRoutingTotalRxOspfThe number of received OSPF bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.10.1.3 |
mfrapPerfRoutingTotalTxOspfThe number of transmitted OSPF bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.10.1.4 |
mfrapPerfRoutingTotalRxRipThe number of received RIP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.10.1.5 |
mfrapPerfRoutingTotalTxRipThe number of transmitted RIP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.10.1.6 |
mfrapPerfRoutingTotalRxNetbiosThe number of received Netbios bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.10.1.7 |
mfrapPerfRoutingTotalTxNetbiosThe number of transmitted Netbios bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.10.1.8 |
mfrapPerfIpxPerDlciTableShort Term Statistics on the IPX
protocol for each DLCI. SEQUENCE OF MfrapPerfIpxPerDlciEntry .1.3.6.1.4.1.485.8.5.4.11 |
mfrapPerfIpxPerDlciEntryThe IPX Short Term Statistics for a particular DLCI. MfrapPerfIpxPerDlciEntry .1.3.6.1.4.1.485.8.5.4.11.1 |
mfrapPerfIpxPerDlciIntervalThe Short Term statistics model maintains three
intervals: current, previous, and cumulative totals.
Interval duration is defined by the Short Term Timer
(CfgFrPerfTimersSTInterval).
(1) Currently active short term interval
(2) Previously completed short term interval
(3) Cumulative total since last cleared.ro Enumeration .1.3.6.1.4.1.485.8.5.4.11.1.1 |
mfrapPerfIpxPerDlciValueThe DLCI value in which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.8.5.4.11.1.2 |
mfrapPerfIpxPerDlciRxTotalThe total number of IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.11.1.3 |
mfrapPerfIpxPerDlciTxTotalThe total number of IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.11.1.4 |
mfrapPerfIpxPerDlciRxSpxThe number of SPX over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.11.1.5 |
mfrapPerfIpxPerDlciTxSpxThe number of SPX over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.11.1.6 |
mfrapPerfIpxPerDlciRxNcpThe number of NCP over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.11.1.7 |
mfrapPerfIpxPerDlciTxNcpThe number of NCP over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.11.1.8 |
mfrapPerfIpxPerDlciRxSapThe number of SAP over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.11.1.9 |
mfrapPerfIpxPerDlciTxSapThe number of SAP over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.11.1.10 |
mfrapPerfIpxPerDlciRxRipThe number of RIP over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.11.1.11 |
mfrapPerfIpxPerDlciTxRipThe number of RIP over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.11.1.12 |
mfrapPerfIpxPerDlciRxNetbiosThe number of NETBIOS over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.11.1.13 |
mfrapPerfIpxPerDlciTxNetbiosThe number of NETBIOS over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.11.1.14 |
mfrapPerfIpxPerDlciRxOtherThe number of received bytes on this DLCI
from protocols over IPX that are not counted
elsewhere in this table.ro Counter .1.3.6.1.4.1.485.8.5.4.11.1.15 |
mfrapPerfIpxPerDlciTxOtherThe number of transmitted bytes on this DLCI
from protocols over IPX that are not counted
elsewhere in this table.ro Counter .1.3.6.1.4.1.485.8.5.4.11.1.16 |
mfrapPerfIpxTotalTableShort Term Statistics on the IPX
protocol for each DLCI. SEQUENCE OF MfrapPerfIpxTotalEntry .1.3.6.1.4.1.485.8.5.4.12 |
mfrapPerfIpxTotalEntryThe IPX Short Term Statistics for a particular DLCI. MfrapPerfIpxTotalEntry .1.3.6.1.4.1.485.8.5.4.12.1 |
mfrapPerfIpxTotalIntervalThe Short Term statistics model maintains three
intervals: current, previous, and cumulative totals.
Interval duration is defined by the Short Term Timer
(CfgFrPerfTimersSTInterval).
(1) Currently active short term interval
(2) Previously completed short term interval
(3) Cumulative total since last cleared.ro Enumeration .1.3.6.1.4.1.485.8.5.4.12.1.1 |
mfrapPerfIpxTotalRxTotalThe total number of IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.12.1.3 |
mfrapPerfIpxTotalTxTotalThe total number of IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.12.1.4 |
mfrapPerfIpxTotalRxSpxThe number of SPX over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.12.1.5 |
mfrapPerfIpxTotalTxSpxThe number of SPX over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.12.1.6 |
mfrapPerfIpxTotalRxNcpThe number of NCP over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.12.1.7 |
mfrapPerfIpxTotalTxNcpThe number of NCP over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.12.1.8 |
mfrapPerfIpxTotalRxSapThe number of SAP over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.12.1.9 |
mfrapPerfIpxTotalTxSapThe number of SAP over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.12.1.10 |
mfrapPerfIpxTotalRxRipThe number of RIP over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.12.1.11 |
mfrapPerfIpxTotalTxRipThe number of RIP over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.12.1.12 |
mfrapPerfIpxTotalRxNetbiosThe number of NETBIOS over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.12.1.13 |
mfrapPerfIpxTotalTxNetbiosThe number of NETBIOS over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.12.1.14 |
mfrapPerfIpxTotalRxOtherThe number of received bytes on this DLCI
from protocols over IPX that are not counted
elsewhere in this table.ro Counter .1.3.6.1.4.1.485.8.5.4.12.1.15 |
mfrapPerfIpxTotalTxOtherThe number of transmitted bytes on this DLCI
from protocols over IPX that are not counted
elsewhere in this table.ro Counter .1.3.6.1.4.1.485.8.5.4.12.1.16 |
mfrapPerfSnaPerDlciTableShort Term Statistics on the SNA
protocol for each DLCI. SEQUENCE OF MfrapPerfSnaPerDlciEntry .1.3.6.1.4.1.485.8.5.4.13 |
mfrapPerfSnaPerDlciEntryThe SNA Short Term Statistics for a particular DLCI. MfrapPerfSnaPerDlciEntry .1.3.6.1.4.1.485.8.5.4.13.1 |
mfrapPerfSnaPerDlciIntervalThe Short Term statistics model maintains three
intervals: current, previous, and cumulative totals.
Interval duration is defined by the Short Term Timer
(CfgFrPerfTimersSTInterval).
(1) Currently active short term interval
(2) Previously completed short term interval
(3) Cumulative total since last cleared.ro Enumeration .1.3.6.1.4.1.485.8.5.4.13.1.1 |
mfrapPerfSnaPerDlciValueThe DLCI value in which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.8.5.4.13.1.2 |
mfrapPerfSnaPerDlciRxTotalThe total number of SNA bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.13.1.3 |
mfrapPerfSnaPerDlciTxTotalThe total number of SNA bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.13.1.4 |
mfrapPerfSnaPerDlciRxSubareaThe number of SNA Subarea bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.13.1.5 |
mfrapPerfSnaPerDlciTxSubareaThe number of SNA Subarea bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.13.1.6 |
mfrapPerfSnaPerDlciRxPeriphThe number of SNA Periph bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.13.1.7 |
mfrapPerfSnaPerDlciTxPeriphThe number of SNA Periph bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.13.1.8 |
mfrapPerfSnaPerDlciRxAppnThe number of SNA Appn bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.13.1.9 |
mfrapPerfSnaPerDlciTxAppnThe number of SNA Appn bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.13.1.10 |
mfrapPerfSnaPerDlciRxNetbiosThe number of SNA Netbios bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.13.1.11 |
mfrapPerfSnaPerDlciTxNetbiosThe number of SNA Netbios bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.13.1.12 |
mfrapPerfSnaPerDlciRxOtherThe number of received bytes on this DLCI
from protocols over SNA that are not counted
elsewhere in this table.ro Counter .1.3.6.1.4.1.485.8.5.4.13.1.13 |
mfrapPerfSnaPerDlciTxOtherThe number of transmitted bytes on this DLCI
from protocols over SNA that are not counted
elsewhere in this table.ro Counter .1.3.6.1.4.1.485.8.5.4.13.1.14 |
mfrapPerfSnaTotalTableShort Term Statistics on the SNA
protocol for each DLCI. SEQUENCE OF MfrapPerfSnaTotalEntry .1.3.6.1.4.1.485.8.5.4.14 |
mfrapPerfSnaTotalEntryThe SNA Short Term Statistics for a particular DLCI. MfrapPerfSnaTotalEntry .1.3.6.1.4.1.485.8.5.4.14.1 |
mfrapPerfSnaTotalIntervalThe Short Term statistics model maintains three
intervals: current, previous, and cumulative totals.
Interval duration is defined by the Short Term Timer
(CfgFrPerfTimersSTInterval).
(1) Currently active short term interval
(2) Previously completed short term interval
(3) Cumulative total since last cleared.ro Enumeration .1.3.6.1.4.1.485.8.5.4.14.1.1 |
mfrapPerfSnaTotalRxTotalThe total number of SNA bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.14.1.3 |
mfrapPerfSnaTotalTxTotalThe total number of SNA bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.14.1.4 |
mfrapPerfSnaTotalRxSubareaThe number of SNA Subarea bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.14.1.5 |
mfrapPerfSnaTotalTxSubareaThe number of SNA Subarea bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.14.1.6 |
mfrapPerfSnaTotalRxPeriphThe number of SNA Periph bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.14.1.7 |
mfrapPerfSnaTotalTxPeriphThe number of SNA Periph bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.14.1.8 |
mfrapPerfSnaTotalRxAppnThe number of SNA Appn bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.14.1.9 |
mfrapPerfSnaTotalTxAppnThe number of SNA Appn bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.14.1.10 |
mfrapPerfSnaTotalRxNetbiosThe number of SNA Netbios bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.14.1.11 |
mfrapPerfSnaTotalTxNetbiosThe number of SNA Netbios bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.14.1.12 |
mfrapPerfSnaTotalRxOtherThe number of received bytes on this DLCI
from protocols over SNA that are not counted
elsewhere in this table.ro Counter .1.3.6.1.4.1.485.8.5.4.14.1.13 |
mfrapPerfSnaTotalTxOtherThe number of transmitted bytes on this DLCI
from protocols over SNA that are not counted
elsewhere in this table.ro Counter .1.3.6.1.4.1.485.8.5.4.14.1.14 |
mfrapPerfArpPerDlciTableShort Term Statistics on the ARP
protocol for each DLCI. SEQUENCE OF MfrapPerfArpPerDlciEntry .1.3.6.1.4.1.485.8.5.4.15 |
mfrapPerfArpPerDlciEntryThe ARP Short Term Statistics for a particular DLCI. MfrapPerfArpPerDlciEntry .1.3.6.1.4.1.485.8.5.4.15.1 |
mfrapPerfArpPerDlciIntervalThe Short Term statistics model maintains three
intervals: current, previous, and cumulative totals.
Interval duration is defined by the Short Term Timer
(CfgFrPerfTimersSTInterval).
(1) Currently active short term interval
(2) Previously completed short term interval
(3) Cumulative total since last cleared.ro Enumeration .1.3.6.1.4.1.485.8.5.4.15.1.1 |
mfrapPerfArpPerDlciValueThe DLCI value in which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.8.5.4.15.1.2 |
mfrapPerfArpPerDlciRxTotalThe total number of ARP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.15.1.3 |
mfrapPerfArpPerDlciTxTotalThe total number of ARP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.15.1.4 |
mfrapPerfArpPerDlciRxArpReqThe number of ARP request bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.15.1.5 |
mfrapPerfArpPerDlciTxArpReqThe number of ARP request bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.15.1.6 |
mfrapPerfArpPerDlciRxArpRepThe number of ARP reply bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.15.1.7 |
mfrapPerfArpPerDlciTxArpRepThe number of ARP reply bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.15.1.8 |
mfrapPerfArpPerDlciRxRarpReqThe number of RARP request bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.15.1.9 |
mfrapPerfArpPerDlciTxRarpReqThe number of RARP request bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.15.1.10 |
mfrapPerfArpPerDlciRxRarpRepThe number of RARP reply bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.15.1.11 |
mfrapPerfArpPerDlciTxRarpRepThe number of RARP reply bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.15.1.12 |
mfrapPerfArpPerDlciRxInarpReqThe number of INARP request bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.15.1.13 |
mfrapPerfArpPerDlciTxInarpReqThe number of INARP request bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.15.1.14 |
mfrapPerfArpPerDlciRxInarpRepThe number of INARP reply bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.15.1.15 |
mfrapPerfArpPerDlciTxInarpRepThe number of INARP reply bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.15.1.16 |
mfrapPerfArpPerDlciRxOtherThe number of received bytes on this DLCI
from ARP message types that are not counted
elsewhere in this table.ro Counter .1.3.6.1.4.1.485.8.5.4.15.1.17 |
mfrapPerfArpPerDlciTxOtherThe number of transmitted bytes on this DLCI
from ARP message types that are not counted
elsewhere in this table.ro Counter .1.3.6.1.4.1.485.8.5.4.15.1.18 |
mfrapPerfArpTotalTableShort Term Statistics on the ARP
protocol across all DLCIs. SEQUENCE OF MfrapPerfArpTotalEntry .1.3.6.1.4.1.485.8.5.4.16 |
mfrapPerfArpTotalEntryThe ARP Short Term Statistics for a particular DLCI. MfrapPerfArpTotalEntry .1.3.6.1.4.1.485.8.5.4.16.1 |
mfrapPerfArpTotalIntervalThe Short Term statistics model maintains three
intervals: current, previous, and cumulative totals.
Interval duration is defined by the Short Term Timer
(CfgFrPerfTimersSTInterval).
(1) Currently active short term interval
(2) Previously completed short term interval
(3) Cumulative total since last cleared.ro Enumeration .1.3.6.1.4.1.485.8.5.4.16.1.1 |
mfrapPerfArpTotalRxTotalThe total number of ARP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.16.1.3 |
mfrapPerfArpTotalTxTotalThe total number of ARP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.16.1.4 |
mfrapPerfArpTotalRxArpReqThe number of ARP request bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.16.1.5 |
mfrapPerfArpTotalTxArpReqThe number of ARP request bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.16.1.6 |
mfrapPerfArpTotalRxArpRepThe number of ARP reply bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.16.1.7 |
mfrapPerfArpTotalTxArpRepThe number of ARP reply bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.16.1.8 |
mfrapPerfArpTotalRxRarpReqThe number of RARP request bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.16.1.9 |
mfrapPerfArpTotalTxRarpReqThe number of RARP request bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.16.1.10 |
mfrapPerfArpTotalRxRarpRepThe number of RARP reply bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.16.1.11 |
mfrapPerfArpTotalTxRarpRepThe number of RARP reply bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.16.1.12 |
mfrapPerfArpTotalRxInarpReqThe number of INARP request bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.16.1.13 |
mfrapPerfArpTotalTxInarpReqThe number of INARP request bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.16.1.14 |
mfrapPerfArpTotalRxInarpRepThe number of INARP reply bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.16.1.15 |
mfrapPerfArpTotalTxInarpRepThe number of INARP reply bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.16.1.16 |
mfrapPerfArpTotalRxOtherThe number of received bytes on this DLCI
from ARP message types that are not counted
elsewhere in this table.ro Counter .1.3.6.1.4.1.485.8.5.4.16.1.17 |
mfrapPerfArpTotalTxOtherThe number of transmitted bytes on this DLCI
from ARP message types that are not counted
elsewhere in this table.ro Counter .1.3.6.1.4.1.485.8.5.4.16.1.18 |
mfrapPerfLmiPerDlciTableShort Term Statistics on LMI protocol for each DLCI. SEQUENCE OF MfrapPerfLmiPerDlciEntry .1.3.6.1.4.1.485.8.5.4.17 |
mfrapPerfLmiPerDlciEntryThe LMI Short Term Statistics for a particular DLCI. MfrapPerfLmiPerDlciEntry .1.3.6.1.4.1.485.8.5.4.17.1 |
mfrapPerfLmiPerDlciIntervalThe Short Term statistics model maintains three
intervals: current, previous, and cumulative totals.
Interval duration is defined by the Short Term Timer
(CfgFrPerfTimersSTInterval).
(1) Currently active short term interval
(2) Previously completed short term interval
(3) Cumulative total since last cleared.ro Enumeration .1.3.6.1.4.1.485.8.5.4.17.1.1 |
mfrapPerfLmiPerDlciValueThe DLCI value with which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.8.5.4.17.1.2 |
mfrapPerfLmiPerDlciRxTotalByteCntThe total number of received LMI bytes
counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.17.1.3 |
mfrapPerfLmiPerDlciTxTotalByteCntThe total number of transmitted LMI bytes
counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.17.1.4 |
mfrapPerfLmiPerDlciRxLivoEnqByteCntThe number of bytes received in Link Integrity
Verification Only (LIVO) enquiries on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.17.1.5 |
mfrapPerfLmiPerDlciTxLivoEnqByteCntThe number of bytes transmitted in Link Integrity
Verification Only (LIVO) enquiries on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.17.1.6 |
mfrapPerfLmiPerDlciRxLivoStatByteCntThe number of bytes received in Link Integrity
Verification Only (LIVO) statuses on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.17.1.7 |
mfrapPerfLmiPerDlciTxLivoStatByteCntThe number of bytes transmitted in Link Integrity
Verification Only (LIVO) statuses on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.17.1.8 |
mfrapPerfLmiPerDlciRxFullEnqByteCntThe number of bytes received in
Full Status enquiries on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.17.1.9 |
mfrapPerfLmiPerDlciTxFullEnqByteCntThe number of bytes transmitted in
Full Status enquiries on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.17.1.10 |
mfrapPerfLmiPerDlciRxFullStatByteCntThe number of bytes received in
Full Status messages on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.17.1.11 |
mfrapPerfLmiPerDlciTxFullStatByteCntThe number of bytes transmitted in
Full Status messages on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.17.1.12 |
mfrapPerfLmiPerDlciRxOtherByteCntThe number of received bytes on this DLCI
from LMI protocols that are not counted
elsewhere (other than Total) in this table.ro Counter .1.3.6.1.4.1.485.8.5.4.17.1.13 |
mfrapPerfLmiPerDlciTxOtherByteCntThe number of transmitted bytes on this DLCI
from LMI protocols that are not counted
elsewhere (other than Total) in this table.ro Counter .1.3.6.1.4.1.485.8.5.4.17.1.14 |
mfrapPerfLmiTotalTableShort Term Statistics on LMI protocol across all DLCIs. SEQUENCE OF MfrapPerfLmiTotalEntry .1.3.6.1.4.1.485.8.5.4.18 |
mfrapPerfLmiTotalEntryThe LMI Short Term Statistics across all DLCIs. MfrapPerfLmiTotalEntry .1.3.6.1.4.1.485.8.5.4.18.1 |
mfrapPerfLmiTotalIntervalThe Short Term statistics model maintains three
intervals: current, previous, and cumulative totals.
Interval duration is defined by the Short Term Timer
(CfgFrPerfTimersSTInterval).
(1) Currently active short term interval
(2) Previously completed short term interval
(3) Cumulative total since last cleared.ro Enumeration .1.3.6.1.4.1.485.8.5.4.18.1.1 |
mfrapPerfLmiTotalDlciValueOBSOLETE.ro INTEGER .1.3.6.1.4.1.485.8.5.4.18.1.2 |
mfrapPerfLmiTotalRxTotalByteCntThe total number of received LMI bytes
counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.18.1.3 |
mfrapPerfLmiTotalTxTotalByteCntThe total number of transmitted LMI bytes
counted on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.18.1.4 |
mfrapPerfLmiTotalRxLivoEnqByteCntThe number of bytes received in Link Integrity
Verification Only (LIVO) enquiries on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.18.1.5 |
mfrapPerfLmiTotalTxLivoEnqByteCntThe number of bytes transmitted in Link Integrity
Verification Only (LIVO) enquiries on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.18.1.6 |
mfrapPerfLmiTotalRxLivoStatByteCntThe number of bytes received in Link Integrity
Verification Only (LIVO) statuses on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.18.1.7 |
mfrapPerfLmiTotalTxLivoStatByteCntThe number of bytes transmitted in Link Integrity
Verification Only (LIVO) statuses on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.18.1.8 |
mfrapPerfLmiTotalRxFullEnqByteCntThe number of bytes received in
Full Status enquiries on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.18.1.9 |
mfrapPerfLmiTotalTxFullEnqByteCntThe number of bytes transmitted in
Full Status enquiries on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.18.1.10 |
mfrapPerfLmiTotalRxFullStatByteCntThe number of bytes received in
Full Status messages on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.18.1.11 |
mfrapPerfLmiTotalTxFullStatByteCntThe number of bytes transmitted in
Full Status messages on this DLCI.ro Counter .1.3.6.1.4.1.485.8.5.4.18.1.12 |
mfrapPerfLmiTotalRxOtherByteCntThe number of received bytes on this DLCI
from LMI protocols that are not counted
elsewhere (other than Total) in this table.ro Counter .1.3.6.1.4.1.485.8.5.4.18.1.13 |
mfrapPerfLmiTotalTxOtherByteCntThe number of transmitted bytes on this DLCI
from LMI protocols that are not counted
elsewhere (other than Total) in this table.ro Counter .1.3.6.1.4.1.485.8.5.4.18.1.14 |
mfrapPerfNetworkLongTerm OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.5.5 |
mfrapPerfNetwLongTermTableLong Term Statistics by DLCI, protocol, and interval.
LT statistics are collected on a configurable set
of DLCIs and protocols. There are 96 intervals maintained
each with a duration defined by the Long Term Timer.
Interval 96 is the current window and Interval 1 is
furthest back in time (96xLT Timer seconds ago). SEQUENCE OF MfrapPerfNetwLongTermEntry .1.3.6.1.4.1.485.8.5.5.1 |
mfrapPerfNetwLongTermEntryThe Long Term Statistic for a particular DLCI,
protocol and interval. MfrapPerfNetwLongTermEntry .1.3.6.1.4.1.485.8.5.5.1.1 |
mfrapPerfNetwLongTermDlciThe DLCI monitored for the statistics. The Long
Term DLCI filter must first be configured.ro INTEGER .1.3.6.1.4.1.485.8.5.5.1.1.1 |
mfrapPerfNetwLongTermProtocolThe type of protocol monitored for the statistics.ro Enumeration .1.3.6.1.4.1.485.8.5.5.1.1.2 |
mfrapPerfNetwLongTermIntervalThe time interval in which the value was collected.
Long Term statistis are maintained for 96 intervals
with the interval duration defined by
(CfgFrPerfTimersLTInterval).ro INTEGER .1.3.6.1.4.1.485.8.5.5.1.1.3 |
mfrapPerfNetwLongTermValueThe statistic collected for the given DLCI and protocol
and within the given time interval.ro Counter .1.3.6.1.4.1.485.8.5.5.1.1.4 |
mfrapPerfNetwLongTermAltTableThis is an alternative method to access the database of
long term statistics. The statistics are indexed by DLCI
and protocol and are returned in an OCTETSTRING. SEQUENCE OF MfrapPerfNetwLongTermAltEntry .1.3.6.1.4.1.485.8.5.5.2 |
mfrapPerfNetwLongTermAltEntryThe Long Term Statistic for a particular
DLCI and protocol. MfrapPerfNetwLongTermAltEntry .1.3.6.1.4.1.485.8.5.5.2.1 |
mfrapPerfNetwLongTermAltDlciThe DLCI monitored for the statistics.ro INTEGER .1.3.6.1.4.1.485.8.5.5.2.1.1 |
mfrapPerfNetwLongTermAltProtocolThe protocol monitored for the statistics.ro Enumeration .1.3.6.1.4.1.485.8.5.5.2.1.2 |
mfrapPerfNetwLongTermAltArrayThe statistic collected for the given DLCI and protocol.ro OCTET STRING .1.3.6.1.4.1.485.8.5.5.2.1.3 |
mfrapPerfNetworkLongTermCommands OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.5.5.3 |
mfrapPerfNetworkLongTermCmdClearAllows the user to zero out all the statistics in
the long term statistics tables.
(1) Clear all Long Term statisticsrw Enumeration .1.3.6.1.4.1.485.8.5.5.3.1 |
mfrapPerfCirPercentUtilization OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.5.6 |
mfrapPerfCirPercentUtilizationTableShort Term Statistics on the percentage of CIR used
on each DLCI. Each short term statistics interval,
the count of bytes transmitted and received is used
to calculate the percentage of CIR used. The byte
count is then added to the appropriate bucket for
the CIR percentage range. SEQUENCE OF MfrapPerfCirPercentUtilizationEntry .1.3.6.1.4.1.485.8.5.6.1 |
mfrapPerfCirPercentUtilizationEntryThe CIR Percentage Statistics for a particular DLCI. MfrapPerfCirPercentUtilizationEntry .1.3.6.1.4.1.485.8.5.6.1.1 |
mfrapPerfCirPercentUtilizationIntervalThe Short Term statistics model maintains three
intervals: current, previous, and cumulative totals.
Interval duration is defined by the Short Term Timer
(CfgFrPerfTimersSTInterval).
(1) Currently active short term interval
(2) Previously completed short term interval
(3) Cumulative total since last cleared.ro Enumeration .1.3.6.1.4.1.485.8.5.6.1.1.1 |
mfrapPerfCirPercentUtilizationDlciValueThe DLCI value with which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.8.5.6.1.1.2 |
mfrapPerfCirRxPercentUtilizationRange1The number of short-term intervals during
which rx data throughput on this DLCI compared
to CIR was in range 1 (0% of CIR).ro INTEGER .1.3.6.1.4.1.485.8.5.6.1.1.21 |
mfrapPerfCirRxPercentUtilizationRange2The number of short-term intervals during
which rx data throughput on this DLCI compared
to CIR was in range 2 (1-10% of CIR).ro INTEGER .1.3.6.1.4.1.485.8.5.6.1.1.22 |
mfrapPerfCirRxPercentUtilizationRange3The number of short-term intervals during
which rx data throughput on this DLCI compared
to CIR was in range 3 (11-20% of CIR).ro INTEGER .1.3.6.1.4.1.485.8.5.6.1.1.23 |
mfrapPerfCirRxPercentUtilizationRange4The number of short-term intervals during
which rx data throughput on this DLCI compared
to CIR was in range 4 (21-50% of CIR).ro INTEGER .1.3.6.1.4.1.485.8.5.6.1.1.24 |
mfrapPerfCirRxPercentUtilizationRange5The number of short-term intervals during
which rx data throughput on this DLCI compared
to CIR was in range 5 (51-80% of CIR).ro INTEGER .1.3.6.1.4.1.485.8.5.6.1.1.25 |
mfrapPerfCirRxPercentUtilizationRange6The number of short-term intervals during
which rx data throughput on this DLCI compared
to CIR was in range 6 (81-100% of CIR).ro INTEGER .1.3.6.1.4.1.485.8.5.6.1.1.26 |
mfrapPerfCirRxPercentUtilizationRange7The number of short-term intervals during
which rx data throughput on this DLCI compared
to CIR was in range 7 (101-150% of CIR).ro INTEGER .1.3.6.1.4.1.485.8.5.6.1.1.27 |
mfrapPerfCirRxPercentUtilizationRange8The number of short-term intervals during
which rx data throughput on this DLCI compared
to CIR was in range 8 (> 150% of CIR).ro INTEGER .1.3.6.1.4.1.485.8.5.6.1.1.28 |
mfrapPerfCirTxPercentUtilizationRange1The number of short-term intervals during
which tx data throughput on this DLCI compared
to CIR was in range 1 (0% of CIR).ro INTEGER .1.3.6.1.4.1.485.8.5.6.1.1.41 |
mfrapPerfCirTxPercentUtilizationRange2The number of short-term intervals during
which tx data throughput on this DLCI compared
to CIR was in range 2 (1-10% of CIR).ro INTEGER .1.3.6.1.4.1.485.8.5.6.1.1.42 |
mfrapPerfCirTxPercentUtilizationRange3The number of short-term intervals during
which tx data throughput on this DLCI compared
to CIR was in range 3 (11-20% of CIR).ro INTEGER .1.3.6.1.4.1.485.8.5.6.1.1.43 |
mfrapPerfCirTxPercentUtilizationRange4The number of short-term intervals during
which tx data throughput on this DLCI compared
to CIR was in range 4 (21-50% of CIR).ro INTEGER .1.3.6.1.4.1.485.8.5.6.1.1.44 |
mfrapPerfCirTxPercentUtilizationRange5The number of short-term intervals during
which tx data throughput on this DLCI compared
to CIR was in range 5 (51-80% of CIR).ro INTEGER .1.3.6.1.4.1.485.8.5.6.1.1.45 |
mfrapPerfCirTxPercentUtilizationRange6The number of short-term intervals during
which tx data throughput on this DLCI compared
to CIR was in range 6 (81-100% o0f CIR).ro INTEGER .1.3.6.1.4.1.485.8.5.6.1.1.46 |
mfrapPerfCirTxPercentUtilizationRange7The number of short-term intervals during
which tx data throughput on this DLCI compared
to CIR was in range 7 (101-150% of CIR).ro INTEGER .1.3.6.1.4.1.485.8.5.6.1.1.47 |
mfrapPerfCirTxPercentUtilizationRange8The number of short-term intervals during
which tx data throughput on this DLCI compared
to CIR was in range 8 (> 150% of CIR).ro INTEGER .1.3.6.1.4.1.485.8.5.6.1.1.48 |
mfrapPerfCurrentPerDlciUtilizationTableThe current measurement of utilization as a percentage
of CIR on each DLCI. Each short term statistics
interval, the count of bytes transmitted and received
is used to calculate the percentage of CIR used. SEQUENCE OF MfrapPerfCurrentPerDlciUtilizationEntry .1.3.6.1.4.1.485.8.5.6.2 |
mfrapPerfCurrentPerDlciUtilizationEntryThe utilization statistics for a particular DLCI. MfrapPerfCurrentPerDlciUtilizationEntry .1.3.6.1.4.1.485.8.5.6.2.1 |
mfrapPerfCurrentPerDlciUtilizationDlciValueThe DLCI value with which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.8.5.6.2.1.1 |
mfrapPerfCurrentPerDlciRxUtilizationThe receive direction utilization as a
percentage of CIR.ro INTEGER .1.3.6.1.4.1.485.8.5.6.2.1.2 |
mfrapPerfCurrentPerDlciTxUtilizationThe transmit direction utilization as a
percentage of CIR.ro INTEGER .1.3.6.1.4.1.485.8.5.6.2.1.3 |
mfrapPerfCurrentPerDlciAggregateUtilizationThe aggregate utilization, the average
of the receive and transmit utilization
as a percentage of CIR.ro INTEGER .1.3.6.1.4.1.485.8.5.6.2.1.4 |
mfrapPerfCurrentUnitUtilization OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.5.6.3 |
mfrapPerfCurrentDteUtilizationThe DTE interface utilization as a
percentage of line rate.ro INTEGER .1.3.6.1.4.1.485.8.5.6.3.2 |
mfrapPerfCurrentWanUtilizationThe WAN interface utilization as a
percentage of line rate.ro INTEGER .1.3.6.1.4.1.485.8.5.6.3.3 |
mfrapPerfCurrentAggregateUtilizationThe aggregate utilization of the unit,
the average of the DTE and WAN interface
utilizations as a percentage of line rate.ro INTEGER .1.3.6.1.4.1.485.8.5.6.3.4 |
mfrapAlarmTypeThe type of alarms that are generated on the nodero Enumeration .1.3.6.1.4.1.485.8.6 |
mfrapDLCINumThe DLCI number for the DLCI active or inactive trapro INTEGER .1.3.6.1.4.1.485.8.7 |
mfrapInterfaceThe interface most recently reported in a TRAP.ro Enumeration .1.3.6.1.4.1.485.8.8 |
mfrapIpAddressThe IP address most recently reported in a TRAP.ro IpAddress .1.3.6.1.4.1.485.8.9 |
mfrapEventTrapLog OBJECT IDENTIFIER .1.3.6.1.4.1.485.8.10 |
mfrapEventTrapLogTableThis table contains the Event/Trap log. The entries are
indexed by sequence number. SEQUENCE OF MFRAPEventTrapLogEntry .1.3.6.1.4.1.485.8.10.1 |
mfrapEventTrapLogEntryThe event record for a particular event. MFRAPEventTrapLogEntry .1.3.6.1.4.1.485.8.10.1.1 |
mfrapEventTrapLogSeqNumThe sequence number associated with an event record.ro INTEGER .1.3.6.1.4.1.485.8.10.1.1.1 |
mfrapEventTrapLogGenericEventThe SNMP generic trap or event number.ro INTEGER .1.3.6.1.4.1.485.8.10.1.1.2 |
mfrapEventTrapLogSpecificEventThe SNMP specific trap or event sub-identifier number.ro INTEGER .1.3.6.1.4.1.485.8.10.1.1.3 |
mfrapEventTrapLogTimeStampThe SNMP trap timestamp.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.485.8.10.1.1.4 |
mfrapEventTrapLogVarBind1Variable Binding 1 for this SNMP Trap event.ro INTEGER .1.3.6.1.4.1.485.8.10.1.1.5 |
mfrapEventTrapLogVarBind2Variable Binding 2 for this SNMP Trap event.ro INTEGER .1.3.6.1.4.1.485.8.10.1.1.6 |
mfrapEventTrapLogVarBind3Variable Binding 3 for this SNMP Trap event.ro INTEGER .1.3.6.1.4.1.485.8.10.1.1.7 |
mfrapEventLogAltTableThis is an alternative method to access the database of the
Event/Trap Log. The database is indexed by Sequence Number
and Event/Trap log's are returned in an OCTETSTRING. SEQUENCE OF MFRAPEventLogAltEntry .1.3.6.1.4.1.485.8.10.2 |
mfrapEventLogAltEntryThe Event/Trap Log for a particular sequence number. MFRAPEventLogAltEntry .1.3.6.1.4.1.485.8.10.2.1 |
mfrapEventLogAltSeqNumThe Sequence Number monitored for the Event Logro INTEGER .1.3.6.1.4.1.485.8.10.2.1.1 |
mfrapEventLogAltArrayThe Event / Trap log for the given sequence number.ro OCTET STRING .1.3.6.1.4.1.485.8.10.2.1.2 |
mfrapEventLogCurrentSeqNumThe current index into the Event Log Table.ro INTEGER .1.3.6.1.4.1.485.8.10.3 |
mfrapEventLogFreezeThis freezes the Event/Trap Log. freeze(1) will
prevent Events / Traps from being entered into the database,
un-freeze(2) will allow Events / Traps to be logged into the
database. An event will be logged indicating a set of this
entryrw Enumeration .1.3.6.1.4.1.485.8.10.4 |
mfrapEventLogClearThis clears the Event/Trap Log.rw Enumeration .1.3.6.1.4.1.485.8.10.5 |
mfrapPercentUtilizationThe percent utilization for a DLCI most recently
reported in a TRAP.ro INTEGER .1.3.6.1.4.1.485.8.11 |
mfrapUtilizationThresholdThe percent utilization threshold for a DLCI most
recently reported in a TRAP.ro INTEGER .1.3.6.1.4.1.485.8.12 |
mfrapCfgLockIpAddressThe IP address of the management station locking
the configuration most recently reported in a TRAP.ro IpAddress .1.3.6.1.4.1.485.8.13 |