XR FCM SIA License Utilization Monitoring

Hello everybody. Good morning, Welcome to this 3rd topic of the FCM expert series. XRFCM SIA license utilization monitoring. Today, today Robert Andre are.00:05Going to be a presenters for both customer success specialists, and if you have any questions at any time, please feel free to raise your hand and I will unmute you to ask your question or you can also leverage the chat window to post your questions and, you know, we will answer you answer those questions for you. I hope you all enjoy.00:20For the session today. With that, Robert, Amir, please the floor is yours. Thank you.00:40All right, thank you very much. So thank you everyone for joining. My name is Robert Hoffman. I am a customer success specialist with the Internet and masskill infrastructure, and today we're gonna be covering XRFCM SI license utilization and monitoring. As you mentioned if you have any questions, please unmute yourself if you're able to or raise your hand, we'll mute you and then.00:45Shoot us a message also in the panel or the chat and me or myself or myself or Amir will go ahead and answer that for you.01:05So, getting started for today's agenda, we're gonna start with the SIA RTU compliance check and reporting. Then we'll move on to reporting automation FCM automation with the netconf, and then SIA capacity management examples. So we'll have three examples here at the end.01:14So let's get started with the SIA RTU compliance check and reporting. Okay, so for this 1st section, we're gonna start with the router licensing, kind of cover what it is, what it's about. Then we'll look at the SSM alerts and inventory so you kind of get familiar with.01:33They look like, then we'll move into the SSM integration reporting and reporting automation. So if you're not familiar with our licensing for the ISXR or the FCM right now, and if you've never seen the class check workflow, we've got that right here on the screen. But basically.01:53The licensing environment is going to be in a healthy state when all our XR routers are registered in the compliance state and the SSM portal does not complain about any expiring or insufficient licenses. Now, we're going to look in detail on how to check the state of these devices and licenses on the.02:13SSM portal. Now, this SSM portal mirrors almost identically to your SSM on prem on the licensing state. So you'll be able to use this presentation for each one. Okay, router licensing states.02:33Now your router's gonna be in a good licensing shape when the smart licenses is enabled, the router is registered and authorized, so basically NO SIA status are out of compliance you want to see SIA status in compliance, and we can use this show license status and show license platform.02:50Summary commands to verify the router state. So you see up top here we've got the show license status, you can see that it's registered, we can see that it's authorized. And if we do a show license platform summary, we do the pipe, include SIA, you can see ISIA status is in compliance.03:10So let's look at these alerts and inventory here. The SOL or the smart software manager uses alert icons to bring your attention to the actions required and this is to effectively manage your smart products and devices.03:27Your major alerts are gonna be noted in the red icons with the number of major alerts listed right beside it. You can see here we've got major, we've got like a thousand alerts. We'll have minor alerts indicated by yellow icons, same with the numbers and then the informational alerts will be in blue. Now, the various categories.03:45Of these alert met messages.04:05They require basically specific actions to be taken for each alert, so each alert is gonna be different. So you see we've got insufficient licenses for to basically get rid of that one, we can use the action and we can just transfer a license, so each.04:08Error or alert is gonna have a different way of resolving it. Product instance failed, so we need to go in there and see why this product instance failed, that's like our 3rd error down, so we'd have to go in there and investigate, hey, why is this router NO longer talking to our SSM?04:25So with each one of those, you can click on the top, and it'll basically go through and filter out the type of alarms, and then with the type of alarms, you can go to the actions and see what type of actions will fix the alarms.04:41Now, the SSM license inventory tab displays information about all the licenses in your virtual account, and we can see the number of licenses vault, which may include your perpetual or your.04:59You're available to use license. Now in the used column, it shows the number of licenses currently in use along with the, number of licenses that have been reserved. And the balance column indicates that the number of licenses that are either in a surplus.05:15A shortage or if it could be just zero, so you're gonna have one of those three. If there is an alert, we'll see it in the alerts column and this message obviously alerts you about the actions required, so it could be major, minor, and informational.05:31So moving on to these alerts, the alerts in the alert column, as I mentioned earlier are gonna be clickable and they contain more information on the actual alert itself. So on the slide we can see.05:51An example for a minor alert for expiring licenses. And as you can see here, we have a hundred and 50 licenses out of 1100 that are gonna expire in 15 days. So we just need to be aware that in 15 days we're gonna have a hundred and 50 less licenses unless we've got purchased more that are about to deposit.06:04Okay.06:24Moving on to the hardware tracking PID. So the tracking licenses were introduced together with FCM and they're used to understand what hardware you have turned up and registered in your network. So a system or a line card will consume a tracking license.06:29When powered up and these PIDs in with the capital T capital R capital K so like TRK, and they're gonna be deposited when you order your routers.06:48Now, when your equipment is purchased, these tracking licenses, are gonna be automatically attached and transferred into the specified virtual account, and this is so that we know our equipment is up and registered so in consumption.07:00So, the reason the reason we really want to use these hardware tracking PIDs is say you have, say you've bought a hundred and 50 routers. So you're gonna get a hundred and 50 of these tracking PIDs delivered.07:17Into your smart account. If you start registering these routers and, you know, you, you finished or you think you're finished with your installation and you come in here and you track it and you see that you've only used 70 out of a hundred and 50, you know that for some reason either you've got.07:32Stuff not registered on your network or you've missed some of your routers during the install and you need to track them down, so it's a way of knowing and keeping track of what you have on your network. Alright, so let's talk about the event summary and email notification.07:49Now, you may want to tune your SSM notifications under the smart software licenses and then preference tab, and you can do this to get updates and alerts on like different informational events. With these summary updates, you can be notified when there's any alerts.08:09Parts in your network like usage, an account that may exceed available license or term limited license have expired. So you can see here right on the right, we've got a whole bunch of different boxes that you can check to get notified on. So if you're the person in charge of managing this virtual account or this smart account, I would highly suggest.08:28Setting up this preference tab so you can get email reports on this because you you're gonna wanna know when you have insufficient licenses or when licenses are about to spy, expire and you don't want to come in here and check every day. So it's much easier to come in and just set up a preference.08:48Alright, let's move on to integrated reporting. If you've never used this reporting, it's a good, quick easy way to either get a CSV file or an Excel Excel spreadsheet.09:05Everything that's in SSM. When I say everything that's in SSM, you'll see the license deposited, license used, the product instances, so you'll see any products that have been registered. What you won't see is if you have products that have not registered. If your product is not registered with the SSM, then you're not gonna be able to pull any information on that.09:21Now, we've got three different license types or license reports here. We've got the license license subscription and the product instances. Your license report is a summary of all the current license counts and usage over a selected virtual account. The license subscription is a summary of the current subscription license counts and the exp.09:40Expiration dates over the selected virtual accounts. So that's really good for tracking when your license are going to expire.10:00Your product instance report is a count and a listing of the current current product instances for the selected virtual account, so you can see which devices are attached to which virtual account using that report.10:06That's really nice if you're like looking for a specific account or you wanna or a specific device, you wanna make sure that it's attached to the right virtual account, so you're consuming the right licenses and not stealing, you know, maybe another department or another organization's license if they're all under the same smart account.10:21Okay, when running a license report, we get information on how many license we have, how many are used, what's available or what's in reserved. Let's give an example here. You can see that we have 250 5501 SE hardware tracking licenses and.10:44That all 250 of them are gonna be available right now.11:04If these licenses are coming from a fresh order, then we can assume the devices have not arrived yet, and then that this output is what we should expect. Otherwise, if we know, these devices are we suppose that these devices have been deployed or installed or the install.11:07Has started already, then we can go ahead and tell that something's not right here because these tracking license should be.11:27Used, at least some of them should be used. If you've got one device registered properly, it should consume one license. So this gives us calls for concern if we know the installation's already started. With the license subscription report, as I mentioned, it's gonna provide us with a summary of the current subscription license counts.11:34Expiration dates over the selected virtual accounts. And on this slide here, you can see that we have.11:54250000 hundred gig SIA essentials and advanced core licenses and you can see that they're expiring in 2027. So we can go ahead and use this report to start planning for future purchases and you know getting the money accounted for that or knowing that, hey, these devices are gonna be unregistered.12:01At this time, we may run into errors.12:20So for the final report, the product instance report, it details the account and the listing of the current registered product instances for the selected virtual accounts. Now, I said for the selected virtual accounts, that's because it shows you the router attached to the virtual account, so you can see that in the.12:24Report breakdown. And what this does is this gives us an idea of how many products are gonna be registered at the SSM and then you can compare it with your expected number. So if you're expecting a hundred routers to be, you know, registered and installed and you pull this report and you're only seeing 50 associated with a certain virtual account, you know that those.12:43Routers are either not installed or that they have not registered properly with the SSM.13:03Which means they were NO longer, they will eventually run out of compliance and they're not gonna be consuming any licenses. Okay, so we're about to do a quick talk about reporting automation. Are there any questions on what we've gone over so far?13:08No hands raised, but if there's any question, please feel free to ask. Okay, so moving on with the reporting automation. Using the Cisco API developer portal, you can register your API client and get an API key as secret to access.13:29This the smart accounts and your licensings API.13:48You'll see this website, I'll show this to you in a few minutes, but once you have access to this, one of the API calls available to us for the reporting is the smart license usage. Now, this API call gives us the license usage.13:53In the specified smart account domain and the optional virtual accounts. So you'll be able to come in here and click on it and then start searching in a smart account down into a virtual account and looking for specific parameters. And this example here, we're using postman for the demonstration to get.14:12Gets smart license usage from our domain. So we can limit the request by the provided array of the virtual accounts and postman also has the ability to generate a code snippet for your desired programming language. And you can see on the right, in our example, we use Python. Python is what we're most familiar with.14:32With so that's what we used here. So you could use the Python code or you could use Postman to return this information.14:52Another API call, that we like to use is for the alerts, and here we specify a single virtual account with only major alerts and the smart account and licensing API can be integrated into your management system to get the license compliant availability reports in a way that.15:00That you know that you most desire.15:20So let's take a look at this website really quick. So this is the website we showed you in the slide, and as you can see, we've got a new one, so it's being replaced with the Cisco new IT API portal. So this one is still up and running, so you can still use it. But if you click on here.15:23It's gonna take you back one. Okay, so it'll take you here. You've got customer assets. The 1st thing you're probably gonna do though is come down here and learn more and you wanna learn more because you need to get started and you need to just request your API.15:43Access so you can come to request api's access steps for API access request and just follow the instructions to get the API access.16:02Now, oh, sorry I have that one still up. Once you do that, you can come back in here, go back one, and you can come to customer access or access.16:11Now, here you will be able to see all the different things if you want to pull in API for you've got licenses, you've got smart accounts, enterprise agreements, software delivery. So if you're looking for smart accounts, you click on smart accounts, you've got user management, virtual accounts smart accounts, we can spend up smart accounts again.16:28In.16:47You got smart accounts, you can download specific look, let me click back over here. If you come down to the API reference, I'll lose it. Request to access my apps, so you can just come here and click on the different parts that you need. But once you get down.16:50Down to.17:09Your smart accounts overview in the API, you'll be able to get to where you can actually see the different types of APIs that we have. So we got validate user access, validate user access version one and version two. Smart account search is what I have here and you can see the type of API call that we have and then we just add in.17:10You know, domain or limit or name. If you're not familiar with APIs or you're just now starting to use them, if you scroll down, they've got really good, they do a really good job of giving you a schema of definition example bodies which you can use. And you can also click right over here.17:31Select what you need, and then if you hit run, you need to add headers. I don't have a header or a key right now. If you had to run, it'll actually build you out a, example of what you need to run this type of configuration. So you can build your own API call right off of this.17:49Website here.18:08Any questions? Okay, the other thing that we covered here was software central. So this is our SSM. Now, this is the web hosted version. Your on prem version will look slightly different until we actually click into it, but.18:13The two main features that you'll end up using here is managed licenses and a managed account. If you don't have a smart account or you need to get access to a smart account, you can come down here to smart licensing, submit request for an existing account, try to create a new smart account. But.18:31These are mostly what we use because most customers already have smart accounts created. Manage account is where you'll go in and actually start doing user access, maybe making new virtual account, get someone access to a virtual account, change your roles and rules. License is where you'll do most of your license, and this is where all the reporting is.18:48So if I click on manage license, the 1st thing I want you to notice, this right here is going to be the smart account that you're in. If you have multiple smart accounts, when you click this dropdown, you will see them listed and you'll be able to click on them. From there, we've got our alerts right here at the top that we mentioned. So we have a hundred and 98 major, 300.19:0858 with 50 minor, and you can see our license right here or our errors right here.19:28So insufficient licenses, we can do transfer licenses giving us message. Moving on to inventory, this will be where you need to actually select a virtual account. So virtual account I'm gonna work in is FCM demo.19:34Here, this is where your token registration is if you're already registering or if you're 1st time registering a device, our license, this is where you'll see all the licenses that you have. We've got a nice search bar, and if this isn't working, you can use the advanced search and search by.19:51Product family, customer PO, subscription ID when you bought it. Once you find your license, you can expand it and take a look at different ones because they're grouped. So this will be all the 82 oh ones, but as you can see, we've got.20:08This is a bad example because they all have the same expiration date, these must be followed at the same time, but you can find some that will have different expiration dates even though they're under the same licensing. So let me see if this one will do it. No, these are all bought at the same time.20:22Okay. Next we got product instances. This is where you'll see all the products that have been associated with this virtual account, and you'll be able to come in here and find different information for it. So you've clicked on it, you can see that it was an 800 series.20:40Okay it was 8201, you can see the serial number virtual account that was associated with. Now this is a lab device which we connect and disconnect, which is why you see that it's failed to renew at the time. But this is where you'll find that. You also have your event log for different events.20:56But today we're mostly interested on reports and managing this. So I really want to show you this preference tab. The preference tab is what I mentioned earlier, where you, if you're managing a smart account or a virtual account and you want to get updates without having to log into this everyday, this is where you're gonna come. So you can.21:13Look at your reverb reserve license pre installation, you can select virtual accounts that you're interested in universe universal license re reservation enabled, disabled, but right here is the notifications. Receive a daily email summary.21:36For the events below. I've already registered this, my email, it's like virtual accounts I've got them all, but you could actually come down here and pick different ones. You can add different email addresses if you've got a backup, maybe you're going on vacation and you need somebody to cover for you.21:49And then, what do you want to get notifications on? Insufficient licenses, license expire, one day, 30 days, 90 days, how far out do you want to go? And, do you want to receive a on prem synchronization?22:04Email, so do you want to know and verify that your on prem is actually syncing with this? This is a really good one because if you're on prem and your web based or our web host one, you come out of sync, you're gonna get miscommunication with your licenses and you'll have devices possibly starting going out of compliance.22:20So the last thing I want to show you is reports. So you got license and product instances, if we click on licenses, license report, all virtual accounts, selected virtual accounts, you can search with tags.22:38Oh, uncheck all. So we just run one license report on that. All licenses export XLL, XML or CSV.22:56And you'll get something like this. Now, if you're looking to track how many licenses you've used or what you have, you've got it all right here. These are your licenses in this one. You can see what's been purchased, what's available, what's currently in use, your balance.23:15License detail, you'll be able to come in here and see your subscription end date, that would be important, your start date, the term, which virtual accounts are associated with, all, all sorts of information in here, and then which devices are actually pulling licenses. You can see by the.23:34Serial number. Alright, so let's go back to the demo or demonstration. Okay, we're about to move into FCM automation with netconf. Were there any questions over what we covered?23:53Okay. So for this section, we're gonna see how to enable routers for netconf. We'll take a look at automation with netconf console, and then we'll see a little bit of automation with Python. Okay.24:12So enabled routers for netconf. So if you've never worked with netconf before, what you're gonna have, you're gonna have a netconf server, a netconf client. So maybe like a Ubuntu device or wherever you're running your netconf, and then like an I/O six R router. What they're gonna do is they're gonna go ahead and.24:31When you connect them, they're gonna exchange information. And what we're really interested in is the hello message exchange. When they 1st connect, they're gonna exchange hello messages, which is basically they are talking to each other and they're exchanging what their capabilities are, so they're letting each other know what they can do.24:48Okay. Now the reason we're interested is because with netconf netconf, you're basically netconf, it's a transport protocol protocol for XML, which is the encoding for yang. So it's.25:07Yang data model, which is what, you know, kind of dictates some of our six R router like configurations is gonna be encapsulated in XML and then the transport is gonna be netconf. So we're gonna use this and manipulate this to pool information that we want.25:23So if you see right up here at the top, this is an XML and we're doing a get config because we got different operations with netconf. We've got git, get config, add config copy config delete.25:38And what we're gonna do is we're gonna pull and use different ones depending on if you want to get information set information, replace information, delete information. So with this, we're doing the git config, we gotta give a source. Now the source or an iOS XR could be like a.25:54Candidate database or it could be a running config. Now, if you're doing a good config, you're gonna use a running config. So we're selecting running config and this would just give us everything that's in our running config. If we want to.26:12Filter this down and get something smaller. What we're gonna do is we're gonna add in this netconf filter here. So you've got same thing get config source running config source filter. Now filter is where we're gonna add in basically this XML coded yang, so right here we're gonna give our Yang data model, so we're using Cisco.26:29So I will say IOS XE-native.26:48And if you've ever looked at netconf, not in netconf yang before, it's basically a bunch of containers and dropdowns like you see here for, for this case, your configuration. So if we want to interface information, we would just put in these XML tags and.26:52Interface interface, so we're gonna gain the interface information. Now, because there's more than one interface, we're gonna get all the interface lifting.27:12Listed. If we want to filter that even further, we'll dropdown in here, you can still be using the same Yang model, but inside interface, we know there's a gigabit interface. So would you put in the gigabit interface and we got our opening and closing, and then what are we interested in? Are we interested in everything? No, we're interested in name, so we'll put in the name.27:21Which would be one of the leafs under this.27:40Container here. So we'll just pull back the name information for the gigabit ethernets and this would be every gigabit ethernet because we didn't set like a port or a single port or, you know, it could very, I'd have to look at this exact Yang and see what's under gigabit ethernet.27:43Alright, so this section going forward focuses on the automation using netconf. And obviously the 1st step is gonna be enable netconf. So we're gonna use this show netconf yang status command to verify.28:04The netconf status, but basically this is the commands you would use on like an ISO six R router. Now this may differ depending on which version you're using, but this is what has worked on the eight thousands. Alright, so let's get started with this automation with netconf.28:22Okay.28:42So, your netconf console is gonna be a console application for interacting with your netconf servers and is built on top of the NC client, which is a Python library. Now here we're gonna look at how it works and how it would serve as an enabled.28:44Meant for your automation ideas.29:04Now, as you probably know, there's many different tools to interact with Netconf enabled devices, and here we're going to use the netconf console two. Now on the screen we can see the URL and where to get the tool from and the command to install, so you can see that we can download it and we can install it for PIP install netconf console too.29:11When establishing a netconf session with a device, as I mentioned, a complete list of all the capabilities in Yang models supported by the device is going to be exchanged with the client. Now, all the Yang models supported by the device are included in that hello message.29:32So we can use the show netconf yang capabilities command to show what's supported by the device and then what is expected to be received during the session establishment. So.29:50This is the IRS device here on the screen. We did the show netconf capabilities. You can see the capabilities, obviously some of this has been deleted just so it off in some screen. But when they do the hello message, when we check the capabilities on the other device, this is what we should see as well.30:01So to test the netconf sessions establishment using the netconf console and asking for a hello capabilities only. So basically, this is where we're doing dash-hello. So netconf console host, we got our host IP, we've got a port. At the end we're doing dash-hello. So we're seeing what the capabilities were sent with the hello, and this should match.30:20What we saw on the router.30:40Now, if we're interested in using licensing support and we want to confirm the router has required models in its capacity list and the netconf console receives it as well. We can do at the top, you should have to show netconf yang capabilities pipe include license, and then at the bottom, well, we get the Yang model.30:45Was associated with licenses.31:04Now at the bomb, we're basically doing the same thing but Linux styles, so we're doing the hello pipe grip, include licenses and then you can see the yang model supported that were received as supported. So to move forward, we need to know which Yang models to use to work with licenses on our routers, and we can use.31:06These data models for all the smart licensing operations such as registering your device with a token, renewing token ID, deregistering devices to remove the software entitlements and you know.31:26So when we're doing this all with netconf remote RPC calls. Now, configuration data is a set of writable data which is required to configure smart licensing on a router.31:37On the left side, we can see the Yang data model for a small license con configuration, and on the right you got corresponding CLI configuration commands. So basically these are the commands that are associated with this Yang model because this is gonna be the configuration data CFG is configuration.31:52Operational data, is a set of data that the system attains at runtime. Now on the left, you can see the Yang data models on the right you can see clis, they'll give you the same output. So common data model, Cisco smart licensing.yang native data model, Cisco lives.32:13Sorry, my smart licensing platform operational, and then these are the corresponding.32:33IOS XR router commands. Now, we also have actions and action is a set of netconf actions that support robust network wide configuration transactions.32:39So that again on the left you can see the Yang data model for actions and on the right you can see the CLI commands matching those actions. On this slide, we see the content of sL_FCM_config.XML file.32:57And we ask here for a running configuration and we filter it for FCM. Now the RPC call returns NO data because there is NO such configuration yet. So basically we asked for.33:17The FCM is the FCM enabled. We want to check and see if FCM enabled, but for the device that we're pulling it doesn't have anything so we're getting an empty reply. To enable FCM, we're gonna use the following XML here.33:31Now, in our 1st example we showed you a get config. Here we're using an edit config and we're doing it to the candidate data store, so it will not take effect unless we, followed up with the commit. So we need to send a commit after the configuration is edited. So.33:52Target? This is just like the source that I showed you earlier, but we're doing candidate because you've got the two stage commit in the islands are, so you've got a candidate data store and then what we're doing, we're checking or we're editing config, we've got our Yang model.34:11Flexible consumption and we're setting it to true. You see that right here inside our, in between our two XML tabs. Now, then we're gonna have to send a second XML for the commit, and let's see what that looks like. All right, so we use the XML file with the configuration following the commit. You can see.34:27All right, we got our host port RPC call, we're sending the 1st XML over, which set it to true, and then we're following it with the XML of commit, so we're following with the commit, so you can see that the 1st one we received the ok.34:48And we receive the ok. So now we can see through the configuration command that it was added to the router. So basically show run license smart flexible consumption enabled, you can now see that that router would be enabled.35:03To do the same thing. If we want to do a sh using netconf, you can send the XML to pull the information because we've got the filter in it and you can see that it is true and this is they're using the same Yang model.35:19Okay, next device registration. So the SL_registration UNDERSL token.XML file has XML with token from our SSM virtual account for the device registration. Now, this is the equivalent of a license smart registered ID token command and sending the.35:39RPC to the device, we're gonna get an operational status of success and registration in progress.35:58So, you can see we have ID token tag here and the ID token closed tag here. So you would just put in your token here that you received from your virtual account. Then we're gonna send it RPC.36:04Token.xml. All right, success, registration in progress. After the registration request is sent to the device, you know, you'd like to get the registration state and we have an XML file for that. So we've got to get.36:19Filter, what yang, our model we're gonna use, then that we've got our different containers, so licensing state state information registration, registration state. So let's see what the registration state is. Once the registration is being completed, you run that.36:34XML file we just showed and you can see that we're getting a registration of complete. Now, you may want to check the authorization state of the device and for the authorization, we're gonna query the authorization state. So same thing as last time we gonna build an XML or.36:52To finding XML already built for that, but basically we're using to get, the filter, the correct smart license or the Yang model, and then we're just gonna follow the containers down to the information that we would like.37:12Now running the request you can see that it is now authorized. Now, you can do the same thing for license usage. You can see we've got the get the filter.37:27Same smart licensing gang model and then we just break it down to what we're interested in receiving. Moving over to the next, you can see that we're going to get a list of all used license in their state. You can see.37:41Advantage under gig RTU-one count we've got two is in compliance. You can see we've got another one NCS 55A2 in ODS tracking license count one in compliance, and this will just repeat on.38:00Until we ran out of all the licensing. Okay, so let's move into this quick demo alright.38:15So we've got two different routers here or one router and one Ubuntu where we're running our netconf from.38:35So the 1st thing we want to do is we want to show our dev conf capabilities. So on the router show netconf yang cap capabilities. You can see all the different Yang models that we have in the different types, right?38:43Now, we want to verify that this was copied into our Ubuntu over here. So what we'll do is we'll check out our command that we saw in the slides.38:59Our host support and then I'm double check, checking the hello to make sure that they're going to be similar. So you would see that what you see here is what you see here. I'm not gonna go here and check one for one for these, but you get the idea that these capabilities were exchanged over here when.39:16They did the hello.39:36Alright, so let's see a couple examples here in the right folder I am. So in this folder we got a couple of different xmls already built. So let's take a look at this 1st one, the registration one. So for the registration XML, you can see we got get filter, we're using a specific.39:40Model and we're doing license state license registration state, which we're building that all the way down.40:00So basically this is gonna be a Git config for specific information which will be, you know, our registration state. If we want to run that netconf host, and you can see, here we go, registration state XML, that's the one that we just checked.40:06And you can see currently that it is not registered. Let's check another one.40:28So, oh, should be the same one, my bad, let's do a filter instead. So for this one.40:39Usage filter, what are we looking for? State information, short name count. All right? So let's run that command, and you can see that what we should should be pulling.40:57Billing is an 8201 tracking license for in the valuation mode.41:17All right, and we can keep doing this and looking at different xmls, so where was it? Okay here it is. Lost myself 1st thing. This one we gotta get filter.41:21And we're looking for a smart license operational, but it's not operational, so you're not gonna see anything at this moment. Now, if we want to register a device, as you can see over here, oh, that's ok. We need to move back over here.41:38Show license summary. You can see currently enabled but it's unregistered. So we're going to go ahead and register a device. Now, before I register it, I want to show you this right here.41:54SL_registration token. So we've got the XML for the token and I've already taken and put the token in here from our smart account. So this is what we're about to run.42:12Alright, I will run that using our netconf and.42:25We run into an error.42:45Try that again ok I pulled the wrong XML last time. So we've got success, we're running the correct one now and the registration in progress.42:51So let's check again over here on the router, and we are registered now to CS demo labs and the virtual account FCM demo. And so we saw that on the router, that was verify it through netconf.43:10Using the RPC registration state XML, and you can see that it has been completed. Now, if you're wondering how we can build these xmls, the best way is to use.43:26Either cat one of these yang files or you can use different software I think Yang suite or Yanger do the same thing, but we also have this right here. So Cisco feature navigator. If you come to Yang data models under the Cisco.43:43Feature navigator, you can pick the router that you want. So if I pick a thousand series router, seven.five.one diversion, submit it, gives you all the different Yang models, right? Now, if you come in here and search for ones that deal with specific licenses, we can look at that one. So we got.44:02License iOS XR smart license config. If we click on this, this is what your XML basically would look like. You have licenses flexible consumption, then you have different leaves. So this is a container, this is a container, and then you would have different leaves. And each one of these leaves would be some of the data that you could pull. If I.44:21I was in like.44:41Interface configuration and this is interface, I would pull all the different interfaces. If, you know, I wanted more information, this could say interface, this could say gigabit ethernet, and then we would have like name or port or description underneath that. So you would just be basically working your way down these.44:43Using XML open and closed tags.45:03Any questions over this? Okay, so let's go back to the demonstration just for the last little piece here.45:08So, automation with Python. Now, in this example, we're going to be using the NC client Python library. Now, the same library or this is basically the same library that's used by the netconf console tool that we just saw.45:24Now, we're doing, we're gonna do a couple examples here that's gonna give you an idea of how to start working with it. Now, 1st we need to assume that Python three and NC client are installed, and then with the NC client manager, we're gonna connect to the specified device and get the server capabilities.45:42So, from NC, NC client, we're gonna input the manager. And if you've ever looked at this, the manager's gonna give you, there's two different ways to basically connect with manager, you know, with manager and.manager, but you can look into that, but we're gonna set the host the netconf port username password.46:01Create capabilities, capabilities we want with manager connect, this is basically how we're connecting to the device. Now, we're setting this manager connect as device, so manager connect is gonna be device. So basically it's gonna be like almost the start of.46:19Your capabilities are almost started like your Yang models and we're gonna say we're going to look for server capabilities. So what capabilities does this server have? Now using the same approach here we get the router's configuration and apply FCM filter to get only the relevant.46:35Part of the configuration. So this should all look fairly simple right here, says device and we're gonna print, you know, netconf SCM configuration for devices print the running filter, and then the filter is gonna be the sub tree and then the CFT filter, the CFT filter.46:53Which is here, CFG filter, what are we looking for? FCM, ok? Is FCM enabled? Any questions?47:11Okay. Now, the script just prints the reply on the screen, but you know, you can further parse that output for other use cases. So you can see this is what it looked like if we run it.47:30The Python we just got, hey, FCM enables true, but you could see how you could take this and run this Python for, you know, a hundred devices with a little bit of modification and say, hey, is the FCM enabled true? Hey, what is the license status? You could build this out for your use case.47:46Now, having a list of all our devices and knowing how to get the information from routers using netconf, you basically can fully automate the configuration and reporting. And here on the screen is basically an example of simple reporting example using the same FCM registration and FCM status yang.48:08You've seen with the netconf console tool, so you could run your own report SL-report and get, you know, device SCM registration SCM status for each device complete, not register, authorize the evaluation. And of course you could do this for a hundred devices if you had a hundred devices, which could possibly make things much quicker in your network.48:26Okay, so let's do a quick demo of that Okay so we got a couple of different ones here and what we're gonna do is we're going to run the capability, so I'll show you the capability.48:49It's 1st.49:09You can see it's what we covered in the slides here, right? And if we go ahead and run that, you can see all the capabilities that came for this device.49:12Basically like checking that hello message.49:32That shows you all the different Yang models, ok? And you could go through and parse that and see which ones you wanted or rewrite the the program file. But you can see how you could take this and write for many many devices, right? Okay, let's on.49:35To our final piece here. So the final piece here is gonna be the SI capacity management examples. We're gonna have three different scenarios, A, B, and C, where we run through basically.49:52Is your SIA compliant and are your routers gonna be are basically your router upgrades gonna be blocked because you're out of compliance? Okay, so our 1st scenario.50:08Let's say we have 500 RTU licenses and 500 purchased SIA subscriptions in a virtual account, but only a hundred RTU licenses are configured and in use. Now, the customer has purchased 500 essentials RTUs and 500 advantage RTUs.50:23For one platform.50:43And our example is CNCS 5500 and these licenses are gonna be deposited into the virtual account. Now, the customer has 500 purchased essentials SI subscriptions and 500 purchased advantage SIA subscriptions deposited into the virtual account, which is gonna equal the metro.50:45Toronto. The customer also has a hundred essential RTUs and a hundred advantage RTUs configured and in use only NCS 5500 routers in the network. All the NCS 5500 routers are registered with the CSSM.51:05Now, the customer's last communication about license usage to the CSSM was on 1123, ok? So 1 January 2023. After that it lost connectivity.51:24So let's take a look at this time frame in a little bit more detail. The last communication from the CSSM about the router usage was on 1 January 2023, then the router's lost connectivity. So we have NO license over usage here. So we've got a hundred used and 500 purchased, you've got more than enough.51:43But your authorization expires in 90 days, therefore, the routers are incomple, in the incomp they are excuse me, the in compliance state. So right now you can still do an upgrade.52:03But if you still have NO communication for the SSM, when the authorization expired after 90 days, the router moved into the out of compliance state and the SIA grace period has started. So that adds another 90 days of the grace period.52:16And an upgrade is still gonna be possible because you're in this grace period. All right? After the hundred and 80 days, the upgrade is not possible anymore because the routers are out of compliant and they're out of compliance because they have not been reporting their SIA information or their license information.52:32To the CSSM. So regardless if you bought enough license like that we did here and you're not using all of them, you can still end up having your upgrades blocked if you're not reporting because you have to have that communication so that it knows that you are in compliant.52:52Okay, so let's look at 2nd scenario. 2nd scenario we have a hundred RTU licenses and a hundred purchased SIA subscriptions in our virtual account, but 500 license are configured and in use. A customer has purchased a hundred essentials RTUs and a hundred advantage RTUs for the NCS 05:40 platforms and these li.53:14Licenses will be deposited into the virtual account. Now the customer has a hundred purchase, excuse me, has a hundred purchased essentials SI subscription and a hundred purchased advantage SI subscription for your NCS 05:40 platform, and these were also deposited into the virtual account.53:34The customer also has 500 essential RTUs and 500 vantage RTUs configured and in use on the NCS 05:40 routers in the network. So all the NCS 05:40 routers are registered CSSM. The last communication about the license usages was on January.53:541st 2023. So let's jump in and look at this timeframe again. Now we don't have enough available licenses on our SSM virtual account. So the routers move into the out of compliance state and the SI grace period starts.54:11Upgrade is still possible. After 90 days of the grace period, the upgrade is NO longer possible as the evaluation period is over, ok? Now for scenario three.54:29We have unregistered routers in the network. Now, we have purchased five ASR nine Ks and four of the ASR nine Ks are registered at the time that the upgrade is attempted. The 5th ASR nine K has not been registered within the 1st 180 days of being installed in the network.54:46So basically there that last one, that 5th ASR nine K has already passed a hundred and days, a hundred and 80 days of the 90 day evaluation period and the 90 day grace period. So your ASR 9K1 through four are registered and reported to the SSM. The virtual account has enough licenses. Routers are in the.55:05In compliance state and the upgrade is possible. But for the 5th ASR nine K, which has never been registered and the SSM has NO knowledge about this, the router upgrade is gonna be possible within the 1st hundred and 80 days because you got the evaluation of 90 days in the grace period of 90 days, but after that.55:25As you can see, once you pass the hundred and 80 days, that upgrade will NO longer be available on your ASR nine K for the 5th one that was never registered to your SSM. All right, so that concludes today's webinar. Are there any questions or anything we.55:45You can clear up. Thank you Robert for the presentation and the demo, personally learned a lot too. Are there any questions for Robert or Amir please feel free to raise your hand.56:05Or post them on the chat window, but since we've completely concluded the session today, that ends our session for today, and we will meet again next week, the same time to to review the final session we have in this series.56:24Thank you all for your time today. Appreciate you joining us. Thank you.56:44