Contents

HH3C-MPLSPCE-MIB· 1

About this MIB· 1

MIB file name· 1

Notifications· 1

hh3cMplsPcePcepSessDown· 1

hh3cMplsPcePcepSessUp· 2

hh3cMplsPceRetDelegation· 3

hh3cMplsPceRetDelegationClear 4

 

 

HH3C-MPLSPCE-MIB

About this MIB

Use this MIB to notify PCE traps.

MIB file name

hh3c-mplspce.mib

Notifications

hh3cMplsPcePcepSessDown

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.2.240.0.1	PCEP session DOWN	Error	Major	1.3.6.1.4.1.25506.2.240.0.2 (hh3cMplsPcePcepSessUp)	ON

 

Notification triggers

This notification is generated when a PCEP session goes down. Possible reasons are as follows:

Hold timer expired

Source address configuration change

Protocol error message received

Protocol close message received

PCEP configuration delete

System impact

If PCEP is used to calculate and delegate RSVP-TE, SR-TE, SR-TE policy, or SRv6-TE policy paths, PCEP might be unable to function and the delegated paths will bypass the nodes after a period of time.

Status control

ON

CLI: Use the snmp-agent trap enable pce-private pcepsess-up-down command.

OFF

CLI: Use the undo snmp-agent trap enable pce-private pcepsess-up-down command.

Object

OID (object name)	Description	Index	Type	Value range
hh3cMplsPcePcepSessInfo (1.3.6.1.4.1.25506.2.240.1.1.1)	PCEP session information	N/A	OCTET STRING	As per the MIB.

 

Recommended action

To resolve this issue:

1.Execute the display current-configuration command to identify whether the source address configured on the PCE server is the same as the candidate server address on the PCE client.

  - If yes, go the next step.

  - If not, edit the configuration on the PCE client to have the source address on the PCE server the same as the candidate server address on the PCE client.

2.Execute the display current-configuration command to identify whether the keychain configuration on the PCE server matches that on the PCE client.

  - If yes, go to the next step.

  - If not, edit the configuration on the PCE client to have the keychain configuration on the PCE server the same as that on the PCE client.

3.Execute the display ip routing-table command on the PCE client to identify whether routes from the server are received.

  - If yes, go to the next step.

  - If not, identify whether the OSPF configuration on the PCE server matches that on the PCE client. If they do not match, edit the OSPF configuration to make sure the PCE client can receive routes from the PCE server.

4.Identify whether the physical link between the PCE client and PCE server is normal.

  - If yes, go to the next step.

  - If not, remove and reconnect or replace the cable between them.

5.If the issue persists, collect alarm information and configuration data, and then contact Technical Support for help.

hh3cMplsPcePcepSessUp

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.2.240.0.2	PCEP session UP	Recovery	Major	N/A (N/A)	ON

 

Notification triggers

This notification is generated when a PCEP session comes up.

System impact

No impact on services.

Status control

ON

CLI: Use the snmp-agent trap enable pce-private pcepsess-up-down command.

OFF

CLI: Use the undo snmp-agent trap enable pce-private pcepsess-up-down command.

Object

OID (object name)	Description	Index	Type	Value range
hh3cMplsPcePcepSessInfo (1.3.6.1.4.1.25506.2.240.1.1.1)	PCEP session information	N/A	OCTET STRING	As per the MIB.

 

Recommended action

No action is required.

hh3cMplsPceRetDelegation

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.2.240.0.3	The PCE server undelegates the paths delegated by the PCC.	Error	Major	1.3.6.1.4.1.25506.2.240.0.4 (hh3cMplsPceRetDelegationClear)	OFF

 

Notification triggers

This notification is generated when the PCE rejects or undelegates the paths delegated by the PCC.

System impact

The rejected or undelegated paths will be delegated to another PCE server. If no PCE server accepts the delegation within a specific period of time, the paths will bypass the nodes.

Status control

ON

CLI: Use the snmp-agent trap enable pcep-private pcep-redelegation command.

OFF

CLI: Use the undo snmp-agent trap enable pcep-private pcep-redelegation command.

Object

OID (object name)	Description	Index	Type	Value range
hh3cMplsPceDelegationInfo (1.3.6.1.4.1.25506.2.240.1.1.2)	PCE delegation information.	N/A	OCTET STRING	As per the MIB.

 

Recommended action

To resolve this issue:

1.Check the reason for the undelegation. If the paths are undelegated because the number of paths that can be delegated reaches the upper limit, remove the paths from delegation or start a new PCE server. If the PCE server undelegates the paths proactively, contact Technical Support of the PCE server.

2.If the issue persists, collect alarm information and configuration data, and then contact Technical Support for help.

hh3cMplsPceRetDelegationClear

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.2.240.0.4	The PCE redelegates MPLS TE tunnels.	Recovery	Major	N/A (N/A)	OFF

 

Notification triggers

This notification is generated when the PCC redelegates paths to the PCE server successfully.

System impact

No impact on services.

Status control

ON

CLI: Use the snmp-agent trap enable pcep-private pcep-redelegation command.

OFF

CLI: Use the undo snmp-agent trap enable pcep-private pcep-redelegation command.

Object

OID (object name)	Description	Index	Type	Value range
hh3cMplsPceDelegationInfo (1.3.6.1.4.1.25506.2.240.1.1.2)	PCE redelegation information.	N/A	OCTET STRING	As per the MIB.

 

Recommended action

No action is required.