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

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.

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

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

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

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

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.

The graph depicts Packets (or Bytes) as a function of Time. Between T1 and T2 the function actually goes back in time. This certainly would be a unique (and lucrative) feature.

This is another graph with a funtion of time actually going back in time. Same as errata with page 235.

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

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!

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

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

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.

"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