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

E9000 Server V100R001 HMM Alarm Handling 19

This document describes E9000 server alarms in terms of the meaning, impact on the system, possible causes, and solutions.
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.10.1 hwIpv4PrefixExceed

Description

The number of IPv4 prefixes exceeded the maximum value. (PrefixCount=[PrefixCount], MaxValue=[MaxValue])

The number of IPv4 prefixes exceeded the maximum value.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

hwIpv4PrefixExceed

Trap OID

1.3.6.1.4.1.2011.5.25.145.10.1

Alarm ID

0x08390004

Alarm Type

qualityOfServiceAlarm

Raise or Clear

Raise

Match trap

RM_1.3.6.1.4.1.2011.5.25.145.10.2 hwIpv4PrefixExceedClear

Parameters

Parameter

Description

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.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.145.8.1

hwCurIpv4PrefixNum

N/A

1.3.6.1.4.1.2011.5.25.145.8.2

hwIpv4PrefixLimitValue

N/A

Impact on the System

If more IPv4 routes are added, they will be discarded. As a result, traffic may be interrupted.

Possible Causes

The number of IPv4 prefixes exceeded the maximum value configured using the ip prefix-limit number { alert-percent [ route-unchanged ] | simply-alert } command.

Procedure
  1. Run the display ip routing-table statistics command to check the number of IPv4 public route prefixes and the display ip routing-table all-vpn-instance statistics command to check the number of IPv4 VPN route prefixes.
  2. Check whether the number of route prefixes of each protocol is within the normal range.

    • If the number of route prefixes of each protocol is within the normal range, go to Step 4.
    • If the number of route prefixes of each protocol is not within the normal range, go to Step 3.

  3. Delete unneeded IPv4 routes and then check whether the alarm persists.

    • If the alarm persists, go to Step 4.
    • If the alarm is cleared, go to Step 6.

  4. Check whether the configured maximum number of IPv4 prefixes is greater than the actual number.

    • If the configured maximum number of IPv4 prefixes is greater than or equal to the actual number, go to Step 5.
    • If the configured maximum number of IPv4 prefixes is less than the actual number, run the ip prefix-limit number { alert-percent [ route-unchanged ] | simply-alert } command to reconfigure the maximum number and go to Step 6.

  5. Collect trap, log, and configuration information, and contact technical support personnel technical support personnel.
  6. End.

RM_1.3.6.1.4.1.2011.5.25.145.10.2 hwIpv4PrefixExceedClear

Description

The number of IPv4 prefixes fell below the maximum value. (PrefixCount=[PrefixCount], MaxValue=[MaxValue])

The number of IPv4 prefixes fell below the maximum value.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

hwIpv4PrefixExceedClear

Trap OID

1.3.6.1.4.1.2011.5.25.145.10.2

Alarm ID

0x08390004

Alarm Type

qualityOfServiceAlarm

Raise or Clear

Clear

Match trap

RM_1.3.6.1.4.1.2011.5.25.145.10.1 hwIpv4PrefixExceed

Parameters

Parameter

Description

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.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.145.8.1

hwCurIpv4PrefixNum

N/A

1.3.6.1.4.1.2011.5.25.145.8.2

hwIpv4PrefixLimitValue

N/A

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

The number of IPv6 prefixes exceeded the maximum value. (PrefixCount=[PrefixCount], MaxValue=[MaxValue])

The number of IPv6 prefixes exceeded the maximum value.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

hwIpv6PrefixExceed

Trap OID

1.3.6.1.4.1.2011.5.25.145.11.1

Alarm ID

0x08390005

Alarm Type

qualityOfServiceAlarm

Raise or Clear

Raise

Match trap

RM_1.3.6.1.4.1.2011.5.25.145.11.2 hwIpv6PrefixExceedClear

Parameters

Parameter

Description

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.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.145.9.1

hwCurIpv6PrefixNum

N/A

1.3.6.1.4.1.2011.5.25.145.9.2

hwIpv6PrefixLimitValue

N/A

Impact on the System

If more IPv6 routes are added, they will be discarded. As a result, traffic may be interrupted.

Possible Causes

The number of IPv6 prefixes exceeded the maximum value configured using the ipv6 prefix-limit number { alert-percent [ route-unchanged ] | simply-alert } command.

Procedure
  1. Run the display ipv6 routing-table statistics command to check the number of IPv6 public route prefixes and the display ipv6 routing-table all-vpn-instance statistics command to check the number of IPv6 VPN route prefixes.
  2. Check whether the number of route prefixes of each protocol is within the normal range.

    • If the number of route prefixes of each protocol is within the normal range, go to Step 4.
    • If the number of route prefixes of each protocol is not within the normal range, go to Step 3.

  3. Delete unneeded IPv6 routes and then check whether the alarm persists.

    • If the alarm persists, go to Step 4.
    • If the alarm is cleared, go to Step 6.

  4. Check whether the configured maximum number of IPv6 prefixes is greater than the actual number.

    • If the configured maximum number of IPv6 prefixes is greater than or equal to the actual number, go to Step 5.
    • If the configured maximum number of IPv6 prefixes is less than the actual number, run the ipv6 prefix-limit number { alert-percent [ route-unchanged ] | simply-alert } command to reconfigure the maximum number and go to Step 6.

  5. Collect trap, log, and configuration information, and contact technical support personnel technical support personnel.
  6. End.

RM_1.3.6.1.4.1.2011.5.25.145.11.2 hwIpv6PrefixExceedClear

Description

The number of IPv6 prefixes fell below the maximum value. (PrefixCount=[PrefixCount], MaxValue=[MaxValue])

The number of IPv6 prefixes fell below the maximum value.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

hwIpv6PrefixExceedClear

Trap OID

1.3.6.1.4.1.2011.5.25.145.11.2

Alarm ID

0x08390005

Alarm Type

qualityOfServiceAlarm

Raise or Clear

Clear

Match trap

RM_1.3.6.1.4.1.2011.5.25.145.11.1 hwIpv6PrefixExceed

Parameters

Parameter

Description

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.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.145.9.1

hwCurIpv6PrefixNum

N/A

1.3.6.1.4.1.2011.5.25.145.9.2

hwIpv6PrefixLimitValue

N/A

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

The number of IPv4 prefixes exceeded the threshold. (PrefixCount=[PrefixCount], MaxValue=[MaxValue])

The number of IPv4 route prefixes exceeded the alarm threshold.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Warning

Mnemonic Code

hwIpv4PrefixThresholdExceed

Trap OID

1.3.6.1.4.1.2011.5.25.145.10.3

Alarm ID

0x08390006

Alarm Type

qualityOfServiceAlarm

Raise or Clear

Raise

Match trap

RM_1.3.6.1.4.1.2011.5.25.145.10.4 hwIpv4PrefixThresholdExceedClear

Parameters

Parameter

Description

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.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.145.8.1

hwCurIpv4PrefixNum

N/A

1.3.6.1.4.1.2011.5.25.145.8.2

hwIpv4PrefixLimitValue

N/A

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

The number of IPv4 prefixes exceeded the threshold of 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 Step 2.
  • If the threshold value is in a proper range, go to Step 3.
  1. Run 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.
  2. 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 Step 4.
    • If services need these routes, go to Step 5.

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

    • If the RM_1.3.6.1.4.1.2011.5.25.145.10.4 hwIpv4PrefixThresholdExceedClear alarm is not generated, go to Step 6.
    • If theRM_1.3.6.1.4.1.2011.5.25.145.10.4 hwIpv4PrefixThresholdExceedClear alarm is generated, go to Step 7

  4. Reset a proper maximum number of IPv4 route prefixes supported by the device, then check whether the RM_1.3.6.1.4.1.2011.5.25.145.10.4 hwIpv4PrefixThresholdExceedClear alarm is generated.

    • If the RM_1.3.6.1.4.1.2011.5.25.145.10.4 hwIpv4PrefixThresholdExceedClear alarm is not generated, go to Step 6.
    • If the RM_1.3.6.1.4.1.2011.5.25.145.10.4 hwIpv4PrefixThresholdExceedClear alarm is generated, go to Step 7.

  5. Collect trap, log, and configuration information, and contact technical support personnel technical support personnel.
  6. End.

RM_1.3.6.1.4.1.2011.5.25.145.10.4 hwIpv4PrefixThresholdExceedClear

Description

The number of IPv4 prefixes fell below the threshold. (PrefixCount=[PrefixCount], MaxValue=[MaxValue])

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

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Warning

Mnemonic Code

hwIpv4PrefixThresholdExceedClear

Trap OID

1.3.6.1.4.1.2011.5.25.145.10.4

Alarm ID

0x08390006

Alarm Type

qualityOfServiceAlarm

Raise or Clear

Clear

Match trap

RM_1.3.6.1.4.1.2011.5.25.145.10.3 hwIpv4PrefixThresholdExceed

Parameters

Parameter

Description

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.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.145.8.1

hwCurIpv4PrefixNum

N/A

1.3.6.1.4.1.2011.5.25.145.8.2

hwIpv4PrefixLimitValue

N/A

Impact on the System

The alarm of the number of IPv4 route prefixes exceeded the alarm threshold is cleared.

Possible Causes

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

Procedure
  • 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

The number of IPv6 prefixes exceeded the threshold. (PrefixCount=[PrefixCount], MaxValue=[MaxValue])

The number of IPv6 route prefixes exceeded the alarm threshold.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Warning

Mnemonic Code

hwIpv6PrefixThresholdExceed

Trap OID

1.3.6.1.4.1.2011.5.25.145.11.3

Alarm ID

0x08390007

Alarm Type

qualityOfServiceAlarm

Raise or Clear

Raise

Match trap

RM_1.3.6.1.4.1.2011.5.25.145.11.4 hwIpv6PrefixThresholdExceedClear

Parameters

Parameter

Description

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.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.145.9.1

hwCurIpv6PrefixNum

N/A

1.3.6.1.4.1.2011.5.25.145.9.2

hwIpv6PrefixLimitValue

N/A

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

The number of IPv6 prefixes exceeded the threshold of the routing table.

Procedure
  1. Run the display current-configurationcommand 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 Step 2.
  • If the threshold value is in a proper range, go to Step 3.
  1. Run 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.
  2. 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 Step 4.
    • If services need these routes, go to Step 5.

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

    • If the RM_1.3.6.1.4.1.2011.5.25.145.11.4 hwIpv6PrefixThresholdExceedClear alarm is not generated, go to Step 6.
    • If the RM_1.3.6.1.4.1.2011.5.25.145.11.4 hwIpv6PrefixThresholdExceedClear alarm is generated, go to Step 7.

  4. Reset a proper maximum number of IPv6 route prefixes supported by the device, then check whether the RM_1.3.6.1.4.1.2011.5.25.145.11.4 hwIpv6PrefixThresholdExceedClear alarm is generated.

    • If the RM_1.3.6.1.4.1.2011.5.25.145.11.4 hwIpv6PrefixThresholdExceedClear alarm is not generated, go to Step 6.
    • If the RM_1.3.6.1.4.1.2011.5.25.145.11.4 hwIpv6PrefixThresholdExceedClear alarm is generated, go to Step 7.

  5. Collect trap, log, and configuration information, and contact technical support personnel technical support personnel.
  6. End.

RM_1.3.6.1.4.1.2011.5.25.145.11.4 hwIpv6PrefixThresholdExceedClear

Description

The number of IPv6 prefixes fell below the threshold. (PrefixCount=[PrefixCount], MaxValue=[MaxValue])

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

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Warning

Mnemonic Code

hwIpv6PrefixThresholdExceedClear

Trap OID

1.3.6.1.4.1.2011.5.25.145.11.4

Alarm ID

0x08390007

Alarm Type

qualityOfServiceAlarm

Raise or Clear

Clear

Match trap

RM_1.3.6.1.4.1.2011.5.25.145.11.3 hwIpv6PrefixThresholdExceed

Parameters

Parameter

Description

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.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.145.9.1

hwCurIpv6PrefixNum

N/A

1.3.6.1.4.1.2011.5.25.145.9.2

hwIpv6PrefixLimitValue

N/A

Impact on the System

The alarm of the number of IPv6 route prefixes exceeded the alarm threshold is cleared.

Possible Causes

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

Procedure
  • 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

The number of public IPv6 prefixes exceeded the maximum value. (PrefixCount=[hwCurIpv6PrefixNum], MaxValue=[hwIpv6PrefixLimitValue])

The number of IPv6 public route prefixes exceeded the maximum number that is allowed.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

hwPublicIpv6PrefixExceed

Trap OID

1.3.6.1.4.1.2011.5.25.145.19.2.1

Alarm ID

0x7012200f

Alarm Type

qualityOfServiceAlarm

Raise or Clear

Raise

Match trap

RM_1.3.6.1.4.1.2011.5.25.145.19.2.2 hwPublicIpv6PrefixExceedClear

Parameters

Parameter

Description

PrefixCount

Number of IPv6 public route prefixes in the routing table

MaxValue

Maximum number of IPv6 public route prefixes that is allowed

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.145.9.1

hwCurIpv6PrefixNum

N/A

1.3.6.1.4.1.2011.5.25.145.9.2

hwIpv6PrefixLimitValue

N/A

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 routes were added to the routing table.

Cause 2:

The maximum number of IPv6 public route prefixes that is allowed was decreased.

Procedure
  1. Run the display ipv6 routing-table statistics command to check the total number of IPv6 public route prefixes and the number of routes of each routing protocol that are added to the IPv6 routing table. Then, run the display ipv6 routing-table limit command to check whether the number of IPv6 public route prefixes exceeds the configured maximum number.
  • If the number of IPv6 public route prefixes exceeds the configured maximum number, go to 2.
  • If the number of IPv6 public route prefixes is less than the configured maximum number, go to 3.
  1. Delete unneeded IPv6 public routes or run the ipv6 prefix-limit number { alert-percent [ route-unchanged ] | simply-alert } command to increase the maximum number. Then, check whether the alarm persists.

    • If the alarm persists, go to 3.
    • If the alarm is cleared, go to 4.

  2. Collect trap, log, and configuration information, and contact technical support personnel technical support personnel.
  3. End.

RM_1.3.6.1.4.1.2011.5.25.145.19.2.2 hwPublicIpv6PrefixExceedClear

Description

The number of public IPv6 prefixes falls below the maximum value. (PrefixCount=[hwCurIpv6PrefixNum], MaxValue=[hwIpv6PrefixLimitValue])

The number of IPv6 public route prefixes fell below the maximum number that is allowed.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

hwPublicIpv6PrefixExceedClear

Trap OID

1.3.6.1.4.1.2011.5.25.145.19.2.2

Alarm ID

0x7012200f

Alarm Type

qualityOfServiceAlarm

Raise or Clear

Clear

Match trap

RM_1.3.6.1.4.1.2011.5.25.145.19.2.1 hwPublicIpv6PrefixExceed

Parameters

Parameter

Description

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.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.145.9.1

hwCurIpv6PrefixNum

N/A

1.3.6.1.4.1.2011.5.25.145.9.2

hwIpv6PrefixLimitValue

N/A

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

The number of public IPv6 prefixes exceeded the threshold. (PrefixCount=[hwCurIpv6PrefixNum], Threshold=[hwIpv6PrefixLimitValue])

The number of IPv6 public route prefixes exceeded the value calculated using the formula (Maximum number x Threshold/100).

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Warning

Mnemonic Code

hwPublicIpv6PrefixThresholdExceed

Trap OID

1.3.6.1.4.1.2011.5.25.145.19.2.3

Alarm ID

0x70122011

Alarm Type

qualityOfServiceAlarm

Raise or Clear

Raise

Match trap

RM_1.3.6.1.4.1.2011.5.25.145.19.2.4 hwPublicIpv6PrefixThresholdExceedClear

Parameters

Parameter

Description

PrefixCount

Number of IPv6 public route prefixes in the routing table

Threshold

Threshold of the number of IPv6 public route prefixes

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.145.9.1

hwCurIpv6PrefixNum

N/A

1.3.6.1.4.1.2011.5.25.145.9.2

hwIpv6PrefixLimitValue

N/A

Impact on the System

The number of IPv6 public route prefixes exceeded the value calculated using the formula (Maximum number x Threshold/100), and services may be affected if the number of IPv6 public route prefixes keeps increasing.

Possible Causes

Cause 1:

A large number of IPv6 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 ipv6 routing-table statistics command to check the total number of IPv6 public route prefixes and the number of routes of each routing protocol that are added to the IPv6 routing table. Then, run the display ipv6 routing-table limit command to check whether the number of IPv6 public route prefixes exceeds the value calculated using the formula (Maximum number x Threshold/100).
  • If the number of IPv6 public route prefixes exceeds the value, go to 2.
  • If the number of IPv6 public route prefixes is less than the value, go to 3.
  1. Delete unneeded IPv6 public routes or run the ipv6 prefix-limit number { alert-percent [ route-unchanged ] | simply-alert } command to increase alert-percent. Then, check whether the alarm persists.

    • If the alarm persists, go to 3.
    • If the alarm is cleared, go to 4.

  2. Collect trap, log, and configuration information, and contact technical support personnel technical support personnel.
  3. End.

RM_1.3.6.1.4.1.2011.5.25.145.19.2.4 hwPublicIpv6PrefixThresholdExceedClear

Description

The number of public IPv6 prefixes falls below the threshold. (PrefixCount=[hwCurIpv6PrefixNum], Threshold=[hwIpv6PrefixLimitValue])

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

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Warning

Mnemonic Code

hwPublicIpv6PrefixThresholdExceedClear

Trap OID

1.3.6.1.4.1.2011.5.25.145.19.2.4

Alarm ID

0x70122011

Alarm Type

qualityOfServiceAlarm

Raise or Clear

Clear

Match trap

RM_1.3.6.1.4.1.2011.5.25.145.19.2.3 hwPublicIpv6PrefixThresholdExceed

Parameters

Parameter

Description

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.

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.145.9.1

hwCurIpv6PrefixNum

N/A

1.3.6.1.4.1.2011.5.25.145.9.2

hwIpv6PrefixLimitValue

N/A

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

The number of IPv6 prefixes in the VPN instance exceeded the maximum value. (VpnInstanceName=[VpnInstanceName], PrefixCount=[VpnInstanceRouteCount], MaxValue=[MaxValue])

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

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

hwL3vpnIpv6PrefixExceed

Trap OID

1.3.6.1.4.1.2011.5.25.145.19.3.1

Alarm ID

0x70122013

Alarm Type

qualityOfServiceAlarm

Raise or Clear

Raise

Match trap

RM_1.3.6.1.4.1.2011.5.25.145.19.3.2 hwL3vpnIpv6PrefixExceedClear

Parameters

Parameter

Description

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

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.145.9.3

hwIpv6PrefixLimitVpnName

N/A

1.3.6.1.4.1.2011.5.25.145.9.1

hwCurIpv6PrefixNum

N/A

1.3.6.1.4.1.2011.5.25.145.9.2

hwIpv6PrefixLimitValue

N/A

Impact on the System

If more IPv6 routes are added, they will be discarded. As a result, traffic may be interrupted.

Possible Causes

Cause 1:

A large number of IPv6 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 IPv6 route prefixes in the VPN instance and the number of routes of each routing protocol that are added to the IPv6 routing table. Then, run the display ipv6 routing-table limit command to check whether the number of IPv6 route prefixes in the VPN instance exceeds the configured maximum number.
  • If the number of IPv6 route prefixes in the VPN instance exceeds the configured maximum number, go to 2.
  • If the number of IPv6 route prefixes in the VPN instance is less than the configured maximum number, go to 3.
  1. Delete unneeded IPv6 VPN routes or run the ipv6 prefix limit number { alert-percent [ route-unchanged ]| simply-alert } command to increase the maximum number. Then, check whether the alarm persists.

    • If the alarm persists, go to 3.
    • If the alarm is cleared, go to 4.

  2. Collect trap, log, and configuration information, and contact technical support personnel technical support personnel.
  3. End.

RM_1.3.6.1.4.1.2011.5.25.145.19.3.2 hwL3vpnIpv6PrefixExceedClear

Description

The number of IPv6 prefixes in the VPN instance fell below the maximum value. (VpnInstanceName=[VpnInstanceName], VpnInstanceRouteCount=[VpnInstanceRouteCount], MaxValue=[MaxValue])

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

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

hwL3vpnIpv6PrefixExceedClear

Trap OID

1.3.6.1.4.1.2011.5.25.145.19.3.2

Alarm ID

0x70122013

Alarm Type

qualityOfServiceAlarm

Raise or Clear

Clear

Match trap

RM_1.3.6.1.4.1.2011.5.25.145.19.3.1 hwL3vpnIpv6PrefixExceed

Parameters

Parameter

Description

VpnInstanceName

Name of a VPN instance

VpnInstanceRouteCount

Current number of IPv6 route prefixes in the VPN instance

MaxValue

Maximum number of IPv6 route prefixes in the VPN instance

VB

VB OID

VB Name

VB Index

1.3.6.1.4.1.2011.5.25.145.9.3

hwIpv6PrefixLimitVpnName

N/A

1.3.6.1.4.1.2011.5.25.145.9.1

hwCurIpv6PrefixNum

N/A

1.3.6.1.4.1.2011.5.25.145.9.2

hwIpv6PrefixLimitValue

N/A

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.
Translation
Download
Updated: 2018-08-16

Document ID: EDOC1000015902

Views: 196432

Downloads: 1571

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