Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Bonjour M02@rt37 ,
> so I wouldn’t say that every pseudowire defaults to VC type 5 ? No ?
This is in the specific context described by the OP, where the xconnect is configured under the service instance. I ran a quick test in a virtual lab and the VC...
Hi @Mitrixsen ,
In IOS-XE the pseudowire operates as a VC type 5 by default. You would use the "interworking vlan" only if you wanted to change the default to a VC type 4.
Bear in mind that the VC type is negotiated and if either end of the pseudowi...
Hi @Mitrixsen ,
With IOS-xe you can set the VC type 4 using the following command under the pseudowire class:
pseudowire-class VC-Type4
encapsulation mplsinterworking vlan
and then assign the pseudowire class to the specific xconnect.
Hi @Mitrixsen ,
The issue is that there is no way for R4-XR and R5 to exchange labels for their respective loopback interfaces. You could use BGP LU or LDP between the two ASes, but the easy way to fix that design is to run multiple VPNv4 BGP session...
Hi @Mitrixsen ,
On R4-XR, make sure the BGP session to R5 is configured as "address-family ipv4 labeled-unicast", rather than "address-family ipv4 unicast".