Turning measurements into actionable insight with Cisco Crosswork Assurance​

Welcome to 2nd installment of our Cisco Crosswork assurance integration, within.00:11The Cisco service provider portfolio. Today I'm excited because we are gonna go into the dynamics. I am going to show you.00:20How everything was built and made, I am going to be flipping. Let me give you some, some ground rules right now. I am going to be flipping from live and some PowerPoint presentations. So we're gonna be going into the system. We're gonna look at what the system is doing.00:31We're gonna I'm gonna be using some command lines so you can see how it's done. So my goal here is to present to you the closed loop automation. So we're gonna try to finish that and then we're gonna move a little bit more into expanding the knowledge of.00:51Onboarding devices into the NSO when it comes to doing another, let's say session, how does it look like? What are the commands that we're sending? Okay. You see how simple it is? Everything could be done with one script, ok? So but I'll be showing you bits and pieces.01:08Alright, so let's just start with the presentation in here. I'm gonna share my screen. There you go. Okay so.01:26In today's session, as I said, we're gonna be doing NSO, Crosswork assurance, and we're gonna show the integration and we're gonna be touching the routers a bit. So you'll see the the setup that we have.01:43Let me move into the agenda. So the agenda today is understanding the crosswork assurance. Definitely, there's so new people in in in this presentation can you are you sharing? Yes, I am sharing. Let me just double check. Okay ok.02:02Okay, it's it's.02:22Okay let me just double check just in case it's not sharing the screen share it's sharing now yeah yeah it's good. Okay, thank you. Thank you Rajesh. So I'm with Rajesh here Rajesh shall we, ok? He is the person on the last presentation that explained to you all the Python.02:24And the action on the NSO, ok? He's gonna be today assisting me in this presentation. If you have any questions at the end regarding the topology, the configuration and the programming, he's the expert in Python, you know, he can help you. If you wanna mimic this with a customer, if you want to present this, I'm.02:44And standalone NSO. Just remember that it's a standalone for the CNC, we'll be doing it on 8 July, ok? So this is just NSO and Cisco Crosswork assurance.03:04So back to the agenda, we're doing how the crosswalk assurance works. We're gonna do the collectors, some of you that know the Crosswalk assurance will understand right away what I'm talking about here. If you're not familiar, I'm gonna give you a good idea what it is. We're gonna look at, we have to do the visualization, but some.03:16You know dashboards a little bit. We gonna do the, the yep. Okay, we're gonna share everything with you guys, yeah. We're gonna do the deployment options. We're gonna see the sensors, ok? I want you to understand the sensors, the hardware and the software sensors.03:35And then we do the integration with Cisco NSO, and we're gonna give you the checklist, we're gonna give you all the pref pre pre flight list of what you have to do or need to do what we're going to do. And the last part is Q and A So I gotta move faster because we have an hour and a half an hour and 20 min, and I wanna.03:55Reached to the goal that is the closed loop assurance closed loop assurance that I want to introduce to you. Okay, so crosswork assurance. So it's an AI power platform that provides clear real time insights into your network health.04:13It goes beyond basic monitoring, to help you track network issues and network performance issues. The solution has two parts. Central, which is the platform, ok, and distributed, which are the sensors.04:31You can choose between a software sensor or a hardware sensor, it all depends what you are presenting to the customer or what your customer wants to do. Crosswork assurance, I could describe it to you for this presentation in three simple ways.04:48Number one, it collects network data using sensors, and number two process a lot of information and number three it provides clear insights and help you manage your network. Crosswork assurance sensors, ok, where do I.05:03Put those sensors, what does the sensors do, ok? You place the sensors where you need to gather data.05:23That's what you're gonna do. If you decide to put software or hardware, you have to architecture this according to what your customer wants. Now, what do they do? They do synthetic packets, you know, they simulate these packets and they sell, it goes like a real traffic.05:29Of of the the your customer traffic, so you get the user experience and you can detect issues before they happen. That's the idea. And we track the network data with microsecond precision. So you will see that in a moment. Now you have the Cisco assurance as.05:49SFP. I wanted to show you some, most of you know the SFP, let me just quickly.06:08Stop here. All of you knows an SFP, ok? I just wanted to show you, you know, a real SFP, how they look like the size that we have, so you can see exactly how they work. So this is your SFP. This is what we call a hardware sensor, ok?06:15You inserted that the beauty is that you inserted any place where you can put an SFP. You have also the modules, ok? And it's got power in here, so this is the difference. You need to have power to put this on the network.06:36Okay, and you can see the size of my hand, you can tell how big it is, ok? And we do have a smaller version in here and this is what we offer right now in the portfolio, ok? Also it's got ACDC power.06:54Well, you can have this, you can have this as you can see for the sfps, one gig ten gig, the vari the variance you we can see what we have in there. If you need more information on this Crosswork assurance.07:10The salesperson or sales engineer can help you get in all the data sheets for this sfps. Then you have the software based agents. They are running in containers or Vmiss and this is on your existing compute infrastructure. So we're talking about VMware, we're talking about.07:30Ubuntu machines, you know, a.07:51Different devices that are compute. And the last one that I show you a moment ago we were the modules and the modules they can this all these devices, the hardware can be ordered based on that you wanted let's say DHCP enabled, you want it when you plug it in, you can detect it right away, you know, so you can have all kind of combinations in here.07:55I don't wanna go into those details, but as as I said again, your Crosswork assurance agent can help you in this or sales engineer.08:15So, the sensors, once you have sensors, you need to instrument it, instrument it in your network. What are they gonna do? They're gonna collect data. That's the idea. You're gonna get a lot of data from these sensors. Remember they work seven.08:2624 seven, you know, non stop, you know, once you activate them and you make them do whatever they're supposed to do, which we're gonna see in a moment, you know, they're gonna work non stop. They have to instream that data to a collector.08:45So the collector, what it's going to do, and I'm gonna put my laser pen in here for a moment there. The collector, what it's gonna do is gonna, it's gonna get all this information in real time normalize it, ok? And if you have any metadata, it's gonna be enriched with the metadata, and it's gonna stream this to the.09:00The Analytics platform, which is the next step.09:20How do we do this? We use the T one protocol, it's a layer three protocol. I'm sure amount you in this presentation are very knowledgeable about this protocol. For those of you that are not familiar with it, this is what we use to make these devices in.09:24Year three.09:43Send that packet and reflect the packet back. So quickly T wamp, ok? The way it works is I'm a sender, you're a reflector on your side. I send you a packet, you reflect it back to me. Now.09:44In T wamp, I'm gonna send you the packet I'm gonna stamp it and there's gonna be, as I recall, a hundred and 14 different KPIs that are coming. Kpis is key performance indicators would be packet loss, delay jitter, and others that I'm not gonna mention it here. And I'm gonna stamp it and I'm gonna send that packet to you. You're gonna receive it.10:05You're gonna stop it and you're gonna send it back to me with all these KPIs, ok? So we're gonna start collecting information how the network is working. This is a light simple T one there, however, it can get complex, you can get a little more detail, ok? We have the T one control.10:23Where we do a handshake in TCP IP, hello, hello, and then we decide to start sending the packets. If we break that handshake, the T one breaks, ok? We do the handshake again, the T one continues, ok? So there's many different ways to do it, many standards to do it. What I want you to remember right now is that the.10:41Is stateful and is stateless. This is very important for the crosswalk assurance products. It's stateful means that I'm gonna keep a sequence number. So if I stamp it and I put packet one and you get it on the other side, you're gonna see it says ok this is packet one. Now I'm gonna put packet two.11:00Stamp it and send it back to me. I received it and says, Oh I got packet two. So here's packet three stamp it and send it to you. So we have a sequence number, and this is only for packet loss, ok? If you send me packet two, ok, and then you receive a pack packet.11:18Six, let's say. That means you lost some packets. So we know that the the the communication was lost in the uplink. Miss send it to you so you know what packet losses in which direction, uplink on that link. That's the way the sequence number worked, ok? We have the same thing for delay, but delay.11:33There is NO need for sequence. Delay works with a NTP with a.11:53A network timing in, in the network, ok? So you need an NTP, you need something like that, that is gonna converge your watch with my watch, something like that. Not the same day, but we need to converge to be able to find.12:00The most precise measurement of uplink delay and downlink delay, ok? That's how it works. Now, I'm going back to the presentation. As you can see here, we have the assurance sensors, which are the sending packets and this is reflecting packets. Now you can dress.12:16This pack is the way you wanna dress them. You can put a suit on them.12:36A VLAN, you can send ten packets per second, which is the default setup or you can send 10000, I'm sorry, a thousand packets per second. If you need to, it is, when would I send a thousand packets per second? Well it depends on what you need to measure, ok? So there are different types. I know some people.12:41When it was a VoIP VoIP over LTE, they were using 20 packets per second, which give them better measurements, ok? So you'll have to discuss that with your engineer to know what is best for you. Priorities DSCP, you know, for voice, I don't know, data, best best effort.13:00And.13:20The result is the collection down to every second that that information brings to us and you'll see it on a graph in a moment. Next, we go into the data collector. I mentioned to you there's something called the data collector, we used to be called the rock runner.13:22It's NO longer the road runner. Right now you might see it in some old documents that you might have or you might hear someone say, No, you have a road runner, ok, it's a data collector now. What does it do? It collects information, ok? It's gonna have all these agents.13:41Going to him, ok, and put it all the information and he's gonna stream it all the way to analytics, to the platform analytics. Let me show you, ok, I'm gonna start flipping back and forth now between.13:59Between, screens. So here's the collectors, here's the collectors in my on prem, this is on prem Crosswork assurance. So these are collectors for me, and they are in charge of collecting data.14:15I have a few devices that are sending information to them, ok? Same thing goes with on cloud, this is on cloud, ok? Let me show you here. You probably see a lot more. There's some updates that I gotta do in here, but I wanted to show you on this one. This is the one I use for teaching, it's a training.14:35Tenant and it's on the cloud. It's not on premises, ok? So these are our collectors ok the collector, we have two types. One of the collectors called telemetry collector. We're not gonna.14:54Be using telemetry collector for this presentation because we are doing some onboarding with the NSO telemetry collectors are, they ingest external telemetry.15:14Okay, that's what they do and they also ingest Cisco devices, ok? We're talking about xrs, you know, you can get information out of the box, you can get information about Cisco XR xs, ok, with the telemetry collector, so we're not gonna be using them when I'm not gonna do anything with the telemetry collector I'm gonna use.15:23Just the, the assurance sensor collector, ok? And as a sensory in here, sensor collector aggregate and four assurance measurement streams. Okay. Visualize. How do we see all this? Okay, so you know it's gotta go to the analytics.15:44Platform. Once we get all this data, we run it inside our system and you start making sense of your data. We have pre built specialized workflows for your investigations.16:03Health analysis, network troubleshooting capacity planning, SLA compliance, this is what we're gonna look today and QA analysis. Remember this is all AI machine learning. Just to give you a good example, ok? I'll bring it on the screen.16:20I'm bringing on the screen, there you go. Okay, I'm looking right now at the training which is on the cloud, ok? And if I go to one of the presentations that I have here already prepared, you will be able to see in here details of your network as you want to see them or presented to a.16:41Customer. Here's the total sessions that I have.17:01And here's a visualization of the network. So you can have you can have strict numbers giving you details of, of what you need to know. In this case is packet loss. You might see some exaggerated values in here. This is because I'm inducing this delay, ok? Zoom in into a specific configuration that you have in here, this is for.17:04For Italy, ok? And you'll have also your.17:24Table to visualize you what you need to see exactly, ok? And you can have different ways to get alerts telling you that this in North America, the Cisco device that is giving you an alert, so you need to be notified that that's happening and what other equipments and so on.17:30Okay, so this is what we call devices that can visualize. We call them widgets. Okay, getting back in here and the most important thing that we're gonna move into it is now the crosswork assurance.17:47It is important to understand now that we're gonna do a closed loop automation.18:08So, Crosswork Assurance has the ability to interconnect with NSO, ok, has also the ability to send messages, ok? There's always some configuration that it has to be done, ok? So if you wanna have, let's say you have a crosswork assurance as you remember is about.18:12Changing a route on, on, on a specific on on the routers to send the traffic in in a path that is better, that has NO issues, ok? You can, you can design how to change a route, you can decide just to send a message to the noc. So you can, we connect to Outlook, Salesforce, Webex.18:32Microsoft.18:52We can also send the data to Splunk, so you we can collect analyze, correlate, deliver insights, alerts, and integrate. So you're looking at generating alerts for and be sent to external monitors. We'll do that using the APIs. We do that using other tools.18:53That I'm not covering in here, and especially with the NSO that we're looking at here, ok? The close of automation, you, if you were part of the last session, you saw how we did it with the kickers and, the programming that was done by Rajez and Robert, you know, that we're able to change A.19:13About that he was having issues.19:33Deployments I need to give you the idea of the deployment because I show you the on prem and I show you the cloud. So this is the cloud. The cloud is NO infrastructure to manage, it gets automatic updates and patches. There is redundancy built in in the cloud, you pay as you.19:38Go for license and you need a good internet connection is very important, ok? You get the latest features and you're on the Cisco cloud.19:55We have the deployment on prem, so for on prem, you're pretty much making sure that everything runs internal, you know, you don't share any data, you don't share nothing inside, and if you do, you have some interconnectivity with.20:04Or some VPN that allows you someone else to come in and connect to it, whether it's someone from Crosswork assurance or someone from Cisco or whatever it is. And on premises it also means you manage all your hardware, your backups and disaster recovery, and you handle all your software. Let me quickly, as I speak to you.20:19Show you my on prem. So it's running on VMware, ok? And goes faster like this.20:39No, I think it's gonna be slowing down today. There you go. So if I go to my virtual machines, you'll see my own premise right here. Okay, it's the only one I have in green I have stopped the other demos that I have running, it's got an IP address, so you'll see it.20:54If I open it in here, 156I always look at the last octet when I work with this. So that's my 01:56 IP address. So it's completely running on prem and yeah, if you know VMware you can take a look at how much CPU was running, and you said we're not gonna cover that in this presentation, but this is the idea.21:13Okay, so you have the other option which is.21:33Yeah, so it's completely fully disconnected of all environments, issued is required by the military defense or critical infrastructure. That's the maximum security. The the thing you need to know is you own the hardware and maintenance, you handle all the software updates yourself and.21:38Requires a dedicated skill team, so you need to have some skill team, IT people that work with that.21:58Alright, so that covers the three deployments. Central agents wireless sensor agents. Okay, so they are containerized, software agents that run on a.22:04Docker, ok? And they're very easy to deploy. They're very, very light, they're flexible, they're learning containers of virtual machines, works with your existing hardware. It uses minimum resources that can be placed anywhere in your network.22:19How to deploy a sensor agent, ok? We I'm I'm using a docker, because it's easy to deploy as I mentioned, but you can go bigger for bigger would be in Kubernetes, ok? Or openstack, and or the cloud, which is a different story. You put everything on the cloud.22:41And we'll take care of it.22:56A typical deployment pattern is, you know, place agent exactly what you need to monitor. That's all, data center branch cloud, whichever we want to monitor, and you need to make sure you do the end to end because this is what we can tell you what the user is having as an experience. We need to monitor it.22:59End to end. Okay, so quickly, I'll show you and here as we're moving a little bit more deep in the presentation, I'm going to.23:19Show you an agent that has been prepared for this demo. If you recall, we have a diagram like this before.23:36That allow us to see what was our lab, four routers, and three different agents, and you have also some sfps that i aggregated in here that I'm gonna show you how they work. So this is our topology. So right now I just got into.23:53Node one agent. I'm right here connected to this, ok? Is deploying docker. So I'm gonna get into it. Let me see if I can enlarge the view in case you're missing. So I'm just gonna do a CD node. I know I call this.24:11Directory node one, and this is where everything is running. If I do an LL, it's gonna show me two files, Docker compose, and secret file. So let's come back in here. So you need a hardware, just show you that i'm using a VMware. You need an operating system where I'm running.24:30In Ubuntu in this notes and you need to start your docker engines. So for me, I I'm complied with everything I have in here. I need these three things. These three types of communication.24:50That is going to have this sensor agent. Number one is need to talk to the platform, ok? The agent uses a secure outbound connection on port four for three to register with the platform, ok? It needs to talk to the.25:02The agent needs to talk to the reflector to do the test traffic. So you have management and you have test traffic. And the reflector in our case since we're using one of our devices needs to have also a heartbeat to our platform.25:20Okay, so these are the three things you need. Management, test traffic and heartbeat, ok, in my example. There are other type of communication and I'll bring it into you quickly right now so you can see a little animation we prepare for you. And what you're gonna see if I'm using.25:35This sensor and control collector sensor collector, ok? I'm using some specific ports. Let me just refresh. If you have a question you need to interrupt me, please go ahead, you know? I want you to understand this very clear. I'm going.25:55Going into the essential collector. Remember collectors are gonna gather all this information and sends it to the, to the platform. There is two ports in here, ok? Management port and this is the one that sends the information, the data.26:15This is what the platform from this port gets the information from here and it starts creating, building that intelligence, so it can show you a graph, it can show you all those details packet loss, and so on. So I'm going to.26:29Show you a little in here so you understand how we prepare this. Right now, this is a server that's got Ubuntu or Santos, and I got installed my docker engine. My collector.26:44For this sensor agents is placed outside. In other words, it's in another machine like this. You can have it in here if you want to. You can have both of them, your sensor agent and you have your sensor, your collector, ok? I chose to have it outside.27:02Okay, in another Ubuntu machine that is all configured like this, ok? But it's a collector. When you start your device, your, your agent, and let me bring it up on the screen in here.27:19Okay, when you start at your agent, and I'm going to go to my agent number two, and I'm gonna go into that directory and I'm gonna do a command that it says pseudo.27:38Docker compose, down ok so I'm bringing this agent down. How do I know it's down?27:56Well, we're gonna go in here, we're gonna look at the agent, and we're gonna see that is right now is offline. I'm in the agent section, ok? I just took it down. So when I start this agent, this is what's gonna happen.28:14Agent is gonna come up and he's gonna go talk to the orchestration agent orchestration that is inside the platform and he's gonna validate, so he's calling home, you know, did he call home, he's calling home and he's saying this is my my secret and this is me, send me the token, so we get authenticated, ok? So.28:35So what I'm going to do now.28:54So I'm gonna do that step. It's very simple as I mentioned docker compose, and I'm gonna change this command from down to app and I'm gonna detach it. Okay, so we don't see the messages on the screen. So it's doing it right now. It is very quick. That's what I like to use this dockers.28:56And in a moment, we're gonna see this communication that happened.29:16Let me do a refresh, one more refresh, and we have node one at online, ok? So this is what just happened. Now, we're gonna do the T wamp.29:21Okay? Because remember I show you this port, this is where the metrics are gonna go through into that collector and he's gonna stream it all the way here to be crashed, ok? So we have our agent in here. He's a sender, ok? These are the reflectors. The reason I put this one is because you you know them already.29:39But you can have a Cisco. Cisco can reflect aT1 or you can have a, you can have Huawei Juniper, you can have many different products that's gonna respond to the T one. I'm using the ones in here. Only one is responding in this example, not the three of them, so I don't want to confuse you with that. So.29:59Just imagine there's only one respondent, the other one is just shown in there for the picture. So we're moving to the, into the T wamp section where we start the T whamp. This is remember, ten PPS per second so ten packets per second is going very quick and is sending the information back and forth, ok? What's gonna.30:15For nexus, it will start streaming and sending it to the data broker and the collector and the collector is gonna send it all the way to the big platform analytics. So this is the result of this. It obviously takes some time to send the data, but I'm going to show you the result. The result is you're gonna have something like this.30:35And you start seeing your data. Okay, right now you're seeing in the inventory, you see in the session, you're not seeing the session, I just started though two to not want to know two because it's gonna take some time. I have to also start the team one session. I haven't started, ok? But you're gonna see something like this.30:56You have the performance, you can see all the KPIs that are enabled. So packet loss, loss bursts, jitter, delay. I, I got a lot of things here. We usually tell you remove the noise. We call this noise. If you don't need to see your jitter max.31:15Well, you don't need to see it in here. You can disable it somewhere else. And that would be in your ingestion, ok? So you won't have it displayed in here that so we said remove the noise, you don't have all this thing clotted in here, put what you need to see. That doesn't mean we're not collecting the data. We are collecting the data. It's just staying inside and you're not seeing it, ok? So.31:32This is what we just did here. We we're not gonna move into the Docker compose file, ok? I'll just touch the important things that you need to know here. Since I'm using this with the NSO, NSO needs to know that I'm.31:52That he is managing these devices, number one and number two, who, what is the device that we're connected to? There's two things in here. This is the, this is the docker compose file. This is like the I know when I know in Kubernetes they call it the manifest, ok? This is that pretend this is.32:10Manifest. You know the manifest it comes from the I think it's on the ship comes in and you got the list of what you carried or the list of the people is your manifest, ok? So this is the manifest pretend it is. It's not the correct name. So I give it a name an old one, ok? This is getting the software from this link.32:31Okay, it's an actuate that means it's gonna do T wamp. I give him some host name for myself so I know what it is. Very important. What ports are we gonna run in those T wamps? Remember that little picture I had put a a port in here, this port is port 8602. That's the one I use. That's it. Usually I want to use for a.32:50My demos, but you can have a different port, ok?33:10This is important for you. Here is my collector IP address, ok? And here is for the NSO. The net ID and the VLAN ID are very important for the NSO and for the setup so they know that I am connecting this.33:14To this node, ok? And this is the logical connection. This is not physical. Physical is something else, ok? So then agent one is attached to this router and this router has a host name. Router host name is here.33:33Put it on the screen. Let's go to the router. Note one host name is note one, ok? So if this was called Cisco one, I will give a host name Cisco one, ok? So let's hope that we got it that clear. It's very important to understand that.33:54And then the rest is pretty much a standard, you know, your secret with remember when you make the call, call home, get authenticated, get your token and all that. Okay, next, I will talk to you about the SFP.34:14Let me bring you quickly to the SFP. Okay, so you need to onboard an SFP. We have something that is called the sensor control. So it's gonna be the Crosswalk assurance sensor control. The sensor control is the one, is the command center for the SFP. That's.34:28That way. Simple as that. Some of you might know this already. So if I look at remote devices in my sensor control, guess who I find them here? My two sfps.34:47Where are they here? In this diagram, right? I should put it on this side, yeah. 2020 2053, they're right here, 2020. Okay, quickly.34:57For them to be able to generate team on traffic, they have to be virtualized and NFB. And it will be, it will become a VC, a virtual connector endpoint. So here are the sfps, they got a few rules in there for the NSO. The plus mean.35:14This is the, this is the device. This is the VLAN, so if I was using VLAN remember I show you here the VLAN one, ok? I'm using VLAN one because it's a native VLAN, so it passes through everywhere. Okay, but if you had like a VLAN 100 in here.35:31You will have to be using 100 right here. And then the plus plus is just if you have anything else that you need to put as a metadata information, ok? I'm not, I'm just using the name and the VLAN, that's all, ok? So it's created.35:51It there's ways to, to, to make sure that this is working, ok? There's a tunnel and it tells you the tunnel has to be green, the tunnel is red here for this device. I'm not using it as an NFB as you can see. Okay, but these two have to have the tunnel green. All right.36:08Back to the VC. Now, in my network, I'd like to ping either from here, here, this IP address. These are the L these are the L days, not the L three, this is the layer three pinging that I will be doing.36:24Or the T wamp, or T one's not a ping, but this is gonna be used for T one also. So I wanna test that connection. So I'm gonna ping from this to this to be able to see that I can reach the other network. And I wanna ping from the VCE remember, from the one that's gonna generate the T one. So quickly.36:40Maintenance system tool. I'm going to select the device, this one, and I'm gonna go to 555 twenties. You can see i've done it already to make sure that everything is ok. I can ping all the way from.37:00This device here all the way to this device here, ok? Now, let's do the trace. Trace route tells me that I'm going to go from 991.37:18And I'm going to 1981911, it's only one step, one route. So from here, I'm going here. 1981911 as you can see, ok? That proves to me that I'm going directly.37:38Let me see how we doing on time. I think we're doing ok. Okay, let's do this. We're gonna enter the router, ok? I'm in node one and I'll put it in here, Picture here.37:56So I'm in node one right here. I'm gonna enter this interface. Gigabyte which is the connection between node one and node three. So int gig zero/zero/0/six.38:13Sorry. Type again interface Okay, much better. Zero/use//6. Why am I typing something wrong in here?38:29Okay, yeah, NO apologies. So gig zero/zero. Refreshing prompt. Okay, for some reason it.38:49Doing some sort of refresh, ok, let me do an exit. Okay, and let me log in into the router one more time. Okay, let's try one more time ok so come.39:09Better, is it refreshing why I can go in and there? Okay, give me a moment, I will figure this one out. You know we're life, so this is what happened for your life, ok.39:30Exit.39:50Oh sure ok so we're good. One more time. Interface.39:54Internet zero? Oh, oh, I'm sorry. This has to do with my I know what the problem is. My apologies, I gotta stop this for a second. It's.40:14My keyboard is right now in French, so the slash doesn't work. Okay, here we go. My apologies, you go back. Okay, here we go. So interface zero/zero/0/six. Okay, I'm inside this interface and I'm gonna shut it down. Shut.40:30Okay, and we're gonna commit this information, so we're good. Ok, so let's do the ping one more time. So ping should work ok we got a ping, and now we're gonna do a trace route.40:49Okay. And if you notice we're going directly to one, ok? So trace route has changed from 1902 to 1912, ok? And then it goes to one. Okay, so we're validating that the route has been changed because I shut down the port, ok? So we'll do.41:06Oh shut.41:26Commit, ok? We'll do the same trace route right now and we should be getting directly to it, ok? All right. So this is just to validate and and.41:28Prove what we are proving today, ok? So you now understand the SFP, we're gonna do some in a moment. Let me continue, let's get into the NSO. NSO, ok, so network service orchestrator. This is the hands on, this is the the one that it does all the provisioning. This is the one that gets in there and it's going.41:47To talk to the routers, he's talk to the Crosswalk assurance and to talk to us, it requires.42:07A net. We have a net already installed, I am not gonna run through doing the net. I'm gonna run into doing the configuration of the crosswalk assurance, ok? So we have a net, we installed the net.42:12And we can see in here, if I log in, I'm bringing it out to the world of the NSO, ok? Dismissed this message. We're gonna go to tools and we go to package and we can see that we have an exceeding. It's called an.42:28CDN, ok? So I will have to use, there you go. I have to use this name the name at CDN, my apologies, but that's what the customer used to be called and it's also called the skylight, ok? So I'm using this version. What is this doing? The net is allowed me and allowing S NSO.42:48To talk to us. It also has an exceeding need in here. So you can, if you onboard a need, the elements, if you're familiar with the elements, there is some availability of the commands you can do here, ok? And also a sensor control. Crosswork assurance sensor control has a need also.43:07So if I was to onboard that sensor control, would you saw the SFP?43:27This is it. You can run some commands from here. Then you got the iOS XR and you've got the iOS XE also that I have here. So we're using the XR. So this allowed me to speak the language of these devices. Remember the word devices, NSO see if everything as a device. Everything is a device. So you'll see in the commands.43:31Okay, back into the net, so we have the net clear we're moving into now the configuration. So what do you need to do? You need to bring the net down.43:51Extracted as a package. You need to download all the young models that we have from the GitHub that are for exceeding or Crosswork assurance. You need to rebuild that net with the new young models and then you verify that you succeeded connected. Doing this will take about.44:0815 to 30 min, so I'm not gonna do this now, ok? But I can tell you that the net is already been loaded. Let me get into the NSO.44:27So this is the world of the NSO. I'm running a version that is called local, ok? I need to run the environment. So I'm gonna use a command here, which is source n NCSSR.44:43The NSO was done also.45:03Before like exceeding, it was known at the NCS. So they still keep those commands as a legacy as we do. Okay, so I run the environment. Now I can go into the NSO. I'm going into the application, and this is the command to get into the application. Right now I'm inside.45:04So.45:25If I do package, packages, ok, I press enter incomplete. My apologies, I missed something in here. Okay, there it is. So here is already loaded the exceeding. That's what we're looking for. We're not gonna talk about the other ones, the Skylatt restconf. Okay.45:26Now, I can get in it now. So, we will do device, I'm sorry we'll do config 1st, that's on Cisco configuration config and we go on device. Remember, they're all devices.45:46Okay, everything is devices, device, devices, and if I press a little tap in here, it will show me all the devices. So here is I, I didn't call it the crosswork assurance I call it PCA. Eventually in my lapse I will change your name. And then you got node one, node two, node three. These are your routers.46:01Okay, and note PC. That's all the stuff we have in there. Now before you build anything and I'm gonna start going into the details in here to talk to to any device, you need to follow some rules.46:21We, we did bring it in. We're now able to synchronize, so now we need to bring credentials, connections, and there's some details that we have to do. So I'm gonna bring you to that. This is the pre flight check.46:40Preflight check installed me download the net. We did that already, young models, we did that already. We rebuild the net to make it clean with the new young information and we verified as we did before, and we see the package, ok. Then we need to start doing.46:53Reloading the package and creating the group's credentials. Group credentials, pretty straightforward. You need to have a group credential and I'm gonna just scroll down here so I separate things. You need to bring it and give it a name. I gave him the name PCA, ok?47:08That was a while back. I'm not gonna change it for this demo, but I will do it for the next demos.47:29I have to give him also, the remote, the remote name, the username. That's the remote name. I was quiz it in here. This is the username. I need to give him the password, and this is the 1st step you do when you bring it to the NSO.47:34Okay, and not just the crosswork assurance, if you bring in routers, whatever it is, this is your 1st step. Now for us, you need to create a device. Remember everything is devices for NSO, so you need to build that device which is this, and put all the information you need. There is a script for this. This could be loaded in.47:50Like I said in 30 s, I'm not gonna do that. I'm gonna, it's done already, but I'm not gonna do that now.48:10You need to have your IP addresses, your port, your net. This is the most important things you need in here, ok? And the rest are part of the configuration. What else? Your certificates. As I said, you know, now we're on certificates to make sure we are fully fully protected. The SSL certificate for the client and the SSL.48:16Certificate private key. All this has to be loaded and this is on one shot, ok? All your rest configure, the capabilities, what to append, what to remove, what's automatic, and at the end, you inject all your capabilities.48:36Alerts, alert metrics, RSC 2540 4T1 slide Y 1564. If you know, if you know the crosswalk assurance, you know what I'm talking about. And then the last step is you synchronize it. And then you have your PCA looking the way it looks in here.48:53Okay here, ok? You have your PCA. There's another way to see it here, Expand it. There you go. You got all the information of your PCA, ok? Alright.49:13Next you gotta start bringing your things. And I'm not gonna bring anything at the moment manually because we need to get that closed loop application working and it takes some time. So what I'm going to do, is I am going to.49:32Bring a few things in here on the screen There you go. Okay.49:53Okay, so, but I talked to you, I told you Betty about the creating the groups. This is for the routers, same process. The group for the routers is called XR, passwords, and then you start adding new routers and you tell them the same thing.50:10The the name, IP address, the net that he's using, and the group to be authenticated and then get your SSH keys and you're ready, ok? If I have time I do a sensor control. I didn't do it, so I'll show you how it's done. Just want to make sure we get the closed group automation finished, ok? And.50:26Then you start bringing your notes, your endpoints, the endpoints are the exceeding devices, ok? So endpoints.50:46One screen here, one screen here, and I'm going to Axian. My endpoints are these ones. Note one, note two, and note three. And remember, I could have called this Cisco one, Cisco two Cisco three. I just call it the same name as the routers.50:55The host name of the routers. So here they are. This is my node one, my node two, and my node three. And if I run these commands, it takes seconds for me to place them inside NSO.51:15I also have the sfps Remember there were some sfps in there or they also onboarded, ok? So these are the commands I have to run. Very simple commands, the name of the device, which is the PCA advantage.51:34Maestro, that's what it means, ok? The name of the endpoint, I put some coordinator location, I put them in New York, ok? And the net ID that I assigned and that's on the, on the SFP and the VLAN, if you recall that, and the IP address that.51:53He's gonna be doing all the technical measurements, the T one. Okay, they all have the same principle.52:11It's just the names that it changed. Let's see it on the NSO, quickly, we're gonna go into config and we go into endpoints, and here they are on the NSO. I can get the same thing as command line. I'll show it to you graphically.52:18Agent one, node agent node one, agent node two, node three, and the sfps, ok? Which matches?52:38This diagram that we have in here, ok? Agent not one, two and three. Now, this environment is built obviously in a lab. Let me show you how it's built quickly so you understand.52:45I'm using VMware. Yes. All the routers, all the agents, and the sensor control are located in here. Node one, node two, node three are routers. Node PC is a router, then you got agent one, two, and three. Then you have your sensor control.53:04And the NSO is right here also.53:25They're all part of this environment. The difference in here is that in the networking, I created virtual switches, which allowed me to make them look like this for this lab, ok? Okay, if you wonder a.53:27Note one. Agent note one. This is the amount of CPU, this is the amount of memory that I placed on this device, ok? And I'm doing just one testing. If you wonder about the routers also, we can take a look at here quickly one of the routers, what is this router using is got.53:47For CPUs, 20 gig and I give 64 gigs of hard disk and so on. So last one, for your curiosity NSO.54:07Acpus, 25 gig and 100 gig. I normally go over what is suggested just to be comfortable. All right? Now, I have told you I wanted to make sure we can do.54:17The closed loop automation, ok? So I'm gonna kind of direct myself towards that, and then we can look at, we can explore other things that, e.g., node two is not in here. So there is note one and there's NO two. I'd like to add it, show you how the, the.54:32Yeah, the data starts coming in and how we start seeing graphics, ok? For the time being, we're gonna stick with node one to node three, which is the one we're gonna do the closed loop automation. In other words, we're gonna break the SLA. So.54:52Behind all this story, after I bring the nodes, I have to create the alert policies. There's a policy here that it says node one to node three and delay. So here it is.55:10Node one to node three. This node has a specific name and it has all the requirements I need to break, not to break, to create the SLA and then I will break it based on this. So I said 1 s.55:27Is the max this policy is gonna, is the minimum this policy is gonna accept. If I go over 1 s, it's going to create an SLA violation and is gonna send this information.55:45To NSO, NSO knows what to do. Let me show you this policy is already built. I sent this comments before. Here's the policy if you're accustomed to see our analytics.55:59Note one to node three. The policy name is here and if the rules are here. This was built with command line on the NSO. This was not built going in here and created anything. Okay, it's important for you to understand that.56:18You are going to be making all your configuration on NSO. Okay, so this is your SLA policy. Next, I I have many other policies that I'm not included in here. We use them as demo when we do a demo for another customer, ok? We need to create the session. The T one session.56:34So let's look for node one to note three. This is the important one. So here it is, Note one two node three. Okay, it's got all the requirement information. You might be familiar with this.56:54Starting with, ok? The name of the session, I call them the same. The session name and the session that I have to assign so the the system knows. The port.57:13For the T one session, the interval every 30 s or I could put every 60 s. This is like a window, ok? I look at this window for 30 s and then I move to the next window. So an interval of 30 s is what we use by default.57:28And then the IP address of the reflector. So if you look at my graph, the topology, the reflector is node three, the sender is node one, ok? So I'm telling that the reflector.57:43Is this IP address, and he's gonna be responded on port A 62. Then I make some configurations for the reflector. You're gonna be also responded on port A 62 7A62 responding 62.57:59Okay, so the session is built. The moment I send these commands, let's look at the session. Number one, we look at it as the agent. So I'm going to the note one here. Remember, this is the agent.58:14And here are the sessions. It's got two sessions running right now from node one. We're gonna concentrate on this one and then I'll show you this one later. Remember this is an SFP, so it's not doing software to software, this is software to software. So you can see that it's running, we're gonna go into inventory I can see it from here if I want to or I can just go to inventory and.58:31Selected. Note one to node three.58:51Let me go back for one sec. Note one to node three, I'm gonna show you the metadata. Okay, so here is the sender ID and the reflective ID. Remember now note one? This is very important.58:56This is the metadata, and also have the metadata for the location, ok? And it's active. It's running. You can click in here and you can see more information. We do a refreshment every minute, so it's been 50 s of the last refreshment, the DHCP if I was using what it shows in here, and who's the reflector.59:13Okay, so now let's go open it.59:33And you can see that it's been running data already and it's been running for a while, I believe I'm looking at 8 h, ok? Default. You can see that jumps in here. I'm gonna create some impediment in a moment to create a problem, ok?59:35I mentioned to you that analytics is very intelligent. The moment you connect, this agent's software or or or hardware agents, analytics start grabbing the information and you can start building something that is called baseline. And I'm gonna show you a baseline, ok?59:53At the moment, this baseline doesn't make much sense because I've been doing some exercise with this, but the baseline, what he's doing right now I'm gonna take a week.01:00:13Shows you past behavior to current behavior. And I have to apologize, but right now it's not gonna show you a very logical thing because that we we induce crazy data, but let me see if I can show you another one that I stopped. Now I don't have it. I'll show it to you after to make more sense.01:00:23Okay, so let's go back to my 8 h of data. So I have all the ingredients, SLA and the session is running, ok? Once you have those ingredients, you need to tie them together.01:00:42In a service, which is right here, and I'm gonna look for the service note one to node three and send the command to tie the session to the service and tie.01:00:58The policy that we built to the session also. Okay so now they're in here we type the nut. We put them together. Next job would be to start the session. So let me show you how I start now you stop the session that I can show you quick.01:01:14Bring this down, I'm inside the NSO. So I'm gonna go inside the PCA device. Remember, these are all devices. So if I put a capital device, I'm sorry, devices, I put a capital letter P I recognize it, and I'm gonna do I'm gonna do configuration, ok? Configuration.01:01:31I'm going to the session that I already built session, session, session sessions. Here they are. I'm looking for node one to node three. It's the session right here.01:01:49Okay, so put NO and I put two and then NO three, there it is, it identified and I say stop, it's going to stop. I'll do it after, ok? After we do the cross loop automation, I'll just stop and then start it. I don't want to interrupt the test that we're gonna do, ok? So do you.01:02:06Do from here. I show you the service before, so the services here, service, services. And if you see node one to node three, this is the one we built in here.01:02:26Okay, are you see this? Yes, there is a way to see all this. I just don't want to bring you there yet, but let me just do a simple show F, ok? And I'm gonna be able to see here. Here's the policy, the name of the policy.01:02:49Okay, if we continue, we see the service, ok? Here's the service. And here's the policy that we saw here. Okay, it's tied to this. And then you get the rest of the configuration. You're gonna get the node, so that node one is right here.01:03:06And so on. And the last thing I want to show you is the session. So I'm gonna look for the session because just bring me all this there's a session, not one two note three.01:03:26Exactly what I show you is in here, ok? If you do any commands in here and gives you an error, that means you're misspelled or or you type something wrong, so it won't let you to commit. Everything you do here has to commit. So let me walk now into.01:03:35Our closed looperation. Let me bring this down here. Let me break this down here. And the 1st thing I'm gonna do is I'm gonna log in into the node and I'm gonna create an issue. Remember? I'm using netm for this.01:03:52And I have prepared here the commands. Okay, we'll do it in a moment, ok? My time, I need to, I need to synchronize time in here. So we'll do it in just one moment.01:04:08In the meantime, let's just create NO two, ok? Before I send that, I need to be on time here. I need I need to synchronize my time. You can see my time in here. I need to synchronize my time in here 1205 to seven.01:04:30So we don't have to wait a long time here to see the the alert happening, ok? So in the meantime.01:04:47What I'm going to do is I'm gonna build that session for node two, ok? As I told you, it's very quick. So I'm looking for node one to node two in my configuration. Here it is note one to node two. I'm gonna copy this.01:04:56And I'm gonna send it, ok? I'm in the config config, that means I'm inside the PCA remember. Okay, so let's send it, paste, done, and I'm gonna commit.01:05:12It's been committed, completed. If I had an error, you will see it in there. Next step, I told you to have to tie the service. So let's find note one to node two service. It will be in here. Node one to node two service. So I'm gonna send it and I'm not adding this policy.01:05:30For alerts because it's not created. I didn't build it. So I'm not gonna bother with that, ok? Next, paste and I'm gonna do exit and then I'm gonna commit this. So it's ready. I'm gonna start it. Okay, so I'm going to session.01:05:46Sessions and I'm looking for note one to node two. Here it is. So note one, two are now it's asking me because it knows there is NO three also, so note one to node two space start and the session has started.01:06:05If I go back and here, agent, I got a note one to node two here, ok? And he's gonna start collecting data. So now let me move now. I think we're good on time now. I'm gonna send the command to create a.01:06:23An alert to break the policy, so copy and paste quickly ok.01:06:42So it's been sent. We are inside a, a docker. Okay, let me bring you inside the docker. Nope, one, so I can do pseudo docker.01:06:56Next sec minus IT, node-one. We're gonna do a bash, minus L, and we're inside the docker, ok? I can do quickly see the bar.01:07:14Log and this is where I see the logs, ok? And I can do a tell quickly minus F.01:07:33AP oop sorry gateway, and I'm seeing the sessions, ok? I would see a jump, probably note one to node 3708. If I look at another one, let me see if I see it. 78, so I started looking at it.01:07:39On the jump. So we send the jump already. Let's go into.01:07:59My alerts. No alert has come in yet. We're going into the NSO. We're gonna prepare the NSO to see the alert, sorry, I gotta get in here. Devices.01:08:05Let's go into the NSO. So devices PCA, we're gonna go into notifications, our data, notifications, there you go, I'm going to.01:08:25The last one, and we have today's date. Today is the 17th. So we haven't received the notification, ok? We will receive it in a moment and I'm going to login into the routers. As I said, you need to be pretty much synchronized to do everything in here. Let's go into the routers. We need only node one.01:08:43I'm gonna go into node one and I'm gonna do a, show segment routing. Traffic engineer, policy.01:09:02Color 200 and we're going the route is here. Remember? Dynamic route is here. We're going from one to three directly, ok? We will receive a message. We got, we got the the message already. So here is we have.01:09:18Has violated the policy. We're gonna look at it in both sides right now.01:09:37Here's the alert in analytics. We got the alert. NSO immediately got the message, and it's going to NSO, ok? We take a look at the alert and we see, let's take a look at the data. The data says the metric it went to 1.2 s.01:09:44So we broke the SLA. This is from inside the NSO, ok? Let's go to the router. What did we do in the router? We know here in this graph that the traffic was.01:10:01From one to two, ok, which it is shown in here. So we're gonna run the same command and we don't see the change right now. Okay, so live traffic.01:10:19I need to do something else in here. My apologies, I need a refresh and note one in here sync. Since I did changes on the router, ok. So, we're we're good on time so I'm gonna stop this.01:10:38And let's try to do it again. My apologies, as I said, this is life. If you missed any detail for this lab.01:10:58You're gonna have a situation like this. I'm gonna stop this, exit this, and paste. Okay, so I just stopped. Okay, we're gonna come back. We had a, we had we had a synchronized node one since I played with node one.01:11:08I did some changes, I needed to synchronize it, my apologies. The synchronization can be done with I know Rajesh is with me here. This could be done through the configuration, ok? Obviously we missed that step. We should have done the, the refresh, and since I played with the router.01:11:26And there's some changes, I need to synchronize it. So let me do the new synchronization, ok? And I am about to send one more time that alert.01:11:44Okay, we give it a moment because it has to clear ok and let's go back into PCA notifications.01:12:03Receive notifications and let me see if the alert clear already. Okay, we haven't received the clear yet. We still unraced alerts, so we wait a moment until we receive it and then we'll try one more time.01:12:23While this happens, ok, let me bring you into the NSO configuration. I keep this in the background because I'm gonna see here when it clears. Okay, so configuration wise, as I said to you before.01:12:40Everything has to start with an authorization group. Remember that?01:12:59Nothing cannot be done without the authorization group. And you're gonna be putting your username and your password in here. This is gonna be a clear text in here, ok? Once you go to retrieve the information, you won't see it. Net is very important, ok? If you don't have your net, you're not.01:13:04Gonna be able to continue. Many times during the configuration I was I was able to upload the net, you know, with this command, but if you don't inject.01:13:23Your capabilities, you won't be able to type anything. Okay, that's one of the 1st mistakes I committed at the beginning. So very clear. So we just received the clearing here, data, alert notification.01:13:35Alert data metric, and it went down to 340, this is microseconds, ok? So we're gonna try it again. Let's go back in here, look at my time, ok? We're gonna wait a moment.01:13:50Okay, another thing I can show you from here, we're gonna come back here, is you can synchronize your PCA, you can synchronize it all the way to NSO. Sync from.01:14:07Take your I'm taking your configuration and I'm bringing it to NSO. That's what I did to the router, ok? I know I missed one more router.01:14:28I can see with the timing here, so I'm gonna do that and doing the sync from, and when the clock is here at 17 I'm gonna proceed to send the alert.01:14:36Okay, and I'm gonna synchronize the last one, Sync from. Okay, and I'll have all the routers properly synchronized.01:14:52Now, going back to analytics, our alert was cleared, so we're good everywhere. Do we have any graphs that I can show you? Let me see? Note one to node three.01:15:12Here is the big jump you just saw, ok? So you have the graph anything below that you lose this data. So if I just zoom in in this data, you can see that the delay was always 400 and we're talking about microseconds in here.01:15:29But when the big change came in, that was the humangous jumped in here. Okay, so we're moving to 16. I'm about to log into the system one more time. I'm gonna prepare my note in here, exit again. Log in.01:15:46Do it again and I'm going to send the command for the violation of the SLA.01:16:06Alright, so we're waiting to the goes to the 17. Okay, we're until the 17th, so I'm gonna paste enter, put my password, so we sent it. I'm gonna stick here with.01:16:25The docker. Let me bring this a little bit bigger so you can see it. Okay, I changing directory to where I have my docker compose. Here's the docker compose is running in here. Now I'm gonna get into the.01:16:45Application of this node. So again, pseudo docker exec minus it, is node one bash.01:17:02Minus L Okay I'm inside the minus L is just to be able to tap the commands so CD and I'm going into bar log, ok again I'm gonna tell minus F.01:17:17The.01:17:37Happy I know what to tell already, so that's why I'm jumping very quick in this. So I'm looking inside the docker, the agent. What is it doing right now? So here's not one two node three, ok? I know this has to, there has been a jump already. Okay, we couldn't see it before because I don't have it running from before.01:17:39So right now it's happening, ok? Let's go and see remember node two? We should have some data for node two. Okay, so here we started the data for node two.01:17:59If I go to an hour, we can see that it started collecting all this data information. Alright, so let's go back into the NSO and wait for the alert.01:18:17Notification. So we're gonna have another one from the 17 in here. Okay, we have two already. There'll be a new one for the 17th. We're going back to analytics. I'm gonna go into my alerts, which is in here.01:18:40Okay? And we should be getting something soon and I don't want to distract your eyes from here.01:18:55Okay, I'll put this. A good way to troubleshoot your connection is coming inside the Docker and look at that is sending packets back and forth. So you can see, I always look at a transmitter receiving here delays and far end delays, ok? And you can see what sessions are running. As you can see here.01:19:10This is called note one to node two and the other one is called note one to node three, so you can see all the sessions that are running in here. So we should be getting the alert and.01:19:30Any moment? And we also run a little bit out of time, and this is the reason why last time we did.01:19:41Yeah Wilson will get back to you in a second. This is the reason why last time we did a video because we have control over this. Go ahead Wilson. Hold on, hold on, let me unmute him, ok. I'll unmute him. And I will cut you off Wilson as soon as I get there.01:20:02Yes, so hang on Wilson, we just received.01:20:20The alert, ok? Again, it went pretty high, ok? This is because of the, of the burst, important here, we got the alerts, so let's go into the router now, ok? So where is my router? It is right.01:20:23Around here. So again, last time I query, I have these values from one to three. So we're gonna do it one more time. So show segment routing, traffic engineer.01:20:44Policy color, 200 and the route has changed because of the delay. Remember that? This is not because we didn't, we didn't stop the interface. I can do a show.01:21:03IP interface brief and is up and running Interface six. Okay, I guess mooded now. Yes, thank you. Go ahead, welcome. Thank you. Yes. So do you understand you.01:21:22You introduce delay on on the path and that's why the the the change of a route, right? Just question about the configuration. I noticed there is a lot of CLI involved in configuring NSO is the.01:21:40That because of just for the purposes of this demo or is that something that could be done via rest APIs? It's the purpose of the demo. Okay. As I said before, you see this whole configuration in here?01:22:00This is, this is the actual configuration, ok? Right. I broke it in pieces. Yes. Right. You can send this in in a in a script. Okay, but even if it is a scripted, it has to be CLI or or is there any a way to do the same via REST APIs?01:22:12You could do it through the NSO, that's a very good question. I have never done it through APIs, but I'm sure there is NO reason why you wouldn't be able to. Yeah, yeah, you can, you can, and then and then NSO onboarding.01:22:34Can be done through that, you know, the NSO GUI that's shown there is a way to onboard a device from there where you don't have to do the CLI command. No, NO, of course yes, I I I understand the UI piece is for manual clicking.01:22:47But just wondering if the same thing could be done via APIs rather than you don't have to go through all this painful configuration I did, ok? One of the reasons I did it and is is to learn.01:23:07Okay, basically I needed to understand how it's done. Anybody who wants to build this lab, I will suggest you to go step by step, you know, I'm gonna I'm gonna stop the the the delay, so allow me just to type this, so we'll see it changes.01:23:22And I'm gonna keep something on the screen, which I'm not about to change, which is the router in here. I'm gonna come back to this because I'm gonna show you this value. Okay, so I'm gonna keep this here. But also if you are comfortable with the.01:23:42With the with the GUI, you can build the same thing on the GUI, but to build it, ok? Definitely you need to understand every single point in here, ok? So if you need two configurations, you need to know what the policy is, so there's a policy built.01:23:56This is a policy, you can come back, you can build it, you can add a new policy. If you put you in operation, you can, if you need to do a metadata configuration, you can do it from here. If you need to see the endpoints, they're right here.01:24:16Okay? You need to be from the beginning I can add net endpoints also if I need to do it from here. All is possible. But before you go ahead and build anything, you need to understand all this configurations step by step. It's very easy. I've done it before.01:24:30And as if you do it once or twice to the GUI, you will stay with the GUI. But if you do a large amount like I did, you know, as you saw I did all these endpoints. I can do one by one, yes, but it was gonna take me a while. Yeah, it's gonna take me a while but if you do the script.01:24:48We send them all and they're up and they're very quick, ok? Let me just go back one step here and the sessions, you can see all the sessions that you're building. You can start the sessions from here too. Everything can be done from here.01:25:06Okay, so let me bring you to the same thing goes with the routers. You can get into the routers and see the configuration, you know, you could practically do anything and see anything on the NSO.01:25:24Now remember, this is an an interconnection between Crosswork assurance and let me put I'm sorry, let me put before we close notifications operations. We're gonna clear the alert in a moment. I wanna show you something on the router.01:25:43Okay, and it would be the 4th clear, so we have three only. We haven't had the clear yet. The clear takes about we put about 60 s a minute and a half, so it's gonna clear in a moment when I see the 3rd one in here. What I send to you is.01:26:00It's very important you stand, you understand that this inter, this interconnection is between NSO, standalone, and Crosswork assurance, ok? We're not using CNC. CNC we're gonna present it on 8 July and there's not gonna be much interaction on this on the CLI like I'm doing in here.01:26:17I'm gonna show you things that are already created. We don't go into the details, but you're gonna see the value.01:26:37And and and and the importance of having this interconnection for customers that already have the CNC. Now, you can also have crosswork assurance without the NSO on the CNC. You know, Crosswork assurance, you just need to place those sensors.01:26:43For for the for the customer, you know? Here you go. We got the 4th one, ok? I'm not gonna click on it because we already know that it's clear just to remove doubts, ok? Critical cleared. We'll go back.01:27:01And here, and it's clear, we have NO alert anymore. Okay, I'm going into the router. This advertise is very important and I'm still connected, great. Okay, I'm gonna show you again the advertise and it has changed to ten.01:27:17This is what we're changing. If you recall, on the 1st presentation I did, by default, we use an IS IS underlying routing, ok. So this is part of the default advertise when you create the advertise, they all become with a value of ten.01:27:36Yeah.01:27:55Okay, so the ten is just saying this route is pretty clear. We have a PCE which is the intelligence of the paths. So what we did, and it might be your case with your customer that you need to manipulate this value. 219 is an auditory number that Rajesh.01:27:55Which he did all this configuration in Python and he's the brain on all this, ok? Robert is the brain of bringing the NSO to understand what the PC what the sorry not the PCA, but the Classbook assurance is doing. So Rajesh was just an alternative you know, number, which is 02:19, but this could have been 100.01:28:15Okay? And actually I wouldn't use 100 because we have an advertiser of another interface, and this interface is 000, which is actually looking in another direction. Ok.01:28:34So this will be your detailed configuration and I'll show you what the interface is looking at, and I think we're right on time in here. Unfortunately, we are almost done with the time. But if you look at interface 000 is this one right here?01:28:52And it's saying that this path has a performance measurement value on that interface of advertise delay 100. The one we were using is on six interface six, so that's the one which is manipulated this one to make the traffic take this direction. Now we clear the delay.01:29:10So it NO longer needs to go this way. Now it's going directly here. So show segment routing is going from one directly to three, which is what we want here. So thank you so much. We're right on time.01:29:31Unfortunately, we had a little mishappy there. That's why it took us a little bit of time, but thank you for coming to this presentation. I hope this was very helpful for you. The whole team of Crosswork Assurance will be ready to help you if you're a customer or if you are someone who needs to.01:29:48Be able to configure this for a customer or do a lab or do a test, we can help you, ok, from CSS. Rajesh, anybody from CSS, you know, the whole team in North America and CSS can help you soon the team in Europe also. So just let us know.01:30:08Thank you so much. There's a lot of people that help on this configuration inside from acciden. I called them Axidian. Thank you guys also. You guys did a lot of work. It shows in here, so I don't want to take the credit from you. I just put things together with the team from CSS.01:30:25And we were able to present this to you. So thank you and have a nice rest of the day. Thank you, Rajesh.01:30:45