Lab E16: Device APIs

Everything so far was typed at a prompt and read by a person. A program cannot read a prompt reliably: the same fact is laid out differently by every command. So the router offers a second way in, where configuration is data with a published structure, a request is a URL and a verb, and the answer is a status code and a document. You met that with a controller in lab N23. Here the router itself answers, and what you send changes its configuration.

In Daveth Pro (Network)Build it from the brief · Two routers · 8 tasks

What you will do

  1. Open the second way in
  2. Knock without a name
  3. Say who you are, every time
  4. The interfaces, as data
  5. Write a loopback as a document
  6. Change one thing, and only that
  7. Twice is a conflict
  8. It was the same router all along

New in this lab: NETCONF, RESTCONF, JSON, codes.

How it is checked

Each of the 8 tasks is checked on the devices themselves as you finish it: the bench reads how the network is configured and what it does, not what you typed. The lab is done when all 8 pass.

The lessons it follows

It opens after these, and uses what they teach:

Open the lab benchIt needs a computer: phones and tablets are not supported.