HUAWEI-BULKSTATISTICS-MIB

File: HUAWEI-BULKSTATISTICS-MIB.mib (137440 bytes)

Imported modules

HUAWEI-MIB SNMPv2-SMI SNMPv2-TC
HUAWEI-LOAD-BACKUP-MIB

Imported symbols

huaweiUtility hwCfgInfoCollect IpAddress
Integer32 Unsigned32 Counter64
OBJECT-TYPE MODULE-IDENTITY OBJECT-IDENTITY
NOTIFICATION-TYPE RowStatus TruthValue
DisplayString hwLoadBackupResult

Defined Types

HwBulkFileEntry  
SEQUENCE    
  hwBulkFileIndex Integer32
  hwBulkFileName OCTET STRING
  hwBulkFileStorage INTEGER
  hwBulkFileFormat INTEGER
  hwBulkFileCollectInterval INTEGER
  hwBulkFileNmsGetInterval INTEGER
  hwBulkFileStatus INTEGER
  hwBulkFileCurrDirectoryPath OCTET STRING
  hwBulkFileObjectMainType Integer32
  hwBulkFileObjectSubType Integer32
  hwBulkFileRowStatus RowStatus
  hwBulkFileColNumMode INTEGER
  hwBulkFileCollectStartTime OCTET STRING
  hwBulkFileCopyNum Integer32
  hwBulkObjectCapItemList BITS

HwBulkSaveFileEntry  
SEQUENCE    
  hwBulkSaveFileIndex Integer32
  hwBulkSaveFileTime OCTET STRING

HwBulkOIDEntry  
SEQUENCE    
  hwBulkOID OBJECT IDENTIFIER
  hwBulkOIDRowStatus RowStatus

HWBulkObjectEntry  
SEQUENCE    
  hwBulkObjectIndex Integer32
  hwBulkObjectOIDIndex OCTET STRING
  hwBulkObjectLength Integer32
  hwBulkObjectRowStatus RowStatus

HwBulkObjectCapItemEntry  
SEQUENCE    
  hwBulkObjectCapItem Integer32
  hwBulkObjectCapItemRowStatus RowStatus

HwFTPClientEntry  
SEQUENCE    
  hwFTPClientIndex Integer32
  hwFTPClientMode INTEGER
  hwFTPClientOper INTEGER
  hwFTPClientFileName OCTET STRING
  hwFTPDestFileName OCTET STRING
  hwFTPClientServerIP IpAddress
  hwFTPClientUserName OCTET STRING
  hwFTPClientPasswd OCTET STRING
  hwFTPClientIfIndex Integer32
  hwFTPClientState INTEGER
  hwFTPClientRowStatus RowStatus
  hwFTPClientServerPort Integer32

HwDefineTCAEntry  
SEQUENCE    
  hwDefineFacilityType INTEGER
  hwDefineMontype INTEGER
  hwDefineAid OCTET STRING
  hwDefineTmper INTEGER
  hwDefineThlev OCTET STRING
  hwDefineRowStatus RowStatus

HwBQueryCapabilityEntry  
SEQUENCE    
  hwBatchQueryType Integer32
  hwBatchQueryCapability OCTET STRING

HwBatchQuerySetEntry  
SEQUENCE    
  hwBatchQuerySn Integer32
  hwBatchQueryCurrentType Integer32
  hwBatchQueryParameter OCTET STRING
  hwBatchQueryRowStatus RowStatus

HwBatchQueryGetEntry  
SEQUENCE    
  hwBatchQueryStartNo Integer32
  hwBatchQueryReturnNum Integer32
  hwBatchQueryReturnList OCTET STRING
  hwBatchQueryIsLast INTEGER

HwCollectSetEntry  
SEQUENCE    
  hwCollectTableName OCTET STRING
  hwCollectOID OCTET STRING
  hwCollectTableRowStatus RowStatus

HwBackupCollectInfoParaEntry  
SEQUENCE    
  hwBackupCollectInfoServerIpAddr IpAddress
  hwBackupCollectInfoMode INTEGER
  hwBackupCollectInfoFileName OCTET STRING
  hwBackupCollectInfoUserName OCTET STRING
  hwBackupCollectInfoPassword OCTET STRING
  hwBackupCollectInfoRequestID Integer32

HwCfgInfoQueryEntry  
SEQUENCE    
  hwQueryCondition OCTET STRING
  hwQueryContent OCTET STRING
  hwQueryResult OCTET STRING

Defined Values

hwBulkStatistics 1.3.6.1.4.1.2011.6.103
Huawei bulk performance statistics MIB object includes bulk performance statistics file configuration, FTP client management, and threshold alarm configuration and management. The NMS creates a performance statistics file, statistical object, and statistical content through the MIB interface, and starts the performance statistics. The host collects the content of the statistical object, creates a file of the statistical content at a fixed interval for collecting statistics, and then reports a trap to the NMS for it to obtain data. The NMS can also back up the statistics file to the NMS server through the MIB interface. A threshold needs to be set for monitoring the performance data. When the data exceeds the threshold, an alarm indicating that the data exceeds the threshold is generated and reported to the NMS automatically. The information item that needs to be collected can be configured through the NMS. The collection task can be started or stopped through the NMS. The item that needs to be collected can be backed up through the NMS.
MODULE-IDENTITY    

hwBulkFile 1.3.6.1.4.1.2011.6.103.1
OBJECT IDENTIFIER    

hwBulkFileMgmt 1.3.6.1.4.1.2011.6.103.1.1
OBJECT IDENTIFIER    

hwBulkFileCopyMax 1.3.6.1.4.1.2011.6.103.1.1.1
Maximum number of the bulk files that are allowed to back up. When the bulk file is created successfully, the NMS will get the bulk file from the devices periodically. It is required that the host device back up the bulk file in periods. Because the system resources are limited, this object defines the maximum of backup files. When it hits, the earliest backup file will be overwritten by new ones. If the hwBulkFileTable is not empty, modification to this object value is not allowed.
Status: obsolete Access: read-write
OBJECT-TYPE    
  Integer32  

hwBulkFileTableNextIndex 1.3.6.1.4.1.2011.6.103.1.1.2
Next available index for table hwBulkFileTable. If no available index, the value will be filled with '-1'.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

hwBulkFileCount 1.3.6.1.4.1.2011.6.103.1.1.3
The total number of the bulk file currently.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

hwBulkFileTable 1.3.6.1.4.1.2011.6.103.1.1.4
Bulk file management table, providing creat/modify/delete operations. To create a bulk file, you need create a related record in this table, and add object ndoes in hwBulkObjectTable.If you delete a record, the object records in hwBulkObjectTable and all backup files will be also deleted. The index of this table is hwBulkFileIndex.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    HwBulkFileEntry

hwBulkFileEntry 1.3.6.1.4.1.2011.6.103.1.1.4.1
Bulk file management table, providing creat/modify/delete operations. To create a bulk file, you need create a related record in this table, and add object ndoes in hwBulkObjectTable.If you delete a record, the object records in hwBulkObjectTable and all backup files will be also deleted. The index of this entry is hwBulkFileIndex.
Status: current Access: not-accessible
OBJECT-TYPE    
  HwBulkFileEntry  

hwBulkFileIndex 1.3.6.1.4.1.2011.6.103.1.1.4.1.1
Index of bulk file,a unique identifier for a bulk file.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

hwBulkFileName 1.3.6.1.4.1.2011.6.103.1.1.4.1.2
Bulk file name. If you specify a path in the file name, this file is invalid.
Status: current Access: read-create
OBJECT-TYPE    
  OCTET STRING Size(1..63)  

hwBulkFileStorage 1.3.6.1.4.1.2011.6.103.1.1.4.1.3
Storage mode of the statistics file. Options: 1.ephemeral(1) -data file of small volume. It applies to be read once. 2.volatile(2) -stored in memory. Easy to lose. 3.permanent(3) -stored in hard disk. Keep well.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER ephemeral(1), volatile(2), permanent(3)  

hwBulkFileFormat 1.3.6.1.4.1.2011.6.103.1.1.4.1.4
Bulk file formats. Options: 1.standardBER(1)-standard SNMP ASN.1 BER. 2.bulkASCIIWithDeflate(2) -readable ASCII with deflate format. 3.bulkASCIIWithZipFile(3) -readable ASCII with zip format.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER standardBER(1), bulkASCIIWithDeflate(2), bulkASCIIWithZipFile(3)  

hwBulkFileCollectInterval 1.3.6.1.4.1.2011.6.103.1.1.4.1.5
Data collection interval. Options: 1.fifteenMinutes(1) -Every 15 minutes. 2.thirtyMinutes(2) -Every 30 minutes. 3.oneHour(3) -Every 1 hour. 4.sixHour(4) -Every 6 hours. 5.oneDay(5) -Every 1 day. 6.twoHour(6) -Every 2 hours. 7.twelveHour(7) -Every 12 hours.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER fifteenMinutes(1), thirtyMinutes(2), oneHour(3), sixHour(4), oneDay(5), twoHour(6), twelveHour(7)  

hwBulkFileNmsGetInterval 1.3.6.1.4.1.2011.6.103.1.1.4.1.6
File report interval. The interval thirtyMinutes is not supported. The file report interval cannot be shorter than the data collection interval. Options: 1.hour(1) -The host generates a statistics file every hour. 2.thirtyMinutes(2) -The host generates a statistics file every 30 minutes. 3.fifteenMinutes(3) -The host generates a statistics file every 15 minutes. 4.sixHour(4) -The host generates a statistics file every six hour. 5.oneDay(5) -The host generates a statistics file every day. Data collection interval and file storage interval can be only one of the following combinations: Data collection interval file storage interval 15 minutes 15 minutes or 1 hour 6 hour 6 hours 1 day 1 day This object takes effect when the centralized bulk feature is enabled, and does not take effect when the distributed bulk feature is enabled.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER hour(1), thirtyMinutes(2), fifteenMinutes(3), sixHour(4), oneDay(5)  

hwBulkFileStatus 1.3.6.1.4.1.2011.6.103.1.1.4.1.7
Bulk file status. Options: 1.ready(1) -indicates that the statistics file is only created, leaving the actual statistics collection to be started. This value cannot be set. 2.create(2) -indicates the starting of the file. If succeeds, the status changes to running. If fails, an error code is returned. 3.running(3) -indicates that the statistics file is already started successfully and in the running state currently. This value cannot be set. 4.nospace(4) -indicates that creating or writing the file failed. The cause is no free space in hard disk. This value cannot be set. 5.noMem(5) -indicates that creating or writing the file failed. The cause is no free memory. This value cannot be set. 6.writeErr(6)-indicates an Unknown error. The file cannot be written. 7.stopped(7) -indicates that the task is suspended. If this value is set when in the running status, then writing file is stopped. Meanwhile, the system generates a file based on the collected data.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER ready(1), create(2), running(3), nospace(4), noMem(5), writeErr(6), stopped(7)  

hwBulkFileCurrDirectoryPath 1.3.6.1.4.1.2011.6.103.1.1.4.1.8
The latest index of the statistics file.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..31)  

hwBulkFileObjectMainType 1.3.6.1.4.1.2011.6.103.1.1.4.1.9
Identify main-type of object. The device will collect statistics of all the ports according to to hwBulkFileObjectMainType and hwBulkFileObjectSubType if these two objects are not null. The values of hwBulkFileObjectMainType and hwBulkFileObjectSubType need to match as follows: -------------------------------------- ulMainType ulSubType Note --------------------------------------- 1 101 Device 3 113 V5 Interface user frame 4 100 Borad 4 101 Memory 6 105 ADSL port(only support ADSL2+) 6 108 E1 port 6 109 Ethernet port 6 111 interboard-port 6 112 backboard port 6 113 V5 user 6 119 ATM port 6 126 SHDSL port 6 141 DS3 port 6 173 Ethernet port 6 175 VDSL2 port 6 1080 E1 port 6 108000 E1 port 7 100 VDSL2 Segment 112 0 Vcl flux 112 1 Vpl flux 112 101 C VLAN 112 102 XPON Service-port 114 1 V5 interface 114 2 2M link 114 3 Logic C channel 120 0 VLAN 127 1 IMA group 127 2 IMA link 145 0 MG 153 0 L2UA link 153 1 L2UA link 182 1 XPON ONT 182 2 XPON UNI 182 3 EPON ONT 182 4 EPON UNI 191 1 GPON UNI PORT 192 1 EPON UNI PORT 191 2 GPON ONU 192 2 EPON ONU 191 15 XPON ONT ETH PORT 192 11 EPON ONT ETH PORT ---------------------------------------
Status: current Access: read-write
OBJECT-TYPE    
  Integer32  

hwBulkFileObjectSubType 1.3.6.1.4.1.2011.6.103.1.1.4.1.10
Identify sub-type of object. The device will collect statistics on all ports according to hwBulkFileObjectMainType and hwBulkFileObjectSubType if these two leaves are not null. The values of hwBulkFileObjectMainType and hwBulkFileObjectSubType need to match as follows: -------------------------------------- ulMainType ulSubType Note --------------------------------------- 1 101 Device 3 113 V5 Interface user frame 4 100 Borad 4 101 Memory 6 105 ADSL port(only support ADSL2+) 6 108 E1 port 6 109 Ethernet port 6 111 interboard-port 6 112 backboard port 6 113 V5 user 6 119 ATM port 6 126 SHDSL port 6 141 DS3 port 6 173 Ethernet port 6 175 VDSL2 port 6 1080 E1 port 6 108000 E1 port 7 100 VDSL2 Segment 112 0 Vcl flux 112 1 Vpl flux 112 101 C VLAN 112 102 XPON Service-port 114 1 V5 interface 114 2 2M link 114 3 Logic C channel 120 0 VLAN 127 1 IMA group 127 2 IMA link 145 0 MG 153 0 L2UA link 153 1 L2UA link 182 1 GPON ONT 182 2 GPON UNI 182 3 EPON ONT 182 4 EPON UNI 191 1 GPON UNI PORT 192 1 EPON UNI PORT 191 2 GPON ONU 192 2 EPON ONU 191 15 GPON ONT ETH PORT 192 11 EPON ONT ETH PORT ---------------------------------------
Status: current Access: read-write
OBJECT-TYPE    
  Integer32  

hwBulkFileRowStatus 1.3.6.1.4.1.2011.6.103.1.1.4.1.11
Row operation object. When the centralized bulk feature is enabled, the file in the running state cannot be deleted, whereas when the distributed bulk feature is enabled, the file in any state can be deleted.
Status: current Access: read-create
OBJECT-TYPE    
  RowStatus  

hwBulkFileColNumMode 1.3.6.1.4.1.2011.6.103.1.1.4.1.12
Setting whether to report the statistics collected in the previous interval. After the statistics file is created, the identifier cannot be changed. Options: 1.reportLastSection(1) -indicates that the statistics collected in the previous interval is contained in the statistics file of the current interval. 2.not-reportLastSection(2)-indicates that the statistics data of the last interval is not contained in the statistics file of the current interval. This object takes effect only when the centralized bulk feature is enabled, and does not take effect when the distributed bulk feature is enabled.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER reportLastSection(1), not-reportLastSection(2)  

hwBulkFileCollectStartTime 1.3.6.1.4.1.2011.6.103.1.1.4.1.13
Setting the start time of the data collection with intervals of six hours or one day. The default start time is 00:00, and can only be an integer multiple of 15 minutes. The start time of the data collection with the interval of 15 minutes can be set, but it does not take effect actually.
Status: current Access: read-create
OBJECT-TYPE    
  OCTET STRING Size(1..5)  

hwBulkFileCopyNum 1.3.6.1.4.1.2011.6.103.1.1.4.1.14
The number of saved files during this task, read-only.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

hwBulkObjectCapItemList 1.3.6.1.4.1.2011.6.103.1.1.4.1.15
List of the statistical index. Through this object, the statistical index can be configured in batches in the format of bit-domain string. Each file supports up to 256 statistical indexes. The statistical index hwBulkObjectCapItemList is of the bit type. It can be configured as follows: to configure the index n, set the nth in the bit string to 1, that is,......000100......For example, to configure the index 1, set the first character of the string to 1, and issue 0100 0000, namely, # 0x40 (note that the value of the bit type starts from 0). For example, to configure the index 8, set the eighth character of the string to 1, and issue 0000 0000 1000 0000, namely, # 0x00 0x80. If the statistical indexes 1, 2, 3, 201, 202 are supported, # 0x70 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00. 0x00 0x00. 0x00 0x60 is issued. This object takes effect only when the distributed bulk feature is enabled.
Status: current Access: read-write
OBJECT-TYPE    
  BITS pmp-dsl-opr-mode(0), pmp-atur-vdr-id(1), pmp-dsl-prf-name(2), pmp-crc-ec-ner-us(3), pmp-crc-ec-fer-ds(4), pmp-fecs-ner-us(5), pmp-fecs-fer-ds(6), pmp-fec-evt-ner-us(7), pmp-fec-evt-fer-ds(8), pmp-es-ner-us(9), pmp-es-fer-ds(10), pmp-ses-ner-us(11), pmp-ses-fer-ds(12), pmp-uas-ner-us(13), pmp-uas-ner-ds(14), pmp-loss-ner-us(15), pmp-loss-fer-ds(16), pmp-lofs-ner-us(17), pmp-lofs-fer-ds(18), pmp-lols-fer-us(19), pmp-lops-fer-ds(20), pmp-suc-init(21), pmp-fail-full-init(22), pmp-line-attn-us(23), pmp-line-attn-ds(24), pmp-snr-us(25), pmp-snr-ds(26), pmp-line-rate-us(27), pmp-line-rate-ds(28), pmp-max-atbl-dr-us(29), pmp-max-atbl-dr-ds(30), pmp-up-time(31), pmp-trfc-us(32), pmp-trfc-ds(33), pmp-pwr-stt(34), pmp-nte-pwr-stt(35), pmp-aatp-us(36), pmp-aatp-ds(37), pmp-r-us(38), pmp-r-ds(39), pmp-s-us(40), pmp-s-ds(41), pmp-d-us(42), pmp-d-ds(43), pmp-n-us(44), pmp-n-ds(45), pmp-act-inp-us(46), pmp-act-inp-ds(47), pmp-inminpeq-us(48), pmp-inminpeq-ds(49), pmp-inmiat-us(50), pmp-inmiat-ds(51), pmp-inmme-us(52), pmp-inmme-ds(53), pmp-rtxused-us(54), pmp-rtxused-ds(55), pmp-resyn-ratio(56), pmp-pcb-ds(57), pmp-modu-mode(58), pmp-pbo-ds(59), pmp-pbo-us(60), pmp-elem1-support(61), pmp-interval-valid(62), pmp-snr-pt-us(201), pmp-snr-pt-ds(202), pmp-bit-al-us(203), pmp-bit-al-ds(204), pmp-hlog-us(205), pmp-hlog-ds(206), pmp-qln-us(207), pmp-qln-ds(208), pmp-grpsize-us(209), pmp-grpsize-ds(210), pmp-u-packets(250), pmp-d-packets(251), pmp-u-bytes(252), pmp-d-bytes(253), pmp-u-car-d-packets(254), pmp-d-car-d-packets(255), pmp-u-o-d-packets(256), pmp-d-o-d-packets(257), pmp-u-cvlan-packets(258), pmp-d-cvlan-packets(259), pmp-xpon-service-vlan(270), pmp-xpon-onu-id(271), pmp-tran-octs(300), pmp-recv-octs(301), pmp-tran-eth-port-packets(302), pmp-recv-eth-port-packets(303), pmp-recv-discard-eth-port-packets(304), pmp-tran-discard-eth-port-packets(305), pmp-tran-green-send-eth-port-octs(306), pmp-tran-green-send-eth-port-number(307), pmp-tran-green-send-discard-eth-number(308), pmp-tran-yellow-send-eth-port-octs(309), pmp-tran-yellow-send-eth-port-number(310), pmp-tran-yellow-send-discard-eth-number(311), pmp-eth-tran-unicast-packets(312), pmp-eth-recv-unicast-packets(313), pmp-eth-tran-multicast-packets(314), pmp-eth-recv-multicast-packets(315), pmp-eth-tran-boardcast-packets(316), pmp-eth-recv-boardcast-packets(317), pmp-eth-tran-pause-packets(318), pmp-eth-alignment-error-packets(319), pmp-eth-tran-crc-error-packets(320), pmp-eth-recv-crc-error-packets(321), pmp-eth-collision-packets(322), pmp-eth-tran-oversized-packets(323), pmp-eth-recv-oversized-packets(324), pmp-eth-single-collision-packets(325), pmp-eth-multi-collision-packets(326), pmp-eth-discard-undersized-packets(327), pmp-eth-tran-undersized-packets(328), pmp-eth-recv-undersized-packets(329), pmp-eth-tran-fragments(330), pmp-eth-recv-fragments(331), pmp-eth-tran-jabbers(332), pmp-eth-recv-jabbers(333), pmp-eth-tran-64-byte-packets(334), pmp-eth-recv-64-byte-packets(335), pmp-eth-tran-65-127-byte-packets(336), pmp-eth-recv-65-127-byte-packets(337), pmp-eth-tran-128-255-byte-packets(338), pmp-eth-recv-128-255-byte-packets(339), pmp-eth-tran-256-511-byte-packets(340), pmp-eth-recv-256-511-byte-packets(341), pmp-eth-tran-512-1023-byte-packets(342), pmp-eth-recv-512-1023-byte-packets(343), pmp-eth-tran-1024-1518-byte-packets(344), pmp-eth-recv-1024-1518-byte-packets(345), pmp-eth-tran-error-packets(346), pmp-eth-recv-error-packets(347), pmp-eth-interval-valid(348), pmp-gpon-uni-us-rate(360), pmp-gpon-uni-ds-rate(361), pmp-gpon-uni-err-pkt-ratio(362), pmp-xpon-uni-optics-temp(363), pmp-xpon-uni-laser-bias-curr(364), pmp-xpon-uni-optics-volt(365), pmp-xpon-uni-optics-tx-power(366), pmp-gpon-uni-tran-octs(367), pmp-gpon-uni-recv-octs(368), pmp-gpon-uni-tran-packets(369), pmp-gpon-uni-recv-packets(370), pmp-gpon-uni-discard-packets(371), pmp-gpon-uni-tx-discard-packets(372), pmp-gpon-uni-recv-error-packets(373), pmp-epon-uni-us-rate(376), pmp-epon-uni-ds-rate(377), pmp-epon-uni-err-pkt-ratio(378), pmp-epon-uni-optics-temp(379), pmp-epon-uni-laser-bias-curr(380), pmp-epon-uni-optics-volt(381), pmp-epon-uni-optics-tx-power(382), pmp-epon-uni-tx-discard-packets(383), pmp-epon-uni-rx-discard-packets(384), pmp-epon-uni-recv-octs(385), pmp-epon-uni-tran-octs(386), pmp-epon-uni-recv-error-packets(387), pmp-epon-uni-tran-packets(388), pmp-epon-uni-recv-packets(389), pmp-gpon-nni-us-octs(390), pmp-gpon-nni-ds-octs(391), pmp-gpon-nni-us-rate(392), pmp-gpon-nni-ds-rate(393), pmp-xpon-nni-optics-temp(394), pmp-xpon-nni-laser-bias-curr(395), pmp-xpon-nni-optics-volt(396), pmp-xpon-nni-optics-tx-power(397), pmp-xpon-nni-optics-rx-power(398), pmp-xpon-olt-nni-optics-rx-power(399), pmp-gpon-nni-lofi(400), pmp-gpon-nni-up-err-delimiter(401), pmp-gpon-nni-up-err-bip(402), pmp-gpon-nni-down-err-bip(403), pmp-gpon-nni-up-fec-correct-block(404), pmp-gpon-nni-up-fec-uncorrect-block(405), pmp-gpon-nni-up-hec(406), pmp-gpon-nni-offline-times(407), pmp-epon-nni-us-rate(408), pmp-epon-nni-ds-rate(409), pmp-epon-nni-optics-temp(410), pmp-epon-nni-laser-bias-curr(411), pmp-epon-nni-optics-volt(412), pmp-epon-nni-optics-tx-power(413), pmp-epon-nni-optics-rx-power(414), pmp-epon-olt-nni-optics-rx-power(415), pmp-epon-nni-us-octs(416), pmp-epon-nni-ds-octs(417), pmp-epon-nni-offline-times(418), pmp-xpon-onu-eth-port-us-rate(424), pmp-xpon-onu-eth-port-ds-rate(425), pmp-xpon-onu-eth-port-rx-total(426), pmp-xpon-onu-eth-port-rx-unic(427), pmp-xpon-onu-eth-port-rx-brdc(428), pmp-xpon-onu-eth-port-rx-mltc(429), pmp-xpon-onu-eth-port-tx-total(430), pmp-xpon-onu-eth-port-tx-unic(431), pmp-xpon-onu-eth-port-tx-brdc(432), pmp-xpon-onu-eth-port-tx-mltc(433), pmp-xpon-onu-eth-port-rx-octs(434), pmp-xpon-onu-eth-port-tx-octs(435), pmp-xpon-onu-eth-port-rx-error-packets(436), pmp-epon-onu-eth-port-us-rate(440), pmp-epon-onu-eth-port-ds-rate(441), pmp-epon-onu-eth-port-recv-total(442), pmp-epon-onu-eth-port-rx-unic(443), pmp-epon-onu-eth-port-rx-brdc(444), pmp-epon-onu-eth-port-rx-mltc(445), pmp-epon-onu-eth-port-tx-total(446), pmp-epon-onu-eth-port-tx-unic(447), pmp-epon-onu-eth-port-tx-brdc(448), pmp-epon-onu-eth-port-tx-mltc(449), pmp-epon-onu-eth-port-rx-octs(450), pmp-epon-onu-eth-port-tx-octs(451), pmp-epon-onu-eth-port-rx-error-packets(452), pmp-backboard-port-bandwith(500), pmp-recv-small-mainboard-octs(501), pmp-tran-small-mainboard-octs(502), pmp-recv-discard-small-mainboard-packets(503), pmp-tran-discard-small-mainboard-packets(504), pmp-recv-big-mainboard-octs(505), pmp-tran-big-mainboard-octs(506), pmp-recv-discard-big-mainboard-packets(507), pmp-tran-discard-big-mainboard-packets(508), pmp-interboardport-bandwith(520), pmp-interboardport-recv-octs(521), pmp-interboardport-tran-octs(522), pmp-interboardport-recv-discard-packets(523), pmp-interboardport-tran-discard-packets(524), board-cpu-occupation(600), board-temperature(601), board-dsp-occupation(602), board-mgif-failed-num(650), pmp-gpon-nni-recv-error-packets(700), pmp-gpon-nni-tran-packets(701), pmp-gpon-nni-recv-packets(702), pmp-epon-nni-recv-error-packets(730), pmp-epon-nni-tran-packets(731), pmp-epon-nni-recv-packets(732)  

hwBulkSaveFileTable 1.3.6.1.4.1.2011.6.103.1.1.5
This table is used for querying information about the history files saved by the statistical object. The indexes of this table are hwBulkFileIndex and hwBulkSaveFileIndex. This table does not support operations such as create, modify and delete, but supports get and walk operations.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    HwBulkSaveFileEntry

hwBulkSaveFileEntry 1.3.6.1.4.1.2011.6.103.1.1.5.1
This table is used for querying information about the history files saved by the statistical object. The indexes of this entry are hwBulkFileIndex and hwBulkSaveFileIndex. This table does not support operations such as create, modify and delete, but supports get and walk operations.
Status: current Access: not-accessible
OBJECT-TYPE    
  HwBulkSaveFileEntry  

hwBulkSaveFileIndex 1.3.6.1.4.1.2011.6.103.1.1.5.1.1
Index of bulk file copy. It is a unique identifier for a bulk save file.
Status: current Access: not-accessible
OBJECT-TYPE    
  Integer32  

hwBulkSaveFileTime 1.3.6.1.4.1.2011.6.103.1.1.5.1.2
Time of saving the statistics file.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..20)  

hwBulkAndTCARelationship 1.3.6.1.4.1.2011.6.103.1.1.6
Switch of the correlation between the bulk performance statistics and threshold alarm. Options: 1.on(1) -the switch is on. 2.off(2)-the switch is off. This object is not supported currently.
Status: obsolete Access: read-write
OBJECT-TYPE    
  INTEGER on(1), off(2)  

hwBulkFileNameRule 1.3.6.1.4.1.2011.6.103.1.1.7
This object is used to set the rule for naming a statistic file. If this object is set to interval, the measurement period is contained in the backup file. If this object is set to ipaddress, the source IP address of the trap is contained in the backup file. If this object is not specified, the default value is used and the rule for naming a statistics file in this version is the same as that in the earlier version.
Status: current Access: read-write
OBJECT-TYPE    
  BITS filenme-ipaddress(0), filenme-interval(1)  

hwBulkObjectMgmt 1.3.6.1.4.1.2011.6.103.1.2
OBJECT IDENTIFIER    

hwBulkOIDTable 1.3.6.1.4.1.2011.6.103.1.2.1
OID management table in the bulk file. Prerequisite for the operation is that the bulk file is listed in the hwBulkFileTable and the file state is ready. The indexes of this table are hwBulkOID and hwBulkFileIndex in hwBulkFileTable. In the case of the distributed bulk performance statistics, this table is not supported.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    HwBulkOIDEntry

hwBulkOIDEntry 1.3.6.1.4.1.2011.6.103.1.2.1.1
OID management table in the bulk file. Prerequisite for the operation is that the bulk file is listed in the hwBulkFileTable and the file state is ready. The indexes of this entry are hwBulkOID and hwBulkFileIndex in hwBulkFileTable. In the case of the distributed bulk performance statistics, this table is not supported.
Status: current Access: not-accessible
OBJECT-TYPE    
  HwBulkOIDEntry  

hwBulkOID 1.3.6.1.4.1.2011.6.103.1.2.1.1.1
Index in the case of adding the object in the statistics file. The OID of the object is collected. The OID need not contain the index. The maximum length of the OID (excluding '.') is 20 digits.
Status: current Access: not-accessible
OBJECT-TYPE    
  OBJECT IDENTIFIER  

hwBulkOIDRowStatus 1.3.6.1.4.1.2011.6.103.1.2.1.1.2
Row operation object hwBulkOIDRowStatus. When the creation operation is performed in hwBulkOIDRowStatus, the enumeration value createAndGo (4) is used. During the creation operation, hwBulkFileIndex and hwBulkObjectIndex must be issued together. Before the creation operation, make sure that hwBulkFileTable contains a statistical file record. If a file corresponds to multiple OIDs, the program checks whether the number of OIDs is the same as the number of indexes. If the number of OIDs is different from the number of indexes, the file cannot be issued. The user must ensure that the indexes corresponding to the same OID in different tables are the same. Otherwise, the collected data may be abnormal. During dynamic creation, the creation configuration takes effect only after the next report period of the statistical file. When the deletion operation is performed, the enumeration value destroy (6) is used. During the deletion operation, the indexes hwBulkFileIndex and hwBulkFileIndexmust must be issued together. When the statistical task is started, after the IOD is deleted, it cannot be queried but still exists actually. The deletion of the OID takes effect after the next report period.
Status: current Access: read-create
OBJECT-TYPE    
  RowStatus  

hwBulkIndexMgmt 1.3.6.1.4.1.2011.6.103.1.3
OBJECT IDENTIFIER    

hwBulkObjectIndexCount 1.3.6.1.4.1.2011.6.103.1.3.1
Total number of object indexes.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

hwBulkObjectTable 1.3.6.1.4.1.2011.6.103.1.3.2
Object management table in the bulk file, providing add/delete operations. Prerequisite for the operation is that the bulk file is listed in hwBulkFileTable and the file state is ready. The indexes of this table are hwBulkObjectIndex and hwBulkFileIndex in hwBulkFileTable. The object hwBulkObjectOIDIndex can be used to configure a precise index or a fuzzy index. When one MIB object has multiple indexes, a '.' is used to separate the indexes. For example, in a MIB table with the shelf ID/slot ID/port ID as the index, when you need to collect the information about shelf 0/slot 5/port 2, configure a precise index, namely, a character string 0.5.2. When you need to collect the information about all the ports in slot 5 of shelf 0, configure a fuzzy index, namely, a character string 0.5.all. all is used to represent fuzzy index. When you need to collect the information about all the ports, use a fuzzy index all.all.all. In the case of the distributed bulk performance statistics, this table is not supported.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    HWBulkObjectEntry

hwBulkObjectEntry 1.3.6.1.4.1.2011.6.103.1.3.2.1
Object management table in the bulk file, providing add/delete operations. Prerequisite for the operation is that the bulk file is listed in hwBulkFileTable and the file state is ready. The indexes of this entry are hwBulkObjectIndex and hwBulkFileIndex in hwBulkFileTable. The object hwBulkObjectOIDIndex can be used to configure a precise index or a fuzzy index. When one MIB object has multiple indexes, a '.' is used to separate the indexes. For example, in a MIB table with the shelf ID/slot ID/port ID as the index, when you need to collect the information about shelf 0/slot 5/port 2, configure a precise index, namely, a character string 0.5.2. When you need to collect the information about all the ports in slot 5 of shelf 0, configure a fuzzy index, namely, a character string 0.5.all. all is used to represent fuzzy index. When you need to collect the information about all the ports, use a fuzzy index all.all.all. In the case of the distributed bulk performance statistics, this table is not supported.
Status: current Access: not-accessible
OBJECT-TYPE    
  HWBulkObjectEntry  

hwBulkObjectIndex 1.3.6.1.4.1.2011.6.103.1.3.2.1.1
Object index in the Bulk file. A unique identifier for a record, indicating the sequence of objects.
Status: current Access: not-accessible
OBJECT-TYPE    
  Integer32  

hwBulkObjectOIDIndex 1.3.6.1.4.1.2011.6.103.1.3.2.1.2
Start index of objects in a task, for each task there can be many start index.In order to get a value , a complete OID can be formed by adding the hwBulkOID in hwBulkOIDTable and the hwBulkObjectOIDIndex from hwBulkObjectTable.
Status: current Access: read-create
OBJECT-TYPE    
  OCTET STRING Size(1..63)  

hwBulkObjectLength 1.3.6.1.4.1.2011.6.103.1.3.2.1.3
Number of continuous objects. The default value is 1, indicating that only this object value will be collected.
Status: obsolete Access: read-create
OBJECT-TYPE    
  Integer32  

hwBulkObjectRowStatus 1.3.6.1.4.1.2011.6.103.1.3.2.1.4
Row operation object hwBulkObjectRowStatus. The enumeration value destroy (6) is used for the deletion.During the deletion operation, the indexes hwBulkFileIndex and hwBulkObjectIndex must be issued together. When the statistics file is running, the deletion will take effect in the next report period after the deletion operation is performed. During the creation operation, hwBulkFileIndex and hwBulkObjectIndex must be issued together. Before the creation operation, make sure that hwBulkFileTable contains a statistical file. hwBulkObjectOIDIndex can be to configure a precise index or a fuzzy index. When one MIB object has multiple indexes, a '.' is used to separate the indexes. For example, in a MIB table with the shelf ID/slot ID/port ID as the index, when you need to collect the information about shelf 0/slot 5/port 2, configure a precise index, namely, a character string 0.5.2. When you need to collect the information about all the ports in slot 5 of shelf 0, configure a fuzzy index, namely, a character string 0.5.all. all is used to represent fuzzy index. When you need to collect the information about all the ports, use a fuzzy index all.all.all. The index with its index type configured to character string type is not supported. If the configured index is the same as the data that is already configured, the operation fails.
Status: current Access: read-create
OBJECT-TYPE    
  RowStatus  

hwBulkObjectCapItemMgnt 1.3.6.1.4.1.2011.6.103.1.5
OBJECT IDENTIFIER    

hwBulkObjectCapItemTable 1.3.6.1.4.1.2011.6.103.1.5.1
This table is used to add or delete the statistical index in the configuration of the statistics file. The indexes of this table are hwBulkObjectCapItem and hwBulkFileIndex in hwBulkFileTable. This table does not support the modify operation. In the case of the distributed bulk performance statistics, this table cannot be operated.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    HwBulkObjectCapItemEntry

hwBulkObjectCapItemEntry 1.3.6.1.4.1.2011.6.103.1.5.1.1
This table is used to add or delete the statistical index in the configuration of the statistics file. The indexes of this entry are hwBulkObjectCapItem and hwBulkFileIndex in hwBulkFileTable. This table does not support the modify operation. In the case of the distributed bulk performance statistics, this table cannot be operated.
Status: current Access: not-accessible
OBJECT-TYPE    
  HwBulkObjectCapItemEntry  

hwBulkObjectCapItem 1.3.6.1.4.1.2011.6.103.1.5.1.1.1
Statistical task index, which is used for setting the performance data items for a statistical task.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

hwBulkObjectCapItemRowStatus 1.3.6.1.4.1.2011.6.103.1.5.1.1.2
Row operation object. When the statistics file is running, the statistical index can be added or deleted. The adding or deletion takes effect after the next period of the statistics file. Each statistics file can be configured with up to 256 statistical indexes. If the number of statistical indexes exceeds 256, you cannot add the statistical index any more.When the statistics file is running, at least one statistics file needs to be left undeleted. If the number of statistical indexes is 1, you cannot delete the statistical index any more. This restriction does not apply to the case of the non-running state of the statistics file. createAndGo(4)is supplied to create a new instance of a conceptual row. destroy(6)is supplied to delete the instances associated with an existing conceptual row.
Status: current Access: read-write
OBJECT-TYPE    
  RowStatus  

hwBulkTrapVbOids 1.3.6.1.4.1.2011.6.103.1.6
OBJECT IDENTIFIER    

hwTrapAutoBackupFileName 1.3.6.1.4.1.2011.6.103.1.6.1
The file name of auto-backup bulk file. The format of the file name is 'statistical task name_time_file index_[ipaddress]_[interval]'. Parameters ipaddress and interval are optional. If the value of node hwBulkFileFormat is bulkASCIIWithZipFile(3), the file is a .zip file and the file name is 'statistical task name_time_file index_[ipaddress]_[interval].zip'.If the value of node hwBulkFileFormat is not bulkASCIIWithZipFile(3), the file is not a .zip file. Statistical task names correspond to the values of parameter hwBulkFileName, and hwBulkFileName contains 1 to 63 characters. The time format for version2 is DDHHMM and that for version3 is YYYYMMDDHHMMSS. The time indicates the time when the file is created for version2. The time indicates the start time of data collection for version3. File indexes correspond to the values of parameter hwBulkSaveFileIndex. Ipaddress is the source IP address of TRAP. Parameter interval indicates data collection interval. File names can be generated automatically before transfer. The length of the file name cannot be longer than 129 characters.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  OCTET STRING Size(1..129)  

hwBulkTraps 1.3.6.1.4.1.2011.6.103.1.7
OBJECT IDENTIFIER    

hwBulkAlarmTraps 1.3.6.1.4.1.2011.6.103.1.7.1
OBJECT IDENTIFIER    

hwBulkAlarmTrapsPrefix 1.3.6.1.4.1.2011.6.103.1.7.1.0
OBJECT IDENTIFIER    

hwBulkFileFailAlarmTrap 1.3.6.1.4.1.2011.6.103.1.7.1.0.1
This trap message is reported when the statistic file is created unsuccessfully.
Status: current Access: accessible-for-notify
NOTIFICATION-TYPE    

hwBulkCommonTraps 1.3.6.1.4.1.2011.6.103.1.7.2
OBJECT IDENTIFIER    

hwBulkCommonTrapsPrefix 1.3.6.1.4.1.2011.6.103.1.7.2.0
OBJECT IDENTIFIER    

hwBulkBackupStartCommonTrap 1.3.6.1.4.1.2011.6.103.1.7.2.0.1
When the centralized bulk performance statistic feature is enabled and a statistical task is started, this trap message is reported after a statistical file is generated. When the distributed bulk performance statistic feature is enabled, this trap message is reported after the host incorporates all the board files.
Status: current Access: accessible-for-notify
NOTIFICATION-TYPE    

hwBulkBackupSuccessCommonTrap 1.3.6.1.4.1.2011.6.103.1.7.2.0.2
This trap message is reported when the statistical file is backed up successfully on the NMS.
Status: current Access: accessible-for-notify
NOTIFICATION-TYPE    

hwBulkAutobackupSuccessTrap 1.3.6.1.4.1.2011.6.103.1.7.2.0.3
This trap message is reported when the statistical file is auto-backed up successfully on the NMS.
Status: current Access: accessible-for-notify
NOTIFICATION-TYPE    

hwBulkAutobackupFailTrap 1.3.6.1.4.1.2011.6.103.1.7.2.0.4
This trap message is reported when the statistical file is auto-backed up unsuccessfully on the NMS.
Status: current Access: accessible-for-notify
NOTIFICATION-TYPE    

hwBulkFTPClient 1.3.6.1.4.1.2011.6.103.2
OBJECT IDENTIFIER    

hwFTPClientMgmt 1.3.6.1.4.1.2011.6.103.2.1
OBJECT IDENTIFIER    

hwFTPClientTableNextIndex 1.3.6.1.4.1.2011.6.103.2.1.1
Next available index for table FTPClientTable. If no available index, the value will be filled with '-1'.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

hwFTPClientTable 1.3.6.1.4.1.2011.6.103.2.1.2
FTP client management table is used for transferring the statistics file, and providing add/delete operations. The host servers as client, while the NMS as server. The index of this table is hwFTPClientIndex. The operation for this table can be successful only when the bulk collection of the backup files is successful.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    HwFTPClientEntry

hwFTPClientEntry 1.3.6.1.4.1.2011.6.103.2.1.2.1
FTP client management table is used for transferring the statistics file, and providing add/delete operations. The host servers as client, while the NMS as server. The index of this entry is hwFTPClientIndex. The operation for this table can be successful only when the bulk collection of the backup files is successful.
Status: current Access: not-accessible
OBJECT-TYPE    
  HwFTPClientEntry  

hwFTPClientIndex 1.3.6.1.4.1.2011.6.103.2.1.2.1.1
FTP client index, an unique identifier of a record.
Status: current Access: not-accessible
OBJECT-TYPE    
  Integer32 1..4  

hwFTPClientMode 1.3.6.1.4.1.2011.6.103.2.1.2.1.2
FTP mode: ftp(1), tftp(2), sftp(3) Options: 1.ftp(1) -FTP client mode. 2.tftp(2) -TFTP client mode. 3.sftp(3) -SFTP client mode. If FTP/SFTP is used to transfer files, hwFTPClientUserName and hwFTPClientPasswd need to be bound. Binding is not required in the case of file transfer through TFTP. The specified port ID needs to be bound in the case of file transfer through SFTP.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER ftp(1), tftp(2), sftp(3)  

hwFTPClientOper 1.3.6.1.4.1.2011.6.103.2.1.2.1.3
File transfer format. Options: 1.putBinary(1) -file transfer format is putBinary.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER putBinary(1)  

hwFTPClientFileName 1.3.6.1.4.1.2011.6.103.2.1.2.1.4
Source file name. In the case of centralized bulk performance statistics, the format is 'copy index of the latest file + / + name of the statistics file'. For example, if the statistical task is ABCD and you need to obtain the second file, the file name of the hwFTPClientFileName is 2/ABCD. In the case of distributed bulk performance statistics, the format is 'version of the file list|index of the file 1(hwBulkSaveFileIndex)/index of the statistical task 1(hwBulkFileIndex), file index 2/statistical task index 2......'. For the file list version, only version2 and version3 are currently supported. For example, when the user needs to obtain the first, second, third, and fourth files with the statistical task index being 1 and the fifth, sixth, seventh and eighth files with the statistical task index being 6, then the value of the issued hwFTPClientFileName is version2|1/1,2/1,3/1,4/1,5/6,6/6,7/6,8/6.
Status: current Access: read-create
OBJECT-TYPE    
  OCTET STRING Size(1..254)  

hwFTPDestFileName 1.3.6.1.4.1.2011.6.103.2.1.2.1.5
Destination file name, including path. In the centralized bulk performance statistics collection, the format of the file name is 'path name + | + destination file name'. For the purpose of saving FTP connections, when the NMS needs to obtain multiple statistics files, the Mput/Mget mode of FTP can be used. In this case, hwFTPClientFileName and hwFTPDestFileName must contain multiple file names. The files are in the format of 'path|file name 1|file name 2|file name 3......'. Even if the path is null, the format must be '|file name 1|file name 2|file name 3......'. In hwFTPClientFileName, each file name corresponds to its own index. In hwFTPDestFileName, however, one path corresponds to multiple file names. For example, when the path is c: emp and two files need to be obtained, hwFTPDestFileName is in the format of 'c: emp|file name 1|file name 2', and hwFTPClientFileName is in the format of '|1/ABCD|20/XYZ|30/XXXX'. In the case of distributed bulk performance statistics, the format is 'version of the file list|path for uploading the file|device ID|day and time|file index (hwBulkSaveFileIndex)/index of the statistical task 1 (hwBulkFileIndex), file index/statistical task index (hwBulkFileIndex)......'.For the file list version, Version2 and version3 are currently supported. Path for uploading the file can be provided with the drive letter, such as c: emp. The time format for version 2 is DDHHMM and that for version3 is YYYYMMDDHHMMSS. The time indicates the time when the file is created for version2. The time indicates the start time of data collection for version3. The system automatically creates the time for version3. For example, if the user needs to transfer the first, second, third and fourth files under the device 7340032 and with the statistical index being 1 at 13:30:20 on the December 2, 2012, and the fifth, sixth, seventh, and eighth files with the statistical index being 6 to the local directory of bulkfile, then the value of the issued hwFTPClientFileName is version2| bulkfile| 7340032|021330|1/1,2/1,3/1,4/1,5/6,6/6,7/6,8/6.If the version is version3,then the value of the issued hwFTPClientFileName is version3| bulkfile|||1/1,2/1,3/1,4/1,5/6,6/6,7/6,8/6. It should be noted that the file lists (file sequence) in hwFTPClientFileName and hwFTPDestFileName must be completely the same. The format of the file name is 'statistical task name (hwBulkFileName)_time_file index[_ipadress][_interval]'. In TFTP mode, the path cannot be configured. hwBulkFileName contains 1 to 63 characters. The path specified for FTP/SFTP contains 1 to 63 characters. Therefore, the sum of hwBulkFileName and path cannot be longer than 128 characters.
Status: current Access: read-create
OBJECT-TYPE    
  OCTET STRING Size(1..254)  

hwFTPClientServerIP 1.3.6.1.4.1.2011.6.103.2.1.2.1.6
IP address of the FTP server.
Status: current Access: read-create
OBJECT-TYPE    
  IpAddress  

hwFTPClientUserName 1.3.6.1.4.1.2011.6.103.2.1.2.1.7
User name for FTP/SFTP connection. For the TFTP mode, this field is invalid.
Status: current Access: read-create
OBJECT-TYPE    
  OCTET STRING Size(0..31)  

hwFTPClientPasswd 1.3.6.1.4.1.2011.6.103.2.1.2.1.8
Password for FTP/SFTP connection. For the TFTP mode, this field is invalid.
Status: current Access: read-create
OBJECT-TYPE    
  OCTET STRING Size(0..15)  

hwFTPClientIfIndex 1.3.6.1.4.1.2011.6.103.2.1.2.1.9
IfIndex in the bulk file in order to get all data with IfIndex as the object index. If the IfIndex equals to zero, the final file will be filled with all data in current memory.
Status: current Access: read-create
OBJECT-TYPE    
  Integer32  

hwFTPClientState 1.3.6.1.4.1.2011.6.103.2.1.2.1.10
FTP operation status: Options: 1.running(1) -indicates that FTP is running. If you set this object as running, the FTP will be started. 2.success(2) -indicates that FTP completed successfully. 3.fileOpenFail(3) -indicates that FTP failed. The cause is file open failure. 4.unreachableServerIp(4)-indicates that FTP failed. The cause is that the IP address of the server is not reachable. 5.linkFailed(5) -indicates that FTP failed. The cause is connecting to server failed. 6.authenticateFailed(6) -indicates that FTP failed. The cause is authenticating failed.For FTP mode only. 7.fileReadFailed(7) -indicates that FTP failed. The cause is reading file failed. 8.fileWriteFailed(8) -indicates that FTP failed. The cause is writing file failed. 9.failed(9) -indicates that FTP failed,General error.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER running(1), success(2), fileOpenFail(3), unreachableServerIp(4), linkFailed(5), authenticateFailed(6), fileReadFailed(7), fileWriteFailed(8), failed(9)  

hwFTPClientRowStatus 1.3.6.1.4.1.2011.6.103.2.1.2.1.11
Row operation object. createAndGo(4)is supplied to create a new instance of a conceptual row. destroy(6)is supplied to delete the instances associated with an existing conceptual row.
Status: current Access: read-create
OBJECT-TYPE    
  RowStatus  

hwFTPClientServerPort 1.3.6.1.4.1.2011.6.103.2.1.2.1.12
In SFTP port.FTP and TFTP modes, this field is invalid.
Status: current Access: read-create
OBJECT-TYPE    
  Integer32  

hwTCAObjects 1.3.6.1.4.1.2011.6.103.3
OBJECT IDENTIFIER    

hwTCAMgmt 1.3.6.1.4.1.2011.6.103.3.1
OBJECT IDENTIFIER    

hwDefineTCATable 1.3.6.1.4.1.2011.6.103.3.1.1
TCA Management Table. This object is not supported currently. The indexes of this table are hwDefineFacilityType, hwDefineMontype, hwDefineAid and hwDefineTmper.
Status: obsolete Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    HwDefineTCAEntry

hwDefineTCAEntry 1.3.6.1.4.1.2011.6.103.3.1.1.1
TCA Management Table. This object is not supported currently. The indexes of this entry are hwDefineFacilityType, hwDefineMontype, hwDefineAid and hwDefineTmper.
Status: obsolete Access: not-accessible
OBJECT-TYPE    
  HwDefineTCAEntry  

hwDefineFacilityType 1.3.6.1.4.1.2011.6.103.3.1.1.1.1
Facility type. This object is not supported currently. Options: 1.system(1) -indicates facility type is system. 2.igmp(2) -indicates facility type is igmp. 3.dhcp(3) -indicates facility type is dhcp. 4.eapol(4) -indicates facility type is eapol. 5.vlan(5) -indicates facility type is vlan. 6.ampeth(100) -indicates facility type is ampeth. 7.xdsladsl(200)-indicates facility type is xdsladsl.
Status: obsolete Access: not-accessible
OBJECT-TYPE    
  INTEGER system(1), igmp(2), dhcp(3), eapol(4), vlan(5), ampeth(100), xdsladsl(200)  

hwDefineMontype 1.3.6.1.4.1.2011.6.103.3.1.1.1.2
Type of the monitored object Options: 1.cpu(1) -cpu 2.memory(2) -memory 3.rxdd(3) -The number of DHCP DISCOVER. 4.rxdrq(4) -The number of DHCP REQUEST. 5.rxdrl(5) -The number of DHCP RELEASE. 6.rxdi(6) -The number of DHCP INFORM. 7.rxuntrust(7) -The number of DHCP Option82 Packets with Untrusted Option82. 8.rxovl(8) -The number of DHCP Option82 Packets exceed the maximum size after appending option82. 9.rxovlopt(9) -The number of packets exceed the maximum option82 size. 10.rxdisp(10) -The number of Discarded Packets of Upstream data flow from user to server in vlan. 11.txdisp(11) -The number of Discarded Packets of Downstream data flow from server to user in vlan. 12.rxgqpm(12) -The number of IGMP General Query Packets Received in MVLAN. 13.rxsqpm(13) -The number of IGMP Specific Query Packets Received in MVLAN. 14.rxrpv2m(14) -The number of IGMP Report Packet of Version 2 Received in MVLAN. 15.rxerpv2m(15) -The number of Error IGMP Report Packet of Version 2 Received in MVLAN. 16.rxrpv3m(16) -The number of IGMP Report Packets of Version 3 Received Per MVLAN. 17.rxerpv3m(17) -The number of Error IGMP Report Packets of Version 3 Received in MVLAN. 18.rxlpm(18) -The number of IGMP Leave Packets Received in MVLAN. 19.txgqpm(19) -The number of IGMP General Query Packets Send Out in MVLAN. 20.txsqpm(20) -The number of IGMP Specific Query Packets Send Out in MVLAN. 21.txrpv2m(21) -The number of IGMP Report Packets of Version 2 Send Out in MVLAN. 22.txerpv2m(22) -The number of IGMP Error Report Packets of Version 2 Send Out in Mvlan. 23.txlpm(23) -The number of IGMP Leave Packets Send Out in Mvlan. 24.acpm(24) -The number of IGMP Actived Programs in Mvlan. 25.acum(25) -The number of IGMP Actived Users in Mvlan. 26.rxinvpm(26) -The number of IGMP Invalid Packets Received in Mvlan. 27.rxrpv1u(27) -The number of IGMP Report Packets of Version v1 Received by user. 28.rxerpv1u(28) -The number of IGMP Error Report Packets of Version v1 Received by user. 29.rxrpv2u(29) -The number of IGMP Report Packets of Version v2 Received by user. 30.rxerv2u(30) -The number of Error IGMP Report Packets of Version v2 Received by user. 31.rxrpv3u(31) -The number of IGMP Report Packets of Version v3 Received by user. 32.rxerpv3u(32) -The number of Error IGMP Report Packets of Version v3 Received by user. 33.rxlpv2u(33) -The number of IGMP Leave Packets of Version v2 Received by user. 34.txgqpu(34) -The number of IGMP General Query Packets Send Out by user. 35.txsqpu(35) -The number of IGMP Specific Query Packets Send Out by user. 36.rxinvpu(36) -The number of IGMP Invalid Packets Received by user. 37.rxeapf(37) -The number of EAPOL Frames of any type that have been received. 38.txeapf(38) -The number of EAPOL Frames of any type that have been transmitted. 39.rxeapsf(39) -The number of EAPOL Start Frames that have been received. 40.rxeaplf(40) -The number of EAPOL Logoff frames that have been received. 41.rxeaprf(41) -The number of EAPOL Resp/Id Frames that have been received. 42.rxeappf(42) -The number of Valid EAPOL Response Frames (other than Resp/Id frames) that have been received. 43.rxieapf(43) -The number of Invalid EAPOL frames that have been received. 44.rxleeapf(44) -The number of Length Error EAPOL frames that have been received. 45.eth-crc(100) -The total number of packets received that had a length of between 64 and 1518 , but had a bad FCS. 46.eth-underpkt(101)-The total number of packets received that were less than 64 octets long and were otherwise well formed. 47.eth-overpkt(102)-The total number of packets received that were longer than 1518 octets and were otherwise well formed. 48.eth-statsfrag(103)-The total number of packets received that were less than 64 octets in length and had a bad FCS. 49.eth-stajavvers(104)-The total number of packets received that were nlonger than 1518 octets had either a bad FCS. 50.modem-initline(200)-Count of full initializations attempted on the line since agent reset. 51.modem-initfial(201)-Count of failed full initializations on the line since agent reset. 52.modem-fecs(202)-Count of seconds since agent reset that there was at least one FEC. 53.modem-es(203)-Count of seconds since agent reset that there was ATU-C and ATU-R. (ATU-C: CRC-8 >= 1 for one or more bearer channels OR LOS >= 1 OR SEF >= 1 OR LPR >= 1 ATU-R: FEBE >= 1 for one or more bearer channels OR LOS-FE >= 1 OR RDI >= 1 OR LPR-FE >= 1.) 54.modem-ses(204)-Count of seconds since agent reset that there was ATU-C and ATU-R. (ATU-C: (CRC-8 summed over all bearer channels) >= 18 OR LOS >= 1 OR SEF >= 1 OR LPR >= 1 ATU-R: (FEBE summed over all bearer channels) >= 18 OR LOS-FE >= 1 OR RDI >= 1 OR LPR-FE >= 1) 55.modem-loss(205)-Count of seconds since agent reset that there was LOS. 56.modem-uas(206) -Count of seconds in Unavailability State since agent reset. 57.modem-chcrc(207)-Count of CRC-8 anomalies occurring in the channel since agent reset. 58.modem-chfec(208)-Count of FEC anomalies occurring in the channel since agent reset. This object is not supported currently.
Status: obsolete Access: not-accessible
OBJECT-TYPE    
  INTEGER cpu(1), memory(2), rxdd(3), rxdrq(4), rxdrl(5), rxdi(6), rxuntrust(7), rxovl(8), rxovlopt(9), rxdisp(10), txdisp(11), rxgqpm(12), rxsqpm(13), rxrpv2m(14), rxerpv2m(15), rxrpv3m(16), rxerpv3m(17), rxlpm(18), txgqpm(19), txsqpm(20), txrpv2m(21), txerpv2m(22), txlpm(23), acpm(24), acum(25), rxinvpm(26), rxrpv1u(27), rxerpv1u(28), rxrpv2u(29), rxerv2u(30), rxrpv3u(31), rxerpv3u(32), rxlpv2u(33), txgqpu(34), txsqpu(35), rxinvpu(36), rxeapf(37), txeapf(38), rxeapsf(39), rxeaplf(40), rxeaprf(41), rxeappf(42), rxieapf(43), rxleeapf(44), eth-crc(100), eth-underpkt(101), eth-overpkt(102), eth-statsfrag(103), eth-stajavvers(104), modem-initline(200), modem-initfial(201), modem-fecs(202), modem-es(203), modem-ses(204), modem-loss(205), modem-uas(206), modem-chcrc(207), modem-chfec(208)  

hwDefineAid 1.3.6.1.4.1.2011.6.103.3.1.1.1.3
Index of the monitored object. This object is not supported currently.
Status: obsolete Access: not-accessible
OBJECT-TYPE    
  OCTET STRING  

hwDefineTmper 1.3.6.1.4.1.2011.6.103.3.1.1.1.4
Monitoring period. This object is not supported currently. Options: 1.fifteenMinutes(1) -monitoring period is fifteen minutes. 2.oneday(2) -monitoring period is one day.
Status: obsolete Access: not-accessible
OBJECT-TYPE    
  INTEGER fifteenMinutes(1), oneday(2)  

hwDefineThlev 1.3.6.1.4.1.2011.6.103.3.1.1.1.5
Threshold of the monitored object. This object is not supported currently.
Status: obsolete Access: read-create
OBJECT-TYPE    
  OCTET STRING Size(1..6)  

hwDefineRowStatus 1.3.6.1.4.1.2011.6.103.3.1.1.1.6
Row status. This object is not supported currently.
Status: obsolete Access: read-create
OBJECT-TYPE    
  RowStatus  

hwBatchQuery 1.3.6.1.4.1.2011.6.103.4
OBJECT IDENTIFIER    

hwBatchQueryMgmt 1.3.6.1.4.1.2011.6.103.4.1
OBJECT IDENTIFIER    

hwBQueryCapabilityTable 1.3.6.1.4.1.2011.6.103.4.1.1
The index of this table is hwBatchQueryType.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    HwBQueryCapabilityEntry

hwBQueryCapabilityEntry 1.3.6.1.4.1.2011.6.103.4.1.1.1
The index of this entry is hwBatchQueryType.
Status: current Access: not-accessible
OBJECT-TYPE    
  HwBQueryCapabilityEntry  

hwBatchQueryType 1.3.6.1.4.1.2011.6.103.4.1.1.1.1
Batch Query type. Options: 1.ontinfo(1)-ont info. 2.ontMulticastForwardingTable(2)-ont multicast forwarding table. 3.ontLearnedMac(3)-ont learned MAC. 4.macinfo(4)-MAC info.
Status: current Access: not-accessible
OBJECT-TYPE    
  Integer32  

hwBatchQueryCapability 1.3.6.1.4.1.2011.6.103.4.1.1.1.2
Indicates the batch query capability. The capability is in the TLV format. The format of the TLV is shown in the following figure. --------------------------------------------------------- | TOTAL-LENGTH | TLV-TYPE | TLV-LENGTH | TLV-VALUE | --------------------------------------------------------- | TLV-TYPE | TLV-LENGTH | TLV-VALUE | ------------------------------------------ | ................................. | |----------------------------------------- | TLV-TYPE | TLV-LENGTH | TLV-VALUE | ------------------------------------------ TOTAL-LENGTH occupies two bytes to store the whole length of all the TLV, including TOTAL-LENGTH itself. TLV-TYPE occupies two bytes to store the TLV type. TLV-LENGTH occupies two bytes to store the TLV length, which indicates the bytes TLV-VALUE occupies. TLV-VALUE is the content of the TLV. Assume that the ONT supported-capability is 00.17.00.00.00.04.00.00.00.3F.00.01.00.04.01.00.01.01.00.02.00.01.00. The capability description is as follows: ---------------------- | TLV total length | | 00.17 | ----------------------------------------------- | TLV1 type | TLV1 length | TLV1 value | | 00.00 | 00.04 | 00.00.00.3F | ----------------------------------------------- | TLV2 type | TLV2 length | TLV2 value | | 00.01 | 00.04 | 01.00.01.01 | ----------------------------------------------- | TLV3 type | TLV3 length | TLV3 value | | 00.02 | 00.01 | 00 | ----------------------------------------------- TLV total length: 00.17: the total length of the TLV is 23 Bytes. TLV1: 00.00: it is the field submask supported by the batch query. 00.04: the length of the TLV1 value is 4 Bytes. 00.00.00.3F: this value indicates that the supported fields are 0, 1, 2, 3, 4, and 5. TLV2: 00.01: it is the TLV type list supported by the batch query. 00.04: the length of the TLV2 value is 4 Bytes. 01.00.01.01: this value indicates that values 256 and 257 are supported. TLV3: 00.02: it indicates whether the batch query to be delayed. 00.01: the length of the TLV3 value is 1 Bytes. 00: it indicates that the batch query does not need to be delayed.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..256)  

hwBatchQuerySetTable 1.3.6.1.4.1.2011.6.103.4.1.2
The index of this table is hwBatchQuerySn.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    HwBatchQuerySetEntry

hwBatchQuerySetEntry 1.3.6.1.4.1.2011.6.103.4.1.2.1
The index of this entry is hwBatchQuerySn.
Status: current Access: not-accessible
OBJECT-TYPE    
  HwBatchQuerySetEntry  

hwBatchQuerySn 1.3.6.1.4.1.2011.6.103.4.1.2.1.1
Batch query SN.
Status: current Access: not-accessible
OBJECT-TYPE    
  Integer32  

hwBatchQueryCurrentType 1.3.6.1.4.1.2011.6.103.4.1.2.1.2
Current batch query type. Options: 1.ontinfo(1)-ont info. 2.ontMulticastForwardingTable(2)-ont multicast forwarding table. 3.ontLearnedMac(3)-ont learned MAC. 4.macinfo(4)-MAC info.
Status: current Access: read-write
OBJECT-TYPE    
  Integer32  

hwBatchQueryParameter 1.3.6.1.4.1.2011.6.103.4.1.2.1.3
Indicates the batch query parameter to set. The parameter is in the TLV format and supports a maximum of 255 characters. The format of the TLV is shown in the following figure. The batch query can be based on board, port, or specific fields. --------------------------------------------------------- | TOTAL-LENGTH | TLV-TYPE | TLV-LENGTH | TLV-VALUE | --------------------------------------------------------- | TLV-TYPE | TLV-LENGTH | TLV-VALUE | ------------------------------------------ | ................................. | |----------------------------------------- | TLV-TYPE | TLV-LENGTH | TLV-VALUE | ------------------------------------------ TOTAL-LENGTH occupies two bytes to store the whole length of all the TLV, including TOTAL-LENGTH itself. TLV-TYPE occupies two bytes to store the TLV type. TLV-LENGTH occupies two bytes to store the TLV length, which indicates the bytes TLV-VALUE occupies. TLV-VALUE is the content of the TLV. For example, 00.0B.01.00.00.05.00.0C.02.00.02 indicates querying the multicast forwarding entries for ONT 2 based on subrack ID/slot ID/port ID 0/12/2. The parameter description is as follows: ---------------------- | TLV total length | | 00.0B | -------------------------------------------------- | TLV1 type | TLV1 length | TLV1 value | | 01.00 | 00.05 | 00.0C.02.00.02 | -------------------------------------------------- TLV total length: 00.0B: the total length of the TLV is 11 Bytes. TLV1: 01.00: indicates a query based on ONT. 00.05: the length of the TLV1 value is 5 Bytes 00.0C.02.00.02: indicates a query on the ONT 2 connected to port 0/12/2.
Status: current Access: read-write
OBJECT-TYPE    
  OCTET STRING Size(1..256)  

hwBatchQueryRowStatus 1.3.6.1.4.1.2011.6.103.4.1.2.1.4
Row operation object. createAndGo(4)is supplied to create a new instance of a conceptual row. destroy(6)is supplied to delete the instances associated with an existing conceptual row..
Status: current Access: read-create
OBJECT-TYPE    
  RowStatus  

hwBatchQueryGetTable 1.3.6.1.4.1.2011.6.103.4.1.3
The indexes of this table are hwBatchQuerySn and hwBatchQueryStartNo.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    HwBatchQueryGetEntry

hwBatchQueryGetEntry 1.3.6.1.4.1.2011.6.103.4.1.3.1
The indexes of this entry are hwBatchQuerySn and hwBatchQueryStartNo.
Status: current Access: not-accessible
OBJECT-TYPE    
  HwBatchQueryGetEntry  

hwBatchQueryStartNo 1.3.6.1.4.1.2011.6.103.4.1.3.1.1
Batch query Start NO.
Status: current Access: not-accessible
OBJECT-TYPE    
  Integer32  

hwBatchQueryReturnNum 1.3.6.1.4.1.2011.6.103.4.1.3.1.2
Batch query return number .
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

hwBatchQueryReturnList 1.3.6.1.4.1.2011.6.103.4.1.3.1.3
List of batch query result.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING  

hwBatchQueryIsLast 1.3.6.1.4.1.2011.6.103.4.1.3.1.4
The result of batch query is the last one or not. Options: 1.islast(1)-last. 2.notlast(2)-not last.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER islast(1), notlast(2)  

hwBatchQueryTrapVbOids 1.3.6.1.4.1.2011.6.103.4.2
OBJECT IDENTIFIER    

hwBatchQueryResult 1.3.6.1.4.1.2011.6.103.4.2.1
The result of batch query.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32  

hwBatchQueryTraps 1.3.6.1.4.1.2011.6.103.4.3
OBJECT IDENTIFIER    

hwBatchQueryCommonTraps 1.3.6.1.4.1.2011.6.103.4.3.1
OBJECT IDENTIFIER    

hwBatchQueryCommonTrapsPrefix 1.3.6.1.4.1.2011.6.103.4.3.1.0
OBJECT IDENTIFIER    

hwBatchQueryResultTrap 1.3.6.1.4.1.2011.6.103.4.3.1.0.1
This trap message is reported when the batch query is complete.
Status: current Access: accessible-for-notify
NOTIFICATION-TYPE    

hwCollectSet 1.3.6.1.4.1.2011.6.121.1
OBJECT IDENTIFIER    

hwCollectSetTable 1.3.6.1.4.1.2011.6.121.1.1
NMS collect information table, providing add/modify/delete operations. The host severs as client, while the NMS as server. The index of this table is hwCollectTableName.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    HwCollectSetEntry

hwCollectSetEntry 1.3.6.1.4.1.2011.6.121.1.1.1
NMS collect information table, providing add/modify/delete operations. The host severs as client, while the NMS as server. The index of this entry is hwCollectTableName.
Status: current Access: not-accessible
OBJECT-TYPE    
  HwCollectSetEntry  

hwCollectTableName 1.3.6.1.4.1.2011.6.121.1.1.1.1
The table name. It is in the format of ASCII code separated by '.'. If the table name is specified to a|b, the index is 97.124.98. Naming standard: In a table name, there should be one vertical line at most, and the left side and right side of the vertical line cannot be null. For example, identifier|table name or table name. The ASCII codes must be from 0x21 to 0x7E. In the configuration phase, when a table name requires to be added, format identifier|all or all cannot be used.
Status: current Access: not-accessible
OBJECT-TYPE    
  OCTET STRING Size(1..63)  

hwCollectOID 1.3.6.1.4.1.2011.6.121.1.1.1.2
Information of the OIDs. When the NMS adds the information about the entries, the value of the information in the format of 'parent object OID:OID of sub object 1, OID of sub object 2......'. This format is called entry object character string hereinafter. The MIB object of the entry OID can be only the OID of the entry object. For the scalar object, the OID of the parent object is directly used. For example, to collect statistics of the objects 1.3.6.1.4.1.2011.6.3.4.1.3, 1.3.6.1.4.1.2011.6.3.4.1.4, and 1.3.6.1.4.1.2011.6.3.4.1.1.5 in hwCpuDevTable, you need to enter the objects in the format of '1.3.6.1.4.1.2011.6.3.4.1:3,4,5'.
Status: current Access: read-write
OBJECT-TYPE    
  OCTET STRING Size(0..128)  

hwCollectTableRowStatus 1.3.6.1.4.1.2011.6.121.1.1.1.3
Row status. createAndGo(4) is supplied to create a new instance of a conceptual row. destroy(6) is supplied to delete the instances associated with an existing conceptual row.
Status: current Access: read-create
OBJECT-TYPE    
  RowStatus  

hwCollectOperationSet 1.3.6.1.4.1.2011.6.121.2
OBJECT IDENTIFIER    

hwCollectState 1.3.6.1.4.1.2011.6.121.2.1
Operation status of the information collection. Options: 1.idle(1) -indicates that the operation is in the idle state. 2.collecting(2) -indicates that the information is being collected. 3.waitfetch(3) -indicates that the information collection is complete and the data is to be extracted. 4.tranfering(4) -indicates that the file is being transferred.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER idle(1), collecting(2), waitfetch(3), tranfering(4)  

hwCollectOperation 1.3.6.1.4.1.2011.6.121.2.2
Administration operation of the information collection. Options: 1.begin(1) -indicates that the information collection starts. 2.stop(2) -indicates that the information collection stops. 3.processing(3)-indicates that the collection is ongoing. In the begin and stop operations, the object hwCollectTableInfo needs to be bound.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER begin(1), stop(2), processing(3)  

hwCollectTableInfo 1.3.6.1.4.1.2011.6.121.2.3
Information of the table. This object is used for informing the host of the name of the entry that needs to be collected before the collection is started. If there are multiple entries, a comma is used to separate them. For example, if the NMS has already configured three tables of entries, namely, a|b, a|c, and a|d, this parameter can be set to a|b,a|c before the information collection is started. It indicates that information in a|b and a|c needs to be collected. If you want to collect the information about all tables carrying a certain flag, configure to flag|all (flag is an identifier) and the information about all required tables can be collected. For example, when you have tables a|b, a|c, and a|d (a is an identifier; b, c, and d are table names) and configure a|all, the information about the three tables can be collected. when the value of hwCollectTableInfo is the collection of many table names that are split by commas, you are not allowed to name a single table with all or Flag|all (Flag stands for any letter of an ASCII code from 0x21 to 0x7E); when the value of hwCollectTableInfo is a single table name, you can name the table with all or Flag|all. (Flag stands for any letter of an ASCII code from 0x21 to 0x7E).
Status: current Access: read-write
OBJECT-TYPE    
  OCTET STRING Size(0..510)  

hwBackupCollect 1.3.6.1.4.1.2011.6.121.3
OBJECT IDENTIFIER    

hwBackupCollectInfoParaTable 1.3.6.1.4.1.2011.6.121.3.1
Backup collectinfo parameter table. This object is not supported currently. The index of this table is hwBackupCollectInfoRequestID.
Status: obsolete Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    HwBackupCollectInfoParaEntry

hwBackupCollectInfoParaEntry 1.3.6.1.4.1.2011.6.121.3.1.1
Backup collectinfo parameter table. This object is not supported currently. The index of this entry is hwBackupCollectInfoRequestID.
Status: obsolete Access: not-accessible
OBJECT-TYPE    
  HwBackupCollectInfoParaEntry  

hwBackupCollectInfoServerIpAddr 1.3.6.1.4.1.2011.6.121.3.1.1.1
The IP address of server. This object is not supported currently.
Status: obsolete Access: read-write
OBJECT-TYPE    
  IpAddress  

hwBackupCollectInfoMode 1.3.6.1.4.1.2011.6.121.3.1.1.2
Load protocol:tftp and MODEM currently supported. Options: 1.tftp(1) -indicates load protocol is tftp. 2.modem(2)-indicates load protocol is modem. 3.ftp(3) -indicates load protocol is ftp. 4.sftp(5) -indicates load protocol is sftp. 5.other(6)-indicates load protocol is other type.
Status: obsolete Access: read-write
OBJECT-TYPE    
  INTEGER tftp(1), modem(2), ftp(3), sftp(5), other(6)  

hwBackupCollectInfoFileName 1.3.6.1.4.1.2011.6.121.3.1.1.3
Backup file name.
Status: obsolete Access: read-write
OBJECT-TYPE    
  OCTET STRING Size(1..127)  

hwBackupCollectInfoUserName 1.3.6.1.4.1.2011.6.121.3.1.1.4
The backup user name,which is necessary in FTP mode and SFTP mode while unnecessary in TFTP mode. This object is not supported currently.
Status: obsolete Access: read-write
OBJECT-TYPE    
  OCTET STRING Size(1..31)  

hwBackupCollectInfoPassword 1.3.6.1.4.1.2011.6.121.3.1.1.5
The backup user password, which is necessary in FTP mode and SFTP mode, while unnecessary in TFTP mode. This object is not supported currently.
Status: obsolete Access: read-write
OBJECT-TYPE    
  OCTET STRING Size(1..16)  

hwBackupCollectInfoRequestID 1.3.6.1.4.1.2011.6.121.3.1.1.6
The request index for xml. This object is not supported currently.
Status: obsolete Access: read-write
OBJECT-TYPE    
  Integer32  

hwCfgInfoQuery 1.3.6.1.4.1.2011.6.121.4
OBJECT IDENTIFIER    

hwCfgInfoQueryTable 1.3.6.1.4.1.2011.6.121.4.1
This table is used for querying information in real time. The indexes of this table are hwQueryCondition and hwQueryContent. When the table is issued, the length of the hwQueryCondition needs to be specified, and hwQueryCondition and hwQueryContent need to be converted into ASCII codes for issuing. For example, if you need to issue conditions for querying the ID and name of the alarm whose type is device and severity is critical, the issued hwQueryCondition is 1.3.6.1.4.1.2011.6.30.7.1.1.6=4, 1.3.6.1.4.1.2011.6.30.6.1.1.4=2, which can be converted into the ASCII code 49.46.51.46.54.46.49.46.52.46.49.46.50.48.49.49.46.54.46.51.48.46.55. 46.49.46.49.46.54.61.52.44.49.46.51.46.54.46.49.46.52.46.49.46.50.48.49.49. 46.54.46.51.48.46.54.46.49.46.49.46.52.61.50; the issued hwQueryContent is abc=1.3.6.1.4.1.2011.6.30.7.1.1:1,2, which can be converted into the ASCII code 97.98.99.61.49.46.51.46.54.46. 49.46.52.46.49.46.50.48.49.49.46.54.46.51.48.46.55.46.49.46.49.58.49.44.50. With the length of the hwQueryCondition, the finally issued index is 63.49.46.51.46.54.46.49.46.52.46.49.46.50.48.49.49.46.54.46.51.48.46.55.46. 49.46.49.46.54.61.52.44.49.46.51.46.54.46.49.46.52.46.49.46.50.48.49.49.46. 54.46.51.48.46.54.46.49.46.49.46.52.61.50.97.98.99.61.49.46.51.46.54.46.49.46.52.46. 49.46.50.48.49.49.46.54.46.51.48.46.55.46.49.46.49.58.49.44.50.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    HwCfgInfoQueryEntry

hwCfgInfoQueryEntry 1.3.6.1.4.1.2011.6.121.4.1.1
This table is used for querying information in real time. The indexes of this entry are hwQueryCondition and hwQueryContent. When the table is issued, the length of the hwQueryCondition needs to be specified, and hwQueryCondition and hwQueryContent need to be converted into ASCII codes for issuing. For example, if you need to issue conditions for querying the ID and name of the alarm whose type is device and severity is critical, the issued hwQueryCondition is 1.3.6.1.4.1.2011.6.30.7.1.1.6=4, 1.3.6.1.4.1.2011.6.30.6.1.1.4=2, which can be converted into the ASCII code 49.46.51.46.54.46.49.46.52.46.49.46.50.48.49.49.46.54.46.51.48.46.55. 46.49.46.49.46.54.61.52.44.49.46.51.46.54.46.49.46.52.46.49.46.50.48.49.49. 46.54.46.51.48.46.54.46.49.46.49.46.52.61.50; the issued hwQueryContent is abc=1.3.6.1.4.1.2011.6.30.7.1.1:1,2, which can be converted into the ASCII code 97.98.99.61.49.46.51.46.54.46. 49.46.52.46.49.46.50.48.49.49.46.54.46.51.48.46.55.46.49.46.49.58.49.44.50. With the length of the hwQueryCondition, the finally issued index is 63.49.46.51.46.54.46.49.46.52.46.49.46.50.48.49.49.46.54.46.51.48.46.55.46. 49.46.49.46.54.61.52.44.49.46.51.46.54.46.49.46.52.46.49.46.50.48.49.49.46. 54.46.51.48.46.54.46.49.46.49.46.52.61.50.97.98.99.61.49.46.51.46.54.46.49.46.52.46. 49.46.50.48.49.49.46.54.46.51.48.46.55.46.49.46.49.58.49.44.50.
Status: current Access: not-accessible
OBJECT-TYPE    
  HwCfgInfoQueryEntry  

hwQueryCondition 1.3.6.1.4.1.2011.6.121.4.1.1.1
Condition index string. The value is in the format of 'OID1=......, OID2=......'.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..256)  

hwQueryContent 1.3.6.1.4.1.2011.6.121.4.1.1.2
Query content. The format is 'name of entry 1 = OID of entry 1:OID number of sub object 1, OID number of sub object 2...... + name of entry 2 = OID of entry 2:number of sub object 1, number of sub object 2......'.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..256)  

hwQueryResult 1.3.6.1.4.1.2011.6.121.4.1.1.3
Query result.
Status: current Access: read-only
OBJECT-TYPE    
  OCTET STRING Size(1..8192)  

hwCollectTrapVbOids 1.3.6.1.4.1.2011.6.121.5
OBJECT IDENTIFIER    

hwCollectFileResult 1.3.6.1.4.1.2011.6.121.5.1
Result of file Collection. If the result is 1, it indicates that the configuration file is generated successfully. If the result is 2, it indicates that the generation of the configuration file fails.
Status: current Access: accessible-for-notify
OBJECT-TYPE    
  Integer32  

hwCollectTraps 1.3.6.1.4.1.2011.6.121.6
OBJECT IDENTIFIER    

hwCollectAlarmTraps 1.3.6.1.4.1.2011.6.121.6.1
OBJECT IDENTIFIER    

hwCollectCommonTraps 1.3.6.1.4.1.2011.6.121.6.2
OBJECT IDENTIFIER    

hwCollectCommonTrapsPrefix 1.3.6.1.4.1.2011.6.121.6.2.0
OBJECT IDENTIFIER    

hwCollectFileResultTrap 1.3.6.1.4.1.2011.6.121.6.2.0.1
This trap message is reported when the configuration information is collected.
Status: current Access: accessible-for-notify
NOTIFICATION-TYPE    

Generation date: July 28, 2023, 16:18:13, Copyright © 2007 - 2022 - Circitor