Errata


Print Print Icon

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 "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



Version Location Description Submitted By 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 
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  May 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  May 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 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 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 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 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 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 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 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 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 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 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  Nov 2008
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  May 2009
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  May 2009
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  May 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 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  May 2009
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  May 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:
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  May 2009
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  May 2009


"Network Warrior is the best network administration book I've ever read...Gary Donahue has written a wonderful book that I highly recommend for anyone who administers, supports, or interacts with networks. Network Warrior may be the best book I will read in 2007. "
--Richard Bejtlich, Amazon.com