SFRAP-MIB
AI MIB Summary
Standard SNMP MIB module defining data structures for SFRAP-MIB.
852
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
852 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 |
sfrap OBJECT IDENTIFIER .1.3.6.1.4.1.485.7 |
sfrapTrapA sfrapTrap trap signifies that the
sending node had its `sfrapAlarmType`
variable modified. TRAP-TYPE .1.3.6.1.4.1.485.7.0.0 |
sfrapBadConfigTrapUnit 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.7.0.1 |
sfrapLocalConfigTrapUnit configuration has been updated locally
(console port or front panel keypad) or
remotely (telnet). TRAP-TYPE .1.3.6.1.4.1.485.7.0.2 |
sfrapLocalUnitLoopbackEnabledTrapUnit is in a bidirectional unit loopback. Data
is received from either interface, processed,
and transmitted back towards the same interface.
When configured for Frame Relay operation the unit
will preserve the LMI path during this loopback.
In Frame Relay mode, only valid frames are looped
back (pseudorandom test patterns will be dropped). TRAP-TYPE .1.3.6.1.4.1.485.7.0.14 |
sfrapLocalUnitLoopbackDisabledTrapBidirectional unit loopback path is removed. TRAP-TYPE .1.3.6.1.4.1.485.7.0.15 |
sfrapLocalUnitLoopbackFailedTrapBidirectional 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.7.0.16 |
sfrapLocalToDteLoopbackEnabledTrapUnit is in a bidirectional TO-DTE loopback. All
data received at the TO-DTE interface is looped
back regardless of format or content (line
loopback). When configured for Frame Relay
operation the unit will not preserve the LMI
path during this loopback. Data received from
the TO-DCE is processed and transmitted back out
the TO-DCE. In Frame Relay mode, on the TO-DCE
interface, only valid frames are looped back
(pseudorandom test patterns will be dropped). TRAP-TYPE .1.3.6.1.4.1.485.7.0.17 |
sfrapLocalToDteLoopbackDisabledTrapBidirectional TO-DTE loopback path is removed. TRAP-TYPE .1.3.6.1.4.1.485.7.0.18 |
sfrapLocalToDteLoopbackFailedTrapBidirectional TO-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.7.0.19 |
sfrapDLCIActiveTrapUnit is reporting this DLCI as active and
provisioned. An active DLCI is one that is
explictly declared ACTIVE in an LMI Full
Status Response (typically coming from a
frame relay switch). TRAP-TYPE .1.3.6.1.4.1.485.7.0.47 |
sfrapDLCIInactiveTrapUnit is reporting this DLCI as inactive. An
inactive DLCI is determined inactive one of two
ways: it is either explictly declared inactive
in an LMI Full Status Response (typically coming
from a frame relay switch) or a Full Status
Response is not seen causing a Full Status Timer
expiry. Having the unit's full status timer too
low could result in the unit falsely declaring DLCIs
inactive (then active again). This does not interfere
with any data activity on the DLCI but could result
in excessive traps. TRAP-TYPE .1.3.6.1.4.1.485.7.0.48 |
sfrapDLCITDThresholdTrapVNIP 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.7.0.49 |
sfrapLmiSourcingChangePassthruTrapUnit 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.7.0.50 |
sfrapLmiSourcingChangeUserToDteTrapUnit is acting as a source of LMI Status Requests
(Link Integrity Verification, Keep Alive). If this
state persists then the equipment attached to the
TO-DTE interface is configured as a Frame Relay DCE
but a companion Frame Relay DTE device is not seen
out the TO-DCE. 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.7.0.51 |
sfrapLmiSourcingChangeNetToDteTrapUnit is acting as a source of LMI Status Responses
(Link Intergrity Verification, Keep Alive). If this
state persists then the equpiment attached to the
TO-DTE interface is configured as a Frame Relay DTE
but a companion Frame Relay DCE device is not seen
out the TO-DCE. 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.7.0.52 |
sfrapLmiSourcingChangeUserToDceTrapUnit is acting as a source of LMI Status Requests
(Link Integrity Verification, Keep Alive). If this
state persists then the equipment attached to the
TO-DCE interface is configured as a Frame Relay DCE
but a companion Frame Relay DTE device is not seen
out the TO-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.7.0.53 |
sfrapLmiSourcingChangeNetToDceTrapUnit is acting as a source of LMI Status Responses
(Link Integrity Verification, Keep Alive). If this
state persists then the equipment attached to the
TO-DCE interface is configured as a Frame Relay DTE
but a companion Frame Relay DCE device is not seen
out the TO-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.7.0.54 |
sfrapDteSignalRtsOnTrapUnit's DTE Request to Send (RTS) interface control
signal is now active (on). This signal is presented
by the external DTE device. Unit may be configured
to ignore the state of this signal or to require
it for data transmission. TRAP-TYPE .1.3.6.1.4.1.485.7.0.55 |
sfrapDteSignalRtsOffTrapUnit's DTE Request to Send (RTS) interface control
signal is now inactive (off). This signal is presented
by the external DTE device. Unit may be configured
to ignore the state of this signal or to require it
for data transmission. TRAP-TYPE .1.3.6.1.4.1.485.7.0.56 |
sfrapDteSignalDtrOnTrapUnit's DTE Data Terminal Ready (DTR) interface control
signal is now active (on). This signal is presented by the
external DTE device. The unit may be configured to ignore
the state of this signal or to require it for data transmission. TRAP-TYPE .1.3.6.1.4.1.485.7.0.57 |
sfrapDteSignalDtrOffTrapUnit's DTE Data Terminal Ready (DTR) interface control
signal is now inactive (off). This signal is presented by
the external DTE device. Unit may be configured to ignore
the state of this signal or to require it for data
transmission. TRAP-TYPE .1.3.6.1.4.1.485.7.0.58 |
sfrapNonIncrLmiSeqNumToDteTrapUnit has detected a non-incrementing LMI sequence number
from the TO-DTE. A Status Enquiry or Status Response message
has been seen at the TO-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 TO-DTE interface. TRAP-TYPE .1.3.6.1.4.1.485.7.0.59 |
sfrapNonIncrLmiSeqNumToDceTrapUnit has detected a non-incrementing LMI sequence number
from the TO-DCE. A Status Enquiry or Status Response message
has been seen at the TO-DCE 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 TO-DCE interface. TRAP-TYPE .1.3.6.1.4.1.485.7.0.60 |
sfrapLmiSeqNumMismatchToDteTrapUnit has detetcted an LMI sequence number mismatch from
the TO-DTE. A Status Enquiry or Status Response message has
been seen at the TO-DTE interface. The Link Inetgrity information
element's Receive Sequence Number was not the most recent
Send Sequence number sent from the TO-DCE interface. TRAP-TYPE .1.3.6.1.4.1.485.7.0.61 |
sfrapLmiSeqNumMismatchToDceTrapUnit has detetcted an LMI sequence number mismatch from
the TO-DCE. A Status Enquiry or Status Response message has
been seen at the TO-DCE interface. The Link Inetgrity information
element's Receive Sequence Number was not the most recent
Send Sequence number sent from the TO-DTE interface. TRAP-TYPE .1.3.6.1.4.1.485.7.0.62 |
sfrapTrapMutingActiveTrap generation is muted. TRAP-TYPE .1.3.6.1.4.1.485.7.0.75 |
sfrapTrapMutingInactiveTrap generation is re-enabled (muting disabled). TRAP-TYPE .1.3.6.1.4.1.485.7.0.76 |
sfrapLowSpeedExceededTrapThe bandwidth has exceeded the maximum bandwidth
for the Low Speed SFRAP. Throttle your network
bandwidth. TRAP-TYPE .1.3.6.1.4.1.485.7.0.80 |
sfrapLowSpeedResumedTrapThe bandwidth has is now under the maximum bandwidth
for the Low Speed SFRAP. Frame Relay processing
will resume. TRAP-TYPE .1.3.6.1.4.1.485.7.0.81 |
sfrapOpModeCutThruEnabledTrapThe Unit has been put into Cut Through mode via the
diagnostic. The unit is now operating as if it were in
Tap mode. The processor is NOT transmitting data. TRAP-TYPE .1.3.6.1.4.1.485.7.0.82 |
sfrapOpModeCutThruDisabledTrapThe Unit has now resumed normal operation based upon the
configured operation mode,Tap or Inband. TRAP-TYPE .1.3.6.1.4.1.485.7.0.83 |
sfrapLocalDte2LoopbackEnabledTrapLocal TO-DCE loopback enabled. TRAP-TYPE .1.3.6.1.4.1.485.7.0.84 |
sfrapLocalDte2LoopbackDisabledTrapLocal TO-DCE loopback disabled. TRAP-TYPE .1.3.6.1.4.1.485.7.0.85 |
sfrapLocalDte2LoopbackFailedTrapUnable to do a local TO-DCE loopback. TRAP-TYPE .1.3.6.1.4.1.485.7.0.86 |
sfrapVloopUpA 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.7.0.90 |
sfrapVloopDownA 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.7.0.91 |
sfrapVloopUpViaRemoteA 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.7.0.92 |
sfrapVloopDownViaRemoteA 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.7.0.93 |
sfrapVloopRequestFailedThe request for a PVC loopback (VLOOP) has been rejected
or did not complete. TRAP-TYPE .1.3.6.1.4.1.485.7.0.94 |
sfrapVbertStartedA 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.7.0.95 |
sfrapVbertStoppedA 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.7.0.96 |
sfrapVbertRequestFailedThe request for a PVC BERT (VBERT) on this DLCI
on this interface has been rejected. TRAP-TYPE .1.3.6.1.4.1.485.7.0.97 |
sfrapDteSignalControlOnTrapUnit's X.21 Control (C) DTE control signal
is now active (on). This signal is presented
by the external DTE device. TRAP-TYPE .1.3.6.1.4.1.485.7.0.100 |
sfrapDteSignalControlOffTrapUnit's X.21 Control (C) DTE control signal
is now inactive (off). This signal is presented
by the external DTE device. TRAP-TYPE .1.3.6.1.4.1.485.7.0.101 |
sfrapDteSignalIndicateOnTrapUnit's X.21 Indicate (I) DTE control signal
is now active (on). This signal is presented
by the external DTE device. TRAP-TYPE .1.3.6.1.4.1.485.7.0.102 |
sfrapDteSignalIndicateOffTrapUnit's X.21 Indicate (I) DTE control signal
is now inactive (off). This signal is presented
by the external DTE device. TRAP-TYPE .1.3.6.1.4.1.485.7.0.103 |
sfrapPvcRxUtilizationExceededTrapPercent 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.7.0.138 |
sfrapPvcTxUtilizationExceededTrapPercent 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.7.0.139 |
sfrapPvcRxUtilizationClearedTrapPercent 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.7.0.140 |
sfrapPvcTxUtilizationClearedTrapPercent 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.7.0.141 |
sfrapConfigInstallSuccessThe configuration install process has successfully
completed. TRAP-TYPE .1.3.6.1.4.1.485.7.0.142 |
sfrapTftpRequestedTrapUnit 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.7.0.257 |
sfrapTftpTransferringTrapUnit 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.7.0.258 |
sfrapTftpProgrammingTrapUnit 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.7.0.259 |
sfrapTftpAbortedTrapUnit'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.7.0.260 |
sfrapTftpSuccessTrapUnit'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.7.0.261 |
sfrapTftpHostUnreachableTrapUnit could not establish a TFTP session with the
designated server. Verify that the correct TFTP
ip address, TFTP DLCI and TFTP interface are
configured on the unit and also verify the TFTP
server confguration. TRAP-TYPE .1.3.6.1.4.1.485.7.0.262 |
sfrapTftpNoFileTrapUnit 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.7.0.263 |
sfrapTftpInvalidFileTrapUnit 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.7.0.264 |
sfrapTftpCorruptFileTrapUnit 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.7.0.265 |
sfrapSystem OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.1 |
sfrapSysTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.1.1 |
sfrapSysTypeA textual description of the system model identifier.
for example: SYNC-sfrapro DisplayString .1.3.6.1.4.1.485.7.1.1.1 |
sfrapSysSoftRevDisplays the Software Revision of the application code
installed in this node.ro DisplayString .1.3.6.1.4.1.485.7.1.1.2 |
sfrapSysHardRevDisplays the Hardware Revision of the node.ro DisplayString .1.3.6.1.4.1.485.7.1.1.3 |
sfrapSysNumToDteInstalledThe number of channels (TO-DTE) that are
installed.ro INTEGER .1.3.6.1.4.1.485.7.1.1.5 |
sfrapSysNumMaintInstalledThe number of Maintenance ports that are
installed.ro INTEGER .1.3.6.1.4.1.485.7.1.1.6 |
sfrapSysNameThe 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.7.1.1.7 |
sfrapSysSerialNoThe serial number of the board.ro DisplayString .1.3.6.1.4.1.485.7.1.1.8 |
sfrapSysResetNodeCommand to reset the node. NODE WILL BE OFF-LINE AND
USER DATA WILL BE INTERRUPTED FOR APPROXIMATELY 15
SECONDS.rw Enumeration .1.3.6.1.4.1.485.7.1.1.9 |
sfrapSysAmtMemoryInstalledThe amount of memory (RAM) installed (in megabytes).ro INTEGER .1.3.6.1.4.1.485.7.1.1.10 |
sfrapSysLocationThe 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.7.1.1.12 |
sfrapSysContactThe 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.7.1.1.13 |
sfrapSysNumToDceInstalledThe number of channels (TO-DCE) that are
installed.ro INTEGER .1.3.6.1.4.1.485.7.1.1.14 |
sfrapSysPromptConfigurable 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.7.1.1.15 |
sfrapSysBootRevDisplays the Software Revision of the Bootstrapping
code installed in this node.ro DisplayString .1.3.6.1.4.1.485.7.1.1.16 |
sfrapSysFeatureTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.1.2 |
sfrapSysSLIPSupportedShows 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.7.1.2.1 |
sfrapSysPPPSupportedShows 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.7.1.2.2 |
sfrapSysRDOSupportedShows whether the unit has Remote Dial Out capability.ro DisplayString .1.3.6.1.4.1.485.7.1.2.3 |
sfrapSysETHSupportedShows whether the unit has Ethernet capability.ro DisplayString .1.3.6.1.4.1.485.7.1.2.4 |
sfrapSysTKRSupportedShows whether the unit has Token Ring capability.ro DisplayString .1.3.6.1.4.1.485.7.1.2.5 |
sfrapSysExtTimSupportedShows 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.7.1.2.6 |
sfrapSysBRISupportedShows whether the unit has BRI (ISDN Basic Rate) capability.ro DisplayString .1.3.6.1.4.1.485.7.1.2.7 |
sfrapSysSelDTESupportedShows 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.7.1.2.8 |
sfrapSysMLSupportedShows whether the unit supports MLs
(out-of-band management links).ro DisplayString .1.3.6.1.4.1.485.7.1.2.9 |
sfrapSysNumDlcisSupportedShows 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.7.1.2.10 |
sfrapSysLTFNumDlcisShows how many DLCIs can be specified
in the Long Term Statistics Filter.ro INTEGER .1.3.6.1.4.1.485.7.1.2.11 |
sfrapSysLTFNumProtocolsShows how many protocols can be specified
in the Long Term Statistics Filter.ro INTEGER .1.3.6.1.4.1.485.7.1.2.12 |
sfrapSysNumUserProtocolsShows 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.7.1.2.13 |
sfrapSysNumSnmpMgrsShows how many SNMP managers can be programmed in the
table sfrapCfgSnmpMngrTable. These managers are sent
TRAPs if configured to do so.ro INTEGER .1.3.6.1.4.1.485.7.1.2.14 |
sfrapSysNumDlciNamesShows how many DLCI names can be defined by the user
in the table sfrapCfgFrPerfDlciNamesTable.ro INTEGER .1.3.6.1.4.1.485.7.1.2.15 |
sfrapSysHighSpeedSupportedShows whether the unit is in high speed mode.ro DisplayString .1.3.6.1.4.1.485.7.1.2.16 |
sfrapConfiguration OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.2 |
sfrapCfgMgmtTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.2.1 |
sfrapCfgIpTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.2.1.1 |
sfrapCfgIpMyIPThe IP address for this node. This address will be unique to
the IP network and is required for in-band or out-of-band
ip and SNMP management.rw IpAddress .1.3.6.1.4.1.485.7.2.1.1.1 |
sfrapCfgIpPeerIPThis parameter is not used internally by
the unit. It is intended to identify either
the device directly connected to the SLIP
port or, in Frame Relay applications, the
address of the primary network management
station. This should always be non-zero.rw IpAddress .1.3.6.1.4.1.485.7.2.1.1.2 |
sfrapCfgIpMaskThe 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.7.2.1.1.3 |
sfrapCfgIpMaxMTUThe 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.7.2.1.1.4 |
sfrapCfgIpChannelThis is the method by which IP traffic is being carried.
Either via the SLIP port or a DLCI. This is how
your InBand Managenent scheme is set up.ro Enumeration .1.3.6.1.4.1.485.7.2.1.1.5 |
sfrapCfgIpTelnetEnableEnables/Disables the telnet feature.
Valid values are enable-telnet (1)
and disable-telnet (2).rw Enumeration .1.3.6.1.4.1.485.7.2.1.1.6 |
sfrapCfgIpTelnetAutoLogOutIf 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.7.2.1.1.7 |
sfrapCfgTftpTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.2.1.2 |
sfrapCfgTftpInitiateSetting 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.7.2.1.2.1 |
sfrapCfgTftpIpAddressThe 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.7.2.1.2.2 |
sfrapCfgTftpFilenameThe 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.7.2.1.2.3 |
sfrapCfgTftpInterfaceThe 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.7.2.1.2.4 |
sfrapCfgTftpDlciThe 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.7.2.1.2.5 |
sfrapCfgTftpStatusThe 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.7.2.1.2.6 |
sfrapCfgTftpNumBytesThe number of Bytes from the ROM image that have been
TFTP'd to the unitro Counter .1.3.6.1.4.1.485.7.2.1.2.7 |
sfrapCfgSnmpTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.2.1.3 |
sfrapCfgSnmpFrTrapControls whether or not the Frame Relay DLCI
status change traps are issued. These traps are
sfrapDLCIActiveTrap and sfrapDLCIInactiveTrap.
When sfrapCfgSnmpFrTrap is enabled (1), a trap
will be sent each time an individual DLCI changes
status between active and inactive. When
sfrapCfgSnmpFrTrap is disabled (2), the traps
are not sent.rw Enumeration .1.3.6.1.4.1.485.7.2.1.3.1 |
sfrapCfgSnmpMgrTableThe 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 SfrapCfgSnmpMgrEntry .1.3.6.1.4.1.485.7.2.1.3.2 |
sfrapCfgSnmpMgrEntryThe IP address of a SNMP manager to receive this node's TRAPs. SfrapCfgSnmpMgrEntry .1.3.6.1.4.1.485.7.2.1.3.2.1 |
sfrapCfgSnmpMgrIndexThe index to the list of SNMP managers receiving TRAPs.ro INTEGER .1.3.6.1.4.1.485.7.2.1.3.2.1.1 |
sfrapCfgSnmpMgrIPThe 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.7.2.1.3.2.1.2 |
sfrapCfgSnmpMgrInterfaceThe interface out which the indexed trap manager can be
reached. This entry is required in Piggyback and Bi-directional
in-band managed applications. In Local, Remote and SLIP-based
applications, the interface is known and this parameter is
ignored.
(1) Traps sent out DTE interface for this manager
(2) Traps sent out WAN interface for this manager
(3) Traps sent out SLIP interface (async maint port)
When the node is configured for SLIP, a GET on this MIB
object will return slip-interface(3) and a SET of this MIB
object to slip-interface(3) is allowed but unnecessary.
When the node is not configured for SLIP, this MIB
object can be SET to dte-interface(1) or to dce-interface(2);
slip-interface(3) would be rejected.rw Enumeration .1.3.6.1.4.1.485.7.2.1.3.2.1.3 |
sfrapCfgSnmpMgrDlciThe 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.7.2.1.3.2.1.4 |
sfrapCfgSnmpTrapMutingControls 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.7.2.1.3.3 |
sfrapCfgSnmpUtilTrapEnableEnables 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.7.2.1.3.6 |
sfrapCfgSnmpMgrClearNDeletes the number of entries in the sfrapCfgSnmpMgrTable
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.7.2.1.3.7 |
sfrapCfgCommTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.2.1.4 |
sfrapCfgCommModeThe 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.7.2.1.4.1 |
sfrapCfgCommBaudAsynchronous 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.7.2.1.4.2 |
sfrapCfgCommDataBitsAsynchronous 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.7.2.1.4.3 |
sfrapCfgCommStopBitsAsynchronous 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.7.2.1.4.4 |
sfrapCfgCommParityAsynchronous 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.7.2.1.4.5 |
sfrapCfgCommFlowCtrlFlow Control for this Communication port. Values
are off-flow-control (1).rw Enumeration .1.3.6.1.4.1.485.7.2.1.4.6 |
sfrapCfgFrDLCITable OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.2.1.5 |
sfrapCfgFrDLCIModeIn-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 TO-DTE 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.7.2.1.5.1 |
sfrapCfgFrDLCIValueIf 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.7.2.1.5.2 |
sfrapCfgFrDLCIEncapThis 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.7.2.1.5.3 |
sfrapCfgFrDLCIMgmtDEProvides 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.7.2.1.5.4 |
sfrapCfgAppTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.2.2 |
sfrapCfgAppCircuitIdAlphanumeric 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.7.2.2.2 |
sfrapCfgAppTypeThis 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.7.2.2.3 |
sfrapCfgAppFormatRefer 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.7.2.2.4 |
sfrapCfgAppLpbkTimeoutThe 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.7.2.2.5 |
sfrapCfgAppTxClkmodeThis MIB object is being obsoleted.
The mode in which the TO-DTE and TO-DCE Transmit
clocks are set to. The transmit clocks can either
be normal or inverted. Here are the choices:
1:Normal-timing both TO-DTE & TO-DCE are set normal
2:Invert-TO-DCE the TO-DCE clock is inverted
3:Invert-TO-DTE the TO-DTE clock is inverted
4:Invert-timing both TO-DTE & TO-DCE are inverted.rw Enumeration .1.3.6.1.4.1.485.7.2.2.6 |
sfrapCfgAppTxtimingSerial Transmit Timing mode. Loop-1 (1) uses the clock
returned from the TO-DTE (TT/TCE) to sample tx data, Loop-2 (2)
uses the clock (ST/TC) generated by the node to sample tx
data. Sourced-tt (3) occurs when the unit is configured for Loop-1
and the clock returned from the TO-DTE (TT/TCE)is not present. The unit
will use the (ST/TC) to sample tx data.rw Enumeration .1.3.6.1.4.1.485.7.2.2.7 |
sfrapCfgAppOperationModeDescribes the Operational Mode of the SFRAP:
(1) cut-through used to place unit in cut-thru
(2) inband used to place unit in inband.rw Enumeration .1.3.6.1.4.1.485.7.2.2.8 |
sfrapCfgAppCutthruTimeoutThe amount of time Cuthtru mode may run before
timing out and automatically terminating.
The timeout is in minutes and a value of 0
means no timeout.rw INTEGER .1.3.6.1.4.1.485.7.2.2.9 |
sfrapCfgAppPerfBuffLimitThis value controls the throttling mechanism
used to determine the optimum level of statistical
processing versus manageability of the unit. The
lower the value (1 - 128), the unit becomes more
responsive to management commands during very heavy
utilization at the possible expense of statistical
accuracy. The larger the value (129 - 512), the more
accurate the SFRAP 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.7.2.2.10 |
sfrapCfgDteTableThe table of DTE port configurations. SEQUENCE OF SfrapCfgDteEntry .1.3.6.1.4.1.485.7.2.4 |
sfrapCfgDteEntryA configuration entry for a DTE port. SfrapCfgDteEntry .1.3.6.1.4.1.485.7.2.4.1 |
sfrapCfgDteIntfTypeGets the electrical interface for the DTE port.ro Enumeration .1.3.6.1.4.1.485.7.2.4.1.1 |
sfrapCfgDteTxClockModeThis 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.7.2.4.1.3 |
sfrapCfgDteRxClockModeClock-normal samples data with the rising edge of the
selected rx clock, clock-invert samples data with the
falling edge of the selected rx clock,auto-sense forces
hardware automated clock selection. The rx clock is
selected using CfgDteTiming. This clock invertion is
most useful when loop-2 timing is used. Only in rare
circumstances will clock-invert (2) be used with loop-1
timing. (3)Auto-sense can only be used on the TO-DTE
interface. Auto-sense automatically determines what
kind of clocking to use on the TO-DTE interface. THIS
OBJECT IS OBSOLETE ON THE TO-DCE INTERFACErw Enumeration .1.3.6.1.4.1.485.7.2.4.1.21 |
sfrapCfgDteRtsCControls the reporting of the status of the To-DTE port's
Request to Send (RTS) and Control (C) control signals,
specifically the generation of traps in response to control
signal state changes. If Signal Assumed Active, the unit
will ignore the actual status and always report this signal
Active. If Signal Monitored, the unit will reflect the status
as driven by the To-DTE; as such, Traps will be generated
due to change of state (these may be useful for a network
manager's assessment of interface status.
(1) Signal Assumed Active
(2) Signal Monitoredrw Enumeration .1.3.6.1.4.1.485.7.2.4.1.22 |
sfrapCfgDteIndexSelects which DTE port.ro Enumeration .1.3.6.1.4.1.485.7.2.4.1.99 |
sfrapCfgFrTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.2.5 |
sfrapCfgFrAddrLenDefines the size of the DLCI address field of the Frame Relay
header. This setting must correspond to the Frame Relay
transmission format; typically Two bytes.
(1) two byte DLCI address field
(2) three byte DLCI address field
(3) four byte DLCI address fieldrw Enumeration .1.3.6.1.4.1.485.7.2.5.1 |
sfrapCfgFrCrcModeThis defines the manner in which the unit handles HDLC
protocol errors (crc errors) in a Frame Relay application.
If Discard is selected the unit will respond to an errored
frame by aborting the frame if transmission has begun; or
simply discarding it if transmission has not begun. If
Passthru is selected the unit will transmit the entire frame
but will place an incorrect crc in it to preserve the error
indication.
(1) discard
(2) passthrurw Enumeration .1.3.6.1.4.1.485.7.2.5.2 |
sfrapCfgFrLmiTypeThe LMI type used in a Frame Relay application. This setting
must match the attached Frame Relay device configuration.
Annex-A and Annex-D use DLCI 0, and Type 1 uses DLCI 1023.
Type 1 is alternatively referred to as Cisco, Group of four,
or simply LMI. Annex-D may be referred to as ANSI T1.617.
Annex-A may be referred to as ITU or CCITT Q.933. Auto-sense
will either use the most recently detected LMI type or, in
the absence of any LMI, will attempt to instigate LMI
communications using each protocol.
(1) Annnex-A: conforms to ITU (CCITT) Q.933 annex A
(2) Annnex-D: conforms to ANSI T1.617 annex D
(3) Type 1: conforms to the original LMI as developed by
the Group of Four
(4) Auto-sense: unit will attempt to detect and synchronize
to the LMI type of the attached equipment.rw Enumeration .1.3.6.1.4.1.485.7.2.5.3 |
sfrapCfgFrLmiInactivityTimeoutTimer 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.7.2.5.4 |
sfrapCfgFrLmiKeepaliveTimeoutTimer 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.7.2.5.5 |
sfrapCfgFrAddrResModeEnable ARP (2), INARP (3), both (4), or neither (1).rw Enumeration .1.3.6.1.4.1.485.7.2.5.6 |
sfrapCfgFrAddrResInarpTimerThe frequency of INARP requests in seconds
from 5 seconds to 86400 seconds (24 hours).rw INTEGER .1.3.6.1.4.1.485.7.2.5.7 |
sfrapCfgFrLmiFullStatusTimer 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.7.2.5.8 |
sfrapCfgFrAddrResDlcisAddress Resolution Dlcis determines which dlcis are
used for address resolution. The choices include
using the configured management dlci only (1), all
dlcis (2), all dlcis on the To-DCE port (3) or all
dlcis on the To-DTE port (4). In the last two cases,
the management dlci is used on the other port.
Multiple DLCI support only applies to piggyback mode;
in other management modes, only the configured
management dlci is used.rw Enumeration .1.3.6.1.4.1.485.7.2.5.9 |
sfrapCfgVnipTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.2.6 |
sfrapCfgVnipModeThis 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 TO-DTE only: unit logs VNIP peers seen
out the TO-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 TO-DTE.
(3) Topology Enabled on WAN only: unit logs VNIP peers seen
out the WAN interface. Unit listens for topology reports
from the TO-DTE but doesn't generate any towards the TO-DTE. Will
report learned TO-DTE topology towards the WAN.
(4) Topolgy Enabled on Both TO-DTE and WAN: Unit logs VNIP peers
seen out both interfaces and generates TO-DTE topolgy reports
towards the WAN and vice versa.rw Enumeration .1.3.6.1.4.1.485.7.2.6.1 |
sfrapCfgVnipInitTimerVNIP 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.7.2.6.2 |
sfrapCfgVnipTxTimerThe frequency of hello messages sent
to neighbor(s) in seconds from
5 seconds to 86400 seconds (24 hours).rw INTEGER .1.3.6.1.4.1.485.7.2.6.3 |
sfrapCfgVnipRxTimerThe timeout on receiving a hello message
from a neighbor in seconds from
5 seconds to 86400 seconds (24 hours).rw INTEGER .1.3.6.1.4.1.485.7.2.6.4 |
sfrapCfgVnipTransitDelayFrequencyTransit 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.7.2.6.5 |
sfrapCfgTransitDelayTableThe 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 SfrapCfgTransitDelayEntry .1.3.6.1.4.1.485.7.2.6.20 |
sfrapCfgTransitDelayEntryA 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 SfrapCfgTransitDelayEntry .1.3.6.1.4.1.485.7.2.6.20.1 |
sfrapCfgTransitDelayInterfaceThe interface being configured for VNIP
Transit Delay, either to-dte-interface (1)
or to-dce-interface (2). This table is
indexed by {interface,dlci}.rw Enumeration .1.3.6.1.4.1.485.7.2.6.20.1.1 |
sfrapCfgTransitDelayDlciValueThis 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.7.2.6.20.1.2 |
sfrapCfgTransitDelayNumHopsVNIP 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.7.2.6.20.1.4 |
sfrapCfgTransitDelayRcvSummaryCancelControls 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.7.2.6.20.1.5 |
sfrapCfgTransitDelayThresholdSpecifies 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.7.2.6.20.1.6 |
sfrapCfgTDDeleteTableThe table allows the user to disable transit delay measurements
for a specific DLCI on a particular interface. SEQUENCE OF SfrapCfgTDDeleteEntry .1.3.6.1.4.1.485.7.2.6.21 |
sfrapCfgTDDeleteEntryDisables VNIP Transit Delay for a particular interface and DLCI. SfrapCfgTDDeleteEntry .1.3.6.1.4.1.485.7.2.6.21.1 |
sfrapCfgTDDeleteInterfaceTransit 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.7.2.6.21.1.1 |
sfrapCfgTDDeleteDlciValueThe DLCI chosen to be deleted from the specified
interface-side of the VNIP Transit Delay
configuration table. This table is indexed by
{interface}. To delete an entry in the
sfrapCfgTransitDelayTable, specify the interface
as the index and set the dlci.rw INTEGER .1.3.6.1.4.1.485.7.2.6.21.1.2 |
sfrapCfgTransitDelayTableClearThe sfrapCfgTransitDelayTable is cleared.
(1) clear the tablerw Enumeration .1.3.6.1.4.1.485.7.2.6.22 |
sfrapCfgFrPerf OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.2.7 |
sfrapCfgFrPerfDlciNamesTableThis 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 SfrapCfgFrPerfDlciNamesEntry .1.3.6.1.4.1.485.7.2.7.1 |
sfrapCfgFrPerfDlciNamesEntryA table entry indexed by DLCI, containing
a DLCI, a DLCI name, a CIR, and how the
CIR value was obtained. SfrapCfgFrPerfDlciNamesEntry .1.3.6.1.4.1.485.7.2.7.1.1 |
sfrapCfgFrPerfDlciNamesDlciValueA 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.7.2.7.1.1.1 |
sfrapCfgFrPerfDlciNamesDlciNameA user-specifiable name for an individual DLCI.rw DisplayString .1.3.6.1.4.1.485.7.2.7.1.1.2 |
sfrapCfgFrPerfDlciNamesCirValueThe 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.7.2.7.1.1.3 |
sfrapCfgFrPerfDlciNamesCirTypeThe 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 TO-DTE Line Rate.
(1) CIR reported in LMI Full Status message
(2) CIR configured by user
(3) CIR defaulted to TO-DTE Line Ratero Enumeration .1.3.6.1.4.1.485.7.2.7.1.1.4 |
sfrapCfgFrPerfDlciNamesUtilThresholdThe threshold for generating a utilization
threshold trap as a percentage of the CIR.
If the utilization percentage is above this
threshold for more than
sfrapCfgFrPerfDlciUtilThreshold number of
sfrapCfgFrPerfTimersSTInterval's a
sfrapPvc(Rx/Tx)UtilizationExceeded trap
will be issued. If the If the utilization
percentage falls below this threshold for
more than sfrapCfgFrPerfDlciUtilThreshold
number of sfrapCfgFrPerfTimersSTInterval's a
sfrapPvc(Rx/Tx)UtilizationExceeded trap
will be issued.rw INTEGER .1.3.6.1.4.1.485.7.2.7.1.1.5 |
sfrapCfgFrPerfDlciNamesEirValueThe 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.7.2.7.1.1.6 |
sfrapCfgFrPerfDlciNamesDeleteSetting 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.7.2.7.2 |
sfrapCfgFrPerfTimers OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.2.7.3 |
sfrapCfgFrPerfTimersSTIntervalThe interval in seconds to collect short term
statistics before moving the current counts into the
previous counts and starting current from zeros.
The range is 3 to 60 seconds.rw INTEGER .1.3.6.1.4.1.485.7.2.7.3.1 |
sfrapCfgFrPerfTimersLTIntervalLong 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.7.2.7.3.2 |
sfrapCfgFrPerfUserProtocolsTableThis 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 SfrapCfgFrPerfUserProtocolsEntry .1.3.6.1.4.1.485.7.2.7.4 |
sfrapCfgFrPerfUserProtocolsEntryAn index and TCP/UDP port number pair. SfrapCfgFrPerfUserProtocolsEntry .1.3.6.1.4.1.485.7.2.7.4.1 |
sfrapCfgFrPerfUserProtocolsIndexAn index. Beginning with index 1, the range is defined
in SysNumUserProtocolsro INTEGER .1.3.6.1.4.1.485.7.2.7.4.1.1 |
sfrapCfgFrPerfUserProtocolsPortNumTx 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.7.2.7.4.1.2 |
sfrapCfgFrPerfLTDlciFilterTableLong 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 SfrapCfgFrPerfLTDlciFilterEntry .1.3.6.1.4.1.485.7.2.7.5 |
sfrapCfgFrPerfLTDlciFilterEntryAn index and DLCI number pair. SfrapCfgFrPerfLTDlciFilterEntry .1.3.6.1.4.1.485.7.2.7.5.1 |
sfrapCfgFrPerfLTDlciFilterIndexAn index. Beginning with index 1, the maximum is
defined by the value of SysLTFNumDlcis.ro INTEGER .1.3.6.1.4.1.485.7.2.7.5.1.1 |
sfrapCfgFrPerfLTDlciFilterDlciNumSetting 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.7.2.7.5.1.2 |
sfrapCfgFrPerfLTProtocolFilterTableLong 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 SfrapCfgFrPerfLTProtocolFilterEntry .1.3.6.1.4.1.485.7.2.7.6 |
sfrapCfgFrPerfLTProtocolFilterEntryAn index and protocol pair. SfrapCfgFrPerfLTProtocolFilterEntry .1.3.6.1.4.1.485.7.2.7.6.1 |
sfrapCfgFrPerfLTProtocolFilterIndexAn index. Beginning with index 1, the maximum is
defined by the value of SysLTFNumProtocols.ro INTEGER .1.3.6.1.4.1.485.7.2.7.6.1.1 |
sfrapCfgFrPerfLTProtocolFilterProtocolLong 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.7.2.7.6.1.2 |
sfrapCfgFrPerfDlciDefaultUtilThresholdThe default threshold for generating a
utilization threshold trap as a percentage
of the CIR. This value is used for
sfrapCfgFrPerfDlciNamesUtilThreshold when
a DLCI is first discovered.rw INTEGER .1.3.6.1.4.1.485.7.2.7.7 |
sfrapCfgFrPerfDlciUtilDurationThe number of Short Term Intervals that a
DLCI's utilization as a percentage of CIR
must be above or below the value of
sfrapCfgFrPerfDlciUtilThreshold before a
sfrapPvc(Rx/Tx)UtilizationExceededTrap or
sfrapPvc(Rx/Tx)UtilizationClearedTrap is
issued.rw INTEGER .1.3.6.1.4.1.485.7.2.7.8 |
sfrapCfgFrPerfDlciNamesTableClearClears 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.7.2.7.9 |
sfrapCfgFrPerfUserProtocolsTableClearClears the sfrapCfgFrPerfUserProtocolsTable
(1) clear the tablerw Enumeration .1.3.6.1.4.1.485.7.2.7.10 |
sfrapCfgFrPerfLTDlciFilterTableClearClears the sfrapCfgFrPerfLTDlciFilterTable
(1) clear the tablerw Enumeration .1.3.6.1.4.1.485.7.2.7.11 |
sfrapCfgFrPerfLTProtocolFilterTableClearClears the sfrapCfgFrPerfLTProtocolFilterTable
(1) clear the tablerw Enumeration .1.3.6.1.4.1.485.7.2.7.12 |
sfrapCfgFrPerfUnprovDlcisDeleteDelete all unprovisioned and Not-In-LMI dlcis
(1) delete all unprovisionedrw Enumeration .1.3.6.1.4.1.485.7.2.7.13 |
sfrapCfgSecurityTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.2.8 |
sfrapCfgTelnetCliPasswordThe password needed to start a
CLI (Command Line Interface) session
using either a terminal connected to the
unit or Telnet.rw DisplayString .1.3.6.1.4.1.485.7.2.8.1 |
sfrapCfgTftpPasswordThe password needed to initiate a TFTP download.rw DisplayString .1.3.6.1.4.1.485.7.2.8.2 |
sfrapCfgCliPasswordOBSOLETE: The Telnet and CLI passwords
are one and the same. Use the above
sfrapCfgTelnetCliLcdPassword to log into
the CLI (Command Line Interface).rw DisplayString .1.3.6.1.4.1.485.7.2.8.3 |
sfrapCfgGetCommunityStringThe 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.7.2.8.5 |
sfrapCfgSetCommunityStringThe 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.7.2.8.6 |
sfrapCfgLockRequest 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.7.2.12 |
sfrapCfgLockIDReturns 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.7.2.13 |
sfrapCfgIDA 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.7.2.14 |
sfrapCfgStatusThe 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 sfrapCfgLock command.
(7) The user sent a sfrapCfgUnlock command before a
sfrapCfgUpdate command. This usually means that one
of the sets in the configuration failed.ro Enumeration .1.3.6.1.4.1.485.7.2.15 |
sfrapCfgUnlockThe 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.7.2.16 |
sfrapCfgUpdateThe 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.7.2.17 |
sfrapDiagnostics OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.3 |
sfrapDiagUnitTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.3.1 |
sfrapDiagUnitLocLoopControls a bi-directional unit loopback. Data
is received from either interface, processed,
and transmitted back towards the same interface.
When configured for Frame Relay operation the unit
will preserve the LMI path and maintain managed access
during this loopback. In Frame Relay mode, only valid
HDLC frames are looped back (pseudorandom test patterns
will be dropped).
(1) enable unit loopback
(2) disable unit loopbackrw Enumeration .1.3.6.1.4.1.485.7.3.1.1 |
sfrapDiagUnitResetEnables the operator to remotely reset the unit.
Using this command will cause the unit to terminate
all its connections and drop data.rw Enumeration .1.3.6.1.4.1.485.7.3.1.2 |
sfrapDiagUnitTimeRemainingThe 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.7.3.1.3 |
sfrapDiagUnitCutThruEnables the operator to control and examine the
UNIT Cut Through mode. This diagnostic occurs on
the TO-DTE and TO-DCE transmit and receive logic.
The unit will transmit To-DTE data onto the TO-DCE
port without any intervention by the processor. If the
CutThruTimeout is greater than 0, then the cut-thru
diagnostic will time out after that interval (in minutes).
(same as Tap Mode operation - see CfgAppOperationMode).rw Enumeration .1.3.6.1.4.1.485.7.3.1.4 |
sfrapDiagUnitCutThruTimeRemainingThe 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.7.3.1.5 |
sfrapDiagDteTableThe table of DTE port diagnostics. SEQUENCE OF SfrapDiagDteEntry .1.3.6.1.4.1.485.7.3.3 |
sfrapDiagDteEntryAn diagnostic entry for a DTE port. SfrapDiagDteEntry .1.3.6.1.4.1.485.7.3.3.1 |
sfrapDiagDteLclLpbkControls the DTE loopback state. This is a
bi-directional loopback state where both the
DTE and WAN ports are placed in line loopback.
All data received on each interface is sent back
out the respective interface regardless of format
or content. In Frame Relay applications the unit
will not preserve the LMI path during this diagnostic
and in-band management will not operate.
(1) enable payload loopback
(2) disable payload loopbackrw Enumeration .1.3.6.1.4.1.485.7.3.3.1.3 |
sfrapDiagDteTimeRemainingThe remaining time on the active loopback
before the loopback times out and disables
itself. The time is in hundredths of seconds
(TimeTicks).ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.485.7.3.3.1.13 |
sfrapDiagDteIndexSelects which DTE port.ro Enumeration .1.3.6.1.4.1.485.7.3.3.1.99 |
sfrapDiagVnipTableTable of Diagnostics performed with the VNIP protocol SEQUENCE OF SFRAPDiagVnipEntry .1.3.6.1.4.1.485.7.3.6 |
sfrapDiagVnipEntryVNIP 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. SFRAPDiagVnipEntry .1.3.6.1.4.1.485.7.3.6.1 |
sfrapDiagVnipInterfaceThe 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.7.3.6.1.1 |
sfrapDiagVnipIndexThe 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.7.3.6.1.2 |
sfrapDiagVnipDlciThis is the DLCI value for the given interface/index
combination. This comes from the VniptTopologyTable.ro INTEGER .1.3.6.1.4.1.485.7.3.6.1.3 |
sfrapDiagVnipIpAddrThis is the ip address for the given interface/index
combination. This comes from the VniptTopologyTable.ro IpAddress .1.3.6.1.4.1.485.7.3.6.1.4 |
sfrapDiagVLOOPControls 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.7.3.6.1.5 |
sfrapDiagVBERTControls 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.7.3.6.1.6 |
sfrapDiagVBERTRateSpecifies the throughput bit rate applied by VBERT or
VLOOP to the DLCI-under-test. For TO-DTE Rates or configured
CIR up to 64K the maximum VBERT rate is either the TO-DTE data
rate or 110% of CIR (which ever is less). For TO-DTE Rates or
configured CIR greater than 64K, the maximum VBERT rate is
75% of the TO-DTE data rate or 110% of CIR (which ever is less).
Note that selecting rates that approach line rate will impact
neighboring PVCs.
(8000-1152000): VBERT/VLOOP data rate (in bits per second).rw INTEGER .1.3.6.1.4.1.485.7.3.6.1.7 |
sfrapDiagVBERTSizeSpecifies 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.7.3.6.1.8 |
sfrapDiagVBERTPktPercentSpecifies percentage of VBERT packets that will have the
Frame Relay Discard Eligibility bit set. Frames with this
bit set may be more likley to get dropped in a congested
network.
(0) 0% of the test frames are marked discard eligible
(25) 25% of the test frames are marked discard eligible
(50) 50% of the test frames are marked discard eligible
(75) 75% of the test frames are marked discard eligible
(100) 100% of the test frames are marked discard eligiblerw Enumeration .1.3.6.1.4.1.485.7.3.6.1.9 |
sfrapDiagVBERTTestPeriodSpecifies 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.7.3.6.1.10 |
sfrapDiagTxClockDetectEnables the operator to activate clock detection
on the TO-DCE Transmit clock. Clock detection
can be stopped by issuing the terminate command.rw Enumeration .1.3.6.1.4.1.485.7.3.7 |
sfrapStatus OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.4 |
sfrapVnipTopologyTableTopology of peers discovered via VNIP, organized
by the interface (DATA1 or DATA2) from which they were
discovered and an entry number or index. The
topology is of limited size per interface. SEQUENCE OF SfrapVnipTopologyEntry .1.3.6.1.4.1.485.7.4.2 |
sfrapVnipTopologyEntryThe DLCI, IP address, and number of hops
for a particular node, discovered via VNIP
off of an interface (DATA1 or DATA2). The entry
may also have transit delay measurements
for the particular node. SfrapVnipTopologyEntry .1.3.6.1.4.1.485.7.4.2.1 |
sfrapVnipTopologyInterfaceThe interface off of which the peer was
discovered. Topology is discovered by
sending VNIP messages out each interface.
Nodes discovered via a particular interface
are kept in a list associated with that
interface.ro Enumeration .1.3.6.1.4.1.485.7.4.2.1.1 |
sfrapVnipTopologyIndexThe number of this discovered peer in the list
of nodes for this interface. For each interface,
the nodes are numbered 1 through n.ro INTEGER .1.3.6.1.4.1.485.7.4.2.1.2 |
sfrapVnipTopologyDlciThe DLCI of the discovered neighboring peer.
This may be different from the local DLCI.ro INTEGER .1.3.6.1.4.1.485.7.4.2.1.3 |
sfrapVnipTopologyIpAddrThe IP address for the discovered peer.ro IpAddress .1.3.6.1.4.1.485.7.4.2.1.4 |
sfrapVnipTopologyNumHopsThe discovered peer is this number of hops away.ro INTEGER .1.3.6.1.4.1.485.7.4.2.1.5 |
sfrapVnipTopologyLocalDlciThe DLCI of this node over which the remote peer
was discovered.ro INTEGER .1.3.6.1.4.1.485.7.4.2.1.6 |
sfrapVnipTopoTDNumSamplesThe number of transit delay samples collected.ro Counter .1.3.6.1.4.1.485.7.4.2.1.10 |
sfrapVnipTopoTDAvgDelayThe average transit delay between this
node and the remote peer.ro Counter .1.3.6.1.4.1.485.7.4.2.1.11 |
sfrapVnipTopoTDMaxDelayThe maximum transit delay between this
node and the remote peer.ro Counter .1.3.6.1.4.1.485.7.4.2.1.12 |
sfrapVnipTopoTDMinDelayThe minimum transit delay between this
node and the remote peer.ro Counter .1.3.6.1.4.1.485.7.4.2.1.13 |
sfrapVnipTopoTDLastDelayThe most recent transit delay measured between
this node and the remote peer.ro Counter .1.3.6.1.4.1.485.7.4.2.1.14 |
sfrapVnipTopoVLOOPStatusThis selection displays the status of the VNIP Loopback
This loopback is initiated by the remote node, causing
this node to loop data back to the remote node.ro Enumeration .1.3.6.1.4.1.485.7.4.2.1.15 |
sfrapVnipTopoVBERTStatusDisplays the current status of the VBERT test, values are
off(1): no test has run or the entry has been cleared,
testing(2): the entry is generating VBERT packets,
in-test(5): the entry is on the receiving end of VBERT packets
test-completed(4): a test has run and is finished results are complete
test-failed(3): the request for a test on this entry failedro Enumeration .1.3.6.1.4.1.485.7.4.2.1.16 |
sfrapVnipTopoVBertTxDESetFramesDisplays the number of Frames transmitted during VBERT Test that
had the Discard Eligibility indicator bit set.ro Counter .1.3.6.1.4.1.485.7.4.2.1.17 |
sfrapVnipTopoVBertRxDESetFramesDisplays the number of Frames received during VBERT Test that
had the Discard Eligibility indicator bit set.ro Counter .1.3.6.1.4.1.485.7.4.2.1.18 |
sfrapVnipTopoVBertTxDEClrFramesDisplays the number of Frames transmitted during VBERT Test that
had the Discard Eligibility indicator bit cleared.ro Counter .1.3.6.1.4.1.485.7.4.2.1.19 |
sfrapVnipTopoVBertRxDEClrFramesDisplays the number of Frames received during VBERT Test that
had the Discard Eligibility indicator bit cleared.ro Counter .1.3.6.1.4.1.485.7.4.2.1.20 |
sfrapVnipTopoVBertTransitDelayMaxThe maximum transit delay between this
node and the remote peer during the VBERT test.ro Counter .1.3.6.1.4.1.485.7.4.2.1.21 |
sfrapVnipTopoVBertTransitDelayAvgThe average transit delay between this
node and the remote peer during the VBERT test.ro Counter .1.3.6.1.4.1.485.7.4.2.1.22 |
sfrapVnipTopoVBertTimeElapseElapsed time since VBERT test was started or cleared.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.485.7.4.2.1.23 |
sfrapVnipTopoVBertPerUtilCIRThe 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.7.4.2.1.24 |
sfrapVnipTopoVBertPerUtilEIRThe 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.7.4.2.1.25 |
sfrapStatusMgmtTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.4.3 |
sfrapStatusMgmtChannelThis 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.7.4.3.1 |
sfrapStatusMgmtInterfaceThis is the port(s) on which the management traffic will appear.
(1) Async Maintenance(Comm)/Console port - SLIP mode
(2) Local TO-DTE interface: unit is configured for Private Local
DLCI mode
(3) Remote WAN Interface: unit is confiogured for Private Remote
DLCI mode
(4) TO-DTE and WAN Interfaces: unit is configured for either Piggyback
Bidirectional mode.ro Enumeration .1.3.6.1.4.1.485.7.4.3.2 |
sfrapStatusMgmtInterfaceStatusThis is the status of the port(s) on which
the management traffic will appear.
(1) Active: port or DLCI is configured and status is okay
(2) Inactive: port or DLCI is declared out of service
(3) Alarm: port or DLCI is experiencing an alarm condition that may
interefere with management accessro Enumeration .1.3.6.1.4.1.485.7.4.3.3 |
sfrapStatusMgmtDefaultDLCINoThis 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.7.4.3.4 |
sfrapStatusMgmtDefaultDLCIStatusThis 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.7.4.3.5 |
sfrapStatusLedTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.4.4 |
sfrapStatusLedOpStatusLEDStatus of the Operation Mode LED.ro Enumeration .1.3.6.1.4.1.485.7.4.4.1 |
sfrapStatusLedToDTETxLEDStatus of the TO-DTE TxD LED.ro Enumeration .1.3.6.1.4.1.485.7.4.4.2 |
sfrapStatusLedToDTERxLEDStatus of the TO-DTE RxD LED.ro Enumeration .1.3.6.1.4.1.485.7.4.4.3 |
sfrapStatusLedRtsLEDStatus of the RTS Signal LED.ro Enumeration .1.3.6.1.4.1.485.7.4.4.4 |
sfrapStatusLedCtsLEDStatus of the CTS Signal LED.ro Enumeration .1.3.6.1.4.1.485.7.4.4.5 |
sfrapStatusLedDsrLEDStatus of the DSR Signal LED.ro Enumeration .1.3.6.1.4.1.485.7.4.4.7 |
sfrapStatusLedDcdLEDStatus of the DCD Signal LED.ro Enumeration .1.3.6.1.4.1.485.7.4.4.8 |
sfrapStatusLedToDCETxLEDStatus of the TO-DCE TxD LED.ro Enumeration .1.3.6.1.4.1.485.7.4.4.9 |
sfrapStatusLedToDCERxLEDStatus of the TO-DCE RxD LED.ro Enumeration .1.3.6.1.4.1.485.7.4.4.10 |
sfrapStatusAllLEDsStatus of all ten SFRAP 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 13 letters are SFRAP Op Mode,
TO-DCE Rx, TO-DCE Tx, RTS, CTS, DCD, DSR,
LMI Error, Frame Activity, Ctrl, Ind, TO-DTE Rx, TO-DTE Tx.ro DisplayString .1.3.6.1.4.1.485.7.4.4.14 |
sfrapStatusLedLmiErrLEDStatus of the LMI Error LED.ro Enumeration .1.3.6.1.4.1.485.7.4.4.15 |
sfrapStatusLedFrmActLEDStatus of the Frame Activity LED.ro Enumeration .1.3.6.1.4.1.485.7.4.4.16 |
sfrapStatusLedCtrlLEDStatus of the X.21 Control Signal LED.
Only applicable when in X.21.ro Enumeration .1.3.6.1.4.1.485.7.4.4.17 |
sfrapStatusLedIndLEDStatus of the X.21 Indication Signal LED.
Only applicable when in X.21.ro Enumeration .1.3.6.1.4.1.485.7.4.4.18 |
sfrapVnipTransitDelayClearAllows the user to clear all the VNIP Transit Delay
data collected in the VNIP topology database.rw Enumeration .1.3.6.1.4.1.485.7.4.5 |
sfrapLmiSourcingWhat type of LMI sourcing is being done: initializing (1),
passthrough (2), emulating a user device on the To-DTE (3),
emulating a user device on the To-DCE (4), emulating a
network device on the To-DTE (5), emulating a network device
on the To-DCE (6), disabled (7), or emulating a switch by
responding to both ports (8).ro Enumeration .1.3.6.1.4.1.485.7.4.6 |
sfrapStatusDteTableThe table of DTE port statuses. SEQUENCE OF SfrapStatusDteEntry .1.3.6.1.4.1.485.7.4.7 |
sfrapStatusDteEntryAn status entry for a DTE port. SfrapStatusDteEntry .1.3.6.1.4.1.485.7.4.7.1 |
sfrapStatusDteModeStatus of the port. no-connections (1) indicates
the port has no connections. Active (2) indicates
connections and data mode. Test (3) indicates
connections and diagnostic state for that port.ro Enumeration .1.3.6.1.4.1.485.7.4.7.1.1 |
sfrapStatusDteRtsStatus of the RTS signal on the port:
on (1) and off (2).ro Enumeration .1.3.6.1.4.1.485.7.4.7.1.2 |
sfrapStatusDteDtrStatus of the DTR signal on the port:
on (1) and off (2).ro Enumeration .1.3.6.1.4.1.485.7.4.7.1.3 |
sfrapStatusDteDcdWhether the DCD signal on the port is on (1) or off (2).ro Enumeration .1.3.6.1.4.1.485.7.4.7.1.4 |
sfrapStatusDteDsrWhether the DSR signal on the port is on (1) or off (2).ro Enumeration .1.3.6.1.4.1.485.7.4.7.1.5 |
sfrapStatusDteCtsWhether the CTS signal on the port is on (1) or off (2).ro Enumeration .1.3.6.1.4.1.485.7.4.7.1.6 |
sfrapStatusDteSendtimingWhether Send Timing is (1)present or (2)not-present
on the interface.ro Enumeration .1.3.6.1.4.1.485.7.4.7.1.7 |
sfrapStatusDteRxtimingWhether Receive Timing is (1)present or (2)not-present
on the interface.ro Enumeration .1.3.6.1.4.1.485.7.4.7.1.8 |
sfrapStatusDteTermtimingWhether Terminal Timing is (1)present or (2)not-present
on the interface.ro Enumeration .1.3.6.1.4.1.485.7.4.7.1.9 |
sfrapStatusDteCtrlThe status of the Control lead when using X.21ro Enumeration .1.3.6.1.4.1.485.7.4.7.1.10 |
sfrapStatusDteIndThe status of the Indication lead when using X.21ro Enumeration .1.3.6.1.4.1.485.7.4.7.1.11 |
sfrapStatusDteIndexSelects which DTE port.ro Enumeration .1.3.6.1.4.1.485.7.4.7.1.99 |
sfrapStatusClockRateThis is the value in Kbps of the Receive Clock Frequency,
for both the TO-DTE and TO-DCE ports.ro INTEGER .1.3.6.1.4.1.485.7.4.8 |
sfrapStatusToDteRxClockModeThe status of the Receive clocking mode.ro Enumeration .1.3.6.1.4.1.485.7.4.9 |
sfrapStatusDipswitchTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.4.10 |
sfrapStatusDipswitchCutthruStatus of the Operation Mode LED.ro Enumeration .1.3.6.1.4.1.485.7.4.10.1 |
sfrapStatusDipswitchToDteLpbkStatus of the TO-DTE TxD LED.ro Enumeration .1.3.6.1.4.1.485.7.4.10.2 |
sfrapStatusDipswitchToDceLpbkStatus of the TO-DTE RxD LED.ro Enumeration .1.3.6.1.4.1.485.7.4.10.3 |
sfrapStatusDipswitchUnusedStatus of the RTS Signal LED.ro Enumeration .1.3.6.1.4.1.485.7.4.10.4 |
sfrapStatusDipswitchIntfMode1Status of the RTS Signal LED.ro Enumeration .1.3.6.1.4.1.485.7.4.10.5 |
sfrapStatusDipswitchIntfMode2Status of the RTS Signal LED.ro Enumeration .1.3.6.1.4.1.485.7.4.10.6 |
sfrapVBertClearAllows 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.rw Enumeration .1.3.6.1.4.1.485.7.4.11 |
sfrapStatusLmiAutosenseThis 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.7.4.12 |
sfrapStatusTxClockDetectThis selection displays the status of the TO-DCE
transmit clock auto detection process.
(1)inactive - The Auto Detect option was not
selected.
(2)initiate - The Auto Detect option was selected
and is initializing.
(3)trying-cut-thru - The Auto Detect option is trying
to verify the integrity of the TO-DCE transmit clock
mode selected in Cut Through mode
(4)failed-cut-thru - This mechanism has detected that the
LMI integrity check has failed.
(5)trying-inband-normal - The Auto Detection mechanism
has set the TO-DCE Tx clock to normal timing and is
performing the link integrity check, to determine if this
selection is correct
(6)success-inband-norm - The Auto Detection mechanism has
determined that the TO-DCE Tx clock timing is successful
in normal mode.
(7)trying-inband-invert - The Auto Detection mechanism
has determined that the TO-DCE clock mode failed using
normal timing, now it has inverted the clock.
(8)success-inband-invert - The mechanism has decided that
the TO-DCE Tx clock needs to be inverted.
(9)failed-in-band - Neither Normal or Invert timing was
successful.
(10)terminated - The Auto Detection mechanism has been
terminated.ro Enumeration .1.3.6.1.4.1.485.7.4.13 |
sfrapPerformance OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.5 |
sfrapPerfMgmtIp OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.5.2 |
sfrapPerfMgmtIpIFStatsTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.5.2.1 |
sfrapPerfMgmtIpIFInOctetsThe count of all octets received.
Same as ifInOctets in mib-2.ro Counter .1.3.6.1.4.1.485.7.5.2.1.1 |
sfrapPerfMgmtIpIFInErrorsThe count of 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.7.5.2.1.2 |
sfrapPerfMgmtIpIFOutOctetsThe count of all octets transmitted.
Same as ifOutOctets in mib-2.ro Counter .1.3.6.1.4.1.485.7.5.2.1.3 |
sfrapPerfMgmtIpIFOperStatusThe current operational state.
Same as ifOperStatus in mib-2.ro Enumeration .1.3.6.1.4.1.485.7.5.2.1.4 |
sfrapPerfMgmtIpIPStatsTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.5.2.2 |
sfrapPerfMgmtIpIPInRcvThe count of all datagrams received.
Same as ipInReceives in mib-2.ro Counter .1.3.6.1.4.1.485.7.5.2.2.1 |
sfrapPerfMgmtIpIPInHdrErrThe count of 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.7.5.2.2.2 |
sfrapPerfMgmtIpIPInAddrErrThe count of 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.7.5.2.2.3 |
sfrapPerfMgmtIpIPInProtUnkThe count of datagrams received that were
discarded because of unsupported protocols.
Same as ipInUnknownProtos in mib-2.ro Counter .1.3.6.1.4.1.485.7.5.2.2.4 |
sfrapPerfMgmtIpIPInDscrdThe count of 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.7.5.2.2.5 |
sfrapPerfMgmtIpIPInDlvrsThe count of datagrams received that were
delivered to IP client-protocols.
Same as ipInDelivers in mib-2.ro Counter .1.3.6.1.4.1.485.7.5.2.2.6 |
sfrapPerfMgmtIpIPOutRqstThe count of all outgoing datagrams
originating in this node.
Same as ipOutRequests in mib-2.ro Counter .1.3.6.1.4.1.485.7.5.2.2.7 |
sfrapPerfMgmtIpIPOutDscrdThe count of outgoing 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.7.5.2.2.8 |
sfrapPerfMgmtIpIPOutNoRtThe count of outgoing 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.7.5.2.2.9 |
sfrapPerfMgmtIpICMPStatsTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.5.2.3 |
sfrapPerfMgmtIpICMPInMsgsThe count of all ICMP messages received.
Same as icmpInMsgs in mib-2.ro Counter .1.3.6.1.4.1.485.7.5.2.3.1 |
sfrapPerfMgmtIpICMPInErrorsThe count of ICMP messages received with
errors. Same as icmpInErrors in mib-2.ro Counter .1.3.6.1.4.1.485.7.5.2.3.2 |
sfrapPerfMgmtIpICMPInDestUnreachsThe count of ICMP Destination Unreachable
messages received.
Same as icmpInDestUnreachs in mib-2.ro Counter .1.3.6.1.4.1.485.7.5.2.3.3 |
sfrapPerfMgmtIpICMPInTimeExcdsThe count of ICMP Time Exceeded messages
received.
Same as icmpInTimeExcds in mib-2.ro Counter .1.3.6.1.4.1.485.7.5.2.3.4 |
sfrapPerfMgmtIpICMPInParmProbsThe count of ICMP Parameter Problem messages
received.
Same as icmpInParmProbs in mib-2.ro Counter .1.3.6.1.4.1.485.7.5.2.3.5 |
sfrapPerfMgmtIpICMPInRedirectsThe count of ICMP Redirect messages received.
Same as icmpInRedirects in mib-2.ro Counter .1.3.6.1.4.1.485.7.5.2.3.6 |
sfrapPerfMgmtIpICMPInEchosThe count of ICMP Echo messages received.
Same as icmpInEchos in mib-2.ro Counter .1.3.6.1.4.1.485.7.5.2.3.7 |
sfrapPerfMgmtIpICMPInEchoRepsThe count of ICMP Echo Reply messages received.
Same as icmpInEchoReps in mib-2.ro Counter .1.3.6.1.4.1.485.7.5.2.3.8 |
sfrapPerfMgmtIpICMPOutMsgsThe count of all outgoing ICMP messages
originating in this node.
Same as icmpOutMsgs in mib-2.ro Counter .1.3.6.1.4.1.485.7.5.2.3.9 |
sfrapPerfMgmtIpICMPOutErrorsThe count of outgoing 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.7.5.2.3.10 |
sfrapPerfMgmtIpICMPOutDestUnreachsThe count of outgoing ICMP Destination Unreachable
messages.
Same as icmpOutDestUnreachs in mib-2.ro Counter .1.3.6.1.4.1.485.7.5.2.3.11 |
sfrapPerfMgmtIpICMPOutParmProbsThe count of outgoing ICMP Parameter Problem
messages.
Same as icmpOutParmProbs in mib-2.ro Counter .1.3.6.1.4.1.485.7.5.2.3.12 |
sfrapPerfMgmtIpICMPOutRedirectsThe count of outgoing ICMP Redirect messages.
Same as icmpOutRedirects in mib-2.ro Counter .1.3.6.1.4.1.485.7.5.2.3.13 |
sfrapPerfMgmtIpICMPOutEchosThe count of outgoing ICMP Echo messages.
Same as icmpOutEchos in mib-2.ro Counter .1.3.6.1.4.1.485.7.5.2.3.14 |
sfrapPerfMgmtIpICMPOutEchoRepsThe count of outgoing ICMP Echo Reply messages.
Same as icmpOutEchoReps in mib-2.ro Counter .1.3.6.1.4.1.485.7.5.2.3.15 |
sfrapPerfMgmtIpUDPStatsTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.5.2.4 |
sfrapPerfMgmtIpUDPInDatagramsThe count of all UDP datagrams received that are
addressed as management frames for this unit. Same
as udpInDatagrams in mib-2.ro Counter .1.3.6.1.4.1.485.7.5.2.4.1 |
sfrapPerfMgmtIpUDPOutDatagramsThe count of all UDP datagrams generated by
this unit. Same as udpOutDatagrams in mib-2.ro Counter .1.3.6.1.4.1.485.7.5.2.4.2 |
sfrapPerfMgmtIpUDPNoPortsThe count of all UDP datagrams received that are
addressed as management frames for this unit with
no application at the destination port. Same as
udpNoPorts in mib-2.ro Counter .1.3.6.1.4.1.485.7.5.2.4.3 |
sfrapPerfMgmtIpTCPStatsTable OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.5.2.5 |
sfrapPerfMgmtIpTCPActiveOpensThe count of the times TCP connections specific to this
unit have made a direct state transition from CLOSED to
SYN-SENT. Same as tcpActiveOpens in mib-2.ro Counter .1.3.6.1.4.1.485.7.5.2.5.1 |
sfrapPerfMgmtIpTCPPassiveOpensThe count of the times TCP connections specific to
this unit have made a direct state transition from
CLOSED to SYN-RCVD. Same as tcpPassiveOpens in mib-2.ro Counter .1.3.6.1.4.1.485.7.5.2.5.2 |
sfrapPerfMgmtIpTCPAttemptFailsThe count of the times TCP connections specific to this unit
have made a direct state transition from SYN-SENT or SYN-RCVD
to CLOSED state, plus the count of the times TCP connections
have made a direct state transition from SYN-RCVD to LISTEN.
Same as tcpAttemptFails in mib-2.ro Counter .1.3.6.1.4.1.485.7.5.2.5.3 |
sfrapPerfMgmtIpTCPCurrEstabThe count of the TCP connections specific to this unit
in state ESTABLISHED or CLOSE-WAIT. Same as tcpCurrEstab
in mib-2.ro Gauge .1.3.6.1.4.1.485.7.5.2.5.4 |
sfrapPerfMgmtIpTCPInSegsThe count of all the segments received that are
addressed as management frames for this unit.
Same as tcpInSegs in mib-2.ro Counter .1.3.6.1.4.1.485.7.5.2.5.5 |
sfrapPerfMgmtIpTCPOutSegsThe count of all the segments generated from this unit.
Same as tcpOutSegs in mib-2.ro Counter .1.3.6.1.4.1.485.7.5.2.5.6 |
sfrapPerfThruput OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.5.3 |
sfrapPerfThruputPerIntfTableThe throughput per interface table. These values are accumulated
across all DLCIs. SEQUENCE OF SfrapPerfThruputPerIntfEntry .1.3.6.1.4.1.485.7.5.3.1 |
sfrapPerfThruputPerIntfEntryAn entry in the throughput per interface table. SfrapPerfThruputPerIntfEntry .1.3.6.1.4.1.485.7.5.3.1.1 |
sfrapPerfThruputPerIntfIndexInterface for which the statistics apply.
(1) TO-DTE interface
(2) TO-DCE interfacero Enumeration .1.3.6.1.4.1.485.7.5.3.1.1.1 |
sfrapPerfThruputPerIntfRxByteCntThe number of framed bytes that have been received
on this interface.ro Counter .1.3.6.1.4.1.485.7.5.3.1.1.2 |
sfrapPerfThruputPerIntfTxByteCntThe number of framed bytes that have been transmitted
on this interface.ro Counter .1.3.6.1.4.1.485.7.5.3.1.1.3 |
sfrapPerfThruputPerIntfRxFrameCntThe number of frames that have been received
on this interface.ro Counter .1.3.6.1.4.1.485.7.5.3.1.1.4 |
sfrapPerfThruputPerIntfTxFrameCntThe number of frames that have been transmitted
on this interface.ro Counter .1.3.6.1.4.1.485.7.5.3.1.1.5 |
sfrapPerfThruputPerIntfRxCrcErrCntThe number of frames with CRC errors received
on this interface.ro Counter .1.3.6.1.4.1.485.7.5.3.1.1.6 |
sfrapPerfThruputPerIntfRxAbortCntThe number of aborted frames received
on this interface.ro Counter .1.3.6.1.4.1.485.7.5.3.1.1.7 |
sfrapPerfThruputPerIntfRxBpvCntThe number of BPV errors received
on this interface.ro Counter .1.3.6.1.4.1.485.7.5.3.1.1.8 |
sfrapPerfThruputPerDlciTableLayer 2 statistics on a per-DLCI basis. Transmit direction
is from TO-DTE to WAN and receive direction is from the WAN
towards the TO-DTE. SEQUENCE OF SfrapPerfThruputPerDlciEntry .1.3.6.1.4.1.485.7.5.3.2 |
sfrapPerfThruputPerDlciEntryThe Statistics for a particular Data Link
Connection Management Interface (DLCI). SfrapPerfThruputPerDlciEntry .1.3.6.1.4.1.485.7.5.3.2.1 |
sfrapPerfThruputPerDlciIndexThis 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.7.5.3.2.1.1 |
sfrapPerfThruputPerDlciValueThe DLCI value in which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.7.5.3.2.1.2 |
sfrapPerfThruputPerDlciCreateTimeThe 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.7.5.3.2.1.3 |
sfrapPerfThruputPerDlciChangeTimeThe 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.7.5.3.2.1.4 |
sfrapPerfThruputPerDlciRxByteThe 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.7.5.3.2.1.5 |
sfrapPerfThruputPerDlciTxByteThe number of bytes that have been transmitted from the
TO-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.7.5.3.2.1.6 |
sfrapPerfThruputPerDlciRxFrameThe 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.7.5.3.2.1.7 |
sfrapPerfThruputPerDlciTxFrameThe number of frames that have been transmitted from the
TO-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.7.5.3.2.1.8 |
sfrapPerfThruputPerDlciRxFecnThe number of frames received from the WAN towards the TO-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.7.5.3.2.1.9 |
sfrapPerfThruputPerDlciRxBecnThe number of frames received from the WAN towards the TO-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.7.5.3.2.1.10 |
sfrapPerfThruputPerDlciRxDeThe number of frames received from the WAN towards the TO-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.7.5.3.2.1.11 |
sfrapPerfThruputPerDlciTxDeThe number of frames transmit towards the WAN from the TO-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.7.5.3.2.1.12 |
sfrapPerfThruputPerDlciRxThruputThe 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.7.5.3.2.1.13 |
sfrapPerfThruputPerDlciTxThruputThe 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.7.5.3.2.1.14 |
sfrapPerfThruputPerDlciCIRThe 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.7.5.3.2.1.15 |
sfrapPerfThruputPerDlciUptimeThe total amount of time that the DLCI has been up as
reported by the LMI Full Status Response (in seconds).ro INTEGER .1.3.6.1.4.1.485.7.5.3.2.1.16 |
sfrapPerfThruputPerDlciDowntimeThe 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.7.5.3.2.1.17 |
sfrapPerfThruputPerDlciCirTypeThe 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.7.5.3.2.1.18 |
sfrapPerfThruputPerDlciPvcStateThe 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.7.5.3.2.1.19 |
sfrapPerfThruputPerDlciOutageCountThe 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.7.5.3.2.1.20 |
sfrapPerfThruputPerDlciAvailabilityThe 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.7.5.3.2.1.21 |
sfrapPerfThruputPerDlciMTBSOMean Time Between Service Outages: UpTime/OutageCount
or zero if OutageCount = 0 (in seconds).ro INTEGER .1.3.6.1.4.1.485.7.5.3.2.1.22 |
sfrapPerfThruputPerDlciMTTSRMean Time to ServiceRestoral: DownTime/OutageCount
or zero if OutageCount = 0 (in seconds).ro INTEGER .1.3.6.1.4.1.485.7.5.3.2.1.23 |
sfrapPerfThruputPerDlciEncapTypeThe 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.7.5.3.2.1.24 |
sfrapPerfThruputPerDlciRxUtilizationStatusThe 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.7.5.3.2.1.25 |
sfrapPerfThruputPerDlciTxUtilizationStatusThe 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.7.5.3.2.1.26 |
sfrapPerfThruputPerDlciEIRThe 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.7.5.3.2.1.27 |
sfrapPerfThruputCommands OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.5.3.3 |
sfrapPerfThruputCmdClearToDteStatsAllows the user to zero out all the interface statistics in
the TO-DTE portion of the ThruputPerIntf statistics table.
(1) Clear TO-DTE interface statistics command.rw Enumeration .1.3.6.1.4.1.485.7.5.3.3.1 |
sfrapPerfThruputCmdClearToDceStatsAllows the user to zero out all the interface statistics in
the WAN portion of the ThruputPerIntf statistics table.
(1) Clear WAN interface statistics command.rw Enumeration .1.3.6.1.4.1.485.7.5.3.3.2 |
sfrapPerfThruputCmdClearAllIntfStatsAllows the user to zero out all the statistics in
the ThruputPerIntf statistics table.rw Enumeration .1.3.6.1.4.1.485.7.5.3.3.3 |
sfrapPerfThruputCmdClearDlciStatsAllows 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.7.5.3.3.4 |
sfrapPerfThruputCmdClearAllStatsAllows 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.7.5.3.3.5 |
sfrapPerfThruputCmdRemoveStsDlciAllows the user to remove a Dlci from the short term
statistics tables.rw INTEGER .1.3.6.1.4.1.485.7.5.3.3.6 |
sfrapPerfThruputCmdReplaceDlciTableAllows the user to replace one DLCI in the short-term
statistics table with another one. SEQUENCE OF SfrapPerfThruputCmdReplaceDlciEntry .1.3.6.1.4.1.485.7.5.3.3.7 |
sfrapPerfThruputCmdReplaceDlciEntryAllows the user to replace one DLCI in the short-term
statistics table with another one. SfrapPerfThruputCmdReplaceDlciEntry .1.3.6.1.4.1.485.7.5.3.3.7.1 |
sfrapPerfThruputCmdReplaceDlciValueA 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.7.5.3.3.7.1.1 |
sfrapPerfThruputCmdReplaceDlciNewValueA 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.7.5.3.3.7.1.2 |
sfrapPerfThruputCmdAvailabilityStsDlciResetAllows 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.7.5.3.3.8 |
sfrapPerfThruputCmdAvailabilityStsDlciResetAllAllows 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.7.5.3.3.9 |
sfrapPerfThruputCmdCountsStsDlciResetAllows 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.7.5.3.3.10 |
sfrapPerfThruputCmdCountsStsDlciResetAllAllows 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.7.5.3.3.11 |
sfrapPerfThruputCmdAllStsDlciResetAllows 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.7.5.3.3.12 |
sfrapPerfThruputCmdAllStsDlciResetAllAllows 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.7.5.3.3.13 |
sfrapPerfNetworkShortTerm OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.5.4 |
sfrapPerfNetwProtoPerDlciTableThe 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 SfrapPerfNetwProtoPerDlciEntry .1.3.6.1.4.1.485.7.5.4.1 |
sfrapPerfNetwProtoPerDlciEntryThe Network Layer Short Term Statistics
for a particular DLCI. This table organizes
statistics by high-layer network protocol. SfrapPerfNetwProtoPerDlciEntry .1.3.6.1.4.1.485.7.5.4.1.1 |
sfrapPerfNetwProtoPerDlciIntervalThe 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.7.5.4.1.1.1 |
sfrapPerfNetwProtoPerDlciValueThe DLCI value with which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.7.5.4.1.1.2 |
sfrapPerfNetwProtoPerDlciRxTotalThe total number of received Network Layer bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.1.1.3 |
sfrapPerfNetwProtoPerDlciTxTotalThe total number of transmitted Network Layer bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.1.1.4 |
sfrapPerfNetwProtoPerDlciRxIpThe number of received IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.1.1.5 |
sfrapPerfNetwProtoPerDlciTxIpThe number of transmitted IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.1.1.6 |
sfrapPerfNetwProtoPerDlciRxIpxThe number of received IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.1.1.7 |
sfrapPerfNetwProtoPerDlciTxIpxThe number of transmitted IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.1.1.8 |
sfrapPerfNetwProtoPerDlciRxSnaThe number of received SNA bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.1.1.9 |
sfrapPerfNetwProtoPerDlciTxSnaThe number of transmitted SNA bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.1.1.10 |
sfrapPerfNetwProtoPerDlciRxArpThe number of received ARP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.1.1.11 |
sfrapPerfNetwProtoPerDlciTxArpThe number of transmitted ARP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.1.1.12 |
sfrapPerfNetwProtoPerDlciRxCiscoThe number of received Cisco protocol bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.1.1.13 |
sfrapPerfNetwProtoPerDlciTxCiscoThe number of transmitted Cisco protocol bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.1.1.14 |
sfrapPerfNetwProtoPerDlciRxOtherThe 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.7.5.4.1.1.15 |
sfrapPerfNetwProtoPerDlciTxOtherThe 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.7.5.4.1.1.16 |
sfrapPerfNetwProtoPerDlciRxVnipThe number of received VNIP protocol bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.1.1.17 |
sfrapPerfNetwProtoPerDlciTxVnipThe number of transmitted VNIP protocol bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.1.1.18 |
sfrapPerfNetwProtoPerDlciRxAnnexGThe number of received Annex G protocol
bytes that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.1.1.19 |
sfrapPerfNetwProtoPerDlciTxAnnexGThe number of transmitted Annex G protocol
bytes that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.1.1.20 |
sfrapPerfNetwProtoTotalTableThe Short Term Statistics on Network Layer
protocols summed across all DLCIs. SEQUENCE OF SfrapPerfNetwProtoTotalEntry .1.3.6.1.4.1.485.7.5.4.2 |
sfrapPerfNetwProtoTotalEntryThe Network Layer Short Term Statistics
for a particular DLCI. SfrapPerfNetwProtoTotalEntry .1.3.6.1.4.1.485.7.5.4.2.1 |
sfrapPerfNetwProtoTotalIntervalThe 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.7.5.4.2.1.1 |
sfrapPerfNetwProtoTotalRxTotalThe total number of received Network Layer bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.2.1.3 |
sfrapPerfNetwProtoTotalTxTotalThe total number of transmitted Network Layer bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.2.1.4 |
sfrapPerfNetwProtoTotalRxIpThe number of received IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.2.1.5 |
sfrapPerfNetwProtoTotalTxIpThe number of transmitted IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.2.1.6 |
sfrapPerfNetwProtoTotalRxIpxThe number of received IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.2.1.7 |
sfrapPerfNetwProtoTotalTxIpxThe number of transmitted IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.2.1.8 |
sfrapPerfNetwProtoTotalRxSnaThe number of received SNA bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.2.1.9 |
sfrapPerfNetwProtoTotalTxSnaThe number of transmitted SNA bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.2.1.10 |
sfrapPerfNetwProtoTotalRxArpThe number of received ARP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.2.1.11 |
sfrapPerfNetwProtoTotalTxArpThe number of transmitted ARP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.2.1.12 |
sfrapPerfNetwProtoTotalRxCiscoThe number of received Cisco protocol bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.2.1.13 |
sfrapPerfNetwProtoTotalTxCiscoThe number of transmitted Cisco protocol bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.2.1.14 |
sfrapPerfNetwProtoTotalRxOtherThe 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.7.5.4.2.1.15 |
sfrapPerfNetwProtoTotalTxOtherThe 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.7.5.4.2.1.16 |
sfrapPerfNetwProtoTotalRxVnipThe number of received VNIP protocol bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.2.1.17 |
sfrapPerfNetwProtoTotalTxVnipThe number of transmitted VNIP protocol bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.2.1.18 |
sfrapPerfNetwProtoTotalRxAnnexGThe number of received Annex G protocol bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.2.1.19 |
sfrapPerfNetwProtoTotalTxAnnexGThe number of transmitted Annex G protocol bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.2.1.20 |
sfrapPerfIpPerDlciTableThe Short Term Statistics on the IP
protocol for each DLCI. SEQUENCE OF SfrapPerfIpPerDlciEntry .1.3.6.1.4.1.485.7.5.4.3 |
sfrapPerfIpPerDlciEntryThe IP Short Term Statistics for a particular DLCI. SfrapPerfIpPerDlciEntry .1.3.6.1.4.1.485.7.5.4.3.1 |
sfrapPerfIpPerDlciIntervalThe 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.7.5.4.3.1.1 |
sfrapPerfIpPerDlciValueThe DLCI value with which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.7.5.4.3.1.2 |
sfrapPerfIpPerDlciRxTotalThe total number of received IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.3.1.3 |
sfrapPerfIpPerDlciTxTotalThe total number of transmitted IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.3.1.4 |
sfrapPerfIpPerDlciRxTcpThe number of received TCP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.3.1.5 |
sfrapPerfIpPerDlciTxTcpThe number of transmitted TCP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.3.1.6 |
sfrapPerfIpPerDlciRxUdpThe number of received UDP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.3.1.7 |
sfrapPerfIpPerDlciTxUdpThe number of transmitted UDP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.3.1.8 |
sfrapPerfIpPerDlciRxIcmpThe number of received ICMP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.3.1.9 |
sfrapPerfIpPerDlciTxIcmpThe number of transmitted ICMP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.3.1.10 |
sfrapPerfIpPerDlciRxOtherThe 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.7.5.4.3.1.11 |
sfrapPerfIpPerDlciTxOtherThe 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.7.5.4.3.1.12 |
sfrapPerfIpPerDlciRxIgrpThe number of received IGRP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.3.1.13 |
sfrapPerfIpPerDlciTxIgrpThe number of transmitted IGRP over IP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.3.1.14 |
sfrapPerfIpTotalTableThe Short Term Statistics on the IP
protocol across all DLCIs. SEQUENCE OF SfrapPerfIpTotalEntry .1.3.6.1.4.1.485.7.5.4.4 |
sfrapPerfIpTotalEntryThe IP Short Term Statistics across all DLCIs. SfrapPerfIpTotalEntry .1.3.6.1.4.1.485.7.5.4.4.1 |
sfrapPerfIpTotalIntervalThe 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.7.5.4.4.1.1 |
sfrapPerfIpTotalRxTotalThe total number of received IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.4.1.3 |
sfrapPerfIpTotalTxTotalThe total number of transmitted IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.4.1.4 |
sfrapPerfIpTotalRxTcpThe number of received TCP over IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.4.1.5 |
sfrapPerfIpTotalTxTcpThe number of transmitted TCP over IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.4.1.6 |
sfrapPerfIpTotalRxUdpThe number of received UDP over IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.4.1.7 |
sfrapPerfIpTotalTxUdpThe number of transmitted UDP over IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.4.1.8 |
sfrapPerfIpTotalRxIcmpThe number of received ICMP over IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.4.1.9 |
sfrapPerfIpTotalTxIcmpThe number of transmitted ICMP over IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.4.1.10 |
sfrapPerfIpTotalRxOtherThe 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.7.5.4.4.1.11 |
sfrapPerfIpTotalTxOtherThe 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.7.5.4.4.1.12 |
sfrapPerfIpTotalRxIgrpThe number of received IGRP over IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.4.1.13 |
sfrapPerfIpTotalTxIgrpThe number of transmitted IGRP over IP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.4.1.14 |
sfrapPerfIcmpPerDlciTableShort Term Statistics on the ICMP
protocol for each DLCI. SEQUENCE OF SfrapPerfIcmpPerDlciEntry .1.3.6.1.4.1.485.7.5.4.5 |
sfrapPerfIcmpPerDlciEntryThe ICMP Short Term Statistics for a particular DLCI. SfrapPerfIcmpPerDlciEntry .1.3.6.1.4.1.485.7.5.4.5.1 |
sfrapPerfIcmpPerDlciIntervalThe 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.7.5.4.5.1.1 |
sfrapPerfIcmpPerDlciValueThe DLCI value in which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.7.5.4.5.1.2 |
sfrapPerfIcmpPerDlciRxTotalThe total number of ICMP bytes that have been
counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.5.1.3 |
sfrapPerfIcmpPerDlciTxTotalThe total number of ICMP bytes that have been
counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.5.1.4 |
sfrapPerfIcmpPerDlciRxEchoRepThe number of bytes in ICMP ECHO replies
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.5.1.5 |
sfrapPerfIcmpPerDlciTxEchoRepThe number of bytes in ICMP ECHO replies
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.5.1.6 |
sfrapPerfIcmpPerDlciRxDestUnrThe number of bytes in ICMP destination unreachables
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.5.1.7 |
sfrapPerfIcmpPerDlciTxDestUnrThe number of bytes in ICMP destination unreachables
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.5.1.8 |
sfrapPerfIcmpPerDlciRxSrcQuenchThe number of bytes in ICMP source quenches
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.5.1.9 |
sfrapPerfIcmpPerDlciTxSrcQuenchThe number of bytes in ICMP source quenches
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.5.1.10 |
sfrapPerfIcmpPerDlciRxRedirectThe number of bytes in ICMP redirects
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.5.1.11 |
sfrapPerfIcmpPerDlciTxRedirectThe number of bytes in ICMP redirects
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.5.1.12 |
sfrapPerfIcmpPerDlciRxEchoReqThe number of bytes in ICMP ECHO requests
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.5.1.13 |
sfrapPerfIcmpPerDlciTxEchoReqThe number of bytes in ICMP ECHO requests
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.5.1.14 |
sfrapPerfIcmpPerDlciRxTimeExcdThe number of bytes in ICMP time exceededs
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.5.1.15 |
sfrapPerfIcmpPerDlciTxTimeExcdThe number of bytes in ICMP time exceededs
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.5.1.16 |
sfrapPerfIcmpPerDlciRxParamProbThe number of bytes in ICMP parameter problems
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.5.1.17 |
sfrapPerfIcmpPerDlciTxParamProbThe number of bytes in ICMP parameter problems
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.5.1.18 |
sfrapPerfIcmpPerDlciRxTimestpReqThe number of bytes in ICMP timestamp requests
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.5.1.19 |
sfrapPerfIcmpPerDlciTxTimestpReqThe number of bytes in ICMP timestamp requests
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.5.1.20 |
sfrapPerfIcmpPerDlciRxTimestpRepThe number of bytes in ICMP timestamp replies
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.5.1.21 |
sfrapPerfIcmpPerDlciTxTimestpRepThe number of bytes in ICMP timestamp replies
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.5.1.22 |
sfrapPerfIcmpPerDlciRxAddrMaskReqThe number of bytes in ICMP address mask requests
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.5.1.23 |
sfrapPerfIcmpPerDlciTxAddrMaskReqThe number of bytes in ICMP address mask requests
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.5.1.24 |
sfrapPerfIcmpPerDlciRxAddrMaskRepThe number of bytes in ICMP address mask replies
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.5.1.25 |
sfrapPerfIcmpPerDlciTxAddrMaskRepThe number of bytes in ICMP address mask replies
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.5.1.26 |
sfrapPerfIcmpPerDlciRxPktTooBigThe number of bytes in ICMP packet too bigs
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.5.1.27 |
sfrapPerfIcmpPerDlciTxPktTooBigThe number of bytes in ICMP packet too bigs
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.5.1.28 |
sfrapPerfIcmpPerDlciRxGmQueryThe number of bytes in ICMP group membership
queries that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.5.1.29 |
sfrapPerfIcmpPerDlciTxGmQueryThe number of bytes in ICMP group membership
queries that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.5.1.30 |
sfrapPerfIcmpPerDlciRxGmReportThe number of bytes in ICMP group membership
reports that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.5.1.31 |
sfrapPerfIcmpPerDlciTxGmReportThe number of bytes in ICMP group membership
reports that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.5.1.32 |
sfrapPerfIcmpPerDlciRxGmReductThe number of bytes in ICMP group membership
reductions that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.5.1.33 |
sfrapPerfIcmpPerDlciTxGmReductThe number of bytes in ICMP group membership
reductions that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.5.1.34 |
sfrapPerfIcmpTotalTableShort Term Statistics on the ICMP
protocol across all DLCIs. SEQUENCE OF SfrapPerfIcmpTotalEntry .1.3.6.1.4.1.485.7.5.4.6 |
sfrapPerfIcmpTotalEntryThe ICMP Short Term Statistics for a particular DLCI. SfrapPerfIcmpTotalEntry .1.3.6.1.4.1.485.7.5.4.6.1 |
sfrapPerfIcmpTotalIntervalThe 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.7.5.4.6.1.1 |
sfrapPerfIcmpTotalRxTotalThe total number of ICMP bytes that have been
counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.6.1.3 |
sfrapPerfIcmpTotalTxTotalThe total number of ICMP bytes that have been
counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.6.1.4 |
sfrapPerfIcmpTotalRxEchoRepThe number of bytes in ICMP ECHO repies
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.6.1.5 |
sfrapPerfIcmpTotalTxEchoRepThe number of bytes in ICMP ECHO repies
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.6.1.6 |
sfrapPerfIcmpTotalRxDestUnrThe number of bytes in ICMP destination unreachables
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.6.1.7 |
sfrapPerfIcmpTotalTxDestUnrThe number of bytes in ICMP destination unreachables
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.6.1.8 |
sfrapPerfIcmpTotalRxSrcQuenchThe number of bytes in ICMP source quenches
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.6.1.9 |
sfrapPerfIcmpTotalTxSrcQuenchThe number of bytes in ICMP source quenches
that have been counte across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.6.1.10 |
sfrapPerfIcmpTotalRxRedirectThe number of bytes in ICMP redirects
that have been counte across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.6.1.11 |
sfrapPerfIcmpTotalTxRedirectThe number of bytes in ICMP redirects
that have been counte across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.6.1.12 |
sfrapPerfIcmpTotalRxEchoReqThe number of bytes in ICMP ECHO requests
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.6.1.13 |
sfrapPerfIcmpTotalTxEchoReqThe number of bytes in ICMP ECHO requests
that have been counte across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.6.1.14 |
sfrapPerfIcmpTotalRxTimeExcdThe number of bytes in ICMP time exceededs
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.6.1.15 |
sfrapPerfIcmpTotalTxTimeExcdThe number of bytes in ICMP time exceededs
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.6.1.16 |
sfrapPerfIcmpTotalRxParamProbThe number of bytes in ICMP parameter problems
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.6.1.17 |
sfrapPerfIcmpTotalTxParamProbThe number of bytes in ICMP parameter problems
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.6.1.18 |
sfrapPerfIcmpTotalRxTimestpReqThe number of bytes in ICMP timestamp requests
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.6.1.19 |
sfrapPerfIcmpTotalTxTimestpReqThe number of bytes in ICMP timestamp requests
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.6.1.20 |
sfrapPerfIcmpTotalRxTimestpRepThe number of bytes in ICMP timestamp replies
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.6.1.21 |
sfrapPerfIcmpTotalTxTimestpRepThe number of bytes in ICMP timestamp replies
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.6.1.22 |
sfrapPerfIcmpTotalRxAddrMaskReqThe number of bytes in ICMP address mask requests
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.6.1.23 |
sfrapPerfIcmpTotalTxAddrMaskReqThe number of bytes in ICMP address mask requests
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.6.1.24 |
sfrapPerfIcmpTotalRxAddrMaskRepThe number of bytes in ICMP address mask replies
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.6.1.25 |
sfrapPerfIcmpTotalTxAddrMaskRepThe number of bytes in ICMP address mask replies
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.6.1.26 |
sfrapPerfIcmpTotalRxPktTooBigThe number of bytes in ICMP packet too bigs
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.6.1.27 |
sfrapPerfIcmpTotalTxPktTooBigThe number of bytes in ICMP packet too bigs
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.6.1.28 |
sfrapPerfIcmpTotalRxGmQueryThe number of bytes in ICMP group membership
queries that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.6.1.29 |
sfrapPerfIcmpTotalTxGmQueryThe number of bytes in ICMP group membership
queries that have been counte across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.6.1.30 |
sfrapPerfIcmpTotalRxGmReportThe number of bytes in ICMP group membership
reports that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.6.1.31 |
sfrapPerfIcmpTotalTxGmReportThe number of bytes in ICMP group membership
reports that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.6.1.32 |
sfrapPerfIcmpTotalRxGmReductThe number of bytes in ICMP group membership
reductions that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.6.1.33 |
sfrapPerfIcmpTotalTxGmReductThe number of bytes in ICMP group membership
reductions that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.6.1.34 |
sfrapPerfApplicationPerDlciTableThe Short Term Statistics on the Application
protocol for each DLCI. SEQUENCE OF SfrapPerfApplicationPerDlciEntry .1.3.6.1.4.1.485.7.5.4.7 |
sfrapPerfApplicationPerDlciEntryThe Application Short Term Statistics for a particular DLCI. SfrapPerfApplicationPerDlciEntry .1.3.6.1.4.1.485.7.5.4.7.1 |
sfrapPerfApplicationPerDlciIntervalThe 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.7.5.4.7.1.1 |
sfrapPerfApplicationPerDlciValueThe DLCI value with which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.7.5.4.7.1.2 |
sfrapPerfApplicationPerDlciRxSnmpThe number of received SNMP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.7.1.3 |
sfrapPerfApplicationPerDlciTxSnmpThe number of transmitted SNMP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.7.1.4 |
sfrapPerfApplicationPerDlciRxSnmpTrapThe number of received SNMP TRAP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.7.1.5 |
sfrapPerfApplicationPerDlciTxSnmpTrapThe number of transmitted SNMP TRAP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.7.1.6 |
sfrapPerfApplicationPerDlciRxHttpThe number of received HTTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.7.1.7 |
sfrapPerfApplicationPerDlciTxHttpThe number of transmitted HTTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.7.1.8 |
sfrapPerfApplicationPerDlciRxTelnetThe number of received Telnet bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.7.1.9 |
sfrapPerfApplicationPerDlciTxTelnetThe number of transmitted Telnet bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.7.1.10 |
sfrapPerfApplicationPerDlciRxSmtpThe number of received SMTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.7.1.11 |
sfrapPerfApplicationPerDlciTxSmtpThe number of transmitted SMTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.7.1.12 |
sfrapPerfApplicationPerDlciRxFtpThe number of received FTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.7.1.13 |
sfrapPerfApplicationPerDlciTxFtpThe number of transmitted FTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.7.1.14 |
sfrapPerfApplicationPerDlciRxTftpThe number of received TFTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.7.1.15 |
sfrapPerfApplicationPerDlciTxTftpThe number of transmitted TFTP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.7.1.16 |
sfrapPerfApplicationPerDlciRxCustom1The 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.7.5.4.7.1.17 |
sfrapPerfApplicationPerDlciTxCustom1The 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.7.5.4.7.1.18 |
sfrapPerfApplicationPerDlciRxCustom2The 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.7.5.4.7.1.19 |
sfrapPerfApplicationPerDlciTxCustom2The 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.7.5.4.7.1.20 |
sfrapPerfApplicationPerDlciRxCustom3The 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.7.5.4.7.1.21 |
sfrapPerfApplicationPerDlciTxCustom3The 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.7.5.4.7.1.22 |
sfrapPerfApplicationPerDlciRxCustom4The 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.7.5.4.7.1.23 |
sfrapPerfApplicationPerDlciTxCustom4The 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.7.5.4.7.1.24 |
sfrapPerfApplicationTotalTableThe Short Term Statistics on the Application
protocol across all DLCIs. SEQUENCE OF SfrapPerfApplicationTotalEntry .1.3.6.1.4.1.485.7.5.4.8 |
sfrapPerfApplicationTotalEntryThe Application Short Term Statistics for a particular DLCI. SfrapPerfApplicationTotalEntry .1.3.6.1.4.1.485.7.5.4.8.1 |
sfrapPerfApplicationTotalIntervalThe 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.7.5.4.8.1.1 |
sfrapPerfApplicationTotalRxSnmpThe number of received SNMP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.8.1.3 |
sfrapPerfApplicationTotalTxSnmpThe number of transmitted SNMP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.8.1.4 |
sfrapPerfApplicationTotalRxSnmpTrapThe number of received SNMP TRAP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.8.1.5 |
sfrapPerfApplicationTotalTxSnmpTrapThe number of transmitted SNMP TRAP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.8.1.6 |
sfrapPerfApplicationTotalRxHttpThe number of received HTTP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.8.1.7 |
sfrapPerfApplicationTotalTxHttpThe number of transmitted HTTP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.8.1.8 |
sfrapPerfApplicationTotalRxTelnetThe number of received Telnet bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.8.1.9 |
sfrapPerfApplicationTotalTxTelnetThe number of transmitted Telnet bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.8.1.10 |
sfrapPerfApplicationTotalRxSmtpThe number of received SMTP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.8.1.11 |
sfrapPerfApplicationTotalTxSmtpThe number of transmitted SMTP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.8.1.12 |
sfrapPerfApplicationTotalRxFtpThe number of received FTP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.8.1.13 |
sfrapPerfApplicationTotalTxFtpThe number of transmitted FTP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.8.1.14 |
sfrapPerfApplicationTotalRxTftpThe number of received TFTP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.8.1.15 |
sfrapPerfApplicationTotalTxTftpThe number of transmitted TFTP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.8.1.16 |
sfrapPerfApplicationTotalRxCustom1The 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.7.5.4.8.1.17 |
sfrapPerfApplicationTotalTxCustom1The 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.7.5.4.8.1.18 |
sfrapPerfApplicationTotalRxCustom2The 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.7.5.4.8.1.19 |
sfrapPerfApplicationTotalTxCustom2The 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.7.5.4.8.1.20 |
sfrapPerfApplicationTotalRxCustom3The 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.7.5.4.8.1.21 |
sfrapPerfApplicationTotalTxCustom3The 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.7.5.4.8.1.22 |
sfrapPerfApplicationTotalRxCustom4The 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.7.5.4.8.1.23 |
sfrapPerfApplicationTotalTxCustom4The 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.7.5.4.8.1.24 |
sfrapPerfRoutingPerDlciTableThe Short Term Statistics on the Routing
protocol for each DLCI. SEQUENCE OF SfrapPerfRoutingPerDlciEntry .1.3.6.1.4.1.485.7.5.4.9 |
sfrapPerfRoutingPerDlciEntryThe Routing Short Term Statistics for a particular DLCI. SfrapPerfRoutingPerDlciEntry .1.3.6.1.4.1.485.7.5.4.9.1 |
sfrapPerfRoutingPerDlciIntervalThe 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.7.5.4.9.1.1 |
sfrapPerfRoutingPerDlciValueThe DLCI value with which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.7.5.4.9.1.2 |
sfrapPerfRoutingPerDlciRxOspfThe number of received OSPF bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.9.1.3 |
sfrapPerfRoutingPerDlciTxOspfThe number of transmitted OSPF bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.9.1.4 |
sfrapPerfRoutingPerDlciRxRipThe number of received RIP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.9.1.5 |
sfrapPerfRoutingPerDlciTxRipThe number of transmitted RIP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.9.1.6 |
sfrapPerfRoutingPerDlciRxNetbiosThe number of received Netbios bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.9.1.7 |
sfrapPerfRoutingPerDlciTxNetbiosThe number of transmitted Netbios bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.9.1.8 |
sfrapPerfRoutingTotalTableThe Short Term Statistics on the Routing
protocol across all DLCIs. SEQUENCE OF SfrapPerfRoutingTotalEntry .1.3.6.1.4.1.485.7.5.4.10 |
sfrapPerfRoutingTotalEntryThe Routing Short Term Statistics for a particular DLCI. SfrapPerfRoutingTotalEntry .1.3.6.1.4.1.485.7.5.4.10.1 |
sfrapPerfRoutingTotalIntervalThe 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.7.5.4.10.1.1 |
sfrapPerfRoutingTotalRxOspfThe number of received OSPF bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.10.1.3 |
sfrapPerfRoutingTotalTxOspfThe number of transmitted OSPF bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.10.1.4 |
sfrapPerfRoutingTotalRxRipThe number of received RIP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.10.1.5 |
sfrapPerfRoutingTotalTxRipThe number of transmitted RIP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.10.1.6 |
sfrapPerfRoutingTotalRxNetbiosThe number of received Netbios bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.10.1.7 |
sfrapPerfRoutingTotalTxNetbiosThe number of transmitted Netbios bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.10.1.8 |
sfrapPerfIpxPerDlciTableShort Term Statistics on the IPX
protocol for each DLCI. SEQUENCE OF SfrapPerfIpxPerDlciEntry .1.3.6.1.4.1.485.7.5.4.11 |
sfrapPerfIpxPerDlciEntryThe IPX Short Term Statistics for a particular DLCI. SfrapPerfIpxPerDlciEntry .1.3.6.1.4.1.485.7.5.4.11.1 |
sfrapPerfIpxPerDlciIntervalThe 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.7.5.4.11.1.1 |
sfrapPerfIpxPerDlciValueThe DLCI value in which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.7.5.4.11.1.2 |
sfrapPerfIpxPerDlciRxTotalThe total number of IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.11.1.3 |
sfrapPerfIpxPerDlciTxTotalThe total number of IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.11.1.4 |
sfrapPerfIpxPerDlciRxSpxThe number of SPX over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.11.1.5 |
sfrapPerfIpxPerDlciTxSpxThe number of SPX over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.11.1.6 |
sfrapPerfIpxPerDlciRxNcpThe number of NCP over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.11.1.7 |
sfrapPerfIpxPerDlciTxNcpThe number of NCP over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.11.1.8 |
sfrapPerfIpxPerDlciRxSapThe number of SAP over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.11.1.9 |
sfrapPerfIpxPerDlciTxSapThe number of SAP over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.11.1.10 |
sfrapPerfIpxPerDlciRxRipThe number of RIP over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.11.1.11 |
sfrapPerfIpxPerDlciTxRipThe number of RIP over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.11.1.12 |
sfrapPerfIpxPerDlciRxNetbiosThe number of NETBIOS over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.11.1.13 |
sfrapPerfIpxPerDlciTxNetbiosThe number of NETBIOS over IPX bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.11.1.14 |
sfrapPerfIpxPerDlciRxOtherThe 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.7.5.4.11.1.15 |
sfrapPerfIpxPerDlciTxOtherThe 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.7.5.4.11.1.16 |
sfrapPerfIpxTotalTableShort Term Statistics on the IPX
protocol across all DLCIs. SEQUENCE OF SfrapPerfIpxTotalEntry .1.3.6.1.4.1.485.7.5.4.12 |
sfrapPerfIpxTotalEntryThe IPX Short Term Statistics for a particular DLCI. SfrapPerfIpxTotalEntry .1.3.6.1.4.1.485.7.5.4.12.1 |
sfrapPerfIpxTotalIntervalThe 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.7.5.4.12.1.1 |
sfrapPerfIpxTotalRxTotalThe total number of IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.12.1.3 |
sfrapPerfIpxTotalTxTotalThe total number of IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.12.1.4 |
sfrapPerfIpxTotalRxSpxThe number of SPX over IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.12.1.5 |
sfrapPerfIpxTotalTxSpxThe number of SPX over IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.12.1.6 |
sfrapPerfIpxTotalRxNcpThe number of NCP over IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.12.1.7 |
sfrapPerfIpxTotalTxNcpThe number of NCP over IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.12.1.8 |
sfrapPerfIpxTotalRxSapThe number of SAP over IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.12.1.9 |
sfrapPerfIpxTotalTxSapThe number of SAP over IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.12.1.10 |
sfrapPerfIpxTotalRxRipThe number of RIP over IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.12.1.11 |
sfrapPerfIpxTotalTxRipThe number of RIP over IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.12.1.12 |
sfrapPerfIpxTotalRxNetbiosThe number of NETBIOS over IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.12.1.13 |
sfrapPerfIpxTotalTxNetbiosThe number of NETBIOS over IPX bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.12.1.14 |
sfrapPerfIpxTotalRxOtherThe 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.7.5.4.12.1.15 |
sfrapPerfIpxTotalTxOtherThe 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.7.5.4.12.1.16 |
sfrapPerfSnaPerDlciTableShort Term Statistics on the SNA
protocol for each DLCI. SEQUENCE OF SfrapPerfSnaPerDlciEntry .1.3.6.1.4.1.485.7.5.4.13 |
sfrapPerfSnaPerDlciEntryThe SNA Short Term Statistics for a particular DLCI. SfrapPerfSnaPerDlciEntry .1.3.6.1.4.1.485.7.5.4.13.1 |
sfrapPerfSnaPerDlciIntervalThe 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.7.5.4.13.1.1 |
sfrapPerfSnaPerDlciValueThe DLCI value in which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.7.5.4.13.1.2 |
sfrapPerfSnaPerDlciRxTotalThe total number of SNA bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.13.1.3 |
sfrapPerfSnaPerDlciTxTotalThe total number of SNA bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.13.1.4 |
sfrapPerfSnaPerDlciRxSubareaThe number of SNA Subarea bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.13.1.5 |
sfrapPerfSnaPerDlciTxSubareaThe number of SNA Subarea bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.13.1.6 |
sfrapPerfSnaPerDlciRxPeriphThe number of SNA Periph bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.13.1.7 |
sfrapPerfSnaPerDlciTxPeriphThe number of SNA Periph bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.13.1.8 |
sfrapPerfSnaPerDlciRxAppnThe number of SNA Appn bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.13.1.9 |
sfrapPerfSnaPerDlciTxAppnThe number of SNA Appn bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.13.1.10 |
sfrapPerfSnaPerDlciRxNetbiosThe number of SNA Netbios bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.13.1.11 |
sfrapPerfSnaPerDlciTxNetbiosThe number of SNA Netbios bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.13.1.12 |
sfrapPerfSnaPerDlciRxOtherThe 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.7.5.4.13.1.13 |
sfrapPerfSnaPerDlciTxOtherThe 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.7.5.4.13.1.14 |
sfrapPerfSnaTotalTableShort Term Statistics on the SNA
protocol across all DLCIs. SEQUENCE OF SfrapPerfSnaTotalEntry .1.3.6.1.4.1.485.7.5.4.14 |
sfrapPerfSnaTotalEntryThe SNA Short Term Statistics for a particular DLCI. SfrapPerfSnaTotalEntry .1.3.6.1.4.1.485.7.5.4.14.1 |
sfrapPerfSnaTotalIntervalThe 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.7.5.4.14.1.1 |
sfrapPerfSnaTotalRxTotalThe total number of SNA bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.14.1.3 |
sfrapPerfSnaTotalTxTotalThe total number of SNA bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.14.1.4 |
sfrapPerfSnaTotalRxSubareaThe number of SNA Subarea bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.14.1.5 |
sfrapPerfSnaTotalTxSubareaThe number of SNA Subarea bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.14.1.6 |
sfrapPerfSnaTotalRxPeriphThe number of SNA Periph bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.14.1.7 |
sfrapPerfSnaTotalTxPeriphThe number of SNA Periph bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.14.1.8 |
sfrapPerfSnaTotalRxAppnThe number of SNA Appn bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.14.1.9 |
sfrapPerfSnaTotalTxAppnThe number of SNA Appn bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.14.1.10 |
sfrapPerfSnaTotalRxNetbiosThe number of SNA Netbios bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.14.1.11 |
sfrapPerfSnaTotalTxNetbiosThe number of SNA Netbios bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.14.1.12 |
sfrapPerfSnaTotalRxOtherThe 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.7.5.4.14.1.13 |
sfrapPerfSnaTotalTxOtherThe 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.7.5.4.14.1.14 |
sfrapPerfArpPerDlciTableShort Term Statistics on the ARP
protocol for each DLCI. SEQUENCE OF SfrapPerfArpPerDlciEntry .1.3.6.1.4.1.485.7.5.4.15 |
sfrapPerfArpPerDlciEntryThe ARP Short Term Statistics for a particular DLCI. SfrapPerfArpPerDlciEntry .1.3.6.1.4.1.485.7.5.4.15.1 |
sfrapPerfArpPerDlciIntervalThe 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.7.5.4.15.1.1 |
sfrapPerfArpPerDlciValueThe DLCI value in which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.7.5.4.15.1.2 |
sfrapPerfArpPerDlciRxTotalThe total number of ARP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.15.1.3 |
sfrapPerfArpPerDlciTxTotalThe total number of ARP bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.15.1.4 |
sfrapPerfArpPerDlciRxArpReqThe number of ARP request bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.15.1.5 |
sfrapPerfArpPerDlciTxArpReqThe number of ARP request bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.15.1.6 |
sfrapPerfArpPerDlciRxArpRepThe number of ARP reply bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.15.1.7 |
sfrapPerfArpPerDlciTxArpRepThe number of ARP reply bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.15.1.8 |
sfrapPerfArpPerDlciRxRarpReqThe number of RARP request bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.15.1.9 |
sfrapPerfArpPerDlciTxRarpReqThe number of RARP request bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.15.1.10 |
sfrapPerfArpPerDlciRxRarpRepThe number of RARP reply bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.15.1.11 |
sfrapPerfArpPerDlciTxRarpRepThe number of RARP reply bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.15.1.12 |
sfrapPerfArpPerDlciRxInarpReqThe number of INARP request bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.15.1.13 |
sfrapPerfArpPerDlciTxInarpReqThe number of INARP request bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.15.1.14 |
sfrapPerfArpPerDlciRxInarpRepThe number of INARP reply bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.15.1.15 |
sfrapPerfArpPerDlciTxInarpRepThe number of INARP reply bytes
that have been counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.15.1.16 |
sfrapPerfArpPerDlciRxOtherThe 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.7.5.4.15.1.17 |
sfrapPerfArpPerDlciTxOtherThe 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.7.5.4.15.1.18 |
sfrapPerfArpTotalTableShort Term Statistics on the ARP
protocol across all DLCIs. SEQUENCE OF SfrapPerfArpTotalEntry .1.3.6.1.4.1.485.7.5.4.16 |
sfrapPerfArpTotalEntryThe ARP Short Term Statistics for a particular DLCI. SfrapPerfArpTotalEntry .1.3.6.1.4.1.485.7.5.4.16.1 |
sfrapPerfArpTotalIntervalThe 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.7.5.4.16.1.1 |
sfrapPerfArpTotalRxTotalThe total number of ARP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.16.1.3 |
sfrapPerfArpTotalTxTotalThe total number of ARP bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.16.1.4 |
sfrapPerfArpTotalRxArpReqThe number of ARP request bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.16.1.5 |
sfrapPerfArpTotalTxArpReqThe number of ARP request bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.16.1.6 |
sfrapPerfArpTotalRxArpRepThe number of ARP reply bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.16.1.7 |
sfrapPerfArpTotalTxArpRepThe number of ARP reply bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.16.1.8 |
sfrapPerfArpTotalRxRarpReqThe number of RARP request bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.16.1.9 |
sfrapPerfArpTotalTxRarpReqThe number of RARP request bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.16.1.10 |
sfrapPerfArpTotalRxRarpRepThe number of RARP reply bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.16.1.11 |
sfrapPerfArpTotalTxRarpRepThe number of RARP reply bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.16.1.12 |
sfrapPerfArpTotalRxInarpReqThe number of INARP request bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.16.1.13 |
sfrapPerfArpTotalTxInarpReqThe number of INARP request bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.16.1.14 |
sfrapPerfArpTotalRxInarpRepThe number of INARP reply bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.16.1.15 |
sfrapPerfArpTotalTxInarpRepThe number of INARP reply bytes
that have been counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.16.1.16 |
sfrapPerfArpTotalRxOtherThe 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.7.5.4.16.1.17 |
sfrapPerfArpTotalTxOtherThe 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.7.5.4.16.1.18 |
sfrapPerfLmiPerDlciTableShort Term Statistics on LMI protocol for each DLCI. SEQUENCE OF SfrapPerfLmiPerDlciEntry .1.3.6.1.4.1.485.7.5.4.17 |
sfrapPerfLmiPerDlciEntryThe LMI Short Term Statistics for a particular DLCI. SfrapPerfLmiPerDlciEntry .1.3.6.1.4.1.485.7.5.4.17.1 |
sfrapPerfLmiPerDlciIntervalThe 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.7.5.4.17.1.1 |
sfrapPerfLmiPerDlciValueThe DLCI value with which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.7.5.4.17.1.2 |
sfrapPerfLmiPerDlciRxTotalByteCntThe total number of received LMI bytes
counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.17.1.3 |
sfrapPerfLmiPerDlciTxTotalByteCntThe total number of transmitted LMI bytes
counted on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.17.1.4 |
sfrapPerfLmiPerDlciRxLivoEnqByteCntThe number of bytes received in Link Integrity
Verification Only (LIVO) enquiries on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.17.1.5 |
sfrapPerfLmiPerDlciTxLivoEnqByteCntThe number of bytes transmitted in Link Integrity
Verification Only (LIVO) enquiries on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.17.1.6 |
sfrapPerfLmiPerDlciRxLivoStatByteCntThe number of bytes received in Link Integrity
Verification Only (LIVO) statuses on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.17.1.7 |
sfrapPerfLmiPerDlciTxLivoStatByteCntThe number of bytes transmitted in Link Integrity
Verification Only (LIVO) statuses on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.17.1.8 |
sfrapPerfLmiPerDlciRxFullEnqByteCntThe number of bytes received in
Full Status enquiries on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.17.1.9 |
sfrapPerfLmiPerDlciTxFullEnqByteCntThe number of bytes transmitted in
Full Status enquiries on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.17.1.10 |
sfrapPerfLmiPerDlciRxFullStatByteCntThe number of bytes received in
Full Status messages on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.17.1.11 |
sfrapPerfLmiPerDlciTxFullStatByteCntThe number of bytes transmitted in
Full Status messages on this DLCI.ro Counter .1.3.6.1.4.1.485.7.5.4.17.1.12 |
sfrapPerfLmiPerDlciRxOtherByteCntThe 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.7.5.4.17.1.13 |
sfrapPerfLmiPerDlciTxOtherByteCntThe 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.7.5.4.17.1.14 |
sfrapPerfLmiTotalTableShort Term Statistics on LMI protocol across all DLCIs. SEQUENCE OF SfrapPerfLmiTotalEntry .1.3.6.1.4.1.485.7.5.4.18 |
sfrapPerfLmiTotalEntryThe LMI Short Term Statistics across all DLCIs. SfrapPerfLmiTotalEntry .1.3.6.1.4.1.485.7.5.4.18.1 |
sfrapPerfLmiTotalIntervalThe 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.7.5.4.18.1.1 |
sfrapPerfLmiTotalDlciValueOBSOLETE.ro INTEGER .1.3.6.1.4.1.485.7.5.4.18.1.2 |
sfrapPerfLmiTotalRxTotalByteCntThe total number of received LMI bytes
counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.18.1.3 |
sfrapPerfLmiTotalTxTotalByteCntThe total number of transmitted LMI bytes
counted across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.18.1.4 |
sfrapPerfLmiTotalRxLivoEnqByteCntThe number of bytes received in Link Integrity
Verification Only (LIVO) enquiries across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.18.1.5 |
sfrapPerfLmiTotalTxLivoEnqByteCntThe number of bytes transmitted in Link Integrity
Verification Only (LIVO) enquiries across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.18.1.6 |
sfrapPerfLmiTotalRxLivoStatByteCntThe number of bytes received in Link Integrity
Verification Only (LIVO) enquiries across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.18.1.7 |
sfrapPerfLmiTotalTxLivoStatByteCntThe number of bytes transmitted in Link Integrity
Verification Only (LIVO) enquiries across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.18.1.8 |
sfrapPerfLmiTotalRxFullEnqByteCntThe number of bytes received in
Full Status enquiries across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.18.1.9 |
sfrapPerfLmiTotalTxFullEnqByteCntThe number of bytes transmitted in
Full Status enquiries across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.18.1.10 |
sfrapPerfLmiTotalRxFullStatByteCntThe number of bytes received in
Full Status messages across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.18.1.11 |
sfrapPerfLmiTotalTxFullStatByteCntThe number of bytes transmitted in
Full Status messages across all DLCIs.ro Counter .1.3.6.1.4.1.485.7.5.4.18.1.12 |
sfrapPerfLmiTotalRxOtherByteCntThe number of received bytes across all DLCIs
from LMI protocols that are not counted
elsewhere (other than Total) in this table.ro Counter .1.3.6.1.4.1.485.7.5.4.18.1.13 |
sfrapPerfLmiTotalTxOtherByteCntThe number of transmitted bytes across all DLCIs
from LMI protocols that are not counted
elsewhere (other than Total) in this table.ro Counter .1.3.6.1.4.1.485.7.5.4.18.1.14 |
sfrapPerfNetworkLongTerm OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.5.5 |
sfrapPerfNetwLongTermTableLong Term Statistics by DLCI, protocol, and interval.
LT statistics are collected on a configurable set
of DLCIs and protocols. There are 96 intervals maintained
each with a duration defined by the Long Term Timer.
Interval 96 is the current window and Interval 1 is
furthest back in time (96xLT Timer seconds ago). SEQUENCE OF SfrapPerfNetwLongTermEntry .1.3.6.1.4.1.485.7.5.5.1 |
sfrapPerfNetwLongTermEntryThe Long Term Statistic for a particular DLCI,
protocol and interval. SfrapPerfNetwLongTermEntry .1.3.6.1.4.1.485.7.5.5.1.1 |
sfrapPerfNetwLongTermDlciThe DLCI monitored for the statistics. The Long
Term DLCI filter must first be configured
(CfgFrPerfLTDlciFilterEntry).ro INTEGER .1.3.6.1.4.1.485.7.5.5.1.1.1 |
sfrapPerfNetwLongTermProtocolThe type of protocol monitored for the statistics.ro Enumeration .1.3.6.1.4.1.485.7.5.5.1.1.2 |
sfrapPerfNetwLongTermIntervalThe 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.7.5.5.1.1.3 |
sfrapPerfNetwLongTermValueThe statistic collected for the given DLCI and protocol
and within the given time interval.ro Counter .1.3.6.1.4.1.485.7.5.5.1.1.4 |
sfrapPerfNetwLongTermAltTableThis 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 SfrapPerfNetwLongTermAltEntry .1.3.6.1.4.1.485.7.5.5.2 |
sfrapPerfNetwLongTermAltEntryThe Long Term Statistic for a particular
DLCI and protocol. SfrapPerfNetwLongTermAltEntry .1.3.6.1.4.1.485.7.5.5.2.1 |
sfrapPerfNetwLongTermAltDlciThe DLCI monitored for the statistics.ro INTEGER .1.3.6.1.4.1.485.7.5.5.2.1.1 |
sfrapPerfNetwLongTermAltProtocolThe protocol monitored for the statistics.ro Enumeration .1.3.6.1.4.1.485.7.5.5.2.1.2 |
sfrapPerfNetwLongTermAltArrayThe statistic collected for the given DLCI and protocol.ro OCTET STRING .1.3.6.1.4.1.485.7.5.5.2.1.3 |
sfrapPerfNetworkLongTermCommands OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.5.5.3 |
sfrapPerfNetworkLongTermCmdClearAllows 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.7.5.5.3.1 |
sfrapPerfCirPercentUtilization OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.5.6 |
sfrapPerfCirPercentUtilizationTableShort 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 SfrapPerfCirPercentUtilizationEntry .1.3.6.1.4.1.485.7.5.6.1 |
sfrapPerfCirPercentUtilizationEntryThe CIR Percentage Statistics for a particular DLCI.
These calculations are done at the completion of each
Short Term interval. SfrapPerfCirPercentUtilizationEntry .1.3.6.1.4.1.485.7.5.6.1.1 |
sfrapPerfCirPercentUtilizationIntervalThe 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.7.5.6.1.1.1 |
sfrapPerfCirPercentUtilizationDlciValueThe DLCI value with which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.7.5.6.1.1.2 |
sfrapPerfCirRxPercentUtilizationRange1The number of short-term intervals during
which rx data throughput on this DLCI compared
to CIR was in range 1 (0% of CIR).ro INTEGER .1.3.6.1.4.1.485.7.5.6.1.1.21 |
sfrapPerfCirRxPercentUtilizationRange2The number of short-term intervals during
which rx data throughput on this DLCI compared
to CIR was in range 2 (1-10% of CIR).ro INTEGER .1.3.6.1.4.1.485.7.5.6.1.1.22 |
sfrapPerfCirRxPercentUtilizationRange3The number of short-term intervals during
which rx data throughput on this DLCI compared
to CIR was in range 3 (11-20% of CIR).ro INTEGER .1.3.6.1.4.1.485.7.5.6.1.1.23 |
sfrapPerfCirRxPercentUtilizationRange4The number of short-term intervals during
which rx data throughput on this DLCI compared
to CIR was in range 4 (21-50% of CIR).ro INTEGER .1.3.6.1.4.1.485.7.5.6.1.1.24 |
sfrapPerfCirRxPercentUtilizationRange5The number of short-term intervals during
which rx data throughput on this DLCI compared
to CIR was in range 5 (51-80% of CIR).ro INTEGER .1.3.6.1.4.1.485.7.5.6.1.1.25 |
sfrapPerfCirRxPercentUtilizationRange6The number of short-term intervals during
which rx data throughput on this DLCI compared
to CIR was in range 6 (81-100% of CIR).ro INTEGER .1.3.6.1.4.1.485.7.5.6.1.1.26 |
sfrapPerfCirRxPercentUtilizationRange7The number of short-term intervals during
which rx data throughput on this DLCI compared
to CIR was in range 7 (101-150% of CIR).ro INTEGER .1.3.6.1.4.1.485.7.5.6.1.1.27 |
sfrapPerfCirRxPercentUtilizationRange8The number of short-term intervals during
which rx data throughput on this DLCI compared
to CIR was in range 8 (> 150% of CIR).ro INTEGER .1.3.6.1.4.1.485.7.5.6.1.1.28 |
sfrapPerfCirTxPercentUtilizationRange1The number of short-term intervals during
which tx data throughput on this DLCI compared
to CIR was in range 1 (0% of CIR).ro INTEGER .1.3.6.1.4.1.485.7.5.6.1.1.41 |
sfrapPerfCirTxPercentUtilizationRange2The number of short-term intervals during
which tx data throughput on this DLCI compared
to CIR was in range 2 (1-10% of CIR).ro INTEGER .1.3.6.1.4.1.485.7.5.6.1.1.42 |
sfrapPerfCirTxPercentUtilizationRange3The number of short-term intervals during
which tx data throughput on this DLCI compared
to CIR was in range 3 (11-20% of CIR).ro INTEGER .1.3.6.1.4.1.485.7.5.6.1.1.43 |
sfrapPerfCirTxPercentUtilizationRange4The number of short-term intervals during
which tx data throughput on this DLCI compared
to CIR was in range 4 (21-50% of CIR).ro INTEGER .1.3.6.1.4.1.485.7.5.6.1.1.44 |
sfrapPerfCirTxPercentUtilizationRange5The number of short-term intervals during
which tx data throughput on this DLCI compared
to CIR was in range 5 (51-80% of CIR).ro INTEGER .1.3.6.1.4.1.485.7.5.6.1.1.45 |
sfrapPerfCirTxPercentUtilizationRange6The number of short-term intervals during
which tx data throughput on this DLCI compared
to CIR was in range 6 (81-100% o0f CIR).ro INTEGER .1.3.6.1.4.1.485.7.5.6.1.1.46 |
sfrapPerfCirTxPercentUtilizationRange7The number of short-term intervals during
which tx data throughput on this DLCI compared
to CIR was in range 7 (101-150% of CIR).ro INTEGER .1.3.6.1.4.1.485.7.5.6.1.1.47 |
sfrapPerfCirTxPercentUtilizationRange8The number of short-term intervals during
which tx data throughput on this DLCI compared
to CIR was in range 8 (> 150% of CIR).ro INTEGER .1.3.6.1.4.1.485.7.5.6.1.1.48 |
sfrapPerfCurrentPerDlciUtilizationTableThe 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 SfrapPerfCurrentPerDlciUtilizationEntry .1.3.6.1.4.1.485.7.5.6.2 |
sfrapPerfCurrentPerDlciUtilizationEntryThe utilization statistics for a particular DLCI. SfrapPerfCurrentPerDlciUtilizationEntry .1.3.6.1.4.1.485.7.5.6.2.1 |
sfrapPerfCurrentPerDlciUtilizationDlciValueThe DLCI value with which the Statistics are associated.ro INTEGER .1.3.6.1.4.1.485.7.5.6.2.1.1 |
sfrapPerfCurrentPerDlciRxUtilizationThe receive direction utilization as a
percentage of CIR.ro INTEGER .1.3.6.1.4.1.485.7.5.6.2.1.2 |
sfrapPerfCurrentPerDlciTxUtilizationThe transmit direction utilization as a
percentage of CIR.ro INTEGER .1.3.6.1.4.1.485.7.5.6.2.1.3 |
sfrapPerfCurrentPerDlciAggregateUtilizationThe aggregate utilization, the average
of the receive and transmit utilization
as a percentage of CIR.ro INTEGER .1.3.6.1.4.1.485.7.5.6.2.1.4 |
sfrapPerfCurrentUnitUtilization OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.5.6.3 |
sfrapPerfCurrentDteUtilizationThe DTE interface utilization as a
percentage of line rate.ro INTEGER .1.3.6.1.4.1.485.7.5.6.3.2 |
sfrapPerfCurrentWanUtilizationThe WAN interface utilization as a
percentage of line rate.ro INTEGER .1.3.6.1.4.1.485.7.5.6.3.3 |
sfrapPerfCurrentAggregateUtilizationThe 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.7.5.6.3.4 |
sfrapPerfFRStatsCollectionStatus OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.5.7 |
sfrapPerfFRStatsCollectionTells the GUI whether or not the Frame Relay Performance
statistics are valid or not. This is a SFRAP Low Speed
option, if the user's network bandwidth has exceeded the
Low Speed boundary, then it is set to not-collecting-stats (1)
all other cases it is set to collecting-stats (2).ro Enumeration .1.3.6.1.4.1.485.7.5.7.1 |
sfrapAlarmTypeThe alarm type of the most recent TRAP generated.ro Enumeration .1.3.6.1.4.1.485.7.6 |
sfrapDLCINumThe DLCI number for the most recent DLCI TRAP generated.ro INTEGER .1.3.6.1.4.1.485.7.7 |
sfrapInterfaceThe interface most recently reported in a TRAP.ro Enumeration .1.3.6.1.4.1.485.7.8 |
sfrapIpAddressThe IP address most recently reported in a TRAP.ro IpAddress .1.3.6.1.4.1.485.7.9 |
sfrapEventTrapLog OBJECT IDENTIFIER .1.3.6.1.4.1.485.7.10 |
sfrapEventTrapLogTableThis table contains the Event/Trap log. The entries are
indexed by sequence number. SEQUENCE OF SFRAPEventTrapLogEntry .1.3.6.1.4.1.485.7.10.1 |
sfrapEventTrapLogEntryThe event record for a particular event. SFRAPEventTrapLogEntry .1.3.6.1.4.1.485.7.10.1.1 |
sfrapEventTrapLogSeqNumThe sequence number associated with an event record.ro INTEGER .1.3.6.1.4.1.485.7.10.1.1.1 |
sfrapEventTrapLogGenericEventThe SNMP generic trap or event number.ro INTEGER .1.3.6.1.4.1.485.7.10.1.1.2 |
sfrapEventTrapLogSpecificEventThe SNMP specific trap or event sub-identifier number.ro INTEGER .1.3.6.1.4.1.485.7.10.1.1.3 |
sfrapEventTrapLogTimeStampThe SNMP trap timestamp.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.485.7.10.1.1.4 |
sfrapEventTrapLogVarBind1Variable Binding 1 for this SNMP Trap event.ro INTEGER .1.3.6.1.4.1.485.7.10.1.1.5 |
sfrapEventTrapLogVarBind2Variable Binding 2 for this SNMP Trap event.ro INTEGER .1.3.6.1.4.1.485.7.10.1.1.6 |
sfrapEventTrapLogVarBind3Variable Binding 3 for this SNMP Trap event.ro INTEGER .1.3.6.1.4.1.485.7.10.1.1.7 |
sfrapEventLogAltTableThis 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 SFRAPEventLogAltEntry .1.3.6.1.4.1.485.7.10.2 |
sfrapEventLogAltEntryThe Event/Trap Log for a particular sequence number. SFRAPEventLogAltEntry .1.3.6.1.4.1.485.7.10.2.1 |
sfrapEventLogAltSeqNumThe Sequence Number monitored for the Event Logro INTEGER .1.3.6.1.4.1.485.7.10.2.1.1 |
sfrapEventLogAltArrayThe Event / Trap log for the given sequence number.ro OCTET STRING .1.3.6.1.4.1.485.7.10.2.1.2 |
sfrapEventLogCurrentSeqNumThe current index into the Event Log Table.ro INTEGER .1.3.6.1.4.1.485.7.10.3 |
sfrapEventLogFreezeThis 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.7.10.4 |
sfrapEventLogClearThis clears the Event/Trap Log.rw Enumeration .1.3.6.1.4.1.485.7.10.5 |
sfrapPercentUtilizationThe percent utilization for a DLCI most recently
reported in a TRAP.ro INTEGER .1.3.6.1.4.1.485.7.11 |
sfrapUtilizationThresholdThe percent utilization threshold for a DLCI most
recently reported in a TRAP.ro INTEGER .1.3.6.1.4.1.485.7.12 |
sfrapCfgLockIpAddressThe IP address of the management station locking
the configuration most recently reported in a TRAP.ro INTEGER .1.3.6.1.4.1.485.7.13 |