Latest Errata for my 6th Edition

[lammle]

If you think you have found an error, or have a general question, or a specific one, or even one to me privately, you have come to the right place!

Here is the latest errata link for my 6th edition:

http://www.sybex.com/WileyCDA/SybexTitle/productCd-0470110082,navId-290611,pageCd-errata.html (http://www.sybex.com/WileyCDA/SybexTitle/productCd-0470110082,navId-290611,pageCd-errata.html)

Secondly, please browse through the forum. There are hundreds of posts, many interesting and some may already answer any question you have.

Cheers!
Todd Lammle

[mr88talent]

Some of this may have been mentioned before, but I am trying not to duplicate errata listed on the Sybex site. Not all is exactly errata, some are suggestions to clarify the text.

Typo, page 175, 2nd paragraph
... that are less expensive then the 2800 series:
s/b (should be)
... that are less expensive than the 2800 series:

Typo, page 176, last sentence
239K of NVARM
s/b
239K of NVRAM

Page 196, missing text:
Todd(config)#line console ?
<0-0> First Line number
Todd(config-line)#password console
s/b
Todd(config)#line console ?
<0-0> First Line number
Todd(config)#line console 0
Todd(config-line)#password console

Page 204, typo:
Router(config)-if)#
s/b
Router(config-if)#

General comment about page 297 in regards to Ctrl+Shift+6:
You might mention that what you are actually entering is Ctrl+^ (the caret symbol), therefore, the 6 on the numeric keypad will not work. You actually want Ctrl+^x, none of which will be seen on the console as you type it.

Pages 341, 343 and 427
already noted here:
http://www.lammle.com/discussion/showthread.php?t=135

Page 349 (sh ip route from Corp router - about half way down the page)
10.0.0.0/24 is subnetted, 4 subnets
s/b
10.0.0.0/24 is subnetted, 3 subnets

Page 373
I’ll start by pinging from the 1242AP to the 871W router.
s/b
I’ll start by pinging from the 871W to the 1242AP router.

Typo, page 397
Why? Because RIPv2 doesn’t send broadcasts; it used the multicast 224.0.0.9.
s/b
Why? Because RIPv2 doesn’t send broadcasts; it uses the multicast 224.0.0.9.


Suggest better wording, page 398:
Sentence located 7/8 of the way down the page:
The output also shows that 172.16.150.0 is directly connected to FastEthernet 0/0 and network 172.16.20.0 is out serial 0/0.
suggestion:
The sh ip route output shows that 172.16.150.0 is directly connected to FastEthernet 0/0; therefore, packets with a destination of 172.26.20.0 are switched to the wrong interface.

Ambiguous wording page 427
Sentence begins after the "Note":
Okay, let’s configure the same network that we configured in the last chapter with RIP and RIPv2.
suggestion:
Okay, let's take the same network that we configured with RIP and RIPv2 (from the last chapter) and reconfigure it.

Possibly incorrect statement, page 442, last paragraph (suggest a little research on this):
the debug ip eigrp notification command (called debug ip eigrp events on pre-12.4 routers)
I think this should read:
the debug ip eigrp notification command (called debug ip eigrp events on pre-12.0 routers)

Sentence wording could be improved, page 509:
There are two things to notice right off the bat here: Switch B is running the IEEE 801.d protocol, and the first output (Root ID) is the root bridge information for the switched network. But it’s not Switch B.
possibly better wording:
There are two things to notice right off the bat here: Switch B is running the IEEE 801.d protocol, and the first output (Root ID) is the root bridge information for the switched network. But switch B is not the root bridge.

Page 511, Figure 8.12
Why is this optimal? If a single 3560 goes down, a third of the network is disconnected. Shouldn't the 2960's be connected together?

Typo. Page 563, a period is missing from the sentence:
Second sentence after VLAN Trunking Protocol (VTP) heading:
The basic goals of VLAN Trunking Protocol (VTP)are to manage all configured VLANs across a switched internetwork and to maintain consistency throughout that network VTP allows you to add, ...
s/b
The basic goals of VLAN Trunking Protocol (VTP)are to manage all configured VLANs across a switched internetwork and to maintain consistency throughout that network. VTP allows you to add, ...

Page 578 and 580, Figure 9.11 and 9.12
I think maybe the F0/0 interface on the router should be marked as such.

Typo, Page 610, last sentence.
... the various strategies for security are based on a some recipe of internal and perimeter routers plus firewall devices.
s/b
... the various strategies for security are based on a recipe of internal and perimeter routers plus firewall devices.

Comment about page 622 and 623 (Standard Access List Example):
I had a hard time understanding the difference between in and out (direction) therefore I had a hard time understanding why the first example made sense to you, but not to me. It would have help a lot if you were to explain something like: To conceptualize inbound or outbound, picture yourself standing in the center of the router.

Page 675, near the bottom of the page:
The ip nat pool todd 170.168.2.2 192.168.2.254 command ...
s/b
The ip nat pool todd 170.168.2.2 170.168.2.254 command ...

Page 679 Figure 11.5
The router labeled Lab_A, might possibly be renamed to BDR_RTR since this is referred to as the border router, with no mention of Lab_A in the text.

[mr88talent]

Continued from my previous post:

Page 682 and 683
Start 2/3 of the way down page 682, it starts off with:
Now that PAT is configured and our interfaces are all set, let’s telnet from HostC to HostD ...
The first 'sh ip nat trans' makes sense.
After that, you talk about HostB (which would have an IP address of 10.1.7.2). I think you wanted to continue on with HostC (10.1.9.2), so every reference to HostB should be changed to HostC. Now, the output from the following 'debug ip nat' would have had to come from HostA (10.1.6.2), so I think you actually want to change every occurance of 10.1.6.2 to 10.1.9.2 so this lines up with what HostC would have produced.

Page 691, missing text on item 2.:
Lab_A#config t
Lab_A(config-router)#network 192.168.20.0
Lab_A(config-router)#network 171.16.0.0
s/b
Lab_A#config t
Lab_A(config)#router rip
Lab_A(config-router)#network 192.168.20.0
Lab_A(config-router)#network 171.16.0.0

Page 709, figure 12.3
Arc #10 is bold, where arc #11 should be bold instead.

[lammle]

I have seen this misinformation in the Nat section after someone brought it up to me. It was probably one of those super long days, late night lab errors. I telnetted from one host, thinking it was a different host.

thanks for the updated missing "router rip" info!
Todd

[lammle]

Thank you for your post! I want to use you as my next tech editor.
Those were some great finds.

I'll be able to go through that and make the changes in the book.

Thank you again for posting and helping me make my book better!

Cheers!
Todd Lammle

[mr88talent]

The post itself has not shown up yet, it's still held by the moderator. :(

[lammle]

Sorry about that, I didnt' notice as everything shows up for me!
Todd

[lammle]

Here is the latest errata link for my 6th edition:

http://www.sybex.com/WileyCDA/SybexTitle/productCd-0470110082,navId-290611,pageCd-errata.html (http://www.sybex.com/WileyCDA/SybexTitle/productCd-0470110082,navId-290611,pageCd-errata.html)

[pcween]

Hello.

Do you already have Errata for your "CCENT Study Guide"? I already looked on the Sybex Website (http://www.sybex.com/WileyCDA/SybexTitle/productCd-0470247029.html), but without success.

Is there a forum for the CCENT-book as well? Where should I post the typos/errors I found?

Greetings,
pcween

[lammle]

No, we do not have an errata yet. Hopefully it will be a small one!! :)

I'll create a link today....
Thank you for bringing this to my attention.

Cheers!
Todd Lammle

[lammle]

I will have a link up shortly for the CCENT errata pages


It won't be THAT big!! :)
Todd

[laser]

Hello,

I've read through the posts and errata link. I hope this is OK.
I don't understand this question on pg. 133:

What is the subnet and broadcast address of the host 172.16.88.255/20?

should that be 172.16.88.254/20?

If I'm off and the book is correct can someone please explain to me.

Thank you very much

Al

[riverfest]

Hi Laser,

172.16.88.255/20 is a legit address. I think you are concerned with the last octet of 255. (88.255 is not a broadcast address 172.16.79.255 would be and so would 172.16.95.255)

A /20 is a 16 block size (a favorite subnet for testing according to Todd) which means four of the bits from the 3rd octet are used for subnetting.
The subnets would be 172.16.0.0, 172.16.16.0, 172.16.32.0, 172.16.48.0, 172.16.64.0, 172.16.80.0, 172.16.96.0, etc.

So if you are looking for subnet and broadcast address.
172.16.80.0 is subnet and the broadcast is the last address before 172.16.96.0 which would be 172.16.95.255.

Riverfest

[laser]

OK I think I understand
Thank you very much Riverfest

[netwayne]

Core switch interfaces are addressed in configuring lines as

f0/5, fa0/5, f0/7 and f0/8. I believe they should be addressed as

fa0/5, fa0/6, fa0/7 and fa0/8.

[netwayne]

Which Cisco 802.1d extension stops BPDU from being transmitted out a port?

I believe the answer to this question should be bpdufilter.


The answer listed on p. 550 says portfast.

Am I wrong?

[newbie]

I have found a few typos/errors in the book. Most of them are listed in the errata and some are documented in this forum. But a few are not mentioned. I'm listing them below.

* On page 352, above the Note, "The Corp, R1, and R2 routers now have all their links up. But we still need to configure R3 (the 871W router) and the 1242 AP"

* On page 385, under R2's configuration, one of the directly connected network (10.1.4.0) is missing.

* On page 468, just before "Okay, that did it", "Routing Process "ospf 132" with ID 172.16.10.1"

* On page 478, last line, "Lab 7.5: OSPF DR and BDR Elections"

* On page 509, just after [output cut], "There are two things to notice right off the bat here: Switch B is running the IEEE 802.1d protocol, and the first output (Root ID) is the root bridge information for the switched network."

* On page 584, towards the bottom, "Switches in VTP server mode will share VLAN information using VTP"

* On page 605, Answer 9, "However, a 3560 can run both ISL and 802.1Q, so you must use the encapsulation command." (Not entirely sure if this is a typo or if you really meant 3550... I think both are correct)

* On page 646, "I can easily add, delete, and manage my ACL from here"

* On page 747, Figure 13.2, "Step 2: Router sends RA message"


* On page 753, at the top
Router1(config)#ipv6 router ospf 10
Router1(config-rtr)#router-id 1.1.1.1I realize most of these are minor typos (hey, I like to nitpick!)... but I believe this excellent book should be completely error free.

CCNA Study Guide, Sixth Edition

[lammle]

Thank you!
I am always looking to improve my book and am not too proud to take emails/posts, etc to help the book become better. And the little errors matter!

It's funny how many errors you see the minute the book is in print. I read the book cover to cover at least a dozen times and didn't see any of these...

Thank you again!
Todd Lammle

[swaminathan]

Hello Mr.Lammle

In the 6th edition of your book, in chapter 1 of Ethernet Networking, about ethernet MAC addresses, it is mentioned that the high-order bit represents the Individual/Group bit (47) & for Global/local bit is 46th bit of the MAC ADDRESS's OUI .http://upload.wikimedia.org/wikipedia/commons/thumb/9/94/MAC-48_Address.svg/475px-MAC-48_Address.svg.png (http://www.lammle.com/wiki/File:MAC-48_Address.svg)


The figure which I pasted is from wikipedia.It is saying that the LSB of the most significant byte of the MAC represents the I/G & G/L

Which is correct?

Please explain to me

Thanks

S.Swaminathan

[TomS]

Todd,
Do you know when the errata provided here, especially that in comment 17 will be added to the official Sybex errata page? It would be very helpful. Also, can an official correction to the ARP process description on page 5 (6th edition) be added as well? The book does not describe where Bob was able to acquire Sally's IP.

Thanks,
Tom