DFRAP-MIB
AI MIB Summary
Standard SNMP MIB module defining data structures for DFRAP-MIB.
849
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
849 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 |
dfrap OBJECT IDENTIFIER .1.3.6.1.4.1.485.6 |
dfrapTrapA dfrapTrap trap signifies that the
sending node had its `dfrapAlarmType`
variable modified. TRAP-TYPE .1.3.6.1.4.1.485.6.0.0 |
dfrapBadConfigTrapUnit has received a configuration update request
through SNMP but the request was rejected due to
an incorrect or inappropriate parameter. TRAP-TYPE .1.3.6.1.4.1.485.6.0.1 |
dfrapLocalConfigTrapUnit configuration has been updated locally
(console port or front panel keypad) or remotely
(telnet) TRAP-TYPE .1.3.6.1.4.1.485.6.0.2 |
dfrapLocalUnitLoopbackEnabledTrapUnit is in 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 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.6.0.14 |
dfrapLocalUnitLoopbackDisabledTrapBi-directional unit loopback path is removed. TRAP-TYPE .1.3.6.1.4.1.485.6.0.15 |
dfrapLocalUnitLoopbackFailedTrapBi-directional 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.6.0.16 |
dfrapLocalDteLoopbackEnabledTrapUnit is in a bi-directional DTE loopback. All
data received at the DTE interface is looped
back regardless of format or content (line
loopback). All data received at the WAN 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. TRAP-TYPE .1.3.6.1.4.1.485.6.0.17 |
dfrapLocalDteLoopbackDisabledTrapBi-directional DTE loopback path is removed. TRAP-TYPE .1.3.6.1.4.1.485.6.0.18 |
dfrapLocalDteLoopbackFailedTrapBi-directional 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.6.0.19 |
dfrapLocalNetLoopbackEnabledTrapUnit 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.6.0.26 |
dfrapLocalNetLoopbackDisabledTrapLocal network loopback path is removed. TRAP-TYPE .1.3.6.1.4.1.485.6.0.27 |
dfrapLocalNetLoopbackFailedTrapLocal 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.6.0.28 |
dfrapV54LoopUpInitiatedTrapUnit 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 bi-directional
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.6.0.29 |
dfrapV54LoopDownCompletedTrapUnit 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 bi-directional 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.6.0.30 |
dfrapV54LoopbackEnabledTrapUnit has received a V54 loop up pattern from a
compatible piece of equipment. A bi-directional DTE
loopback is activated. All data received at the
DTE interface is looped back regardless of format
or content. All data received at the
WAN 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. TRAP-TYPE .1.3.6.1.4.1.485.6.0.31 |
dfrapV54LoopbackDisabledTrapUnit has received a V54 loop down pattern from
a compatible piece of equipment. The bi-directional
local DTE loopback is removed TRAP-TYPE .1.3.6.1.4.1.485.6.0.32 |
dfrapV54LoopbackFailedTrapUnit 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.6.0.33 |
dfrapBertInitiatedTrapUnit 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.6.0.44 |
dfrapBertCompletedTrapUnit has stopped sending a pseudorandom test
pattern out the WAN. TRAP-TYPE .1.3.6.1.4.1.485.6.0.45 |
dfrapBertFailedTrapUnit 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.6.0.46 |
dfrapDLCIActiveTrapUnit is reporting this DLCI as active and
provisioned. An active DLCI is one that is
explicitly declared ACTIVE in an LMI Full
Status Response (typically coming from a
frame relay switch). TRAP-TYPE .1.3.6.1.4.1.485.6.0.47 |
dfrapDLCIInactiveTrapUnit is reporting this DLCI as inactive. An
inactive DLCI is determined inactive one of two
ways: it is either explicitly 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.6.0.48 |
dfrapDLCITDThresholdTrapVNIP 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.6.0.49 |
dfrapLmiSourcingChangePassthruTrapUnit 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.6.0.50 |
dfrapLmiSourcingChangeUserDteTrapUnit 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.6.0.51 |
dfrapLmiSourcingChangeNetDteTrapUnit is acting as a source of LMI Status Responses
(Link Integrity Verification, Keep Alive). If this
state persists then the equipment 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.6.0.52 |
dfrapLmiSourcingChangeUserDdsTrapUnit 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.6.0.53 |
dfrapLmiSourcingChangeNetDdsTrapUnit 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.6.0.54 |
dfrapDteSignalRtsOnTrapUnit's DTE Request to Send (RTS) interface control
signal is now active (on). This signal is presented
by the external DTE device. TRAP-TYPE .1.3.6.1.4.1.485.6.0.55 |
dfrapDteSignalRtsOffTrapUnit's DTE Request to Send (RTS) interface control
signal is now inactive (off). This signal is presented
by the external DTE device. TRAP-TYPE .1.3.6.1.4.1.485.6.0.56 |
dfrapDteSignalDtrOnTrapUnit's DTE Data Terminal Ready (DTR) interface control
signal is now active (on). This signal is presented by the
external DTE device. TRAP-TYPE .1.3.6.1.4.1.485.6.0.57 |
dfrapDteSignalDtrOffTrapUnit's DTE Data Terminal Ready (DTR) interface control
signal is now inactive (off). This signal is presented by
the external DTE device. TRAP-TYPE .1.3.6.1.4.1.485.6.0.58 |
dfrapNonIncrLmiSeqNumDteTrapUnit 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.6.0.59 |
dfrapNonIncrLmiSeqNumDdsTrapUnit 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.6.0.60 |
dfrapLmiSeqNumMismatchDteTrapUnit has detected 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.6.0.61 |
dfrapLmiSeqNumMismatchDdsTrapUnit has detected an LMI sequence number mismatch from
the WAN. A Status Enquiry or Status Response message has
been seen at the WAN interface. The Link Integrity 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.6.0.62 |
dfrapLineFailureTrapThe unit is reporting error conditions that inditate that the
WAN connection is not fully functional. TRAP-TYPE .1.3.6.1.4.1.485.6.0.63 |
dfrapLineInServiceTrapThe unit is reporting that its WAN link has transitioned from a
failure state to one which is functioning normally. TRAP-TYPE .1.3.6.1.4.1.485.6.0.64 |
dfrapBPVThresholdExceededTrapThe unit may be configured to issue this alarm in response to line code
violations being received from the service provider. If more than 5
violations are detected within a one-second interval, this trap is
generated. Network control codes which include bipolar violations
are not considered errors and will not contribute to this trap. If
this condition persists then contact your WAN service provider. TRAP-TYPE .1.3.6.1.4.1.485.6.0.69 |
dfrapBPVThresholdAcceptableTrapThis trap is to announce that the bipolar violation threshold of at least
5 per second is no longer being exceeded. TRAP-TYPE .1.3.6.1.4.1.485.6.0.70 |
dfrapSimplexCurrentLoopbackEnabledTrapThe unit has received a DDS-standard simplex current reversal from the
WAN. In response, a Network Line Loopback path will be initiated for
the duration of the current reversal. TRAP-TYPE .1.3.6.1.4.1.485.6.0.71 |
dfrapSimplexCurrentLoopbackDisabledTrapThe unit has ceased receiving a simplex current reversal from the WAN. In
response, the Network Line Loopback path will be removed. TRAP-TYPE .1.3.6.1.4.1.485.6.0.72 |
dfrapNonLatchingLoopbackEnabledTrapThe unit has received a DDS-standard in-band loopback command. In response,
a Network Line Loopback path will be initiated and maintained as long as the
appropriate command is recognized. TRAP-TYPE .1.3.6.1.4.1.485.6.0.73 |
dfrapNonLatchingLoopbackDisabledTrapThe unit has ceased receiving a DDS-standard in-band loopback command.
In response, a Network Line Loopback path will be removed. TRAP-TYPE .1.3.6.1.4.1.485.6.0.74 |
dfrapTrapMutingActiveTrap generation is muted. This trap will be issued at the configured
trap muting frequency. No other traps will be issued. TRAP-TYPE .1.3.6.1.4.1.485.6.0.75 |
dfrapTrapMutingInactiveTrap generation is re-enabled (muting disabled). TRAP-TYPE .1.3.6.1.4.1.485.6.0.76 |
dfrapVloopUpA 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.6.0.90 |
dfrapVloopDownA 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.6.0.91 |
dfrapVloopUpViaRemoteA 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.6.0.92 |
dfrapVloopDownViaRemoteA 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.6.0.93 |
dfrapVloopRequestFailedThe request for a PVC loopback (VLOOP) has been rejected
or did not complete. TRAP-TYPE .1.3.6.1.4.1.485.6.0.94 |
dfrapVbertStartedA 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.6.0.95 |
dfrapVbertStoppedA 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.6.0.96 |
dfrapVbertRequestFailedThe request for a PVC BERT (VBERT) on this DLCI
on this interface has been rejected. TRAP-TYPE .1.3.6.1.4.1.485.6.0.97 |
dfrapPvcRxUtilizationExceededTrapPercent 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.6.0.138 |
dfrapPvcTxUtilizationExceededTrapPercent 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.6.0.139 |
dfrapPvcRxUtilizationClearedTrapPercent 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.6.0.140 |
dfrapPvcTxUtilizationClearedTrapPercent 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.6.0.141 |
dfrapConfigInstallSuccessThe configuration install process has successfully
completed. TRAP-TYPE .1.3.6.1.4.1.485.6.0.142 |
dfrapTftpRequestedTrapUnit 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.6.0.257 |
dfrapTftpTransferringTrapUnit 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.6.0.258 |
dfrapTftpProgrammingTrapUnit 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.6.0.259 |
dfrapTftpAbortedTrapUnit'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.6.0.260 |
dfrapTftpSuccessTrapUnit'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.6.0.261 |
dfrapTftpHostUnreachableTrapUnit 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 configuration TRAP-TYPE .1.3.6.1.4.1.485.6.0.262 |
dfrapTftpNoFileTrapUnit 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.6.0.263 |
dfrapTftpInvalidFileTrapUnit 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.6.0.264 |
dfrapTftpCorruptFileTrapUnit 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.6.0.265 |
dfrapSystem OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.1 |
dfrapSysTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.1.1 |
dfrapSysTypeA textual description of the system model identifier.
for example: SYNC-DFRAPro DisplayString .1.3.6.1.4.1.485.6.1.1.1 |
dfrapSysSoftRevDisplays the Software Revision installed in this node.ro DisplayString .1.3.6.1.4.1.485.6.1.1.2 |
dfrapSysHardRevDisplays the Hardware Revision of the node.ro DisplayString .1.3.6.1.4.1.485.6.1.1.3 |
dfrapSysNumT1InstalledThe number of T1 ports that are installed.ro INTEGER .1.3.6.1.4.1.485.6.1.1.4 |
dfrapSysNumDteInstalledThe number of DTE ports that are
installed.ro INTEGER .1.3.6.1.4.1.485.6.1.1.5 |
dfrapSysNumMaintInstalledThe number of Async Maintenance/Console ports that are
installed.ro INTEGER .1.3.6.1.4.1.485.6.1.1.6 |
dfrapSysNameThe 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.6.1.1.7 |
dfrapSysSerialNoThe serial number of the board.ro DisplayString .1.3.6.1.4.1.485.6.1.1.8 |
dfrapSysResetNodeCommand to reset the node. NODE WILL BE OFF-LINE AND
USER DATA WILL BE INTERRUPTED FOR APPROXIMATELY 15
SECONDS. Full network recovery may take longer.rw Enumeration .1.3.6.1.4.1.485.6.1.1.9 |
dfrapSysAmtMemoryInstalledThe amount of memory (RAM) installed (in megabytes).ro INTEGER .1.3.6.1.4.1.485.6.1.1.10 |
dfrapSysNumDdsInstalledThe number of DDS ports that are installed.ro INTEGER .1.3.6.1.4.1.485.6.1.1.11 |
dfrapSysLocationThe 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.6.1.1.12 |
dfrapSysContactThe 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.6.1.1.13 |
dfrapSysPromptConfigurable Command Line Interface (CLI) prompt. CLI
is the User Interface protocol used for directly
attached VT100 terminal access as well as Remote
access via Telnet.rw DisplayString .1.3.6.1.4.1.485.6.1.1.15 |
dfrapSysBootRevDisplays the bootblock Software Revision
installed in this node.ro DisplayString .1.3.6.1.4.1.485.6.1.1.16 |
dfrapSysFeatureTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.1.2 |
dfrapSysSLIPSupportedShows 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.6.1.2.1 |
dfrapSysPPPSupportedShows 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.6.1.2.2 |
dfrapSysRDOSupportedShows whether the unit has Remote Dial Out capability.ro DisplayString .1.3.6.1.4.1.485.6.1.2.3 |
dfrapSysETHSupportedShows whether the unit has direct Ethernet capability.ro DisplayString .1.3.6.1.4.1.485.6.1.2.4 |
dfrapSysTKRSupportedShows whether the unit has direct Token Ring capability.ro DisplayString .1.3.6.1.4.1.485.6.1.2.5 |
dfrapSysExtTimSupportedShows 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.6.1.2.6 |
dfrapSysBRISupportedShows whether the unit has BRI (ISDN Basic Rate) capability.ro DisplayString .1.3.6.1.4.1.485.6.1.2.7 |
dfrapSysSelDTESupportedShows 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.6.1.2.8 |
dfrapSysMLSupportedShows 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.6.1.2.9 |
dfrapSysNumDlcisSupportedShows 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.6.1.2.10 |
dfrapSysLTFNumDlcisShows how many DLCIs can be specified
in the Long Term Statistics Filter.ro INTEGER .1.3.6.1.4.1.485.6.1.2.11 |
dfrapSysLTFNumProtocolsShows how many protocols can be specified
in the Long Term Statistics Filter.ro INTEGER .1.3.6.1.4.1.485.6.1.2.12 |
dfrapSysNumUserProtocolsShows 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.6.1.2.13 |
dfrapSysNumSnmpMgrsShows how many SNMP managers can be programmed in the
table dfrapCfgSnmpMngrTable. These managers are sent TRAPs.ro INTEGER .1.3.6.1.4.1.485.6.1.2.14 |
dfrapSysNumDlciNamesShows how many DLCI names can be defined by the user
in the table dfrapCfgFrPerfDlciNamesTable.ro INTEGER .1.3.6.1.4.1.485.6.1.2.15 |
dfrapConfiguration OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.2 |
dfrapCfgMgmtTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.2.1 |
dfrapCfgIpTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.2.1.1 |
dfrapCfgIpMyIPThe IP address for this node.rw IpAddress .1.3.6.1.4.1.485.6.2.1.1.1 |
dfrapCfgIpPeerIPThis 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.rw IpAddress .1.3.6.1.4.1.485.6.2.1.1.2 |
dfrapCfgIpMaskThe 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.6.2.1.1.3 |
dfrapCfgIpMaxMTUThe 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.6.2.1.1.4 |
dfrapCfgIpChannelThis 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.6.2.1.1.5 |
dfrapCfgIpTelnetEnableEnables/Disables the telnet feature.
(1) enable-telnet
(2) disable-telnetrw Enumeration .1.3.6.1.4.1.485.6.2.1.1.6 |
dfrapCfgIpTelnetAutoLogOutIf 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.6.2.1.1.7 |
dfrapCfgTftpTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.2.1.2 |
dfrapCfgTftpInitiateSetting 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.6.2.1.2.1 |
dfrapCfgTftpIpAddressThe 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.6.2.1.2.2 |
dfrapCfgTftpFilenameThe 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.6.2.1.2.3 |
dfrapCfgTftpInterfaceThe 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.6.2.1.2.4 |
dfrapCfgTftpDlciThe 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.6.2.1.2.5 |
dfrapCfgTftpStatusThe 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.6.2.1.2.6 |
dfrapCfgTftpNumBytesThe number of Bytes from the ROM image that have been
TFTP'd to the unitro Counter .1.3.6.1.4.1.485.6.2.1.2.7 |
dfrapCfgSnmpTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.2.1.3 |
dfrapCfgSnmpFrTrapControls whether or not the Frame Relay DLCI
status change traps are issued. These traps are
dfrapDLCIActiveTrap and dfrapDLCIInactiveTrap.
When dfrapCfgSnmpFrTrap is enabled (1), a trap
will be sent each time an individual DLCI changes
status between active and inactive. When
dfrapCfgSnmpFrTrap is disabled (2), the traps
are not sent.rw Enumeration .1.3.6.1.4.1.485.6.2.1.3.1 |
dfrapCfgSnmpMgrTableThe 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 DfrapCfgSnmpMgrEntry .1.3.6.1.4.1.485.6.2.1.3.2 |
dfrapCfgSnmpMgrEntryThe SNMP trap manager profiles to which the unit
sends TRAPs. DfrapCfgSnmpMgrEntry .1.3.6.1.4.1.485.6.2.1.3.2.1 |
dfrapCfgSnmpMgrIndexThe index to the list of SNMP managers receiving TRAPs.ro INTEGER .1.3.6.1.4.1.485.6.2.1.3.2.1.1 |
dfrapCfgSnmpMgrIPThe 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.6.2.1.3.2.1.2 |
dfrapCfgSnmpMgrInterfaceThe 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.
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 dds-interface(2);
slip-interface(3) would be rejected.rw Enumeration .1.3.6.1.4.1.485.6.2.1.3.2.1.3 |
dfrapCfgSnmpMgrDlciThe 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.6.2.1.3.2.1.4 |
dfrapCfgSnmpTrapMutingControls 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.6.2.1.3.3 |
dfrapCfgSnmpUtilTrapEnableEnables 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.6.2.1.3.6 |
dfrapCfgSnmpMgrClearNDeletes the number of entries in the dfrapCfgSnmpMgrTable
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.6.2.1.3.7 |
dfrapCfgCommTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.2.1.4 |
dfrapCfgCommModeThe 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.6.2.1.4.1 |
dfrapCfgCommBaudAsynchronous baud rate 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.
(2) baud-2400
(4) baud-9600
(5) baud-19200
(6) baud-38400rw Enumeration .1.3.6.1.4.1.485.6.2.1.4.2 |
dfrapCfgCommDataBitsAsynchronous 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.6.2.1.4.3 |
dfrapCfgCommStopBitsAsynchronous 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.6.2.1.4.4 |
dfrapCfgCommParityAsynchronous 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.6.2.1.4.5 |
dfrapCfgCommFlowCtrlFlow Control for the Maintenance/Comm port (Console).
(1) no flow control supported.rw Enumeration .1.3.6.1.4.1.485.6.2.1.4.6 |
dfrapCfgFrDLCITable OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.2.1.5 |
dfrapCfgFrDLCIModeIn-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.6.2.1.5.1 |
dfrapCfgFrDLCIValueIf 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.6.2.1.5.2 |
dfrapCfgFrDLCIEncapThis 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.6.2.1.5.3 |
dfrapCfgFrDLCIMgmtDEProvides 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.6.2.1.5.4 |
dfrapCfgAppTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.2.2 |
dfrapCfgAppClockSourceTiming 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.6.2.2.1 |
dfrapCfgAppCircuitIdAlphanumeric 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.6.2.2.2 |
dfrapCfgAppTypeThis 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.6.2.2.3 |
dfrapCfgAppFormatRefer 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.6.2.2.4 |
dfrapCfgAppLpbkTimeoutThe 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.6.2.2.5 |
dfrapCfgAppPerfBuffLimitThis value controls the throttling mechanism
used to determine the optimum level of statistical
processing versus managability of the unit. The
lower the value (1 - 128), the unit becomes more
responsive to management commands during very heavy
utilization at the possible expense of statistical
accuracy. The larger the value (129 - 512), the more
accurate the DFRAP 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.6.2.2.10 |
dfrapCfgDdsTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.2.3 |
dfrapCfgDdsLoopRateProvisioned DDS WAN data rate. This unit conforms
to either 56K DDS service or 64K (72K with framing)
DDS service.
(1) 56Kbps DDS
(2) 64Kbs DDS (72K loop rate)rw Enumeration .1.3.6.1.4.1.485.6.2.3.1 |
dfrapCfgDdsBPVThresholdingThe unit may be configured to issue traps in response to
Bipolar Violations (BPVs) received from the WAN. If enabled
the unit will issue a trap when more than 5 BPVs are detected
in a one-second interval and a follow-up trap when the BPV
threshold is no longer exceeded. BPVs that are part of network
control codes do not contribute to this feature.
(1) BPV Trap Threshold is 10e-4
(2) Disable BPV Trapsrw Enumeration .1.3.6.1.4.1.485.6.2.3.2 |
dfrapCfgDteTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.2.4 |
dfrapCfgDteIntfTypeThe electrical interface for the DTE port
(3) V.35 interface
(4) RS-449 interfacero Enumeration .1.3.6.1.4.1.485.6.2.4.1 |
dfrapCfgDteClockModeThis 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.6.2.4.3 |
dfrapCfgDteTimingSerial 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.6.2.4.4 |
dfrapCfgDteRtsControls 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 fora network manager's assessment of interface
status.
(1) Internally Held Active
(2) Externally Presented from DTErw Enumeration .1.3.6.1.4.1.485.6.2.4.15 |
dfrapCfgDteDtrControls 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 fora network manager's assessment of
interface status.
(1) Internally Held Active
(2) Externally Presented from DTErw Enumeration .1.3.6.1.4.1.485.6.2.4.16 |
dfrapCfgDteDcdOutputSpecifies 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.
Frame Synchronization is only applicable with 64K DDS service,
otherwise this is equivalent to (6).
(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.6.2.4.18 |
dfrapCfgDteDsrOutputSpecifies 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 Synchronization is only applicable with 64K DDS service,
otherwise this is equivalent to (6).
(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.6.2.4.19 |
dfrapCfgDteCtsOutputSpecifies 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.
Frame Synchronization is only applicable with 64K DDS service,
otherwise this is equivalent to (6).
(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.6.2.4.20 |
dfrapCfgFrTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.2.5 |
dfrapCfgFrAddrLenShows the size that DLCI address field. 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.6.2.5.1 |
dfrapCfgFrCrcModeThis 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 transmit the entire frame but
will place an incorrect crc in it to preserve the error
indication.
(1) discard
(2) pasthrurw Enumeration .1.3.6.1.4.1.485.6.2.5.2 |
dfrapCfgFrLmiTypeThe 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) Annex-A: conforms to ITU (CCITT) Q.933 annex A
(2) Annex-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.6.2.5.3 |
dfrapCfgFrLmiInactivityTimeoutTimer 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.6.2.5.4 |
dfrapCfgFrLmiKeepaliveTimeoutTimer 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.6.2.5.5 |
dfrapCfgFrAddrResModeThe ip-based Address Resolution protocol supported in the
application. With ARP, requests are received and replies
are generated accordingly. With InARP, requests are received
and replies are generated; additionally, InARP requests are
issued by the unit at the frequency defined by the InARP timer.
Address Resolution will circumvent the need for static routes
and automatically log an associated dynamic entry into the
routing tables.
(1) inactive: no address resolution support
(2) ARP: only provide ARP responses. ARP is useful when the
router knows the unit's ip address but doesn't know the DLCI.
(3) InARP: provide both InARP responses and InARP requests. InARP
is useful when the router knows the DLCI but not the ip address.
(4) Both ARP and InARP.rw Enumeration .1.3.6.1.4.1.485.6.2.5.6 |
dfrapCfgFrAddrResInarpTimerIf the unit is configured to support the InARP
address resolution protocol, this is the frequency
of INARP requests that the unit will generate.
(5-86400) - InARP Request Timer in secondsrw INTEGER .1.3.6.1.4.1.485.6.2.5.7 |
dfrapCfgFrLmiFullStatusTimer 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
declared 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.6.2.5.8 |
dfrapCfgFrAddrResDlcisAddress Resolution Dlcis determines which dlcis will
support address resolution. In Private management
modes (Local, Remote, Bidirectional), address
resolution runs on the single defined management DLCI only
(regardless of this setting). In Piggyback management
the user has options based upon two models: Single, where the
address resolution protocols run only upon the defined
managment DLCI and Multiple, where its supported on all active
DLCIs recognized by the unit.
(1) Single - address resolution on the defined default DLCI on
both ports
(2) Multiple - address resolution on all active DLCIs on
both ports
(3) DDSMulti - Single on DTE and Multiple on DDS
(4) DTEMulti - Single on DDS and Multiple on DTErw Enumeration .1.3.6.1.4.1.485.6.2.5.9 |
dfrapCfgVnipTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.2.6 |
dfrapCfgVnipModeThis 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.6.2.6.1 |
dfrapCfgVnipInitTimerVNIP 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.6.2.6.2 |
dfrapCfgVnipKeepAliveTimerThis 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.6.2.6.3 |
dfrapCfgVnipInactivityTimerThe 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.6.2.6.4 |
dfrapCfgVnipTransitDelayFrequencyTransit 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.6.2.6.5 |
dfrapCfgTransitDelayTableThe 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 DfrapCfgTransitDelayEntry .1.3.6.1.4.1.485.6.2.6.20 |
dfrapCfgTransitDelayEntryA 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 DfrapCfgTransitDelayEntry .1.3.6.1.4.1.485.6.2.6.20.1 |
dfrapCfgTransitDelayInterfaceThis 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.6.2.6.20.1.1 |
dfrapCfgTransitDelayDlciValueThis 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.6.2.6.20.1.2 |
dfrapCfgTransitDelayNumHopsVNIP 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.6.2.6.20.1.4 |
dfrapCfgTransitDelayRcvSummaryCancelControls 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.6.2.6.20.1.5 |
dfrapCfgTransitDelayThresholdSpecifies 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.6.2.6.20.1.6 |
dfrapCfgTDDeleteTableThe table allows the user to disable transit delay measurements
for a specific DLCI on a particular interface. SEQUENCE OF DfrapCfgTDDeleteEntry .1.3.6.1.4.1.485.6.2.6.21 |
dfrapCfgTDDeleteEntryDisables VNIP Transit Delay for a particular interface and DLCI. DfrapCfgTDDeleteEntry .1.3.6.1.4.1.485.6.2.6.21.1 |
dfrapCfgTDDeleteInterfaceTransit 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.6.2.6.21.1.1 |
dfrapCfgTDDeleteDlciValueTransit 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.6.2.6.21.1.2 |
dfrapCfgTransitDelayTableClearThe dfrapCfgTransitDelayTable is cleared.
(1) clear the tablerw Enumeration .1.3.6.1.4.1.485.6.2.6.22 |
dfrapCfgFrPerf OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.2.7 |
dfrapCfgFrPerfDlciNamesTableThis 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 DFRAPCfgFrPerfDlciNamesEntry .1.3.6.1.4.1.485.6.2.7.1 |
dfrapCfgFrPerfDlciNamesEntryA table entry indexed by DLCI, containing
a DLCI, a DLCI name, a CIR, and how the
CIR value was obtained. DFRAPCfgFrPerfDlciNamesEntry .1.3.6.1.4.1.485.6.2.7.1.1 |
dfrapCfgFrPerfDlciNamesDlciValueA 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.6.2.7.1.1.1 |
dfrapCfgFrPerfDlciNamesDlciNameA user-specifiable name for an individual DLCI.rw DisplayString .1.3.6.1.4.1.485.6.2.7.1.1.2 |
dfrapCfgFrPerfDlciNamesCirValueThe 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 teh CIR is the DTE Line Rate.rw INTEGER .1.3.6.1.4.1.485.6.2.7.1.1.3 |
dfrapCfgFrPerfDlciNamesCirTypeThe 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.6.2.7.1.1.4 |
dfrapCfgFrPerfDlciNamesUtilThresholdThe threshold for generating a utilization
threshold trap as a percentage of the CIR.
If the utilization percentage is above this
threshold for more than
dfrapCfgFrPerfDlciUtilThreshold number of
dfrapCfgFrPerfTimersSTInterval's a
dfrapPvc(Rx/Tx)UtilizationExceeded trap
will be issued. If the If the utilization
percentage falls below this threshold for
more than dfrapCfgFrPerfDlciUtilThreshold
number of dfrapCfgFrPerfTimersSTInterval's a
dfrapPvc(Rx/Tx)UtilizationExceeded trap
will be issued.rw INTEGER .1.3.6.1.4.1.485.6.2.7.1.1.5 |
dfrapCfgFrPerfDlciNamesEirValueThe 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.6.2.7.1.1.6 |
dfrapCfgFrPerfDlciNamesDeleteSetting 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.6.2.7.2 |
dfrapCfgFrPerfTimers OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.2.7.3 |
dfrapCfgFrPerfTimersSTIntervalShort 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.6.2.7.3.1 |
dfrapCfgFrPerfTimersLTIntervalLong 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.6.2.7.3.2 |
dfrapCfgFrPerfUserProtocolsTableThis 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 DFRAPCfgFrPerfUserProtocolsEntry .1.3.6.1.4.1.485.6.2.7.4 |
dfrapCfgFrPerfUserProtocolsEntryAn index and TCP/UDP port number pair. DFRAPCfgFrPerfUserProtocolsEntry .1.3.6.1.4.1.485.6.2.7.4.1 |
dfrapCfgFrPerfUserProtocolsIndexAn index. Beginning with index 1, the range is defined
in SysNumUserProtocolsro INTEGER .1.3.6.1.4.1.485.6.2.7.4.1.1 |
dfrapCfgFrPerfUserProtocolsPortNumTx 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.6.2.7.4.1.2 |
dfrapCfgFrPerfLTDlciFilterTableLong 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 DFRAPCfgFrPerfLTDlciFilterEntry .1.3.6.1.4.1.485.6.2.7.5 |
dfrapCfgFrPerfLTDlciFilterEntryAn index and DLCI number pair. DFRAPCfgFrPerfLTDlciFilterEntry .1.3.6.1.4.1.485.6.2.7.5.1 |
dfrapCfgFrPerfLTDlciFilterIndexAn index. Beginning with index 1, the maximum is
defined by the value of SysLTFNumDlcis.ro INTEGER .1.3.6.1.4.1.485.6.2.7.5.1.1 |
dfrapCfgFrPerfLTDlciFilterDlciNumSetting 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.6.2.7.5.1.2 |
dfrapCfgFrPerfLTProtocolFilterTableLong 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 DFRAPCfgFrPerfLTProtocolFilterEntry .1.3.6.1.4.1.485.6.2.7.6 |
dfrapCfgFrPerfLTProtocolFilterEntryAn index and protocol pair. DFRAPCfgFrPerfLTProtocolFilterEntry .1.3.6.1.4.1.485.6.2.7.6.1 |
dfrapCfgFrPerfLTProtocolFilterIndexAn index. Beginning with index 1, the maximum is
defined by the value of SysLTFNumProtocols.ro INTEGER .1.3.6.1.4.1.485.6.2.7.6.1.1 |
dfrapCfgFrPerfLTProtocolFilterProtocolLong 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.6.2.7.6.1.2 |
dfrapCfgFrPerfDlciDefaultUtilThresholdThe default threshold for generating a
utilization threshold trap as a percentage
of the CIR. This value is used for
dfrapCfgFrPerfDlciNamesUtilThreshold when
a DLCI is first discovered.rw INTEGER .1.3.6.1.4.1.485.6.2.7.7 |
dfrapCfgFrPerfDlciUtilDurationThe number of Short Term Intervals that a
DLCI's utilization as a percentage of CIR
must be above or below the value of
dfrapCfgFrPerfDlciUtilThreshold before a
dfrapPvc(Rx/Tx)UtilizationExceededTrap or
dfrapPvc(Rx/Tx)UtilizationClearedTrap is
issued.rw INTEGER .1.3.6.1.4.1.485.6.2.7.8 |
dfrapCfgFrPerfDlciNamesTableClearClears 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.6.2.7.9 |
dfrapCfgFrPerfUserProtocolsTableClearClears the dfrapCfgFrPerfUserProtocolsTable
(1) clear the tablerw Enumeration .1.3.6.1.4.1.485.6.2.7.10 |
dfrapCfgFrPerfLTDlciFilterTableClearClears the dfrapCfgFrPerfLTDlciFilterTable
(1) clear the tablerw Enumeration .1.3.6.1.4.1.485.6.2.7.11 |
dfrapCfgFrPerfLTProtocolFilterTableClearClears the dfrapCfgFrPerfLTProtocolFilterTable
(1) clear the tablerw Enumeration .1.3.6.1.4.1.485.6.2.7.12 |
dfrapCfgFrPerfUnprovDlcisDeleteDelete all unprovisioned and Not-In-LMI dlcis
(1) delete all unprovisionedrw Enumeration .1.3.6.1.4.1.485.6.2.7.13 |
dfrapCfgSecurityTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.2.8 |
dfrapCfgTelnetCliLcdPasswordThe password needed to start a
CLI (Command Line Interface),
Telnet or LCD session.rw DisplayString .1.3.6.1.4.1.485.6.2.8.1 |
dfrapCfgTftpPasswordThe password needed to initiate a TFTP download.rw DisplayString .1.3.6.1.4.1.485.6.2.8.2 |
dfrapCfgCliPasswordOBSOLETE: The Telnet, CLI and LCD passwords
are one and the same. Use the above
CfgTelnetCliLcdPassword to log into
the CLI (Command Line Interface).rw DisplayString .1.3.6.1.4.1.485.6.2.8.3 |
dfrapCfgLcdPasswordOBSOLETE: The Telnet, CLI and LCD passwords
are one and the same. Use the above
CfgTelnetCliLcdPassword to log into
the LCD Interface.rw DisplayString .1.3.6.1.4.1.485.6.2.8.4 |
dfrapCfgGetCommunityStringThe 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.6.2.8.5 |
dfrapCfgSetCommunityStringThe 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.6.2.8.6 |
dfrapCfgLockRequest 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.6.2.12 |
dfrapCfgLockIDReturns 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.6.2.13 |
dfrapCfgIDA 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.6.2.14 |
dfrapCfgStatusThe 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 dfrapCfgLock command.
(7) The user sent a dfrapCfgUnlock command before a
dfrapCfgUpdate command. This usually means that one
of the sets in the configuration failed.ro Enumeration .1.3.6.1.4.1.485.6.2.15 |
dfrapCfgUnlockThe 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.6.2.16 |
dfrapCfgUpdateThe 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.6.2.17 |
dfrapDiagnostics OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.3 |
dfrapDiagUnitTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.3.1 |
dfrapDiagUnitLocLoopControls 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 during this loopback.
In Frame Relay mode, only valid frames are looped
back (pseudorandom test patterns will be dropped).
(1) enable unit loopbackrw Enumeration .1.3.6.1.4.1.485.6.3.1.1 |
dfrapDiagUnitResetEnables the operator to remotely reset the unit.
Using this command will cause the unit to terminate
all its connections and drop data.
(1): reset unitrw Enumeration .1.3.6.1.4.1.485.6.3.1.2 |
dfrapDiagUnitTimeRemainingThe remaining time on the active loopback
before the loopback times out. The time is
in hundredths of seconds (TimeTicks).ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.485.6.3.1.3 |
dfrapDiagDdsTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.3.2 |
dfrapDiagDdsLclLpbkControls 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.
(1) enable DDS line loopback
(2) disable DDS line loopbackrw Enumeration .1.3.6.1.4.1.485.6.3.2.2 |
dfrapDiagDdsRmtLpbkEnables the operator to examine (ONLY) the
status of network loopbacks placed by external
equipment, such as your local CO. Any of these
conditions will result in a DDS line loopback.
(1) no remote loop up command
(2) simplex current reversal loopback command
(3) non-latching loopback command
(4) latching loopback comamndro Enumeration .1.3.6.1.4.1.485.6.3.2.3 |
dfrapDiagDdsTimeRemainingThe remaining time on the active loopback
before the loopback times out. The time is
in hundredths of seconds (TimeTicks).ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.485.6.3.2.4 |
dfrapDiagDteTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.3.3 |
dfrapDiagDteLclLpbkControls a bi-directional DTE loopback. All
data received at the DTE interface is looped
back regardless of format or content (line
loopback). All data received at the WAN 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.
(1) enable DTE loopback
(2) disable DTE loopbackrw Enumeration .1.3.6.1.4.1.485.6.3.3.3 |
dfrapDiagDteV54LpbkThis selection displays the status of the DTE Channel
V.54 Loopback for the channel. This loopback is
initiated by the remote node, causing this unit to enter
a Local DTE loopback condition.
(1) V54 loopback pattern received from WAN
(2) V54 loopback pattern not received from WANro Enumeration .1.3.6.1.4.1.485.6.3.3.4 |
dfrapDiagDteRmtV54LpbkThis selection controls the DTE Channel V.54 Remote Loopback.
Transmit-code-enable (3) will cause the node to transmit
a V.54 code to the remote node which will then enter a Local
DTE Loopback state. transmit-code-disable (4) will transmit
the loopdown code and cause the remote unit to remove the
Local DTE Loopback path.
(1) send remote V54 loop up command
(2) send remote V54 loop down commandrw Enumeration .1.3.6.1.4.1.485.6.3.3.5 |
dfrapDiagDteTimeRemainingThe remaining time on the active loopback
before the loopback times out. The time is
in hundredths of seconds (TimeTicks).ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.485.6.3.3.13 |
dfrapDiagBertTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.3.5 |
dfrapDiagBertStateThe 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. This test may be ineffective in
certain frame relay applications 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
(2) Stop a BERT test
(4) Inject a single bit error into the outgoing pattern
(5) Clear current BERT resultsrw Enumeration .1.3.6.1.4.1.485.6.3.5.1 |
dfrapDiagBertStatusDisplays 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.6.3.5.2 |
dfrapDiagBertErrorsDisplays the number of errors detected in Bert Test.ro Counter .1.3.6.1.4.1.485.6.3.5.3 |
dfrapDiagBertErrSecDisplays the number of seconds containing 1 or more errors
in BERT Test.ro Counter .1.3.6.1.4.1.485.6.3.5.4 |
dfrapDiagBertTimeElapsElapsed time since BERT test was started or last cleared.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.485.6.3.5.5 |
dfrapDiagBertResyncsDisplays 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.6.3.5.6 |
dfrapDiagBertPatternThe 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.6.3.5.7 |
dfrapDiagVnipTableTable of Diagnostics performed with the VNIP protocol SEQUENCE OF DFRAPDiagVnipEntry .1.3.6.1.4.1.485.6.3.6 |
dfrapDiagVnipEntryVNIP 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. DFRAPDiagVnipEntry .1.3.6.1.4.1.485.6.3.6.1 |
dfrapDiagVnipInterfaceThe 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.6.3.6.1.1 |
dfrapDiagVnipIndexThe 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.6.3.6.1.2 |
dfrapDiagVnipDlciThis is the DLCI value for the given interface/index
combination. This comes from the VniptTopologyTable.ro INTEGER .1.3.6.1.4.1.485.6.3.6.1.3 |
dfrapDiagVnipIpAddrThis is the ip address for the given interface/index
combination. This comes from the VniptTopologyTable.ro IpAddress .1.3.6.1.4.1.485.6.3.6.1.4 |
dfrapDiagVLOOPControls 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.6.3.6.1.5 |
dfrapDiagVBERTControls 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.6.3.6.1.6 |
dfrapDiagVBERTRateSpecifies the throughput bit rate applied by VBERT or
VLOOP to the DLCI-under-test. Any rate up to the
DTE line rate may be selected. Note that selecting
rates that approach line rate will impact neighboring DLCIs.
(8000-64000): VBERT/VLOOP data rate (in bits per second).rw INTEGER .1.3.6.1.4.1.485.6.3.6.1.7 |
dfrapDiagVBERTSizeSpecifies the size of framed data that will be used
during the VBERT test, measures 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.6.3.6.1.8 |
dfrapDiagVBERTPktPercentSpecifies 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.
(1) 0% of the test frames are marked discard eligible
(2) 25% of the test frames are marked discard eligible
(3) 50% of the test frames are marked discard eligible
(4) 75% of the test frames are marked discard eligible
(5) 100% of the test frames are marked discard eligiblerw Enumeration .1.3.6.1.4.1.485.6.3.6.1.9 |
dfrapDiagVBERTTestPeriodSpecifies 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.6.3.6.1.10 |
dfrapStatus OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.4 |
dfrapVnipTopologyTableVNIP 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 DFRAPVnipTopologyEntry .1.3.6.1.4.1.485.6.4.2 |
dfrapVnipTopologyEntryThe 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. DFRAPVnipTopologyEntry .1.3.6.1.4.1.485.6.4.2.1 |
dfrapVnipTopologyInterfaceThe 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.6.4.2.1.1 |
dfrapVnipTopologyIndexThe 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.6.4.2.1.2 |
dfrapVnipTopologyDlciThe DLCI of the discovered neighboring peer.
This may be different from the local DLCI.ro INTEGER .1.3.6.1.4.1.485.6.4.2.1.3 |
dfrapVnipTopologyIpAddrThe IP address for the discovered peer.ro IpAddress .1.3.6.1.4.1.485.6.4.2.1.4 |
dfrapVnipTopologyNumHopsThe discovered peer is this number of hops away.
Each hop is a VNIP peer.ro INTEGER .1.3.6.1.4.1.485.6.4.2.1.5 |
dfrapVnipTopologyLocalDlciThe DLCI from this unit over which the remote peer
was discovered.ro INTEGER .1.3.6.1.4.1.485.6.4.2.1.6 |
dfrapVnipTopoTDNumSamplesThe number of transit delay samples collected.ro Counter .1.3.6.1.4.1.485.6.4.2.1.10 |
dfrapVnipTopoTDAvgDelayThe average transit delay between this
unit and the remote peer (in milliseconds).ro Counter .1.3.6.1.4.1.485.6.4.2.1.11 |
dfrapVnipTopoTDMaxDelayThe maximum transit delay between this
unit and the remote peer (in milliseconds).ro Counter .1.3.6.1.4.1.485.6.4.2.1.12 |
dfrapVnipTopoTDMinDelayThe minimum transit delay between this
node and the remote peer (in milliseconds).ro Counter .1.3.6.1.4.1.485.6.4.2.1.13 |
dfrapVnipTopoTDLastDelayThe most recent transit delay measured between
this node and the remote peer (in milliseconds).ro Counter .1.3.6.1.4.1.485.6.4.2.1.14 |
dfrapVnipTopoVLOOPStatusThis 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.ro Enumeration .1.3.6.1.4.1.485.6.4.2.1.15 |
dfrapVnipTopoVBERTStatusDisplays 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.6.4.2.1.16 |
dfrapVnipTopoVBertTxDESetFramesDisplays the number of Frames transmitted during VBERT/VLOOP Test
that had the Discard Eligibility indicator bit set.ro Counter .1.3.6.1.4.1.485.6.4.2.1.17 |
dfrapVnipTopoVBertRxDESetFramesDisplays the number of Frames received during VBERT/VLOOP Test
that had the Discard Eligibility indicator bit set.ro Counter .1.3.6.1.4.1.485.6.4.2.1.18 |
dfrapVnipTopoVBertTxDEClrFramesDisplays the number of Frames transmitted during VBERT/VLOOP Test
that had the Discard Eligibility indicator bit cleared.ro Counter .1.3.6.1.4.1.485.6.4.2.1.19 |
dfrapVnipTopoVBertRxDEClrFramesDisplays the number of Frames received during VBERT/VLOOP Test
that had the Discard Eligibility indicator bit cleared.ro Counter .1.3.6.1.4.1.485.6.4.2.1.20 |
dfrapVnipTopoVBertTransitDelayMaxThe maximum transit delay between this
node and the remote peer during the VBERT/VLOOP test.ro Counter .1.3.6.1.4.1.485.6.4.2.1.21 |
dfrapVnipTopoVBertTransitDelayAvgThe average transit delay between this
node and the remote peer during the VBERT/VLOOP test.ro Counter .1.3.6.1.4.1.485.6.4.2.1.22 |
dfrapVnipTopoVBertTimeElapseElapsed time since VBERT/VLOOP test was started or cleared.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.485.6.4.2.1.23 |
dfrapVnipTopoVBertPerUtilCIRThe 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.6.4.2.1.24 |
dfrapVnipTopoVBertPerUtilEIRThe 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.6.4.2.1.25 |
dfrapStatusMgmtTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.4.3 |
dfrapStatusMgmtChannelThis 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.6.4.3.1 |
dfrapStatusMgmtInterfaceThis 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.6.4.3.2 |
dfrapStatusMgmtInterfaceStatusThis is the status of the port(s) on which
the management traffic will appear.
(1) Active: port is configured and status is okay
(2) Inactive: port is declared out of service
(3) Alarm: port is experiencing an alarm condition that may
interefere with management accessro Enumeration .1.3.6.1.4.1.485.6.4.3.3 |
dfrapStatusMgmtDefaultDLCINoThis 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.6.4.3.4 |
dfrapStatusMgmtDefaultDLCIStatusThis 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.6.4.3.5 |
dfrapStatusLedTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.4.4 |
dfrapStatusDteModeLEDStatus 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.6.4.4.1 |
dfrapStatusDteStatusLEDStatus of the DTE Status LED.
(1) DTE Status LED green: normalro Enumeration .1.3.6.1.4.1.485.6.4.4.2 |
dfrapStatusDteTxLEDStatus 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.6.4.4.3 |
dfrapStatusDteRxLEDStatus 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.6.4.4.4 |
dfrapStatusDdsModeLEDStatus of the DDS Mode LED.
(1) DDS Mode LED is green: normal data mode
(2) DDS Mode LED is yellow: test modero Enumeration .1.3.6.1.4.1.485.6.4.4.5 |
dfrapStatusDdsStatusLEDStatus of the DDS Status LED.
(1) DDS Status LED is OFF: no signal received from WAN
(2) DDS Status LED is green: normal
(3) DDS Status LED is yellow: remote alarmro Enumeration .1.3.6.1.4.1.485.6.4.4.6 |
dfrapStatusAllLEDsStatus of all six DFRAP 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, DDS Mode, and DDS Status. For example,
'555550' would mean: DTE in normal mode, active status,
transmitting and receiving and DDS normal with remote alarm.ro DisplayString .1.3.6.1.4.1.485.6.4.4.7 |
dfrapVnipTransitDelayClearAllows 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.6.4.5 |
dfrapLmiSourcingIf 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.6.4.6 |
dfrapStatusDteTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.4.7 |
dfrapStatusDteModeStatus of the DTE port.
(1) No-connections: indicates the port is not completely
to pass data to/from the WAN.
(2) Active: port is configured and ready to pass data.
(3) Test: diagnostic condition in process.ro Enumeration .1.3.6.1.4.1.485.6.4.7.1 |
dfrapStatusDteRtsStatus 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.6.4.7.2 |
dfrapStatusDteDtrStatus 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.6.4.7.3 |
dfrapStatusDteDcdStatus 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.6.4.7.4 |
dfrapStatusDteDsrStatus 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.6.4.7.5 |
dfrapStatusDteCtsStatus 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.6.4.7.6 |
dfrapStatusDdsTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.4.8 |
dfrapStatusDdsLineStatusThe Current status of the physical interface.
Your network carrier can send Out-of-Service
or Maintenance Mode codes.
(1) in sync
(2) out of service
(3) out of frame
(4) bipolar violations
(5) loss of signal
(6) simplex current loopbackro Enumeration .1.3.6.1.4.1.485.6.4.8.1 |
dfrapStatusDdsLoopLengthThe estimated line attenuation (signal loss) on the
DDS channel. Actual cable length can be estimated with
the assumption that a good quality data grade cable
is used. Use of lower quality cabling will produce
greater line attenuation on shorter cable runs.
(1) est. between 40 and 50dB line loss, equivalent
to roughly 8 to 9 Kilometers of nominal cable length.
(2) est. between 39 and 44dB line loss, equivalent
to roughly 7 to 8 Kilometers of nominal cable length.
(3) est. between 33 and 38dB line loss, equivalent
to roughly 6 to 7 Kilometers of nominal cable length.
(4) est. between 27 and 22dB line loss, equivalent
to roughly 5 to 6 Kilometers of nominal cable length.
(5) est. between 21 and 26dB line loss, equivalent
to roughly 4 to 5 Kilometers of nominal cable length.
(6) est. between 15 and 20dB line loss, equivalent
to roughly 3 to 4 Kilometers of nominal cable length
(7) est. between 8 and 14dB line loss, equivalent
to roughly 2 to 3 Kilometers of nominal cable length
(8) est. between 1 and 7dB line loss, equivalent
to roughly .5 to 2 Kilometers of nominal cable length
(9) est. 0dB line loss, equivalent to less than 1Km nominal
cable lengthro Enumeration .1.3.6.1.4.1.485.6.4.8.2 |
dfrapVBertClearAllows 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.6.4.11 |
dfrapStatusLmiAutosenseThis 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.6.4.12 |
dfrapPerformance OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.5 |
dfrapPerfMgmtIp OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.5.2 |
dfrapPerfMgmtIpIFStatsTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.5.2.1 |
dfrapPerfMgmtIpIFInOctetsThe count of all management octets received.
Same as ifInOctets in mib-2.ro Counter .1.3.6.1.4.1.485.6.5.2.1.1 |
dfrapPerfMgmtIpIFInErrorsThe count of management packets received that could
not be delivered because of errors. Same as
ifInErrors in mib-2.ro Counter .1.3.6.1.4.1.485.6.5.2.1.2 |
dfrapPerfMgmtIpIFOutOctetsThe count of all management octets transmitted.
Same as ifOutOctets in mib-2.ro Counter .1.3.6.1.4.1.485.6.5.2.1.3 |
dfrapPerfMgmtIpIFOperStatusThe current operational state.
Same as ifOperStatus in mib-2.
(1) link up
(2) link down
(30 testro Enumeration .1.3.6.1.4.1.485.6.5.2.1.4 |
dfrapPerfMgmtIpIPStatsTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.5.2.2 |
dfrapPerfMgmtIpIPInRcvThe count of all management datagrams received.
Same as ipInReceives in mib-2.ro Counter .1.3.6.1.4.1.485.6.5.2.2.1 |
dfrapPerfMgmtIpIPInHdrErrThe count of management datagrams received 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.6.5.2.2.2 |
dfrapPerfMgmtIpIPInAddrErrThe count of management datagrams received 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.6.5.2.2.3 |
dfrapPerfMgmtIpIPInProtUnkThe count of management datagrams received that were
discarded because of unsupported protocols.
Same as ipInUnknownProtos in mib-2.ro Counter .1.3.6.1.4.1.485.6.5.2.2.4 |
dfrapPerfMgmtIpIPInDscrdThe count of management datagrams received 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.6.5.2.2.5 |
dfrapPerfMgmtIpIPInDlvrsThe count of management datagrams received that were
delivered to IP client-protocols.
Same as ipInDelivers in mib-2.ro Counter .1.3.6.1.4.1.485.6.5.2.2.6 |
dfrapPerfMgmtIpIPOutRqstThe count of all outgoing management datagrams
originating in this node.
Same as ipOutRequests in mib-2.ro Counter .1.3.6.1.4.1.485.6.5.2.2.7 |
dfrapPerfMgmtIpIPOutDscrdThe count of outgoing management datagrams 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.6.5.2.2.8 |
dfrapPerfMgmtIpIPOutNoRtThe count of outgoing management datagrams 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.6.5.2.2.9 |
dfrapPerfMgmtIpICMPStatsTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.5.2.3 |
dfrapPerfMgmtIpICMPInMsgsThe count of all management ICMP messages received.
Same as icmpInMsgs in mib-2.ro Counter .1.3.6.1.4.1.485.6.5.2.3.1 |
dfrapPerfMgmtIpICMPInErrorsThe count of management ICMP messages received with
errors. Same as icmpInErrors in mib-2.ro Counter .1.3.6.1.4.1.485.6.5.2.3.2 |
dfrapPerfMgmtIpICMPInDestUnreachsThe count of management ICMP Destination Unreachable
messages received.
Same as icmpInDestUnreachs in mib-2.ro Counter .1.3.6.1.4.1.485.6.5.2.3.3 |
dfrapPerfMgmtIpICMPInTimeExcdsThe count of management ICMP Time Exceeded messages
received.
Same as icmpInTimeExcds in mib-2.ro Counter .1.3.6.1.4.1.485.6.5.2.3.4 |
dfrapPerfMgmtIpICMPInParmProbsThe count of management ICMP Parameter Problem messages
received.
Same as icmpInParmProbs in mib-2.ro Counter .1.3.6.1.4.1.485.6.5.2.3.5 |
dfrapPerfMgmtIpICMPInRedirectsThe count of management ICMP Redirect messages received.
Same as icmpInRedirects in mib-2.ro Counter .1.3.6.1.4.1.485.6.5.2.3.6 |
dfrapPerfMgmtIpICMPInEchosThe count of management ICMP Echo messages received.
Same as icmpInEchos in mib-2.ro Counter .1.3.6.1.4.1.485.6.5.2.3.7 |
dfrapPerfMgmtIpICMPInEchoRepsThe count of management ICMP Echo Reply messages received.
Same as icmpInEchoReps in mib-2.ro Counter .1.3.6.1.4.1.485.6.5.2.3.8 |
dfrapPerfMgmtIpICMPOutMsgsThe count of all outgoing management ICMP messages
originating in this node.
Same as icmpOutMsgs in mib-2.ro Counter .1.3.6.1.4.1.485.6.5.2.3.9 |
dfrapPerfMgmtIpICMPOutErrorsThe count of outgoing management ICMP messages not
transmitted due problems found by the ICMP layer. which this entity did
Same as icmpOutErrors in mib-2.ro Counter .1.3.6.1.4.1.485.6.5.2.3.10 |
dfrapPerfMgmtIpICMPOutDestUnreachsThe count of outgoing management ICMP Destination Unreachable
messages.
Same as icmpOutDestUnreachs in mib-2.ro Counter .1.3.6.1.4.1.485.6.5.2.3.11 |
dfrapPerfMgmtIpICMPOutParmProbsThe count of outgoing management ICMP Parameter Problem
messages.
Same as icmpOutParmProbs in mib-2.ro Counter .1.3.6.1.4.1.485.6.5.2.3.12 |
dfrapPerfMgmtIpICMPOutRedirectsThe count of outgoing management ICMP Redirect messages.
Same as icmpOutRedirects in mib-2.ro Counter .1.3.6.1.4.1.485.6.5.2.3.13 |
dfrapPerfMgmtIpICMPOutEchosThe count of management outgoing ICMP Echo messages.
Same as icmpOutEchos in mib-2.ro Counter .1.3.6.1.4.1.485.6.5.2.3.14 |
dfrapPerfMgmtIpICMPOutEchoRepsThe count of management outgoing ICMP Echo Reply messages.
Same as icmpOutEchoReps in mib-2.ro Counter .1.3.6.1.4.1.485.6.5.2.3.15 |
dfrapPerfMgmtIpUDPStatsTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.5.2.4 |
dfrapPerfMgmtIpUDPInDatagramsThe count of all management UDP datagrams received.
Same as udpInDatagrams in mib-2.ro Counter .1.3.6.1.4.1.485.6.5.2.4.1 |
dfrapPerfMgmtIpUDPOutDatagramsThe count of all management UDP datagrams sent.
Same as udpOutDatagrams in mib-2.ro Counter .1.3.6.1.4.1.485.6.5.2.4.2 |
dfrapPerfMgmtIpUDPNoPortsThe count of all management UDP datagrams received
with no application at the destination port.
Same as udpNoPorts in mib-2.ro Counter .1.3.6.1.4.1.485.6.5.2.4.3 |
dfrapPerfMgmtIpTCPStatsTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.5.2.5 |
dfrapPerfMgmtIpTCPActiveOpensThe count of the times management TCP connections
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.6.5.2.5.1 |
dfrapPerfMgmtIpTCPPassiveOpensThe count of the times management TCP connections
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.6.5.2.5.2 |
dfrapPerfMgmtIpTCPAttemptFailsThe count of the times management TCP connections
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.6.5.2.5.3 |
dfrapPerfMgmtIpTCPCurrEstabThe count of the management TCP connections in state
ESTABLISHED or CLOSE-WAIT.
Same as tcpCurrEstab in mib-2.ro Gauge .1.3.6.1.4.1.485.6.5.2.5.4 |
dfrapPerfMgmtIpTCPInSegsThe count of all the management segments received.
Same as tcpInSegs in mib-2.ro Counter .1.3.6.1.4.1.485.6.5.2.5.5 |
dfrapPerfMgmtIpTCPOutSegsThe count of all the management segments sent.
Same as tcpOutSegs in mib-2.ro Counter .1.3.6.1.4.1.485.6.5.2.5.6 |
dfrapPerfThruput OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.5.3 |
dfrapPerfThruputPerIntfTableThe throughput per interface table. These values are accumulated
across all DLCIs. SEQUENCE OF DfrapPerfThruputPerIntfEntry .1.3.6.1.4.1.485.6.5.3.1 |
dfrapPerfThruputPerIntfEntryAn entry in the throughput per interface table. DfrapPerfThruputPerIntfEntry .1.3.6.1.4.1.485.6.5.3.1.1 |
dfrapPerfThruputPerIntfIndexInterface for which the statistics apply.
(1) DTE interface
(2) DDS interfacero Enumeration .1.3.6.1.4.1.485.6.5.3.1.1.1 |
dfrapPerfThruputPerIntfRxByteCntThe number of framed bytes that have been received
on this interface.ro Counter .1.3.6.1.4.1.485.6.5.3.1.1.2 |
dfrapPerfThruputPerIntfTxByteCntThe number of framed bytes that have been transmit
on this interface.ro Counter .1.3.6.1.4.1.485.6.5.3.1.1.3 |
dfrapPerfThruputPerIntfRxFrameCntThe number of frames that have been received
on this interface.ro Counter .1.3.6.1.4.1.485.6.5.3.1.1.4 |
dfrapPerfThruputPerIntfTxFrameCntThe number of frames that have been transmit
on this interface.ro Counter .1.3.6.1.4.1.485.6.5.3.1.1.5 |
dfrapPerfThruputPerIntfRxCrcErrCntThe number of frames with CRC errors received
on this interface.ro Counter .1.3.6.1.4.1.485.6.5.3.1.1.6 |
dfrapPerfThruputPerIntfRxAbortCntThe number of aborted frames received
on this interface.ro Counter .1.3.6.1.4.1.485.6.5.3.1.1.7 |
dfrapPerfThruputPerIntfRxBpvCntThe number of BPV errors received
on this interface.ro Counter .1.3.6.1.4.1.485.6.5.3.1.1.8 |
dfrapPerfThruputPerDlciTableLayer 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 DfrapPerfThruputPerDlciEntry .1.3.6.1.4.1.485.6.5.3.2 |
dfrapPerfThruputPerDlciEntryThe Statistics for a particular Data Link
Connection Management Interface (DLCI). DfrapPerfThruputPerDlciEntry .1.3.6.1.4.1.485.6.5.3.2.1 |
dfrapPerfThruputPerDlciIndexThis 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.6.5.3.2.1.1 |
dfrapPerfThruputPerDlciValueThe DLCI value in which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.6.5.3.2.1.2 |
dfrapPerfThruputPerDlciCreateTimeThe 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.6.5.3.2.1.3 |
dfrapPerfThruputPerDlciChangeTimeThe 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.6.5.3.2.1.4 |
dfrapPerfThruputPerDlciRxByteThe 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.6.5.3.2.1.5 |
dfrapPerfThruputPerDlciTxByteThe 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.6.5.3.2.1.6 |
dfrapPerfThruputPerDlciRxFrameThe 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.6.5.3.2.1.7 |
dfrapPerfThruputPerDlciTxFrameThe 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.6.5.3.2.1.8 |
dfrapPerfThruputPerDlciRxFecnThe 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.6.5.3.2.1.9 |
dfrapPerfThruputPerDlciRxBecnThe 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.6.5.3.2.1.10 |
dfrapPerfThruputPerDlciRxDeThe 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.6.5.3.2.1.11 |
dfrapPerfThruputPerDlciTxDeThe 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.6.5.3.2.1.12 |
dfrapPerfThruputPerDlciRxThruputThe 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.6.5.3.2.1.13 |
dfrapPerfThruputPerDlciTxThruputThe 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.6.5.3.2.1.14 |
dfrapPerfThruputPerDlciCIRThe 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.6.5.3.2.1.15 |
dfrapPerfThruputPerDlciUptimeThe 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.6.5.3.2.1.16 |
dfrapPerfThruputPerDlciDowntimeThe 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.6.5.3.2.1.17 |
dfrapPerfThruputPerDlciCirTypeThe 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.6.5.3.2.1.18 |
dfrapPerfThruputPerDlciPvcStateThe 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.6.5.3.2.1.19 |
dfrapPerfThruputPerDlciOutageCountThe 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.6.5.3.2.1.20 |
dfrapPerfThruputPerDlciAvailabilityThe 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.6.5.3.2.1.21 |
dfrapPerfThruputPerDlciMTBSOMean Time Between Service Outages: UpTime/OutageCount
or zero if OutageCount = 0 (in seconds).ro INTEGER .1.3.6.1.4.1.485.6.5.3.2.1.22 |
dfrapPerfThruputPerDlciMTTSRMean Time to ServiceRestoral: DownTime/OutageCount
or zero if OutageCount = 0 (in seconds).ro INTEGER .1.3.6.1.4.1.485.6.5.3.2.1.23 |
dfrapPerfThruputPerDlciEncapTypeThe 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.6.5.3.2.1.24 |
dfrapPerfThruputPerDlciRxUtilizationStatusThe 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.6.5.3.2.1.25 |
dfrapPerfThruputPerDlciTxUtilizationStatusThe 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.6.5.3.2.1.26 |
dfrapPerfThruputPerDlciEIRThe 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.6.5.3.2.1.27 |
dfrapPerfThruputCommands OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.5.3.3 |
dfrapPerfThruputCmdClearDteStatsAllows 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.6.5.3.3.1 |
dfrapPerfThruputCmdClearDdsStatsAllows the user to zero out all the interface statistics in
the DDS portion of the ThruputPerIntf statistics table.
(1) Clear WAN interface statistics command.rw Enumeration .1.3.6.1.4.1.485.6.5.3.3.2 |
dfrapPerfThruputCmdClearAllIntfStatsAllows the user to zero out all the statistics in
the ThruputPerIntf statistics table.rw Enumeration .1.3.6.1.4.1.485.6.5.3.3.3 |
dfrapPerfThruputCmdClearDlciStatsAllows 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.6.5.3.3.4 |
dfrapPerfThruputCmdClearAllStatsAllows 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.6.5.3.3.5 |
dfrapPerfThruputCmdRemoveStsDlciAllows the user to remove a Dlci from the short term
statistics tables.rw INTEGER .1.3.6.1.4.1.485.6.5.3.3.6 |
dfrapPerfThruputCmdReplaceDlciTableAllows the user to replace one DLCI in the short-term
statistics table with another one. SEQUENCE OF DfrapPerfThruputCmdReplaceDlciEntry .1.3.6.1.4.1.485.6.5.3.3.7 |
dfrapPerfThruputCmdReplaceDlciEntryAllows the user to replace one DLCI in the short-term
statistics table with another one. DfrapPerfThruputCmdReplaceDlciEntry .1.3.6.1.4.1.485.6.5.3.3.7.1 |
dfrapPerfThruputCmdReplaceDlciValueA 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.6.5.3.3.7.1.1 |
dfrapPerfThruputCmdReplaceDlciNewValueA 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.6.5.3.3.7.1.2 |
dfrapPerfThruputCmdAvailabilityStsDlciResetAllows 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.6.5.3.3.8 |
dfrapPerfThruputCmdAvailabilityStsDlciResetAllAllows 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.6.5.3.3.9 |
dfrapPerfThruputCmdCountsStsDlciResetAllows 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.6.5.3.3.10 |
dfrapPerfThruputCmdCountsStsDlciResetAllAllows 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.6.5.3.3.11 |
dfrapPerfThruputCmdAllStsDlciResetAllows 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.6.5.3.3.12 |
dfrapPerfThruputCmdAllStsDlciResetAllAllows 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.6.5.3.3.13 |
dfrapPerfNetworkShortTerm OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.5.4 |
dfrapPerfNetwProtoPerDlciTableThe 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 DfrapPerfNetwProtoPerDlciEntry .1.3.6.1.4.1.485.6.5.4.1 |
dfrapPerfNetwProtoPerDlciEntryThe Network Layer Short Term Statistics
for a particular DLCI. This table organizes
statistics by high-layer network protocol. DfrapPerfNetwProtoPerDlciEntry .1.3.6.1.4.1.485.6.5.4.1.1 |
dfrapPerfNetwProtoPerDlciIntervalThe 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.6.5.4.1.1.1 |
dfrapPerfNetwProtoPerDlciValueThe DLCI value with which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.6.5.4.1.1.2 |
dfrapPerfNetwProtoPerDlciRxTotalThe total number of received Network Layer bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.1.1.3 |
dfrapPerfNetwProtoPerDlciTxTotalThe total number of transmitted Network Layer bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.1.1.4 |
dfrapPerfNetwProtoPerDlciRxIpThe number of received IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.1.1.5 |
dfrapPerfNetwProtoPerDlciTxIpThe number of transmitted IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.1.1.6 |
dfrapPerfNetwProtoPerDlciRxIpxThe number of received IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.1.1.7 |
dfrapPerfNetwProtoPerDlciTxIpxThe number of transmitted IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.1.1.8 |
dfrapPerfNetwProtoPerDlciRxSnaThe number of received SNA bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.1.1.9 |
dfrapPerfNetwProtoPerDlciTxSnaThe number of transmitted SNA bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.1.1.10 |
dfrapPerfNetwProtoPerDlciRxArpThe number of received ARP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.1.1.11 |
dfrapPerfNetwProtoPerDlciTxArpThe number of transmitted ARP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.1.1.12 |
dfrapPerfNetwProtoPerDlciRxCiscoThe number of received Cisco protocol bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.1.1.13 |
dfrapPerfNetwProtoPerDlciTxCiscoThe number of transmitted Cisco protocol bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.1.1.14 |
dfrapPerfNetwProtoPerDlciRxOtherThe 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.6.5.4.1.1.15 |
dfrapPerfNetwProtoPerDlciTxOtherThe 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.6.5.4.1.1.16 |
dfrapPerfNetwProtoPerDlciRxVnipThe number of received VNIP protocol bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.1.1.17 |
dfrapPerfNetwProtoPerDlciTxVnipThe number of transmitted VNIP protocol bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.1.1.18 |
dfrapPerfNetwProtoPerDlciRxAnnexGThe number of received Annex G protocol
bytes that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.1.1.19 |
dfrapPerfNetwProtoPerDlciTxAnnexGThe number of transmitted Annex G protocol
bytes that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.1.1.20 |
dfrapPerfNetwProtoTotalTableThe Short Term Statistics on Network Layer
protocols summed across all DLCIs. SEQUENCE OF DfrapPerfNetwProtoTotalEntry .1.3.6.1.4.1.485.6.5.4.2 |
dfrapPerfNetwProtoTotalEntryThe Network Layer Short Term Statistics
across all DLCIs. DfrapPerfNetwProtoTotalEntry .1.3.6.1.4.1.485.6.5.4.2.1 |
dfrapPerfNetwProtoTotalIntervalThe 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.6.5.4.2.1.1 |
dfrapPerfNetwProtoTotalRxTotalThe total number of received Network Layer bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.2.1.3 |
dfrapPerfNetwProtoTotalTxTotalThe total number of transmitted Network Layer bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.2.1.4 |
dfrapPerfNetwProtoTotalRxIpThe number of received IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.2.1.5 |
dfrapPerfNetwProtoTotalTxIpThe number of transmitted IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.2.1.6 |
dfrapPerfNetwProtoTotalRxIpxThe number of received IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.2.1.7 |
dfrapPerfNetwProtoTotalTxIpxThe number of transmitted IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.2.1.8 |
dfrapPerfNetwProtoTotalRxSnaThe number of received SNA bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.2.1.9 |
dfrapPerfNetwProtoTotalTxSnaThe number of transmitted SNA bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.2.1.10 |
dfrapPerfNetwProtoTotalRxArpThe number of received ARP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.2.1.11 |
dfrapPerfNetwProtoTotalTxArpThe number of transmitted ARP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.2.1.12 |
dfrapPerfNetwProtoTotalRxCiscoThe number of received Cisco protocol bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.2.1.13 |
dfrapPerfNetwProtoTotalTxCiscoThe number of transmitted Cisco protocol bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.2.1.14 |
dfrapPerfNetwProtoTotalRxOtherThe 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.6.5.4.2.1.15 |
dfrapPerfNetwProtoTotalTxOtherThe 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.6.5.4.2.1.16 |
dfrapPerfNetwProtoTotalRxVnipThe number of received VNIP protocol bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.2.1.17 |
dfrapPerfNetwProtoTotalTxVnipThe number of transmitted VNIP protocol bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.2.1.18 |
dfrapPerfNetwProtoTotalRxAnnexGThe number of received Annex G protocol bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.2.1.19 |
dfrapPerfNetwProtoTotalTxAnnexGThe number of transmitted Annex G protocol bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.2.1.20 |
dfrapPerfIpPerDlciTableThe Short Term Statistics on the IP
protocol for each DLCI. SEQUENCE OF DfrapPerfIpPerDlciEntry .1.3.6.1.4.1.485.6.5.4.3 |
dfrapPerfIpPerDlciEntryThe IP Short Term Statistics for a particular DLCI. DfrapPerfIpPerDlciEntry .1.3.6.1.4.1.485.6.5.4.3.1 |
dfrapPerfIpPerDlciIntervalThe 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.6.5.4.3.1.1 |
dfrapPerfIpPerDlciValueThe DLCI value with which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.6.5.4.3.1.2 |
dfrapPerfIpPerDlciRxTotalThe total number of received IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.3.1.3 |
dfrapPerfIpPerDlciTxTotalThe total number of transmitted IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.3.1.4 |
dfrapPerfIpPerDlciRxTcpThe number of received TCP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.3.1.5 |
dfrapPerfIpPerDlciTxTcpThe number of transmitted TCP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.3.1.6 |
dfrapPerfIpPerDlciRxUdpThe number of received UDP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.3.1.7 |
dfrapPerfIpPerDlciTxUdpThe number of transmitted UDP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.3.1.8 |
dfrapPerfIpPerDlciRxIcmpThe number of received ICMP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.3.1.9 |
dfrapPerfIpPerDlciTxIcmpThe number of transmitted ICMP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.3.1.10 |
dfrapPerfIpPerDlciRxOtherThe 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.6.5.4.3.1.11 |
dfrapPerfIpPerDlciTxOtherThe 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.6.5.4.3.1.12 |
dfrapPerfIpPerDlciRxIgrpThe number of received IGRP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.3.1.13 |
dfrapPerfIpPerDlciTxIgrpThe number of transmitted IGRP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.3.1.14 |
dfrapPerfIpTotalTableThe Short Term Statistics on the IP
protocol for each DLCI. SEQUENCE OF DfrapPerfIpTotalEntry .1.3.6.1.4.1.485.6.5.4.4 |
dfrapPerfIpTotalEntryThe IP Short Term Statistics across all DLCIs. DfrapPerfIpTotalEntry .1.3.6.1.4.1.485.6.5.4.4.1 |
dfrapPerfIpTotalIntervalThe 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.6.5.4.4.1.1 |
dfrapPerfIpTotalRxTotalThe total number of received IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.4.1.3 |
dfrapPerfIpTotalTxTotalThe total number of transmitted IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.4.1.4 |
dfrapPerfIpTotalRxTcpThe number of received TCP over IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.4.1.5 |
dfrapPerfIpTotalTxTcpThe number of transmitted TCP over IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.4.1.6 |
dfrapPerfIpTotalRxUdpThe number of received UDP over IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.4.1.7 |
dfrapPerfIpTotalTxUdpThe number of transmitted UDP over IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.4.1.8 |
dfrapPerfIpTotalRxIcmpThe number of received ICMP over IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.4.1.9 |
dfrapPerfIpTotalTxIcmpThe number of transmitted ICMP over IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.4.1.10 |
dfrapPerfIpTotalRxOtherThe 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.6.5.4.4.1.11 |
dfrapPerfIpTotalTxOtherThe 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.6.5.4.4.1.12 |
dfrapPerfIpTotalRxIgrpThe number of received IGRP over IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.4.1.13 |
dfrapPerfIpTotalTxIgrpThe number of transmitted IGRP over IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.4.1.14 |
dfrapPerfIcmpPerDlciTableShort Term Statistics on the ICMP
protocol for each DLCI. SEQUENCE OF DfrapPerfIcmpPerDlciEntry .1.3.6.1.4.1.485.6.5.4.5 |
dfrapPerfIcmpPerDlciEntryThe ICMP Short Term Statistics for a particular DLCI. DfrapPerfIcmpPerDlciEntry .1.3.6.1.4.1.485.6.5.4.5.1 |
dfrapPerfIcmpPerDlciIntervalThe 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.6.5.4.5.1.1 |
dfrapPerfIcmpPerDlciValueThe DLCI value in which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.6.5.4.5.1.2 |
dfrapPerfIcmpPerDlciRxTotalThe total number of ICMP bytes that have been
counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.5.1.3 |
dfrapPerfIcmpPerDlciTxTotalThe total number of ICMP bytes that have been
counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.5.1.4 |
dfrapPerfIcmpPerDlciRxEchoRepThe number of bytes in ICMP ECHO repies
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.5.1.5 |
dfrapPerfIcmpPerDlciTxEchoRepThe number of bytes in ICMP ECHO repies
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.5.1.6 |
dfrapPerfIcmpPerDlciRxDestUnrThe number of bytes in ICMP destination unreachables
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.5.1.7 |
dfrapPerfIcmpPerDlciTxDestUnrThe number of bytes in ICMP destination unreachables
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.5.1.8 |
dfrapPerfIcmpPerDlciRxSrcQuenchThe number of bytes in ICMP source quenches
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.5.1.9 |
dfrapPerfIcmpPerDlciTxSrcQuenchThe number of bytes in ICMP source quenches
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.5.1.10 |
dfrapPerfIcmpPerDlciRxRedirectThe number of bytes in ICMP redirects
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.5.1.11 |
dfrapPerfIcmpPerDlciTxRedirectThe number of bytes in ICMP redirects
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.5.1.12 |
dfrapPerfIcmpPerDlciRxEchoReqThe number of bytes in ICMP ECHO requests
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.5.1.13 |
dfrapPerfIcmpPerDlciTxEchoReqThe number of bytes in ICMP ECHO requests
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.5.1.14 |
dfrapPerfIcmpPerDlciRxTimeExcdThe number of bytes in ICMP time exceededs
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.5.1.15 |
dfrapPerfIcmpPerDlciTxTimeExcdThe number of bytes in ICMP time exceededs
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.5.1.16 |
dfrapPerfIcmpPerDlciRxParamProbThe number of bytes in ICMP parameter problems
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.5.1.17 |
dfrapPerfIcmpPerDlciTxParamProbThe number of bytes in ICMP parameter problems
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.5.1.18 |
dfrapPerfIcmpPerDlciRxTimestpReqThe number of bytes in ICMP timestamp requests
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.5.1.19 |
dfrapPerfIcmpPerDlciTxTimestpReqThe number of bytes in ICMP timestamp requests
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.5.1.20 |
dfrapPerfIcmpPerDlciRxTimestpRepThe number of bytes in ICMP timestamp replies
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.5.1.21 |
dfrapPerfIcmpPerDlciTxTimestpRepThe number of bytes in ICMP timestamp replies
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.5.1.22 |
dfrapPerfIcmpPerDlciRxAddrMaskReqThe number of bytes in ICMP address mask requests
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.5.1.23 |
dfrapPerfIcmpPerDlciTxAddrMaskReqThe number of bytes in ICMP address mask requests
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.5.1.24 |
dfrapPerfIcmpPerDlciRxAddrMaskRepThe number of bytes in ICMP address mask replies
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.5.1.25 |
dfrapPerfIcmpPerDlciTxAddrMaskRepThe number of bytes in ICMP address mask replies
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.5.1.26 |
dfrapPerfIcmpPerDlciRxPktTooBigThe number of bytes in ICMP packet too bigs
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.5.1.27 |
dfrapPerfIcmpPerDlciTxPktTooBigThe number of bytes in ICMP packet too bigs
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.5.1.28 |
dfrapPerfIcmpPerDlciRxGmQueryThe number of bytes in ICMP group membership
queries that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.5.1.29 |
dfrapPerfIcmpPerDlciTxGmQueryThe number of bytes in ICMP group membership
queries that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.5.1.30 |
dfrapPerfIcmpPerDlciRxGmReportThe number of bytes in ICMP group membership
reports that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.5.1.31 |
dfrapPerfIcmpPerDlciTxGmReportThe number of bytes in ICMP group membership
reports that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.5.1.32 |
dfrapPerfIcmpPerDlciRxGmReductThe number of bytes in ICMP group membership
reductions that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.5.1.33 |
dfrapPerfIcmpPerDlciTxGmReductThe number of bytes in ICMP group membership
reductions that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.5.1.34 |
dfrapPerfIcmpTotalTableShort Term Statistics on the ICMP
protocol across all DLCIs. SEQUENCE OF DfrapPerfIcmpTotalEntry .1.3.6.1.4.1.485.6.5.4.6 |
dfrapPerfIcmpTotalEntryThe ICMP Short Term Statistics across all DLCIs. DfrapPerfIcmpTotalEntry .1.3.6.1.4.1.485.6.5.4.6.1 |
dfrapPerfIcmpTotalIntervalThe 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.6.5.4.6.1.1 |
dfrapPerfIcmpTotalRxTotalThe total number of ICMP bytes that have been
counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.6.1.3 |
dfrapPerfIcmpTotalTxTotalThe total number of ICMP bytes that have been
counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.6.1.4 |
dfrapPerfIcmpTotalRxEchoRepThe number of bytes in ICMP ECHO repies
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.6.1.5 |
dfrapPerfIcmpTotalTxEchoRepThe number of bytes in ICMP ECHO repies
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.6.1.6 |
dfrapPerfIcmpTotalRxDestUnrThe number of bytes in ICMP destination unreachables
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.6.1.7 |
dfrapPerfIcmpTotalTxDestUnrThe number of bytes in ICMP destination unreachables
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.6.1.8 |
dfrapPerfIcmpTotalRxSrcQuenchThe number of bytes in ICMP source quenches
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.6.1.9 |
dfrapPerfIcmpTotalTxSrcQuenchThe number of bytes in ICMP source quenches
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.6.1.10 |
dfrapPerfIcmpTotalRxRedirectThe number of bytes in ICMP redirects
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.6.1.11 |
dfrapPerfIcmpTotalTxRedirectThe number of bytes in ICMP redirects
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.6.1.12 |
dfrapPerfIcmpTotalRxEchoReqThe number of bytes in ICMP ECHO requests
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.6.1.13 |
dfrapPerfIcmpTotalTxEchoReqThe number of bytes in ICMP ECHO requests
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.6.1.14 |
dfrapPerfIcmpTotalRxTimeExcdThe number of bytes in ICMP time exceededs
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.6.1.15 |
dfrapPerfIcmpTotalTxTimeExcdThe number of bytes in ICMP time exceededs
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.6.1.16 |
dfrapPerfIcmpTotalRxParamProbThe number of bytes in ICMP parameter problems
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.6.1.17 |
dfrapPerfIcmpTotalTxParamProbThe number of bytes in ICMP parameter problems
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.6.1.18 |
dfrapPerfIcmpTotalRxTimestpReqThe number of bytes in ICMP timestamp requests
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.6.1.19 |
dfrapPerfIcmpTotalTxTimestpReqThe number of bytes in ICMP timestamp requests
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.6.1.20 |
dfrapPerfIcmpTotalRxTimestpRepThe number of bytes in ICMP timestamp replies
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.6.1.21 |
dfrapPerfIcmpTotalTxTimestpRepThe number of bytes in ICMP timestamp replies
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.6.1.22 |
dfrapPerfIcmpTotalRxAddrMaskReqThe number of bytes in ICMP address mask requests
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.6.1.23 |
dfrapPerfIcmpTotalTxAddrMaskReqThe number of bytes in ICMP address mask requests
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.6.1.24 |
dfrapPerfIcmpTotalRxAddrMaskRepThe number of bytes in ICMP address mask replies
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.6.1.25 |
dfrapPerfIcmpTotalTxAddrMaskRepThe number of bytes in ICMP address mask replies
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.6.1.26 |
dfrapPerfIcmpTotalRxPktTooBigThe number of bytes in ICMP packet too bigs
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.6.1.27 |
dfrapPerfIcmpTotalTxPktTooBigThe number of bytes in ICMP packet too bigs
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.6.1.28 |
dfrapPerfIcmpTotalRxGmQueryThe number of bytes in ICMP group membership
queries that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.6.1.29 |
dfrapPerfIcmpTotalTxGmQueryThe number of bytes in ICMP group membership
queries that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.6.1.30 |
dfrapPerfIcmpTotalRxGmReportThe number of bytes in ICMP group membership
reports that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.6.1.31 |
dfrapPerfIcmpTotalTxGmReportThe number of bytes in ICMP group membership
reports that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.6.1.32 |
dfrapPerfIcmpTotalRxGmReductThe number of bytes in ICMP group membership
reductions that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.6.1.33 |
dfrapPerfIcmpTotalTxGmReductThe number of bytes in ICMP group membership
reductions that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.6.1.34 |
dfrapPerfApplicationPerDlciTableThe Short Term Statistics on the Application
protocol for each DLCI. SEQUENCE OF DfrapPerfApplicationPerDlciEntry .1.3.6.1.4.1.485.6.5.4.7 |
dfrapPerfApplicationPerDlciEntryThe Application Short Term Statistics for a particular DLCI. DfrapPerfApplicationPerDlciEntry .1.3.6.1.4.1.485.6.5.4.7.1 |
dfrapPerfApplicationPerDlciIntervalThe 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.6.5.4.7.1.1 |
dfrapPerfApplicationPerDlciValueThe DLCI value with which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.6.5.4.7.1.2 |
dfrapPerfApplicationPerDlciRxSnmpThe number of received SNMP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.7.1.3 |
dfrapPerfApplicationPerDlciTxSnmpThe number of transmitted SNMP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.7.1.4 |
dfrapPerfApplicationPerDlciRxSnmpTrapThe number of received SNMP TRAP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.7.1.5 |
dfrapPerfApplicationPerDlciTxSnmpTrapThe number of transmitted SNMP TRAP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.7.1.6 |
dfrapPerfApplicationPerDlciRxHttpThe number of received HTTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.7.1.7 |
dfrapPerfApplicationPerDlciTxHttpThe number of transmitted HTTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.7.1.8 |
dfrapPerfApplicationPerDlciRxTelnetThe number of received Telnet bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.7.1.9 |
dfrapPerfApplicationPerDlciTxTelnetThe number of transmitted Telnet bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.7.1.10 |
dfrapPerfApplicationPerDlciRxSmtpThe number of received SMTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.7.1.11 |
dfrapPerfApplicationPerDlciTxSmtpThe number of transmitted SMTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.7.1.12 |
dfrapPerfApplicationPerDlciRxFtpThe number of received FTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.7.1.13 |
dfrapPerfApplicationPerDlciTxFtpThe number of transmitted FTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.7.1.14 |
dfrapPerfApplicationPerDlciRxTftpThe number of received TFTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.7.1.15 |
dfrapPerfApplicationPerDlciTxTftpThe number of transmitted TFTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.7.1.16 |
dfrapPerfApplicationPerDlciRxCustom1The 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.6.5.4.7.1.17 |
dfrapPerfApplicationPerDlciTxCustom1The 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.6.5.4.7.1.18 |
dfrapPerfApplicationPerDlciRxCustom2The 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.6.5.4.7.1.19 |
dfrapPerfApplicationPerDlciTxCustom2The 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.6.5.4.7.1.20 |
dfrapPerfApplicationPerDlciRxCustom3The 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.6.5.4.7.1.21 |
dfrapPerfApplicationPerDlciTxCustom3The 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.6.5.4.7.1.22 |
dfrapPerfApplicationPerDlciRxCustom4The 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.6.5.4.7.1.23 |
dfrapPerfApplicationPerDlciTxCustom4The 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.6.5.4.7.1.24 |
dfrapPerfApplicationTotalTableThe Short Term Statistics on the Application
protocol across all DLCIs. SEQUENCE OF DfrapPerfApplicationTotalEntry .1.3.6.1.4.1.485.6.5.4.8 |
dfrapPerfApplicationTotalEntryThe Application Short Term Statistics across all DLCIs.. DfrapPerfApplicationTotalEntry .1.3.6.1.4.1.485.6.5.4.8.1 |
dfrapPerfApplicationTotalIntervalThe 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.6.5.4.8.1.1 |
dfrapPerfApplicationTotalRxSnmpThe number of received SNMP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.8.1.3 |
dfrapPerfApplicationTotalTxSnmpThe number of transmitted SNMP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.8.1.4 |
dfrapPerfApplicationTotalRxSnmpTrapThe number of received SNMP TRAP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.8.1.5 |
dfrapPerfApplicationTotalTxSnmpTrapThe number of transmitted SNMP TRAP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.8.1.6 |
dfrapPerfApplicationTotalRxHttpThe number of received HTTP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.8.1.7 |
dfrapPerfApplicationTotalTxHttpThe number of transmitted HTTP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.8.1.8 |
dfrapPerfApplicationTotalRxTelnetThe number of received Telnet bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.8.1.9 |
dfrapPerfApplicationTotalTxTelnetThe number of transmitted Telnet bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.8.1.10 |
dfrapPerfApplicationTotalRxSmtpThe number of received SMTP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.8.1.11 |
dfrapPerfApplicationTotalTxSmtpThe number of transmitted SMTP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.8.1.12 |
dfrapPerfApplicationTotalRxFtpThe number of received FTP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.8.1.13 |
dfrapPerfApplicationTotalTxFtpThe number of transmitted FTP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.8.1.14 |
dfrapPerfApplicationTotalRxTftpThe number of received TFTP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.8.1.15 |
dfrapPerfApplicationTotalTxTftpThe number of transmitted TFTP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.8.1.16 |
dfrapPerfApplicationTotalRxCustom1The 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.6.5.4.8.1.17 |
dfrapPerfApplicationTotalTxCustom1The 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.6.5.4.8.1.18 |
dfrapPerfApplicationTotalRxCustom2The 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.6.5.4.8.1.19 |
dfrapPerfApplicationTotalTxCustom2The 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.6.5.4.8.1.20 |
dfrapPerfApplicationTotalRxCustom3The 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.6.5.4.8.1.21 |
dfrapPerfApplicationTotalTxCustom3The 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.6.5.4.8.1.22 |
dfrapPerfApplicationTotalRxCustom4The 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.6.5.4.8.1.23 |
dfrapPerfApplicationTotalTxCustom4The 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.6.5.4.8.1.24 |
dfrapPerfRoutingPerDlciTableThe Short Term Statistics on the Routing
protocol for each DLCI. SEQUENCE OF DfrapPerfRoutingPerDlciEntry .1.3.6.1.4.1.485.6.5.4.9 |
dfrapPerfRoutingPerDlciEntryThe Routing Short Term Statistics for a particular DLCI. DfrapPerfRoutingPerDlciEntry .1.3.6.1.4.1.485.6.5.4.9.1 |
dfrapPerfRoutingPerDlciIntervalThe 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.6.5.4.9.1.1 |
dfrapPerfRoutingPerDlciValueThe DLCI value with which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.6.5.4.9.1.2 |
dfrapPerfRoutingPerDlciRxOspfThe number of received OSPF bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.9.1.3 |
dfrapPerfRoutingPerDlciTxOspfThe number of transmitted OSPF bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.9.1.4 |
dfrapPerfRoutingPerDlciRxRipThe number of received RIP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.9.1.5 |
dfrapPerfRoutingPerDlciTxRipThe number of transmitted RIP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.9.1.6 |
dfrapPerfRoutingPerDlciRxNetbiosThe number of received Netbios bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.9.1.7 |
dfrapPerfRoutingPerDlciTxNetbiosThe number of transmitted Netbios bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.9.1.8 |
dfrapPerfRoutingTotalTableThe Short Term Statistics on the Routing
protocol across all DLCIs. SEQUENCE OF DfrapPerfRoutingTotalEntry .1.3.6.1.4.1.485.6.5.4.10 |
dfrapPerfRoutingTotalEntryThe Routing Short Term Statistics across all DLCIs. DfrapPerfRoutingTotalEntry .1.3.6.1.4.1.485.6.5.4.10.1 |
dfrapPerfRoutingTotalIntervalThe 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.6.5.4.10.1.1 |
dfrapPerfRoutingTotalRxOspfThe number of received OSPF bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.10.1.3 |
dfrapPerfRoutingTotalTxOspfThe number of transmitted OSPF bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.10.1.4 |
dfrapPerfRoutingTotalRxRipThe number of received RIP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.10.1.5 |
dfrapPerfRoutingTotalTxRipThe number of transmitted RIP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.10.1.6 |
dfrapPerfRoutingTotalRxNetbiosThe number of received Netbios bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.10.1.7 |
dfrapPerfRoutingTotalTxNetbiosThe number of transmitted Netbios bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.10.1.8 |
dfrapPerfIpxPerDlciTableShort Term Statistics on the IPX
protocol for each DLCI. SEQUENCE OF DfrapPerfIpxPerDlciEntry .1.3.6.1.4.1.485.6.5.4.11 |
dfrapPerfIpxPerDlciEntryThe IPX Short Term Statistics for a particular DLCI. DfrapPerfIpxPerDlciEntry .1.3.6.1.4.1.485.6.5.4.11.1 |
dfrapPerfIpxPerDlciIntervalThe 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.6.5.4.11.1.1 |
dfrapPerfIpxPerDlciValueThe DLCI value in which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.6.5.4.11.1.2 |
dfrapPerfIpxPerDlciRxTotalThe total number of IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.11.1.3 |
dfrapPerfIpxPerDlciTxTotalThe total number of IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.11.1.4 |
dfrapPerfIpxPerDlciRxSpxThe number of SPX over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.11.1.5 |
dfrapPerfIpxPerDlciTxSpxThe number of SPX over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.11.1.6 |
dfrapPerfIpxPerDlciRxNcpThe number of NCP over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.11.1.7 |
dfrapPerfIpxPerDlciTxNcpThe number of NCP over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.11.1.8 |
dfrapPerfIpxPerDlciRxSapThe number of SAP over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.11.1.9 |
dfrapPerfIpxPerDlciTxSapThe number of SAP over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.11.1.10 |
dfrapPerfIpxPerDlciRxRipThe number of RIP over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.11.1.11 |
dfrapPerfIpxPerDlciTxRipThe number of RIP over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.11.1.12 |
dfrapPerfIpxPerDlciRxNetbiosThe number of NETBIOS over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.11.1.13 |
dfrapPerfIpxPerDlciTxNetbiosThe number of NETBIOS over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.11.1.14 |
dfrapPerfIpxPerDlciRxOtherThe 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.6.5.4.11.1.15 |
dfrapPerfIpxPerDlciTxOtherThe 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.6.5.4.11.1.16 |
dfrapPerfIpxTotalTableShort Term Statistics on the IPX
protocol across all DLCIs. SEQUENCE OF DfrapPerfIpxTotalEntry .1.3.6.1.4.1.485.6.5.4.12 |
dfrapPerfIpxTotalEntryThe IPX Short Term Statistics across all DLCIs. DfrapPerfIpxTotalEntry .1.3.6.1.4.1.485.6.5.4.12.1 |
dfrapPerfIpxTotalIntervalThe 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.6.5.4.12.1.1 |
dfrapPerfIpxTotalRxTotalThe total number of IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.12.1.3 |
dfrapPerfIpxTotalTxTotalThe total number of IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.12.1.4 |
dfrapPerfIpxTotalRxSpxThe number of SPX over IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.12.1.5 |
dfrapPerfIpxTotalTxSpxThe number of SPX over IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.12.1.6 |
dfrapPerfIpxTotalRxNcpThe number of NCP over IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.12.1.7 |
dfrapPerfIpxTotalTxNcpThe number of NCP over IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.12.1.8 |
dfrapPerfIpxTotalRxSapThe number of SAP over IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.12.1.9 |
dfrapPerfIpxTotalTxSapThe number of SAP over IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.12.1.10 |
dfrapPerfIpxTotalRxRipThe number of RIP over IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.12.1.11 |
dfrapPerfIpxTotalTxRipThe number of RIP over IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.12.1.12 |
dfrapPerfIpxTotalRxNetbiosThe number of NETBIOS over IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.12.1.13 |
dfrapPerfIpxTotalTxNetbiosThe number of NETBIOS over IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.12.1.14 |
dfrapPerfIpxTotalRxOtherThe 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.6.5.4.12.1.15 |
dfrapPerfIpxTotalTxOtherThe 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.6.5.4.12.1.16 |
dfrapPerfSnaPerDlciTableShort Term Statistics on the SNA
protocol for each DLCI. SEQUENCE OF DfrapPerfSnaPerDlciEntry .1.3.6.1.4.1.485.6.5.4.13 |
dfrapPerfSnaPerDlciEntryThe SNA Short Term Statistics for a particular DLCI. DfrapPerfSnaPerDlciEntry .1.3.6.1.4.1.485.6.5.4.13.1 |
dfrapPerfSnaPerDlciIntervalThe 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.6.5.4.13.1.1 |
dfrapPerfSnaPerDlciValueThe DLCI value in which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.6.5.4.13.1.2 |
dfrapPerfSnaPerDlciRxTotalThe total number of SNA bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.13.1.3 |
dfrapPerfSnaPerDlciTxTotalThe total number of SNA bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.13.1.4 |
dfrapPerfSnaPerDlciRxSubareaThe number of SNA Subarea bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.13.1.5 |
dfrapPerfSnaPerDlciTxSubareaThe number of SNA Subarea bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.13.1.6 |
dfrapPerfSnaPerDlciRxPeriphThe number of SNA Periph bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.13.1.7 |
dfrapPerfSnaPerDlciTxPeriphThe number of SNA Periph bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.13.1.8 |
dfrapPerfSnaPerDlciRxAppnThe number of SNA Appn bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.13.1.9 |
dfrapPerfSnaPerDlciTxAppnThe number of SNA Appn bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.13.1.10 |
dfrapPerfSnaPerDlciRxNetbiosThe number of SNA Netbios bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.13.1.11 |
dfrapPerfSnaPerDlciTxNetbiosThe number of SNA Netbios bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.13.1.12 |
dfrapPerfSnaPerDlciRxOtherThe 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.6.5.4.13.1.13 |
dfrapPerfSnaPerDlciTxOtherThe 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.6.5.4.13.1.14 |
dfrapPerfSnaTotalTableShort Term Statistics on the SNA
protocol across all DLCIs. SEQUENCE OF DfrapPerfSnaTotalEntry .1.3.6.1.4.1.485.6.5.4.14 |
dfrapPerfSnaTotalEntryThe SNA Short Term Statistics across all DLCIs. DfrapPerfSnaTotalEntry .1.3.6.1.4.1.485.6.5.4.14.1 |
dfrapPerfSnaTotalIntervalThe 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.6.5.4.14.1.1 |
dfrapPerfSnaTotalRxTotalThe total number of SNA bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.14.1.3 |
dfrapPerfSnaTotalTxTotalThe total number of SNA bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.14.1.4 |
dfrapPerfSnaTotalRxSubareaThe number of SNA Subarea bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.14.1.5 |
dfrapPerfSnaTotalTxSubareaThe number of SNA Subarea bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.14.1.6 |
dfrapPerfSnaTotalRxPeriphThe number of SNA Periph bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.14.1.7 |
dfrapPerfSnaTotalTxPeriphThe number of SNA Periph bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.14.1.8 |
dfrapPerfSnaTotalRxAppnThe number of SNA Appn bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.14.1.9 |
dfrapPerfSnaTotalTxAppnThe number of SNA Appn bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.14.1.10 |
dfrapPerfSnaTotalRxNetbiosThe number of SNA Netbios bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.14.1.11 |
dfrapPerfSnaTotalTxNetbiosThe number of SNA Netbios bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.14.1.12 |
dfrapPerfSnaTotalRxOtherThe 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.6.5.4.14.1.13 |
dfrapPerfSnaTotalTxOtherThe 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.6.5.4.14.1.14 |
dfrapPerfArpPerDlciTableShort Term Statistics on the ARP
protocol for each DLCI. SEQUENCE OF DfrapPerfArpPerDlciEntry .1.3.6.1.4.1.485.6.5.4.15 |
dfrapPerfArpPerDlciEntryThe ARP Short Term Statistics for a particular DLCI. DfrapPerfArpPerDlciEntry .1.3.6.1.4.1.485.6.5.4.15.1 |
dfrapPerfArpPerDlciIntervalThe 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.6.5.4.15.1.1 |
dfrapPerfArpPerDlciValueThe DLCI value in which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.6.5.4.15.1.2 |
dfrapPerfArpPerDlciRxTotalThe total number of ARP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.15.1.3 |
dfrapPerfArpPerDlciTxTotalThe total number of ARP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.15.1.4 |
dfrapPerfArpPerDlciRxArpReqThe number of ARP request bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.15.1.5 |
dfrapPerfArpPerDlciTxArpReqThe number of ARP request bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.15.1.6 |
dfrapPerfArpPerDlciRxArpRepThe number of ARP reply bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.15.1.7 |
dfrapPerfArpPerDlciTxArpRepThe number of ARP reply bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.15.1.8 |
dfrapPerfArpPerDlciRxRarpReqThe number of RARP request bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.15.1.9 |
dfrapPerfArpPerDlciTxRarpReqThe number of RARP request bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.15.1.10 |
dfrapPerfArpPerDlciRxRarpRepThe number of RARP reply bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.15.1.11 |
dfrapPerfArpPerDlciTxRarpRepThe number of RARP reply bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.15.1.12 |
dfrapPerfArpPerDlciRxInarpReqThe number of INARP request bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.15.1.13 |
dfrapPerfArpPerDlciTxInarpReqThe number of INARP request bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.15.1.14 |
dfrapPerfArpPerDlciRxInarpRepThe number of INARP reply bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.15.1.15 |
dfrapPerfArpPerDlciTxInarpRepThe number of INARP reply bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.15.1.16 |
dfrapPerfArpPerDlciRxOtherThe 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.6.5.4.15.1.17 |
dfrapPerfArpPerDlciTxOtherThe 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.6.5.4.15.1.18 |
dfrapPerfArpTotalTableShort Term Statistics on the ARP
protocol across all DLCIs. SEQUENCE OF DfrapPerfArpTotalEntry .1.3.6.1.4.1.485.6.5.4.16 |
dfrapPerfArpTotalEntryThe ARP Short Term Statistics across all DLCIs. DfrapPerfArpTotalEntry .1.3.6.1.4.1.485.6.5.4.16.1 |
dfrapPerfArpTotalIntervalThe 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.6.5.4.16.1.1 |
dfrapPerfArpTotalRxTotalThe total number of ARP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.16.1.3 |
dfrapPerfArpTotalTxTotalThe total number of ARP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.16.1.4 |
dfrapPerfArpTotalRxArpReqThe number of ARP request bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.16.1.5 |
dfrapPerfArpTotalTxArpReqThe number of ARP request bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.16.1.6 |
dfrapPerfArpTotalRxArpRepThe number of ARP reply bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.16.1.7 |
dfrapPerfArpTotalTxArpRepThe number of ARP reply bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.16.1.8 |
dfrapPerfArpTotalRxRarpReqThe number of RARP request bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.16.1.9 |
dfrapPerfArpTotalTxRarpReqThe number of RARP request bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.16.1.10 |
dfrapPerfArpTotalRxRarpRepThe number of RARP reply bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.16.1.11 |
dfrapPerfArpTotalTxRarpRepThe number of RARP reply bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.16.1.12 |
dfrapPerfArpTotalRxInarpReqThe number of INARP request bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.16.1.13 |
dfrapPerfArpTotalTxInarpReqThe number of INARP request bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.16.1.14 |
dfrapPerfArpTotalRxInarpRepThe number of INARP reply bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.16.1.15 |
dfrapPerfArpTotalTxInarpRepThe number of INARP reply bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.6.5.4.16.1.16 |
dfrapPerfArpTotalRxOtherThe 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.6.5.4.16.1.17 |
dfrapPerfArpTotalTxOtherThe 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.6.5.4.16.1.18 |
dfrapPerfLmiPerDlciTableShort Term Statistics on LMI protocol for each DLCI. SEQUENCE OF DfrapPerfLmiPerDlciEntry .1.3.6.1.4.1.485.6.5.4.17 |
dfrapPerfLmiPerDlciEntryThe LMI Short Term Statistics for a particular DLCI. DfrapPerfLmiPerDlciEntry .1.3.6.1.4.1.485.6.5.4.17.1 |
dfrapPerfLmiPerDlciIntervalThe 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.6.5.4.17.1.1 |
dfrapPerfLmiPerDlciValueThe DLCI value with which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.6.5.4.17.1.2 |
dfrapPerfLmiPerDlciRxTotalByteCntThe total number of received LMI bytes
counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.17.1.3 |
dfrapPerfLmiPerDlciTxTotalByteCntThe total number of transmitted LMI bytes
counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.17.1.4 |
dfrapPerfLmiPerDlciRxLivoEnqByteCntThe number of bytes received in Link Integrity
Verification Only (LIVO) enquiries on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.17.1.5 |
dfrapPerfLmiPerDlciTxLivoEnqByteCntThe number of bytes transmitted in Link Integrity
Verification Only (LIVO) enquiries on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.17.1.6 |
dfrapPerfLmiPerDlciRxLivoStatByteCntThe number of bytes received in Link Integrity
Verification Only (LIVO) statuses on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.17.1.7 |
dfrapPerfLmiPerDlciTxLivoStatByteCntThe number of bytes transmitted in Link Integrity
Verification Only (LIVO) statuses on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.17.1.8 |
dfrapPerfLmiPerDlciRxFullEnqByteCntThe number of bytes received in
Full Status enquiries on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.17.1.9 |
dfrapPerfLmiPerDlciTxFullEnqByteCntThe number of bytes transmitted in
Full Status enquiries on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.17.1.10 |
dfrapPerfLmiPerDlciRxFullStatByteCntThe number of bytes received in
Full Status messages on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.17.1.11 |
dfrapPerfLmiPerDlciTxFullStatByteCntThe number of bytes transmitted in
Full Status messages on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.17.1.12 |
dfrapPerfLmiPerDlciRxOtherByteCntThe 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.6.5.4.17.1.13 |
dfrapPerfLmiPerDlciTxOtherByteCntThe 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.6.5.4.17.1.14 |
dfrapPerfLmiTotalTableShort Term Statistics on LMI protocol across all DLCIs. SEQUENCE OF DfrapPerfLmiTotalEntry .1.3.6.1.4.1.485.6.5.4.18 |
dfrapPerfLmiTotalEntryThe LMI Short Term Statistics across all DLCIs. DfrapPerfLmiTotalEntry .1.3.6.1.4.1.485.6.5.4.18.1 |
dfrapPerfLmiTotalIntervalThe 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.6.5.4.18.1.1 |
dfrapPerfLmiTotalDlciValueOBSOLETE.ro INTEGER .1.3.6.1.4.1.485.6.5.4.18.1.2 |
dfrapPerfLmiTotalRxTotalByteCntThe total number of received LMI bytes
counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.18.1.3 |
dfrapPerfLmiTotalTxTotalByteCntThe total number of transmitted LMI bytes
counted on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.18.1.4 |
dfrapPerfLmiTotalRxLivoEnqByteCntThe number of bytes received in Link Integrity
Verification Only (LIVO) enquiries on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.18.1.5 |
dfrapPerfLmiTotalTxLivoEnqByteCntThe number of bytes transmitted in Link Integrity
Verification Only (LIVO) enquiries on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.18.1.6 |
dfrapPerfLmiTotalRxLivoStatByteCntThe number of bytes received in Link Integrity
Verification Only (LIVO) statuses on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.18.1.7 |
dfrapPerfLmiTotalTxLivoStatByteCntThe number of bytes transmitted in Link Integrity
Verification Only (LIVO) statuses on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.18.1.8 |
dfrapPerfLmiTotalRxFullEnqByteCntThe number of bytes received in
Full Status enquiries on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.18.1.9 |
dfrapPerfLmiTotalTxFullEnqByteCntThe number of bytes transmitted in
Full Status enquiries on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.18.1.10 |
dfrapPerfLmiTotalRxFullStatByteCntThe number of bytes received in
Full Status messages on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.18.1.11 |
dfrapPerfLmiTotalTxFullStatByteCntThe number of bytes transmitted in
Full Status messages on this DLCI.ro Counter .1.3.6.1.4.1.485.6.5.4.18.1.12 |
dfrapPerfLmiTotalRxOtherByteCntThe 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.6.5.4.18.1.13 |
dfrapPerfLmiTotalTxOtherByteCntThe 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.6.5.4.18.1.14 |
dfrapPerfNetworkLongTerm OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.5.5 |
dfrapPerfNetwLongTermTableLong 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).
(CfgFrPerfTimersLTInterval). SEQUENCE OF DfrapPerfNetwLongTermEntry .1.3.6.1.4.1.485.6.5.5.1 |
dfrapPerfNetwLongTermEntryThe Long Term Statistic for a particular DLCI,
protocol and interval. DfrapPerfNetwLongTermEntry .1.3.6.1.4.1.485.6.5.5.1.1 |
dfrapPerfNetwLongTermDlciThe DLCI monitored for the statistics. The Long
Term DLCI filter must first be configured
(CfgFrPerfLTDlciFilterEntry).ro INTEGER .1.3.6.1.4.1.485.6.5.5.1.1.1 |
dfrapPerfNetwLongTermProtocolThe type of protocol monitored for the statistics.ro Enumeration .1.3.6.1.4.1.485.6.5.5.1.1.2 |
dfrapPerfNetwLongTermIntervalThe 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.6.5.5.1.1.3 |
dfrapPerfNetwLongTermValueThe statistic collected for the given DLCI and protocol
and within the given time interval.ro Counter .1.3.6.1.4.1.485.6.5.5.1.1.4 |
dfrapPerfNetwLongTermAltTableThis 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 DfrapPerfNetwLongTermAltEntry .1.3.6.1.4.1.485.6.5.5.2 |
dfrapPerfNetwLongTermAltEntryThe Long Term Statistic for a particular
DLCI and protocol. DfrapPerfNetwLongTermAltEntry .1.3.6.1.4.1.485.6.5.5.2.1 |
dfrapPerfNetwLongTermAltDlciThe DLCI monitored for the statistics.ro INTEGER .1.3.6.1.4.1.485.6.5.5.2.1.1 |
dfrapPerfNetwLongTermAltProtocolThe protocol monitored for the statistics.ro Enumeration .1.3.6.1.4.1.485.6.5.5.2.1.2 |
dfrapPerfNetwLongTermAltArrayThe statistic collected for the given DLCI and protocol.ro OCTET STRING .1.3.6.1.4.1.485.6.5.5.2.1.3 |
dfrapPerfNetworkLongTermCommands OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.5.5.3 |
dfrapPerfNetworkLongTermCmdClearAllows 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.6.5.5.3.1 |
dfrapPerfCirPercentUtilization OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.5.6 |
dfrapPerfCirPercentUtilizationTableShort 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 DfrapPerfCirPercentUtilizationEntry .1.3.6.1.4.1.485.6.5.6.1 |
dfrapPerfCirPercentUtilizationEntryThe CIR Percentage Statistics for a particular DLCI.
These calculations are done at the completion of each
Short Term interval. DfrapPerfCirPercentUtilizationEntry .1.3.6.1.4.1.485.6.5.6.1.1 |
dfrapPerfCirPercentUtilizationIntervalThe 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.6.5.6.1.1.1 |
dfrapPerfCirPercentUtilizationDlciValueThe DLCI value with which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.6.5.6.1.1.2 |
dfrapPerfCirRxPercentUtilizationRange1The number of received bytes counted on this DLCI
during intervals where the percentage of
CIR was in range 1 (0% of CIR).ro INTEGER .1.3.6.1.4.1.485.6.5.6.1.1.21 |
dfrapPerfCirRxPercentUtilizationRange2The number of received bytes counted on this DLCI
during intervals where the percentage of
CIR was in range 2 (1-10% of CIR).ro INTEGER .1.3.6.1.4.1.485.6.5.6.1.1.22 |
dfrapPerfCirRxPercentUtilizationRange3The number of received bytes counted on this DLCI
during intervals where the percentage of
CIR was in range 3 (11-20% of CIR).ro INTEGER .1.3.6.1.4.1.485.6.5.6.1.1.23 |
dfrapPerfCirRxPercentUtilizationRange4The number of received bytes counted on this DLCI
during intervals where the percentage of
CIR was in range 4 (21-50% of CIR).ro INTEGER .1.3.6.1.4.1.485.6.5.6.1.1.24 |
dfrapPerfCirRxPercentUtilizationRange5The number of received bytes counted on this DLCI
during intervals where the percentage of
CIR was in range 5 (51-80% of CIR).ro INTEGER .1.3.6.1.4.1.485.6.5.6.1.1.25 |
dfrapPerfCirRxPercentUtilizationRange6The number of received bytes counted on this DLCI
during intervals where the percentage of
CIR was in range 6 (81-100% of CIR).ro INTEGER .1.3.6.1.4.1.485.6.5.6.1.1.26 |
dfrapPerfCirRxPercentUtilizationRange7The number of received bytes counted on this DLCI
during intervals where the percentage of
CIR was in range 7 (101-150% of CIR).ro INTEGER .1.3.6.1.4.1.485.6.5.6.1.1.27 |
dfrapPerfCirRxPercentUtilizationRange8The number of received bytes counted on this DLCI
during intervals where the percentage of
CIR was in range 8 (> 150% of CIR).ro INTEGER .1.3.6.1.4.1.485.6.5.6.1.1.28 |
dfrapPerfCirTxPercentUtilizationRange1The number of transmitted bytes counted on this DLCI
during intervals where the percentage of
CIR was in range 1 (0% of CIR).ro INTEGER .1.3.6.1.4.1.485.6.5.6.1.1.41 |
dfrapPerfCirTxPercentUtilizationRange2The number of transmitted bytes counted on this DLCI
during intervals where the percentage of
CIR was in range 2 (1-10% of CIR).ro INTEGER .1.3.6.1.4.1.485.6.5.6.1.1.42 |
dfrapPerfCirTxPercentUtilizationRange3The number of transmitted bytes counted on this DLCI
during intervals where the percentage of
CIR was in range 3 (11-20% of CIR).ro INTEGER .1.3.6.1.4.1.485.6.5.6.1.1.43 |
dfrapPerfCirTxPercentUtilizationRange4The number of transmitted bytes counted on this DLCI
during intervals where the percentage of
CIR was in range 4 (21-50% of CIR).ro INTEGER .1.3.6.1.4.1.485.6.5.6.1.1.44 |
dfrapPerfCirTxPercentUtilizationRange5The number of transmitted bytes counted on this DLCI
during intervals where the percentage of
CIR was in range 5 (51-80% of CIR).ro INTEGER .1.3.6.1.4.1.485.6.5.6.1.1.45 |
dfrapPerfCirTxPercentUtilizationRange6The number of transmitted bytes counted on this DLCI
during intervals where the percentage of
CIR was in range 6 (81-100% o0f CIR).ro INTEGER .1.3.6.1.4.1.485.6.5.6.1.1.46 |
dfrapPerfCirTxPercentUtilizationRange7The number of transmitted bytes counted on this DLCI
during intervals where the percentage of
CIR was in range 7 (101-150% of CIR).ro INTEGER .1.3.6.1.4.1.485.6.5.6.1.1.47 |
dfrapPerfCirTxPercentUtilizationRange8The number of transmitted bytes counted on this DLCI
during intervals where the percentage of
CIR was in range 8 (> 150% of CIR).ro INTEGER .1.3.6.1.4.1.485.6.5.6.1.1.48 |
dfrapPerfCurrentPerDlciUtilizationTableThe 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 DfrapPerfCurrentPerDlciUtilizationEntry .1.3.6.1.4.1.485.6.5.6.2 |
dfrapPerfCurrentPerDlciUtilizationEntryThe utilization statistics for a particular DLCI. DfrapPerfCurrentPerDlciUtilizationEntry .1.3.6.1.4.1.485.6.5.6.2.1 |
dfrapPerfCurrentPerDlciUtilizationDlciValueThe DLCI value with which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.6.5.6.2.1.1 |
dfrapPerfCurrentPerDlciRxUtilizationThe receive direction utilization as a
percentage of CIR.ro INTEGER .1.3.6.1.4.1.485.6.5.6.2.1.2 |
dfrapPerfCurrentPerDlciTxUtilizationThe transmit direction utilization as a
percentage of CIR.ro INTEGER .1.3.6.1.4.1.485.6.5.6.2.1.3 |
dfrapPerfCurrentPerDlciAggregateUtilizationThe aggregate utilization, the average
of the receive and transmit utilization
as a percentage of CIR.ro INTEGER .1.3.6.1.4.1.485.6.5.6.2.1.4 |
dfrapPerfCurrentUnitUtilization OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.5.6.3 |
dfrapPerfCurrentDteUtilizationThe DTE interface utilization as a
percentage of line rate.ro INTEGER .1.3.6.1.4.1.485.6.5.6.3.2 |
dfrapPerfCurrentWanUtilizationThe WAN interface utilization as a
percentage of line rate.ro INTEGER .1.3.6.1.4.1.485.6.5.6.3.3 |
dfrapPerfCurrentAggregateUtilizationThe 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.6.5.6.3.4 |
dfrapAlarmTypeThe alarm type of the most recent TRAP generated.ro Enumeration .1.3.6.1.4.1.485.6.6 |
dfrapDLCINumThe DLCI number for the most recent DLCI TRAP generated.ro INTEGER .1.3.6.1.4.1.485.6.7 |
dfrapInterfaceThe interface most recently reported in a TRAP.ro Enumeration .1.3.6.1.4.1.485.6.8 |
dfrapIpAddressThe IP address most recently reported in a TRAP.ro IpAddress .1.3.6.1.4.1.485.6.9 |
dfrapEventTrapLog OBJECT IDENTIFIER .1.3.6.1.4.1.485.6.10 |
dfrapEventTrapLogTableThis table contains the Event/Trap log. The entries are
indexed by sequence number. SEQUENCE OF DFRAPEventTrapLogEntry .1.3.6.1.4.1.485.6.10.1 |
dfrapEventTrapLogEntryThe event record for a particular event. DFRAPEventTrapLogEntry .1.3.6.1.4.1.485.6.10.1.1 |
dfrapEventTrapLogSeqNumThe sequence number associated with an event record.ro INTEGER .1.3.6.1.4.1.485.6.10.1.1.1 |
dfrapEventTrapLogGenericEventThe SNMP generic trap or event number.ro INTEGER .1.3.6.1.4.1.485.6.10.1.1.2 |
dfrapEventTrapLogSpecificEventThe SNMP specific trap or event sub-identifier number.ro INTEGER .1.3.6.1.4.1.485.6.10.1.1.3 |
dfrapEventTrapLogTimeStampThe SNMP trap timestamp.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.485.6.10.1.1.4 |
dfrapEventTrapLogVarBind1Variable Binding 1 for this SNMP Trap event.ro INTEGER .1.3.6.1.4.1.485.6.10.1.1.5 |
dfrapEventTrapLogVarBind2Variable Binding 2 for this SNMP Trap event.ro INTEGER .1.3.6.1.4.1.485.6.10.1.1.6 |
dfrapEventTrapLogVarBind3Variable Binding 3 for this SNMP Trap event.ro INTEGER .1.3.6.1.4.1.485.6.10.1.1.7 |
dfrapEventLogAltTableThis 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 DFRAPEventLogAltEntry .1.3.6.1.4.1.485.6.10.2 |
dfrapEventLogAltEntryThe Event/Trap Log for a particular sequence number. DFRAPEventLogAltEntry .1.3.6.1.4.1.485.6.10.2.1 |
dfrapEventLogAltSeqNumThe Sequence Number monitored for the Event Logro INTEGER .1.3.6.1.4.1.485.6.10.2.1.1 |
dfrapEventLogAltArrayThe Event / Trap log for the given sequence number.ro OCTET STRING .1.3.6.1.4.1.485.6.10.2.1.2 |
dfrapEventLogCurrentSeqNumThe current index into the Event Log Table.ro INTEGER .1.3.6.1.4.1.485.6.10.3 |
dfrapEventLogFreezeThis 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.6.10.4 |
dfrapEventLogClearThis clears the Event/Trap Log.rw Enumeration .1.3.6.1.4.1.485.6.10.5 |
dfrapPercentUtilizationThe percent utilization for a DLCI most recently
reported in a TRAP.ro INTEGER .1.3.6.1.4.1.485.6.11 |
dfrapUtilizationThresholdThe percent utilization threshold for a DLCI most
recently reported in a TRAP.ro INTEGER .1.3.6.1.4.1.485.6.12 |
dfrapCfgLockIpAddressThe IP address of the management station locking
the configuration most recently reported in a TRAP.ro INTEGER .1.3.6.1.4.1.485.6.13 |