Errata

I would like to especially thank Glenn Bradley with his help
I would like to especially thank Glenn Bradley for his help

I?ve simply changed the point in which the line wraps
I?ve simply changed the point at which the line wraps

state-of-the art
state-of-the-art

VLANs spanning across physical locations,
VLANs spanning physical locations,

Sometimes you italicize 'bash', but sometimes it's plaintext. I suggest monospace (like 'sudo', 'ps', etc.).

Zero Touch Provisioning (ZTP) allows your Arista switch to not only load its configuration from the network, but also from its operating system.
Zero Touch Provisioning (ZTP) allows your Arista switch to not only load its configu?ration from the network, but also its operating system.

used to described chips,
used to describe chips,

comma used where there should be none:

bad: Easy to implement, newer ASICs
good: Easy to implement newer ASICs

Hi,

"sports 32 10 Gbps ports" should be "supports 32 10 Gbps ports"

Regards,

missing 'r' in 'ports'

wrong: ...dedicated pots highlighted
right: ...dedicated ports highlighted

The Arista 7500 chassis 48-port 10 Gbps non-blocking modules has one ASIC per...

You should write either "... modules have ..." or "... module has ...", but the combination of "modules" (plural) and "has" (singular) is incorrect.

Both the QSFP+ and the SFP+ support twinax cables
Both QSFP+ and SFP+ support twinax cables

a non-blocking 480 Gbps backplane, which ensures a non- blocking backplane

the last line of new code reads:

ptint ""

but it should read:

print ""

# Version is same as original - proced with copy
# Version is same as original - proceed with copy

the available bandwidth too and from switch C
the available bandwidth to and from switch C

The first list item has a line break in the word "detail", printing it as two words over two lines ("de\ntail").

not good: "[...] that Cisco 3750s only support STP up to 256 VLANs."
good" "[...] that Cisco 3750s only support up to 256 STP instances."

The limit is for STP instances, which equates VLANs iff some kind of per-VLAN-STP is used. With MST, Cisco supports a higher number of STP instances.

Of course, the number of supported STP instances is model specific.

wrong: "[...] Cisco enhanced the MST protocol [...]"
right: "[...] Cisco uses a non-standard-compliant MST implementation [...]"

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.

VARP is very useful for an MLAG configuration, e.g. the server 20.20.20.20 would use both SW1 and SW2 as default gateway, depending on the hash for each individual flow.

The picture is not "wrong", it is just a bit too vague and probably leads people to wrong ideas (just as most pictures showing setups with Cisco's GLBP).

wrong: "[...] show ip virtual router [...]"
right: "[...] show ip virtual-router [...]"

The hyphen is missing from "virtual-router".

the way you?d expect them too.
the way you?d expect them to.

End of page 199 and start of 200.

Where you say there are two fields we care about in his chapter. You say we care about CFI and VID. But you defined CFI as relating to token ring. I think you meant pcp instead. Either you meant pcp or the definitions on page 199 are wrong.

The definition of "TPID" has a spurious "0v" in front of "0x8100", which should be deleted.

This can be altered with the 􏰣􏰅􏰑􏰓􏰕􏰂􏰓􏰄􏰥􏰍􏰙􏰚􏰁􏰘􏰚􏰑􏰄 􏰙􏰚􏰁􏰘􏰚􏰑􏰄 􏰅􏰐􏰚 tx-queue command.
This can be altered with the bandwidth percent percentage tx-queue command.
On the page, "percent age" is wrapped without a hyphen.

The correct URL for sFlowTrend is http://www.inmon.com

VM Tracer can be given a range of VLANs with which it can add,
VM Tracer can be given a range of VLANs which it can add,

The trunk between the switched (port-channel 20 on both sides)
The trunk between the switches (port-channel 20 on both sides)

Luckily, we can limit the number of VLANs for which VM Tracer is allowed to change.
Luckily, we can limit the VLANs which VM Tracer is allowed to change.
It's not just *quantity* -- it's selection of particular VLANs.

but it get?s worse.
but it gets worse.

Missing space in Linux command:

wrong: "ps-ef r"
right: "ps -ef r"

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.

Mispelling of MLAG where it says MALG interface (VLAN 4094)

MAC address shown in code block on 306 does not match MAC address shown in dhcp options section on 307

MAC on 306 is 001c.7308.80.ac (00:1c:73:08:80:ac in dhcp format)

MAC on 307 is 001c.7308.80ae (00:1c:73:08:80:ae in dhcp format)

They should match.

there is a spurious closing parenthesis after VMTracer that should be deleted:

wrong: "[...] a VM discovered with VMTracer) is moved."
right: "[...] a VM discovered with VMTracer is moved."

wrong: "We've already see it in use for the MLAG peer, [...]"
right: "We've already seen it in use for the MLAG peer, [...]"

Missing n, that is "see" used where "seen" needs to be.

wrong: "[...] apply the trunk group Servers [...]"
right: "[...] apply the trunk group Leelu [...]"

This one sentence uses the trunk group "Servers", while all the examples and the text on the same page use "Leelu" as trunk group name. It might be correct to implement the change suggested by Tom Leach and replace Leelu with Server, but I like the movie reference and would prefer to change "Servers" to "Leelu" (or maybe "Leeloo" for the pedantic ;).