If preferred path option is not there then probably you need to do routing to prefer TE tunnel for xconnect destination. It can be done via static route or auto-route announce. If this causes all traffic between two PE taking one TE tunnel, you can have different loopback for the xconnect so that only traffic for that L2vpn can be routed via that tunnel.
I have tried setting up another tunnel interface between different loopbacks which comes up fine, however when I try to xconnect between the new loopbacks i get an MPLS Config error saying the loopback address is not a valid LDP id, use the original loopback instead.
For TE to come up , TE destination should be TE router-id on tail-end but for xconnect there is no such requirement. Please share the error message and check if LSP to new loopback is through or not. you can use command "ping mpls ipv4 <destination loopback> <source loopback>"
1. Introduction Internet security is important with the increasing
attacks that are happening every day. Many internet and browsing
security solutions exist, but some are not very easy to use or maybe the
question is how can I enable them? In this referen...
Cisco Software Manager Server API Guide This document describes the
programmatic interfaces, RESTful APIs, which are supported by Cisco
Software Manager Server (CSM Server). Overview CSM Server supports a set
of finite RESTful APIs. The first step to use ...
If you are using Cisco's new linux-based Cisco Software Manager server,
then you probably want to make sure there is a startup service for
it.I'll assume that you've already installed the CSM server on a
systemd-based linux system. The commands given belo...