User Tools

Site Tools


dido:public:ra:xapend:xapend.d_opsys:apstra:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
dido:public:ra:xapend:xapend.d_opsys:apstra:start [2021/08/18 11:12]
murphy
dido:public:ra:xapend:xapend.d_opsys:apstra:start [2021/11/09 15:55] (current)
char ↷ Page moved and renamed from dido:public:ra:xapend:xapend.d_opsys:apstra to dido:public:ra:xapend:xapend.d_opsys:apstra:start
Line 1: Line 1:
 ====== Apstra ====== ====== Apstra ======
-[[dido:​public:​ra:​xapend:​xapend.d_opsys| Return to Operating Systems ]]+[[dido:​public:​ra:​xapend:​xapend.d_opsys:start| Return to Operating Systems ]]
  
 EOS is **Arista'​s** network [[dido:​public:​ra:​xapend:​xapend.a_glossary:​o:​os|operating system]], and comes as one image that runs across all Arista devices or in a [[dido:​public:​ra:​xapend:​xapend.a_glossary:​v:​vm]]. EOS runs on an unmodified Linux kernel under a Fedora-based userland. There are more than 100 independent regular processes, called agents, responsible for different aspects and features of the [[dido:​public:​ra:​xapend:​xapend.a_glossary:​s:​switch|switch]],​ including drivers that manage the switching [[dido:​public:​ra:​xapend:​xapend.a_glossary:​a:​asic]],​ the command-line interface (CLI), Simple Network Management Protocol (SNMP), Spanning Tree Protocol, and various routing protocols. All the state of the switch and its various [[dido:​public:​ra:​xapend:​xapend.a_glossary:​p:​protocol|protocols]] is centralized in another process, called Sysdb. Separating processing (carried by the agents) from the state (in Sysdb) gives EOS two important properties. The first is software fault containment,​ which means that if a software fault occurs, any damage is limited to one agent. The second is stateful restarts, since the state is stored in Sysdb, when an agent restarts it picks up where it left off. Since agents are independent processes, they can also be upgraded while the switch is running (a feature called ISSU – In-Service Software Upgrade). EOS is **Arista'​s** network [[dido:​public:​ra:​xapend:​xapend.a_glossary:​o:​os|operating system]], and comes as one image that runs across all Arista devices or in a [[dido:​public:​ra:​xapend:​xapend.a_glossary:​v:​vm]]. EOS runs on an unmodified Linux kernel under a Fedora-based userland. There are more than 100 independent regular processes, called agents, responsible for different aspects and features of the [[dido:​public:​ra:​xapend:​xapend.a_glossary:​s:​switch|switch]],​ including drivers that manage the switching [[dido:​public:​ra:​xapend:​xapend.a_glossary:​a:​asic]],​ the command-line interface (CLI), Simple Network Management Protocol (SNMP), Spanning Tree Protocol, and various routing protocols. All the state of the switch and its various [[dido:​public:​ra:​xapend:​xapend.a_glossary:​p:​protocol|protocols]] is centralized in another process, called Sysdb. Separating processing (carried by the agents) from the state (in Sysdb) gives EOS two important properties. The first is software fault containment,​ which means that if a software fault occurs, any damage is limited to one agent. The second is stateful restarts, since the state is stored in Sysdb, when an agent restarts it picks up where it left off. Since agents are independent processes, they can also be upgraded while the switch is running (a feature called ISSU – In-Service Software Upgrade).
dido/public/ra/xapend/xapend.d_opsys/apstra/start.1629299560.txt.gz · Last modified: 2021/08/18 11:12 by murphy