OID reference

loadIndex

1.3.6.1.4.1.207.8.4.4.4.48.1.1.1

Description

There are two sets of load information, dynamic and static. The dynamic information is used once, then cleared. The static information is used whenever the dynamic information is not available. The dynamic information is also used to indicate the current load parameters when a load is in progress.

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.207.8.4.4.4.48.1.1 (loadEntry)
Node code
1
Node name
loadIndex
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.207.8.4.4.4.48.1.1.1
URN notation
urn:oid:1.3.6.1.4.1.207.8.4.4.4.48.1.1.1
Type
OBJECT-TYPE
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 207 8 4 4 4 48 1 1 1}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedtelesyn(207) mibObject(8) brouterMib(4) atRouter(4) modules(4) loader(48) loadTable(1) loadEntry(1) loadIndex(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedtelesyn(207) mibObjects(8) brouterMib(4) atRouter(4) modules(4) loader(48) loadTable(1) loadEntry(1) loadIndex(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedtelesyn(207) mibobjs(8) brouterMib(4) atRouter(4) modules(4) loader(48) loadTable(1) loadEntry(1) loadIndex(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) ati(207) mibObject(8) brouterMib(4) atRouter(4) modules(4) loader(48) loadTable(1) loadEntry(1) loadIndex(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) ati(207) mibObjects(8) brouterMib(4) atRouter(4) modules(4) loader(48) loadTable(1) loadEntry(1) loadIndex(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) ati(207) mibobjs(8) brouterMib(4) atRouter(4) modules(4) loader(48) loadTable(1) loadEntry(1) loadIndex(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedTelesis(207) mibObject(8) brouterMib(4) atRouter(4) modules(4) loader(48) loadTable(1) loadEntry(1) loadIndex(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedTelesis(207) mibObjects(8) brouterMib(4) atRouter(4) modules(4) loader(48) loadTable(1) loadEntry(1) loadIndex(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedTelesis(207) mibobjs(8) brouterMib(4) atRouter(4) modules(4) loader(48) loadTable(1) loadEntry(1) loadIndex(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedTelesyn(207) mibObject(8) brouterMib(4) atRouter(4) modules(4) loader(48) loadTable(1) loadEntry(1) loadIndex(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedTelesyn(207) mibObjects(8) brouterMib(4) atRouter(4) modules(4) loader(48) loadTable(1) loadEntry(1) loadIndex(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedTelesyn(207) mibobjs(8) brouterMib(4) atRouter(4) modules(4) loader(48) loadTable(1) loadEntry(1) loadIndex(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) alliedtelesyn(207) mibObject(8) brouterMib(4) atRouter(4) modules(4) loader(48) loadTable(1) loadEntry(1) loadIndex(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) alliedtelesyn(207) mibObjects(8) brouterMib(4) atRouter(4) modules(4) loader(48) loadTable(1) loadEntry(1) loadIndex(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) alliedtelesyn(207) mibobjs(8) brouterMib(4) atRouter(4) modules(4) loader(48) loadTable(1) loadEntry(1) loadIndex(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) ati(207) mibObject(8) brouterMib(4) atRouter(4) modules(4) loader(48) loadTable(1) loadEntry(1) loadIndex(1)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/207/8/4/4/4/48/1/1/1
  • /ISO/Identified-Organization/6/1/4/1/207/8/4/4/4/48/1/1/1
  • /ISO/3/6/1/4/1/207/8/4/4/4/48/1/1/1
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/alliedtelesyn/mibObject/brouterMib/atRouter/modules/loader/loadTable/loadEntry/loadIndex
  • /iso/identified-organization/dod/internet/private/enterprise/alliedtelesyn/mibObjects/brouterMib/atRouter/modules/loader/loadTable/loadEntry/loadIndex
  • /iso/identified-organization/dod/internet/private/enterprise/alliedtelesyn/mibobjs/brouterMib/atRouter/modules/loader/loadTable/loadEntry/loadIndex
  • /iso/identified-organization/dod/internet/private/enterprise/ati/mibObject/brouterMib/atRouter/modules/loader/loadTable/loadEntry/loadIndex
  • /iso/identified-organization/dod/internet/private/enterprise/ati/mibObjects/brouterMib/atRouter/modules/loader/loadTable/loadEntry/loadIndex
  • /iso/identified-organization/dod/internet/private/enterprise/ati/mibobjs/brouterMib/atRouter/modules/loader/loadTable/loadEntry/loadIndex
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesis/mibObject/brouterMib/atRouter/modules/loader/loadTable/loadEntry/loadIndex
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesis/mibObjects/brouterMib/atRouter/modules/loader/loadTable/loadEntry/loadIndex
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesis/mibobjs/brouterMib/atRouter/modules/loader/loadTable/loadEntry/loadIndex
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesyn/mibObject/brouterMib/atRouter/modules/loader/loadTable/loadEntry/loadIndex
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesyn/mibObjects/brouterMib/atRouter/modules/loader/loadTable/loadEntry/loadIndex
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesyn/mibobjs/brouterMib/atRouter/modules/loader/loadTable/loadEntry/loadIndex
  • /iso/identified-organization/dod/internet/private/enterprises/alliedtelesyn/mibObject/brouterMib/atRouter/modules/loader/loadTable/loadEntry/loadIndex
  • /iso/identified-organization/dod/internet/private/enterprises/alliedtelesyn/mibObjects/brouterMib/atRouter/modules/loader/loadTable/loadEntry/loadIndex
  • /iso/identified-organization/dod/internet/private/enterprises/alliedtelesyn/mibobjs/brouterMib/atRouter/modules/loader/loadTable/loadEntry/loadIndex
  • /iso/identified-organization/dod/internet/private/enterprises/ati/mibObject/brouterMib/atRouter/modules/loader/loadTable/loadEntry/loadIndex
  • Additional combinations skipped.

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
mandatory, current

Definitions may combine these properties differently.

Compare 2 source variants

Variant 1 — MIBdepot

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
mandatory

Variant 2 — Circitor

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
current

Enumerated values

Numbers refer to source variants above. Each value is shown only for variants that define it.

ValueNameSource variants
1static1, 2
2dynamic1, 2

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition.

In ALLIEDTELESYN-MIB, the row index loadIndex is declared as INTEGER. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.207.8.4.4.4.48.1.1.1.<loadIndex>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.207.8.4.4.4.48.1.1.1

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

There are two sets of load information, dynamic and static.
The dynamic information is used once, then cleared. The static
information is used whenever the dynamic information is not
available. The dynamic information is also used to indicate the
current load parameters when a load is in progress.
Sources for this description

Circitor

Parsed from AT-LOADER-MIB.mib · AT-LOADER-MIB

Source file: Download AT-LOADER-MIB · Publisher's file

Vendor MIB copy from the LibreNMS archive.

Other archive copies with the same file

Observium Community

Source file: Download AT-LOADER-MIB.mib

Browse all files from Circitor

MIBdepot

Source file: Download ALLIEDTELESYN-MIB · Publisher's file

Vendor MIB copy from the Observium Community archive.

Related source files and packages:

Source file: Download ATROUTER.MIB.txt

Source data warning: The published file uses lowercase ASN.1 type identifiers. The reviewed grammar preserves their exact names, all OID assignments and every original source byte; no type or value is renamed.

Source file: Download ALLIEDTELESYN-MIB.mib

Source file: Download ATROUTER-MIB.my.txt

Browse all files from MIBdepot

Historical records

Additional source information

Information from OID Repository
Vendor: Allied Telesis, Inc.
Module: ALLIEDTELESYN-MIB

[Automatically extracted from oidview.com]
Information from MIBdepot
loadIndex OBJECT-TYPE
        SYNTAX  INTEGER {
                    static(1),
                    dynamic(2)
                }
        ACCESS  read-write
        STATUS  mandatory
        DESCRIPTION
                "There are two sets of load information, dynamic and static.
                The dynamic information is used once, then cleared. The static
                information is used whenever the dynamic information is not
                available. The dynamic information is also used to indicate the
                current load parameters when a load is in progress."
        ::= { loadEntry 1 }
Information from Circitor
loadIndex OBJECT-TYPE
    SYNTAX      INTEGER {
                static(1),
                dynamic(2)
            }
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
            "There are two sets of load information, dynamic and static.
            The dynamic information is used once, then cleared. The static
            information is used whenever the dynamic information is not
            available. The dynamic information is also used to indicate the
            current load parameters when a load is in progress."
    ::= { loadEntry 1 }

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.207)

Scott Holley

Siblings (4)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.207.8.4.4.4.48.1.1.2 loadServer00 The IP address from which load will load or upload.
1.3.6.1.4.1.207.8.4.4.4.48.1.1.3 loadDestination00 The destination of the file loaded, either flash or nvs
memory, or undefined.
1.3.6.1.4.1.207.8.4.4.4.48.1.1.4 loadFilename00 The file name of the file being loaded or uploaded.
1.3.6.1.4.1.207.8.4.4.4.48.1.1.5 loadDelay00 A delay in seconds between the initiation of the load and the
start of the load. This allows for time to set up TFTP servers
in c…