[c-nsp] MPLS TE traffic forwarding.

[Pshem Kowalczyk]

I would add one more option here

5. Statically bind VPNs to particular tunnel (not all software
versions support this).

kind regards
Pshem

On 25 March 2010 14:28, Robert Crowe (rocrowe) <rocrowe at cisco.com> wrote:
> Many ways, simple to complex:
>
> 1. Static routes - route specific destinations down the TE tunnel
> 2. Autoroute - let the IGP SPF compute paths down the TE tunnel (headend local)
> 3. Forwarding Adjacency - injects the TE tunnel into the IGP
> 4. CBTS/PBTS - forward specific EXP values down the TE tunnel
>
> Robert Crowe
> Email: rocrowe at cisco.com
>
> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Michael Sprouffske
> Sent: Wednesday, March 24, 2010 7:15 PM
> To: cisco-nsp at puck.nether.net
> Subject: [c-nsp] MPLS TE traffic forwarding.
>
> I'm not sure if this has already been posted.
> I'm trying to figure out a concept of the TE tunnel.  It appears that when a tunnel is created it will forward all traffic destined for the end point down the tunnel.  My question is, is there  a way to create a tunnel and have only specific traffic go down the tunnel? If this is already answered please give a link for the location.
>
>
>
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>