So the end to end path simulation function is, it can be obtained very, very easily. And, the advantage over the GUI simulation that you will have all the information in a structured form, which will be to JSON, and we will observe that in a minute. So the input path function will look like this. The only thing you need to input is the query and the headers. The query will, include the API endpoint for the request, and the request is simple it's gonna be simply get request because you cannot change anything.

Right? The oldest source and inform and destination IP address will be included in the query. That's how it works. Here's a little check for checking if the response is okay or not. It doesn't mean that the simulation is is, done properly.

It only means that the response is okay. And, in return, we will get the response itself that we can observe and investigate further on. So let's have a look how the simple end to end path simulation can be run through an API. This is a quick scriptlet, how you can define all you need. Here is a very very long dictionary, which is which will be including the endpoint, source IP, destination, source port, the asymmetry, we don't need to play with it now, the RPF option protocol type, and the snapshot ID.

The the snapshot ID is different because you need to use a snapshot ID. If we go back to the IP fabric because we remember we can get the snapshot IDs through an API as well if we call the get snapshots function. If you wanna check where you can find the snapshot or the snapshot ID in the GUI, you can find it at floating place. If you go to the URL, this is the snapshot ID. Right?

Or pretty much anywhere, if I go to the inventory and devices and ask for the API, again, this is the snapshot ID. So we go back to the discovery snapshot because this is the snapshot with only 2 devices. I don't wanna run a simulation there because there's not gonna be the information I'm looking for. I wanna run a simulation in this particular snapshot, so I want to define the snapshot ID. So if you go back to the function here where we're gonna define it, so it's gonna be the same.

So, again, I'm gonna prepare the end to end query, which will be consisting of following parameters. So right now I'm gonna create a end to end query which is gonna be an empty string, and I'm gonna put all the values from the dictionary. K. And this is how it looks like. So it is the endpoint and kind of a payload at the same time if you if you imagine that you're not posting but getting information from a certain endpoint.

So it's that's that's a little bit of analogy to that. So let's call a function and see what we have in response or in return. Okay? Seems that the simulation is ready. It only means that we have the correct response that we expected.

Let's see what we have in the simulation itself. So the JSON. Let's see what keys we have. So we have 2 keys right now. The response is you got a graph and AD.

If there is an error in the Android path, we will get an error key called error. But we have only graph and AD right now, which means it seems to be successful, but we need to observe all the hubs to make sure. The graph will include all the information about all the hubs that the packet is traveling from the source to destination. The AD is a list of the sites as they are defined in the IP fabric. So we can see what we have in the AD.

Alright? And it seems that there's only one side. So the the package is only within one side. So it's not leaving the the side. And now let's see what we have in the graph.

Okay. So this is all the information we have in the Internet. And you see, it's a very structured information because it's showing you all the information about layer 2, layer 3. The security portion, it will show you all the source and the and the and the exit interfaces. And so for example, let's analyze the entry path more closely.

So we see in in require we have a dictionary, then there's notes, and there's just a list of the notes. Now the the notes are already going from 0 to whatever number. They are the exact hops. So they are ordered in a way that end to end path was simulated, and this is a very important information to know. So if we check for notes, We have the list.

So what we can do and define a no list, which is gonna be list or n in node list. And let's see what we can have. So we have device type, router, forwarding, and, let's search for the host name. Here we go. Okay.

So this is at least what we can have. We have basically the trace route hops, but they are not only trace route hubs because it works also on there too. And see, it's ordered the other way around. Because if we go for back to our internal spa simulation, the source IP was 112. And you realize that we searched for the host name.

The reason for that is the the last hop in the list is the origin is the originating host. So it's not a router, but it's defined as a host in the IP fabric. That's why its host name is just the IP address. The next hop is layer 2. I think that this one is with the first layer 3 hop.

The second layer 3 and our layer 2, layer 3, layer 3, and and the the last hop. So the the the the list is reversed. When you're going from from the source to destination, it will actually show you the destination where where the end to end path ends as a first part in the list. So, again, I hope that the webinar was helpful and informative for you. I hope you enjoyed it.

I hope that you enjoy more webinars. There are there are there's more to come. We will definitely touch the API the API again. We will do other webinars focused on security. We'll do other barriers focused on us, more simulation and the new features that we have in the IP fabric because with the 3.5.0 version in the IP fabric, we have just started with the API based discovery, which is a great stepping stone for any further focus on the SDN networks, the networks in the cloud, and there's more to come.

So I wanna again thank you for watching, and have a great a great day.