TFRAP-MIB
AI MIB Summary
Standard SNMP MIB module defining data structures for TFRAP-MIB.
926
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
926 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 |
tfrap OBJECT IDENTIFIER .1.3.6.1.4.1.485.5 |
tfrapTrapA tfrapTrap trap signifies that the
sending node had its `tfrapAlarmType`
variable modified. TRAP-TYPE .1.3.6.1.4.1.485.5.0.0 |
tfrapBadConfigTrapUnit 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.5.0.1 |
tfrapLocalConfigTrapUnit configuration has been updated locally
(console port or front panel keypad) or
remotely (telnet). TRAP-TYPE .1.3.6.1.4.1.485.5.0.2 |
tfrapt1netwcarrierlossUnit is not detecting a signal from the
wide area network. TRAP-TYPE .1.3.6.1.4.1.485.5.0.3 |
tfrapt1netwcarrierdetectUnit is detecting a signal from the wide
area network. TRAP-TYPE .1.3.6.1.4.1.485.5.0.4 |
tfrapt1netwsynclossdeclareUnit 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.5.0.5 |
tfrapt1netwsyncacquireUnit is now synchronized with the signal
received from the wide area network. TRAP-TYPE .1.3.6.1.4.1.485.5.0.6 |
tfrapt1netwredalarmdeclareUnit 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.5.0.7 |
tfrapt1netwredalarmclearUnit 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.5.0.8 |
tfrapt1netwyellowalarmdetectUnit 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.5.0.9 |
tfrapt1netwyellowalarmclearUnit 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.5.0.10 |
tfrapt1netwaisdetectUnit 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.5.0.11 |
tfrapt1netwaisclearUnit 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.5.0.12 |
tfrapt1controlledslipUnit 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.5.0.13 |
tfrapLocalUnitLoopbackEnabledTrapUnit 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.5.0.14 |
tfrapLocalUnitLoopbackDisabledTrapBidirectional unit loopback path is removed. TRAP-TYPE .1.3.6.1.4.1.485.5.0.15 |
tfrapLocalUnitLoopbackFailedTrapBidirectional 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.5.0.16 |
tfrapLocalDteLoopbackEnabledTrapUnit 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.5.0.17 |
tfrapLocalDteLoopbackDisabledTrapBidirectional DTE loopback path is removed. TRAP-TYPE .1.3.6.1.4.1.485.5.0.18 |
tfrapLocalDteLoopbackFailedTrapBidirectional 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.5.0.19 |
tfrapLocalAggregateLoopbackEnabledTrapUnit 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.5.0.20 |
tfrapLocalAggregateLoopbackDisabledTrapLocal aggregate loopback path is removed. TRAP-TYPE .1.3.6.1.4.1.485.5.0.21 |
tfrapLocalAggregateLoopbackFailedTrapLocal 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.5.0.22 |
tfrapLocalPayloadLoopbackEnabledTrapUnit 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.5.0.23 |
tfrapLocalPayloadLoopbackDisabledTrapLocal payload loopback path is removed. TRAP-TYPE .1.3.6.1.4.1.485.5.0.24 |
tfrapLocalPayloadLoopbackFailedTrapLocal 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.5.0.25 |
tfrapLocalNetLoopbackEnabledTrapUnit 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.5.0.26 |
tfrapLocalNetLoopbackDisabledTrapLocal network loopback path is removed. TRAP-TYPE .1.3.6.1.4.1.485.5.0.27 |
tfrapLocalNetLoopbackFailedTrapLocal 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.5.0.28 |
tfrapV54LoopUpInitiatedTrapUnit 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.5.0.29 |
tfrapV54LoopDownCompletedTrapUnit 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.5.0.30 |
tfrapV54LoopbackEnabledTrapUnit 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.5.0.31 |
tfrapV54LoopbackDisabledTrapUnit 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.5.0.32 |
tfrapV54LoopbackFailedTrapUnit 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.5.0.33 |
tfrapCsuLoopUpInitiatedTrapUnit 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.5.0.34 |
tfrapCsuLoopDownCompletedTrapUnit 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.5.0.35 |
tfrapCsuLoopbackEnabledTrapUnit 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.5.0.36 |
tfrapCsuLoopbackDisabledTrapUnit 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.5.0.37 |
tfrapCsuLoopbackFailedTrapUnit 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.5.0.38 |
tfrapDsuLoopUpInitiatedTrapUnit 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.5.0.39 |
tfrapDsuLoopDownCompletedTrapUnit 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.5.0.40 |
tfrapDsuLoopbackEnabledTrapUnit 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.5.0.41 |
tfrapDsuLoopbackDisabledTrapUnit 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.5.0.42 |
tfrapDsuLoopbackFailedTrapUnit 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.5.0.43 |
tfrapBertInitiatedTrapUnit 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.5.0.44 |
tfrapBertCompletedTrapUnit has stopped sending a pseudorandom test
pattern out the WAN. TRAP-TYPE .1.3.6.1.4.1.485.5.0.45 |
tfrapBertFailedTrapUnit 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.5.0.46 |
tfrapDLCIActiveTrapUnit 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.5.0.47 |
tfrapDLCIInactiveTrapUnit 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.5.0.48 |
tfrapDLCITDThresholdTrapVNIP 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.5.0.49 |
tfrapLmiSourcingChangePassthruTrapUnit 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.5.0.50 |
tfrapLmiSourcingChangeUserDteTrapUnit 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.5.0.51 |
tfrapLmiSourcingChangeNetDteTrapUnit 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.5.0.52 |
tfrapLmiSourcingChangeUserT1TrapUnit 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.5.0.53 |
tfrapLmiSourcingChangeNetT1TrapUnit 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.5.0.54 |
tfrapDteSignalRtsOnTrapUnit'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.5.0.55 |
tfrapDteSignalRtsOffTrapUnit'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.5.0.56 |
tfrapDteSignalDtrOnTrapUnit'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.5.0.57 |
tfrapDteSignalDtrOffTrapUnit'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.5.0.58 |
tfrapNonIncrLmiSeqNumDteTrapUnit 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.5.0.59 |
tfrapNonIncrLmiSeqNumT1TrapUnit 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.5.0.60 |
tfrapLmiSeqNumMismatchDteTrapUnit 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.5.0.61 |
tfrapLmiSeqNumMismatchT1TrapUnit 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.5.0.62 |
tfrapTrapMutingActiveTrap generation is muted. TRAP-TYPE .1.3.6.1.4.1.485.5.0.75 |
tfrapTrapMutingInactiveTrap generation is re-enabled (muting disabled). TRAP-TYPE .1.3.6.1.4.1.485.5.0.76 |
tfrapVloopUpA 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.5.0.90 |
tfrapVloopDownA 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.5.0.91 |
tfrapVloopUpViaRemoteA 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.5.0.92 |
tfrapVloopDownViaRemoteA 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.5.0.93 |
tfrapVloopRequestFailedThe request for a PVC loopback (VLOOP) has been rejected
or did not complete. TRAP-TYPE .1.3.6.1.4.1.485.5.0.94 |
tfrapVbertStartedA 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.5.0.95 |
tfrapVbertStoppedA 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.5.0.96 |
tfrapVbertRequestFailedThe request for a PVC BERT (VBERT) on this DLCI
on this interface has been rejected. TRAP-TYPE .1.3.6.1.4.1.485.5.0.97 |
tfrapLocalPayloadLoopbackEnabledViaRemoteTrapLocal Payload loopback enabled Via Remote unit. TRAP-TYPE .1.3.6.1.4.1.485.5.0.136 |
tfrapLocalPayloadLoopbackDisabledViaRemoteTrapLocal Payload loopback disabled Via Remote unit. TRAP-TYPE .1.3.6.1.4.1.485.5.0.137 |
tfrapPvcRxUtilizationExceededTrapPercent 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.5.0.138 |
tfrapPvcTxUtilizationExceededTrapPercent 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.5.0.139 |
tfrapPvcRxUtilizationClearedTrapPercent 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.5.0.140 |
tfrapPvcTxUtilizationClearedTrapPercent 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.5.0.141 |
tfrapConfigInstallSuccessThe configuration install process has successfully
completed. TRAP-TYPE .1.3.6.1.4.1.485.5.0.142 |
tfrapTftpRequestedTrapUnit 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.5.0.257 |
tfrapTftpTransferringTrapUnit 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.5.0.258 |
tfrapTftpProgrammingTrapUnit 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.5.0.259 |
tfrapTftpAbortedTrapUnit'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.5.0.260 |
tfrapTftpSuccessTrapUnit'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.5.0.261 |
tfrapTftpHostUnreachableTrapUnit 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.5.0.262 |
tfrapTftpNoFileTrapUnit 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.5.0.263 |
tfrapTftpInvalidFileTrapUnit 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.5.0.264 |
tfrapTftpCorruptFileTrapUnit 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.5.0.265 |
tfrapSystem OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.1 |
tfrapSysTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.1.1 |
tfrapSysTypeA textual description of the system model identifier.
for example: SYNC-TFRAPro DisplayString .1.3.6.1.4.1.485.5.1.1.1 |
tfrapSysSoftRevDisplays the Software Revision of the application code
installed in this node.ro DisplayString .1.3.6.1.4.1.485.5.1.1.2 |
tfrapSysHardRevDisplays the Hardware Revision of the node.ro DisplayString .1.3.6.1.4.1.485.5.1.1.3 |
tfrapSysNumT1InstalledThe number of Wide Area Network (T1) ports that are
installed. There is 1 on the TFRAP.ro INTEGER .1.3.6.1.4.1.485.5.1.1.4 |
tfrapSysNumDteInstalledThe number of user serial date channels (DTE) that are
installed. There is 1 on the TFRAP.ro INTEGER .1.3.6.1.4.1.485.5.1.1.5 |
tfrapSysNumMaintInstalledThe number of Async Maintenance/Comm (console) ports
that are installed. There is 1 dual-purpose comm port
on the TFRAP which may configured as either a VT-100
console or a SLIP management port.ro INTEGER .1.3.6.1.4.1.485.5.1.1.6 |
tfrapSysNameThe 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.5.1.1.7 |
tfrapSysSerialNoThe serial number of the board.ro DisplayString .1.3.6.1.4.1.485.5.1.1.8 |
tfrapSysResetNodeCommand to reset the node. NODE WILL BE OFF-LINE AND
USER DATA WILL BE INTERRUPTED FOR APPROXIMATELY 15
SECONDS. Full network recovery may take longerrw Enumeration .1.3.6.1.4.1.485.5.1.1.9 |
tfrapSysAmtMemoryInstalledThe amount of memory (RAM) installed (in megabytes).ro INTEGER .1.3.6.1.4.1.485.5.1.1.10 |
tfrapSysLocationThe 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.5.1.1.12 |
tfrapSysContactThe 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.5.1.1.13 |
tfrapSysPromptConfigurable 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.5.1.1.15 |
tfrapSysBootRevDisplays the Software Revision of the Bootstrapping
code installed in this node.ro DisplayString .1.3.6.1.4.1.485.5.1.1.16 |
tfrapSysFeatureTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.1.2 |
tfrapSysSLIPSupportedShows 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.5.1.2.1 |
tfrapSysPPPSupportedShows 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.5.1.2.2 |
tfrapSysRDOSupportedShows whether the unit has Remote Dial Out capability.ro DisplayString .1.3.6.1.4.1.485.5.1.2.3 |
tfrapSysETHSupportedShows whether the unit has Ethernet capability.ro DisplayString .1.3.6.1.4.1.485.5.1.2.4 |
tfrapSysTKRSupportedShows whether the unit has Token Ring capability.ro DisplayString .1.3.6.1.4.1.485.5.1.2.5 |
tfrapSysExtTimSupportedShows whether the unit has External Timing capability.
This is the ability to derive WAN timing from the DTE port.ro DisplayString .1.3.6.1.4.1.485.5.1.2.6 |
tfrapSysBRISupportedShows whether the unit has BRI (ISDN Basic Rate) capability.ro DisplayString .1.3.6.1.4.1.485.5.1.2.7 |
tfrapSysSelDTESupportedShows whether the unit has a Selectable DTE interface.
This being the ability to select amongst various electrical
interface formats (V.35, RS449, RS232, etc.) via software.ro DisplayString .1.3.6.1.4.1.485.5.1.2.8 |
tfrapSysMLSupportedShows whether the unit supports MLs (out-of-band management
links). N/A to frame relay networks.ro DisplayString .1.3.6.1.4.1.485.5.1.2.9 |
tfrapSysNumDlcisSupportedShows how many DLCIs can be monitored for frame-based
statistics. The unit will pass an unlimited number of
DLCIs but will only collect statistics on this number
(first come first served).ro INTEGER .1.3.6.1.4.1.485.5.1.2.10 |
tfrapSysLTFNumDlcisShows how many DLCIs can be specified
in the Long Term Statistics Filter.ro INTEGER .1.3.6.1.4.1.485.5.1.2.11 |
tfrapSysLTFNumProtocolsShows how many protocols can be specified
in the Long Term Statistics Filter.ro INTEGER .1.3.6.1.4.1.485.5.1.2.12 |
tfrapSysNumUserProtocolsShows 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.5.1.2.13 |
tfrapSysNumSnmpMgrsShows how many SNMP managers can be programmed in the
table tfrapCfgSnmpMngrTable. These managers are sent
TRAPs if configured to do so.ro INTEGER .1.3.6.1.4.1.485.5.1.2.14 |
tfrapSysNumDlciNamesShows how many DLCI names can be defined by the user
in the table tfrapCfgFrPerfDlciNamesTable.ro INTEGER .1.3.6.1.4.1.485.5.1.2.15 |
tfrapConfiguration OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.2 |
tfrapCfgMgmtTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.2.1 |
tfrapCfgIpTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.2.1.1 |
tfrapCfgIpMyIPThe 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.5.2.1.1.1 |
tfrapCfgIpPeerIPThis 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.5.2.1.1.2 |
tfrapCfgIpMaskThe IP Subnet Mask (eg 255.255.255.0). This
parameter should be consisent with the IP
subnet address setting of the external
internetworking equipment (router/frad).rw IpAddress .1.3.6.1.4.1.485.5.2.1.1.3 |
tfrapCfgIpMaxMTUThe Maximum Transmission Unit is the size of the
largest IP packet supported (including header).
This value should be set to the lowest value supported
by any equipment in the transmission path.
For Frame Relay management the typical value is 1500.
For SLIP management the typical value is 1006.rw INTEGER .1.3.6.1.4.1.485.5.2.1.1.4 |
tfrapCfgIpChannelThis is the method by which IP traffic is being carried.
Either via the SLIP port or a DLCI. This reflects how
your Management scheme is configured (read only).ro Enumeration .1.3.6.1.4.1.485.5.2.1.1.5 |
tfrapCfgIpTelnetEnableEnables/Disables the telnet feature.
(1) enable-telnet
(2) disable-telnetrw Enumeration .1.3.6.1.4.1.485.5.2.1.1.6 |
tfrapCfgIpTelnetAutoLogOutIf Telnet Auto logout is enabled the unit
will automatically disconnect from a Telnet
session after a period of inactivity (absence
of key strokes from remote terminal).
(2) disables this feature
(1) auto logout after 15 minutes inactivity
(3) auto logout after 3 minutes inactivity
(5) auto logout after 5 minutes inactivity
(10) auto logout after 10 minutes inactivity
(30) auto logout after 30 minutes inactivity
(60) auto logout after 60 minutes inactivityrw Enumeration .1.3.6.1.4.1.485.5.2.1.1.7 |
tfrapCfgTftpTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.2.1.2 |
tfrapCfgTftpInitiateSetting this object to a value that matches
the TFTP Password will command the unit to
attempt a TFTP file transfer. A TFTP profile
including host ip address, dlci value, interface,
and file name must first be configured.rw DisplayString .1.3.6.1.4.1.485.5.2.1.2.1 |
tfrapCfgTftpIpAddressThe IP address of the TFTP host with which
the unit will attempt to establish a TFTP
session when initiated.rw IpAddress .1.3.6.1.4.1.485.5.2.1.2.2 |
tfrapCfgTftpFilenameThe name of the file located on the TFTP host
that will be transferred to the unit. Typically
this is a product-specific software image that
will be programmed into unit FLASH. The unit
provides several levels of checking to verify
the validity and integrity of this file.
Note - depending upon the host, this file name
may be case sensitive.rw DisplayString .1.3.6.1.4.1.485.5.2.1.2.3 |
tfrapCfgTftpInterfaceThe physical interface out which the TFTP host
is located. This parameter is only required for
Piggyback and Bi-directional in-band frame relay
managed applications. With Local and Remote in-band
and SLIP-based applications the interface is known
and Sets to this will be ignored.rw Enumeration .1.3.6.1.4.1.485.5.2.1.2.4 |
tfrapCfgTftpDlciThe local DLCI value on which the TFTP host can be
reached. This DLCI should be active prior to
initiating the TFTP session. This parameter is only
required for Piggyback in-band frame relay managed
applications. With Private management (Local, Remote
or Bi-directional in-band applications) the DLCI is
known and will be reported here (Sets will be ignored).
In SLIP-based applications the DLCI value is not
applicable and a value of -1 is reported (Sets will
be ignored).rw INTEGER (-1..63487) .1.3.6.1.4.1.485.5.2.1.2.5 |
tfrapCfgTftpStatusThe status of current or most recent TFTP operation.
(1) TFTP inactive, sets to this value will abort the session
(2) TFTP requested
(3) TFTP transferring
(4) TFTP programming FLASH - unit will reset
(5) TFTP fail: session aborted by user or error condition
(6) TFTP fail: host no reply - verify TFTP profile and host
(7) TFTP fail: file not found - verify file name and location
(8) TFTP fail: invalid file - file rejected by unit as inappropriate
(9) TFTP fail: corrupt file - session terminated due to checksum error
(10) TFTP transfer successful and file has been verifiedrw Enumeration .1.3.6.1.4.1.485.5.2.1.2.6 |
tfrapCfgTftpNumBytesThe number of Bytes from the ROM image that have been
TFTP'd to the unitro Counter .1.3.6.1.4.1.485.5.2.1.2.7 |
tfrapCfgSnmpTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.2.1.3 |
tfrapCfgSnmpFrTrapControls whether or not the Frame Relay DLCI
status change traps are issued. These traps are
tfrapDLCIActiveTrap and tfrapDLCIInactiveTrap.
(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.5.2.1.3.1 |
tfrapCfgSnmpMgrTableThe table of SNMP manager profiles to which
traps are sent. In all managed modes an SNMP
trap mangager's ip address is required as a
minimum. Additionally for Piggyback managed
units the DLCI and interface must also be
configured appropriately. For Local, Remote
and SLIP-based management, the DLCI and
interface are implied and need not be
configured as part of this profile. SEQUENCE OF TfrapCfgSnmpMgrEntry .1.3.6.1.4.1.485.5.2.1.3.2 |
tfrapCfgSnmpMgrEntryThe SNMP trap manager profiles to which the unit
sends TRAPs. TfrapCfgSnmpMgrEntry .1.3.6.1.4.1.485.5.2.1.3.2.1 |
tfrapCfgSnmpMgrIndexThe index to the list of SNMP managers receiving TRAPs.ro INTEGER .1.3.6.1.4.1.485.5.2.1.3.2.1.1 |
tfrapCfgSnmpMgrIPThe 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.5.2.1.3.2.1.2 |
tfrapCfgSnmpMgrInterfaceThe 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.5.2.1.3.2.1.3 |
tfrapCfgSnmpMgrDlciThe DLCI out which the indexed trap manager can be
reached. This entry is required in Piggyback in-band
managed applications. In Private in-band applications
the DLCI is known and Sets to this parameter will be
ignored. In SLIP mode the DLCI is not applicable,
Sets will be ignored and a -1 will be returned as the
DLCI value.rw INTEGER .1.3.6.1.4.1.485.5.2.1.3.2.1.4 |
tfrapCfgSnmpTrapMutingControls whether Traps are Sent or Muted. If traps
are Muted then a single trap (#75) will be periodically
issued by the unit at the programmed frequency. If Muting
is Disabled then the full set of Trap events are reported
accordingly.
(0) Disable Trap Muting
(30-10080) Trap Muting frequency in minutes.rw INTEGER .1.3.6.1.4.1.485.5.2.1.3.3 |
tfrapCfgSnmpUtilTrapEnableEnables 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.5.2.1.3.6 |
tfrapCfgSnmpMgrClearNDeletes the number of entries in the tfrapCfgSnmpMgrTable
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.5.2.1.3.7 |
tfrapCfgCommTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.2.1.4 |
tfrapCfgCommModeThe protocol running on the Maintenance/Comm port (console).
Setting this to SLIP mode will automatically disable
in-band management if it's enabled.
(1) VT100 for directly attached async terminal
(2) SLIP - Serial Line IP out-of-band managementrw Enumeration .1.3.6.1.4.1.485.5.2.1.4.1 |
tfrapCfgCommBaudAsynchronous 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.5.2.1.4.2 |
tfrapCfgCommDataBitsAsynchronous data format for the Maintenance/Comm port
(Console). This must be configured to match either the
VT100 compatible terminal or the SLIP Terminal Server
depending upon the Comm port mode.
(1) 7 databits per character
(2) 8 databits per characterrw Enumeration .1.3.6.1.4.1.485.5.2.1.4.3 |
tfrapCfgCommStopBitsAsynchronous intercharacter protocol for the Maintenance/Comm
port (Console). This must be configured to match either the
VT100 compatible terminal or the SLIP Terminal Server
depending upon the Comm port mode.
(1) 1 stopbit
(2) 1.5 stopbits
(3) 3 stopbitsrw Enumeration .1.3.6.1.4.1.485.5.2.1.4.4 |
tfrapCfgCommParityAsynchronous parity checking protocol for the
Maintenance/Comm port (Console). This must be configured
to match either the VT100 compatible terminal or the SLIP
Terminal Server depending upon the Comm port mode.
(1) no parity
(2) odd-parity
(3) even-parityrw Enumeration .1.3.6.1.4.1.485.5.2.1.4.5 |
tfrapCfgCommFlowCtrlFlow Control for this Communication port. Values
are no-flow-control (1).rw Enumeration .1.3.6.1.4.1.485.5.2.1.4.6 |
tfrapCfgFrDLCITable OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.2.1.5 |
tfrapCfgFrDLCIModeIn-band Frame Relay management mode. A variety of options
exist which are differentiated by how PVCs can be provisioned
to manage the unit and the resulting impact to the logical
processing of Link Management Protocol messages (LMI spoofing
and sourcing). The unit is designed to support these management
modes even in non-provisioned or failed frame relay networks.
This setting also has implications upon how networking protocols
such as ARP and InARP are handled by the unit.
(1) inactive: in-band management is not enabled
(2) local DLCI mode: in-band managed using a private dedicated DLCI
accessible via the DTE port only. A DLCI value is configured
which, through LMI spoofing, will only be visible to the DTE
equipment and need not be provisioned on the WAN. All traffic on
this DLCI will be terminated by the unit.
(3) remote DLCI mode: in-band managed using a private dedicated DLCI
accessible via the WAN port only. A DLCI value is configured
which, through LMI spoofing, will only be visible from the WAN
side and will not be seen by any DTE equipment. All traffic on
this DLCI will be terminated by the unit.
(4) bidirectional mode: in-band managed using a private dedicated DLCI
accessible through either port. A DLCI value is configured
which is expected to be fully provisioned in the frame relay
network but dedicated to the management function of this particular
unit. All traffic on this DLCI will be terminated by the unit.
(5) piggyback mode: in-band managed using any DLCI on any interface. A
DLCI value is defined that becomes the default DLCI that will be
maintained by the unit during network or LMI failure conditions.
The unit will terminate and respond accordingly to management and
networking data while transparently passing on user data.
(6) fixed DCE mode: special mode of operation to support frame relay
applications that do not include a switch (frame relay DCE). The
unit will independently respond to LMI requests on each interface
and will provision the configured DLCI to each Frame Relay DTE device.
Except for this, the unit behaves like piggyback.rw Enumeration .1.3.6.1.4.1.485.5.2.1.5.1 |
tfrapCfgFrDLCIValueIf in-band management is being used this DLCI value should be defined.
In all modes of in-band management with the LMI Sourcing feature enabled
the unit may provision this DLCI during LMI failure to facilitate management
access. In Private modes (Local, Remote, and Bidirectional) this is the
dedicated DLCI for management data and address resolution protocols - all
other traffic on this DLCI will be discarded. In Piggyback mode this DLCI
is treated like all others except during LMI failure sourcing when it may
be provisioned by the unit. In Piggyback mode if InARP is enabled on a single
DLCI then this value defines that DLCI.rw INTEGER .1.3.6.1.4.1.485.5.2.1.5.2 |
tfrapCfgFrDLCIEncapThis 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.5.2.1.5.3 |
tfrapCfgFrDLCIMgmtDEProvides 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.5.2.1.5.4 |
tfrapCfgAppTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.2.2 |
tfrapCfgAppClockSourceTiming source for transmission of data towards the WAN
and for the generation of DTE clocking. There should be
only one source per end-to-end WAN link. Unit is typically
network timed in a point-to-network application.
(1) internal: derive timing from a high-stability on-board
crystal oscillator.
(2) network: or Loop timing, derive timing from the signal
received at the WAN interface
(3) dte: derive timing from the clock presented by the DTE
equipment on the Terminal Timing(TT)/Transmit Clock
External (TCE) leads. This setting expects the DTE timing
mode to be Loop 1 and the DTE device to be generating a
clock at the DTE data rate.rw Enumeration .1.3.6.1.4.1.485.5.2.2.1 |
tfrapCfgAppCircuitIdAlphanumeric circuit identifier may be provided by the service
provider for reference or assigned arbitrarily per user
requirements.rw DisplayString .1.3.6.1.4.1.485.5.2.2.2 |
tfrapCfgAppTypeThis unit provides many features specifically adapted
to Frame Relay transmission links; this includes diagnostic
utilities, statistical analysis, protocol trends, quality of
service reporting, and in-band SNMP management. If the unit
will be operating in a Frame Relay network the Application Type
must be set to Frame Relay to enable these features. To
operate in a non-Frame Relay network or to bypass this feature
set the unit may be placed in Dedicated mode and will emulate a
more familiar DSU/CSU. Note - changing this value will
automatically change the Application Format setting and vice
versa.
(1) dedicated: protocol-independent transparent DSU/CSU
(2) Frame Relay: Frame and protocol aware DSU/CSUrw Enumeration .1.3.6.1.4.1.485.5.2.2.3 |
tfrapCfgAppFormatRefer 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.5.2.2.4 |
tfrapCfgAppLpbkTimeoutThe length of time a service-impacting loopback
or diagnostic utility may run before automatically
returning to normal operation. This setting will
override any alternatively timed tests (such as
VBERT).
(0) Loopbak Timeout Disabled
(1-1440) Loopback Timeoutrw INTEGER .1.3.6.1.4.1.485.5.2.2.5 |
tfrapCfgAppPerfBuffLimitThis value controls the throttling mechanism
used to determine the optimum level of statistical
processing versus manageability 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 TFRAP 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.5.2.2.10 |
tfrapCfgT1Table OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.2.3 |
tfrapCfgT1FramingType 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.5.2.3.1 |
tfrapCfgT1LineEncodingT1 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.5.2.3.2 |
tfrapCfgT1DensityCSU '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.5.2.3.3 |
tfrapCfgT1InterfaceEnables 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 acces.
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.5.2.3.4 |
tfrapCfgT1LboSettingCSU 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.5.2.3.5 |
tfrapCfgDteTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.2.4 |
tfrapCfgDteIntfTypeThe 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.5.2.4.1 |
tfrapCfgDteDataModeInverts 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.5.2.4.2 |
tfrapCfgDteClockModeThis 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.5.2.4.3 |
tfrapCfgDteTimingSerial 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. Loop-1 is the preferred mode. Loop-2 timing could experience
data errors at high rates or due to long DTE cable runs - may
need to Invert the clock (see CfgDteClockMode).
(1) Loop 1: external clock returned from DTE with data
(2) Loop 2: internal clock used to sample incoming datarw Enumeration .1.3.6.1.4.1.485.5.2.4.4 |
tfrapCfgDteLineRateSerial 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.5.2.4.5 |
tfrapCfgDteChannelDensityPacking 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.5.2.4.6 |
tfrapCfgDteStartDs0T1 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.5.2.4.7 |
tfrapCfgDteConnStatusThe 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.5.2.4.8 |
tfrapCfgDteConnStartDs0T1 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.5.2.4.9 |
tfrapCfgDteConnRateSerial 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.5.2.4.10 |
tfrapCfgDteConnDensityPacking 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.5.2.4.11 |
tfrapCfgDteConnDs0RequiredThe 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.5.2.4.12 |
tfrapCfgDteConnAutoStatusThere'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.5.2.4.13 |
tfrapCfgDteConnAutoUpdateUpdates the connection-critical parameters: line rate,
channel density and starting ds0; drops the current
connection; and initiate the new connection. Following
the issuance of this command, DteAutoStatus should be
queried to verify the update was successful.rw Enumeration .1.3.6.1.4.1.485.5.2.4.14 |
tfrapCfgDteRtsControls the reporting of the status of the DTE's Request
to Send (RTS) control signal, specifically the generation
of traps in response to control signal state changes. If
Internally Held Active, the unit will ignore the actual
status and always report this signal Active. If External,
the unit will reflect the status as driven by the DTE; as
such, Traps will be generated due to change of state (these
may be useful for a network manager's assessment of interface
status.
(1) Internally Held Active
(2) Externally Presented from DTErw Enumeration .1.3.6.1.4.1.485.5.2.4.15 |
tfrapCfgDteDtrControls the reporting of the status of the DTE's Data
Terminal Ready (DTR) control signal, specifically the
generation of traps in response to control signal state
changes. If Internally Held Active, the unit will ignore
the actual status and always report this signal Active. If
External, the unit will reflect the status as driven by the
DTE; as such, Traps will be generated due to change of state
(these may be useful for a network manager's assessment of
interface status.
(1) Internally Held Active
(2) Externally Presented from DTErw Enumeration .1.3.6.1.4.1.485.5.2.4.16 |
tfrapCfgDteDcdOutputSpecifies the behavior of the Data Carrier Detect (DCD)
control signal generated by the unit towards the DTE.
(1) inactive always: signal is permanently INACTIVE.
(2) active always: signal is permanently ACTIVE.
(3) reflect WAN carrier: signal echoes the received signal status
from the WAN.
(4) inactive with test mode: signal is ACTIVE during normal
data transfer and INACTIVE during diagnostic conditions
that interfere with data transfer from the DTE to the WAN.
(5) follow RTS: signal echoes the status of RTS as processed
from the DTE.
(6) reflect carrier and RTS: signal is a logical AND between
RTS processed from the DTE and the received signal status
from the WAN. No signal received from the WAN or RTS INACTIVE
will cause this control signal to be asserted INACTIVE.
(7) reflect sync and RTS: 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.
(8) reflect LMI and carrier and RTS: 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. In non-Frame Relay applications (type = dedicated)
LMI will be presumed ACTIVE so this will setting is equivalent
to (6).
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.5.2.4.18 |
tfrapCfgDteDsrOutputSpecifies the behavior of the Data Set Ready (DSR)
control signal generated by the unit towards the DTE.
(1) inactive always: signal is permanently INACTIVE.
(2) active always: signal is permanently ACTIVE.
(3) reflect WAN carrier: signal echoes the received signal status
from the WAN.
(4) inactive with test mode: signal is ACTIVE during normal
data transfer and INACTIVE during diagnostic conditions
that interfere with data transfer from the DTE to the WAN.
(5) follow RTS: signal echoes the status of RTS as processed
from the DTE.
(6) reflect carrier and RTS: signal is a logical AND between
RTS processed from the DTE and the received signal status
from the WAN. No signal received from the WAN or RTS INACTIVE
will cause this control signal to be asserted INACTIVE.
(7) reflect sync and RTS: signal is a logical AND between RTS
processed from the DTE and the frame synchronization with the WAN.
Frame Red Alarm defines the threshold for declaring synchronization.
(8) reflect LMI and carrier and RTS: 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. In non-Frame Relay applications (type = dedicated)
LMI will be presumed ACTIVE so this will setting is equivalent
to (6).
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.5.2.4.19 |
tfrapCfgDteCtsOutputSpecifies the behavior of the Clear to Send (CTS)
control signal generated by the unit towards the DTE.
(1) inactive always: signal is permanently INACTIVE.
(2) active always: signal is permanently ACTIVE.
(3) reflect WAN carrier: signal echoes the received signal status
from the WAN.
(4) inactive with test mode: signal is ACTIVE during normal
data transfer and INACTIVE during diagnostic conditions
that interfere with data transfer from the DTE to the WAN.
(5) follow RTS: signal echoes the status of RTS as processed
from the DTE.
(6) reflect carrier and RTS: signal is a logical AND between
RTS processed from the DTE and the received signal status
from the WAN. No signal received from the WAN or RTS INACTIVE
will cause this control signal to be asserted INACTIVE.
(7) reflect sync and RTS: 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.
(8) reflect LMI and carrier and RTS: 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. In non-Frame Relay applications (type = dedicated)
LMI will be presumed ACTIVE so this will setting is equivalent
to (6).
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.5.2.4.20 |
tfrapCfgFrTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.2.5 |
tfrapCfgFrAddrLenDefines 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.5.2.5.1 |
tfrapCfgFrCrcModeThis 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.5.2.5.2 |
tfrapCfgFrLmiTypeThe 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.5.2.5.3 |
tfrapCfgFrLmiInactivityTimeoutTimer 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.5.2.5.4 |
tfrapCfgFrLmiKeepaliveTimeoutTimer 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.5.2.5.5 |
tfrapCfgFrAddrResModeEnable ARP (2), INARP (3), both (4), or neither (1).rw Enumeration .1.3.6.1.4.1.485.5.2.5.6 |
tfrapCfgFrAddrResInarpTimerThe 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.5.2.5.7 |
tfrapCfgFrLmiFullStatusTimer 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.5.2.5.8 |
tfrapCfgFrAddrResDlcisAddress 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.5.2.5.9 |
tfrapCfgVnipTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.2.6 |
tfrapCfgVnipModeThis 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.5.2.6.1 |
tfrapCfgVnipInitTimerVNIP peer to peer communications are initiated following
the detection of a VNIP Hello message. The unit will
periodically issue this message out interfaces that have
VNIP enabled until a Hello response is received. Following
the reception of the Hello response, the unit will stop
issuing Hello messahges on that DLCI/interface and generate
periodic topology reports at the VNIP Keep Alive frequency.
The unit will generate periodic Hello messages, at the
InitTimer frequency if no Hello responses are ever detected
or a topology message not been detected within the time period
defined by the VNIP Inactivity timer.
(5-86400) VNIP Hello frequency (in seconds)rw INTEGER .1.3.6.1.4.1.485.5.2.6.2 |
tfrapCfgVnipKeepAliveTimerThis 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.5.2.6.3 |
tfrapCfgVnipInactivityTimerThe 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.5.2.6.4 |
tfrapCfgVnipTransitDelayFrequencyTransit 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.5.2.6.5 |
tfrapCfgTransitDelayTableThe 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 TfrapCfgTransitDelayEntry .1.3.6.1.4.1.485.5.2.6.20 |
tfrapCfgTransitDelayEntryA 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 TfrapCfgTransitDelayEntry .1.3.6.1.4.1.485.5.2.6.20.1 |
tfrapCfgTransitDelayInterfaceThis 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.5.2.6.20.1.1 |
tfrapCfgTransitDelayDlciValueThis 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.5.2.6.20.1.2 |
tfrapCfgTransitDelayNumHopsVNIP 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.5.2.6.20.1.4 |
tfrapCfgTransitDelayRcvSummaryCancelControls 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.5.2.6.20.1.5 |
tfrapCfgTransitDelayThresholdSpecifies 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.5.2.6.20.1.6 |
tfrapCfgTDDeleteTableThe table allows the user to disable transit delay measurements
for a specific DLCI on a particular interface. SEQUENCE OF TfrapCfgTDDeleteEntry .1.3.6.1.4.1.485.5.2.6.21 |
tfrapCfgTDDeleteEntryDisables VNIP Transit Delay for a particular interface and DLCI. TfrapCfgTDDeleteEntry .1.3.6.1.4.1.485.5.2.6.21.1 |
tfrapCfgTDDeleteInterfaceTransit 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.5.2.6.21.1.1 |
tfrapCfgTDDeleteDlciValueTransit 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.5.2.6.21.1.2 |
tfrapCfgTransitDelayTableClearThe tfrapCfgTransitDelayTable is cleared.
(1) clear the tablerw Enumeration .1.3.6.1.4.1.485.5.2.6.22 |
tfrapCfgFrPerf OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.2.7 |
tfrapCfgFrPerfDlciNamesTableThis 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 TFRAPCfgFrPerfDlciNamesEntry .1.3.6.1.4.1.485.5.2.7.1 |
tfrapCfgFrPerfDlciNamesEntryA table entry indexed by DLCI, containing
a DLCI, a DLCI name, a CIR, how the
CIR value was obtained, and EIR. TFRAPCfgFrPerfDlciNamesEntry .1.3.6.1.4.1.485.5.2.7.1.1 |
tfrapCfgFrPerfDlciNamesDlciValueA 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.5.2.7.1.1.1 |
tfrapCfgFrPerfDlciNamesDlciNameA user-specifiable name for an individual DLCI.rw DisplayString .1.3.6.1.4.1.485.5.2.7.1.1.2 |
tfrapCfgFrPerfDlciNamesCirValueThe 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.5.2.7.1.1.3 |
tfrapCfgFrPerfDlciNamesCirTypeThe 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.5.2.7.1.1.4 |
tfrapCfgFrPerfDlciNamesUtilThresholdThe threshold for generating a utilization
threshold trap as a percentage of the CIR.
If the utilization percentage is above this
threshold for more than
tfrapCfgFrPerfDlciUtilThreshold number of
tfrapCfgFrPerfTimersSTInterval's a
tfrapPvc(Rx/Tx)UtilizationExceeded trap
will be issued. If the If the utilization
percentage falls below this threshold for
more than tfrapCfgFrPerfDlciUtilThreshold
number of tfrapCfgFrPerfTimersSTInterval's a
tfrapPvc(Rx/Tx)UtilizationExceeded trap
will be issued.rw INTEGER .1.3.6.1.4.1.485.5.2.7.1.1.5 |
tfrapCfgFrPerfDlciNamesEirValueThe 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.5.2.7.1.1.6 |
tfrapCfgFrPerfDlciNamesDeleteSetting this object with a specific DLCI value
will remove the DLCI form the DLCI-specific
parameters database.rw INTEGER .1.3.6.1.4.1.485.5.2.7.2 |
tfrapCfgFrPerfTimers OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.2.7.3 |
tfrapCfgFrPerfTimersSTIntervalShort 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.5.2.7.3.1 |
tfrapCfgFrPerfTimersLTIntervalLong 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.5.2.7.3.2 |
tfrapCfgFrPerfUserProtocolsTableThis 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 TFRAPCfgFrPerfUserProtocolsEntry .1.3.6.1.4.1.485.5.2.7.4 |
tfrapCfgFrPerfUserProtocolsEntryAn index and TCP/UDP port number pair. TFRAPCfgFrPerfUserProtocolsEntry .1.3.6.1.4.1.485.5.2.7.4.1 |
tfrapCfgFrPerfUserProtocolsIndexAn index. Beginning with index 1, the range is defined
in SysNumUserProtocolsro INTEGER .1.3.6.1.4.1.485.5.2.7.4.1.1 |
tfrapCfgFrPerfUserProtocolsPortNumTx 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.5.2.7.4.1.2 |
tfrapCfgFrPerfLTDlciFilterTableLong 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 TFRAPCfgFrPerfLTDlciFilterEntry .1.3.6.1.4.1.485.5.2.7.5 |
tfrapCfgFrPerfLTDlciFilterEntryAn index and DLCI number pair. TFRAPCfgFrPerfLTDlciFilterEntry .1.3.6.1.4.1.485.5.2.7.5.1 |
tfrapCfgFrPerfLTDlciFilterIndexAn index. Beginning with index 1, the maximum is
defined by the value of SysLTFNumDlcis.ro INTEGER .1.3.6.1.4.1.485.5.2.7.5.1.1 |
tfrapCfgFrPerfLTDlciFilterDlciNumSetting 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.5.2.7.5.1.2 |
tfrapCfgFrPerfLTProtocolFilterTableLong 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 TFRAPCfgFrPerfLTProtocolFilterEntry .1.3.6.1.4.1.485.5.2.7.6 |
tfrapCfgFrPerfLTProtocolFilterEntryAn index and protocol pair. TFRAPCfgFrPerfLTProtocolFilterEntry .1.3.6.1.4.1.485.5.2.7.6.1 |
tfrapCfgFrPerfLTProtocolFilterIndexAn index. Beginning with index 1, the maximum is
defined by the value of SysLTFNumProtocols.ro INTEGER .1.3.6.1.4.1.485.5.2.7.6.1.1 |
tfrapCfgFrPerfLTProtocolFilterProtocolLong 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.5.2.7.6.1.2 |
tfrapCfgFrPerfDlciDefaultUtilThresholdThe default threshold for generating a
utilization threshold trap as a percentage
of the CIR. This value is used for
tfrapCfgFrPerfDlciNamesUtilThreshold when
a DLCI is first discovered.rw INTEGER .1.3.6.1.4.1.485.5.2.7.7 |
tfrapCfgFrPerfDlciUtilDurationThe number of Short Term Intervals that a
DLCI's utilization as a percentage of CIR
must be above or below the value of
tfrapCfgFrPerfDlciUtilThreshold before a
tfrapPvc(Rx/Tx)UtilizationExceededTrap or
tfrapPvc(Rx/Tx)UtilizationClearedTrap is
issued.rw INTEGER .1.3.6.1.4.1.485.5.2.7.8 |
tfrapCfgFrPerfDlciNamesTableClearClears 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.5.2.7.9 |
tfrapCfgFrPerfUserProtocolsTableClearClears the tfrapCfgFrPerfUserProtocolsTable
(1) clear the tablerw Enumeration .1.3.6.1.4.1.485.5.2.7.10 |
tfrapCfgFrPerfLTDlciFilterTableClearClears the tfrapCfgFrPerfLTDlciFilterTable
(1) clear the tablerw Enumeration .1.3.6.1.4.1.485.5.2.7.11 |
tfrapCfgFrPerfLTProtocolFilterTableClearClears the tfrapCfgFrPerfLTProtocolFilterTable
(1) clear the tablerw Enumeration .1.3.6.1.4.1.485.5.2.7.12 |
tfrapCfgFrPerfUnprovDlcisDeleteDelete all unprovisioned and Not-In-LMI dlcis
(1) delete all unprovisionedrw Enumeration .1.3.6.1.4.1.485.5.2.7.13 |
tfrapCfgSecurityTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.2.8 |
tfrapCfgTelnetCliLcdPasswordThe password needed to start a
CLI (Command Line Interface),
Telnet or LCD session.rw DisplayString .1.3.6.1.4.1.485.5.2.8.1 |
tfrapCfgTftpPasswordThe password needed to initiate a TFTP download.rw DisplayString .1.3.6.1.4.1.485.5.2.8.2 |
tfrapCfgCliPasswordOBSOLETE: The Telnet, CLI and LCD passwords
are one and the same. Use the above
tfrapCfgTelnetCliLcdPassword to log into
the CLI (Command Line Interface).rw DisplayString .1.3.6.1.4.1.485.5.2.8.3 |
tfrapCfgLcdPasswordOBSOLETE: The Telnet, CLI and LCD passwords
are one and the same. Use the above
tfrapCfgTelnetCliLcdPassword to log into
the LCD Interface.rw DisplayString .1.3.6.1.4.1.485.5.2.8.4 |
tfrapCfgGetCommunityStringThe 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.5.2.8.5 |
tfrapCfgSetCommunityStringThe 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.5.2.8.6 |
tfrapCfgLcdPswdEnableThis selection controls whether a password is
necessary to use the LCD interface.rw Enumeration .1.3.6.1.4.1.485.5.2.8.7 |
tfrapCfgLcdPswdTimeoutOBSOLETE.rw INTEGER .1.3.6.1.4.1.485.5.2.8.8 |
tfrapCfgLockRequest 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.5.2.12 |
tfrapCfgLockIDReturns 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.5.2.13 |
tfrapCfgIDA 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.5.2.14 |
tfrapCfgStatusThe 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.5.2.15 |
tfrapCfgUnlockThe 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.5.2.16 |
tfrapCfgUpdateThe 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.5.2.17 |
tfrapDiagnostics OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.3 |
tfrapDiagUnitTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.3.1 |
tfrapDiagUnitLocLoopControls a bi-directional 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 and maintain managed access
during this loopback. In Frame Relay mode, only valid
HDLC frames are looped back (pseudorandom test patterns
will be dropped).
(1) enable unit loopback
(2) disable unit loopbackrw Enumeration .1.3.6.1.4.1.485.5.3.1.1 |
tfrapDiagUnitResetEnables 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.5.3.1.2 |
tfrapDiagUnitTimeRemainingThe 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.5.3.1.3 |
tfrapDiagT1Table OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.3.2 |
tfrapDiagT1LocLineLpbkControls 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.5.3.2.1 |
tfrapDiagT1LocPylLpbkControls 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.5.3.2.2 |
tfrapDiagT1LocAggrLpbkControls Local Aggregate Loopback. All data
received from the DTE is framed, formatted
and transmit towards the WAN while being looped
back towards the DTE. 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.5.3.2.3 |
tfrapDiagT1RmtLpbkStatusStatus of Remote Loopback commands sent or received on the WAN.
(1) 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.
(2) 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.
(3) 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.
(4) 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.
(5) 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.5.3.2.4 |
tfrapDiagT1RmtLpbkCmdRemote 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.5.3.2.5 |
tfrapDiagT1TimeRemainingThe 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.5.3.2.6 |
tfrapDiagDteTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.3.3 |
tfrapDiagDteSigRTSStatus 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.5.3.3.1 |
tfrapDiagDteSigDTRStatus 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.5.3.3.2 |
tfrapDiagDteLclLpbkControls 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.5.3.3.3 |
tfrapDiagDteV54LpbkThis reports the status of any remote V54 testing initiated by
this unit. Remote 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.
(1) V54 loop up issued - indicates the node has sent 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.
(2) V54 loop down issued - indicates the node has sent 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.ro Enumeration .1.3.6.1.4.1.485.5.3.3.4 |
tfrapDiagDteRmtV54LpbkRemote 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.5.3.3.5 |
tfrapDiagDteBerStateThe 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 either the full T1 payload or only the bandwidth
allocated to the DTE (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 fractional T1 - replaces only the protion
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.rw Enumeration .1.3.6.1.4.1.485.5.3.3.6 |
tfrapDiagDteBerStatusDisplays 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.5.3.3.7 |
tfrapDiagDteBerErrorsDisplays the number of errors detected in Bert Test.ro Counter .1.3.6.1.4.1.485.5.3.3.8 |
tfrapDiagDteBerErrSecDisplays the number of seconds containing 1 or more errors
in BERT Test.ro Counter .1.3.6.1.4.1.485.5.3.3.9 |
tfrapDiagDteBerTimeElapsElapsed time since BERT test was started or cleared.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.485.5.3.3.10 |
tfrapDiagDteBerResyncsDisplays 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.5.3.3.11 |
tfrapDiagDteBerPatternThe 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.5.3.3.12 |
tfrapDiagDteTimeRemainingThe remaining time on the active diagnostic
before it times out and the unit returns to
normal operation. The time is hundredths of
seconds (TimeTicks).ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.485.5.3.3.13 |
tfrapDiagVnipTableTable of Diagnostics performed with the VNIP protocol SEQUENCE OF TFRAPDiagVnipEntry .1.3.6.1.4.1.485.5.3.6 |
tfrapDiagVnipEntryVNIP 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. TFRAPDiagVnipEntry .1.3.6.1.4.1.485.5.3.6.1 |
tfrapDiagVnipInterfaceThe 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.5.3.6.1.1 |
tfrapDiagVnipIndexThe 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.5.3.6.1.2 |
tfrapDiagVnipDlciThis is the DLCI value for the given interface/index
combination. This comes from the VniptTopologyTable.ro INTEGER .1.3.6.1.4.1.485.5.3.6.1.3 |
tfrapDiagVnipIpAddrThis is the ip address for the given interface/index
combination. This comes from the VniptTopologyTable.ro IpAddress .1.3.6.1.4.1.485.5.3.6.1.4 |
tfrapDiagVLOOPControls 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.5.3.6.1.5 |
tfrapDiagVBERTControls 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.5.3.6.1.6 |
tfrapDiagVBERTRateSpecifies 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.5.3.6.1.7 |
tfrapDiagVBERTSizeSpecifies 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 Enumeration .1.3.6.1.4.1.485.5.3.6.1.8 |
tfrapDiagVBERTPktPercentSpecifies 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.5.3.6.1.9 |
tfrapDiagVBERTTestPeriodSpecifies 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.5.3.6.1.10 |
tfrapStatus OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.4 |
tfrapStatusIntfTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.4.1 |
tfrapIntfDteModeStatus 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.5.4.1.1 |
tfrapIntfDteRtsStatus 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.5.4.1.2 |
tfrapIntfDteDtrStatus 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.5.4.1.3 |
tfrapIntfT1ModeStatus 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.5.4.1.4 |
tfrapIntfT1StatusStatus 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.5.4.1.5 |
tfrapIntfT1AlarmsAlarms 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.5.4.1.6 |
tfrapIntfDteDcdStatus 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.5.4.1.7 |
tfrapIntfDteDsrStatus 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.5.4.1.8 |
tfrapIntfDteCtsStatus 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.5.4.1.9 |
tfrapVnipTopologyTableVNIP 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 TFRAPVnipTopologyEntry .1.3.6.1.4.1.485.5.4.2 |
tfrapVnipTopologyEntryThe DLCI, IP address, and number of hops for a particular
node, discovered via VNIP off of an interface. The entry
may also have transit delay measurements and VBERT diagnostic
status to report as well. TFRAPVnipTopologyEntry .1.3.6.1.4.1.485.5.4.2.1 |
tfrapVnipTopologyInterfaceThe 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.5.4.2.1.1 |
tfrapVnipTopologyIndexThe 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.5.4.2.1.2 |
tfrapVnipTopologyDlciThe DLCI of the discovered neighboring peer.
This may be different from the local DLCI.ro INTEGER .1.3.6.1.4.1.485.5.4.2.1.3 |
tfrapVnipTopologyIpAddrThe IP address for the discovered peer.ro IpAddress .1.3.6.1.4.1.485.5.4.2.1.4 |
tfrapVnipTopologyNumHopsThe discovered peer is this number of hops away.
Each hop is a VNIP peer.ro INTEGER .1.3.6.1.4.1.485.5.4.2.1.5 |
tfrapVnipTopologyLocalDlciThe DLCI from this unit over which the remote peer
was discovered.ro INTEGER .1.3.6.1.4.1.485.5.4.2.1.6 |
tfrapVnipTopoTDNumSamplesThe number of transit delay samples collected.ro Counter .1.3.6.1.4.1.485.5.4.2.1.10 |
tfrapVnipTopoTDAvgDelayThe average transit delay between this
unit and the remote peer (in milliseconds).ro Counter .1.3.6.1.4.1.485.5.4.2.1.11 |
tfrapVnipTopoTDMaxDelayThe maximum transit delay between this
node and the remote peer (in milliseconds).ro Counter .1.3.6.1.4.1.485.5.4.2.1.12 |
tfrapVnipTopoTDMinDelayThe minimum transit delay between this
node and the remote peer (in milliseconds).ro Counter .1.3.6.1.4.1.485.5.4.2.1.13 |
tfrapVnipTopoTDLastDelayThe most recent transit delay measured between
this node and the remote peer (in milliseconds).ro Counter .1.3.6.1.4.1.485.5.4.2.1.14 |
tfrapVnipTopoVLOOPStatusThis 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.5.4.2.1.15 |
tfrapVnipTopoVBERTStatusDisplays 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.5.4.2.1.16 |
tfrapVnipTopoVBertTxDESetFramesDisplays 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.5.4.2.1.17 |
tfrapVnipTopoVBertRxDESetFramesDisplays 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.5.4.2.1.18 |
tfrapVnipTopoVBertTxDEClrFramesDisplays 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.5.4.2.1.19 |
tfrapVnipTopoVBertRxDEClrFramesDisplays 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.5.4.2.1.20 |
tfrapVnipTopoVBertTransitDelayMaxThe 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.5.4.2.1.21 |
tfrapVnipTopoVBertTransitDelayAvgThe 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.5.4.2.1.22 |
tfrapVnipTopoVBertTimeElapseElapsed time since VBERT/VLOOP test was started or cleared
(in seconds).ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.485.5.4.2.1.23 |
tfrapVnipTopoVBertPerUtilCIRThe 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.5.4.2.1.24 |
tfrapVnipTopoVBertPerUtilEIRThe 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.5.4.2.1.25 |
tfrapStatusMgmtTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.4.3 |
tfrapStatusMgmtChannelThis 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.5.4.3.1 |
tfrapStatusMgmtInterfaceThis 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.5.4.3.2 |
tfrapStatusMgmtInterfaceStatusThis 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.5.4.3.3 |
tfrapStatusMgmtDefaultDLCINoThis 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.5.4.3.4 |
tfrapStatusMgmtDefaultDLCIStatusThis 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.5.4.3.5 |
tfrapStatusLedTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.4.4 |
tfrapStatusDteModeLEDStatus 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.5.4.4.1 |
tfrapStatusDteStatusLEDStatus 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.5.4.4.2 |
tfrapStatusDteTxLEDStatus 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.5.4.4.3 |
tfrapStatusDteRxLEDStatus 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.5.4.4.4 |
tfrapStatusT1ModeLEDStatus 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.5.4.4.5 |
tfrapStatusT1StatusLEDStatus 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.5.4.4.6 |
tfrapStatusAllLEDsStatus of all six TFRAP 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 6 letters are DTE Mode, DTE status,
Dte Tx, Dte Rx, T1 Mode, and T1 Status. For example,
'555556' would mean: DTE in normal mode, active status,
transmitting and receiving and T1 normal with transient errors.ro DisplayString .1.3.6.1.4.1.485.5.4.4.7 |
tfrapVnipTransitDelayClearAllows 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.5.4.5 |
tfrapLmiSourcingIf 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.5.4.6 |
tfrapVBertClearAllows the user to clear all the VBERT data
collected in the VNIP topology database as long as
the entry is not in a test status.
(1) Clear all VBERT/VLOOP status informationrw Enumeration .1.3.6.1.4.1.485.5.4.11 |
tfrapStatusLmiAutosenseThis 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.5.4.12 |
tfrapPerformance OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.5 |
tfrapPerfPhysicalIntf OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.5.1 |
tfrapPerfT1CurrentTableThe 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 TfrapT1CurrentEntry .1.3.6.1.4.1.485.5.5.1.1 |
tfrapT1CurrentEntryAn entry in the T1 Current Perf table. This table is
structured for devices to support multiple T1 interfaces. TfrapT1CurrentEntry .1.3.6.1.4.1.485.5.5.1.1.1 |
tfrapT1CurrentIndexThe index value which uniquely identifies the
T1 interface to which this entry is applicable.
There's only one T1 on this unit so the index
will always be 1.ro INTEGER .1.3.6.1.4.1.485.5.5.1.1.1.1 |
tfrapT1CurrentCrc6EventsCount 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 tfrapT1PerfClearEvents.
Not applicable if D4/SF framing is selcted.ro Gauge .1.3.6.1.4.1.485.5.5.1.1.1.2 |
tfrapT1CurrentOofEventsCount 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 tfrapT1PerfClearEvents.ro Gauge .1.3.6.1.4.1.485.5.5.1.1.1.3 |
tfrapT1CurrentESsThe 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.5.5.1.1.1.4 |
tfrapT1CurrentSESsThe 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.5.5.1.1.1.5 |
tfrapT1CurrentSEFSsThe 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.5.5.1.1.1.6 |
tfrapT1CurrentUASsThe 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.5.5.1.1.1.7 |
tfrapT1CurrentCSSsThe 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.5.5.1.1.1.8 |
tfrapT1CurrentBESsThe 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.5.5.1.1.1.9 |
tfrapT1CurrentLCVsThe 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.5.5.1.1.1.10 |
tfrapPerfT1IntervalTableThe 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 TfrapT1IntervalEntry .1.3.6.1.4.1.485.5.5.1.2 |
tfrapT1IntervalEntryAn entry in the DS1 Interval table which includes physical
layer statistics for each of the prior 96 15-minute intervals. TfrapT1IntervalEntry .1.3.6.1.4.1.485.5.5.1.2.1 |
tfrapT1IntervalIndexThe index value which uniquely identifies the
t1 interface to which this entry is applicable.
There is only one T1 on this unit so this index
will be 1.ro INTEGER .1.3.6.1.4.1.485.5.5.1.2.1.1 |
tfrapT1IntervalNumberA number between 1 and 96, where 96 is the most
recently completed 15 minute interval and 1
occurred 24 hours ago (assuming that all 96
intervals are valid).ro INTEGER .1.3.6.1.4.1.485.5.5.1.2.1.2 |
tfrapT1IntervalESsThe 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.5.5.1.2.1.3 |
tfrapT1IntervalSESsThe 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.5.5.1.2.1.4 |
tfrapT1IntervalSEFSsThe 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.5.5.1.2.1.5 |
tfrapT1IntervalUASsThe 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.5.5.1.2.1.6 |
tfrapT1IntervalCSSsThe 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.5.5.1.2.1.7 |
tfrapT1IntervalBESsThe 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.5.5.1.2.1.8 |
tfrapT1IntervalLCVsThe 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.5.5.1.2.1.9 |
tfrapPerfT1TotalTableThe 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 TfrapT1TotalEntry .1.3.6.1.4.1.485.5.5.1.3 |
tfrapT1TotalEntryAn entry in the T1 Physical Layer Measurement Totals table. TfrapT1TotalEntry .1.3.6.1.4.1.485.5.5.1.3.1 |
tfrapT1TotalIndexThe index value which uniquely identifies the
t1 interface to which this entry is applica-
ble. There is only one T1 port on this device
so this index must be 1.ro INTEGER .1.3.6.1.4.1.485.5.5.1.3.1.1 |
tfrapT1TotalESsThe 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.5.5.1.3.1.2 |
tfrapT1TotalSESsThe 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.5.5.1.3.1.3 |
tfrapT1TotalSEFSsThe 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.5.5.1.3.1.4 |
tfrapT1TotalUASsThe 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.5.5.1.3.1.5 |
tfrapT1TotalCSSsThe 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.5.5.1.3.1.6 |
tfrapT1TotalBESsThe 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.5.5.1.3.1.7 |
tfrapT1TotalLCVsThe 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.5.5.1.3.1.8 |
tfrapT1PerfCmdTypeTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.5.1.4 |
tfrapT1PerfFreezeStateThis 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.5.5.1.4.1 |
tfrapT1PerfClearEventsThis 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.5.5.1.4.2 |
tfrapT1PerfClearAllThis command resets all of the (user's) performance
registers.rw Enumeration .1.3.6.1.4.1.485.5.5.1.4.3 |
tfrapPerfMgmtIp OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.5.2 |
tfrapPerfMgmtIpIFStatsTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.5.2.1 |
tfrapPerfMgmtIpIFInOctetsThe 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.5.5.2.1.1 |
tfrapPerfMgmtIpIFInErrorsThe 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.5.5.2.1.2 |
tfrapPerfMgmtIpIFOutOctetsThe 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.5.5.2.1.3 |
tfrapPerfMgmtIpIFOperStatusThe 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.5.5.2.1.4 |
tfrapPerfMgmtIpIPStatsTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.5.2.2 |
tfrapPerfMgmtIpIPInRcvThe 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.5.5.2.2.1 |
tfrapPerfMgmtIpIPInHdrErrThe 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.5.5.2.2.2 |
tfrapPerfMgmtIpIPInAddrErrThe 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.5.5.2.2.3 |
tfrapPerfMgmtIpIPInProtUnkThe 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.5.5.2.2.4 |
tfrapPerfMgmtIpIPInDscrdThe 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.5.5.2.2.5 |
tfrapPerfMgmtIpIPInDlvrsThe 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.5.5.2.2.6 |
tfrapPerfMgmtIpIPOutRqstThe 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.5.5.2.2.7 |
tfrapPerfMgmtIpIPOutDscrdThe 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.5.5.2.2.8 |
tfrapPerfMgmtIpIPOutNoRtThe 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.5.5.2.2.9 |
tfrapPerfMgmtIpICMPStatsTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.5.2.3 |
tfrapPerfMgmtIpICMPInMsgsThe 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.5.5.2.3.1 |
tfrapPerfMgmtIpICMPInErrorsThe 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.5.5.2.3.2 |
tfrapPerfMgmtIpICMPInDestUnreachsThe 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.5.5.2.3.3 |
tfrapPerfMgmtIpICMPInTimeExcdsThe 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.5.5.2.3.4 |
tfrapPerfMgmtIpICMPInParmProbsThe 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.5.5.2.3.5 |
tfrapPerfMgmtIpICMPInRedirectsThe 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.5.5.2.3.6 |
tfrapPerfMgmtIpICMPInEchosThe 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.5.5.2.3.7 |
tfrapPerfMgmtIpICMPInEchoRepsThe 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.5.5.2.3.8 |
tfrapPerfMgmtIpICMPOutMsgsThe 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.5.5.2.3.9 |
tfrapPerfMgmtIpICMPOutErrorsThe 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.5.5.2.3.10 |
tfrapPerfMgmtIpICMPOutDestUnreachsThe 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.5.5.2.3.11 |
tfrapPerfMgmtIpICMPOutParmProbsThe 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.5.5.2.3.12 |
tfrapPerfMgmtIpICMPOutRedirectsThe 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.5.5.2.3.13 |
tfrapPerfMgmtIpICMPOutEchosThe 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.5.5.2.3.14 |
tfrapPerfMgmtIpICMPOutEchoRepsThe 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.5.5.2.3.15 |
tfrapPerfMgmtIpUDPStatsTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.5.2.4 |
tfrapPerfMgmtIpUDPInDatagramsThe 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.5.5.2.4.1 |
tfrapPerfMgmtIpUDPOutDatagramsThe count of all UDP datagrams generated by
this unit. Same as udpOutDatagrams in mib-2.ro Counter .1.3.6.1.4.1.485.5.5.2.4.2 |
tfrapPerfMgmtIpUDPNoPortsThe 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.5.5.2.4.3 |
tfrapPerfMgmtIpTCPStatsTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.5.2.5 |
tfrapPerfMgmtIpTCPActiveOpensThe 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.5.5.2.5.1 |
tfrapPerfMgmtIpTCPPassiveOpensThe 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.5.5.2.5.2 |
tfrapPerfMgmtIpTCPAttemptFailsThe 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.5.5.2.5.3 |
tfrapPerfMgmtIpTCPCurrEstabThe 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.5.5.2.5.4 |
tfrapPerfMgmtIpTCPInSegsThe 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.5.5.2.5.5 |
tfrapPerfMgmtIpTCPOutSegsThe count of all the segments generated from this unit.
Same as tcpOutSegs in mib-2.ro Counter .1.3.6.1.4.1.485.5.5.2.5.6 |
tfrapPerfThruput OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.5.3 |
tfrapPerfThruputPerIntfTableThe throughput per interface table. These values are accumulated
across all DLCIs. SEQUENCE OF TfrapPerfThruputPerIntfEntry .1.3.6.1.4.1.485.5.5.3.1 |
tfrapPerfThruputPerIntfEntryAn entry in the throughput per interface table. TfrapPerfThruputPerIntfEntry .1.3.6.1.4.1.485.5.5.3.1.1 |
tfrapPerfThruputPerIntfIndexInterface for which the statistics apply.
(1) DTE interface
(2) T1 interfacero Enumeration .1.3.6.1.4.1.485.5.5.3.1.1.1 |
tfrapPerfThruputPerIntfRxByteCntThe number of framed bytes that have been received
on this interface.ro Counter .1.3.6.1.4.1.485.5.5.3.1.1.2 |
tfrapPerfThruputPerIntfTxByteCntThe number of framed bytes that have been transmit
on this interface.ro Counter .1.3.6.1.4.1.485.5.5.3.1.1.3 |
tfrapPerfThruputPerIntfRxFrameCntThe number of frames that have been received
on this interface.ro Counter .1.3.6.1.4.1.485.5.5.3.1.1.4 |
tfrapPerfThruputPerIntfTxFrameCntThe number of frames that have been transmit
on this interface.ro Counter .1.3.6.1.4.1.485.5.5.3.1.1.5 |
tfrapPerfThruputPerIntfRxCrcErrCntThe number of frames with CRC errors received
on this interface.ro Counter .1.3.6.1.4.1.485.5.5.3.1.1.6 |
tfrapPerfThruputPerIntfRxAbortCntThe number of aborted frames received
on this interface.ro Counter .1.3.6.1.4.1.485.5.5.3.1.1.7 |
tfrapPerfThruputPerDlciTableLayer 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 TfrapPerfThruputPerDlciEntry .1.3.6.1.4.1.485.5.5.3.2 |
tfrapPerfThruputPerDlciEntryThe Statistics for a particular Data Link
Connection Management Interface (DLCI). TfrapPerfThruputPerDlciEntry .1.3.6.1.4.1.485.5.5.3.2.1 |
tfrapPerfThruputPerDlciIndexThis 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.5.5.3.2.1.1 |
tfrapPerfThruputPerDlciValueThe DLCI value in which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.5.5.3.2.1.2 |
tfrapPerfThruputPerDlciCreateTimeThe 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.5.5.3.2.1.3 |
tfrapPerfThruputPerDlciChangeTimeThe 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.5.5.3.2.1.4 |
tfrapPerfThruputPerDlciRxByteThe 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.5.5.3.2.1.5 |
tfrapPerfThruputPerDlciTxByteThe 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.5.5.3.2.1.6 |
tfrapPerfThruputPerDlciRxFrameThe 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.5.5.3.2.1.7 |
tfrapPerfThruputPerDlciTxFrameThe 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.5.5.3.2.1.8 |
tfrapPerfThruputPerDlciRxFecnThe 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.5.5.3.2.1.9 |
tfrapPerfThruputPerDlciRxBecnThe 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.5.5.3.2.1.10 |
tfrapPerfThruputPerDlciRxDeThe 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.5.5.3.2.1.11 |
tfrapPerfThruputPerDlciTxDeThe 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.5.5.3.2.1.12 |
tfrapPerfThruputPerDlciRxThruputThe 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.5.5.3.2.1.13 |
tfrapPerfThruputPerDlciTxThruputThe 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.5.5.3.2.1.14 |
tfrapPerfThruputPerDlciCIRThe 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.5.5.3.2.1.15 |
tfrapPerfThruputPerDlciUptimeThe 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.5.5.3.2.1.16 |
tfrapPerfThruputPerDlciDowntimeThe 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.5.5.3.2.1.17 |
tfrapPerfThruputPerDlciCirTypeThe 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.5.5.3.2.1.18 |
tfrapPerfThruputPerDlciPvcStateThe 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.5.5.3.2.1.19 |
tfrapPerfThruputPerDlciOutageCountThe 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.5.5.3.2.1.20 |
tfrapPerfThruputPerDlciAvailabilityThe 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.5.5.3.2.1.21 |
tfrapPerfThruputPerDlciMTBSOMean Time Between Service Outages: UpTime/OutageCount
or zero if OutageCount = 0 (in seconds).ro INTEGER .1.3.6.1.4.1.485.5.5.3.2.1.22 |
tfrapPerfThruputPerDlciMTTSRMean Time to ServiceRestoral: DownTime/OutageCount
or zero if OutageCount = 0 (in seconds).ro INTEGER .1.3.6.1.4.1.485.5.5.3.2.1.23 |
tfrapPerfThruputPerDlciEncapTypeThe 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.5.5.3.2.1.24 |
tfrapPerfThruputPerDlciRxUtilizationStatusThe 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.5.5.3.2.1.25 |
tfrapPerfThruputPerDlciTxUtilizationStatusThe 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.5.5.3.2.1.26 |
tfrapPerfThruputPerDlciEIRThe 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.5.5.3.2.1.27 |
tfrapPerfThruputCommands OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.5.3.3 |
tfrapPerfThruputCmdClearDteStatsAllows 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.5.5.3.3.1 |
tfrapPerfThruputCmdClearT1StatsAllows 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.5.5.3.3.2 |
tfrapPerfThruputCmdClearAllIntfStatsAllows the user to zero out all the statistics in
the ThruputPerIntf statistics table.rw Enumeration .1.3.6.1.4.1.485.5.5.3.3.3 |
tfrapPerfThruputCmdClearDlciStatsAllows 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.5.5.3.3.4 |
tfrapPerfThruputCmdClearAllStatsAllows 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.5.5.3.3.5 |
tfrapPerfThruputCmdRemoveStsDlciAllows the user to remove a Dlci from the short term
statistics tables.rw INTEGER .1.3.6.1.4.1.485.5.5.3.3.6 |
tfrapPerfThruputCmdReplaceDlciTableAllows the user to replace one DLCI in the short-term
statistics table with another one. SEQUENCE OF TfrapPerfThruputCmdReplaceDlciEntry .1.3.6.1.4.1.485.5.5.3.3.7 |
tfrapPerfThruputCmdReplaceDlciEntryAllows the user to replace one DLCI in the short-term
statistics table with another one. TfrapPerfThruputCmdReplaceDlciEntry .1.3.6.1.4.1.485.5.5.3.3.7.1 |
tfrapPerfThruputCmdReplaceDlciValueA 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.5.5.3.3.7.1.1 |
tfrapPerfThruputCmdReplaceDlciNewValueA 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.5.5.3.3.7.1.2 |
tfrapPerfThruputCmdAvailabilityStsDlciResetAllows 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.5.5.3.3.8 |
tfrapPerfThruputCmdAvailabilityStsDlciResetAllAllows 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.5.5.3.3.9 |
tfrapPerfThruputCmdCountsStsDlciResetAllows 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.5.5.3.3.10 |
tfrapPerfThruputCmdCountsStsDlciResetAllAllows 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.5.5.3.3.11 |
tfrapPerfThruputCmdAllStsDlciResetAllows 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.5.5.3.3.12 |
tfrapPerfThruputCmdAllStsDlciResetAllAllows 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.5.5.3.3.13 |
tfrapPerfNetworkShortTerm OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.5.4 |
tfrapPerfNetwProtoPerDlciTableThe 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 TfrapPerfNetwProtoPerDlciEntry .1.3.6.1.4.1.485.5.5.4.1 |
tfrapPerfNetwProtoPerDlciEntryThe Network Layer Short Term Statistics
for a particular DLCI. This table organizes
statistics by high-layer network protocol. TfrapPerfNetwProtoPerDlciEntry .1.3.6.1.4.1.485.5.5.4.1.1 |
tfrapPerfNetwProtoPerDlciIntervalThe 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.5.5.4.1.1.1 |
tfrapPerfNetwProtoPerDlciValueThe DLCI value with which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.5.5.4.1.1.2 |
tfrapPerfNetwProtoPerDlciRxTotalThe total number of received Network Layer bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.1.1.3 |
tfrapPerfNetwProtoPerDlciTxTotalThe total number of transmitted Network Layer bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.1.1.4 |
tfrapPerfNetwProtoPerDlciRxIpThe number of received IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.1.1.5 |
tfrapPerfNetwProtoPerDlciTxIpThe number of transmitted IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.1.1.6 |
tfrapPerfNetwProtoPerDlciRxIpxThe number of received IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.1.1.7 |
tfrapPerfNetwProtoPerDlciTxIpxThe number of transmitted IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.1.1.8 |
tfrapPerfNetwProtoPerDlciRxSnaThe number of received SNA bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.1.1.9 |
tfrapPerfNetwProtoPerDlciTxSnaThe number of transmitted SNA bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.1.1.10 |
tfrapPerfNetwProtoPerDlciRxArpThe number of received ARP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.1.1.11 |
tfrapPerfNetwProtoPerDlciTxArpThe number of transmitted ARP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.1.1.12 |
tfrapPerfNetwProtoPerDlciRxCiscoThe number of received Cisco protocol bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.1.1.13 |
tfrapPerfNetwProtoPerDlciTxCiscoThe number of transmitted Cisco protocol bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.1.1.14 |
tfrapPerfNetwProtoPerDlciRxOtherThe 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.5.5.4.1.1.15 |
tfrapPerfNetwProtoPerDlciTxOtherThe 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.5.5.4.1.1.16 |
tfrapPerfNetwProtoPerDlciRxVnipThe number of received VNIP protocol bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.1.1.17 |
tfrapPerfNetwProtoPerDlciTxVnipThe number of transmitted VNIP protocol bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.1.1.18 |
tfrapPerfNetwProtoPerDlciRxAnnexGThe number of received Annex G protocol
bytes that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.1.1.19 |
tfrapPerfNetwProtoPerDlciTxAnnexGThe number of transmitted Annex G protocol
bytes that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.1.1.20 |
tfrapPerfNetwProtoTotalTableThe Short Term Statistics on Network Layer
protocols summed across all DLCIs. SEQUENCE OF TfrapPerfNetwProtoTotalEntry .1.3.6.1.4.1.485.5.5.4.2 |
tfrapPerfNetwProtoTotalEntryThe Network Layer Short Term Statistics
for a particular DLCI. TfrapPerfNetwProtoTotalEntry .1.3.6.1.4.1.485.5.5.4.2.1 |
tfrapPerfNetwProtoTotalIntervalThe 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.5.5.4.2.1.1 |
tfrapPerfNetwProtoTotalRxTotalThe total number of received Network Layer bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.2.1.3 |
tfrapPerfNetwProtoTotalTxTotalThe total number of transmitted Network Layer bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.2.1.4 |
tfrapPerfNetwProtoTotalRxIpThe number of received IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.2.1.5 |
tfrapPerfNetwProtoTotalTxIpThe number of transmitted IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.2.1.6 |
tfrapPerfNetwProtoTotalRxIpxThe number of received IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.2.1.7 |
tfrapPerfNetwProtoTotalTxIpxThe number of transmitted IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.2.1.8 |
tfrapPerfNetwProtoTotalRxSnaThe number of received SNA bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.2.1.9 |
tfrapPerfNetwProtoTotalTxSnaThe number of transmitted SNA bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.2.1.10 |
tfrapPerfNetwProtoTotalRxArpThe number of received ARP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.2.1.11 |
tfrapPerfNetwProtoTotalTxArpThe number of transmitted ARP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.2.1.12 |
tfrapPerfNetwProtoTotalRxCiscoThe number of received Cisco protocol bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.2.1.13 |
tfrapPerfNetwProtoTotalTxCiscoThe number of transmitted Cisco protocol bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.2.1.14 |
tfrapPerfNetwProtoTotalRxOtherThe number of received bytes across all DLCIs
from protocols that are not counted elsewhere
in this table.ro Counter .1.3.6.1.4.1.485.5.5.4.2.1.15 |
tfrapPerfNetwProtoTotalTxOtherThe number of transmitted bytes across all DLCIs
from protocols that are not counted elsewhere
in this table.ro Counter .1.3.6.1.4.1.485.5.5.4.2.1.16 |
tfrapPerfNetwProtoTotalRxVnipThe number of received VNIP protocol bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.2.1.17 |
tfrapPerfNetwProtoTotalTxVnipThe number of transmitted VNIP protocol bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.2.1.18 |
tfrapPerfNetwProtoTotalRxAnnexGThe number of received Annex G protocol bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.2.1.19 |
tfrapPerfNetwProtoTotalTxAnnexGThe number of transmitted Annex G protocol bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.2.1.20 |
tfrapPerfIpPerDlciTableThe Short Term Statistics on the IP
protocol for each DLCI. SEQUENCE OF TfrapPerfIpPerDlciEntry .1.3.6.1.4.1.485.5.5.4.3 |
tfrapPerfIpPerDlciEntryThe IP Short Term Statistics for a particular DLCI. TfrapPerfIpPerDlciEntry .1.3.6.1.4.1.485.5.5.4.3.1 |
tfrapPerfIpPerDlciIntervalThe 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.5.5.4.3.1.1 |
tfrapPerfIpPerDlciValueThe DLCI value with which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.5.5.4.3.1.2 |
tfrapPerfIpPerDlciRxTotalThe total number of received IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.3.1.3 |
tfrapPerfIpPerDlciTxTotalThe total number of transmitted IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.3.1.4 |
tfrapPerfIpPerDlciRxTcpThe number of received TCP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.3.1.5 |
tfrapPerfIpPerDlciTxTcpThe number of transmitted TCP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.3.1.6 |
tfrapPerfIpPerDlciRxUdpThe number of received UDP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.3.1.7 |
tfrapPerfIpPerDlciTxUdpThe number of transmitted UDP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.3.1.8 |
tfrapPerfIpPerDlciRxIcmpThe number of received ICMP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.3.1.9 |
tfrapPerfIpPerDlciTxIcmpThe number of transmitted ICMP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.3.1.10 |
tfrapPerfIpPerDlciRxOtherThe 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.5.5.4.3.1.11 |
tfrapPerfIpPerDlciTxOtherThe 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.5.5.4.3.1.12 |
tfrapPerfIpPerDlciRxIgrpThe number of received IGRP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.3.1.13 |
tfrapPerfIpPerDlciTxIgrpThe number of transmitted IGRP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.3.1.14 |
tfrapPerfIpTotalTableThe Short Term Statistics on the IP
protocol across all DLCIs. SEQUENCE OF TfrapPerfIpTotalEntry .1.3.6.1.4.1.485.5.5.4.4 |
tfrapPerfIpTotalEntryThe IP Short Term Statistics across all DLCIs. TfrapPerfIpTotalEntry .1.3.6.1.4.1.485.5.5.4.4.1 |
tfrapPerfIpTotalIntervalThe 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.5.5.4.4.1.1 |
tfrapPerfIpTotalRxTotalThe total number of received IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.4.1.3 |
tfrapPerfIpTotalTxTotalThe total number of transmitted IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.4.1.4 |
tfrapPerfIpTotalRxTcpThe number of received TCP over IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.4.1.5 |
tfrapPerfIpTotalTxTcpThe number of transmitted TCP over IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.4.1.6 |
tfrapPerfIpTotalRxUdpThe number of received UDP over IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.4.1.7 |
tfrapPerfIpTotalTxUdpThe number of transmitted UDP over IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.4.1.8 |
tfrapPerfIpTotalRxIcmpThe number of received ICMP over IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.4.1.9 |
tfrapPerfIpTotalTxIcmpThe number of transmitted ICMP over IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.4.1.10 |
tfrapPerfIpTotalRxOtherThe number of received bytes across all DLCIs
from protocols over IP that are not counted
elsewhere in this table.ro Counter .1.3.6.1.4.1.485.5.5.4.4.1.11 |
tfrapPerfIpTotalTxOtherThe number of transmitted bytes across all DLCIs.
from protocols over IP that are not counted
elsewhere in this table.ro Counter .1.3.6.1.4.1.485.5.5.4.4.1.12 |
tfrapPerfIpTotalRxIgrpThe number of received IGRP over IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.4.1.13 |
tfrapPerfIpTotalTxIgrpThe number of transmitted IGRP over IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.4.1.14 |
tfrapPerfIcmpPerDlciTableShort Term Statistics on the ICMP
protocol for each DLCI. SEQUENCE OF TfrapPerfIcmpPerDlciEntry .1.3.6.1.4.1.485.5.5.4.5 |
tfrapPerfIcmpPerDlciEntryThe ICMP Short Term Statistics for a particular DLCI. TfrapPerfIcmpPerDlciEntry .1.3.6.1.4.1.485.5.5.4.5.1 |
tfrapPerfIcmpPerDlciIntervalThe 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.5.5.4.5.1.1 |
tfrapPerfIcmpPerDlciValueThe DLCI value in which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.5.5.4.5.1.2 |
tfrapPerfIcmpPerDlciRxTotalThe total number of ICMP bytes that have been
counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.5.1.3 |
tfrapPerfIcmpPerDlciTxTotalThe total number of ICMP bytes that have been
counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.5.1.4 |
tfrapPerfIcmpPerDlciRxEchoRepThe number of bytes in ICMP ECHO repies
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.5.1.5 |
tfrapPerfIcmpPerDlciTxEchoRepThe number of bytes in ICMP ECHO repies
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.5.1.6 |
tfrapPerfIcmpPerDlciRxDestUnrThe number of bytes in ICMP destination unreachables
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.5.1.7 |
tfrapPerfIcmpPerDlciTxDestUnrThe number of bytes in ICMP destination unreachables
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.5.1.8 |
tfrapPerfIcmpPerDlciRxSrcQuenchThe number of bytes in ICMP source quenches
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.5.1.9 |
tfrapPerfIcmpPerDlciTxSrcQuenchThe number of bytes in ICMP source quenches
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.5.1.10 |
tfrapPerfIcmpPerDlciRxRedirectThe number of bytes in ICMP redirects
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.5.1.11 |
tfrapPerfIcmpPerDlciTxRedirectThe number of bytes in ICMP redirects
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.5.1.12 |
tfrapPerfIcmpPerDlciRxEchoReqThe number of bytes in ICMP ECHO requests
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.5.1.13 |
tfrapPerfIcmpPerDlciTxEchoReqThe number of bytes in ICMP ECHO requests
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.5.1.14 |
tfrapPerfIcmpPerDlciRxTimeExcdThe number of bytes in ICMP time exceededs
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.5.1.15 |
tfrapPerfIcmpPerDlciTxTimeExcdThe number of bytes in ICMP time exceededs
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.5.1.16 |
tfrapPerfIcmpPerDlciRxParamProbThe number of bytes in ICMP parameter problems
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.5.1.17 |
tfrapPerfIcmpPerDlciTxParamProbThe number of bytes in ICMP parameter problems
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.5.1.18 |
tfrapPerfIcmpPerDlciRxTimestpReqThe number of bytes in ICMP timestamp requests
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.5.1.19 |
tfrapPerfIcmpPerDlciTxTimestpReqThe number of bytes in ICMP timestamp requests
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.5.1.20 |
tfrapPerfIcmpPerDlciRxTimestpRepThe number of bytes in ICMP timestamp replies
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.5.1.21 |
tfrapPerfIcmpPerDlciTxTimestpRepThe number of bytes in ICMP timestamp replies
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.5.1.22 |
tfrapPerfIcmpPerDlciRxAddrMaskReqThe number of bytes in ICMP address mask requests
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.5.1.23 |
tfrapPerfIcmpPerDlciTxAddrMaskReqThe number of bytes in ICMP address mask requests
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.5.1.24 |
tfrapPerfIcmpPerDlciRxAddrMaskRepThe number of bytes in ICMP address mask replies
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.5.1.25 |
tfrapPerfIcmpPerDlciTxAddrMaskRepThe number of bytes in ICMP address mask replies
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.5.1.26 |
tfrapPerfIcmpPerDlciRxPktTooBigThe number of bytes in ICMP packet too bigs
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.5.1.27 |
tfrapPerfIcmpPerDlciTxPktTooBigThe number of bytes in ICMP packet too bigs
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.5.1.28 |
tfrapPerfIcmpPerDlciRxGmQueryThe number of bytes in ICMP group membership
queries that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.5.1.29 |
tfrapPerfIcmpPerDlciTxGmQueryThe number of bytes in ICMP group membership
queries that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.5.1.30 |
tfrapPerfIcmpPerDlciRxGmReportThe number of bytes in ICMP group membership
reports that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.5.1.31 |
tfrapPerfIcmpPerDlciTxGmReportThe number of bytes in ICMP group membership
reports that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.5.1.32 |
tfrapPerfIcmpPerDlciRxGmReductThe number of bytes in ICMP group membership
reductions that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.5.1.33 |
tfrapPerfIcmpPerDlciTxGmReductThe number of bytes in ICMP group membership
reductions that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.5.1.34 |
tfrapPerfIcmpTotalTableShort Term Statistics on the ICMP
protocol across all DLCIs. SEQUENCE OF TfrapPerfIcmpTotalEntry .1.3.6.1.4.1.485.5.5.4.6 |
tfrapPerfIcmpTotalEntryThe ICMP Short Term Statistics for a particular DLCI. TfrapPerfIcmpTotalEntry .1.3.6.1.4.1.485.5.5.4.6.1 |
tfrapPerfIcmpTotalIntervalThe 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.5.5.4.6.1.1 |
tfrapPerfIcmpTotalRxTotalThe total number of ICMP bytes that have been
counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.6.1.3 |
tfrapPerfIcmpTotalTxTotalThe total number of ICMP bytes that have been
counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.6.1.4 |
tfrapPerfIcmpTotalRxEchoRepThe number of bytes in ICMP ECHO repies
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.6.1.5 |
tfrapPerfIcmpTotalTxEchoRepThe number of bytes in ICMP ECHO repies
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.6.1.6 |
tfrapPerfIcmpTotalRxDestUnrThe number of bytes in ICMP destination unreachables
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.6.1.7 |
tfrapPerfIcmpTotalTxDestUnrThe number of bytes in ICMP destination unreachables
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.6.1.8 |
tfrapPerfIcmpTotalRxSrcQuenchThe number of bytes in ICMP source quenches
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.6.1.9 |
tfrapPerfIcmpTotalTxSrcQuenchThe number of bytes in ICMP source quenches
that have been counte across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.6.1.10 |
tfrapPerfIcmpTotalRxRedirectThe number of bytes in ICMP redirects
that have been counte across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.6.1.11 |
tfrapPerfIcmpTotalTxRedirectThe number of bytes in ICMP redirects
that have been counte across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.6.1.12 |
tfrapPerfIcmpTotalRxEchoReqThe number of bytes in ICMP ECHO requests
that have been counte across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.6.1.13 |
tfrapPerfIcmpTotalTxEchoReqThe number of bytes in ICMP ECHO requests
that have been counte across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.6.1.14 |
tfrapPerfIcmpTotalRxTimeExcdThe number of bytes in ICMP time exceededs
that have been counte across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.6.1.15 |
tfrapPerfIcmpTotalTxTimeExcdThe number of bytes in ICMP time exceededs
that have been counte across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.6.1.16 |
tfrapPerfIcmpTotalRxParamProbThe number of bytes in ICMP parameter problems
that have been counte across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.6.1.17 |
tfrapPerfIcmpTotalTxParamProbThe number of bytes in ICMP parameter problems
that have been counte across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.6.1.18 |
tfrapPerfIcmpTotalRxTimestpReqThe number of bytes in ICMP timestamp requests
that have been counte across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.6.1.19 |
tfrapPerfIcmpTotalTxTimestpReqThe number of bytes in ICMP timestamp requests
that have been counte across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.6.1.20 |
tfrapPerfIcmpTotalRxTimestpRepThe number of bytes in ICMP timestamp replies
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.6.1.21 |
tfrapPerfIcmpTotalTxTimestpRepThe number of bytes in ICMP timestamp replies
that have been counte across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.6.1.22 |
tfrapPerfIcmpTotalRxAddrMaskReqThe number of bytes in ICMP address mask requests
that have been counte across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.6.1.23 |
tfrapPerfIcmpTotalTxAddrMaskReqThe number of bytes in ICMP address mask requests
that have been counte across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.6.1.24 |
tfrapPerfIcmpTotalRxAddrMaskRepThe number of bytes in ICMP address mask replies
that have been counte across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.6.1.25 |
tfrapPerfIcmpTotalTxAddrMaskRepThe number of bytes in ICMP address mask replies
that have been counte across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.6.1.26 |
tfrapPerfIcmpTotalRxPktTooBigThe number of bytes in ICMP packet too bigs
that have been counte across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.6.1.27 |
tfrapPerfIcmpTotalTxPktTooBigThe number of bytes in ICMP packet too bigs
that have been counte across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.6.1.28 |
tfrapPerfIcmpTotalRxGmQueryThe number of bytes in ICMP group membership
queries that have been counte across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.6.1.29 |
tfrapPerfIcmpTotalTxGmQueryThe number of bytes in ICMP group membership
queries that have been counte across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.6.1.30 |
tfrapPerfIcmpTotalRxGmReportThe number of bytes in ICMP group membership
reports that have been counte across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.6.1.31 |
tfrapPerfIcmpTotalTxGmReportThe number of bytes in ICMP group membership
reports that have been counte across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.6.1.32 |
tfrapPerfIcmpTotalRxGmReductThe number of bytes in ICMP group membership
reductions that have been counte across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.6.1.33 |
tfrapPerfIcmpTotalTxGmReductThe number of bytes in ICMP group membership
reductions that have been counte across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.6.1.34 |
tfrapPerfApplicationPerDlciTableThe Short Term Statistics on the Application
protocol for each DLCI. SEQUENCE OF TfrapPerfApplicationPerDlciEntry .1.3.6.1.4.1.485.5.5.4.7 |
tfrapPerfApplicationPerDlciEntryThe Application Short Term Statistics for a particular DLCI. TfrapPerfApplicationPerDlciEntry .1.3.6.1.4.1.485.5.5.4.7.1 |
tfrapPerfApplicationPerDlciIntervalThe 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.5.5.4.7.1.1 |
tfrapPerfApplicationPerDlciValueThe DLCI value with which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.5.5.4.7.1.2 |
tfrapPerfApplicationPerDlciRxSnmpThe number of received SNMP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.7.1.3 |
tfrapPerfApplicationPerDlciTxSnmpThe number of transmitted SNMP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.7.1.4 |
tfrapPerfApplicationPerDlciRxSnmpTrapThe number of received SNMP TRAP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.7.1.5 |
tfrapPerfApplicationPerDlciTxSnmpTrapThe number of transmitted SNMP TRAP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.7.1.6 |
tfrapPerfApplicationPerDlciRxHttpThe number of received HTTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.7.1.7 |
tfrapPerfApplicationPerDlciTxHttpThe number of transmitted HTTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.7.1.8 |
tfrapPerfApplicationPerDlciRxTelnetThe number of received Telnet bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.7.1.9 |
tfrapPerfApplicationPerDlciTxTelnetThe number of transmitted Telnet bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.7.1.10 |
tfrapPerfApplicationPerDlciRxSmtpThe number of received SMTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.7.1.11 |
tfrapPerfApplicationPerDlciTxSmtpThe number of transmitted SMTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.7.1.12 |
tfrapPerfApplicationPerDlciRxFtpThe number of received FTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.7.1.13 |
tfrapPerfApplicationPerDlciTxFtpThe number of transmitted FTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.7.1.14 |
tfrapPerfApplicationPerDlciRxTftpThe number of received TFTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.7.1.15 |
tfrapPerfApplicationPerDlciTxTftpThe number of transmitted TFTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.7.1.16 |
tfrapPerfApplicationPerDlciRxCustom1The 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.5.5.4.7.1.17 |
tfrapPerfApplicationPerDlciTxCustom1The 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.5.5.4.7.1.18 |
tfrapPerfApplicationPerDlciRxCustom2The 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.5.5.4.7.1.19 |
tfrapPerfApplicationPerDlciTxCustom2The 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.5.5.4.7.1.20 |
tfrapPerfApplicationPerDlciRxCustom3The 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.5.5.4.7.1.21 |
tfrapPerfApplicationPerDlciTxCustom3The 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.5.5.4.7.1.22 |
tfrapPerfApplicationPerDlciRxCustom4The 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.5.5.4.7.1.23 |
tfrapPerfApplicationPerDlciTxCustom4The 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.5.5.4.7.1.24 |
tfrapPerfApplicationTotalTableThe Short Term Statistics on the Application
protocol across all DLCIs. SEQUENCE OF TfrapPerfApplicationTotalEntry .1.3.6.1.4.1.485.5.5.4.8 |
tfrapPerfApplicationTotalEntryThe Application Short Term Statistics for a particular DLCI. TfrapPerfApplicationTotalEntry .1.3.6.1.4.1.485.5.5.4.8.1 |
tfrapPerfApplicationTotalIntervalThe 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.5.5.4.8.1.1 |
tfrapPerfApplicationTotalRxSnmpThe number of received SNMP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.8.1.3 |
tfrapPerfApplicationTotalTxSnmpThe number of transmitted SNMP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.8.1.4 |
tfrapPerfApplicationTotalRxSnmpTrapThe number of received SNMP TRAP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.8.1.5 |
tfrapPerfApplicationTotalTxSnmpTrapThe number of transmitted SNMP TRAP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.8.1.6 |
tfrapPerfApplicationTotalRxHttpThe number of received HTTP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.8.1.7 |
tfrapPerfApplicationTotalTxHttpThe number of transmitted HTTP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.8.1.8 |
tfrapPerfApplicationTotalRxTelnetThe number of received Telnet bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.8.1.9 |
tfrapPerfApplicationTotalTxTelnetThe number of transmitted Telnet bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.8.1.10 |
tfrapPerfApplicationTotalRxSmtpThe number of received SMTP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.8.1.11 |
tfrapPerfApplicationTotalTxSmtpThe number of transmitted SMTP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.8.1.12 |
tfrapPerfApplicationTotalRxFtpThe number of received FTP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.8.1.13 |
tfrapPerfApplicationTotalTxFtpThe number of transmitted FTP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.8.1.14 |
tfrapPerfApplicationTotalRxTftpThe number of received TFTP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.8.1.15 |
tfrapPerfApplicationTotalTxTftpThe number of transmitted TFTP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.8.1.16 |
tfrapPerfApplicationTotalRxCustom1The number of received bytes of
User Defined Protocol #1 that have
been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.8.1.17 |
tfrapPerfApplicationTotalTxCustom1The number of transmitted bytes of
User Defined Protocol #1 that have
been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.8.1.18 |
tfrapPerfApplicationTotalRxCustom2The number of received bytes of
User Defined Protocol #2 that have
been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.8.1.19 |
tfrapPerfApplicationTotalTxCustom2The number of transmitted bytes of
User Defined Protocol #2 that have
been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.8.1.20 |
tfrapPerfApplicationTotalRxCustom3The number of received bytes of
User Defined Protocol #3 that have
been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.8.1.21 |
tfrapPerfApplicationTotalTxCustom3The number of transmitted bytes of
User Defined Protocol #3 that have
been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.8.1.22 |
tfrapPerfApplicationTotalRxCustom4The number of received bytes of
User Defined Protocol #4 that have
been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.8.1.23 |
tfrapPerfApplicationTotalTxCustom4The number of transmitted bytes of
User Defined Protocol #4 that have
been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.8.1.24 |
tfrapPerfRoutingPerDlciTableThe Short Term Statistics on the Routing
protocol for each DLCI. SEQUENCE OF TfrapPerfRoutingPerDlciEntry .1.3.6.1.4.1.485.5.5.4.9 |
tfrapPerfRoutingPerDlciEntryThe Routing Short Term Statistics for a particular DLCI. TfrapPerfRoutingPerDlciEntry .1.3.6.1.4.1.485.5.5.4.9.1 |
tfrapPerfRoutingPerDlciIntervalThe 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.5.5.4.9.1.1 |
tfrapPerfRoutingPerDlciValueThe DLCI value with which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.5.5.4.9.1.2 |
tfrapPerfRoutingPerDlciRxOspfThe number of received OSPF bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.9.1.3 |
tfrapPerfRoutingPerDlciTxOspfThe number of transmitted OSPF bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.9.1.4 |
tfrapPerfRoutingPerDlciRxRipThe number of received RIP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.9.1.5 |
tfrapPerfRoutingPerDlciTxRipThe number of transmitted RIP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.9.1.6 |
tfrapPerfRoutingPerDlciRxNetbiosThe number of received Netbios bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.9.1.7 |
tfrapPerfRoutingPerDlciTxNetbiosThe number of transmitted Netbios bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.9.1.8 |
tfrapPerfRoutingTotalTableThe Short Term Statistics on the Routing
protocol across all DLCIs. SEQUENCE OF TfrapPerfRoutingTotalEntry .1.3.6.1.4.1.485.5.5.4.10 |
tfrapPerfRoutingTotalEntryThe Routing Short Term Statistics for a particular DLCI. TfrapPerfRoutingTotalEntry .1.3.6.1.4.1.485.5.5.4.10.1 |
tfrapPerfRoutingTotalIntervalThe 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.5.5.4.10.1.1 |
tfrapPerfRoutingTotalRxOspfThe number of received OSPF bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.10.1.3 |
tfrapPerfRoutingTotalTxOspfThe number of transmitted OSPF bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.10.1.4 |
tfrapPerfRoutingTotalRxRipThe number of received RIP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.10.1.5 |
tfrapPerfRoutingTotalTxRipThe number of transmitted RIP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.10.1.6 |
tfrapPerfRoutingTotalRxNetbiosThe number of received Netbios bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.10.1.7 |
tfrapPerfRoutingTotalTxNetbiosThe number of transmitted Netbios bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.10.1.8 |
tfrapPerfIpxPerDlciTableShort Term Statistics on the IPX
protocol for each DLCI. SEQUENCE OF TfrapPerfIpxPerDlciEntry .1.3.6.1.4.1.485.5.5.4.11 |
tfrapPerfIpxPerDlciEntryThe IPX Short Term Statistics for a particular DLCI. TfrapPerfIpxPerDlciEntry .1.3.6.1.4.1.485.5.5.4.11.1 |
tfrapPerfIpxPerDlciIntervalThe 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.5.5.4.11.1.1 |
tfrapPerfIpxPerDlciValueThe DLCI value in which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.5.5.4.11.1.2 |
tfrapPerfIpxPerDlciRxTotalThe total number of IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.11.1.3 |
tfrapPerfIpxPerDlciTxTotalThe total number of IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.11.1.4 |
tfrapPerfIpxPerDlciRxSpxThe number of SPX over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.11.1.5 |
tfrapPerfIpxPerDlciTxSpxThe number of SPX over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.11.1.6 |
tfrapPerfIpxPerDlciRxNcpThe number of NCP over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.11.1.7 |
tfrapPerfIpxPerDlciTxNcpThe number of NCP over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.11.1.8 |
tfrapPerfIpxPerDlciRxSapThe number of SAP over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.11.1.9 |
tfrapPerfIpxPerDlciTxSapThe number of SAP over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.11.1.10 |
tfrapPerfIpxPerDlciRxRipThe number of RIP over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.11.1.11 |
tfrapPerfIpxPerDlciTxRipThe number of RIP over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.11.1.12 |
tfrapPerfIpxPerDlciRxNetbiosThe number of NETBIOS over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.11.1.13 |
tfrapPerfIpxPerDlciTxNetbiosThe number of NETBIOS over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.11.1.14 |
tfrapPerfIpxPerDlciRxOtherThe 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.5.5.4.11.1.15 |
tfrapPerfIpxPerDlciTxOtherThe 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.5.5.4.11.1.16 |
tfrapPerfIpxTotalTableShort Term Statistics on the IPX
protocol across all DLCIs. SEQUENCE OF TfrapPerfIpxTotalEntry .1.3.6.1.4.1.485.5.5.4.12 |
tfrapPerfIpxTotalEntryThe IPX Short Term Statistics for a particular DLCI. TfrapPerfIpxTotalEntry .1.3.6.1.4.1.485.5.5.4.12.1 |
tfrapPerfIpxTotalIntervalThe 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.5.5.4.12.1.1 |
tfrapPerfIpxTotalRxTotalThe total number of IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.12.1.3 |
tfrapPerfIpxTotalTxTotalThe total number of IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.12.1.4 |
tfrapPerfIpxTotalRxSpxThe number of SPX over IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.12.1.5 |
tfrapPerfIpxTotalTxSpxThe number of SPX over IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.12.1.6 |
tfrapPerfIpxTotalRxNcpThe number of NCP over IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.12.1.7 |
tfrapPerfIpxTotalTxNcpThe number of NCP over IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.12.1.8 |
tfrapPerfIpxTotalRxSapThe number of SAP over IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.12.1.9 |
tfrapPerfIpxTotalTxSapThe number of SAP over IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.12.1.10 |
tfrapPerfIpxTotalRxRipThe number of RIP over IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.12.1.11 |
tfrapPerfIpxTotalTxRipThe number of RIP over IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.12.1.12 |
tfrapPerfIpxTotalRxNetbiosThe number of NETBIOS over IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.12.1.13 |
tfrapPerfIpxTotalTxNetbiosThe number of NETBIOS over IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.12.1.14 |
tfrapPerfIpxTotalRxOtherThe number of received bytes across all DLCIs
from protocols over IPX that are not counted
elsewhere in this table.ro Counter .1.3.6.1.4.1.485.5.5.4.12.1.15 |
tfrapPerfIpxTotalTxOtherThe number of transmitted bytes across all DLCIs
from protocols over IPX that are not counted
elsewhere in this table.ro Counter .1.3.6.1.4.1.485.5.5.4.12.1.16 |
tfrapPerfSnaPerDlciTableShort Term Statistics on the SNA
protocol for each DLCI. SEQUENCE OF TfrapPerfSnaPerDlciEntry .1.3.6.1.4.1.485.5.5.4.13 |
tfrapPerfSnaPerDlciEntryThe SNA Short Term Statistics for a particular DLCI. TfrapPerfSnaPerDlciEntry .1.3.6.1.4.1.485.5.5.4.13.1 |
tfrapPerfSnaPerDlciIntervalThe 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.5.5.4.13.1.1 |
tfrapPerfSnaPerDlciValueThe DLCI value in which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.5.5.4.13.1.2 |
tfrapPerfSnaPerDlciRxTotalThe total number of SNA bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.13.1.3 |
tfrapPerfSnaPerDlciTxTotalThe total number of SNA bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.13.1.4 |
tfrapPerfSnaPerDlciRxSubareaThe number of SNA Subarea bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.13.1.5 |
tfrapPerfSnaPerDlciTxSubareaThe number of SNA Subarea bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.13.1.6 |
tfrapPerfSnaPerDlciRxPeriphThe number of SNA Periph bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.13.1.7 |
tfrapPerfSnaPerDlciTxPeriphThe number of SNA Periph bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.13.1.8 |
tfrapPerfSnaPerDlciRxAppnThe number of SNA Appn bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.13.1.9 |
tfrapPerfSnaPerDlciTxAppnThe number of SNA Appn bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.13.1.10 |
tfrapPerfSnaPerDlciRxNetbiosThe number of SNA Netbios bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.13.1.11 |
tfrapPerfSnaPerDlciTxNetbiosThe number of SNA Netbios bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.13.1.12 |
tfrapPerfSnaPerDlciRxOtherThe 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.5.5.4.13.1.13 |
tfrapPerfSnaPerDlciTxOtherThe 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.5.5.4.13.1.14 |
tfrapPerfSnaTotalTableShort Term Statistics on the SNA
protocol across all DLCIs. SEQUENCE OF TfrapPerfSnaTotalEntry .1.3.6.1.4.1.485.5.5.4.14 |
tfrapPerfSnaTotalEntryThe SNA Short Term Statistics for a particular DLCI. TfrapPerfSnaTotalEntry .1.3.6.1.4.1.485.5.5.4.14.1 |
tfrapPerfSnaTotalIntervalThe 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.5.5.4.14.1.1 |
tfrapPerfSnaTotalRxTotalThe total number of SNA bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.14.1.3 |
tfrapPerfSnaTotalTxTotalThe total number of SNA bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.14.1.4 |
tfrapPerfSnaTotalRxSubareaThe number of SNA Subarea bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.14.1.5 |
tfrapPerfSnaTotalTxSubareaThe number of SNA Subarea bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.14.1.6 |
tfrapPerfSnaTotalRxPeriphThe number of SNA Periph bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.14.1.7 |
tfrapPerfSnaTotalTxPeriphThe number of SNA Periph bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.14.1.8 |
tfrapPerfSnaTotalRxAppnThe number of SNA Appn bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.14.1.9 |
tfrapPerfSnaTotalTxAppnThe number of SNA Appn bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.14.1.10 |
tfrapPerfSnaTotalRxNetbiosThe number of SNA Netbios bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.14.1.11 |
tfrapPerfSnaTotalTxNetbiosThe number of SNA Netbios bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.14.1.12 |
tfrapPerfSnaTotalRxOtherThe number of received bytes across all DLCIs
from protocols over SNA that are not counted
elsewhere in this table.ro Counter .1.3.6.1.4.1.485.5.5.4.14.1.13 |
tfrapPerfSnaTotalTxOtherThe number of transmitted bytes across all DLCIs
from protocols over SNA that are not counted
elsewhere in this table.ro Counter .1.3.6.1.4.1.485.5.5.4.14.1.14 |
tfrapPerfArpPerDlciTableShort Term Statistics on the ARP
protocol for each DLCI. SEQUENCE OF TfrapPerfArpPerDlciEntry .1.3.6.1.4.1.485.5.5.4.15 |
tfrapPerfArpPerDlciEntryThe ARP Short Term Statistics for a particular DLCI. TfrapPerfArpPerDlciEntry .1.3.6.1.4.1.485.5.5.4.15.1 |
tfrapPerfArpPerDlciIntervalThe 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.5.5.4.15.1.1 |
tfrapPerfArpPerDlciValueThe DLCI value in which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.5.5.4.15.1.2 |
tfrapPerfArpPerDlciRxTotalThe total number of ARP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.15.1.3 |
tfrapPerfArpPerDlciTxTotalThe total number of ARP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.15.1.4 |
tfrapPerfArpPerDlciRxArpReqThe number of ARP request bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.15.1.5 |
tfrapPerfArpPerDlciTxArpReqThe number of ARP request bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.15.1.6 |
tfrapPerfArpPerDlciRxArpRepThe number of ARP reply bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.15.1.7 |
tfrapPerfArpPerDlciTxArpRepThe number of ARP reply bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.15.1.8 |
tfrapPerfArpPerDlciRxRarpReqThe number of RARP request bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.15.1.9 |
tfrapPerfArpPerDlciTxRarpReqThe number of RARP request bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.15.1.10 |
tfrapPerfArpPerDlciRxRarpRepThe number of RARP reply bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.15.1.11 |
tfrapPerfArpPerDlciTxRarpRepThe number of RARP reply bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.15.1.12 |
tfrapPerfArpPerDlciRxInarpReqThe number of INARP request bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.15.1.13 |
tfrapPerfArpPerDlciTxInarpReqThe number of INARP request bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.15.1.14 |
tfrapPerfArpPerDlciRxInarpRepThe number of INARP reply bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.15.1.15 |
tfrapPerfArpPerDlciTxInarpRepThe number of INARP reply bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.15.1.16 |
tfrapPerfArpPerDlciRxOtherThe 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.5.5.4.15.1.17 |
tfrapPerfArpPerDlciTxOtherThe 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.5.5.4.15.1.18 |
tfrapPerfArpTotalTableShort Term Statistics on the ARP
protocol across all DLCIs. SEQUENCE OF TfrapPerfArpTotalEntry .1.3.6.1.4.1.485.5.5.4.16 |
tfrapPerfArpTotalEntryThe ARP Short Term Statistics for a particular DLCI. TfrapPerfArpTotalEntry .1.3.6.1.4.1.485.5.5.4.16.1 |
tfrapPerfArpTotalIntervalThe 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.5.5.4.16.1.1 |
tfrapPerfArpTotalRxTotalThe total number of ARP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.16.1.3 |
tfrapPerfArpTotalTxTotalThe total number of ARP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.16.1.4 |
tfrapPerfArpTotalRxArpReqThe number of ARP request bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.16.1.5 |
tfrapPerfArpTotalTxArpReqThe number of ARP request bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.16.1.6 |
tfrapPerfArpTotalRxArpRepThe number of ARP reply bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.16.1.7 |
tfrapPerfArpTotalTxArpRepThe number of ARP reply bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.16.1.8 |
tfrapPerfArpTotalRxRarpReqThe number of RARP request bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.16.1.9 |
tfrapPerfArpTotalTxRarpReqThe number of RARP request bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.16.1.10 |
tfrapPerfArpTotalRxRarpRepThe number of RARP reply bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.16.1.11 |
tfrapPerfArpTotalTxRarpRepThe number of RARP reply bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.16.1.12 |
tfrapPerfArpTotalRxInarpReqThe number of INARP request bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.16.1.13 |
tfrapPerfArpTotalTxInarpReqThe number of INARP request bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.16.1.14 |
tfrapPerfArpTotalRxInarpRepThe number of INARP reply bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.16.1.15 |
tfrapPerfArpTotalTxInarpRepThe number of INARP reply bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.16.1.16 |
tfrapPerfArpTotalRxOtherThe number of received bytes across all DLCIs
from ARP message types that are not counted
elsewhere in this table.ro Counter .1.3.6.1.4.1.485.5.5.4.16.1.17 |
tfrapPerfArpTotalTxOtherThe number of transmitted bytes across all DLCIs
from ARP message types that are not counted
elsewhere in this table.ro Counter .1.3.6.1.4.1.485.5.5.4.16.1.18 |
tfrapPerfLmiPerDlciTableShort Term Statistics on LMI protocol for each DLCI. SEQUENCE OF TfrapPerfLmiPerDlciEntry .1.3.6.1.4.1.485.5.5.4.17 |
tfrapPerfLmiPerDlciEntryThe LMI Short Term Statistics for a particular DLCI. TfrapPerfLmiPerDlciEntry .1.3.6.1.4.1.485.5.5.4.17.1 |
tfrapPerfLmiPerDlciIntervalThe 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.5.5.4.17.1.1 |
tfrapPerfLmiPerDlciValueThe DLCI value with which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.5.5.4.17.1.2 |
tfrapPerfLmiPerDlciRxTotalByteCntThe total number of received LMI bytes
counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.17.1.3 |
tfrapPerfLmiPerDlciTxTotalByteCntThe total number of transmitted LMI bytes
counted on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.17.1.4 |
tfrapPerfLmiPerDlciRxLivoEnqByteCntThe number of bytes received in Link Integrity
Verification Only (LIVO) enquiries on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.17.1.5 |
tfrapPerfLmiPerDlciTxLivoEnqByteCntThe number of bytes transmitted in Link Integrity
Verification Only (LIVO) enquiries on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.17.1.6 |
tfrapPerfLmiPerDlciRxLivoStatByteCntThe number of bytes received in Link Integrity
Verification Only (LIVO) statuses on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.17.1.7 |
tfrapPerfLmiPerDlciTxLivoStatByteCntThe number of bytes transmitted in Link Integrity
Verification Only (LIVO) statuses on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.17.1.8 |
tfrapPerfLmiPerDlciRxFullEnqByteCntThe number of bytes received in
Full Status enquiries on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.17.1.9 |
tfrapPerfLmiPerDlciTxFullEnqByteCntThe number of bytes transmitted in
Full Status enquiries on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.17.1.10 |
tfrapPerfLmiPerDlciRxFullStatByteCntThe number of bytes received in
Full Status messages on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.17.1.11 |
tfrapPerfLmiPerDlciTxFullStatByteCntThe number of bytes transmitted in
Full Status messages on this DLCI.ro Counter .1.3.6.1.4.1.485.5.5.4.17.1.12 |
tfrapPerfLmiPerDlciRxOtherByteCntThe 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.5.5.4.17.1.13 |
tfrapPerfLmiPerDlciTxOtherByteCntThe 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.5.5.4.17.1.14 |
tfrapPerfLmiTotalTableShort Term Statistics on LMI protocol across all DLCIs. SEQUENCE OF TfrapPerfLmiTotalEntry .1.3.6.1.4.1.485.5.5.4.18 |
tfrapPerfLmiTotalEntryThe LMI Short Term Statistics across all DLCIs. TfrapPerfLmiTotalEntry .1.3.6.1.4.1.485.5.5.4.18.1 |
tfrapPerfLmiTotalIntervalThe 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.5.5.4.18.1.1 |
tfrapPerfLmiTotalDlciValueOBSOLETE.ro INTEGER .1.3.6.1.4.1.485.5.5.4.18.1.2 |
tfrapPerfLmiTotalRxTotalByteCntThe total number of received LMI bytes
counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.18.1.3 |
tfrapPerfLmiTotalTxTotalByteCntThe total number of transmitted LMI bytes
counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.18.1.4 |
tfrapPerfLmiTotalRxLivoEnqByteCntThe number of bytes received in Link Integrity
Verification Only (LIVO) enquiries across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.18.1.5 |
tfrapPerfLmiTotalTxLivoEnqByteCntThe number of bytes transmitted in Link Integrity
Verification Only (LIVO) enquiries across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.18.1.6 |
tfrapPerfLmiTotalRxLivoStatByteCntThe number of bytes received in Link Integrity
Verification Only (LIVO) statuses across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.18.1.7 |
tfrapPerfLmiTotalTxLivoStatByteCntThe number of bytes transmitted in Link Integrity
Verification Only (LIVO) statuses across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.18.1.8 |
tfrapPerfLmiTotalRxFullEnqByteCntThe number of bytes received in
Full Status enquiries across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.18.1.9 |
tfrapPerfLmiTotalTxFullEnqByteCntThe number of bytes transmitted in
Full Status enquiries across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.18.1.10 |
tfrapPerfLmiTotalRxFullStatByteCntThe number of bytes received in
Full Status messages across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.18.1.11 |
tfrapPerfLmiTotalTxFullStatByteCntThe number of bytes transmitted in
Full Status messages across all DLCIs.ro Counter .1.3.6.1.4.1.485.5.5.4.18.1.12 |
tfrapPerfLmiTotalRxOtherByteCntThe number of received bytes across all DLCIs
from LMI protocols that are not counted
elsewhere (other than Total) in this table.ro Counter .1.3.6.1.4.1.485.5.5.4.18.1.13 |
tfrapPerfLmiTotalTxOtherByteCntThe number of transmitted bytes across all DLCIs
from LMI protocols that are not counted
elsewhere (other than Total) in this table.ro Counter .1.3.6.1.4.1.485.5.5.4.18.1.14 |
tfrapPerfNetworkLongTerm OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.5.5 |
tfrapPerfNetwLongTermTableLong 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 TfrapPerfNetwLongTermEntry .1.3.6.1.4.1.485.5.5.5.1 |
tfrapPerfNetwLongTermEntryThe Long Term Statistic for a particular DLCI,
protocol and interval. TfrapPerfNetwLongTermEntry .1.3.6.1.4.1.485.5.5.5.1.1 |
tfrapPerfNetwLongTermDlciThe DLCI monitored for the statistics. The Long
Term DLCI filter must first be configured
(CfgFrPerfLTDlciFilterEntry).ro INTEGER .1.3.6.1.4.1.485.5.5.5.1.1.1 |
tfrapPerfNetwLongTermProtocolThe type of protocol monitored for the statistics.ro Enumeration .1.3.6.1.4.1.485.5.5.5.1.1.2 |
tfrapPerfNetwLongTermIntervalThe 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.5.5.5.1.1.3 |
tfrapPerfNetwLongTermValueThe statistic collected for the given DLCI and protocol
and within the given time interval.ro Counter .1.3.6.1.4.1.485.5.5.5.1.1.4 |
tfrapPerfNetwLongTermAltTableThis 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 TfrapPerfNetwLongTermAltEntry .1.3.6.1.4.1.485.5.5.5.2 |
tfrapPerfNetwLongTermAltEntryThe Long Term Statistic for a particular
DLCI and protocol. TfrapPerfNetwLongTermAltEntry .1.3.6.1.4.1.485.5.5.5.2.1 |
tfrapPerfNetwLongTermAltDlciThe DLCI monitored for the statistics.ro INTEGER .1.3.6.1.4.1.485.5.5.5.2.1.1 |
tfrapPerfNetwLongTermAltProtocolThe protocol monitored for the statistics.ro Enumeration .1.3.6.1.4.1.485.5.5.5.2.1.2 |
tfrapPerfNetwLongTermAltArrayThe statistic collected for the given DLCI and protocol.ro OCTET STRING .1.3.6.1.4.1.485.5.5.5.2.1.3 |
tfrapPerfNetworkLongTermCommands OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.5.5.3 |
tfrapPerfNetworkLongTermCmdClearAllows 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.5.5.5.3.1 |
tfrapPerfCirPercentUtilization OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.5.6 |
tfrapPerfCirPercentUtilizationTableShort 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 TfrapPerfCirPercentUtilizationEntry .1.3.6.1.4.1.485.5.5.6.1 |
tfrapPerfCirPercentUtilizationEntryThe CIR Percentage Statistics for a particular DLCI.
These calculations are done at the completion of each
Short Term interval. TfrapPerfCirPercentUtilizationEntry .1.3.6.1.4.1.485.5.5.6.1.1 |
tfrapPerfCirPercentUtilizationIntervalThe 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.5.5.6.1.1.1 |
tfrapPerfCirPercentUtilizationDlciValueThe DLCI value with which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.5.5.6.1.1.2 |
tfrapPerfCirRxPercentUtilizationRange1The 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.5.5.6.1.1.21 |
tfrapPerfCirRxPercentUtilizationRange2The 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.5.5.6.1.1.22 |
tfrapPerfCirRxPercentUtilizationRange3The 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.5.5.6.1.1.23 |
tfrapPerfCirRxPercentUtilizationRange4The 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.5.5.6.1.1.24 |
tfrapPerfCirRxPercentUtilizationRange5The 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.5.5.6.1.1.25 |
tfrapPerfCirRxPercentUtilizationRange6The 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.5.5.6.1.1.26 |
tfrapPerfCirRxPercentUtilizationRange7The 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.5.5.6.1.1.27 |
tfrapPerfCirRxPercentUtilizationRange8The 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.5.5.6.1.1.28 |
tfrapPerfCirTxPercentUtilizationRange1The 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.5.5.6.1.1.41 |
tfrapPerfCirTxPercentUtilizationRange2The 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.5.5.6.1.1.42 |
tfrapPerfCirTxPercentUtilizationRange3The 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.5.5.6.1.1.43 |
tfrapPerfCirTxPercentUtilizationRange4The 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.5.5.6.1.1.44 |
tfrapPerfCirTxPercentUtilizationRange5The 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.5.5.6.1.1.45 |
tfrapPerfCirTxPercentUtilizationRange6The 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.5.5.6.1.1.46 |
tfrapPerfCirTxPercentUtilizationRange7The 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.5.5.6.1.1.47 |
tfrapPerfCirTxPercentUtilizationRange8The 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.5.5.6.1.1.48 |
tfrapPerfCurrentPerDlciUtilizationTableThe 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 TfrapPerfCurrentPerDlciUtilizationEntry .1.3.6.1.4.1.485.5.5.6.2 |
tfrapPerfCurrentPerDlciUtilizationEntryThe utilization statistics for a particular DLCI. TfrapPerfCurrentPerDlciUtilizationEntry .1.3.6.1.4.1.485.5.5.6.2.1 |
tfrapPerfCurrentPerDlciUtilizationDlciValueThe DLCI value with which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.5.5.6.2.1.1 |
tfrapPerfCurrentPerDlciRxUtilizationThe receive direction utilization as a
percentage of CIR.ro INTEGER .1.3.6.1.4.1.485.5.5.6.2.1.2 |
tfrapPerfCurrentPerDlciTxUtilizationThe transmit direction utilization as a
percentage of CIR.ro INTEGER .1.3.6.1.4.1.485.5.5.6.2.1.3 |
tfrapPerfCurrentPerDlciAggregateUtilizationThe aggregate utilization, the average
of the receive and transmit utilization
as a percentage of CIR.ro INTEGER .1.3.6.1.4.1.485.5.5.6.2.1.4 |
tfrapPerfCurrentUnitUtilization OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.5.6.3 |
tfrapPerfCurrentDteUtilizationThe DTE interface utilization as a
percentage of line rate.ro INTEGER .1.3.6.1.4.1.485.5.5.6.3.2 |
tfrapPerfCurrentWanUtilizationThe WAN interface utilization as a
percentage of line rate.ro INTEGER .1.3.6.1.4.1.485.5.5.6.3.3 |
tfrapPerfCurrentAggregateUtilizationThe 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.5.5.6.3.4 |
tfrapAlarmTypeThe type of alarms that are generated on the nodero Enumeration .1.3.6.1.4.1.485.5.6 |
tfrapDLCINumThe DLCI number for the DLCI active or inactive trapro INTEGER .1.3.6.1.4.1.485.5.7 |
tfrapInterfaceThe interface most recently reported in a TRAP.ro Enumeration .1.3.6.1.4.1.485.5.8 |
tfrapIpAddressThe IP address most recently reported in a TRAP.ro IpAddress .1.3.6.1.4.1.485.5.9 |
tfrapEventTrapLog OBJECT IDENTIFIER .1.3.6.1.4.1.485.5.10 |
tfrapEventTrapLogTableThis table contains the Event/Trap log. The entries are
indexed by sequence number. SEQUENCE OF TFRAPEventTrapLogEntry .1.3.6.1.4.1.485.5.10.1 |
tfrapEventTrapLogEntryThe event record for a particular event. TFRAPEventTrapLogEntry .1.3.6.1.4.1.485.5.10.1.1 |
tfrapEventTrapLogSeqNumThe sequence number associated with an event record.ro INTEGER .1.3.6.1.4.1.485.5.10.1.1.1 |
tfrapEventTrapLogGenericEventThe SNMP generic trap or event number.ro INTEGER .1.3.6.1.4.1.485.5.10.1.1.2 |
tfrapEventTrapLogSpecificEventThe SNMP specific trap or event sub-identifier number.ro INTEGER .1.3.6.1.4.1.485.5.10.1.1.3 |
tfrapEventTrapLogTimeStampThe SNMP trap timestamp.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.485.5.10.1.1.4 |
tfrapEventTrapLogVarBind1Variable Binding 1 for this SNMP Trap event.ro INTEGER .1.3.6.1.4.1.485.5.10.1.1.5 |
tfrapEventTrapLogVarBind2Variable Binding 2 for this SNMP Trap event.ro INTEGER .1.3.6.1.4.1.485.5.10.1.1.6 |
tfrapEventTrapLogVarBind3Variable Binding 3 for this SNMP Trap event.ro INTEGER .1.3.6.1.4.1.485.5.10.1.1.7 |
tfrapEventLogAltTableThis 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 TFRAPEventLogAltEntry .1.3.6.1.4.1.485.5.10.2 |
tfrapEventLogAltEntryThe Event/Trap Log for a particular sequence number. TFRAPEventLogAltEntry .1.3.6.1.4.1.485.5.10.2.1 |
tfrapEventLogAltSeqNumThe Sequence Number monitored for the Event Logro INTEGER .1.3.6.1.4.1.485.5.10.2.1.1 |
tfrapEventLogAltArrayThe Event / Trap log for the given sequence number.ro OCTET STRING .1.3.6.1.4.1.485.5.10.2.1.2 |
tfrapEventLogCurrentSeqNumThe current index into the Event Log Table.ro INTEGER .1.3.6.1.4.1.485.5.10.3 |
tfrapEventLogFreezeThis 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.5.10.4 |
tfrapEventLogClearThis clears the Event/Trap Log.rw Enumeration .1.3.6.1.4.1.485.5.10.5 |
tfrapPercentUtilizationThe percent utilization for a DLCI most recently
reported in a TRAP.ro INTEGER .1.3.6.1.4.1.485.5.11 |
tfrapUtilizationThresholdThe percent utilization threshold for a DLCI most
recently reported in a TRAP.ro INTEGER .1.3.6.1.4.1.485.5.12 |
tfrapCfgLockIpAddressThe IP address of the management station locking
the configuration most recently reported in a TRAP.ro IpAddress .1.3.6.1.4.1.485.5.13 |