Network Warrior

Errata for Network Warrior

Submit your own errata for this product.


The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color Key: Serious Technical Mistake Minor Technical Mistake Language or formatting error Typo Question Note Update



Version Location Description Submitted By Date Submitted Date Corrected
Safari Books Online
Ch 29
Figure 29-4

Figure 29-4 is a duplicate of 29-2. From the text, it needs to be showing some VOIP phones along with the computers.

Note from the Author or Editor:
Can be fixed - I need to know how to upload new images. This is a minor mistake.

Anonymous  Jun 08, 2008 
Printed
Page Ch 29
Beneath Figure 29-2

The author talks about a T1 link at 1.5Mbps, then below he says "A T1 can handle 1,500,000 packets per second." This is 2-3 orders of magnitude in error!

Note from the Author or Editor:
Page 418, last paragraph. Change "1,500,000 packets per second" to "roughly 1,500,000 bits per second"

Anonymous  Jun 08, 2008  May 01, 2009
Printed
Page 8.3
First paragraph

"because someone decided to plug both network drops under his desk into the little switch she'd brought in from home" -- pick one gender or the other.

Note from the Author or Editor:
change "she'd" to "he'd": "...little switch he'd brought in..."

Anonymous  Jun 07, 2008  May 01, 2009
Printed
Page 9-10
15th Paragraph

"One of the other major problems when using hubs is the possibility of broadcast storms. Figure 2-6 shows two hubs connected with two connections. A frame enters the network on Switch 1, and is replicated on every port, which includes the two connections to Switch 2, which now repeats the frame out all of its ports, including the two ports connecting the two switches. Once Switch 1 receives the frame, it again repeats it out every interface, effectively causing an endless loop." AUTHOR'S RESPONSE: Since broadcasts are forwarded out every port in a switch, the result would be the same with either hubs or switches. In order to make the diagram match the text, Switch1 and Switch2 in the text should be replaced with Hub 1 and Hub 2.

Anonymous    Jun 01, 2008
Other Digital Version
9-10
15th Paragraph

"One of the other major problems when using hubs is the possibility of broadcast storms. Figure 2-6 shows two hubs connected with two connections. A frame enters the network on Switch 1, and is replicated on every port, which includes the two connections to Switch 2, which now repeats the frame out all of its ports, including the two ports connecting the two switches. Once Switch 1 receives the frame, it again repeats it out every interface, effectively causing an endless loop." AUTHOR'S RESPONSE: Since broadcasts are forwarded out every port in a switch, the result would be the same with either hubs or switches. In order to make the diagram match the text, Switch1 and Switch2 in the text should be replaced with Hub 1 and Hub 2.

Anonymous    Jun 01, 2008
Printed
Page 9-10
15th Paragraph

"One of the other major problems when using hubs is the possibility of broadcast storms. Figure 2-6 shows two hubs connected with two connections. A frame enters the network on Switch 1, and is replicated on every port, which includes the two connections to Switch 2, which now repeats the frame out all of its ports, including the two ports connecting the two switches. Once Switch 1 receives the frame, it again repeats it out every interface, effectively causing an endless loop." AUTHOR'S RESPONSE: Since broadcasts are forwarded out every port in a switch, the result would be the same with either hubs or switches. In order to make the diagram match the text, Switch1 and Switch2 in the text should be replaced with Hub 1 and Hub 2.

Anonymous   
Printed
Page 13
Last command/output example

Switch1-IOS> sho mac-address-table | include 0013.bada.d1ca * 18 0013.bada.61ca dynamic Yes 0 Gi3/22 SHOULD READ Switch1-IOS> sho mac-address-table | include 0013.bada.d1ca * 18 0013.bada.d1ca dynamic Yes 0 Gi3/22

Anonymous    Jun 01, 2008
Printed
Page 13
Last command/output example

Switch1-IOS> sho mac-address-table | include 0013.bada.d1ca * 18 0013.bada.61ca dynamic Yes 0 Gi3/22 SHOULD READ Switch1-IOS> sho mac-address-table | include 0013.bada.d1ca * 18 0013.bada.d1ca dynamic Yes 0 Gi3/22

Anonymous    Jun 01, 2008
Other Digital Version
13
Last command/output example

Switch1-IOS> sho mac-address-table | include 0013.bada.d1ca * 18 0013.bada.61ca dynamic Yes 0 Gi3/22 SHOULD READ Switch1-IOS> sho mac-address-table | include 0013.bada.d1ca * 18 0013.bada.d1ca dynamic Yes 0 Gi3/22

Anonymous    Jun 01, 2008
Printed
Page 38
1st paragraph

auto indicates that the port will listen for for DTP but will not actively attempt to become a port. Should be: auto indicates that the port will listen for for DTP but will not actively attempt to become a trunk.

Anonymous    Jun 01, 2008
Other Digital Version
38
1st paragraph

auto indicates that the port will listen for for DTP but will not actively attempt to become a port. Should be: auto indicates that the port will listen for for DTP but will not actively attempt to become a trunk.

Anonymous    Jun 01, 2008
Printed
Page 38
1st paragraph

auto indicates that the port will listen for for DTP but will not actively attempt to become a port. Should be: auto indicates that the port will listen for for DTP but will not actively attempt to become a trunk.

Anonymous   
Printed
Page 53
1st complete paragraph, and 1st inset paragraph

On page 53, first full paragraph, stated "If you configure VLAN 10 to be eligible for pruning, IOS considers this to mean that only VLAN 10 should be eligible." The following inset shows the command, "switchport trunk pruning vlan 10." However, the next paragraph and next inset paragraph indicate that VLAN 100 was the VLAN in question, instead of 10. AUTHOR'S RESPONSE: The first paragraph and following code inset should say VLAN 100.

Anonymous    Jun 01, 2008
Other Digital Version
53
1st complete paragraph, and 1st inset paragraph

On page 53, first full paragraph, stated "If you configure VLAN 10 to be eligible for pruning, IOS considers this to mean that only VLAN 10 should be eligible." The following inset shows the command, "switchport trunk pruning vlan 10." However, the next paragraph and next inset paragraph indicate that VLAN 100 was the VLAN in question, instead of 10. AUTHOR'S RESPONSE: The first paragraph and following code inset should say VLAN 100.

Anonymous    Jun 01, 2008
Printed
Page 53
1st complete paragraph, and 1st inset paragraph

On page 53, first full paragraph, stated "If you configure VLAN 10 to be eligible for pruning, IOS considers this to mean that only VLAN 10 should be eligible." The following inset shows the command, "switchport trunk pruning vlan 10." However, the next paragraph and next inset paragraph indicate that VLAN 100 was the VLAN in question, instead of 10. AUTHOR'S RESPONSE: The first paragraph and following code inset should say VLAN 100.

Anonymous   
Printed
Page 64
2nd paragraph

The sentence: "The hardware is listed as EtherChannel, and there is a line in the output that shows the members of this EtherChannel to be Gi3/1, Gi3/2, Gi3/4 and Gi3/4:" Should be: "The hardware is listed as EtherChannel, and there is a line in the output that shows the members of this EtherChannel to be Gi3/1, Gi3/2, Gi3/3 and Gi3/4:"

Note from the Author or Editor:
Thank you - this is fixed in the 2nd edition

Tim Slot  Feb 03, 2010 
Printed
Page 66
Second paragraph

"A bridge is a device that connects multiple segments within a single collision domain. Hubs and switches are both considered bridges." This is not true. A bridge is a device that conforms to the IEEE 802.1d standard. Bridges connect ethernet segments from different collision domains. Switches are fast bridges that can perform cut-through switching. Hubs are not bridges, but rather repeaters.

Note from the Author or Editor:
Thanks - this is fixed in the second edition

Anonymous  Jun 09, 2009 
Printed
Page 73
First paragraph under Preventing Loops with Spanning Tree

"because someone decided to plug both network drops under his desk into the little switch she'd brought in from home" -- pick one gender or the other.

Note from the Author or Editor:
This is resolved in the second edition - thanks!

Anonymous   
Printed
Page 95
Supernet description

The text says "A supernet is single route that ...". This probably should read "A supernet is a single route that ...".

Note from the Author or Editor:
Thanks - this is fixed in current editions, as well as the 2nd edition.

Anonymous  Nov 02, 2008 
Printed
Page 102
4th paragraph, last sentence

The example between the 3rd and 4th paragraphs states: ip route 0.0.0.0 0.0.0.0 192.168.1.1 1 ip route 0.0.0.0 0.0.0.0 10.0.0.1 2 The primary default route points to 192.168.1.1, and has a metric of 1. The second default route points to 192.168.1.2 and has a metric of 2. The last senetence should read: The second default route points to 10.0.0.1 and has a metric of 2. The IP in the text doesn't match the example.

Note from the Author or Editor:
Thanks! This has been resolved in the second edition.

Anonymous   
Printed
Page 104,105
3rd paragraph

In the text and in Figure 10-2 it states that the process ID is included in OSPF updates. This is not the case as the process ID has only local significance on the router, the following (from rfc2740) explains how the stated topology could be achieved. In OSPF for IPv4 this was supported in a haphazard fashion using the authentication fields in the OSPF for IPv4 header. However the stated example does apply to OSPF for IPv6 (See section 2.4 of rfc2740), which has the concept of 'Instance ID' which is included in updates

Note from the Author or Editor:
Thanks - this is resolved in the 2nd edition

Anonymous  Nov 13, 2008 
Printed
Page 104
2nd paragraph

The second paragraph goes on to say "These separate areas of control are called autonomous systems in EIGRP, and processes in OSPF. Each instance is referenced with a number--either an autonomous system number (ASN), or a process ID (PID)." This is incorrect, OSPF uses "Areas" to do this, not processes. The process number can be the same or different on all OSPF routers and it will not have any effect with regards to routing updates.

Note from the Author or Editor:
Thanks - this is resolved in the second edition

Anonymous   
Printed
Page 105
1st Paragraph

The paragraph states that OSPF must be run with the same process ID between routers for routes to be shared, this is false. process Id's are not passed between routers. If multiple routers exist on the same segment OSPF will form a neighbor adjaceny and share routes as long as the following are met: -Must pass authentication -Must be in the same primary subnet, including subnet mask -Must be in the same OSPF AREA -Must be of the same area type (NSSA, stub, etc) -Must no have duplicate RID -OSPF Hello and Dead timers must be equal (REF. Routing TCP/IP Vol. 1)

Note from the Author or Editor:
Thanks - this is resolved in the 2nd edition

Anonymous   
Printed
Page 105
Figures 10-2 & 10-3

As drawn, both figures show two OSPF processes running on various routers. These routers are connected to the same Ethernet. Given a standard OSPF configuration (no authentication, no statically configured neighbors, etc.) all routers shown will associate as neighbors. Process ID has no bearing on OSPF external to the router. The context given does not clear this up. (Contextual errata have already been submitted). The diagrams would be nearly correct if OSPF Areas are being discussed except that all OSPF areas must connect to area zero (0), which is not displayed.

Note from the Author or Editor:
This is resolved in the second edition.

cisco@malweth.net  Oct 06, 2009 
Printed
Page 115
2nd paragraph

"The passive-interface command causes RIP to ignore updates received on the specified interface. The command also prevents RIP from sending updates on the interface." The passive-interface command causes RIP to stop sending updates on the interface but the RIP process continues to listen and use advertisements received via the interface. It acts like an outgoing only filter for the RIP communication via the interface. See: http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a0080208748.shtml Remove the sentence "The command also prevents RIP from sending updates on the interface."

Anonymous   
Printed
Page 115
2nd paragraph

"The passive-interface command causes RIP to ignore updates received on the specified interface. The command also prevents RIP from sending updates on the interface." The passive-interface command causes RIP to stop sending updates on the interface but the RIP process continues to listen and use advertisements received via the interface. It acts like an outgoing only filter for the RIP communication via the interface. See: http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a0080208748.shtml

Note from the Author or Editor:
Reader is correct. Remove the sentence "The command also prevents RIP from sending updates on the interface."

Anonymous  Jun 22, 2008  Nov 01, 2008
Printed
Page 116
15th line

page 116: "The maximum hop count is 255 instead of 15. 256 is now the unreachable metric,as opposed to 16 with RIPv1." The hop count for Rip version 2 is 1 to 15 with 16 being unreachable. This is the same as Rip version 1. below are references http://www.cisco.com/en/US/docs/ios/12_0/np1/configuration/guide/1crip.html

Note from the Author or Editor:
Thanks. This has been resolved in recent printings, and is also resolved in the second edition.

Anonymous   
Printed
Page 116
RIPv2 section

An important benefit of RIPv2 is support for triggered updates (ref RFC 2453 and Cisco doc). It would also be good to emphasise that RIPv2 should always be used in preference to v1; and also that IOS defaults to v1 (i.e. you must explicitly include the 'version 2' IOS command - this has bitten me more than once...).

Note from the Author or Editor:
Second bullet on page 116. Replace entire bullet (it is inaccurate) with "RIPv2 supports triggered updates.

Anonymous  Sep 09, 2008  May 01, 2009
Printed
Page 122
Eighth definition ("Not So Stubby Area...")

Type-7 LSAs are described thus: "NSSA LSAs are sent by ABRs. These advertisements describe links within the NSSA." NSSA External LSAs are, in fact, sent by ASBRs. As is the case with type-5 LSAs, type-7s actually advertise the routes redistributed by the ASBR. Unlike type-5s, however, type-7s will either be blocked by all ABRs attached to the NSSA or translated into type-5s and propagated throughout the backbone area.

Note from the Author or Editor:
Fixed in second edition

Jonathan Storm  May 24, 2010 
Printed
Page 123
Last paragraph

Fouth line of the last paragraph on page 123 states: " ...the router will assign it to be the IP address of the LOWEST-NUMBERED loopback address, if one is configured" Should read: "...the router will assign it to be the IP address of the HIGHEST-NUMBERED loopback address, if one is configured" REFERENCE: CCNP BSCI OFFICAL EXAM CERTIFICATION GUIDE, ISBN-13 978-1-58720147-9, PAGE 142, 1st paragraph: " The OSPF router ID can be defined by the router-id command. If the router-id command is not present, then the router ID will be THE HIGHEST IP ADDRESS OF A LOOPBACK INTERFACE."

Note from the Author or Editor:
Thanks - fixed in the second edition.

Alvaro Gutierrez  Feb 24, 2010 
Printed
Page 141
1st paragraph

R2 advertises the router to R1 via OSPF should be R2 advertises the route to R1 via OSPF

Note from the Author or Editor:
Thanks - this is fixed in the second edition

Anonymous   
Printed
Page 141
Last Line

In the output for the show ip route for R3, the advertised external route to network 10.10.10.0/24 should be via 20.20.20.1 rather than 20.20.20.2 as network 10.10.10.0/24 was redistibuted into EIGRP by router R1, not router R2

Note from the Author or Editor:
Thanks - this is fixed in the second edition

Anonymous  Dec 04, 2009 
Printed
Page 157
Router A config at bottom of page

The ethernet interface configured should be ethernet 0/0 not 0/1 to match the diagram and also to match the statement over the page where ethernet 0/0 rather than ethernet 0/1 is made passive. On page 157 the router D config should also probably refer to ethernet0/0 rather than fastethernet0/0 to match the diagram.

Note from the Author or Editor:
Good catch. Thanks - this is fixed in the second edition.

Anonymous  Dec 05, 2009 
Printed
Page 160
Config after second paragraph

The new config shown appears to be the eigrp config for router D not router A as stated. Also this config should not have network 10.200.200.0 in it as the whole point was to take the local loopback interface out of eigrp.

Note from the Author or Editor:
Resolved in the 2nd edition - thanks!

Anonymous  Dec 05, 2009 
Printed
Page 174
half-way through "Building a Route Map"

Current software does not permit the "AND" syntax for matches of the same type: route-map GAD permit 10 match ip address 101 match ip address 102 route-map GAD deny 20 Will be automatically converted to: route-map GAD permit 10 match ip address 101 102 route-map GAD deny 20

Note from the Author or Editor:
Hey it worked on the code I was using when I wrote the first edition! :) This section has been updated to reflect the behavior of more modern code.

Anonymous   
Printed
Page 177
Bottom

In this example of policy-based routing, the route maps shown will force traffic to take the same route as the routing protocol. The route maps, as written, are: route-map Company-1 permit 10 match ip address 101 set interface Serial0/0.109 route-map Company-2 permit 10 match ip address 102 set interface Serial0/0.209 When applied as written in the text, the Company-1 route map will take traffic sourced from Company-2 users that's destined for Company-1 servers and send it out interface Serial0/0.109. The routing protocol will choose this same path without the policy routing and this path is against the rational given for the example. The "set" commands in the route maps should be switched to obtain the correct functionality: route-map Company-1 permit 10 match ip address 101 set interface Serial0/0.209 route-map Company-2 permit 10 match ip address 102 set interface Serial0/0.109

Note from the Author or Editor:
This is fixed in the second edition

Jeffrey Sprankle  Sep 14, 2009 
Printed
Page 177
Middle and bottom of page

The route map pseudocode (in the middle of the page) and the route map configuration (at the bottom) is incorrect. The destination network in the pseudocode is reversed for the two statements. The destination interface in the configuration is reversed: "If the source network is 10.109.0.0/24 and the destination is 10.101.0.0/24 Then send the packet out interface S0/0.109" Should be: If the source network is 10.109.0.0/24 and the destination is 10.201.0.0/24 Then send the packet out interface S0/0.109 "If the source network is 10.209.0.0/24 and the destination is 10.201.0.0/24 Then send the packet out interface S0/0.209" Should be: If the source network is 10.209.0.0/24 and the destination is 10.101.0.0/24 Then send the packet out interface S0/0.209 "route-map Company-1 permit 10 match ip address 101 set interface Serial0/0.109" Last line should be: set interface Serial0/0.209 "route-map Company-2 permit 10 match ip address 102 set interface Serial0/0.209" Last line should be: set interface Serial0/0.109

Note from the Author or Editor:
This is fixed in the 2nd edition

Cory McCarthy  Jan 21, 2010 
Printed
Page 178
2nd paragraph

"...To accomplish this, we applied the Company-2 route map to the Company-1 Ethernet interface, and vice versa. This was done on the Branch-9 router: Interface FastEthernet0/0 description <[ Company-1 Users ]> ip address 10.109.0.1 255.255.255.0 ip policy route-map Company-2 half-duplex Interface FastEthernet0/1 description <[ Company-2 Users ]> ip address 10.209.0.1 255.255.255.0 ip policy route-map Company-1 half-duplex " The route maps (defined on page 177) are: access-list 101 permit ip any 10.101.0.0 0.0.0.255 access-list 101 remark <[ Company-1 Network ]> ! access-list 102 permit ip any 10.201.0.0 0.0.0.255 access-list 102 remark <[ Company-2 Network ]> route-map Company-1 permit 10 match ip address 101 set interface Serial0/0.109 route-map Company-2 permit 10 match ip address 102 set interface Serial0/0.209 The route maps appear to route Company-1's traffic over Company-2's link and vice versa. This violates the requirment stated on page 176, 3rd paragraph, that "...each company insisted that its employees should only use the frame-relay link that that company had purchased." Assuming that the interface configuration is left as stated above, the route maps should be changed to route Company-1's employee traffic destined to Comapny-2's servers over Company-1's frame-relay link and vice versa. The route-maps should be configured as follows: route-map Company-1 permit 10 match ip address 101 set interface Serial0/0.209 <-- output interface changed route-map Company-2 permit 10 match ip address 102 set interface Serial0/0.109 <-- output interface changed

Note from the Author or Editor:
This is fixed in the second edition

Anonymous   
Printed
Page 210
1st paragrah

In the portion that explains the difference between module layouts between the 6506, 6509 and 6513, it incorrectly states that the 6513 module layout is the same as the 6506/6509. When in actuality, the sup720's in a 6513 should be in slots 7-8, not 5-6 like in the 6506/6509: See 'Slot Requirements' on: http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps708/product_data_sheet09186a0080159856.html

Note from the Author or Editor:
Thanks. This has been resolved in recent printings and is also fixed in the upcoming second edition.

Anonymous   
Printed
Page 210
1st paragrah

In the portion that explains the difference between module layouts between the 6506, 6509 and 6513, it incorrectly states that the 6513 module layout is the same as the 6506/6509. When in actuality, the sup720's in a 6513 should be in slots 7-8, not 5-6 like in the 6506/6509: See 'Slot Requirements' on: http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps708/product_data_sheet09186a0080159856.html

Note from the Author or Editor:
Last paragraph before new header. Change "are allocated the same way, but with the addition of slots 10-13, which" to "are allocated similarly, though Sup-720s must reside in slots 7 and 8 instead of 5 and 6. The additional slots (10-13) "

Anonymous  Jul 15, 2008  May 01, 2009
Printed
Page 216
4th paragraph (last)

Second sentence of last paragraph reads "The fabric-only module in slot 1 has two 20 Gbps channels to the fiber bus", should this read "fabric bus" ?

Note from the Author or Editor:
Good catch - thanks. This has been resolved in the 2nd edition.

Anonymous   
Printed
Page 218
2nd paragraph

Example of connecting to an FWSM in slot 8: Switch-IOS# session slot 8 proc 1 The default escape characteris Ctrl-^, then x. You can also type 'exit' at the remote prompt to end the session Trying 127.0.0.71 ... Open That last line should read: Trying 127.0.0.81 ... Open

Note from the Author or Editor:
Thanks - this is fixes in the 2nd edition.

Anonymous   
Printed
Page 218
2nd paragraph

Example of connecting to an FWSM in slot 8: Switch-IOS# session slot 8 proc 1 The default escape characteris Ctrl-^, then x. You can also type 'exit' at the remote prompt to end the session Trying 127.0.0.71 ... Open That last line should read: Trying 127.0.0.81 ... Open

Note from the Author or Editor:
First block of code - forth line in the block. Replace "Trying 127.0.0.71 ... Open" with "Trying 127.0.0.81 ... Open"

Anonymous  Jul 30, 2008  May 01, 2009
Printed
Page 223
Last paragraph

Author mentions, regarding the show port command, that "IOS has nothing that directly compares to this command." Actually, the IOS command "show interface status" will show the same output. This command may have shown up after print of book.

Note from the Author or Editor:
Thank you - this is resolved in the second edition.

Adrian Smith  Feb 16, 2009 
Printed
Page 223
3rd section: "Another advantage of CatOS ..."

The author states there is no corresponding command in IOS to the CatoS "show port" command. This isn't necessarily true. In IOS running on a Catalyst 6500 (2960,3550,3560,3750,4500) you can issue the command "show interface status". The output looks just like the CatOS output: Cat6500-sup720>show interface status Port Name Status Vlan Duplex Speed Type Gi1/1 Switch1 connected trunk full 1000 1000BaseSX Gi1/2 Switch2 connected trunk full 1000 1000BaseSX Gi1/3 Switch3 connected trunk full 1000 1000BaseSX . . . Gi8/7 Server1 connected 201 a-full a-100 10/100/1000BaseT Gi8/8 Server2 connected 205 a-full a-1000 10/100/1000BaseT Gi8/9 Server3 connected 210 a-full a-100 10/100/1000BaseT AUTHOR's RESPONSE: "show interface status" is a fantastic command that I learned when readers emailed me regarding this error. I wish I had known about this command years ago! This proves again that a) writing in absolutes is rarely a good idea and b) I always have more to learn.

Anonymous   
Printed
Page 316
United Kingdom

For sub-interface Serial0/0.103 on router A, the frame-relay interface-dlci command should be for ip address 192.168.2.2, not 192.168.2.3

Note from the Author or Editor:
Thanks - this is fixed in the second edition

Anonymous  Dec 12, 2009 
Printed
Page 335
1st paragraph

The first step in restricting host A's communications is to create the necessary ACL. You must allow access to the default gateway, then deny access to other hosts in the network, and, finally, permit access to the rest of the world: Last line in the access-list should be: access-list 101 permit ip any any

Note from the Author or Editor:
This entire section has been revamped for the second edition.

Anonymous   
Printed
Page 335
1st paragraph

The first step in restricting host A's communications is to create the necessary ACL. You must allow access to the default gateway, then deny access to other hosts in the network, and, finally, permit access to the rest of the world: Last line in the access-list should be: access-list 101 permit ip any any

Note from the Author or Editor:
third line of code after first full paragraph. Replace "access-list 101 deny ip any any" with "access-list 101 permit ip any any"

Anonymous  Aug 05, 2008  May 01, 2009
Printed
Page 418
Beneath Figure 29-2

The author talks about a T1 link at 1.5Mbps, then below he says "A T1 can handle 1,500,000 packets per second." This is 2-3 orders of magnitude in error!

Note from the Author or Editor:
Nice catch. This is resolved in the second edition.

Anonymous   
Printed
Page 438-439
Interface definition under Service Policies

The policy map name applied to the interface is WAN-Edge, not WAN-Link which is the name used in defining the policy-map.

Note from the Author or Editor:
Nice catch. This is resolved in the second edition.

Anonymous   
Printed
Page 438-439
Interface definition under Service Policies

The policy map name applied to the interface is WAN-Edge, not WAN-Link which is the name used in defining the policy-map.

Note from the Author or Editor:
Second line of code under heading "Service Policies" Change "WAN-Edge" to "WAN-Link"

Anonymous  Jun 17, 2008  May 01, 2009
Printed
Page 442
First paragraph

"The link is saturated, but only in one direction: while txload is 249/255, rxload is only 42/255." I think txload and rxload have to be interchanged to reflect the console output on page 441 (line 7). Where txload is 42/255 and rxload is 249/255.

Note from the Author or Editor:
Thanks - this has been resolved in the 2nd edition.

Anonymous   
Printed
Page 442
First paragraph

"The link is saturated, but only in one direction: while txload is 249/255, rxload is only 42/255." I think txload and rxload have to be interchanged to reflect the console output on page 441 (line 7). Where txload is 42/255 and rxload is 249/255.

Note from the Author or Editor:
page 442, first sentence. Change "while txload is 249/255, rxload is only 42/255." to "while rxload is 249/255, txload is only 42/255."

Anonymous  Jul 22, 2008  May 01, 2009
Printed
Page 464
the paragraph just after the first tip, 4th line

ERRATA: ... you'll need if you want to allow for growth: 340 + 51 = 411, and 411 / 48 = 8.56. This means you'll need... CORRECTION: 340 + 51 = 391. Anyway, the following figures in the paragraph are still correct because 391 / 48 = 8.15, so you still need nine modules. SUGGESTION: To include a 15% percent growth on a figure of 340 interfaces, it is simpler to just calculate 340 * 1.15 = 391, instead of doing two operations: 340 * 0.15 = 51; 340 + 51 = 391.

Note from the Author or Editor:
Nice catch, and an elegant solution. This has been implemented in the 2nd edition. Thanks.

Anonymous   
Printed
Page 485
2nd paragraph

The ranges 172.0.0.0-172.15.255.255 and 172.32.0.0-172.255.255.255 are not composed of private addresses... *not* The ranges 172.0.0.0-172.31.255.255...

Note from the Author or Editor:
Fixed in recent printings as well as the second edition. Thanks!

Anonymous   
Printed
Page 485
2nd paragraph

This looks like a typo in the details of the 172.16/12 private prefix range, the passage states "... private range is 172.16.0.0 - 172.31.255.255. The ranges 172.0.0.0-172.31.255.255 and 173.32.0.0-172.255.255.255 are not composed of private addresses." 172.0.0.0 - 172.31.255.255 would cover the private range in 172.16/12 (16.0 - 31.255.255) the passage should read: ... private range is 172.16.0.0 - 172.31.255.255. The ranges 172.0.0.0-172.15.255.255 and 173.32.0.0-172.255.255.255 are not composed of private addresses.

Note from the Author or Editor:
Correct - this is fixed in both recent printings and the second edition. Thanks!

Anonymous   
Printed
Page 485
2nd para

"... The ranges 172.0.0.0-172.31.255.255 and ..." should be "... The ranges 172.0.0.0-172.15.255.255 and ..." (i.e. the second octet in the end of the range should be 15, not 31).

Note from the Author or Editor:
Page 485 2nd paragraph, fifth sentence. Replace "The ranges 172.0.0.0-172.31.255.255" with "The ranges 172.0.0.0-172.15.255.255"

Anonymous  Sep 09, 2008  May 01, 2009
PDF
Page 488
1st dog-paw comment

-------------------- Some Nexus switches support Virtual Device Contexts (VDCs), which are similar in principle to the contexts we’re dealing with here. Just to confuse us all, Cisco decided that the command to change between ASA contexts is switchto, while the command to change between Nexus VDCs is changeto. If you’re working with me in a data center that has both, count on lots of profanity while I continuously use the wrong command on both platforms. ---------------------- I believe switchto and changeto should be the other way around :-)

Note from the Author or Editor:
Reader is correct. Replace sentence beginning with "Just to..." with: "Just to confuse us all, Cisco decided that the command to change between ASA contexts is changeto, while the command to change between Nexus VDCs is switchto." Changeto and switchto should be in code format.

Anonymous  Dec 01, 2011 
Printed
Page 490
3rd paragraph

"Figure 34-4 shows how a single route statment can reference eight Class C neworks." The diagram seems to show 16 networks, not eight.

Note from the Author or Editor:
Nice catch. This is resolved in the second edition.

Anonymous   
Printed
Page 491
3rd paragraph

"Those entries are taking up 18.4 MB of mory in the router" Shouldn't it be 17.5 megabytes? http://www.google.com/search?hl=en&q=18417047+bytes+in+MB

Note from the Author or Editor:
Reworded to remove the reference to megabytes.

Anonymous   
Printed
Page 495
1st paragraph

"Because we cannot use the last subnet due to the rules of networking, a lot of space is wasted." That statement is at best a historical curiosity and is inappropriate in a practical discussion of using VLSM in 2007. To quote from RFC 1878: "For the sake of completeness within this memo, tables 2-1 and 2-2 illistrate some options for subnet/host partions within selected block sizes using calculations which exclude all-zeros and all-ones subnets [2]. Many vendors only support subnetting based upon this premise. This practice is obsolete! Modern software will be able to utilize all definable networks." and that was in Dec of 1995. This was an effect of the requirements in RFC 1812 from earlier that year.

Note from the Author or Editor:
Resolved in the 2nd edition.

Anonymous   
Printed
Page 509
Tip at bottom

"Older versions of Windows do not support NTP" Would be nice to be more specific. My understanding is XP and 2003 use NTP. 2000 and presumably lower use SNTP.

Note from the Author or Editor:
Updated this section for the 2nd edition.

Anonymous   
PDF
Page 514
7th paragraph

To cancel an impeding scheduled reload, execute the reload cancel command: the word "impeding" should be "impending"

Note from the Author or Editor:
Thanks! This is fixed in the second edition.

sunjian  Sep 08, 2010 
PDF
Page 534
6th paragraph

"If your idea if valid, you will have plenty of time to expound on the details later." should it be read : "If your idea is valid, you will have plenty of time to expound on the details later."?

Note from the Author or Editor:
Thanks - this is fixed in the second edition

sunjian  Sep 16, 2010