11-MPLS

HomeSupportRoutersH3C SR8800-F Router SeriesReference GuidesMIB CompanionH3C SR8800-F Routers MIB Reference-R8530Pxx-6W10011-MPLS
11-HH3C-MPLSTE-MIB
Title Size Download
11-HH3C-MPLSTE-MIB 232.72 KB

HH3C-MPLSTE-MIB

About this MIB

Use this MIB to manage MPLS TE and RSVP TE settings.

MIB file name

hh3c-mplste.mib

Root object

iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).hh3c(25506).hh3cCommon(2).hh3cMplsTe(143)

Scalar objects

hh3cMplsTeStatus (1.3.6.1.4.1.25506.2.143.1.1.1)

Object (OID)

Access

Syntax

Value range

Description

Implementation

hh3cMplsTeStatus (1.3.6.1.4.1.25506.2.143.1.1.1)

read-write

TruthValue

true(1),

false(2)

Globally enable MPLS TE (mpls te) or TE attribute (te attribute enable) for the device.

As per the MIB.

 

hh3cMplsTeRsvpStatus (1.3.6.1.4.1.25506.2.143.1.1.2)

Object (OID)

Access

Syntax

Value range

Description

Implementation

hh3cMplsTeRsvpStatus (1.3.6.1.4.1.25506.2.143.1.1.2)

read-write

TruthValue

true(1),

false(2)

Enabling status of global RSVP TE.

As per the MIB.

 

hh3cMplsTeTunnelInfo (1.3.6.1.4.1.25506.2.143.1.1.3)

Object (OID)

Access

Syntax

Value range

Description

Implementation

hh3cMplsTeTunnelInfo (1.3.6.1.4.1.25506.2.143.1.1.3)

accessible-for-notify

OCTET STRING

OCTET STRING (1..127)

MPLS TE tunnel information

As per the MIB.

 

Tabular objects

hh3cMplsTeTable

About this table

This table specifies per-interface MPLS TE settings.

Support for operations

CreateSupported only when the value for hh3cMplsTeCapability is true(1)

Edit/ModifyNot supported

DeleteSupported

ReadSupported

Columns

The table index is hh3cMplsTeIndex.

Object (OID)

Access

Syntax

Value range

Description

Implementation

hh3cMplsTeIndex

(1.3.6.1.4.1.25506.2.143.1.2.1.1)

not-accessible

Unsigned32

Unsigned32

(1..2147483647)

Index of an MPLS TE interface.

As per the MIB.

hh3cMplsTeCapability

(1.3.6.1.4.1.25506.2.143.1.2.1.2)

read-create

TruthValue

true(1),

false(2)

MPLS TE capability of the interface. No MPLS TE capability information can be obtained when MPLS TE is not enabled on the interface.

As per the MIB.

hh3cMplsTeRowStatus

(1.3.6.1.4.1.25506.2.143.1.2.1.3)

read-create

RowStatus

active(1)

createAndGo(4)

destroy(6).

Row status.

Supports only the following values: active(1), createAndGo(4), and destroy(6).

 

hh3cMplsTeRsvpTable

About this table

This table specifies per-interface RSVP TE settings.

Support for operations

CreateSupported only when the value for hh3cMplsTeRsvpCapability is true(1)

Edit/ModifyNot supported

DeleteSupported

ReadSupported

Columns

The table index is hh3cMplsTeRsvpIndex.

Object (OID)

Access

Syntax

Value range

Description

Implementation

hh3cMplsTeRsvpIndex

(1.3.6.1.4.1.25506.2.143.1.3.1.1)

not-accessible

Unsigned32

Unsigned32

(1..4294967295)

Index of an RSVP TE interface.

As per the MIB.

hh3cMplsTeRsvpRowStatus

(1.3.6.1.4.1.25506.2.143.1.3.1.3)

read-create

RowStatus

active(1)

createAndGo(4)

destroy(6).

Row status.

Supports only the following values: active(1), createAndGo(4), and destroy(6).

 

Notifications

hh3cMplsTeTunnelHsbSwitch

Basic information

OID

Event

Type

Severity

Recovery notification

Default status

1.3.6.1.4.1.25506.2.143.0.1

The primary LSP fails, and traffic is switched to the hot-standby backup LSP.

Error

Major

1.3.6.1.4.1.25506.2.143.0.2 (hh3cMplsTeTunnelHsbResume)

ON

 

Notification triggers

This notification is generated when the primary LSP fails and the system detects a hot-standby backup LSP and switches the traffic to the backup LSP.

System impact

The TE tunnel uses the hot-standby backup LSP for forwarding, which weakens the risk resistance capability.

Status control

ON

CLI: Use the snmp-agent trap enable te-private hsb-switch command.

OFF

CLI: Use the undo snmp-agent trap enable te-private hsb-switch command.

Object

OID (object name)

Description

Index

Type

Value range

hh3cMplsTeTunnelInfo (1.3.6.1.4.1.25506.2.143.1.1.3)

MPLS TE tunnel information

N/A

OCTET STRING

As per the MIB.

 

Recommended action

To resolve this issue:

1.Check the current tunnel interface configuration, RSVP and IGP configuration, and the whole tunnel path and bandwidth.

  - If an explicit path is configured, check whether the interfaces on each hop of the explicit path are faulty.

If yes, proceed to step 2.

If not, proceed to step 3.

  - If no explicit path is configured, check whether a path that satisfies the tunnel requirements exists. If yes, proceed to step 3.

2.Clear link faults.

3.Collect alarm information and configuration data, and then contact Technical Support for help.

hh3cMplsTeTunnelHsbResume

Basic information

OID

Event

Type

Severity

Recovery notification

Default status

1.3.6.1.4.1.25506.2.143.0.2

The primary LSP recovers from failure and traffic is switched back from the backup LSP to the primary LSP.

Recovery

Major

N/A (N/A)

ON

 

Notification triggers

This notification is generated when the primary LSP recovers from failure and traffic is switched back from the hot-standby backup LSP to the primary LSP.

System impact

No negative impact on services.

Status control

ON

CLI: Use the snmp-agent trap enable te-private hsb-switch command.

OFF

CLI: Use the undo snmp-agent trap enable te-private hsb-switch command.

Object

OID (object name)

Description

Index

Type

Value range

hh3cMplsTeTunnelInfo (1.3.6.1.4.1.25506.2.143.1.1.3)

MPLS TE tunnel information

N/A

OCTET STRING

As per the MIB.

 

Recommended action

No action is required.

hh3cMplsTeTunnelObSwitch

Basic information

OID

Event

Type

Severity

Recovery notification

Default status

1.3.6.1.4.1.25506.2.143.0.3

The primary LSP fails and traffic is switched to the ordinary backup LSP.

Error

Major

1.3.6.1.4.1.25506.2.143.0.4 (hh3cMplsTeTunnelObResume)

ON

 

Notification triggers

This notification is generated when the primary LSP fails and an ordinary backup LSP becomes up and takes over traffic forwarding.

System impact

The TE tunnel uses the ordinary backup LSP for forwarding, which weakens the risk resistance capability.

Status control

ON

CLI: Use the snmp-agent trap enable te-private ob-switch command.

OFF

CLI: Use the undo snmp-agent trap enable te-private ob-switch command.

Object

OID (object name)

Description

Index

Type

Value range

hh3cMplsTeTunnelInfo (1.3.6.1.4.1.25506.2.143.1.1.3)

MPLS TE tunnel information

N/A

OCTET STRING

As per the MIB.

 

Recommended action

To resolve this issue:

1.Check the current tunnel interface configuration, RSVP and IGP configuration, and the whole tunnel path and bandwidth.

  - If an explicit path is configured, check whether the interfaces on each hop of the explicit path are faulty.

If yes, proceed to step 2.

If not, proceed to step 3.

  - If no explicit path is configured, check whether a path that satisfies the tunnel requirements exists. If yes, proceed to step 3.

2.Clear link faults.

3.Collect log messages and configuration data, and then contact Technical Support for help.

hh3cMplsTeTunnelObResume

Basic information

OID

Event

Type

Severity

Recovery notification

Default status

1.3.6.1.4.1.25506.2.143.0.4

The primary LSP recovers from failure and traffic is switched back from the ordinary backup LSP to the primary LSP.

Recovery

Major

N/A (N/A)

ON

 

Notification triggers

This notification is generated when the primary LSP recovers from failure and traffic is switched back from the ordinary backup LSP to the primary LSP.

System impact

No negative impact on the system.

Status control

ON

CLI: Use the snmp-agent trap enable te-private ob-switch command.

OFF

CLI: Use the undo snmp-agent trap enable te-private ob-switch command.

Object

OID (object name)

Description

Index

Type

Value range

hh3cMplsTeTunnelInfo (1.3.6.1.4.1.25506.2.143.1.1.3)

MPLS TE tunnel information

N/A

OCTET STRING

As per the MIB.

 

Recommended action

No action is required.

hh3cMplsTeTunnelHsbLspDown

Basic information

OID

Event

Type

Severity

Recovery notification

Default status

1.3.6.1.4.1.25506.2.143.0.5

Hot-standby LSP down

Error

Major

1.3.6.1.4.1.25506.2.143.0.6 (hh3cMplsTeTunnelHsbLspUp)

ON

 

Notification triggers

For all types of tunnels, this notification might be generated when the following events occur:

The interface went Down.

The configuration of the tunnel was deleted.

The link was faulty.

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

The tunnel was manually shut down.

Others.

For RSVP-TE tunnels, this notification might be generated when the following events occur:

RSVP-TE LSP resources were preempted.

Transmission of an RSVP message timed out.

RSVP Hello mechanism detected a downstream node failure.

CSPF failed to calculate a path.

For Segment Routing TE tunnels, this notification might be generated when the following events occur:

IGP calculation or verification failed.

The main and standby LSP are not configured with explicit-path.

System impact

No negative impact on services that do not use the hot-standby LSP of the tunnel for forwarding.

Services that use the hot-standby LSP of the tunnel for forwarding will be switch to another available LSP of the tunnel or will be dropped if no other LSPs are available for the tunnel.

Status control

ON

CLI: Use the snmp-agent trap enable te-private hsblsp-up-down command.

OFF

CLI: Use the undo snmp-agent trap enable te-private hsblsp-up-down command.

Object

OID (object name)

Description

Index

Type

Value range

hh3cMplsTeTunnelInfo (1.3.6.1.4.1.25506.2.143.1.1.3)

MPLS TE tunnel information

N/A

OCTET STRING

As per the MIB.

 

Recommended action

To resolve this issue:

1.Check the current tunnel interface configuration, RSVP and IGP configuration, and the whole tunnel path and bandwidth.

  - If an explicit path is configured, check whether the interfaces on each hop of the explicit path are faulty.

If yes, clear link faults.

If not, proceed to step 2.

  - If no explicit path is configured, check whether a path that satisfies the tunnel requirements exists. If yes, proceed to step 2.

2.For an RSVP-TE tunnel, check whether RSVP, link bandwidth and link affinity settings are correct.

  - If the settings are correct but the issue persists, go to step 3.

  - If the settings are not correct, edit the related configuration.

  - If the tunnel is not an RSVP-TE tunnel, go to step 3.

3.Collect log messages and configuration data, and then contact Technical Support for help.

hh3cMplsTeTunnelHsbLspUp

Basic information

OID

Event

Type

Severity

Recovery notification

Default status

1.3.6.1.4.1.25506.2.143.0.6

Hot-standby LSP up

Recovery

Major

N/A (N/A)

ON

 

Notification triggers

This notification is generated when LSP hot standby is configured on an MPLS TE tunnel interface and the hot-standby LSP comes up.

System impact

No negative impact on the system.

Status control

ON

CLI: Use the snmp-agent trap enable te-private hsblsp-up-down command.

OFF

CLI: Use the undo snmp-agent trap enable te-private hsblsp-up-down command.

Object

OID (object name)

Description

Index

Type

Value range

hh3cMplsTeTunnelInfo (1.3.6.1.4.1.25506.2.143.1.1.3)

MPLS TE tunnel information

N/A

OCTET STRING

As per the MIB.

 

Recommended action

No action is required.

hh3cMplsTeTunnelObLspDown

Basic information

OID

Event

Type

Severity

Recovery notification

Default status

1.3.6.1.4.1.25506.2.143.0.7

Ordinary backup LSP down

Error

Major

1.3.6.1.4.1.25506.2.143.0.8 (hh3cMplsTeTunnelObLspUp)

ON

 

Notification triggers

For all types of tunnels, this notification might be generated when the following events occur:

The interface went Down.

The configuration of the tunnel was deleted.

The link was faulty.

The tunnel was manually shut down.

Main LSP changed UP.

Others.

For RSVP-TE tunnels, this notification might be generated when the following events occur:

RSVP-TE LSP resources were preempted.

Transmission of an RSVP message timed out.

RSVP Hello mechanism detected a downstream node failure.

CSPF failed to calculate a path.

For Segment Routing TE tunnels, this notification might be generated when the following events occur:

IGP calculation or verification failed.

System impact

No negative impact on services that do not use the ordinary LSP of the tunnel for forwarding.

Services that use the ordinary LSP of the tunnel for forwarding will be switch to another available LSP of the tunnel or will be dropped if no other LSPs are available for the tunnel.

Status control

ON

CLI: Use the snmp-agent trap enable te-private oblsp-up-down command.

OFF

CLI: Use the undo snmp-agent trap enable te-private oblsp-up-down command.

Object

OID (object name)

Description

Index

Type

Value range

hh3cMplsTeTunnelInfo (1.3.6.1.4.1.25506.2.143.1.1.3)

MPLS TE tunnel information

N/A

OCTET STRING

As per the MIB.

 

Recommended action

To resolve this issue:

1.Check the current tunnel interface configuration, RSVP and IGP configuration, and the whole tunnel path and bandwidth.

  - If an explicit path is configured, check whether the interfaces on each hop of the explicit path are faulty.

If yes, clear link faults.

If not, proceed to step 2.

  - If no explicit path is configured, check whether a path that satisfies the tunnel requirements exists. If yes, proceed to step 2.

2.For an RSVP-TE tunnel, check whether RSVP, link bandwidth and link affinity settings are correct.

  - If the settings are correct but the issue persists, go to step 3.

  - If the settings are not correct, edit the related configuration.

  - If the tunnel is not an RSVP-TE tunnel, go to step 3.

3.Collect log messages and configuration data, and then contact Technical Support for help.

hh3cMplsTeTunnelObLspUp

Basic information

OID

Event

Type

Severity

Recovery notification

Default status

1.3.6.1.4.1.25506.2.143.0.8

Ordinary backup LSP up

Recovery

Major

N/A (N/A)

ON

 

Notification triggers

This notification is generated when ordinary backup is configured on an MPLS TE tunnel interface and the backup LSP comes up.

System impact

No negative impact on the system.

Status control

ON

CLI: Use the snmp-agent trap enable te-private hsblsp-up-down command.

OFF

CLI: Use the undo snmp-agent trap enable te-private hsblsp-up-down command.

Object

OID (object name)

Description

Index

Type

Value range

hh3cMplsTeTunnelInfo (1.3.6.1.4.1.25506.2.143.1.1.3)

MPLS TE tunnel information

N/A

OCTET STRING

As per the MIB.

 

Recommended action

No action is required.

hh3cMplsTeTunnelMainLspDown

Basic information

OID

Event

Type

Severity

Recovery notification

Default status

1.3.6.1.4.1.25506.2.143.0.9

Primary LSP down

Error

Major

1.3.6.1.4.1.25506.2.143.0.10 (hh3cMplsTeTunnelMainLspUp)

ON

 

Notification triggers

For all types of tunnels, this notification might be generated when the following events occur:

The interface went Down.

The configuration of the tunnel was deleted.

The link was faulty.

The tunnel was manually shut down.

Others.

For RSVP-TE tunnels, this notification might be generated when the following events occur:

RSVP-TE LSP resources were preempted.

Transmission of an RSVP message timed out.

RSVP Hello mechanism detected a downstream node failure.

CSPF failed to calculate a path.

For Segment Routing TE tunnels, this notification might be generated when the following events occur:

IGP calculation or verification failed.

System impact

No negative impact on services that do not use the primary LSP of the tunnel for forwarding.

Services that use the primary LSP of the tunnel for forwarding will be switch to an available backup LSP of the tunnel or will be dropped if no backup LSPs are available for the tunnel.

Status control

ON

CLI: Use the snmp-agent trap enable te-private mainlsp-up-down command.

OFF

CLI: Use the undo snmp-agent trap enable te-private mainlsp-up-down command.

Object

OID (object name)

Description

Index

Type

Value range

hh3cMplsTeTunnelInfo (1.3.6.1.4.1.25506.2.143.1.1.3)

MPLS TE tunnel information

N/A

OCTET STRING

As per the MIB.

 

Recommended action

To resolve this issue:

1.Check the current tunnel interface configuration, RSVP and IGP configuration, and the whole tunnel path and bandwidth.

  - If an explicit path is configured, check whether the interfaces on each hop of the explicit path are faulty.

If yes, clear link faults.

If not, proceed to step 2.

  - If no explicit path is configured, check whether a path that satisfies the tunnel requirements exists. If yes, proceed to step 2.

2.For an RSVP-TE tunnel, check whether RSVP, link bandwidth and link affinity settings are correct.

  - If the settings are correct but the issue persists, go to step 3.

  - If the settings are not correct, edit the related configuration.

  - If the tunnel is not an RSVP-TE tunnel, go to step 3.

3.Collect log messages and configuration data, and then contact Technical Support for help.

hh3cMplsTeTunnelMainLspUp

Basic information

OID

Event

Type

Severity

Recovery notification

Default status

1.3.6.1.4.1.25506.2.143.0.10

Primary LSP up

Recovery

Major

N/A (N/A)

ON

 

Notification triggers

This notification is generated when the primary LSP comes up from the down state.

System impact

The tunnel will come up. If traffic was switched to the backup LSP of the tunnel, the tunnel will switch the traffic back to the primary LSP.

Status control

ON

CLI: Use the snmp-agent trap enable te-private mainlsp-up-down command.

OFF

CLI: Use the undo snmp-agent trap enable te-private mainlsp-up-down command.

Object

OID (object name)

Description

Index

Type

Value range

hh3cMplsTeTunnelInfo (1.3.6.1.4.1.25506.2.143.1.1.3)

MPLS TE tunnel information

N/A

OCTET STRING

As per the MIB.

 

Recommended action

No action is required.

hh3cMplsTeTunnelChangeBw

Basic information

OID

Event

Type

Severity

Recovery notification

Default status

1.3.6.1.4.1.25506.2.143.0.11

MPLS TE tunnel bandwidth changes.

Informational

Major

N/A (N/A)

ON

 

Notification triggers

This notification is generated when the bandwidth of the MPLS TE tunnel changes in the following situation:

The bandwidth was set or edited manually.

The bandwidth was adjusted automatically by the automatic bandwidth adjustment feature.

System impact

No negative impact on the system.

Status control

ON

CLI: Use the snmp-agent trap enable te-private tunnelbw-change command.

OFF

CLI: Use the undo snmp-agent trap enable te-private tunnelbw-change command.

Object

OID (object name)

Description

Index

Type

Value range

hh3cMplsTeTunnelInfo (1.3.6.1.4.1.25506.2.143.1.1.3)

MPLS TE tunnel information

N/A

OCTET STRING

As per the MIB.

 

Recommended action

No action is required.

hh3cMplsTeAutoTunnelUp

Basic information

OID

Event

Type

Severity

Recovery notification

Default status

1.3.6.1.4.1.25506.2.143.0.12

Automatic TE tunnel up

Informational

Major

None (None)

ON

 

Notification triggers

This notification is generated when an automatic TE tunnel comes up.

System impact

No negative impact on the system.

Status control

ON

CLI: Use the snmp-agent trap enable te-private auto-tunnel-up command.

OFF

CLI: Use the undo snmp-agent trap enable te-private auto-tunnel-up command.

Object

OID (object name)

Description

Index

Type

Value range

hh3cMplsTeTunnelInfo (1.3.6.1.4.1.25506.2.143.1.1.3)

MPLS TE tunnel information

N/A

OCTET STRING

As per the MIB.

 

Recommended action

No action is required.

hh3cMplsTeLspBfdDown

Basic information

OID

Event

Type

Severity

Recovery notification

Default status

1.3.6.1.4.1.25506.2.143.0.13

BFD detected TE LSP Down.

Error

Major

1.3.6.1.4.1.25506.2.143.0.14 (hh3cMplsTeLspBfdDownClear)

ON

 

Notification triggers

This notification is generated when TE LSP down is detected by BFD.

System impact

If the tunnel protection is not configured, the tunnel's traffic will be lost. If tunnel protection is configured, the tunnel's traffic will be switched to the backup LSP for forwarding.

Status control

ON

CLI: Use the snmp-agent trap enable te-private lspbfd-up-down command.

OFF

CLI: Use the undo snmp-agent trap enable te-private lspbfd-up-down command.

Object

OID (object name)

Description

Index

Type

Value range

hh3cMplsTeTunnelInfo (1.3.6.1.4.1.25506.2.143.1.1.3)

MPLS TE tunnel information.

N/A

OCTET STRING

As per the MIB.

 

Recommended action

To resolve this issue:

1.Verify that no packet loss occurs on the links of the LSP.

2.If the issue persists, contact Technical Support for help.

hh3cMplsTeLspBfdDownClear

Basic information

OID

Event

Type

Severity

Recovery notification

Default status

1.3.6.1.4.1.25506.2.143.0.14

The alarm that BFD detected TE LSP Down was cleared.

Recovery

Major

N/A (N/A)

ON

 

Notification triggers

This notification might be generated when the following events occur:

BFD detected that a down TE LSP goes up.

The down TE LSP was deleted.

The BFD session for the down TE LSP was deleted.

System impact

No negative impact on the system.

Status control

ON

CLI: Use the snmp-agent trap enable te-private lspbfd-up-down command.

OFF

CLI: Use the undo snmp-agent trap enable te-private lspbfd-up-down command.

Object

OID (object name)

Description

Index

Type

Value range

hh3cMplsTeTunnelInfo (1.3.6.1.4.1.25506.2.143.1.1.3)

MPLS TE tunnel information.

N/A

OCTET STRING

As per the MIB.

 

Recommended action

No action is required.

hh3cMplsTeTunnelDelete

Basic information

OID

Event

Type

Severity

Recovery notification

Default status

1.3.6.1.4.1.25506.2.143.0.15

The MPLS TE tunnel was deleted.

Informational

Major

N/A (N/A)

ON

 

Notification triggers

This notification is generated when an MPLS TE tunnel is deleted.

System impact

Traffic forwarding on the tunnel is interrupted.

Status control

ON

CLI: Use the snmp-agent trap enable te-private tunnel-delete command.

OFF

CLI: Use the undo snmp-agent trap enable te-private tunnel-delete command.

Object

OID (object name)

Description

Index

Type

Value range

hh3cMplsTeTunnelInfo (1.3.6.1.4.1.25506.2.143.1.1.3)

MPLS TE tunnel information.

N/A

OCTET STRING

As per the MIB.

 

Recommended action

No action is required.

hh3cMplsTeAutoTunnelMainLspUp

Basic information

OID

Event

Type

Severity

Recovery notification

Default status

1.3.6.1.4.1.25506.2.143.0.16

The main LSP of the automatic tunnel went up.

Informational

Major

-

ON

 

Notification triggers

This notification is generated when the main LSP of the automatic tunnel goes up.

System impact

No negative impact on the system.

Status control

ON

CLI: Use the snmp-agent trap enable te-private auto-tunnel-mainlsp-up command.

OFF

CLI: Use the undo snmp-agent trap enable te-private auto-tunnel-mainlsp-up command.

Object

OID (object name)

Description

Index

Type

Value range

hh3cMplsTeTunnelInfo (1.3.6.1.4.1.25506.2.143.1.1.3)

MPLS TE tunnel information.

N/A

OCTET STRING

As per the MIB.

 

Recommended action

No action is required.

hh3cMplsTeP2mpTunnelSubLspDown

Basic information

OID

Event

Type

Severity

Recovery notification

Default status

1.3.6.1.4.1.25506.2.143.0.17

P2MP TE tunnel sub-LSP DOWN

Error

Major

N/A (N/A)

ON

 

Notification triggers

This notification might be generated when the following events occur:

The interface went Down

The configuration of the tunnel was deleted.

The link was faulty.

The out interface of the RSVP LSP ingress is down.

RSVP-TE LSP resources were preempted.

Transmission of an RSVP message timed out.

RSVP Hello mechanism detected a downstream node failure.

Others

System impact

If FRR is configured for the sub-LSP, traffic will be switched to the bypass tunnel. If FRR is not configured, the multicast traffic forwarded on the sub-LSP will be lost.

Status control

ON

CLI: Use the snmp-agent trap enable te-private p2mp-sublsp-down command.

OFF

CLI: Use the undo snmp-agent trap enable te-private p2mp-sublsp-down command.

Object

OID (object name)

Description

Index

Type

Value range

hh3cMplsTeTunnelInfo (1.3.6.1.4.1.25506.2.143.1.1.3)

MPLS TE tunnel information.

N/A

OCTET STRING

As per the MIB.

 

Recommended action

1.Identify the destination address of the down sub-LSP by using the display mpls te p2mp tunnel-interface command and then check if the link to the destination address is faulty.

  - If yes, repair the link.

  - If not, proceed to step 2.

2.Check whether the tunnel related configuration and protocol configuration are correct.

  - If yes, proceed to step 3.

  - If not, correct the configurations.

3.Collect log messages and configuration data, and then contact Technical Support for help.

hh3cMplsTeP2mpTunnelDown

Basic information

OID

Event

Type

Severity

Recovery notification

Default status

1.3.6.1.4.1.25506.2.143.0.18

P2MP TE tunnel DOWN

Error

Major

1.3.6.1.4.1.25506.2.143.0.19 (hh3cMplsTeP2mpTunnelUp)

ON

 

Notification triggers

This notification might be generated when the following events occur:

Multicast service changed.

The link was faulty.

P2MP Tunnel All Sub Lsp Down.

Others.

System impact

Multicast services forwarded by this tunnel are interrupted.

Status control

ON

CLI: Use the snmp-agent trap enable te-private p2mp-tunnel-up-down command.

OFF

CLI: Use the undo snmp-agent trap enable te-private p2mp-tunnel-up-down command.

Object

OID (object name)

Description

Index

Type

Value range

hh3cMplsTeTunnelInfo (1.3.6.1.4.1.25506.2.143.1.1.3)

MPLS TE tunnel information.

N/A

OCTET STRING

As per the MIB.

 

Recommended action

1.Identify the destination address of the down sub-LSP by using the display mpls te p2mp tunnel-interface command and then check if the link to the destination address is faulty.

  - If yes, repair the link.

  - If not, proceed to step 2.

2.Check whether the tunnel related configuration and protocol configuration are correct.

  - If yes, proceed to step 3.

  - If not, correct the configurations.

3.Collect log messages and configuration data, and then contact Technical Support for help.

hh3cMplsTeP2mpTunnelUp

Basic information

OID

Event

Type

Severity

Recovery notification

Default status

1.3.6.1.4.1.25506.2.143.0.19

P2MP TE tunnel UP

Recovery

Major

N/A (N/A)

ON

 

Notification triggers

This notification is generated when a P2MP TE tunnel becomes up.

System impact

No negative impact on the system.

Status control

ON

CLI: Use the snmp-agent trap enable te-private p2mp-tunnel-up-down command.

OFF

CLI: Use the undo snmp-agent trap enable te-private p2mp-tunnel-up-down command.

Object

OID (object name)

Description

Index

Type

Value range

hh3cMplsTeTunnelInfo (1.3.6.1.4.1.25506.2.143.1.1.3)

MPLS TE tunnel information.

N/A

OCTET STRING

As per the MIB.

 

Recommended action

No action is required.

 

  • Cloud & AI
  • InterConnect
  • Intelligent Computing
  • Intelligent Storage
  • Security
  • SMB Products
  • Intelligent Terminal Products
  • Product Support Services
  • Technical Service Solutions
All Services
  • Resource Center
  • Policy
  • Online Help
  • Technical Blogs
All Support
  • Become A Partner
  • Partner Policy & Program
  • Global Learning
  • Partner Sales Resources
  • Partner Business Management
  • Service Business
All Partners
  • Profile
  • News & Events
  • Online Exhibition Center
  • Contact Us
All About Us
新华三官网