Arista Warrior, 2nd Edition

Chapter 33. Aristacisms

This chapter is an appendix of sorts, but it’s not really, because some of the content comprises items that I felt should be included in the book, but weren’t long enough to warrant their own chapter, whereas other items are just Arista-specific terms or nuances that I felt should be included but didn’t fit in any other chapter. This chapter is like the trash bin in my brain. I took a lot of notes for topics to put in this book, and this is the stuff that’s left over or didn’t make it into other chapters.

It is with great pleasure that a writer makes up his own words, and because I’ve been writing for a year and this is the last chapter, I’m a little punchy. I do hereby dub the items in this chapter, Aristacisms.

Arista-Specific Configuration Items

Although Arista’s Extensible Operating System (EOS) is a decidedly open source platform, there are some things that are configured differently on an Arista switch than on other vendor’s switches. This is my repository for such items that don’t warrant their own chapters.

There Is No Duplex Statement in EOS

I learned this the hard way when I tried to import 20 or so Cisco switch configurations into my client’s shiny new Arista switches. Many of the ports had hardcoded speed and duplex settings (which I quickly scolded them for; read Chapter 3 in Network Warrior if you don’t know why). Every one of these entries failed when I pasted them into EOS. Here’s what happened when I tried:

SW1(config-if-Et5)#Speed 1000 ...