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).
RM

RM

RM_1.3.6.1.4.1.2011.5.25.145.6.1 hwTunnelGroupUp

Description

RM/2/TNLGROUP_UP:OID [oid] The status of the tunnel group changed to Up. (Destionation=[IPADDR], TunnelPolicy=[STRING])

The status of the tunnel group used by the service changed to Up.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.145.6.1

Major

qualityOfServiceAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

Destionation

Destination IP address of the tunnel on which services depend.

TunnelPolicy

Tunnel policy used by services.

Impact on the System

Services are restored.

Possible Causes

1:

The link fault was rectified, and the tunnel became available.

2:

A TE, LDP, or GRE tunnel was configured, causing the tunnel to a specified destination to be unavailable.

3:

The VPN route iterated to the public tunnel was added again after being withdrawn.

Procedure

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

RM_1.3.6.1.4.1.2011.5.25.145.6.2 hwTunnelGroupDown

Description

RM/2/TNLGROUP_DOWN:OID [oid] The status of the tunnel group changed to Down. (Destionation=[IPADDR], TunnelPolicy=[STRING])

The status of the tunnel group used by the service changed to Down.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.145.6.2

Major

qualityOfServiceAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

Destionation

Destination IP address of the tunnel on which services depend.

TunnelPolicy

Tunnel policy used by services.

Impact on the System

Services may be interrupted.

Possible Causes

1:

A link fault occurred.

2:

The configuration was changed, causing no available tunnel to the specified destination.

3:

The VPN routes iterated to public network tunnels are deleted.

Procedure

  1. After a tunnel group fails, the device sends an alarm with information about the destination address and tunnel policy to inform users of the tunnel group failure. You can run the display this command in the tunnel policy view to check whether tunnel-policy tunnel-policy-name is displayed.

    • If tunnel-policy tunnel-policy-name is displayed, run the display tunnel-policy tunnel-policy-name command to check the tunnel policy.
      • If Select-Seq is displayed, the sequence tunnel policy is used. Then, go to Step 2.
      • If Destination and Tunnel Intf are displayed, the binding tunnel policy is used. Then, go to Step 3.
    • If tunnel-policy tunnel-policy-name is not displayed, go to Step 4.

  2. Run the display tunnel-info all command to check whether there are tunnels of the type configured in the tunnel policy.

    • If there are tunnels of the type configured in the tunnel policy, go to Step 5.
    • If there is no tunnel of the type configured in the tunnel policy, change the tunnel policy used by VPN services.

  3. If a binding tunnel policy is used, run the display interface tunnel interface-number command to check whether the bound tunnel interface is Up.

    • If the bound tunnel interface is Up, go to Step 5.
    • If the bound tunnel interface is not Up, configure the TE interface.

  4. Check where there is an LSP.

    • If there is an LSP, go to Step 5.
    • If there is no LSP (LDP LSP, BGP LSP, or static LSP), check the LSP configuration.

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

RM_1.3.6.1.4.1.2011.5.25.145.10.1 hwIpv4PrefixExceed

Description

RM/2/IPV4_PREFIX_EXCEED:OID [oid] The number of IPv4 prefixes exceeded the maximum value. (PrefixCount=[Integer], MaxValue=[Integer])

The number of IPv4 route prefixes exceeded that supported by the device.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.145.10.1

Major

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

PrefixCount

Indicates the number of IPv4 route prefixes in the routing table.

MaxValue

Indicates the maximum number of IPv4 route prefixes supported by the device.

Impact on the System

New IPv4 route prefixes cannot be added to the routing table. Services will be affected if the number of IPv4 route prefixes keeps increasing.

Possible Causes

A large number of IPv4 dynamic protocol routes (BGP or IGP routes for example), static routes, or direct routes were added to the routing table.

Procedure

  1. Run the display ip routing-table statistics and display ip routing-table all-vpn-instance statistics commands to check the numbers of IPv4 public and private route prefixes and the number of routes of each protocol that are added to the routing table.

    Check whether services need these routes or whether the routes are added to the routing table due to incorrect configurations.
    • If the routes are added to the routing table due to incorrect configurations, go to 2.

    • If services need these routes, replace the license or contact technical support personnel for specification expansion.

  2. Adjust the configurations to delete unneeded routes, and check whether the RM_1.3.6.1.4.1.2011.5.25.145.10.2 hwIpv4PrefixExceedClear alarm is generated.

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

RM_1.3.6.1.4.1.2011.5.25.145.10.2 hwIpv4PrefixExceedClear

Description

RM/2/IPV4_PREFIX_EXCEED_RESM:OID [oid] The number of IPv4 prefixes falls below the maximum value. (PrefixCount=[Integer], MaxValue=[Integer])

The total number of IPv4 route prefixes fell below that supported by the system.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.145.10.2

Major

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

PrefixCount

Indicates the number of IPv4 route prefixes in the routing table.

MaxValue

Indicates the maximum number of IPv4 route prefixes supported by the device.

Impact on the System

Services will not be affected.

Possible Causes

The network administrator deleted some routes from the routing table or the number of routes learned by dynamic protocols decreased due to network topology changes.

Procedure

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

RM_1.3.6.1.4.1.2011.5.25.145.10.3 hwIpv4PrefixThresholdExceed

Description

RM/4/IPV4_PREFIX_THRESHOLD_EXCEED:OID [oid] The number of IPv4 prefixes exceeded the threshold. (PrefixCount=[Integer], MaxValue=[Integer])

The number of IPv4 route prefixes exceeded the alarm threshold.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.145.10.3

Warning

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

PrefixCount

Indicates the number of IPv4 route prefixes in the routing table.

MaxValue

Indicates the maximum number of IPv4 route prefixes supported by the device.

Impact on the System

The number of IPv4 route prefixes exceeded the alarm threshold, and services may be affected if the number of IPv4 route prefixes keeps increasing.

Possible Causes

A large number of IPv4 dynamic protocol routes (BGP or IGP routes for example), static routes, or direct routes were added to the routing table.

Procedure

  1. Run the display current-configuration command to check whether the threshold value specified in the ip prefix-limit system threshold-alarm command is too small.

    • If the threshold value is too small, go to 2.
    • If the threshold value is in a proper range, go to 3.

  2. Rerun the ip prefix-limit system threshold-alarm upper-limit upper-limit-value lower-limit lower-limit-value command to increase the value of upper-limit-value.
  3. Run the display ip routing-table statistics and display ip routing-table all-vpn-instance statistics commands to check the numbers of IPv4 public and private route prefixes and the number of routes of each protocol that are added to the routing table.

    Check whether services need these routes or whether the routes are added to the routing table due to incorrect configurations.
    • If the routes are added to the routing table due to incorrect configurations, go to 4.

    • If services need these routes, replace the license or contact technical support personnel for specification expansion.

  4. Adjust the configurations to delete unneeded routes and ensure that the number of IPv4 route prefixes falls below the lower-limit-value configured using the ip prefix-limit system threshold-alarm command, then check whether the RM_1.3.6.1.4.1.2011.5.25.145.10.4 hwIpv4PrefixThresholdExceedClear alarm is generated.

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

RM_1.3.6.1.4.1.2011.5.25.145.10.4 hwIpv4PrefixThresholdExceedClear

Description

RM/4/IPV4_PREFIX_THRESHOLD_EXCEED_RESM:OID [oid] The number of IPv4 prefixes falls below the threshold. (PrefixCount=[Integer], MaxValue=[Integer])

The number of IPv4 route prefixes fell below the clear alarm threshold.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.145.10.4

Warning

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

PrefixCount

Indicates the number of IPv4 route prefixes in the routing table.

MaxValue

Indicates the maximum number of IPv4 route prefixes supported by the device.

Impact on the System

Services will not be affected.

Possible Causes

The network administrator deleted some routes from the routing table or the number of routes learned by dynamic protocols decreased due to network topology changes.

Procedure

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

RM_1.3.6.1.4.1.2011.5.25.145.11.1 hwIpv6PrefixExceed

Description

RM/2/IPV6_PREFIX_EXCEED:OID [oid] The number of IPv6 prefixes exceeded the maximum value. (PrefixCount=[Integer], MaxValue=[Integer])

The number of IPv6 route prefixes exceeded that supported by the device.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.145.11.1

Major

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

PrefixCount

Indicates the number of IPv6 route prefixes in the routing table.

MaxValue

Indicates the maximum number of IPv6 route prefixes supported by the device.

Impact on the System

New IPv6 route prefixes cannot be added to the routing table. Services will be affected if the number of IPv6 route prefixes keeps increasing.

Possible Causes

A large number of IPv6 dynamic protocol routes (BGP or IGP routes for example), static routes, or direct routes were added to the routing table.

Procedure

  1. Run the display ipv6 routing-table statistics and display ipv6 routing-table all-vpn-instance statistics commands to check the numbers of IPv6 public and private route prefixes and the number of routes of each protocol that are added to the routing table.

    Check whether services need these routes or whether the routes are added to the routing table due to incorrect configurations.
    • If the routes are added to the routing table due to incorrect configurations, go to 2.

    • If services need these routes, replace the license or contact technical support personnel for specification expansion.

  2. Adjust the configurations to delete unneeded routes, and check whether the RM_1.3.6.1.4.1.2011.5.25.145.11.2 hwIpv6PrefixExceedClear alarm is generated.

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

RM_1.3.6.1.4.1.2011.5.25.145.11.2 hwIpv6PrefixExceedClear

Description

RM/2/IPV6_PREFIX_EXCEED_RESM:OID [oid] The number of IPv6 prefixes falls below the maximum value. (PrefixCount=[Integer], MaxValue=[Integer])

The number of IPv6 route prefixes fell below that supported by the device.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.145.11.2

Major

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

PrefixCount

Indicates the number of IPv6 route prefixes in the routing table.

MaxValue

Indicates the maximum number of IPv6 route prefixes supported by the device.

Impact on the System

Services will not be affected.

Possible Causes

The network administrator deleted some routes from the routing table or the number of routes learned by dynamic protocols decreased due to network topology changes.

Procedure

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

RM_1.3.6.1.4.1.2011.5.25.145.11.3 hwIpv6PrefixThresholdExceed

Description

RM/4/IPV6_PREFIX_THRESHOLD_EXCEED:OID [oid] The number of IPv6 prefixes exceeded the threshold. (PrefixCount=[Integer], MaxValue=[Integer])

The number of IPv6 route prefixes exceeded the alarm threshold.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.145.11.3

Warning

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

PrefixCount

Indicates the number of IPv6 route prefixes in the routing table.

MaxValue

Indicates the maximum number of IPv6 route prefixes supported by the device.

Impact on the System

The number of IPv6 route prefixes exceeded the alarm threshold, and services may be affected if the number of IPv6 route prefixes keeps increasing.

Possible Causes

A large number of IPv6 dynamic protocol routes (BGP or IGP routes for example), static routes, or direct routes were added to the routing table.

Procedure

  1. Run the display current-configuration command to check whether the threshold value specified in the ipv6 prefix-limit system threshold-alarm command is too small.

    • If the threshold value is too small, go to 2.
    • If he threshold value is in a proper range, go to 3.

  2. Rerun the ipv6 prefix-limit system threshold-alarm upper-limit upper-limit-value lower-limit lower-limit-value command to increase the value of upper-limit-value.
  3. Run the display ipv6 routing-table statistics and display ipv6 routing-table all-vpn-instance statistics commands to check the numbers of IPv6 public and private route prefixes and the number of routes of each protocol that are added to the routing table.

    Check whether services need these routes or whether the routes are added to the routing table due to incorrect configurations.
    • If the routes are added to the routing table due to incorrect configurations, go to 4.

    • If services need these routes, replace the license or contact technical support personnel for specification expansion.

  4. Adjust the configurations to delete unneeded routes and ensure that the number of IPv6 route prefixes falls below the lower-limit-value configured using the ipv6 prefix-limit system threshold-alarm command, then check whether the RM_1.3.6.1.4.1.2011.5.25.145.11.4 hwIpv6PrefixThresholdExceedClear alarm is generated.

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

RM_1.3.6.1.4.1.2011.5.25.145.11.4 hwIpv6PrefixThresholdExceedClear

Description

RM/4/IPV6_PREFIX_THRESHOLD_EXCEED_RESM:OID [oid] The number of IPv6 prefixes falls below the threshold. (PrefixCount=[Integer], MaxValue=[Integer])

The number of IPv6 route prefixes fell below the clear alarm threshold.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.145.11.4

Warning

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

PrefixCount

Indicates the number of IPv6 route prefixes in the routing table.

MaxValue

Indicates the maximum number of IPv6 route prefixes supported by the device.

Impact on the System

Services will not be affected.

Possible Causes

The network administrator deleted some routes from the routing table or the number of routes learned by dynamic protocols decreased due to network topology changes.

Procedure

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

RM_1.3.6.1.4.1.2011.5.25.145.19.1.1 hwPublicIpv4PrefixExceed

Description

RM/2/PUBLIC_IPV4_PREFIX_EXCEED:OID [oid] The number of public IPv4 prefixes exceeded the maximum value. (PrefixCount=[Integer], MaxValue=[Integer])

The number of IPv4 public route prefixes exceeded that supported by the system.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.145.19.1.1

Major

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

PrefixCount

Indicates the number of IPv4 public route prefixes in the routing table.

MaxValue

Indicates the maximum number of IPv4 public route prefixes supported by the device.

Impact on the System

New IPv4 public route prefixes cannot be added to the routing table. Services will be affected if the number of IPv4 route prefixes keeps increasing.

Possible Causes

Cause 1:

A large number of IPv4 dynamic protocol routes (BGP or IGP routes for example), static routes, or direct routes were added to the routing table.

Cause 2:

The maximum number of IPv4 public route prefixes supported by the system was decreased.

Procedure

  1. Run the display ip routing-table statistics command to check the number of IPv4 public route prefixes and the number of routes of each protocol that are added to the routing table. Run the display ip routing-table limit command to check the number of IPv4 public route prefixes supported by the system.

    Check whether services need these routes or whether the routes are added to the routing table due to incorrect configurations.
    • If the routes are added to the routing table due to incorrect configurations, go to 2.

    • If services need these routes, replace the license or contact technical support personnel for specification expansion.

  2. Adjust the configurations to delete unneeded routes, and check whether the RM_1.3.6.1.4.1.2011.5.25.145.19.1.2 hwPublicIpv4PrefixExceedClear alarm is generated.

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

RM_1.3.6.1.4.1.2011.5.25.145.19.1.2 hwPublicIpv4PrefixExceedClear

Description

RM/2/PUBLIC_IPV4_PREFIX_EXCEED_RESM:OID [oid] The number of public IPv4 prefixes falls below the maximum value. (PrefixCount=[Integer], MaxValue=[Integer])

The number of IPv4 public route prefixes fell below that supported by the system.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.145.19.1.2

Major

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

PrefixCount

Indicates the number of IPv4 public route prefixes in the routing table.

MaxValue

Indicates the maximum number of IPv4 public route prefixes supported by the device.

Impact on the System

Services will not be affected.

Possible Causes

Cause 1:

The network administrator deleted some routes from the routing table or the number of routes learned by dynamic protocols decreased due to network topology changes.

Cause 2:

The maximum number of IPv4 public route prefixes supported by the system was increased or the limit on the number of IPv4 public route prefixes was deleted.

Procedure

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

RM_1.3.6.1.4.1.2011.5.25.145.19.1.3 hwPublicIpv4PrefixThresholdExceed

Description

RM/4/PUBLIC_IPV4_PREFIX_THRESHOLD_EXCEED:OID [oid] The number of public IPv4 prefixes exceeded the threshold. (PrefixCount=[Integer], Threshold=[Integer])

The number of IPv4 public route prefixes exceeded the alarm threshold.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.145.19.1.3

Warning

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

PrefixCount

Indicates the number of IPv4 public route prefixes in the routing table.

Threshold

Indicates the threshold of the number of IPv4 public route prefixes.

Impact on the System

The number of IPv4 public route prefixes exceeded the alarm threshold, and services may be affected if the number of IPv4 public route prefixes keeps increasing.

Possible Causes

Cause 1:

A large number of IPv4 dynamic protocol routes (BGP or IGP routes for example), static routes, or direct routes were added to the routing table.

Cause 2:

The threshold of the number of IPv4 public route prefixes was decreased.

Procedure

  1. Run the display current-configuration command to check whether the threshold value specified in the ip prefix-limit command is too small.

    • If the threshold value is too small, go to 2.
    • If the threshold value is in a proper range, go to 3.

  2. Rerun the ip prefix-limit number alert-percent command to increase number and alert-percent.
  3. Run the display ip routing-table statistics command to check the number of IPv4 public route prefixes and the number of routes of each protocol that are added to the routing table.

    Check whether services need these routes or whether the routes are added to the routing table due to incorrect configurations.
    • If the routes are added to the routing table due to incorrect configurations, go to 4.

    • If services need these routes, replace the license or contact technical support personnel for specification expansion.

  4. Adjust the configurations to delete unneeded routes, and check whether the RM_1.3.6.1.4.1.2011.5.25.145.19.1.4 hwPublicIpv4PrefixThresholdExceedClear alarm is generated.

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

RM_1.3.6.1.4.1.2011.5.25.145.19.1.4 hwPublicIpv4PrefixThresholdExceedClear

Description

RM/4/PUBLIC_IPV4_PREFIX_THRESHOLD_EXCEED_RESM:OID [oid] The number of public IPv4 prefixes falls below the threshold. (PrefixCount=[Integer], Threshold=[Integer])

The number of IPv4 public route prefixes fell below the clear alarm threshold.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.145.19.1.4

Warning

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

PrefixCount

Indicates the number of IPv4 public route prefixes in the routing table.

Threshold

Indicates the threshold of the number of IPv4 public route prefixes.

Impact on the System

Services will not be affected.

Possible Causes

Cause 1:

The network administrator deleted some routes from the routing table or the number of routes learned by dynamic protocols decreased due to network topology changes.

Cause 2:

The threshold of IPv4 public route prefixes was increased or the limit on the number of IPv4 public route prefixes was deleted.

Procedure

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

RM_1.3.6.1.4.1.2011.5.25.145.19.2.1 hwPublicIpv6PrefixExceed

Description

RM/2/PUBLIC_IPV6_PREFIX_EXCEED:OID [oid] The number of public IPv6 prefixes exceeded the maximum value. (PrefixCount=[Integer], MaxValue=[Integer])

The number of IPv6 public route prefixes exceeded that supported by the system.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.145.19.2.1

Major

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

PrefixCount

Indicates the number of IPv6 public route prefixes in the routing table.

MaxValue

Indicates the maximum number of IPv6 public route prefixes supported by the device.

Impact on the System

New IPv6 public route prefixes cannot be added to the routing table. Services will be affected if the number of IPv6 route prefixes keeps increasing.

Possible Causes

Cause 1:

A large number of IPv6 dynamic protocol routes (BGP or IGP routes for example), static routes, or direct routes were added to the routing table.

Cause 2:

The maximum number of IPv6 public route prefixes supported by the system was decreased.

Procedure

  1. Run the display ipv6 routing-table statistics command to check the number of IPv6 public route prefixes and the number of routes of each protocol that are added to the routing table. Run the display ipv6 routing-table limit command to check the number of IPv6 public route prefixes supported by the system.

    Check whether services need these routes or whether the routes are added to the routing table due to incorrect configurations.
    • If the routes are added to the routing table due to incorrect configurations, go to 2.

    • If services need these routes, replace the license or contact technical support personnel for specification expansion.

  2. Adjust the configurations to delete unneeded routes, and check whether the RM_1.3.6.1.4.1.2011.5.25.145.19.2.2 hwPublicIpv6PrefixExceedClear alarm is generated.

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

RM_1.3.6.1.4.1.2011.5.25.145.19.2.2 hwPublicIpv6PrefixExceedClear

Description

RM/2/PUBLIC_IPV6_PREFIX_EXCEED_RESM:OID [oid] The number of public IPv6 prefixes falls below the maximum value. (PrefixCount=[Integer], MaxValue=[Integer])

The number of IPv6 public route prefixes fell below that supported by the system.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.145.19.2.2

Major

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

PrefixCount

Indicates the number of IPv6 public route prefixes in the routing table.

MaxValue

Indicates the maximum number of IPv6 public route prefixes supported by the device.

Impact on the System

Services will not be affected.

Possible Causes

Cause 1:

The network administrator deleted some routes from the routing table or the number of routes learned by dynamic protocols decreased due to network topology changes.

Cause 2:

The maximum number of IPv6 public route prefixes supported by the system was increased or the limit on the number of IPv6 public route prefixes was deleted.

Procedure

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

RM_1.3.6.1.4.1.2011.5.25.145.19.2.3 hwPublicIpv6PrefixThresholdExceed

Description

RM/4/PUBLIC_IPV6_PREFIX_THRESHOLD_EXCEED:OID [oid] The number of public IPv6 prefixes exceeded the threshold. (PrefixCount=[Integer], Threshold=[Integer])

The number of IPv6 public route prefixes exceeded the alarm threshold.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.145.19.2.3

Warning

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

PrefixCount

Indicates the number of IPv6 public route prefixes in the routing table.

Threshold

Indicates the threshold of the number of IPv6 public route prefixes.

Impact on the System

The number of IPv6 public route prefixes exceeded the alarm threshold, and services may be affected if the number of IPv6 public route prefixes keeps increasing.

Possible Causes

Cause 1:

A large number of IPv6 dynamic protocol routes (BGP or IGP routes for example), static routes, or direct routes were added to the routing table.

Cause 2:

The threshold of the number of IPv6 public route prefixes was decreased.

Procedure

  1. Run the display current-configuration command to check whether the threshold value specified in the ipv6 prefix-limit command is too small.

    • If the threshold value is too small, go to 2.
    • If the threshold value is in a proper range, go to 3.

  2. Rerun the ipv6 prefix-limit number alert-percent command to increase number and alert-percent.
  3. Run the display ipv6 routing-table statistics command to check the number of IPv6 public route prefixes and the number of routes of each protocol that are added to the routing table.

    Check whether services need these routes or whether the routes are added to the routing table due to incorrect configurations.
    • If the routes are added to the routing table due to incorrect configurations, go to 4.

    • If services need these routes, replace the license or contact technical support personnel for specification expansion.

  4. Adjust the configurations to delete unneeded routes, and check whether the RM_1.3.6.1.4.1.2011.5.25.145.19.2.4 hwPublicIpv6PrefixThresholdExceedClear alarm is generated.

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

RM_1.3.6.1.4.1.2011.5.25.145.19.2.4 hwPublicIpv6PrefixThresholdExceedClear

Description

RM/4/PUBLIC_IPV6_PREFIX_THRESHOLD_EXCEED_RESM:OID [oid] The number of public IPv6 prefixes falls below the threshold. (PrefixCount=[Integer], Threshold=[Integer])

The number of IPv6 public route prefixes fell below the clear alarm threshold.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.145.19.2.4

Warning

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

PrefixCount

Indicates the number of IPv6 public route prefixes in the routing table.

Threshold

Indicates the threshold of the number of IPv6 public route prefixes.

Impact on the System

Services will not be affected.

Possible Causes

Cause 1:

The network administrator deleted some routes from the routing table or the number of routes learned by dynamic protocols decreased due to network topology changes.

Cause 2:

The threshold of IPv6 public route prefixes was increased or the limit on the number of IPv4 public route prefixes was deleted.

Procedure

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

RM_1.3.6.1.4.1.2011.5.25.145.19.3.1 hwL3vpnIpv6PrefixExceed

Description

RM/2/L3VPN_IPV6_PREFIX_EXCEED:OID [OID] The number of IPv6 prefixes in the VPN instance exceeded the maximum value. (VpnInstanceName=[octet], PrefixCount=[Integer], MaxValue=[Integer])

The number of IPv6 route prefixes in the VPN instance exceeded the maximum number that is allowed.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.145.19.3.1 Major

qualityOfServiceAlarm

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VpnInstanceName

Name of a VPN instance

PrefixCount

Current number of IPv6 route prefixes in the VPN instance

MaxValue

Maximum number of IPv6 route prefixes in the VPN instance

Impact on the System

New route prefixes cannot be added.

Possible Causes

Cause 1:

A large number of IPv6 VPN dynamic protocol (BGP or an IGP), static, direct, and UNR routes were added to the routing table.

Cause 2:

The maximum number of IPv6 route prefixes in the VPN instance was reduced.

Procedure

  1. Run the display ipv6 routing-table vpn-instance vpn-instance-name statistics command to check the total number of route prefixes and the number of route prefixes of each protocol. Then run the display ipv6 routing-table limit command to check whether the number of IPv6 route prefixes in the VPN instance has exceeded the maximum number that is allowed.

    • If the number of IPv6 route prefixes in the VPN instance has exceeded the maximum number that is allowed, go to Step 3.

    • If the number of IPv6 route prefixes in the VPN instance has not exceeded the maximum number that is allowed, go to Step 2.

  2. Collect alarm information and configuration information, and then contact technical support personnel.
  3. Implement capacity expansion or delete unnecessary services.
  4. End.

RM_1.3.6.1.4.1.2011.5.25.145.19.3.2 hwL3vpnIpv6PrefixExceedClear

Description

RM/2/L3VPN_IPV6_PREFIX_EXCEED_RESM:OID [OID] The number of IPv6 prefixes in the VPN instance falls below the maximum value. (VpnInstanceName=[octet], PrefixCount=[Integer], MaxValue=[Integer])

The number of IPv6 route prefixes in the VPN instance fell below the maximum number that is allowed.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.145.19.3.2 Major

qualityOfServiceAlarm

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VpnInstanceName

Name of a VPN instance

PrefixCount

Current number of IPv6 route prefixes in the VPN instance

MaxValue

Maximum number of IPv6 route prefixes in the VPN instance

Impact on the System

Services will not be affected.

Possible Causes

Cause 1:

Some protocol routes were deleted.

Cause 2:

The maximum number of IPv6 route prefixes in the VPN instance was increased to a value greater than the current number of IPv6 route prefixes in the VPN instance.

Procedure

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

RM_1.3.6.1.4.1.2011.5.25.145.19.3.3 hwL3vpnIpv6PrefixThresholdExceed

Description

RM/4/L3VPN_IPV6_PREFIX_THRESHOLD_EXCEED:OID [OID] The number of IPv6 prefixes in the VPN instance exceeded the threshold. (VpnInstanceName=[octet], PrefixCount=[Integer], Threshold=[Integer])

The number of IPv6 route prefixes in the VPN instance exceeded the alarm threshold.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.145.19.3.3 Warning

qualityOfServiceAlarm

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VpnInstanceName

Name of a VPN instance

PrefixCount

Current number of IPv6 route prefixes in the VPN instance

Threshold

Alarm threshold for the number of IPv6 route prefixes in the VPN instance

Impact on the System

The number of IPv6 route prefixes in the VPN instance is approaching the maximum number that is allowed, and route prefixes will no longer be accepted if the maximum number is reached, affecting services.

Possible Causes

Cause 1:

A large number of IPv6 VPN dynamic protocol (BGP or an IGP), static, direct, and UNR routes were added to the routing table.

Cause 2:

The alarm threshold for the number of IPv6 route prefixes in the VPN instance was reduced.

Procedure

  1. Run the display ipv6 routing-table vpn-instance vpn-instance-name statistics command to check the total number of route prefixes and the number of route prefixes of each protocol. Then run the display ipv6 routing-table limit command to check whether the number of IPv6 route prefixes in the VPN instance has exceeded the alarm threshold.

    • If the number of IPv6 route prefixes in the VPN instance has exceeded the alarm threshold, go to Step 2.

    • If the number of IPv6 route prefixes in the VPN instance has not exceeded the alarm threshold, go to Step 3.

  2. If the configured private network prefix threshold value is too small, run the prefix limit command in the IPv6 address family view of the VPN instance to reconfigure the threshold. Then check whether the fault is rectified.

    • If yes, go to step 4.

    • If no, go to step 3.

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

Related Information

None

Translation
Download
Updated: 2019-04-09

Document ID: EDOC1100065855

Views: 3531

Downloads: 2

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