09-19-2014 02:33 AM
Dear All,
I have problem with l2tpv3 over ASR9001 and IOS is not working the tunnel is up the the ping traffic is not passed through please help to advise.
RP/0/RSP0/CPU0:CR02#show run l2vpn
Fri Sep 19 16:28:34.628 KHMER
l2vpn
pw-class TEST
encapsulation l2tpv3
protocol l2tpv3
ipv4 source 175.28.0.5
!
!
xconnect group TEST
p2p TEST
interface GigabitEthernet0/0/0/5
neighbor ipv4 119.82.248.165 pw-id 111
pw-class TEST
!
RP/0/RSP0/CPU0:CR02#show run interface GigabitEthernet0/0/0/5
Fri Sep 19 16:29:17.230 KHMER
interface GigabitEthernet0/0/0/5
load-interval 30
l2transport
IOS
Router#show run int g0/1
Building configuration...
Current configuration : 136 bytes
!
interface GigabitEthernet0/1
no ip address
duplex auto
speed auto
xconnect 175.28.0.5 111 encapsulation l2tpv3 pw-class TEST
end
Router#show run
Building configuration...
pseudowire-class TEST
encapsulation l2tpv3
ip local interface Loopback0
!!!!!!!!!!!!!!!!!
RP/0/RSP0/CPU0:CR02#show l2vpn xconnect detail
Fri Sep 19 16:31:47.141 KHMER
Group TEST, XC TEST, state is up; Interworking none
AC: GigabitEthernet0/0/0/5, state is up
Type Ethernet
MTU 1500; XC ID 0x1080003; interworking none
Statistics:
packets: received 210068, sent 3592
bytes: received 23011939, sent 822568
drops: MTU exceeded 0, other 0
PW: neighbor 119.82.248.165, PW ID 111, state is up ( established )
PW class TEST, XC ID 0x1080003
Encapsulation L2TPv3, protocol L2TPv3
PW type Ethernet, control word disabled, interworking none
PW backup disable delay 0 sec
Sequencing not set
L2TP class l2tp_default_class, IPv4 source address 175.28.0.5
TOS 0 (reflect disabled), TTL 255, DF bit not set
Path MTU: disabled
Tunnel state connected, remote circuit status up
L2TPv3 Local Remote
--------------- ---------------------------- ---------------------------
Session 1401163178 3990078582
Cookie size 0 bytes 0 bytes
Cookie unassigned unassigned
MTU 1500 1500
Control word disabled disabled
PW type Ethernet Ethernet
--------------- ---------------------------- ---------------------------
Create time: 19/09/2014 14:46:13 (01:45:26 ago)
Last time status changed: 19/09/2014 14:46:13 (01:45:26 ago)
Statistics:
packets: received 3592, sent 210068
bytes: received 822568, sent 23011939
drops: out of sequence 0, other 0
This is the error on IOS XR I got.
Sep 19 16:14:04.446 l2vpn/err 0/RSP0/CPU0 t6 XC|ERR:1019: XC DB operation failed. Reason: Invalid context 0x5151ff90 or container type 0
Sep 19 16:14:04.446 l2vpn/err 0/RSP0/CPU0 t6 XC|ERR:1544: XC DB operation failed. Reason: Invalid context 0x5151ff90 or container type 0
Sep 19 16:14:04.446 l2vpn/xc 0/RSP0/CPU0 t6 XC|ERR:1544: XC DB operation failed. Reason: Invalid context 0x5151ff90 or container type 0
Sep 19 16:14:04.446 l2vpn/xc 0/RSP0/CPU0 t6 XC|ERR:1019: XC DB operation failed. Reason: Invalid context 0x5151ff90 or container type 0
Sep 19 16:14:04.446 l2vpn/xc 0/RSP0/CPU0 t6 XC|ERR:1544: XC DB operation failed. Reason: Invalid context 0x5151ff90 or container type 0
please help.
Regards, Pok.
Solved! Go to Solution.
09-24-2014 06:21 AM
hi pok,
let me be more specific, l2tpv3 over ipv4 is not supported (and you seem to have ipv4 correct?), in XR43 we can do the l2tpv3 over ipv6.
here is the command reference for that functionality over ipv6:
http://www.cisco.com/c/en/us/td/docs/routers/asr9000/software/asr9k_r4-3/lxvpn/configuration/guide/lesc43xbook/lesc43p2ps.html#pgfId-1298172
cheers!
xander
09-25-2014 05:14 AM
Config is correct, but we need to do some troubleshooting as to why the packets are not making it through.
dropped at ingress, or egress and on which device etc. follow the packet troubleshooting guide on the forums to identify if there is an np counter that reflects the drops of the sample data rate and that likely will give some insight as to what to do next.
xander
09-22-2014 08:53 AM
I am very sorry, but asr9000/xr sw doesnt support l2tpv3 encapsulation for PW's only mpls encap is supported (and soon also GRE).
xander
09-24-2014 06:09 AM
Dear Xander,
So even the new version also doesn't support it ? Currently I am using 4.3.4
Regards, Pok.
09-24-2014 06:21 AM
hi pok,
let me be more specific, l2tpv3 over ipv4 is not supported (and you seem to have ipv4 correct?), in XR43 we can do the l2tpv3 over ipv6.
here is the command reference for that functionality over ipv6:
http://www.cisco.com/c/en/us/td/docs/routers/asr9000/software/asr9k_r4-3/lxvpn/configuration/guide/lesc43xbook/lesc43p2ps.html#pgfId-1298172
cheers!
xander
09-24-2014 07:51 AM
Dear Xander,
Yes I am using IPv4. I will try it out over IPv6 if anything require will seek for your help. Thank you very much for your support.
Regards, Pok.
09-24-2014 07:40 PM
Dear Xander,
I have tried it over IPv6 it won't come up with dynamic configuration but it came up with static but the ping CE to CE still not work.
CR01#show run l2vpn
Thu Sep 25 09:39:11.992 KHM
l2vpn
pw-class ABC
encapsulation l2tpv3
!
!
xconnect group ABC
p2p ABC
interface TenGigE0/0/2/1.558
neighbor ipv6 2403:6600::5 pw-id 558
pw-class ABC
source 2403:6600::10
l2tp static
local cookie size 8 value 0x123 0x456
remote cookie size 8 value 0x123 0x456
CR01#show l2vpn xconnect
Thu Sep 25 09:39:31.792 KHM
Legend: ST = State, UP = Up, DN = Down, AD = Admin Down, UR = Unresolved,
SB = Standby, SR = Standby Ready, (PP) = Partially Programmed
XConnect Segment 1 Segment 2
Group Name ST Description ST Description ST
------------------------ ----------------------------- -----------------------------
ABC ABC UP Te0/0/2/1.558 UP 558 UP
2403:6600::5
CR02#show run l2vpn
Thu Sep 25 09:39:52.508 KHMER
l2vpn
pw-class ABC
encapsulation l2tpv3
!
!
xconnect group ABC
p2p ABC
interface TenGigE0/0/2/1.558
neighbor ipv6 2403:6600::10 pw-id 558
pw-class ABC
source 2403:6600::5
l2tp static
local cookie size 8 value 0x123 0x456
remote cookie size 8 value 0x123 0x456
!
CR02#show l2vpn xconnect
Thu Sep 25 09:39:56.516 KHMER
Legend: ST = State, UP = Up, DN = Down, AD = Admin Down, UR = Unresolved,
SB = Standby, SR = Standby Ready, (PP) = Partially Programmed
XConnect Segment 1 Segment 2
Group Name ST Description ST Description ST
------------------------ ----------------------------- -----------------------------
ABC ABC UP Te0/0/2/1.558 UP 558 UP
2403:6600::10
Please advise if something is missing in my configuration.
Regards, Pok.
09-25-2014 05:14 AM
Config is correct, but we need to do some troubleshooting as to why the packets are not making it through.
dropped at ingress, or egress and on which device etc. follow the packet troubleshooting guide on the forums to identify if there is an np counter that reflects the drops of the sample data rate and that likely will give some insight as to what to do next.
xander
09-25-2014 11:08 AM
Dear Xander,
Could you please provide the guideline as I am still getting the same error.
Sep 25 13:56:17.171 l2vpn/cfg-prov 0/RSP0/CPU0 t1 CFG-PROV:496: LOG_PROV(caller:1): UnProvisioned 0 items in 0 msec. First/Last item priority: -1/-1. Items remaining in queue: 0
Sep 25 13:56:17.171 l2vpn/cfg-prov 0/RSP0/CPU0 t1 CFG-PROV:565: LOG_PROV(caller:1): Provisioned 0 items in 0 msec. First/Last item priority: -1/-1. Items remaining in queue: 0
Sep 25 13:56:17.171 l2vpn/cfg-prov 0/RSP0/CPU0 t1 CFG-PROV:591: Post-provision Callback Function succeeded. index = 1, flags = 0x20,0x21
Sep 25 13:56:25.439 l2vpn/err 0/RSP0/CPU0 t6 XC|ERR:1544: XC DB operation failed. Reason: Invalid context 0x5151ff90 or container type 0
Sep 25 13:56:25.439 l2vpn/err 0/RSP0/CPU0 t6 XC|ERR:1019: XC DB operation failed. Reason: Invalid context 0x5151ff90 or container type 0
Sep 25 13:56:25.439 l2vpn/err 0/RSP0/CPU0 t6 XC|ERR:1544: XC DB operation failed. Reason: Invalid context 0x5151ff90 or container type 0
Sep 25 13:56:25.439 l2vpn/xc 0/RSP0/CPU0 t6 XC|ERR:1544: XC DB operation failed. Reason: Invalid context 0x5151ff90 or container type 0
Sep 25 13:56:25.439 l2vpn/xc 0/RSP0/CPU0 t6 XC|ERR:1019: XC DB operation failed. Reason: Invalid context 0x5151ff90 or container type 0
Sep 25 13:56:25.439 l2vpn/xc 0/RSP0/CPU0 t6 XC|ERR:1544: XC DB operation failed. Reason: Invalid context 0x5151ff90 or container type 0
Sep 25 13:56:55.670 l2vpn/err 0/RSP0/CPU0 t6 XC|ERR:1544: XC DB operation failed. Reason: Invalid context 0x5151ff90 or container type 0
Sep 25 13:56:55.670 l2vpn/err 0/RSP0/CPU0 t6 XC|ERR:1019: XC DB operation failed. Reason: Invalid context 0x5151ff90 or container type 0
Sep 25 13:56:55.670 l2vpn/err 0/RSP0/CPU0 t6 XC|ERR:1544: XC DB operation failed. Reason: Invalid context 0x5151ff90 or container type 0
Sep 25 13:56:55.670 l2vpn/xc 0/RSP0/CPU0 t6 XC|ERR:1544: XC DB operation failed. Reason: Invalid context 0x5151ff90 or container type 0
Sep 25 13:56:55.670 l2vpn/xc 0/RSP0/CPU0 t6 XC|ERR:1019: XC DB operation failed. Reason: Invalid context 0x5151ff90 or container type 0
Sep 25 13:56:55.670 l2vpn/xc 0/RSP0/CPU0 t6 XC|ERR:1544: XC DB operation failed. Reason: Invalid context 0x5151ff90 or container type 0
Sep 25 14:33:19.616 l2vpn/err 0/RSP0/CPU0 t6 XC|ERR:1544: XC DB operation failed. Reason: Invalid context 0x5151ff90 or container type 0
Sep 25 14:33:19.616 l2vpn/err 0/RSP0/CPU0 t6 XC|ERR:1019: XC DB operation failed. Reason: Invalid context 0x5151ff90 or container type 0
Sep 25 14:33:19.616 l2vpn/err 0/RSP0/CPU0 t6 XC|ERR:1544: XC DB operation failed. Reason: Invalid context 0x5151ff90 or container type 0
Sep 25 14:33:19.616 l2vpn/xc 0/RSP0/CPU0 t6 XC|ERR:1544: XC DB operation failed. Reason: Invalid context 0x5151ff90 or container type 0
Sep 25 14:33:19.616 l2vpn/xc 0/RSP0/CPU0 t6 XC|ERR:1019: XC DB operation failed. Reason: Invalid context 0x5151ff90 or container type 0
Sep 25 14:33:19.616 l2vpn/xc 0/RSP0/CPU0 t6 XC|ERR:1544: XC DB operation failed. Reason: Invalid context 0x5151ff90 or container type 0
Regards, Pok.
09-25-2014 11:39 AM
hi pok,
I am browsing the code to see what error 1019 and 1544 precisely mean.
basically a lookup in the cross connect database resulted in an error.
apparently the context/identifier of the record was not found.
I see some known issues with this pertaining to mpls encapped xconns also.
do you have flexibility to try out XR 513? or is this not a lab device and not easy to verify a different release.
I'll report back when I have more detail on this error number 1019/1544.
regards
xander
09-25-2014 08:05 PM
Dear Xander,
Thank you very much. This is a production router can not lab it out sorry for that.
Anyway I also have tried the dynamic configuration but never get the xconnect up.
CR01#show run l2vpn
Fri Sep 26 10:03:32.445 KHM
l2vpn
pw-class ABC
encapsulation l2tpv3
protocol l2tpv3
!
!
xconnect group ABC
p2p ABC
interface TenGigE0/0/2/1.558
neighbor ipv6 2403:6600::5 pw-id 558
pw-class ABC
source 2403:6600::10
CR01#show l2vpn xconnect
Fri Sep 26 10:03:38.393 KHM
Legend: ST = State, UP = Up, DN = Down, AD = Admin Down, UR = Unresolved,
SB = Standby, SR = Standby Ready, (PP) = Partially Programmed
XConnect Segment 1 Segment 2
Group Name ST Description ST Description ST
------------------------ ----------------------------- -----------------------------
ABC ABC UR Te0/0/2/1.558 DN 558 UR
2403:6600::5
CR02#show run l2vpn
Fri Sep 26 10:02:56.642 KHMER
l2vpn
pw-class ABC
encapsulation l2tpv3
protocol l2tpv3
!
!
xconnect group ABC
p2p ABC
interface TenGigE0/0/2/1.558
neighbor ipv6 2403:6600::10 pw-id 558
pw-class ABC
source 2403:6600::5
CR02#show l2vpn xconnect
Fri Sep 26 10:03:13.503 KHMER
Legend: ST = State, UP = Up, DN = Down, AD = Admin Down, UR = Unresolved,
SB = Standby, SR = Standby Ready, (PP) = Partially Programmed
XConnect Segment 1 Segment 2
Group Name ST Description ST Description ST
------------------------ ----------------------------- -----------------------------
ABC ABC UR Te0/0/2/1.558 DN 558 UR
2403:6600::10
I think dynamic l2tpv3 is not support in this version could you please help to confirm ?
Regards, Pok.
09-26-2014 04:55 AM
as far as I know Pok you need to set the cookie stuff, so yeah that makes it static config.
I havent been able to derive yet what the error codes precisely mean.
The other thing that we can do is when the tunnel is up and there is packet dropping going on, we can possibly trace where they are getting lost in the NPU and for what reason. Considering the XID messages, I am afraid that the NPU has the wrong config in its hw also and for that reason packets are getting dropped in the NPU, but we can confirm that if you like.
regards
xander
09-26-2014 05:20 AM
Dear Xander,
Yes please help to analyse the problem and advise for the solution.
Regards, Pok.
09-26-2014 05:28 AM
hi pok, follow this guide for packet drop troubleshooting:
https://supportforums.cisco.com/document/59721/asr9000xr-troubleshooting-packet-drops-and-understanding-np-drop-counters
send a continous stream of 100 or 1000 packets per second into the tunnel
and then clear the np counters and show the controller np counters.
there should be a few conters that are at about 1000pps (or 100 whatever you send) and then we can likely easily identify what the cause is for not forwarding them.
xander
09-26-2014 06:13 AM
Dear Xander,
Below is the show command output after CE to CE ping.
CR01#show controllers np counters np0
Fri Sep 26 20:11:42.096 KHM
Node: 0/0/CPU0:
----------------------------------------------------------------
Show global stats counters for NP0, revision v2
Read 58 non-zero NP counters:
Offset Counter FrameValue Rate (pps)
-------------------------------------------------------------------------------
16 MDF_TX_LC_CPU 1165693 945
17 MDF_TX_WIRE 1628361884 1318746
21 MDF_TX_FABRIC 1436000506 1168972
29 PARSE_FAB_RECEIVE_CNT 1628357179 1318742
33 PARSE_INTR_RECEIVE_CNT 27389 22
37 PARSE_INJ_RECEIVE_CNT 107710 87
41 PARSE_ENET_RECEIVE_CNT 1436140372 1169086
45 PARSE_TM_LOOP_RECEIVE_CNT 6111 5
49 PARSE_TOP_LOOP_RECEIVE_CNT 923254 748
57 PARSE_ING_DISCARD 3957 3
63 PRS_HEALTH_MON 6111 5
72 INTR_FRAME_TYPE_7 14776 12
92 PARSE_ING_8023 238 0
98 PARSE_ING_IPV6_LINK_LOCAL 2976 2
102 PARSE_RSP_INJ_FAB_CNT 34639 26
105 PARSE_EGR_INJ_PKT_TYP_UNKNOWN 61 0
106 PARSE_EGR_INJ_PKT_TYP_IPV4 28633 21
107 PARSE_EGR_INJ_PKT_TYP_IPV6 5797 5
109 PARSE_EGR_INJ_PKT_TYP_CLNS 148 0
110 PARSE_EGR_INJ_PKT_TYP_IPV4_PREROUTE 42 0
116 PARSE_LC_INJ_FAB_CNT 102671 83
117 PARSE_LC_INJ_PORT_CNT 5018 4
118 PARSE_LC_INJ_DIAGS_CNT 21 0
124 PARSE_ING_ISIS 196 0
129 PARSE_DROP_IN_UIDB_TCAM_MISS 5592 4
137 PARSE_IPV4_SANITY_ADDR_CHK_FAILURES 2947 2
159 PARSE_L3_TAGGED_PUNT_DROP 3155 2
160 PARSE_MSTP_DOT1D 631 0
201 PARSE_LLDP 42 0
203 UNKNOWN_L2_ON_L3_DISCARD 802 1
220 PARSE_UDLD 21 0
260 DBG_RSV_EP_L_RSV_ING_L3_IFIB 92796 74
261 DBG_RSV_EP_L_RSV_ING_L3_IFIB_MATCH 92796 74
262 DBG_RSV_EP_L_RSV_ING_L3_IFIB_PUNT_LOCAL 92796 74
264 DBG_RSV_EP_L_RSV_ING_L3_RSLTS_MATCH 92796 74
265 DBG_RSV_EP_L_RSV_ING_PUNT 700940 566
381 RSV_DROP_IN_L3_NOT_MYMAC 1640 1
404 RSV_ING_VPWS_ERR_DROP 84 0
482 RSV_SNF_SAMPLE_PKT 922368 747
483 RSV_SNF_IPV4 922370 747
484 RSV_SNF_ING_PUNT 515480 417
485 RSV_SNF_EGR_PUNT 406890 330
774 CDP 21 0
776 ARP 58158 49
790 DIAGS 21 0
806 MSTP 631 0
840 IPV4_TTL_ERROR 18942 14
850 PUNT_ADJ 268 0
862 IPV6_HOP_BY_HOP 28 0
864 IPV6_TTL_ERROR 4 0
902 PUNT_STATISTICS 14758 12
908 NETIO_RP_TO_LC_CPU_PUNT 61 0
936 PUNT_NETFLOW 923426 747
958 PUNT_LLDP 42 0
1156 MDF_PIPE_LPBK 924310 748
1177 MDF_PUNT_RSP_VIA_HOST_PORT 57744 48
1209 MODIFY_PUNT_NF_MSG 923425 747
1210 MODIFY_PUNT_NF_IPV4 922369 747
CR02#show controllers np counters np0
Fri Sep 26 20:11:24.158 KHMER
Node: 0/0/CPU0:
----------------------------------------------------------------
Show global stats counters for NP0, revision v2
Read 61 non-zero NP counters:
Offset Counter FrameValue Rate (pps)
-------------------------------------------------------------------------------
16 MDF_TX_LC_CPU 590264 1295
17 MDF_TX_WIRE 484964642 1069136
21 MDF_TX_FABRIC 519434690 1141405
29 PARSE_FAB_RECEIVE_CNT 485072540 1069409
33 PARSE_INTR_RECEIVE_CNT 9469 21
37 PARSE_INJ_RECEIVE_CNT 104223 227
41 PARSE_ENET_RECEIVE_CNT 519420975 1141365
45 PARSE_TM_LOOP_RECEIVE_CNT 2223 5
49 PARSE_TOP_LOOP_RECEIVE_CNT 507066 1114
57 PARSE_ING_DISCARD 8689 10
63 PRS_HEALTH_MON 2223 5
72 INTR_FRAME_TYPE_7 4879 11
92 PARSE_ING_8023 175 0
96 PARSE_ING_SLOW_PROTO 67 0
98 PARSE_ING_IPV6_LINK_LOCAL 19 0
102 PARSE_RSP_INJ_FAB_CNT 33468 72
105 PARSE_EGR_INJ_PKT_TYP_UNKNOWN 160 0
106 PARSE_EGR_INJ_PKT_TYP_IPV4 32482 69
107 PARSE_EGR_INJ_PKT_TYP_IPV6 763 2
109 PARSE_EGR_INJ_PKT_TYP_CLNS 54 0
110 PARSE_EGR_INJ_PKT_TYP_IPV4_PREROUTE 57 0
111 PARSE_EGR_INJ_PKT_TYP_IPV6_PREROUTE 12 0
112 PARSE_EGR_INJ_PKT_TYP_IPV6_LINK_LOCAL 7 0
116 PARSE_LC_INJ_FAB_CNT 101554 224
117 PARSE_LC_INJ_PORT_CNT 2661 3
118 PARSE_LC_INJ_DIAGS_CNT 8 0
124 PARSE_ING_ISIS 53 0
129 PARSE_DROP_IN_UIDB_TCAM_MISS 688 1
132 PARSE_DROP_IN_UIDB_DOWN 687 1
135 PARSE_DROP_IPV4_MCAST_NOT_ENABLED 12 0
153 PARSE_DROP_IPV6_DISABLED 38 0
159 PARSE_L3_TAGGED_PUNT_DROP 2283 5
203 UNKNOWN_L2_ON_L3_DISCARD 130 0
220 PARSE_UDLD 53 0
240 PARSE_DROP_PPPOE_NOT_ENABLED 5539 3
260 DBG_RSV_EP_L_RSV_ING_L3_IFIB 19887 43
261 DBG_RSV_EP_L_RSV_ING_L3_IFIB_MATCH 19887 43
262 DBG_RSV_EP_L_RSV_ING_L3_IFIB_PUNT_LOCAL 19887 43
264 DBG_RSV_EP_L_RSV_ING_L3_RSLTS_MATCH 19887 43
265 DBG_RSV_EP_L_RSV_ING_PUNT 545867 1198
323 RSV_DROP_QOS_DENY 110062 275
404 RSV_ING_VPWS_ERR_DROP 283 1
482 RSV_SNF_SAMPLE_PKT 506659 1113
483 RSV_SNF_IPV4 506659 1113
484 RSV_SNF_ING_PUNT 506659 1113
537 RSV_EGR_IPV6_LINK_LOCAL 7 0
774 CDP 53 0
776 ARP 208 0
782 LOOP 46 0
786 BUNDLE_PROTO_PUNT 67 0
790 DIAGS 8 0
840 IPV4_TTL_ERROR 12822 28
850 PUNT_ADJ 1579 3
864 IPV6_TTL_ERROR 2 0
902 PUNT_STATISTICS 4879 11
908 NETIO_RP_TO_LC_CPU_PUNT 160 0
936 PUNT_NETFLOW 506658 1113
1156 MDF_PIPE_LPBK 507069 1114
1177 MDF_PUNT_RSP_VIA_HOST_PORT 43892 96
1209 MODIFY_PUNT_NF_MSG 506660 1113
1210 MODIFY_PUNT_NF_IPV4 506660 1113
Please advise for next step.
Regards, Pok.
09-29-2014 06:16 PM
Dear Xander,
Any good news about the error code above ?
Regards, Pok.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: