Thanks for the suggestion Dale, I'll have a look into that. In the meantime, if anybody has any more ideas please let me know.
Regards, Fernando On 05/03/2013, at 18:13, Dale Shaw <[email protected]> wrote: > Hi Fernando, > > On Mar 5, 2013 9:52 PM, "Fernando Santos" <[email protected]> > wrote: > > > >[…] > > We were trying to figure out if there is a way to keep only 1 tunnel > > between each remote and central site, while if the primary circuit goes > > down on a remote site, the QoS policies are afected also on the central > > site VTI tunnel. > > This is just an untested idea but perhaps you could combine EEM on the spoke > side with the "per-tunnel QoS" NHRP feature available for DMVPN? > > http://www.cisco.com/en/US/docs/ios/sec_secure_connectivity/configuration/guide/sec_per_tunnel_qos.html > > Maybe using EEM to change the NHRP parameters on the spoke's VTI when it > switches to the backup link is enough to signal to the hub that it should use > a different outbound service-policy. > > I'm not sure if you'd have to be running DMVPN to make this work -- it'd have > to be tested. > > Cheers, > Dale _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
