OID reference

h3cSysImageType

1.3.6.1.4.1.43.45.1.10.2.3.1.4.2.1.5

Description

It indicates the reloading sequence attribute of the image. For devices which support dual image: If the value is 'main(1)',the image will be the first image in the next reloading procedure. If the value is 'backup(2)', the image will be used if the main image fails. If the value is 'secure(4)', the image will be used…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.43.45.1.10.2.3.1.4.2.1 (h3cSysImageEntry)
Node code
5
Node name
h3cSysImageType
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.43.45.1.10.2.3.1.4.2.1.5
URN notation
urn:oid:1.3.6.1.4.1.43.45.1.10.2.3.1.4.2.1.5
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

  • {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) h3cSysImage(4) h3cSysImageTable(2) h3cSysImageEntry(1) h3cSysImageType(5)}
  • {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) h3cSysImage(4) h3cSysImageTable(2) h3cSysImageEntry(1) h3cSysImageType(5)}
  • {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) h3cSysImage(4) h3cSysImageTable(2) h3cSysImageEntry(1) h3cSysImageType(5)}
  • {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) h3cSysImage(4) h3cSysImageTable(2) h3cSysImageEntry(1) h3cSysImageType(5)}
  • {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) h3cSysImage(4) h3cSysImageTable(2) h3cSysImageEntry(1) h3cSysImageType(5)}
  • {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) h3cSysImage(4) h3cSysImageTable(2) h3cSysImageEntry(1) h3cSysImageType(5)}
  • {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) h3cSysImage(4) h3cSysImageTable(2) h3cSysImageEntry(1) h3cSysImageType(5)}
  • {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) h3cSysImage(4) h3cSysImageTable(2) h3cSysImageEntry(1) h3cSysImageType(5)}
  • {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) h3cSysImage(4) h3cSysImageTable(2) h3cSysImageEntry(1) h3cSysImageType(5)}
  • {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) h3cSysImage(4) h3cSysImageTable(2) h3cSysImageEntry(1) h3cSysImageType(5)}
  • {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) h3cSysImage(4) h3cSysImageTable(2) h3cSysImageEntry(1) h3cSysImageType(5)}
  • {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) h3cSysImage(4) h3cSysImageTable(2) h3cSysImageEntry(1) h3cSysImageType(5)}
  • {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) h3cSysImage(4) h3cSysImageTable(2) h3cSysImageEntry(1) h3cSysImageType(5)}
  • {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) h3cSysImage(4) h3cSysImageTable(2) h3cSysImageEntry(1) h3cSysImageType(5)}
  • {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) h3cSysImage(4) h3cSysImageTable(2) h3cSysImageEntry(1) h3cSysImageType(5)}
  • {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) h3cSysImage(4) h3cSysImageTable(2) h3cSysImageEntry(1) h3cSysImageType(5)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/43/45/1/10/2/3/1/4/2/1/5
  • /ISO/Identified-Organization/6/1/4/1/43/45/1/10/2/3/1/4/2/1/5
  • /ISO/3/6/1/4/1/43/45/1/10/2/3/1/4/2/1/5
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysImage/h3cSysImageTable/h3cSysImageEntry/h3cSysImageType
  • /iso/identified-organization/dod/internet/private/enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysImage/h3cSysImageTable/h3cSysImageEntry/h3cSysImageType
  • /iso/identified-organization/dod/internet/private/enterprises/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysImage/h3cSysImageTable/h3cSysImageEntry/h3cSysImageType
  • /iso/identified-organization/dod/internet/private/enterprises/a3com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysImage/h3cSysImageTable/h3cSysImageEntry/h3cSysImageType
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysImage/h3cSysImageTable/h3cSysImageEntry/h3cSysImageType
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysImage/h3cSysImageTable/h3cSysImageEntry/h3cSysImageType
  • /iso/identified-organization/dod/internet/private/vendor-objects/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysImage/h3cSysImageTable/h3cSysImageEntry/h3cSysImageType
  • /iso/identified-organization/dod/internet/private/vendor-objects/a3com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysImage/h3cSysImageTable/h3cSysImageEntry/h3cSysImageType
  • /iso/org/dod/internet/private/enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysImage/h3cSysImageTable/h3cSysImageEntry/h3cSysImageType
  • /iso/org/dod/internet/private/enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysImage/h3cSysImageTable/h3cSysImageEntry/h3cSysImageType
  • /iso/org/dod/internet/private/enterprises/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysImage/h3cSysImageTable/h3cSysImageEntry/h3cSysImageType
  • /iso/org/dod/internet/private/enterprises/a3com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysImage/h3cSysImageTable/h3cSysImageEntry/h3cSysImageType
  • /iso/org/dod/internet/private/ldap-enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysImage/h3cSysImageTable/h3cSysImageEntry/h3cSysImageType
  • /iso/org/dod/internet/private/ldap-enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysImage/h3cSysImageTable/h3cSysImageEntry/h3cSysImageType
  • /iso/org/dod/internet/private/vendor-objects/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysImage/h3cSysImageTable/h3cSysImageEntry/h3cSysImageType
  • /iso/org/dod/internet/private/vendor-objects/a3com/jv-mib/huawei/h3c/h3cCommon/h3cSystemMan/h3cSystemManMIBObjects/h3cSysImage/h3cSysImageTable/h3cSysImageEntry/h3cSysImageType
  • Additional combinations skipped.

SNMP properties

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

Enumerated values

ValueName
1main
2backup
3none
4secure
5main-backup
6main-secure
7backup-secure
8main-backup-secure

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 A3COM-HUAWEI-SYS-MAN-MIB, the row index h3cSysImageIndex is declared as Integer32. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.43.45.1.10.2.3.1.4.2.1.5.<h3cSysImageIndex>. 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.43.45.1.10.2.3.1.4.2.1.5

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

h3cSysImageType · current

h3cSysImageType OBJECT-TYPE
    SYNTAX INTEGER
        {
        main(1),
        backup(2),
        none(3),
        secure(4),
        main-backup(5),
        main-secure(6),
        backup-secure(7),
        main-backup-secure(8)
        }
    MAX-ACCESS read-write
    STATUS current
    DESCRIPTION
        "
        It indicates the reloading sequence attribute of the image.

        For devices which support dual image:

        If the value is 'main(1)',the image will be the first image
        in the next reloading procedure. If the value is 'backup(2)',
        the image will be used if the main image fails. If the value
        is 'secure(4)', the image will be used if the main image and
        backup image both fail. If the value is 'none(3)',the image will
        not be used in the next reloading procedure.

        At the same time,you also can specify the main image by
        h3cSysReloadImage in h3cSysReloadScheduleTable. If the
        image is different from previous main image, the previous main image
        will not be main image again. And the image table will update with
        this variation. Vice versa, if you have defined the reload schedule,
        and then you define a new main image through h3cSysImageType when you
        are waiting the reload schedule to be executed, the real main image
        will be the latest one.


        It is strongly suggested to define the main image here, not by h3cSysReloadImage
        in h3cSysReloadScheduleTable.

        There are some rules for setting the value of h3cSysImageType:

        a)When a new image file is defined as 'main' or 'backup' file,the h3cSysImageType
          of old 'main' or 'backup' file will automatically be 'none'.
        b)It is forbidden to set 'none' attribute manually.
        c)It is forbidden to set 'secure' attribute manually.
        d)If 'main' image is set to 'backup', the file keeps 'main'. And vice versa.
          At this time, the file has 'main-backup' property.
        e)If the secure image is set to 'main' or 'backup', the file has 'main-secure' or 'backup-secure'property.
        f)If the secure image is set to 'main' and 'backup', the file has the 'main-backup-secure' property.
        g)If the none image is set to 'main' or 'backup', the file has the 'main' or 'backup' property.

        The following table describes whether it is ok to set to another state
        directly from original state.

                        +--------------+-----------+-------------+-------------+
                        |   set to     | set to    |  set to     |   set to    |
                        |              |           |             |             |
             original   |    'main'    | 'backup'  |  'none'     |  'secure'   |
             state      |              |           |             |             |
          --------------+--------------+-----------+-------------+-------------+
                        |              |           |             |             |
             main       |     ---      |   yes     |   no        |   no        |
                        |              |           |             |             |
                        |              |           |             |             |
          --------------+--------------+-----------+-------------|-------------+
                        |              |           |             |             |
             backup     |     yes      |   ---     |   no        |   no        |
                        |              |           |             |             |
          --------------+--------------+-----------+-------------|-------------+
                        |              |           |             |             |
                        |              |           |             |             |
              none      |     yes      |   yes     |   ---       |   no        |
                        |              |           |             |             |
          --------------+--------------+-----------+-------------+-------------+
                        |              |           |             |             |
              secure    |     yes      |   yes     |   no        |   ---       |
                        |              |           |             |             |
                        |              |           |             |             |
          --------------+--------------+-----------+-------------+-------------+

        If there is one main image in the system, one row of H3cSysReloadScheduleEntry
        whose  h3cSysReloadImage is equal to the main image's h3cSysImageIndex will be
        created automatically. But if any row is deleted, it will not be created
        automatically in h3cSysReloadScheduleTable.




        For the device which doesn't support dual image(main/backup):

        Only 'main' and 'none' is supported and it only can be set from none to main.
        When a new image file is defined as 'main' file,the h3cSysImageType of old 'main'
        file will automatically be 'none'.
        "
    ::= { h3cSysImageEntry 5 }

h3cSysImageType · current

h3cSysImageType OBJECT-TYPE
    SYNTAX INTEGER
        {
        main(1),
        backup(2),
        none(3),
        secure(4),
        main-backup(5),
        main-secure(6),
        backup-secure(7),
        main-backup-secure(8)
        }
    MAX-ACCESS read-write
    STATUS current
    DESCRIPTION
        "
        It indicates the reloading sequence attribute of the image.

        For devices which support dual image:

        If the value is 'main(1)',the image will be the first image
        in the next reloading procedure. If the value is 'backup(2)',
        the image will be used if the main image fails. If the value
        is 'secure(4)', the image will be used if the main image and
        backup image both fail. If the value is 'none(3)',the image will
        not be used in the next reloading procedure.

        At the same time,you also can specify the main image by
        h3cSysReloadImage in h3cSysReloadScheduleTable. If the
        image is different from previous main image, the previous main image
        will not be main image again. And the image table will update with
        this variation. Vice versa, if you have defined the reload schedule,
        and then you define a new main image through h3cSysImageType when you
        are waiting the reload schedule to be executed, the real main image
        will be the latest one.


        It is strongly suggested to define the main image here, not by h3cSysReloadImage
        in h3cSysReloadScheduleTable.

        There are some rules for setting the value of h3cSysImageType:

        a)When a new image file is defined as 'main' or 'backup' file,the h3cSysImageType
          of old 'main' or 'backup' file will automatically be 'none'.
        b)It is forbidden to set 'none' attribute manually.
        c)It is forbidden to set 'secure' attribute manually.
        d)If 'main' image is set to 'backup', the file keeps 'main'. And vice versa.
          At this time, the file has 'main-backup' property.
        e)If the secure image is set to 'main' or 'backup', the file has 'main-secure' or 'backup-secure'property.
        f)If the secure image is set to 'main' and 'backup', the file has the 'main-backup-secure' property.
        g)If the none image is set to 'main' or 'backup', the file has the 'main' or 'backup' property.

        The following table describes whether it is ok to set to another state
        directly from original state.

                        +--------------+-----------+-------------+-------------+
                        |   set to     | set to    |  set to     |   set to    |
                        |              |           |             |             |
             original   |    'main'    | 'backup'  |  'none'     |  'secure'   |
             state      |              |           |             |             |
          --------------+--------------+-----------+-------------+-------------+
                        |              |           |             |             |
             main       |     ---      |   yes     |   no        |   no        |
                        |              |           |             |             |
                        |              |           |             |             |
          --------------+--------------+-----------+-------------|-------------+
                        |              |           |             |             |
             backup     |     yes      |   ---     |   no        |   no        |
                        |              |           |             |             |
          --------------+--------------+-----------+-------------|-------------+
                        |              |           |             |             |
                        |              |           |             |             |
              none      |     yes      |   yes     |   ---       |   no        |
                        |              |           |             |             |
          --------------+--------------+-----------+-------------+-------------+
                        |              |           |             |             |
              secure    |     yes      |   yes     |   no        |   ---       |
                        |              |           |             |             |
                        |              |           |             |             |
          --------------+--------------+-----------+-------------+-------------+

        If there is one main image in the system, one row of H3cSysReloadScheduleEntry
        whose  h3cSysReloadImage is equal to the main image's h3cSysImageIndex will be
        created automatically. But if any row is deleted, it will not be created
        automatically in h3cSysReloadScheduleTable.




        For the device which doesn't support dual image(main/backup):

        Only 'main' and 'none' is supported and it only can be set from none to main.
        When a new image file is defined as 'main' file,the h3cSysImageType of old 'main'
        file will automatically be 'none'.
        "
    ::= { h3cSysImageEntry 5 }

Meaning

Descriptions

1 unique

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

It indicates the reloading sequence attribute of the image. For devices which support dual image: If the value is 'main(1)',the image will be the first image in the next reloading procedure. If the value is 'backup(2)', the image will be used if the main image fails. If the value is 'secure(4)', the image will be used if the main image and backup image both fail. If the value is 'none(3)',the image will not be used in the next reloading procedure. At the same time,you also can specify the main image by h3cSysReloadImage in h3cSysReloadScheduleTable. If the image is different from previous main image, the previous main image will not be main image again. And the image table will update with this variation. Vice versa, if you have defined the reload schedule, and then you define a new main image through h3cSysImageType when you are waiting the reload schedule to be executed, the real main image will be the latest one. It is strongly suggested to define the main image here, not by h3cSysReloadImage in h3cSysReloadScheduleTable. There are some rules for setting the value of h3cSysImageType: a)When a new image file is defined as 'main' or 'backup' file,the h3cSysImageType of old 'main' or 'backup' file will automatically be 'none'. b)It is forbidden to set 'none' attribute manually. c)It is forbidden to set 'secure' attribute manually. d)If 'main' image is set to 'backup', the file keeps 'main'. And vice versa. At this time, the file has 'main-backup' property. e)If the secure image is set to 'main' or 'backup', the file has 'main-secure' or 'backup-secure'property. f)If the secure image is set to 'main' and 'backup', the file has the 'main-backup-secure' property. g)If the none image is set to 'main' or 'backup', the file has the 'main' or 'backup' property. The following table describes whether it is ok to set to another state directly from original state. +--------------+-----------+-------------+-------------+ | set to | set to | set to | set to | | | | | | original | 'main' | 'backup' | 'none' | 'secure' | state | | | | | --------------+--------------+-----------+-------------+-------------+ | | | | | main | --- | yes | no | no | | | | | | | | | | | --------------+--------------+-----------+-------------|-------------+ | | | | | backup | yes | --- | no | no | | | | | | --------------+--------------+-----------+-------------|-------------+ | | | | | | | | | | none | yes | yes | --- | no | | | | | | --------------+--------------+-----------+-------------+-------------+ | | | | | secure | yes | yes | no | --- | | | | | | | | | | | --------------+--------------+-----------+-------------+-------------+ If there is one main image in the system, one row of H3cSysReloadScheduleEntry whose h3cSysReloadImage is equal to the main image's h3cSysImageIndex will be created automatically. But if any row is deleted, it will not be created automatically in h3cSysReloadScheduleTable. For the device which doesn't support dual image(main/backup): Only 'main' and 'none' is supported and it only can be set from none to main. When a new image file is defined as 'main' file,the h3cSysImageType of old 'main' file will automatically be 'none'.

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

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

Status in source: current.

Names: h3cSysImageType

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "h3cSysImageType",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "main",
    "(",
    "1",
    ")",
    ",",
    "backup",
    "(",
    "2",
    ")",
    ",",
    "none",
    "(",
    "3",
    ")",
    ",",
    "secure",
    "(",
    "4",
    ")",
    ",",
    "main-backup",
    "(",
    "5",
    ")",
    ",",
    "main-secure",
    "(",
    "6",
    ")",
    ",",
    "backup-secure",
    "(",
    "7",
    ")",
    ",",
    "main-backup-secure",
    "(",
    "8",
    ")",
    "}",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\" It indicates the reloading sequence attribute of the image. For devices which support dual image: If the value is 'main(1)',the image will be the first image in the next reloading procedure. If the value is 'backup(2)', the image will be used if the main image fails. If the value is 'secure(4)', the image will be used if the main image and backup image both fail. If the value is 'none(3)',the image will not be used in the next reloading procedure. At the same time,you also can specify the main image by h3cSysReloadImage in h3cSysReloadScheduleTable. If the image is different from previous main image, the previous main image will not be main image again. And the image table will update with this variation. Vice versa, if you have defined the reload schedule, and then you define a new main image through h3cSysImageType when you are waiting the reload schedule to be executed, the real main image will be the latest one. It is strongly suggested to define the main image here, not by h3cSysReloadImage in h3cSysReloadScheduleTable. There are some rules for setting the value of h3cSysImageType: a)When a new image file is defined as 'main' or 'backup' file,the h3cSysImageType of old 'main' or 'backup' file will automatically be 'none'. b)It is forbidden to set 'none' attribute manually. c)It is forbidden to set 'secure' attribute manually. d)If 'main' image is set to 'backup', the file keeps 'main'. And vice versa. At this time, the file has 'main-backup' property. e)If the secure image is set to 'main' or 'backup', the file has 'main-secure' or 'backup-secure'property. f)If the secure image is set to 'main' and 'backup', the file has the 'main-backup-secure' property. g)If the none image is set to 'main' or 'backup', the file has the 'main' or 'backup' property. The following table describes whether it is ok to set to another state directly from original state. +--------------+-----------+-------------+-------------+ | set to | set to | set to | set to | | | | | | original | 'main' | 'backup' | 'none' | 'secure' | state | | | | | --------------+--------------+-----------+-------------+-------------+ | | | | | main | --- | yes | no | no | | | | | | | | | | | --------------+--------------+-----------+-------------|-------------+ | | | | | backup | yes | --- | no | no | | | | | | --------------+--------------+-----------+-------------|-------------+ | | | | | | | | | | none | yes | yes | --- | no | | | | | | --------------+--------------+-----------+-------------+-------------+ | | | | | secure | yes | yes | no | --- | | | | | | | | | | | --------------+--------------+-----------+-------------+-------------+ If there is one main image in the system, one row of H3cSysReloadScheduleEntry whose h3cSysReloadImage is equal to the main image's h3cSysImageIndex will be created automatically. But if any row is deleted, it will not be created automatically in h3cSysReloadScheduleTable. For the device which doesn't support dual image(main/backup): Only 'main' and 'none' is supported and it only can be set from none to main. When a new image file is defined as 'main' file,the h3cSysImageType of old 'main' file will automatically be 'none'. \"",
    "::=",
    "{",
    "h3cSysImageEntry",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "main",
            1
          ],
          [
            "backup",
            2
          ],
          [
            "none",
            3
          ],
          [
            "secure",
            4
          ],
          [
            "main-backup",
            5
          ],
          [
            "main-secure",
            6
          ],
          [
            "backup-secure",
            7
          ],
          [
            "main-backup-secure",
            8
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "It indicates the reloading sequence attribute of the image. For devices which support dual image: If the value is 'main(1)',the image will be the first image in the next reloading procedure. If the value is 'backup(2)', the image will be used if the main image fails. If the value is 'secure(4)', the image will be used if the main image and backup image both fail. If the value is 'none(3)',the image will not be used in the next reloading procedure. At the same time,you also can specify the main image by h3cSysReloadImage in h3cSysReloadScheduleTable. If the image is different from previous main image, the previous main image will not be main image again. And the image table will update with this variation. Vice versa, if you have defined the reload schedule, and then you define a new main image through h3cSysImageType when you are waiting the reload schedule to be executed, the real main image will be the latest one. It is strongly suggested to define the main image here, not by h3cSysReloadImage in h3cSysReloadScheduleTable. There are some rules for setting the value of h3cSysImageType: a)When a new image file is defined as 'main' or 'backup' file,the h3cSysImageType of old 'main' or 'backup' file will automatically be 'none'. b)It is forbidden to set 'none' attribute manually. c)It is forbidden to set 'secure' attribute manually. d)If 'main' image is set to 'backup', the file keeps 'main'. And vice versa. At this time, the file has 'main-backup' property. e)If the secure image is set to 'main' or 'backup', the file has 'main-secure' or 'backup-secure'property. f)If the secure image is set to 'main' and 'backup', the file has the 'main-backup-secure' property. g)If the none image is set to 'main' or 'backup', the file has the 'main' or 'backup' property. The following table describes whether it is ok to set to another state directly from original state. +--------------+-----------+-------------+-------------+ | set to | set to | set to | set to | | | | | | original | 'main' | 'backup' | 'none' | 'secure' | state | | | | | --------------+--------------+-----------+-------------+-------------+ | | | | | main | --- | yes | no | no | | | | | | | | | | | --------------+--------------+-----------+-------------|-------------+ | | | | | backup | yes | --- | no | no | | | | | | --------------+--------------+-----------+-------------|-------------+ | | | | | | | | | | none | yes | yes | --- | no | | | | | | --------------+--------------+-----------+-------------+-------------+ | | | | | secure | yes | yes | no | --- | | | | | | | | | | | --------------+--------------+-----------+-------------+-------------+ If there is one main image in the system, one row of H3cSysReloadScheduleEntry whose h3cSysReloadImage is equal to the main image's h3cSysImageIndex will be created automatically. But if any row is deleted, it will not be created automatically in h3cSysReloadScheduleTable. For the device which doesn't support dual image(main/backup): Only 'main' and 'none' is supported and it only can be set from none to main. When a new image file is defined as 'main' file,the h3cSysImageType of old 'main' file will automatically be 'none'."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.43)

Jeremy Siegel

Siblings (4)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.43.45.1.10.2.3.1.4.2.1.1 h3cSysImageIndex00
1.3.6.1.4.1.43.45.1.10.2.3.1.4.2.1.2 h3cSysImageName00
1.3.6.1.4.1.43.45.1.10.2.3.1.4.2.1.3 h3cSysImageSize00
1.3.6.1.4.1.43.45.1.10.2.3.1.4.2.1.4 h3cSysImageLocation00