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

L3VPNBASE

L3VPN_1.3.6.1.2.1.10.166.11.0.1 mplsL3VpnVrfUp

Description

The interface bound to the VPN instance went Up. (VpnInstanceName=[VpnInstanceName], IfName=[IfName], IfCurRowStatus=[IfCurRowStatus], VRFOperationStatus=[VRFOperationStatus])

One of the interfaces in the Down state that are bound to VPN instance goes Up.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Informational

Mnemonic Code

L3VPN_MIB_TRAP_VRF_UP

Trap OID

1.3.6.1.2.1.10.166.11.0.1

Alarm ID

0x09110000

Alarm Type

communicationsAlarm

Raise or Clear

Clear

Match trap

L3VPN_1.3.6.1.2.1.10.166.11.0.2 mplsL3VpnVrfDown

Parameters

Name

Meaning

VpnInstanceName

Indicates the name of the VPN.

IfName

Indicates the name of the interface.

IfCurRowStatus

Indicates the row status of the interface. Including:

  • 1: Active
  • 2: Not in Service
  • 3: Not Ready
  • 4: Create and Go
  • 5: Create and Wait
  • 6: Destroy

VRFOperationStatus

Indicates the status of the VRF. Including:

  • 1: Up
  • 2: Down
VB

VB OID

VB Name

VB Index

1.3.6.1.2.1.10.166.11.1.2.1.1.5

mplsL3VpnIfConfRowStatus

mplsL3VpnVrfName;

mplsL3VpnIfConfIndex;

1.3.6.1.2.1.10.166.11.1.2.2.1.6

mplsL3VpnVrfOperStatus

mplsL3VpnVrfName;

Impact on the System

At least one available interface is bound with the VPN instance.

Possible Causes

1. No interface was bound with the VPN instance, and An Up interface is bound to the VPN instance.

2. One interface was bound with the VPN instance, and the interface status changed from Down to Up.

3. Multiple interfaces were bound with the VPN instance; the status of all the interfaces was Down, the first interface went Up.

Procedure
  • This alarm message is informational only, and no action is required.
Related Information

L3VPN_1.3.6.1.2.1.10.166.11.0.2 mplsL3VpnVrfDown

L3VPN_1.3.6.1.2.1.10.166.11.0.2 mplsL3VpnVrfDown

Description

The interface bound to the VPN instance went Down. (VpnInstanceName=[VpnInstanceName], IfName=[IfName], IfCurRowStatus=[IfCurRowStatus], VRFOperationStatus=[VRFOperationStatus])

Of the interfaces that are bound to VPN instance, the last interface in the Up state goes Down.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

L3VPN_MIB_TRAP_VRF_DOWN

Trap OID

1.3.6.1.2.1.10.166.11.0.2

Alarm ID

0x09110000

Alarm Type

communicationsAlarm

Raise or Clear

Raise

Match trap

L3VPN_1.3.6.1.2.1.10.166.11.0.1 mplsL3VpnVrfUp

Parameters

Name

Meaning

VpnInstanceName

Indicates the name of the VPN.

IfName

Indicates the name of the interface.

IfCurRowStatus

Indicates the row status of the interface. Including:

  • 1: Active
  • 2: Not in Service
  • 3: Not Ready
  • 4: Create and Go
  • 5: Create and Wait
  • 6: Destroy

VRFOperationStatus

Indicates the status of the VRF. Including:

  • 1: Up
  • 2: Down
VB

VB OID

VB Name

VB Index

1.3.6.1.2.1.10.166.11.1.2.1.1.5

mplsL3VpnIfConfRowStatus

mplsL3VpnVrfName;

mplsL3VpnIfConfIndex;

1.3.6.1.2.1.10.166.11.1.2.2.1.6

mplsL3VpnVrfOperStatus

mplsL3VpnVrfName;

Impact on the System

No available interface is bound with the VPN instance.

Possible Causes

1. One interface was bound with the VPN instance, and the interface status changed from Up to Down.

2. Multiple interfaces were bound with the VPN instance; the status of all the interfaces changed from Up to Down; the last interface in the Up state went Down.

3. The last interface with Up state is disassociated from the VPN instance.

Procedure
  1. Run the display ip vpn-instance verbose vpn-instance-name command to check which interfaces are bound with the VPN instance.
  • If no interface is bound with the VPN instance, search the log file and find whether there is a log message containing the keywords "undo ip binding vpn-instance" and generated with the alarm.
    • If so, and the VPN instance should be unbound, the problem is resolved, go to step 6. If the VPN instance cannot be unbound, run the ip binding vpn-instance vpn-instance-name command in the interface view to bound the interface with the VPN instance, and then run ip adress ipv4-address command to configure IP address for the interface.
  • If the L3VPN_1.3.6.1.2.1.10.166.11.0.1 mplsL3VpnVrfUp of this VPN instance appears later, the problem is resolved, go to step 6.
  • If not, go to step 5.
    • If there is not the relative log, go to step 5.
  • If there are some interfaces bound with the VPN instance, go to Step 2.
  1. Run the display ip interface brief command to check whether there are one or more interfaces bound with the VPN instance and in Up state.

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

  2. Check whether the interfaces are configured with IP addresses.

    • If so, go to Step 4.
    • If not, run ip adress ipv4-address comand to configure IP addresses for the interfaces if necessary. Then,
      • If the L3VPN_1.3.6.1.2.1.10.166.11.0.1 mplsL3VpnVrfUp of this VPN instance appears later, the problem is resolved, go to step 6.
      • If not, go to step 4.

  3. Run the display this command in the interface view to check whether the interfaces are shut down.

    • If so, run the undo shutdown command on the interfaces if necessary. Then,
      • If the L3VPN_1.3.6.1.2.1.10.166.11.0.1 mplsL3VpnVrfUp of this VPN instance appears later, the problem is resolved, go to step 6.
      • If not, go to step 5.
    • If all the interfaces are not shut down, go to Step 5.

  4. Collect the trap information, log information, and configuration information, and contact technical personnel.
  5. End.
Related Information

L3VPN_1.3.6.1.2.1.10.166.11.0.1 mplsL3VpnVrfUp

L3VPN_1.3.6.1.2.1.10.166.11.0.3 mplsL3VpnVrfRouteMidThreshExceeded

Description

The number of prefixes in the VPN instance exceeded the middle threshold. (VpnInstanceName=[VpnInstanceName], VpnInstanceRouteCount=[VpnInstanceRouteCount], MidThresholdValue=[MidThresholdValue])

The number of public network route prefixes exceeded the middle threshold set by using the ip prefix-limit number alert-percent [ route-unchanged ] command.

The number of route prefixes contained by the specified VPN exceeded the middle threshold set by using the prefix limit number alert-percent [ route-unchanged ] command.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Warning

Mnemonic Code

L3VPN_MIB_TRAP_MID_THRESH_EXCEED

Trap OID

1.3.6.1.2.1.10.166.11.0.3

Alarm ID

0x09110002

Alarm Type

qualityOfServiceAlarm

Raise or Clear

Raise

Match trap

L3VPN_1.3.6.1.4.1.2011.5.25.177.1.3.8 hwL3vpnVrfRouteMidThreshCleared

Parameters

Name

Meaning

VpnInstanceName

Indicates the name of a VPN instance.

NOTE:

If a VPN instance name is "_public_", the alarm cause is that the number of public network route prefixes exceeds or is about to exceed the maximum limit.

VpnInstanceRouteCount

Indicates the number of existing route prefixes.

MidThresholdValue

Indicates that the alarm threshold of route prefixes.

VB

VB OID

VB Name

VB Index

1.3.6.1.2.1.10.166.11.1.3.1.1.3

mplsL3VpnVrfPerfCurrNumRoutes

N/A

1.3.6.1.2.1.10.166.11.1.2.2.1.9

mplsL3VpnVrfConfMidRteThresh

mplsL3VpnVrfName;

Impact on the System

When the total number of public network route prefix exceeds the alarm threshold, routes can still be installed to the routing table. That is, the routes are not discarded and traffic is not interrupted for the moment.

When the total number of VPN route prefixes exceeds the alarm threshold, routes can still be installed to the routing table. That is, the routes are not discarded and traffic is not interrupted for the moment.

Possible Causes

1.The total number of public network route prefixes exceeds the alarm threshold of public route prefixes specified in the ip prefix-limit command, and is smaller than the maximum number of route prefixes.

2.The total number of the VPN route prefixes in the VPN routing table exceeds the alarm threshold of VPN route prefixes specified in the prefix limit command, and is smaller than the maximum number of route prefixes.

Procedure
  • Cause 1. The total number of public network route prefixes exceeds the alarm threshold of public route prefixes specified in the ip prefix-limit command, and is smaller than the maximum number of route prefixes.
    1. Run the display ip routing-table limit command to check whether the number of public network route prefixes exceeds the upper limit.
    2. Run the display ip routing-table statistics command to check whether the number of existing public network route prefixes meets the requirements.
      • If so, go to Step 4.
      • If not, go to Step 3.
    3. Check whether the number of route prefixes still exceeds the alarm threshold after redundant public routes are deleted.
      • If so, go to Step 5.
      • If not, go to Step 6.
    4. In the system view and run the display this command to view the configuration of the ip prefix-limit command. Then, check whether the set alarm threshold of public routes is proper.
      • If so, go to Step 5.
      • If not, run the ip prefix-limit number { alert-percent | simply-alert } command to set a proper alarm threshold of route prefixes. Then, go to Step 6.
    5. Collect the trap information, log information, and configuration information, and contact technical personnel.
    6. End.
  • Cause 2. The total number of the VPN route prefixes in the VPN routing table exceeds the alarm threshold of VPN route prefixes specified in the prefix limit command, and is smaller than the maximum number of route prefixes.
    1. Run the display ip routing-table limit vpn-instance vpn-instance-name command to check whether the number of route prefixes in the VPN instance exceeds the upper limit.
    2. Run the display ip routing-table vpn-instance vpn-instance-name statistics command to check whether the number of existing route prefixes in the VPN instance meets the requirements.
      • If so, go to Step 4.
      • If not, go to Step 3.
    3. Check whether the number of route prefixes still exceeds the alarm threshold after redundant VPN routes are deleted.
      • If so, go to Step 5.
      • If not, go to Step 6.
    4. Enter the VPN instance view and run the display this command to view the configuration of the prefix limit command. Then, check whether the set alarm threshold of VPN routes is proper.
      • If so, go to Step 5.
      • If not, run the prefix limit number { alert-percent | simply-alert } command to set a proper alarm threshold of route prefixes. Then, go to Step 6.
    5. Collect the trap information, log information, and configuration information, and contact technical personnel.
    6. End.
Related Information

L3VPN_1.3.6.1.4.1.2011.5.25.177.1.3.8 hwL3vpnVrfRouteMidThreshCleared

L3VPN_1.3.6.1.2.1.10.166.11.0.4 mplsL3VpnVrfNumVrfRouteMaxThreshExceeded

Description

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

The number of public network route prefixes exceeded the maximum limit specified using the ip prefix-limit command.

The number of VPN route prefixes in the VPN instance exceeded the maximum limit specified using the prefix limit command.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

L3VPN_MIB_TRAP_THRESH_EXCEED

Trap OID

1.3.6.1.2.1.10.166.11.0.4

Alarm ID

0x09110001

Alarm Type

qualityOfServiceAlarm

Raise or Clear

Raise

Match trap

L3VPN_1.3.6.1.2.1.10.166.11.0.6 mplsL3VpnNumVrfRouteMaxThreshCleared

Parameters

Name

Meaning

VpnInstanceName

Indicates the name of a VPN instance.

NOTE:

If a VPN instance name is "_public_", the alarm cause is that the number of public network route prefixes exceeds the maximum limit.

VpnInstanceRouteCount

Indicates the number of existing route prefixes.

MaxValue

Indicates that the maximum number of route prefixes allowed.

VB

VB OID

VB Name

VB Index

1.3.6.1.2.1.10.166.11.1.3.1.1.3

mplsL3VpnVrfPerfCurrNumRoutes

N/A

1.3.6.1.2.1.10.166.11.1.2.2.1.10

mplsL3VpnVrfConfHighRteThresh

mplsL3VpnVrfName;

Impact on the System

If the number of public network route prefixes exceeds the maximum limit:

No public network route prefixes can be added. As a result, some public network routes will be discarded and some traffic cannot be forwarded.

If the number of VPN route prefixes in the VPN instance exceeds the maximum limit:

No more VPN route prefixes can be added. As a result, some VPN routes will be discarded and some traffic cannot be forwarded.

Possible Causes

1. The number of public network route prefixes in the public network routing table exceeded the maximum limit specified using the ip prefix-limit command.

2. The number of VPN route prefixes in the VPN instance exceeded the maximum limit specified in the license or specified using the prefix limit command.

Procedure
  • Cause 1: The number of public network route prefixes in the public network routing table exceeded the maximum limit.
    1. Run the display ip routing-table limit command to check the maximum limit for public network route prefixes.
    2. Run the display ip routing-table statistics command to check whether the number of existing public network route prefixes exceeds the maximum limit.
      • If so, go to Step 4.
      • If not, go to Step 3.
    3. Check whether the number of public network route prefixes exceeds the maximum limit after deleting excess public network routes.
      • If so, go to Step 5.
      • If not, go to Step 6.
    4. In the system view, run the display this command to check whether the ip prefix-limit command configuration is appropriate.
      • If so, go to Step 5.
      • If not, run the ip prefix-limit number { alert-percent [ route-unchanged ] | simply-alert } command to set an appropriate maximum limit for public network route prefixes. Then, go to Step 6.
    5. Collect the trap information, log information, and configuration information, and contact technical personnel.
    6. End.
  • Cause 2: The number of VPN route prefixes in the VPN instance exceeded the maximum limit.
    1. Run the display ip routing-table limit vpn-instance vpn-instance-name command to check whether the number of VPN route prefixes in the VPN instance exceeds the upper limit.
    2. Run the display ip routing-table vpn-instance vpn-instance-name statistics command to check whether the number of existing VPN route prefixes in the VPN instance meets the requirements.
      • If so, go to Step 4.
      • If not, go to Step 3.
    3. Check whether the number of VPN route prefixes still exceeds the maximum limit specified in the license or specified using the prefix limit command after deleting excess VPN routes.
      • If so, go to Step 5.
      • If not, go to Step 6.
    4. Enter the VPN instance view and run the display this command to check the configuration of the prefix limit command. Check whether the maximum limit for VPN route prefixes is appropriate.
      • If so, go to Step 5.
      • If not, run the prefix limit number { alert-percent | simply-alert } command to set an appropriate maximum limit for VPN route prefixes. Then, go to Step 6.
    5. Collect the trap information, log information, and configuration information, and contact technical personnel.
    6. End.
Related Information

L3VPN_1.3.6.1.2.1.10.166.11.0.6 mplsL3VpnNumVrfRouteMaxThreshCleared

L3VPN_1.3.6.1.2.1.10.166.11.0.6 mplsL3VpnNumVrfRouteMaxThreshCleared

Description

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

The number of public network route prefixes fell below the maximum limit specified using the ip prefix-limit command.

The number of VPN route prefixes in the VPN instance fell below the maximum limit specified using the prefix limit command.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Critical

Mnemonic Code

L3VPN_MIB_TRAP_THRESH_CLEARED

Trap OID

1.3.6.1.2.1.10.166.11.0.6

Alarm ID

0x09110001

Alarm Type

qualityOfServiceAlarm

Raise or Clear

Raise

Match trap

L3VPN_1.3.6.1.2.1.10.166.11.0.4 mplsL3VpnVrfNumVrfRouteMaxThreshExceeded

Parameters

Name

Meaning

VpnInstanceName

Indicates the name of a VPN instance.

NOTE:

If a VPN instance name is "_public_", the alarm cause is that the number of public network route prefixes exceeds or is about to exceed the maximum limit.

VpnInstanceRouteCount

Indicates the number of existing route prefixes.

MaxValue

Indicates the maximum number of route prefixes allowed.

VB

VB OID

VB Name

VB Index

1.3.6.1.2.1.10.166.11.1.3.1.1.3

mplsL3VpnVrfPerfCurrNumRoutes

N/A

1.3.6.1.2.1.10.166.11.1.2.2.1.10

mplsL3VpnVrfConfHighRteThresh

mplsL3VpnVrfName;

Impact on the System

After the number of public network route prefixes fell below the maximum limit, public network routes can be received normally.

After the number of VPN route prefixes fell below the maximum limit, VPN routes can be received normally.

Possible Causes

1. The number of public network route prefixes reached the maximum limit, and then it fell below the maximum limit.

2. The maximum limit for public network route prefixes was adjusted higher using the ip prefix-limit command.

3. The number of VPN route prefixes reached the maximum limit, and then it fell below the maximum limit.

4. The maximum limit for VPN route prefixes was adjusted higher using the prefix limit command.

Procedure
  • This alarm message is informational only, and no action is required.
Related Information

L3VPN_1.3.6.1.2.1.10.166.11.0.4 mplsL3VpnVrfNumVrfRouteMaxThreshExceeded

L3VPN_1.3.6.1.4.1.2011.5.25.177.1.3.8 hwL3vpnVrfRouteMidThreshCleared

Description

The number of prefixes in the VPN instance fell below the middle threshold. (VpnInstanceName=[VpnInstanceName], VpnInstanceRouteCount=[VpnInstanceRouteCount], MidThresholdValue=[MidThresholdValue])

The number of public network route prefixes fell below the middle threshold set by using the ip prefix-limit number alert-percent [ route-unchanged ] command.

The number of route prefixes in a VPN instance fell below the middle threshold set by using the prefix limit number alert-percent [ route-unchanged ] command.

Attributes

Attribute

Description

Alarm or Event

Alarm

Trap Severity

Warning

Mnemonic Code

L3VPN_MIB_TRAP_MID_CLEARED

Trap OID

1.3.6.1.4.1.2011.5.25.177.1.3.8

Alarm ID

0x09110002

Alarm Type

qualityOfServiceAlarm

Raise or Clear

Clear

Match trap

L3VPN_1.3.6.1.2.1.10.166.11.0.3 mplsL3VpnVrfRouteMidThreshExceeded

Parameters

Name

Meaning

VpnInstanceName

Indicates the name of a VPN instance.

NOTE:

If a VPN instance name is "_public_", the alarm cause is that the number of public network route prefixes exceeds or is about to exceed the maximum limit.

VpnInstanceRouteCount

Indicates the number of existing routes or prefixes.

MidThresholdValue

Indicates that the alarm threshold of routes or prefixes.

VB

VB OID

VB Name

VB Index

1.3.6.1.2.1.10.166.11.1.3.1.1.3

mplsL3VpnVrfPerfCurrNumRoutes

N/A

1.3.6.1.2.1.10.166.11.1.2.2.1.9

mplsL3VpnVrfConfMidRteThresh

mplsL3VpnVrfName;

Impact on the System

After the number of route prefixes falls below the ip prefix-limit value, a device can normally receive routes.

After the number of route prefixes falls below the prefix limit value, a device can normally receive routes.

Possible Causes

The number of public network route prefixes fell below the threshold specified in the ip prefix-limit command.

The total number of VPN prefixes in the VPN routing table fell below the threshold specified in the prefix limit command.

Procedure
  • This trap message is informational only, and no action is required.
Related Information

L3VPN_1.3.6.1.2.1.10.166.11.0.3 mplsL3VpnVrfRouteMidThreshExceeded

Translation
Download
Updated: 2018-08-16

Document ID: EDOC1000015902

Views: 210869

Downloads: 1591

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