No relevant resource is found in the selected language.
Enterprise
Worldwide
Search
Support Documentation
S1700, S2720, S5700, and S6700 V200R019C10 Alarm Handling

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

LSPM

LSPM_1.3.6.1.2.1.10.166.2.0.1 mplsXCUp

Description

LSPM/4/MPLSXCUP:OID [oid] LSP went Up. (BeginLspIndex=[octet].[octet].[octet], EndLspIndex=[octet].[octet].[octet])

A trap was generated when the LSP went Up.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.2.1.10.166.2.0.1

Warning

 communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

BeginLspIndex

Indicates the index of the starting LSP, which is expressed in the format of [index of the starting LSP].[index of the inbound interface on the starting LSP].[index of the outbound interface on the starting LSP].

EndLspIndex

Indicates the index of the ending LSP, which is expressed in the format of [index of the ending LSP].[index of the inbound interface on the ending LSP].[index of the outbound interface on the ending LSP].

Impact on the System

Services will not be affected.

Possible Causes

The LSP was created successfully.

Procedure

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

Related Information

LSPM_1.3.6.1.2.1.10.166.2.0.2 mplsXCDown

LSPM_1.3.6.1.2.1.10.166.2.0.2 mplsXCDown

Description

LSPM/4/MPLSXCDOWN:OID [oid] LSP went Down. (BeginLspIndex=[octet].[octet].[octet], EndLspIndex=[octet].[octet].[octet])

A trap was generated when the LSP went Down.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.2.1.10.166.2.0.2

Warning

 communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

BeginLspIndex

Index of the starting LSP, which is expressed in the format of [index of the starting LSP].[index of the inbound interface on the starting LSP].[index of the outbound interface on the starting LSP].

EndLspIndex

Index of the ending LSP, which is expressed in the format of [index of the ending LSP].[index of the inbound interface on the ending LSP].[index of the outbound interface on the ending LSP].

Impact on the System

1. If the protection function, such as FRR, is configured, services will not be affected.

2. If the protection function is not configured, all the services to be forwarded through the LSP will be interrupted.

Possible Causes

  • The interface went Down.

  • LDP LSPs went Down.

  • Static LSPs went Down.

  • In the case that the LDP LSP or BGP LSP was set Up, routes changed; or, in the case that the static LSP was bound to the tunnel, the next hop configured for the static LSP was inconsistent with the next hop in the routing table after routes changed.

  • The link was faulty.

Procedure

  1. If the snmp-agent trap enable feature-name mpls_lspm trap-name is run and the trap functions indicating the status of LSPs are enabled in the LSPM, you can check the traps to obtain the types of the LSPs that go Down. If no trap functions indicating the status of LSPs are enabled in the LSPM, you can check the values of the BeginLspIndex and EndLspIndex fields in the traps to obtain the types of the LSPs that go Down. (Run the display mpls entry summary command in the diagnostic view to view the index ranges of LSPs of different protocols of the MPLS module.)

  2. Collect the trap information, log information, and configuration of the switch, and Collect alarm information and configuration information, and then contact technical support personnel.
  3. End.

Related Information

LSPM_1.3.6.1.2.1.10.166.2.0.1 mplsXCUp

LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp

Description

LSPM/2/MPLSTUNNELUP:OID [oid] Tunnel Changes to Up.(SessionTunnelId=[integer], LocalLspId=[integer], IngressLsrId=[integer], EgressLsrId=[integer], OutIfIndex=[integer], mplsTunnelAdminStatus=[integer], mplsTunnelOperStatus=[integer], mplsTunnelIfName=[octet], OutIfName=[octet], mplsTunnelDownReason=[integer])

A trap was generated when a tunnel was established successfully and was Up.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.2.1.10.166.3.0.1

Major

communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

SessionTunnelId

Indicates the ID of the tunnel.

LocalLspId

Indicates the LSP ID of a session.

IngressLsrId

Indicates the LSR ID of the ingress on the tunnel.

EgressLsrId

Indicates the LSR ID of the egress on the tunnel.

OutIfIndex

Indicates the outgoing interface index of the ingress of the LSP that goes Up.

mplsTunnelAdminStatus

Indicates the management status of the tunnel.

  • 1: Up
  • 2: Down

mplsTunnelOperStatus

Indicates the operating status of the tunnel:

  • 1: Up
  • 2: Down

mplsTunnelIfName

Indicates the name of a tunnel.

OutIfName

Indicates the name of the outgoing interface on the ingress of the LSP that goes Up.

mplsTunnelDownReason
Indicates the reason of Tunnel down.

  • 1: other

  • 2: staticLspDown

  • 3: staticCrlspDown

  • 4: outIfDown

  • 5: resourcePreempted

  • 6: rsvpMessageTimeout

  • 7: rsvpNbrLost

  • 8: bypassTunnelDownOrUnbinded

  • 100: clear

Impact on the System

Services will not be affected.

Possible Causes

The tunnel was created successfully.

Procedure

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

Related Information

LSPM_1.3.6.1.2.1.10.166.3.0.2 mplsTunnelDown

LSPM_1.3.6.1.2.1.10.166.3.0.2 mplsTunnelDown

Description

LSPM/2/MPLSTUNNELDOWN:OID [oid] Tunnel Changes to Down.(SessionTunnelId=[integer], LocalLspId=[integer], IngressLsrId=[integer], EgressLsrId=[integer], OutIfIndex=[integer], mplsTunnelAdminStatus=[integer], mplsTunnelOperStatus=[integer], mplsTunnelIfName=[octet], OutIfName=[octet], mplsTunnelDownReason=[integer])

A trap was generated when the current tunnel became faulty and went Down.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.2.1.10.166.3.0.2

Major

 communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

SessionTunnelId

ID of the tunnel

LocalLspId

LSP ID of a session.

IngressLsrId

LSR ID of the ingress on the tunnel

EgressLsrId

LSR ID of the egress on the tunnel

OutIfIndex

Outbound interface index of the ingress of the LSP that goes Down.

mplsTunnelAdminStatus
Management status of the tunnel:
  • 1: Up
  • 2: Down

mplsTunnelOperStatus
Operating status of the tunnel:
  • 1: Up
  • 2: Down

mplsTunnelIfName

Name of a tunnel

OutIfName

Name of the outgoing interface on the ingress of the LSP that goes Down.

mplsTunnelDownReason
Reason of Tunnel down.

  • 1: other

  • 2: staticLspDown

  • 3: staticCrlspDown

  • 4: outIfDown

  • 5: resourcePreempted

  • 6: rsvpMessageTimeout

  • 7: rsvpNbrLost

  • 8: bypassTunnelDownOrUnbinded

  • 100: clear

Impact on the System

The service traffic to be forwarded through the tunnel will be interrupted.

Possible Causes

1. The interface was Down.

2. In the case that the static LSP was bound to the tunnel, the next hop configured for the static LSP was inconsistent with the next hop in the routing table after routes changed.

3. The link was faulty.

Procedure

  1. Run the display mpls te tunnel-interface tunnel-name command on the ingress (that is, the node that generates the trap) to check the configurations of the tunnel. View the Tunnel State Desc field to check whether the tunnel is in the Down state. Then, run the display mpls te tunnel-interface last-error command to view the prompt.

    • In the case of the following error prompts, do as required:
      • If the error prompt is "Cspf failed to calculate a path for Tunnel." (indicating that the ingress is enabled with CSPF, but the CSPF path calculation fails), go to Step 2.
      • If the error prompt is "Trigger Rsvp failed", go to Step 2.
      • If the error prompt is "One LSP is deleted at smooth period", go to Step 6.
      • If the error prompt is "One LSP is deleted at Tunnel aging period", go to Step 6.
      • For other types of errors, go to Step 6.
    • If there is no error prompt, go to Step 2.

  2. Run the ping command on the ingress to check whether the destination IP address of the tunnel can be pinged.

    • If the ping fails, rectify the route fault to ensure that the destination IP address of the tunnel can be pinged, and then check whether the alarmLSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp is generated.
      • If so, go to Step 7.
      • If not, go to Step 3.
    • If the ping is successful, go to Step 3.

  3. Run the display this command in the MPLS view of the ingress to check whether the mpls te cspf command is configured, that is, to check whether the CSPF is enabled.

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

  4. Run the display mpls te cspf destination command on the ingress to check for paths that satisfy specified constraints. If such paths exist, the path of the TE tunnel is displayed, indicating CSFP path computation is successful. If the output is empty, CSFP path computation fails.

    • If CSFP path computation is successful, perform the following operations to confirm tunnel configurations:
      • Run the display current-configuration interface interface-type interface-number command on the ingress to view configurations.
      • Check whether mpls te auto-frr command is run in the MPLS view. If this command exists, automatic protection is enabled. Check the tunnel configuration and find the primary tunnel. If this command does not exist, check the mpls te fast-reroute, mpls te record-route, mpls te bypass-tunnel command configurations to determine the primary and backup tunnels.
      • Check whether the explicit-path command is run to configure an explicit path.
      • Check whether the mpls te affinity property command is run to configure affinities.
      • Check whether the mpls te bandwidth command is run to configure bandwidth values.
      Run the display mpls te cspf destination command with constraints specified based on tunnel configurations. The parameters include priority setup-priority, bandwidth, explicit-path path-name, affinity properties, and hop-limit hop-limit-number. Then check whether the path that satisfies the constraints exists. If such paths exist, the path of the TE tunnel is displayed, indicating CSFP path computation is successful. If the output is empty, CSFP path computation fails.
      1. If CSPF fails to use an explicit path to compute a path, check whether the interfaces along the explicit path are Up and check whether MPLS and MPLS TE are enabled on the interfaces. If CSPF path computation is successful, check whether affinities and bandwidth values are successfully used to compute a path and whether the tunnel is established on the explicit path. Run the display mpls te cspf destination ip-address bandwidth ct0 ct0-bandwidth explicit-path path-name command.
      2. If affinities fail to be used to compute a path, run the mpls te affinity property command in the tunnel interface view to modify affinities and run the mpls te link administrative group command in the view of each interface along the path to modify the administrative group attribute.
      3. If the other constraints fail to be used to compute a path, go to Step 6.
      Check whether LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp is displayed.
      • If this alarm is generated, go to Step 7.
      • If this alarm is not generated, go to Step 5.
    • If path computation fails, go to Step 5.

  5. Run the display explicit-path command to check the interfaces along the tunnel. Then, run the display this command in the interface view of each interface of the tunnel to check whether the interface is enabled with MPLS, MPLS TE, and RSVP-TE.

    • If MPLS, MPLS TE, or RSVP-TE is not enabled, run the mpls, mpls te or mpls rsvp-te commands in the view of the interface.
    • If any interface along the tunnel is not in Up state, restart the interface. That is, run the shutdown and then undo shutdown commands in the interface view, or run the restart command in the interface view, or run the restart command in the interface view.
    Then, check whether the alarm LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp is generated.
    • If so, go to Step 7.
    • If not, go to Step 6.

  6. Collect the trap information, log information, and configuration of the switch, and Collect alarm information and configuration information, and then contact technical support personnel.
  7. End.

Related Information

LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp

LSPM_1.3.6.1.2.1.10.166.3.0.3 mplsTunnelRerouted

Description

LSPM/4/MPLSTUNNELREROUTED: OID [oid] Tunnel Re-routed.(SessionTunnelId=[integer], LocalLspId=[integer], IngressLsrId=[integer], EgressLsrId=[integer], MplsTunnelAdminStatus=[integer], MplsTunnelOperStatus=[integer])

A trap was generated when FRR switchover or FRR switchback was performed.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.2.1.10.166.3.0.3 Warning communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

SessionTunnelId

Indicates the ID of the tunnel.

LocalLspId

Indicates the local LSP ID of a tunnel.

IngressLsrId

Indicates the LSR ID of the ingress on the tunnel.

EgressLsrId

Indicates the LSR ID of the egress on the tunnel.

MplsTunnelAdminStatus
Indicates the management status of the tunnel.
  • 1: Up
  • 2: Down

MplsTunnelOperStatus
Indicates the operating status of the tunnel:
  • 1: Up
  • 2: Down

Impact on the System

Services will not be affected.

Possible Causes

1. FRR switchover was performed.

2. FRR switchback was performed.

Procedure

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

Related Information

None

LSPM_1.3.6.1.2.1.10.166.3.0.4 mplsTunnelReoptimized

Description

LSPM/4/MPLSTUNNELREOP: OID [oid] Tunnel Re-Optimized.(SessionTunnelId=[integer], LocalLspId=[integer], IngressLsrId=[integer], EgressLsrId=[integer], MplsTunnelAdminStatus=[integer], MplsTunnelOperStatus=[integer])

A trap was generated when the route of the tunnel was re-optimized successfully.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.2.1.10.166.3.0.4 Warning communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

SessionTunnelId

Indicates the ID of the tunnel.

LocalLspId

Indicates the local LSP ID of a tunnel.

IngressLsrId

Indicates the LSR ID of the ingress on the tunnel.

EgressLsrId

Indicates the LSR ID of the egress on the tunnel.

MplsTunnelAdminStatus
Indicates the management status of the tunnel.
  • 1: Up
  • 2: Down

MplsTunnelOperStatus
Indicates the operating status of the tunnel:
  • 1: Up
  • 2: Down

Impact on the System

Services will not be affected.

Possible Causes

The tunnel succeeded in re-selecting the optimal route.

Procedure

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

Related Information

None

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.1 hwMplsStaticLSPUp

Description

LSPM/2/STATICLSPUP:OID [oid] Static LSP went Up. (LspIndex=[octet], InSegmentIndex=[octet], OutSegmentIndex=[octet], OutIfIndex=[integer], LspName=[octet], LspStatus=[integer], OutIfName=[octet], InIfIndex=[octet], InIfName=[octet], DownReason=[integer])

The private trap message was output when the static LSP was in the Up state.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.121.2.1.1

Major

 environmentalAlarm(6)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

LspIndex

Indicates the index of the LSP.

InSegmentIndex

Indicates the inSegment index of a static LSP.

OutSegmentIndex

Indicates the outSegment index of a static LSP.

OutIfIndex

Indicates the outbound interface index of a static LSP.

LspName

Indicates the name of a static LSP.

LspStatus

Indicates the status of a static LSP.

OutIfName

Indicates the outbound interface name of a static LSP.

InIfIndex

Indicates the inbound interface index of a static LSP.

InIfName

Indicates the inbound interface name of a static LSP.

DownReason

Indicates the reason that the static LSP down.

Impact on the System

Services will not be affected.

Possible Causes

1. The interface was Up.

2. The next hop configured for the static LSP was consistent with the next hop in the routing table after routes changed.

3. The link was recovered or the new static LSPs were configured.

Procedure

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

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.2 hwMplsStaticLspDown

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.2 hwMplsStaticLSPDown

Description

LSPM/2/STATICLSPDOWN: OID [oid] Static LSP went Down. (LspIndex=[octet], InSegmentIndex=[octet], OutSegmentIndex=[octet], OutIfIndex=[integer], lspName=[octet], LspStatus=[integer], OutIfName=[octet], InIfIndex=[octet], InIfName=[octet], DownReason=[integer])

The private trap message was output when the static LSP was in the Down state.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.121.2.1.2

Major

 communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

LspIndex

Indicates the index of the LSP.

InSegmentIndex

Indicates the inSegment index of a static LSP.

OutSegmentIndex

Indicates the outSegment index of a static LSP.

OutIfIndex

Indicates the outbound interface index of a static LSP.

lspName

Indicates the name of a static LSP.

LspStatus

Indicates the status of a static LSP.

OutIfName

Indicates the outbound interface name of a static LSP.

InIfIndex

Indicates the inbound interface index of a static LSP.

InIfName

Indicates the inbound interface name of a static LSP.

DownReason

Indicates the reason that the static LSP down.

Impact on the System

If there is some service using this static LSP, the service is interrupted. If there is not any service using this static LSP, there is no impact.

Possible Causes

1. The interface was Down.

2. The next hop configured for the static LSP was inconsistent with the next hop in the routing table after routes changed.

3. The link was damaged.

Procedure

  1. Run the display mpls interface. If the trap is generated on the ingress of static LSPs, you need to check the information about only the outbound interface; if the trap is generated on the egress of static LSPs, you need to check the information about only the inbound interface; if the trap is generated on the transit of static LSPs, you need to check the information about both the inbound interface and the outbound interface. You need to check whether the corresponding interface is displayed in the command output, and whether the Status field of the interface is Up.

    • If the interface status is not Up, check the interface.

    • If the corresponding interface is not displayed in the command output, it indicates that MPLS is not enabled on the interface. In this case, you need to enable MPLS on the interface. Then, check whether the trap is cleared.

      • If so, go to Step 5.

      • If not, go to Step 2.

    • If the trap is generated on the ingress of static LSPs, go to Step 2.
    • If the trap is generated on the egress or transit of static LSPs, go to Step 4.

  2. Run the display ip routing-table ip-address mask command to check the routing information. Check whether the configured destination addresses, masks, outbound interfaces, and next hops of static LSPs are the same as those in the routing information. Note that if a static LSP is configured by specifying the outbound interface, the address of the outbound interface is used as the next hop. This configuration is used only in a small number of scenarios.

    • If so, go to Step 3.

    • If not, check the configuration of the static LSP route on the ingress and make it strictly match with the route in the RM. Then, check whether the trap is cleared.

      • If so, go to Step 5.

      • If not, go to Step 2.

  3. If the ingress is bound to the tunnel, run the display mpls interface command to check whether the TE Attr field is En. If not, it indicates that MPLS TE is not enabled on the interface. Run the display current-configuration interface interface-type interface-number command to check whether the corresponding tunnel is correctly configured.

    • If the MPLS TE is not enabled, enable MPLS TE on the interface.

    • Run the display current-configuration interface interface-type interface-number command to check whether the corresponding tunnel is correctly configured.
      • If the tunnel is not consistent with the destination address of the static LSP, you need to enter the corresponding tunnel view and run the destination command to modify the destination address of the tunnel.
      • After modifying the configuration of the tunnel, run the mpls te commit command to commit the modification.
      • If the signaling mode is not static, run the mpls te signal-protocol static command to modify the signaling mode of the tunnel.
      If neither preceding operations can locate the fault, go to Step 4.

  4. Collect the trap information, log information, and configuration of the switch, and Collect alarm information and configuration information, and then contact technical support personnel.
  5. End.

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.1 hwMplsStaticLspUp

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.3 hwMplsStaticCRLSPUp

Description

LSPM/2/STATICCRLSPUP: OID [oid] Static CR-LSP went Up. (LspIndex=[octet], InSegmentIndex=[octet], OutSegmentIndex=[octet], OutIfIndex=[integer], LspName=[octet], LspStatus=[integer], OutIfName=[octet], InIfIndex=[octet], InIfName=[octet], DownReason=[integer])

The private trap message was output when the static CR-LSP was in the Up state.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.121.2.1.3

Major

 communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

LspIndex

Indicates the index of the LSP.

InSegmentIndex

Indicates the inSegment index of an Up static LSP.

OutSegmentIndex

Indicates the outSegment index of an Up static LSP.

OutIfIndex

Indicates the outbound interface index of an Up static LSP.

LspName

Indicates the name of an Up static LSP.

LspStatus

Indicates the status of an Up static LSP.

OutIfName

Indicates the outbound interface name of an Up static LSP.

InIfIndex

Indicates the inbound interface index of an Up static LSP.

InIfName

Indicates the inbound interface name of an Up static LSP.

DownReason

Indicates the reason that the static LSP down.

Impact on the System

Services will not be affected.

Possible Causes

1. The interface was Up.

2. The link was recovered or the new static CR-LSPs were configured.

Procedure

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

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.4 hwMplsStaticCRLspDown

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.4 hwMplsStaticCRLSPDown

Description

LSPM/2/STATICCRLSPDOWN: OID [oid] Static CR-LSP went Down. (LspIndex=[octet], InSegmentIndex=[octet], OutSegmentIndex=[octet], OutIfIndex=[integer], LspName=[octet], LspStatus=[integer], OutIfName=[octet], InIfIndex=[octet], InIfName=[octet], DownReason=[integer])

The private trap message was output when the static CR-LSP was in the Down state.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.121.2.1.4

Major

communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

LspIndex

Index of the LSP.

InSegmentIndex

InSegment index of a static CR-LSP.

OutSegmentIndex

OutSegment index of a static CR-LSP.

OutIfIndex

Outbound interface index of a static CR-LSP.

LspName

Name of a static CR-LSP.

LspStatus

Status of a static CR-LSP.

OutIfName

Outbound interface name of a static CR-LSP.

InIfIndex

Inbound interface index of a static CR-LSP.

InIfName

Inbound interface name a static CR-LSP.

DownReason

Reason that the static CR-LSP down.

Impact on the System

If there is some service using the tunnel, the service is interrupted. If a backup path is used to protect the tunnel, the flow of the service is changed to the backup path. If there is not any service using the tunnel, there is no impact.

Possible Causes

1. The interface was Down.

2. The link was damaged.

Procedure

  1. Run the display mpls interface command. If the trap is generated on the ingress of static CR-LSPs, you need to check the information about only the outbound interface; if the trap is generated on the egress of static CR-LSPs, you need to check the information about only the inbound interface; if the trap is generated on the transit of static LSPs, you need to check the information about the outbound interface and inbound interface. You need to check whether the corresponding interface is displayed in the command output, whether the Status field of the interface is Up, and whether the TE Attr field is En.

    • If the interface status is not Up, check the interface.

    • If the MPLS or MPLS TE is not enabled, configure this function.

    • If the output is correct, go to Step 2.
    Then check whether the trap is cleared.

    • If the trap is cleared, go to Step 5.

    • If the trap is not cleared, go to Step 2.

  2. Run the display current-configuration interface tunnel interface-number command on the ingress to check whether the corresponding tunnel is correctly configured.

    • If the tunnel is not consistent with the destination address of the static CR-LSP, you need to enter the corresponding tunnel view and run the destination command to modify the destination address of the tunnel.

    • If the signaling mode is not cr-static, run the mpls te signal-protocol cr-static command to modify the signaling mode of the tunnel.

    • After modifying the configuration of the tunnel, run the mpls te commit command to commit the modification.

    • If neither preceding operations can locate the fault, go to Step 3.

  3. If the static CR-LSP is configured with the bandwidth attribute, run the display current-configuration interface interface-number command to check the maximal bandwidth and the maximal reservable bandwidth on the outbound interface.

    • If the available bandwidth of the outgoing interface is smaller than the bandwidth required by the static CR-LSP, you need to increase the bandwidth of the outgoing interface.

    • After modifying the configuration of the tunnel, run the mpls te commit command to commit the modification.

    • If neither preceding operations can locate the fault, go to Step 4.

    Then check whether the trap is cleared.

    • If the trap is cleared, go to Step 5.

    • If the trap is not cleared, go to Step 4.

  4. Collect the trap information, log information, and configuration of the switch, and Collect alarm information and configuration information, and then contact technical support personnel.
  5. End.

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.3 hwMplsStaticCRLspUp

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.5 hwMplsTeFrrProtAval

Description

LSPM/2/HWFRRPROTAVAL:OID [oid] The primary Tunnel has been protected by bypass Tunnel.(primary Tunnel index=[integer].[integer].[integer].[integer], bypass Tunnel index=[integer], inner label=[integer])

The trap message was sent when the bypass tunnel was bound to the primary tunnel.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.121.2.1.5

Major

 communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

primary Tunnel index

Indicates the index of the main tunnel.

bypass Tunnel index

Indicates the index of the bypass tunnel.

inner label

Indicates the inner label.

Impact on the System

Services will not be affected.

Possible Causes

The bypass tunnel was successfully bound to the primary tunnel.

Procedure

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

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.6 hwMplsTeFrrProtNotAval

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.6 hwMplsTeFrrProtNotAval

Description

LSPM/2/HWFRRPROTNOTAVAL:OID [oid] The primary Tunnel has been unbound by bypass Tunnel.(primary Tunnel index=[integer1].[integer2].[integer3].[integer4], bypass Tunnel index=[integer5])

The trap message was sent when the binding between the primary tunnel and the bypass tunnel was deleted.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.121.2.1.6

Major

 communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

primary Tunnel index

Indicates the index of the main tunnel.

bypass Tunnel index

Indicates the index of the bypass tunnel.

Impact on the System

The binding between the primary tunnel and the bypass tunnel is deleted. This causes traffic interruption once the working tunnel goes down.

Possible Causes

1. Configurations changed.

2. The protected tunnel went Down.

Procedure

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

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.5 hwMplsTeFrrProtAval

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.7 hwMplsTeFrrSwitch

Description

LSPM/3/MPLSTEFRRSWITCH:OID [oid] Tunnel switches.(SessionTunnelId=[integer], LocalLspId=[integer], IngressLsrId=[integer], EgressLsrId=[integer], MplsTunnelAdminStatus=[integer], MplsTunnelOperStatus=[integer], BypassSessionTunnelId=[integer], BypassLocalLspId=[integer], BypassIngressLsrId=[integer], BypassEgressLsrId=[integer])

The trap message was output when the primary tunnel was Down and the traffic was switched to the bypass tunnel.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.121.2.1.7

Minor

 communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

SessionTunnelId

ID of the tunnel

LocalLspId

Local LSP ID of a tunnel.

IngressLsrId

LSR ID of the ingress on the tunnel.

EgressLsrId

LSR ID of the egress on the tunnel

MplsTunnelAdminStatus
Management status of the tunnel:
  • 1: Up
  • 2: Down

MplsTunnelOperStatus
Operating status of the tunnel:
  • 1: Up
  • 2: Down

BypassSessionTunnelId

ID of the bypass session tunnel.

BypassLocalLspId

Local LSP ID of a bypass tunnel.

BypassIngressLsrId

LSR ID of the ingress on the bypass tunnel.

BypassEgressLsrId

LSR ID of the egress on the bypass tunnel.

Impact on the System

Services will not be affected.

Possible Causes

The node or the link protected by the bypass tunnel was Down.

Procedure

  1. Run the display mpls te tunnel-interface tunnel-name command on the ingress (that is, the node that generates the trap) to check the configurations of the tunnel. View the Tunnel State Desc field to check whether the tunnel is in the Down state. Then, run the display mpls te tunnel-interface last-error command to view the prompt.

    • In the case of the following error prompts, do as required:
      • If the error prompt is "Cspf failed to calculate a path for Tunnel." (indicating that the ingress is enabled with CSPF, but the CSPF path calculation fails), go to Step 2.
      • If the error prompt is "Trigger Rsvp failed", go to Step 2.
      • If the error prompt is "One LSP is deleted at smooth period", go to Step 6.
      • If the error prompt is "One LSP is deleted at Tunnel aging period", go to Step 6.
      • For other types of errors, go to Step 6.
    • If there is no error prompt, go to Step 2.

  2. Run the ping command on the ingress to check whether the destination IP address of the tunnel can be pinged.

    • If the ping fails, rectify the route fault to ensure that the destination IP address of the tunnel can be pinged, and then check whether the alarm LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp is generated.
      • If so, go to Step 7.
      • If not, go to Step 3.
    • If the ping is successful, go to Step 3.

  3. Run the display this command in the MPLS view of the ingress to check whether the mpls te cspf command is configured, that is, to check whether the CSPF is enabled.

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

  4. Run the display mpls te cspf destination command on the ingress to check whether a path that meets the constraints is available. If so, the path of the TE tunnel is displayed, indicating that CSPF calculation is successful. If not, null is displayed, indicating that CSPF calculation fails.

    • If the path is successfully calculated, run the display current-configuration interface interface-type interface-number command on the ingress to check the tunnel configurations, including the primary tunnel, protection tunnel, and the protection interface. Check whether the mpls te auto-frr command is configured in the MPLS view. If so, it indicates that Auto FRR is enabled. In this case, you can check the primary tunnel. If not, check whether the mpls te fast-reroute, mpls te record-route, and mpls te bypass-tunnel are configured to identify the primary and backup tunnels.

      After the primary and backup tunnels are checked, you can check the explicit-path command to verify whether the explicit path is configured; check the mpls te affinity property command to verify whether the affinity property is configured.

      Run the display mpls te cspf destination command and configure the parameters of constraints one by one, including the priority (priority setup-priority), bandwidth (bandwidth), explicit path (explicit-path path-name), affinity property (affinity properties), and hop limit (hop-limit hop-limit-number), and you can check whether the path that meets the constraints is available. If so, the path of the TE tunnel is displayed, indicating that CSPF calculation is successful. If not, null is displayed, indicating that CSPF calculation fails.
      1. If the explicit path fails to be calculated, check whether the interfaces along the explicit path are in the Up state and are enabled with MPLS and MPLS TE. If the explicit path is successfully calculated, check whether the path calculation according to the affinity property and bandwidth is consistent with the explicit path by running the display mpls te cspf destination ip-address bandwidth ct0 ct0-bandwidth explicit-path path-name command.
      2. If CSPF path calculation fails after affinity property is configured, run the mpls te affinity property command in the tunnel view to modify the affinity property of the tunnel, or run the mpls te link administrative group on the interfaces along the tunnel to modify the administrative group property of the link.
      3. If CSPF path calculation fails because of other constraints, go to Step 6.
      Then, check whether the alarm LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp is generated.
      • If so, go to Step 7.
      • If not, go to Step 5.
    • If CSPF path calculation fails, go to Step 5.

  5. Run the display explicit-path command to check the interfaces along the tunnel. Then, run the display this command in the interface view of each interface of the tunnel to check whether the interface is enabled with MPLS, MPLS TE, and RSVP-TE.

    • If MPLS, MPLS TE, or RSVP-TE is not enabled, run the mpls, mpls te or mpls rsvp-te commands in the view of the interface.
    • If any interface along the tunnel is not in Up state, restart the interface. That is, run the shutdown and then undo shutdown commands in the interface view, or run the restart command in the interface view.
    Then, check whether the alarm LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp is generated.
    • If so, go to Step 7.
    • If not, go to Step 6.

  6. Collect the trap information, log information, and configuration of the switch, and Collect alarm information and configuration information, and then contact technical support personnel.
  7. End.

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.8 hwMplsTeFrrResume

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.8 hwMplsTeFrrResume

Description

LSPM/3/MPLSTEFRRRESUME:OID [oid] Tunnel resumes.(SessionTunnelId=[integer], LocalLspId=[integer], IngressLsrId=[integer], EgressLsrId=[integer], MplsTunnelAdminStatus=[integer], MplsTunnelOperStatus=[integer])

The trap message was output when the primary tunnel was recovered and the traffic was switched back from the bypass tunnel.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.121.2.1.8

Minor

 communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

SessionTunnelId

Indicates the ID of the tunnel.

LocalLspId

Indicates the local LSP ID of a tunnel.

IngressLsrId

Indicates the LSR ID of the ingress on the tunnel.

EgressLsrId

Indicates the LSR ID of the egress on the tunnel.

MplsTunnelAdminStatus
Indicates the management status of the tunnel.
  • 1: Up
  • 2: Down

MplsTunnelOperStatus
Indicates the operating status of the tunnel:
  • 1: Up
  • 2: Down

Impact on the System

Services will not be affected.

Possible Causes

The status of the node or the link protected by the bypass tunnel changed from Down to Up.

Procedure

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

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.7 hwMplsTeFrrSwitch

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.9 hwMplsTunnelHSBSwitch

Description

LSPM/3/MPLSTUNNELHSBSWITCH:OID [oid] Main LSP of Tunnel switches to backup LSP in HSB.(SessionTunnelId=[integer], LocalLspId=[integer], IngressLsrId=[integer], EgressLsrId=[integer], MplsTunnelAdminStatus=[integer], MplsTunnelOperStatus=[integer])

The trap message was output when the primary CR-LSP went Down and traffic was switched to a hot-standby CR-LSP.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.121.2.1.9

Minor

communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

SessionTunnelId

ID of the tunnel

LocalLspId

Local LSP ID of a tunnel

IngressLsrId

LSR ID of the ingress on the tunnel

EgressLsrId

LSR ID of the egress on the tunnel

MplsTunnelAdminStatus
Management status of the tunnel:
  • 1: Up
  • 2: Down

MplsTunnelOperStatus
Operating status of the tunnel:
  • 1: Up
  • 2: Down

Impact on the System

Services will not be affected.

Possible Causes

The primary LSP was Down and the backup LSP was in use. The backup mode was HSB.

Procedure

  1. Run the display mpls te tunnel-interface tunnel-name command on the ingress (that is, the node that generates the trap) to check the configurations of the tunnel. View the Tunnel State Desc field to check whether the tunnel is in the Down state. Then, run the display mpls te tunnel-interface last-error command to view the prompt.

    • In the case of the following error prompts, do as required:
      • If the error prompt is "Cspf failed to calculate a path for Tunnel." (indicating that the ingress is enabled with CSPF, but the CSPF path calculation fails), go to Step 2.
      • If the error prompt is "Trigger Rsvp failed", go to Step 2.
      • If the error prompt is "One LSP is deleted at smooth period", go to Step 6.
      • If the error prompt is "One LSP is deleted at Tunnel aging period", go to Step 6.
      • For other types of errors, go to Step 6.
    • If there is no error prompt, go to Step 2.

  2. Run the ping command on the ingress to check whether the destination IP address of the tunnel can be pinged.

    • If the ping fails, rectify the route fault to ensure that the destination IP address of the tunnel can be pinged, and then check whether the alarm LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp is generated.
      • If so, go to Step 7.
      • If not, go to Step 3.
    • If the ping is successful, go to Step 3.

  3. Run the display this command in the MPLS view of the ingress to check whether the mpls te cspf command is configured, that is, to check whether the CSPF is enabled.

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

  4. Run the display mpls te cspf destination command on the ingress to check for paths that satisfy specified constraints. If such paths exist, the path of the TE tunnel is displayed, indicating CSFP path computation is successful. If the output is empty, CSFP path computation fails.

    • If CSFP path computation is successful, perform the following operations to confirm tunnel configurations:
      • Run the display current-configuration interface interface-type interface-number command on the ingress to view configurations.
      • Check whether mpls te auto-frr command is run in the MPLS view. If this command exists, automatic protection is enabled. Check the tunnel configuration and find the primary tunnel. If this command does not exist, check the mpls te fast-reroute, mpls te record-route, mpls te bypass-tunnel command configurations to determine the primary and backup tunnels.
      • Check whether the explicit-path command is run to configure an explicit path.
      • Check whether the mpls te affinity property command is run to configure affinities.
      • Check whether the mpls te bandwidth command is run to configure bandwidth values.
      Run the display mpls te cspf destination command with constraints specified based on tunnel configurations. The parameters include priority setup-priority, bandwidth, explicit-path path-name, affinity properties, and hop-limit hop-limit-number. Then check whether the path that satisfies the constraints exists. If such paths exist, the path of the TE tunnel is displayed, indicating CSFP path computation is successful. If the output is empty, CSFP path computation fails.
      1. If CSPF fails to use an explicit path to compute a path, check whether the interfaces along the explicit path are Up and check whether MPLS and MPLS TE are enabled on the interfaces. If CSPF path computation is successful, check whether affinities and bandwidth values are successfully used to compute a path and whether the tunnel is established on the explicit path. Run the display mpls te cspf destination ip-address bandwidth ct0 ct0-bandwidth explicit-path path-name command.
      2. If affinities fail to be used to compute a path, run the mpls te affinity property command in the tunnel interface view to modify affinities and run the mpls te link administrative group command in the view of each interface along the path to modify the administrative group attribute.
      3. If the other constraints fail to be used to compute a path, go to Step 6.
      Check whether LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp is displayed.
      • If this alarm is generated, go to Step 7.
      • If this alarm is not generated, go to Step 5.
    • If path computation fails, go to Step 5.

  5. Run the display explicit-path command to check the interfaces along the tunnel. Then, run the display this command in the interface view of each interface of the tunnel to check whether the interface is enabled with MPLS, MPLS TE, and RSVP-TE.

    • If MPLS, MPLS TE, or RSVP-TE is not enabled, run the mpls, mpls te or mpls rsvp-te commands in the view of the interface.
    • If any interface along the tunnel is not in Up state, restart the interface. That is, run the shutdown and then undo shutdown commands in the interface view, or run the restart command in the interface view.

    Then, check whether the alarm LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp is generated.

    • If so, go to Step 7.
    • If not, go to Step 6.

  6. Collect the trap information, log information, and configuration of the switch, and Collect alarm information and configuration information, and then contact technical support personnel.
  7. End.

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.10 hwMplsTunnelHSBResume

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.10 hwMplsTunnelHSBResume

Description

LSPM/3/MPLSTUNNELHSBRESUME:OID [oid] Main LSP of Tunnel resumes from backup LSP in HSB.(SessionTunnelId=[integer], LocalLspId=[integer], IngressLsrId=[integer], EgressLsrId=[integer], MplsTunnelAdminStatus=[integer], MplsTunnelOperStatus=[integer])

The trap message was output when the primary CR-LSP went Up and traffic was switched back from the hot-standby CR-LSP to the primary CR-LSP.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.121.2.1.10

Minor

 communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

SessionTunnelId

Indicates the ID of the tunnel.

LocalLspId

Indicates the local LSP ID of a tunnel.

IngressLsrId

Indicates the LSR ID of the ingress on the tunnel.

EgressLsrId

Indicates the LSR ID of the egress on the tunnel.

MplsTunnelAdminStatus
Indicates the management status of the tunnel.
  • 1: Up
  • 2: Down

MplsTunnelOperStatus
Indicates the operating status of the tunnel:
  • 1: Up
  • 2: Down

Impact on the System

Services will not be affected.

Possible Causes

When the tunnel was in the HSB inuse state, the status of the primary LSP changed from Down to Up.

Procedure

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

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.9 hwMplsTunnelHSBSwitch

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.11 hwMplsTunnelOBSwitch

Description

LSPM/3/MPLSTUNNELOBSWITCH:OID [oid] Main LSP of Tunnel switches to back up LSP in OB.(SessionTunnelId=[integer], LocalLspId=[integer], IngressLsrId=[integer], EgressLsrId=[integer], MplsTunnelAdminStatus=[integer], MplsTunnelOperStatus=[integer])

The trap message was output when the primary CR-LSP went Down and traffic was switched to an ordinary backup CR-LSP.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.121.2.1.11

Minor

 communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

SessionTunnelId

ID of the tunnel

LocalLspId

Local LSP ID of a tunnel

IngressLsrId

LSR ID of the ingress on the tunnel

EgressLsrId

LSR ID of the egress on the tunnel

MplsTunnelAdminStatus
Management status of the tunnel:
  • 1: Up
  • 2: Down

MplsTunnelOperStatus
Operating status of the tunnel:
  • 1: Up
  • 2: Down

Impact on the System

The primary LSP was Down and the backup LSP was used, and the traffic interruption occurred.

Possible Causes

The primary LSP was Down and the backup LSP was Up. The backup mode was OB.

Procedure

  1. Run the display mpls te tunnel-interface tunnel-name command on the ingress (that is, the node that generates the trap) to check the configurations of the tunnel. View the Tunnel State Desc field to check whether the tunnel is in the Down state. Then, run the display mpls te tunnel-interface last-error command to view the prompt.

    • In the case of the following error prompts, do as required:
      • If the error prompt is "Cspf failed to calculate a path for Tunnel." (indicating that the ingress is enabled with CSPF, but the CSPF path calculation fails), go to Step 2.
      • If the error prompt is "Trigger Rsvp failed", go to Step 2.
      • If the error prompt is "One LSP is deleted at smooth period", go to Step 6.
      • If the error prompt is "One LSP is deleted at Tunnel aging period", go to Step 6.
      • For other types of errors, go to Step 6.
    • If there is no error prompt, go to Step 2.

  2. Run the ping command on the ingress to check whether the destination IP address of the tunnel can be pinged.

    • If the ping fails, rectify the route fault to ensure that the destination IP address of the tunnel can be pinged, and then check whether the alarm LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp is generated.
      • If so, go to Step 7.
      • If not, go to Step 3.
    • If the ping is successful, go to Step 3.

  3. Run the display this command in the MPLS view of the ingress to check whether the mpls te cspf command is configured, that is, to check whether the CSPF is enabled.

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

  4. Run the display mpls te cspf destination command on the ingress to check for paths that satisfy specified constraints. If such paths exist, the path of the TE tunnel is displayed, indicating CSFP path computation is successful. If the output is empty, CSFP path computation fails.

    • If CSFP path computation is successful, perform the following operations to confirm tunnel configurations:
      • Run the display current-configuration interface interface-type interface-number command on the ingress to view configurations.
      • Check whether the mpls te auto-frr command is run in the MPLS view. If this command exists, automatic protection is enabled. Check the tunnel configuration and find the primary tunnel. If this command does not exist, check the mpls te fast-reroute, mpls te record-route, mpls te bypass-tunnel command configurations to determine the primary and backup tunnels.
      • Check whether the explicit-path command is run to configure an explicit path.
      • Check whether the mpls te affinity property command is run to configure affinities.
      • Check whether the mpls te bandwidth command is run to configure bandwidth values.
      Run the display mpls te cspf destination command with constraints specified based on tunnel configurations. The parameters include priority setup-priority, bandwidth, explicit-path path-name, affinity properties, and hop-limit hop-limit-number. Then check whether the path that satisfies the constraints exists. If such paths exist, the path of the TE tunnel is displayed, indicating CSFP path computation is successful. If the output is empty, CSFP path computation fails.
      1. If CSPF fails to use an explicit path to compute a path, check whether the interfaces along the explicit path are Up and check whether MPLS and MPLS TE are enabled on the interfaces. If CSPF path computation is successful, check whether affinities and bandwidth values are successfully used to compute a path and whether the tunnel is established on the explicit path. Run the display mpls te cspf destination ip-address bandwidth ct0 ct0-bandwidth explicit-path path-name command.
      2. If affinities fail to be used to compute a path, run the mpls te affinity property command in the tunnel interface view to modify affinities and run the mpls te link administrative group command in the view of each interface along the path to modify the administrative group attribute.
      3. If the other constraints fail to be used to compute a path, go to Step 6.
      Check whether LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp is displayed.
      • If this alarm is generated, go to Step 7.
      • If this alarm is not generated, go to Step 5.
    • If path computation fails, go to Step 5.

  5. Run the display explicit-path command to check the interfaces along the tunnel. Then, run the display this command in the interface view of each interface of the tunnel to check whether the interface is enabled with MPLS, MPLS TE, and RSVP-TE.

    • If MPLS, MPLS TE, or RSVP-TE is not enabled, run the mpls, mpls te or mpls rsvp-te commands in the view of the interface.
    • If any interface along the tunnel is not in Up state, restart the interface. That is, run the shutdown and then undo shutdown commands in the interface view, or run therestart command in the interface view.
    Then, check whether the alarm LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp is generated.
    • If so, go to Step 7.
    • If not, go to Step 6.

  6. Collect the trap information, log information, and configuration of the switch, and Collect alarm information and configuration information, and then contact technical support personnel.
  7. End.

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.12 hwMplsTunnelOBResume

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.12 hwMplsTunnelOBResume

Description

LSPM/3/MPLSTUNNELOBRESUME:OID [oid] Main LSP of Tunnel resumes from backup LSP in OB.(SessionTunnelId=[integer], LocalLspId=[integer], IngressLsrId=[integer], EgressLsrId=[integer], MplsTunnelAdminStatus=[integer], MplsTunnelOperStatus=[integer])

The trap message was output when the primary CR-LSP went Up and traffic was switched back from the ordinary backup CR-LSP to the primary CR-LSP.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.121.2.1.12

Minor

 communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

SessionTunnelId

Indicates the ID of the tunnel.

LocalLspId

Indicates the local LSP ID of a tunnel.

IngressLsrId

Indicates the LSR ID of the ingress on the tunnel.

EgressLsrId

Indicates the LSR ID of the egress on the tunnel.

MplsTunnelAdminStatus
Indicates the management status of the tunnel.
  • 1: Up
  • 2: Down

MplsTunnelOperStatus
Indicates the operating status of the tunnel:
  • 1: Up
  • 2: Down

Impact on the System

Services will not be affected.

Possible Causes

When the tunnel was in the OB inuse state, the status of the primary LSP changed from Down to Up.

Procedure

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

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.11 hwMplsTunnelOBSwitch

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.15 hwMplsTunnelChangeBw

Description

LSPM/4/HWMPLSTUNCHANGEBW:OID [oid] The bandwidth of the tunnel has changed. (SessionTunnelId=[integer1], LocalLspId=[integer2], IngressLsrId=[integer3], EgressLsrId=[integer4])

The trap message was sent when the bandwidth of the tunnel changed.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.121.2.1.15

Warning

environmentalAlarm(6)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

SessionTunnelId

Indicates the ID of the tunnel.

LocalLspId

Indicates the ID of the local LSP.

IngressLsrId

Indicates the ID of the ingress LSR.

EgressLsrId

Indicates the ID of the egress LSR.

Impact on the System

Services will not be affected.

Possible Causes

The bandwidth of a specified type on the tunnel was changed.

Procedure

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

Related Information

None.

LSPM_1.3.6.1.4.1.2011.5.25.182.1.54.1 hwMplsLdpVirtualTunnelUp

Description

LSPM/1/LDPVTUNNEL_UP:OID [oid] LDP virtual tunnel went Up. (VirtualTunnelIndex=[gauge][gauge], FecNodeIpAddress=[IPADDR], FecNodeMask=[INTEGER])

This alarm is generated when the LDP virtual tunnel goes Up.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.182.1.54.1

Critical

communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VirtualTunnelIndex

Indicates the index of the virtual tunnel.

FecNodeIpAddress

FEC node's IP address

FecNodeMask

FEC node's mask

Impact on the System

Services will not be affected.

Possible Causes

The first LDP ingress LSP under a certain LDP virtual tunnel is successfully set up.

Procedure

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

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.182.1.54.2_hwMplsLdpVirtualTunnelDown

LSPM_1.3.6.1.4.1.2011.5.25.182.1.54.2 hwMplsLdpVirtualTunnelDown

Description

LSPM/1/LDPVTUNNEL_DOWN:OID [oid] LDP virtual tunnel went Down. (VirtualTunnelIndex=[gauge], FecNodeIpAddress=[IPADDR], FecNodeMask=[INTEGER])

The LDP virtual tunnel went Down.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.182.1.54.2

Critical

communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

VirtualTunnelIndex

Index of the virtual tunnel

FecNodeIpAddress

FEC node's IP address

FecNodeMask

FEC node's mask

Impact on the System

If an LSP in an LDP virtual tunnel carries services, services may be interrupted.

Possible Causes

All the LDP ingress LSPs under a certain LDP virtual tunnel are deleted.

Procedure

  • If no services are carried over the LSP under the flapping LDP virtual tunnel, no action is required. If services are carried, run the display mpls last-info lsp-down verbose command to check the FEC field in the command output. Find the tunnel whose FEC field value is the same as the FecNodeIpAddress value. Then, check the tunnel flapping cause based on the Down Reason field and rectify the fault accordingly.

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.182.1.54.1_hwMplsLdpVirtualTunnelUp

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.46 hwMplsTunnelPrimaryUp

Description

LSPM/2/MPLSTUNPRIUP:OID [oid] The primary LSP of the tunnel changes to Up. (SessionTunnelId=[INTEGER], TunnelInstIndex=[integer], IngressLsrId=[integer], EgressLsrId=[integer], mplsTunnelIfName=[octet])

The primary LSP of the tunnel changes to Up.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.121.2.1.46

Major

 communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

SessionTunnelId

Indicates the ID of the tunnel.

TunnelInstIndex

Indicates the InstIndex of the tunnel.

IngressLsrId

Indicates the LSR ID of the ingress on the tunnel.

EgressLsrId

Indicates the LSR ID of the egress on the tunnel.

mplsTunnelIfName

indicates the name of a tunnel.

Impact on the System

Services will not be affected.

Possible Causes

The primary LSP of the tunnel changes to Up.

Procedure

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

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.47 hwMplsTunnelPrimaryDown

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.47 hwMplsTunnelPrimaryDown

Description

LSPM/2/MPLSTUNPRIDOWN:OID [oid] The primary LSP of the tunnel changes to Down. (SessionTunnelId=[INTEGER], TunnelInstIndex=[integer], IngressLsrId=[integer], EgressLsrId=[integer], mplsTunnelIfName=[octet], hwMplsTunnelDownReason=[integer], hwMplsTunnelDownLSRId=[binary], hwMplsTunnelDownIfAddrType=[integer], hwMplsTunnelDownIfAddr=[binary])

The primary LSP of the tunnel changes to Down.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.121.2.1.47

Major

 communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

SessionTunnelId

ID of the tunnel

TunnelInstIndex

InstIndex of the tunnel

IngressLsrId

LSR ID of the ingress on the tunnel

EgressLsrId

LSR ID of the egress on the tunnel

mplsTunnelIfName

Name of a tunnel

hwMplsTunnelDownReason

Reason why a tunnel goes Down

hwMplsTunnelDownLSRId

LSR ID of the error node on a tunnel

hwMplsTunnelDownIfAddrType

IP address type of the error interface on a tunnel

hwMplsTunnelDownIfAddr

IP address of the error interface on a tunnel

Impact on the System

If traffic is not forwarded along the primary LSP of the tunnel, traffic forwarding will not be affected. If traffic is forwarded along the primary LSP of the tunnel and a backup LSP is configured, traffic will be switched to the backup LSP. If not, traffic forwarding will be interrupted.

Possible Causes

Cause 1: The interface went Up.

Cause 1: The configuration of the tunnel was deleted.

Cause 3: The link was faulty.

Procedure

  1. Run the display mpls te tunnel-interface tunnel-name command on the ingress (that is, the node that generates the trap) to check the configurations of the tunnel. View the Tunnel State Desc field to check whether the tunnel is in the Down state. Then, run the display mpls te tunnel-interface last-error command to view the prompt.

    • In the case of the following error prompts, do as required:
      • If the error prompt is "Cspf failed to calculate a path for Tunnel." (indicating that the ingress is enabled with CSPF, but the CSPF path calculation fails), go to Step 2.
      • If the error prompt is "Trigger Rsvp failed", go to Step 2.
      • If the error prompt is "One LSP is deleted at smooth period", go to Step 6.
      • If the error prompt is "One LSP is deleted at Tunnel aging period", go to Step 6.
      • For other types of errors, go to Step 6.
    • If there is no error prompt, go to Step 2.

  2. Run the ping command on the ingress to check whether the destination IP address of the tunnel can be pinged.

    • If the ping fails, rectify the route fault to ensure that the destination IP address of the tunnel can be pinged, and then check whether the alarmLSPM_1.3.6.1.4.1.2011.5.25.121.2.1.47 hwMplsTunnelPrimaryUp is generated.
      • If so, go to Step 7.
      • If not, go to Step 3.
    • If the ping is successful, go to Step 3.

  3. Run the display this command in the MPLS view of the ingress to check whether the mpls te cspf command is configured, that is, to check whether the CSPF is enabled.

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

  4. Run the display mpls te cspf destination command on the ingress to check for paths that satisfy specified constraints. If such paths exist, the path of the TE tunnel is displayed, indicating CSFP path computation is successful. If the output is empty, CSFP path computation fails.

    • If CSFP path computation is successful, perform the following operations to confirm tunnel configurations:
      • Run the display current-configuration interface interface-type interface-number command on the ingress to view configurations.
      • Check whether mpls te auto-frr command is run in the MPLS view. If this command exists, automatic protection is enabled. Check the tunnel configuration and find the primary tunnel. If this command does not exist, check the mpls te fast-reroute, mpls te record-route, mpls te bypass-tunnel command configurations to determine the primary and backup tunnels.
      • Check whether the explicit-path command is run to configure an explicit path.
      • Check whether the mpls te affinity property command is run to configure affinities.
      • Check whether the mpls te bandwidth command is run to configure bandwidth values.
      Run the display mpls te cspf destination command with constraints specified based on tunnel configurations. The parameters include priority setup-priority, bandwidth, explicit-path path-name, affinity properties, and hop-limit hop-limit-number. Then check whether the path that satisfies the constraints exists. If such paths exist, the path of the TE tunnel is displayed, indicating CSFP path computation is successful. If the output is empty, CSFP path computation fails.
      1. If CSPF fails to use an explicit path to compute a path, check whether the interfaces along the explicit path are Up and check whether MPLS and MPLS TE are enabled on the interfaces. If CSPF path computation is successful, check whether affinities and bandwidth values are successfully used to compute a path and whether the tunnel is established on the explicit path. Run the display mpls te cspf destination ip-address bandwidth ct0 ct0-bandwidth explicit-path path-name command.
      2. If affinities fail to be used to compute a path, run the mpls te affinity property command in the tunnel interface view to modify affinities and run the mpls te link administrative group command in the view of each interface along the path to modify the administrative group attribute.
      3. If the other constraints fail to be used to compute a path, go to Step 6.
      Check whether LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp is displayed.
      • If this alarm is generated, go to Step 7.
      • If this alarm is not generated, go to Step 5.
    • If path computation fails, go to Step 5.

  5. Run the display explicit-path command or identify interfaces that an LSP passes through based on the network topology to check the interfaces along the tunnel. Then, run the display this command in the interface view of each interface of the tunnel to check whether the interface is enabled with MPLS, MPLS TE, and RSVP-TE.

    • If MPLS, MPLS TE, or RSVP-TE is not enabled, run the mpls, mpls te or mpls rsvp-te commands in the view of the interface.
    • If any interface along the tunnel is not in Up state, restart the interface. That is, run the shutdown and then undo shutdown commands in the interface view, or run the restart command in the interface view.
    Then, check whether the alarm LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.47 hwMplsTunnelPrimaryUp is generated.
    • If so, go to Step 7.
    • If not, go to Step 6.

  6. Collect the trap information, log information, and configuration of the switch, and Collect alarm information and configuration information, and then contact technical support personnel.
  7. End.

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.46 hwMplsTunnelPrimaryUp

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.48 hwMplsTunnelHotstandbyUp

Description

LSPM/2/MPLSTUNHSBUP:OID [oid] The hot-standby LSP of the tunnel changes to Up. (SessionTunnelId=[INTEGER], TunnelInstIndex=[integer], IngressLsrId=[integer], EgressLsrId=[integer], mplsTunnelIfName=[octet])

The hot-standby LSP of the tunnel changes to Up.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.121.2.1.48

Major

 communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

SessionTunnelId

Indicates the ID of the tunnel.

TunnelInstIndex

Indicates the InstIndex of the tunnel.

IngressLsrId

Indicates the LSR ID of the ingress on the tunnel.

EgressLsrId

Indicates the LSR ID of the egress on the tunnel.

mplsTunnelIfName

indicates the name of a tunnel.

Impact on the System

Services will not be affected.

Possible Causes

The hot-standby LSP of the tunnel changes to Up.

Procedure

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

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.49 hwMplsTunnelHotstandbyDown

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.49 hwMplsTunnelHotstandbyDown

Description

LSPM/2/MPLSTUNHSBDOWN:OID [oid] The hot-standby LSP of the tunnel changes to Down. (SessionTunnelId=[INTEGER], TunnelInstIndex=[integer], IngressLsrId=[integer], EgressLsrId=[integer], mplsTunnelIfName=[octet], hwMplsTunnelDownReason=[integer], hwMplsTunnelDownLSRId=[binary], hwMplsTunnelDownIfAddrType=[integer], hwMplsTunnelDownIfAddr=[binary])

The hot-standby LSP of the tunnel changes to Down.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.121.2.1.49 Major communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

SessionTunnelId

ID of the tunnel

TunnelInstIndex

InstIndex of the tunnel

IngressLsrId

LSR ID of the ingress on the tunnel

EgressLsrId

LSR ID of the egress on the tunnel

mplsTunnelIfName

Name of a tunnel

hwMplsTunnelDownReason

Reason why a tunnel goes Down

hwMplsTunnelDownLSRId

LSR ID of the error node on a tunnel

hwMplsTunnelDownIfAddrType

IP address type of the error interface on a tunnel

hwMplsTunnelDownIfAddr

IP address of the error interface on a tunnel

Impact on the System

If traffic is not forwarded along the hot-standby LSP of the tunnel, traffic forwarding will not be affected. If traffic is forwarded along the primary LSP of the tunnel and other LSP of the tunnel is in up state, traffic will be switched to the other LSP. If not, traffic forwarding will be interrupted.

Possible Causes

Cause 1: The interface went Up.

Cause 2: The configuration of the tunnel was deleted.

Cause 3: The link was faulty.

Cause 4: The hot-standby LSP had nodes through which the primary LSP passed.

Procedure

  1. Run the display mpls te tunnel-interface tunnel-name command on the ingress (that is, the node that generates the trap) to check the configurations of the tunnel. View the Tunnel State Desc field to check whether the tunnel is in the Down state. Then, run the display mpls te tunnel-interface last-error command to view the prompt.

    • In the case of the following error prompts, do as required:
      • If the error prompt is "Cspf failed to calculate a path for Tunnel." (indicating that the ingress is enabled with CSPF, but the CSPF path calculation fails), go to Step 2.
      • If the error prompt is "Trigger Rsvp failed", go to Step 2.
      • If the error prompt is "One LSP is deleted at smooth period", go to Step 6.
      • If the error prompt is "One LSP is deleted at Tunnel aging period", go to Step 6.
      • For other types of errors, go to Step 6.
    • If there is no error prompt, go to Step 2.

  2. Run the ping command on the ingress to check whether the destination IP address of the tunnel can be pinged.

  3. Run the display this command in the MPLS view of the ingress to check whether the mpls te cspf command is configured, that is, to check whether the CSPF is enabled.

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

  4. Run the display mpls te cspf destination command on the ingress to check for paths that satisfy specified constraints. If such paths exist, the path of the TE tunnel is displayed, indicating CSFP path computation is successful. If the output is empty, CSFP path computation fails.

    • If CSFP path computation is successful, perform the following operations to confirm tunnel configurations:
      • Run the display current-configuration interface interface-type interface-number command on the ingress to view configurations.
      • Check whether mpls te auto-frr command is run in the MPLS view. If this command exists, automatic protection is enabled. Check the tunnel configuration and find the primary tunnel. If this command does not exist, check the mpls te fast-reroute, mpls te record-route, mpls te bypass-tunnel command configurations to determine the primary and backup tunnels.
      • Check whether the explicit-path command is run to configure an explicit path.
      • Check whether the mpls te affinity property command is run to configure affinities.
      • Check whether the mpls te bandwidth command is run to configure bandwidth values.
      Run the display mpls te cspf destination command with constraints specified based on tunnel configurations. The parameters include priority setup-priority, bandwidth, explicit-path path-name, affinity properties, and hop-limit hop-limit-number. Then check whether the path that satisfies the constraints exists. If such paths exist, the path of the TE tunnel is displayed, indicating CSFP path computation is successful. If the output is empty, CSFP path computation fails.
      1. If CSPF fails to use an explicit path to compute a path, check whether the interfaces along the explicit path are Up and check whether MPLS and MPLS TE are enabled on the interfaces. If CSPF path computation is successful, check whether affinities and bandwidth values are successfully used to compute a path and whether the tunnel is established on the explicit path. Run the display mpls te cspf destination ip-address bandwidth ct0 ct0-bandwidth explicit-path path-name command.
      2. If affinities fail to be used to compute a path, run the mpls te affinity property command in the tunnel interface view to modify affinities and run the mpls te link administrative group command in the view of each interface along the path to modify the administrative group attribute.
      3. If the other constraints fail to be used to compute a path, go to Step 6.
      Check whether LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp is displayed.
      • If this alarm is generated, go to Step 7.
      • If this alarm is not generated, go to Step 5.
    • If path computation fails, go to Step 5.

  5. Run the display explicit-path command or identify interfaces that an LSP passes through based on the network topology to check the interfaces along the tunnel. Then, run the display this command in the interface view of each interface of the tunnel to check whether the interface is enabled with MPLS, MPLS TE, and RSVP-TE.

    • If MPLS, MPLS TE, or RSVP-TE is not enabled, run the mpls, mpls te or mpls rsvp-te commands in the view of the interface.
    • If any interface along the tunnel is not in Up state, restart the interface. That is, run the shutdown and then undo shutdown commands in the interface view, or run the restart command in the interface view.
    Then, check whether the alarm LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.48 hwMplsTunnelHotstandbyUp is generated.
    • If so, go to Step 7.
    • If not, go to Step 6.

  6. Collect the trap information, log information, and configuration of the switch, and Collect alarm information and configuration information, and then contact technical support personnel.
  7. End.

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.48 hwMplsTunnelHotstandbyUp

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.50 hwMplsTunnelOrdinaryUp

Description

LSPM/3/MPLSTUNOBKUP: OID [oid] The ordinary LSP of the tunnel changes to Up. (SessionTunnelId=[INTEGER], TunnelInstIndex=[integer], IngressLsrId=[integer], EgressLsrId=[integer], mplsTunnelIfName=[octet])

The ordinary LSP of the tunnel changes to Up.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.121.2.1.50 Minor communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

SessionTunnelId

Indicates the ID of the tunnel.

TunnelInstIndex

Indicates the InstIndex of the tunnel.

IngressLsrId

Indicates the LSR ID of the ingress on the tunnel.

EgressLsrId

Indicates the LSR ID of the egress on the tunnel.

mplsTunnelIfName

indicates the name of a tunnel.

Impact on the System

Services will not be affected.

Possible Causes

The ordinary LSP of the tunnel changes to Up.

Procedure

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

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.51 hwMplsTunnelOrdinaryDown

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.51 hwMplsTunnelOrdinaryDown

Description

LSPM/3/MPLSTUNOBKDOWN:OID [oid] The ordinary LSP of the tunnel changes to Down. (SessionTunnelId=[INTEGER], TunnelInstIndex=[integer], IngressLsrId=[integer], EgressLsrId=[integer], mplsTunnelIfName=[octet], hwMplsTunnelDownReason=[integer], hwMplsTunnelDownLSRId=[binary], hwMplsTunnelDownIfAddrType=[integer], hwMplsTunnelDownIfAddr=[binary])

The ordinary LSP of the tunnel changes to Down.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.121.2.1.51 Minor communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

SessionTunnelId

ID of the tunnel

TunnelInstIndex

InstIndex of the tunnel

IngressLsrId

LSR ID of the ingress on the tunnel

EgressLsrId

LSR ID of the egress on the tunnel

mplsTunnelIfName

Name of a tunnel

hwMplsTunnelDownReason

Reason why a tunnel goes Down

hwMplsTunnelDownLSRId

LSR ID of the error node on a tunnel

hwMplsTunnelDownIfAddrType

IP address type of the error interface on a tunnel

hwMplsTunnelDownIfAddr

IP address of the error interface on a tunnel

Impact on the System

If traffic is not forwarded along the backup LSP of the tunnel, traffic forwarding will not be affected. If traffic is forwarded along the backup LSP of the tunnel and another backup LSP is configured, traffic will be switched to the other backup LSP. If not, traffic forwarding will be interrupted.

Possible Causes

Cause 1: The interface went Up.

Cause 2: The configuration of the tunnel was deleted.

Cause 3: The link was faulty.

Cause 4: An LSP with higher priority became Up.

Procedure

  1. Run the display mpls te tunnel-interface tunnel-name command on the ingress (where the alarm is generated) to check the tunnel status. The PrimaryLSP State field indicates whether the primary LSP of the tunnel is in the Up state and the Hot-Standby LSP State field indicates whether the Hot-standby LSP is in the Up state.

    • If the primary LSPs or hot-standby LSPs are in the Up state, the backup LSP cannot go Up. To address such a problem, go to Step 8.
    • If both the primary and hot-standby LSPs are in the Down state, go to Step 2.

  2. Run the display mpls te tunnel-interface tunnel-name command on the ingress (that is, the node that generates the trap) to check the configurations of the tunnel. View the Tunnel State Desc field to check whether the tunnel is in the Down state. Then, run the display mpls te tunnel-interface last-error command to view the prompt.

    • In the case of the following error prompts, do as required:
      • If the error prompt is "Cspf failed to calculate a path for Tunnel." (indicating that the ingress is enabled with CSPF, but the CSPF path calculation fails), go to Step 3.
      • If the error prompt is "Trigger Rsvp failed", go to Step 3.
      • If the error prompt is "One LSP is deleted at smooth period", go to Step 7.
      • If the error prompt is "One LSP is deleted at Tunnel aging period", go to Step 7.
      • For other types of errors, go to Step 7.
    • If there is no error prompt, go to Step 3.

  3. Run the ping command on the ingress to check whether the destination IP address of the tunnel can be pinged.

    • If the ping fails, rectify the route fault to ensure that the destination IP address of the tunnel can be pinged, and then check whether the alarmLSPM_1.3.6.1.4.1.2011.5.25.121.2.1.50 hwMplsTunnelOrdinaryUp is generated.
      • If so, go to Step 8.
      • If not, go to Step 4.
    • If the ping is successful, go to Step 4.

  4. Run the display this command in the MPLS view of the ingress to check whether the mpls te cspf command is configured, that is, to check whether the CSPF is enabled.

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

  5. Run the display mpls te cspf destination command on the ingress to check for paths that satisfy specified constraints. If such paths exist, the path of the TE tunnel is displayed, indicating CSFP path computation is successful. If the output is empty, CSFP path computation fails.

    • If CSFP path computation is successful, perform the following operations to confirm tunnel configurations:
      • Run the display current-configuration interface interface-type interface-number command on the ingress to view configurations.
      • Check whether mpls te auto-frr command is run in the MPLS view. If this command exists, automatic protection is enabled. Check the tunnel configuration and find the primary tunnel. If this command does not exist, check the mpls te fast-reroute, mpls te record-route, mpls te bypass-tunnel command configurations to determine the primary and backup tunnels.
      • Check whether the explicit-path command is run to configure an explicit path.
      • Check whether the mpls te affinity property command is run to configure affinities.
      • Check whether the mpls te bandwidth command is run to configure bandwidth values.
      Run the display mpls te cspf destination command with constraints specified based on tunnel configurations. The parameters include priority setup-priority, bandwidth, explicit-path path-name, affinity properties, and hop-limit hop-limit-number. Then check whether the path that satisfies the constraints exists. If such paths exist, the path of the TE tunnel is displayed, indicating CSFP path computation is successful. If the output is empty, CSFP path computation fails.
      1. If CSPF fails to use an explicit path to compute a path, check whether the interfaces along the explicit path are Up and check whether MPLS and MPLS TE are enabled on the interfaces. If CSPF path computation is successful, check whether affinities and bandwidth values are successfully used to compute a path and whether the tunnel is established on the explicit path. Run the display mpls te cspf destination ip-address bandwidth ct0 ct0-bandwidth explicit-path path-name command.
      2. If affinities fail to be used to compute a path, run the mpls te affinity property command in the tunnel interface view to modify affinities and run the mpls te link administrative group command in the view of each interface along the path to modify the administrative group attribute.
      3. If the other constraints fail to be used to compute a path, go to Step 7.
      Check whether LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp is displayed.
      • If this alarm is generated, go to Step 8.
      • If this alarm is not generated, go to Step 6.
    • If path computation fails, go to Step 6.

  6. Run the display explicit-path command or identify interfaces that an LSP passes through based on the network topology to check the interfaces along the tunnel. Then, run the display this command in the interface view of each interface of the tunnel to check whether the interface is enabled with MPLS, MPLS TE, and RSVP-TE.

    • If MPLS, MPLS TE, or RSVP-TE is not enabled, run the mpls, mpls te or mpls rsvp-te commands in the view of the interface.
    • If any interface along the tunnel is not in Up state, restart the interface. That is, run the shutdown and then undo shutdown commands in the interface view, or run the restart command in the interface view.
    Then, check whether the alarm LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.50 hwMplsTunnelOrdinaryUp is generated.
    • If so, go to Step 8.
    • If not, go to Step 7.

  7. Collect the trap information, log information, and configuration of the switch, and Collect alarm information and configuration information, and then contact technical support personnel.
  8. End.

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.50 hwMplsTunnelOrdinaryUp

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.52 hwMplsTunnelBesteffortUp

Description

LSPM/3/MPLSTUNBBKUP:OID [oid] The best-effort LSP of the tunnel changes to Up. (SessionTunnelId=[INTEGER], TunnelInstIndex=[integer], IngressLsrId=[integer], EgressLsrId=[integer], mplsTunnelIfName=[octet])

The best-effort LSP of the tunnel changes to Up.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.121.2.1.52 Minor communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

SessionTunnelId

Indicates the ID of the tunnel.

TunnelInstIndex

Indicates the InstIndex of the tunnel.

IngressLsrId

Indicates the LSR ID of the ingress on the tunnel.

EgressLsrId

Indicates the LSR ID of the egress on the tunnel.

mplsTunnelIfName

indicates the name of a tunnel.

Impact on the System

Services will not be affected.

Possible Causes

The best-effort LSP of the tunnel changes to Up.

Procedure

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

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.53 hwMplsTunnelBesteffortDown

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.53 hwMplsTunnelBesteffortDown

Description

LSPM/3/MPLSTUNBBKDOWN:OID [oid] The best-effort LSP of the tunnel changes to Down. (SessionTunnelId=[INTEGER], TunnelInstIndex=[integer], IngressLsrId=[integer], EgressLsrId=[integer], mplsTunnelIfName=[octet], hwMplsTunnelDownReason=[integer], hwMplsTunnelDownLSRId=[binary], hwMplsTunnelDownIfAddrType=[integer], hwMplsTunnelDownIfAddr=[binary])

The best-effort LSP of the tunnel changes to Down.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.121.2.1.53 Minor communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

SessionTunnelId

ID of the tunnel

TunnelInstIndex

InstIndex of the tunnel

IngressLsrId

LSR ID of the ingress on the tunnel

EgressLsrId

LSR ID of the egress on the tunnel

mplsTunnelIfName

Indicates the name of the tunnel interface.

hwMplsTunnelDownReason

Reason why a tunnel goes Down

hwMplsTunnelDownLSRId

LSR ID of the error node on a tunnel

hwMplsTunnelDownIfAddrType

IP address type of the error interface on a tunnel

hwMplsTunnelDownIfAddr

IP address of the error interface on a tunnel

mplsTunnelIfName

Name of a tunnel

Impact on the System

If traffic is not forwarded along the best-effort LSP of the tunnel, traffic forwarding will not be affected. If traffic is forwarded along the best-effort LSP of the tunnel and a backup LSP is configured, traffic will be switched to the backup LSP. If not, traffic forwarding will be interrupted.

Possible Causes

Cause 1: The interface went Up.

Cause 2: The configuration of the tunnel was deleted.

Cause 3: The link was faulty.

Cause 4: An LSP with higher priority became Up.

Procedure

  1. Run the display mpls te tunnel-interface tunnel-name command on the ingress (where the alarm is generated) to check the tunnel status. The PrimaryLSP State field indicates whether the primary LSP of the tunnel is in the Up state and the Hot-Standby LSP State field indicates whether the Hot-standby LSP is in the Up state.

    • If the primary LSPs or hot-standby LSPs are in the Up state, the backup LSP cannot go Up. To address such a problem, go to Step 7.
    • If both the primary and hot-standby LSPs are in the Down state, go to Step 2.

  2. Run the display mpls te tunnel-interface tunnel-name command on the ingress (that is, the node that generates the trap) to check the configurations of the tunnel. View the Tunnel State Desc field to check whether the tunnel is in the Down state. Then, run the display mpls te tunnel-interface last-error command to view the prompt.

    • In the case of the following error prompts, do as required:
      • If the error prompt is "Cspf failed to calculate a path for Tunnel." (indicating that the ingress is enabled with CSPF, but the CSPF path calculation fails), go to Step 3.
      • If the error prompt is "Trigger Rsvp failed", go to Step 3.
      • If the error prompt is "One LSP is deleted at smooth period", go to Step 7.
      • If the error prompt is "One LSP is deleted at Tunnel aging period", go to Step 7.
      • For other types of errors, go to Step 6.
    • If there is no error prompt, go to Step 3.

  3. Run the ping command on the ingress to check whether the destination IP address of the tunnel can be pinged.

  4. Run the display this command in the MPLS view of the ingress to check whether the mpls te cspf command is configured, that is, to check whether the CSPF is enabled.

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

  5. Run the display mpls te cspf destination command on the ingress to check for paths that satisfy specified constraints. If such paths exist, the path of the TE tunnel is displayed, indicating CSFP path computation is successful. If the output is empty, CSFP path computation fails.

    • If CSFP path computation is successful, perform the following operations to confirm tunnel configurations:
      • Run the display current-configuration interface interface-type interface-number command on the ingress to view configurations.
      • Check whether mpls te auto-frr command is run in the MPLS view. If this command exists, automatic protection is enabled. Check the tunnel configuration and find the primary tunnel. If this command does not exist, check the mpls te fast-reroute, mpls te record-route, mpls te bypass-tunnel command configurations to determine the primary and backup tunnels.
      • Check whether the explicit-path command is run to configure an explicit path.
      • Check whether the mpls te affinity property command is run to configure affinities.
      • Check whether the mpls te bandwidth command is run to configure bandwidth values.
      Run the display mpls te cspf destination command with constraints specified based on tunnel configurations. The parameters include priority setup-priority, bandwidth, explicit-path path-name, affinity properties, and hop-limit hop-limit-number. Then check whether the path that satisfies the constraints exists. If such paths exist, the path of the TE tunnel is displayed, indicating CSFP path computation is successful. If the output is empty, CSFP path computation fails.
      1. If CSPF fails to use an explicit path to compute a path, check whether the interfaces along the explicit path are Up and check whether MPLS and MPLS TE are enabled on the interfaces. If CSPF path computation is successful, check whether affinities and bandwidth values are successfully used to compute a path and whether the tunnel is established on the explicit path. Run the display mpls te cspf destination ip-address bandwidth ct0 ct0-bandwidth explicit-path path-name command.
      2. If affinities fail to be used to compute a path, run the mpls te affinity property command in the tunnel interface view to modify affinities and run the mpls te link administrative group command in the view of each interface along the path to modify the administrative group attribute.
      3. If the other constraints fail to be used to compute a path, go to Step 7.
      Check whether LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp is displayed.
      • If this alarm is generated, go to Step 7.
      • If this alarm is not generated, go to Step 6.
    • If path computation fails, go to Step 6.

  6. Collect the trap information, log information, and configuration of the switch, and Collect alarm information and configuration information, and then contact technical support personnel.
  7. End.

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.52 hwMplsTunnelBesteffortUp

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.54 hwMplsTeAutoTunnelDownClear

Description

LSPM/2/MPLSTEAUTOTUNNELDOWNCLEAR:OID [oid] The TE Auto tunnel Down alarm was cleared. (SessionTunnelId=[integer], LocalLspId=[integer], IngressLsrId=[integer], EgressLsrId=[integer], mplsTunnelAdminStatus=[integer], mplsTunnelOperStatus=[integer], mplsTunnelIfName=[octet])

The TE Auto tunnel Down alarm was cleared.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.121.2.1.54

Major

 communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

SessionTunnelId

Indicates the ID of the tunnel.

LocalLspId

Indicates the ID of local LSP.

IngressLsrId

Indicates the ID of the ingress LSR.

EgressLsrId

Indicates the ID of the egress LSR.

mplsTunnelAdminStatus

Indicates the administration status of the tunnel.

mplsTunnelOperStatus

Indicates the operating status of the tunnel.

mplsTunnelIfName

Indicates the name of the tunnel interface.

Impact on the System

Services will not be affected.

Possible Causes

The TE Auto tunnel was created successfully.

Procedure

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

Related Information

None.

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.55 hwMplsTeAutoTunnelPrimaryDownClear

Description

LSPM/2/MPLSTEAUTOTUNNEL_PRIDOWNCLEAR:OID [oid] The Down alarm about the primary LSP in the TE Auto tunnel was cleared. (SessionTunnelId=[INTEGER], TunnelInstIndex=[integer], IngressLsrId=[integer], EgressLsrId=[integer], mplsTunnelIfName=[octet])

The Down alarm about the primary LSP in the TE Auto tunnel was cleared.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.121.2.1.55

Major

 communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

SessionTunnelId

Indicates the ID of the tunnel.

TunnelInstIndex

Indicates the index of the tunnel.

IngressLsrId

Indicates the ID of the ingress LSR.

EgressLsrId

Indicates the ID of the egress LSR.

mplsTunnelIfName

Indicates the name of the tunnel interface.

Impact on the System

Services will not be affected.

Possible Causes

The primary LSP in the TE Auto tunnel was created successfully.

Procedure

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

Related Information

None.

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.56 hwMplsTunnelBBSwitch

Description

LSPM/3/MPLSTUNNELBBSWITCH:OID [oid] Main LSP of Tunnel switches to back up LSP in BBK.(SessionTunnelId=[integer], LocalLspId=[integer], IngressLsrId=[integer], EgressLsrId=[integer], MplsTunnelAdminStatus=[integer], MplsTunnelOperStatus=[integer])

Main LSP of Tunnel switches to back up LSP in BBK.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.121.2.1.56

Minor

 communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

SessionTunnelId

ID of the tunnel

LocalLspId

Local LSP ID of a tunnel

IngressLsrId

LSR ID of the ingress on the tunnel

EgressLsrId

LSR ID of the egress on the tunnel

MplsTunnelAdminStatus
Management status of the tunnel:
  • 1: Up
  • 2: Down

MplsTunnelOperStatus
Operating status of the tunnel:
  • 1: Up
  • 2: Down

Impact on the System

The service traffic to be forwarded will be interrupted.

Possible Causes

The primary LSP was Down and the backup LSP was in Up state. The backup mode was OB.

Procedure

  1. Run the display mpls te tunnel-interface tunnel-name command on the ingress (that is, the node that generates the trap) to check the configurations of the tunnel. View the Tunnel State Desc field to check whether the tunnel is in the Down state. Then, run the display mpls te tunnel-interface last-error command to view the prompt.

    • In the case of the following error prompts, do as required:
      • If the error prompt is "Cspf failed to calculate a path for Tunnel." (indicating that the ingress is enabled with CSPF, but the CSPF path calculation fails), go to Step 2.
      • If the error prompt is "Trigger Rsvp failed", go to Step 2.
      • If the error prompt is "One LSP is deleted at smooth period", go to Step 6.
      • If the error prompt is "One LSP is deleted at Tunnel aging period", go to Step 6.
      • For other types of errors, go to Step 6.
    • If there is no error prompt, go to Step 2.

  2. Run the ping command on the ingress to check whether the destination IP address of the tunnel can be pinged.

    • If the ping fails, rectify the route fault to ensure that the destination IP address of the tunnel can be pinged, and then check whether the alarm LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp is generated.
      • If so, go to Step 7.
      • If not, go to Step 3.
    • If the ping is successful, go to Step 3.

  3. Run the display this command in the MPLS view of the ingress to check whether the mpls te cspf command is configured, that is, to check whether the CSPF is enabled.

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

  4. Run the display mpls te cspf destination command on the ingress to check for paths that satisfy specified constraints. If such paths exist, the path of the TE tunnel is displayed, indicating CSFP path computation is successful. If the output is empty, CSFP path computation fails.

    • If CSFP path computation is successful, perform the following operations to confirm tunnel configurations:
      • Run the display current-configuration interface interface-type interface-number command on the ingress to view configurations.
      • Check whether mpls te auto-frr command is run in the MPLS view. If this command exists, automatic protection is enabled. Check the tunnel configuration and find the primary tunnel. If this command does not exist, check the mpls te fast-reroute, mpls te record-route, mpls te bypass-tunnel command configurations to determine the primary and backup tunnels.
      • Check whether the explicit-path command is run to configure an explicit path.
      • Check whether the mpls te affinity property command is run to configure affinities.
      • Check whether the mpls te bandwidth command is run to configure bandwidth values.
      Run the display mpls te cspf destination command with constraints specified based on tunnel configurations. The parameters include priority setup-priority, bandwidth, explicit-path path-name, affinity properties, and hop-limit hop-limit-number. Then check whether the path that satisfies the constraints exists. If such paths exist, the path of the TE tunnel is displayed, indicating CSFP path computation is successful. If the output is empty, CSFP path computation fails.
      1. If CSPF fails to use an explicit path to compute a path, check whether the interfaces along the explicit path are Up and check whether MPLS and MPLS TE are enabled on the interfaces. If CSPF path computation is successful, check whether affinities and bandwidth values are successfully used to compute a path and whether the tunnel is established on the explicit path. Run the display mpls te cspf destination ip-address bandwidth ct0 ct0-bandwidth explicit-path path-name command.
      2. If affinities fail to be used to compute a path, run the mpls te affinity property command in the tunnel interface view to modify affinities and run the mpls te link administrative group command in the view of each interface along the path to modify the administrative group attribute.
      3. If the other constraints fail to be used to compute a path, go to Step 6.
      Check whether LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp is displayed.
      • If this alarm is generated, go to Step 7.
      • If this alarm is not generated, go to Step 5.
    • If path computation fails, go to Step 5.

  5. Run the display explicit-path command to check the interfaces along the tunnel. Then, run the display this command in the interface view of each interface of the tunnel to check whether the interface is enabled with MPLS, MPLS TE, and RSVP-TE.

    • If MPLS, MPLS TE, or RSVP-TE is not enabled, run the mpls, mpls te or mpls rsvp-te commands in the view of the interface.
    • If any interface along the tunnel is not in Up state, restart the interface. That is, run the shutdown and then undo shutdown commands in the interface view.
    Then, check whether the alarm LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp is generated.
    • If so, go to Step 7.
    • If not, go to Step 6.

  6. Collect the trap information, log information, and configuration of the switch, and Collect alarm information and configuration information, and then contact technical support personnel.
  7. End.

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.57 hwMplsTunnelBBResume

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.57 hwMplsTunnelBBResume

Description

LSPM/3/MPLSTUNNELBBRESUME:OID [oid] Main LSP of Tunnel resumes from backup LSP in BBK.(SessionTunnelId=[integer], LocalLspId=[integer], IngressLsrId=[integer], EgressLsrId=[integer], MplsTunnelAdminStatus=[integer], MplsTunnelOperStatus=[integer])

Main LSP of Tunnel resumes from backup LSP in BBK.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.121.2.1.57

Minor

 communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

SessionTunnelId

Indicates the ID of the tunnel.

LocalLspId

Indicates the local LSP ID of a tunnel.

IngressLsrId

Indicates the LSR ID of the ingress on the tunnel.

EgressLsrId

Indicates the LSR ID of the egress on the tunnel.

MplsTunnelAdminStatus
Indicates the management status of the tunnel.
  • 1: Up
  • 2: Down

MplsTunnelOperStatus
Indicates the operating status of the tunnel:
  • 1: Up
  • 2: Down

Impact on the System

Services will not be affected.

Possible Causes

When the tunnel was in the BBK inuse state, the status of the primary LSP changed from Down to Up.

Procedure

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

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.56 hwMplsTunnelBBSwitch

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.58 hwMplsExtTunnelDown

Description

LSPM/2/MPLSEXTTUNNELDOWN:OID [oid] The TE tunnel changes to Down.(SessionTunnelId=[integer], LocalLspId=[integer], IngressLsrId=[integer], EgressLsrId=[integer], OutIfIndex=[integer], hwMplsTunnelInterfaceName=[octet], hwMplsTunnelType=[integer], hwMplsTunnelAdminStatus=[integer], hwMplsTunnelOperStatus=[integer], hwMplsTunnelDownReason=[integer], OutIfName=[octet], hwMplsTunnelDownLSRId=[binary], hwMplsTunnelDownIfAddrType=[integer], hwMplsTunnelDownIfAddr=[binary])

The TE tunnel changes to Down.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.121.2.1.58

Major

 communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

SessionTunnelId

ID of the tunnel

LocalLspId

Local LSP ID of a tunnel

IngressLsrId

LSR ID of the ingress on the tunnel

EgressLsrId

LSR ID of the egress on the tunnel

OutIfIndex

Index of the outbound interface.

hwMplsTunnelInterfaceName

Name of a TE tunnel interface.

hwMplsTunnelType

Indicates the type of a tunnel

hwMplsTunnelAdminStatus

Management status of a tunnel

hwMplsTunnelOperStatus

Running status of a tunnel

hwMplsTunnelDownReason

Reason why a tunnel goes Down

OutIfName

Name of the outbound interface.

hwMplsTunnelDownLSRId

LSR ID of the error node on a tunnel

hwMplsTunnelDownIfAddrType

IP address type of the error interface on a tunnel

hwMplsTunnelDownIfAddr

IP address of the error interface on a tunnel

Impact on the System

Traffic forwarded along the tunnel will be interrupted.

Possible Causes

Cause 1: The interface went Down.

Cause 2: The route changed.

Cause 3: The link was faulty.

Procedure

  1. Run the display mpls te tunnel-interface last-error command to view the prompt.

    • In the case of the following error prompts, do as required:
      • If the error prompt is "Cspf failed to calculate a path for Tunnel." (indicating that the ingress is enabled with CSPF, but the CSPF path calculation fails), go to Step 2.
      • If the error prompt is "Trigger Rsvp failed", go to Step 2.
      • If the error prompt is "One LSP is deleted at smooth period", go to Step 6.
      • If the error prompt is "One LSP is deleted at Tunnel aging period", go to Step 6.
      • For other types of errors, go to Step 6.
    • If there is no error prompt, go to Step 2.

  2. Run the ping command on the ingress to check whether the destination IP address of the tunnel can be pinged.

  3. Run the display this command in the MPLS view of the ingress to check whether the mpls te cspf command is configured, that is, to check whether the CSPF is enabled.

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

  4. Run the display mpls te cspf destination command on the ingress to check for paths that satisfy specified constraints. If such paths exist, the path of the TE tunnel is displayed, indicating CSFP path computation is successful. If the output is empty, CSFP path computation fails.

    • If CSFP path computation is successful, perform the following operations to confirm tunnel configurations:
      • Run the display current-configuration interface interface-type interface-number command on the ingress to view configurations.
      • Check whether mpls te auto-frr command is run in the MPLS view. If this command exists, automatic protection is enabled. Check the tunnel configuration and find the primary tunnel. If this command does not exist, check the mpls te fast-reroute, mpls te record-route, mpls te bypass-tunnel command configurations to determine the primary and backup tunnels.
      • Check whether the explicit-path command is run to configure an explicit path.
      • Check whether the mpls te affinity property command is run to configure affinities.
      • Check whether the mpls te bandwidth command is run to configure bandwidth values.
      Run the display mpls te cspf destination command with constraints specified based on tunnel configurations. The parameters include priority setup-priority, bandwidth, explicit-path path-name, affinity properties, and hop-limit hop-limit-number. Then check whether the path that satisfies the constraints exists. If such paths exist, the path of the TE tunnel is displayed, indicating CSFP path computation is successful. If the output is empty, CSFP path computation fails.
      1. If CSPF fails to use an explicit path to compute a path, check whether the interfaces along the explicit path are Up and check whether MPLS and MPLS TE are enabled on the interfaces. If CSPF path computation is successful, check whether affinities and bandwidth values are successfully used to compute a path and whether the tunnel is established on the explicit path. Run the display mpls te cspf destination ip-address bandwidth ct0 ct0-bandwidth explicit-path path-name command.
      2. If affinities fail to be used to compute a path, run the mpls te affinity property command in the tunnel interface view to modify affinities and run the mpls te link administrative group command in the view of each interface along the path to modify the administrative group attribute.
      3. If the other constraints fail to be used to compute a path, go to Step 6.
      Check whether LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp is displayed.
      • If this alarm is generated, go to Step 7.
      • If this alarm is not generated, go to Step 5.
    • If path computation fails, go to Step 5.

  5. Run the display explicit-path command or identify interfaces that an LSP passes through based on the network topology to check the interfaces along the tunnel. Then, run the display this command in the interface view of each interface of the tunnel to check whether the interface is enabled with MPLS, MPLS TE, and RSVP-TE.

    • If MPLS, MPLS TE, or RSVP-TE is not enabled, run the mpls, mpls te or mpls rsvp-te commands in the view of the interface.
    • If any interface along the tunnel is not in Up state, restart the interface. That is, run the shutdown and then undo shutdown commands in the interface view, or run the restart command in the interface view.
    Then, check whether the alarm LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.59 hwMplsExtTunnelDownClear is generated.
    • If so, go to Step 7.
    • If not, go to Step 6.

  6. Collect the trap information, log information, and configuration of the switch, and Collect alarm information and configuration information, and then contact technical support personnel.
  7. End.

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.59 hwMplsExtTunnelDownClear

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.59 hwMplsExtTunnelDownClear

Description

LSPM/2/MPLSEXTTUNNELDOWNCLEAR:OID [oid] The TE tunnel Down alarm was cleared.(SessionTunnelId=[integer], LocalLspId=[integer], IngressLsrId=[integer], EgressLsrId=[integer], OutIfIndex=[integer], hwMplsTunnelInterfaceName=[octet], hwMplsTunnelType=[integer], hwMplsTunnelAdminStatus=[integer], hwMplsTunnelOperStatus=[integer], hwMplsTunnelDownReason=[integer], OutIfName=[octet])

The TE tunnel Down alarm was cleared.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.121.2.1.59

Major

 communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

SessionTunnelId

Indicates the ID of the tunnel.

LocalLspId

Indicates the local LSP ID of a tunnel.

IngressLsrId

Indicates the LSR ID of the ingress on the tunnel.

EgressLsrId

Indicates the LSR ID of the egress on the tunnel.

OutIfIndex

Indicates the index of the outbound interface.

hwMplsTunnelInterfaceName

Indicates the name of a TE tunnel interface.

hwMplsTunnelType

Indicates the type of a tunnel.

hwMplsTunnelAdminStatus

Indicates the management status of a tunnel.

hwMplsTunnelOperStatus

Indicates the running status of a tunnel.

hwMplsTunnelDownReason

Indicates the reason why a tunnel goes Down.

OutIfName

Indicates the name of the outbound interface.

Impact on the System

Services will not be affected.

Possible Causes

The tunnel was successfully set up or the attributes of the tunnel changed.

Procedure

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

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.58 hwMplsExtTunnelDown

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.62 hwMplsTunnelDelete

Description

LSPM/2/MPLSTUNNELDELETE:OID [oid] The MPLS TE tunnel was deleted.(SessionTunnelId=[integer], LocalLspId=[integer], IngressLsrId=[integer], EgressLsrId=[integer], mplsTunnelAdminStatus=[integer], mplsTunnelOperStatus=[integer], mplsTunnelIfName=[octet])

The MPLS TE tunnel was deleted.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.121.2.1.62

Major

communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

SessionTunnelId

Tunnel ID

LocalLspId

Local LSP ID

IngressLsrId

Ingress LSR ID

EgressLsrId

Egress LSR ID

mplsTunnelAdminStatus

Administrative status of a tunnel. 1: Up. 2: Down.

mplsTunnelOperStatus

Operating status of a tunnel. 1: Up. 2: Down.

mplsTunnelIfName

Tunnel interface name

Impact on the System

None

Possible Causes

The MPLS TE tunnel was deleted.

Procedure

  1. The alarm is informational only, and no action is required.

Related Information

None

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.63 hwMplsLspThresholdExceed

Description

LSPM/3/MPLSLSPTHRESHOLDEXCEED:OID [oid] The lsp count exceeds the threshold. (hwMplsLspProtocol=[integer], hwMplsLspCurrentCount=[integer], hwMplsLspThreshold=[integer], hwMplsLspTotalCount=[integer])

The number of LSPs exceeded the upper threshold.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.121.2.1.63

Minor

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

hwMplsLspProtocol

LSP protocol type

hwMplsLspCurrentCount

Number of the current LSPs

hwMplsLspThreshold

Upper threshold of LSPs

hwMplsLspTotalCount

Upper limit of supported LDP LSPs

Impact on the System

The number of hwMplsLspProtocol LSPs has reached the upper threshold. If the number continues to increase, which exceeds the threshold, services will be affected.

Possible Causes

The number of the current hwMplsLspProtocol LSPs exceeded the upper threshold.

Procedure

  1. Run the display mpls lsp command to check whether unwanted hwMplsLspProtocol LSPs exist on the device.
    • If no unwanted LSPs exist, go to Step 3.
    • If unwanted LSPs exist, go to Step 2.
  2. Run the lsp-trigger command to modify a policy used by LDP to establish LSPs to reduce unwanted LSPs. Alternatively, run the undo interface tunnel command to delete unwanted RSVP-TE tunnels, and run the undo static-lsp ingress, undo static-lsp transit, and undo static-lsp static-lsp egress commands to delete unwanted static LSPs. Then check whether the alarm is cleared.
    • If the alarm is cleared, go to Step 4.
    • If the alarm persists, go to Step 3.
  3. Collect alarm information and configuration information, and then contact technical support personnel.
  4. End.

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.64 hwMplsLspThresholdExceedClear

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.64 hwMplsLspThresholdExceedClear

Description

LSPM/3/MPLSLSPTHRESHOLDEXCEEDCLEAR:OID [oid] The lsp count falls from the threshold.(hwMplsLspProtocol=[integer])

The total number of LSPs fell below the upper threshold.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.121.2.1.64

Minor

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

hwMplsLspProtocol

LSP protocol type

Impact on the System

None.

Possible Causes

The number of LDP LSPs fell below the upper threshold.

Procedure

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

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.63 hwMplsLspThresholdExceed

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.65 hwMplsLspTotalCountExceed

Description

LSPM/2/MPLSLSPTOTALCOUNTEXCEED:OID [oid] The lsp count reaches the upper limit.(hwMplsLspProtocol=[integer], hwMplsLspTotalCount=[integer])

The total number of LSPs exceeded the upper limit.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.121.2.1.65

Major

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

hwMplsLspProtocol

LSP protocol type

hwMplsLspTotalCount

Upper limit of supported LDP LSPs

Impact on the System

The number of hwMplsLspProtocol LSPs has reached the upper limit. If subsequent LSPs continue to be established, services of the new LSPs may be affected.

Possible Causes

The number of the current hwMplsLspProtocol LSPs reached the upper limit.

Procedure

  1. Run the display mpls lsp command to check whether unwanted hwMplsLspProtocol LSPs exist on the device.
    • If no unwanted LSPs exist, go to Step 3.
    • If unwanted LSPs exist, go to Step 2.
  2. Run the lsp-trigger command to modify a policy used by LDP to establish LSPs to reduce unwanted LSPs. Alternatively, run the undo interface tunnel command to delete unwanted RSVP-TE tunnels, and run the undo static-lsp ingress, undo static-lsp transit, and undo static-lsp static-lsp egress commands to delete unwanted static LSPs. Then check whether the alarm is cleared.
    • If the alarm is cleared, go to Step 4.
    • If the alarm persists, go to Step 3.
  3. Collect alarm information and configuration information, and then contact technical support personnel.
  4. End.

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.66 hwMplsLspTotalCountExceedClear

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.66 hwMplsLspTotalCountExceedClear

Description

LSPM/2/MPLSLSPTOTALCOUNTEXCEEDCLEAR:OID [oid] The lsp count falls from the upper limit.(hwMplsLspProtocol=[integer])

The total number of LSPs fell below the upper limit.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.121.2.1.66

Major

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

hwMplsLspProtocol

LSP protocol type

Impact on the System

None.

Possible Causes

The number of LDP LSPs fell below the upper limit.

Procedure

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

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.65 hwMplsLspTotalCountExceed

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.67 hwMplsDynamicLabelThresholdExceed

Description

LSPM/4/LABEL_THRESHOLD_EXCEED:OID [oid] The dynamic label usage exceeds the threshold. BGP, LDP, RSVP TE, or MPLS VPN creation will be affected. ( hwMplsDynamicLabelTotalCount=[INTEGER], hwMplsDynamicLabelCurrentCount=[INTEGER], hwMplsDynamicLabelThresholdUpperLimit=[INTEGER], hwMplsDynamicLabelThresholdLowerLimit=[INTEGER])

Dynamic label usage reached the upper limit, which adversely affected the creation of BGP/LDP/RSVP-TE/MPLS VPNs.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.121.2.1.67

Warning

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

hwMplsDynamicLabelTotalCount

Total number of dynamic labels

hwMplsDynamicLabelCurrentCount

Number of dynamic labels used

hwMplsDynamicLabelThresholdUpperLimit

Upper limit of dynamic label usage

hwMplsDynamicLabelThresholdLowerLimit

Lower limit of dynamic label usage

Impact on the System

If dynamic label usage reaches a specific threshold, subsequent LSPs may fail to be established because all dynamic labels will be used.

Possible Causes

A great number of LSPs are established, and dynamic label usage reaches the upper limit.

Procedure

  1. Run the display mpls lsp statistics command to view statistics about LDP LSPs, RSVP-TE CR-LSPs, and BGP LSPs. Re-plan the services and delete unwanted LSPs that use dynamic labels.

    • For LDP LSPs, run the lsp-trigger command to modify a policy used by LDP to establish LSPs to reduce unwanted LSPs.
    • For RSVP LSPs, run the undo interface tunnel command to delete unwanted RSVP-TE tunnels.
    • For static LSPs, run the undo static-lsp ingress, undo static-lsp transit, and undo static-lsp static-lsp egress commands to delete unwanted static LSPs.

    Then check whether LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.68 hwMplsDynamicLabelThresholdExceedClear is generated.

    • If this clear alarm is generated, go to step 3.
    • If this clear alarm is not generated, go to step 2.
  2. Collect trap, log, and configuration information, and Collect alarm information and configuration information, and then contact technical support personnel.
  3. End.

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.68 hwMplsDynamicLabelThresholdExceedClear

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.68 hwMplsDynamicLabelThresholdExceedClear

Description

LSPM/4/LABEL_THRESHOLD_EXCEED_RESM:OID [oid] The dynamic label usage falls from the threshold. (hwMplsDynamicLabelTotalCount=[INTEGER], hwMplsDynamicLabelCurrentCount=[INTEGER], hwMplsDynamicLabelThresholdUpperLimit=[INTEGER], hwMplsDynamicLabelThresholdLowerLimit=[INTEGER])

Dynamic label usage reached the lower limit.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.121.2.1.68

Warning

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

hwMplsDynamicLabelTotalCount

Total number of dynamic labels

hwMplsDynamicLabelCurrentCount

Number of dynamic labels used

hwMplsDynamicLabelThresholdUpperLimit

Upper limit of dynamic label usage

hwMplsDynamicLabelThresholdLowerLimit

Lower limit of dynamic label usage

Impact on the System

None.

Possible Causes

Unwanted LSPs were torn down, and the system reclaimed some dynamic labels.

Procedure

  1. The log is informational only, and no action is required.

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.67 hwMplsDynamicLabelThresholdExceed

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.69 hwMplsDynamicLabelTotalCountExceed

Description

LSPM/2/LABEL_TOTAL_EXCEED:OID [oid] The dynamic label usage exceeds the threshold. BGP, LDP, RSVP TE, or MPLS VPN will fail to be created.( hwMplsDynamicLabelTotalCount=[INTEGER], hwMplsDynamicLabelCurrentCount=[INTEGER])

Dynamic label usage reached 100%, and LSPs could not be created for BGP/LDP/RSVP-TE/MPLS VPNs.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.121.2.1.69

Major

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

hwMplsDynamicLabelTotalCount

Total number of dynamic labels

hwMplsDynamicLabelCurrentCount

Number of dynamic labels used

Impact on the System

All dynamic labels are used, and no subsequent LSPs can be established.

Possible Causes

A great number of LSPs were established, and all dynamic labels were used.

Procedure

  1. Run the display mpls lsp statistics command to view statistics about LDP LSPs, RSVP-TE CR-LSPs, and BGP LSPs. Re-plan the services and delete unwanted LSPs that use dynamic labels.

    • For LDP LSPs, run the lsp-trigger command to modify a policy used by LDP to establish LSPs to reduce unwanted LSPs.
    • For RSVP LSPs, run the undo interface tunnel command to delete unwanted RSVP-TE tunnels.
    • For static LSPs, run the undo static-lsp ingress, undo static-lsp transit, and undo static-lsp static-lsp egress commands to delete unwanted static LSPs.

    Then check whether LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.70 hwMplsDynamicLabelTotalCountExceedClear is generated.

    • If this clear alarm is generated, go to step 3.
    • If this clear alarm is not generated, go to step 2.
  2. Collect log messages and Collect alarm information and configuration information, and then contact technical support personnel.
  3. End.

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.70 hwMplsDynamicLabelTotalCountExceedClear

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.70 hwMplsDynamicLabelTotalCountExceedClear

Description

LSPM/2/LABEL_TOTAL_EXCEED_RESM:OID [oid] The dynamic label count falls from the upper limit. (hwMplsDynamicLabelTotalCount=[INTEGER], hwMplsDynamicLabelCurrentCount=[INTEGER])

Dynamic label usage fell to 95%.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.121.2.1.70

Major

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

hwMplsDynamicLabelTotalCount

Total number of dynamic labels

hwMplsDynamicLabelCurrentCount

Number of dynamic labels used

Impact on the System

None.

Possible Causes

Unwanted LSPs were torn down, and the system reclaimed some dynamic labels.

Procedure

  1. The log is informational only, and no action is required.

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.69 hwMplsDynamicLabelTotalCountExceed

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.71 hwMplsResourceThresholdExceed

Description

LSPM/3/MPLSRESOURCETHRESHOLDEXCEED: OID [oid] The number of used MPLS resources exceeded the threshold. (hwMplsResourceType=[integer], hwMplsResourceCurrentCount=[integer], hwMplsResourceThreshold=[integer], hwMplsResourceTotalCount=[integer])

The proportion of used MPLS resources to all MPLS resources supported by a device reached the upper alarm threshold.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.121.2.1.71

Minor

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

hwMplsResourceType

Type of MPLS resource

hwMplsResourceCurrentCount

Number of available MPLS resources

hwMplsResourceThreshold

Upper alarm threshold for MPLS resource usage

hwMplsResourceTotalCount

Maximum number of MPLS resources supported by a device

Impact on the System

If new MPLS services are created after the number of existing MPLS resources of a specific type has exceeded the upper threshold, services may be affected.

Possible Causes

The number of MPLS resources of a specific type reached the upper threshold.

Procedure

  1. Check the hwMplsResourceType field and obtain the MPLS resource type.
  2. Check whether hwMplsResourceThreshold is set in a specified range.
    • If the value is within the specified range, go to Step 4.
    • If the value is out of the specified range, go to Step 3.
  3. Change the alarm threshold to be within the specified range. Then check whether the alarm is cleared.
    • If the alarm is cleared, go to Step 6.
    • If the alarm persists, go to Step 4.
  4. Delete configurations that use MPLS resources or configurations or messages that trigger MPLS resource consumption to reduce MPLS resource usage. Then check whether the alarm is cleared.
    • If the alarm is cleared, go to Step 6.
    • If the alarm persists, go to Step 5.
  5. Collect alarm information and configuration information, and then contact technical support personnel.
  6. End.

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.72 hwMplsResourceThresholdExceedClear

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.72 hwMplsResourceThresholdExceedClear

Description

LSPM/3/MPLSRESOURCETHRESHOLDEXCEEDCLEAR: OID [oid] The number of used MPLS resources fell below the threshold. (hwMplsResourceType=[integer])

The proportion of used MPLS resources to all MPLS resources supported by a device fell below the lower alarm threshold.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.121.2.1.72

Minor

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

hwMplsResourceType

Type of MPLS resource

Impact on the System

None

Possible Causes

The proportion of used MPLS resources to all MPLS resources supported by a device fell below the lower alarm threshold.

Procedure

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

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.71 hwMplsResourceThresholdExceed

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.73 hwMplsResourceTotalCountExceed

Description

LSPM/2/MPLSRESOURCETOTALCOUNTEXCEED: OID [oid] The number of used MPLS resources reached the maximum number. (hwMplsResourceType=[integer], hwMplsResourceTotalCount=[integer])

The number of used MPLS resources reached the maximum number of MPLS resources supported by a device.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.121.2.1.73

Major

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

hwMplsResourceType

Type of MPLS resource

hwMplsResourceTotalCount

Maximum number of MPLS resources supported by a device

Impact on the System

If new MPLS services are created after the number of existing MPLS resources of a specific type has reached the maximum number, services may be affected.

Possible Causes

The number of used MPLS resources reached the maximum number of MPLS resources supported by a device.

Procedure

  1. Check the hwMplsResourceType field and obtain the MPLS resource type.
  2. Delete configurations that use MPLS resources or configurations or messages that trigger MPLS resource consumption to reduce MPLS resource usage. Then check whether the alarm is cleared.
    • If the alarm is cleared, go to Step 4.
    • If the alarm persists, go to Step 3.
  3. Collect alarm information and configuration information, and then contact technical support personnel.
  4. End.

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.74 hwMplsResourceTotalCountExceedClear

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.74 hwMplsResourceTotalCountExceedClear

Description

LSPM/2/MPLSRESOURCETOTALCOUNTEXCEEDCLEAR: OID [oid] The number of used MPLS resources fell below the maximum number. (hwMplsResourceType=[integer])

The number of used MPLS resources fell below 95% of the maximum number of MPLS resources supported by a device.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.121.2.1.74

Major

qualityOfServiceAlarm(3)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

hwMplsResourceType

Type of MPLS resource

Impact on the System

None

Possible Causes

The number of used MPLS resources fell below 95% of the maximum number of MPLS resources supported by a device.

Procedure

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

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.73 hwMplsResourceTotalCountExceed

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.77 hwMplsTunnelCommitLost

Description

LSPM/2/MplsTunnelCommitLost: OID [oid] The configurations of some MPLS TE tunnels were not committed. Related MPLS TE tunnels fail to go Up after the device is restarted.

The configuration of an MPLS TE tunnel was not committed. The MPLS TE tunnel will not go Up after the device is restarted.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.121.2.1.77

Major

operationalViolation(8)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

Impact on the System

After the device saves the configurations and restarts, the MPLS TE tunnel fails to go Up.

Possible Causes

The configuration of an MPLS TE tunnel was not committed.

Procedure

  1. Check the configurations of all MPLS TE tunnels. Check whether some tunnel configurations are not committed based on service deployment information. Run the display current-configuration interface Tunnel command and find each tunnel interface on which the mpls te commit command is not run.
  2. Confirm whether the mpls te commit command needs to run to commit the configurations of each MPLS TE tunnel.

    • If the configuration needs to be committed, run the mpls te commit command on the tunnel interface and go to Step 3.
    • If the configuration does not need to be committed, go to Step 3.

  3. End.

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.78 hwMplsTunnelCommitLostClear

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.78 hwMplsTunnelCommitLostClear

Description

LSPM/2/MplsTunnelCommitLostClear: OID [oid] The configurations of all MPLS TE tunnels were committed.

The configurations of all MPLS TE tunnels were committed.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.121.2.1.78

Major

operationalViolation(8)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

Impact on the System

None.

Possible Causes

The configurations of all MPLS TE tunnels were committed.

Procedure

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

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.77 hwMplsTunnelCommitLost

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.79 hwMplsTunnelHotstandbySwitch

Description

LSPM/2/MPLSTUNNELHOTSTANDBYSWITCH:OID [oid] Traffic switched from the primary LSP to the hot-standby LSP.(SessionTunnelId=[integer], LocalLspId=[integer], IngressLsrId=[integer], EgressLsrId=[integer], TunnelName=[OCTET])

The trap message was output when the primary LSP went Down and traffic was switched to a hot-standby LSP.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.121.2.1.79

Major

 communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

SessionTunnelId

ID of the tunnel

LocalLspId

Local LSP ID of a tunnel

IngressLsrId

LSR ID of the ingress on the tunnel

EgressLsrId

LSR ID of the egress on the tunnel

TunnelName

Indicates the tunnel name.

Impact on the System

Services will not be affected.

Possible Causes

The primary LSP was Down and the backup LSP was in use. The backup mode was HSB.

Procedure

  1. Run the display mpls te tunnel-interface tunnel interface-number command on the ingress (that is, the node that generates the trap) to check the configurations of the tunnel. View the Tunnel State Desc field to check whether the tunnel is in the Down state. Then, run the display mpls te tunnel-interface last-error command to view the prompt.

    • In the case of the following error prompts, do as required:
      • If the error prompt is "Cspf failed to calculate a path for Tunnel." (indicating that the ingress is enabled with CSPF, but the CSPF path calculation fails), go to Step 2.
      • If the error prompt is "Trigger Rsvp failed", go to Step 2.
      • If the error prompt is "One LSP is deleted at smooth period", go to Step 6.
      • If the error prompt is "One LSP is deleted at Tunnel aging period", go to Step 6.
      • For other types of errors, go to Step 6.
    • If there is no error prompt, go to Step 2.

  2. Run the ping command on the ingress to check whether the destination IP address of the tunnel can be pinged.

    • If the ping fails, rectify the route fault to ensure that the destination IP address of the tunnel can be pinged, and then check whether the alarm LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp is generated.
      • If so, go to Step 7.
      • If not, go to Step 3.
    • If the ping is successful, go to Step 3.

  3. Run the display this command in the MPLS view of the ingress to check whether the mpls te cspf command is configured, that is, to check whether the CSPF is enabled.

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

  4. Run the display mpls te cspf destination command on the ingress to check for paths that satisfy specified constraints. If such paths exist, the path of the TE tunnel is displayed, indicating CSFP path computation is successful. If the output is empty, CSFP path computation fails.

    • If CSFP path computation is successful, perform the following operations to confirm tunnel configurations:
      • Run the display current-configuration interface interface-type interface-number command on the ingress to view configurations.
      • Check whether mpls te auto-frr command is run in the MPLS view. If this command exists, automatic protection is enabled. Check the tunnel configuration and find the primary tunnel. If this command does not exist, check the mpls te fast-reroute, mpls te record-route, mpls te bypass-tunnel command configurations to determine the primary and backup tunnels.
      • Check whether the explicit-path command is run to configure an explicit path.
      • Check whether the mpls te affinity property command is run to configure affinities.
      • Check whether the mpls te bandwidth command is run to configure bandwidth values.
      Run the display mpls te cspf destination command with constraints specified based on tunnel configurations. The parameters include priority setup-priority, bandwidth, explicit-path path-name, affinity properties, and hop-limit hop-limit-number. Then check whether the path that satisfies the constraints exists. If such paths exist, the path of the TE tunnel is displayed, indicating CSFP path computation is successful. If the output is empty, CSFP path computation fails.
      1. If CSPF fails to use an explicit path to compute a path, check whether the interfaces along the explicit path are Up and check whether MPLS and MPLS TE are enabled on the interfaces. If CSPF path computation is successful, check whether affinities and bandwidth values are successfully used to compute a path and whether the tunnel is established on the explicit path. Run the display mpls te cspf destination ip-address bandwidth ct0 ct0-bandwidth explicit-path path-name command.
      2. If affinities fail to be used to compute a path, run the mpls te affinity property command in the tunnel interface view to modify affinities and run the mpls te link administrative group command in the view of each interface along the path to modify the administrative group attribute.
      3. If the other constraints fail to be used to compute a path, go to Step 6.
      Check whether LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp is displayed.
      • If the alarm is displayed, go to step 7.
      • If the alarm is not displayed, go to Step 5.
    • If path computation fails, go to Step 5.

  5. Run the display explicit-path command to check the interfaces along the tunnel. Then, run the display this command in the interface view of each interface of the tunnel to check whether the interface is enabled with MPLS, MPLS TE, and RSVP-TE.

    • If MPLS, MPLS TE, or RSVP-TE is not enabled, run the mpls, mpls te or mpls rsvp-te commands in the view of the interface.
    • If any interface along the tunnel is not in Up state, restart the interface. That is, run the shutdown and then undo shutdown commands in the interface view, or run the restart command in the interface view.
    Then, check whether the alarm LSPM_1.3.6.1.2.1.10.166.3.0.1 mplsTunnelUp is generated.
    • If so, go to Step 7.
    • If not, go to Step 6.

  6. Collect the trap information, log information, and configuration of the switch, and Collect alarm information and configuration information, and then contact technical support personnel.
  7. End.

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.80 hwMplsTunnelHotstandbyResume

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.80 hwMplsTunnelHotstandbyResume

Description

LSPM/2/MPLSTUNNELHOTSTANDBYRESUME:OID [oid] Traffic switched back from the hot-standby LSP to the primary LSP.(SessionTunnelId=[integer], LocalLspId=[integer], IngressLsrId=[integer], EgressLsrId=[integer], TunnelName=[OCTET])

The trap message was output when the primary LSP went Up and traffic was switched back from the hot-standby LSP to the primary LSP.

Attribute

Alarm ID Alarm Severity Alarm Type
1.3.6.1.4.1.2011.5.25.121.2.1.80

Major

 communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

SessionTunnelId

Indicates the ID of the tunnel.

LocalLspId

Indicates the local LSP ID of a tunnel.

IngressLsrId

Indicates the LSR ID of the ingress on the tunnel.

EgressLsrId

Indicates the LSR ID of the egress on the tunnel.

TunnelName

Indicates the tunnel name.

Impact on the System

Services will not be affected.

Possible Causes

When the tunnel was in the HSB inuse state, the status of the primary LSP changed from Down to Up.

Procedure

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

Related Information

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.79 hwMplsTunnelHotstandbySwitch

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.83 hwMplsTeLspBfdDown

Description

LSPM/2/MPLSTELSPBFDDOWN: OID [oid] The status of BFD for TE LSP changed to down.(SessionTunnelId=[integer], LocalLspId=[integer], IngressLsrId=[integer], EgressLsrId=[integer], TunnelName=[OCTET], LspRole=[integer])

BFD detected a TE LSP fault.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.121.2.1.83

Major

communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

SessionTunnelId

Tunnel ID

LocalLspId

Local LSP ID

IngressLsrId

LSR ID of the ingress

EgressLsrId

Egress LSR ID

TunnelName

Tunnel name

LspRole

LSP type

Impact on the System

Traffic to be transmitted over the faulty TE LSP is interrupted.

Possible Causes

BFD detected a TE LSP fault.

Procedure

LSPM_1.3.6.1.4.1.2011.5.25.121.2.1.84 hwMplsTeLspBfdDownClear

Description

LSPM/2/MPLSTELSPBFDDOWNCLEAR: OID [oid] The BFD for TE LSP down alarm was cleared.(SessionTunnelId=[integer], LocalLspId=[integer], IngressLsrId=[integer], EgressLsrId=[integer], TunnelName=[OCTET], LspRole=[integer])

The TE LSP fault monitored by BFD was rectified.

Attribute

Alarm ID Alarm Severity Alarm Type

1.3.6.1.4.1.2011.5.25.121.2.1.84

Major

communicationsAlarm(2)

Parameters

Name Meaning

oid

Indicates the MIB object ID of the alarm.

SessionTunnelId

Tunnel ID

LocalLspId

Local LSP ID

IngressLsrId

LSR ID of the ingress

EgressLsrId

Egress LSR ID

TunnelName

Tunnel name

LspRole

LSP type

Impact on the System

Services will not be affected.

Possible Causes

Cause 1: BFD detected a TE LSP Up event.

Cause 2: The TE LSP monitored by BFD was deleted.

Cause 3: The BFD session was deleted.

Procedure

  • This trap message is informational only, and no action is required.
Translation
日本語 简体中文
Download
Updated: 2022-05-25

Document ID: EDOC1100127008

Views: 80342

Downloads: 335

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Digital Signature File

Digital Signature Authentication Mode
Share
Previous Next

Copyright © 2023 Huawei Technologies Co., Ltd. All rights reserved.

You are going to visit :