hh3cSysImageType

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
hh3cSysReloadImage in hh3cSysReloadScheduleTable. 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 hh3cSysImageType 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 hh3cSysReloadImage
in hh3cSysReloadScheduleTable.
              
There are some rules for setting the value of hh3cSysImageType:
              
a)When a new image file is defined as 'main' or 'backup' file,the hh3cSysImageType
  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 Hh3cSysReloadScheduleEntry
whose  hh3cSysReloadImage is equal to the main image's hh3cSysImageIndex will be
created automatically. But if any row is deleted, it will not be created
automatically in hh3cSysReloadScheduleTable.
              
              
              
              
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 hh3cSysImageType of old 'main'
file will automatically be 'none'.

MIB

HH3C-SYS-MAN-MIB

OID

.1.3.6.1.4.1.25506.2.3.1.4.2.1.5

Type

column

Access

readwrite

Status

current

Parent

hh3cSysImageEntry

Table

hh3cSysImageTable

Siblings

4