Would your solution satisfy all the requirements and restrictions of the task? Will it behave in a scenario with asymmetric routing?
-- Marko Milivojevic - CCIE #18427 Senior Technical Instructor - IPexpert FREE CCIE training: http://bit.ly/vLecture Mailto: [email protected] Telephone: +1.810.326.1444 Web: http://www.ipexpert.com/ On Mon, Nov 15, 2010 at 13:46, Jay Taylor <[email protected]> wrote: > Any thoughts on this? > > ---------- Forwarded message ---------- > From: Jay Taylor <[email protected]> > Date: Sat, Nov 13, 2010 at 10:17 AM > Subject: Fwd: Vol1 Lab18 > To: CCIE OSL <[email protected]> > > > > > ---------- Forwarded message ---------- > From: Jay Taylor <[email protected]> > Date: Fri, Nov 12, 2010 at 7:01 PM > Subject: Fwd: Vol1 Lab18 > To: CCIE OSL <[email protected]> > > > > > ---------- Forwarded message ---------- > From: Jay Taylor <[email protected]> > Date: Wed, Nov 10, 2010 at 8:59 PM > Subject: Vol1 Lab18 > To: CCIE OSL <[email protected]> > > > For Vol1 Lab18 Task18.6c would using 'ip verify unicast source reachable-via > rx' on the eBGP peer interfaces be an acceptable answer? Curious why the DSG > goes through the trouble of creating several lines of ACL's rather than just > 1 interface command unless it's just to show another potential way of > handling the task. > > > > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
