Errata

Server Load Balancing

Errata for Server Load Balancing

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.

The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.

Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted by Date submitted
Printed Page 15
Table 2-1, last row last column

"nything" should be "anything"

Anonymous   
Printed Page 20
2nd paragraph

VRRP uses multicast address 244.0.0.18 (as defined in RFC2338)instead of 225.0.0.2.

Anonymous   
Printed Page 20
1st Paragraph

In VRRP, only the active router broadcasts notifications.
A backup will listen for these notifications and become
active if it no longer hears them.

Anonymous   
Printed Page 21
Service Checking (last paragraph)

The third sentence begins:

It can be ... a ping check, a port check, (to see if ...),
^
The comma before the parenthetical comment doesn't belong.

Additionally, the sentence ends:

or even a content check, in which the web server is queried ...

Because of the comma within that section, the other commas in the sentence probably
need to become semicolons.

Anonymous   
Printed Page 22
2nd paragraph, Provider Infrastructure

The first sentence refers to connectivity to "the Internet, Extranet, or Intranet."
The Internet is capitalized because it is _the_ Internet, the biggest internet
(network of networks) of them all; but I'm aware of no grammatical or conventional
reason to capitalize "extranet" and "intranet."

Anonymous   
Printed Page 24
Figure 3-1

The arrows to the rightmost two Real Servers are drawn in a heavier line weight than
the other arrows in that and other related figures. This emboldening doesn't appear
to be for any specific purpose.


Anonymous   
Printed Page 27
1st paragraph

The paragraph begins:

As introduced in Chapter 2, Direct Server Return ...

But I could find no reference to DSR anywhere in chapter 2. (I did spend a while
rereading chapter 2 to see whether I'd missed DSR's introduction.)

Anonymous   
Printed Page 28
last full paragraph

Discussion about traffic ratio, uses terms "in" and "out" without
clarification from whose perspecitive those are (server's? client's?).
Discussion of ratios on page 66 (first full paragraph) is much cleaner and easier to
understand (and I might mention, the use of "in/out" is from the server's perspective
instead of the clients).

Anonymous   
Printed Page 28
1st paragraph

Final sentence of paragraph states: ".....the destination address is already that of the VIP, thus......."

to my knowledge this should be: "".....the source address is already that of the VIP, thus......."

Anonymous   
Printed Page 28
2nd-last paragraph

Another reader has mentioned that the use of "inbound" and "outbound" in this
paragraph needs clarification. Not only that, but the terms are used in the first
sentence in opposition to their use in the last sentence (and in opposition to common
sense :-) ). The first sentence should probably read:

Web traffic has a ratio of about 1:8, which is one packet in for every eight packets
out.

or

Web traffic has a ratio of about 8:1, which is one packet out for every one packet
in.

Anonymous   
Printed Page 34
4th paragraph (3rd of The 100 Mbps Barrier)

The paragraph again claims DSR was introduced in Chapter 2, which it doesn't appear
to have been (at least by the time the book went to print).

Additionally, the second sentence has a misplaced modifier:

Since DSR does not involve the outbound traffic passing the SLB device, which is
typically the majority of a site's traffic, ...

The SLB device isn't traffic. Perhaps:

Since DSR does not involve the outbound traffic (typically the majority of a site's
traffic) passing the SLB device, ...

Anonymous   
Printed Page 35
middle paragraph (HTTP)

The fourth sentence is missing the word "able," inserted here:

The HTTP 1.1 standard makes things a little more efficient by making one connection
_able_ to retrieve several objects during a given session.

Anonymous   
Printed Page 44
Top

The terms "Bridge-path" and "route-path" are never defined.
This page seems to be the first place where they are used.

Anonymous   
Printed Page 44
Section "Return Traffic Management: Bridging-Path versus Routing-Path versus DSR"

Section entitled:
"Return Traffic Management: Bridging-Path versus Routing-Path versus DSR"
only deals with bridging-path and routing-path. No mention of DSR is made.

Anonymous   
Printed Page 51
address list, middle of page

The middle range should be 172.16.0.0-172._31_.255.255.

Anonymous   
Printed Page 52
second paragraph under "Web Servers" last sentence

"default toute for the web server" should be:
"default route for the web server"

Anonymous   
Printed Page 54
last paragraph second sentence

"have access to the outbound to the network" should be:
"have access to the outbound network"

Anonymous   
Printed Page 56
Figure 6-2

The switches sw-1 and sw-2 are labelled as "Layer 3 switch" when they ought to be
labelled as "Layer 2 switch".

Anonymous   
Printed Page 59
Section: Redundancy

2nd sentence: "Whe using route-path, a Layer 2 redundancy is required." However on
Figure 6-3. Flat-based, bridge-path, two-armed SLB, a "Redundacy (Layer 2)" is shown.

In another part of the book, page 56, 2nd paragraph, last sentance, it is stated that
more than one Layer 2 path in a route-path "would create a nasty bridging loop".

I am new to networking, but these is confusing for me.

Anonymous   
Printed Page 63,64
Figure 7-1 and 7-2

Ip addresses of the webservers in the NAT based scenario's should be in the 10.0.0.0/24 netblock (as described in chapter 5, cast o
f characters [pg 53]), i.e 10.0.0.100 for ws-1 instead of 192.168.0.100.

Anonymous   
Printed Page 65
Figure 7-3

Within the private network part it should state "Layer 3 router Private Network Interface 10.0.0.1" instead of "Layer 3 router Publ
ic Network Interface 10.0.0.1".

Anonymous   
Printed Page 66
3rd paragraph

"To understand how flat-based SLB works,....." should be "To understand how NAT-based SLB works,...."

Anonymous   
Printed Page 67
Table 7-3

Although the shared address for the public network (192.168.0.10) doesn't show in figures 7-1, 7-2 and 7-3 and the 4th paragraph on
page 67 explicitly states there is no default route on the public VLAN it is present in table 7-3 (3rd row), but shouldn't necessa
ry be in that table.

Anonymous   
Printed Page 114
2nd paragraph, redundancy protocol link

IP address within config example on lb-1 should be 172.16.0.1/24 not 172.16.0.11/24

and missing "redundancy-protocol" statement within example.

Anonymous   
Printed Page 116
lb-2(config)# circuit VLAN 3

VLAN 3 is not configured yet on lb-2 when you follow the examples.

include:

lb-2(config)# int e12
lb-2(config-if[ethernet12])# bridge vlan 3
lb-2(config-if[ethernet12])# circuit VLAN 3 etc.

Anonymous   
Printed Page 162,163
Figure C-7 and C-8

Ip addresses of the webservers in the NAT based scenario's should be in the 10.0.0.0/24 netblock (as described in chapter 5, cast o
f characters [pg 53]), i.e 10.0.0.100 for ws-1 instead of 192.168.0.100.

Anonymous