FRSLD-MIB

        The MIB module to describe generic objects for
FRF.13 Frame Relay Service Level Definitions.
    
Source file
FRSLD-MIB
Last revised
Identity
frsldMIB
Base OID
1.3.6.1.2.1.95
Imported Objects
FRAME-RELAY-DTE-MIB DLCI
HCNUM-TC CounterBasedGauge64
IF-MIB ifIndex
SNMPv2-CONF MODULE-COMPLIANCE (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter32 Counter64 Gauge32 Integer32 mib-2 MODULE-IDENTITY (no object page) OBJECT-TYPE (no object page) TimeTicks
SNMPv2-TC RowStatus TEXTUAL-CONVENTION (no object page) TimeStamp
Net-SNMP examples using the rfc MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'FRSLD-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'FRSLD-MIB::frsldMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'FRSLD-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'FRSLD-MIB::frsldMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (81)
.1.3.6.1.2.1.95
.1.3.6.1.2.1.95.1
.1.3.6.1.2.1.95.1.1
.1.3.6.1.2.1.95.1.1.1
.1.3.6.1.2.1.95.1.1.1.1
Enumeration
.1.3.6.1.2.1.95.1.1.1.10
.1.3.6.1.2.1.95.1.1.1.11
.1.3.6.1.2.1.95.1.1.1.2
.1.3.6.1.2.1.95.1.1.1.3
.1.3.6.1.2.1.95.1.1.1.4
secondsInteger32
.1.3.6.1.2.1.95.1.1.1.5
octetsInteger32
.1.3.6.1.2.1.95.1.1.1.6
Enumeration
.1.3.6.1.2.1.95.1.1.1.7
secondsInteger32
.1.3.6.1.2.1.95.1.1.1.8
secondsInteger32
.1.3.6.1.2.1.95.1.1.1.9
.1.3.6.1.2.1.95.1.2
.1.3.6.1.2.1.95.1.2.1
Integer32
.1.3.6.1.2.1.95.1.2.1.1
.1.3.6.1.2.1.95.1.2.1.2
secondsInteger32
.1.3.6.1.2.1.95.1.2.1.3
Integer32
.1.3.6.1.2.1.95.1.2.1.4
Integer32
.1.3.6.1.2.1.95.1.2.1.5
.1.3.6.1.2.1.95.1.3
.1.3.6.1.2.1.95.1.3.1
.1.3.6.1.2.1.95.1.3.1.1
.1.3.6.1.2.1.95.1.3.1.10
.1.3.6.1.2.1.95.1.3.1.11
.1.3.6.1.2.1.95.1.3.1.12
.1.3.6.1.2.1.95.1.3.1.13
.1.3.6.1.2.1.95.1.3.1.14
.1.3.6.1.2.1.95.1.3.1.15
.1.3.6.1.2.1.95.1.3.1.16
.1.3.6.1.2.1.95.1.3.1.17
.1.3.6.1.2.1.95.1.3.1.18
.1.3.6.1.2.1.95.1.3.1.19
.1.3.6.1.2.1.95.1.3.1.2
.1.3.6.1.2.1.95.1.3.1.3
.1.3.6.1.2.1.95.1.3.1.4
.1.3.6.1.2.1.95.1.3.1.5
.1.3.6.1.2.1.95.1.3.1.6
.1.3.6.1.2.1.95.1.3.1.7
.1.3.6.1.2.1.95.1.3.1.8
.1.3.6.1.2.1.95.1.3.1.9
.1.3.6.1.2.1.95.1.4
.1.3.6.1.2.1.95.1.4.1
Integer32
.1.3.6.1.2.1.95.1.4.1.1
.1.3.6.1.2.1.95.1.4.1.10
.1.3.6.1.2.1.95.1.4.1.11
.1.3.6.1.2.1.95.1.4.1.12
.1.3.6.1.2.1.95.1.4.1.13
.1.3.6.1.2.1.95.1.4.1.14
.1.3.6.1.2.1.95.1.4.1.15
.1.3.6.1.2.1.95.1.4.1.16
.1.3.6.1.2.1.95.1.4.1.17
.1.3.6.1.2.1.95.1.4.1.18
.1.3.6.1.2.1.95.1.4.1.19
microsecondsSNMPv2-SMIGauge32
.1.3.6.1.2.1.95.1.4.1.2
.1.3.6.1.2.1.95.1.4.1.20
.1.3.6.1.2.1.95.1.4.1.21
.1.3.6.1.2.1.95.1.4.1.22
.1.3.6.1.2.1.95.1.4.1.23
.1.3.6.1.2.1.95.1.4.1.24
.1.3.6.1.2.1.95.1.4.1.25
microsecondsSNMPv2-SMIGauge32
.1.3.6.1.2.1.95.1.4.1.3
microsecondsSNMPv2-SMIGauge32
.1.3.6.1.2.1.95.1.4.1.4
.1.3.6.1.2.1.95.1.4.1.5
.1.3.6.1.2.1.95.1.4.1.6
.1.3.6.1.2.1.95.1.4.1.7
.1.3.6.1.2.1.95.1.4.1.8
.1.3.6.1.2.1.95.1.4.1.9
.1.3.6.1.2.1.95.2
Bits
.1.3.6.1.2.1.95.2.1
Bits
.1.3.6.1.2.1.95.2.2
Bits
.1.3.6.1.2.1.95.2.3
Integer32
.1.3.6.1.2.1.95.2.4
.1.3.6.1.2.1.95.2.5
Integer32
.1.3.6.1.2.1.95.2.6
.1.3.6.1.2.1.95.2.7
.1.3.6.1.2.1.95.3
.1.3.6.1.2.1.95.3.1
.1.3.6.1.2.1.95.3.2
Dependencies (11) 6 direct · 5 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Type Definitions (2)
Enumeration
desLocalRP(1)
ingRxLocalRP(2)
tpRxLocalRP(3)
eqiRxLocalRP(4)
eqoRxLocalRP(5)
otherRxLocalRP(6)
desRemoteRP(7)
ingRxRemoteRP(8)
tpRxRemoteRP(9)
eqiRxRemoteRP(10)
eqoRxRemoteRP(11)
otherRxRemoteRP(12)
Enumeration
srcLocalRP(1)
ingTxLocalRP(2)
tpTxLocalRP(3)
eqiTxLocalRP(4)
eqoTxLocalRP(5)
otherTxLocalRP(6)
srcRemoteRP(7)
ingTxRemoteRP(8)
tpTxRemoteRP(9)
eqiTxRemoteRP(10)
eqoTxRemoteRP(11)
otherTxRemoteRP(12)
Conformance Groups (15)
A collection of required objects providing
control information applicable to a PVC which
implements Service Level Definitions.
.1.3.6.1.2.1.95.3.1.1
A collection of optional objects providing packet
level control information applicable to a PVC which
implements Service Level Definitions.
.1.3.6.1.2.1.95.3.1.2
A collection of optional objects providing delay
control information applicable to a PVC which
implements Service Level Definitions.

If this group is implemented, frsldPvcPacketGroup
and frsldPvcDelayDataGroup MUST also be implemented.
.1.3.6.1.2.1.95.3.1.3
A collection of optional objects providing sample
control information applicable to a PVC which
implements Service Level Definitions.

If this group is implemented, frsldPvcReqDataGroup
and frsldPvcSampleGeneralGroup MUST also be
implemented.
.1.3.6.1.2.1.95.3.1.4
A collection of required objects providing data
collected on a PVC which implements Service
Level Definitions.
.1.3.6.1.2.1.95.3.1.5
A collection of optional objects providing delay
data collected on a PVC which implements Service
Level Definitions.

If this group is implemented, frsldPvcDelayCtrlGroup
MUST also be implemented.
.1.3.6.1.2.1.95.3.1.6
A collection of optional objects providing high
capacity frame data collected on a PVC which
implements Service Level Definitions.
.1.3.6.1.2.1.95.3.1.7
A collection of optional objects providing high
capacity octet data collected on a PVC which
implements Service Level Definitions.
.1.3.6.1.2.1.95.3.1.8
A collection of optional objects providing delay
sample data collected on a PVC which implements
Service Level Definitions.

If this group is implemented, frsldPvcDelayCtrlGroup
MUST also be implemented.
.1.3.6.1.2.1.95.3.1.9
A collection of optional objects providing data
and frame delivery sample data collected on a PVC
which implements Service Level Definitions.

If this group is implemented, frsldPvcReqDataGroup
MUST also be implemented.
.1.3.6.1.2.1.95.3.1.10
A collection of optional objects providing high
capacity frame delivery sample data collected on a PVC
which implements Service Level Definitions.

If this group is implemented, frsldPvcHCFrameDataGroup
MUST also be implemented.
.1.3.6.1.2.1.95.3.1.11
A collection of optional objects providing high
capacity data delivery sample data collected on a PVC
which implements Service Level Definitions.

If this group is implemented, frsldPvcHCOctetDataGroup

MUST also be implemented.
.1.3.6.1.2.1.95.3.1.12
A collection of optional objects providing
availability sample data collected on a PVC which
implements Service Level Definitions.

If this group is implemented, frsldPvcReqDataGroup
MUST also be implemented.
.1.3.6.1.2.1.95.3.1.13
A collection of optional objects providing
general sample data collected on a PVC which
implements Service Level Definitions.
.1.3.6.1.2.1.95.3.1.14
A collection of required objects providing
capability information and control for this
MIB module.
.1.3.6.1.2.1.95.3.1.15
Compliance Statements (1)

OID .1.3.6.1.2.1.95.3.2.1
The compliance statement for SNMP entities
which support with Frame Relay Service Level
Definitions. This group defines the minimum
level of support required for compliance.
Required groups
mandatory frsldPvcReqCtrlGroup
mandatory frsldPvcReqDataGroup
mandatory frsldCapabilitiesGroup
optional frsldPvcHCFrameDataGroup This group is mandatory only for those network
interfaces with corresponding instance of ifSpeed
greater than 650,000,000 bits/second.
optional frsldPvcHCOctetDataGroup This group is mandatory only for those network
interfaces with corresponding instance of ifSpeed
greater than 650,000,000 bits/second.
optional frsldPvcPacketGroup This group is optional. Network interfaces that
allow control of the packets used to collect
information are encouraged to implement this
group.
optional frsldPvcDelayCtrlGroup This group is optional. Network interfaces that
offer control of the delay measurement are
strongly encouraged to implement this group.
optional frsldPvcSampleCtrlGroup This group is mandatory only for those network

interfaces that allow data sampling.
optional frsldPvcDelayDataGroup This group is only mandatory when
frsldPvcDelayCtrlGroup is implemented. It is
strongly encouraged that any device capable
of measuring delay implement this group.
optional frsldPvcSampleDelayGroup This group is only mandatory when both
frsldPvcSampleCtrlGroup and frsldPvcDelayDataGroup
are supported.
optional frsldPvcSampleDataGroup This group is mandatory whenever
frsldPvcSampleCtrlGroup is supported.
optional frsldPvcSampleHCFrameGroup This group is mandatory whenever both
frsldPvcSampleCtrlGroup and frsldPvcHCFrameDataGroup
are supported.
optional frsldPvcSampleHCDataGroup This group is mandatory whenever both
frsldPvcSampleCtrlGroup and frsldPvcHCOctetDataGroup
are supported.
optional frsldPvcSampleAvailGroup This group is mandatory whenever
frsldPvcSampleCtrlGroup is supported.
optional frsldPvcSampleGeneralGroup This group is mandatory whenever
frsldPvcSampleCtrlGroup is supported.
Object refinements
ObjectAccessSyntaxDescription
frsldPvcCtrlStatus readonly
active(1)
Row creation can be done outside of the scope of
the SNMP protocol. If this object is implemented

with max-access of read-only, then the only value
that MUST be returned is active(1) and
frsldPvcCtrlWriteCaps MUST return 0 for the
frsldPvcCtrlStatus(0) bit.
frsldPvcCtrlPurge readonly
Write access is not required. If this object is
implemented with a max-access of read-only, then
the frsldPvcCtrlPurge(5) bit must return 0.
frsldPvcCtrlDeleteOnPurge readonly
Write access is not required. If this object is
implemented with a max-access of read-only, then
the frsldPvcCtrlDeleteOnPurge(6) bit must return
0.
frsldMaxPvcCtrls readonly
Write access is not required if the device either
dynamically allocates memory or statically allocates
a fixed number of entries. In the case of static
allocation, the device should always report the
correct maximum number of controls. In the case
of dynamic allocation, the device SHOULD always
report a number greater than frsldNumPvcCtrls
when allocation is possible and a number equal to
frsldNumPvcCtrls when allocation is not possible.
frsldMaxSmplCtrls readonly
Write access is not required if the device either
dynamically allocates memory or statically allocates
a fixed number of entries. In the case of static
allocation, the device should always report the
correct maximum number of controls. In the case
of dynamic allocation, the device SHOULD always
report a number greater than frsldNumSmplCtrls
when allocation is possible and a number equal to
frsldNumSmplCtrls when allocation is not possible.