cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2137
Views
0
Helpful
8
Replies
Highlighted
Enthusiast

IOS-XE ISR 4K L2TPv3 and SM-X

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?

Thanks!

 

l2tp-class L2-VLAN199-CLASS
 authentication
 password asdfasdf

!

pseudowire-class L2-VLAN199-PW
 encapsulation l2tpv3
 protocol l2tpv3 L2-VLAN199-CLASS
 ip local interface Loopback199
 ip pmtu

!

interface Ethernet-Internal1/0/0

 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

!

interface Loopback199

 ip address 172.17.199.1 255.255.255.255

 

8 REPLIES 8
Highlighted
Enthusiast

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!

Highlighted

Looks like it might be supported now.
https://gns3.com/discussions/l2tpv3-psudowire

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.

Highlighted
Beginner

Can you explain how you moved the xconnect to the ISR4331 dot1q sub-if ?
Mine won't support the connect command on a sub-if ?
It has the appxk9 license.

Highlighted

it does support the commands now, must have been operator error :]

Highlighted
Beginner

Hello

 

did you finally managed to make it work ? I'm facing the same issue and I wanted to know if now it is supported or not.

 

thanks

Highlighted

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.

 

pseudowire-class PWname

encapsulation l2tpv3  

ip local interface Loopback0

 

interface GigabitEthernet0/2

xconnect 192.168.1.nn 10 pw-class [PWname]

!

 

interface GigabitEthernet0/2.701

no ip address

encapsulation dot1q 701

!

interface GigabitEthernet0/2.702

no ip address

encapsulation dot1q 702

 

Highlighted

Hi,

thanks

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 ?

 

thanks

Highlighted

No, that wasn't the intention.
I wanted to tunnel L2 traffic in the same VLAN i.e. a pseudowire or stretched vlan.
>From a logical interface, could you not assign an ip address and use a GRE tunnel ?