Cisco Smart Software Manager (CSSM) Overview

Welcome everybody, good morning and welcome today is 2nd session of our FCM expert series on the topic Cisco Smart software manager overview. Our.00:05Panelists for today are presenters and panelis panelists are Robert Hoffman, Amir, and Gopal who are the customer success specialists who will be taking over the presentation from here. If you have any questions, please feel free to post them on the chat window or raise your hands and I will unmute.00:20Like you to to ask your questions. Let's try to keep this series as interactive as possible and I will post the links where the recordings and the presentation will be made available for the FCM series and thank you again for taking the time to join us on this journey of expert inside series.00:40With that, I will leave it to you. How Robert, please take it away. Thank you.01:00Alright, welcome everybody. So this is the F FCM expert series. Today we're gonna be talking about Cisco Smart software manager overview. If you've got any questions like said, please unmute yourself if you're able to raise your hand if you're not, you can ask me directly or I've got two panelists here. I have Amir and Gopal who'll be.01:06I'm more than happy to help with any questions that we have.01:25Alright, so today's discussion, we're gonna talk about the CSSM on prem, we're gonna check out the overview, the install and the setup. We're gonna look at some product registration for your CSS on prem, and then we'll have a demo for you. Okay, let's go ahead and get started with the CSS on prem overview.01:28All right. So we've got a couple of different ways that we're able to hook up this CSSM on prem. So 1st, as you can see here, we've got the direct cloud access. This is what we showed, last week. This is where we have our Cisco products are speaking directly with our CS or our CSSM, so our hosted server. So our web hosted server.01:49Here at Cisco and we're getting the information.02:092nd way we have, we're able to connect and get our license information is through an HTTPS proxy. So this is where your Cisco products, you'll go into your call home, you'll say, hey, we're going to use a proxy, you'll bring your proxy command, you'll densen your information through a proxy then to our hosted web servers.02:12And we'll gain the license information that way. The last two is when we're going to be using a CSSM on prem, which is what we'll be talking about today. Your CSSM prem is basically a.02:31Almost a mirror image of our hosted web service, but you'll just deploy this inside your network. You'll spin this up on Linux VM and then your Cisco products are actually going to register and talk to your on prem just like you would our software essential, and then.02:48Our on prem or your on prem server will then relay the information back to our web services. So you'll kind of be able to use these two in conjunction and pass the information. Then lastly we have the mediated access for the on prem. This is where it's disconnected. So you'll still install a CSS on prem. You'll register your products.03:02Still talk back and forth and then you'll have to kinda email sneaker net or move over.03:22A product file from your CSSM on prem to our Cisco service to update your usage, and this would be more for like financial institutions, military services, things of those natures. All right, so.03:27What is the smart software manager? Well, the Cisco smart software manager on prem is a component of the Cisco smart licensing, and it works in conjunction with the cloud based Cisco smart licensing or a smart server manager, to basically intelligently.03:47Manage your product licenses, and this will provide visibility and reporting of your licenses that you purchase and consume.04:07Now, the on prem is a openprint version of the CSSM and it can be downloaded free of charge from Cisco.com, and it was created for the customer who basically has strict security requirements and they don't want to.04:16Or they really don't want their products to communicate with the central licensing database or our CSSM or cloud CSSM that we have, and they they basically don't want a direct connection. And as I mentioned earlier, this is most often used by like financial institutions, service providers government entities, things like that, that nature who much rather have their.04:34Licensing information stored in house. Alright, once your CSSM on prem is installed, on your premises and you get it registered with Cisco, your devices and your software products, they're gonna self register.04:54And report license consumption to your CSSM on prem as you would do your normal CSM or our web based CSS.05:14Or SSM, not CSS excuse me. And then the way they update it is your on prem is going to periodically synchronize with our cloud service and you're going to update.05:23Any information you have. So if you install a new router, your new router connects to your CSSM on prem, they exchange, you consume a license, it knows that you consume a license. Based off whatever schedule that you assign for that on prem to talk to our central server, it'll send a package and it'll say, ok, he's used.05:40In this much or this much is how.05:59You know, he's consuming five licenses or he was consuming ten licenses, now he's gonna consuming four license and they'll kind of update that way. And we'll go a little bit more in depth of that in a few slides. Alright, let's talk about these benefits for the on prem. 1st and foremost, is gonna be security.06:02So your on prem has a similar experience also as your direct cloud access, but it's got higher security. You know, some users may not want to connect to your your SSM with direct internet connections, but with the on prem, you can have a secure on premises.06:21Single source of truth of your license consumption.06:42Second, you're going to receive near real time license entitlement based on the synchronization schedules that I had mentioned. Additionally, because your CSSM on prem is a component of the smart licensing, users.06:45Are also going to receive the benefit of the smart licensing, which is gonna be included. So basically you're gonna have a full view of your licenses and the devices all in the centralized location. So when you connect your licenses and you start pulling the pulling licenses and your product will registers with your on prem, you'll be able to go into your on prem and SE.07:03The the exact same thing that you would if you log into our actual like SSM server. Now the on prem is targeted for small enterprise customers as well as service providers and.07:23It's also targeted for Cisco partners and large enterprises who really want the ability to manage their own, accounts and multiple customer accounts on a single portal, which is a term we call them multi tenancy, and this is all gonna be done through the on prem prem platform. Now the application.07:43Scales up to 300000 product instances and 500 local accounts. It also provides options for online and offline connectivity as we had mentioned.08:03Okay, let's talk about how we're going to access this and what we see when we do access. So to support your CSSM functionalities, there are going to be two portals. There's a licensing portal and the administration portal. The licensing portal has similar functionality to our software.cisco.com, so our.08:19You know our hosted web services, and it's gonna allow you to.08:40Manage your local accounts, your user, your users like your product instances, devices, and all the licenses. In addition to this, the account management function, which is going to be similar to the account administration was added to this licensing portal, and this is where users can create new on prem accounts.08:45Request access to on prem accounts and basically do any type of management for your on prem, for your virtual and local accounts. The administration portal functions separately from your license portal, and it allows for internal administrative functions such as user control, local account creation.09:05Registration synchronization, along with your network system and security settings. It also has options to configure features such as external authentication, syslog, and proxy support.09:25Now, just like our SSM, there are gonna be different roles that users can have within the licensing and administration portal. In the licensing side of the portal, systems users can be assigned the role of a local account user, a local account administrator.09:40A local virtual account user and local virtual account administrator, and these roles function similarly to your smart account and virtual account on your SSM, but they're gonna be at the local level within your on prem deployment. So basically the same thing as your SSM except it's.09:57Locked down to your on prem, and I said that back, it's the same as our Cisco hosted license portal, but it the administration has locked down to this only to this on prem. Now within the administration portal, users can be either system administrators.10:16System operators or system users.10:35System users have read only permission on the administration portal and have role based access control in the licensing portal. Your system operators have full admin access to all local accounts and can perform SSM on prem registration and synchronization in the admin portal, but they cannot.10:38Change any system configurations.10:58Your system admins have all the abilities as a system operator plus they can approve and delete local accounts and configure the IP addresses syslog and proxy for your on prem. So essentially, the difference between the system admins and the system operators is that the system admin can.11:01Change system parameters where system operators cannot.11:20Alright, let's understand the two modes for this deployment. We have your CSSM on prem, which can be deployed in either connected or disconnected as we mentioned. The connected mode is used when there is connectivity to cisco.com directly from your CSSM on prem.11:27In this mode, your license consumption entitlements can be synchronized with.11:48Your SSM on demand or automatically through daily, weekly or monthly scheduling. Now the connected mode is the standard mode and it's the easiest to deploy. The disconnected mode is used when there's NO connectivity to cisco.com from your CSSM on prem.11:55And this mode, the on prem can be manually synchronized with your SSM via a file upload or download. Okay, so we've covered what the CSSM on prem is. We're gonna talk about the installation. I'll pause for a second. Are there any questions?12:14Yeah hand raises. Okay, let's talk about this installation then. So David has a hand raised. Let me unmute you David, 1 s.12:33Please, please go ahead. The local accounts on the SSM are local only. They do not need a Cisco account to log on to this device. Is that what you're saying? I do not believe they need a Cisco catalog onto that one.12:52Amir, do you know that one for sure? I'm not 90 % sure you don't need a Cisco account for that. Right, yeah. The the local accounts do not require a, a CCO login. Only instance where you will actually need a CCO login is when you're doing the initial registration of and mapping.13:11Your smart account portal on the web and pushing that to a lo as a local account on the on premise server. That's the only instance where you'll need a single sign on login with your cco ID. But after the registration is completed, you can add local LDAP users without them having any Cisco credentials at all.13:31To just local users added to the system who can access the on prem.13:51Okay, thank you. Appreciate that Amir. Are there any other questions before we move forward? We got, we are good to go Robert, thank you. Thank you. Okay, so let's look at the installation. So we've got this installation checklist here. The 1st thing you're gonna need obviously is an on prem item.13:55Or ISO. Now, as we mentioned, you can download these from software central Dark.14:16Come or excuse me, software downloads.com and they are a free download so you can just go out there and grab the latest version. With the version you'll also need to get the on prem installation guide that will actually come with your deployment or you can check look it up individually. You'll need to understand what type of deployment you want. Are you going.14:20Going to go with a standard or a STIG environment and we'll cover that in a couple of slides.14:40You'll need to know your IP address, in your mask, your default gateway address, your DNS server address, and you'll go have to go ahead and decide on what password you want. Now, with our passwords, like most things now is a minimum of 15 characters, and it's gonna have a mixture of uppercase lowercase numbers and special characters.14:45Alright, so this on prem can be deployed on a physical server as well as a virtual machine, and the installation should meet the following requirements based off the number of products that you plan to license. So if you're doing a small medium, large or maximum, you'll need a.15:05Look at your corresponding hard disk memory and CPU. Now, with this, I want you.15:25To, always check your installation guide because we're always pushing out new versions of your on prem and you know you maybe getting version nine.zero or nine.three. It could change or vary so always check this. This was the last time we checked but please.15:30Look at your hard disk memory and CPU before you actually begin your install. Okay, in our example here, we're gonna be using the VMware vSphere, vSphere excuse me, and we're gonna start by creating a new virtual machine.15:50So you see we select creation type, create a new virtual machine. We're gonna give it a name. I'm just gonna name it on prem, but you could pick obviously a more appropriate name based off your company or whatever your uses are. Now I did just skip a few steps like compute resources, storage selection, and we moved.16:06Straight to your guest OS screen. Now, we need to make that make sure that your OS type is we set to Linux.16:26For this, alright, and we probably wouldn't be set to Linux or Linux other 64 bit. You used to be able to use Centos, but I don't believe that Centos is supported in the newest version. Is that correct Amir? Centos is NO longer supported.16:34That is correct. The, the most recent version of of your on prem are is alma OX because CentOS has already reached the end of life milestones. So the newer releases and the most recent releases of your on prem, starting from believe I believe version 920247, this.16:53The guest OS would be on my OS but upon when you're doing the install you can just select the Linux kernel, and that should still allow you to set up your on prem on the on the virtual machine.17:13Awesome. Thank you, Amir. All right, so in this example, we're gonna be using a small profile with two CPUs 8 gb of RAM and 200 gb of disk space. We're gonna connect the iOS or ISO.17:26With the CSSM on prem to the CDDVVD drive and work connect and power on. Now, your SSM on prem only supports your legacy BIOS mode for installations. If you must use the EFI for security reasons to install your applications, then it's not gonna be possible.17:42To install this SSCM.18:02We now need to review the options in the ready to complete screen, click finish, and then we're gonna go ahead and start the machine. Once the machine starts booting, you'll get an image much like this one, basically it's booting from the CD drive that we paid earlier.18:06And there's gonna be two options, test or install directly. Here we're just gonna go ahead and install. Now, as I mentioned, the on prem provides two profiles. We have standard and we have the this stig. Your standard, if you deselect this one, you're gonna be prompted with the default.18:24Send oS shell with the option to use the on prem console. Now, this profile provides basically the standard security features that are gonna be usually required by like normal organizations. Now, when you pick the stig.18:45You're gonna be placed into a whitelisted console, which is gonna prevent root access and limit you to using only the white listed console commands in the on prem console. Now, we select this security profile at the installation and if still compliance.19:03Is required. Now, it will need a host name and this will be the name that you basically give it. The next thing that we'll need to do is look up our IP address, gateway DNS server, and if you're going to do IPV six, you need to enable it here and then go ahead and fill out the values for your checklist.19:19Okay.19:39Alright, next it's going to ask for a password. Now the default password in the installation guide is gonna be capital Cisco capital admin, exclamation mark 2345. Now you're gonna want to choose her.19:42Choose one of these passwords that's gonna be relev relevant for you and I don't really recommend that you leave this as the default for your production environment, but once you change your password, just click ok. It's gonna take about 15 min to complete the installation from start to finish.20:01So, you can see setup is complete, took around 20 min. You can now log in. So let's take a look at how we're gonna set up the on prem now that we've got it installed.20:15Any questions moving forward? Does anybody have their hand raised? Can y'all see? I'm not available to view there right now. No, we're good to go Robert. Okay. Okay, so we got a setup checklist. So we did.20:32Reinstalled, now we need to actually set up our CSSL on prem.20:52So for our setup, obviously we've got to have the on prem server installed and running. We're gonna need a new password, alright, so we're gonna have to change our password that we just said. We're gonna know what language, we need a host name, we need access to our Cisco smart account and we need permissions to create a virtual account.20:56Now, in our browser, we're gonna type in the IP address of our on prem license server, a note here, you're gonna want to put the port 8443 to reach the user interface. Now the standard port 443 is gonna be used by the products for product registration.21:16So your products are gonna speak to your CSSM on prem, on prem through 443, we're gonna view the web UI through 48443.21:36Now the initial login password is not the password that you use during the installation. This is gonna be the user interface password, which is gonna be available in your user guide. So we're gonna enter the information, which is gonna be admin and then our password, Cisco admin.21:48XMH .2345. The 1st thing that you're gonna see when you get logged in is it's gonna be this four step process here. The 1st step is we're gonna check our language. Here we're selecting English. Next, we're going to change the password from the factory defaults.22:05Then we'll go ahead and confirm that. We'll add in our host name. Now you can do an IP address for your on prem server or if you're using a DNS server, you can actually enter your fully qualified domain name here. Now, last step, we're just gonna go ahead and verify our language.22:25Our password has been set and our host name.22:45Once we do this, it's basically gonna kick us out and make us log back in with our new password, so don't be, you know, alarmed if that happens as soon as you hit apply. Once we're logged in, you're gonna be presented with this licensing workspace. Now here.22:48Currently we don't have any accounts, so we're not able to reach the licensing workspace, which is where we would do all of our stuff like generate tokens, deliver a license, view any virtual accounts, anything like that. So the 1st thing we need to do is go to this admin workspace, which is gonna be in the top right.23:05Right, and this is where we're basically going to associate.23:25And start connecting ourself to one of our smart accounts, and you can see right here that smart licensing is blocked out right now because we don't have an account. Alright, on this admin side of this workspace, there's gonna be a number of options available here.23:29Some of these are gonna be access management for LDAP or Active directory. There'll be some security settings, you'll have the ability to create additional local users. You've got some system settings, you're able to enable APIs. Now, what we want to do.23:49Is we want to add an account, so you can see we've got this account blocked circled or cubed. This is where we'll go in here. We need to create a new account because we need to link an account to this. So click on new account.24:09Now, here we recommend that your account name mapped to your Cisco virtual account. So we have a virtual account called Cisco or account at Cisco called CSSM, alright? The Cisco smart account that we're going to use is CS demo lab.24:29For our virtual account name, really best practice is.24:48Just to use your local account name so that you don't get confused. So, you can just copy it as CSSM or you can create a new one called, you know, we here we're using demo SW lab, but it's really, you just want your virtual account to make sense to your company.24:52Then lastly we have to add the email, and this is a local indication of who created this account, so we don't use this email because it's not sent to Cisco. It is strictly for you to know who created.25:09This account. After that, we're gonna go ahead and hit submit. Then what we need to do is in our accounts tab, we move from account to account requests. You'll see our new request here. We'll go ahead and move to approve.25:28Right, it actually skipped a step there, but basically when you click approve, another box is gonna come up and you'll have to put in your your CCOID and basically authenticate that you are allowed to create.25:47And or allow this account to be created. So you'll need your CCOID and a password to confirm that the information is correct because you'll actually be basically approving this account to use that, that smart licensing or be attached to your smart account. All right, once you do the approval, it's gonna start an automatic synchronization.26:06You can see that this synchronization.26:25Right here. What this is doing is this is going ahead and saying, hey, we have this virtual account. I am now switching this virtual account with the smart account that you said, and this is all happening between our on prem and our actual, you know, cloud based server. So as soon as this is done synchronizing, if you log into your cloud based server, the one that's hosted.26:28Cisco and go under your smart account, you'll see this new virtual account.26:48Created. Alright, so now if we move to our licensing side of it, you'll actually be able to basically back out the admin portal and click on the licensing side and you'll be able to go in here and see that, hey, we have a.26:52On prem account. Alright, and as I mentioned, we now have access to it. So in our admin workspace or our our licensing workspace are on prem, you can actually get your tokens, you can pull your smart call home registration URL for connecting devices. You'll see what ports preference.27:10You actually better go ahead and do everything.27:30Like normal. Okay. Moving on to a CSSM upgrade. Any questions on setting up your on prem after the install? Okay, i'll move forward.27:33No hands up, guys.27:53No hands up, please feel free to raise your raise your hand if you if there are any questions. Thank you. Thank you, Bhavna. Okay, for the installation checklist or we can call the upgrade checklist, again, you're going to have your on prem installation guide for the correct version that you're using.27:55You're gonna need your user guide.28:15Your on prem release upgrade software, your, database backup, and your on prem snapshot. So let's take a look at how we're gonna get those. Now, your upgrade, like your install should meet the requirements based on the number of products you plan to license. Now requirements may change, so we want to look at the installation guide.28:17Every time.28:37Alright, so here's an example where our on prem is installed on a ESXi host. We need to verify the VM hardware from vSphere, or from the vSphere client to make sure it matches the on prem installation needs. Here is an example of us checking the on prem requirements from.28:44On the servers itself using the Linux command line interface.29:04Now you can find the backup and restore procedure in the on prem user guide. We do recommend checking because like I said, check steps can change. Now being on the server itself, we're on the server. We 1st run the on prem console command, we verify the current.29:12Version and then we're gonna run the database_backup. Now, when the backup is complete, we're gonna copy the file into your backup repository.29:32With the on prem running in a virtual environment, we may also want to take, a VM snapshot before proceeding with the upgrade. The snapshot we see on the slide is taken here from the vSphere client.29:44Then in the on prem console, we're gonna use the copy command to get the upgrade, image, and then we're gonna get the upgrade Shaw 02:56 files with the new version from your SCP server.30:05Into your current on prem server, and then we're gonna place the files into the patches folder. When we copy or when the copy is complete, we're gonna use the upgrade command specifying the path to the uploaded upgrade script, and then after the script has completed the up.30:22Upgrade takes about five to 15 min. You're gonna be notified that the process is complete. We're gonna reboot your system.30:41And then basically your update is gonna be complete. So here we're just confirming the new version. Also, once your reboot is complete and you've confirmed your new version, we need to perform a synchronization on the systems from the admin workspace.30:49And we can also confirm the on prem version here as well. You can see that in the top right corner. Alright, let's move into product registration. I think this is what people are gonna be the most interested in. So, as you probably know, registration is gonna be a one time process.31:08That needs to be completed in order to bring your devices into compliance.31:28Now this is done once the device is booted by obtaining a registration token from your CSSM. Once the token is obtained, it's gonna be used by device for registration and once the registration process is complete, the device communicates to the SSM in order to determine its compliance status.31:33And here we have the steps on how to register devices. We would need to verify or configure smart call home. We need to enable FCM on devices such as Cisco 8000, excuse me, not Cisco 8000. Your Cisco 9000 and your NCS 55 hundreds.31:54Your Cisco 8000 and your NCS five forties.32:14Have FCM enabled by default. Then we need to generate a registration token on your SSM or your on prem server and we're gonna use that token for registration. Now, it's it's really important to make sure that our calendars and time are correctly set on a router before connecting to our.32:18License server because shifting time after a registration may end the evaluation license.32:38Early or it could affect things because we're going off that timing a little bit. Now you'll also want to use DNS, so by default devices use spark call home infrastructure to communicate to your SSM by using tools.cisco.com. That's the DNS.32:47Last name, and tools.cisco.com can be pinged and in case your organ, you know, if your organization allows the ICMP to pass through, you can try pinging it, which is a great way to make sure that you are able to register or you're going to not run into any registration problems when you're doing a direct.33:06Or you can try Telnet to port 443, to make sure your transport path is ok. Now, tools.cisco.com is what you want to ping if you're trying to connect to, use a direct connect. You need to ping your DNS.33:26Name of your on prem server or the IP address if you're using the on prem server, obviously. Alright, another thing we need to check is the smart call home configuration. Now, if you're using the direct method.33:45Then the configurations are gonna be there at RSA, you know, call home destination, HTTP, and then that address. Because we're doing the on prem, we'll need to change that. Now, the call home is also where if you're using a VRF or a proxy, you'll need to add in some information there. So, under call home.34:01If you're using VRF, you'll have to say VRF and then the VRF neff name, and then you'll need to use a source interface to tell them where we source the interface from. Same thing with proxy, there's a command for a proxy, you put it right here under your call home.34:21If you're gonna use a proxy. Now, as I mentioned, for the devices connect to your on prem server, what we need to do is we need to delete this current address right here. So we have this destination URL, HTTP tools.cisco. This is what's gonna come by default. This is.34:32Pointing towards our web hosted service. So we don't want this if we're using it on prem. So we need to come in here and do a NO destination, so call home profile, Cisco tech is a profile that comes automatically. You can change this. Just make sure that you know.34:53Move all your configuration, make sure it's active and stuff like that. But profile Cisco tag-one. We're gonna do a NO destination address, we're gonna get rid of this one, and then we're gonna do destination address HTTP, and then this address right here, you will pull out of your on prem server. Don't try copying this, you might get something wrong. It's easier.35:07To just copy and paste it directly from your on prem server into here instead of trying to like hand type it.35:27Oh, this command here basically allows the acceptance of the smart license self generated certificates. And we want to add it to allow device to do get connection to our SSM on prem.35:35Now there are some variations of versions like this or commands like this, so this is not on every version, there's a couple of versions that is missing, but there are some other commands that do the exact same thing so you can accept that smart license.35:52Server or a certificate. Alright, so some platforms like your 8000 your NC five fortune, as I mentioned have FCM enabled by default, so this step right here is not gonna be needed.36:09Otherwise we need to activate FCM with the license smart flexible consumption enabled command, and we can verify with the show license platform summary, right here it indicates that it's being used for FCM. You can actually see that you're pulling FCM licenses. So remember license smart flexible consumption enabled, that would be new.36:25Used to own your like Cisco nine thousands or not your ASR nine thousands or.36:45Your NCS 55 hundreds. Alright, so newly booted or newly FCM configured devices would need to be or they're gonna be in the unregistered state and they can be in the unregistered state for 90 days, so this is basically your evaluation mode.36:52You can see that we're not connecting anything, we're in evaluation mode, we've got 90 days, so 89 days, 4 h 90 min. In this 90 days, there's NO repercussions. You can do upgrades, everything works as normal. After the 90 days, if you're not consumed licenses, you're going to.37:11Move into an out of compliance and then upgrades will be blocked. Alright, so regardless of your CSSM or your on prem, we're gonna go to the license management. We need to click the inventory tab, select the required virtual account and then click create new token. So.37:27This is how we register.37:46A device to a virtual account. So we'll go to the actual virtual account, click new token. Now you can add in a name or a description, you can say it expires up to 30 days or you can set this to like 999. Same thing with max usage. And you can just use this for you can set this up for whatever type of deployment you.37:48Going, you know, if you're doing a deployment where you know you're only gonna set up five licenses and you've got security concerns, you can set this up for, you know, only five uses so you're only gonna be able to register five devices.38:08Now once your token is created, we're gonna copy it and then use it for device registration. So we mentioned just go to copy here. Also, this is where I was saying you can get the URL. So when we change that URL from tools.cisco.com, you can just click smart call home registration URL copy this, and we'll use this in our devices.38:26So, this is where we're gonna use the token, license smart registered token or registered ID token, then this is our token. Once that in you'll get the license registration successful, and you'll see that it's changed from unregistered to register if everything went well.38:46To verify this, you're going to use the show license summary and it should say registered and then it should say your smart account and virtual account underneath that, and you'll see that in the demo. Now, once the device is registered, we can go to the SSM and then the device is going to appear under the products.39:05Tab. So if you go under inventory and then product instances, you'll see your device. This is where you get your token under the general tab. License to show you the license that you currently have in this virtual account. You see our virtual account is default. SCMD cloud is our smart license.39:24Her smart account excuse me. Okay, any questions before I start the demo? All right? Okay guys, so here's what we have. So this is the on prem server.39:39So, get logged in here. I've already installed it to bypass that product or process and I have set it up already, ok, let's.39:58Let's refresh that there we go. So when you 1st log in, this is the two different spaces we're talking about. We got our licensing space, which is gonna be blocked out until you actually register your account. Then you've got the admin.40:18Administration side.40:38You can see I've already got a smart account linked to this. All right? So when you 1st log in, this will be grayed out. We're gonna come over here to admin workspace. In admin workspace, we've got access management, accounts, network, API tools, security settings synchronization, support, and users.40:39As I mentioned, the 1st thing we need to do is go to accounts. So we need to create an account. So I created this virtual account expert CS demo or expert FCM. It's linked to CS demo labs, which is my smart account. Here's the virtual account, I just named the same to keep up with it.40:59To create a new account, you click new account, head in your name, test, your smart account, CS demo labs, test, and then your notification. I would submit this.41:18Move over to accounts and then actions approve. Once I approve this, I put in my username, and it'll be created on our web hosted service. Then it'll start the synchronization synchronization process. So if you come here.41:38Come to actions, you can deactivate it under account request, prove reject. Now, the next important thing that you want to do in this other than setup users is going to be the synchronization.41:54If we click on synchronization, I can select on all my different accounts and I can sync selected and click on it. I can get some general information account, but when it was registered last synchronization, synchronization date, you can check the event log.42:11But what you really want to do is go to schedules. You can choose to exclude any of these host name, IP or MAC address when sending data, but we want to set a synchronization only you want to set a frequency. So I recommend doing.42:31You know, about once every 30 days is usually pretty good. That keeps you, that keeps your license pretty in sync with our on prem server or our our hosted server because it.42:48Your on prem server and your in our hosted server get out of sync. You could be consuming licenses that you don't have that maybe have expired or you could be out of compliance because you haven't pulled in new licenses, so it's really good to go ahead and set the synchronization to make sure that the two are talking. So we go ahead and hit apply.43:08Now, with that, let's take our take a look at our licensing workspace. So smart licensing, if you've ever used our web hosted service, this should look very similar to you. So it should look.43:27Almost identical actually. We've got alerts, we've got our inventory, convert to smart licensing, we've got our reports, we've got our preferences, and we got our activity. So preferences, show license transaction details in inventory. We've got disabled reports, we've got the same reports that you can run off of your web hosted service.43:43We have alerts, and then we have inventory. Inventory is where you, if you remember, we can create our token. So I can create a new token, I can do a description, set to expire max number of uses.44:01And then I just create token. So you can see I already created this token here, actions, and I can copy it. And I got the smart call home registration URL, so this is where I get that for my call home. Now if we look here, you can see that I've already.44:19Connected to device. Let's check out licenses. No product cancels I mentioned that. So you can see we've already got a device connected. I've already connected the CAK. All right? Name, product. I'm not sending Mac address or host information.44:38We've got a serial number, licensings what we're consuming, we move to the licensing tab, you can see what we currently have. You can see that I am.44:58Good for my SIA essentials. I have four available to use, I am currently using four. I am out of compliance because I am consuming one more than I have of the hardware tracking and four more of the right to use. So.45:14If we had other virtual accounts, we could transfer a license from those or you could go to your software central. So this is our web hosted one, where we got CSSM, I could come here to another account and transfer license into this account.45:31So you won't really do much here because, oh, get that reloaded there.45:50You won't be able to do much here because this is a on prem one, so they want you to go match it off the on prem server. But you can move license around like this. So if I want SCM demo and say licenses, so I needed.46:06I know the license say I needed, one of these I've got 40. I could come in here, select on the license that I need, transfer, click virtual account, expert.46:23We'll transfer one transfer. Now we'll go back and forth to a synchronization real quick.46:39Give me just a second.47:17Okay, While that's pulling up.47:24Successful. Let's move back to our licensing workspace, inventory, licenses. You can now see that we have an additional license that we weren't using before. All right, so this is all good. Let's check out, check this out from the router side.47:30All right, so I'm in the right one here. So you can see this is the router we had connected. Ca K zero, we can verify that by coming to a product instances CaK0.47:52What I had to do to get this device registered is let's do a show call home profile because we had to change this. See where we changed that? It's now, it's NO longer.48:10Tools.cisco.com hits 198.18.34.33, which is the IP address of my on prem server. You can see it right here.thirty three. So that was the 1st thing we had to change. Then we did the license token, so we had to do license.48:26Smart register ID token, and then our token. Show license summary. Alright, so you can see that we are registered.48:46The smart account is expert SCM, virtual account is default. Now, we will both know that the, this reports a little differently because it's reporting to the SSM and the SSCM views.49:02For the SSM on prem views that virtual account expert FCM as a smart account because it's registered directly on that smart account, but we know it's a virtual account under another one. We're currently under virtual account defaults, so you could have multiple virtual accounts underneath this on your SSM on prem.49:17We have our functionality allowed, we are currently out of compliance and we're out of compliance because I am missing the license on these two. Now, why am I consuming these licenses? I'm consuming them because I have one port enabled? Show show brief.49:36You can see that I have this port enabled, that's why we're consuming license. If I went in to shut that down.49:54Oh, so it's gonna take a minute. Now, I did add an additional command in here to make this faster. So there is a command, it's called, here I'll just post it so everybody can see it.50:12Test license platform intervals collection one reporting one. So I've dropped everything all the reporting down to 1 min, so how often, you know, my router's update and reporting back to us this is him on prem, how fast it's doing this? This is great for testing purposes.50:30Because your normal is your collection 60 min and a hundred and 40 401444 reporting. So it's been about a minute, so this should have updated. So let's see. Let me try and force that.50:45There we go. Okay, you can also force with the smart.51:20Right renew all. Now you can see we're still out of compliance but we're not consuming any licenses.51:23Because we have NO ports open anymore for the IP, it's. Alright, any questions so far? Okay, so we've got a little bit of time left, so I'll go ahead and just.51:28Registered this other device here. So we never registered 2nd device.51:47So the 1st thing you do is you should run call home profile off. Alright, so.51:53So we need to change our profile, so see.52:13Okay, you do this other one too.52:33That's what I wanted there cause I want to take this out.52:54So we're gonna remove this and it's NO HTTP. Okay let's do show on.53:15Yeah, was it, is it HTTP? No, a destination address? That's what I was missing address.53:42HTTP. Okay cool. There we go. So we need NO destination address HTTP, and then we're gonna copy that old one, so we do not want this one anymore.53:56And we're going to paste our new one, so destination I don't know why I wanna keep starting that with HTTP address HTTP.54:18And let's get it from our home from server here, so back to journal copy.54:27And then license more register ID token, describe our token now.54:49Alright, you can now see that register is pending. Let's give it a second here let me drop the command back in here so it doesn'.55:12A little faster.55:24It's taking a minute.55:47Interesting. That should not have happened. Wonder if I missed this command.56:17Yeah, can you verify the reachability? Oh, ok. I might have forgotten that when I did the setup.56:24And then I fat fingered one of the show call home profiles.56:55Then we'll try, might just be acting out because it's a virtual.57:08Do you want to ping and verify.57:26Okay alright yeah we're having a little issue there. Okay, I actually troubleshoot this offline and see why that one's not working, but we'll jump back over here.57:41All right, so we've got one registered, we're having a little error on 2nd one here, but i'll troubleshoot that one offline. Are there any questions over the registration process? No hands up, nothing.57:58Robert, please go ahead. Okay, that's actually it for the demo presentation. If there's NO questions I'll go ahead and stop sharing here. Awesome.58:19Yeah, thank you guys for joining. If there's NO questions, just let us know if you got anything and I hand it back to you Bovna. Thank you Robert. Thank you everybody for joining today. This is this, this was 2nd session in the series. We have two more.58:36To go in this expert series. Thank you for taking the time to attend the session. If you have if you do have any follow up questions as we go forward, please reach out to please reach out to this email address and we will get you.58:55The help you would need. In addition to that we do have an a public facing community post community page where all these recordings will be updated. It should be available to you via email once you.59:16Once we disconnect this towards the end of the day, any, and thank you for taking the time again. I see you all next Wednesday at 1111 30 central time to to to to continue with this series. Thank you. Appreciate it.59:34All. Thank you to panelists and Robert for presenting today's topic.59:53