Transcript
Hello, and welcome to today's.00:13Expert insight series. This session will be on unified Edge Foundations, and this is part two, following part one that was last week. Now today we will have myself Joe Francis, and.00:17My fellow colleague Alan Clark doing a presentation and demonstration for our topic today. Now we will be using Slido for today's session. Here you've got a QR code on your screen to make it easy.00:34You want to scan that code with your mobile device and you should be able to get a URL to click on. Otherwise you can just open a web browser, go to slido.com, and use edge number two as both the join code and the passcode.00:52That is EDGE number two for those codes. Now as always we have some audience interaction, we would like to know where you are joining us for today.01:12Now this might be any part of the world, country city state, province, a living room couch, depending on the mood you're in, let us know where you're joining us from so that we can get a better gauge on our audience.01:31And we'll give everybody a minute to get connected, and start to type in here.01:53Now we've got a couple more questions coming, sprinkled throughout the presentation, so please get ready for those. Those able to use the the Webex app, you should have Slido pop out to the right.02:04Using the hamburger menu there, you should have some additional links that we put in there for more information that should make it easy to get to. I'll post the link.02:19Where the session series information is posted and from there you'll have the registration capability along with, the recordings as they get generated.02:37And posted live. So for our next question, we would like to know how you are managing your edge sites currently. If you can, please join us throw in an answer there, whether it's just an ad hoc.02:54Kind of as needed basis, different methods or if you're doing all of that centrally managed or if you've got folks out at your edge sites where they're doing that locally, you've got smart hands there so we've got.03:15A few answers here. Let me get those displayed for us. We can see how folks are answering that. Going down the list there also too, we've got some not managed, not needed at some head sites, maybe it's just personnel, maybe it's just a branch office where very little's done, you don't.03:35Need to provide any new services, but overall folks are responding there between ad hoc centrally managed, and it's like some sites at least have some local management going on, a little more now, so that's.03:55Excellent fantastic. Thanks for providing that information that will help guide our demonstration and presentation today so we can now have a better gauge on how your environment is at work.04:12Now for today's topic, we're gonna jump right in. This is part two again, as I said.04:33Part one was last week, and today we're gonna jump in and join how, how to build directly on the foundations we covered in part one, show you how they apply to fleet management at scale. One of the most exciting additions to our fleet management strategy.04:47Is the introduction of blueprints. You can think of these as templates for your edge deployments. They come preloaded with best practice configurations specifically designed for your workloads. Now this takes the guesswork out of the setup that you have to do.05:06And this blueprint approach offers three advantages for anyone managing edge environments. It gives you consistency at scale. Now this is where it ensures that whether you're deploying ten sites or thousand, every single one is considered identity.05:25Or configured dynamically. Secondly, it provides you with a golden configuration, allows you to establish a fleet wide standard golden config that ensures every device meets your specific security and performance requirements.05:45And thirdly, zero touch provisioning. Well, this is the ultimate goal with zero touch provisioning. You can ship hardware to a site, plug it in, and let the blueprint handle the rest automatically.06:06Hey Joe, I think we lost your audio.06:54Yeah me now? Yes, I can hear you now, thank you. Okay, great. Yeah, so now we're looking at edge management compared to data center management. The difference has really come down to two key fe.07:02Factors that we see here.07:22Now the scale looks different. In a data center, customers typically deploy hundreds or even thousands of devices. These are all with just a handful of locations. At the edge though that kind of flips, and we see customers deploy only a small number of devices.07:24But across hundreds or even thousands of locations, Instead of scaling vertically in one place, the edge is gonna scale horizontally across many places. Now the consistency is critical in edge environments, workloads and deployments are usually very cookie cutter.07:42Would you see at site one is the same as site two, site 50 and so on the site 500, and this repeatable or repeat about repeatability matters because there's rarely on site IT staff at these locations, but we saw with just our poll.08:02Kind of what scale might have on site smart hands. I think it was around a 3rd or so. Now if something goes wrong hover often needs to be swapped or configurations rebuilt in a way that's fast, consistent, and reliable.08:21Essentially it just has to work every time as we see here to address the edge management requirements.08:37The new suite of features that are being built into Intersight called Intersight fleet management. And this can be divided into three main themes. We've got our simplified onboarding and zero touch provisioning.08:56Considering that day zero to day one, next we've got our automated life cycle management, which would kind of be day in. And lastly, we've got our global visualization.09:13Blueprint, in inter site unified edge speak, the prescriptive setup for platforms and targets supported by intersight. The blueprints are gonna provide end users with an easy way to deploy and manage complex solutions on top of compute.09:42Networking and virtualization and containerized infrastructure. Now the blueprints meant to be simple, intuitive, and a painless way to deploy common solutions on top of data center and the edge infrastructure. By reducing the number of inputs needed.10:01Reference reduce friction and risk, making it easier for end users to deploy and manage solutions throughout their life cycle. Now here we can see the parameterization.10:19Of typical blueprint configurations. We see the blueprints made up a collection of parameterized policies, templates, and configuration files. Remember that? And that's gonna define the configuration for the blueprint.10:37Based on the best practices and expose those parameters that would require or be unique to your your particular deployment. Now there's two different types here. We've got static and dynamic. Static ones are gonna be parameters, they're gonna set by the actual designer of the blueprint.10:54And not exposed to the end user to be configured dynamically. Now the dynamic parameters on the other hand are gonna be defined as variables, again by the blueprint designer's posted the end user.11:13And these can be things such as a pre filled default value, NO default value, and a dynamically curated parameters, of course when the end user is going through, they'll, they'll see the pre filled value.11:30Or NO default value or the dynamic one is interesting because it can be acquired through API queries and might give you a recommended firmware version, e.g., from the hardware compatibility. Now the actual types of blueprints.11:48We see here, 1st we've got bare metal blueprints, which would be things such as server profiles pools, policies, and we've got compute node blueprints, where it's got the hardware plus the operating system configuration.12:10And that would include any hypervisors like VMware, Microsoft, Red Hat, Suse, and those type of deployments. Other types are gonna be supported.12:26Coming up, clustered infrastructure blueprints, which would be the operating system and the hardware blueprint coupled together along with a clustered operating environment configuration in your application blueprints.12:42It can be deployed on Vmiss based on infrastructure service, again your VMware, Nutanix, hyper V, Kubernetes, et cetera.12:58Yeah we see the compute node blueprints.13:18Curated, tested, and authorized by Cisco. These are gonna be available in a marketplace as options for your deployment, and they'll also be fully supported and maintained by Cisco.13:25Along with engineering and tech, we'll see we have our options where you can choose from, and the targets for that to deploy against, whether it's operating system, server profiles, and then your intended outcome.13:43Look at whether it's the operating system, the operating system configuration or the particular network settings for your unique environment. So the profile is gonna draw from pools, hardware policies, and network config, and those validators are gonna kick in.14:00And look at the hardware, the environment, the location, search through things such as these actual hardware PIDs, the CPU memory, different network interfaces. So look at your bandwidth.14:18And it's also going to check out the slot num slot numbers, chassis numbers, rack location, et cetera, and for the bare metal blueprints, again, that's things.14:33Right or profiles, rules policies, compute node blueprints, which would be the hardware blueprint plus the operating system and installation configuration of the blueprint types that are gonna be supported clustered infrastructure blueprints.14:53Where you'll have the cluster operating environment configured along with the operating system and hardware. You'll have application, blueprints, deploys a virtual machine or a containerized solution.15:14Again your VMware, Nutanix, hyper V, Kubernetes et cetera, for the workload definition?15:30The workload definition is gonna be collection or configuration of one of the one or more blueprints coupled with the user defined parameters that will be used as a golden configuration will be deployed and life cycle managed to your infrastructure across the fleet.15:58Of a settings and workflow definition include platform configuration where your configuration details you use for shared infrastructure across multiple blue group multiple blueprints within a single workload definition. So you have your system configuration.16:16How your switchboards, your DNS, NTP quality of service or QoS, owns your VLANs, your IMC access, etc. Local users, and then the operating.16:32Settings or that'll be your, your LDAP, your syslog, SNMP et cetera. Now for customers looking for granular R back or role role based access control.16:50There's gonna be resource distribution across orgs that you've set up in their site, they can keep the workload definitions in the source org, they can be managed by your global admin or the workload deployments themselves and other resources can be deployed as part of the consumer org.17:09And be managed by regional admins for best practices. Now the settings that are available in a workload definition, again, you've got your blueprints, you have supplied values or the dynamic variables exposed.17:27Like each blueprint.17:47You have your platform config, which will be your shared infrastructure used across multiple blueprints, that system config will be again your DNS, NDP QoS, et cetera. Optional settings.17:49Again your LDAP, syslog, SNMP, and the overrides for the parameters, the ability for an end user to select which parameters set to be overridable, region or locale.18:07Giving you excellent customization of your environment.18:23Now we'll take a look at day zero zero touch provi provisioning, gonna be a derivation of workload definitions, used to create, deploy, and manage the life cycle of the resources that you're managing.18:39And with the workload deployment, you can specify unique configuration parameters that are able to override the the locale or actually be applied per locale. That'll give you localized maintenance windows.18:57We'll see more on that in our upcoming demo by Alan, and you'll create qualification criteria that's gonna automatically match resources that are able to deploy. Now again for that.19:13You do have or you do not have the ability to change affiliation to another workload definition, and you can create those in consumer orgs that are tied to your definition source org.19:33Now for the settings that you'll have in a workload deployment, you'll be able to schedule policy.19:53You'll have a strategy around your rollout, where you'll be able to do batch and canary operations for the policy, you'll have the collections or one or more single instances for the windows.19:59They're gonna define the available windows for your maintenance, again more on that in our demo. For the actual strategy itself on doing the rollout, you'll be able to deploy new workload instances or apply updates to existing workload instances.20:15For your batches, you'll be able to have operations scheduled and executed concurrently during the scheduled maintenance windows and for the canary operations, having exponentially increasing scale, 11050a hundred.20:35So who has your confidence increases during the scheduled maintenance window, you'll be able to roll that out into larger and larger batches and you will have the ability to qualify the resources.20:54Are being targeted. We want to make sure that those match resources within a consumer org. And lastly, you'll be able to override parameter values. Those that are marked as overridable.21:09As you see, they'll be exposed to allow for localized overrides in case you have a one off condition at a branch, Otherwise have values will be shown as read only.21:29And here we're moving down to review and deploy.21:49For our zero touch provisioning and we'll see you've got a unique instance of a workload deployed to a resource on premise with your golden configuration will be automatically.21:53Created and utilized resources.22:14That are selectable from those available within the organization that you're rolling that out in and you have to operate within the constraints as defined in the blueprint from the blueprint owner, and the objects such as server files and policies will be created automatically.22:17Under source blueprint configs as read only moving on to deploy consistency anywhere.22:38That aspect of inter site unified Edge allow you to combine one or more blueprints together to deploy the entire site's infrastructure. As you see in the top left here, my borner there.22:54In our top left, we've got Cisco intersight. Beneath that your full stack automation, with your compute, your cluster blueprint, and your app blueprint, and then for your small branches.23:10You've got all your settings, options and parameters, and to break those out, you'll be able to use America's US West, US East, and then there is an inter site instance in Europe, specifically in Germany, if you weren't aware.23:26And that will be available to you as well. As you can see, you'll have a global admin and you'll also have regional admin. Just be aware of the differences there. The global admin is gonna pick the actual blueprints used in the workload definition.23:43And the regional admin will be able to override specific parameters that might be specific to that particular region and bring out our map.24:02So that we can see the actual deployment zones there. You can see US West, you can see US East, and then the European deployment in Germany.24:22Once those workloads are deployed, configured and life cycle managed together, we give it a workload definition. E.g. branch_small or whatever makes sense in your particular naming environment.24:41Let's move on to day two, which would be deployment at scale. Get that, there we go.25:01Now we've got our graphical representation, your servers spread throughout North America, e.g.. So here we see you got in this case a large global organization ready for deployment via blueprints, going to sites across different regions.25:20For the global admin, be able to identify which designated configuration and constraints of the workload are defined and can be modified or or overridgen.25:41By the regional admins. So you, e.g., you might have a regional admin for one country or another and actually even a region.25:52A particular country, whether it's east or west, might be able to go in and override different configuration parameters or just something differently if that's needed.26:09Now if we also take a look at day two.26:29For the automated upgrades and conformance tracking, see that the workload definitions are versioned, so during creation, your workload definitions can be saved with a one.26:32Or set as something preferred. Any change post creation will require saving with a new version and administrators can choose if the new to saved version is set as preferred. The actual workload deployments.26:49You can either reference a specified version or enable an option or maintain preferred version of a certain workload definition. Now if you choose to maintain preferred version.27:05Then all of the definitions will be from a single source of truth for applying the configuration for workload instances despite where that is in your fleet. And changes are executed on workload instances based on the workload deployments.27:21Schedule policy and rollout policy, which I'm sure we'll see more of in our demo make a whole lot more sense there. Now the user will get to choose the actual rollout strategy as far as how it.27:38It's defined for the workload deployments versus how they apply updates to existing workload instances. And the failure threshold, it's fixed at 10 %.27:54At FCS and for batches, the operations scheduled or the operations are scheduled and executed concurrently during the scheduled maintenance window, and that's the canary, as we mentioned before, you can start at one, you can go up to 1050a hundred, whatever.28:11Whatever that does, build your confidence, and therefore you can increase your scheduled maintenance windows. Now if we wanna look at versioning with particular workloads, as we saw before, you can use numerical versioning.28:31And when you create those, you can, you can set that actual number or set it as preferred. And once you go in and change that post creation, it will require a new version number that can be set automatically.28:50Or can be preferred. Now if you want to maintain that preferred version, this can be the same source of truth for applying configurations for workload instances.29:10And that'll be per your scheduled policy and rollout strategy. Now for day two, location based global dashboards will be available.29:30You'll be easily observable and remediate issues across the scale of thousands of systems. If you overlay options of health, conformance, and deployment cycle, you switch context as needed.29:48Also give you cross domain visibility into upstream networking health via Catalyst Center.30:04We'll look at geolocations.30:28These can provide you with the ability to set a point on a map for your locations of objects within your inter site objects like your chassis, servers, targets.30:31Fis, it can be added either one at a time or you can upload this in bulk via a CSV file. You'll need to provide the name, location, and set a tag for it.30:49Okay, the name can be in line with your naming conventions, kind of a, it'll be a friendly name. Location could be DPS coordinates.31:05Or different type of address and for the tags there, you'll be able to specify to be auto added or on a target whenever a geolocation is being utilized.31:21And those geolocations can be propagated on your parent objects down to the child objects that they are managed under. So e.g., you're gonna apply a geolocation to an object called SJCO two in a chassis that's named food 123.31:42So therefore, all the compute nodes that are within that chassis will have that geolocation auto applied to them as far as path tags go, take a look at the screenshots there.32:00Where you'll see the path tags, be able to drill down, you need to rename those as possible, actually even add a sub tag. Since those are drill downable, you'll see their hierarchical.32:19And allow you to organize your resources based on your business aware boundaries. When you create a tag, you do only want to use the key tag value, go down to.32:37Maximum of five levels, you'll be able to rename it any level where that hierarchy is supported, and it's gonna propagate that tag apply it to a parent object down to any child objects.32:53So for in the example here we see we've got the global America US San Jose, down to the actual chassis there. So any servers in that chassis are going to inherit those tags. As far as tag.33:15Management goes, you'll be able to view those tagged objects as a sortable, you should have a widget there that you can expose or collapse. That's just part of a basic inter site navigation, but you should have a clickable.33:35View to hide or expose that widget. Both those filters in that search box might be your friend or finding your particular tagged objects. Again make sure that the.33:56RBAC or role based access control privileges are in place to allow you to view those tags. Now at this point we're gonna have a Slido question that's available.34:16We get that started up. We'll see if you are able to just let us know what kind of services you're providing at your edge locations, could be file sharing, could be just basic DNS DCP.34:35Services could be an AI application. It could be anything like that did you forecast your company's gonna need, please let us know what you want to have.34:52Provided at your edge locations in the future, that's gonna be important. See, we've got a couple of responses so far. Let's see if we can bring these up and share these right before we move into.35:07Our demo with Alan, get this shared out here so we can see that from our respondents, we've got video monitoring, physical security, point of sale.35:26That's somebody providing desktop services at the remote branch, some common, some uncommon. We appreciate your feedback. Thank you. That'll help guide our actual.35:46Demo coming up, get ready to pass it over to Alan here in a second. And if you're ready Alan, we'll pass it over to you for a demo. Take it away Alan. All right, thank you very much Joe. Give me 1 s. I'll get my screen shared out here.36:06So I'm actually gonna start here with our inter site dashboard real quick to just show you what we've got here. We've got 22 XE servers, those are those unified edges, and then from here, just to show you how we've got those currently configured.36:24You can see here I actually have one of our unified edge already set up with a workload, we'll use that later on in the demo. Our other ten are waiting to be configured. We've assigned locations to to nine out of our eleven. So what our 1st steps actually gonna be is fixing the locations for our San Francisco and San Jose locations.36:40But 1st I wanted to show you that, you know, before we do that, there are NO tags here on our chassis, and if we go into the inventory and look at our two, oh, sorry, that's the ECMC I wanted to grab the server, my, my mistake. If we go into our servers, there's also NO tags currently on the server.37:01So we are gonna start by going over here to our system, going to locations. Actually, let me go to tags 1st. We can see here we've set up a tag, global Americas, US and we've got Central and East with San Jose and.37:19Said for him we're gonna want to add a new tag. So we're gonna add our West coast tag, so global, so I'm gonna go ahead and create that tag.37:38And now we see that we've created this tag underneath our hierarchy, but we don't have any locations assigned to it Pardon me. So now that we've got our tag in there, we're gonna go add our locations.37:58So we've got our 1st nine locations. I need to add my two new stores, so click add location, now we can add a single location, you can fill out this form, name, address, city, region, you know, country, postcode GPS coordinates or.38:16If we're doing multiples, we can do this via CSV file. So I'm gonna go ahead and browse my CSV file in case you're curious to what this one looks like for our two west coast locations. It's just a standard CSV file, so we've got all of our headers for those boxes you saw in the 1st one up here at the top.38:34And then our two locations defined below, I'm gonna go ahead and add that and it adds my two new locations, so I'm gonna verify my information here is correct and click add.38:53So we can see here that we've now got our San Jose location has been added. We're only showing ten to a screen so expand to 25 so we now see San Francisco as well. So now that we've got these locations.39:19We're gonna wanna go ahead and set the tags. So I'm gonna edit San Jose and I'm gonna come in here and.39:37And when I start typing I'll actually see it filled out global west, save, and then we'll go in here to San Francisco and do the same thing.39:56And now if I scroll over here to the side, I'll see my tags are populated here for the west. If I go over here to tags and I expand this back out, I'll now see that I have two locations that are used for this tag.40:15Now I need to associate with associate that with those chassis. So we're gonna go over here to operate and we're going to our unified Edge systems. We come down here to San Francisco and we're gonna set its location. Now I'll get a full list of all my locations that are here right now. I'm just gonna start typing.40:34Grabbed San Francisco, and we'll get San Jose. And so now we've got those tagged properly, and we'll see that when we go into these chassis.40:56They've now got that location tag. If I check the inventory and go down to the servers that are associated with these chassis, they're now also gonna have that location tag right there and its address is set, so we now know where this is sitting. So we now.41:11Quickly set up our locations, we've got everything going here. We're really curious about where it is. This map is incredibly zoomed in, so it'll even show us, you know, we put our GPS locations, it'll show us exactly where that's sitting here in the US.41:29So we're now ready, we've got all our locations set up, all our stores configured properly. We're gonna create our workload definitions. So we are gonna go over here to configure workloads. I'm gonna it's a little bit smaller. You can see my existing workload that I've configured for my upgrade demo here.41:45On our, one server if we mouse over here, we've got one deployed. But we're gonna go ahead and create a new definition call it work definition.42:04And then we're gonna select our blueprint. So for today's demo, we're gonna be using our bare metal servers. But before I do that, I just want to show you one thing with if you had selected say a Ubutu or red Hat server just to show the difference real quick.42:23So 1st we're gonna do this. The main difference here is that if you select that OS, it adds this OS configurations option here. And through there you would select your OS version, say Red X96 or ten. And then you would point it specifically to your existing ISO images that you had ready to go that were configured.42:38As a software in your software repository for inter site same with the SCU image, but for today's today's demo we're just gonna do a bare metal, so we're not gonna do the pre staged OS. I'm gonna back this up. We're just gonna run through bare metal.42:58If you needed to do a mix, by the way, so if you wanted to do two bare metals, a Windows box and a Red hat box, you could set that up as well. You'll see here that as we change these, it just changes what servers we need to configure. So I'm gonna configure my bare metal server one.43:17I'm gonna select the firmware version, so we've got six oh here, I need to provide some VLANs for this. So this is server one, so it's gonna be on VLAN ten. Give me 1 s.43:36So we've got VLAN ten here configured for server one and we're gonna set our constraints. I want bare metal server one to be the server in slot one. I'm gonna go over here to server two and we're gonna do something very similar, we're gonna.44:05Give the firmware version. Server two is gonna run by we'll call it our VDI environment and server one's doing our our cameras of physical security. So we're gonna put that on a different VLAN, we're gonna put it on VLAN 20.44:23And constraints, we're gonna want this to be our server in slot two on the chassis. Then we need to do our system configuration, so this is our overall high bed system, so we're gonna select that IP pool.44:41I'm gonna create RI people here. We're gonna call it unified Edge IMZ access pool.44:59Get our subnet mask, our gateway, our DMS server, and then we'll add a block of IP addresses that we can use to assign to our servers.45:17Or yeah for so we'll start one three and I've got two servers times ten locations, so I'm gonna go ahead and make a pool of 20, so that way I have enough for everybody.45:36We're not gonna configure IPV six today. We'll go ahead and create our server pool. Okay, now that's assigned and we're gonna put that in our management VLAN and we're gonna call our management VLAN we'll go VLAN 30 today.45:56And we need our infrastructure bundles. These are gonna be for the chassis, the ecmcs. We'll select that. We're gonna create a local user policy, we could just select one if we've got one already created. We're gonna call this our unified edge.46:13Local user policy we'll, we'll go ahead and leave it on forced strong password, password history of five, and then we're gonna create our new user, we're actually just gonna recreate our admin user here.46:32We're gonna give it an admin role, we're gonna give it a strong password and we're gonna hope I type both of those the same.46:53We're gonna hit create. Then we're gonna select that as our policy here. We have our ECMC password, so this is gonna be the admin user for those ecmcs.47:09We're gonna set that there, put that there. We need DNS, so we're gonna We we set DNS for SIMC, now we need to set DNS for the chassis. We're gonna go ahead and put our DNS back in.47:30Switch control, we can do default, we can do custom, so this is just your Mac address aging table, we're gonna leave it at 300 so which is the default. We were gonna enable jumbo frames it's kind of up to you up links from the ECMC, so here's where you would set whether you want to use a single uplink or you want to do.47:46Two two links in a port channel as part of your uplink for our purposes, we're gonna do two ports, we're gonna have that port channel enabled and you can see here that's grayed out because it's kind of the default option if you used to we're gonna let it go to speed auto.48:06And now we need to add the VLANs we need on those uplinks. So the old prefix VLANs, and then we need the VLANs ten and 20 for our servers and 30 for our out of band management. So we will add those.48:23If you need to add VLANs that are completely contained within the cluster, so if you're just doing service server traffic, it doesn't need to go to the uplink, you would use the auto allow on cluster links as opposed to the auto allow on uplinks here. So you can create one set of VLANs for leaving the, for going out of the fabric or unified edge.48:39And you can create a second set of VLANs that are all used internally with unified edge. We'll add those, we'll click next. And now we have our optional policies. So if we wanted to set up system QoS, SNMP or NTB servers, we could set all those here.48:58We're just gonna kind of skip over this for now because we don't really need these for showing the fleet management piece. But I do highly encourage everyone to to set at least NTP servers when they're doing this in a real production environment just to keep your clock synced. And then we'll have our summary, we can kind of review our config, so ok blade one.49:17One VLAN 10.2 VLAN 20. Management is on VLAN 30, and carrying all those upstream, we've got our VLANs configured, everything's good, we'll create and validate. We did everything right, we'll get our green check mark definition is validated.49:37That's what we're really after here. The next thing we're gonna do is really gonna kind of create our deployments. You can click that and it'll go straight into the wizard, but for now I'm actually gonna do this from from start. So we go over to configuration, workloads.49:56And then we're gonna do configuration workloads, create a definition, and we're gonna define kind of what's going on with our our different workloads that we're gonna call this sorry NO wait. I already did the.50:13Definitions, we're gonna create deployments.50:32I do apologize, so we need our store definition, action, create deployments. And we're gonna do multiple deployments because we want to set up all of these stores at once.50:35So we adhere, deployment name, the US East.50:54Give US central deployment, and I just realized I cannot spell the word deployment.51:19And that'll be our central standard and then we'll have US.51:34So we now have all three of our different deployments that we're gonna do, one for each of our time zones, and we're gonna click create and it's gonna take it a little bit and we go over here to deployments now, we should see these starting to be built. We now have our drafts.51:55So we're gonna go over here and we're gonna grab US East, have our configuration matches up, we have our instance, NO instances yet, so we'll get to that in a second.52:18So let's go ahead and edit our east deployment. So we've got US East, got all this over here.52:41Now going down here for resource qualifications, and I want to add a rule, and I want to say, I want to do this where the location for the path tag equals US East, and.52:59Where my location, and this is just because we we have our RTP one kind of set up by itself, not RTP. Next, and then it's gonna say, ok, what instance configuration you want? This is gonna be our 1st one. So this is gonna be our 1st instance.53:17Summary and definition, we're still good here. Everything was what we want to see. We're gonna go ahead and validate. We're gonna prepare to deploy. Okay, we're still resource pool evaluations and process, so click through a little quick there.53:36There it goes. So now we are ready to deploy our four sites. So our four sites have already moved into staging for US East. So if we click here again, we're now gonna see that we've picked up our locations here on the map.54:00If we zoom in here, we'll see which ones are exactly where they're and they are ready to deploy. So we're ready to deploy at this store, ready to deploy here, and we'll see our instances and we can actually see which definitions we're attached to when we're on the definitions. This is Fulton, Georgia.54:19New York, Atlanta and DC, action, deploy. So do we wanna do batch or canary? We're gonna do batch today. We're just doing our initial deployment, so we're gonna go ahead and let it deploy all four of these. And now this is successfully deployed to our US East locations.54:39While that's going, I'm gonna go ahead and quickly grab our West location and just set our definitions there as well, at our group.54:59That type equals west. I'm still clicking through a little too fast here, so.55:19There it goes, and then we'll grab, we'll go ahead and start the deployment here still validate it, ok? Deploy.55:38And then for central, we are gonna, one more time, go ahead and quickly edit.55:55We're just gonna give that a second here, then we'll prepare to deploy and we'll start deploying. So we've now got in that time, all ten of our locations, so it's ten unified edge chassis, it's 20 servers.56:14All already in the process of deployment. We can track that standard for UCS through here or for inter site we can see our in process deployments pop in and out. This normally takes some time. It's about 15 or 20 min.56:33So while that's going on, I want to go ahead and show you what's gonna be like if you need to do an update or a change. So that's what we've got our little upgrade set up here for. So this has already been deployed here for our RTP location, but let's say I needed to do an update. So I'm gonna go ahead and edit.56:50And we need to change the configuration on bare metal server too. We'll we'll we'll we'll say that. So we know this is what our deployment looks like, but now, now I need to change my instance, so.57:09Let's go to workloads, definitions.57:25We'll go to our, we'll see our store definitions here slowly getting deployed, they're in progress, our demo upgrade, however, this out so we can see a little better. Our demo update is ready, so we'll go into our demo update.57:40And we'll go to manage versions, and we'll create a new version. So we're gonna create version four now. You can see a couple of previous versions here where I was making changes. And we're going to bare metal server one. We're gonna add a VLAN, so we're, we're adding VLAN eleven.57:59Next 01:40 just to stay with our theme. So we now add VLAN 40 here because we need to add a new VLAN. We'll click next. We only need to add it to that server. Check our summary, we'll create and validate, so this is gonna validate our changes.58:21Set this as our new preferred version and then we can batch roll it out. So I hit save, we're ready to go. It's gonna roll out our strategy cause I'm set on to just kind of roll it out here. So this has been updated.58:41And so if I go over here, what I should see, it might show take a minute to show up, there's just a lot going on in here right now. You should see the changes show up, so there's our upgrade deployment starting to work right now, so.58:59We're now starting to make the change for that one to add that extra VLAN, so we're just gonna go and close this. What we should now see if we go back to workloads is, well we see it's more store definition deployment show up our demo update.59:20So we're now at version four. It's an in progress update for that one, but otherwise we are healthy and good to go. Am i confus.59:42Configuration now reflects that I've added that VLAN 40. So we are good here. Now, if you wanted to make a different type of change, let's say you do want to make these changes, but you don't want to make them immediately. We're going to our store definition. We're going to instances.59:59We're gonna go to manage versions. So we have one is our preferred version right now. They wanted to add that change to everything else. So I'm gonna create, we'll go down here to bare metal server two. Oh, too fast.01:00:19And I'm gonna add VLAN 40. But I don't want this affected big change for everything right away. RTP is my test store, but everything else I really want to do after hours. So before I do that, I'm gonna actually cancel out right here.01:00:36Yep, and I'm going to go back into my workloads. I'm gonna go over to my deployments and I'm gonna go into what's, we'll just do the east coast one for today. I'm gonna make a quick change here. I'm gonna edit this. I'm gonna go into the scheduled maintenance.01:00:55And I'm gonna set up a scheduled maintenance policy for my East Coast server, so I'm gonna create a policy. We are gonna call it, what do you want? Schedule.01:01:13Does not let this space there. We're gonna click next. Then we're gonna add our time zone here. So this is.01:01:34New York, gives me your US East, and then I'm gonna add a schedule schedule Schedule name.01:01:52I'm gonna set my start time to 08:00 P.M. and I'm gonna set it to Friday. I want this to happen Fridays at eight. I'm gonna set my maintenance window for 8 h, so that gets still.01:02:194aM the next morning.01:02:35Under repeats, I'm gonna ensure that this maintenance window can repeat, so we're gonna do our cadence of we'll say a monthly maintenance window, we can pick which week, 1st week, day of the month, last day of the month, what have you, we'll do.01:02:39The 1st week of the month on a Friday, every month. We can never ends, we always have this maintenance window maximum threshold of failure is set to one. And what this means is the number of consecutive failures that happens before we just suspend that operation. We don't try to keep pushing the change through.01:02:57So we're gonna add that, and then this is gonna be our schedule, which means when I go to make changes now, I can stage my change and have it go on my schedule versus immediate, Invalid monthly option.01:03:17Week hopefully, every week on Friday. So we'll do it every Friday, now we select that policy. So this is now my scheduled policy. So my.01:03:38Maintenance window my changes happen on this server.01:03:57On Fridays at 08:00 P.M. last for 8 h, I can go back and create the same thing under central for central based on its time zone for the west based on its time zone. And then when I do make changes, my changes now go through on my schedule versus immediate.01:04:00And we can see here it's still taking a little bit of time for these deploy three of them have deployed on the central, one's done on west. East has finished this deployment, my upgrade is still going. So we can see here that you have the ability to make changes on a large scale, we can deploy at a large scale, we can schedule our updates so we don't have to.01:04:17Didn't necessarily wait until we're in the maintenance window to do our configurations.01:04:37This is kind of the way we really want to manage a large and distributed infrastructure. So that is kind of everything I had to show on my demo. Joe I'm gonna go ahead and hand it over back to you. I think you had a few more slides and some stuff to close this out here today. Excellent, great. Thanks a lot Adam.01:04:43And yes, for our audience, we do have another slide part of the presentation. Let me get that shared out. We will take a look at it together around our key takeaways for today.01:05:01Just a quick review. Again, the excellent demo, Alan. Thank you very much for that. I learned a lot myself. But for our audience, we want to come away.01:05:16With a reminder that the simplified onboarding and zero touch provisioning part of the inter site fleet management strategy has implemented in your current inter site infrastructure, as we saw During this demo.01:05:30It will appear there once you claim those targets. Now the blueprints will help you deliver consistent repeatable policies and profiles.01:05:46To your deployments across your various sites at the edge. And the zero touch provisioning is gonna help accelerate your large scale rollouts. Now the life cycle management, as was covered is automated and it's gonna help you with config versioning for your performance tracking, your.01:06:03Localized maintenance windows as Alan covered there that at the end to assist with your global automated upgrades.01:06:23And you'll be able to have customized rollout strategies to help you maximize uptime, even based on local dependencies. Now the visualization, as we see here, and as we saw.01:06:31In screenshots, now it's demo is global and the map view is gonna help you to instantly identify and resolve issues across thousands of systems if you deployed that many. Again, you've got your red, yellow, green color coding there to help catch your eye.01:06:47And address those items that are more urgent than others. And it's also geolocation that is shown. You'll have path tags that'll be searchable to assist with your organization and your business aware resource views.01:07:05Now we do have time for a few minutes of Q and A If you have some questions there, as Mohammed said, please put those in Slido so that our moderators standing by can assist in answering those questions for you.01:07:23Now I do have a few links that will be helpful and handy for you. I'm going to put those in our chat. Let me get there.01:07:42And send those out. The recordings for this session, in this series along with the other sessions in this series will be available at that bottom link there that I put in chat also the ability to register for the upcoming sessions.01:08:03Still left in this series, quick review of any questions that we have. I don't see any yet. Please do visit and join the Cisco community at that 1st link.01:08:22That's where you will be able to find and locate a community of like minded Cisco users for this environment along with partners and communicate around life cycle provisioning time.01:08:37Guidance, answers.01:08:57And get some deep engagements as part of a holistic digital experience. Now we do have a survey coming up as well. Let me get that kicked off for you if you're using the Webex client, that should pop up automatically. Again, those same links I put in chat are available.01:08:59Mobile in the Webex client through that hamburger menu in the top left corner.01:09:19But if you can, please take a moment now and fill out our survey that will help with our future presentations and demonstrations to maybe just give us a quick rating there at the very least.01:09:25And let us know what you think. We'll give everybody a few minutes to get connected and participate in that survey or ask questions as needed.01:09:40All right, so we've got some survey responses coming in.01:10:16Thank you for that rating, those who haven't had time yet, please give us, please give us yours. No chat in the official Webex window, don't see any questions there yet. There's something in chat around post OS install and script instructions.01:10:20API for non programmers et cetera, API docs. Now, I know personally there's if you go to inter site.com and you visit the help center there, there's a link down at the bottom.01:10:39And then navigate to, I think it's ABI docs down at the bottom again on the actual help page. You should find find some of the information that you're looking at there. I don't know if any of the moderators have a direct link for that. They want to throw in the channel.01:10:55Again, we've got even more votes and survey feedback coming in. Thank you kindly for the time you take there. Give everybody another minute or two to ask questions that they have them.01:11:11Oh, see even more feedback coming in to our survey. Thank you again for that. No questions at this point. So we'll look to close in a minute here. We appreciate everybody's time and attention for joining today, all the responses that you gave for our polls.01:12:19I threw a link in there to the API docs available through Cisco intersight. Hopefully that helps. You can reply in in Slido or chat there if that's what you were looking for.01:12:38Otherwise, catch the recording of session one. There maybe some answers in that session in case you missed it. The recording should come at the link above in the chat for the recordings.01:12:54Again, we've got NO more questions from our audience attendees. Thank you for your poll participation. And again, this was the unified Edge Foundations, part number two from our expert insight series.01:13:26Thank you for your time today.01:13:42
About this Video
Author : Cisco Customer Success
Uploaded : October 13, 2026
See how Cisco Intersight Unified Edge streamlines Fleet Management with Blueprints, Zero Touch Provisioning, Workload Definitions, and global dashboards. The recording shows creating geolocations and path tags, building parameterized Blueprints, validating configurations, and deploying consistent edge sites across regions using batch and canary strategies. It also details Automated Lifecycle Management, versioning with preferred versions, and localized maintenance windows, plus visibility with Catalyst Center.
Internal error
No related resources available.