On Sat, Oct 27, 2012 at 5:01 PM, Randy Bush wrote:
>> It's often cited as a headache to maintain the PTRs (not really,
>> automation ftw!) I think really it gets down to "how does it really
>> help?"
>
> why is my traffic between seattle and new york going through tokyo?
'because someone forgot t
> It's often cited as a headache to maintain the PTRs (not really,
> automation ftw!) I think really it gets down to "how does it really
> help?"
why is my traffic between seattle and new york going through tokyo?
randy
You might want to take a look at the CEF book, which expands on this
http://www.amazon.com/Cisco-Express-Forwarding-ebook/dp/B0015V9DQU/
both of these are still very accurate on how IOS operates today. The
only major changes with IOS-XE is that IOS is now a process and packet
forwarding is handled
On Sat, Oct 27, 2012 at 7:05 AM, Anurag Bhatia wrote:
> Hi Blair
>
>
> I guess that's pretty much because they don't really wish to put any info
> related to routers in public including location & circuit bandwidth which is
> often given major networks in PTR.
>
more over, what help is it? I'm of
Hi Blair
I guess that's pretty much because they don't really wish to put any info
related to routers in public including location & circuit bandwidth which
is often given major networks in PTR.
Btw I guess you must be troubleshooting some routing issue. My experience
has been decent with them
All vendors should be writing in depth architecture books. The Juniper MX book
is a great example. Tell us exactly what your product can do and we'll likely
use more of it
> Date: Fri, 26 Oct 2012 20:01:58 -0400
> Subject: Re: IOS architecture
> From: da...@davidswafford.com
> To: khomyakov.and
6 matches
Mail list logo