Books
Advanced IP Routing in Cisco Networks (Second Edition)
Corrections to the Book
The bugs are sorted by inverse bug ID. To check for a bug on a particular page, use your browser's 'Edit->Find' function to search for the page number. Each line is organized by severity, bug ID, date, person, page number, and description. Bug severity is identified by the following key:
* Cosmetic or formatting
** Minor technical
*** Major technical
We've been asked about sorting the bugs list via various keys, such as the page number, or who found the bug. We don't have that capability, but you can do the sorting yourself by downloading a CSV version (Comma-Separated-Values) of the bugs list. Open the CSV file in a spreadsheet and enjoy!
Make sure you hit REFRESH or RELOAD if you've been viewing the bugs list lately.
There should be a lot fewer bugs in this edition than in the first edition. There are a couple of reasons for this. First, we started with the text and corrections from the first edition. Thanks to all the folks who reported bugs. The second reason is that we used Frame Maker to create the second edition. Using a quality tool like this to write a book really improved the process and allowed us to avoid many of the errors that crept into the first edition, particularly the formatting errors.
**,58,8/5/03,Tom Petch,431,"Second line on the page, change 'The static outside global address …' to 'The static outside local address …'."
**,57,8/5/03,Tom Petch,428,"Second line on the page, change 'Line 12 shows the translation of inside global to inside global …' to 'Line 12 shows the translation of inside local to inside global …'."
**,56,8/5/03,Tom Petch,422,"End of the third paragraph, change 'Line 10 shows the translation of inside global to inside global …' to 'Line 10 shows the translation of inside global to inside local …'."
**,55,8/5/03,Tom Petch,406,"Second paragraph, change 'Line 4 defines a pool of valid outside addresses, …' to 'Line 4 defines a pool of valid inside global addresses, …'."
**,54,8/5/03,Tom Petch,396,"Second paragraph, change 'Line 4 defines a pool of valid outside addresses, …' to 'Line 4 defines a pool of valid inside global addresses, …'."
*,53,1/28/03,Patrick Horne,581,The first sentence under CCIE tips has a 'the the' in it. I think you meant 'to the.'
*,52,1/28/03,Patrick Horne,429,"The command in Code Listing 8-47should technically be 'show ip nat translation(s)'. I know 'show ip nat translation' works at the CLI, but the 's' drives the point that it shows all IP protocols. There are a couple of instances of this in the following pages."
*,51,1/28/03,Patrick Horne,334,"There's a miscellaneous ""19"" hanging around in the upper right corner of the diagram."
*,50,1/28/03,Patrick Horne,327,There's a miscellaneous '0' hanging around in the upper right corner of the diagram.
*,49,1/28/03,Patrick Horne,319,There should be a space between '...example.The..' in the first paragraph.
*,48,1/28/03,Patrick Horne,"299, 311",Questions #1 (p299) and #2 (p311) don't mention that the answers are at the end of the chapter.
*,47,1/28/03,Patrick Horne,299,"The command in Code Listing 7-23 should technically be 'show ip protocol(s)'. I know 'show ip protocol' works at the CLI, but the 's' drives the point that it shows all IP protocols. There are a couple of instances of this in the following pages."
*,46,1/28/03,Patrick Horne,246,The last sentence should be 'Hello packets are use(d) to elect…'
*,45,1/28/03,Patrick Horne,217,The very top network address number connecting NY e0 and Moscow e0 is chopped off. I think the image in the Framemaker box needs to be moved down just a tad.
**,44,1/18/03,Patrick Horne,202,Last sentence says 'Lines 13and 14…' There should be a space between '13' and 'and.'
**,43,1/17/03,Patrick Horne,187,"In the first full paragraph, the phrase '...routing table lookups is call the patricia…' should be '...routing table lookups is called the patricia…'."
**,42,1/16/03,Patrick Horne,181,"At the top of the page, the configuration for London's Serial 1.2 interface should have an IP address of 192.168.3.162."
**,41,9/30/02,Terry Slattery,55,"In Table 1-8, the delay for the 100,000,000 bps link should be .00675, not .010. This bug is probably due to rounding on a calculator and not taking the time to extend the precision beyond two digits. It's weird how long some of these bugs have existed."
***,40,9/16/02,Jason Molz,209,Figure 5-10 is missing the subnet number for the NewYork-Moscow link. It should be labeled 172.16.1.0/24.
***,39,5/29/01,Steve Hubbard,453,"Figure 9-2 is incorrect. It should show Paris and Moscow as well. The correct figure is available via a link at http://www.netcordia.com/advip-second-edition/advip2.html. Steve reported this bug before Mike Rubino's report (bug 30), only we lost Steve's email in our inbox. Steve receives a reward for finding the bug first. No, we don't ask Mike to return his ;-)."
*,38,4/26/02,Terry Slattery,519,"In the first paragraph, change 'for networks 172.31.1.0 through 172.31.8.0' to 'for networks 172.31.1.0/24 through 172.31.7.0/24'."
*,37,4/26/02,Terry Slattery,525,"Code Listing 10-55, line 36 should be deleted. It shows 10.0.0.1 as being a source of BGP routing information and there is no 10.0.0.1 in the network drawing or in the routing tables."
**,36,4/22/02,Michael Falar,46,"The bug report from the first edition reads: 'On Page 48, Table 1-6, the book indicates Type 2 to be 'destination unreachable' when it should be Type 3. As stated on page 47, 'message type 3 is destination unreachable'.' Michael is correct about the bug. In addition, the type code for Echo Reply should be 0, not 1. Both errors were due to a change by the editor - our manuscript is correct and the first revision back from the editor is incorrect. The change was not noted in the revised manuscript and we missed in our proof reading. Michael still gets his reward for finding the bug, which exists in both editions of the book."
**,35,2/4/02,Yulan Lee,412,Line 16 of Code Listing 8-26 should be deleted. There is no 10.0.2.1 in Figure 8-3.
** ,34,2/4/02,Yulan Lee,179,"Under the section of Discontiguous Subnets, line #2, 'that occurs with classless routing protocols' should be 'that occurs with classful routing protocols'."
**,33,1/21/02,Yulan Lee,389,"On the 7th line: 'A global address is used on the inside of the network …', it should replace 'inside' with 'outside'."
**,32,1/21/02,Yulan Lee,393,"In Table 7-2, change the description for 'ip nat inside source' (the one for a static parameter) from 'Outside global address that maps to a specific inside local address.' to 'Outside global address that maps to a specific outside local address.'"
**,31,1/21/02,Yulan Lee,393,"In Table 7-2, change the description for 'ip nat inside source' from 'Inside local address that maps to a specific outside global address.' to 'Inside local address that maps to a specific inside global address.'"
***,30,1/18/02,Mike Rubino,453,"Figure 9-2 shows a 3-router pod and should show a 6-router pod. The text references Moscow and Paris, which don't appear in the figure."
**,29,1/18/02,Mike Rubino,314,"Change "".. where 192.168.1.1 exists."" to ""… where 192.168.6.1 exists."""
**,28,1/14/02,Yulan Lee,524,"Line 39, Code Listing 10-53, should be ""ip route 0.0.0.0 0.0.0.0 Serial2.1""."
**,27,4/22/01,Terry Slattery,575,"Second paragraph, second sentence, change ""autonomous system 200."" to ""autonomous system 300."""
**,26,4/22/01,Terry Slattery,575,"In Figure 11-3, remove London's Loop2 interface. It is not included in this example."
***,25,4/22/01,Terry Slattery,575,"In Figure 11-3, remove Paris and the serial link to NewYork and the interface on NewYork that is designated as S1/0:23 - .1. Paris and this link are not used in the example."
**,24,4/2/01,Jared Badger,474,"The AS Path 300, 400, 200, 100 is absent from the list."
**,23,1/5/01,Terry Slattery,392,Table 7-2 should be labeled Table 8-1.
*,22,12/31/00,Jeffrey Wickham,614,HTTP should be defined as Hypertext Transfer Protocol.
*,21,12/31/00,Jeffrey Wickham,613,CCO should be defined as Cisco Connection Online.
*,20,12/31/00,Jeffrey Wickham,"613, 230",ASBR should be defined as Autonomous System Boundary Router.
*,19,12/31/00,Jeffrey Wickham,600,"In the last sentence, change computer to computers."
***,18,12/31/00,Jeffrey Wickham,581,"In Code Listing 11-30, the network of the PC IP address that you attempt to ping, presumably 192.168.200.0/24, does not appear in Figure 11-3 on page 575. Change the ping target address to 192.168.1.1, which is NewYork's Loop0 interface address."
***,17,12/31/00,Jeffrey Wickham,579,"In Code Listing 11-26, NewYork's configuration should not contain any ISDN parameters because it is not part of the ISDN configuration in this example. Replace the following lines with an empty comment line, ""!"": 6, 16, 17, 23, 24, 25."
*,16,12/31/00,Jeffrey Wickham,576,"In Code Listing 11-21, there should be a space between line 14 and the beginning of the dialer map command."
**,15,12/31/00,Jeffrey Wickham,575,Figure 11-3 shows OSPF areas while the example is using EIGRP. The fix is to remove the OSPF areas from Figure 11-3.
**,14,12/31/00,Jeffrey Wickham,575,"Based upon the configurations for London (Code Listing 11-21-pages 575-576) and NewYork (Code Listing 11-26-pages 578-579), the S1/0:23 for NewYork and London should be a BRI interface as you are using a basic-ni switch type for both NewYork and London. Change the NewYork and London S1/0:23 interface designations to BRI0/0 interfaces in Figure 11-3."
*,13,12/31/00,Jeffrey Wickham,556,"On the last line of text, ""Let's move to NewYork to finish the SnapShot configuration,"" change SnapShot to snapshot."
**,12,12/31/00,Jeffrey Wickham,420,"Following Code Listing 8-37, the sentence ""Code Listing 8-42 shows the Moscow configuration where our NAT process takes place"" should be changed to reference Code Listing 8-38."
**,11,12/31/00,Jeffrey Wickham,405,"In figure 8-3, the London ethernet is listed as 131.108.2/24 when it should have been 131.108.2.0/24."
**,10,12/31/00,Jeffrey Wickham,405,"In figure 8-3, the 131.108.1.0/24 network is shown as attached to E0 on NewYork, but it never appears in the configuration or routing tables for NewYork. The fix is to remove 131.108.1.0/24 from Figure 8-3."
*,9,12/31/00,Jeffrey Wickham,262,"The sentence under the FYI on page 262 does not make much sense: ""During development, a number of ideas were shared between the IS-IS developers, the OSPF developers, and their experience and operation with the DECnet Phase IV routing protocol."" Quite right! A better wording is ""During development, a number of ideas were shared between the IS-IS developers and the OSPF developers. The knowledge gained from thne DECnet Phase IV routing protocol also helped both OSPF and IS-IS."""
*,8,12/31/00,Jeffrey Wickham,262,"""OSPF, Anatomy of an Internet Routing Protocol"" should be changed to ""OSPF: Anatomy of an Internet Routing Protocol"" (the comma after OSPF should be a colon)."
**,7,12/31/00,Jeffrey Wickham,405,"On page 405, the network connecting Tokyo S0 to New York S1 is listed as 131.108.3.0/24 when it should have been 144.251.1.0/24 (based upon the configs and show commands used for New York and Tokyo)."
**,6,12/31/00,Jeffrey Wickham,389," On page 389, ip nat input and ip nat output (in bold) should be ip nat inside and ip nat outside, respectively."
*,5,12/31/00,Jeffrey Wickham,"xii, 624","The URL for books is not valid. The file books.html existed, but that wasn't the URL listed in the book. Thanks, Jeffrey, for reporting the problem!"
* *,4,12/6/00,Jim Fickett,111,The line numbers are incorrect in Code Listing 3-1. The line numbers in the figure should start at 1.
,3,,,,Skipped bug ID.
*,2,11/29/00,Daron Goodson,xii,"""… DCE (data circuit-terminating equipment) is the correct meaning of the acronym ""DCE"" and not (data communications equipment)."" On 2/11/03, Patrick Horne reported the following: ""I was studying for my BCRAN exam yesterday with a Ciscopress book and it mentions that there are two definitions of DCE. The ITU-T defines DCE as Data Circuit-Terminating Equipment. However, EIA defines DCE as Data Communications Equipment."" So it seems that either definition is correct, depending on whose standards you read."
*,1,9/30/00,Terry Slattery,ix,"In the last line of the fourth paragraph, change www.intaligent.com to www.netcordia.com."