Reference record for OID 1.3.6.1.2.1.95.3.2.1


parent
1.3.6.1.2.1.95.3.2 (frsldMIBCompliances)
node code
1
node name
frsldCompliance
dot oid
1.3.6.1.2.1.95.3.2.1
type
MODULE-COMPLIANCE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) frsldMIB(95) frsldConformance(3) frsldMIBCompliances(2) frsldCompliance(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) frsldMIB(95) frsldConformance(3) frsldMIBCompliances(2) frsldCompliance(1)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) frsldMIB(95) frsldConformance(3) frsldMIBCompliances(2) frsldCompliance(1)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) frsldMIB(95) frsldConformance(3) frsldMIBCompliances(2) frsldCompliance(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) frsldMIB(95) frsldConformance(3) frsldMIBCompliances(2) frsldCompliance(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) frsldMIB(95) frsldConformance(3) frsldMIBCompliances(2) frsldCompliance(1)}
  • iri oid
  • /iso/identified-organization/dod/internet/mgmt/mib-2/frsldMIB/frsldConformance/frsldMIBCompliances/frsldCompliance
  • /iso/identified-organization/dod/internet/mgmt/mib/frsldMIB/frsldConformance/frsldMIBCompliances/frsldCompliance
  • /iso/org/dod/internet/mgmt/mib-2/frsldMIB/frsldConformance/frsldMIBCompliances/frsldCompliance
  • /iso/org/dod/internet/mgmt/mib/frsldMIB/frsldConformance/frsldMIBCompliances/frsldCompliance
  • /iso/iso-identified-organization/dod/internet/mgmt/mib-2/frsldMIB/frsldConformance/frsldMIBCompliances/frsldCompliance
  • /iso/iso-identified-organization/dod/internet/mgmt/mib/frsldMIB/frsldConformance/frsldMIBCompliances/frsldCompliance
  • iri by oid_info
    /ISO/Identified-Organization/6/1/2/1/95/3/2/1

    Description by oid_info

    frsldCompliance MODULE-COMPLIANCE
    STATUS current
    DESCRIPTION
    "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."
    MODULE -- this module
    MANDATORY-GROUPS { frsldPvcReqCtrlGroup,
    frsldPvcReqDataGroup,
    frsldCapabilitiesGroup}
    GROUP frsldPvcHCFrameDataGroup
    DESCRIPTION
    "This group is mandatory only for those network
    interfaces with corresponding instance of ifSpeed
    greater than 650,000,000 bits/second."
    GROUP frsldPvcHCOctetDataGroup
    DESCRIPTION
    "This group is mandatory only for those network
    interfaces with corresponding instance of ifSpeed
    greater than 650,000,000 bits/second."
    GROUP frsldPvcPacketGroup
    DESCRIPTION
    "This group is optional. Network interfaces that
    allow control of the packets used to collect
    information are encouraged to implement this
    group."
    GROUP frsldPvcDelayCtrlGroup
    DESCRIPTION
    "This group is optional. Network interfaces that
    offer control of the delay measurement are
    strongly encouraged to implement this group."GROUP frsldPvcSampleCtrlGroup
    DESCRIPTION
    "This group is mandatory only for those network
    interfaces that allow data sampling."
    GROUP frsldPvcDelayDataGroup
    DESCRIPTION
    "This group is only mandatory when
    frsldPvcDelayCtrlGroup is implemented. It is
    strongly encouraged that any device capable
    of measuring delay implement this group."
    GROUP frsldPvcSampleDelayGroup
    DESCRIPTION
    "This group is only mandatory when both
    frsldPvcSampleCtrlGroup and frsldPvcDelayDataGroup
    are supported."
    GROUP frsldPvcSampleDataGroup
    DESCRIPTION
    "This group is mandatory whenever
    frsldPvcSampleCtrlGroup is supported."
    GROUP frsldPvcSampleHCFrameGroup
    DESCRIPTION
    "This group is mandatory whenever both
    frsldPvcSampleCtrlGroup and frsldPvcHCFrameDataGroup
    are supported."
    GROUP frsldPvcSampleHCDataGroup
    DESCRIPTION
    "This group is mandatory whenever both
    frsldPvcSampleCtrlGroup and frsldPvcHCOctetDataGroup
    are supported."
    GROUP frsldPvcSampleAvailGroup
    DESCRIPTION
    "This group is mandatory whenever
    frsldPvcSampleCtrlGroup is supported."
    GROUP frsldPvcSampleGeneralGroup
    DESCRIPTION
    "This group is mandatory whenever
    frsldPvcSampleCtrlGroup is supported."
    OBJECT frsldPvcCtrlStatus
    SYNTAX RowStatus { active(1) } -- subset of RowStatus
    MIN-ACCESS read-only
    DESCRIPTION
    "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."
    OBJECT frsldPvcCtrlPurge
    MIN-ACCESS read-only
    DESCRIPTION
    "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."
    OBJECT frsldPvcCtrlDeleteOnPurge
    MIN-ACCESS read-only
    DESCRIPTION
    "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."
    OBJECT frsldMaxPvcCtrls
    MIN-ACCESS read-only
    DESCRIPTION
    "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."
    OBJECT frsldMaxSmplCtrls
    MIN-ACCESS read-only
    DESCRIPTION
    "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."

    View at oid-info.com

    Description by circitor

    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.

    Parsed from file FRSLD-MIB.mib
    Module: FRSLD-MIB

    Information by oid_info

    Automatically extracted from RFC3202

    Information by circitor

    frsldCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "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." MODULE MANDATORY-GROUPS { frsldPvcReqCtrlGroup, frsldPvcReqDataGroup, frsldCapabilitiesGroup} GROUP frsldPvcHCFrameDataGroup DESCRIPTION "This group is mandatory only for those network interfaces with corresponding instance of ifSpeed greater than 650,000,000 bits/second." GROUP frsldPvcHCOctetDataGroup DESCRIPTION "This group is mandatory only for those network interfaces with corresponding instance of ifSpeed greater than 650,000,000 bits/second." GROUP frsldPvcPacketGroup DESCRIPTION "This group is optional. Network interfaces that allow control of the packets used to collect information are encouraged to implement this group." GROUP frsldPvcDelayCtrlGroup DESCRIPTION "This group is optional. Network interfaces that offer control of the delay measurement are strongly encouraged to implement this group." GROUP frsldPvcSampleCtrlGroup DESCRIPTION "This group is mandatory only for those network interfaces that allow data sampling." GROUP frsldPvcDelayDataGroup DESCRIPTION "This group is only mandatory when frsldPvcDelayCtrlGroup is implemented. It is strongly encouraged that any device capable of measuring delay implement this group." GROUP frsldPvcSampleDelayGroup DESCRIPTION "This group is only mandatory when both frsldPvcSampleCtrlGroup and frsldPvcDelayDataGroup are supported." GROUP frsldPvcSampleDataGroup DESCRIPTION "This group is mandatory whenever frsldPvcSampleCtrlGroup is supported." GROUP frsldPvcSampleHCFrameGroup DESCRIPTION "This group is mandatory whenever both frsldPvcSampleCtrlGroup and frsldPvcHCFrameDataGroup are supported." GROUP frsldPvcSampleHCDataGroup DESCRIPTION "This group is mandatory whenever both frsldPvcSampleCtrlGroup and frsldPvcHCOctetDataGroup are supported." GROUP frsldPvcSampleAvailGroup DESCRIPTION "This group is mandatory whenever frsldPvcSampleCtrlGroup is supported." GROUP frsldPvcSampleGeneralGroup DESCRIPTION "This group is mandatory whenever frsldPvcSampleCtrlGroup is supported." OBJECT frsldPvcCtrlStatus SYNTAX RowStatus { active(1) } MIN-ACCESS read-only DESCRIPTION "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." OBJECT frsldPvcCtrlPurge MIN-ACCESS read-only DESCRIPTION "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." OBJECT frsldPvcCtrlDeleteOnPurge MIN-ACCESS read-only DESCRIPTION "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." OBJECT frsldMaxPvcCtrls MIN-ACCESS read-only DESCRIPTION "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." OBJECT frsldMaxSmplCtrls MIN-ACCESS read-only DESCRIPTION "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." ::= { frsldMIBCompliances 1 }

    First Registration Authority (recovered by parent 1.3.6)

    Defense Communication Agency

    Current Registration Authority (recovered by parent 1.3.6.1.2)

    Internet Assigned Numbers Authority