I can't get L2TPv3 to work from the SM-X backplane interface on an ISR 4K (4331/4451).
The tunnel/session both show established, but no egress packets are being sent.
The same configuration works fine if I move the xconnect to a dot1q subinterface on one of the ISR 4K physical interfaces (i.e. gi0/0/1.199), but I'd rather not have to use a physical cable going from one of the router's interfaces to the SM-X interfaces...
Anyone know if this is the correct method for configuring L2TPv3 on the SM-X backplane interface?
protocol l2tpv3 L2-VLAN199-CLASS
ip local interface Loopback199
service instance 199 ethernet
encapsulation dot1q 199
rewrite ingress tag pop 1 symmetric
xconnect 172.16.199.1 199 encapsulation l2tpv3 pw-class L2-VLAN199-PW
ip address 172.17.199.1 255.255.255.255
I opened a TAC case and it turns out this is not yet supported. Still waiting on an ETA for a feature update. In the meantime, a workaround will have to be physically cabling one of the ISR 4K ports to the SM-X to use as a trunk rather than the backplane interface. Boo!
Looks like it might be supported now.
reports the l2tpv3 feature supported in various ISR4k platforms as wel as x900 according to Cisco Feature Navigator.
n.b. we tested this fine on 2921's, when the connection is moved to a 4331 for one of them there are no packets passed.
Yes, the solution was not to try and use L3 ip addresses on the sub-interfaces.
I had to use dot1q trunking and make the xconnect using the parent I-f.
ip local interface Loopback0
xconnect 192.168.1.nn 10 pw-class [PWname]
no ip address
encapsulation dot1q 701
no ip address
encapsulation dot1q 702
but you finally still used one of the physical interface of the ISR. Did you succeed to use L2TPv3 on the ethernet-Internal interface ? I mean instead of using and extra external cable, using the backplace interface ?