From: Christian Peterson (Christian.Peterson@xxxxxxxxxxx)
Date: Thu Dec 23 1999 - 12:05:54 GMT-3
Don't forget to investigate providing ddr/dial backup through policy-based
routing. in this scenario no statics are used (neither are backup
interface commands). tricky, but it is a requirement i have seen on the
lab.
christian
SSinyagin@mtu.ru on 12/19/99 01:47:00 PM
To: cliftonlstewart@home.com
cc: ccielab@groupstudy.com (bcc: Christian Peterson/US/ABNAMRO/NL)
Subject: Re: One-way DDR example?
Clifton L. Stewart <cliftonlstewart@home.com> wrote:
CLS> Guys,
CLS> I still wondering about that post from yesterday regarding the One-Way
CLS> DDR. Why would you ever want to implement a design like that? I
thought
CLS> the whole purpose is the have either side dial in case of an circuit
CLS> outage. I have posted my configs from my 2520 and 2504, to better
CLS> understand the concept, I welcome any suggestions for changes to my
CLS> config, thanks.
Sometimes it's a Lab requirement that only one router issues the
connection. As a variant, it could be that both routers can initiate
the connection, but one of them should always call back (meaning that
the calls from A to B are cheaper than those from B to A)
Also, if we build the DDR for a frame-relay link, and one of the ends
of the PVC is a FR interface without subinterfaces, then that router
can't issue the DDR calls in principle.
Be ready to implement any possible scenario on the exam lab: one-way
DDR, two-way, callback, with backup interface, without it (floating
statics), be ready to specify the conditions when to bring up the
second B-channel (on 60% load, never, etc.), DDR with dialer map or
without it (dialer string), a protocol going through the DDR link, but
not bringing it up..... and so on
Stan
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:22:00 GMT-3