EVPN_1.3.6.1.4.1.2011.5.25.356.1.1.2.7 hwEvpnDiscardRoute

Trap Buffer Description

The EVPN instance discards the newly learned MAC and MAC/IP routes. (RouteType=[RouteType])

The EVPN instance discards newly learned MAC and MAC/IP routes.

In VS mode, this trap is supported only by the admin VS.

Trap Attributes

Trap Attribute	Description
Alarm or Event	Event
Trap Severity	Warning
Mnemonic Code	EVPN_RESILIENCE_DISCARD_ROUTE
Trap OID	1.3.6.1.4.1.2011.5.25.356.1.1.2.7
MIB	HUAWEI-EVPN-MIB
Alarm ID	This is an event trap and does not involve alarm ID.
Alarm Name	This is an event trap and does not involve alarm name.
Alarm Type	This is an event trap and does not involve alarm type.
Raise or Clear	This is an event trap and does not involve alarm generation or clearance.
Match trap	-

Trap Buffer Parameters

Parameter	Description
RouteType	Route type.(local/remote cross-connection)

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.4.1.2011.5.25.356.1.1.3.5	hwEvpnDiscardRouteType	-

Impact on the System

When the board memory is overloaded, the device no longer learns local MAC addresses, ARP entries, or ND entries, and generates local EVPN MAC and MAC/IP routes. The MAC and ARP entries received from the remote device are not imported to the EVPN instance, and traffic related to these routes is affected.

Possible Causes

When the memory of a board is overloaded, the board discards the MAC and MAC/IP routes that are newly learned from the remote cross-connect board and the local board.

Procedure

1. Check whether a large number of EVPN instances are configured with the same vpn-target import-extcommunity and whether the RT attribute of the remote route is the same as the vpn-target import-extcommunity.

If yes, go to Step 2.

If no, go to Step 4.

2. Check whether the vpn-target import-extcommunity in the EVPN instance meets the actual application requirements.

If yes, go to Step 4.

If no, go to Step 3.

3. Modify the vpn-target import-extcommunity of the EVPN instance as required.

4. Check that EVPN services and traffic are normal.

If yes, ignore this event.

If not, go to Step 5.

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