HUAWEI-BULKSTATISTICS-MIB Table View

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 nodes 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.

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.

Indicates the statistical condition table, on which users can add, delete, 
or modify statistical conditions. Before adding a statistical condition, 
use hwBulkFileTable to configure a statistical task. To delete a statistical condition, 
use hwBulkFileCollectRowStatus. Before deleting a statistical task, use hwBulkFileConditionTable 
to delete corresponding statistical conditions. To modify an existing statistical condition, modify 
the value of the hwBulkFileCollectCondition field.Statistical conditions can be issued in hexadecimal notation or using a character string.
The index of this table is hwBulkFileObjectMainType, hwBulkFileObjectSubType and hwBulkFileCollectInterval.

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.

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.

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.

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.

TCA Management Table. This object is not supported currently.
The indexes of this table are hwDefineFacilityType, hwDefineMontype, hwDefineAid and hwDefineTmper.

The index of this table is hwBatchQueryType.

The index of this table is hwBatchQuerySn.

The indexes of this table are hwBatchQuerySn and hwBatchQueryStartNo.

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.

Backup collectinfo parameter table. This object is not supported currently.
The index of this table is hwBackupCollectInfoRequestID.

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.