HH3C-SYS-MAN-MIB
AI MIB Summary
HH3C-SYS-MAN-MIB enables SNMP-based management of H3C network devices for monitoring active configuration and image files, defining reload targets, and managing XRN (Cross-Device Link Aggregation) system states.
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.
Main OID:
hh3cSystemMan.1.3.6.1.4.1.25506.2.3
147
Objects
Active
Status
5
Dependencies
Imported Objects
Objects
147 total| Object Name |
|---|
hh3cSystemManThis 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. MODULE-IDENTITY .1.3.6.1.4.1.25506.2.3 |
hh3cSystemManMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.25506.2.3.1 |
hh3cSysClock OBJECT IDENTIFIER .1.3.6.1.4.1.25506.2.3.1.1 |
hh3cSysLocalClockThis node gives the current local time of the system. The unit of it is DateAndTime.rw DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.25506.2.3.1.1.1 |
hh3cSysSummerTime OBJECT IDENTIFIER .1.3.6.1.4.1.25506.2.3.1.1.2 |
hh3cSysSummerTimeEnableThis 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.ro Enumeration .1.3.6.1.4.1.25506.2.3.1.1.2.1 |
hh3cSysSummerTimeZoneThis 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 hh3cSysLocalClock has the time zone information means that summer time is running.rw DisplayString .1.3.6.1.4.1.25506.2.3.1.1.2.2 |
hh3cSysSummerTimeMethodThis 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.rw Enumeration .1.3.6.1.4.1.25506.2.3.1.1.2.3 |
hh3cSysSummerTimeStartThis node provides the start time of summer time.rw DateAndTime .1.3.6.1.4.1.25506.2.3.1.1.2.4 |
hh3cSysSummerTimeEndThis 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.rw DateAndTime .1.3.6.1.4.1.25506.2.3.1.1.2.5 |
hh3cSysSummerTimeOffsetThis 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.rw Integer32 .1.3.6.1.4.1.25506.2.3.1.1.2.6 |
hh3cSysLocalClockStringThis 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.0Zrw OCTET STRING .1.3.6.1.4.1.25506.2.3.1.1.3 |
hh3cSysCurrent OBJECT IDENTIFIER .1.3.6.1.4.1.25506.2.3.1.2 |
hh3cSysCurTableThe current status of system. A configuration file, an image file and bootrom information are used to describe the current status. SEQUENCE OF Hh3cSysCurEntry .1.3.6.1.4.1.25506.2.3.1.2.1 |
hh3cSysCurEntryAn entry of hh3cSysCurTable. Hh3cSysCurEntry .1.3.6.1.4.1.25506.2.3.1.2.1.1 |
hh3cSysCurEntPhysicalIndexThe 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. Integer32 .1.3.6.1.4.1.25506.2.3.1.2.1.1.1 |
hh3cSysCurCFGFileIndexThe 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 hh3cSysCFGFileIndex in hh3cSysCFGFileTable.ro Integer32 .1.3.6.1.4.1.25506.2.3.1.2.1.1.2 |
hh3cSysCurImageIndexThe image file currently used by the specified entity. It will be the value of corresponding hh3cSysImageIndex in hh3cSysImageTable.ro Integer32 .1.3.6.1.4.1.25506.2.3.1.2.1.1.3 |
hh3cSysCurBtmFileNameThe bootrom file currently used by the specified entity.ro OCTET STRING .1.3.6.1.4.1.25506.2.3.1.2.1.1.4 |
hh3cSysCurUpdateBtmFileNameThe default value of this object is the same as the value of hh3cSysCurBtmFileName. The value will be changed after updating the bootrom successfully. This bootrom will take effect on next startup.ro OCTET STRING .1.3.6.1.4.1.25506.2.3.1.2.1.1.5 |
hh3cSysReload OBJECT IDENTIFIER .1.3.6.1.4.1.25506.2.3.1.3 |
hh3cSysReloadScheduleThe object points one row in hh3cSysReloadScheduleTable. Its value is equal to the value of hh3cSysReloadScheduleIndex. When a reload action is finished, the value of it would be zero which means no any reload schedule is selected.rw Integer32 .1.3.6.1.4.1.25506.2.3.1.3.1 |
hh3cSysReloadActionWriting reloadOnSchedule(2) to this object performs the reload operation on schedule. If hh3cSysReloadScheduleTime is not set, the value of hh3cSysReloadAction can't be set to 'reloadOnSchedule(2)'. Writing reloadAtOnce(3)to this object performs the reload operation at once, regardless of the hh3cSysReloadScheduleTime. When reloadCancel(4)is set, the scheduled reload action will be cancelled and the value of hh3cSysReloadAction will be 'reloadUnavailable(1)',the value of hh3cSysReloadSchedule will be 0, hh3cSysReloadTag will be given a value of zero length, but the content of hh3cSysReloadScheduleTable will remain. The hh3cSysReloadSchedule and hh3cSysReloadTag determine the reload entity(ies) in mutually exclusive way. And the hh3cSysReloadSchedule will be handled at first. If the value of hh3cSysReloadSchedule is invalid, then the hh3cSysReloadTag will be handled. If the value of hh3cSysReloadSchedule is valid, the value of hh3cSysReloadTag is ignored and a reload action will be implemented to the entity specified by hh3cSysReloadEntity in the entry pointed by hh3cSysReloadSchedule. If hh3cSysReloadSchedule is valid, but the entry hh3cSysReloadSchedule 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 hh3cSysReloadTag must be specified to select the reload parameters in the hh3cSysReloadSceduelTable, and hh3cSysReloadSchedule 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 hh3cSysReloadSceduelTable with the same tag in hh3cSysReloadSceduelTagList. When a reload action is done, or there is no reload action, the value should be reloadUnavailable(1).rw Enumeration .1.3.6.1.4.1.25506.2.3.1.3.2 |
hh3cSysReloadScheduleTableA 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. SEQUENCE OF Hh3cSysReloadScheduleEntry .1.3.6.1.4.1.25506.2.3.1.3.3 |
hh3cSysReloadScheduleEntryEntry of hh3cSysReloadScheduleTable. Hh3cSysReloadScheduleEntry .1.3.6.1.4.1.25506.2.3.1.3.3.1 |
hh3cSysReloadScheduleIndexThe index of hh3cSysReloadScheduleTable. 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. Integer32 .1.3.6.1.4.1.25506.2.3.1.3.3.1.1 |
hh3cSysReloadEntityThe value of hh3cSysReloadEntity 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 hh3cSysReloadScheduleTable.rw Integer32 .1.3.6.1.4.1.25506.2.3.1.3.3.1.2 |
hh3cSysReloadCfgFileThe value indicates an entry in hh3cSysCFGFileTable. It defines a configuration file for reload action. It is the value of corresponding hh3cSysCFGFileIndex in hh3cSysCFGFileTable. The zero value means no configuration file has been set for this entry, and no configuration file is used during system reloading.rw Integer32 .1.3.6.1.4.1.25506.2.3.1.3.3.1.3 |
hh3cSysReloadImageThe value indicates an entry in hh3cSysImageTable. It defines an image file for reload action. It is the value of corresponding hh3cSysImageIndex in hh3cSysImageTable. If dual image is supported, the main image attribute can be set through this object or by hh3cSysImageType of hh3cSysImageTable of the entity. It is strongly suggested to set this attribute by the latter. If main image attribute is set here, the hh3cSysImageType in hh3cSysImageTable 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.rw Integer32 .1.3.6.1.4.1.25506.2.3.1.3.3.1.4 |
hh3cSysReloadReasonThe reason of system's reloading. It is a zero length octet string when not set.rw DisplayString .1.3.6.1.4.1.25506.2.3.1.3.3.1.5 |
hh3cSysReloadScheduleTimeSpecify 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 hh3cSysLocalClock 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).rw DateAndTime .1.3.6.1.4.1.25506.2.3.1.3.3.1.6 |
hh3cSysReloadRowStatusIf one of the value of hh3cSysReloadEntity,hh3cSysReloadImage is invalid, the value of hh3cSysReloadRowStatus can not be set to the value of ACTIVE. A valid entry means the specified element is available in current system.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.25506.2.3.1.3.3.1.7 |
hh3cSysReloadScheduleTagListIt specifies a tag list for the entry.rw SnmpTagList (SNMP-TARGET-MIB) .1.3.6.1.4.1.25506.2.3.1.3.3.1.8 |
hh3cSysReloadTagThis object contains a single tag value which is used to select entries in the hh3cSysReloadScheduleTable. In the hh3cSysReloadScheduleTable,any entry that contains a tag value which is equal to the value of this object is selected. For example, the value of hh3cSysReloadTag is 'TOM',and the hh3cSysReloadScheduleTagList of each hh3cSysReloadScheduleTable 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.rw SnmpTagValue (SNMP-TARGET-MIB) .1.3.6.1.4.1.25506.2.3.1.3.4 |
hh3cSysImage OBJECT IDENTIFIER .1.3.6.1.4.1.25506.2.3.1.4 |
hh3cSysImageNumThe number of system images. It indicates the total entries of hh3cSysImageTable.ro Integer32 .1.3.6.1.4.1.25506.2.3.1.4.1 |
hh3cSysImageTableThe system image management table. When 'copy srcfile destfile' is executed via the CLI, if destfile is not existed, then hh3cSysImageType of the new file will be 'none'; otherwise hh3cSysImageType keeps its current value. When 'move srcfile destfile' is executed via the CLI, hh3cSysImageType and hh3cSysImageIndex remain the same while hh3cSysImageLocation changes. When 'rename srcfile' is executed via the CLI,hh3cSysImageType and hh3cSysImageIndex remain the same while hh3cSysImageName changes. When 'delete srcfile' is executed via the CLI, the file is deleted from hh3cSysImageTable while index of the file keeps and will not be allocated. SEQUENCE OF Hh3cSysImageEntry .1.3.6.1.4.1.25506.2.3.1.4.2 |
hh3cSysImageEntryAn entity image entry. Each entry consists of information of an entity image. The hh3cSysImageIndex exclusively defines an image file. Hh3cSysImageEntry .1.3.6.1.4.1.25506.2.3.1.4.2.1 |
hh3cSysImageIndexThere 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 hh3cSysImageIndex will be the maximum image index plus one. If the image file is removed, renamed, or moved from one place to another, its hh3cSysImageIndex is not reallocated. If the image file's content is replaced, its hh3cSysImageIndex will not change. Integer32 .1.3.6.1.4.1.25506.2.3.1.4.2.1.1 |
hh3cSysImageNameThe file name of the image. It MUST NOT contain the path of the file.ro DisplayString .1.3.6.1.4.1.25506.2.3.1.4.2.1.2 |
hh3cSysImageSizeSize of the file in bytes.ro Integer32 .1.3.6.1.4.1.25506.2.3.1.4.2.1.3 |
hh3cSysImageLocationThe 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:/ro DisplayString .1.3.6.1.4.1.25506.2.3.1.4.2.1.4 |
hh3cSysImageTypeIt 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'.rw Enumeration .1.3.6.1.4.1.25506.2.3.1.4.2.1.5 |
hh3cSysCFGFile OBJECT IDENTIFIER .1.3.6.1.4.1.25506.2.3.1.5 |
hh3cSysCFGFileNumThe number of the configuration files in the system. It indicates the total entries of hh3cSysCFGFileTable.ro Integer32 .1.3.6.1.4.1.25506.2.3.1.5.1 |
hh3cSysCFGFileTableA 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. SEQUENCE OF Hh3cSysCFGFileEntry .1.3.6.1.4.1.25506.2.3.1.5.2 |
hh3cSysCFGFileEntryA configuration file entry. Each entry consists of information of a configuration file. hh3cSysCFGFileIndex exclusively decides a configuration file. Hh3cSysCFGFileEntry .1.3.6.1.4.1.25506.2.3.1.5.2.1 |
hh3cSysCFGFileIndexThere 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. Integer32 .1.3.6.1.4.1.25506.2.3.1.5.2.1.1 |
hh3cSysCFGFileNameConfiguration 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.ro DisplayString .1.3.6.1.4.1.25506.2.3.1.5.2.1.2 |
hh3cSysCFGFileSizeSize 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.ro Integer32 .1.3.6.1.4.1.25506.2.3.1.5.2.1.3 |
hh3cSysCFGFileLocationThe 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:/ro DisplayString .1.3.6.1.4.1.25506.2.3.1.5.2.1.4 |
hh3cSysBtmFile OBJECT IDENTIFIER .1.3.6.1.4.1.25506.2.3.1.6 |
hh3cSysBtmFileLoad OBJECT IDENTIFIER .1.3.6.1.4.1.25506.2.3.1.6.1 |
hh3cSysBtmLoadMaxNumberThis object shows the maximum number of hh3cSysBtmLoadEntry in each device/unit.ro Integer32 .1.3.6.1.4.1.25506.2.3.1.6.1.1 |
hh3cSysBtmLoadTableThis table is used to update the bootrom and show the results of the update operation. The bootrom files are listed at the hh3cFlhFileTable. These files are used to update bootrom. SEQUENCE OF Hh3cSysBtmLoadEntry .1.3.6.1.4.1.25506.2.3.1.6.2 |
hh3cSysBtmLoadEntryEntries in the hh3cSysBtmLoadTable are created and deleted using the hh3cSysBtmRowStatus object. When a new row is being created and the number of entries is hh3cSysBtmLoadMaxNumber, the row with minimal value of hh3cSysBtmLoadTime and the value of hh3cSysBtmFileType is none(2), should be destroyed automatically. Hh3cSysBtmLoadEntry .1.3.6.1.4.1.25506.2.3.1.6.2.1 |
hh3cSysBtmLoadIndexThe index of hh3cSysBtmLoadTable. 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. Integer32 .1.3.6.1.4.1.25506.2.3.1.6.2.1.1 |
hh3cSysBtmFileNameThe 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 hh3cSysBtmErrorStatus should be failed(4).rw OCTET STRING .1.3.6.1.4.1.25506.2.3.1.6.2.1.2 |
hh3cSysBtmFileTypemain(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).rw Enumeration .1.3.6.1.4.1.25506.2.3.1.6.2.1.3 |
hh3cSysBtmRowStatusOnly 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 hh3cSysBtmFileName and hh3cSysBtmFileType can not be modified by users. When bootrom is being updated, the value of hh3cSysBtmErrorStatus is inProgress(2). When bootrom failed to be updated, the value of hh3cSysBtmErrorStatus should be failed(4). When bootrom is updated successfully, the value of hh3cSysBtmErrorStatus should be success(3). The value of hh3cSysCurUpdateBtmFileName 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 hh3cSysBtmFileType should be none(2) automatically. If a row is destroyed, hh3cSysCurUpdateBtmFileName should not change. If a device/unit reboots, hh3cSysBtmLoadTable should be empty.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.25506.2.3.1.6.2.1.4 |
hh3cSysBtmErrorStatusThis 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.ro Enumeration .1.3.6.1.4.1.25506.2.3.1.6.2.1.5 |
hh3cSysBtmLoadTimeThis object indicates operation time.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.25506.2.3.1.6.2.1.6 |
hh3cSysPackage OBJECT IDENTIFIER .1.3.6.1.4.1.25506.2.3.1.7 |
hh3cSysPackageNumThe number of software packages. It indicates the total entries of hh3cSysPackageTable.ro Integer32 .1.3.6.1.4.1.25506.2.3.1.7.1 |
hh3cSysPackageTableThe system package management table. SEQUENCE OF Hh3cSysPackageEntry .1.3.6.1.4.1.25506.2.3.1.7.2 |
hh3cSysPackageEntryAn software package entry. Each entry consists of information of an software package. Hh3cSysPackageEntry .1.3.6.1.4.1.25506.2.3.1.7.2.1 |
hh3cSysPackageIndexThere 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 hh3cSysPackageIndex will be the maximum image index plus one. If the package file is removed, renamed, or moved from one place to another, its hh3cSysPackageIndex is not reallocated. If the package file's content is replaced, its hh3cSysPackageIndex will not change. Integer32 .1.3.6.1.4.1.25506.2.3.1.7.2.1.1 |
hh3cSysPackageNameThe file name of the package. It MUST NOT contain the path of the file.ro DisplayString .1.3.6.1.4.1.25506.2.3.1.7.2.1.2 |
hh3cSysPackageSizeSize of the file in bytes.ro Unsigned32 .1.3.6.1.4.1.25506.2.3.1.7.2.1.3 |
hh3cSysPackageLocationThe 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:/ro DisplayString .1.3.6.1.4.1.25506.2.3.1.7.2.1.4 |
hh3cSysPackageTypeIt 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.ro Enumeration .1.3.6.1.4.1.25506.2.3.1.7.2.1.5 |
hh3cSysPackageAttributeIt 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.rw Enumeration .1.3.6.1.4.1.25506.2.3.1.7.2.1.6 |
hh3cSysPackageStatusIt indicates the status of the package file. If this file is used in the current system, its status is 'active'.ro Enumeration .1.3.6.1.4.1.25506.2.3.1.7.2.1.7 |
hh3cSysPackageDescriptionIt is the description of the package.ro DisplayString .1.3.6.1.4.1.25506.2.3.1.7.2.1.8 |
hh3cSysPackageFeatureIndicate the feature of the package. Different package files could be the same feature.ro DisplayString .1.3.6.1.4.1.25506.2.3.1.7.2.1.9 |
hh3cSysPackageVersionIndicate the version of the package.ro DisplayString .1.3.6.1.4.1.25506.2.3.1.7.2.1.10 |
hh3cSysPackageLoadAttributeFile 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.rw Enumeration .1.3.6.1.4.1.25506.2.3.1.7.2.1.11 |
hh3cSysPackageModelIndicates whether the image file is for an extended device or the parent device. Examples of extended devices include PEXs and firewall modules.ro DisplayString .1.3.6.1.4.1.25506.2.3.1.7.2.1.12 |
hh3cSysPackageOperateEntryLimitThe maximum number of the entries in hh3cSysPackageOperateTable.rw Integer32 .1.3.6.1.4.1.25506.2.3.1.7.3 |
hh3cSysPackageOperateTableA table of package file operate. SEQUENCE OF Hh3cSysPackageOperateEntry .1.3.6.1.4.1.25506.2.3.1.7.4 |
hh3cSysPackageOperateEntryAn operate request entry. Hh3cSysPackageOperateEntry .1.3.6.1.4.1.25506.2.3.1.7.4.1 |
hh3cSysPackageOperateIndexThe unique index value of a row in this table. Integer32 .1.3.6.1.4.1.25506.2.3.1.7.4.1.1 |
hh3cSysPackageOperatePackIndexSpecify the package file in the hh3cSysPackageTable.rw Integer32 .1.3.6.1.4.1.25506.2.3.1.7.4.1.2 |
hh3cSysPackageOperateStatusactivate or deactivate a package in the hh3cSysPackageTable.rw Enumeration .1.3.6.1.4.1.25506.2.3.1.7.4.1.3 |
hh3cSysPackageOperateRowStatusthe status of this table entry. When the status is active all the object's value in the entry is not allowed to modified.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.25506.2.3.1.7.4.1.4 |
hh3cSysPackageOperateResultthe result of the operation.ro Enumeration .1.3.6.1.4.1.25506.2.3.1.7.4.1.5 |
hh3cSysIpeFile OBJECT IDENTIFIER .1.3.6.1.4.1.25506.2.3.1.8 |
hh3cSysIpeFileNumThe number of software IPE(Image Package Envelop) files. It indicates the total entries of hh3cSysIpeFileTable.ro Integer32 .1.3.6.1.4.1.25506.2.3.1.8.1 |
hh3cSysIpeFileTableThe system IPE file manage table. SEQUENCE OF Hh3cSysIpeFileEntry .1.3.6.1.4.1.25506.2.3.1.8.2 |
hh3cSysIpeFileEntryAn IPE package file entry. Each entry consists of information of an IPE package file. hh3cSysIpeFileIndex exclusively decides an IPE file. Hh3cSysIpeFileEntry .1.3.6.1.4.1.25506.2.3.1.8.2.1 |
hh3cSysIpeFileIndexThere 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 hh3cSysIpeFileIndex will be the maximum image ndex plus one. If the IPE file is removed, renamed, or moved from one place to another, its hh3cSysIpeFileIndex is not reallocated. If the IPE file's content is replaced, its hh3cSysIpeFileIndex will not change. Integer32 .1.3.6.1.4.1.25506.2.3.1.8.2.1.1 |
hh3cSysIpeFileNameThe file name of the IPE file. It MUST NOT contain the path of the file.ro DisplayString .1.3.6.1.4.1.25506.2.3.1.8.2.1.2 |
hh3cSysIpeFileSizeSize of the file in bytes.ro Unsigned32 .1.3.6.1.4.1.25506.2.3.1.8.2.1.3 |
hh3cSysIpeFileLocationThe 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:/ro DisplayString .1.3.6.1.4.1.25506.2.3.1.8.2.1.4 |
hh3cSysIpeFileModelDevice 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.ro SnmpTagList (SNMP-TARGET-MIB) .1.3.6.1.4.1.25506.2.3.1.8.2.1.5 |
hh3cSysIpePackageTableThe IPE package file table. It shows the package files in the IPE file. SEQUENCE OF Hh3cSysIpePackageEntry .1.3.6.1.4.1.25506.2.3.1.8.3 |
hh3cSysIpePackageEntryAn entry of the hh3cIpePackageTable. Indexed by hh3cSysIpeFileIndex and hh3cSysIpePackageIndex. Hh3cSysIpePackageEntry .1.3.6.1.4.1.25506.2.3.1.8.3.1 |
hh3cSysIpePackageIndexIt 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. Integer32 .1.3.6.1.4.1.25506.2.3.1.8.3.1.1 |
hh3cSysIpePackageNameThe file name of the package file.ro DisplayString .1.3.6.1.4.1.25506.2.3.1.8.3.1.2 |
hh3cSysIpePackageSizeSize of the package file in bytes.ro Unsigned32 .1.3.6.1.4.1.25506.2.3.1.8.3.1.3 |
hh3cSysIpePackageTypeIt 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.ro Enumeration .1.3.6.1.4.1.25506.2.3.1.8.3.1.4 |
hh3cSysIpePackageDescriptionIt is the description of the package.ro DisplayString .1.3.6.1.4.1.25506.2.3.1.8.3.1.5 |
hh3cSysIpePackageFeatureIndicate the feature of the package.ro DisplayString .1.3.6.1.4.1.25506.2.3.1.8.3.1.6 |
hh3cSysIpePackageVersionThe version of the package.ro DisplayString .1.3.6.1.4.1.25506.2.3.1.8.3.1.7 |
hh3cSysIpePackageModelIndicates whether the image package file is for an extended device, the parent device, or both. Examples of extended devices include PEXs and firewall modules.ro DisplayString .1.3.6.1.4.1.25506.2.3.1.8.3.1.8 |
hh3cSysIpeFileOperateTableA table of IPE file operate. SEQUENCE OF Hh3cSysIpeFileOperateEntry .1.3.6.1.4.1.25506.2.3.1.8.4 |
hh3cSysIpeFileOperateEntryAn operate request entry. Hh3cSysIpeFileOperateEntry .1.3.6.1.4.1.25506.2.3.1.8.4.1 |
hh3cSysIpeFileOperateIndexThe unique index value of a row in this table. Integer32 .1.3.6.1.4.1.25506.2.3.1.8.4.1.1 |
hh3cSysIpeFileOperateFileIndexSpecify the IPE file in the hh3cSysIpeFileTable. This IPE file will be unpacked to package files.rw Integer32 .1.3.6.1.4.1.25506.2.3.1.8.4.1.2 |
hh3cSysIpeFileOperateAttributeIt 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.rw Enumeration .1.3.6.1.4.1.25506.2.3.1.8.4.1.3 |
hh3cSysIpeFileOperateRowStatusthe status of this table entry. When the status is active all the object's value in the entry is not allowed to modified.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.25506.2.3.1.8.4.1.4 |
hh3cSysIpeFileOperateResultthe result of the operation.ro Enumeration .1.3.6.1.4.1.25506.2.3.1.8.4.1.5 |
hh3cSysSetBootImage OBJECT IDENTIFIER .1.3.6.1.4.1.25506.2.3.1.9 |
hh3cSysSetBootImageOp OBJECT IDENTIFIER .1.3.6.1.4.1.25506.2.3.1.9.1 |
hh3cSysSetBootImageActionSets 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 -------------------------+-----------------------+---------------------------------------------------rw Enumeration .1.3.6.1.4.1.25506.2.3.1.9.1.1 |
hh3cSysSetBootImageFileOverWriteDetermines whether to overwrite the existing image file with the same name as the downloaded image file.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.25506.2.3.1.9.1.2 |
hh3cSysSetBootImageRemoveIpeFileDetermines 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.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.25506.2.3.1.9.1.3 |
hh3cSysSetBootImageStatusStatus of the startup image set operation.ro Enumeration .1.3.6.1.4.1.25506.2.3.1.9.1.4 |
hh3cSysSetBootImageFailedReasonStartup image operation failure reason. The field is empty if the operation was successful.ro DisplayString .1.3.6.1.4.1.25506.2.3.1.9.1.5 |
hh3cSysBootPackageTableTable of images to be set as startup images. It should be used when hh3cSysBootIpeTable is empty. SEQUENCE OF Hh3cSysBootPackageEntry .1.3.6.1.4.1.25506.2.3.1.9.2 |
hh3cSysBootPackageEntryEntry of the image table. Hh3cSysBootPackageEntry .1.3.6.1.4.1.25506.2.3.1.9.2.1 |
hh3cSysBootPackageIndexIndex of the software images. The index must be included in hh3cSysPackageTable. Integer32 .1.3.6.1.4.1.25506.2.3.1.9.2.1.1 |
hh3cSysBootPackageRowStatusRow status of the image entry.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.25506.2.3.1.9.2.1.2 |
hh3cSysBootIpeTableTable of the IPE files to be set for startup. It should be used when hh3cSysBootPackageTable is empty. SEQUENCE OF Hh3cSysBootIpeEntry .1.3.6.1.4.1.25506.2.3.1.9.3 |
hh3cSysBootIpeEntryEntry in the IPE file table. Hh3cSysBootIpeEntry .1.3.6.1.4.1.25506.2.3.1.9.3.1 |
hh3cSysBootIpeIndexIPE file index. The index must be included in hh3cSysIpeFileTable. Integer32 .1.3.6.1.4.1.25506.2.3.1.9.3.1.1 |
hh3cSysBootIpeRowStatusRow status of the IPE file table entry.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.25506.2.3.1.9.3.1.2 |
hh3cSysSetBootImageResultTableTable of startup image operation results. This table shows the result for each card. SEQUENCE OF Hh3cSysSetBootImageResultEntry .1.3.6.1.4.1.25506.2.3.1.9.4 |
hh3cSysSetBootImageResultEntryEntry in the startup image operation result table. Hh3cSysSetBootImageResultEntry .1.3.6.1.4.1.25506.2.3.1.9.4.1 |
hh3cSysSetBootImageResultIndexIndex of a startup image operation result. It is identical to the entity index of each card. Integer32 .1.3.6.1.4.1.25506.2.3.1.9.4.1.1 |
hh3cSysSetBootImageResultStatusOfEachCardStatus of the startup image set operation.ro Enumeration .1.3.6.1.4.1.25506.2.3.1.9.4.1.2 |
hh3cSysSetBootImageFailedReasonOfEachCardReason of the startup image set failure for a card. It is empty if the operation was successful.ro DisplayString .1.3.6.1.4.1.25506.2.3.1.9.4.1.3 |
hh3cSystemManMIBNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.25506.2.3.2 |
hh3cSysClockChangedNotificationA clock changed notification is generated when the current local date and time for the system has been manually changed. The value of hh3cSysLocalClock reflects new date and time. NOTIFICATION-TYPE .1.3.6.1.4.1.25506.2.3.2.1 |
hh3cSysReloadNotificationA hh3cSysReloadNotification 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. NOTIFICATION-TYPE .1.3.6.1.4.1.25506.2.3.2.2 |
hh3cSysStartUpNotificationa hh3cSysStartUpNotification 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. NOTIFICATION-TYPE .1.3.6.1.4.1.25506.2.3.2.3 |
hh3cSystemManMIBConformance OBJECT IDENTIFIER .1.3.6.1.4.1.25506.2.3.3 |
hh3cSystemManMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.25506.2.3.3.1 |
hh3cSystemManMIBComplianceThe compliance statement for entities which implement the system management MIB. Unknown .1.3.6.1.4.1.25506.2.3.3.1.1 |
hh3cSystemManMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.25506.2.3.3.2 |
hh3cSysClockGroupA collection of objects providing mandatory system clock information. Unknown .1.3.6.1.4.1.25506.2.3.3.2.1 |
hh3cSysReloadGroupA collection of objects providing mandatory system reload. Unknown .1.3.6.1.4.1.25506.2.3.3.2.2 |
hh3cSysImageGroupA collection of objects providing mandatory system image information. Unknown .1.3.6.1.4.1.25506.2.3.3.2.3 |
hh3cSysCFGFileGroupA collection of objects providing mandatory system configuration file information. Unknown .1.3.6.1.4.1.25506.2.3.3.2.4 |
hh3cSysCurGroupA collection of system current status. Unknown .1.3.6.1.4.1.25506.2.3.3.2.5 |
hh3cSystemManNotificationGroupA collection of notifications. Unknown .1.3.6.1.4.1.25506.2.3.3.2.6 |
hh3cSystemBtmLoadGroupA collection of objects providing system update bootrom information. Unknown .1.3.6.1.4.1.25506.2.3.3.2.7 |