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

L3VPN

L3VPN_1.3.6.1.2.1.10.166.11.0.1 mplsL3VpnVrfUp

Description

L3VPN/2/L3V_TRAP_VRF_UP:OID [oid] The interface bound to the VPN instance went Up. (VpnInstanceName=[octet], IfIndex=[integer], BindingVpnInstanceName=[octet], IfCurRowStatus=[integer], VRFOperationStatus=[integer], IfName=[octet])

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

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.2.1.10.166.11.0.1

Major

communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VpnInstanceName

Indicates the name of the VPN.

IfIndex

Indicates the index of the interface.

BindingVpnInstanceName

Indicates the name of the binding VPN .

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

IfName

Indicates the name of the interface.

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 the status of the first interface bound with the VPN instance changed from Down to Up.

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, all the interfaces went Down, and then the first interface went Up.

Procedure

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

Related Information

None

L3VPN_1.3.6.1.2.1.10.166.11.0.2 mplsL3VpnVrfDown

Description

L3VPN/2/L3V_TRAP_VRF_DOWN: OID [oid] The interface bound to the VPN instance went Down. (VpnInstanceName=[octet], IfIndex=[integer], BindingVpnInstanceName=[octet], IfCurRowStatus=[integer], OperationStatus=[integer], IfName=[octet])

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

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.2.1.10.166.11.0.2

Major

communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VpnInstanceName

Indicates the name of the VPN.

IfIndex

Indicates the index of the interface.

BindingVpnInstanceName

Indicates the name of the binding VPN.

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

OperationStatus

Indicates the status of the VRF. Including:

  • 1: Up

  • 2: Down

IfName

Indicates the name of the interface.

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 address ipv4-address command to configure IP address for the interface.
      • 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.

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

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

    • If so, go to Step 4.
    • If not, run ip address ipv4-address command to configure IP addresses for the interfaces if necessary. Then,

  4. 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 all the interfaces are not shut down, go to Step 5.

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

L3VPN_1.3.6.1.2.1.10.166.11.0.3 mplsL3VpnVrfRouteMidThreshExceeded

Description

L3VPN/4/L3V_TRAP_MID_EXCEED:OID [oid] The number of routes in the VPN instance exceeded the middle threshold. (VpnInstanceName=[octet], VpnInstanceRouteCount=[gauge], MidThresholdValue=[gauge])

The number of routes contained by the specified VRF exceeds the value indicated by mplsL3VpnVrfMidRouteThreshold.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.2.1.10.166.11.0.3

Warning

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VpnInstanceName

Indicates the name of a VPN instance.

VpnInstanceRouteCount

Indicates the number of existing routes or prefixes.

MidThresholdValue

Indicates that the alarm threshold of routes or prefixes.

Impact on the System

When the total number of VPN routes or 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 the VPN routes in the VPN routing table exceeds the alarm threshold of VPN routes specified in the routing-table limit command, and is smaller than the maximum number of routes.

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

  1. Run the display ip routing-table limit vpn-instance vpn-instance-name command to check whether the number of routes or prefixes in the VPN instance exceeds the upper limit.
  2. Analyze the source of each route and check whether the number of existing routes or 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 routes or 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 routing-table limit command and 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 routing-table limit number { alert-percent | simply-alert } or prefix limit number { alert-percent | simply-alert } command to set a proper alarm threshold of routes or prefixes. Then, go to Step 6.

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

Related Information

None.

L3VPN_1.3.6.1.2.1.10.166.11.0.4 mplsL3VpnVrfNumVrfRouteMaxThreshExceeded

Description

L3VPN/2/L3V_TRAP_THRE_EXCEED:OID [oid] The number of routes in the VPN instance exceeded the maximum value. (VpnInstanceName=[octet], VPNInstanceRouteCount=[gauge], MaxValue=[gauge])

The number of routes contained by the specified VRF exceeds or attempts to exceed the maximum allowed value as indicated by mplsVrfMaxRouteThreshold.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.2.1.10.166.11.0.4

Major

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VpnInstanceName

Indicates the name of the VPN instance.

VPNInstanceRouteCount

Indicates the number of current routes.

MaxValue

Indicates that the maximum value of routes or prefixes.

Impact on the System

The number of private routes or prefixes exceeds the maximum value, and no routes or prefixes can be added. As a result, routes will be discarded and some traffic cannot be forwarded.

Possible Causes

1. The total number of the VPN routes in the VPN routing table exceeded the upper limit specified in the License or exceeded the maximum value specified in the routing-table limit command.

2. The total number of the VPN route prefixes in the VPN routing table exceeded the upper limit specified in the License or exceeded the maximum value specified in the prefix limit command.

Procedure

  1. Run the display ip routing-table limit vpn-instance vpn-instance-name command to check whether the number of routes or prefixes in the VPN instance exceeds the upper limit.
  2. Analyze the source of each route and check whether the number of existing routes or 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 routes or prefixes still exceeds the maximum value 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 routing-table limit number { alert-percent | simply-alert } command and the prefix limit command. Then, check whether the set maximum value of VPN routes is proper.

    • If so, go to Step 5.

    • If not, run the routing-table limit number { alert-percent | simply-alert } command or the prefix limit number { alert-percent | simply-alert } command to set a proper maximum value of routes or prefixes. Then, go to Step 6.

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

L3VPN_1.3.6.1.2.1.10.166.11.0.6 mplsL3VpnNumVrfRouteMaxThreshCleared

Description

L3VPN/2/L3V_TRAP_THRE_CLEARED:OID [oid] The number of routes in the VPN instance fell below the maximum value. (VpnInstanceName=[octet], VPNInstanceRouteCount=[gauge], MaxValue=[gauge])

The number of routes contained by the specified VRF exceeds the maximum allowed value as indicated by mplsVrfMaxRouteThreshold and then falls below this value.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.2.1.10.166.11.0.6

Major

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VpnInstanceName

Indicates the name of the VPN.

VPNInstanceRouteCount

Indicates the number of current routes.

MaxValue

Indicates that the maximum value of routes or prefixes.

Impact on the System

The number of private routes or prefixes falls below the maximum value, and routes can be received and sent normally.

Possible Causes

1. The number of VRF routes reached the maximum value, and then it fell below the maximum value.

2. The number of VRF prefixes reached the maximum value, and then it fell below the maximum value.

3. The maximum number of VRF routes increases after the routing-table limit command is run for the VPN instance routing table.

4. The maximum number of VRF route prefixes increases after the prefix limit command is run for the VPN instance routing table.

Procedure

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

Related Information

None.

L3VPN_1.3.6.1.4.1.2011.5.25.177.8.1 hwTnl2VpnTrapEvent

Description

L3VPN/4/L3V_TRAP_TUNNEL_UPDOWN_EVENT:OID [oid] The tunnel up/down event is occurred. (VpnIndex=[gauge], NextHop=[ipaddr], Ckey=[gauge], TrapType=[gauge])

The status of the tunnel used by a VPN changed.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.177.8.1

Warning

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VpnIndex

Indicates the index of the VPN instance.

NextHop

Indicates the next hop address of the public network.

TrapType

Indicates the trap type:
  • 1: indicates that a tunnel goes Up.
  • 2: indicates that a tunnel goes Down.

Ckey

Indicates the Ckey value, which is used to obtain information about the current iterated tunnel.

Impact on the System

The VPN services of the VPN instance with the specified index will be restored or interrupted.

Possible Causes

1. The status of the tunnel currently used by VPN services changed from reachable to unreachable or from unreachable to reachable.

2. During the tunnel switchover for VPN services, the result of tunnel iteration changed from success (a tunnel is iterated) to failure (a tunnel fails to be iterated); or the opposite.

Procedure

  1. Run the display ip vpn-instance vpn-instance-name verbose command in the VPN instance view to check whether the tnl-policy field exists.

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

  2. Run the display tunnel-policy tunnel-policy-name command to check the contents of the tunnel policy.

    • If the tunnel policy is the select-sequence policy, run the display tunnel-info all command to check whether there is a tunnel of the type configured in the tunnel policy.
      • If so, go to Step 4.
      • If not, change the tunnel policy used by VPN services.
    • If the tunnel policy is the tunnel binding policy, run the display interface tunnel command to check whether the bound tunnel interface in the tunnel policy is Up.
      • If so, go to Step 4.
      • If not, check the configuration on the TE interface.

  3. Run the display tunnel-info all command to check whether an LSP tunnel exists.

    • If so, go to Step 4.
    • If not, check the configuration of the LSP tunnel (LDP LSP, BGP LSP, or static LSP).

  4. Collect alarm information and configuration information, and then contact technical support personnel.
  5. End.
Translation
Download
Updated: 2019-04-09

Document ID: EDOC1100065855

Views: 3446

Downloads: 2

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