Errata
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 |
---|---|---|---|---|
Page xvi 4th para |
I would like to especially thank Glenn Bradley with his help |
Chris Pepper | Feb 27, 2013 | |
Page xviii p1 |
I?ve simply changed the point in which the line wraps |
Chris Pepper | Feb 27, 2013 | |
Page 1 p4 |
state-of-the art |
Chris Pepper | Feb 27, 2013 | |
Page 5 p4 |
VLANs spanning across physical locations, |
Chris Pepper | Feb 27, 2013 | |
Printed | Page 6 4th paragraph |
"NAS" is used where "NFS" should be: |
Anonymous | Jan 20, 2015 |
Page 7 p3, p4 |
Sometimes you italicize 'bash', but sometimes it's plaintext. I suggest monospace (like 'sudo', 'ps', etc.). |
Chris Pepper | Feb 27, 2013 | |
Page 9 p1 |
Zero Touch Provisioning (ZTP) allows your Arista switch to not only load its configuration from the network, but also from its operating system. |
Chris Pepper | Feb 27, 2013 | |
Printed | Page 13 last paragraph |
Last paragraph describes a situation where e3 sends a message to e1. On the next page the example continues, but it is talking about e3 sending to e2 (not e1). |
Daniel Bethke | Jan 16, 2013 |
Printed | Page 15 figure 2-4 |
In the example given in the text, the relevant buffers would be output buffers. The figure could be improved by moving the buffers to the output side. |
Anonymous | Jan 20, 2015 |
Printed | Page 21 Top |
Hello, |
Jean-Edouard Babin | Nov 16, 2012 |
21 1st |
I set up my lab with the following IP addresses: |
saar | May 08, 2013 | |
Page 21 1st paragraph |
Fifty ms is 1/20th of a second, or 0.20 seconds. |
Nathan Wolfe | Jan 28, 2014 | |
Page 23 p3, p4 |
used to described chips, |
Chris Pepper | Feb 27, 2013 | |
Printed | Page 24 3rd bullet list |
comma used where there should be none: |
Anonymous | Jan 20, 2015 |
Printed | Page 33 middle |
Hi, |
Jean-Edouard Babin | Nov 19, 2012 |
Printed | Page 34 figure 4-5 caption |
missing 'r' in 'ports' |
Anonymous | Jan 20, 2015 |
Printed | Page 38 last paragraph |
The Arista 7500 chassis 48-port 10 Gbps non-blocking modules has one ASIC per... |
Anonymous | Jan 20, 2015 |
Printed | Page 40 "Airflow" section |
The description of the meaning of the red and blue handles is not quite correct. it was correct at the time of publishing simply because at that point all of our products had their fans and PSUs on the back of the unit |
Robert F Merrill | Mar 09, 2014 |
Page 42 p3, p4 |
Both the QSFP+ and the SFP+ support twinax cables |
Chris Pepper | Feb 27, 2013 | |
Page 45 p2 |
a non-blocking 480 Gbps backplane, which ensures a non- blocking backplane |
Chris Pepper | Feb 27, 2013 | |
Page 79-81 All |
The first three pages of the LLDP chapter are incorrect in regards to CDP. The book says that the Arista switch will listen to and understand the CDP advertisements and then put them in its LLDP table; however, this is not the case. |
Kyle Birkeland | Apr 03, 2013 | |
Page 98 End of Second Paragraph |
Arista#boot system flash:/EOS-4.8.1.swi |
Hiten Thakkar | Oct 07, 2014 | |
Printed | Page 102 last line of modified code |
the last line of new code reads: |
Anonymous | Jan 20, 2015 |
Page 104 code example at bottom of page |
# Version is same as original - proced with copy |
Omar Ali | Apr 15, 2013 | |
Page 108 p1 |
the available bandwidth too and from switch C |
Chris Pepper | Feb 27, 2013 | |
Printed | Page 108 2nd paragraph |
"dot1Q" is used to refer to link aggregation), but 802.1Q standardizes VLAN tagging. Link aggregation is standardized in 802.1AX (formerly in 802.3ad, thus link aggregation and LACP are usually known as 802.3ad). |
Erik Auerswald | Jul 10, 2015 |
Printed | Page 110 3rd paragraph |
incorrect: "Here's what would happen on a Cisco switch:" |
Erik Auerswald | Jul 10, 2015 |
Printed | Page 113 1st paragraph |
"dot1Q" is used to refer to link aggregation), but 802.1Q standardizes VLAN tagging. Link aggregation is standardized in 802.1AX (formerly in 802.3ad, thus link aggregation and LACP are usually known as 802.3ad). |
Erik Auerswald | Jul 10, 2015 |
Printed | Page 123 numbered list |
The first list item has a line break in the word "detail", printing it as two words over two lines ("de\ntail"). |
Erik Auerswald | Jul 10, 2015 |
Printed | Page 127 2nd paragraph |
not good: "[...] that Cisco 3750s only support STP up to 256 VLANs." |
Erik Auerswald | Jul 10, 2015 |
Printed | Page 133 1st text paragraph |
The description of MST behaviours very clearly shows the author's Cisco background. I'd suggest rewriting the whole paragraph. |
Erik Auerswald | Jul 10, 2015 |
Printed | Page 136 2nd to last paragraph |
Only the plus (+) variants of (R)PVST use multicast MAC destination addresses. This often overlooked change, together with untagged CST BPDUs, created some compatibility between Cisco's proprietary default STP and other vendors' standards based default STPs. Thus the + should be added here explicitly. |
Erik Auerswald | Jul 10, 2015 |
Printed | Page 136 last paragraph |
wrong: "[...] Cisco enhanced the MST protocol [...]" |
Erik Auerswald | Jul 10, 2015 |
Printed | Page 137 3rd text paragraph |
wrong: "With MST, BPDUs are only ever sent over VLAN1 (by default), [...]" |
Erik Auerswald | Jul 10, 2015 |
Printed | Page 155 2nd paragraph |
VRRP is called an "open source protocol", while it is just an "open" standard. In fact, VRRP is patent-encumbered, which lead to the development of the open source, even free software, CARP protocol and implementations. |
Erik Auerswald | Jul 10, 2015 |
Printed | Page 169 figure 14-4 |
It would be better to attach the servers directly to SW1 resp. SW2, as in an STP enabled layer 2 network (which would connect all the servers in VLAN 99) usually the remote end of the link from Sw2 et10 would be blocked and thus not used at all. |
Erik Auerswald | Jul 10, 2015 |
Printed | Page 170 tech tip at top of page |
The ARP responses for the virtual IP from both of the switches are identical. The layer 2 network determines the path used by a frame from a server to reach one of the VARP enabled gateways. The first gateway reached by the frame will process it for layer 3 forwarding. Thus the peer link is never used to reach the "active" gateway with VARP, as both peers are active. This is an important difference compared to standard VRRP. |
Erik Auerswald | Jul 10, 2015 |
Printed | Page 170 2nd text paragraph |
Please delete "in routing, nor can it be used". |
Erik Auerswald | Jul 10, 2015 |
Printed | Page 170 last line of page |
The "rule for making up MAC addresses" is to set the second lowest bit in the first octet to 1. So you could change the Arista OUI used to "02:1c:73" to create a locally administered MAC address (02:1c:73:00:00:99). It would probably work to just use 02:00:00:00:00:99. |
Erik Auerswald | Jul 10, 2015 |
Printed | Page 173 1st text paragraph |
wrong: "[...] show ip virtual router [...]" |
Erik Auerswald | Jul 10, 2015 |
Page 175 p2 |
the way you?d expect them too. |
Chris Pepper | Feb 27, 2013 | |
Printed | Page 186 1st text paragrph (after the list starting the page) |
The text omits the crucial part of _unsupported_. |
Erik Auerswald | Jul 10, 2015 |
Printed | Page 194 2nd text paragraph |
VRRP is an IP based protocol with protocol number 112, but the text claims it is _not_ part of IP and would use protocol number 118. The author might have been confused by the IP multicast address used, which is 224.0.0.18. |
Erik Auerswald | Jul 10, 2015 |
Printed | Page 199,200 bottom of 199 start of 200 |
End of page 199 and start of 200. |
Craig Gleason | Nov 28, 2012 |
Printed | Page 199 definition list at bottom of page, 1st item |
The definition of "TPID" has a spurious "0v" in front of "0x8100", which should be deleted. |
Erik Auerswald | Jul 10, 2015 |
Page 211 p1 |
This can be altered with the 􏰣􏰅􏰑􏰓􏰕􏰂􏰓􏰄􏰥􏰍􏰙􏰚􏰁􏰘􏰚􏰑􏰄 􏰙􏰚􏰁􏰘􏰚􏰑􏰄 􏰅􏰐􏰚 tx-queue command. |
Chris Pepper | Feb 27, 2013 | |
Printed, | Page 258 1st Paragraph under "Configuring sFlow" |
The correct URL for sFlowTrend is http://www.inmon.com |
Harish Dommathamari | Jun 08, 2016 |
Page 263 2 |
VM Tracer can be given a range of VLANs with which it can add, |
Chris Pepper | Feb 27, 2013 | |
Page 266 1 |
The trunk between the switched (port-channel 20 on both sides) |
Chris Pepper | Feb 27, 2013 | |
Page 271 3 |
Luckily, we can limit the number of VLANs for which VM Tracer is allowed to change. |
Chris Pepper | Feb 27, 2013 | |
Page 276 1 |
but it get?s worse. |
Chris Pepper | Feb 27, 2013 | |
Printed | Page 284 last line on page |
Missing space in Linux command: |
Erik Auerswald | Jul 10, 2015 |
Page 287 Intro |
It would be worth mentioning in the introduction that 'tcpdump' and 'wireshark' use a standard file format and files are intercompatible, so you can capture data with 'tcpdump' on the switch and analyze it at leisure on a graphical workstation. |
Chris Pepper | Feb 27, 2013 | |
Printed | Page 291 1st text paragraph |
The text in this first paragraph uses "STP.capture" as file name, but all the examples below use "GAD.capture". The text should be changed to use "GAD.capture" as well. |
Erik Auerswald | Jul 10, 2015 |
Printed | Page 295 1st paragraph |
Mispelling of MLAG where it says MALG interface (VLAN 4094) |
Craig Gleason | Nov 29, 2012 |
Printed | Page 306-307 code block on 306 and dhcp config on 307 |
MAC address shown in code block on 306 does not match MAC address shown in dhcp options section on 307 |
Craig Gleason | Nov 29, 2012 |
Printed | Page 312 tech tip at top of page, 1st paragraph therein |
there is a spurious closing parenthesis after VMTracer that should be deleted: |
Erik Auerswald | Jul 10, 2015 |
Page 317 3 |
did not effect any |
Chris Pepper | Feb 27, 2013 | |
Printed | Page 359 2nd paragraph |
In 2nd paragraph, the commaned mentioned is the reboot now command. I believe the correct command (and one shown in figure 29-16) is actually reload now. |
Craig Gleason | Nov 30, 2012 |
Printed | Page 367 1st paragraph |
The load values are NOT given in percent, they are given in a fractional number representing the number of concurrently runnable processes. As such the description given is just wrong, the percentages show are totally misleading. |
Erik Auerswald | Jul 10, 2015 |
Page 380 3 |
other vendor?s switches. |
Chris Pepper | Feb 27, 2013 | |
Page 381 4 |
hardcoded 1,000 Gbps/full duplex |
Chris Pepper | Feb 27, 2013 | |
Printed | Page 383 Trunk groups section, paragraph 3 |
There is a mix of the trunk group name used through the Trunk groups example. Some times the trunk group name 'Servers' is referenced and other times the trunk group 'Leelu' is referenced. I believe all references to 'Leelu' should be replaced with 'Servers' on pages 383-386 |
Tom Leach | Sep 12, 2013 |
Printed | Page 383 5th normal text paragraph |
wrong: "We've already see it in use for the MLAG peer, [...]" |
Erik Auerswald | Jul 10, 2015 |
Printed | Page 383 2nd to last text paragraph |
wrong: "[...] apply the trunk group Servers [...]" |
Erik Auerswald | Jul 10, 2015 |