No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Alarm Handling

S9300, S9300E, and S9300X V200R013C00

This document provides the explanations, causes, and recommended actions of alarms on the product.
Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
BULKSTAT

BULKSTAT

BULKSTAT_1.3.6.1.4.1.2011.5.25.140.2.1 hwBulkStatCollectIncomplete

Description

BULKSTAT/3/COLLECT_INCOMPLETE:OID [oid] The file collection is incomplete during the collection period. (FileIndex=[integer], FileName=[octet])

Collecting statistics on all statistics objects was not complete within a collection interval. The data collection in the last collection interval is complete. If the collection interval is the first one, the trap is directly generated.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.140.2.1 Minor processingErrorAlarm(4)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

FileIndex

indicates the index of a file.

filename

indicates the name of a file.

Impact on the System

Data collected in a collection cycle is incomplete, and thus the FTP server loses the data in an uploading cycle.

Possible Causes

1:

The CPU usage of the system was high.

2:

The number of sampling objects that were configured was beyond the sampling capability of the system.

Procedure

  1. Run the display bulk-stat command to check the maximum number of data items to be collected per 5 minutes.
  2. The number of data items to be collected per 5 minutes is obtained through the weighted calculation.

    The weighted calculation formula is as follows:
    1. Number of data items collected per 5 minutes = Number of data items to be collected in file 1 + Number of data items to be collected in file 2 + ... + Number of data items to be collected in file n.

    2. Number of data items to be collected in file N = ( Number of data items to be collected in single class + Number of data items to be collected in column class 1 × number of instances in column class 1 + Number of data items to be collected in column class 2 × number of instances in column class 2 + ... + Number of data items to be collected in column class n × number of instances in column class n) ÷ (Collection interval in minute ÷ 5).

    3. Run the display bulk-stat [ file-name ] to check the collection interval.

  3. Check whether the currently configured number of data items to be collected per 5 minutes is more than the maximum data items to be collected per 5 minutes.

    • If so, go to Step 5.

    • If not, go to Step 4.

  4. Run the display cpu-usage command to check the current CPU usage. If the CPU usage is more than 70%, wait for the automatic system reset.

    • If so, go to Step 5.

    • If not, go to Step 6.

  5. Run the undo object command to delete some data items, and ensure that the currently configured number of data items collected per 5 minutes is less than the maximum data items collected per 5 minutes. Observe a whole collection interval to find whether the trap indicating the automatic system reset is received.

    • If so, go to Step 7.

    • If not, go to Step 6.

  6. Collect alarm information and configuration information, and then contact technical support personnel.
  7. End.

BULKSTAT_1.3.6.1.4.1.2011.5.25.140.2.2 hwBulkStatCollectResume

Description

BULKSTAT/3/COLLECT_RESUME:OID [oid] The file collection resumed itself to normal during next collection period. (FileIndex=[integer], FileName=[octet])

Collecting statistics on all statistics objects is complete during this collection period. The data collection in the last collection interval is not complete.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.140.2.2 Minor processingErrorAlarm(4)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

FileIndex

Indicates the index of a file.

filename

Indicates the name of a file.

Impact on the System

The data collection is from incomplete to complete. The system will not be affected.

Possible Causes

1:

The CPU usage was restored to a normal level.

2:

The user reduced the number of sampling objects within the capability of the system.

Procedure

  1. This trap message is informational only, and no action is required.

BULKSTAT_1.3.6.1.4.1.2011.5.25.140.2.3 hwBulkStatURLConnectionFail

Description

BULKSTAT/2/CONNECTION_FAILED:OID [oid] Failed to upload the URL. (FileIndex=[integer], FileName=[octet],PrimaryUrl=[octet], SecondaryUrl=[octet])

Uploading files through FTP failed after using both the primary and secondary URLs. The trap cannot be resent. No trap is sent when the upload fails again.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.140.2.3 Major processingErrorAlarm(4)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

FileIndex

Indicates the index of a file.

filename

Indicates the name of a file.

PrimaryUrl

Indicates the primary URL.

SecondaryUrl

Indicates the secondary URL.

Impact on the System

The data collected in this uploading interval needs to be retransmitted, and the system will not be affected.

Possible Causes

1:

The configured primary transfer URL and secondary transfer URL were incorrect.

2:

The configuration of the FTP/TFTP server was incorrect.

3:

The link connecting the local device to the file server was faulty.

Procedure

  1. Run the display bulk-stat [ filename ] command to check whether the primary URL and secondary URL are correctly configured.

    • If so, go to Step 2.

    • If not, go to Step 4.

  2. Check whether the user name of the FTP/TFTP and the password of FTP is correctly configured. In addition, check whether the server can be started normally.

    • If so, go to Step 3.

    • If not, go to Step 4.

  3. Run the ping command to check whether the link is in the normal state.

    • If so, go to Step 5.

    • If not, go to Step 4.

  4. Re-configure the upload link or the server. Observe a whole collection interval to find whether the trap indicating the link recovery is received.

    • If so, go to Step 6.

    • If not, go to Step 5.

  5. Collect alarm information and configuration information, and then contact technical support personnel.
  6. End.

BULKSTAT_1.3.6.1.4.1.2011.5.25.140.2.4 hwBulkStatURLConnectionResume

Description

BULKSTAT/2/CONNECTION_RESUME:OID [oid] Succeeded in uploading the URL. (FileIndex=[integer], FileName=[octet], PrimaryUrl=[octet], SecondaryUrl=[octet])

Uploading collected files through FTP failed after using both the primary and secondary URLs. Uploading collected files through FTP succeeded after using either the primary or secondary URL.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.140.2.4 Major processingErrorAlarm(4)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

FileIndex

Indicates the index of a file.

filename

Indicates the name of a file.

PrimaryUrl

Indicates the primary URL.

SecondaryUrl

Indicates the secondary URL.

Impact on the System

The link is recovered. The system will not be affected.

Possible Causes

1:

The user corrected the configurations of the primary transfer URL and secondary transfer URL.

2:

The user corrected the configuration of the FTP/TFTP server.

3:

The link connecting the local device to the file server was faulty.

Procedure

  1. This trap message is informational only, and no action is required.

BULKSTAT_1.3.6.1.4.1.2011.5.25.140.2.5 hwBulkStatTransferFileDiscard

Description

BULKSTAT/4/FILE_DISCARD:OID [oid] The file was discarded because of transfer failure. (FileIndex=[integer], FileName=[octet], LastTransferFailTime=[integer])

The file is not uploaded when the saving period for the statistics file is over. The device stops the upload, deletes the compressed file in the memory, and sends this trap. The trap has no corresponding recovery trap because the file cannot be restored after being deleted.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.140.2.5 Warning processingErrorAlarm(4)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

FileIndex

Indicates the index of a file.

filename

Indicates the name of a file.

LastTransferFailTime

Indicates the last data-collecting moment in the last failed upload.

Impact on the System

The data of an upload interval is lost on the BULK FTP host server.

Possible Causes

Failed to upload the file.

Procedure

  1. Check whether the hwBulkStatURLConnectionFail alarm is received.

    • If so, go to Step 2.

    • If not, go to Step 3.

  2. Clear the alarm based on the hwBulkStatURLConnectionFail alarm handling suggestion. Go to Step 5.
  3. Increase the bandwidth of the upload link, or run the undo object command to simplify the configuration and reduce the size of the uploaded file. Then check whether the trap is recovered.

    • If so, go to Step 5.

    • If not, go to Step 4.

  4. Collect alarm information and configuration information, and then contact technical support personnel.
  5. End.

Related Information

None

Translation
Download
Updated: 2019-04-09

Document ID: EDOC1100065855

Views: 3468

Downloads: 2

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next