topic RE: MPLS Kernel error 16.1.3.6 in ExtremeSwitching (EXOS/Switch Engine)

MPLS Kernel error 16.1.3.6

Sergey_Vekli — Tue, 30 Aug 2016 12:59:00 GMT

VPLS VPN not working. After disabling see error

MPLS gport resolve failed for unit = 0 vpn = 0x70e3, port = 0xffffffff vp = 0x18000a0c, rv = -7 (Entry not found)08/30/2016 11:37:25.99
extreme_mpls_del_vp_nh_xref: MPLS ECMP NH vp : 0xa0c l3intf = 0x83f map entry not found in btree rv = -7 (Entry not found)
extreme_custom_mpls_l2vpn_port_del: MPLS port delete: vp: 0xa0c l3Intf = 0x83f map entry not found in btree rv = -7 (Entry not found)
MPLS bcm_mpls_port_del failed for unit = 0 vpn = 0x70e3, vp = 0x18000a0c rv = -7 (Entry not found)

after enabling
* MPLS: bcm_mpls_port_add failed for unit = 0 vpn = 0x70e3, port = 0x8000809 vp = 0x18000a0d, rv = -14 (No resources for operation)

sh ver
Switch : Rev 12.0 BootROM: 2.0.2.1 IMG: 16.1.3.6

Image : ExtremeXOS version 16.1.3.6 16.1.3.6-patch1-9 by release-manager
on Mon Jul 18 10:45:49 EDT 2016
BootROM : 2.0.2.1
Diagnostics : 6.4

sh switch

System Type: X670-48x

Same problem resolved on previous release ?
https://extremeportal.force.com/ExtrArticleDetail?an=000063617

RE: MPLS Kernel error 16.1.3.6

Necheporenko__N — Tue, 30 Aug 2016 16:26:00 GMT

MPLS kernel message you have faced logged due to unavailability of hardware resources it is similar to the another article that you have mentioned, but in that case issue appears after changing dot1q tag (include/exclude), so it is not the same issue for sure.
Also it is not clear what interface/protocol you have disabled/enabled.

In a case when your services are affected after the issue try to removed/re-add service VLAN to VPLS as a workaround for restoring connectivity.

RE: MPLS Kernel error 16.1.3.6

Sergey_Vekli — Tue, 30 Aug 2016 16:38:00 GMT

Can you explain where in message info about vlan problem?
Now we planned downgrade to 16.1.3.6-1-8.

RE: MPLS Kernel error 16.1.3.6

Sergey_Vekli — Tue, 30 Aug 2016 16:57:00 GMT

We already try to delete and create same vpls but problem is not disappear.

RE: MPLS Kernel error 16.1.3.6

Chad_Smith1 — Tue, 30 Aug 2016 18:06:00 GMT

Sergey,

Did the VPN problem start after a network failure or OSPF neighborship loss?

It is probably best to open a case with GTAC so that this can be analyzed.

How to contact Extreme Networks Global Technical Assistance Center (GTAC)

RE: MPLS Kernel error 16.1.3.6

Sergey_Vekli — Tue, 30 Aug 2016 18:16:00 GMT

Yes. Ospf flap was before first mpls error in log. Down due to BFD path down.

8/30/2016 03:44:37.98 MPLS: bcm_mpls_port_add failed for unit = 0 vpn = 0x7055, port = 0x800080a vp = 0x180005c7, rv = -14 (No resources for operation)
08/30/2016 03:44:37.98
08/30/2016 03:44:37.98 MPLS: bcm_mpls_port_add failed for unit = 0 vpn = 0x7054, port = 0x800080a vp = 0x180005c6, rv = -14 (No resources for operation)
08/30/2016 03:44:37.98
08/30/2016 03:44:37.98 MPLS: bcm_mpls_port_add failed for unit = 0 vpn = 0x7053, port = 0x800080a vp = 0x180005c5, rv = -14 (No resources for operation)
08/30/2016 03:44:37.98
08/30/2016 03:44:37.98 MPLS: bcm_mpls_port_add failed for unit = 0 vpn = 0x7052, port = 0x800080a vp = 0x180005c4, rv = -14 (No resources for operation)
08/30/2016 03:44:37.84 Changing the state of neighbor rtid 10.16.0.1 ipa 10.16.248.10 to state = FULL due to Loading done.
08/30/2016 03:44:37.84 Changing the state of neighbor rtid 10.16.0.1 ipa 10.16.248.10 to state = LOADING due to exchange done event.
08/30/2016 03:44:37.83 Changing the state of neighbor rtid 10.16.0.1 ipa 10.16.248.10 to state = EXCHANGE due to negotiation done event.
08/30/2016 03:44:36.86 Changing the state of neighbor rtid 10.16.0.1 ipa 10.16.248.10 to state = EX_START due to AdjOK event.
08/30/2016 03:44:35.86 Changing the state of neighbor rtid 10.16.0.1 ipa 10.16.248.10 to state = 2WAY due to two way event.
08/30/2016 03:44:35.86 Changing the state of neighbor rtid 10.16.0.1 ipa 10.16.248.10 to state = INIT due to hello received.
08/30/2016 03:44:35.86 Changing the state of neighbor rtid 10.16.0.1 ipa 0.0.0.0 to state = DOWN due to new neighbor.
08/30/2016 03:44:35.59 Changing the state of neighbor rtid 10.16.0.1 ipa 10.16.248.10 to state = DOWN due to BFD path down.
08/30/2016 03:32:52.66 Changing the state of neighbor rtid 10.16.16.1 ipa 10.16.248.5 to state = FULL due to Loading done.
08/30/2016 03:32:52.66 Changing the state of neighbor rtid 10.16.16.1 ipa 10.16.248.5 to state = LOADING due to exchange done event.

RE: MPLS Kernel error 16.1.3.6

Chad_Smith1 — Tue, 30 Aug 2016 18:16:00 GMT

Sergey,

There is a known issue that this could be related to. However, this could also be a new issue. I think it is best to open up a GTAC case for investigation.

RE: MPLS Kernel error 16.1.3.6

Sergey_Vekli — Tue, 30 Aug 2016 18:17:00 GMT

Can high CPU load cause BFD timeout?

RE: MPLS Kernel error 16.1.3.6

Chad_Smith1 — Tue, 30 Aug 2016 18:17:00 GMT

Yes under certain conditions a high CPU load could cause a BFD timeout.

RE: MPLS Kernel error 16.1.3.6

Sergey_Vekli — Wed, 31 Aug 2016 01:46:00 GMT

Case opened.

RE: MPLS Kernel error 16.1.3.6

Julian_Eble — Fri, 09 Sep 2016 16:56:00 GMT

Sergey,

Is there any RSVP enabled on that path?
I suggest you to disable it in case of lose of connectivity.
We faced the same problem and we're waiting for a patch to solve this problem.

RE: MPLS Kernel error 16.1.3.6