[c-nsp] easy way to re-route sql traffic down alternate link?

[Rodney Dunn]

And depending on what your overall topology looks like it
might be easier to build a GRE tunnel through the network
and leak the route to the tunnel destination down the path
you want to pull the traffic down.  Then at the tunnel headend
you apply PBR and route the traffic in the tunnel.

That way you might can get away without having to do PBR
on every single hop along the path.

Rodney

On Tue, Apr 12, 2005 at 09:43:48AM -0700, Bruce Pinsky wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Matt Bazan wrote:
> | Hi all, We have a mesh of offices connected via T1's running OSPF.  What
> | I need to do is direct sql traffic from one office along a specific path
> | to its destination and back along the same route.  Is this best
> | accomplished using an ACL to capture the sql traffic and then statically
> | route?
> 
> Policy Based Routing can be used to match the SQL traffic (and optionally
> the source and/or destination addresses as well) and then direct it to the
> appropriate T1.  No need for static routes in this case as you will make
> the switching decision based on the type of traffic (not the destination
> address) and set either the IP next hop or the next hop interface manually.
> 
> - --
> =========
> bep
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.0 (MingW32)
> 
> iD8DBQFCW/rEE1XcgMgrtyYRAnB8AJ9YMBGGCLF81/rd5+sOQVx5j+ez0QCgqy3P
> riTfZDB2N5+f0rdE5x7mSko=
> =+rvt
> -----END PGP SIGNATURE-----
> _______________________________________________
> 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/