Cloud Native Data Center Networking

Errata for Cloud Native Data Center Networking

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
Printed, PDF, ePub, Mobi, Safari Books Online, Other Digital Version
Page 35
First paragraph of

"For example, with a 256-port chassis spine switch and a 64-port leaf switch, you can build 256 × 32 = 8,192 servers instead of the 2,048 switches available with just 64-port switches.“ I guess the "switches" in "2048 switches" is a typo, it should be servers.

Dinesh Dutt
 
Jan 08, 2020 
Printed
Page 77
Figure 4-6 captions

The captions for (a) and (b) of figure 4-6 are different. One reads "Packet Send Model" and the other reads "Packet Receive Flow". Change the second to be "Packet Receive Model".

Note from the Author or Editor:
Fix as per the comment.

Siddhartha Sen  Dec 10, 2019  Jan 03, 2020
Printed, PDF, ePub, Mobi, Safari Books Online, Other Digital Version
Page 97
First paragraph of

"R1 must find its path to R3 (via R4), R2 now has multipathing to R4 (R1-R3-R6-R4 and R5-R7-R6-R4), and so on. " It should be "R1 must find its path to R4 (via R3)"

Dinesh Dutt
 
Jan 08, 2020 
Printed
Page 103
Last paragraph on page

The sentence in the last paragraph that reads: "To illustrate this, in Figure 5-7, S11 updates the other connected spines about its lost connectivity to S11" states S11 twice. The first use of S11 should be replaced by L11 i.e. the sentence should read: "To illustrate this, in Figure 5-7, L11 updates the other connected spines about its lost connectivity to S11.

Note from the Author or Editor:
I'll submit the fix as per the comment.

Siddhartha Sen  Dec 10, 2019  Jan 03, 2020
Printed, PDF, ePub, Mobi, Safari Books Online, Other Digital Version
Page 103
Paragraph above Figure 5-8

I guess the "SSo" is a typo in this sentence "As an example, traffic from SS2 cannot reach SSo as indicated by the crossed out link.", it should be" As an example, traffic from SS2 cannot reach SSp as indicated by the crossed out link.".

Zhao Huabing  Jan 10, 2020 
Printed, PDF, ePub, Mobi, Safari Books Online, Other Digital Version
Page 104
1st sentence of 2nd paragraph

L11 withdraws reachability to the loopback IP address of S11 because reachability to the other leaves is still possible via the other leaves. I think "L11 withdraws reachability to the loopback IP address of S11" just because the link between L11 and S11 went down.

Dinesh Dutt
 
Jan 10, 2020 
Printed, PDF, ePub, Mobi, Safari Books Online, Other Digital Version
Page 105
2nd line first paragraph

"One possible benefit of link state’s additional computation and message exchange is that any in-flight packets to L11 can find their way to T11 eventually." T11 should be L11

Zhao Huabing  Jan 16, 2020 
Printed, PDF, Safari Books Online
Page 155
Figure 7-6

In figure 7-6, container2 in server1 should have the IP address 172.17.0.1.

Note from the Author or Editor:
The submitter's comment is correct. We need to fix it as per the comment.

Siddhartha Sen  Dec 10, 2019  Jan 03, 2020