ADPVXLAN
ADPVXLAN_1.3.6.1.4.1.2011.5.25.227.2.1.40 hwNotsuppDecapVxlanFragPackets
Description
ADPVXLAN/4/NOSUPPDECAPFRAG(t):OID [OID] The slot does not support to decapsulate VXLAN fragments.(Slot=[OCTET1],Vni=[INTEGER],SourceIP=[OCTET2],PeerIP=[OCTET3])
The device cannot decapsulate fragmented VXLAN packets.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
| 1.3.6.1.4.1.2011.5.25.227.2.1.40 | Warning |
processingErrorAlarm(4) |
Parameters
| Name | Meaning |
|---|---|
| OID | Indicates the MIB object ID of the alarm. |
| OCTET1 | Indicates the slot ID. |
| INTEGER | Indicates the VNI ID of VXLAN packets. |
| OCTET2 | Indicates the source VTEP IP address of VXLAN packets. |
| OCTET3 | Indicates the remote VTEP IP address of VXLAN packets. |
Impact on the System
VXLAN tunnel termination fails and fragmented VXLAN packets cannot be decapsulated, which may lead to a forwarding failure of the VXLAN service traffic.
Procedure
- Find the source VTEP based on the source IP address in the alarm and determine the access device connected to it. Set the MTU value of the interface on the access device or data source that sends the fragmented VXLAN packets to a smaller
value. To change the MTU value on a Huawei S series switch, run the mtu command. Check whether the alarm is cleared.
If so, go to step 5.
If not, go to step 2.
- Locate the forwarding devices on the VXLAN packet forwarding path based on the source and remote VTEP IP addresses in the alarm and set the MTU value of the interfaces of these devices to a larger value. To change the MTU value on a Huawei
S series switch, run the mtu command. Check whether the alarm is cleared.
If so, go to step 5.
If not, go to step 4.
- Replace the device that receives fragmented VXLAN packets on the VXLAN tunnel side with the one that supports VXLAN packet decapsulation, and then check whether the alarm is cleared.
If so, go to step 5.
If not, go to step 4.
- Contact technical support personnel.
- End.
ADPVXLAN_1.3.6.1.4.1.2011.5.25.227.2.1.42 hwVxlanTnlCfgFailed
Description
ADPVXLAN/4/VXLANTNLFAIL(t):OID [OID] Failed to add VXLAN tunnel table due to hash conflict.(Slot=[OCTET])
The device failed to deliver entries during VXLAN tunnel establishment due to a hash conflict.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
1.3.6.1.4.1.2011.5.25.227.2.1.42 |
Warning |
processingErrorAlarm(4) |
Impact on the System
VXLAN tunnels cannot be established, which may affect forwarding of VXLAN service traffic.
ADPVXLAN_1.3.6.1.4.1.2011.5.25.227.2.1.43 hwNotsuppDecapVxlanPackets
Description
ADPVXLAN/4/NOSUPPENCAPDECAPPKTS(t):OID [OID] The slot does not support to encapsulate and decapsulate VXLAN packets.(Slot=[OCTET1],Vni=[INTEGER],SourceIP=[OCTET2],PeerIP=[OCTET3])
The VXLAN-incapable device failed to decapsulate received VXLAN packets.
Attribute
| Alarm ID | Alarm Severity | Alarm Type |
|---|---|---|
1.3.6.1.4.1.2011.5.25.227.2.1.43 |
Warning |
processingErrorAlarm(4) |
Parameters
| Name | Meaning |
|---|---|
OID |
Indicates the MIB object ID of the alarm. |
OCTET1 |
Indicates the slot ID. |
INTEGER |
Indicates the VNI ID of VXLAN packets. |
OCTET2 |
Indicates the source VTEP IP address of VXLAN packets. |
OCTET3 |
Indicates the remote VTEP IP address of VXLAN packets. |
Procedure
- Run the display arp command to locate the interface receiving VXLAN packets based on the source VTEP IP address in the alarm, and check whether the device where the interface resides supports VXLAN packet decapsulation.
If so, go to step 3.
If not, go to step 2.
- Replace the device with the one supporting VXLAN packet decapsulation, and then check whether the alarm is cleared.
If so, go to step 4.
If not, go to step 3.
- Contact technical support personnel.
- End.