Now, with the introduction of all this advanced configuration and different
resources that we can tamper with, RME Configur,
we need to be able to go in and take a look at the actual API.
And I wanted to introduce a couple of things in this particular skill because
API configuration
is more expansive inside of infrastructure as a service within Cisco.
So let's hop on over and I'll show you an example real quick.
Now inside of our DevNet sandbox, I'm actually taking a look and searching for WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Now inside of our DevNet sandbox, I'm actually taking a look and searching for
API.
And what I've done is I've gone in and opened up another sandbox environment.
This one is open in XOS.
And if you go back in here and your search, you'll see it in here down at the
bottom if you search for API.
And I just went down here to launch and that just gave us our new environment
because remember inside of this arena,
we can only do one at a time.
So listed up here is the top and I'm going to double click on it and go inside
of it.
Now it may not seem like there's actually a lot going on here, but oh bear with WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Now it may not seem like there's actually a lot going on here, but oh bear with
me for just a second.
This one doesn't require VPN access per se, but it does requires to be able to
fire it up and be able to access it through HTTPS.
I bring it up for a very specific reason here momentarily.
If you look on the actual, excuse me, instructions tab of what's going on here,
you can scroll down and go into access details and you will be given a host
username password and different port numbers. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
username password and different port numbers.
And these port numbers come into play with what we'll talk about here in a
second between the difference between net comp,
which you see there.
It's port 830 and rest comp, which is portable for three.
Now I took the actual credentials that we have here in the site.
Let me scroll back over for you right here.
The SBX and then the username password and open up another browser to come up
to this right here.
Now it's going to ask for your username password and I'm going to copy the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Now it's going to ask for your username password and I'm going to copy the
password and just type in admin admin and then paste in password and it will
bring this up.
Now also note up at the top.
It's not secure.
So that means that we'll have to make sure that we add an exemption for this SS
L TLS certificate.
Now inside of here, we get a configuration arena to where we could go through
and enter CLI commands on per line.
And you can see here that it comes in different languages, Python, Python,
three job of JavaScript, going and then you also get response is responses as WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
three job of JavaScript, going and then you also get response is responses as
well.
And you also have post.
I'll be going into this here very momentarily, but I just wanted to show you
what the environment look like.
So that way you can open it up yourself and play along at home.
And that brings us into introducing net comp and rest comp net comp works to
define and manage device configurations in a very somewhat structured way.
And it's usually done in XML format, making it easier for us humans to read it WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And it's usually done in XML format, making it easier for us humans to read it
and for the machines to process it.
Now the reasons that we saw the actual different ports wall ago is because net
comp usually uses SSH as a secure mechanism transport, but it can also use TLS
and other transport.
protocols at that secure level.
And you have different operations that you can use like get config and a config
copy config and so forth to be able to manage device configurations.
The uniqueness here is that net comp is transaction oriented, meaning that it's WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
The uniqueness here is that net comp is transaction oriented, meaning that it's
all or none of the changes are being committed to the actual device.
Rest comp on the other hand uses HTTP methods like get post put patch, etc,
which is why we saw that post command wall ago.
To using it to interact with the network and devices, making it familiar for us
working within the actual web services.
So if you're familiar with HTML, this ought to be a bit of a walk in a park for
you.
And now while net comp relies on XML rest comp is allowing for Jason to work WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And now while net comp relies on XML rest comp is allowing for Jason to work
alongside XML as well in representing data.
Now rest comp typically uses HTTP or HTTPS is a transport protocol.
And we want to communicate through TLS because we can apply those different
certificates to be able to ensure that data emotion is taken care of in terms
of security.
But rest comp is resource oriented and it presents resources such as
configurations and operational states in a high arqueal structure, meaning like WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
configurations and operational states in a high arqueal structure, meaning like
top to bottom and more organization based and utilizes you are eyes uniform
resource identifiers, meaning we can access each device configuration or
operational state as an individual resource, which can be manipulated using the
appropriate HTTP methods.
Like the ones we were talking about with the HTML commands that we usually use
like get push, etc. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
like get push, etc.