Errata

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.

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"

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

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

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

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.

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.

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.

"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

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

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.

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!

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

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

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.

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

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.

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.

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"

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.

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.

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.

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"

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.

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.

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"

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

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

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.

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

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

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