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 V200R010C00

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).
FIB_1.3.6.1.4.1.2011.5.25.129.2.9.3 hwFIBOverloadForward

FIB_1.3.6.1.4.1.2011.5.25.129.2.9.3 hwFIBOverloadForward

Description

FIB/1/OVLDFORWARD/0x40012002 T/R "OID [oid] The interface board is in the overload forwarding state because the FIB module is overloaded. (EntityPhysicalIndex=[INTEGER], HwBaseTrapSeverity=[INTEGER], HwBaseTrapProbableCause=[INTEGER], HwBaseTrapEventType=[INTEGER], HwFibOverloadModule=[INTEGER], entPhysicalName=[STRING])"

The trap was generated when the number of IPv4/IPv6 FIB route prefixes on the interface board exceeds the upper threshold. You can run the display fib slot-id statistics all and display ipv6 fib slot-id statistics all commands to view the specific number of FIB route prefixes. The number of route prefixes varied with the type of the interface board. When the interface board was in overload forwarding state, it no longer received FIB route prefixes from the main control board. Instead, it used the existing IPv4/IPv6 FIB route prefixes to forward packets.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.129.2.9.3

Critical

processingErrorAlarm(4)

Parameters

Name Meaning
oid Indicates the MIB object ID of the alarm.
EntityPhysicalIndex Indicates the index of the entity.
HwBaseTrapSeverity Indicates the alarm severity.
HwBaseTrapProbableCause Indicates possible causes.
HwBaseTrapEventType Indicates the alarm type.
HwFibOverloadModule Indicates overloaded modules:
  • 1: IPv4 module
  • 2: IPv6 module
entPhysicalName Indicates the name of the entity.

Impact on the System

The interface board no longer receives new FIB route prefixes but forwards packets according to the existing FIB route prefixes.

Possible Causes

The number of IPv4/IPv6 FIB route prefixes on the interface board exceeds the upper threshold. You can run the display fib slot-id statistics all and display ipv6 fib slot-id statistics all commands to view the specific number of FIB route prefixes. The number of FIB route prefixes varied with the type of the interface board.

Procedure

  1. Run the display fib overload state slot command to check whether the number of IPv4 routes on the interface board exceeds the threshold.

    • If so, go to Step 3.
    • If not, go to Step 2.

  2. Run the display ipv6 fib overload state slot command to check whether the number of IPv6 routes on the interface board exceeds the threshold.

    • If so, go to Step 8.
    • If not, go to Step 13.

  3. Run the display fib slot-id statistics all command to view the capacity of IPv4 FIB route prefixes on the interface board. Then, run the display fib statistics all command and determine whether the number of IPv4 FIB route prefixes on the main control board equals or exceeds the capacity of IPv4 FIB route prefixes on the interface board.

    • If so, go to Step 4.
    • If not, go to Step 5.

  4. Run the apply fib-policy command in the system view to configure the IPv4 FIB policy on the interface board.
  5. Run the recover fib overload forward command in the system view to recover the interface board from the overload forwarding state.
  6. Run the refresh fib command in the system view to refresh IPv4 FIB entries.

    NOTE:
    After this command is used, the interface board refreshes routes according to the IPv4 FIB policy configured through the apply fib-policy command. As a result, routes that do not comply with the policy are deleted.

  7. Run the display fib overload state command to check whether the current IPv4 FIB module on the interface board works normally.

    • If so, go to Step 14.
    • If not, go to Step 13.

  8. Run the display ipv6 fib slot-id statistics all command to view the capacity of IPv6 FIB route prefixes on the interface board. Then, run the display ipv6 fib command and determine whether the number of IPv6 FIB route prefixes on the main control board equals or exceeds the capacity of IPv6 FIB route prefixes on the interface board.

    • If so, go to Step 9.
    • If not, go to Step 10.

  9. Run the apply ipv6 fib-policy command in the system view to configure the IPv6 FIB policy on the interface board.
  10. Run the recover ipv6 fib overload forward command in the system view to recover the interface board from the overload suspension state.
  11. Run the refresh ipv6 fib command in the system view to refresh IPv6 FIB entries.

    NOTE:
    After this command is used, the interface board refreshes routes according to the IPv6 FIB policy configured through the apply ipv6 fib-policy command. As a result, routes that do not comply with the policy are deleted.

  12. Run the display ipv6 fib overload state command to check whether the current IPv6 FIB module on the interface board works normally.

    • If so, go to Step 14.
    • If not, go to Step 13.

  13. Collect alarm information and configuration information, and then contact technical support personnel.
  14. End.
Translation
Download
Updated: 2019-08-21

Document ID: EDOC1000142054

Views: 181612

Downloads: 44

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