HPN-ICF-SYS-MAN-MIB: View SNMP OID List / Download MIB

This MIB contains objects to manage the system. It focuses on the display of current configure file and image file,and the definition of reloading image. Add the support for XRN.

This node gives the current local time of the system. The unit of it is DateAndTime.

This node indicates the status of summer time. If the value of this node is enable, means that summer time is enabled. If the value is disable, means that summer time is disabled. Enumeration: 'enable': 1, 'disable': 2.

This node describes the name of time zone in summer. The string is only used to display in local time when summer time is running. That the value of hpnicfSysLocalClock has the time zone information means that summer time is running.

This node provides the execute method of summer time. oneOff(1): means that summer time only takes effect at specified time. repeating(2): means that summer time takes effect in specified month/day once a year. Enumeration: 'repeating': 2, 'oneOff': 1.

This node provides the start time of summer time.

This node provides the end time of summer time. The end time must be more than start time one day and less than start time one year.

This node provides the offset time of summer time. The offset time(in seconds) means that how much time need to be appended to the local time.

This node gives the current local time of the system. For example, Tuesday May 26, 2002 at 1:30:15 would be displayed as: 2002-5-26T13:30:15.0Z

The current status of system. A configuration file, an image file and bootrom information are used to describe the current status.

An entry of hpnicfSysCurTable.

The value of this object is the entity index which depends on the implementation of ENTITY-MIB. If ENTITY-MIB is not supported, the value for this object is the unit ID for XRN devices , 0 for non-XRN device which has only one mainboard, the board number for non-XRN device which have several mainboards.

The startup configuration file currently used by the specified entity. If the value of it is zero, no configuration file is used. It will be the value of corresponding hpnicfSysCFGFileIndex in hpnicfSysCFGFileTable.

The image file currently used by the specified entity. It will be the value of corresponding hpnicfSysImageIndex in hpnicfSysImageTable.

The bootrom file currently used by the specified entity.

The default value of this object is the same as the value of hpnicfSysCurBtmFileName. The value will be changed after updating the bootrom successfully. This bootrom will take effect on next startup.

The object points one row in hpnicfSysReloadScheduleTable. Its value is equal to the value of hpnicfSysReloadScheduleIndex. When a reload action is finished, the value of it would be zero which means no any reload schedule is selected.

Writing reloadOnSchedule(2) to this object performs the reload operation on schedule. If hpnicfSysReloadScheduleTime is not set, the value of hpnicfSysReloadAction can't be set to 'reloadOnSchedule(2)'. Writing reloadAtOnce(3)to this object performs the reload operation at once, regardless of the hpnicfSysReloadScheduleTime. When reloadCancel(4)is set, the scheduled reload action will be cancelled and the value of hpnicfSysReloadAction will be 'reloadUnavailable(1)',the value of hpnicfSysReloadSchedule will be 0, hpnicfSysReloadTag will be given a value of zero length, but the content of hpnicfSysReloadScheduleTable will remain. The hpnicfSysReloadSchedule and hpnicfSysReloadTag determine the reload entity(ies) in mutually exclusive way. And the hpnicfSysReloadSchedule will be handled at first. If the value of hpnicfSysReloadSchedule is invalid, then the hpnicfSysReloadTag will be handled. If the value of hpnicfSysReloadSchedule is valid, the value of hpnicfSysReloadTag is ignored and a reload action will be implemented to the entity specified by hpnicfSysReloadEntity in the entry pointed by hpnicfSysReloadSchedule. If hpnicfSysReloadSchedule is valid, but the entry hpnicfSysReloadSchedule 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 hpnicfSysReloadTag must be specified to select the reload parameters in the hpnicfSysReloadSceduelTable, and hpnicfSysReloadSchedule 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 hpnicfSysReloadSceduelTable with the same tag in hpnicfSysReloadSceduelTagList. When a reload action is done, or there is no reload action, the value should be reloadUnavailable(1). Enumeration: 'reloadUnavailable': 1, 'reloadAtOnce': 3, 'reloadCancel': 4, 'reloadOnSchedule': 2.

A reload parameters set table. The table is exclusively used for reloading. When reloading action finished, the value of the table may be empty or still exist. If the mainboard in non-XRN device or all the units of the fabric in XRN device are reloaded,then the table will be refreshed.

Entry of hpnicfSysReloadScheduleTable.

The index of hpnicfSysReloadScheduleTable. There are two parts for this index depicted as follows: 31 15 0 +++++++++++++++++++++++++++++++++++++++++ + physical index + random index + ( bit 16..31 ) ( bit 0..15 ) +++++++++++++++++++++++++++++++++++++++++ From bit0 to bit15 (two bytes), if the row is automatic created, the value is zero, and if the row is created by users, then the value is determined by the users. From bit16 to bit31 (two bytes) is the physical index the same as the entPhysicalIndex specified in ENTITY-MIB. For XRN devices, physical index is the value of a chassis entPhysicalIndex. 0 for non-XRN device which has only one main board, the board number for non-XRN device which have multiple main boards.

The value of hpnicfSysReloadEntity indicates an entry in entPhysicalTable, which is the physical entity to be reloaded. If ENTITY-MIB is not supported,the value for this object is the unit ID for XRN devices , 0 for non-XRN device which has only one mainboard, the board number for non-XRN device which have several mainboards. Each entity has only one row in hpnicfSysReloadScheduleTable.

The value indicates an entry in hpnicfSysCFGFileTable. It defines a configuration file for reload action. It is the value of corresponding hpnicfSysCFGFileIndex in hpnicfSysCFGFileTable. The zero value means no configuration file has been set for this entry, and no configuration file is used during system reloading.

The value indicates an entry in hpnicfSysImageTable. It defines an image file for reload action. It is the value of corresponding hpnicfSysImageIndex in hpnicfSysImageTable. If dual image is supported, the main image attribute can be set through this object or by hpnicfSysImageType of hpnicfSysImageTable of the entity. It is strongly suggested to set this attribute by the latter. If main image attribute is set here, the hpnicfSysImageType in hpnicfSysImageTable of the corresponding entity will be updated, and vice versa. Before reboot, the device will check the validation of the entry. If the file does not exist, the device will not reboot and a trap will be send to NMS.

The reason of system's reloading. It is a zero length octet string when not set.

Specify the local time at which the reload action will occur. we will only take octet strings with length 8 for this object which indicates the local time of the switch. The maximum scheduled interval between the specified time and the current system clock time is 24 days . field octets contents range ----- ------ -------- ----- 1 1-2 year 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 For example, Tuesday May 26, 1992 at 1:30:15 PM would be displayed as: 1992-5-26,13:30:15 If the set value is less than the value of hpnicfSysLocalClock or beyond the maximum scheduled time limit, a bad value error occurred. The value of all-zero octet strings indicates system reload at once if the reload action is reloadOnSchedule(2).

If one of the value of hpnicfSysReloadEntity,hpnicfSysReloadImage is invalid, the value of hpnicfSysReloadRowStatus can not be set to the value of ACTIVE. A valid entry means the specified element is available in current system.

It specifies a tag list for the entry.

This object contains a single tag value which is used to select entries in the hpnicfSysReloadScheduleTable. In the hpnicfSysReloadScheduleTable,any entry that contains a tag value which is equal to the value of this object is selected. For example, the value of hpnicfSysReloadTag is 'TOM',and the hpnicfSysReloadScheduleTagList of each hpnicfSysReloadScheduleTable entry are as follows: 1)'TOM,ROBERT,MARY' 2)'TOM,DAVE' 3)'DAVE,MARY' Since there are 'TOM' in 1) and 2),so 1) and 2) are selected. If this object contains a value of zero length, no entries are selected.

The number of system images. It indicates the total entries of hpnicfSysImageTable.

The system image management table. When 'copy srcfile destfile' is executed via the CLI, if destfile is not existed, then hpnicfSysImageType of the new file will be 'none'; otherwise hpnicfSysImageType keeps its current value. When 'move srcfile destfile' is executed via the CLI, hpnicfSysImageType and hpnicfSysImageIndex remain the same while hpnicfSysImageLocation changes. When 'rename srcfile' is executed via the CLI,hpnicfSysImageType and hpnicfSysImageIndex remain the same while hpnicfSysImageName changes. When 'delete srcfile' is executed via the CLI, the file is deleted from hpnicfSysImageTable while index of the file keeps and will not be allocated.

An entity image entry. Each entry consists of information of an entity image. The hpnicfSysImageIndex exclusively defines an image file.

There are two parts for the index depicted as follows: 31 15 0 +++++++++++++++++++++++++++++++++++ + physical index + image index + +++++++++++++++++++++++++++++++++++ From bit0 to bit15 (two bytes) is the image index;Image file Index is a monotonically increasing integer for the sole purpose of indexing events. When it reaches the maximum value, an extremely unlikely event, the agent wraps the value back to 1 and may flush existing entries. From bit16 to bit31 (two bytes) is the physical index the same as the entPhysicalIndex specified in ENTITY-MIB. If ENTITY-MIB is not supported,the value for this object is the unit ID for XRN devices ,0 for non-XRN device which has only one main board,the board number for non-XRN device which have several main boards. Any index beyond the above range will not be supported. If a file is added in, its hpnicfSysImageIndex will be the maximum image index plus one. If the image file is removed, renamed, or moved from one place to another, its hpnicfSysImageIndex is not reallocated. If the image file's content is replaced, its hpnicfSysImageIndex will not change.

The file name of the image. It MUST NOT contain the path of the file.

Size of the file in bytes.

The directory path of the image. Its form should be the same as what defined in file system. Currently it is defined as follows: For mainboard: flash:/ For slave mainboard and subboards: slotN#flash:/ For XRN devices: unitN>slotN#flash:/

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 hpnicfSysReloadImage in hpnicfSysReloadScheduleTable. 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 hpnicfSysImageType 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 hpnicfSysReloadImage in hpnicfSysReloadScheduleTable. There are some rules for setting the value of hpnicfSysImageType: a)When a new image file is defined as 'main' or 'backup' file,the hpnicfSysImageType 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 HpnicfSysReloadScheduleEntry whose hpnicfSysReloadImage is equal to the main image's hpnicfSysImageIndex will be created automatically. But if any row is deleted, it will not be created automatically in hpnicfSysReloadScheduleTable. 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 hpnicfSysImageType of old 'main' file will automatically be 'none'. Enumeration: 'main-backup': 5, 'none': 3, 'secure': 4, 'main-backup-secure': 8, 'backup-secure': 7, 'main-secure': 6, 'main': 1, 'backup': 2.

The number of the configuration files in the system. It indicates the total entries of hpnicfSysCFGFileTable.

A table of configuration files in this system. At present, the system doesn't support dual configure file, it should act as 'dual image' if dual configure file is supported.

A configuration file entry. Each entry consists of information of a configuration file. hpnicfSysCFGFileIndex exclusively decides a configuration file.

There are two parts for the index depicted as follows: 31 15 0 +++++++++++++++++++++++++++++++++++ + physical index + cfgFile index + +++++++++++++++++++++++++++++++++++ From bit0 to bit15 (two bytes) is the configuration file index; the configuration file index is a monotonically increasing integer for the sole purpose of indexing events. When it reaches the maximum value, an extremely unlikely event, the agent wraps the value back to 1 and may flush existing entries. From bit16 to bit31 (two bytes) is the physical index the same as the entPhysicalIndex specified in ENTITY-MIB. If ENTITY-MIB is not supported, the value for this object is the unit ID for XRN devices ,0 for non-XRN device which has only one slot,the board number for non-XRN device which have several slots. Any index beyond the above range will not be supported.

Configuration file name. The name should not include the colon (:) character as it is a special separator character used to delineate the device name, partition name and the file name.

Size of the file in bytes. Note that it does not include the size of the filesystem file header. File size will always be non-zero.

The directory path of the image. Its form should be the same as what defined in filesystem. Currently it is defined as follows: For mainboard: flash:/ For slave mainboard and subboards: slotN#flash:/ For XRN devices: unitN>slotN#flash:/

This object shows the maximum number of hpnicfSysBtmLoadEntry in each device/unit.

This table is used to update the bootrom and show the results of the update operation. The bootrom files are listed at the hpnicfFlhFileTable. These files are used to update bootrom.

Entries in the hpnicfSysBtmLoadTable are created and deleted using the hpnicfSysBtmRowStatus object. When a new row is being created and the number of entries is hpnicfSysBtmLoadMaxNumber, the row with minimal value of hpnicfSysBtmLoadTime and the value of hpnicfSysBtmFileType is none(2), should be destroyed automatically.

The index of hpnicfSysBtmLoadTable. There are two parts for this index depicted as follows: 31 15 0 +++++++++++++++++++++++++++++++++++++++++ + physical index + random index + ( bit 16..31 ) ( bit 0..15 ) +++++++++++++++++++++++++++++++++++++++++ From bit0 to bit15 (two bytes), if the row is created by command line, the value is determined by system, and if the row is created by SNMP, the value is determined by users. From bit16 to bit31 (two bytes) is the physical index the same as the entPhysicalIndex specified in ENTITY-MIB. If ENTITY-MIB is not supported, the value of this object is the unit ID for XRN devices, 0 for non-XRN device which has only one main board, the board number for non-XRN device which has multiple main boards.

The bootrom file name is determined by the users. The file must exist in corresponding entity. The validity of the bootrom file will be identified by system. If the file is invalid, the bootrom should fail to be updated, and the value of hpnicfSysBtmErrorStatus should be failed(4).

main(1) - The effective bootrom file. none(2) - The noneffective file. When bootrom is being updated, this object must be set to main(1). When bootrom is updated successfully, this object should be main(1), and the former object with the same physical index should be none(2). When bootrom failed to be updated, this object should be none(2). Enumeration: 'none': 2, 'main': 1.

Only support active(1), createAndGo(4), destroy(6). When a row is created successfully, the value of this object should be active(1), the value of hpnicfSysBtmFileName and hpnicfSysBtmFileType can not be modified by users. When bootrom is being updated, the value of hpnicfSysBtmErrorStatus is inProgress(2). When bootrom failed to be updated, the value of hpnicfSysBtmErrorStatus should be failed(4). When bootrom is updated successfully, the value of hpnicfSysBtmErrorStatus should be success(3). The value of hpnicfSysCurUpdateBtmFileName should change to the new bootrom file name. When another row is created successfully with the same physical index, and the update is successful, then the value of former hpnicfSysBtmFileType should be none(2) automatically. If a row is destroyed, hpnicfSysCurUpdateBtmFileName should not change. If a device/unit reboots, hpnicfSysBtmLoadTable should be empty.

This object shows the status of the specified operation after creating a row. invalidFile(1) - file is invalid. inProgress(2) - the operation is in progress. success(3) - the operation was done successfully. failed(4) - the operation failed. Enumeration: 'failed': 4, 'inProgress': 2, 'invalidFile': 1, 'success': 3.

This object indicates operation time.

The number of software packages. It indicates the total entries of hpnicfSysPackageTable.

The system package management table.

An software package entry. Each entry consists of information of an software package.

There are two parts for the index depicted as follows: 31 15 0 +++++++++++++++++++++++++++++++++++ + physical index + package index + +++++++++++++++++++++++++++++++++++ From bit0 to bit15 (two bytes) is the Package index; Package file Index is a monotonically increasing integer for the sole purpose of indexing events. When it reaches the maximum value, an extremely unlikely event, the agent wraps the value back to 1 and may flush existing entries. From bit16 to bit31 (two bytes) is the physical index the same as the entPhysicalIndex specified in ENTITY-MIB. Any index beyond the above range will not be supported. If a file is added in, its hpnicfSysPackageIndex will be the maximum image index plus one. If the package file is removed, renamed, or moved from one place to another, its hpnicfSysPackageIndex is not reallocated. If the package file's content is replaced, its hpnicfSysPackageIndex will not change.

The file name of the package. It MUST NOT contain the path of the file.

Size of the file in bytes.

The directory path of the package. Its form should be the same as what defined in file system. Currently it is defined as follows: For mainboard: flash:/ For slave mainboard and subboards: slotN#flash:/

It indicates the type of the package file. boot : kernel, file system, memory management and other core components. system : interface management, configuration management and other basic system package. feature : feature packages, providing different services. patch : patch file contains fixes for a specific defect. Enumeration: 'patch': 4, 'boot': 1, 'system': 2, 'feature': 3.

It indicates the attribute of the package file. If the value is 'primary', the package will be the first package in the next reloading procedure. If the value is 'secondary', the package will be used if the primary package fails. If the value is 'none', it will not be used in the next reloading procedure. Enumeration: 'primarySecondary': 4, 'none': 1, 'primary': 2, 'secondary': 3.

It indicates the status of the package file. If this file is used in the current system, its status is 'active'. Enumeration: 'active': 1, 'inactive': 2.

It is the description of the package.

Indicate the feature of the package. Different package files could be the same feature.

Indicate the version of the package.

File attribute of the startup image for an extended device to load from the parent device. Examples of extended devices include PEXs and firewall modules. The none attribute is returned if the image is not for extended devices, or if the load attribute is not specified. Enumeration: 'primarySecondary': 4, 'none': 1, 'primary': 2, 'secondary': 3.

Indicates whether the image file is for an extended device or the parent device. Examples of extended devices include PEXs and firewall modules.

The maximum number of the entries in hpnicfSysPackageOperateTable.

A table of package file operate.

An operate request entry.

The unique index value of a row in this table.

Specify the package file in the hpnicfSysPackageTable.

activate or deactivate a package in the hpnicfSysPackageTable. Enumeration: 'active': 1, 'inactive': 2.

the status of this table entry. When the status is active all the object's value in the entry is not allowed to modified.

the result of the operation. Enumeration: 'opNotSupport': 5, 'opInProgress': 1, 'opUnknownFailure': 3, 'opInvalidFile': 4, 'opSuccess': 2.

The number of software IPE(Image Package Envelop) files. It indicates the total entries of hpnicfSysIpeFileTable.

The system IPE file manage table.

An IPE package file entry. Each entry consists of information of an IPE package file. hpnicfSysIpeFileIndex exclusively decides an IPE file.

There are two parts for the index depicted as follows: 31 15 0 +++++++++++++++++++++++++++++++++++ + physical index + IPE index + +++++++++++++++++++++++++++++++++++ From bit0 to bit15 (two bytes) is the IPE file index; IPE file Index is a monotonically increasing integer for the sole purpose of indexing events. When it reaches the maximum value, an extremely unlikely event, the agent wraps the value back to 1 and may flush existing entries. From bit16 to bit31 (two bytes) is the physical index the same as the entPhysicalIndex specified in ENTITY-MIB. Any index beyond the above range will not be supported. If a file is added in, its hpnicfSysIpeFileIndex will be the maximum image ndex plus one. If the IPE file is removed, renamed, or moved from one place to another, its hpnicfSysIpeFileIndex is not reallocated. If the IPE file's content is replaced, its hpnicfSysIpeFileIndex will not change.

The file name of the IPE file. It MUST NOT contain the path of the file.

Size of the file in bytes.

The directory path of the IPE file. Its form should be the same as what defined in file system. Currently it is defined as follows: For mainboard: flash:/ For slave mainboard and subboards: slotN#flash:/

Device models for which the IPE file contains software images. For the ease of software upgrade, an IPE file might contain software images for a parent device and extended devices. Examples of extended devices include PEXs and firewall modules.

The IPE package file table. It shows the package files in the IPE file.

An entry of the hpnicfIpePackageTable. Indexed by hpnicfSysIpeFileIndex and hpnicfSysIpePackageIndex.

It is the IPE package index; IPE Package Index is a monotonically increasing integer for the sole purpose of indexing events. When it reaches the maximum value, an extremely unlikely event, the agent wraps the value back to 1 and may flush existing entries. Any index beyond the above range will not be supported.

The file name of the package file.

Size of the package file in bytes.

It indicates the type of the package file. boot : kernel, file system, memory management and other core components. system : interface management, configuration management and other basic system package. feature : feature packages, providing different services. patch : patch file contains fixes for a specific defect. Enumeration: 'patch': 4, 'boot': 1, 'system': 2, 'feature': 3.

It is the description of the package.

Indicate the feature of the package.

The version of the package.

Indicates whether the image package file is for an extended device, the parent device, or both. Examples of extended devices include PEXs and firewall modules.

A table of IPE file operate.

An operate request entry.

The unique index value of a row in this table.

Specify the IPE file in the hpnicfSysIpeFileTable. This IPE file will be unpacked to package files.

It indicates the attribute of the IPE file when it is used in the reloading. If the value is 'primary', the packages in the IPE file will be the first packages in the next reloading procedure. If the value is 'secondary', the package in the IPE file will be used if the primary packages fails. If the value is 'none', the IPE file is only unpacked, will not be used in the reloading procedure. Enumeration: 'primarySecondary': 4, 'none': 1, 'primary': 2, 'secondary': 3.

the status of this table entry. When the status is active all the object's value in the entry is not allowed to modified.

the result of the operation. Enumeration: 'opInProgress': 1, 'opFileOpenError': 6, 'opInvalidFile': 4, 'opDeviceFull': 5, 'opSuccess': 2, 'opUnknownFailure': 3.

Sets images as primary startup images, secondary startup images, or both. Primary startup images are also called 'main' startup images. For extended devices, startup images saved on their local media are called 'local startup images,' and images saved on the parent device are called 'remote startup images.' none: Returns a success without setting image attributes. done: Clears data for the previous startup image operation. This object must be set 'done' before each startup image operation. -------------------------+-----------------------+--------------------------------------------------- Action | Parent devices | Extended devices -------------------------+-----------------------+--------------------------------------------------- bootLoadPrimary | Sets images as the | Sets images as the primary startup images | primary startup | | images | With storage medium: Sets both local and | | remote startup images | | Without storage medium: Sets remote startup images -------------------------+-----------------------+--------------------------------------------------- bootLoadSecondary | Sets images as the | Sets images as the backup startup images | backup startup images | | | With storage medium: Sets both local and | | remote startup images | | Without storage medium: Sets remote startup images -------------------------+-----------------------+--------------------------------------------------- bootLoadPrimarySecondary | Sets images as both | Sets images as both the primary and backup startup | the primary and | images | backup startup images | With storage medium: Sets both local and | | remote startup images | | Without storage medium: Sets remote startup images -------------------------+-----------------------+--------------------------------------------------- bootPrimary | Sets images as the | Sets images as the primary startup images | primary startup | | images | With storage medium: Sets local startup images | | Without storage medium: N/A -------------------------+-----------------------+--------------------------------------------------- bootSecondary | Sets images as the | Sets images as the backup startup images | backup startup images | | | With storage medium: Sets local startup images | | Without storage medium: N/A -------------------------+-----------------------+--------------------------------------------------- bootPrimarySecondary | Sets images as both | Sets images as both the primary and backup startup | the primary and | images | backup startup images | With storage medium: Sets local startup images | | Without storage medium: N/A -------------------------+-----------------------+--------------------------------------------------- loadPrimary | N/A | Sets images as the remote primary startup images -------------------------+-----------------------+--------------------------------------------------- loadSecondary | N/A | Sets images as the remote backup startup images -------------------------+-----------------------+--------------------------------------------------- loadPrimarySecondary | N/A | Sets images as both the remote primary and | | backup startup images -------------------------+-----------------------+--------------------------------------------------- Enumeration: 'none': 1, 'bootLoadPrimary': 3, 'bootLoadSecondary': 4, 'bootLoadPrimarySecondary': 5, 'bootSecondary': 7, 'done': 2, 'loadPrimary': 9, 'loadPrimarySecondary': 11, 'bootPrimary': 6, 'bootPrimarySecondary': 8, 'loadSecondary': 10.

Determines whether to overwrite the existing image file with the same name as the downloaded image file.

Determines whether the IPE file will be removed when the startup images are set successfully. If this object is set to TRUE, the IPE file will be removed.

Status of the startup image set operation. Enumeration: 'doing': 2, 'failed': 4, 'none': 1, 'success': 3.

Startup image operation failure reason. The field is empty if the operation was successful.

Table of images to be set as startup images. It should be used when hpnicfSysBootIpeTable is empty.

Entry of the image table.

Index of the software images. The index must be included in hpnicfSysPackageTable.

Row status of the image entry.

Table of the IPE files to be set for startup. It should be used when hpnicfSysBootPackageTable is empty.

Entry in the IPE file table.

IPE file index. The index must be included in hpnicfSysIpeFileTable.

Row status of the IPE file table entry.

Table of startup image operation results. This table shows the result for each card.

Entry in the startup image operation result table.

Index of a startup image operation result. It is identical to the entity index of each card.

Status of the startup image set operation. Enumeration: 'doing': 2, 'failed': 4, 'none': 1, 'success': 3.

Reason of the startup image set failure for a card. It is empty if the operation was successful.

A clock changed notification is generated when the current local date and time for the system has been manually changed. The value of hpnicfSysLocalClock reflects new date and time.

A hpnicfSysReloadNotification will be sent before the corresponding entity is rebooted. It will also be sent if the entity fails to reboot because the clock has changed.

a hpnicfSysStartUpNotification trap will be sent when the system starts up with 'main' image file failed, a trap will be sent to indicate which type the current image file (I.e backup or secure)is.

The compliance statement for entities which implement the system management MIB.

A collection of objects providing mandatory system clock information.

A collection of objects providing mandatory system reload.

A collection of objects providing mandatory system image information.

A collection of objects providing mandatory system configuration file information.

A collection of system current status.

A collection of notifications.

A collection of objects providing system update bootrom information.