Edwin Beekman

OpsCode Chef on Arista EOS switches

Configuring switches can be cumbersome and boring.  At least I find it something  I would really like to automate and make it better available for colleagues.

For coding the infrastructure we have chosen for Opscode Chef and rolled out our own private Chef infrastructure. We can automate an awful lot: roll-out new Hypervisors, applications, configurations, services. But coding the underlay is still something that is in development. read more >

Configure Arista eAPI with Python

It is possible to manage Arista switches with the Beta Devops Extension, however this is not yet production worthy. But Arista has a much more cooler extension which is far better usable; the Arista eAPI.

With Arista eAPI you can use industry standard CLI commands to send requests, and get returned data that is structured and documented. These requests and responses using JSON-RPC, a lightweight data-interchange format that is easy to read and write and to parse and generate. read more >

Create your own Arista switch CLI commands

How cool would it be if you could create your own CLI commands on a switch?
With the Arista EOS you can. Under the hood is a Linux kernel running which
gives you all the flexibility you need.
Basically the EOS switch commands are written in Python.
When a user logs in you get the CLI and you can interact with the switch.
Every command that is entered has an associated Python program, the switch CLI command. read more >

Schuberg Philis cloud L2-L3 Use Case

How can you connect existing customers with a legacy infrastructure  to a virtual infrastructure in a cloud or how can you extend these infrastructures with a virtual infrastructure?
The answer is actually very simple when your Cloud infrastructure is using Nicira NVP, because this will give you the possibility to use their cool NVP Gateway. If your cloud infrastructure happens to be controlled by read more >

IPv6 Adressing Plan and Policy

There are several ways to create an IPv6 addressing scheme.
The following example is based on the Ripe addressing plan, which can be found here:

Define primary subnet
Location and Environment (E):

Round-up to 4 bits, i.e. 16 groups

Define secondary subnets
Layers (L): read more >