OID reference

h3cSysReloadAction

1.3.6.1.4.1.43.45.1.10.2.3.1.3.2

Description

Writing reloadOnSchedule(2) to this object performs the reload operation on schedule. If h3cSysReloadScheduleTime is not set, the value of h3cSysReloadAction can't be set to 'reloadOnSchedule(2)'. Writing reloadAtOnce(3)to this object performs the reload operation at once, regardless of the h3cSysReloadScheduleTime. W…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.43.45.1.10.2.3.1.3 (h3cSysReload)
Node code
2
Node name
h3cSysReloadAction
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.43.45.1.10.2.3.1.3.2
URN notation
urn:oid:1.3.6.1.4.1.43.45.1.10.2.3.1.3.2
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 43 45 1 10 2 3 1 3 2}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cSystemMan(3) h3cSystemManMIBObjects(1) h3cSysReload(3) h3cSysReloadAction(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cSystemMan(3) h3cSystemManMIBObjects(1) h3cSysReload(3) h3cSysReloadAction(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cSystemMan(3) h3cSystemManMIBObjects(1) h3cSysReload(3) h3cSysReloadAction(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cSystemMan(3) h3cSystemManMIBObjects(1) h3cSysReload(3) h3cSysReloadAction(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cSystemMan(3) h3cSystemManMIBObjects(1) h3cSysReload(3) h3cSysReloadAction(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cSystemMan(3) h3cSystemManMIBObjects(1) h3cSysReload(3) h3cSysReloadAction(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cSystemMan(3) h3cSystemManMIBObjects(1) h3cSysReload(3) h3cSysReloadAction(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cSystemMan(3) h3cSystemManMIBObjects(1) h3cSysReload(3) h3cSysReloadAction(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cSystemMan(3) h3cSystemManMIBObjects(1) h3cSysReload(3) h3cSysReloadAction(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cSystemMan(3) h3cSystemManMIBObjects(1) h3cSysReload(3) h3cSysReloadAction(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cSystemMan(3) h3cSystemManMIBObjects(1) h3cSysReload(3) h3cSysReloadAction(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cSystemMan(3) h3cSystemManMIBObjects(1) h3cSysReload(3) h3cSysReloadAction(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cSystemMan(3) h3cSystemManMIBObjects(1) h3cSysReload(3) h3cSysReloadAction(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cSystemMan(3) h3cSystemManMIBObjects(1) h3cSysReload(3) h3cSysReloadAction(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cSystemMan(3) h3cSystemManMIBObjects(1) h3cSysReload(3) h3cSysReloadAction(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cSystemMan(3) h3cSystemManMIBObjects(1) h3cSysReload(3) h3cSysReloadAction(2)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/43/45/1/10/2/3/1/3/2
  • /ISO/Identified-Organization/6/1/4/1/43/45/1/10/2/3/1/3/2
  • /ISO/3/6/1/4/1/43/45/1/10/2/3/1/3/2
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysReload/h3cSysReloadAction
  • /iso/identified-organization/dod/internet/private/enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysReload/h3cSysReloadAction
  • /iso/identified-organization/dod/internet/private/enterprises/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysReload/h3cSysReloadAction
  • /iso/identified-organization/dod/internet/private/enterprises/a3com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysReload/h3cSysReloadAction
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysReload/h3cSysReloadAction
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysReload/h3cSysReloadAction
  • /iso/identified-organization/dod/internet/private/vendor-objects/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysReload/h3cSysReloadAction
  • /iso/identified-organization/dod/internet/private/vendor-objects/a3com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysReload/h3cSysReloadAction
  • /iso/org/dod/internet/private/enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysReload/h3cSysReloadAction
  • /iso/org/dod/internet/private/enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysReload/h3cSysReloadAction
  • /iso/org/dod/internet/private/enterprises/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysReload/h3cSysReloadAction
  • /iso/org/dod/internet/private/enterprises/a3com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysReload/h3cSysReloadAction
  • /iso/org/dod/internet/private/ldap-enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysReload/h3cSysReloadAction
  • /iso/org/dod/internet/private/ldap-enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysReload/h3cSysReloadAction
  • /iso/org/dod/internet/private/vendor-objects/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysReload/h3cSysReloadAction
  • /iso/org/dod/internet/private/vendor-objects/a3com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysReload/h3cSysReloadAction
  • Additional combinations skipped.

SNMP properties

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

Enumerated values

ValueName
1reloadUnavailable
2reloadOnSchedule
3reloadAtOnce
4reloadCancel

Using this OID with SNMP

At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.

snmpget [connection options] DEVICE .1.3.6.1.4.1.43.45.1.10.2.3.1.3.2.0

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.

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

h3cSysReloadAction · current

h3cSysReloadAction OBJECT-TYPE
    SYNTAX INTEGER
        {
        reloadUnavailable(1),
        reloadOnSchedule(2),
        reloadAtOnce(3),
        reloadCancel(4)
        }
    MAX-ACCESS read-write
    STATUS current
    DESCRIPTION
        "
        Writing reloadOnSchedule(2) to this object performs the reload operation on schedule.
        If h3cSysReloadScheduleTime is not set, the value of h3cSysReloadAction can't be set to
        'reloadOnSchedule(2)'.

        Writing reloadAtOnce(3)to this object performs the reload operation at once,
        regardless of the h3cSysReloadScheduleTime.

        When reloadCancel(4)is set, the scheduled reload action will be cancelled and the value of
        h3cSysReloadAction will be 'reloadUnavailable(1)',the value of h3cSysReloadSchedule will be
        0, h3cSysReloadTag will be given a value of zero length, but the content of
        h3cSysReloadScheduleTable will remain.


        The h3cSysReloadSchedule and h3cSysReloadTag  determine the reload entity(ies) in mutually
        exclusive way. And the h3cSysReloadSchedule will be handled at first. If the value of
        h3cSysReloadSchedule is invalid, then the h3cSysReloadTag will be handled.

        If the value of h3cSysReloadSchedule is valid, the value of h3cSysReloadTag is ignored and a
        reload action will be implemented to the entity specified by h3cSysReloadEntity in the entry
        pointed by h3cSysReloadSchedule.

        If h3cSysReloadSchedule is valid, but the entry h3cSysReloadSchedule pointing to is not active,
        the reload action will be ignored , and an inconsistent value will be returned.


        If multiple entities are required to be reloaded at the same time, the value of h3cSysReloadTag
        must be specified to select the reload parameters in the h3cSysReloadSceduelTable, and
        h3cSysReloadSchedule must have the value of '0'.

        If the whole fabric is to be reloaded in an XRN device, all the units in the fabric must
        have at least one entry in the h3cSysReloadSceduelTable with the same tag in h3cSysReloadSceduelTagList.

        When a reload action is done, or there is no reload action, the value
        should be reloadUnavailable(1).
        "
    ::= { h3cSysReload 2 }

h3cSysReloadAction · current

h3cSysReloadAction OBJECT-TYPE
    SYNTAX INTEGER
        {
        reloadUnavailable(1),
        reloadOnSchedule(2),
        reloadAtOnce(3),
        reloadCancel(4)
        }
    MAX-ACCESS read-write
    STATUS current
    DESCRIPTION
        "
        Writing reloadOnSchedule(2) to this object performs the reload operation on schedule.
        If h3cSysReloadScheduleTime is not set, the value of h3cSysReloadAction can't be set to
        'reloadOnSchedule(2)'.

        Writing reloadAtOnce(3)to this object performs the reload operation at once,
        regardless of the h3cSysReloadScheduleTime.

        When reloadCancel(4)is set, the scheduled reload action will be cancelled and the value of
        h3cSysReloadAction will be 'reloadUnavailable(1)',the value of h3cSysReloadSchedule will be
        0, h3cSysReloadTag will be given a value of zero length, but the content of
        h3cSysReloadScheduleTable will remain.


        The h3cSysReloadSchedule and h3cSysReloadTag  determine the reload entity(ies) in mutually
        exclusive way. And the h3cSysReloadSchedule will be handled at first. If the value of
        h3cSysReloadSchedule is invalid, then the h3cSysReloadTag will be handled.

        If the value of h3cSysReloadSchedule is valid, the value of h3cSysReloadTag is ignored and a
        reload action will be implemented to the entity specified by h3cSysReloadEntity in the entry
        pointed by h3cSysReloadSchedule.

        If h3cSysReloadSchedule is valid, but the entry h3cSysReloadSchedule pointing to is not active,
        the reload action will be ignored , and an inconsistent value will be returned.


        If multiple entities are required to be reloaded at the same time, the value of h3cSysReloadTag
        must be specified to select the reload parameters in the h3cSysReloadSceduelTable, and
        h3cSysReloadSchedule must have the value of '0'.

        If the whole fabric is to be reloaded in an XRN device, all the units in the fabric must
        have at least one entry in the h3cSysReloadSceduelTable with the same tag in h3cSysReloadSceduelTagList.

        When a reload action is done, or there is no reload action, the value
        should be reloadUnavailable(1).
        "
    ::= { h3cSysReload 2 }

Meaning

Descriptions

1 unique

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

Writing reloadOnSchedule(2) to this object performs the reload operation on schedule. If h3cSysReloadScheduleTime is not set, the value of h3cSysReloadAction can't be set to 'reloadOnSchedule(2)'. Writing reloadAtOnce(3)to this object performs the reload operation at once, regardless of the h3cSysReloadScheduleTime. When reloadCancel(4)is set, the scheduled reload action will be cancelled and the value of h3cSysReloadAction will be 'reloadUnavailable(1)',the value of h3cSysReloadSchedule will be 0, h3cSysReloadTag will be given a value of zero length, but the content of h3cSysReloadScheduleTable will remain. The h3cSysReloadSchedule and h3cSysReloadTag determine the reload entity(ies) in mutually exclusive way. And the h3cSysReloadSchedule will be handled at first. If the value of h3cSysReloadSchedule is invalid, then the h3cSysReloadTag will be handled. If the value of h3cSysReloadSchedule is valid, the value of h3cSysReloadTag is ignored and a reload action will be implemented to the entity specified by h3cSysReloadEntity in the entry pointed by h3cSysReloadSchedule. If h3cSysReloadSchedule is valid, but the entry h3cSysReloadSchedule pointing to is not active, the reload action will be ignored , and an inconsistent value will be returned. If multiple entities are required to be reloaded at the same time, the value of h3cSysReloadTag must be specified to select the reload parameters in the h3cSysReloadSceduelTable, and h3cSysReloadSchedule must have the value of '0'. If the whole fabric is to be reloaded in an XRN device, all the units in the fabric must have at least one entry in the h3cSysReloadSceduelTable with the same tag in h3cSysReloadSceduelTagList. When a reload action is done, or there is no reload action, the value should be reloadUnavailable(1).

Sources for this description

3Com MIB copies (LibreNMS/Observium Community)Netdisco MIB archive copies

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 13Com MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies1 record · 2 sources

Description 1

h3cSysReloadAction · current3Com MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies2 sources

Status in source: current.

Names: h3cSysReloadAction

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "h3cSysReloadAction",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "reloadUnavailable",
    "(",
    "1",
    ")",
    ",",
    "reloadOnSchedule",
    "(",
    "2",
    ")",
    ",",
    "reloadAtOnce",
    "(",
    "3",
    ")",
    ",",
    "reloadCancel",
    "(",
    "4",
    ")",
    "}",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\" Writing reloadOnSchedule(2) to this object performs the reload operation on schedule. If h3cSysReloadScheduleTime is not set, the value of h3cSysReloadAction can't be set to 'reloadOnSchedule(2)'. Writing reloadAtOnce(3)to this object performs the reload operation at once, regardless of the h3cSysReloadScheduleTime. When reloadCancel(4)is set, the scheduled reload action will be cancelled and the value of h3cSysReloadAction will be 'reloadUnavailable(1)',the value of h3cSysReloadSchedule will be 0, h3cSysReloadTag will be given a value of zero length, but the content of h3cSysReloadScheduleTable will remain. The h3cSysReloadSchedule and h3cSysReloadTag determine the reload entity(ies) in mutually exclusive way. And the h3cSysReloadSchedule will be handled at first. If the value of h3cSysReloadSchedule is invalid, then the h3cSysReloadTag will be handled. If the value of h3cSysReloadSchedule is valid, the value of h3cSysReloadTag is ignored and a reload action will be implemented to the entity specified by h3cSysReloadEntity in the entry pointed by h3cSysReloadSchedule. If h3cSysReloadSchedule is valid, but the entry h3cSysReloadSchedule pointing to is not active, the reload action will be ignored , and an inconsistent value will be returned. If multiple entities are required to be reloaded at the same time, the value of h3cSysReloadTag must be specified to select the reload parameters in the h3cSysReloadSceduelTable, and h3cSysReloadSchedule must have the value of '0'. If the whole fabric is to be reloaded in an XRN device, all the units in the fabric must have at least one entry in the h3cSysReloadSceduelTable with the same tag in h3cSysReloadSceduelTagList. When a reload action is done, or there is no reload action, the value should be reloadUnavailable(1). \"",
    "::=",
    "{",
    "h3cSysReload",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "reloadUnavailable",
            1
          ],
          [
            "reloadOnSchedule",
            2
          ],
          [
            "reloadAtOnce",
            3
          ],
          [
            "reloadCancel",
            4
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Writing reloadOnSchedule(2) to this object performs the reload operation on schedule. If h3cSysReloadScheduleTime is not set, the value of h3cSysReloadAction can't be set to 'reloadOnSchedule(2)'. Writing reloadAtOnce(3)to this object performs the reload operation at once, regardless of the h3cSysReloadScheduleTime. When reloadCancel(4)is set, the scheduled reload action will be cancelled and the value of h3cSysReloadAction will be 'reloadUnavailable(1)',the value of h3cSysReloadSchedule will be 0, h3cSysReloadTag will be given a value of zero length, but the content of h3cSysReloadScheduleTable will remain. The h3cSysReloadSchedule and h3cSysReloadTag determine the reload entity(ies) in mutually exclusive way. And the h3cSysReloadSchedule will be handled at first. If the value of h3cSysReloadSchedule is invalid, then the h3cSysReloadTag will be handled. If the value of h3cSysReloadSchedule is valid, the value of h3cSysReloadTag is ignored and a reload action will be implemented to the entity specified by h3cSysReloadEntity in the entry pointed by h3cSysReloadSchedule. If h3cSysReloadSchedule is valid, but the entry h3cSysReloadSchedule pointing to is not active, the reload action will be ignored , and an inconsistent value will be returned. If multiple entities are required to be reloaded at the same time, the value of h3cSysReloadTag must be specified to select the reload parameters in the h3cSysReloadSceduelTable, and h3cSysReloadSchedule must have the value of '0'. If the whole fabric is to be reloaded in an XRN device, all the units in the fabric must have at least one entry in the h3cSysReloadSceduelTable with the same tag in h3cSysReloadSceduelTagList. When a reload action is done, or there is no reload action, the value should be reloadUnavailable(1)."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.43)

Jeremy Siegel

Siblings (3)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.43.45.1.10.2.3.1.3.1 h3cSysReloadSchedule00
1.3.6.1.4.1.43.45.1.10.2.3.1.3.3 h3cSysReloadScheduleTable19
1.3.6.1.4.1.43.45.1.10.2.3.1.3.4 h3cSysReloadTag00