From: Kenneth Wygand (KWygand@customonline.com)
Date: Tue Feb 24 2004 - 11:28:12 GMT-3
Do you have access to configure Rtr C and Rtr D?
Kenneth E. Wygand
Systems Engineer, Project Services
CISSP #37102, CCNP, CCDP, ACSP, Cisco IPT Design Specialist, MCP, CNA,
Network+, A+
Custom Computer Specialists, Inc.
"The only unattainable goal is the one not attempted."
-Anonymous
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Nordhoff, Michael G. (US - Hermitage)
Sent: Tuesday, February 24, 2004 9:13 AM
To: ccielab@groupstudy.com
Subject: Policy-based Routing (Failover)
Any ideas on handling the following scenario that incorporates 4 routers
and policy-based routing (PBR)?
Rtr A --- Rtr C --- MPLS Carrier 2
|
Rtr B --- Rtr D --- MPLS Carrier 1
Router A and Router B are directly connected. Router B is the primary
router in an HSRP group with Router A. Router A is connected to Router
C which connects to MPLS carrier 2. Router B is connected to Router D
which connects to MPLS carrier 1. PBR is implemented on the ingress
port of Router B such that all voice traffic is sent to Router D as long
as it is up and to Router A if Router D is down. All other traffic is
sent to Router A as long as it is up and to Router D if Router A is
down. The problem is that from Router B my PBR configuration cannot
detect an MPLS link failure on Router D and automatically redirect all
traffic to Router A. I've implemented PBR because I need to route
packets based on more than just destination network. I'm not
necessarily locked-in to using PBR if there is a better way to
accomplish this. Any thoughts?
Mike Nordhoff - CCIE #12849
WAN Engineer
Deloitte Services LP
Main: +1 615-882-7600
Direct: +1 615-882-7741
Pager: +1 888-490-3968
Mobile: +1 615-403-7869
mnordhoff@deloitte.com
www.deloitte.com
4022 Sells Drive
Hermitage, TN 37076
United States
This message (including any attachments) contains confidential
information
intended for a specific individual and purpose, and is protected by law.
If
you are not the intended recipient, you should delete this message. Any
disclosure, copying, or distribution of this message, or the taking of
any
action based on it, is strictly prohibited.
This archive was generated by hypermail 2.1.4 : Fri Mar 05 2004 - 07:13:56 GMT-3