Reference record for OID 1.3.6.1.4.1.16.101.1.2.2.6.1.2



parent
1.3.6.1.4.1.16.101.1.2.2.6.1 (restBundleEntry)
node code
2
node name
restBundleDiagnostics
dot oid
1.3.6.1.4.1.16.101.1.2.2.6.1.2
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) unisys-timeplex(16) synchrony(101) st50(1) resource(2) reStatus(2) restBundleTable(6) restBundleEntry(1) restBundleDiagnostics(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) unisys(16) synchrony(101) st50(1) resource(2) reStatus(2) restBundleTable(6) restBundleEntry(1) restBundleDiagnostics(2)}
  • ...skipped...
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) perc(16) synchrony(101) st50(1) resource(2) reStatus(2) restBundleTable(6) restBundleEntry(1) restBundleDiagnostics(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) ami(16) synchrony(101) st50(1) resource(2) reStatus(2) restBundleTable(6) restBundleEntry(1) restBundleDiagnostics(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) unisys-timeplex(16) synchrony(101) st50(1) resource(2) reStatus(2) restBundleTable(6) restBundleEntry(1) restBundleDiagnostics(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) unisys(16) synchrony(101) st50(1) resource(2) reStatus(2) restBundleTable(6) restBundleEntry(1) restBundleDiagnostics(2)}
  • ...skipped...
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) perc(16) synchrony(101) st50(1) resource(2) reStatus(2) restBundleTable(6) restBundleEntry(1) restBundleDiagnostics(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) ami(16) synchrony(101) st50(1) resource(2) reStatus(2) restBundleTable(6) restBundleEntry(1) restBundleDiagnostics(2)}
  • iri oid
  • /iso/identified-organization/dod/internet/private/enterprise/unisys-timeplex/synchrony/st50/resource/reStatus/restBundleTable/restBundleEntry/restBundleDiagnostics
  • /iso/identified-organization/dod/internet/private/enterprise/unisys/synchrony/st50/resource/reStatus/restBundleTable/restBundleEntry/restBundleDiagnostics
  • ...skipped...
  • /iso/org/dod/internet/private/enterprise/perc/synchrony/st50/resource/reStatus/restBundleTable/restBundleEntry/restBundleDiagnostics
  • /iso/org/dod/internet/private/enterprise/ami/synchrony/st50/resource/reStatus/restBundleTable/restBundleEntry/restBundleDiagnostics
  • /iso/org/dod/internet/private/enterprises/unisys-timeplex/synchrony/st50/resource/reStatus/restBundleTable/restBundleEntry/restBundleDiagnostics
  • /iso/org/dod/internet/private/enterprises/unisys/synchrony/st50/resource/reStatus/restBundleTable/restBundleEntry/restBundleDiagnostics
  • ...skipped...
  • /iso/iso-identified-organization/dod/internet/private/enterprises/perc/synchrony/st50/resource/reStatus/restBundleTable/restBundleEntry/restBundleDiagnostics
  • /iso/iso-identified-organization/dod/internet/private/enterprises/ami/synchrony/st50/resource/reStatus/restBundleTable/restBundleEntry/restBundleDiagnostics
  • iri by oid_info
    /ISO/Identified-Organization/6/1/4/1/16/101/1/2/2/6/1/2

    Description by mibdepot

    Remove will free the bandwidth used by the
    bundle. If the bundle is an INL, then all
    channels connected over the INL will be
    disconnected. If the bundle is I/O, then that
    channel will be disconnected. The start
    mode of the bundle in the configuration
    MIB will be set to off.

    Insert only works on removed bundles (i.e.,
    bundles whose status is unknown). It will get
    the new bundle configuration MIB and attempt to
    bring the bundle up. The start mode of the
    bundle in the configuration MIB will be set to
    automatic.

    Reset is equivalent to a remove followed by an
    insert, except that the start mode in the bundle
    configuration MIB will not be changed.

    Update will load in the new bundle configuration
    MIB without affecting the INL or channel on that
    bundle. It will fail if any intrusive parameters
    in the bundle configuration MIB have been
    changed.

    Parsed from file STMIB.mib.txt
    Company: None
    Module: STMIB

    Description by circitor

    Remove will free the bandwidth used by the
    bundle. If the bundle is an INL, then all
    channels connected over the INL will be
    disconnected. If the bundle is I/O, then that
    channel will be disconnected. The start
    mode of the bundle in the configuration
    MIB will be set to off.

    Insert only works on removed bundles (i.e.,
    bundles whose status is unknown). It will get
    the new bundle configuration MIB and attempt to
    bring the bundle up. The start mode of the
    bundle in the configuration MIB will be set to
    automatic.

    Reset is equivalent to a remove followed by an
    insert, except that the start mode in the bundle
    configuration MIB will not be changed.

    Update will load in the new bundle configuration
    MIB without affecting the INL or channel on that
    bundle. It will fail if any intrusive parameters
    in the bundle configuration MIB have been
    changed.

    Parsed from file STMIB.mib
    Module: STMIB

    Information by oid_info

    Vendor: Timeplex
    Module: STMIB

    [Automatically extracted from oidview.com]

    Information by mibdepot

    restBundleDiagnostics OBJECT-TYPE SYNTAX INTEGER { insert(4), remove(5), reset(6), update(7) } ACCESS write-only STATUS mandatory DESCRIPTION "Remove will free the bandwidth used by the bundle. If the bundle is an INL, then all channels connected over the INL will be disconnected. If the bundle is I/O, then that channel will be disconnected. The start mode of the bundle in the configuration MIB will be set to off. Insert only works on removed bundles (i.e., bundles whose status is unknown). It will get the new bundle configuration MIB and attempt to bring the bundle up. The start mode of the bundle in the configuration MIB will be set to automatic. Reset is equivalent to a remove followed by an insert, except that the start mode in the bundle configuration MIB will not be changed. Update will load in the new bundle configuration MIB without affecting the INL or channel on that bundle. It will fail if any intrusive parameters in the bundle configuration MIB have been changed." ::= { restBundleEntry 2 }

    Information by circitor

    restBundleDiagnostics OBJECT-TYPE SYNTAX INTEGER { insert(4), remove(5), reset(6), update(7) } ACCESS write-only STATUS mandatory DESCRIPTION "Remove will free the bandwidth used by the bundle. If the bundle is an INL, then all channels connected over the INL will be disconnected. If the bundle is I/O, then that channel will be disconnected. The start mode of the bundle in the configuration MIB will be set to off. Insert only works on removed bundles (i.e., bundles whose status is unknown). It will get the new bundle configuration MIB and attempt to bring the bundle up. The start mode of the bundle in the configuration MIB will be set to automatic. Reset is equivalent to a remove followed by an insert, except that the start mode in the bundle configuration MIB will not be changed. Update will load in the new bundle configuration MIB without affecting the INL or channel on that bundle. It will fail if any intrusive parameters in the bundle configuration MIB have been changed." ::= { restBundleEntry 2 }

    First Registration Authority (recovered by parent 1.3.6.1.4.1.16)

    Laura Bridge

    Brothers (13)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.4.1.16.101.1.2.2.6.1.1 restBundleAddr 0 0 None
    1.3.6.1.4.1.16.101.1.2.2.6.1.3 restBundleStatus 0 0 The status is always enabled if the bundle
    is an INL. Unknown value means that the bundle
    is undefined.
    1.3.6.1.4.1.16.101.1.2.2.6.1.4 restBundleBwCntStatus 0 0 Bandwidth contention status.
    1.3.6.1.4.1.16.101.1.2.2.6.1.5 restBundleMillwattSignalABCD 0 0 Controls the tone generator for
    PCM channels.
    1.3.6.1.4.1.16.101.1.2.2.6.1.6 restBundleDS0Map 0 0 None
    1.3.6.1.4.1.16.101.1.2.2.6.1.7 restBundleSignalA 0 0 None
    1.3.6.1.4.1.16.101.1.2.2.6.1.8 restBundleSignalB 0 0 None
    1.3.6.1.4.1.16.101.1.2.2.6.1.9 restBundleSignalC 0 0 None
    1.3.6.1.4.1.16.101.1.2.2.6.1.10 restBundleSignalD 0 0 None
    1.3.6.1.4.1.16.101.1.2.2.6.1.11 restBundleOutSigA 0 0 This is not supported on
    T1M and E1M 4-port hardware
    configurationis
    1.3.6.1.4.1.16.101.1.2.2.6.1.12 restBundleOutSigB 0 0 This is not supported on
    T1M and E1M 4-port hardware
    configurationis
    1.3.6.1.4.1.16.101.1.2.2.6.1.13 restBundleOutSigC 0 0 This is not supported on
    T1M and E1M 4-port hardware
    configurationis
    1.3.6.1.4.1.16.101.1.2.2.6.1.14 restBundleOutSigD 0 0 This is not supported on
    T1M and E1M 4-port hardware
    configurationis