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 |
Page 779
3rd paragraph |
"wolrd" -> "world"
Note from the Author or Editor:
hello-wolrd.xslt should be hello-world.xslt. This appears to be a typo. |
perw07 |
Sep 01, 2010 |
|
| Printed |
Page 775
2nd line |
"zone untrust" -> "zone test-zone"
Note from the Author or Editor:
set interfaces ge-0/0/3 unit 0 apply-macro zone untrust
Should be
set interfaces ge-0/0/3 unit 0 apply-macro zone test-zone |
perw07 |
Sep 01, 2010 |
|
| Printed |
Page 769
2nd paragraph from end of page |
The text reads:
display commit
but it should be:
display commit-scripts
Note from the Author or Editor:
And a useful tool to see the candidate configuration after all commit scripts have been applied is the | display commit command:
should be
And a useful tool to see the candidate configuration after all commit scripts have been applied is the | display commit-scripts command: |
perw07 |
Sep 01, 2010 |
|
| Printed |
Page 767
Last paragraph |
The text refers to Figure 13-3, but it should refer to Figure 13-4
Note from the Author or Editor:
In fact, this description is incomplete. An intermediate step is performed after the can- didate configuration is loaded but before the commit check is performed, as shown in Figure 13-4.
should be
In fact, this description is incomplete. An intermediate step is performed after the can- didate configuration is loaded but before the commit check is performed, as shown in Figure 13-3. |
perw07 |
Sep 01, 2010 |
|
| Printed |
Page 756
2nd paragraph from end of page |
Sentence ending in:
"either operational or command mode."
should read:
"either operational or configuration mode."
Note from the Author or Editor:
It is in this context that one should try to understand the two very different modes in which the Junos UI operates, either operational or command mode.
should be
It is in this context that one should try to understand the two very different modes in which the Junos UI operates, either operational or configuration mode. |
perw07 |
Aug 31, 2010 |
|
| PDF |
Page 627
2nd paragraph from end of page |
Three usages of network 10.0.0.0/0 or 10/0 instead of the intended 10.0.0.0/8 or 10/8
Note from the Author or Editor:
You begin building a route toward the 10.0.0.0/0 network (which you smartly abbre-
viate 10/0, a well-understood abbreviation for the Junos CLI) and examine the CLI help:
[edit routing-options static] jamesq@SRX5800-1# set route 10/0 ?
should be
You begin building a route toward the 10.0.0.0/8 network (which you smartly abbre-
viate 10/0, a well-understood abbreviation for the Junos CLI) and examine the CLI help:
[edit routing-options static] jamesq@SRX5800-1# set route 10/8 ? |
perw07 |
Aug 29, 2010 |
|
| PDF |
Page 573
middle of page |
The line that reads:
root@SRX210-A# set chassis cluster reth-count 2
is in the wrong conext. That is the right command in the "root" context, but in the current context it should read:
root@SRX210-A# set reth-count 2
Note from the Author or Editor:
{primary:node0}[edit chassis cluster] root@SRX210-A# set chassis cluster reth-count 2
should be
{primary:node0}[edit chassis cluster] root@SRX210-A#set reth-count 2 |
perw07 |
Aug 23, 2010 |
|
| PDF |
Page 551
last paragraph |
The text refers to picture 10-9 and describes M120s. The picture, however, is showing M10is instead.
Note from the Author or Editor:
The two SRXs each have two interfaces connected into two different M120 routers
should be
The two SRXs each have two interfaces connected into two different M10i routers |
perw07 |
Aug 23, 2010 |
|