If you want to use TE tunnels only for a specific VPN, but not for all of them, you have to define different Lo address for the next-hop for that particular VPN (VRF) and route this address via the TE tunnel. This will force the traffic flow over the TE tunnel.
It is supported for sure! In you case you can simply route with static route statement the Lo0 (the default next-hops of the VPNv4 routes) via the TE tunnel you want to use. The other option is to use autoroute announce feature.
For example Case 1 from the link you provided in your first post.
Yes, this is supported and shouldn't be a problem. As mentioned already by Hristo, you need the RIB to point the BGP nexthop (other PE) to go over the tunnel. This can be done statically, or via the IGP with the use of "autoroute announce". Then you need to have LDP neighborship over the tunnel. This is done simply by adding the TE interface under the MPLS LDP config. You will also have to configure "discovery targeted-hello accept" on the tunnel tail-end to accept the targetted session. This will allow you to send labelled traffic over the tunnel.
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...