more on wendell's new icnd2...

1. The sending VPN device  feeds the orignal packet and the session key into the encryption formula, calculating the encrypted data.

2. The sending device encapsulates the encrypted data into a packet, which includes the   new IP header and VPN header.
 
3. The sending device sends this new packet to the destination VPN device  

4. The receiving VPN device runs the corresponding decryption formula, using the
encrypted data and session key—the same key value as was used on the sending VPN
 device—to decrypt the data.

it is safe to say the icnd2 is no longer the same animal as it was... for those just starting out, go right to the new books... for those half way through ccna, go back to the beginning if you don't think you'll make it to the exam before october 1st... for those who have ccna or better, this is a must read...

wendell's new ccna series...

if you haven't done so already, get over to ciscopress and get wendell's new cnna book(s)...  this is a major departure from the last icnd1 and 2...  any self respecting network guy/ccna or better will want to read this right away... there are also many extras, videos, tests, etc... 

no matter your certification level, this is a must... it'll probably be quite a few years before another...

i got mine two days ago....

below is a post i did over on ccieordie.com

quote of the day, wendell…

of course i got the new ccna book (the icnd2, anyway) because this is monumental… it has been quite a while since there has been a sweeping change to this series…  anyone who has slaved through ccna will want to read this, no matter your current cert level… it also comes with extra content like videos, test engine, etc…  you owe it to yourself to take a walk down memory lane…

here is a nice sample tidbit…  you know by default the priority of a switch is 32,768 without the extended system id… when using the root primary macro, the new setting will be 24,576… you also know that priority is set in 4096 increments… but that’s an 8192 difference not 4096… do the math…

For the switch intended to take over as the root if the first switch fails, use the spanning-tree vlan vlan-id root secondary command. This command is much like the spanning-tree vlan vlan-id root primary command, but with a priority value worse than the primary switch but better than all the other switches. This command sets the switch’s base priority to 28,672 regardless of the current root’s current priority value.

ccie... concentrate...

this is a companion to an earlier post...

i've heard complaints about wendell's cert guide for ccie r&s... regardless of the complaints it is a must read... end of story there...

it is very long but so is this adventure... by contrast the ccie quick reference is only 250 pages... i have to laugh as i look at that... quick ref, only 250 pages, there's some irony in that...

here's the thing; yeah i'm gonna tell you the thing... this stuff is not meant to be read like normal human's would read...  you have to dissect this shit with a microscope...

here's an example:

i have read various articles about the elusive lsa type 4, and i'm pretty sure i have a good handle on that one... elaborate articles, with configuration examples, output, all that...

if you are simply reading, which means, looking, you will miss this:

When an ABR then floods the type 5 LSA into another area, the ABR creates a type 4 LSA, listing the ABR’s metric to reach the ASBR that created the type 5 LSA.

it is frightening how you can convince yourself you got it when you read it when in fact you missed the whole thing...

the ABR creates a type 4 LSA, listing the ABR’s metric to reach the ASBR that created the type 5 LSA.

now that's the thing 

the ABR creates a type 4 LSA, listing the ABR’s metric to reach the ASBR that created the type 5 LSA.

the ABR creates a type 4 LSA, listing the ABR’s metric to reach the ASBR that created the type 5 LSA.  

sh run...

hit it wendell...

As in all CCIE exams, you should expect that the easiest or most direct ways to a solution might be unavailable to you. In troubleshooting, perhaps the easiest way to the source of most problems is through the show run command or variations on it. Therefore, we’ll institute a simple “no show run” rule in this section that will force you to use your knowledge of more in-depth troubleshooting commands in the Cisco IOS portion of this section.

and he's right...

sh run is for pussy's...