Errata

Network Programmability and Automation

Errata for Network Programmability and Automation

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 498
1st paragraph

Sentence begins, “The value of this short circuit decreases over time …”

I believe the authors meant, “The value of these certifications decrease over time …”

 Brannen Taylor  Aug 01, 2021 
Printed Page 176
Paragraph before second code sample

"A YANG leaf-list statement is represented in XML and JSON as a single element [...]". The code sample immediately following this shows two "stand-alone" elements. So the statement seems to only be true for JSON, not for XML. This is an interesting difference in data representation (conventions) between XML and JSON, I think.

 Simon Leinen  Apr 06, 2021 
PDF Page 50
4th paragraph

"You may also see these permissions listed as a string of characters, like rxwr-xr-x .
This breaks down to the read ( r ), write ( w ), and execute ( x ) permissions for each of
the three entities (user, group, and others). Here are the same examples as earlier, but
written in alternate format:
644 = rw-r--r--
755 = rwxr-xr-w
600 = rw-------
620 = rw--w----"


In first line above, rxw is wrong. It should be rwx.
same mistake is done in third last line where r-w is written but it should be r-x.

 MANOJ KUMAR  Feb 09, 2021 
PDF Page 50
3rd paragraph

"Similarly, if you wanted to allow users in the file’s group to
read the file but not write or execute it, you’d assign the value 2 to the group’s permis‐
sions."

In above line, you would assign a value of 4 to the group's permissions.

 MANOJ KUMAR  Feb 09, 2021 
Printed Page 52
4th paragraph (explaining string representations of permissions)

The section explains permissions of files and directories on linux systems.
The 2nd example reads:

755 = rwxr-xr-w

This is incorrect, it should either be

755 = rwxr-xr-x

or

756 = rwxr-xrw-

 Manuel Stausberg   Mar 04, 2020 
PDF Page chapter 1
Chapter 1. Network Industry Trends (https://learning.oreilly.com/library/view/network-programmability-and/9781491931240/ch01.html)

is there a misspelled word near the end of this sentence:

"Oftentimes these solutions offer integrations with the best-of-breed Layer 4–7 services companies as well, offering choice as to which technology could be deployed within network virtualzation platforms."

"virtualzation" should be "virtualization"

 viorel haiciu  Feb 21, 2020 
Printed Page 52
Paragraph 4, in the example 755

755=rwxr-xr-w
The correcto Is
755=rwx-rxr-x

 Emilio Oropeza Zurita  Dec 11, 2019 
Printed Page 414
first example, first line

missing --out option

Tom McCreary  Oct 11, 2019 
Printed Page 82
1st and 3rd paragraphs

The reference to the Figures 3.7 and 3.8 on page 82 is incorrect.

The command in the beginning of page 82 which is used to create a bridge corresponds to Figure 3.6 and not 3.7 as stated.
Similarly further down on the same page a single physical interface is added to the bridge, so the corresponding Figure should be 3.7 and not 3.8 as stated.

 Anonymous  Apr 08, 2019 
Printed Page 206
Page 206 3rd Paragraph, 2nd Sentence

I agree with what Andrew Mason states :

- Sentence reads "If you are using an HTTP-based API that always uses the same URL and does not allow you to access a specific resource by a URL change, the API is a RESTful HTTP-based API."

I believe this should read ...the API is a non-RESTful HTTP-based API.-

Furthermore to what he suggest on page 250 last paragraph. 2nd sentence you can read :

"...whreas a true RESTful API using http as transport has a different URL based on the resource in question..."

this contradicts what stated in the referenced page for the error.

 Giorgio Tosi  Jan 30, 2019 
Printed Page 206
3rd Paragraph, 2nd Sentence

Sentence reads "If you are using an HTTP-based API that always uses the same URL and does not allow you to access a specific resource by a URL change, the API is a RESTful HTTP-based API."

I believe this should read ...the API is a non-RESTful HTTP-based API.

Examples of this can be seen from page 235 where the Cisco NX-API is demonstrated.

 Andrew Mason  Dec 03, 2018 
PDF, ePub Page 62
Chapter 2 - Heading "Changing permissions"

In the sentence "Similarly, if you wanted to allow users in the file’s group to read the file but not write or execute it, you’d assign the
value 2 to the group’s permissions."

The value assigned for read should be 4 instead of 2.

 Syed Faraz Ali  Nov 19, 2018 
PDF, ePub Page 51
Chapter 2 - Heading "Debian, Ubuntu, and Other Derivatives"

The third paragraph states:

All Ubuntu codenames are cmposed of an adjective and an animal with the same first letter (Warty Warthog, Hoary Hedgehog, Breezy Badger, etc.).

Please correct the spelling "composed"

 Syed Faraz Ali  Nov 16, 2018 
Printed, PDF, ePub, Mobi, , Other Digital Version Page 91
Example for set

Example for set is wrong. It should be

set(facts) returns set(["vendor", "platform", "os"])

 Yoong Hor Meng  Sep 03, 2018 
Printed, PDF, ePub, Mobi, , Other Digital Version Page 91
Table 4-1

The example for tuple is wrong. The IP address should be quoted using single or double quotes.

 Hor Meng Yoong  Sep 03, 2018 
Printed, PDF, ePub, Mobi, , Other Digital Version Page 88
Output from running python interpreter

In section "Using the Python Interactive Interpreter", the example in page 89 uses print() syntax but the output from running python interpreter is 2.7.6 which does not support print() unless import future.

 Yoong hor meng  Sep 03, 2018 
Printed Page 143
code segment

The example code prints incorrect data as args[0] is the script name.

Text above the code segment correctly states this.

 Anonymous  Sep 02, 2018 
Printed Page 55
general note block

The general note regarding the shebang states that scripts starting with an exclamation mark only. I think it should be hash and exclamation mark: #!

The original sentence is even more missleading:

"the shebang is the first line in a text-based script and it starts with the characters !, followed by the path to the interpreter to the script."

This might lead to the understanding the shebang is made of the two characters "!,"

Kind regards,
Patrick Gerhartz

 Patrick Gerhartz  Apr 01, 2018