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

FusionAccess 6.5 Alarm Handling 04

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).
1007006 Iptables Connection Tracking Usage of Server Exceeds the Threshold

1007006 Iptables Connection Tracking Usage of Server Exceeds the Threshold

Description

After startup, the alarm module checks the iptables trace usage every two minutes. This alarm is generated when the alarm module detects that the iptables trace usage exceeds the threshold (80% by default) for three consecutive times. This alarm is cleared when the alarm module detects that the usage is lower than the threshold.

Attribute

Alarm ID

Alarm Severity

Auto Clear

1007006

Critical

Yes

Parameters

Name

Meaning

Alarm ID

Identifies an alarm. Each alarm is uniquely identified by an alarm ID and an alarm name.

Alarm Severity

Indicates the severity of an alarm. Value:

  • Critical: indicates that a fault affecting services provided by the system occurs. You need to rectify the fault immediately. If a device or resource is faulty, rectify it immediately even if the fault occurs during non-working hours.
  • Major: indicates that a fault affecting the service quality of the system occurs. You need to rectify the fault immediately. If the service quality of a device or resource is degraded, rectify it immediately during working hours.
  • Minor: indicates a fault that does not affect service quality. To prevent more serious faults, this type of alarm needs to be observed or handled if necessary.
  • Warning: indicates a fault that may affect service quality. This type of alarm must be handled based on the error type.

Alarm Name

Identifies an alarm. Each alarm is uniquely identified by an alarm ID and an alarm name.

Object Type

Specifies the type of the object for which the alarm is generated.

Alarm Object Name

Specifies the name of the object for which the alarm is generated.

Generation Time

Specifies the time when the alarm is generated.

Clear Time

Specifies the time when the alarm is cleared.

Clear Mode

Specifies whether the alarm is manually or automatically cleared.

Operation

Specifies the operation that can be performed on the alarm.

Value: Manually Clear Alarm

Impact on the System

After the number of iptables connection tracing records reaches the upper limit of the OS, the server cannot respond to new connection requests.

Possible Causes

  • The server is overloaded for a short period of time.
  • There are a large number of abnormal connection tracing records that are not aged normally.

Procedure

  1. Check whether the number of abnormal connection tracing records in the alarm details is greater than 20,000.

    • If yes, go to 3.
    • If no, go to 2.

  2. Choose FusionAccess > Alarm to check whether the alarm still exists.

    • If yes, go to 3.
    • If no, no further action is required.

  3. Log in to the server as user root and run the reboot command to restart the server without affecting services.
  4. Wait for about 10 minutes. Choose FusionAccess > Alarm to check whether the alarm still exists.

    • If yes, contact technical support.
    • If no, no further action is required.

Related Information

None

Translation
Download
Updated: 2019-10-11

Document ID: EDOC1100061083

Views: 5618

Downloads: 16

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