All MIBs › H3C-SYS-MAN-MIB
Organization: Huawei-3COM Technologies Co., Ltd.
Last Updated: 2009-06-07
Category: Device Management, Vendor: H3C/HH3C
Description: H3C MIB for system management including device reboot, clock configuration, and system-wide operational controls.
Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.
What Is H3C-SYS-MAN-MIB?
H3C-SYS-MAN-MIB is an H3C proprietary MIB for general system management, focused on displaying the device's current configuration file and boot image file information and controlling image reloading, with added support for XRN (H3C's earlier stacking technology, a precursor to IRF). Although no sample objects were supplied for this MIB, based on its description it centers on software/firmware state — which configuration file and system image are currently active — and on triggering a system reload with a specified image. This makes it directly relevant to monitoring and managing software version and boot status of a device, letting an administrator confirm what firmware is running and orchestrate controlled reboots/upgrades. It functions as a vendor-specific complement to standard system-identification objects (e.g. SNMPv2-MIB's sysDescr) by adding file-level configuration/image detail. It is deployed across the H3C switch and router product line for firmware/config-file management and remote reload operations. Engineers can download the H3C-SYS-MAN-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in H3C-SYS-MAN-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- H3C switches and routers (including XRN-stack-capable models)
Monitoring Examples
No sample objects were provided for this module, so specific table or scalar names cannot be confirmed without inspecting the source; conceptually, an administrator would query objects reporting the currently active configuration file name and boot image file name to verify the device is running the intended firmware version, then use a reload-triggering object to schedule a reboot with a specified image. This entry should be revisited once the actual object tree can be inspected for precise names.
What Can Be Monitored
- active configuration file
- active boot image file
- system reload/reboot control
This MIB depends on
Related MIBs
Imported Objects
From ENTITY-MIB
| PhysicalIndex |
From HUAWEI-3COM-OID-MIB
| h3cCommon | OBJECT-IDENTITY |
From SNMP-TARGET-MIB
| SnmpTagList | |
| SnmpTagValue |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| NOTIFICATION-GROUP | |
| OBJECT-GROUP |
From SNMPv2-SMI
| Integer32 | |
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-TYPE | |
| TimeTicks |
From SNMPv2-TC
| DateAndTime | |
| DisplayString | |
| RowPointer | |
| RowStatus |
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| h3cSystemMan | 1.3.6.1.4.1.2011.10.2.3 | 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. | ||
| h3cSystemManMIBObjects | 1.3.6.1.4.1.2011.10.2.3.1 | |||
| h3cSysClock | 1.3.6.1.4.1.2011.10.2.3.1.1 | |||
| DAT h3cSysLocalClock | 1.3.6.1.4.1.2011.10.2.3.1.1.1 | DateAndTime | read-write | This node gives the current local time of the system. The unit of it is DateAndTime. |
| h3cSysSummerTime | 1.3.6.1.4.1.2011.10.2.3.1.1.2 | |||
| INT h3cSysSummerTimeEnable | 1.3.6.1.4.1.2011.10.2.3.1.1.2.1 | INTEGER | read-only | 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. |
| STR h3cSysSummerTimeZone | 1.3.6.1.4.1.2011.10.2.3.1.1.2.2 | DisplayString | read-write | 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 h3cSysLocalClock has the time zone information means that summer time is running. |
| INT h3cSysSummerTimeMethod | 1.3.6.1.4.1.2011.10.2.3.1.1.2.3 | INTEGER | read-write | 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. |
| DAT h3cSysSummerTimeStart | 1.3.6.1.4.1.2011.10.2.3.1.1.2.4 | DateAndTime | read-write | This node provides the start time of summer time. |
| DAT h3cSysSummerTimeEnd | 1.3.6.1.4.1.2011.10.2.3.1.1.2.5 | DateAndTime | read-write | 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. |
| I32 h3cSysSummerTimeOffset | 1.3.6.1.4.1.2011.10.2.3.1.1.2.6 | Integer32 | read-write | 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. |
| h3cSysCurrent | 1.3.6.1.4.1.2011.10.2.3.1.2 | |||
| h3cSysCurTable | 1.3.6.1.4.1.2011.10.2.3.1.2.1 | not-accessible | The current status of system. A configuration file, an image file and bootrom information are used to describe the current status. | |
| h3cSysCurEntry | 1.3.6.1.4.1.2011.10.2.3.1.2.1.1 | not-accessible | An entry of h3cSysCurTable. | |
| I32 h3cSysCurEntPhysicalIndex | 1.3.6.1.4.1.2011.10.2.3.1.2.1.1.1 | Integer32 | not-accessible | 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. |
| I32 h3cSysCurCFGFileIndex | 1.3.6.1.4.1.2011.10.2.3.1.2.1.1.2 | Integer32 | read-only | 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 h3cSysCFGFileIndex in h3cSysCFGFileTable. |
| I32 h3cSysCurImageIndex | 1.3.6.1.4.1.2011.10.2.3.1.2.1.1.3 | Integer32 | read-only | The image file currently used by the specified entity. It will be the value of corresponding h3cSysImageIndex in h3cSysImageTable. |
| OCT h3cSysCurBtmFileName | 1.3.6.1.4.1.2011.10.2.3.1.2.1.1.4 | OCTET STRING | read-only | The bootrom file currently used by the specified entity. |
| OCT h3cSysCurUpdateBtmFileName | 1.3.6.1.4.1.2011.10.2.3.1.2.1.1.5 | OCTET STRING | read-only | The default value of this object is the same as the value of h3cSysCurBtmFileName. The value will be changed after updating the bootrom successfully. This bootrom will take effect on next startup. |
| h3cSysReload | 1.3.6.1.4.1.2011.10.2.3.1.3 | |||
| I32 h3cSysReloadSchedule | 1.3.6.1.4.1.2011.10.2.3.1.3.1 | Integer32 | read-write | The object points one row in h3cSysReloadScheduleTable. Its value is equal to the value of h3cSysReloadScheduleIndex. When a reload action is finished, the value of it would be zero which means no any reload schedule is selected. |
| INT h3cSysReloadAction | 1.3.6.1.4.1.2011.10.2.3.1.3.2 | INTEGER | read-write | Writing reloadOnSchedule(2) to this object performs the reload operation on schedule. If h3cSysReloadScheduleTime is not set, the value of h3cSysReloadAction can't be set to 'reloadOnSchedule(2)'. Writing reloadAtOnce(3)to this object performs the reload operation at once, regardless of the h3cSysReloadScheduleTime. When reloadCancel(4)is set, the scheduled reload action will be cancelled and the value of h3cSysReloadAction will be 'reloadUnavailable(1)',the value of h3cSysReloadSchedule will be 0, h3cSysReloadTag will be given a value of zero length, but the content of h3cSysReloadScheduleTable will remain. The h3cSysReloadSchedule and h3cSysReloadTag determine the reload entity(ies) in mutually exclusive way. And the h3cSysReloadSchedule will be handled at first. If the value of h3cSysReloadSchedule is invalid, then the h3cSysReloadTag will be handled. If the value of h3cSysReloadSchedule is valid, the value of h3cSysReloadTag is ignored and a reload action will be implemented to the entity specified by h3cSysReloadEntity in the entry pointed by h3cSysReloadSchedule. If h3cSysReloadSchedule is valid, but the entry h3cSysReloadSchedule pointing to is not active, the reload action will be ignored , and an inconsistent value will be returned. If multiple entities are required to be reloaded at the same time, the value of h3cSysReloadTag must be specified to select the reload parameters in the h3cSysReloadSceduelTable, and h3cSysReloadSchedule must have the value of '0'. If the whole fabric is to be reloaded in an XRN device, all the units in the fabric must have at least one entry in the h3cSysReloadSceduelTable with the same tag in h3cSysReloadSceduelTagList. When a reload action is done, or there is no reload action, the value should be reloadUnavailable(1). |
| h3cSysReloadScheduleTable | 1.3.6.1.4.1.2011.10.2.3.1.3.3 | not-accessible | 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. | |
| h3cSysReloadScheduleEntry | 1.3.6.1.4.1.2011.10.2.3.1.3.3.1 | not-accessible | Entry of h3cSysReloadScheduleTable. | |
| I32 h3cSysReloadScheduleIndex | 1.3.6.1.4.1.2011.10.2.3.1.3.3.1.1 | Integer32 | not-accessible | The index of h3cSysReloadScheduleTable. 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(RFC2737). 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. |
| I32 h3cSysReloadEntity | 1.3.6.1.4.1.2011.10.2.3.1.3.3.1.2 | Integer32 | read-create | The value of h3cSysReloadEntity 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 h3cSysReloadScheduleTable. |
| I32 h3cSysReloadCfgFile | 1.3.6.1.4.1.2011.10.2.3.1.3.3.1.3 | Integer32 | read-create | The value indicates an entry in h3cSysCFGFileTable. It defines a configuration file for reload action. It is the value of corresponding h3cSysCFGFileIndex in h3cSysCFGFileTable. The zero value means no configuration file has been set for this entry, and no configuration file is used during system reloading. |
| I32 h3cSysReloadImage | 1.3.6.1.4.1.2011.10.2.3.1.3.3.1.4 | Integer32 | read-create | The value indicates an entry in h3cSysImageTable. It defines an image file for reload action. It is the value of corresponding h3cSysImageIndex in h3cSysImageTable. If dual image is supported, the main image attribute can be set through this object or by h3cSysImageType of h3cSysImageTable of the entity. It is strongly suggested to set this attribute by the latter. If main image attribute is set here, the h3cSysImageType in h3cSysImageTable 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. |
| STR h3cSysReloadReason | 1.3.6.1.4.1.2011.10.2.3.1.3.3.1.5 | DisplayString | read-create | The reason of system's reloading. It is a zero length octet string when not set. |
| DAT h3cSysReloadScheduleTime | 1.3.6.1.4.1.2011.10.2.3.1.3.3.1.6 | DateAndTime | read-create | 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 h3cSysLocalClock 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). |
| ROW h3cSysReloadRowStatus | 1.3.6.1.4.1.2011.10.2.3.1.3.3.1.7 | RowStatus | read-create | If one of the value of h3cSysReloadEntity,h3cSysReloadImage is invalid, the value of h3cSysReloadRowStatus can not be set to the value of ACTIVE. A valid entry means the specified element is available in current system. |
| SNM h3cSysReloadScheduleTagList | 1.3.6.1.4.1.2011.10.2.3.1.3.3.1.8 | SnmpTagList | read-create | It specifies a tag list for the entry. |
| SNM h3cSysReloadTag | 1.3.6.1.4.1.2011.10.2.3.1.3.4 | SnmpTagValue | read-write | This object contains a single tag value which is used to select entries in the h3cSysReloadScheduleTable. In the h3cSysReloadScheduleTable,any entry that contains a tag value which is equal to the value of this object is selected. For example, the value of h3cSysReloadTag is 'TOM',and the h3cSysReloadScheduleTagList of each h3cSysReloadScheduleTable 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. |
| h3cSysImage | 1.3.6.1.4.1.2011.10.2.3.1.4 | |||
| I32 h3cSysImageNum | 1.3.6.1.4.1.2011.10.2.3.1.4.1 | Integer32 | read-only | The number of system images. It indicates the total entries of h3cSysImageTable. |
| h3cSysImageTable | 1.3.6.1.4.1.2011.10.2.3.1.4.2 | not-accessible | The system image management table. When 'copy srcfile destfile' is executed via the CLI, if destfile is not existed, then h3cSysImageType of the new file will be 'none'; otherwise h3cSysImageType keeps its current value. When 'move srcfile destfile' is executed via the CLI, h3cSysImageType and h3cSysImageIndex remain the same while h3cSysImageLocation changes. When 'rename srcfile' is executed via the CLI,h3cSysImageType and h3cSysImageIndex remain the same while h3cSysImageName changes. When 'delete srcfile' is executed via the CLI, the file is deleted from h3cSysImageTable while index of the file keeps and will not be allocated. | |
| h3cSysImageEntry | 1.3.6.1.4.1.2011.10.2.3.1.4.2.1 | not-accessible | An entity image entry. Each entry consists of information of an entity image. The h3cSysImageIndex exclusively defines an image file. | |
| I32 h3cSysImageIndex | 1.3.6.1.4.1.2011.10.2.3.1.4.2.1.1 | Integer32 | not-accessible | 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(RFC2737). 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 h3cSysImageIndex will be the maximum image index plus one. If the image file is removed, renamed, or moved from one place to another, its h3cSysImageIndex is not reallocated. If the image file's content is replaced, its h3cSysImageIndex will not change. |
| STR h3cSysImageName | 1.3.6.1.4.1.2011.10.2.3.1.4.2.1.2 | DisplayString | read-only | The file name of the image. It MUST NOT contain the path of the file. |
| I32 h3cSysImageSize | 1.3.6.1.4.1.2011.10.2.3.1.4.2.1.3 | Integer32 | read-only | Size of the file in bytes. |
| STR h3cSysImageLocation | 1.3.6.1.4.1.2011.10.2.3.1.4.2.1.4 | DisplayString | read-only | 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:/ |
| INT h3cSysImageType | 1.3.6.1.4.1.2011.10.2.3.1.4.2.1.5 | INTEGER | read-write | 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'. |
| h3cSysCFGFile | 1.3.6.1.4.1.2011.10.2.3.1.5 | |||
| I32 h3cSysCFGFileNum | 1.3.6.1.4.1.2011.10.2.3.1.5.1 | Integer32 | read-only | The number of the configuration files in the system. It indicates the total entries of h3cSysCFGFileTable. |
| h3cSysCFGFileTable | 1.3.6.1.4.1.2011.10.2.3.1.5.2 | not-accessible | 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. | |
| h3cSysCFGFileEntry | 1.3.6.1.4.1.2011.10.2.3.1.5.2.1 | not-accessible | A configuration file entry. Each entry consists of information of a configuration file. h3cSysCFGFileIndex exclusively decides a configuration file. | |
| I32 h3cSysCFGFileIndex | 1.3.6.1.4.1.2011.10.2.3.1.5.2.1.1 | Integer32 | not-accessible | 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(RFC2737). 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. |
| STR h3cSysCFGFileName | 1.3.6.1.4.1.2011.10.2.3.1.5.2.1.2 | DisplayString | read-only | 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. |
| I32 h3cSysCFGFileSize | 1.3.6.1.4.1.2011.10.2.3.1.5.2.1.3 | Integer32 | read-only | 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. |
| STR h3cSysCFGFileLocation | 1.3.6.1.4.1.2011.10.2.3.1.5.2.1.4 | DisplayString | read-only | 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:/ |
| h3cSysBtmFile | 1.3.6.1.4.1.2011.10.2.3.1.6 | |||
| h3cSysBtmFileLoad | 1.3.6.1.4.1.2011.10.2.3.1.6.1 | |||
| I32 h3cSysBtmLoadMaxNumber | 1.3.6.1.4.1.2011.10.2.3.1.6.1.1 | Integer32 | read-only | This object shows the maximum number of h3cSysBtmLoadEntry in each device/unit. |
| h3cSysBtmLoadTable | 1.3.6.1.4.1.2011.10.2.3.1.6.2 | not-accessible | This table is used to update the bootrom and show the results of the update operation. The bootrom files are listed at the h3cFlhFileTable. These files are used to update bootrom. | |
| h3cSysBtmLoadEntry | 1.3.6.1.4.1.2011.10.2.3.1.6.2.1 | not-accessible | Entries in the h3cSysBtmLoadTable are created and deleted using the h3cSysBtmRowStatus object. When a new row is being created and the number of entries is h3cSysBtmLoadMaxNumber, the row with minimal value of h3cSysBtmLoadTime and the value of h3cSysBtmFileType is none(2), should be destroyed automatically. | |
| I32 h3cSysBtmLoadIndex | 1.3.6.1.4.1.2011.10.2.3.1.6.2.1.1 | Integer32 | not-accessible | The index of h3cSysBtmLoadTable. 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(RFC2737). 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. |
| OCT h3cSysBtmFileName | 1.3.6.1.4.1.2011.10.2.3.1.6.2.1.2 | OCTET STRING | read-create | 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 h3cSysBtmErrorStatus should be failed(4). |
| INT h3cSysBtmFileType | 1.3.6.1.4.1.2011.10.2.3.1.6.2.1.3 | INTEGER | read-create | 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). |
| ROW h3cSysBtmRowStatus | 1.3.6.1.4.1.2011.10.2.3.1.6.2.1.4 | RowStatus | read-create | 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 h3cSysBtmFileName and h3cSysBtmFileType can not be modified by users. When bootrom is being updated, the value of h3cSysBtmErrorStatus is inProgress(2). When bootrom failed to be updated, the value of h3cSysBtmErrorStatus should be failed(4). When bootrom is updated successfully, the value of h3cSysBtmErrorStatus should be success(3). The value of h3cSysCurUpdateBtmFileName 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 h3cSysBtmFileType should be none(2) automatically. If a row is destroyed, h3cSysCurUpdateBtmFileName should not change. If a device/unit reboots, h3cSysBtmLoadTable should be empty. |
| INT h3cSysBtmErrorStatus | 1.3.6.1.4.1.2011.10.2.3.1.6.2.1.5 | INTEGER | read-only | 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. |
| TIK h3cSysBtmLoadTime | 1.3.6.1.4.1.2011.10.2.3.1.6.2.1.6 | TimeTicks | read-only | This object indicates operation time. |
| h3cSystemManMIBNotifications | 1.3.6.1.4.1.2011.10.2.3.2 | |||
| NTF h3cSysClockChangedNotification | 1.3.6.1.4.1.2011.10.2.3.2.1 | A clock changed notification is generated when the current local date and time for the system has been manually changed. The value of h3cSysLocalClock reflects new date and time. | ||
| NTF h3cSysReloadNotification | 1.3.6.1.4.1.2011.10.2.3.2.2 | A h3cSysReloadNotification 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. | ||
| NTF h3cSysStartUpNotification | 1.3.6.1.4.1.2011.10.2.3.2.3 | a h3cSysStartUpNotification 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. | ||
| h3cSystemManMIBConformance | 1.3.6.1.4.1.2011.10.2.3.3 | |||
| h3cSystemManMIBCompliances | 1.3.6.1.4.1.2011.10.2.3.3.1 | |||
| h3cSystemManMIBCompliance | 1.3.6.1.4.1.2011.10.2.3.3.1.1 | The compliance statement for entities which implement the Huawei 3Com system management MIB. | ||
| h3cSystemManMIBGroups | 1.3.6.1.4.1.2011.10.2.3.3.2 | |||
| h3cSysClockGroup | 1.3.6.1.4.1.2011.10.2.3.3.2.1 | A collection of objects providing mandatory system clock information. | ||
| h3cSysReloadGroup | 1.3.6.1.4.1.2011.10.2.3.3.2.2 | A collection of objects providing mandatory system reload. | ||
| h3cSysImageGroup | 1.3.6.1.4.1.2011.10.2.3.3.2.3 | A collection of objects providing mandatory system image information. | ||
| h3cSysCFGFileGroup | 1.3.6.1.4.1.2011.10.2.3.3.2.4 | A collection of objects providing mandatory system configuration file information. | ||
| h3cSysCurGroup | 1.3.6.1.4.1.2011.10.2.3.3.2.5 | A collection of system current status. | ||
| h3cSystemManNotificationGroup | 1.3.6.1.4.1.2011.10.2.3.3.2.6 | A collection of notifications. | ||
| h3cSystemBtmLoadGroup | 1.3.6.1.4.1.2011.10.2.3.3.2.7 | A collection of objects providing system update bootrom information. |
RFC description
Manages system configuration including image loading, reloading schedules, and file management on H3C/Huawei devices.
Start monitoring H3C switch/router (config/image file management, XRN stacking) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.